u-blox cellular modules
Data and voice modules
AT commands manual

Abstract
Description of standard and proprietary AT commands used with u-blox
cellular modules.

UBX-13002752 - R67

www.u-blox.com

u-blox cellular modules - AT commands manual

Document Information
Title

u-blox cellular modules

Subtitle

Data and voice modules

Document type

AT commands manual

Document number

UBX-13002752

Revision and date

R67

07-Aug-2020

Disclosure restriction

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 mostrecent 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.
UBX-13002752 - R67

Page 2 of 1001

u-blox cellular modules - AT commands manual

Preface
Applicable productsThis document applies to the following products:
Name
LARA-R202

Type number
LARA-R202-02B-00

Modem version
30.42

Application version
A01.00

PCN reference
UBX-17057959

LARA-R202-02B-01

30.42

A01.01UBX-18018067

LARA-R202-02B-02

30.42

A01.02

UBX-18057549

LARA-R202-02B-03

30.44

A01.02

UBX-19011731

LARA-R202-82B-00
LARA-R203-02B-00

30.53
30.39

A01.03
A01.00UBX-19043497
UBX-17048311

LARA-R203-02B-01

30.39

A01.02

UBX-18018067

LARA-R203-02B-02

30.39

A01.03

UBX-18057549

LARA-R203-02B-03

30.41

A01.03

UBX-19011731

LARA-R203-02B-34
LARA-R204-02B-00

30.54
31.34

A01.00
A01.00UBX-19056532
UBX-17012269

LARA-R204-02B-01

31.35

A01.03

UBX-18013471

LARA-R204-02B-02
LARA-R211-02B-00
LARA-R211-02B-01
LARA-R211-02B-02
LARA-R211-02B-03
LARA-R220-62B-00

31.40
30.31
30.49
30.49
30.49
30.44

A01.00
A01.00
A01.01
A01.02
A01.05
A01.03

UBX-18046834
UBX-17012270
UBX-17054295
UBX-18057549
UBX-20012865
UBX-17061668

LARA-R220-62B-01

30.44

A01.04UBX-18050698

LARA-R220-62B-02

30.44

A01.05UBX-18057549

LARA-R220-62B-03
LARA-R280-02B-00

30.44
30.43

A01.07
A01.01UBX-19029271
UBX-17063950

LARA-R280-02B-01

30.43

A01.02

UBX-18018067

LARA-R280-02B-02

30.43

A01.03

UBX-18052020

LARA-R280-02B-03

30.43

A01.04UBX-18057549

LARA-R280-02B-04
LEON-G100-06S-02

30.43
07.60.17

A01.06

UBX-19029271
UBX-13005361

LEON-G100-07S-01

07.92

UBX-13005361

LEON-G100-08S-01
LISA-U100-01S-00
LISA-U110-01S-00

07.92
11.40
11.40

UBX-13005361
UBX-TN-12008
UBX-TN-12008

LISA-U110-50S-00

11.46

UBX-TN-12081

LISA-U120

LISA-U110-60S-00
LISA-U120-01S-00

11.43
11.40

UBX-TN-12050
UBX-TN-12008

LISA-U130

LISA-U120-01S-01
LISA-U130-01S-00

11.50
11.40

UBX-13002821
UBX-TN-12008

LISA-U200

LISA-U130-60S-00
LISA-U200-00S-00

11.43
21.21

-

UBX-TN-12050
UBX-TN-12009

LISA-U200-01S-00

22.40

-

UBX-TN-12040

LISA-U200-01S-01

22.40

A01.00UBX-14005764

LISA-U200-01S-02

22.40

A01.02

UBX-17048820

LISA-U200-01S-03

22.40

A01.03

UBX-18055867

LARA-R203

LARA-R204

LARA-R211

LARA-R220

LARA-R280

LEON-G100

LISA-U100
LISA-U110

UBX-13002752 - R67

Preface

Page 3 of 1001

u-blox cellular modules - AT commands manual

Name

Type number
LISA-U200-02S-01

Modem version
22.90

Application version
A01.01

PCN reference
UBX-14005768

LISA-U200-02S-02

22.90

A01.03

UBX-17048820

LISA-U200-03S-00

23.41

A01.01UBX-15020745

LISA-U200-03S-01

23.41

A01.04UBX-17048820

LISA-U200-03S-02

23.41

A01.05UBX-18055867

LISA-U200-04B-00

23.41

A01.11UBX-19035887

LISA-U200-52S-01

22.86

A01.01UBX-14005768

LISA-U200-52S-02

22.86

A01.03

UBX-17048820

LISA-U200-52S-03

22.86

A01.04UBX-18055867

LISA-U200-62S-01

22.90

A01.01UBX-14005768

LISA-U200-62S-02

22.90

A01.02

UBX-16017712

LISA-U200-62S-03

22.90

A01.03

UBX-17048820

LISA-U200-62S-04
LISA-U200-83S-00
LISA-U201-03A-00

22.90
23.41
23.41

A01.04
A01.01
A01.01UBX-18055867
UBX-15020745
UBX-16010501

LISA-U201-03A-01

23.41

A01.02

UBX-17010533

LISA-U201-03A-02

23.41

A01.04UBX-17046899

LISA-U201-03S-00

23.41

A01.01UBX-15020745

LISA-U201-03S-01

23.41

A01.04UBX-17048820

LISA-U201 FOTA

LISA-U201-04B-00
LISA-U201-83S-00

23.41
23.41

A01.11
A01.02

UBX-19035887
UBX-16006079

LISA-U230

LISA-U201-83S-01
LISA-U230-01S-01

23.41
22.40

A01.04
A01.00UBX-17048820
UBX-TN-12040

LISA-U230-01S-02

22.40

A01.02

UBX-17048820

LISA-U230-01S-03
LISA-U260-01S-02

22.40
22.61

A01.03
A01.02

UBX-18055867
UBX-14042086

LISA-U260-01S-03

22.61

A01.05UBX-17048820

LISA-U260-02S-02

22.90

A01.02

UBX-14042086

LISA-U260-02S-03
LISA-U270-01S-02

22.90
22.61

A01.04
A01.02

UBX-17048820
UBX-14042086

LISA-U270-02S-02

22.90

A01.02

UBX-14042086

LISA-U270-02S-03

22.90

A01.04UBX-17048820

LISA-U270-62S-04

22.93

A01.02

UBX-14042086

LISA-U270-62S-05

22.93

A01.04UBX-15029938

LISA-U270-62S-06

22.93

A01.05UBX-16009934

LISA-U270-62S-07

22.93

A01.07

UBX-17048820

LISA-U270-63S-00

22.93

A01.06

UBX-16010383

LISA-U270-63S-01

22.93

A01.07

UBX-17048820

LISA-U270-63S-02

22.93

A01.08UBX-18055867

LISA-U270-68S-00

22.93

A01.03

UBX-15019240

LISA-U270-68S-01
MPCI-L200-00S-00
MPCI-L200-00S-01
MPCI-L200-02S-00
MPCI-L200-02S-01
MPCI-L200-03S-00

22.93
09.71
09.71
15.90
15.90
15.90

A01.07
A01.15
A01.30
A01.00
A01.10A01.50UBX-17048820
UBX-14044437
UBX-16026448
UBX-15029946
UBX-16031212
UBX-17022983

15.90

A01.52

UBX-19058317

LISA-U200 FOTA
LISA-U201

LISA-U260

LISA-U270

MPCI-L200

UBX-13002752 - R67

Preface

Page 4 of 1001

u-blox cellular modules - AT commands manual

Name
MPCI-L201

Type number
MPCI-L201-01S-00
MPCI-L201-02S-00

Modem version
09.93
For AT&T: 09.93

Application version
A01.07
For AT&T: A02.50

PCN reference
UBX-15031360
UBX-17013932

For AT&T: 09.93

For AT&T: A02.52

UBX-19058317

For VZW: 09.94

For VZW: A01.02

UBX-17013932

For VZW: 10.04
For AT&T: 20.03

For VZW: A01.01
For AT&T: A01.02

UBX-19058317
UBX-19000820

For AT&T: 20.03

For AT&T: A01.04

UBX-19058317

For VZW: 20.03

For VZW: A01.02

UBX-19000820

MPCI-L210-00S-00
MPCI-L210-02S-00
MPCI-L210-02S-01
MPCI-L210-03S-00

For VZW: 20.04
09.71
15.63
15.63
15.63

For VZW: A01.00
A01.15
A01.03
A01.10A01.50UBX-19058317
UBX-14044437
UBX-15029946
UBX-16031212
UBX-17022983

MPCI-L210-60S-00
MPCI-L210-60S-01

15.63
09.94
09.94

A01.52
A01.00
A01.01UBX-19058317
UBX-15021694
UBX-16005471

MPCI-L210-63S-00
MPCI-L220-02S-00

09.94
09.94
15.93

A01.08
A01.07
A01.00UBX-19058317
UBX-20009693
UBX-16025501

MPCI-L220-62S-00

15.93
16.04

A01.04
A01.00UBX-19058317
UBX-17013073

MPCI-L280

MPCI-L280-02S-00
MPCI-L280-02S-01
MPCI-L280-03S-00

16.04
15.63
15.63
15.63

A01.02
A01.03
A01.10A01.50UBX-19058317
UBX-15029946
UBX-16031212
UBX-17022983

15.63

A01.52

UBX-19058317

SARA-G300

SARA-G300-00S-00

08.58

-

GSM.G2-TN-13007

SARA-G310

SARA-G300-00S-01
SARA-G310-00S-00

08.58
08.58

A01.01-UBX-16010060
GSM.G2-TN-13007

SARA-G340

SARA-G310-00S-01
SARA-G340-00S-00

08.58
08.49

A01.01-UBX-16010060
UBX-14000382

SARA-G340-01S-00

08.70

-

UBX-14039634

SARA-G340-02S-00

08.90

A00.02

UBX-16001074

SARA-G340 ATEXSARA-G340-02S-01
SARA-G340-02X-00

08.90
08.90

A01.13
A00.02

UBX-18008871
UBX-16017766

SARA-G350

SARA-G340-02X-01
SARA-G350-00S-00

08.90
08.49

A01.13-

UBX-18008871
GSM.G2-TN-13002

SARA-G350-01S-00

08.70

-

UBX-14039634

SARA-G350-02A-01

08.90

A00.06

UBX-17003537

SARA-G350-02A-02

08.90

A01.18UBX-18013749

SARA-G350-02S-00

08.90

A00.02

UBX-16001074

SARA-G350-02S-01

08.90

A01.13

UBX-18008871

SARA-G350-01B-00
SARA-G350-00X-00

08.70
08.49

A00.02-

UBX-14039634
GSM.G2-TN-13002

SARA-G350-02X-00

08.90

A00.02

UBX-16001074

SARA-G350-02X-01
SARA-G450-00C-00

08.90
09.02

A01.13
A02.01UBX-18008871
UBX-18067098

SARA-G450-00C-01

09.02

A03.17

UBX-20033037

SARA-G450-01C-00

09.02

A04.23

UBX-20033037

MPCI-L201-02S-01

MPCI-L210

MPCI-L220

SARA-G350 ATEXSARA-G450

UBX-13002752 - R67

Preface

Page 5 of 1001

u-blox cellular modules - AT commands manual

Name
SARA-U201

Type number
SARA-U201-03A-00

Modem version
23.60

Application version
A01.02

PCN reference
UBX-17012748

SARA-U201-03B-00

23.60

A01.01UBX-16018086

SARA-U201-63B-00

23.62

A01.01UBX-17053345

SARA-U201-63B-01

23.63

A01.02

UBX-18005738

SARA-U201-63B-02

23.63

A01.03

UBX-18071209

SARA-U201-04A-00

23.60

A01.06

UBX-17058162

SARA-U201-04A-01

23.60

A01.07

UBX-18053645

SARA-U201 ATEXSARA-U201-04B-00
SARA-U201-03X-00

23.60
23.60

A01.06
A01.01UBX-17058162
UBX-16030157

SARA-U260

SARA-U201-04X-00
SARA-U260-00S-01

23.60
23.20

A01.06
A01.01UBX-17058162
UBX-15013844

SARA-U260-00S-02

23.20

A01.02

UBX-17061316

SARA-U260-03S-00

23.41

A01.01UBX-15020745

SARA-U260-03S-01
SARA-U270-00S-00

23.41
23.20

A01.02
A01.00UBX-17061316
UBX-14015739

SARA-U270-00S-01

23.20

A01.01UBX-16006754

SARA-U270-00S-02

23.20

A01.02

UBX-17061316

SARA-U270-03A-00

23.41

A01.01UBX-17004455

SARA-U270-03A-01

23.41

A01.02

UBX-17064001

SARA-U270-03S-00

23.41

A01.01UBX-15020745

SARA-U270-03S-01

23.41

A01.02

UBX-17061316

SARA-U270-53S-00

23.41

A01.03

UBX-16008757

SARA-U270-53S-01

23.41

A01.04UBX-17011151

SARA-U270-53S-02

23.41

A01.05UBX-17061316

SARA-U270-73S-00

23.41

A01.02

UBX-16028821

SARA-U270 ATEXSARA-U270-73S-01
SARA-U270-00X-00

23.41
23.20

A01.03
A01.00UBX-17061316
UBX-14015739

SARA-U280

SARA-U270-00X-01
SARA-U280-00S-00

23.20
23.28

A01.02
A01.00UBX-17061316
UBX-15013708

SARA-U280-00S-01

23.28

A01.01UBX-17061316

SARA-U280-03S-00

23.41

A01.01UBX-15020745

SARA-U280-03S-01
TOBY-L200-00S-00
TOBY-L200-00S-01
TOBY-L200-02S-00
TOBY-L200-02S-01
TOBY-L200-03S-00

23.41
09.71
09.71
15.90
15.90
15.90

A01.02
A01.15
A01.30
A01.00
A01.10A01.50UBX-17061316
UBX-14044437
UBX-16026448
UBX-15029946
UBX-16031212
UBX-17022983

TOBY-L200-03S-01

15.90
16.19

A01.52
A01.02

UBX-19058317
UBX-19000820

TOBY-L200-03A-01

16.19
16.19

A01.04
A01.02

UBX-19058317
UBX-19016270

16.19

A01.04UBX-19058317

09.93
For AT&T: 09.93

A01.07
For AT&T: A02.50

UBX-18012849
UBX-17013932

For AT&T: 09.93

For AT&T: A02.52

UBX-19058317

For VZW: 09.94

For VZW: A01.02

UBX-17013932

For VZW: 10.04
For AT&T: 20.03

For VZW: A01.01
For AT&T: A01.02

UBX-19058317
UBX-19000820

SARA-U270

TOBY-L200

TOBY-L201

TOBY-L201-01S-00
TOBY-L201-02S-00

TOBY-L201-02S-01

UBX-13002752 - R67

Preface

Page 6 of 1001

u-blox cellular modules - AT commands manual

Name

TOBY-L210

TOBY-L220

TOBY-L280

Type number

Modem version
For AT&T: 20.03

Application version
For AT&T: A01.04

PCN reference
UBX-19058317

For VZW: 20.03

For VZW: A01.02

UBX-19000820

TOBY-L210-00S-00
TOBY-L210-02S-00
TOBY-L210-02S-01
TOBY-L210-03S-00

For VZW: 20.04
09.71
15.63
15.63
15.63

For VZW: A01.00
A01.15
A01.03
A01.10A01.50UBX-19058317
UBX-14044437
UBX-15029946
UBX-16031212
UBX-17022983

TOBY-L210-03S-01

15.63
16.19

A01.52
A01.02

UBX-19058317
UBX-19000820

TOBY-L210-03S-34
TOBY-L210-03A-00

16.19
16.19
15.63

A01.04
A01.03
A01.60UBX-19058317
UBX-19056311
UBX-18010749

TOBY-L210-03A-01

15.63
16.19

A01.62
A01.02

UBX-19058317
UBX-19012118

TOBY-L210-60S-00
TOBY-L210-60S-01
TOBY-L210-62S-00

16.19
09.94
09.94
16.05

A01.04
A01.00
A01.01
A01.02

UBX-19058317
UBX-15021694
UBX-16005471
UBX-19042394

TOBY-L210-65S-00
TOBY-L220-02S-00

16.05
16.05
15.93

A01.05
A01.05
A01.00UBX-19058317
UBX-20009693
UBX-16025501

TOBY-L220-62S-00

15.93
16.04

A01.04
A01.00UBX-19058317
UBX-17013073

16.04

A01.02

UBX-19058317

TOBY-L280-02S-00
TOBY-L280-02S-01
TOBY-L280-03S-00

15.63
15.63
15.63

A01.03
A01.10A01.50UBX-15029946
UBX-16031212
UBX-17022983

TOBY-L280-03S-01

15.63
16.19

A01.52
A01.02

UBX-19058317
UBX-19000820

TOBY-L280-03A-01

16.19
16.19

A01.04
A01.02

UBX-19058317
UBX-19016270

16.19

A01.04UBX-19058317

TOBY-L4006

TOBY-L4006-01A-00

40.35

A10.21

UBX-20032733

TOBY-L4106

TOBY-L4006-51A-00
TOBY-L4106-01A-00

40.35
40.35

A00.21
A10.21

UBX-20032733
UBX-20032733

TOBY-L4206

TOBY-L4106-51A-00
TOBY-L4206-01A-00

40.35
40.35

A00.21
A10.21

UBX-20032733
UBX-20032733

TOBY-L4906

TOBY-L4206-51A-00
TOBY-L4906-01A-00

40.35
40.35

A00.21
A10.21

UBX-20032733
UBX-20032733

TOBY-L4906-50A-01

40.25

A00.17

UBX-18069505

TOBY-L4906-51A-00
TOBY-R200-02B-00

40.35
30.31

A00.21
A01.01

UBX-20032733
UBX-17006265

TOBY-R200-02B-01

30.31

A02.00UBX-17048314

TOBY-R200-02B-02

30.31

A02.01UBX-18018067

TOBY-R200-02B-03

30.31

A02.02

UBX-18057549

TOBY-R200-02B-04

30.33

A02.02

UBX-19011731

TOBY-R200-42B-00

30.53

A01.02

UBX-19045985

TOBY-R200-82B-00
TOBY-R202-02B-00

30.53
30.31

A01.03
A01.01UBX-19043497
UBX-17006265

TOBY-R202-02B-01

30.31

A02.00UBX-17048314

TOBY-R200

TOBY-R202

UBX-13002752 - R67

Preface

Page 7 of 1001

u-blox cellular modules - AT commands manual

Name

Type number
TOBY-R202-02B-02

Modem version
30.31

Application version
A02.01

PCN reference
UBX-18018067

TOBY-R202-02B-03

30.31

A02.02

UBX-18057549

TOBY-R202-02B-04

30.33

A02.02

UBX-19011731

TOBY-R202-02B-34

30.33

A02.04UBX-19039777

How to use this Manual
The u-blox Cellular Modules AT Commands Manual provides the necessary information to successfully designin 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
Modules
TOBY-L2 MPCI-L2
LISA-U110 LISA-U120 LISA-U130 LISA-U2
LEON-G1 SARA-G3
SyntaxPIN required
Settings saved Can be aborted
Attributes
full
No
No
No

Response time-Error reference-

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'LISA-U2' is reported, the command applies to all the modules having LISA form factor, second chipset
version provided with any release of firmware.
• Attributeso Syntax- 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 toprevious cellular standards)
o PIN 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 commando Settings saved- Profile: the command setting can be saved in a personal profile as specified in Chapter 1.2- NVM: the command setting is saved in the non-volatile memory as specified in Chapter 1.2- <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 withthe +UMNOPROF AT command (if supported)- No: the current command setting is volatile and cannot be savedo Can be aborted- Yes: the command execution can be aborted if a character is sent to the DCE during the commandexecution- No: the command cannot be aborted during the command execution

UBX-13002752 - R67

Preface

Page 8 of 1001

u-blox cellular modules - AT commands manualo Response 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 thecommand 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 thecommand acquisition by the DCE.
For example, the maximum expected response time shall be extended if the communication with themodule 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 meansthat 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 adifferent 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 cantherefore postpone the execution of the AT commands issued by the user.
o Error 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 ishighlighted in Chapter 1.2 for the saving of settings, in Chapter 1.1.6 for the abortability, and in a product specificnote 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 technicaldocumentation 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.
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 thesoftware point of view. It provides hardware design guidelines for the optimal integration of the cellular modulein 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 / SARA-N4
Application Development Guide [177].
• For some guidelines when developing applications for NB-IoT technologies, see the NB-IoT Application
Development Guide [179].
• 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 [175].
See Related documents for application notes related to your cellular module.

QuestionsIf 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

UBX-13002752 - R67

Preface

Page 9 of 1001

u-blox cellular modules - AT commands manual

Technical Support
Worldwide Web
Our website (www.u-blox.com) is a rich pool of information. Product information, technical documents andhelpful FAQ can be accessed 24h a day.
By E-mailIf 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

UBX-13002752 - R67

Preface

Page 10 of 1001

u-blox cellular modules - AT commands manualContents
1

AT command settings.................................................................................................... 23
1.1
1.2
1.3
1.4

2

General operation............................................................................................................ 30
2.1
2.2

3

Start up and initialization............................................................................................................................. 30
AT commands types...................................................................................................................................... 31

IPC - Inter Processor Communication.......................................................................33
3.1

4

Definitions......................................................................................................................................................... 23
Storing of AT commands setting................................................................................................................28
S-parameters................................................................................................................................................... 29+UDCONF AT command................................................................................................................................29

Multiplexing mode +CMUX........................................................................................................................... 33

General................................................................................................................................ 36
4.1 Manufacturer identification +CGMI............................................................................................................ 36
4.2 Manufacturer identification +GMI.............................................................................................................. 36
4.3 Model identification +CGMM.......................................................................................................................36
4.4 Model identification +GMM..........................................................................................................................37
4.5 Firmware version identification +CGMR....................................................................................................37
4.6 Firmware version identification +GMR...................................................................................................... 38
4.7 Request product serial number identification +CGSN........................................................................... 38
4.8 IMEI identification +GSN.............................................................................................................................. 39
4.9 Identification information I.......................................................................................................................... 40
4.10 TE character set configuration +CSCS................................................................................................... 40
4.11 International mobile subscriber identification +CIMI............................................................................. 41
4.12 Card identification +CCID........................................................................................................................... 42
4.13 Request complete capabilities list +GCAP..............................................................................................42
4.14 Repeat last command A/............................................................................................................................ 43
4.15 List all available AT commands +CLAC...................................................................................................43
4.16 Help displaying all commands &H.............................................................................................................44

5

Mobile equipment control and status.......................................................................46
5.1 Phone activity status +CPAS....................................................................................................................... 46
5.2 Module switch off +CPWROFF....................................................................................................................46
5.3 Set module functionality +CFUN................................................................................................................ 47
5.4 Indicator control +CIND................................................................................................................................ 49
5.5 Configuration of indicator control +UCIND...............................................................................................52
5.6 Mobile termination event reporting +CMER............................................................................................ 52
5.7 Clock +CCLK....................................................................................................................................................54
5.8 Alarm +CALA.................................................................................................................................................. 55
5.9 Delete alarm +CALD...................................................................................................................................... 57
5.10 Alert sound mode +CALM.......................................................................................................................... 57
5.11 Ringer sound level +CRSL........................................................................................................................... 58
5.12 Loudspeaker volume level +CLVL............................................................................................................. 59
5.13 Mute control +CMUT................................................................................................................................... 60
5.14 Set greeting text +CSGT............................................................................................................................. 61
5.15 Automatic time zone update +CTZU....................................................................................................... 62
5.16 Time zone reporting +CTZR.......................................................................................................................62
5.17 List current calls +CLCC............................................................................................................................. 64
5.18 IMS single radio voice call continuity +CISRVCC................................................................................... 65
5.19 Report mobile termination error +CMEE.................................................................................................66
5.20 Extended error report +CEER....................................................................................................................67
5.21 Proprietary extended error report +UCEER............................................................................................ 68

6

Call control........................................................................................................................ 70

UBX-13002752 - R67

Contents

Page 11 of 1001

u-blox cellular modules - AT commands manual

6.1 Select type of address +CSTA..................................................................................................................... 70
6.2 Dial command D............................................................................................................................................. 70
6.3 Direct calling from phonebooks D>............................................................................................................ 73
6.4 Select tone dialling T.....................................................................................................................................74
6.5 Select pulse dialling P................................................................................................................................... 74
6.6 Call answer A...................................................................................................................................................75
6.7 Hook control H................................................................................................................................................ 75
6.8 Monitor speaker loudness L.........................................................................................................................76
6.9 Monitor speaker mode M..............................................................................................................................76
6.10 Call mode +CMOD.........................................................................................................................................77
6.11 Hang up call +CHUP...................................................................................................................................... 77
6.12 Single numbering scheme +CSNS............................................................................................................ 78
6.13 Set reporting call status +UCALLSTAT.................................................................................................. 79
6.14 Information to in-band-tones availability +UPROGRESS.....................................................................80
6.15 Tone duration +VTD..................................................................................................................................... 81
6.16 DTMF and tone generation +VTS..............................................................................................................81
6.17 Start and stop tone generation +UVTS...................................................................................................82
6.18 Redial last telephone number DL..............................................................................................................83
6.19 Automatic answer S0.................................................................................................................................. 83
6.20 Set voice mail number +CSVM................................................................................................................. 84
6.21 Emergency call reporting configuration +UEMC................................................................................... 85
6.22 Emergency number verification +UEMN................................................................................................ 86

7

Network service............................................................................................................... 87
7.1 Network parameters definition.................................................................................................................... 87
7.2 Subscriber number +CNUM......................................................................................................................... 89
7.3 Signal quality +CSQ....................................................................................................................................... 90
7.4 Extended signal quality +CESQ...................................................................................................................92
7.5 Operator selection +COPS............................................................................................................................94
7.6 MCC update table +UNVMMCC................................................................................................................. 101
7.7 PLMN information list +UNVMPLMN.......................................................................................................103
7.8 Radio Access Technology (RAT) selection +URAT................................................................................ 106
7.9 Preferred Radio Access Technology (RAT) scope +UDCONF=59....................................................... 109
7.10 Display EONS names +UEONS................................................................................................................. 110
7.11 Display operator name +UDOPN............................................................................................................... 110
7.12 Preferred PLMN list selection +CPLS......................................................................................................112
7.13 PS operator selection +UCGOPS.............................................................................................................. 113
7.14 Network registration status +CREG........................................................................................................ 114
7.15 HSDPA/HSUPA mode configuration +UHSDUPA..................................................................................118
7.16 Preferred operator list +CPOL...................................................................................................................119
7.17 Read operator names +COPN....................................................................................................................121
7.18 Network emergency bearer services support +CNEM......................................................................... 121
7.19 Steering of Roaming configuration +UDCONF=20.............................................................................. 122
7.20 Fast Dormancy activation +UFDAC....................................................................................................... 123
7.21 Fast Dormancy configuration +UDCONF=61......................................................................................... 124
7.22 Network selection control +PACSP........................................................................................................ 125
7.23 Integrity check on test networks configuration +UDCONF=81.........................................................126
7.24 Select band +UBANDSEL..........................................................................................................................127
7.25 Select band +UACT....................................................................................................................................128
7.26 Cell environment description +CGED......................................................................................................131
7.27 Neighbour cells configuration +UDCONF=83........................................................................................ 141
7.28 Channel and network environment description +UCGED................................................................... 141
7.29 Provide cell information +UCELLINFO................................................................................................... 147
7.30 Lock on a specific cell +UCELLLOCK..................................................................................................... 149
7.31 Wireless service selection +WS46...........................................................................................................153
7.32 Service specific access control restriction status +CSSAC.............................................................. 155
7.33 Home zone reporting +UHOMEZR..........................................................................................................157
7.34 Jamming detection +UCD........................................................................................................................ 157
7.35 Smart jamming detection +UJAD.......................................................................................................... 160
7.36 IMSI detach +UCSDETACH....................................................................................................................... 161
7.37 MNO configuration +UMNOCONF...........................................................................................................162

UBX-13002752 - R67

Contents

Page 12 of 1001

u-blox cellular modules - AT commands manual

7.38 PLMN list extensions +UMNOPLMN......................................................................................................167
7.39 LTE category configuration +ULTECAT................................................................................................ 168
7.40 Edit Verizon wireless APN table +VZWAPNE.......................................................................................169
7.41 Read RSRP values +VZWRSRP................................................................................................................170
7.42 Read RSRQ values +VZWRSRQ............................................................................................................... 171
7.43 Closed Subscriber Group +UCSG............................................................................................................. 171
7.44 Network Friendly Mode (NFM) activation +UNFM...............................................................................173
7.45 Network Friendly Mode (NFM) configuration +UNFMCONF..............................................................174
7.46 Radio Policy Manager (RPM) activation +URPM.................................................................................. 175
7.47 Radio Policy Manager (RPM) configuration +URPMCONF................................................................. 176
7.48 Device Aggresion Management configuration +UDAMCFG.............................................................. 178
7.49 PLMN search configuration in Out Of Coverage +UDCONF=55....................................................... 178
7.50 Purging of temporary mobile identities after SIM refresh +UDCONF=56...................................... 179
7.51 Smart radio coverage manager configuration +UDCONF=57............................................................180
7.52 Set MNO profile +UMNOPROF.................................................................................................................181

8

IP Multimedia Subsystem (IMS)............................................................................... 184
8.1 Introduction.................................................................................................................................................... 184
8.2 Domain configuration for supplementary services +UISS................................................................... 184
8.3 IMS client configuration +UIMSCFG........................................................................................................ 184
8.4 IMS client registration / deregistration in network +UIMSREG.......................................................... 188
8.5 IMS configuration setting +UIMSCONF.................................................................................................. 189
8.6 Read IMS configuration +UIMSRCONF....................................................................................................193
8.7 IMS registration information +CIREG.......................................................................................................194
8.8 IMS network reporting +CIREP..................................................................................................................195
8.9 Availability for SMS using IMS +CASIMS................................................................................................196
8.10 UE's Mobility Management IMS Voice Termination +CMMIVT.........................................................196
8.11 UE's voice domain preference E-UTRAN +CEVDP................................................................................ 197
8.12 Domain configuration for MO SMS messages +UISMS..................................................................... 198
8.13 MO SMS mode configuration +UICMGSMODE.................................................................................... 198
8.14 Send 3GPP2 SMS message +UCMGS3GPP2........................................................................................199
8.15 Enable/disable the 3GPP2 SMS URC +UCMT3GPP2...........................................................................199

9

Device lock...................................................................................................................... 202
9.1
9.2
9.3
9.4
9.5

10

Enter PIN +CPIN............................................................................................................................................202
Read remaining SIM PIN attempts +UPINCNT..................................................................................... 203
Facility lock +CLCK......................................................................................................................................204
Change password +CPWD......................................................................................................................... 206
Custom SIM lock +USIMLCK.....................................................................................................................207

Phonebook.....................................................................................................................209
10.1 Select phonebook memory storage +CPBS.......................................................................................... 209
10.2 Read phonebook entries +CPBR..............................................................................................................210
10.3 Find phonebook entries +CPBF................................................................................................................212
10.4 Write phonebook entry +CPBW............................................................................................................... 213
10.5 Read/rename phonebook group +UPBGR.............................................................................................. 215

11

Short Messages Service............................................................................................. 217
11.1 Introduction....................................................................................................................................................217
11.2 Select message service +CSMS............................................................................................................... 218
11.3 Preferred message storage +CPMS........................................................................................................ 219
11.4 Preferred message format +CMGF..........................................................................................................221
11.5 Save settings +CSAS..................................................................................................................................221
11.6 Restore settings +CRES............................................................................................................................222
11.7 Show text mode parameters +CSDH...................................................................................................... 222
11.8 New message indication +CNMI.............................................................................................................. 223
11.9 Incoming SMS/CBM indication via different AT interfaces +UDCONF=82..................................... 227
11.10 Select service for MO SMS messages +CGSMS................................................................................ 228
11.11 Read message +CMGR..............................................................................................................................229
11.12 New message acknowledgement to MT +CNMA................................................................................ 231
11.13 List message +CMGL............................................................................................................................... 232

UBX-13002752 - R67

Contents

Page 13 of 1001

u-blox cellular modules - AT commands manual

11.14 Send message (+CMGS/+CMSS) set commands conclusion configuration +UDCONF=13...... 234
11.15 Send message +CMGS.............................................................................................................................235
11.16 Write message to memory +CMGW......................................................................................................236
11.17 Send message from storage +CMSS.................................................................................................... 237
11.18 Set text mode parameters +CSMP....................................................................................................... 238
11.19 Delete message +CMGD.......................................................................................................................... 239
11.20 Primary notification event reporting +CPNER................................................................................... 240
11.21 Service center address +CSCA...............................................................................................................240
11.22 Select cell broadcast message types +CSCB......................................................................................241
11.23 Read concatenated message +UCMGR............................................................................................... 242
11.24 List concatenated message +UCMGL................................................................................................. 245
11.25 Send concatenated message +UCMGS............................................................................................... 247
11.26 Write concatenated message to memory +UCMGW........................................................................248
11.27 More messages to send +CMMS.......................................................................................................... 249
11.28 Peek message +UCMGP..........................................................................................................................250
11.29 Message waiting indication +UMWI...................................................................................................... 251
11.30 Earthquake and Tsunami Warning System configuration +UETWCFG........................................252
11.31 Start ETWS notifications +UETWNTFYSTART................................................................................. 253
11.32 Stop ETWS notifications +UETWNTFYSTOP.................................................................................... 255

12Supplementary services............................................................................................25612.1 Introduction.................................................................................................................................................. 256
12.2 Call forwarding +CCFC.............................................................................................................................. 256
12.3 Call waiting +CCWA...................................................................................................................................258
12.4 Calling line identification restriction +CLIR.......................................................................................... 260
12.5 Calling line identification presentation +CLIP.......................................................................................261
12.6 Connected line identification presentation +COLP.............................................................................262
12.7 Connected line identification restriction +COLR................................................................................. 263
12.8 Advice of charge +CAOC...........................................................................................................................26412.9 Accumulated call meter +CACM.............................................................................................................26512.10 Call meter maximum event +CCWE..................................................................................................... 265
12.11 Accumulated call meter maximum +CAMM........................................................................................ 266
12.12 Price per unit and currency table +CPUC.............................................................................................267
12.13 Call related supplementary services +CHLD.......................................................................................267
12.14 Call deflection +CTFR.............................................................................................................................. 268
12.15 Supplementary service notifications +CSSN......................................................................................269
12.16 User to user signalling service 1 +CUUS1.............................................................................................270
12.17 Unstructured supplementary service data +CUSD............................................................................272
12.18 Closed user group +CCUG.......................................................................................................................273
12.19 Calling name presentation +CNAP........................................................................................................274
12.20 eMLPP priority registration and interrogation +CAEMLPP.............................................................275
12.21 eMLPP subscriptions +CPPS..................................................................................................................275
12.22 Automatic answer for eMLPP service +CAAP....................................................................................276

13

Circuit switched data services................................................................................ 277
13.1 Introduction...................................................................................................................................................277
13.2 Select bearer service type +CBST...........................................................................................................277
13.3 Connection type groups configuration +UDCONF=32........................................................................279
13.4 Circuit switched data (CSD) configuration +UCSD.............................................................................280
13.5 Circuit switched data (CSD) action +UCSDA........................................................................................ 281
13.6 Circuit switched network-assigned data +UCSND............................................................................. 282
13.7 Service class selection and identification +FCLASS.......................................................................... 283
13.8 Service reporting control +CR................................................................................................................. 284
13.9 Cellular result codes +CRC.......................................................................................................................284
13.10 Radio link protocol +CRLP...................................................................................................................... 286

14

FAX class 2.................................................................................................................... 287
14.1
14.2
14.3
14.4

Introduction.................................................................................................................................................. 287
Adaptive answer +FAA..............................................................................................................................287
Address & polling capabilities +FAP.......................................................................................................287
Buffer size +FBS.........................................................................................................................................288

UBX-13002752 - R67

Contents

Page 14 of 1001

u-blox cellular modules - AT commands manual

14.5 Data bit order +FBO.................................................................................................................................. 288
14.6 HDLC frame reporting +FBU....................................................................................................................289
14.7 DS capabilities parameters +FCC...........................................................................................................289
14.8 Copy quality checking +FCQ....................................................................................................................290
14.9 Capability to receive data +FCR.............................................................................................................. 291
14.10 Current session results +FCS.................................................................................................................291
14.11 DTE phase C response timeout +FCT...................................................................................................292
14.12 Receive data +FDR................................................................................................................................... 292
14.13 Transmit Data +FDT................................................................................................................................ 292
14.14 Phase C received EOL alignment +FEA............................................................................................... 293
14.15 Format conversion +FFC.........................................................................................................................293
14.16 Report file transfer diagnostic frame +FFD........................................................................................294
14.17 Call termination status +FHS................................................................................................................ 294
14.18 Procedure interrupt enable +FIE........................................................................................................... 295
14.19 Initialize facsimile parameters +FIP..................................................................................................... 295
14.20 Current session parameters +FIS........................................................................................................ 296
14.21 Inactivity timeout +FIT............................................................................................................................ 297
14.22 Session termination +FKS, +FK............................................................................................................ 297
14.23 Local ID string +FLI..................................................................................................................................297
14.24 Set flow control +FLO............................................................................................................................. 298
14.25 Indicate document to poll +FLP............................................................................................................298
14.26 Request manufacturer identification +FMI........................................................................................299
14.27 Request model identification +FMM....................................................................................................299
14.28 Request revision identification +FMR................................................................................................. 300
14.29 Minimum phase C speed +FMS........................................................................................................... 300
14.30 Negotiation reporting +FNR...................................................................................................................301
14.31 Non-standard frame FIF octet string +FNS........................................................................................ 301
14.32 NSF message data indication +FND................................................................................................... 302
14.33 Selective polling address +FPA............................................................................................................ 302
14.34 Local polling ID string +FPI....................................................................................................................303
14.35 Packet protocol control +FPP............................................................................................................... 303
14.36 Page status +FPS....................................................................................................................................304
14.37 Password parameter +FPW...................................................................................................................304
14.38 Receive quality thresholds +FRQ......................................................................................................... 305
14.39 Error correction mode retry count +FRY............................................................................................ 305
14.40 SubAddress parameter +FSA............................................................................................................... 306
14.41 Request to poll +FSP............................................................................................................................... 306
14.42 Fax intermediate result codes.............................................................................................................. 306

15

V24 control and V25ter.............................................................................................308
15.1 Introduction..................................................................................................................................................308
15.2 Circuit 109 behavior &C.............................................................................................................................308
15.3 Circuit 108/2 behavior &D.........................................................................................................................309
15.4 DSR override &S..........................................................................................................................................310
15.5 Flow control &K............................................................................................................................................ 311
15.6 DTE-DCE character framing +ICF........................................................................................................... 314
15.7 DTE-DCE local flow control +IFC..............................................................................................................316
15.8 Set flow control \Q...................................................................................................................................... 317
15.9 UART data rate configuration +IPR........................................................................................................ 319
15.10 Return to on-line data state O.............................................................................................................. 323
15.11 Escape character S2.................................................................................................................................324
15.12 Command line termination character S3............................................................................................ 325
15.13 Response formatting character S4...................................................................................................... 326
15.14 Command line editing character S5..................................................................................................... 326
15.15 Pause before blind dialling S6................................................................................................................ 327
15.16 Connection completion timeout S7...................................................................................................... 328
15.17 Command dial modifier time S8............................................................................................................328
15.18 Automatic disconnect delay S10........................................................................................................... 329
15.19 Escape prompt delay (EPD) S12............................................................................................................ 330
15.20 Command echo E.....................................................................................................................................330
15.21 Result code suppression Q......................................................................................................................331

UBX-13002752 - R67

Contents

Page 15 of 1001

u-blox cellular modules - AT commands manual

15.22
15.23
15.24
15.25
15.26
15.27
15.28
15.29

16

DCE response format V...........................................................................................................................331
Result code selection and call progress monitoring control X........................................................332
Reset to default configuration Z.......................................................................................................... 332
Set to factory defined configuration &F............................................................................................. 333
Store current configuration &W........................................................................................................... 334
Display current configuration &V......................................................................................................... 334
Designate a default reset profile &Y................................................................................................... 335
Parity bit transmission over the air +UTPB........................................................................................336

SIM management........................................................................................................ 339
16.1 Generic SIM access +CSIM....................................................................................................................... 339
16.2 Restricted SIM access +CRSM............................................................................................................... 339
16.3 Read the SIM language +CLAN............................................................................................................... 341
16.4 Check for UICC card +UUICC................................................................................................................... 342
16.5 Customer service profile +UCSP.............................................................................................................342
16.6 SIM hot insertion configuration +UDCONF=50................................................................................... 343
16.7 UICC application discovery +CUAD.........................................................................................................344
16.8 Open logical channel +CCHO................................................................................................................... 345
16.9 Close logical channel +CCHC................................................................................................................... 346
16.10 Generic UICC logical channel access +CGLA...................................................................................... 346
16.11 Restricted UICC logical channel access +CRLA.................................................................................. 347
16.12 SIM states reporting +USIMSTAT........................................................................................................ 349
16.13 Answer To Reset contents +USIMATR............................................................................................... 350
16.14 Perform SIM switch +XSIMSWITCH.....................................................................................................350

17

SIM toolkit..................................................................................................................... 352
17.1 Introduction.................................................................................................................................................. 352
17.2 Terminal profile +STKPROF..................................................................................................................... 352
17.3 Proactive command in dedicated mode +STKPRO............................................................................. 353
17.4 Terminal response in dedicated mode +STKTR.................................................................................. 356
17.5 Proactive session status in dedicated mode +STKCNF.....................................................................359
17.6 Bearer Independent Protocol status indication +UBIP....................................................................... 360
17.7 Default BIP APN configuration +UBIPAPN............................................................................................. 361
17.8 Envelope in dedicated mode +STKENV..................................................................................................361
17.9 Call and short message control in dedicated mode +STKCC............................................................362
17.10 Proactive command indication in raw mode +SATI...........................................................................363
17.11 Proactive command notification in raw mode +SATN.......................................................................363
17.12 Send terminal response in raw mode +SATR..................................................................................... 364
17.13 Terminal response confirmation in raw mode +SATF.......................................................................364
17.14 User confirmation for setup call in raw mode +SATD.......................................................................365
17.15 Envelope download in raw mode +SATE..............................................................................................365
17.16 Call and Short Message Control in Raw Mode +STKCTRLIND........................................................366
17.17 Terminal profile +UCATPROF................................................................................................................. 367
17.18 Proactive command indication in dedicated mode +UCATPROI..................................................... 367
17.19 Proactive command notification in dedicated mode +UCATPRON................................................ 369
17.20 Terminal response in dedicated mode +UCATTR............................................................................. 369
17.21 Proactive Session Status in Dedicated Mode +UCATCNF................................................................ 371
17.22 Envelope in Dedicated Mode +UCATENV............................................................................................ 371
17.23 Call and Short Message Control in Dedicated Mode +UCATCC...................................................... 371
17.24 Proactive Command Indication in Raw Mode +URCATI................................................................... 372
17.25 Proactive Command Notification in Raw Mode +URCATN..............................................................372
17.26 Terminal response in Raw Mode +URCATR....................................................................................... 373
17.27 Proactive Session Status in Raw Mode +URCATF............................................................................ 373
17.28 Envelope in Raw Mode +URCATE......................................................................................................... 373
17.29 Call and Short Message Control in Raw Mode +URCATCC............................................................. 374
17.30 User setting for proactive DTMF tone generation +UDTMF...........................................................375
17.31 Refresh delay events management +UDCONF=54............................................................................376

18

Packet switched data services............................................................................... 378
18.1 PDP contexts and parameter definition.................................................................................................378
18.2 PPP LCP handshake behaviour............................................................................................................... 382

UBX-13002752 - R67

Contents

Page 16 of 1001

u-blox cellular modules - AT commands manual

18.3 Printing IP address format +CGPIAF..................................................................................................... 382
18.4 PDP context definition +CGDCONT....................................................................................................... 383
18.5 Protocol configuration options configuration +UPCO........................................................................ 388
18.6 IPv6 configuration +UDCONF=66........................................................................................................... 390
18.7 Packet switched data configuration +UPSD........................................................................................ 392
18.8 Packet switched data action +UPSDA.................................................................................................. 399
18.9 Packet switched network-assigned data +UPSND..............................................................................401
18.10 Read PDP context DNS information +UDCONF=11............................................................................402
18.11 Dynamic DNS request +UDNS................................................................................................................403
18.12 Quality of service profile (requested) +CGQREQ................................................................................404
18.13 Quality of service profile (minimum acceptable) +CGQMIN............................................................ 405
18.14 GPRS attach or detach +CGATT...........................................................................................................406
18.15 Configure the auto attach to PS domain on power on +UCGATT.................................................. 407
18.16 PDP context activate or deactivate +CGACT..................................................................................... 408
18.17 Control ESM cause 52 handling +UDCONF=12.................................................................................... 411
18.18 Manual response to a network request for PDP context activation +CGANS...............................412
18.19 Automatic response to a network request for PDP context activation +CGAUTO...................... 413
18.20 Enter data state +CGDATA....................................................................................................................414
18.21 Enter PPP state/GPRS dial-up D*.......................................................................................................... 416
18.22 Show PDP address +CGPADDR............................................................................................................. 418
18.23 GPRS MS class configuration +CGCLASS.......................................................................................... 418
18.24 GPRS MS class configuration at start up +UCGCLASS.................................................................. 420
18.25 Device class setting +UCLASS.............................................................................................................. 421
18.26 Packet switched event reporting +CGEREP.......................................................................................423
18.27 GPRS network registration status +CGREG.......................................................................................426
18.28 Extended Packet Switched network registration status +UREG...................................................429
18.29 Manual deactivation of a PDP context H............................................................................................430
18.30 PDP context modify +CGCMOD............................................................................................................430
18.31 3G Quality of service profile (requested) +CGEQREQ........................................................................ 431
18.32 3G Quality of service profile (minimum acceptable) +CGEQMIN................................................... 435
18.33 3G Quality of Service Profile (negotiated) +CGEQNEG.................................................................... 439
18.34 Define secondary PDP context +CGDSCONT..................................................................................... 441
18.35 UE modes of operation for EPS +CEMODE........................................................................................443
18.36 EPS network registration status +CEREG......................................................................................... 444
18.37 Delete non-active PDP contexts +CGDEL........................................................................................... 446
18.38 Traffic flow template read dynamic parameters +CGTFTRDP...................................................... 447
18.39 Configure the authentication parameters of a PDP/EPS bearer +UAUTHREQ...........................449
18.40 Send custom packets over a context +UTGSINK.............................................................................. 451
18.41 Define EPS quality of service +CGEQOS.............................................................................................. 451
18.42 EPS quality of service read dynamic parameters +CGEQOSRDP.................................................. 452
18.43 Secondary PDP context read dynamic parameters +CGSCONTRDP............................................453
18.44 UE's usage setting for EPS +CEUS......................................................................................................454
18.45 PDP context read dynamic parameters +CGCONTRDP.................................................................. 455
18.46 Configure the initial EPS bearer / PDP context +UCGDFLT............................................................ 457
18.47 Always-On mode parameters settings +CGPERMSET.................................................................... 460
18.48 Always-On mode settings +CGPERMACT..........................................................................................460
18.49 Always-On mode check state +CGPERMSTATE................................................................................461
18.50 Traffic flow template +CGTFT..............................................................................................................462
18.51 Read counters of sent or received PSD data +UGCNTRD................................................................465
18.52 Set/reset counter of sent or received PSD data +UGCNTSET....................................................... 466
18.53 Uplink user data plane configuration +UDCONF=9.......................................................................... 467
18.54 Feature Group Indicators (FGI) settings +UFGI.................................................................................470

19

System features.......................................................................................................... 472
19.1 Firmware installation +UFWINSTALL.....................................................................................................472
19.2 Firmware update Over AT (FOAT) +UFWUPD......................................................................................475
19.3 Firmware installation with signature verification +UFWSINSTALL................................................ 479
19.4 Antenna detection +UANTR.................................................................................................................... 480
19.5 RX antenna selection +UANT...................................................................................................................481
19.6 Rx diversity +URXDIV................................................................................................................................ 482
19.7 ADC read command +UADC.................................................................................................................... 483

UBX-13002752 - R67

Contents

Page 17 of 1001

u-blox cellular modules - AT commands manual

19.8 End user test +UTEST.............................................................................................................................. 484
19.9 Smart temperature supervisor +USTS................................................................................................. 495
19.10 MSPR profile handling configuration +UDCONF=40.........................................................................496
19.11 Data channel configuration +UDATACHANNEL................................................................................. 498
19.12 RING line handling +URING.....................................................................................................................499
19.13 CTS line state in case of disabled HW flow control +UCTS.............................................................500
19.14 PPP/LCP silent mode configuration +UDCONF=0..............................................................................501
19.15 F-DPCH/enhanced F-DPCH configuration +UDCONF=60.................................................................501
19.16 USB profiles configuration +UUSBCONF.............................................................................................502
19.17 Serial interfaces configuration selection +USIO................................................................................ 504
19.18 USB disable/enable selection and status +UDCONF=78................................................................. 508
19.19 Establish ECM data connection +UCEDATA...................................................................................... 509
19.20 Start, stop and configure the OMA-DM client +UOMADM..............................................................510
19.21 OMA-DM alert +UOMADMALERT.......................................................................................................... 511
19.22 OMA-DM repository access +UOMADMREP...................................................................................... 512
19.23 Enable/disable OMA-DM unsolicited status messages +UOMASTAT.......................................... 514
19.24 Internal temperature monitor +UTEMP...............................................................................................519
19.25 Restore factory configuration +UFACTORY...................................................................................... 520
19.26 NVM RAM mode management +UDCONF=110.................................................................................. 521
19.27 NVM configuration management commit +UNVMW.......................................................................522
19.28 NVM configuration management reset +UNVMR............................................................................ 523
19.29 NVM configuration management factory restore +UNVMF...........................................................523
19.30 KT remote reset KTCFUN...................................................................................................................... 524
19.31 KT reading quality information KTDEVSTAT..................................................................................... 524
19.32 KT configuration command KTUBXCONF.......................................................................................... 526
19.33 Reject international calls KTUCALLREJ............................................................................................. 527
19.34 Request KT OTA opening *KTF*OPENING..........................................................................................527
19.35 Display the current UMTS environment KTUUMTSENV.................................................................528
19.36 Last gasp configuration +ULGASP...................................................................................................... 529

20Power management...................................................................................................532
20.1

21

GPIO................................................................................................................................. 538
21.1
21.2
21.3
21.4

22

Introduction.................................................................................................................................................. 538
GPIO select configuration command +UGPIOC................................................................................... 548
GPIO read command +UGPIOR................................................................................................................ 551
GPIO set command +UGPIOW.................................................................................................................552

File System...................................................................................................................553
22.1
22.2
22.3
22.4
22.5
22.6
22.7

23

Power saving control (Power SaVing) +UPSV...................................................................................... 532

File tags........................................................................................................................................................553
Download file +UDWNFILE...................................................................................................................... 555
List files information +ULSTFILE...........................................................................................................557
Read file +URDFILE...................................................................................................................................558
Partial read file +URDBLOCK.................................................................................................................. 560
Delete file +UDELFILE.............................................................................................................................. 560
File system limits....................................................................................................................................... 561

Audio interface............................................................................................................ 563
23.1 Audio path mode setting +USPM...........................................................................................................563
23.2 I2S digital interface mode +UI2S............................................................................................................ 570
23.3 Play audio resource +UPAR..................................................................................................................... 579
23.4 Stop audio resource +USAR....................................................................................................................582
23.5 Play audio file +UPLAYFILE.....................................................................................................................583
23.6 Record audio file +URECFILE..................................................................................................................586
23.7 Stop audio file +USTOPFILE................................................................................................................... 588
23.8 Play audio file +UAPLAY.......................................................................................................................... 589
23.9 Record audio file +UAREC........................................................................................................................ 591
23.10 Tone generator +UTGN.......................................................................................................................... 593
23.11 Ringing tone selection +URNG.............................................................................................................. 595
23.12 SMS alert sound mode (Message Sound Muting) +UMSM............................................................ 596

UBX-13002752 - R67

Contents

Page 18 of 1001

u-blox cellular modules - AT commands manual

23.13
23.14
23.15
23.16
23.17
23.18

24

Master clock control +UMCLK.............................................................................................................. 596
External device configuration +UEXTDCONF.................................................................................... 598
Speech codec information +USPEECHINFO....................................................................................... 601
Speech codec configuration +UDCONF=30....................................................................................... 602
Waiting call tone configuration +UDCONF=33.................................................................................. 604
Hardware audio path test +UMAAT.................................................................................................... 604

Audio parameters tuning......................................................................................... 606
24.1 Introduction................................................................................................................................................. 606
24.2 Microphone gain (Microphone Gain Control) +UMGC......................................................................... 619
24.3 Speaker Gain (Speaker Gain Control) +USGC...................................................................................... 621
24.4 Sidetone configuration +USTN...............................................................................................................624
24.5 Uplink Digital Filters (Uplink Biquad Filters) +UUBF.......................................................................... 625
24.6 Downlink Digital Filters (Downlink Biquad Filters) +UDBF................................................................ 627
24.7 Hands-Free Parameters (Hands-Free Parameters) +UHFP............................................................. 630
24.8 Audio parameters tuning +UAPT...........................................................................................................639
24.9 Audio parameters tuning +UTI............................................................................................................... 642
24.10 Volume gain control +UVGC.................................................................................................................. 643
24.11 Microphone analog and digital gains +UMAFE.................................................................................. 644
24.12 Speaker analog and digital gains +USAFE......................................................................................... 645
24.13 Microphone select +UMSEL.................................................................................................................. 646

25

DNS................................................................................................................................. 648
25.1 Resolve name / IP number through DNS +UDNSRN........................................................................... 648
25.2 Dynamic DNS update +UDYNDNS.........................................................................................................650

26Internet protocol transport layer.......................................................................... 653
26.1 Introduction................................................................................................................................................. 653
26.2 IPv4/IPv6 addressing.................................................................................................................................653
26.3 Create Socket +USOCR............................................................................................................................655
26.4 SSL/TLS/DTLS mode configuration on TCP/UDP socket +USOSEC.............................................. 656
26.5 Set socket option +USOSO..................................................................................................................... 657
26.6 Get Socket Option +USOGO....................................................................................................................659
26.7 Close Socket +USOCL.............................................................................................................................. 660
26.8 Get Socket Error +USOER........................................................................................................................ 661
26.9 Connect Socket +USOCO........................................................................................................................ 662
26.10 Write socket data +USOWR..................................................................................................................663
26.11 SendTo command (UDP only) +USOST............................................................................................... 665
26.12 Read Socket Data +USORD................................................................................................................... 667
26.13 Receive From command (UDP only) +USORF.................................................................................... 669
26.14 Set Listening Socket +USOLI................................................................................................................670
26.15 Firewall control +UFRW........................................................................................................................... 671
26.16 HEX mode configuration +UDCONF=1................................................................................................. 672
26.17 Set socket in Direct Link mode +USODL............................................................................................ 673
26.18 UDP Direct Link Packet Size configuration +UDCONF=2................................................................ 675
26.19 UDP Direct Link Sending timer configuration +UDCONF=3............................................................676
26.20 Timer Trigger configuration for Direct Link +UDCONF=5.............................................................. 676
26.21 Data Length Trigger configuration for Direct Link +UDCONF=6................................................... 677
26.22 Character trigger configuration for Direct Link +UDCONF=7........................................................ 678
26.23 Congestion timer configuration for Direct Link +UDCONF=8........................................................678
26.24 Direct Link disconnect DSR line handling +UDCONF=10................................................................ 679
26.25 Socket control +USOCTL...................................................................................................................... 680
26.26 IP Change Notification +UIPCHGN....................................................................................................... 681
26.27 Socket Always On +USOAO.................................................................................................................. 685

27

Device and data security..........................................................................................690
27.1

28

Data security............................................................................................................................................... 690

FTP................................................................................................................................... 713
28.1
28.2

FTP service configuration +UFTP............................................................................................................713
FTP command +UFTPC.............................................................................................................................717

UBX-13002752 - R67

Contents

Page 19 of 1001

u-blox cellular modules - AT commands manual

28.3

29

HTTP................................................................................................................................ 721
29.1
29.2
29.3
29.4

30

Ping command +UPING..............................................................................................................................736
ICMP echo reply configuration +UDCONF=4........................................................................................ 738

Positioning.................................................................................................................... 739
32.1
32.2
32.3
32.4
32.5

33

SMTP control +USMTP.............................................................................................................................730
SMTP mail control +USMTPM................................................................................................................732
SMTP command +USMTPC.................................................................................................................... 734
SMTP error +USMTPER........................................................................................................................... 734

Ping.................................................................................................................................. 736
31.1
31.2

32

HTTP control +UHTTP............................................................................................................................... 721
HTTP advanced control+UHTTPAC....................................................................................................... 724
HTTP command +UHTTPC......................................................................................................................726
HTTP protocol error +UHTTPER.............................................................................................................729

SMTP.............................................................................................................................. 730
30.1
30.2
30.3
30.4

31

FTP error +UFTPER...................................................................................................................................720

NMEA............................................................................................................................................................ 739
AssistNow services................................................................................................................................... 739
GNSS............................................................................................................................................................ 740
CellLocate and hybrid positioning..........................................................................................................758
UTIME........................................................................................................................................................... 767

Location Services....................................................................................................... 769
33.1 LCS positioning capabilities configuration +UDCONF=70.................................................................769
33.2 Mobile originated location request +CMOLR.......................................................................................770
33.3 Mobile terminated location request notification +CMTLR............................................................... 772
33.4 Mobile terminated location request disclosure allowance +CMTLRA............................................ 773
33.5 Report mobile originated location request error +CMOLRE............................................................. 774
33.6 LCS event notification +ULCSEVT........................................................................................................ 775

34

DTMF.............................................................................................................................. 776
34.1
34.2
34.3

35

36

37

eCall.................................................................................................................................782
35.1
35.2
35.3
35.4
35.5
35.6
35.7
35.8
2

Introduction................................................................................................................................................. 782
eIM sends and receives data +UECALLDATA..................................................................................... 783
IVS eIM voice control +UECALLVOICE..................................................................................................786
eCall configuration +UECALLSTAT........................................................................................................ 791
eCall and InBM test configuration +UDCONF=90.............................................................................. 792
eCall type +UECALLTYPE........................................................................................................................794
Initiate eCall +CECALL............................................................................................................................. 795
eCall audio path mode setting +UECALLCFG..................................................................................... 796

36.1
36.2
36.3
36.4
36.5
36.6

Introduction................................................................................................................................................. 798
I2C open logical channel +UI2CO............................................................................................................ 798
I2C write to peripheral +UI2CW...............................................................................................................799
I2C read from peripheral +UI2CR............................................................................................................800
I2C read from peripheral register +UI2CREGR..................................................................................... 801
I2C close logical channel +UI2CC............................................................................................................ 801

I C.................................................................................................................................... 798

SAP..................................................................................................................................803
37.1
37.2
37.3

38

DTMF detection +UDTMFD......................................................................................................................776
DTMF generation +UDTMFG...................................................................................................................779
Local and in-band DTMF tone generation configuration +UDCONF=31......................................... 781

Introduction................................................................................................................................................. 803
SAP mode activation +USAPMODE.......................................................................................................803
SAP mode indications +USAPIND..........................................................................................................805

Networking................................................................................................................... 806

UBX-13002752 - R67

Contents

Page 20 of 1001

u-blox cellular modules - AT commands manual

38.1 System networking modes...................................................................................................................... 806
38.2 Change the boot mode configuration +UBMCONF............................................................................ 807
38.3 Configure the Ethernet over USB IP network +UIPCONF................................................................. 808
38.4 Interface configuration +UIFCONF........................................................................................................809
38.5 Get the USB IP configuration +UIPADDR..............................................................................................813
38.6 IP routing configuration +UIPROUTE.....................................................................................................815
38.7 IP firewall tables configuration +UIPTABLES....................................................................................... 817
38.8 IPv6 firewall tables configuration +UIP6TABLES................................................................................ 819
38.9 Configure PDP/EPS bearer connection type over USB +UDPDP......................................................820
38.10 RNDIS driver optimization configuration +UDCONF=67.................................................................. 821
38.11 Automatic default gateway route handling mechanism control +UDCONF=64..........................822
38.12 Throughput optimization via CDC-NCM or Ethernet +UDCONF=71..............................................822
38.13 Advanced DNS configuration +UDNSCONF.......................................................................................823

39

Wi-Fi................................................................................................................................825
39.1 Introduction................................................................................................................................................. 825
39.2 Web User Interface (WebUI)................................................................................................................... 828
39.3
Wi-Fi module power mode, connection manager and Cellular / Wi-Fi conflict detection+UWCFG............................................................................................................................................................. 829
39.4 Wi-Fi access point physical layer configuration +UWAPCFG.......................................................... 830
39.5 Wi-Fi access point network layer configuration +UWAPIPCFG....................................................... 832
39.6 Wi-Fi station physical layer configuration +UWSTACFG..................................................................833
39.7 Wi-Fi station network layer configuration +UWSTAIPCFG.............................................................. 835
39.8 Wi-Fi station signal level indicator +UWSTACSQ.............................................................................. 836
39.9 Wi-Fi access point connected stations list +UWAPSTALIST.......................................................... 837
39.10 Wi-Fi access point MAC address +UWAPMACADDR...................................................................... 837
39.11 Web user interface configuration +UWWEBUI.................................................................................. 838
39.12 Web user interface customization through FTP service +UWWEBUIFTP................................... 838
39.13 Wi-Fi module firmware reset +UWFWRESET....................................................................................839
39.14 Wi-Fi network scan +UWSCAN............................................................................................................ 840
39.15 Maximum allowed output power configuration +UWMP..................................................................841
39.16 Wi-Fi regulatory domains block configuration +UWREGBLOCK....................................................842
39.17 Wi-Fi test mode +UWTEST................................................................................................................... 843

A

Appendix: Error result codes.....................................................................................845
A.1 Mobile termination error result codes +CME ERROR...........................................................................845
A.2 Message service error result codes +CMS ERROR.............................................................................. 850
A.3 +CEER error result codes.......................................................................................................................... 855
A.4 Firmware install final result codes...........................................................................................................867
A.5 Firmware install with signature verification final result codes..........................................................869
A.6 FOAT error result codes............................................................................................................................ 869
A.7 Dynamic DNS unsolicited indication codes............................................................................................870
A.8 Internal TCP/UDP/IP stack class error codes......................................................................................... 871
A.9 Internet suite error classes....................................................................................................................... 873
A.10 IP change notification error result codes..............................................................................................877
A.11 Ping error result codes.............................................................................................................................. 878
A.12 Mobile termination error result codes................................................................................................... 878

B

Appendix: AT Commands List.................................................................................. 879
B.1
B.2
B.3
B.4
B.5

C

Parameters stored in profiles.................................................................................................................... 957
Parameters stored in non volatile memory............................................................................................ 964
Saving AT commands configuration....................................................................................................... 975
Estimated command response time....................................................................................................... 976
Multiple AT command interfaces............................................................................................................. 977

Appendix: UDP Direct Link workflow...................................................................... 979
C.1 Data from the IP network to the external port...................................................................................... 979
C.2 Data from the external port to the IP network......................................................................................979

D

Appendix: Glossary....................................................................................................... 981

Related documents..............................................................................................................984

UBX-13002752 - R67

Contents

Page 21 of 1001

u-blox cellular modules - AT commands manual

Revision history.................................................................................................................... 989
Contact................................................................................................................................... 1001

UBX-13002752 - R67

Contents

Page 22 of 1001

u-blox cellular modules - AT commands manual

1 AT command settings
u-blox cellular modules provide at least one physical serial interface that is compliant to V.24 [23]. When themodule 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 themodule• 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.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
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). Eachinterface works as specified by the followings definitions. If not differently stated, all the subsequentdescriptions 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.
LARA-R2 / SARA-U2 / SARA-G4 / SARA-G3
Where supported, two UART AT interfaces can be used at the same time (it is not the default behaviour).
See +USIO command description for details on how to set such behaviour.
According to the terminology used in the data sheet, UART is the main asynchronous serial interface,
while AUX UART is the auxiliary asynchronous interface. For more details on supported serial interfaces
and their characteristics, see the corresponding module data sheet.
The same naming will be used in the rest of the document (when not clearly specified, the description shallbe considered applicable to both the interfaces).
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 outcomeof 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 thecommand 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 linkare 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.
• 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.
• 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: 1) AT command port; 2) binary data port. The binary data port is used forthe exchange of binary data between the DCE and DTE. For more details, on the configuration of the TCP
ports see +UIFCONF.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The AT commands over IP connection is not supported.

UBX-13002752 - R67

1 AT command settings

Page 23 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
For more details on PSD connection see the +UPSD, +UPSDA and +UPSND commands description.
SARA-G3 / LEON-G1
For more details on CSD connection see the +UCSD, +UCSDA and +UCSND commands description.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-G450-01C / SARA-G340-02S /SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X
The AUX UART interface only supports the command mode. CSD or PSD connections are not allowed.
LARA-R211
The AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01
LARA-R211-02B-02) only supports the command mode. CSD or PSD connections are not allowed.

and

TOBY-L4
The online command mode is not supported.

1.1.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 commanddescription
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 themultiplexer 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).
• TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3 / LEON-G1 - For more details, see the u-blox
multiplexer implementation application note [168]).

1.1.2 Command description
The AT commands configure and enable the cellular module functionalities according to 3GPP normative andu-blox specifications. The AT commands are issued to the module via a hyper terminal through a commandline 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.

UBX-13002752 - R67

1 AT command settings

Page 24 of 1001

u-blox cellular modules - AT commands manual

1.1.3 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.1.4 Command line
The AT commands are typically issued to the cellular modules using a command line with the following genericsyntax:"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 commandline
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 acceptedon a single command line (including the command line termination character).
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
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.
SARA-G4
In order to synchronize the UART interface, issue the first AT command with the "AT" string in uppercase.
When writing or sending an SMS, Ctrl-Z or ESC terminates the command; <CR> is used between the twoparts of the SMS (address and text).

The serial interface driver generally does not allow a new command until the previous one has been terminatedby "OK" final result code or by an error result code. In specific cases (see the abortability attribute), thecommand execution may be aborted if a character is sent to DCE before the command has ended.
TOBY-L4
The command execution is aborted only if an AT command (the "AT" string suffices) is issued before thecommand has ended.
1.1.4.1 Concatenation of AT commands
TOBY-L4
It is not possible to concatenate the AT commands.
More than one AT command can be entered on the same command line. The "AT" prefix must be provided onlyat 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.

UBX-13002752 - R67

1 AT command settings

Page 25 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
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.1.5 Notes
TOBY-L2 / MPCI-L2• Any character entered at the end of the command line (e.g. after the <CR> has been entered) will not
be discarded but will be processed at the end of the current command execution, namely after the
result code has been issued. This usage is deprecated; it is warmly recommended to always wait for thecommand to end before entering new commands.
• The maximum length of the command line is 1024 characters.
• String parameter type limitations - The following characters are not allowed in the parameter string:o From 0x00 to 0x1F (from NUL to US)
o 0x22 (")
o 0x5C (\)
o 0xA2 (¢)
o 0xDC (Ü)
o From 0x80 to 0x9F (From ? to Y)
TOBY-L4 / LARA-R2 / TOBY-R2• The maximum length of the command line is 1024 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-U2 / LISA-U2 / LISA-U1• The maximum length of the command line is 1024 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 (")
SARA-G4 / SARA-G3 / LEON-G1• The maximum length of the command line is 544 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 (")

1.1.6 Information text responses and result codes
The AT command response comprises an optional information text string and a final result code that canassume 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

UBX-13002752 - R67

1 AT command settings

Page 26 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4
The V AT command configures the result code in numeric or verbose format.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
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.
VerboseOK

Numeric Result code type Description
0
Final
Command line successfully processed and the command iscorrectly 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 toestablish 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
8Final
No hang up detected after a fixed network timeout
CONNECT<data rate>
9Intermediate
Same as CONNECT including also the data rate (data call).
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
In case of data/fax call, see Circuit 108/2, +++ behaviour forthe different &D: summarizing table to return in commandmode and disconnect the 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

Table 1: Allowed result codes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The DISCONNECT result code is not supported.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
These result codes are not supported: NOT SUPPORT, INVALID COMMAND LINE, CR, SIM DROP.
LARA-R2 / TOBY-R2
In case of a VoLTE call redirected to CS plane the NO CARRIER final result code will be printed when the
CSFB call is terminated from the remote part or the CSFB call establishment fails.
In case of a VoLTE call experiencing entrance into out of coverage area, if service coverage cannot be
regained within 10 s the call will be locally dropped and NO CARRIER will be printed; if the call is a VoLTE
emergency call, NO CARRIER will not be printed and no local call release will be performed because theemergency call shall be maintained despite the speech interruption.
As already stated in the Preface section (see the "Can be aborted" attribute), some AT commands can beaborted after having issued them.
TOBY-L2 / MPCI-L2
The AT commands cannot be aborted, except if explicitly stated in the corresponding AT commanddescription.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
When a command is aborted the ABORTED final result code (numeric result code: 18) is displayed.
SARA-G4 / SARA-G3 / LEON-G1
When a command is aborted the OK result code (numeric result code: 0) is displayed.

UBX-13002752 - R67

1 AT command settings

Page 27 of 1001

u-blox cellular modules - AT commands manual

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 commanddescription), additional command line termination and linefeed characters may be inserted for sake ofreadability.
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 commandsetting.
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)
TOBY-L2 / MPCI-L2
The AT command parser accepts optional commas at the end of the command line, as well as String
parameters not delimited by "".
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 andprovide different error result codes:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - Firmware update Over The Air:see the Appendix A.4• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - Firmware update Over AT command: see the Appendix A.6• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- DNS: see the Appendix A.7 and Appendix A.8• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- TCP and UDP connections: see the Appendix A.8, Appendix A.9• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- FTP: see the Appendix A.9.1• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- HTTP: see the Appendix A.9.2• SARA-G3 / LEON-G1 - SMTP: see the Appendix A.9.3• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 - IP change
notification: see the Appendix A.10
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 / LEON-G1 - Ping: see
the Appendix A.11
The corresponding sections provide more details for retrieving the error result codes for these operations.

1.2 Storing of AT commands setting
Several user settings may be stored in the cellular module's memory. Some are directly stored in the non volatilememory (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.
Appendix B.1 lists the complete settings stored in the profiles and the corresponding commands.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
More details about loading, storing and updating profiles can be found in the command descriptions for:
ATZ, AT&F, AT&W, AT&V, and AT&Y.
TOBY-L4
The module allows to store +COPS and S0 settings in the single profile it supports: since only one profile
is available, the AT&Y command is not supported; more details about updating such profile on TOBY-L4
series can be found in the command description of AT&W.

UBX-13002752 - R67

1 AT command settings

Page 28 of 1001

u-blox cellular modules - AT commands manual

1.3 S-parameters
The S-parameters, as specified in ITU-T recommendation V250 [19], constitute a group of commands thatbegin with the string "ATS". They are generally indicated as S registers and are used to configure the way themodule 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
S0
S2
S3
S4
S5
S6
S7
S8
S10
S12

S Number
0
2
3
4
5
6
7
8
10
12

Description
Automatic answer setting
Escape character setting
Command line termination character setting
Response formatting character setting
Command line editing character setting
Pause before blind dialling setting
Connection completion timeout setting
Command dial modifier time setting
Automatic disconnect delay setting
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.4 +UDCONF AT command
The UDCONF AT commands constitute a group of u-blox proprietary AT commands that allow to configuresome 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 thecorresponding "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.

UBX-13002752 - R67

1 AT command settings

Page 29 of 1001

u-blox cellular modules - AT commands manual

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 thecorresponding 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.
TOBY-L4
After a successful boot and successful AT command interface initialization, if the USB cable is alreadyinserted, an +AT: READY URC is sent to the AT command interface. AT commands can be issued only
after +AT: READY URC is received. In case of USB cable detach/attach the +AT: READY URC is received
only after at least a byte has been sent to the module.
A complete start up including cellular network operation can only take place with a SIM card.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
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 cardis re-established by the module after an unrecoverable error, caused e.g. by mechanical vibrations or electricalinterference. If no SIM is inserted in the module, the module will anyway select a cell of the cellular network andtry to maintain synchronization with it in limited service.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
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.
TOBY-L4
During the auto-registration any further network request (by means of AT+COPS=0 or AT+COPS=1) will
be rejected and an error result code will be provided. A new +COPS AT command shall be issued.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
The radio access technology selected by the module at start up is defined by the <PreferredAct>
parameter of the +URAT command; afterwards the module will reselect the RAT based on therequirements 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 or on a specific cell via +UCELLLOCK (if supported).
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 boottime 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 failuresof 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:

UBX-13002752 - R67

2 General operation

Page 30 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•

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 themodule is restarted in +CFUN: 4 or +CFUN: 19 modes, because they are persistent
MPCI-L2 only - when the W_DISABLE# line is asserted
TOBY-L2 / SARA-U2 / LISA-U2 - The Radio Policy Manager has reached the maximum number ofregistrations or PDP contexts activation per hour (only with AT&T SIM cards [48])In case the module is in operational restricted state, it may reject all or specific service requests (e.g. operator
selection, connection establishment).
MPCI-L2
When the W_DISABLE# line is asserted, to SW reset the module, AT+CFUN=0,1 or AT+CFUN=4,1 may be
used as they refer to minimum functionality power modes.
TOBY-L2 / MPCI-L2
If the SIM is not inserted or the PIN is required and not inserted, the network scan (+COPS=?) is notallowed.

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 likemanufacturer name, firmware version, etc.

2.2.2 Set commandA 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.
TOBY-L2 / MPCI-L2
The set command without parameters (e.g. AT+CGEQREQ=) is syntactically equivalent to the actioncommand (e.g. AT+CGEQREQ).

2.2.3 Read commandA read command provides the current setting of the command parameters. It is used to find out the current
command configuration.

2.2.4 Test commandA 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 informationtext response to a previous AT command and can be output, when enabled, at any time to inform the DTE ofa 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 anothercommand (e.g. the +CMTI URC must be enabled by AT+CNMI AT command).
2.2.5.1 URCs presentation deferring
TOBY-L4
The URCs presentation deferring is not supported.
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 ATcommand's text response or viceversa.

UBX-13002752 - R67

2 General operation

Page 31 of 1001

u-blox cellular modules - AT commands manual

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, formost 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 forthe executing command (e.g.: ATH); in case it is handled as an unsolicited result code, it follows the rule of theother URCs.
Generally, the buffered URCs are sent to the terminal as soon as the terminal exits the data mode or thecommand execution is terminated. An exception to this behavior is implemented for the following URCs
classes:Class
Reception of a new SMS related URCs
+CIEV URCs
+CGEV URCs

AT command to configure the class
AT+CNMI AT command
AT+CMER AT command
AT+CGEREP 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 [2]; the buffering or discarding are the two possible choices (URCs are lost in the lattercase). This is done by means of the corresponding AT command (see the AT command listed in the table above).
If the URCs are enabled or for the three described classes of URCs, the buffered URCs are sent out only whenthe 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
LARA-R204
The presentation of +UCMT3GPP2 URCs is not deferred and is always routed to the AT interface.
LEON-G1
The modules does not support the full URCs buffering/deferring capability: only the presentation
deferring of the three above specified URCs classes is supported.
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 totransmit 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.

UBX-13002752 - R67

2 General operation

Page 32 of 1001

u-blox cellular modules - AT commands manual

3 IPC - Inter Processor Communication
3.1 Multiplexing mode +CMUX+CMUXModules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-60S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

3.1.1 Description
Enables the multiplexing protocol control channel as defined in 3GPP TS 27.010 [40]. The command sets theparameters 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

TOBY-L2
TOBY-R2
LARA-R202 / LARA-R203 /LARA-R211 / LARA-R220 /LARA-R280
LARA-R204
SARA-U2
LISA-U2
LISA-U200-00S
LISA-U1
SARA-G450-01C
SARA-G450-00C
SARA-G340 / SARA-G350
SARA-G300 / SARA-G310
LEON-G1

Channel 0
Channel 0
Channel 0

AT commands / data GNSS tunnelingconnection
Channel 1 - 5
Channel 1 - 5
Channel 61
Channel 1 - 5
Channel 62

Channel 0
Channel 0
Channel 0
Channel 0
Channel 0
Channel 0
Channel 0
Channel 0
Channel 0
Channel 0

Channel 1 - 5
Channel 1 - 5
Channel 1 - 5
Channel 1 - 5
Channel 1 - 5
Channel 1 - 5
Channel 1 - 5
Channel 1 - 5
Channel 1 - 2
Channel 1 - 5

Channel 6
Channel 6
Channel 6
Channel 6
Channel 6

SAP (SIM AccessProfile)Channel 7
Channel 7

Channel 6
Channel 6

Table 2: Multiplexer configuration

3.1.2 Syntax
Type
Set

Read

SyntaxAT+CMUX=<mode>[,<subset>[,<port_speed>[,<N1>[,<T1>[,<N2>[,<T2>[,<T3>[,<k>]]]]]]]
AT+CMUX?

Test

AT+CMUX=?

1
2

Response
OK

ExampleAT+CMUX=0,0,,1500,50,3,90
OK+CMUX: <mode>,[<subset>],<port_ +CMUX: 0,0,0,1500,253,3,254,0,0
speed>,<N1>,<T1>,<N2>,<T2>,
OK<T3>[,<k>]OK+CMUX: (list of supported+CMUX: (0),(0),,(1-1509),(1-255),(0<mode>s),(list of supported
5),(2-255),,<subset>s),(list of supported <port_OK
speed>s),(list of supported <N1>s),

Not supported by TOBY-R200-02B-00 and TOBY-R202-02B-00
Not supported by LARA-R211-02B-00

UBX-13002752 - R67

3 IPC - Inter Processor Communication

Page 33 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Example(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

3.1.3 Defined values
Parameter<mode>

Type
Number<subset>Number<port_speed>

Number

<N1>

Number

<T1>

Number

<N2>

Number

<T2>

Number

<T3>

Number<k>

NumberDescription
Multiplexer transparency mechanism:• 0: basic option
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.
Transmission rate. The allowed range is 0-7.
This parameter is ignored and the value 0 is always displayed in case of readcommand.
Maximum frame size:• Allowed range is 1-1509.
• The default value is 31.
Acknowledgement timer in units of ten milliseconds. The allowed range is 1-255.
This parameter is ignored and the value 253 is always set.
Maximum number of re-transmissions:• Allowed range is 0-5.
• The default value is 3.
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.
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 readcommand.
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 readcommand.

3.1.4 Notes•••

If the multiplexer protocol is not started (the +CMUX set command has not been issued or returned anerror 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>.

TOBY-L2• <subset> can only assume the value 0.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• <subset> can only assume the value 0.
• <T1>, <T2>, <N2> values are ignored, since the related timers are not implemented.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the multiplexer protocol is not supported.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• On the AUX UART interface, the multiplexer protocol is not supported.

UBX-13002752 - R67

3 IPC - Inter Processor Communication

Page 34 of 1001

u-blox cellular modules - AT commands manual

SARA-G4 / SARA-G3• <subset> can assume the value 0 and 1.
• The range of <T2> is 0-255 (0 means that the timer is ignored).
SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S• <subset> can only assume the value 0.
SARA-G450-01C / SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S /SARA-G350-02X• On the AUX UART interface, the multiplexer protocol is not supported.
LEON-G1• <subset> can only assume the value 0.
• The requested <N1> value is correctly set, but the +CMUX read command returns a value higher (<N1>+6
or <N1>+7), since it returns the maximum multiplexer protocol frame size (including the 6 or 7 bytes of theframe header). This does not affect the multiplexer protocol behavior, which uses the requested value.
• The range of <T2> is 0-255 (0 means that the timer is ignored).
LEON-G100-06S• <port_speed>, <T3> and <k> can only assume the value 0.

UBX-13002752 - R67

3 IPC - Inter Processor Communication

Page 35 of 1001

u-blox cellular modules - AT commands manual

4 General
4.1 Manufacturer identification +CGMI+CGMI
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.1.1 Description
Text string identifying the manufacturer.

4.1.2 Syntax
Type
ActionSyntaxAT+CGMI

Response<manufacturer>

Exampleu-bloxAT+CGMI=?

OK
OK

OK

Test

4.1.3 Defined values
Parameter<manufacturer>

Type
StringDescription
Manufacturer name

4.2 Manufacturer identification +GMI
+GMI
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.2.1 Description
Text string identifying the manufacturer.

4.2.2 Syntax
Type
ActionSyntax
AT+GMI

Response<manufacturer>

Exampleu-bloxOK

OK

4.2.3 Defined values
Parameter<manufacturer>

Type
StringDescription
Manufacturer name

4.3 Model identification +CGMM+CGMM
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.3.1 Description
Text string identifying the model identification.

UBX-13002752 - R67

4 General

Page 36 of 1001

u-blox cellular modules - AT commands manual

4.3.2 Syntax
Type
ActionSyntaxAT+CGMM

Response<model>ExampleLISA-U200

AT+CGMM=?

OK
OK

OK

Test

4.3.3 Defined values
Parameter<model>Type
StringDescription
Name of model

4.4 Model identification +GMM
+GMM
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.4.1 Description
Text string identifying the model identification.

4.4.2 Syntax
Type
ActionSyntax
AT+GMM

Response<model>ExampleLISA-U120

OK

OK

4.4.3 Defined values
Parameter<model>Type
StringDescription
Name of model

4.5 Firmware version identification +CGMR+CGMR
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.5.1 Description
Returns the firmware version of the module.

4.5.2 Syntax
Type
ActionSyntaxAT+CGMR

Response<version>

Example11.40

AT+CGMR=?

OK
OK

OK

Test

4.5.3 Defined values
Parameter<version>

UBX-13002752 - R67

TypeStringDescription
Firmware version

4 General

Page 37 of 1001

u-blox cellular modules - AT commands manual

4.6 Firmware version identification +GMR
+GMR
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.6.1 Description
Returns the firmware version of the module.

4.6.2 Syntax
Type
ActionSyntax
AT+GMR

Response<version>

Example
11.40

OK

OK

4.6.3 Defined values
Parameter<version>

Type
StringDescription
Firmware version

4.7 Request product serial number identification +CGSN+CGSN
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+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
SyntaxGeneric syntax
Set
AT+CGSN[=<snt>]

Response

Example[+CGSN: ]<param_val>

AT+CGSN=0OK357520070120767
OK

Serial number request
Set
AT+CGSN[=0]<sn>

AT+CGSNOK

357520070120767
OK

IMEI request
Set
AT+CGSN=1+CGSN: <imei>

AT+CGSN=1

OK+CGSN: "357520070120767"
OK

IMEISV request
Set
AT+CGSN=2+CGSN: <imeisv>

AT+CGSN=2

OK+CGSN: "3575200701207601"
OK

SVN request
Set
AT+CGSN=3+CGSN: <svn>

AT+CGSN=3

OK+CGSN: "01"OK

UBX-13002752 - R67

4 General

Page 38 of 1001

u-blox cellular modules - AT commands manualType
Syntax
Full IMEI and SVN request
Set
AT+CGSN=255

Response

Example<imei_full>

AT+CGSN=255

OK35752007012076701
OK

Test

AT+CGSN=?

+CGSN: (list of supported <snt>s)+CGSN: (0-3,255)

OKOK

4.7.3 Defined values
Parameter
<snt>

Type
Number<sn><imei>

NumberString<imeisv>

String<svn><imei_full

StringNumber<param_val>

Number/StringDescription
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
MT serial number, typically the International Mobile station Equipment Identity (IMEI)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).
International Mobile station Equipment Identity and Software Version Number(IMEISV). The 16 digits of IMEISV are composed of Type Allocation Code (TAC) (8digits), Serial Number (SNR) (6 digits) and the software version (SVN) (2 digits).
Software Version Number (SVN) which is a part of IMEISV.
International Mobile station Equipment Identity (IMEI), Check Digit and Software
Version Number.
Type and supported content depend on related <snt> (details are given above)

4.7.4 Notes
TOBY-L4906-50A / TOBY-L2 / MPCI-L2 / SARA-U260-00S / SARA-U270-00S / SARA-U270-00X /SARA-U280-00S / LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S /LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The <snt> parameter is not supported.
• The response to the test command does not provide the information text response.

4.8 IMEI identification +GSN
+GSN
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.8.1 Description
The commands handling is the same of +CGSN.

4.8.2 Syntax
Type
ActionSyntaxAT+GSN[=<snt>]

Response<sn>

Example004999010640000

AT+GSN=?

OK
OK

OK

Test

UBX-13002752 - R67

4 General

Page 39 of 1001

u-blox cellular modules - AT commands manual

4.8.3 Defined values
See +CGSN AT command.

4.9 Identification information I
I
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+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 themodule where applicable; it returns "Undefined" where not applicable.

4.9.2 Syntax
Type
ActionSyntaxType number request
ATI[0]

Response<type_number>

ExampleATI0

OK

SARA-G350-00S-00

Module boot sequence version
request
ATI6<module_boot_sequence_version>

OK
ATI6

OK

1

Modem and application version
request
ATI9<modem_version>,<applications_version>
OK

OK
ATI9
29.90,A01.00
OK

4.9.3 Defined values
Parameter<manufacturer><type_number><ordering_code><modem_version><FW_rel_date><applications_version><SVN><IMEI><module_boot_sequence_version>

Type
StringStringStringStringStringStringDescription
Manufacturer nameProduct type number
Product ordering code
Module modem version
Firmware release date and time
Module application version. Where not applicable the module provides "Undefined"

StringStringNumberSoftware Version Number
International Mobile Equipment Identity (IMEI) of the MT
Module boot sequence version. Where not applicable the module provides"Undefined"

4.10 TE character set configuration +CSCS+CSCS
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+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 typeparameters whose description explicitly references the +CSCS setting itself.

UBX-13002752 - R67

4 General

Page 40 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
The command setting is not stored in the profile.
SARA-G4
The command setting is stored in the NVM following the procedure described in the Saving AT commands
configuration section.

4.10.2 Syntax
Type
Set

SyntaxAT+CSCS=<chset>

Response
OK

ExampleAT+CSCS="IRA"

Read

AT+CSCS?

+CSCS: <chset>

OK+CSCS: "IRA"

Test

AT+CSCS=?

OK
OK+CSCS: (list of supported <chset>'s) +CSCS: ("IRA","GSM","PCCP437","8859-1","UCS2","HEX", "PCCP936")
OKOK

4.10.3 Defined values
Parameter<chset>Type
StringDescription
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; noconversions to the original MT character set shall be done• "PCCP936": Chinese character set
Allowed values:• TOBY-L4 - "IRA" (factory-programmed value), "GSM", "UCS2", "HEX"• TOBY-L2 / MPCI-L2 - "IRA" (factory-programmed value), "GSM", "8859-1", "UCS2","HEX"• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 "IRA" (factory-programmed value), "GSM", "PCCP437", "8859-1", "UCS2", "HEX"• SARA-G4 - "IRA", "GSM" (factory-programmed value), "UCS2", "HEX"

4.10.4 Notes
SARA-G4• If <chset>="IRA", only SMS commands are affected; for other commands, "GSM" character set is valid.

4.11 International mobile subscriber identification +CIMI+CIMI
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.11.1 Description
Request the IMSI (International Mobile Subscriber Identity).

4.11.2 Syntax
Type
ActionSyntaxAT+CIMIUBX-13002752 - R67

Response<IMSI>

4 General

Example222107701772423

Page 41 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+CIMI=?

Response
OK
OK

ExampleOK

4.11.3 Defined values
Parameter<IMSI>

Type
NumberDescription
International Mobile Subscriber Identity

4.12 Card identification +CCID+CCID
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+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
ActionSyntaxAT+CCID

Response+CCID: <ICCID>

Example+CCID: 8939107800023416395

Read

AT+CCID?

OK+CCID: <ICCID>

OK+CCID: 8939107900010087330

AT+CCID=?

OK
OK

OK

Test

4.12.3 Defined values
Parameter<ICCID>Type
StringDescription
ICCID of the SIM card

4.12.4 Notes•

The command needs of the SIM to correctly work.

4.13 Request complete capabilities list +GCAP+GCAPModules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.13.1 Description
This command requests the list of capabilities, containing the corresponding command names. The Complete
Capabilities List command indicates the major capability areas of the MT. Each area is presented by theselection command name of the specific capability area or some other predefined response.
The first response text (+FCLASS) informs that some fax or voice capabilities are present while the second
supported area presented with +CGSM shows that all GSM commands of the present document are supported.

4.13.2 Syntax
Type
ActionSyntaxAT+GCAP

Response+GCAP: <capability_area 1>[,
<capability_area 2>[...]]

Example+GCAP: +FCLASS, +CGSM
OK

OK

UBX-13002752 - R67

4 General

Page 42 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+GCAP=?

Response
OK

Example4.13.3 Defined values
Parameter<capability_area>

Type
StringDescription
Command name or predefined response of the specific capability area
In the example: +FCLASS response text informs that some fax or voice capabilities
are present, while +CGSM response text shows that all GSM commands of thepresent document are supported by the MT

4.14 Repeat last command A/
A/
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.14.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.14.2 Syntax
Type
ActionSyntaxA/

Response

Example4.15 List all available AT commands +CLAC+CLAC
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.15.1 Description
Causes the MT to return one or more lines of AT commands that are available for the DTE user. Each line
contains one AT command.

4.15.2 Syntax
Type
ActionSyntaxAT+CLAC

Response<AT command 1>

Example[<AT command 2>[...]]
Test

AT+CLAC=?

UBX-13002752 - R67

OKOK

4 General

Page 43 of 1001

u-blox cellular modules - AT commands manual

4.15.3 Defined values
Parameter<AT command>

Type
StringDescription
AT command name4.16 Help displaying all commands &H&H
Modules

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Attributes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

4.16.1 Description
Lists all the supported commands.

4.16.2 Syntax
Type
ActionSyntaxAT&H

Response
Example<AT command 1> : <AT command 1 ATA : Answer an Incoming Calltitle>[<CR><LF><AT command 2> :ATE : Echo
<AT command 2 title>
ATH : Hook Control[...]]ATV : Enable/Disable verbose
OK
response...
AT+UTEST : End User Test
ATS : Query or Set an S-register
ATD : Dial
OK

4.16.3 Defined values
Parameter<AT command n><AT command ntitle>Type
StringStringDescription
AT command name
AT command title

4.16.4 Notes
TOBY-L2 / MPCI-L2 / SARA-G3 / LEON-G1• The response is:<AT command 1>, <AT command 2>, ..., <AT command n>[,<CR><LF><AT command n+1>, ..., <ATcommand n+m>[...]]OK
Example:&W, &Y, A, B, E, H, I, L, M, O, P, Q, S0, S10, S12,S2, S3, S4, S5, S6, S7, S8, T, V, X, Z, \Q,...
+USORD, +USORF, +USOSO, +USOST, +USOWR, +USPM, +USTN,+USTOPFILE, +USTS, +UTEST, +UTGN, +UUBF

UBX-13002752 - R67

4 General

Page 44 of 1001

u-blox cellular modules - AT commands manual

OK

UBX-13002752 - R67

4 General

Page 45 of 1001

u-blox cellular modules - AT commands manual

5 Mobile equipment control and status
5.1 Phone activity status +CPAS+CPAS
Modules

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Attributes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

5.1.1 Description
Returns the activity status <pas> of the MT.

5.1.2 Syntax
Type
ActionSyntaxAT+CPAS

Response+CPAS: <pas>

Example+CPAS: 0

Test

AT+CPAS=?

OK+CPAS: (list of supported <pas>s)

OK+CPAS: (0-5)

OKOK

5.1.3 Defined values
Parameter
<pas>

Type
NumberDescription
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:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G3 / LEON-G1 - 0, 1, 2, 3, 4, 5

5.1.4 Notes
TOBY-L2 / MPCI-L2• During a MO call the information text response of the action command returns 4 (call in progress).
• The reported status <pas> of the MT is tied to network status registration.

5.2 Module switch off +CPWROFF+CPWROFF
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time
< 40 sError reference+CME Error

5.2.1 Description
Switches off the MT. During shut-down current settings are saved in module's non-volatile memory.
Using this command can result in the following command line being ignored.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 46 of 1001

u-blox cellular modules - AT commands manual

See the corresponding System Integration Manual for the timing and the electrical details of the module
power-off sequence via the +CPWROFF command.
MPCI-L2
The command does not switch off the PCIe module but it causes a reset (reboot). The current parametersettings are stored in the NVM performing a network detach, with a subsequent module reset (reboot).

5.2.2 Syntax
Type
ActionTest
URC

SyntaxAT+CPWROFF
AT+CPWROFF=?

Response
OK
OK+UCPWROFF

Example+UCPWROFF

5.2.3 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• The +UCPWROFF URC is not supported.

5.3 Set module functionality +CFUN+CFUN
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
No
No

Response time
Up to 3 min

Error reference+CME Error

5.3.1 Description
Selects the level of functionality <fun> in the MT.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
If the syntax AT+CFUN=15 or AT+CFUN=16 (resets) or AT+CFUN=127 is used, the rest of the command
line, placed after that will be ignored.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
A SW reset started via AT+CFUN=x,1 or AT+CFUN=16 triggers signalling attempts whose number isinternally counted by the FW and limited based on mobile network operators' thresholds. The AT&T RPM
feature (see also the +URPM AT command) 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
Set

SyntaxAT+CFUN=<fun>[,<rst>]

Response
OK

Read

AT+CFUN?

+CFUN: <power_mode>,<STK_
mode>

Test

AT+CFUN=?

OK+CFUN: (list of supported <fun>'s),(list of supported <rst>'s)

ExampleAT+CFUN=1
OK+CFUN: 1,0
OK+CFUN: (0,1,4,6,7,8,15,16),(0-1)
OKOK

5.3.3 Defined values
Parameter<fun>

UBX-13002752 - R67

Type
NumberDescription
Selected functionality:• 0: sets the MT to minimum functionality (disable both transmit and receive RF
circuits by deactivating both CS and PS services)

5 Mobile equipment control and status

Page 47 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 1 (factory-programmed value): sets the MT to full functionality, e.g. from airplanemode 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=16 or AT+CPWROFF (where supported)• 6: enables the SIM toolkit interface in dedicated mode and fetching of proactive
commands by SIM Application Toolkit from the SIM card
• 7 or 8: disables the SIM toolkit interface and fetching of proactive commands by
SIM Application Toolkit from the SIM card
• 9: enables the SIM toolkit interface in raw mode and fetching of proactive
commands by SIM Application Toolkit from the SIM card
• 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, cachedsettings are discarded and not saved.
• 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), withreset of the SIM card
• 19: sets the MT to minimum functionality by deactivating CS and PS services andthe SIM card
• 127: sets the MT in a deep low power state "HALT" (with detach from the networkand saving of the NVM parameters); the only way to wake up the module is a power
cycle or a module reset
Allowed values:• TOBY-L4 - 0, 1, 4, 6, 7, 8, 15, 16, 19• TOBY-L2 / MPCI-L2 - 0, 1, 4, 6, 9, 15, 16, 19, 127• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - 0, 1, 4, 6, 7, 8, 9, 15, 16• SARA-G4 - 0, 1, 7, 8, 15, 16• SARA-G3 / LEON-G1 - 0, 1, 6, 7, 8, 15, 16
Reset mode. This parameter can be used only when <fun> is 1, 4 or 19.
• 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><rst>

Number<power_mode>

Number••••0: MT is switched on with minimum functionality
1: MT is switched on
4: MT is in "airplane mode"
19: MT is in minimum functionality with SIM deactivated<STK_mode>

Number

•6: the SIM-toolkit interface in dedicated mode and fetching of proactive commands
by SIM-APPL from the SIM-card are enabled
0, 7 or 8: the SIM-toolkit interface is disabled; fetching of proactive commands by
SIM-APPL from the SIM-card is enabled
9: the SIM-toolkit interface in raw mode and fetching of proactive commands by
SIM-APPL from the SIM-card are enabled••

5.3.4 Notes
TOBY-L4• AT+CFUN=19 does not support the <rst> parameter.
• <STK_mode>=9 is not supported.
• The MT silent reset without the SIM card reset (<fun>=15) restarts the protocol stack tasks (without
triggering a detach if the module is attached) while retaining the SIM status, i.e. the PIN shall not be
inserted again. This mimics a silent reset and sets the module in a known initial state. Drivers andapplications are not restarted, therefore if e.g audio was active, it might be negatively affected by
the AT+CFUN=15 command. Additionally, most volatile parameters (e.g. URC) are lost and need to bereconfigured.
TOBY-L2 / MPCI-L2• After enabling the STK interface in raw mode it is not possible to switch to dedicated mode (and viceversa) without performing a reset.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 48 of 1001

u-blox cellular modules - AT commands manual•••<fun>=15 restarts the protocol stack tasks (without triggering a detach if the module is attached) while
retaining the SIM status, i.e. the PIN shall not be inserted again. This mimics a silent reset and sets
the module in a known initial state. Drivers and applications are not restarted, therefore if e.g. a MUX
port was opened, communication with it is maintained, unless the AT+CFUN=15 interrupts a pending AT
command requiring interaction with the protocol stack, in which case communication on MUX channels
can be negatively affected. Additionally, most non-volatile parameters are not saved, as this kind of reset
does not imply a complete module restart<rst> parameter is ignored when entered after a <fun> not supporting reset.
In case the application needs to interact with the SIM, the AT+CFUN=1 command must be issued after
the AT+CFUN=19 command.

TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03A /TOBY-L280-03S / MPCI-L200-03S / MPCI-L210-03S / MPCI-L280-03S• The AT+CFUN=15 command issued in SAP client mode (+USAPMODE: 1) will disable the remote SIM
connection and restart the protocol stack on the local SIM card.
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• <fun>=15 behaves as <fun>=16: the MT is reset as well as the SIM card.
• <fun>=4 is not persistent between power cycles.
LARA-R2 / TOBY-R2• A change of module functionality via <fun>=0, 1 or 4 also triggers the reset of the UICC driver, hence canbe used to refresh the SIM card status after a SIM insertion or removal.
SARA-U2 / LISA-U2 / LISA-U1• <power_mode>=19 is not supported.
• The AT+CFUN=15 command shall not be issued in SAP client mode (+USAPMODE: 1).
SARA-G4• After setting <fun>=0, ensure the module is detached from network before setting the <fun> parameterwith any other value.
• <fun>=15 behaves as <fun>=16: the MT is reset as well as the SIM card.
• <rst>=1 can be used only if <fun>=1.
• <power_mode>=19 is not supported.
• <STK_mode>=6 and 9 are not supported.
SARA-G3 / LEON-G1• After setting <fun>=0, ensure the module is detached from network before setting the <fun> parameterwith any other value.
• <fun>=15 behaves as <fun>=16: the MT is reset as well as the SIM card.
• <rst>=1 can be used only if <fun>=1.
• <power_mode>=19 is not supported.
• <STK_mode>=9 is not supported.

5.4 Indicator control +CIND+CIND
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+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, sothat the first <ind> corresponds to "battchg" and so on.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 49 of 1001

u-blox cellular modules - AT commands manual

For more details see the 3GPP TS 27.007 [2].

5.4.2 Syntax
Type
Set

SyntaxAT+CIND=[<ind>[,<ind>[,...]]]

Response
OK

ExampleAT+CIND=

Read

AT+CIND?

+CIND: <ind>[,<ind>[,...]]

OK+CIND: 5,0,0,0,0,0,0,0,0,0,0,0

Test

AT+CIND=?

OK+CIND: (list of <descr>s)
OK

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

Type
Number<descr>StringUBX-13002752 - R67

Description
Range of corresponding <descr> used to identify the service when an unsolicitedindication is provided
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 networko 1: registered to the networko 65535: indication not available• "sounder": sounder activity, indicating when the module is generating a soundo 0: no soundo 1: sound is generated• "message": unread message available in <mem1> storageo 0: no messageso 1: unread message available• "call": call in progresso 0: no call in progresso 1: call in progress• "roam": registration on a roaming networko 0: not in roaming or not registeredo 1: roamingo 65535: indication not available• "smsfull": indication that an SMS has been rejected with the cause of SMS storagefull
o 0: SMS storage not fullo 1: SMS storage full• "gprs": PS indication status:o 0: no PS available in the networko 1: PS available in the network but not registeredo 2: registered to PS
o 65535: indication not available• "callsetup": call set-up:
o 0: no call set-upo 1: incoming call not accepted or rejectedo 2: outgoing call in dialling stateo 3: outgoing call in remote party alerting state• "callheld": call on hold:o 0: no calls on holdo 1: at least one call on hold5 Mobile equipment control and status

Page 50 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• "simind": SIM detectiono 0: no SIM detectedo 1: SIM detectedo 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
0
1
2
3
4
5

Power level(< -105 dBm or unknown)(< -93 dBm)(< -81 dBm)(< -69 dBm)(< -57 dBm)(>= -57 dBm)

TOBY-L4• <descr>="battchg", "signal", "service", "sounder", "message", "smsfull", "gprs", "callsetup", "callheld" arenot supported.
• The value "2" for the "simind" indicator is not supported.
• The set command allows enabling (1) or disabling (0) each indicator (i.e. to enable the SIM indication issue
the command AT+CIND=,,1). All indicators are by default enabled.
TOBY-L4906-50A• All indicators are by default disabled.
TOBY-L2 / MPCI-L2• The value "2" for the "simind" indicator is not supported.
• The set command is actually a dummy command always returning the "OK" final result code.
TOBY-L200-00S / TOBY-L201-01S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S /MPCI-L201-01S / MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• <descr>="simind" is not supported.
• The "callsetup", "callheld", "sounder" indications are not provided.
TOBY-L201-02S / MPCI-L201-02S• The "callsetup", "callheld", "sounder" indications are not provided.
SARA-U2 / LISA-U2 / LISA-U1• To enable the "SIM detection" feature the SIM_DET pin must be properly configured (if not already set);
for more details see the GPIO introduction and +UGPIOC command description.
SARA-G340 / SARA-G350• If the battery charging is not supported, "battchg" always returns 0 (full charge).
• <descr>="sounder" indication is always set to 0, hence the +CIEV: 4,x URC is never displayed.
SARA-G300 / SARA-G310 / LEON-G1• <descr>="simind" is not supported.
• <descr>="sounder" indication is always set to 0, hence the +CIEV: 4,x URC is never displayed.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 51 of 1001

u-blox cellular modules - AT commands manual

5.5 Configuration of indicator control +UCIND+UCIND
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

5.5.1 Description
Allows the configuration of unsolicited results for indications with +CIEV.

5.5.2 Syntax
Type
Set

SyntaxAT+UCIND=[<conf>]

Response
OK

ExampleAT+UCIND=7

Read

AT+UCIND?

+UCIND: <conf>

OK+UCIND: 7

Test

AT+UCIND=?

OK
OK

OK

5.5.3 Defined values
Parameter<conf>

Type
NumberDescription
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 ordernumber (see the <descr> parameter of +CMER). The least significant bit is used forthe 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).

5.6 Mobile termination event reporting +CMER+CMER
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

5.6.1 Description
Configures sending of URCs from MT to DTE for indications. The <mode> parameter controls the processingof URCs specified within this command.
The URC is generated each time an indicator which is defined in +CIND command changes status. The code isactually submitted to MT according to the +CMER settings.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
The command +UCIND allows enabling or disabling indicators.

5.6.2 Syntax
Type
Set

SyntaxAT+CMER=[<mode>[,<keyp>[,<disp>[,<ind>[,<bfr>]]]]]

Response
OK

Read

AT+CMER?

+CMER: <mode>,<keyp>,<disp>,<ind>,<bfr>

Test

AT+CMER=?

UBX-13002752 - R67

OK+CMER: (list of supported<mode>'s),(list of supported

5 Mobile equipment control and status

ExampleAT+CMER=1,0,0,2,1
OK+CMER: 1,0,0,0,1
OK+CMER: (0-3),(0),(0),(0-2),(0,1)

Page 52 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Example<keyp>'s),(list of supported
OK<disp>'s),(list of supported <ind>'s),(list of supported <bfr>'s)
OK+CIEV: <descr>,<value>

URC

5.6.3 Defined values
Parameter<mode>

Type
Number<keyp>

Number<disp>

Number<ind>

Number<bfr>

Number<descr>NumberUBX-13002752 - R67

Description
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
Allowed values:• 0: no keypad event reporting
Allowed values:• 0: no display event reporting
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 bedirected from MT to DTE.
Allowed values:• 0: MT buffer of URCs defined within this command is cleared when <mode> 1...3 isentered• 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 thecodes).
Indicates the indicator order number. The name in the brackets indicates thecorresponding <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 levelo 0: < -105 dBmo 1: < -93 dBmo 2: < -81 dBm
o 3: < -69 dBm
o 4: < - 57 dBmo 5: >= -57 dBm• 3 ("service"): <value> provides the network service availability:o 0: not registered to the networko 1: registered to the network• 4 ("sounder"): <value> provides the sounder activity:o 0: no soundo 1: sound is generated• 5 ("message"): <value> provides the unread message available in <mem1> storage:o 0: no messageso 1: unread message available• 6 ("call"): <value> provides the call in progress:
o 0: no call in progresso 1: call in progress• 7 ("roam"): <value> provides the registration on a roaming network:o 0: not in roamingo 1: roaming• 8 ("smsfull"): <value> provides the SMS storage status:o 0: SMS storage not full

5 Mobile equipment control and status

Page 53 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Descriptiono 1: SMS Storage full (an SMS has been rejected with the cause of SMS storagefull)• 9 ("gprs"): <value> provides the GPRS indication status:o 0: no GPRS available in the networko 1: GPRS available in the network but not registeredo 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-upo 1: incoming call not accepted or rejectedo 2: outgoing call in dialing stateo 3: outgoing call in remote party alerting state• 11 ("callheld"): <value> provides the call on hold:o 0: no calls on holdo 1: at least one call on hold• 12 ("simind"): <value> provides the SIM detection:o 0: no SIM detectedo 1: SIM detectedo 2: not available

5.6.4 Notes
TOBY-L4• <ind>=2 is not supported.
• <descr>=1 ("battchg", battery charge level), 2 ("signal", signal quality), 3 ("service", network service
availability), 4 ("sounder", sounder activity), 5 ("message", unread message available in <mem1> storage),
8 ("smsfull", SMS storage status), 9 ("gprs", GPRS indication status), 10 ("callsetup", call set-up), 11("callheld", the call on hold) are not supported.
LARA-R2 / TOBY-R2• During a VOLTE call, the network might implement the alerting phase via early media with forking model.
In this scenario no +CIEV: 10,3 URC will be generated and the audio will play the ringback tone provided
by the network.
TOBY-L2 / MPCI-L2• The <mode> parameter cannot be set to 2 and 3.
TOBY-L200-00S / TOBY-L201-01S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S /MPCI-L201-01S / MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• <descr>=12 ("simind", SIM detection) is not supported.
• The "callsetup", "callheld", "sounder" indications are not provided.
TOBY-L201-02S / MPCI-L201-02S• The "callsetup", "callheld", "sounder" indications are not provided.
SARA-G300 / SARA-G310 / LEON-G1• <descr>=12 ("simind", SIM detection) is not supported.

5.7 Clock +CCLK+CCLKModules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

5.7.1 Description
Sets and reads the real-time clock of the MT.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 54 of 1001

u-blox cellular modules - AT commands manual

5.7.2 Syntax
Type
Set

SyntaxAT+CCLK=<time>

Response
OK

ExampleAT+CCLK="14/07/01,15:00:00+01"

Read

AT+CCLK?

+CCLK: <time>OK+CCLK: "14/07/01,15:00:00+01"

Test

AT+CCLK=?

OK
OK

OK

5.7.3 Defined values
Parameter<time>Type
StringDescription
Format is "yy/MM/dd,hh:mm:ss+TZ". Characters indicate year, month, day, hours,
minutes, seconds, time zone.
• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1 - The factory-programmed value is "04/01/01,00:0
0: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 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 rangethat goes from -96 to +96.

SARA-G340 / SARA-G350 / LEON-G1• The PIN insertion is mandatory before the command execution.

5.8 Alarm +CALA+CALA
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

5.8.1 Description
Sets an alarm time in the MT. There can be an array of different types of alarms. If the setting fails, an error
result code is returned. To set up a recurrent alarm for more days in the week, the <recurr> parameter is used.
When an alarm time is reached, the alarm actions are executed:• Sound alarm (if not silent and if the sound is supported)• URC +CALV: <n> is displayed on DTE

5.8.2 Syntax
Type
Set

SyntaxAT+CALA=<time>[,<n>[,<type>[,<text>[,<recurr>[,<silent>]]]]]

Response
OK

Read

AT+CALA?

[+CALA: <time>,<n1>,<type>,<text>,<recurr>,<silent>[+CALA: <time>,<n2>,<type>,<text>,<recurr>,<silent>

UBX-13002752 - R67

5 Mobile equipment control and status

ExampleAT+CALA="02/07/01,14:56:00+04",1,
1,"Alarm"
OK+CALA: "02/07/01,14:56:00+04",1,1,"Alarm","",1
OK

Page 55 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse[...]]]

Test

AT+CALA=?

ExampleOK+CALA: (list of supported <n>s),(list +CALA: (1-3),,255,13,(0-1)
of supported <type>s),<tlength>,OK<rlength>,(list of supported<silent>'s)
OK+CALV: <n>URC

5.8.3 Defined values
Parameter<time>Type
String<n>, <n1>, <n2><type><text><tlength><recurr>

NumberNumberStringNumberString<rlength><silent>

NumberNumberDescription
Format is "yy/MM/dd,hh:mm:ss+TZ". Characters indicate year, month, day, hour,
minutes, seconds, time zone.
Indicates the index of the alarm, the range is 1-3; the default value is 1.
Type of the alarm
Text to be displayed when the alarm time is reached.
Maximum length of <text>; the maximum length is 255.
Maximum string length is 13, it indicates the day of week for the alarm in one of thefollowing formats:• "<1..7>[,<1..7>[...]]": sets a recurrent alarm for one or more days in the week. The
digits 1 to 7 corresponds to the days in the week, Monday (1), ..., Sunday (7). Example:
the string "1,2,3,4,5" may be used to set an alarm for some weekdays.
• "0": sets a recurrent alarm for all days in the week and all following weeks• when the recurrent parameter is set, the time parameter format is "hh:mm:ss+TZ" (hour, minutes, seconds, time zone)
Indicates the maximum length of <recurr>
Indicates if the alarm is silent or not:• 0 (default value): the alarm will not be silent• 1: the alarm will be silent and the only result from the alarm is the +CALV URC

5.8.4 Notes••••

The alarm is not by default configured.
The <type> parameter is ignored.
The <silent> parameter can only be set to 1 when sound is not supported, if the audio interface is available
in the interested product version then the silent mode 0 or 1 can be set.
The module can be switched off after setting the alarm, in which case the module switches on as soon as
the alarm time is reached. The following is an example procedure using the alarm setting:o Set the RTC clock by AT command: AT+CCLK="06/12/29,11:00:00+00" (the time can be checkedwith the AT+CCLK read command)o Set the RTC alarm by AT command: AT+CALA="06/12/29,11:01:00+00",1,0,"","",0 (the alarm set canbe checked by the AT+CALA read command)o Switch off the MT with AT+CPWROFF
Output: the MT switches on as soon as the minute is expired and answers "+CALV: 1". Try to send "AT"on the hyper terminal, the MT replies properly.

TOBY-L2 / MPCI-L2• The <n> parameter can only be set to 1.
• If <recurr> parameter is used, the <time> parameter must not contain a date (the format "hh:mm:ss+TZ"
is used in this case).
• The <silent> default parameter is set to 1.
• Alarm reprogramming is possible only after deletion through +CALD command.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• The <text> parameter is ignored.
LARA-R204 / LARA-R220• The <silent>=0 is not supported.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 56 of 1001

u-blox cellular modules - AT commands manual

SARA-G340 / SARA-G350 / LEON-G1• The <tlength> parameter is ignored.
SARA-G4• The <tlength> parameter is ignored. The <text> parameter maximum length is 32 characters.
• The <silent> parameter is not supported.
• The <type> parameter shall be set to 0 or omitted.

5.9 Delete alarm +CALD+CALD
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

5.9.1 Description
Deletes an alarm in the MT.

5.9.2 Syntax
Type
Set

SyntaxAT+CALD=<n>

Response
OK

ExampleAT+CALD=1

Test

AT+CALD=?

+CALD: (list of <n>s)

OK+CALD: (1-3)

OKOK

5.9.3 Defined values
Parameter<n>Type
NumberDescription
Indicates the index of the alarm; see the +CALA command description for the allowed
range of indexes.

5.9.4 Notes
SARA-G340 / SARA-G350 / LEON-G1• The PIN insertion is mandatory before the command execution.

5.10 Alert sound mode +CALM+CALM
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

5.10.1 Description
Selects the general alert sound mode.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 57 of 1001

u-blox cellular modules - AT commands manual

5.10.2 Syntax
Type
Set

SyntaxAT+CALM=<mode>

Response
OK

ExampleAT+CALM=0

Read

AT+CALM?

+CALM: <mode>OK+CALM: 0

Test

AT+CALM=?

OK
OK+CALM: (list of supported <mode>s) +CALM: (0-1)
OKOK

5.10.3 Defined values
Parameter<mode>

Type
NumberDescription••

0 (factory-programmed value): normal mode
1: silent mode (ring tones and SMS tones are muted; +UTGN AT command is notsupported)

5.10.4 Notes••

If +CALM is set to 1, the +UTGN command returns an error result code (+CME ERROR: operation notsupported).
If an incorrect number of parameters is provided or the parameter value is out of range, then the error
result code "+CME ERROR: operation not supported" will be provided (if +CMEE is set to 2).

TOBY-L2 / SARA-G340 / SARA-G350 / LEON-G1• If +CALM is set to 1, the service tones (e.g.: Call Waiting tone) and alarm tone (see +CALA command)
are also muted; furthermore the +UPLAYFILE and +UPAR commands return an error result code (+CME
ERROR: operation not supported).
SARA-G4• The command setting is not stored in NVM.
• If <mode>=1, the SMS tones are not muted.

5.11 Ringer sound level +CRSL+CRSLModules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

5.11.1 Description
Selects the sound level for the ringer of an incoming call and for the tone generator (see the +UPAR command).
SARA-G4
The command selects also the downlink speech level and the +UPLAYFILE AT command level.
Since the +CLVL and +CRSL AT commands set the same gain (for more details, see SARA-G4 audio
interface), the application processor shall use only one of these commands.

5.11.2 Syntax
Type
Set

SyntaxAT+CRSL=[<level>]

Response
OK

ExampleAT+CRSL=2

Read

AT+CRSL?

+CRSL: <level>OK+CRSL: 2

UBX-13002752 - R67

5 Mobile equipment control and status

Page 58 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+CRSL=?

ResponseOK+CRSL: (list of supported <level>s)

ExampleOK+CRSL: (0-5)

OKOK

5.11.3 Defined values
Parameter<level>Type
NumberDescription
Range 0-5 (0 means mute). The default value and factory-programmed value is 4
4 means -8 dB; each step corresponds to 18 levels and each level corresponds to 0.5
dB; e.g.: 5 means +1 dB

5.11.4 Notes•

If an incorrect number of parameters is provided or the parameter value is out of range, then the error
result code "+CME ERROR: operation not supported" will be provided (if +CMEE is set to 2).

TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.
• The command controls the volume of the following locally generated supervisory tones: call waiting,ringing tone, subscriber busy, ringer. The tones are generated locally when the in-band tones are notavailable (see the +UPROGRESS AT command).
LISA-U1• If +CRSL is set to 0, the AMR player (see the +UPLAYFILE command) is muted.
SARA-G4• The command setting is not stored in NVM.
• The <level> parameter is mandatory and its range goes from 0 to 15. The factory-programmed value is 6.
SARA-G340 / SARA-G350 / LEON-G1• The <level> parameter is mandatory.
• If +CRSL is set to 0, the +UPLAYFILE command returns an error result code (+CME ERROR: operation
not supported).
• The command also selects the volume of the MIDI player (see the +UPAR command), the AMR player(see the +UPLAYFILE command), the service tones (e.g.: Call Waiting tone) and the alarm tone (see the+CALA command).

5.12 Loudspeaker volume level +CLVL+CLVLModules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

5.12.1 Description
Selects the speech volume.
SARA-G4
The command selects also the ringer level.
Since the +CLVL and +CRSL AT commands set the same gain (for more details, see SARA-G4 audio
interface), the application processor shall use only one of these commands.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 59 of 1001

u-blox cellular modules - AT commands manual

5.12.2 Syntax
Type
Set

SyntaxAT+CLVL=[<level>]

Response
OK

ExampleAT+CLVL=30

Read

AT+CLVL?

+CLVL: <level>

OK+CLVL: 80

Test

AT+CLVL=?

OK+CLVL: (list of supported <level>s)

OK+CLVL: (0-100)

OKOK

5.12.3 Defined values
Parameter<level>Type
NumberDescription
0-100 (0 means mute). The default and factory-programmed value is 80
100 means +6 dB; the step size is 0.5 dB; e.g.: 80 means -4 dB

5.12.4 Notes••

If an incorrect number of parameters is provided or the parameter value is out of range, then the error
result code "+CME ERROR: operation not supported" will be provided (if +CMEE is set to 2).
The command affects only the speech volume during the call. Other players volume and tone generator
volume are not affected.

TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.
TOBY-L2• The allowed <level> range is 0-37, where 0 means mute, 37 means 0 dB and the step size is 1 dB (e.g.: 30
means -7 dB). The default and factory-programmed value is 30.
SARA-G340 / SARA-G350 / LEON-G1• The <level> parameter is mandatory. Moreover <level>=100 means 0 dB and the step size is 0.25 dB (e.g.:
80 means -5 dB).
SARA-G4• The command setting is not stored in NVM.
• The <level> parameter is mandatory and its range goes from 0 to 15. The factory-programmed value is 6.

5.13 Mute control +CMUT+CMUT
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

5.13.1 Description
Configures the uplink voice muting during all the voice calls.

5.13.2 Syntax
Type
Set

SyntaxAT+CMUT=<n>

Response
OK

ExampleAT+CMUT=0

Read

AT+CMUT?

+CMUT: <n>

OK+CMUT: 0

UBX-13002752 - R67

5 Mobile equipment control and status

Page 60 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+CMUT=?

Response
OK+CMUT: (list of supported <n>s)

ExampleOK+CMUT: (0-1)

OKOK

5.13.3 Defined values
Parameter<n>Type
NumberDescription••

0 (default value): mute off
1: mute on

5.13.4 Notes•

If an incorrect number of parameters is provided or the parameter value is out of range, then the error
result code "+CME ERROR: operation not supported" will be provided (if +CMEE is set to 2).

5.14 Set greeting text +CSGT+CSGTModules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

5.14.1 Description
Configures and activates/deactivates the greeting text. The greeting text configuration's change will beapplied at the subsequent boot. If active, the greeting text is shown at boot once, on any AT interface, the firsttime the TE sets the DTR line to ON state.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
Take care about restrictions related to the baud rate described in the Autobauding description.

5.14.2 Syntax
Type
Set

SyntaxAT+CSGT=<mode>[,<text>]

Response
OK

ExampleAT+CSGT=1,"Hello user"

Read

AT+CSGT?

+CSGT: <text>,<mode>

OK+CSGT: "Hello",0Test

AT+CSGT=?

OK
OK+CSGT: (list of supported <mode>s), +CSGT: (0-1),49<ltext>OK
OK

5.14.3 Defined values
Parameter<text><mode>Type
StringNumber<ltext>NumberDescription
Greeting text. The factory-programmed value is the empty string.
• 0: turn off the greeting text
• 1: turn on the greeting text
Maximum length of the <text> parameter.

5.14.4 Notes
LARA-R2 / TOBY-R2 / SARA-G4 / SARA-G3 / LEON-G1• The greeting text is shown even if the DTR line is set to OFF state.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 61 of 1001

u-blox cellular modules - AT commands manual

5.15 Automatic time zone update +CTZU+CTZU
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

5.15.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 timezone information).

5.15.2 Syntax
Type
Set

Syntax
AT+CTZU=<on_off>

Response
OK

ExampleAT+CTZU=1

Read

AT+CTZU?

+CTZU: <on_off>

OK+CTZU: 0

Test

AT+CTZU=?

OK+CTZU: (list of supported <on_off>s)OK+CTZU: (0-2)
OKOK

5.15.3 Defined values
Parameter<on_off>Type
NumberDescription
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 theservice, update the GMT time to the module (not only time zone)
Allowed values:• TOBY-L4 / TOBY-L201-02S / TOBY-L210-62S / TOBY-L210-65S / MPCI-L201-02S /LARA-R2 / TOBY-R2 - 0, 1 (factory-programmed value)• TOBY-L200 / TOBY-L201-01S / TOBY-L210-00S / TOBY-L210-02S /TOBY-L210-03A / TOBY-L210-03S / TOBY-L210-60S / TOBY-L220 / TOBY-L280 /MPCI-L200 / MPCI-L201-01S / MPCI-L210 / MPCI-L220 / MPCI-L280 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - 0 (factory-programmed value),1

5.15.4 Notes
TOBY-L201-02S / MPCI-L201-02S• In TOBY-L201-02S-00 and MPCI-L201-02S-00 the factory-programmed value of the <on_off> parameteris 0.

5.16 Time zone reporting +CTZR+CTZR
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

5.16.1 Description
Configures the time zone change event reporting. If the reporting is enabled, according with the <mode>parameter the MT returns:

UBX-13002752 - R67

5 Mobile equipment control and status

Page 62 of 1001

u-blox cellular modules - AT commands manualthe +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.16.2 Syntax
Type
Set

Syntax
AT+CTZR=<mode>

Response
OK

ExampleAT+CTZR=1

Read

AT+CTZR?

+CTZR: <mode>OK+CTZR: 0

Test

AT+CTZR=?

OK
OK+CTZR: (list of supported <mode>s) +CTZR: (0-1)
OK+CTZV: <tz>[,<time>]+CTZE: <tz>,<dst>[,<time>]+CTZEU: <tz>,<dst>[,<utime>]+CTZDST: <dst>

URC
URC
URC
URC

OK
+CTZV: +04,"12/12/31,23:46:33"+CTZE: +04,1,"12/12/31,23:46:33"+CTZEU: +04,1+CTZDST: 1

5.16.3 Defined values
Parameter<mode>

Type
Number<tz><time>

NumberString<dst>

Number<utime>StringDescription
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:• TOBY-L2 / MPCI-L2 - 0 (default value), 1, 2. The +CTZDST URC is not supported.
• TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - 0 (default value), 1• SARA-G4 / SARA-G3 / LEON-G1 - 0 (default value), 1. The +CTZDST URC is notsupported.
Indicates the time zone. The range goes from -48 to +56.
Current local time in format "yy/MM/dd,hh:mm:ss". The characters indicate year,
month, day, hour, minutes, seconds.
Indicates the daylight saving time. The allowed values are:
• 0: no adjustments• 1: +1 hour adjustment• 2: +2 hours adjustment
Universal time in format "yyyy/MM/dd,hh:mm:ss". The characters indicate year,
month, day, hour, minutes, seconds.

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

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The command setting is not stored in the NVM.
SARA-G4 / SARA-G3 / LEON-G1• The command setting is not stored in the NVM.
• The <time> parameter is not supported.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 63 of 1001

u-blox cellular modules - AT commands manual

5.17 List current calls +CLCC+CLCC
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
+CME Error

5.17.1 Description
Returns the list of current calls of MT. If no calls are available, no information text response is sent.

5.17.2 Syntax
Type
ActionSyntaxAT+CLCC

Response
Example[+CLCC: <id1>,<dir>,<stat>,<mode>, +CLCC: 1,0,0,0,0,"0913137880",129<mpty>[,<number>,<type>[,alpha>[,OK<priority>[,<CLI_validity>]]]][+CLCC: <id2>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>[,<priority>[,<CLI_
validity>]]]][...]]]
OK
or

Test

AT+CLCC=?

OK (if no calls)
OK

5.17.3 Defined values
Parameter
<idx>
<dir>

Type
NumberNumber<stat>

Number<mode>

Number<mpty>

Number<number><type><alpha>StringNumberString<priority>

NumberUBX-13002752 - R67

Description
Indicates the call identification (see +CHLD x)
Direction:• 0: mobile originated (MO) call
• 1: mobile terminated (MT) callState of the call:• 0: active• 1: held• 2: dialling (Mobile Originated call)• 3: alerting (Mobile Originated cal)
• 4: incoming (Mobile Terminated call)• 5: waiting (Mobile Terminated call)
Teleservice:• 0: voice• 1: data• 2: FAX• 9: unknown• 0: call is not one of multiparty (conference) call parties• 1: call is one of multiparty call parties
Indicates the phone number in format specified by <type>Type of address octet (phone number)
Optional string alphanumeric representation of <number> corresponding to the entry
found in phonebook; this parameter is not managed
Indicates the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [47].

5 Mobile equipment control and status

Page 64 of 1001

u-blox cellular modules - AT commands manual

Parameter<CLI_validity>

Type
NumberDescription
Provide details why <number> does not contain a calling party BCD number (see the
3GPP TS 24.008 [12] subclause 10.5.4.30). The parameter is not present for MO calltypes:• 0: CLI valid• 1: CLI has been withheld by the originator (see the 3GPP TS 24.008 [12] table 10.5.135a/3GPP TS 24.008 code "Reject by user")• 2: CLI is not available due to interworking problems or limitations of originating
network (see the 3GPP TS 24.008 [12] table 10.5.135a/3GPP TS 24.008 code
"Interaction with other service")• 3: CLI is not available due to calling party being of type payphone (see the 3GPP TS
24.008 [12] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone")• 4: CLI is not available due to other reasons (see the 3GPP TS 24.008 [12] table 10.5.135a/3GPP TS 24.008 code "Unavailable")
When the CLI is not available (<CLI_validity>=2, <CLI_validity>=3 or <CLI_validity>=4), the <number> parameter shall be an empty string ("") and <type> value will not
be significant. Nevertheless, the MT may return the recommended value 128 for<type> (TON/NPI unknown in accordance with 3GPP TS 24.008 [12] subclause 10.5.4.7). When the CLI has been withheld by the originator, (<CLI_validity>=1) and the
CLIP is provisioned with the "override category" option (see the 3GPP TS 22.081 [30]and 3GPP TS 23.081 [31]), <number> and <type> is provided. Otherwise, the MT shallreturn the same setting for <number> and <type> as if the CLI was not available

5.17.4 Notes
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• The <priority> and <CLI_validity> parameters are not supported.

5.18 IMS single radio voice call continuity +CISRVCC+CISRVCC
Modules
Attributes

LARA-R202 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

5.18.1 Description
Informs the MT about the SRVCC (single radio voice call continuity) support. The MT normally updates the
network when changing this parameter. The SRVCC provides the ability to have a seamless handover of a voice
call between the PS domain and the CS domain for calls that are anchored in IMS, when the UE is capable oftransmitting/receiving on only one of those access networks (PS or CS) at a given time, see 3GPP TS 23.221[70] subclause 7.2a, annex A.1 and annex A.2

5.18.2 Syntax
Type
Set

SyntaxAT+CISRVCC=[<uesrvcc>]

Response
OK

ExampleAT+CISRVCC=0

Read

AT+CISRVCC?

+CISRVCC: <uesrvcc>

OK+CISRVCC: 1

Test

AT+CISRVCC=?

OK+CISRVCC: (list of supported<uesrvcc>s)

OK+CISRVCC: (0,1)
OKOK

5.18.3 Defined values
Parameter<uesrvcc>

UBX-13002752 - R67

Type
NumberDescription
SRVCC support status. Allowed values:• 0 (default value): SRVCC not supported• 1: SRVCC supported
The factory-programmed value is:

5 Mobile equipment control and status

Page 65 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• LARA-R202-82B / TOBY-R200-42B / TOBY-R200-82B - 0• LARA-R202-02B / LARA-R211 / TOBY-R200-02B / TOBY-R202 - 1

5.19 Report mobile termination error +CMEE+CMEEModules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

5.19.1 Description
Configures the formatting of the result code +CME ERROR: <err> as an indication of an error relating to thefunctionality of the MT. When enabled, MT related errors cause +CME ERROR: <err> final result code insteadof the regular ERROR final result code. The error result code is returned normally when an error is related tosyntax, invalid parameters or MT functionality.
SARA-G4
The command setting is stored in the personal profile following the procedure described in the Saving AT
commands configuration section.

5.19.2 Syntax
Type
Set

SyntaxAT+CMEE=[<n>]Response
OK

ExampleAT+CMEE=2

Read

AT+CMEE?

+CMEE: <n>

OK+CMEE: 0

Test

AT+CMEE=?

OK+CMEE: (list of supported <n>s)

OK+CMEE: (0-2)

OKOK

5.19.3 Defined values
Parameter<n>Type
NumberDescription•••

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.19.4 Notes•

The following convention is valid:
Numeric error code
3

Verbose error code
"operation not allowed"

4"operation not supported"

Description
The MT is in a state which does not allow performing theentered command.
The error result code is related to a parameter not covered by
the GSM/ETSI or u-blox specification

SARA-G4• The <n> factory-programmed value is 0.

UBX-13002752 - R67

5 Mobile equipment control and status

Page 66 of 1001

u-blox cellular modules - AT commands manual

5.20 Extended error report +CEER+CEER
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

5.20.1 Description
Causes the MT to return one or more lines of the information text response which offer an extended report of
the reason for:• the failure in the last unsuccessful call setup or in-call modification,• the last call release,• the last unsuccessful GPRS attach / EPS bearer establishment or unsuccessful PDP context activation,• the last GPRS / EPS bearer detach or PDP context deactivation.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
The total number of characters in the information text response shall not exceed 2041 characters(including line terminators). The textual report is the failure cause according with 3GPP TS 24.008 [12].
SARA-G4 / SARA-G3
The command also provides an extended report about the reason for the last SM STATUS message sent
to the network. When <type>="SM STATUS msg sent" is reported, it is suggested to reset the PS data
connection.

5.20.2 Syntax
Type
ActionSyntaxAT+CEER

Test

AT+CEER=?

Response+CEER: <type>[,<cause>,<error_
description>]

Example+CEER: "CC setup error",277,"SIMstatus failure"

OK
OK

OK

5.20.3 Defined values
Parameter<type><cause>Type
StringNumber<error_description> String

UBX-13002752 - R67

Description
•
•
•
•
•
•
•
•
•
•
•
•
•
•

"CC setup error": <cause> and <error_description> parameters are provided"CC modification error": <cause> and <error_description> parameters are provided"CC release": <cause> and <error_description> parameters are provided"SM attach error": <cause> and <error_description> parameters are provided"SM detach": <cause> and <error_description> parameters are provided"SM activation error": <cause> and <error_description> parameters are provided"SM deactivation": <cause> and <error_description> parameters are provided"SS network GSM cause": <SS_cause_errors> parameters are provided"SS network reject cause": <tag> and <SS_cause> parameters are provided"EMM cause": <cause> and <error_description> parameters are provided"ESM attach error": <cause> and <error_description> parameters are provided"ESM detach": <cause> and <error_description> parameters are provided"IMS USSD Network cause": <cause> parameter is provided"No report available": no more parameters are provided

SARA-G3
An additional report type is supported: "SM STATUS msg sent". The <cause> and<error_description> parameters indicate respectively the SM cause (see 3GPP
TS 24.008 [12]) and the time, based on +CCLK?, when the message was sent to
the network
Code number of the received error (internal or network originated); more details inAppendix A.3
Code description of the received error; more details in Appendix A.3

5 Mobile equipment control and status

Page 67 of 1001

u-blox cellular modules - AT commands manual

5.20.4 Notes
TOBY-L200-00S / TOBY-L200-02S / TOBY-L201-01S / TOBY-L210-00S / TOBY-L210-02S /TOBY-L210-60S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S / MPCI-L200 /MPCI-L201-01S / MPCI-L210 / MPCI-L220 / MPCI-L280• <type>="EMM cause", "ESM attach error", "ESM detach" and "IMS USSD Network cause" are notsupported.
TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S /MPCI-L201-02S• <type>="ESM attach error", "ESM detach" and "IMS USSD Network cause" are not supported.
• <type>="EMM cause" is not supported by TOBY-L200-03S-00, TOBY-L201-02S-00, TOBY-L210-03S-00,
TOBY-L210-03A-00, TOBY-L280-03S-00, MPCI-L201-02S-00.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• <type>="EMM cause", "ESM attach error", "ESM detach" and "IMS USSD Network cause" are notsupported.
SARA-G3• If no mapping for <cause> is available, the <error_description> response is "Unknown".
SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S• <type>="SM STATUS msg sent" is not supported.
SARA-G4• If no mapping for <cause> is available, the <error_description> response is "Unknown".
• <type>="CC modification error", "SM attach error", "SM detach", "SM activation error", "SM deactivation","SS network GSM cause", "SS network reject cause", "EMM cause", "ESM attach error", "ESM detach","IMS USSD Network cause" are not supported.
LEON-G1• <type> parameter is not supported while <cause> and <error_description> parameters are mandatory in
the response to the action command.
• If no mapping for <cause> is available, the <error_description> response is "Unknown".

5.21 Proprietary extended error report +UCEER+UCEER
Modules
Attributes

LISA-U200-00S LISA-U1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CEER Error

5.21.1 Description
Causes the MT to return one or more lines of information text (<report>, <cause>) determined by the MT
providing an extended report of the reason of:••••

The failure in the last unsuccessful call set-up or in-call modification
The last call release
The last unsuccessful GPRS attach or unsuccessful PDP context activation
The last GPRS detach or PDP context deactivation

5.21.2 Syntax
Type
ActionSyntaxAT+UCEER

Response+UCEER: <report>,<cause>

Example+UCEER: 1,1

AT+UCEER=?

OK
OK

OK

Test

UBX-13002752 - R67

5 Mobile equipment control and status

Page 68 of 1001

u-blox cellular modules - AT commands manual

5.21.3 Defined values
Parameter<report><cause>UBX-13002752 - R67

Type
NumberNumberDescription
Numeric error result code
Indicates the error result code as previously displayed with the response +CME
ERROR on DTE corresponding to the <report>

5 Mobile equipment control and status

Page 69 of 1001

u-blox cellular modules - AT commands manual

6 Call control
6.1 Select type of address +CSTA+CSTA
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.1.1 Description
Selects the type of number for further dialling commands (D) according to 3GPP specifications.
The type of address is automatically detected from the dialling string thus the +CSTA command has noeffect.
TOBY-L2
The type of address is not automatically detected on voice capable devices.

6.1.2 Syntax
Type
Set

SyntaxAT+CSTA=[<type>]

Response
OK

ExampleAT+CSTA=145

Read

AT+CSTA?

+CSTA: <type>OK+CSTA: 145

Test

AT+CSTA=?

OK+CSTA: (list of supported <type>s)

OK+CSTA: (129,145)

OK

OK

6.1.3 Defined values
Parameter<type>

Type
NumberDescription
Type of address in integer format••

145: dialing string includes international access code character '+'129 (default value): national coded dialing string

6.2 Dial command D
D
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L220-02S TOBY-L280 MPCI-L200
MPCI-L201 MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G450-01C SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
Yes
Up to 3 min+CME Error

6.2.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 [5] and initiates the indicated kind of call. No
further commands may follow in the command line in case of data or fax calls.

UBX-13002752 - R67

6 Call control

Page 70 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
If the semicolon ';' is given after the dial string, a voice call is originated, regardless of the value set
via +FCLASS command; otherwise the kind of call depends on the service class previously selected via+FCLASS command.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1"ATD1;" is used to call the Voice Mail number. The number is stored in the SIM card (in EFCPHS or EFMBDN)
but the presence of both files is not mandatory. The command returns an error result code if the number
cannot be retrieved but also if the Voice Mail number has been disabled (see +CSVM for further details).
TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03A /TOBY-L280-03S / LARA-R2 / TOBY-R2
The '+' character in the middle of the <number> parameter is used as separator between the called party
number and the called party subaddress. The subaddress is a sequence of bytes in hexadecimal format
and is structured as the subaddress information element defined in 3GPP TS 24.008 [12]. The Called party
Subaddress IEI (first byte of the called party subaddress information element) is added by the PS. The
maximum size of the subaddress is 22.

6.2.2 Syntax
Type
ActionSyntax
ATD<number>[<I>][<G>][;]

Response
See Result codes

ExampleVoice call
ATD123456;
OK
Data / fax call
ATD123456
CONNECT 9600
Supplementary services
ATD*#43#+CCWA: 0,1+CCWA: 0,2
OK

6.2.3 Defined values
Parameter<number>Type
Number<I>

String<G>

StringDescription
Dial string; the allowed characters are: 1 2 3 4 5 6 7 8 9 0 * # + A B C D , T P ! W @ (seethe 3GPP TS 27.007 [2]). The following characters are ignored: , T ! W @.
• TOBY-L2 / MPCI-L2 - The character D is ignored when present in the dial number (itis valid only for the DTMF string).
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- The character A is interpreted as P due to the BCD extended coding (see the 3GPP
TS 31.102 [18] and 3GPP TS 24.008 [12]).
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- The character D is ignored due to the BCD extended coding (see the 3GPP TS 31.10
2 [18] and 3GPP TS 24.008 [12]).
The first occurrence of P is interpreted as pause and separator between thedialling 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.
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.
Configures the CUG supplementary service for the specific call:• G: CUG activated• g: CUG deactivated
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G3 / LEON-G1

UBX-13002752 - R67

6 Call control

Page 71 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description
The index and the information parameters used during the call will be the same
previously set with +CCUG command.

6.2.4 Notes
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3• The ATD*#06# command provides IMEI (not including the spare digit), the check digit and the SVN.
• To change the PIN, issue the ATD**04*OLD_PIN*NEW_PIN*NEW_PIN# command.
• To unblock the PIN, issue the ATD**05*PIN_UNBLOCKING_KEY*NEW_PIN*NEW_PIN# command.
• To change the PIN2, issue the ATD**042*OLD_PIN2*NEW_PIN2*NEW_PIN2# command.
• To unblock the PIN2, issue the ATD**052*PIN2_UNBLOCKING_KEY*NEW_PIN2*NEW_PIN2# command.
• The maximum number of characters accepted by the dial command is 81.
TOBY-L2 / MPCI-L2• The ATD*#06# command provides IMEI (not including the spare digit), the check digit and the SVN.
• The maximum number of characters accepted by the dial command is 40.
TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S• The maximum number of characters accepted by the dial command is 86.
• The subaddress feature is not supported by TOBY-L200-03S-00, TOBY-L210-03A-00,
TOBY-L210-03S-00, TOBY-L280-03S-00, therefore the number of characters accepted for theseproducts is 40.
SARA-G4• The ATD*#06# command provides IMEI (not including the spare digit), the check digit and the SVN.
• The maximum number of characters accepted by the dial command is 81.
LEON-G1• The syntax ATD is allowed. It is only used for service TS61 (alternate speech and G3 FAX) to trigger an
in-call modification.
• The ATD*#06# command provides IMEI (not including the spare digit), the check digit and the SVN.
• To change the PIN, issue the ATD**04*OLD_PIN*NEW_PIN*NEW_PIN# command.
• To unblock the PIN, issue the ATD**05*PIN_UNBLOCKING_KEY*NEW_PIN*NEW_PIN# command.
• To change the PIN2, issue the ATD**042*OLD_PIN2*NEW_PIN2*NEW_PIN2# command.
• To unblock the PIN2, issue the ATD**052*PIN2_UNBLOCKING_KEY*NEW_PIN2*NEW_PIN2# command.
• The maximum number of characters accepted by the dial command is 63.

6.2.5 Voice call example
The following diagram illustrates the possible transitions in both Mobile Terminated and Mobile Originatedcalls. Information text responses and result codes generated by MT are in italic.

UBX-13002752 - R67

6 Call control

Page 72 of 1001

u-blox cellular modules - AT commands manual

Figure 1: Mobile Terminated and Mobile Originated calls possible transitions

6.3 Direct calling from phonebooks D>
D>
Modules

Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time
Up to 3 min

Error reference+CME Error

6.3.1 Description
Allows voice, data or fax calls, selecting the phone number from the phonebook.
If the semicolon ';' is given after the phone number, a voice call is originated, regardless of the value set
via +FCLASS command; otherwise the kind of call depends on the service class previously selected via
See +FCLASS command.

6.3.2 Syntax
Type
ActionSyntax
ATD><str>[I][G][;]

Response
See Result codes

ExampleATD>"u-blox";

ATD><mem><n>[I][G][;]

See Result codes

OK
ATD>SM1;

ATD><n>[I][G][;]

See Result codes

OK
ATD>1;
OK

6.3.3 Defined values
Parameter<str>

UBX-13002752 - R67

TypeStringDescription
D><str>[I][G][;] originates a call to phone number with corresponding alphanumericfield in the phonebook (set via +CPBS command) is <str>.

6 Call control

Page 73 of 1001

u-blox cellular modules - AT commands manual

Parameter<mem><n>Type
StringDescription
D><mem><n>[I][G][;] originates a call to phone number in memory (one of thephonebooks) <mem> entry location <n>; see the +CPBS command for <mem> value.
<mem> value must be inserted without quotation marks (")<n>String[I][G][;]

StringD><n>[I][G][;] originate a call to phone number in entry location <n> of the phonebook(set via +CPBS command).
See the D

6.4 Select tone dialling T
T
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.4.1 Description
Causes subsequent (or previous) D command to assume that DTMF dialling is to be used. Since DTMF diallingis default in GSM, this command has no effect.

6.4.2 Syntax
Type
ActionSyntaxATT

Response
OK

Example6.5 Select pulse dialling P
P
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.5.1 Description
Causes subsequent (or previous) D command to assume that pulse dialling is to be used. Since DTMF diallingis default in GSM, this command has no effect.

6.5.2 Syntax
Type
ActionSyntaxATP

UBX-13002752 - R67

ResponseOK

6 Call control

ExamplePage 74 of 1001

u-blox cellular modules - AT commands manual

6.6 Call answer A
A
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G450-01C SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 20 s+CME Error

6.6.1 Description
Instructs the DCE to immediately connect to the line and start the answer sequence as specified for theunderlying DCE. Any additional command that appears after A on the same command line is ignored. The
command is abortable.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The user is informed that an incoming call is waiting, by the RING IRC or +CRING: <type> (see the +CRLP
AT command description) displayed on MT.

6.6.2 Syntax
Type
ActionSyntaxATA

Response
RING

ExampleOK

6.7 Hook control H
H
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G450-01C SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 20 s+CME Error

6.7.1 Description
Disconnects the remote user. In case of multiple calls, all the active calls and held calls are released while thewaiting calls are not.
In case of dual service calls, the command will switch the call from data (if different from fax) to voice.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
If the module has a PDP context activated and is in Online Command Mode (OLCM), the command
deactivates the context. During the PSD OLCM an incoming CS call can be accepted with an ATA
command. Subsequent ATH command releases the current CS call while leaving the PDP context
activated. In this state a second ATH command also deactivates the PDP context. For additional
information about OLCM, see the AT command settings.

6.7.2 Syntax
Type
ActionSyntaxATH

UBX-13002752 - R67

ResponseOK

6 Call control

ExamplePage 75 of 1001

u-blox cellular modules - AT commands manual

6.7.3 Notes
LISA-U2 / LISA-U1• A CS data call cannot be established during PSD OLCM (CS voice call only where is supported).
SARA-G4 / SARA-G340 / SARA-G350 / LEON-G1• In case of multiple calls, all the active calls are released while the waiting and held calls are not.

6.8 Monitor speaker loudness L
L
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.8.1 Description
This command has no effect. It is implemented for compatibility with ITU-T V.25ter recommendation [21].

6.8.2 Syntax
Type
ActionSyntaxATL[<value>]Response
OK

ExampleATL0
OK

6.8.3 Defined values
Parameter<value>Type
NumberDescription
0-3

6.9 Monitor speaker mode M
M
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.9.1 Description
This command has no effect. It is implemented for compatibility with ITU-T V.25ter recommendation [21].

6.9.2 Syntax
Type
ActionSyntaxATM<value>

Response
OK

ExampleATM0
OK

6.9.3 Defined values
Parameter<value>UBX-13002752 - R67

Type
NumberDescription
0-2

6 Call control

Page 76 of 1001

u-blox cellular modules - AT commands manual

6.10 Call mode +CMOD+CMOD
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.10.1 Description
Selects the call mode of further dialing commands (D) or for next answering command (A).

6.10.2 Syntax
Type
Set

SyntaxAT+CMOD=<mode>

Response
OK

ExampleAT+CMOD=0

Read

AT+CMOD?

+CMOD: <mode>

OK+CMOD: 0

Test

AT+CMOD=?

OK+CMOD: (list of supported<mode>s)OK+CMOD: (0-1)
OKOK

6.10.3 Defined values
Parameter<mode>

Type
NumberDescription••

0: single mode
1: TS61 (voice alternating with fax) (TS means Tele Service)

6.10.4 Notes•<mode>=1 is only available on modules where the fax is available.

TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / MPCI-L200-00S / MPCI-L201 / MPCI-L210-00S• The set command returns an error result code and the test command result code only returns "OK".

6.11 Hang up call +CHUP+CHUP
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 20 s+CME Error

6.11.1 Description
Causes the MT to hang up the current GSM or UMTS call.
In case of multiple calls, all active calls will be released, while waiting and held calls are not.
The command does not replace the ITU-T V.250 [20] command H, but gives an assured procedure toterminate an alternating mode call. For further information see the 3GPP TS 27.007 [2].

UBX-13002752 - R67

6 Call control

Page 77 of 1001

u-blox cellular modules - AT commands manual

6.11.2 Syntax
Type
ActionSyntaxAT+CHUP

Response
OK

ExampleAT+CHUP

Test

AT+CHUP=?

OK

OK
AT+CHUP=?
OK

6.12 Single numbering scheme +CSNS+CSNS
Modules

Attributes

TOBY-L4
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialNo
ProfileNo

Response time-Error reference+CME Error

6.12.1 Description
Selects the bearer service to be used when a mobile terminated single numbering scheme call is established, i.e.
when a call without bearer capability information element is received. See the 3GPP TS 23.972 [49]. Parametervalues set with +CBST command shall be used when <mode> equals to a data service.
The behavior of this command depends on the network service.
The test command returns values supported as compound values.
Before setting +CSNS to 4 (data), the bearer capability to be sent to the network must be defined with
AT+CBST command (e.g. AT+CBST=0,0,1).

6.12.2 Syntax
Type
Set

SyntaxAT+CSNS=<mode>

Response
OK

ExampleAT+CSNS=0

Read

AT+CSNS?

+CSNS: <mode>

OK+CSNS: 0

Test

AT+CSNS=?

OK
OK+CSNS: (list of supported <mode>s) +CSNS: (0,4)
OKOK

6.12.3 Defined values
Parameter<mode>

Type
NumberDescription•••

0 (factory-programmed value): voice
2: fax (TS 62; TS means Tele Service)
4: data

6.12.4 Notes••<mode>=0 is only supported by modules where the voice is available.
<mode>=2 is only supported by modules where the fax is available.

LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1• The command setting is not stored in the Profile.
SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G1• The command setting is not stored in the Profile.

UBX-13002752 - R67

6 Call control

Page 78 of 1001

u-blox cellular modules - AT commands manual

6.13 Set reporting call status +UCALLSTAT+UCALLSTAT
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L210
MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.13.1 Description
Allows to enable / disable the reporting voice or data call status on the DTE using the URC +UCALLSTAT. This
URC is generated each time a call status change occurs. When multiple calls change status at the same time(e.g. when all multiparty calls are terminated) a URC +UCALLSTAT is generated for each of them.

6.13.2 Syntax
Type
Set

SyntaxAT+UCALLSTAT=<enable>

Response
OK

ExampleAT+UCALLSTAT=1

Read

AT+UCALLSTAT?

+UCALLSTAT: <enable>

OK+UCALLSTAT: 1

Test

AT+UCALLSTAT=?

OK+UCALLSTAT: (list of supported<enable>'s)
OK+UCALLSTAT: <call_id>,<stat>

URC

OK+UCALLSTAT: (0-1)
OK+UCALLSTAT: 1,2

6.13.3 Defined values
Parameter<enable>Type
Number<call_id><stat>

NumberNumberDescription• 0: reporting disabled• 1: reporting enabled
Indicates the call identification (see the 3GPP TS 22.030 [5])Indicates the call status:• 0: active• 1: hold• 2: dialling (Mobile Originated call)• 3: alerting (Mobile Originated call; ringing for the remote party)• 4: ringing (Mobile Terminated call)• 5: waiting (Mobile Terminated call)• 6: disconnected• 7: connected (indicates the completion of a call setup first time for MT and MO calls- this is reported in addition to state active)

6.13.4 Notes••

The URC is displayed on the terminal where the command has been issued.
For the USB terminals, the <enable> flag is reset when the USB cable is disconnected.

LARA-R2 / TOBY-R2• During a VOLTE call, the network might implement the alerting phase via early media with forking model.
In this scenario no +UCALLSTAT: 1,3 URC will be generated and the audio will play the ringback tone
provided by the network.
LARA-R202 / LARA-R211 / TOBY-R2• In case of a IMS call redirected to CS plane the +UCALLSTAT URC will show the intermediate
disconnection.

UBX-13002752 - R67

6 Call control

Page 79 of 1001

u-blox cellular modules - AT commands manual

6.14 Information to in-band-tones availability +UPROGRESS+UPROGRESS
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.14.1 Description
Configures the display of URC +UPROGRESS: <cin>,<status> on the DTE while a speech call is in progress.

6.14.2 Syntax
Type
Set

SyntaxAT+UPROGRESS=<mode>

Response
OK

ExampleAT+UPROGRESS=1

Read

AT+UPROGRESS?

+UPROGRESS: <mode>

OK+UPROGRESS: 1

Test

AT+UPROGRESS=?

URC

OK
OK
+UPROGRESS: (list of the supported +UPROGRESS: (0,1)<mode>s)OK
OK+UPROGRESS: <cin>,<status>+UPROGRESS: 1,7

6.14.3 Defined values
Parameter<mode>

Type
Number<cin><status>

StringNumberDescription
Enabling the +UPROGRESS URC. Allowed values:• 0: disable the +UPROGRESS URC• 1: enable the +UPROGRESS URC
Call number indication
Indicates the call progress status. Allowed values:• 0: no progress• 1: alerting, in-band tones or TCH (traffic channel) not yet available• 2: mobile terminated call now accepted, TCH available• 3: in-band tones available• 4: in-band tones not available• 5: TCH now available, mobile terminated call accepted• 6: TCH now available, in-band tones available• 7: TCH now available, in-band tones not available• 8: TCH changed from data to speech• 9: TCH changed from speech to data
• 10: TCH changed to signalling or data
• 11: the last speech call has been terminated and the speech can be disabled. Mute
uplink, downlink and disable speech• 12: fast connection is available• 13: fast connection is closed• 14: progress information element playing announcement has been received

6.14.4 Notes
TOBY-L2 / MPCI-L2• <status>=5, 6, 7, 8, 9 and 10 (CSD calls with alternate voice-data BS not supported) are not supported.
LARA-R202 / LARA-R203 / LARA-R211 / LARA-R280• Call progress status depends on 2G/3G Call Control signalling messages, therefore not all values apply to
VoLTE calls, e.g. when a dedicated EPS bearer for VoLTE calls is available, <status> 7 is usually issued.

UBX-13002752 - R67

6 Call control

Page 80 of 1001

u-blox cellular modules - AT commands manual•

In case of a IMS call redirected to CS plane the +UPROGRESS URC will show the intermediate
disconnection.

6.15 Tone duration +VTD
+VTD
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.15.1 Description
Refers to an integer <n> that defines the length of DTMF tones emitted as a result of the +VTS command.
For details on the effective tone duration in GSM, UMTS and VoLTE see +VTS AT command.

6.15.2 Syntax
Type
Set

SyntaxAT+VTD=[<n>]Response
OK

ExampleAT+VTD=2

Read

AT+VTD?

+VTD: <n>OK
+VTD: 1Test

AT+VTD=?

OK+VTD: (list of supported <n>s)OK+VTD: (0-255)

OKOK

6.15.3 Defined values
Parameter<n>Type
NumberDescription
Range is from 0 to 255. The default value is 1. A value different than zero causes
a tone of duration <n>/10 seconds (<n> * 0.1 s). If the value 0 is selected, the tone
duration is set to the default value.

6.16 DTMF and tone generation +VTS+VTS
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
Yes
Up to 7 min+CME Error

6.16.1 Description
Allows the transmission of DTMF tones. These tones may be used e.g. when announcing the start of a recording
period. The command can only be used during an active voice call. The command can be aborted if a characteris sent to DCE during the command execution; this behavior is not covered by the 3GPP specification.
In GSM and UMTS the tone duration is network dependent; hence the value set with +VTS command is only
the desired duration and, in particular for short tone durations, it is not guaranteed. Also the actual maximum

UBX-13002752 - R67

6 Call control

Page 81 of 1001

u-blox cellular modules - AT commands manual

DTMF tone duration is network dependent, i.e. the receiver can experience a shorter tone duration than the
one specified with +VTS (or with +VTD). For more information see the 3GPP TS 23.014 [63]
In VoLTE DTMF tone generation is based on RTP events according to RFC 4733 [119].

6.16.2 Syntax
Type
Set

SyntaxAT+VTS=<DTMF>[,<duration>]

Response
OK

ExampleAT+VTS=2
OK
AT+VTS=2A,10

Test

AT+VTS=?

+VTS: (list of <DTMF>s),(list of
supported <duration>s)

OK+VTS: (0-9,#,*,A-D),(0-255)
OKOK

6.16.3 Defined values
Parameter<DTMF><duration>

Type
Character
NumberDescription
String (without quotation marks) of ASCII characters from the set 0-9, #, *, A-D.
Range 0-255, expressed in <duration>/100 seconds (0.01 s). If left out or set to 0, thetone duration is given by the +VTD setting

6.16.4 Notes•

If the command is invoked when not in a call, an error result code is reported ("+CME ERROR: noconnection to phone" if +CMEE=2 is set to 2).

TOBY-L210-62S / TOBY-L210-65S• In case of single DTMF tone the <duration> parameter must be set to 11 or above as per SBM requirement.
• In case of multiple DTMF tones the <duration> parameter must be in range [11,38]; the gap time between
each tone is set to 215 ms as per SBM requirement.
• It is not possible to concatenate more +VTS AT commands (an error result code is provided in that case).
LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2• In VoLTE the minimum supported value for the <duration> parameter is 7.

6.17 Start and stop tone generation +UVTS+UVTS
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U120 LISA-U130
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.17.1 Description
Starts and stops the DTMF tones. It can be used during speech calls and is not operative during CSD calls. For
more information see the 3GPP TS 23.014 [63].
When the <DTMF> parameter is omitted the tone is stopped.

6.17.2 Syntax
Type
Set

SyntaxAT+UVTS=[<DTMF>]

Response
OK

Test

AT+UVTS=?

OK+UVTS: (list of supported <DTMF>s) +UVTS: (0-9,#,*,A-D)

UBX-13002752 - R67

6 Call control

ExampleAT+UVTS=2

Page 82 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

ExampleOK

6.17.3 Defined values
Parameter<DTMF>TypeChar

Description
Single ASCII character in the set 0-9, #, *, A-D

6.17.4 Notes•

If the command is invoked when not in a call, an error result code is reported ("+CME ERROR: noconnection to phone" if +CMEE is set to 2).

TOBY-L2 / MPCI-L2• A tone started with AT+UVTS shall always be explicitly stopped with AT+UVTS=, otherwise subsequent
DTMF tone generations triggered via +UVTS or +VTS commands are not allowed.

6.18 Redial last telephone number DL
DL
Modules

Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time
Up to 3 min

Error reference+CME Error

6.18.1 Description
Redials the last number used in the ATD command. The command redials the last called number as a data call,while the ATDL; command redials the last called number as a voice call, regardless of whether the number waspreviously dialled as data or voice call. The last called number is stored locally in volatile memory.

6.18.2 Syntax
Type
ActionSyntaxATDL[;]

Response
See Result codes

ExampleATDL
OK

6.18.3 Notes
SARA-G340 / SARA-G350 / LEON-G1• Both "ATDL" and "ATDL;" commands redial the last called number as voice call, regardless if the number
was previously dialled as data or voice call. The last called number is stored in the SIM card's last-diallingphonebook.

6.19 Automatic answer S0
S0Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

6.19.1 Description
Controls the automatic answering feature of the DCE. If set to 0, the automatic answering is disabled,
otherwise it causes the DCE to answer when the incoming call indication (RING) has occurred the number oftimes indicated by the value.
For an incoming CSD call, if the autoanswering is enabled and the <value> parameter of &D command is
set to 2, the autoanswering only works if the DTR line of the AT interface with activated autoanswering

UBX-13002752 - R67

6 Call control

Page 83 of 1001

u-blox cellular modules - AT commands manualis set to ON. Otherwise, if DTR is OFF, then the call is rejected. If the <value> parameter of &D commandis not set to 2, the DTR state has no impact on autoanswering.
TOBY-L210-62S / TOBY-L210-65S
The voice call autoanswering is not supported and the command is therefore not effective.

6.19.2 Syntax
Type
Set

SyntaxATS0=<value>

Response
OK

ExampleATS0=2

Read

ATS0?

<value>

OK
000

OK

OK

6.19.3 Defined values
Parameter<value>Type
NumberDescription
Value in the range 0-255; the answer to the read command is in "xxx" format.
• 0 (factory-programmed value): disables automatic answer mode
• 1-255: enables automatic answering after specified number of rings

6.19.4 Notes
TOBY-L4906-50A• The command setting is stored in the NVM.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the CSD call autoanswering is not supported.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• On the AUX UART interface, the CSD call autoanswering is not supported.
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory, the default value is 0.
SARA-G450-01C / SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S /SARA-G350-02X• On the AUX UART interface, the CSD call autoanswering is not supported.

6.20 Set voice mail number +CSVM+CSVM
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R204 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
< 20 s+CME Error

6.20.1 Description
Sets the phone number of the voice mail server.
If the parameter <mode> is set to 0, the remaining parameters are ignored.
The voice number is stored in EFCPHS or EFMBDN. Their presence on the SIM card is not mandatory. Ifneither are present, then the set and read command returns an error result code.
To call the voice mail number (if possible), use the ATD1; command.

UBX-13002752 - R67

6 Call control

Page 84 of 1001

u-blox cellular modules - AT commands manual

6.20.2 Syntax
Type
Set

SyntaxAT+CSVM=<mode>[,<number>[,<type>]]

Read

AT+CSVM?

Test

AT+CSVM=?

Response
OK

ExampleAT+CSVM=1,"+1234567890",145

OK+CSVM: <mode>,<number>,<type> +CSVM: 0,"+1234567890",145
OK+CSVM: (list of supported<mode>s),(list of supported<type>s)OK+CSVM: (0-1),(128-255)
OKOK

6.20.3 Defined values
Parameter<mode>

Type
Number<number><type>

StringNumberDescription• 0: voice mail number disabled• 1: voice mail number enabled
Phone number; see the D command description
Type of address, octet in number format••

145: <number> string includes '+'129: otherwise

6.20.4 Notes•

The <number> and <type> parameters can be left out if the parameter <mode> is set to 0.

6.21 Emergency call reporting configuration +UEMC+UEMC
Modules

Attributes

TOBY-L4
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.21.1 Description
Enables / disables the +UUEMC URC that reports the presence of an emergency call.

6.21.2 Syntax
Type
Set

SyntaxAT+UEMC=<mode>

Response
OK

ExampleAT+UEMC=0

Read

AT+UEMC?

+UEMC: <mode>

OK+UEMC: 0

Test

AT+UEMC=?

OK
OK+UEMC: (list of supported <mode>s) +UEMC: (0,1)
OK+UUEMC: <state>

URC

OK+UUEMC: 1

6.21.3 Defined values
Parameter<mode>

Type
NumberDescription••

0: +UUEMC URC reporting disabled
1: +UUEMC URC reporting enabled<state>Number••0: emergency call ended
1: emergency call ongoing

UBX-13002752 - R67

6 Call control

Page 85 of 1001

u-blox cellular modules - AT commands manual

6.22 Emergency number verification +UEMN+UEMN
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

6.22.1 Description
Verifies if the given <number> is recognized as an Emergency Call Code (ECC).

6.22.2 Syntax
Type
Set

Test

SyntaxAT+UEMN=<number>

AT+UEMN=?

Response+UEMN: <number>,<result>

ExampleAT+UEMN="911"OK+UEMN: "911",1

OK

OK
OK

6.22.3 Defined values
Parameter<number><result>

UBX-13002752 - R67

TypeStringNumberDescription
Number to be verified••

0: <number> is not recognized as an ECC
1: <number> is recognized as an ECC

6 Call control

Page 86 of 1001

u-blox cellular modules - AT commands manual

7 Network service
7.1 Network parameters definition
Parameter
<MCC>

Type
Number<MNC>

Number

<LAC>

Number<CI>

Number<RxLev>

Number<RAC>

Number<t_adv>

Number<ch_type>

Number<ch_mode>

NumberUBX-13002752 - R67

Description
Commands
Mobile Country Code. The range is 0-999 (3 digits). +COPS, +CGED, +UCGED,• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / +UCELLINFO
LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - Other
values are to be considered invalid / not available• TOBY-L2 / MPCI-L2 - The FFF value is to beconsidered not known or not detectable
Mobile Network Code. The range is 0-999 (1 to 3
+COPS, +CGED, +UCGED,
digits).
+UCELLINFO• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - Other
values are to be considered invalid / not available• TOBY-L2 / MPCI-L2 - the FFF value is to beconsidered not known or not detectable
Location Area Code, The range is 0x0-0xFFFF (2+COPS, +CGED,
octets)+UCELLINFOCell identity.
+COPS, +CGED,• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / +UCELLINFO
LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - The
range is:o 2G cell: range 0x0-0xFFFF (2 octets)o 3G cell: range 0x0-0xFFFFFFF (28 bits)
o 4G cell: range (decimal format) 04294967295 (default value).
Received Signal Strength Indicator (RSSI) index as +COPS, +CGED, +UCGED,
defined in 3GPP TS 45.008 [25]:+UCELLINFO• 0: less than -110 dBm• 1..62: from -110 to less than -48 dBm with 1 dBm
steps• 63: -48 dBm or greater• TOBY-L2 / MPCI-L2 - The value 255 is return if not
known or not detectable
Routing Area Code, range 0h-FFh (1 octet); see the +COPS, +CGED
3GPP TS 44.018 [136]Timing Advance, it is valid during a connection and +CGED, +UCELLINFO
it will updated during the next connection; see the
3GPP TS 04.18 [36]Channel type of the current connection (see the+CGED, +UCELLINFO
3GPP TS 04.18 [36]):• 0: invalid channel type
• 1: TCH/F• 2: TCH/H• 3: SDCCH/4• 4: SDCCH/8• other values are to be considered invalid / notavailable
Channel mode of current connection (see the 3GPP +CGED, +UCELLINFO
TS 04.18 [36]):• 0: signalling only
• 1: speech full rate
• 2: speech half rate
• 3: data full rate, 12.0 kb/s radio interface rate
• 4: data full rate, 6.0 kb/s radio interface rate
• 5: data half rate, 6.0 kb/s radio interface rate
• 6: data full rate, 3.6 kb/s radio interface rate

7 Network service

Page 87 of 1001

u-blox cellular modules - AT commands manual

ParameterType<scrambling_code>

Number<dl_frequency>

Number<ul_frequency><arfcn>NumberNumber<rscp_lev>

Number<ecn0_lev>

Number<rrc_state>

String<EARFCN>

Number<PhysCellID>

Number<TAC>

NumberUBX-13002752 - R67

Description
Commands• 7: data half rate, 3.6 kb/s radio interface rate
• 8: speech full rate version 2• 9: speech full rate version 3• 10: speech half rate version 2• 11: speech half rate version 3• other values are to be considered invalid / notavailable
Scrambling code.
+COPS, +CGED, +UCGED,• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / +UCELLINFO
LISA-U1 - The range is 0-511• TOBY-L2 / MPCI-L2 - The range is 0-512, 0 if not
known or not detectable
Downlink frequency. The range is 0-16383.
+COPS, +CGED,+UCELLINFO
Uplink frequency. The range is 0-16383.
+COPS, +CGED
Absolute Radio Frequency Channel Number+COPS, +CGED, +UCGED(ARFCN).
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - The
range is 0-1023. The string INVALID_ARFCN will
be provided if the information is not available.
The parameter value also decodes the band
indicator bit (DCS or PCS) by means of themost significant byte (8 means 1900 band) (i.e.
if the parameter reports the value 33485, it
corresponds to 0x82CD, in the most significant
byte there is the band indicator bit, so the<arfcn> is 0x2CD (717) and belongs to 1900 band).
• TOBY-L2 / MPCI-L2 - The range is 0-1023, 65535
if not known or not detectable.
Received Signal Code Power expressed in dBm+COPS, +CGED,
levels:+UCELLINFO• 0: less than -115 dBm• 1..90: from -115 dBm to less than -25 dBm with 1
dBm steps• 91: -25 dBm
Energy per Chip/Noise ratio expressed in dB levels: +COPS, +CGED, +UCGED,+UCELLINFO• 0: less than -24 dB• 1..48: from -24 dB to less than 0 dB with 0.5 dB
steps• 49: 0 dB
• TOBY-L2 / MPCI-L2 The value 255 is return if not
known or not detectable
Allowed values:+CGED, +UCELLINFO• "CD": CELL_DCH (0)• "CF": CELL_FACH(1)• "CP": CELL_PCH(2)• "UP": URA_PCH(3)• "ID": IDLE(4)• "ST": START(5)E-UTRAN Absolute radio frequency channel+CGED, +UCGED,
number.
+UCELLINFO, +VZWRSRQ• LARA-R2 / TOBY-R2 - The range is 0-0xFFFF• TOBY-L2 / MPCI-L2 - The range is 0-6449 (0x1931), 65535 if not known or not detectable
Physical cell ID. The range is 0-503.
+COPS, +CGED,+UCELLINFO
Tracking area code.
+COPS, +CGED, +UCGED,+UCELLINFO• LARA-R2 / TOBY-R2 - The range is 0-0xFFFF

7 Network service

Page 88 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<LcellId>

Number<dl_EARFCN>

Number<ul_EARFCN>

Number<RSRP>

Number<RSRQ>

Number<TA>

Number<BSIC>

Number

<Lband>NumberDescription
Commands• TOBY-L2 / MPCI-L2 - The range is 0-0xFFFF (2octets), FFFF if not known or not detectable
E-UTRAN CI (cell identifier) in hexadecimal format; +UCGED
the range is 0h-FFFFFFFh (28 bits), 0000000 if not
known or not detectable.
Downlink E-UTRAN absolute radio frequency+COPS
channel number in decimal format.
Uplink E-UTRAN absolute radio frequency channel +COPS
number in decimal format.
Reference Signal Received Power (RSRP) as defined +COPS, +CGED, +UCGED,in 3GPP TS 36.133 [83]:+UCELLINFO• 0: less than -140 dBm• 1..96: from -140 dBm to less than -44 dBm with 1
dBm steps• 97: -44 dBm or greater• TOBY-L2 / MPCI-L2 - The value 255 is return if not
known or not detectable• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 - +COPS, +CGED, +UCGED,
Reference Signal Received Quality (RSRQ) as +UCELLINFO
defined in 3GPP TS 36.133 [83]: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 greatero TOBY-L2 / MPCI-L2 - The value 255 is return
if not known or not detectable
Timing advance information:+CGED, +UCELLINFO• In RRC_IDLE state, the value of timing advance(TA) is updated from the Random-AccessResponse message; the range is 0-1282.
• In RRC_CONNECTED state, the value of timing
advance (TA) is updated from the MAC control
element; the range is 0-63.
Base Station Identify Code (BSIC) in hexadecimal+COPS, +CGED, +UCGED
format, the range is 0x0-0x3F (6 bits).
• TOBY-L2 / MPCI-L2 - The FF value is returned if
the BSIC is not known or not detectable.
E-UTRAN band (see 3GPP TS 36.101 Table 5.5-1+UCGED[78]). Allowed values:• TOBY-L2 / MPCI-L2 - From 0 to 44, 255 if not
known or not detectable

7.2 Subscriber number +CNUM+CNUM
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time< 10 sError reference+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.

UBX-13002752 - R67

7 Network service

Page 89 of 1001

u-blox cellular modules - AT commands manual

7.2.2 Syntax
Type
ActionSyntax
AT+CNUM

Response+CNUM: [<alpha1>],<number1>,<type1>

Example+CNUM: "Mario Rossi","+39320
821708",145[+CNUM: [<alpha2>],<number2>,<type2>+CNUM: "ABCD . AAA","1234567890
12",129[...]]

OK

OK
or
Test

OK
OK

AT+CNUM=?

7.2.3 Defined values
Parameter<alphax><numberx><typex>Type
StringStringNumberDescription
Associated with <numberx>
Phone number of format specified by <typex>
Type of address, octet in Number format (145 when <numberx> string includes '+',
otherwise 129)7.2.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• The character set of the <alphax> parameter is selected by means of +CSCS AT command.

7.3 Signal quality +CSQ
+CSQ
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.3.1 Description
Returns the radio signal strength <signal_power> and <qual> from the MT.
TOBY-L4 / LARA-R2 / TOBY-R2
The +CSQ utilization is deprecated. It is warmly recommended to use the command +CESQ to obtain thesame information more accurately.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
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 commanddescription).
In dedicated mode, during the radio channel reconfiguration (e.g. handover), invalid measurements may bereturned for a short transitory because the MT must compute them on the newly assigned channel.

7.3.2 Syntax
Type
ActionSyntaxAT+CSQ

Test

AT+CSQ=?

UBX-13002752 - R67

Response+CSQ: <signal_power>,<qual>

Example+CSQ: 2,5

OK
OK
+CSQ: (list of supported <signal_+CSQ: (0-31,99),(0-7,99)
power>s),(list of supported <qual>s)OK
OK

7 Network service

Page 90 of 1001

u-blox cellular modules - AT commands manual

7.3.3 Defined values
Parameter<signal_power>

Type
Number<qual>

NumberDescription
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 moredetails 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 isreturned.
TOBY-L4 / LARA-R2 / TOBY-R2
In LTE RAT, the <signal_power> represents the Reference Signal Received Power(RSRP).
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 [124]• In 2G RAT EGPRS packet transfer mode indicates the Mean Bit Error Probability(BEP) of a radio block. 3GPP TS 45.008 [124] 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 thecurrent cell. 3GPP TS 25.133 [84] 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 [83]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>
0
1
2
3
4
5
6
7
99

2G RAT CS and GPRSBER < 0.2%
0.2% < BER < 0.4%
0.4% < BER < 0.8%
0.8% < BER < 1.6%
1.6% < BER < 3.2%
3.2% < BER < 6.4%
6.4% < BER < 12.8%
BER > 12.8%

2G RAT EGPRS
UMTS RAT
28 <= MEAN_BEP <= 31
ECN0_LEV >= 44
24 <= MEAN_BEP <= 27
38 <= ECNO_LEV < 44
20 <= MEAN_BEP <= 23
32 <= ECNO_LEV < 38
16 <= MEAN_BEP <= 19
26 <= ECNO_LEV < 32
12 <= MEAN_BEP <= 15
20 <= ECNO_LEV < 26
8 <= MEAN_BEP <= 11
14 <= ECNO_LEV < 20
4 <= MEAN_BEP <= 7
8 <= ECNO_LEV < 14
0 <= MEAN_BEP <= 3
ECNO_LEV < 8
Not known or not detectable

LTE RAT
RSRQ_LEV < 5
5 <= RSRQ_LEV < 10
10 <= RSRQ_LEV < 14
14 <= RSRQ_LEV < 18
18 <= RSRQ_LEV < 22
22 <= RSRQ_LEV < 26
26 <= RSRQ_LEV < 30
RSRQ _LEV >= 30

Table 3: <qual> parameter mapping for each supported RAT
TOBY-L2 / MPCI-L2• When the module enters the Out Of Service condition, the latest valid <signal_power> level is reported.
• The command can be used with no need of SIM insertion, because the module always try to camp on
a suitable cell at boot, unless it is started in minimum functionality or it is deregistered from network(+COPS: 2).
• In UMTS RAT, the <signal_power> returned by the command is the RSCP, that is proportional to RSSI
according to the following relationship:
RSSI (dBm) = RSCP (dBm) - EC_NO (dB)
Table 4 maps several <signal_power> values and RSSI when the corresponding P-CPICH is equal to -2 dB.
Other values can be interpolated based on this.
<signal_power>
31
30
27
24
22
19
17

UBX-13002752 - R67

RSSI of the network-46 dBm <= RSSI of the network <= -25 dBm-50.5 dBm
-55.5 dBm
-60.5 dBm
-65.5 dBm
-70.5 dBm
-75.5 dBm

7 Network service

Page 91 of 1001

u-blox cellular modules - AT commands manual<signal_power>
14
12
10
7
4
2
0

•

RSSI of the network-80.5 dBm
-85.5 dBm
-90.5 dBm
-95.5 dBm
-100.5 dBm-105.5 dBm
RSSI of the network <= -110.5 dBm

Table 4: Mapping between <signal_power> reported from UE and the RSSI when the P-CPICH= -2 dB
Table 5 maps several <signal_power> values reported from UE and the RSSI transmitted by the networkin LTE RAT. Other values can be interpolated based on this.
<signal_power>
31
30
28
24
22
19
16
14
12
10
8
Packet data connection lost

RSSI of the network-48.5 dBm <= RSSI of the network-53.5 dBm
-58.5 dBm
-63.5 dBm
-68.5 dBm
-73.5 dBm
-78.5 dBm
-83.5 dBm
-88.5 dBm
-93.5 dBm
-98.5 dBm
RSSI of the network <= -99.5 dBm

Table 5: Mapping between <signal_power> reported from UE and the RSSI transmitted by the network
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270 / LISA-U1• The <qual> parameter is not updated in GPRS and EGPRS packet transfer mode.
SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S• The <qual> parameter is not updated in GPRS packet transfer mode.
LEON-G100-07S / LEON-G100-08S• The <signal_power> and the <qual> parameters are updated in GPRS packet transfer mode.
• If CS4 is used in GPRS packet transfer mode, the module is allowed to report <qual>=7.
LEON-G100-06S• The <qual> parameter is not updated in GPRS packet transfer mode.

7.4 Extended signal quality +CESQ+CESQModules
Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+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.

UBX-13002752 - R67

7 Network service

Page 92 of 1001

u-blox cellular modules - AT commands manual

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 asingle 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
ActionSyntaxAT+CESQ

Test

AT+CESQ=?

Response
Example+CESQ: <rxlev>,<ber>,<rscp>,<ecn0 +CESQ: 99,99,255,255,20,80>,<rsrq>,<rsrp>
OK
OK+CESQ: (list of supported <rxlev>s), +CESQ: (0-63,99),(0-7,99),(0-96,(list of supported <ber>s),(list255),(0-49,255),(0-34,255),(0-97,
of supported <rscp>s),(list255)
of supported <ecn0>s),(listOKof supported <rsrq>s),(list of
supported <rsrp>s)OK

7.4.3 Defined values
Parameter<rxlev>Type
Number<ber>

Number<rscp>

Number<ecn0>

Number<rsrq>

Number<rsrp>

NumberDescription
Received Signal Strength Indication (RSSI).
• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 - 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 greatero 99: not known or not detectable
Bit Error Rate (BER):• 0..7: as RXQUAL values in the table in 3GPP TS 45.008 [124], subclause 8.2.4• 99: not known or not detectable
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
Ratio of received energy per PN chip to the total received power spectral density (see3GPP TS 25.133 [84] 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
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
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.4.4 Notes
TOBY-L2 / MPCI-L2• When the module enters the Out Of Service condition, the lowest level of the <rxlev>, <ber>, <rscp>,<ecn0> parameters is reported.

UBX-13002752 - R67

7 Network service

Page 93 of 1001

u-blox cellular modules - AT commands manual•

The command can be used with no need of the SIM insertion, because the module always try to camp on
a suitable cell at the module boot, unless it is started in minimum functionality or it is deregistered fromnetwork (+COPS: 2).

LARA-R2 / TOBY-R2• When the module is not registered (i.e. it enters the Out Of Service condition), all the parameters values
are reset to 'not known or not detectable'.

7.5 Operator selection +COPS+COPS
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
ProfileYes

Response time
Up to 3 min

Error reference+CME Error

7.5.1 Description
Forces an attempt to select and register with the GSM/UMTS/LTE network operator, that can be chosen in thelist 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 (where supported).
By default, u-blox cellular modules support the auto-registration. Fore more details, see Auto-registration.
TOBY-L2 / MPCI-L2
In manual PLMN selection mode, if the optional <AcT> parameter is not specified, the modules will selectGSM if available and fall back to LTE or UMTS in priority order.
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
In manual PLMN selection mode, if the optional <AcT> parameter is not specified, the modules will selectthe default access technology with the following priority order: LTE, UMTS and GSM (not supported
technologies will be ignored).
SARA-G4
The command cannot be aborted.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings 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 command isaccessible also without an inserted SIM. In this case the command AT+COPS=0 always returns an error result
code because the network registration cannot be performed without the SIM, while the configuration (i.e.
automatic registration) is correctly set. 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 (for more details on the <mode>parameter allowed values, see Defined values):• <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 inmanual 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.
• <mode>=5 and <mode>=6: an extended network search, also called deep scan, is triggered; all cells
detected during the PLMN scan are reported at the AT interface, more precisely:o for GSM networks: all cells found of any visible PLMNs will be reported, including those belonging to
the neighbour list of the serving cell. The command response includes the following data (if supported):
AcT, MCC, MNC, LAC, CI, BSIC, Arfcn, RxLev (see the Network parameters definition section for theparameter description)o for UMTS networks: all cells found on any visible PLMNs will be reported, including those belonging to
the neighbour list of the serving cell. For each cell, the scan will trigger the additional reception of the SIB

UBX-13002752 - R67

7 Network service

Page 94 of 1001

u-blox cellular modules - AT commands manual•

type 1 and type 3, to properly report the LAC, RAC, and CI of the cell. The command response includes
the following data: MCC, MNC, LAC, RAC, CI, DLF, ULF, SC, RSCP LEV, ECN0 LEV (see the Network
parameters definition section for the parameter description)o for LTE networks: all cells found will be reported, including those belonging to the neighbour list of
the serving cell. For each cell, the command response includes the following data: MCC, MNC, TAC,
CI, DLF, ULF, PCI, RSRP and RSRQ (see the Network parameters definition section for the parameter
description).
<mode>=8: when a module is registered on the GSM network, a network timing advance search is performed
o The network timing advance search is performed only on the serving cell and the 6 neighbour cells of BA
list with the higher power levels.
o The information text response always includes the following data for the serving cell and for the other 6neighbour cells: MCC, MNC, LAC, CI, BSIC, Arfcn, RxLev (see the Network parameters definition section
for the parameter description) and TA. When the <CI> value is not valid, no data of the correspondentneighbour cell is inside the information text response.
o It can be started only when the module is in idle mode and no cell reselection is ongoing. The network
condition could sometimes increase the estimated response time.
o No mobile terminated/originated SMS, PS or CS call are handled when the network timing advancesearch is running. Furthermore mobility management procedures (for example: routing area updateprocedure or location update procedure) are delayed after the end of timing advance search.

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 [56]), i.e. the module triggers a search for the HPLMN or a higher order
PLMN excluding the previously selected PLMN/access technology combination. 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 either selects another PLMN that has the best signal quality or remains in the state it was in prior
to the search (e.g. camped and/or registered on the PLMN before the search). Both behaviors are accepted by
3GPP TS 23.122 [56]•TOBY-L4 - If no HPLMN or higher order PLMN is found, PLMN with the best signal quality is selected (alreadyselected PLMN might change)• LARA-R2 / TOBY-R2 - If no HPLMN or higher order PLMN is found, the module remains in the state it wasin prior to the search (i.e. previously selected PLMN will be chosen and no signalling takes place)
The AT+COPS=1,<format>,<oper> command forces the MT to select and register with the network even if theoperator currently belongs to the list of the Forbidden Public Land Mobile Networks (FPLMNs).
The PLMN search cannot be performed in RRC connected state when the RAT is 3G or LTE, hence no PLMN
list will be returned at the end of the PLMN scan attempt.
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 check the current network registration status:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - Network registration status +CREG• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - GPRS network registration status +CGREG• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 - EPS network registration status +CEREGThe 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 waita few seconds before entering AT+COPS=2 in order to let the pending registration procedure (automaticallytriggered by the module in most cases) successfully end.
The test command returns long and short <oper> strings from the module's ROM PLMN name list (see+COPN). To handle possible mismatches between the PLMN names returned by the test command and theread command, the numeric format should be preferred.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
The manual PLMN selection can fail due to the MNO control on the network selection procedure via EFCSP
setting; for further details see +PACSP.

UBX-13002752 - R67

7 Network service

Page 95 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / TOBY-L2 / MPCI-L2 / SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S /LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G3 / LEON-G1
If more than one PLMN have the same alphanumeric name in the ROM PLMN name list (see +COPN), a
manual PLMN selection can fail because the device tries to register only on the first PLMN in the ROM list
whose alphanumeric code matches the one specified in the +COPS command.
LARA-R2 / TOBY-R2 / SARA-U201 / SARA-U260-03S / SARA-U270-03A / SARA-U270-03S /SARA-U270-53S / SARA-U270-73S / SARA-U280-03S / LISA-U200-03S / LISA-U200-04B /LISA-U200-83S / LISA-U201
The response time of a manual PLMN selection specifying the target network in alphanumeric format canexceed the documented value, because the device tries to register on all PLMNs in the ROM list whosealphanumeric code matches the one specified in the +COPS command.

7.5.2 Syntax
Type
Set

SyntaxAT+COPS=[<mode>[,<format>[,<oper>[,<AcT>]]]]

Response
If <mode>=0, 1, 2, 3, 4:

ExampleAT+COPS=0,0

OK
If <mode>=5 and on GSM networks:

OK
AT+COPS=5[MCC:<MCC>, MNC:<MNC>, LAC:<LAC>, MCC:222, MNC: 88, LAC:55fa, CI:ffff,
CI:<CI>, BSIC:<BSIC>, Arfcn:<arfcn>,
BSIC:3f, Arfcn:00104, RxLev:037
RxLev:<RxLev>
MCC:222, MNC: 10, LAC:4e54, CI:ffff,[MCC:<MCC>, MNC:<MNC>, LAC:<LAC>, BSIC:32, Arfcn:00080, RxLev:032
CI:<CI>, BSIC:<BSIC>, Arfcn:<arfcn>,...
RxLev:<RxLev>...
[...]]]
MCC:222, MNC: 88, LAC:55fa, CI:1d39,
OK
BSIC:3d, Arfcn:00756, RxLev:005
If <mode>=5 and on UMTS networks:

OK
AT+COPS=5[MCC:<MCC>, MNC:<MNC>, LAC:<LAC>, MCC:222, MNC:10, LAC:61ef, RAC:14, CI:0
RAC:<RAC>, CI:<CI>, DLF:<dl_frequency>, 7d2088, DLF:10788, ULF: 9838, SC:81,
ULF:<ul_frequency>, SC:<scrambling_
RSCP LEV:23, ECN0 LEV:41
code>, RSCP LEV:<rscp_lev>, ECN0
MCC:222, MNC:10, LAC:61ef, RAC:14, CI:0
LEV:<ecn0_lev>
7d2085, DLF:10813, ULF: 9863, SC:81,[MCC:<MCC>, MNC:<MNC>, LAC:<LAC>, RSCP LEV:26, ECN0 LEV:41
RAC:<RAC>, CI:<CI>, DLF:<dl_frequency>,...
ULF:<ul_frequency>, SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0...
LEV:<ecn0_lev>
MCC:222, MNC:01, LAC:ef8d, RAC:0[...]]], CI:52d36fb, DLF:10688, ULF: 9738,
SC:285, RSCP LEV:16, ECN0 LEV:32
OK
OK
If <mode>=5 and on LTE networks:
AT+COPS=5[MCC:<MCC>, MNC:<MNC>, TAC:<TAC>, MCC:222, MNC:88, TAC:562c, CI:573670
CI:<CI>, DLF:<dl_EARFCN>, ULF:<ul_
43, DLF: 1325, ULF:19325, PCI:163, RSRP
EARFCN>, PCI:<PhysCellID>, RSRP
LEV:25, RSRQ LEV:1
LEV:<RSRP>, RSRQ LEV:<RSRQ>
MCC:222, MNC:10, TAC:5a25, CI:100[MCC:<MCC>, MNC:<MNC>, TAC:<TAC>, 86944, DLF: 1850, ULF:19850, PCI:287,
CI:<CI>, DLF:<dl_EARFCN>, ULF:<ul_
RSRP LEV:25, RSRQ LEV:6
EARFCN>, PCI:<PhysCellID>, RSRP...
LEV:<RSRP>, RSRQ LEV:<RSRQ>...
[...]]]
MCC:293, MNC:40, TAC:27ec, CI:519425,
OK
DLF: 6400, ULF:24400, PCI:393, RSRP
LEV:27, RSRQ LEV:9
If <mode>=6 and on GSM networks:

UBX-13002752 - R67

7 Network service

OK
AT+COPS=6

Page 96 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse[<AcT>,<MCC>,<MNC>,<LAC>,<CI>,<BSIC>,<arfcn>,<RxLev>[<AcT>,<MCC>,<MNC>,<LAC>,<CI>,<BSIC>,<arfcn>,<RxLev> [...]]]

Example0,222,88,55fa,ffff,3f,00104,037...
0,222,10,4e54,ffff,32,00080,032...

OK
If <mode>=6 and on UMTS networks:

OK
AT+COPS=6[<MCC>,<MNC>,<LAC>,<RAC>,<CI>,<dl_ 222,99,754f,2,03554d7,10713,9763,341,
frequency>,<ul_frequency>,<scrambling_ 255,14
code>,<RSCP LEV>,<ecn0_lev>...
[<MCC>,<MNC>,<LAC>,<RAC>,<CI>,<dl_
222,01,ef8d,0,52d2647,10663,9713,453,4,
frequency>,<ul_frequency>,<scrambling_
23code>,<RSCP LEV>,<ecn0_lev>...
[...]]]OKOK
If <mode>=6 and on LTE networks:
AT+COPS=6[<AcT>,<MCC>,<MNC>,<TAC>,<CI>,<dl_ 7,222,88,562c,57367043,1325,19325,163,
EARFCN>,<ul_EARFCN>,<PhysCellID>,
35,10<RSRP>,<RSRQ>
7,222,01,3aa3,179291197,6300,24300,271,[<AcT>,<MCC>,<MNC>,<TAC>,<CI>,<dl_ 48,14
EARFCN>,<ul_EARFCN>,<PhysCellID>,
7,222,01,3aa3,179290685,6300,24300,40<RSRP>,<RSRQ>
2,27,11[...]]]
7,293,40,27ec,519425,6400,24400,393,24,
OK
1
If <mode>=8 and on GSM networks:

OK
AT+COPS=8[MCC:<MCC>, MNC:<MNC>, LAC:<LAC>, MCC:222, MNC: 10, LAC:4e54, CI:12f1,
CI:<CI>, BSIC:<BSIC>, Arfcn:<arfcn>,
BSIC:3f, Arfcn:00104, RxLev:037, TA:3
RxLev:<RxLev>, TA:<TA>
MCC:222, MNC: 10, LAC:4e54, CI:8841,[MCC:<MCC>, MNC:<MNC>, LAC:<LAC>, BSIC:32, Arfcn:00080, RxLev:032, TA:5
CI:<CI>, BSIC:<BSIC>, Arfcn:<arfcn>,
MCC:222, MNC: 10, LAC:4e54, CI:1ef4,
RxLev:<RxLev>, TA:<TA>
BSIC:31, Arfcn:00082, RxLev:022, TA:255[...]]]...
OK
MCC:222, MNC: 10, LAC:55fa, CI:1d39,
BSIC:3d, Arfcn:00756, RxLev:005, TA:7
Read

Test

AT+COPS?

AT+COPS=?

+COPS: <mode>[,<format>,<oper>[,<AcT>]]OK+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: 0,0,"vodafone IT"
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)
OKOK

7.5.3 Defined values
Parameter<mode>

UBX-13002752 - R67

Type
NumberDescription
Is used to chose whether the network selection is automatically done by the MT or isforced 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

7 Network service

Page 97 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 3: set only <format>• 4: manual/automatic• 5: extended network search• 6: extended network search without the tags (e.g. MCC, RxLev will not be printed,
see the syntax and the command example)• 8: network timing advance search
Allowed values:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 - 0, 1, 2, 3, 4
• SARA-U201 / SARA-U260-03S / SARA-U270-03A / SARA-U270-03S /SARA-U270-53S / SARA-U270-73S / SARA-U280-03S / LISA-U200-03S /LISA-U200-04B / LISA-U200-83S / LISA-U201 / LISA-U1 / SARA-G450-00C /LEON-G100-07S / LEON-G100-08S - 0, 1, 2, 3, 4, 5, 6
• SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S /LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S /LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270 / SARA-G300 / SARA-G310 /SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G100-06S - 0, 1, 2, 3, 4, 5
• SARA-G450-01C / SARA-G340-02S / SARA-G340-02X / SARA-G350-02A /SARA-G350-02S / SARA-G350-02X - 0, 1, 2, 3, 4, 5, 6, 8

<format>Number<oper>

String• 0 (factory-programmed value): long alphanumeric <oper>• 1: short format alphanumeric <oper>• 2: numeric <oper>
Given in format <format> this field may be up to 24 characters long for longalphanumeric 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 FFFFF (undefined).

<stat>

Number

<AcT>

Number<TA>

Number

<MCC>
<MNC>
<LAC>
<CI>

NumberNumberNumberNumberUBX-13002752 - R67• 0: unknown• 1: available• 2: current• 3: forbidden
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• 6: UTRAN with HSDPA and HSUPA availability• 7: LTE• 8: EC-GSM-IoT (A/Gb mode)• 9: E-UTRAN (NB-S1 mode)
Allowed values:• TOBY-L4 - 0, 1, 2, 3, 4, 5, 6, 7
• TOBY-L200 / TOBY-L201 / TOBY-L210 / TOBY-L220-02S / TOBY-L280 /MPCI-L200 / MPCI-L201 / MPCI-L210 / MPCI-L220-02S / MPCI-L280 - 0, 1, 2, 3, 4,
5, 6, 7
• TOBY-L220-62S / MPCI-L220-62S / LARA-R203 / LARA-R204 / LARA-R220 - 7• TOBY-R200 - 0, 1, 2, 3, 4, 5, 6, 7
• LARA-R202 / LARA-R280 / TOBY-R202 - 2, 4, 5, 6, 7
• LARA-R211 - 0, 1, 3, 7
• SARA-U201 / SARA-U260 / SARA-U270-00S / SARA-U270-00X / SARA-U270-03A /SARA-U270-03S / LISA-U2 / LISA-U1 - 0, 2
• SARA-U270-53S / SARA-U270-73S / SARA-U280 - 2
Timing Advance; the range is 0-63. If the information is not known or not detectableor currently not available, the value is 255.
See <MCC>.
See <MNC>.
See <LAC>.
See <CI>.

7 Network service

Page 98 of 1001

u-blox cellular modules - AT commands manual

Parameter<BSIC><arfcn><RxLev><RAC><dl_frequency><ul_frequency><scrambling_code><rscp_lev><ecn0_lev><TAC><dl_EARFCN><ul_EARFCN><PhysCellID><RSRP><RSRQ>

Type
NumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberDescription
See <BSIC>.
See <arfcn>.
See <RxLev>.
See <RAC>.
See <dl_frequency>.
See <ul_frequency>.
See <scrambling_code>.
See <rscp_lev>.
See <ecn0_lev>.
See <TAC>.
See <dl_EARFCN>.
See <ul_EARFCN>.
See <PhysCellID>.
See <RSRP>.
See <RSRQ>.

7.5.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• <format> and <oper> parameters are optional only if the value of <mode> parameter is 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)
TOBY-L4• If a manual PLMN selection fails to find the specified PLMN, the modules autonomously searches for
the HPLMN and, if it is visible, it registers on it; in this case the AT+COPS=1 command ends successfully
as if the user had manually selected the HPLMN.
• When <format> is set to alphanumeric (0 or 1) the read command's <oper> value is retrieved from thefirst match found in the following "name sources" (from highest to lowest priority):o EFOPL and EFPNN files (SIM card dependent, see below)
o NITZ service (network dependant)o CPHS operator name string (SIM card dependent)o Hardcoded list in the module's firmware
If no match is found in the "name sources" the broadcasted MCC-MNC is displayed. If the PLMN
network name and operator name list services are "enabled" in the SIM card, then the EFOPL and EFPNN
are used for displaying the <oper> name if a match can be found.
• Issue the AT+CFUN=4,1 command to start with auto-COPS disabled (AT+COPS=2).
TOBY-L4906-50A• The command setting is not stored in NVM.
TOBY-L2 / MPCI-L2• When <format> is set to alphanumeric (0 or 1) the read command's <oper> value is retrieved from thefirst match found in the following "name sources" (from highest to lowest priority):o EFOPL and EFPNN files (SIM card dependent, see below)
o NITZ service (network dependent)
o CPHS operator name string (SIM card dependent)o Hardcoded list in the module's firmware
If no match is found in the "name sources" the broadcasted MCC-MNC is displayed. If the PLMN
network name and operator name list services are "enabled" in the SIM card, then the EFOPL and EFPNN
are used for displaying the <oper> name if a match can be found.
• The user reselection cannot be managed through the issuing of two set commands with <mode>=0.
• In case of 3G cells, regardless of the actual HSPA support, the <AcT> value in the information text
response of the test command is 2.
• If the current network selection mode is manual, by issuing the set command with <mode>=0 themodule triggers a search for the HPLMN.

UBX-13002752 - R67

7 Network service

Page 99 of 1001

u-blox cellular modules - AT commands manual•••

In case of 2G cells, regardless of the actual EGPRS support, the <AcT> value in the information text
response of the test command is 0.
If the module is set to "CG" class with +CGCLASS command, the manual selection of a forbidden
PLMN shall be triggered with +UCGOPS command; the AT+COPS=1 command cannot be issued forthis purpose.
If a network with MCC|MNC not in the network operator name list is available on air interface, thenumeric value will be used also as short and long alphanumeric operator name.

LARA-R2 / TOBY-R2• If a manual PLMN selection fails to find the specified PLMN, the modules autonomously searches for
the HPLMN and, if it is visible, it registers on it; in this case the AT+COPS=1 command ends successfully
as if the user had manually selected the HPLMN.
• When <format> is set to alphanumeric (0 or 1) the read command's <oper> value is retrieved from thefirst match found in the following "name sources" (from highest to lowest priority):o EFOPL and EFPNN files (SIM card dependent, see below)
o NITZ service (network dependant)o CPHS operator name string (SIM card dependent)o Hardcoded list in the module's firmware
If no match is found in the "name sources" the broadcasted MCC-MNC is displayed. If the PLMN
network name and operator name list services are "enabled" in the SIM card, then the EFOPL and EFPNN
are used for displaying the <oper> name if a match can be found.
• In 2G/3G RAT, +COPS set command with <mode>=0 ,1 or 4 will return OK after CS registration has beenaccomplished; if another +COPS set command with <mode>=0,1 or 4 is issued while the PS registrationis pending, an error can be returned. In this case the user shall check +CGREG and retry the +COPS
command as soon as the PS registration status is updated.
SARA-U2 / LISA-U2 / LISA-U1• When <format> is set to alphanumeric (0 or 1) the read command's <oper> value is retrieved from thefirst match found in the following "name sources" (from highest to lowest priority):o EFOPL and EFPNN files (SIM card dependent, see below)
o NITZ service (network dependant)o CPHS operator name string (SIM card dependent)o Hardcoded list in the module's firmware
If no match is found in the "name sources" the broadcasted MCC-MNC is displayed. If the PLMN
network name and operator name list services are "enabled" in the SIM card, then the EFOPL and EFPNN
are used for displaying the <oper> name if a match can be found.
• The <AcT> parameter is not available in the information text response of the set command with<mode>=6 (extended network search without the tags).
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270• If a manual PLMN selection fails to find the specified PLMN, the modules autonomously searches for
the HPLMN and, if it is visible, it registers on it; in this case the AT+COPS=1 command ends successfully
as if the user had manually selected the HPLMN.
• In GSM networks, the extended network search will not report the neighbour cells (BA - BCCH Allocationlist) of the 2G serving cell. Such cells are reported by AT+CGED command if <mode> is set e.g. to 5.
SARA-G4• The AT command settings are not automatically stored in the current activated profile.
• The <AcT> parameter is only available in the information text response of the set command with<mode>=6 (extended network search without the tags).
• Supporting <mode>=5 the following restrictions apply:o If the SIM card is inserted and the PIN verification is enabled but has not been verified, <mode>=
5 cannot be used.
o If the SIM card is not inserted, <mode>=5 cannot be immediately used after a switch on. Before
issuing the command, the RF circuits must be enabled, e.g. by starting an emergency call orentering AT+COPS=0.

UBX-13002752 - R67

7 Network service

Page 100 of 1001

u-blox cellular modules - AT commands manual••

If the cellular module is de-registered from the network (<mode>=2) it is not possible to start a network
scan (with AT+COPS=? or AT+COPS=5 or AT+COPS=6) until AT+COPS is invoked with <mode>=0 or 1.
If the RPLMN (Registered PLMN) is not present in the ROM PLMN name list, the read command
displays <oper> in the format <MCC>:<MNC>.

SARA-G3 / LEON-G1• The AT command settings are not automatically stored in the current activated profile.
• When the command is aborted during the execution the final result code is "OK".
• When the <mode> parameter is set to manual or manual/automatic (1 or 4), set the <format>
parameter to numeric (2).
• The <AcT> parameter is only available in the information text response of the set command with<mode>=6 (extended network search without the tags).
• Supporting <mode>=5 the following restrictions apply:o If the SIM card is inserted and the PIN verification is enabled but has not been verified, <mode>=
5 cannot be used.
o If the SIM card is not inserted, <mode>=5 cannot be immediately used after a switch on. Before
issuing the command, the RF circuits must be enabled, e.g. by starting an emergency call orentering AT+COPS=0.
• If the cellular module boots with <mode>=2 it is not possible to start a network scan (with AT+COPS=? or AT+COPS=5 or AT+COPS=6) until AT+COPS is invoked with <mode>=0 or 1.
• If the RPLMN (Registered PLMN) is not present in the ROM PLMN name list, the read command
displays <oper> in the format <MCC>:<MNC>.
SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S• The extended network search will not report the neighbour cells (BA - BCCH Allocation list) of theserving cell. Such cells are reported by AT+CGED command if <mode> is set e.g. to 5.
LEON-G1• The extended network search will not report the neighbour cells (BA - BCCH Allocation list) of theserving cell. Such cells are reported by AT+CGED command if <mode> is set e.g. to 5.

7.6 MCC update table +UNVMMCC+UNVMMCC
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

7.6.1 Description
Allows the access to the MCC update list. This list is a writeable extension to the MCC Nettype List.
The set command overwrites the entry if it has already been entered. The MCC update list is stored in NVM.
The list is first stored in the volatile NVM mirror, and the NVM copy is then updated in the background. It is
recommended to power cycle the module after the list is updated.

7.6.2 Syntax
Type
Set

Read

SyntaxResponse
AT+UNVMMCC=<mode>[,<idx>[,
OK<mcc>,<gsmbands>,<umtsbands>,<lte_bands_fdd>,<lte_bands_tdd>]]
AT+UNVMMCC?
+UNVMMCC: <idx>,<mcc>,<gsmbands>,<umtsbands>,<lte_bands_fdd>,<lte_bands_tdd>[...]

ExampleAT+UNVMMCC=1,10,5,4,2,2,8
OK+UNVMMCC: 1,10,5,4,2,2,8[...]+UNVMMCC: 20,0,0,0
OK

UBX-13002752 - R67

7 Network service

Page 101 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse+UNVMMCC: <idx>,<mcc>,<gsmbands>,<umtsbands>,<lte_bands_fdd>,<lte_bands_tdd>

Test

AT+UNVMMCC=?

ExampleOK+UNVMMCC: (list of supported+UNVMMCC: (0-1),(1-20),(0-999),<mode>s),(list of supported <idx>s), (1-128),(1-8192),(0-4294967293),(0(list of supported <mcc>s),(list of
4294967293)
supported <gsmbands>s),...,(list ofOKsupported <umtsbands>s),(list of
supported <lte_bands_fdd>s),(list of
supported <lte_bands_tdd>s)OK

7.6.3 Defined values
Parameter<mode>

Type
Number<idx><mcc><gsmbands>

NumberNumberNumber<umtsbands>

Number<lte_bands_tdd>

NumberUBX-13002752 - R67

Description
Defines the command.
• 0: clear one or all entries in a list:o Select an entry to clear with <idx>o If <idx> is omitted, all the entries will be cleared• 1: write one entry
Index of the entries in the MCC update list. The allowed range is 1-20.
Mobile Country Code. The allowed range is 0-999.
GSM/2G band selection. The parameter is a bit mask, 16-bits in length given as aninteger. Only the values listed below are allowed.
• 1: PGSM 900• 2: EGSM 900• 4: RGSM 900• 8: DCS 1800
• 16: PCS 1900
• 32: GSM 450• 64: GSM 480• 128: GSM 850
UMTS/3G band selection. The parameter is a bit mask, 16-bits in length given as aninteger. Only the values listed below are allowed.
• 1: band 1• 2: band 2• 4: band 3• 8: band 4• 16: band 5• 32: band 6• 64: band 7• 128: band 8• 256: band 9• 512: band 10• 1024: band 11• 2048: band 12• 4096: band 13• 8192: band 14
LTE TDD bands. It is a 32-bit bitmap, each bit representing one LTE TDD band (LTEbands 33 to 64), (see 3GPP TS 36.101 section 5.5 [78]). The bitmap value can beformed as below:• 1: E-UTRA band 33• 2: E-UTRA band 34• 4: E-UTRA band 35• 8: E-UTRA band 36• ......
• 2147483648: E-UTRA band 64

7 Network service

Page 102 of 1001

u-blox cellular modules - AT commands manual

ParameterType<lte_bands_fdd>

NumberDescription
For multiple band selection, the corresponding bits should be OR'ed and accordingly
the bitmap value should be given.
LTE FDD bands. It is a 32-bit bitmap, each bit representing one LTE FDD band (LTEbands 1 to 32), (see 3GPP TS 36.101 section 5.5 [78]). The bitmap value can be formed
as below:• 1: E-UTRA band 1• 2: E-UTRA band 2• 4: E-UTRA band 3• 8: E-UTRA band 4• ......
• 2147483648: E-UTRA band 32
For multiple band selection, the corresponding bits should be OR'ed and accordingly
the bitmap value should be given.

7.6.4 Notes•

The 2G / 3G / 4G tables are by default empty.

SARA-U2 / LISA-U2• The <lte_bands_fdd> and <lte_bands_tdd> parameters are not supported.
LARA-R2 / TOBY-R2• The <lte_bands_tdd> parameter setting is ignored.

7.7 PLMN information list +UNVMPLMN+UNVMPLMN
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

7.7.1 Description
Provides the access to the protocol stack's PLMN tables used to improve the PLMN selection procedure. A
table is available for each RAT (GSM RAT, UMTS RAT and LTE RAT).
The PLMN information is stored in NVM and may be updated by the protocol stack. Thus the +COPS=2 AT
command shall be issued before updating the list.
After the list is updated, the module shall be power cycled.

7.7.2 Syntax
Type
SyntaxPLMN tables management generic syntax
GSM / UMTS
Set

Response

ExampleOK

GSM / UMTS

AT+UNVMPLMN=<op_code>,<rat>[,<idx>[,<mcc>,<mnc>,<bands>[,<f1>[,<f2>...[,<fn>]]]]]LTE
AT+UNVMPLMN=<op_code>,<rat>[,<idx>[,<mcc>,<mnc>,<lte_bands_fdd>,<f1>,[<f2>],...,[<fn>],<lte_bands_tdd>,<channel_bw>]]
PLMN tables cleaning
Set
AT+UNVMPLMN=0,<rat>[,<idx>]

AT+UNVMPLMN=1,1,1,222,1,1,10663,
10688,10638
OK
LTE

OK

AT+UNVMPLMN=1,2,1,222,1,1,10663,
10688,10638,,,,,,,,0,0OK
OK

AT+UNVMPLMN=0,1,1
OK

UBX-13002752 - R67

7 Network service

Page 103 of 1001

u-blox cellular modules - AT commands manualType
SyntaxPLMN tables editing
GSM / UMTS
Set

Response

ExampleOK

GSM / UMTS

AT+UNVMPLMN=1,<rat>,<idx>,<mcc>,<mnc>,<bands>,<f1>[,<f2>...
[,<fn>]]LTE

AT+UNVMPLMN=1,1,1,222,1,1,10663,
10688,10638
OK
LTE

OK

AT+UNVMPLMN=1,<rat>,<idx>,<mcc>,<mnc>,<lte_bands_fdd>,<f1>,[<f2>],...,[<fn>],<lte_bands_
tdd>,<channel_bw>
PLMN tables reading
Set
AT+UNVMPLMN=2,<rat>[,<idx>]

AT+UNVMPLMN=1,2,1,222,10,1,10
788,10838,10813,,,,,,,,1,63
OK
GSM / UMTS

GSM / UMTS

+UNVMPLMN: <rat>,<idx>,<mcc>, AT+UNVMPLMN=2,1<mnc>,<bands>,<f1>[,<f2>...[,<fn>]]+UNVMPLMN: 1,1,222,1,1,10663,10[...]
688,10638[+UNVMPLMN: <rat>,<idx>,<mcc>, +UNVMPLMN: 1,2,222,88,1,10563,10<mnc>,<bands>,<f1>[,<f2>...[,
588,10613<fn>]]]...
OK+UNVMPLMN: 1,50,0,0,0
LTE+UNVMPLMN: <rat>,<idx>,<mcc>,<mnc>,<lte_bands_fdd>,<f1>[,<f2>...[,<fn>]],<lte_bands_tdd>,<channel_bw>
[...]

OK
LTE
AT+UNVMPLMN=2,2,1+UNVMPLMN: 2,1,222,10,1,10788,10
838,10813,1,63
OK[+UNVMPLMN: <rat>,<idx>,<mcc>,<mnc>,<lte_bands_fdd>,<f1>[,<f2>...[,<fn>]],<lte_bands_tdd>,<channel_bw>]
OK
Test

AT+UNVMPLMN=?

GSM / UMTS
+UNVMPLMN: (list of supported<mode>s),(list of supported+UNVMPLMN: (0-2),(0,1),(1-50),(0<rat>s),(list of supported <idx>s),999),(0-999),(1-8192),(0-10838),...,(0(list of supported <mcc>s),-10838)(list of supported <mnc>s),(listof supported <bands>s),(listOKof supported <f1>s) ...,(list ofLTEsupported <fn>s),(list of supported<lte_bands_tdd>s),(list of supported +UNVMPLMN: (0-2),(0-2),(1-50),(0-999),(0-999),(0-4294967293),<channel_bw>s)(0-65535),...,(0-65535),(0OK4294967293),(0-63)
OK

7.7.3 Defined values
Parameter<op_code>Type
Number<rat>

NumberUBX-13002752 - R67

Description
Defines the command to be executed. Allowed values:• 0: clear one or all the entries in a list; if the <idx> parameter is omitted, all the entries
will be cleared• 1: write one entry; at least one frequency must be provided (<f1>)• 2: read one or all entries in a list; if the <idx> parameter is omitted, all the entries
will be read
Selects the PLMN information list:• 0: GSM list
• 1: UMTS list

7 Network service

Page 104 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

<idx>

Number<mcc><mnc><bands>NumberNumberNumber<lte_bands_fdd>

Number<f1>...<fn>

NumberDescription• 2: LTE list
Index of the entries in the PLMN information lists. The allowed range is 1-50.
If the parameter is omitted, all the entries will be cleared or read depending on the<op_code> parameter value.
Mobile Country Code. The allowed range is 0-999.
Mobile Network Code. The allowed range is 0-999.
Band:• GSM:
o 1: PGSM 900
o 2: EGSM 900
o 4: RGSM 900
o 8: DCS 1800
o 16: PCS 1900
o 32: GSM 450
o 64: GSM 480
o 128: GSM 850• UMTS:o 1: band 1
o 2: band 2
o 4: band 3o 8: band 4
o 16: band 5
o 32: band 6
o 64: band 7
o 128: band 8
o 256: band 9o 512: band 10
o 1024: band 11
o 2048: band 12
o 4096: band 13
o 8192: band 14
o 262144: band 19
o 524288: band 20
o 1048576: band 21
LTE FDD bands. It is a 32-bit bitmap, each bit representing one LTE FDD band (LTEbands 1 to 32), (see 3GPP TS 36.101 section 5.5 [78]). The bitmap value can be formed
as below:• 1: E-UTRA band 1• 2: E-UTRA band 2• 4: E-UTRA band 3• 8: E-UTRA band 4• ......
• 2147483648: E-UTRA band 32
For multiple band selection, the corresponding bits should be OR'ed and accordingly
the bitmap value should be given.
Frequency. In GSM represents the ARFCN, in UMTS the UARFCN, in LTE the
EARFCN.
n's range is 1-32 in GSM, 1-10 in UMTS and LTE.

<lte_bands_tdd>

UBX-13002752 - R67

NumberLTE TDD bands. It is a 32-bit bitmap, each bit representing one LTE TDD band (LTEbands 33 to 64), (see 3GPP TS 36.101 section 5.5 [78]). The bitmap value can beformed as below:• 1: E-UTRA operating band 33• 2: E-UTRA band 34• 4: E-UTRA band 35• 8: E-UTRA band 36• ......
• 2147483648: E-UTRA band 64

7 Network service

Page 105 of 1001

u-blox cellular modules - AT commands manual

ParameterType<channel_bw>

NumberDescription
For multiple band selection, the corresponding bits should be OR'ed and accordingly
the bitmap value should be given.
LTE channel bandwidth. It is a 8-bit bitmap representing up to six possible LTE
channel bandwidth (see 3GPP TS 36.101 section 5.6 [78]). The bitmap value can beformed as below:• 1: LTE channel bandwidth 1.4 MHz• 2: LTE channel bandwidth 3 MHz• 4: LTE channel bandwidth 5 MHz• 8: LTE channel bandwidth 10 MHz• 16: channel bandwidth 15 MHz• 32: LTE channel bandwidth 20 MHz
Bits 6,7 are unused, shall be set to 0.
For multiple band selection, the corresponding bits should be OR'ed and accordingly
the bitmap value should be given.

7.7.4 Notes••

As factory-programmed settings the PLMN tables are empty, but it may be updated by the protocol
stack.
North American PLMNs whose 3rd MNC digit is 0, may be displayed with a 2 digit MNC (1st and 2nd
MNC digit). For example <mcc>=310, <mnc>=150 may be displayed as [...]310,15 (see 3GPP TS 23.122 [56]Annex A)SARA-U2 / LISA-U2• <lte_bands_fdd>, <lte_bands_tdd>, <channel_bw> are not supported.
• The maximum value for <bands> is 8192.

7.8 Radio Access Technology (RAT) selection +URAT+URAT
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
partialNo

Settings saved Can be aborted
NVM / OP
No

Response time
<10 s

Error reference+CME Error

7.8.1 Description
Forces the selection of the Radio Access Technology (RAT) in the protocol stack. On the subsequent network
registration (+COPS, +CGATT) the selected RAT is used.
By means of <PreferredAct> and <2ndPreferredAct> parameters it is possible to define the order of RAT
selection at boot or when entering full functionality from de-registered state. If <SelectedAcT> is set to dualor tri mode, it is possible to specify the preferred RAT parameter <PreferredAct>, which determines which
RAT is selected first. If the preferred RAT parameter is omitted, it will be set by default to the highest RAT
in the current multi-mode range. If tri mode is selected, it is also possible to specify a second preferred RAT<2ndPreferredAct> in addition to the preferred RAT. This parameter determines which RAT is selected if nocellular service can be obtained by the module on the preferred RAT. The remaining RAT will be selected whenno service can be obtained in the preferred one(s).
Any change in the RAT selection must be done deregistered state, entered by issuing the AT+CFUN=0 or
AT+CFUN=4 AT command. Use AT+CFUN=1 to return to the module full functionality.
SARA-U2 / LISA-U2 / LISA-U1
See Notes for the procedure to enter the detach state.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the command

UBX-13002752 - R67

7 Network service

Page 106 of 1001

u-blox cellular modules - AT commands manual

settings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
In dual mode and tri mode, all the requested Access Stratum protocols are active and Inter-RAT
measurements as well as Inter-RAT handovers may be performed (if ordered by the network).
TOBY-L200 / TOBY-L201 / MPCI-L200 / MPCI-L201 / LARA-R202-02B / LARA-R203 / TOBY-R200-02B /TOBY-R202
AT&T RAT balancing feature, by means of updating RAT related SIM files, can force RAT usage (seeNotes).

7.8.2 Syntax
Type
Set

Read

Test

Syntax
AT+URAT=<SelectedAcT>[,<PreferredAct>[,<2ndPreferredAct>]]
AT+URAT?

AT+URAT=?

Response
OK

ExampleAT+URAT=1,0
OK+URAT: <SelectedAcT>[,<PreferredAct>[,<2ndPreferredAct>]]+URAT: 1,2
OK

OK+URAT: (list of the supported+URAT: (0-6),(0,2,3),(0,2,3)<SelectedAcT>s),(list of theOKsupported <PreferredAct>s),(list of
the supported <2ndPreferredAct>s)OK

7.8.3 Defined values
Parameter<SelectedAcT>

Type
Number<PreferredAct>

NumberUBX-13002752 - R67

Description
Indicates the radio access technology and may be:• 0: GSM / GPRS / eGPRS (single mode)• 1: GSM / UMTS (dual mode)• 2: UMTS (single mode)• 3: LTE (single mode)• 4: GSM / UMTS / LTE (tri mode)• 5: GSM / LTE (dual mode)• 6: UMTS / LTE (dual mode)
Allowed values depend on the module series:• TOBY-L4 / TOBY-L2 / MPCI-L2 / TOBY-R200 - 0, 1, 2, 3, 4 (factory-programmed
value), 5, 6
• TOBY-L220-62S / MPCI-L220-62S - 3 (factory-programmed value)• TOBY-L201 / TOBY-L220-02S / MPCI-L201 / MPCI-L220-02S / LARA-R202 /LARA-R280 / TOBY-R202 - 2, 3, 6 (factory-programmed value)• LARA-R203 / LARA-R204 / LARA-R220 - 3 (factory-programmed value)• LARA-R211 - 0, 3, 5 (factory-programmed value)• SARA-U2 / LISA-U2 / LISA-U1 - 0, 1 (factory-programmed value), 2• SARA-U270-53S / SARA-U270-73S / SARA-U280 - 2 (factory-programmed value)
Indicates the preferred access technology; it is ignored if dual mode or tri mode are
not selected.
• 0: GSM / GPRS / eGPRS• 2: UTRAN• 3: LTE
Allowed values depend on the module series:• TOBY-L4 / TOBY-L2 / MPCI-L2 / TOBY-R200 - 0, 2, 3 (default and factoryprogrammed value)• TOBY-L201 / TOBY-L220 / MPCI-L201 / MPCI-L220 / LARA-R202 / LARA-R280 /TOBY-R202 - 2, 3 (default and factory-programmed value)• LARA-R203 / LARA-R204 / LARA-R220 - The parameter is not supported• LARA-R211 - 0, 3 (default and factory-programmed value)

7 Network service

Page 107 of 1001

u-blox cellular modules - AT commands manual

ParameterType<2ndPreferredAct>

NumberDescription• SARA-U2 / LISA-U2 / LISA-U1 - 0, 2 (default and factory-programmed value)• SARA-U270-53S / SARA-U270-73S / SARA-U280 - 2 (default and factoryprogrammed value)
Indicates the second preferred access technology; it is ignored if tri mode is notselected.
• 0: GSM / GPRS / eGPRS• 2: UTRAN• 3: LTE
Allowed values depend on the module series:• TOBY-R200 - 0, 2 (default and factory-programmed value), 3• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R202 / SARA-U2 / LISA-U2 /LISA-U1 - The parameter is not supported

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

TOBY-L4• Any change in the RAT selection should be done in the de-registered state. In this case the response timeis immediate.
• The +UDCONF=59 AT command can be used to configure the scope of the preferred RAT settings
in automatic network selection mode. If AT+UDCONF=59 parameter <preferred_rat_conf>=0 the<PreferredAct> may not be the highest priority RAT.
TOBY-L2 / MPCI-L2• The set command changing RAT selection (although entered in de-registered state) re-activates the
protocol stack by triggering a network scan. As such network scan may interfere with successive
registration commands, that may answer with an error result code due to overlapping activities, it issuggested to wait 15 s after the +URAT set command before entering any AT command that triggers a
PS or a CS registration. Alternatively, the user can neglect the error result code and wait for the module
to complete the registration by polling the registration status or waiting for appropriate URCs.
• In boot phase and SIM refresh phase the RAT selection does not consider <PreferredAct> parametervalue. If possible, the module always registers on 3G RAT (or 2G RAT if 3G RAT is not available) andthen performs a reselection on the highest available RAT. It is possible to register directly on the highest
available RAT in case if it was the last selected in AT+COPS=2 / AT+COPS=0 cycles if <SelectedAcT>=
5 (GSM / LTE dual mode).
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S /MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280• When a 2G only SIM is used (the +UUICC AT command can be used to check the SIM type), LTE support
is implicitly disabled by the module because a 2G SIM cannot register on LTE radio access technology.
The +URAT read command will reflect the actual setting of the module. This automatic RAT adaptation
occurs after the SIM has been read, e.g. after the PIN insertion.
LARA-R2 / TOBY-R2• After a AT+COPS=2 / AT+COPS=0 cycle the DUT registers on the last selected RAT, AT+CFUN=0 / AT
+CFUN=1 or AT+CFUN=4 / AT+CFUN=1 cycle restores the order of RAT selection according to +URAT
settings.
• Any change in the RAT selection should be done in the de-registered state. In this case the response timeis immediate.
TOBY-R200• If <SelectedAcT> = 4 (GSM / UMTS / LTE (tri mode)) the <2ndPreferredAct> parameter is notsupported.
• If <SelectedAcT> = 4 or 6 the <PreferredAct> parameter is not supported.
LARA-R202 / LARA-R211 / LARA-R280 / TOBY-R202• If <SelectedAcT> = 6 (UMTS / LTE (dual mode)) the <PreferredAct> selection is not supported.

UBX-13002752 - R67

7 Network service

Page 108 of 1001

u-blox cellular modules - AT commands manual

SARA-U2 / LISA-U2 / LISA-U1• Issue AT+COPS=2 AT command to detach the module from the network. Use AT+COPS=0 to return tothe module full functionality.

7.9 Preferred Radio Access Technology (RAT) scope+UDCONF=59+UDCONF=59
Modules
Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
NVM
No
-

Error reference+CME Error

7.9.1 Description
Configures the scope of the preferred Radio Access Technology (RAT) which is set by means of the +URAT
AT command.
The setting applies only to automatic network selection mode (see +COPS AT command):• <preferred_rat_conf>=0: the RAT indicated in EFHPLMNwAct has the highest priority during automatic
HPLMN selection (see the 3GPP TS 23.122 [56]). If EFHPLMNwAct is not present or if the information containedin it does not apply to the PLMN selected, the RAT of the last RPLMN (Registered PLMN) retrieved fromthe NVM has the highest priority. If the last RPLMN information is not available, the preferred RAT which
is set by means of the +URAT AT command has the highest priority.
• <preferred_rat_conf>=1: the preferred RAT set by means of the +URAT AT command is forced to be thehighest priority RAT.
The AT command setting is stored to NVM and is immediately effective.

7.9.2 Syntax
Type
Set

SyntaxAT+UDCONF=59,<preferred_rat_
conf>

Read

AT+UDCONF=59

Response
OK

ExampleAT+UDCONF=59,0

OK+UDCONF: 59,<preferred_rat_conf> AT+UDCONF=59
OK+UDCONF: 59,0OK

7.9.3 Defined values
Parameter<preferred_rat_
conf>

UBX-13002752 - R67

Type
NumberDescription
Allowed values:• 0 (factory-programmed value): the preferred Access Technology set by means of+URAT AT command has the highest priority during automatic network selection
when EFHPLMNwAct is not present and when the last RPLMN information is notavailable.
• 1: the preferred Access Technology set by means of +URAT AT command is forced
to be the highest priority RAT during automatic network selection.
• 2: reserved

7 Network service

Page 109 of 1001

u-blox cellular modules - AT commands manual

7.10 Display EONS names +UEONS+UEONS
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
Yes

Response time
< 40 sError reference+CME Error

7.10.1 Description
This command displays the list of available networks adding EONS names if available. The list of available
networks with details like long operator name, short operator name, MCC/MNC, Long EONS name, Short EONS
name for each PLMN is reported. This command is an extension of AT+COPS=? command and it provides
additionally EONS names for the available PLMN's.

7.10.2 Syntax
Type
ActionSyntaxAT+UEONS

Response+UEONS: [list of supported (<stat>,long alphanumeric <oper>,shortalphanumeric <oper>,numeric<oper>[,<AcT>],[EONS long
operator name],[EONS short
operator name])s]
OK

Example+UEONS: (2,"T-Mobile D","TMobile D","26201","T-Mob D"," TMobile De"), (3, "Vodafone.de","Vodafone.de", "26202", "testnetwork EONS", "test EONS"), (3,"EPlus","E-Plus","26203"), (3,"o2 - de","o2 - de","26207")
OK

Test

AT+UEONS=?

OK

7.10.3 Defined values
See the description of +COPS parameters.

7.10.4 Notes
SARA-G3 / LEON-G1• the <AcT> parameter is not supported.

7.11 Display operator name +UDOPN+UDOPN
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
No
No

Response time
Up to 1 s

Error reference+CME Error

7.11.1 Description
Displays the network name accordingly to the selected <type>:• If the requested information is not available (e.g. no SIM-files EFOPL and EFPNN), the command displays the
network name which is most similar to the requested <type>• If the requested name is the Service Provider Name (<type>= 7), a null string is displayed if not available• In case EONS names are not available, NITZ names are displayed, if any• In case no NITZ name is available, CPHS names are used
• In case no CPHS name is available, ROM PLMN names are displayed• In case no ROM PLMN name matches to the current network, its numeric format (i.e. <type>=0) is returned

UBX-13002752 - R67

7 Network service

Page 110 of 1001

u-blox cellular modules - AT commands manual

The maximum expected response time could request about 1 s if the data are read by the SIM.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
The set command provides an error result code ("no network service") when the module is registered only
to a PS (Packet Switched) network operator. Issue a +UCGOPS read command to retrieve the Registered
PLMN in case the module is PS only attached due to SIM subscription restrictions.

7.11.2 Syntax
Type
Set

SyntaxAT+UDOPN=<type>

Response+UDOPN: <type>[,<name>[,<display_condition>]]OK

ExampleAT+UDOPN=4+UDOPN: 4,"Main Network"
OK
AT+UDOPN=7+UDOPN: 7,"SERVICE-PROVIDER",1OK
AT+UDOPN=7+UDOPN: 7,""

Test

AT+UDOPN=?

OK+UDOPN: (list of supported <type>s) +UDOPN: (0-9)
OKOK

7.11.3 Defined values
Parameter<type>

Type
NumberDescription
Network name format:• 0: numeric format of MCC/MNC network (three BCD digit country code and two/
three BCD digit network code)• 1: short name in ROM• 2: long name in ROM• 3: short network operator name (CPHS)• 4: long network operator name (CPHS)• 5: short NITZ name
• 6: full NITZ name• 7: service provider name• 8: EONS short operator name• 9: EONS long operator name• 11: short network operator name• 12: long network operator name
• 13: numeric format of network MCC/MNC even in limited service
Allowed values:• TOBY-L4 / LARA-R2 / TOBY-R2 - 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12 , 13
• TOBY-L2 / MPCI-L2 / SARA-U2 / LISA-U2 / LISA-U1 - 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12• SARA-G3 / LEON-G1 - 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

<name>

String• MCC/MNC code for <type>= 0 or 13• Corresponding network name for <type>= 1, 2, 3, 4, 5, 6, 8, 9, 11 or 12• Service provider name followed by <display_condition> for <type>=7Display condition as stored on SIM for the service provider name in respect to theregistered PLMN (see 3GPP TS 51.011 [17] for more details).

<display_condition> Number

7.11.4 Notes
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• EONS means Enhanced Operator Name from SIM-files EFOPL and EFPNN.
• The coding of <name> is according to the +CSCS setting.
TOBY-L2 / MPCI-L2• EONS means Enhanced Operator Name from SIM-files EFOPL and EFPNN.

UBX-13002752 - R67

7 Network service

Page 111 of 1001

u-blox cellular modules - AT commands manual••

The coding of <name> is according to the +CSCS setting.
The NITZ name (<type>=5 or 6) does not provide significant information.

7.12 Preferred PLMN list selection +CPLS+CPLS
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.12.1 Description
Selects one PLMN selector with Access Technology list in the SIM card or active application in the UICC (GSM
or USIM), that is used by +CPOL command.
The set command selects a list in the SIM/USIM. The read command returns the selected PLMN selector list
from the SIM/USIM.
The test command returns the whole index range supported lists by the SIM/USIM.

7.12.2 Syntax
Type
Set

SyntaxAT+CPLS=<list>

Response
OK

ExampleAT+CPLS=1

Read

AT+CPLS?

+CPLS: <list>

OK+CPLS: 1

Test

AT+CPLS=?

OK+CPLS: (list of supported <list>s)

OK+CPLS: (0-2)

OKOK

7.12.3 Defined values
Parameter<list>

Type
NumberDescription•••

0 (factory-programmed and default value): user controlled PLMN selector with
Access Technology EFPLMNwAcT, if not found in the SIM/UICC then PLMN preferred
list EFPLMNsel (this file is only available in SIM card or GSM application selected in
UICC); these files can be read and updated (see the 3GPP TS 31.102 [18]).
1: operator controlled PLMN selector with Access Technology EFOPLMNwAcT; this filecan be read only (see the 3GPP TS 31.102 [18]).
2: HPLMN selector with Access Technology EFHPLMNwAcT; this file can be read only
(see the 3GPP TS 31.102 [18]).

7.12.4 Notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The set command can be issued also omitting the <list> parameter.

UBX-13002752 - R67

7 Network service

Page 112 of 1001

u-blox cellular modules - AT commands manual

7.13 PS operator selection +UCGOPS+UCGOPS
Modules

Attributes

TOBY-L2 MPCI-L2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
No
No

Response time
Up to 3 min

Error reference+CME Error

7.13.1 Description
Forces an attempt to select and register on the PS (Packet Switched) network operator either automaticallyselected by the MT, or manually specified by the user.
The read command returns the network on which the MT is PS attached to, if any.
The test command returns a list of the available networks, specifying if they are forbidden and if PS is
supported.
The command in the execution syntax can be aborted if a character is sent to the DCE during the commandexecution. If the automatic selection is set (<mode>=0), the other parameters must be omitted.

7.13.2 Syntax
Type
Set

Read

Test

SyntaxResponse
AT+UCGOPS=[<mode>[,<format>[, OK<oper>[,<AcT>]]]]

AT+UCGOPS?

AT+UCGOPS=?

+UCGOPS: <status>[,<format>,<oper>,<AcT>]OK+UCGOPS: [(<stat>,longalphanumeric <oper>, shortalphanumeric <oper>, numeric<oper>,[<AcT>,]<ps_availability>)],,(list of supported <mode>s),(list of
supported <format>s)

ExampleAT+UCGOPS=0
OK
AT+UCGOPS=1,2,"22201"
OK+UCGOPS: 1,2,"22210",0OK+UCGOPS: (1,"vodafone IT","voda IT",
"22210",1),(3,"I TIM","TIM","22201",1),(3,"I WIND","I WIND","22288",1),,(0-1),
(0-2)
OK

OK

7.13.3 Defined values
Parameter<mode>

Type
Number<format>Number<oper>

String<stat>

NumberUBX-13002752 - R67

Description
Specified whether the operator selection is done automatically by the MT or is
manually bound to a specific network• 0 (default value): automatic (<oper> field is ignored)• 1: manual
Mandatory parameter if <mode> value is 1, it specifies the format of the network
operator name• 0 (default value): long alphanumeric <oper>• 1: short format alphanumeric <oper>• 2: numeric <oper>
String type given in format <format>; this field may be up to 36 characters long forlong alphanumeric format, up to 8 characters for short alphanumeric format and 5
characters long for numeric format (MCC/MNC codes); this parameter is mandatory
if <mode> value is 1
PLMN status attribute with respect to the MT• 0: unknown• 1: available• 2: current• 3: forbidden

7 Network service

Page 113 of 1001

u-blox cellular modules - AT commands manual

Parameter<ps_availability>

Type
Number

<AcT>

Number<status>NumberDescription
GPRS availability• 0: not supported• 1: supported
Indicates the radio access technology• 0: GSM• 1: GSM COMPACT• 2: UTRAN (UMTS)• 3: GSM with EDGE availability• 4: UTRAN with HSDPA availability• 5: UTRAN with HSUPA availability• 6: UTRAN with HSDPA and HSUPA availability• 7: LTE
Current GPRS registration status and PLMN selection mode of the MT• 0: attached, automatic PLMN selection mode
• 1: attached, manual PLMN selection mode
• 2: detached7.13.4 Notes
TOBY-L2 / MPCI-L2• The test command triggers a network search only when the MT is in class "CG" or detached from the
network (i.e. +COPS: 2). If the MT is in class "B", the test command will immediately return an error resultcode.
• The test commands will return only packet-switched capable 2G/3G PLMNs and LTE PLMNs.
SARA-U2 / LISA-U2 / LISA-U1• The <AcT> parameter can be set only to 0 and 2.
SARA-G3 / LEON-G1• The <AcT> parameter is not supported.

7.14 Network registration status +CREG+CREG
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.14.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 theUTRAN INFORMATION MOBILITY message during dedicated connections; in the latter cases the reported

UBX-13002752 - R67

7 Network service

Page 114 of 1001

u-blox cellular modules - AT commands manual<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.
The DTE application should set a reasonable timer (10 s) when receiving the +CREG: 3 URC, since thismight 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 andread command result codes, where supported, apply to the registration status and location information
for those services.
SARA-G4
The command setting is stored in the personal profile following the procedure described in the Saving AT
commands configuration section.

7.14.2 Syntax
Type
Set

SyntaxAT+CREG=[<n>]Response
OK

Read

AT+CREG?

+CREG: <n>,<stat>[,<lac>,<ci>[,<AcTStatus>]]Test

AT+CREG=?

OK+CREG: 0,0

OK
OK+CREG: (list of the supported <n>s) +CREG: (0-2)
OK+CREG: <stat>[,[<lac>],[<ci>][,[<AcTStatus>][,<cause_type>,<reject_cause>]]]URC

ExampleAT+CREG=1

OK+CREG: 1,"4E54","44A5"

7.14.3 Defined values
Parameter<n>Type
Number<stat>

Number<lac>

String<ci>

String<AcTStatus>

NumberUBX-13002752 - R67

Description
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
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 [12] and 3GPP
TS 24.301 [68] 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)
Two bytes location area code or tracking area code (if <AcTStatus>=7) inhexadecimal format (e.g. "00C3"). The value FFFF means that the current <lac> value
is invalid.
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.
Indicates the radio access technology:

7 Network service

Page 115 of 1001

u-blox cellular modules - AT commands manual

ParameterType<cause_type>

Number<reject_cause>

NumberDescription• 0: GSM• 1: GSM COMPACT• 2: UTRAN• 3: GSM/GPRS with EDGE availability• 4: UTRAN with HSDPA availability• 5: UTRAN with HSUPA availability• 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:• TOBY-L4 / TOBY-L200 / TOBY-L210 / TOBY-L280 / MPCI-L200 / MPCI-L210 /MPCI-L280 / TOBY-R200 - 0, 2, 3, 4, 5, 6, 7
• TOBY-L201 / TOBY-L220-02S / MPCI-L201 / MPCI-L220-02S / LARA-R202 /LARA-R280 / TOBY-R202 - 2, 4, 5, 6, 7
• TOBY-L220-62S / MPCI-L220-62S / LARA-R203 / LARA-R204 / LARA-R220 - 7• LARA-R211 - 0, 3, 7
• SARA-U201 / SARA-U260 / SARA-U270-00S / SARA-U270-00X / SARA-U270-03A /SARA-U270-03S / LISA-U2 - 0, 2, 3, 4, 5, 6
• SARA-U270-53S / SARA-U270-73S / SARA-U280 - 2, 4, 5, 6
• LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - parameter not supported<reject_cause> type. Allowed values:• 0: indicates that <reject_cause> contains an EMM cause value, see 3GPP TS 24.30
1 [68] Annex A
Cause of the failed registration. The value is of type as defined by <cause_type>7.14.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 makeemergency calls if some network is available. Possible causes:
o PIN not enteredo 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 levelo HPLMN or allowed PLMN are available but the registration is rejected, e.g. roaming is not allowedin 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 MSo Illegal ME
o IMSI unknown at HLR
o PLMN not allowedo Location area not allowedo Roaming not allowed in this location areao 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 registerwith it. If the registration type is automatic, the MS may look for an allowed PLMN if the rejection cause

UBX-13002752 - R67

7 Network service

Page 116 of 1001

u-blox cellular modules - AT commands manual

•

•
•

•

•
•

•

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 Normalo Limitedo No service
o Service detachedo Service disabled
It may be issued after the failure of a registration procedure, before starting a PLMN search, when<stat>=2.
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 theequivalent HPLMN's)
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L210-00S /MPCI-L210-60S / MPCI-L210-63S
Being SMS the only non-EPS service supported by these modules, this status is equivalent to 1.
7: in LTE, the MT is registered only for the SMS circuit-switched service on a VPLMN, in national orinternational roaming
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L210-00S /MPCI-L210-60S / MPCI-L210-63S
Being SMS the only non-EPS service supported by these modules, this status is equivalent to 5.
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 theequivalent 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 orinternational 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.

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.
• <n>=3 is not supported.
• <stat>=8 is not supported.
TOBY-L4• The URC does not notify access technology information changes that might change in polling; see the+UREG AT command to monitor the RAT changes.
TOBY-L2 / MPCI-L2• The information text response to the read command and the URC will assume these values in these
conditions:o During the initial network searching at the module power-on, the <stat> parameter is 2
o If the module is CS attached to the GSM/UTRAN/E-UTRAN home network, the <stat> parameteris 1
o In the out of coverage state, the <stat> parameter is 2
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L210-00S /MPCI-L210-60S / MPCI-L210-63S• <stat>=9 and 10 are not supported.
SARA-G4 / SARA-G3 / LEON-G1• If GPRS is enabled and +CREG and +CGREG URCs are both enabled too, once the module is registeredand attached then the two URCs are sent out quite at the same time.
SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G1• Equivalent HPLMN for <stat>=1 is not supported: <stat>=5 is indicated in this case.

UBX-13002752 - R67

7 Network service

Page 117 of 1001

u-blox cellular modules - AT commands manual

7.15 HSDPA/HSUPA mode configuration +UHSDUPA+UHSDUPA
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

7.15.1 Description
Enables / disables the HSDPA and HSUPA also configuring the related data rate. The settings are saved in the
NVM at the module power off; the new configuration will be effective at the next power on.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

7.15.2 Syntax
Type
Set

Read

Test

SyntaxAT+UHSDUPA=<HSDPA-mode>,<HS-DSCH_category>[,<HSUPAmode>[,<E-DCH_category>]]
AT+UHSDUPA?

AT+UHSDUPA=?

Response
OK

ExampleAT+UHSDUPA=1,8,1,6
OK+UHSDUPA: <HSDPA-mode>,<HSDSCH_category>,<HSUPA-mode>,<E-DCH_category>OK+UHSDUPA: (<list of supported<HSDPA-mode>s),(<listof supported <HS-DSCH_
category>s>),(<list of supported<HSUPA-mode>s),(<list of
supported>,<E-DCH_category>s)+UHSDUPA: 1,8,1,6
OK+UHSDUPA: (0-1),(6,8,10,12,13,14),(0,1),(1,2,6)
OKOK

7.15.3 Defined values
Parameter<HSDPA-mode>

Type
Number<HS-DSCH_
category>

Number<HSUPA-mode>

Number<E-DCH_category>

NumberUBX-13002752 - R67

Description• 0: HSDPA off• 1 (default and factory-programmed value): HSDPA on
Integer value representing the HS-DSCH category as defined in 3GPP TS 25.306 [43]:• TOBY-L4 - Allowed values: 6, 8, 10, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24. The
factory-programmed value is 24.
• TOBY-L200 / TOBY-L201 / MPCI-L200 / MPCI-L201 - Allowed values: 8, 14. The
factory-programmed value is 14.
• TOBY-L210 / TOBY-L220-02S / TOBY-L280 / MPCI-L210 / MPCI-L220-02S /MPCI-L280 - Allowed values: 8, 14, 24. The factory-programmed value is 24.
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200 / LISA-U201 / LISA-U260 / LISA-U270 /LISA-U1 - Allowed values: 6, 8. The factory-programmed value is 8.
• LISA-U230 - Allowed values: 6, 8, 10, 12, 13, 14. The default value is 14.
• 0: HSUPA off• 1 (default and factory-programmed value): HSUPA on
Integer value representing the E-DCH category as defined in 3GPP TS 25.306 [43]:• TOBY-L4 / LARA-R2 / TOBY-R2 - Allowed values: 1, 2, 6. The factory-programmed
value is 6.
• TOBY-L2 / MPCI-L2 - Allowed values: 5, 6. The factory-programmed value is 6.

7 Network service

Page 118 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• SARA-U2 / LISA-U2 - Allowed values: 1, 2, 4, 6. The factory-programmed value is 6.
• SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S /LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S /LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270 - Allowed values: 1, 2, 6. The
factory-programmed value is 6.
• LISA-U1 - Allowed values: 1, 2, 4, 5, 6. The factory-programmed value is 6.

7.16 Preferred operator list +CPOL+CPOL
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
No
No

Response time< 10 sError reference+CME Error

7.16.1 Description
Edits the user preferred list of networks in the active application on the UICC (GSM or USIM) or preferred listof networks in the SIM card.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The command accesses the list of preferred PLMNs previously selected by +CPLS, if implemented. If+CPLS is not implemented the command tries to access EFPLMNwAcT and if this file is not present and a
UICC GSM application is selected or a SIM card is used then the EFPLMNsel file is accessed.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The set command writes an entry in the selected list. When an entry is added to the preferred operator list,
it should have a correspondence in the ROM PLMN names returned by the +COPN command. If <index>
is given but <oper> is left out, the entry is deleted. If only <format> is given, the <oper> format in theread command is changed. The <GSM_AcT>, <GSM_Compact_AcT>, <UTRAN_AcT> and <E-UTRAN_
AcT> parameters are required when writing user controlled PLMN selector with Access Technology(EFPLMNwAcT).
The read command returns all used entries from the SIM list of preferred PLMNs and the Access Technologies
for each PLMN in the list where provided.
If a new PLMN is added in a different format than the one previously set, the <format> parameter always
switches to the last used.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
If in the +COPN list there are more than one PLMN with the same name in alphanumeric (short orlong) format, the numeric format shall be used to add this PLMN <entry> in the preferred operator list;
otherwise the result will be unpredictable.

7.16.2 Syntax
Type
Set

Read

SyntaxResponse
AT+CPOL=[<index>][,<format>[,OK<oper>[,<GSM_AcT>,<GSM_
Compact_AcT>,<UTRAN_AcT>[,<EUTRAN_AcT>]]]]
AT+CPOL?
+CPOL: <index1>,<format>,<oper1>[,<GSM_AcT1>,<GSM_
Compact_AcT1>,<UTRAN_AcT1>[,<E-UTRAN_AcT>]]

ExampleAT+CPOL=2,0,"I WIND",1,0,1
OK+CPOL: 1,0,"F SFR",1,0,1+CPOL: 2,0,"TIM I",1,0,1
OK[+CPOL: <index2>,<format>,<oper2>[,<GSM_AcT2>,<GSM_
Compact_AcT2>,<UTRAN_AcT2>[,<E-UTRAN_AcT>]]...]OK

UBX-13002752 - R67

7 Network service

Page 119 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+CPOL=?

Response
Example+CPOL: (list of supported<index>s), +CPOL: (1-30),(0-2)(list of supported <format>s)OKOK

7.16.3 Defined values
Parameter<index> / <indexn>

Type
Number<format>Number<oper> / <opern><GSM_AcT>

StringNumber<GSM_Compact_
AcT>

Number<UTRAN_AcT>

Number<E-UTRAN_AcT>

NumberDescription
Represents the order number of operator in the SIM preferred operator list. The
parameter range depends on the number of entries in SIM card (i.e. its size), but canbe further limited by the module capabilities of the module.
See also +COPS command description:• 0: long format alphanumeric <oper>• 1: short format alphanumeric <oper>• 2 (default value): numeric <oper>
Format indicated by <format>
GSM access technology. Allowed values:• 0: access technology not selected• 1: access technology selected
GSM compact access technology. Allowed values:• 0: access technology not selected• 1: access technology selected
UTRA access technology. Allowed values:• 0: access technology not selected• 1: access technology selected
E-UTRAN access technology. Allowed values:• 0: access technology not selected• 1: access technology selected

7.16.4 Notes
TOBY-L2 / MPCI-L2• When an entry is deleted the subsequent entries are shifted up of one position.
• The <oper> format in the read command is always changed when the <format> parameter is given.
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S /MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280• If the module is not registered (+COPS=2), the set command returns an error result code.
• To modify an already inserted entry (whose order number is <index>), delete the original entry andinsert the new one with the same <index>.
• When inserting a new entry, it is possible to set to 1 only one "access technology" parameter: <GSM_
AcT> or <GSM_Compact_AcT> or <UTRAN_AcT> or <E-UTRAN_AcT>.
SARA-U2 / LISA-U2 / LISA-U1• The <E-UTRAN_AcT> parameter is not supported.
• The default value of <format> parameter is 0 (long format alphanumeric <oper>).
• The <oper> format in the read command is always changed when the <format> parameter is given.
SARA-G4 / SARA-G3 / LEON-G1• <GSM_AcT>, <GSM_Compact_AcT>, <UTRAN_AcT> and <E-UTRAN_AcT> parameters are notsupported.
• The default value of <format> parameter is 0 (long format alphanumeric <oper>).
• The <oper> format in the read command is always changed when the <format> parameter is given.
• If the network operator is not present in the SIM list of preferred PLMNs, then the information text
response to the read command will display the PLMN in the short format alphanumeric format.

UBX-13002752 - R67

7 Network service

Page 120 of 1001

u-blox cellular modules - AT commands manual

7.17 Read operator names +COPN+COPN
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.17.1 Description
Returns the list of operator names from the MT. Each operator code <numeric n> that has an alphanumericequivalent <alpha n> in the MT memory shall be returned.

7.17.2 Syntax
Type
ActionSyntaxAT+COPN

Response+COPN: <numeric 1>,<alpha1>

Example+COPN: "21901","T-Mobile HR"[+COPN: <numeric2>,<alpha2> [...]] +COPN: "21910","HR VIP"OK

+COPN: "22201","I TIM"
+COPN: "22210","vodafone IT"

Test

AT+COPN=?

OK
OK

OK

7.17.3 Defined values
Parameter<numeric n><alpha n>Type
StringStringDescription
Operator in numeric format (see +COPS AT command)
Operator in long alphanumeric format (see +COPS AT command)

7.17.4 Notes
TOBY-L2 / MPCI-L2• In case the module is not registered to the network (+COPS: 2) the action command provides an error
result code.
SARA-G4• The PIN insertion is not mandatory before the command execution.

7.18 Network emergency bearer services support +CNEM+CNEM
Modules
Attributes

TOBY-L4
LARA-R202 LARA-R203 LARA-R204 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
partial
No
NVM
No

Response time-Error reference+CME Error

7.18.1 Description
Configures sending of URCs from MT to the TE, in case of changes in the emergency bearer services support.

7.18.2 Syntax
Type
Set

Syntax
AT+CNEM=[<reporting>]

Response
OK

Read

AT+CNEM?

+CNEM: <reporting>,<emb_Iu_
supp>,<emb_S1_supp>

Test

AT+CNEM=?

UBX-13002752 - R67

OK+CNEM: (list of supported<reporting>s)

7 Network service

ExampleAT+CNEM=1
OK+CNEM: 1,0,1
OK+CNEM: (0,1)
OK

Page 121 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK+CNEMIU: <emb_Iu_supp>+CNEMS1: <emb_S1_supp>

URC
URC

Example+CNEMIU: 0+CNEMS1: 1

7.18.3 Defined values
Parameter<reporting>Type
Number<emb_Iu_supp>

Number<emb_S1_supp>

NumberDescription
Reporting configuration:• 0 (default and factory programmed value): URCs disabled• 1: URCs enabled
Emergency bearer services support indicator for Iu mode (see Notes):• 0: emergency bearer services in Iu mode and A/Gb mode not supported
Emergency bearer services support indicator for S1 mode (see Notes):• 0: emergency bearer services in S1 mode not supported• 1: emergency bearer services in S1 mode supported

7.18.4 Notes••

The command needs the SIM card to work correctly.
The indicators <emb_Iu_supp> and <emb_S1_supp> are only set to supported when explicitly signalledfrom the network. When an emergency bearer services support indicator is not signalled from the networkor if no network is available, this is interpreted as "emergency bearer services not supported".

TOBY-L4 / LARA-R2 / TOBY-R2• The AT command setting is not saved in NVM.

7.19 Steering of Roaming configuration +UDCONF=20+UDCONF=20
Modules

Attributes

LARA-R211 TOBY-R200-42B
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SARA-G3 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

7.19.1 Description
Enables / disables the Steering of Roaming feature.
The setting can be changed only when the module is not registered to, and not searching for, a network (i.e.
when +CREG's <stat> is 0). The new setting is saved in NVM and takes place at the next network registration /search.

7.19.2 Syntax
Type
Set

SyntaxAT+UDCONF=20,<SoR_enable>

Response
OK

ExampleAT+UDCONF=20,1

Read

AT+UDCONF=20+UDCONF: 20,<SoR_enable>

OK
AT+UDCONF=20

OK+UDCONF: 20,1
OK

7.19.3 Defined values
Parameter<SoR_enable>

UBX-13002752 - R67

Type
NumberDescription
Enables / disables the Steering of Roaming feature:• 0: Steering of Roaming disabled• 1 (factory-programmed value): Steering of Roaming enabled

7 Network service

Page 122 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 2: Steering of Roaming enabled with automatic switch from manual to automatic
PLMN selection mode if the maximum number of registration attempts rejectedwith cause 17 (Network Failure) has been reached7.19.4 Notes
LARA-R211• The command is not supported by LARA-R211-02B-00.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-01S /LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270• <SoR_enable>=2 is not supported.
SARA-U270-53S• The factory-programmed value of <SoR_enable> parameter is 0.
SARA-G3 / LEON-G1• The factory-programmed value of <SoR_enable> parameter is 0.
• <SoR_enable>=2 is not supported.

7.20 Fast Dormancy activation +UFDAC+UFDAC
Modules

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

Attributes

7.20.1 Description
Activates or deactivates the autonomous Fast Dormancy or triggers a single Fast Dormancy request
depending on the specified mode. If all the constraints are satisfied a Signaling Connection Release Indication(SCRI) is sent to the network. There is no final confirmation if the SCRI was sent to the network, i.e. the "OK"final result code only indicates that the command's syntax has been fulfilled.

7.20.2 Syntax
Type
Set

Read

Test

Syntax
AT+UFDAC=[[<FD_mode>][,<FD_
Delay_Timer_duration>[,<FD_
Inhibit_Timer_duration>]]]AT+UFDAC?

AT+UFDAC=?

Response
OK

ExampleAT+UFDAC=1
OK+UFDAC: <FD_mode>,<FD_Delay_
Timer_duration>,<FD_Inhibit_
Timer_duration>+UFDAC: 3,5,5
OK

OK+UFDAC: (list of the supported <FD_ +UFDAC: (1-3),(1-60),(0,1-120)
mode>s),(list of the supported <FD_
OK
Delay_Timer_duration>s),(list of
the supported <FD_Inhibit_Timer_
duration>s)OK

7.20.3 Defined values
Parameter<FD_mode>

UBX-13002752 - R67

Type
NumberDescription
Indicates the action to perform:• 1: one shot SCRI transmission request (application-driven FD)

7 Network service

Page 123 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<FD_Delay_Timer_
duration>

Number<FD_Inhibit_Timer_
duration>

NumberDescription• 2: activate automatic SCRI transmission request (autonomous FD)• 3 (factory-programmed value): deactivate automatic SCRI transmission request
If omitted, only the delay and inhibit timer values are saved and no other action is
performed.
Delay Timer duration in seconds, range 1-60. The factory-programmed value is 5.
The Delay Timer is used for the autonomous FD (<FD_mode>=2). When the module isin connected mode with no data available on the user plane this timer starts running.
At its expiry, the evaluation for the SCRI transmission is done.
Inhibit Timer duration in seconds, range 1-120 (the value 0 disables the Inhibit Timer).
The factory-programmed value is 5.
The Inhibit Timer is an extension of T323. If the network supports 3GPP R8 Fast
Dormancy, the Inhibit Timer and T323 are the same and thus the timer's duration is
network specified. Otherwise the value <FD_Inhibit_Timer_duration> is used.

7.20.4 Notes••••

The Fast Dormancy feature is available only in UMTS RAT.
The set command updates the <FD_Delay_Timer_duration> and <FD_Inhibit_Timer_duration> values
stored in NVM, if they are specified; otherwise the values previously stored in NVM are used.
If automatic SCRI transmission request is active, one shot SCRI transmission requests are ignored.
The constraints to be satisfied before sending a SCRI are:o No 'relevant' RRC procedure is ongoingo Inhibit Timer is not runningo No NAS signaling is ongoingo No data on the user plane was transferred during the last <FD_Delay_Timer_duration> seconds

LISA-U270-62S / LISA-U270-63S / LISA-U270-68S• The <FD_mode> factory-programmed value is 2.
• The <FD_Delay_Timer_duration> and <FD_Inhibit_Timer_duration> are set respectively to 7 and 120 andcannot be modified by means of AT commands.

7.21 Fast Dormancy configuration +UDCONF=61+UDCONF=61
Modules

Attributes

TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201 MPCI-L210
MPCI-L220-02S MPCI-L280
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

7.21.1 Description
Configures the Fast Dormancy modes.

7.21.2 Syntax
Type
Set

SyntaxAT+UDCONF=61,<FD_conf>

Response
OK

ExampleAT+UDCONF=61,1

Read

AT+UDCONF=61+UDCONF: 61,<FD_conf>

OK
AT+UDCONF=61

OK+UDCONF: 61,2
OK

UBX-13002752 - R67

7 Network service

Page 124 of 1001

u-blox cellular modules - AT commands manual

7.21.3 Defined values
Parameter<FD_conf>

Type
NumberDescription
Specifies which <FD_mode>'s values are allowed in the +UFDAC AT command. If a notallowed <FD_mode> value is issued, +UFDAC will display the error result code "+CME
ERROR: operation not allowed":• 0: values 1 and 2 are not allowed in <FD_mode>• 1: value 2 is not allowed in <FD_mode>• 2 (factory-programmed value): all the <FD_mode> values are allowed

7.22 Network selection control +PACSP+PACSP
Modules

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Attributes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.22.1 Description
If the EFCSP (Customer Service Profile) is available the +PACSP URC is provided in the following cases:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - at the module boot time
• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - whenever the SIM/
USIM issues the REFRESH proactive command related to the EFCSPFor further information, see the AT&T Device Requirements [48].
The EFCSP is available on SIM/USIM cards from AT&T mobile network operator.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
The command allows checking whether the EFCSP (Customer Service Profile) is available on the SIM/USIM
card and, if available, what is the value of the PLMN mode bit; otherwise an error result code is provided("+CME ERROR: operation not allowed" if +CMEE is set to 2).
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
This functionality will typically be used in cases where AT&T subscribers internationally travel, or if there
is a need to enable manual network selection functionality.

7.22.2 Syntax
Type
Read

SyntaxAT+PACSP?

URC

Response+PACSP<bit_value>

Example+PACSP1

OK+PACSP<bit_value>

OK+PACSP0

7.22.3 Defined values
Parameter<bit_value>

Type
NumberDescription
PLMN mode bit value:• 0: automatic network selection is forced (see Notes)• 1: network selection mode unchanged (see Notes)

7.22.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>0
1
2

UBX-13002752 - R67

PLMN mode bit <bit_value>000

7 Network service

Autoregistration behavior
Automatic network selection
Automatic network selection
Disabled

Page 125 of 1001

u-blox cellular modules - AT commands manual

Autoregistration <mode>
0
1

PLMN mode bit <bit_value>
1
1

2

1

Autoregistration behavior
Automatic network selection
Manual network selection (search for the PLMN
stored in the selected profile)
Disabled

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The PIN insertion is not mandatory before the command execution.

7.23 Integrity check on test networks configuration+UDCONF=81+UDCONF=81
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S
TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
MPCI-L200-02S MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

7.23.1 Description
Configures the integrity check on 3G/4G test networks.
Integrity check on 3G/4G test networks shall be disabled only when the authentication and integrity are
disabled on the 3G/4G test network on which the module will be registered.
Configure the network simulator with a PLMN not present in the ROM PLMN list (+COPN).
Disabling integrity and security will not affect IMS, thus the command cannot be used when using IMS.

7.23.2 Syntax
Type
Set

SyntaxAT+UDCONF=81,<integrity_check_enabled>Response
OK

Read

AT+UDCONF=81+UDCONF: 81,<integrity_check_enabled>OK

ExampleAT+UDCONF=81,0OK
AT+UDCONF=81+UDCONF: 81,1
OK

7.23.3 Defined values
Parameter<integrity_check_enabled>Type
NumberDescription
Integrity check on 3G/4G test networks configuration. Allowed values:• 0: integrity check on test networks disabled (MCC/MNC not available in +COPN set
command's response)• 1 (factory-programmed value): integrity check on test networks enabled (MCC/MNC
not available in +COPN set command's response)

7.23.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• The command setting is not stored in the NVM.

UBX-13002752 - R67

7 Network service

Page 126 of 1001

u-blox cellular modules - AT commands manual

7.24 Select band +UBANDSEL+UBANDSEL
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

7.24.1 Description
Allows switching from the automatic band selection to the selected ones. Up to four bands can be set.
SARA-U201-04B
Up to five bands can be set.
LISA-U200-04B / LISA-U201-04B
Up to six bands can be set.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
To make the setting effective, the module must be deregistered and registered again. (see Notes for theprocedure to enter the detach state).
The MT will camp on a cell, if suitable, belonging to one of the selected band; the OK final result code is
not related to the result of the camping on the new cell.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
The list of supported bands presents exclusively GSM, UMTS or LTE bands depending on which RAT the
MT is currently registered. If it is not registered, the bands presented depend on +URAT command:••

If in single mode, depends on <AcT>
If in dual mode, depends on <PreferredAct>

TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S
The set command forces a single mode behaviour thus the +URAT <AcT> parameter value could be
modified.
TOBY-L2 / MPCI-L2
After having issued a set command the module automatically performs a de-registration/registration
cycle.
See the corresponding module data sheet for the bands supported by each module.

7.24.2 Syntax
Type
Set

SyntaxResponse
AT+UBANDSEL=<band_1>[,<band_ OK
2>[,...]]Read

AT+UBANDSEL?

Test

AT+UBANDSEL=?

UBX-13002752 - R67

ExampleAT+UBANDSEL=900

OK+UBANDSEL: <band_1>[,<band_2>[, +UBANDSEL: 850,900,1800,1900
...]]
OK
OK
+UBANDSEL: (list of supported+UBANDSEL: (0,850,900,1800,1900)<band_x>)
OKOK

7 Network service

Page 127 of 1001

u-blox cellular modules - AT commands manual

7.24.3 Defined values
Parameter<band_x>

TypeNumberDescription
•
•
•
•
•
•
•
•
•
•
•

0: restore the factory-programmed configuration of the module
700: selection of 700 MHz band (3G and 4G band 12, band 13, band 17, band 28)
800: selection of 800 MHz band (3G and 4G band 6, band 19, band 20)
850: selection of 850 MHz band (3G and 4G band 5)
900: selection of 900 MHz band (3G and 4G band 8)
1500: selection of 1500 MHz band (3G and 4G band 11)
1700: selection of 1700 MHz band (3G and 4G band 4)
1800: selection of 1800 MHz band (3G and 4G band 3)
1900: selection of 1900 MHz band (3G and 4G band 2)
2100: selection of 2100 MHz band (3G and 4G band 1)
2600: selection of 2600 MHz band (3G and 4G band 7)

7.24.4 Notes
TOBY-L2 / MPCI-L2• Issue the AT+CFUN=4 AT command to detach the module from the network. Use AT+CFUN=1 to returnto the module full functionality.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• Issue the AT+COPS=2 AT command to detach the module from the network.
SARA-U201 / LISA-U200 / LISA-U201 / LISA-U230• In order to set the band 800 MHz issue the AT+UBANDSEL=800,850 command.

7.25 Select band +UACT+UACT
Modules
Attributes

TOBY-L4
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

7.25.1 Description
Allows switching from the automatic band selection to the selection of one or more allowed GSM, UMTS and
LTE bands.
The MT will camp on a cell, if suitable, belonging to one of the select bands; the OK final result code is not
related to the result of the camping on the new cell.
Band changes for one particular RAT will not affect the other RAT configuration. (i.e. setting LTE bands
will not change anything on GSM/UMTS bands)
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

7.25.2 Syntax
Type
Set

Read

SyntaxResponse
AT+UACT=<reserved>,<reserved>, OK<reserved>,<band_1>[,<band_2>[,...]]
AT+UACT?
+UACT: ,,,<band_1>[,<band_2>[,...]]

Test

AT+UACT=?

UBX-13002752 - R67

ExampleAT+UACT=,,,900,8,103
OK+UACT: ,,,900,8,103

OK
OK+UACT: ,,,(list of supported GSM+UACT: ,,,(900,1800),(1,8),(101,103,10<band_X>),(list of supported UMTS 7,108,120),(138)7 Network service

Page 128 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse<band_X>),(list of supported LTE<band_X>)

ExampleOKOK

7.25.3 Defined values
Parameter<band_x>

TypeNumberDescription• 0: restore the factory-programmed configuration of the module
GSM band:• 900: selection of 900 MHz band• 1800: selection of 1800 MHz band• 1900: selection of 1900 MHz band
• 850: selection of 850 MHz band
• 450: selection of 450 MHz band• 480: selection of 480 MHz band
• 750: selection of 750 MHz band
• 380: selection of 380 MHz band
• 410: selection of 410 MHz band
• 710: selection of 710 MHz band
• 810: selection of 810 MHz band
UMTS band:• 1: band UMTS I• 2: band UMTS II• 3: band UMTS III• 4: band UMTS IV• 5: band UMTS V• 6: band UMTS VI• 7: band UMTS VII• 8: band UMTS VIII
• 9: band UMTS IX• 10: band UMTS X• 11: band UMTS XI• 12: band UMTS XII• 13: band UMTS XIII
• 14: band UMTS XIV• 15: band UMTS XV• 16: band UMTS XVI• 17: band UMTS XVII
• 18: band UMTS XVIII• 19: band UMTS XIX• 20: band UMTS XX• 21: band UMTS XXI• 22: band UMTS XXII
• 25: band UMTS XXV
UMTS TDD band:• 201: band UMTS TDD A• 202: band UMTS TDD B• 203: band UMTS TDD C• 204: band UMTS TDD D• 205: band UMTS TDD E• 206: band UMTS TDD F
LTE band:• 101: band LTE 1• 102: band LTE 2• 103: band LTE 3• 104: band LTE 4• 105: band LTE 5

UBX-13002752 - R67

7 Network service

Page 129 of 1001

u-blox cellular modules - AT commands manual

Parameter

UBX-13002752 - R67

Type

Description• 106: band LTE 6• 107: band LTE 7• 108: band LTE 8• 109: band LTE 9• 110: band LTE 10• 111: band LTE 11• 112: band LTE 12• 113: band LTE 13• 114: band LTE 14• 115: band LTE 15• 116: band LTE 16• 117: band LTE 17• 118: band LTE 18• 119: band LTE 19• 120: band LTE 20• 121: band LTE 21• 122: band LTE 22• 123: band LTE 23• 124: band LTE 24• 125: band LTE 25• 126: band LTE 26• 127: band LTE 27• 128: band LTE 28• 129: band LTE 29• 130: band LTE 30• 131: band LTE 31• 132: band LTE 32• 133: band LTE 33• 134: band LTE 34• 135: band LTE 35• 136: band LTE 36• 137: band LTE 37• 138: band LTE 38• 139: band LTE 39• 140: band LTE 40• 141: band LTE 41• 142: band LTE 42• 143: band LTE 43• 144: band LTE 44• 145: band LTE 45• 146: band LTE 46• 147: band LTE 47• 148: band LTE 48• 149: band LTE 49• 150: band LTE 50• 151: band LTE 51• 152: band LTE 52• 153: band LTE 53• 154: band LTE 54• 155: band LTE 55• 156: band LTE 56• 157: band LTE 57• 158: band LTE 58• 159: band LTE 59• 160: band LTE 60• 161: band LTE 61• 162: band LTE 62• 163: band LTE 63

7 Network service

Page 130 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 164: band LTE 64

7.26 Cell environment description +CGED+CGED
Modules

Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.26.1 Description
Provides the cell environment information that can be periodic (with a period of 5 s) or performed only once
depending on the <mode> parameter value:• <mode>=0, 1, 128, 129:o Both the serving and neighbour cell information are provided• <mode>=3, 4, 131, 132:o A subset of the network parameters of the serving cell information is provided• <mode>=5, 6, 133, 134:o Both the serving and neighbour cell information are providedo A subset of the network parameters of the serving cell information is provided
o The information on neighbour cells contained in radio resource BA list is reported. The number ofneighbour cells can be configured by means of the +UDCONF=83 AT command (where supported);by default, the neighbour cell content may be available up to 32 times in idle-mode, up to 6 indedicated-mode; in packet transfer mode (PDP context active) no reporting is possible on AT UART
interface as it is used for data transfer (the multiplexer can be used to create two virtual serial ports,
one for data transfer, one for AT commands)
If <mode> parameter value is greater than 127 the information text response will provide the cell information
in a compact, machine readable format without the tags (e.g. "MCC", "RxLev" will not be printed).
LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270
The SIM verification is needed.
The information text response of the set command depends on the cellular standard and the access technology(if present).
In case of LTE radio access technology:• The information for up to 32 neighbour cells is available
In case of UMTS radio access technology:• The information for up to 56 neighbour cells is available (32 reserved for 3G cells and 24 for 2G cells)• The syntax for cell information differs in the channel typeIn case of GSM radio access technology:• The information for up to 32 neighbour cells is available
An Equivalent PLMN (Public Land Mobile Network) is a PLMN equivalent to the RPLMN (Registered
PLMN). The MT has a list of EPLMN's that is updated at the end of each location update procedure, routing
area update procedure and GPRS attach procedure.

7.26.2 Syntax
Type
Set

SyntaxAT+CGED=[<mode>[,<details>]]

Response
Response syntax for 2G modules:+CGED:
Service-Cell:
MCC: <MCC>, MNC: <MNC>, LAC: <LAC>, CI: <CI>, BSIC: <BSIC>[Equivalent PLMNs:

UBX-13002752 - R67

7 Network service

Page 131 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
MCC: <MCC>, MNC: <MNC>]
Arfcn: <arfcn>, [RxLevServ:: <RxLevServ>,] [RfChannels: <RfChannels>,]Arfcn_ded: <Arfcn_ded>, [RxLevFull: <RxLevFull>,] [RxLevSub: <RxLevSub>,][RxQualFull: <RxQualFull>, RxQualSub: <RxQualSub>, Ciphering: <ciphering>
ms_txpwr: <ms_txpwr>, rx_acc_min: <rx_acc_min>, cbq: <cbq>, cba: <cba>, c2_
valid: <c2_valid>, cr_offset: <cr_offset>, tmp_offset: <tmp_offset>, penalty_t:<penalty_t>, c1: <c1>, c2: <c2>, ch_type: <ch_type>, ch_mode: <ch_mode>, txpwr:<txpwr>, dtx_used: <dtx_used>, t3212: <t3212>, acc: <acc>,][t_adv: <t_adv>,][bs_pa_mfrms: <bs_pa_mfrms>, dsc: <dsc>, rll: <rll>]
Neighbour Cell <n>:MCC: <MCC>, MNC: <MNC>, LAC: <LAC>, CI: <CI>, BSIC: <BSIC>, Arfcn: <arfcn>,[RxLev: <RxLev>][C1_nc: <C1_nc>, C2_nc: <C2_nc>][GPRS-Parameters:
GPRS_sup: <GPRS_sup>, RAC: <RAC>, SplitPg: <SplitPg>, NCO: <NCO>, NOM:
<NOM>, T3192: <T3192>, Acc_Burst_type: <Acc_Burst_type>, DRX_Timer_Max:<DRX_Timer_Max>, PBCCH: <PBCCH>, Ext_Measure_Order: <Ext_Measure_
Order>,
PSI1_r_per: <PSI1_r_per>, Count_LR: <Count_LR>, Count_HR: <Count_HR>, C_R_
Hyst: <C_R_Hyst>,
C31: <C31>, C32: <C32>, Prior_Acc_Thr: <Prior_Acc_Thr>]
OK
Response syntax for 4G/3G modules (3G RAT):+CGED: RAT:<rat>,
URR:<rrc_state>,
DC:<urrcdc_state>, BP:<urrcbp_state>, M:<urrcm_state>, ERR:<as_error_code>,
RC:<release_cause>, OOS:<out_of_service>, BLER:<meas_bler>,TSIR:<target_sir>,MSIR:<meas_sir>,
HSC:<hierarchical_cell_structure>, HMD:<high_mobility_detected>,
LM:<limited_service>,
Cell-ID:<cell_identity>, DLF:<dl_frequency>, ULF:<ul_frequency>,
SC:<scrambling_code>, RSCP LEV:<rscp lev>, ECN0 LEV:<ecn0_lev>,
C:<ciphering>, D:<ps_data_transfered>, PSM:<power_saving_mode>,[Cell:<cell_type>=AS, SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0
LEV:<ecn0_lev>, DLF:<dl_frequency>][Cell:<cell_type>=VAS, SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0
LEV:<ecn0_lev>, DLF:<dl_frequency>][Cell:<cell_type>=M, SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0
LEV:<ecn0_lev>, DLF:<dl_frequency>][Cell:<cell_type>=D, SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0
LEV:<ecn0_lev>, DLF:<dl_frequency>][Cell:<cell_type>=G, B:<gsm_band>,Arfcn:<arfcn>, RXLEV:<RxLev>, Bsic:<BSIC>,
RV:<ranking_value>][Cell:<cell_type>=U, SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0
LEV:<ecn0_lev>, DLF:<dl_frequency>, RV:<ranking_value>][Cell:<cell_type>=NU, SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0
LEV:<ecn0_lev>, DLF:<dl_frequency>, RS:<ranking_status>][Cell:<cell_type>=NG B:<gsm band>, Arfcn:<arfcn>, RXLEV:<RxLev>,
Bsic:<BSIC>, RS:<ranking_status>]
RR measurement evaluation:
MeasId:<meas_id>, EventId:<event_id>, <par 3>, <par 4>, <par 5>, <par 6>,...,<par N>,
MeasId:<meas_id>, EventId:, <par 3>, <par 4>, <par 5>, <par 6>,..., <par M>, etc...

UBX-13002752 - R67

7 Network service

Page 132 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
MM:
Process:CO, MMs:<mm_state>, MMSs:<mm_service_state>, MSC:<ms_class>,
T:<active_timer_bitmap>
Process:CS, MMs:<mm_state>, MMSs:<mm_service_state>, LUS:<mm_update_status>, T:<active_timer_bitmap>, L:<limited_service>
Process:PS, MMs:<mm_state>, MMSs:<mm_service_state>, LUS:<mm_update_status>, T:<active_timer_bitmap>, L:<limited_service>, GS:<gprs_supported>,
R:<ready_state>
Cell change counters:
CRT:<cell_reselecetion_total>, IRCR:<ir_cell_reselecetion>, AIRCR:<attempted_
ir_cell_reselecetion>,IRHO:<ir_handover>, AIRHO:<attempted_ir_handover>
Equivalent PLMNs:
MCC:<mobile_country_code>, MNC:<mobile_network_code>
Serving PLMN:
MCC:<mobile_country_code>, MNC:<mobile_network_code>, LAC:<location_area_code>, RAC:<routing_area_code>
OK
Response syntax for 4G/3G modules (2G RAT):+CGED: RAT: <rat>,
RR:<grr_state>
SFRLC:<signal_failure/radio_link_counter>, RSR:<reselection_reason>,
RC:<release_cause>, LM:<limited_service>
B:<gsm_band>, Arfcn:<arfcn>, RXLEV:<RxLev>, C1:<C1>, C2:<C2>, Bsic:<BSIC>,
MA:<nr_of_rf_in_ma>,MADed:<dedicated_arfcn>,
GSM: Ci:<CI>, B:<gsm_band>, Arfcn:<arfcn>,RXLEV:<RxLev>, C1:<C1>,
Bsic:<BSIC>
UMTS: SC:<scrambling_code>, RSCP LEV:<rscp_lev>, ECN0 LEV:<ecn0_lev>,
DLF:<dl_frequency>
MM:
Process:CO, MMs:<mm_state>, MMSs:<mm_service_state>, MSC:<ms_class>,
T:<active_timer_bitmap>
Process:CS, MMs:<mm_state>, MMSs:<mm_service_state>, LUS:<location_
update_status>, T:<active_timer_bitmap>, L:<limited_service>
Process:PS, MMs:<mm_state>, MMSs:<mm_service_state>, LUS:<location_
update_status>, T:<active_timer_bitmap>, L:<limited_service>, GS:<gprs_
supported>, R:<ready_state>
Cell change counters:
CRT:<cell_reselecetion_total>, IRCR:<ir_cell_reselection_counter>,
AIRCR:<attempted_ir_cell_reselection>,
IRHO:<ir_handover>, AIRHO:<attempted_ir_handover>
Coding Scheme:
dl_sc:<dl_sc>,ul_sc:<ul_sc>
Equivalent PLMNs:
MCC:<MCC>, MNC:<MNC>
Serving PLMN:
MCC:<MCC>, MNC:<MNC>, LAC:<LAC>, RAC:<RAC>, AcT:<AcT>GPRS-Parameters:
SplitPg:<SplitPg>,NCO:<NCO>,NOM:<NOM>, T3192:<T3192>, Acc_Burst_
type:<Acc_Burst_type>, DRX_Timer_Max:<DRX_Timer_Max>, PBCCH:<PBCCH>,
Ext_Measure_Order:<Ext_Measure_Order>

UBX-13002752 - R67

7 Network service

Page 133 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
PSI1_r_per:<PSI1_r_per>,si13_location: <si13_location>
packet_psi_status:<packet_psi_status>
packet_si_status:<packet_si_status>
ext_upl_tbf_supported:<ext_upl_tbf_supported>
ccn_active:<ccn_active>
pfc_feat_supported:<pfc_feat_supported>
Count_LR:<Count_LR>, Count_HR:<Count_HR>,
C_R_Hyst:<C_R_Hyst>,
C31:<C31>, C32:<C32>, Prior_Acc_Thr:<Prior_Acc_Thr>
OK
Response syntax for 4G modules (4G RAT):+CGED: RAT:<rat>,
MCC:<MCC>, MNC:<MNC>, CellID:<CI>, PhysCellID:<PhysCellID>, TAC:<TAC>,
RSRP:<RSRP>, RSRQ:<RSRQ>, TA:<TA>, TA_type:<TA_type><num_measured_EUTRA> Measured EUTRA neighbour cells:
Neighbour[]: EARFCN:<EARFCN>, PhysCellID:<PhysCellID> RSRP:<RSRP>,
RSRQ:<RSRQ>
OK
Response syntax in machine readable format for 3G modules (2G RAT):+CGED: RAT:"GSM",
S:<MCC>,<MNC>,<LAC>,<CI>,<BSIC>,<arfcn>,<RxLev>,<nr_of_rf_in_ma>,<dedicated_arfcn>,<RxLevFull>,<RxLevSub>,<RxQualFull>,<RxQualSub>,<ciphering>,<ms_txpwr>,<rx_acc_min>,<cbq>,<cba>,<c2_valid>,<cr_offset>,<tmp_offset>,<penalty_t>,<c1>,<c2>,<ch_type>,<ch_mode>,<txpwr>,<dtx_used>,<t3212>,<acc>,<t_adv>,<bs_pa_mfrms>,<dsc>,<rll>
GS:<GPRS_sup>,<RAC>,<SplitPg>,<NCO>,<NOM>,<T3192>,<Acc_Burst_type>,<DRX_Timer_Max>,<PBCCH>,<Ext_Measure_Order>,<PSI1_r_per>,<Count_LR>,<Count_HR>,<C_R_Hyst>,<C31>,<C32>,<Prior_Acc_Thr>[EPLMN<eplmn_index>:<MNC>,<MCC>][N<cell_index>:<LAC>,<CI>,<BSIC>,<arfcn>,<RxLev>,<c1>,<c2>][UN<cell_index>:<scrambling_code>,<rscp_lev>,<ecn0_lev>,<dl_frequency>]
OK
Response syntax in machine readable format for 3G modules (3G RAT):+CGED: RAT:"UMTS",
S:<MCC>,<MNC>,<LAC>,<RAC>,<CI>,<dl_frequency>,<ul_frequency>,<scrambling_code>,<rscp_lev>,<ecn0_lev>,<ciphering>,<ps_data_transfered>,<hierarchical_cell_structure>,<high_mobility_detect>,<limited_service>,<rrc_
state>[EPLMN<eplmn_index>:<MNC>,<MCC>][AS:FFFF,FFFF,FFFF,FFFF,<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>][VAS:FFFF,FFFF,FFFF,FFFF,<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>][M:FFFF,FFFF,FFFF,FFFF,<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>][D:FFFF,FFFF,FFFF,FFFF,<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>][U:FFFF,FFFF,FFFF,FFFF,<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>]

UBX-13002752 - R67

7 Network service

Page 134 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse[NU:FFFF,FFFF,FFFF,FFFF,<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>]
OK
Response syntax in machine readable format for 2G modules:+CGED:
S:<MCC>,<MNC>,<LAC>,<CI>,<BSIC>,<arfcn>,<RxLev>,<nr_of_rf_in_ma>,<dedicated_arfcn>,<RxLevFull>,<RxLevSub>,<RxQualFull>,<RxQualSub>,<ciphering>,<ms_txpwr>,<rx_acc_min>,<cbq>,<cba>,<c2_valid>,<cr_offset>,<tmp_offset>,<penalty_t>,<c1>,<c2>,<ch_type>,<ch_mode>,<txpwr>,<dtx_used>,<t3212>,<acc>,<t_adv>,<bs_pa_mfrms>,<dsc>,<rll>
GS:<GPRS_sup>,<RAC>,<SplitPg>,<NCO>,<NOM>,<T3192>,<Acc_Burst_type>,<DRX_Timer_Max>,<PBCCH>,<Ext_Measure_Order>,<PSI1_r_per>,<Count_LR>,<Count_HR>,<C_R_Hyst>,<C31>,<C32>,<Prior_Acc_Thr>[EPLMN<eplmn_index>:<MNC>,<MCC>][N<cell_index>:<LAC>,<CI>,<BSIC>,<arfcn>,<RxLev>,<c1>,<c2>]

Read

AT+CGED?

OK+CGED: <mode>

Test

AT+CGED=?

OK+CGED: (list of supported <mode>s)OK

7.26.3 Defined values
Parameter<mode>

Type
NumberDescription
Cell environment information mode:• 0 (default value): one shot dump
• 1: periodic refreshed dump; the information for up to 32 neighbour cells is available• 2: stop periodic dump
• 3: one shot serving cell dump
• 4: periodic serving cell refreshed dump
• 5: one shot serving cell and neighbour cells dump
• 6: periodic serving cell and neighbour cells refreshed dump
• 128: one shot dump without the tags
• 129: periodic refreshed dump without the tags
• 130: stop periodic dump (same as 2)• 131: one shot serving cell without the tags
• 132: periodic serving cell refreshed without the tags
• 133: one shot serving cell and neighbour cells without the tags
• 134: periodic serving cell and neighbour cells refreshed without the tags

<details>

Number•<rat>

String

<MCC>
<MNC>
<LAC>
<CI>
<BSIC><arfcn><RxLev><RxLevServ>

NumberNumberNumberNumberNumberNumberNumberNumberUBX-13002752 - R67

0 (default value): it does not display <scrambling_code> (3G RAT) or <physCellID>(4G RAT) if <mode>=3 or <mode>=4 is set• 1: displays <scrambling_code> (3G RAT) or <physCellID> (4G RAT) if <mode>=3 or<mode>=4 is set
Indicates the radio access technology and may be:• "GSM"• "UMTS"• "LTE"
See <MCC>.
See <MNC>.
See <LAC>.
See <CI>.
See <BSIC>.
See <arfcn>.
See <RxLev>.
Received signal level on the cell, range 0 - 63 and 255 (255 is provided if theinformation is not available); see the 3GPP TS 05.08 [25]7 Network service

Page 135 of 1001

u-blox cellular modules - AT commands manual

Parameter<RfChannels>

Type
Number

<Arfcn_ded><RxLevFull>

NumberNumber<RxLevSub>

Number<RxQualFull>

Number<RxQualSub>

Number<ciphering>Number<ms_txpwr>

Number<rx_acc_min>
<cbq>
<cba>
<c2_valid><cr_offset><tmp_offset><penalty_t><c1>, <C1_nc><c2>, <C2_nc><ch_type><ch_mode><txpwr>NumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumber<dtx_used><t3212>

NumberNumber<acc><t_adv><bs_pa_mfrms>

NumberNumberNumber<dsc><rll><grr_state>

NumberNumberNumberUBX-13002752 - R67

Description
Number of frequencies in Mobile Allocation: 0x01 if single RF and 0 if n.a.; see the
3GPP TS 04.18 [36]Single ARFCN of dedicated channel; it is the first ARFCN of Mobile Allocation
Received signal strength on serving cell, measured on all slots; range 0h-3Fh; see the
3GPP TS 04.18 [36]Received signal strength on serving cell, measured on a subset of slots; range 0h3Fh; see the 3GPP TS 04.18 [36]Received signal quality on serving cell, measured on all slots; range 0-7; see the 3GPP
TS 04.18 [36]Received signal quality on serving cell, measured on a subset of slots, range 0-7; see
the 3GPP TS 04.18 [36]
GSM ciphering. Allowed values:
• ON
• OFF
Maximum TX power level an MT may use when accessing the system until otherwisecommanded, range 0 - 31; see the 3GPP TS 04.18 [36]
RXLEV-ACCESS-MIN, range 0 - 63; see the 3GPP TS 04.18 [36]
CELL_BAR_QUALIFY, range 0 - 1; see the 3GPP TS 05.08 [25]
CELL_BAR_ACCESS, range 0 - 1; see the 3GPP TS 05.08 [25]True if all parameter for calculation of c2 are available; range 0 - 1
CELL_RESELECT_OFFSET, range 0 - 63 (6 bits); see the 3GPP TS 04.18 [36]TEMPORARY_OFFSET, range 0 - 7; see the 3GPP TS 04.18 [36]Penalty time, range 0 - 31; see the 3GPP TS 04.18 [36]Value of c1; see the 3GPP TS 05.08 [25]Value of c2; see the 3GPP TS 05.08 [25]See <ch_type>.
See <ch_mode>.
Transmit power level of the current connection, range 0-31 or 255 if the module is notconnected; see the 3GPP TS 04.18 [36]DTX used, range 0 - 1; see the 3GPP TS 04.18 [36]T3212. The T3212 timeout value field is coded as the binary representation of thetimeout value for periodic updating in decihours; range 0-255 (8 bits); see the 3GPP
TS 04.18 [36]Access control class (RACH Control Parameters); see the 3GPP TS 04.18 [36]See <t_adv>.
BS_PA_MFRMS (multiframes period for transmission of PAGING REQUEST), range 0- 7 mapped to 2-9; see the 3GPP TS 05.02 [38]Downlink Signalling Counter
Radio Link Loss Counter
RR state. Allowed values:• 0: GRR_UNDEFINED• 1: GRR_START• 2: GRR_CELL_SELECTION• 3: GRR_WAIT_CELL_SELECTION• 4: GRR_DEACT_CELL_SELECTION• 5: GRR_SELECT_ANY_CELL• 6: GRR_WAIT_SELECT_ANY_CELL• 7: GRR_DEACT_SELECT_ANY_CELL• 8: GRR_WAIT_INACTIVE• 9: GRR_INACTIVE• 10: GRR_IDLE• 11: GRR_PLMN_SEARCH• 12: GRR_CELL_RESELECTION• 13: GRR_WAIT_CELL_RESELECTION• 14: GRR_DEACT_PLMN_SEARCH• 15: GRR_CELL_CHANGE• 16: GRR_CS_CELL_CHANGE• 17: GRR_WAIT_CELL_CHANGE

7 Network service

Page 136 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 18: GRR_SINGLE_BLOCK_ASSIGN• 19: GRR_DOWNL_TBF_EST• 20: GRR_UPL_TBF_EST• 21: GRR_WAIT_TBF• 22: GRR_TRANSFER• 23: GRR_WAIT_SYNC• 24: GRR_DTM_ENH_CALL_EST• 25: GRR_DTM• 26: GRR_DTM_ENH_MO_CAL_EST• 27: GRR_MO_CON_EST• 28: GRR_MT_CON_EST• 29: GRR_RR_CONNECTION• 30: GRR_DTM_REL• 31: GRR_CALL_REESTABLISH• 32: GRR_DEACT_CALL_REESTABLISH• 33: GRR_NORMAL_CHN_REL• 34: GRR_LOCAL_CHN_REL• 35: GRR_WAIT_IDLE• 36: GRR_DEACTIVATION• 37: GRR_ENH_DTM_CS_CALL_EST• 38: GRR_IR_CELL_RESEL_TO_UTRAN• 39: GRR_DTM_ENH_CS_CALL_EST• 40: GRR_IR_ACTIVE_ON_HOLD• 41: GRR_IR_RESEL_ABORT• 42: GRR_IR_WAIT_INTER_RAT• 43: GRR_IR_WAIT_FOR_RSRCParameter<GPRS_sup><RAC><SplitPg>

Type
NumberNumberNumber<NCO>

Number<NOM>

Number

<T3192>

Number<Acc_Burst_type>

Number<DRX_Timer_Max><PBCCH><Ext_Measure_
Order><PSI1_r_per>

NumberNumberNumberDescription
GPRS supported (in serving cell); range 0 - 1; see the 3GPP TS 04.18 [36]See <RAC>.
SPGC_CCCH_SUP split pg_cycle on ccch by network, range 0 - 1 (2 bits); see the 3GPP
TS 04.18 [36]NETWORK_CONTROL_ORDER (GPRS_Cell_Options), range 0 - 3 (2 bits); see the
3GPP TS 04.18 [36]NETWORK OPERATION MODE (GPRS_Cell_Options), range 0 - 3 (2 bits); see the
3GPP TS 04.18 [36]T3192 (Wait for Release of the TBF after reception of the final block), range 0 - 7
mapped to 0-1500 msec (3 bits); see the 3GPP TS 04.60 [37]:• 0: 500 ms• 1: 1000 ms• 2: 1500 ms• 3: 0 ms• 4: 80 ms• 5: 120 ms• 6: 160 ms• 7: 200 ms
ACCESS_BURST_TYPE, range 0 - 1 (mapped to 8-bits format,11-bit format); see the
3GPP TS 04.60 [37]
DRX_TIMER_MAX, range 0 - 7 (3 bits); see the 3GPP TS 04.60 [37]
PBCCH present, range 0 - 1
EXT_MEASUREMENT_ORDER, range 0 - 3 (2 bits); see the 3GPP TS 04.60 [37]<Count_LR><Count_HR><C_R_Hyst>

NumberNumberNumberGPRS parameters:

UBX-13002752 - R67

Number

PSI1_REPEAT_PERIOD, range 0 - 15 mapped to 1-16 (4 bits); see the 3GPP TS 04.60[37]
PSI_COUNT_LR, range 0 - 63 (6 bits); see the 3GPP TS 04.60 [37]
PSI_COUNT_HR, range 0 - 15 mapped to 1-16 (4 bits); see the 3GPP TS 04.60 [37]
CELL_RESELECT_HYSTERESIS, range 0 - 7 (3 bits); see the 3GPP TS 04.60 [37]7 Network service

Page 137 of 1001

u-blox cellular modules - AT commands manual

Parameter
<C31>
<C32>
<Prior_Acc_Thr>

Type
NumberNumberNumberDescription
Value of c31, number; see the 3GPP TS 05.08 [25]Value of c32, number; see the 3GPP TS 05.08 [25]PRIORITY_ACCESS_THR, range 0-7 (3 bits); see the 3GPP TS 04.18 [36]Parameter<rrc_state><urrcdc_state><urrcbp_state><urrcm_state><as_error_code>

Type
StringNumberNumberNumberNumber<release_cause><out_of_service>

NumberNumber<meas_bler>

Number<target_sir>

Number<meas_sir>

Number<hierarchical_cell_structure>

Number<high_mobility_
detect>Number<cell_identity><dl_frequency><ul_frequency><ciphering>NumberNumberNumberString<ps_data_transfered>

Number<power_saving_mode>

Number<cell_type>

String<scrambling_code><rscp_lev>

NumberNumberDescription
See <rrc_state>.
Three hexadecimal digits (octet 1, 2: event, 3: state). For debug purposes only.
Four hexadecimal digits (octet 1, 2: event, 3, 4: state). For debug purposes only.
Three hexadecimal digits (octet 1, 2: event, 3: state). For debug purposes only.
Indicates if an AS error occurred. Allowed values:• 0: no error• 81: UMAC, no TFCI (Transport Format Code identifier) found• 82: UMAC, RLC timing error
MM RR release cause. For debug purposes only
Service state:• 0: service present• 1: out of service
Measured BLER (Block Error Rate). Allowed values:• Range: 0.000001 to 0.99
• If out of range: Targeted SIR (Signal to Interference Ratio). Allowed values:• Range: -10 to 20• If out of range: Measured SIR (Signal to Interference Ratio). Allowed values:• Range: -10 to 20• If out of range: HCS (Hierarchical Cell Structure):• 0: not used
• 1: usedHigh mobility:• 0: not detected• 1: detected
Cell identity (eight hex digits)
See <dl_frequency>.
See <ul_frequency>.
Ciphering:• 1: enabled• 2: disabled
PS data:• 0: transferred• 1: not transferredPower saving:• 0: disabled• 1: enabled
Cell type:• "AS": Active Set• "VAS": Virtual Active Set• "M": Monitored Cells• "D": Detected Cells• "G": GSM cells• "U": UMTS cells• "NU": Non Ranked UMTS cells• "NG": Non Ranked GSM cells
See <scrambling_code>.
See <rscp_lev>.

UMTS parameters:

UBX-13002752 - R67

7 Network service

Page 138 of 1001

u-blox cellular modules - AT commands manual

Parameter<ecn0_lev><gsm_band>

Type
NumberString<ranking_value><ranking_status>

NumberNumber<meas_id><event_id><par 3,4,5..,M,..,N><signal_failure/radio_link_counter><reselection_
reason>NumberNumberNumberNumber<dl_sc>/<ul_sc>

NumberNumberDescription
See <ecn0_lev>.
GSM band:• "D": 1800 MHz• "P": 1900 MHz• "G": 900 MHz
Cell's ranking value
Ranking status for Non Ranked UMTS cells. Allowed values:• 0: EM_CELL_SUITABLE• 1: EM_NOT_MEASURED• 2: EM_CELL_BARRED• 3: EM_WRONG_PLMN• 4: EM_HCS_CRITERIA_PRIO• 5: EM_HCS_H_VALUE• 6: EM_S_VALUE
RR measurement ID (one hex digit). For debug purpose only
Event ID (two hex digits). For debug purpose only
Range 0-99
Range 0-99. For debug purpose only
Indicates the reason for cell reselection. Allowed values:• 0: RESEL_PLMN_CHANGE• 1: RESEL_SERV_CELL_NOT_SUITABLE• 2: RESEL_BETTER_C2_C32• 3: RESEL_DOWNLINK_FAIL• 4: RESEL_RA_FAILURE• 5: RESEL_SI_RECEIPT_FAILURE• 6: RESEL_C1_LESS_NULL• 7: RESEL_CALL_REEST_TIMEOUT• 8: RESEL_ABNORMAL_RESEL• 9: RESEL_CELL_CHANGE_ORDER• 10: RESEL_NOT_OCCURRED
Current burst configuration and Coding Scheme of downlink (<dl_sc>) or uplink (<ul_sc>) TBF may be:• "NB_CS_1"• "NB_CS_2"• "NB_CS_3"• "NB_CS_4"• "NB_MCS_1"• "NB_MCS_2"• "NB_MCS_3"• "NB_MCS_4"• "NB_MCS_5"• "NB_MCS_6"• "NB_MCS_7"• "NB_MCS_8"• "NB_MCS_9"• "NB_MCS_5_7"• "NB_MCS_6_9"• "AB_8"• "AB_11"• "AB_11_E"• if none of the previous ""UMTS/GSM MM parameters:
ParameterType<mm_state>
Number<mm_service_state> Number

UBX-13002752 - R67

Description
MM state. For debug purpose only. Range 1 - 16
MM service state. For debug purpose only. Range 1 - 10.

7 Network service

Page 139 of 1001

u-blox cellular modules - AT commands manual

Parameter<mm_update_status>Type
Number<ms_class>

String<limited_service>

Number<ready_state>

Number<active_timer_
bitmap>NumberDescription
Location update status. For debug purpose only. Allowed values:• 1: updated (MMST_U1_UPDATED)• 2: not updated (MMST_U2_NOT_UPDATED)• 3: roaming not allowed (MMST_U3_ROAMING_NOT_ALLOWED)MS GPRS-class. Allowed values:• 0: class A• 1: class B• 2: class C• 3: class CG: class C in GPRS only mode
• 4: class CC: class C in circuit switched only mode (lowest class)
Limited service information. Allowed values:• 0: no limited service• 1: limited Service
MM READY state. Allowed values:• 0: not in ready state• 1: in ready state
Bitmap of the active MM timers: T3302, T3310, T3311, T3312, T3314, T3321, T3330.
T3302 is the least significant bit and T3330 the most significant bit

Number

The bitmap values are presented in hexadecimal format (the range goes from 0x000
0 to 0x007F)
Total number of cell reselections. Range 0 - 65535.

NumberNumber of inter-rat cell reselections. Range 0 - 65535.

NumberNumber of attempts of inter-rat cell reselections. Range 0 - 65535.

NumberNumberNumber of inter-rat handovers. Range 0 - 65535.
Number of attempts of inter-rat handovers. Range 0 - 65535.

NumberNumber

Progressive index of displayed EPLMN. Range 1 - 16.
Progressive index of displayed cell. Range 1 - 32.

Parameter<PhysCellID><TAC><RSRP><RSRQ><TA><TA_type>

Type
NumberNumberNumberNumberNumberNumber<EARFCN><num_measured_
EUTRA>

NumberNumberDescription
See <PhysCellID>.
See <TAC>.
See <RSRP>.
See <RSRQ>.
See <TA>.
The indication of RRC STATE when TA updated, allowed values:• 0: indicating no timing advance available• 1: indicating the RRC STATE in RRC_IDLE• 2: indicating the RRC STATE in RRC_CONNECTED
See <EARFCN>.
Number of E-UTRA neighbor cell measurements; valid range: 0 - 32.

<cell_reselection_
total><ir_cell_reselection_
counter><attempted_ir_cell_
reselction><ir_handover><attempted_ir_
handover><eplmn_index><cell_index>

LTE parameters:

7.26.4 Notes
LARA-R2 / TOBY-R2• <mode>=5, 6, 133 and 134 are not supported.
SARA-U2 / LISA-U2 / LISA-U1• <mode>=5, 6, 133 and 134 are not supported.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270• <mode>=128, 129, 130, 131, 132, 133 and 134 are not supported.

UBX-13002752 - R67

7 Network service

Page 140 of 1001

u-blox cellular modules - AT commands manual•

The <details> parameter is not supported.

LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270• The SIM verification is needed.
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S• The set command can be issued when the module is not registered to the network.
LISA-U1• <mode>=128, 129, 130, 131, 132, 133 and 134 are not supported.
• The <details> parameter is not supported.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S• <mode>=128, 129, 130, 131, 132, 133 and 134 are not supported.
SARA-G3 / LEON-G1• The <details> and <rat> parameters are not supported.
• The <Arfcn_ded> parameter can assume also the value "INVALID_ARFCN".
SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G100-06S• <mode>=128, 129, 130, 131, 132, 133 and 134 are not supported.

7.27 Neighbour cells configuration +UDCONF=83+UDCONF=83
Modules
Attributes

SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

7.27.1 Description
Configures the number of neighbour cells which information will be reported in the information text responseof the AT+CGED=0 / AT+CGED=1 / AT+CGED=5 / AT+CGED=6 / AT+CGED=128 AT+CGED=129 / AT+CGED=
133 / AT+CGED=134 set command.

7.27.2 Syntax
Type
Set

SyntaxAT+UDCONF=83,<max_2g_ncells>

Response
OK

ExampleAT+UDCONF=83,6

Read

AT+UDCONF=83+UDCONF: 83,<max_2g_ncells>

OK+UDCONF: 83,6OKOK

7.27.3 Defined values
Parameter<max_2g_ncells>

Type
NumberDescription
Indicates the number of neighbour cells to be reported.
The range goes from 0 to 32. The default value is 32. In the dedicated-mode the<max_2g_ncells> setting will be limited to 6 cells.

7.28 Channel and network environment description +UCGED+UCGED
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.28.1 Description
Enables the protocol stack and network environment information collection.

UBX-13002752 - R67

7 Network service

Page 141 of 1001

u-blox cellular modules - AT commands manual

The information text response of the read command reports only the current RAT (if any) parameters,
determined by the <rat> parameter value.
Table 6 lists the supported <mode> parameter values:
Modules<mode>=0
TOBY-L2*
MPCI-L2*
TOBY-L200-00S /*TOBY-L210-00S
MPCI-L200-00S / MPCI-L210-00S *<mode>=2***<mode>=3**<mode>=5*

Table 6: <mode> parameter applicability<tti_bundling> is supported only by these products:
TOBY-L210-62S;TOBY-L210-65S;

7.28.2 Syntax
Type
Set

SyntaxAT+UCGED=<mode>

Response[+UCGED: <svc>

ExampleAT+UCGED=2<arfcn>,<Gmcc>,<Gmnc>,<GcellId>, OK<BSIC>,<RxLev>
AT+UCGED=3<uarfcn>,<Wband>,<Wmcc>,+UCGED: 0<Wmnc>,<WcellId>,<Wrrc>,<rssi>,
65535,fff,fff,0000,ff,99<ecn0_lev>
10588,1,222,88,1281d24,255,11,40<EARFCN>,<Lband>,<ul_BW>,

Read

AT+UCGED?

<dl_BW>,<Lmcc>,<Lmnc>,<TAC>, 65535,255,255,255,fff,fff,ffff,0000<LcellId>,<P-CID>,<RSRP>,<RSRQ>, 000,65535,255,255,255,255<Lsinr>,<Lrrc>]
OKOK<mode>= 0:+UCGED: 0+UCGED: 0

OK

OK<mode>= 2, <rat>= 2:+UCGED: 2+UCGED: 2

2,4,001,01

2,<svc>,<MCC>,<MNC>

810,1,0000,01,0000,80,63,255,255,
255<arfcn>,<band1900>,<GcellId>,<BSIC>,<Glac>,<Grac>,<RxLev>,<grr>,<t_adv>,<Gspeech_mode>

OKOK<mode>= 2, <rat>= 3:+UCGED: 2+UCGED: 2

3,4,001,01

3,<svc>,<MCC>,<MNC>

4400,5,0000000,0000,80,9,4,62,42,
255<uarfcn>,<Wband>,<WcellId>,<Wlac>,<Wrac>,<scrambling_code>,<Wrrc>,<rssi>,<ecn0_lev>,<Wspeech_mode>

OKOK<mode>= 2, <rat>= 4:+UCGED: 2+UCGED: 2

4,0,001,01

4,<svc>,<MCC>,<MNC>

2525,5,25,50,2b67,69f6bc7,111,0000
0000,ffff,ff,67,19,0.00,255,255,255,<EARFCN>,<Lband>,<ul_BW>,<dl_
67,11,255,0,255,255,0,0
BW>,<TAC>,<LcellId>,<P-CID>,<mTmsi>,<mmeGrId>,<mmeCode>, OK

UBX-13002752 - R67

7 Network service

Page 142 of 1001

u-blox cellular modules - AT commands manual

Type

Test

SyntaxResponse<RSRP>,<RSRQ>,<Lsinr>,<Lrrc>,<RI>,<CQI>,<avg_rsrp>,<totalPuschPwr>,<avgPucchPwr>,<drx>, <l2w>,<volte_mode>[,<meas_gap>,<tti_bundling>]

AT+UCGED=?

ExampleOK<mode>= 2, <rat>= 5:+UCGED: 2+UCGED: 2

5,15,<svc>OK

OK+UCGED: (list of supported<mode>s)+UCGED: (0,2)
OKOK

7.28.3 Defined values
Parameter<mode>

Type
Number<rat>

Number<svc>

Number<MCC><MNC><arfcn><band1900>

NumberNumberNumberNumber<GcellId><BSIC><Glac>

NumberNumberNumber<Grac>

Number<RxLev><grr><t_adv><Gspeech_mode>

NumberNumberNumberNumberUBX-13002752 - R67

Description• 0: reporting disabled• 2: short form reporting enabled• 3: retrieve the short form text information report• 5: RSRP and RSRQ reporting enabled
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
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.
See <MCC>.
See <MNC>.
See <arfcn>.
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
GERAN Cell Identifier (CI) in hexadecimal format; the range is 0h-FFFFh (2 octets).
See <BSIC>.
Two bytes location area of the GERAN cell in hexadecimal format; FFFF if not known
or not detectable.
One byte routing area of the GERAN cell in hexadecimal format; FF if not known or notdetectable.
See <RxLev>.
Reserved for future use.
Reserved for future use.
Reports the latest obtained value of the GSM speech code. Allowed values:

7 Network service

Page 143 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 0: GSM Enhanced Full Rate (12.2 kb/s)• 1: GSM Full Rate (13.0 kb/s)• 2: GSM Half Rate (5.6 kb/s)• 3..10: AMR NB FR (from 4.75 kb/s to 12.2 kb/s) the value indicates the first codec
type chosen from the DUT; see the corresponding value of <Wspeech_mode>parameter for the baud rate mapping• 3..8: AMR NB HR (from 4.75 kb/s to 7.95 kb/s) the value indicates the first codec typechosen from the DUT; see the corresponding value of <Wspeech_mode> parameterfor the baud rate mapping• 11..13: AMR WB FR (from 6.60 kb/s to 12.65 kb/s) the value indicates the first
codec type chosen from the DUT; see the corresponding value of <Wspeech_mode>parameter for the baud rate mapping• 255: not known or not detectable
See 3GPP TS 26.201 [91] for more details on GSM codecs used during a voice call<uarfcn>

Number<Wband>Number<WcellId>

Number

<Wlac>

Number<Wrac>

Number<scrambling_code><Wrrc>

NumberNumber<rssi>

Number<ecn0_lev><Wspeech_mode>

NumberNumberUBX-13002752 - R67

In case a set of speech codecs is assigned by the network, then the parameter
reports the lowest one and this one is not necessary the one used.
UTRAN Absolute Radio Frequency Channel Number (UARFCN); the range is 1537-10
838, 65535 if not known or not detectable.
UTRAN band:• 1: band 1 (2 GHz)
• 2: band 2 (1900 MHz)• 4: band 4 (2100 MHz)• 5: band 5 (800 MHz)• 8: band 8 (900 MHz)• 255: not known or not detectable
UTRAN CI (cell identifier) in hexadecimal format; the range is 0h-FFFFFFFh (28 bits),
0000000 if not known or not detectable.
Two bytes location area of the UTRAN cell in hexadecimal format; FFFF if not known
or not detectable.
One byte routing area of the GERAN cell in hexadecimal format; FF if not known or notdetectable.
See <scrambling_code>.
3G RRC state:• 0: idle• 1: URA_PCH• 2: CELL_PCH• 3: CELL_FACH• 4: CELL_DCH• 255: not known or not detectable
UTRAN cell Received Signal Strength Indicator as defined in 3GPP TS 25.133 [84]:• 0: less than -100 dBm• 1..75: from -100 to -25 dBm with 1 dBm steps• 76: -25 dBm or greater• 255: not known or not detectable
See <ecn0_lev>.
Reports the latest obtained value of the UMTS speech code. Allowed values:• 3: AMR NB (4.75 kb/s)• 4: AMR NB (5.15 kb/s)• 5: AMR NB (5.90 kb/s)• 6: AMR NB (6.70 kb/s)• 7: AMR NB (7.40 kb/s)• 8: AMR NB (7.95 kb/s)• 9: AMR NB (10.2 kb/s)• 10: AMR NB (12.2 kb/s)• 11: AMR WB (6.60 kb/s)• 12: AMR WB (8.85 kb/s)• 13: AMR WB (12.65 kb/s)• 14: AMR WB (14.25 kb/s)

7 Network service

Page 144 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 15: AMR WB (15.85 kb/s)• 16: AMR WB (18.25 kb/s)• 17: AMR WB (19.85 kb/s)• 18: AMR WB (23.05 kb/s)• 19: AMR WB (23.85 kb/s)• 255: not known or not detectable
See 3GPP TS 26.201 [91] for more details on UMTS codecs used during a voice call.

<EARFCN><Lband><ul_BW>

NumberNumberNumber<dl_BW>

Number<TAC><LcellId><mTmsi>NumberNumberNumber<mmeGrId>

Number<RSRP><RSRQ><mmeCode><Lsinr>NumberNumberNumberNumber

<Lrrc>

Number<RI>

Number<CQI>

Number<avg_rsrp><totalPuschPwr>

NumberNumber

<avgPucchPwr>

Number<drx>

Number<l2w>

Number<volte_mode><meas_gap>

NumberNumberUBX-13002752 - R67

In case a set of speech codecs is assigned by the network, then the parameter
reports the lowest one and this one is not necessary the one used.
See <EARFCN>.
See <Lband>.
Number of Uplink Resource Blocks (see 3GPP TS 36.101 Table 5.6-1 [78]), 255 if not
known or not detectable.
Number of Downlink Resource Blocks (see 3GPP TS 36.101 Table 5.6-1 [78]), 255 if not
known or not detectable.
See <TAC>.
See <LcellId>.
4 bytes MME Temporary Mobile Subscriber Identity in hexadecimal format; 0000000
0 if not known or not detectable.
2 bytes MME Group Identifier in hexadecimal format; FFFF if not known or notdetectable.
See <RSRP>.
See <RSRQ>.
1 byte MME Code in hexadecimal format; FF if not known or not detectable.
E-UTRAN Signal to Interference and Noise ratio in dB.
• TOBY-L2 / MPCI-L2 - The range goes from -15,88 to 15,88; 255 if not known or notdetectable.
4G 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
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 [107] section 7.2 and 3GPP TS 36.212 [108] section
5.2.2.6 for more details.
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 [107] section 7.2 for more details.
Average value of last 10th Reference Signal Received Power (RSRP).
Mobile output power for PUSCH transmission averaged over 480 ms in dBm; 255 if
not known or not detectable.
Mobile output power for PUCCH transmission averaged over 480 ms in dBm; 255 if
not known or not detectable.
Discontinuous Reception "drx-Inactivity-Timer" value in ms; 0 if not known or notdetectable.
SIB3 LTE to WCDMA reselection criteria: (threshServingLow)x2 +(q-RxLevMin)x2;
255 if not known or not detectable.
Reserved for future use.
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 [83])7 Network service

Page 145 of 1001

u-blox cellular modules - AT commands manual

ParameterType<tti_bundling>

Number<NBMsinr>

Number<esm_cause><emm_state>

NumberNumber<tx_pwr><drx_cycle_len><tmsi><P-CID>

NumberNumberStringNumber<RSRP_value>

String<RSRQ_value>

StringDescription• 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 [83])TTi (Transmission Time interval) bundling status:• 0: off• 1: on
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 value as defined in 3GPP TS 24.301 [68]
EMM state value as defined in 3GPP TS 24.301 [68]. 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 power value in 1/10 dBm if device is in traffic, 255 otherwise
Idle DRX cycle length in 10 ms radio-frame units
TMSI in hexadecimal format, with most significant byte first
E-UTRAN cell Physical Cell ID; the range is 0-503, 65535 if not known or notdetectable.
Current Reference Signal Received Power (RSRP) expressed in dBm, the range goesfrom "-140.00" dBm to "-44.00" dBm.
Current Reference Signal Received Quality (RSRQ) expressed in dB, the range goesfrom "-20.00" dB to "-3.00" dB.

7.28.4 Notes
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S / MPCI-L200-03S / MPCI-L210-02S /MPCI-L210-03S / MPCI-L220 / MPCI-L280• <meas_gap> and <tti_bundling> parameters are not supported.
• In order to report the speech codec value the AT+UCGED=2 command must be issued before starting avoice call and the audio codec enabling to the UE. To cater also for MT calls, AT+UCGED=2 should be set
at the module boot or after the network registration.
TOBY-L210-62S / TOBY-L210-65S• In order to report the speech codec value the AT+UCGED=2 command must be issued before starting avoice call and the audio codec enabling to the UE. To cater also for MT calls, AT+UCGED=2 should be set
at the module boot or after the network registration.
TOBY-L201 / MPCI-L201• The values provided by the <Gspeech_mode> and <Wspeech_mode> parameters must not be
considered.
• <meas_gap> and <tti_bundling> parameters are not supported.
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L210-00S /MPCI-L210-60S / MPCI-L210-63S• The command is supported with partial functionality and a limited range for testing purposes only.
• The read command syntax not compatible.
• <mode>=3 is allowed only if short form reporting is enabled, i.e. <mode>=2 previously set.
• <meas_gap> and <tti_bundling> parameters are not supported.
TOBY-L220-62S / MPCI-L220-62S• <meas_gap>=2, 3 are not supported.

UBX-13002752 - R67

7 Network service

Page 146 of 1001

u-blox cellular modules - AT commands manual

7.29 Provide cell information +UCELLINFO+UCELLINFOModules
Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time
<5s

Error reference+CME Error

7.29.1 Description
Provides diagnostic information on the GSM, UMTS or LTE serving cell and on the neighbour cells. This
information can be retrieved in two ways:••

Periodic reporting: it is started by enabling URC reporting with the set command; if the module is camped on
a PLMN (regardless of its registration status), URCs periodically convey the main attributes of the serving
cell and of the neighbour cells.
One-shot query: it is triggered by issuing the read command.

7.29.2 Syntax
Type
Set

SyntaxAT+UCELLINFO=<mode>[,<timer_value>]

Response
OK

ExampleAT+UCELLINFO=1

Read

AT+UCELLINFO?

2G cells:

OK+UCELLINFO: 0,0,222,1,D5BD,5265,
36,1,255,255+UCELLINFO: <mode>,<type>,<MCC>,<MNC>,<LAC>,<CI>,
OK<RxLev>[,<t_adv>[,<ch_type>,<ch_mode>]]
OK
3G cells:+UCELLINFO: 0,2,222,1,EF8D,
52D2388,49,10638,16,38,"ID"+UCELLINFO: <mode>,<type>,<MCC>,<MNC>,<LAC>,<CI>,
OK<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>[,<rrc_state>]OK
4G serving cell:+UCELLINFO: 0,5,222,1,179291197,
121,15011,26,18,0+UCELLINFO: <mode>,<type>,<MCC>,<MNC>,<CI>,<PhysCellID>, OK<TAC>,<RSRP>,<RSRQ>,<TA>OK
4G neighbour cells:+UCELLINFO: <mode>,<type>,<EARFCN>,<PhysCellID>,<RSRP>,<RSRQ>
Test

AT+UCELLINFO=?

URCOK+UCELLINFO: (list of supported<mode>s)OK
2G cells:+UCELLINFO: 1,6,6400,200,27,18
OK+UCELLINFO: (0-1)
OK+UCELLINFO: 1,1,222,1,D5BD,5266,
22+UCELLINFO: <mode>,<type>,<MCC>,<MNC>,<LAC>,<CI>,<RxLev>[,<t_adv>[,<ch_type>,<ch_mode>]]
3G cells:+UCELLINFO: 1,2,222,1,EF8D,
52D2388,49,10638,18,35,"ID"+UCELLINFO: <mode>,<type>,<MCC>,<MNC>,<LAC>,<CI>,<scrambling_code>,<dl_frequency>,<rscp_lev>,<ecn0_lev>[,<rrc_state>]

UBX-13002752 - R67

7 Network service

Page 147 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
4G serving cell:

Example+UCELLINFO: 1,5,222,1,179291197,
121,15011,26,18,0+UCELLINFO: <mode>,<type>,<MCC>,<MNC>,<CI>,<PhysCellID>,<TAC>,<RSRP>,<RSRQ>,<TA>
4G neighbour cells:+UCELLINFO: 1,6,6400,200,27,18+UCELLINFO: <mode>,<type>,<EARFCN>,<PhysCellID>,<RSRP>,<RSRQ>

7.29.3 Defined values
Parameter<mode>

Type
Number<timer_value>

Number<type>

NumberDescription
Allowed values:• 0: periodic reporting disabled• 1: periodic reporting enabled• 2: configure the URC periodic reporting interval
Periodic URC reporting interval. The range goes from 1 s to 65535 s, the default value
is 5 s. This parameter is accepted only if <mode>=2. When modified, the new periodic
URC reporting interval value is applied runtime.
For 2G cells:• 0: 2G serving cell
• 1: neighbour 2G cell
For 3G cells:• 2: 3G serving cell or cell belonging to the Active Set• 3: neighbour 3G cell
• 4: detected 3G cell

<MCC>
<MNC>
<LAC>
<CI>
<RxLev><t_adv><ch_type><ch_mode><scrambling_code><dl_frequency><rscp_lev><ecn0_lev><rrc_state><EARFCN><PhysCellID><TAC><RSRP><RSRQ><TA>

NumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberNumberStringNumberNumberNumberNumberNumberNumberFor 4G cells:• 5: 4G serving cell
• 6: neighbour 4G cellSee <MCC>.
See <MNC>.
See <LAC>.
See <CI>.
See <RxLev>.
See <t_adv>.
See <ch_type>.
See <ch_mode>.
See <scrambling_code>.
See <dl_frequency>.
See <rscp_lev>.
See <ecn0_lev>.
See <rrc_state>.
See <EARFCN>.
See <PhysCellID>.
See <TAC>.
See <RSRP>.
See <RSRQ>.
See <TA>.

7.29.4 Notes
If the MT is 3G registered with an active radio connection (CELL_DCH):• <MCC>, <MNC>, <LAC> and <CI> will be always invalid for 3G cells belonging to Active Set or Detected
Set.
• The 3G serving cell data could be outdated. Use the Active Set data for any information regarding involved
cells in the current radio connection.

UBX-13002752 - R67

7 Network service

Page 148 of 1001

u-blox cellular modules - AT commands manual

LARA-R2 / TOBY-R2• <mode>=2 (configure the URC periodic reporting interval) is not supported.
SARA-U2 / LISA-U2 / LISA-U1• <mode>=2 (configure the URC periodic reporting interval) is not supported.
• The parameters <EARFCN>, <PhysCellID>, <TAC>, <RSRP>, <RSRQ>, <TA> are not supported.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270 / LISA-U1• The parameters <ch_type>, <ch_mode>, <rrc_state> are not supported.

7.30 Lock on a specific cell +UCELLLOCK+UCELLLOCK
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SARA-G340 SARA-G350 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

7.30.1 Description
Forces the module to lock on a:• A specific GSM cell only (identified by its BCCH ARFCN)• A specific UMTS cell only (identified by its UARFCN and PSC)
• A specific GSM or a specific UMTS cell
• A specific LTE cell only (identified by its EARFCN and P-CID)• A specific GSM or a specific UTMS or a specific LTE cell
• A specific GSM or a specific LTE cell
• A specific UMTS or a specific LTE cell
The feature can work in idle-mode only (basic lock: the reselections are inhibited) and in both idle andconnected-mode (extended lock: both the reselections and the handovers are inhibited).
Based on the specified cell(s):•••GSM only (set the module in 2G RAT with AT+URAT=0): the user only sets the ARFCN and the module
enters a GSM only mode:o If any lock is set, the reselections are inhibited in idle-mode and if the specific BCCH ARFCN is notavailable, the module enters the Out Of Coverage (OOC) stateo If the extended lock mode is set, the handovers are inhibited in connected-modeo Extended redirection lock mode is equivalent to the extended lock mode
UMTS only (set the module in 3G RAT with AT+URAT=2): the user only sets the UARFCN+PSC pair and themodule enters a UMTS only mode. The reselections are inhibited and if the specific UARFCN and PSC are
not available, the module enters the OOC stateo In the normal lock mode the UE can leave the locked cell due to the handovers and the radio
reconfiguration by the networko In the extended lock mode, the handovers are inhibited. The reconfiguration via redirection IEs is stillallowedo In extended redirection lock mode any reconfiguration via redirection IEs (see 3GPP TS 25.331 [77]) is
rejected or ignored
LTE only (set the module in 4G RAT with AT+URAT=3): the user only sets the EUARFCN+P-CID pair and themodule enters a LTE only mode. The reselections are inhibited and if the specific EARFCN and P-CID are
not available, the module enters the OOC state.

UBX-13002752 - R67

7 Network service

Page 149 of 1001

u-blox cellular modules - AT commands manual

•

•

•

•

o In normal lock mode, the UE can leave the locked cell due to the handovers and the radio reconfigurationby the networko In extended lock mode, the handovers are inhibited. The reconfiguration via redirection IEs is still allowedo In extended redirection lock mode, any reconfiguration via redirection IEs is rejected or ignored
GSM and UMTS (set the module in the automatic 2G/3G RAT with AT+URAT=1,2 or AT+URAT=1,0): theuser sets both the ARFCN and the UARFCN, PSC pair to make the module enter dual mode. The modulesearches for any of the two locking cells and camps on the first cell found. Reselections in idle mode areallowed to the other locking cell only. In connected mode:o In normal lock mode, the UE can leave the locked cells due to the handovers and the radio reconfigurationby the network. The Ue cannot leave its RATso In extended lock mode, the handovers are inhibited. The reconfiguration via redirection IEs is still allowedo In extended redirection lock mode, any reconfiguration via redirection IEs is rejected or ignored
GSM and LTE (set the module in automatic 2G/4G RAT with AT+URAT=5,3 or AT+URAT=5,0): the user sets
both the ARFCN and the EARFCN, P-CID pair to make the module enter dual mode. The module searches
for any of the two locking cells and camps on the first cell found. Reselections in idle mode are allowed tothe other locking cell only. In connected mode the behaviour is the same of the GSM and UMTS case
UMTS and LTE (set the module in automatic 3G/4G RAT with AT+URAT=6,2 or AT+URAT=6,3): the user
sets both the UARFCN,PSC and the EARFCN, P-CID pairs to make the module enter dual mode. The modulesearches for any of the two locking cells and camps on the first cell found. Reselections in idle mode areallowed to the other locking cell only. In connected mode the behaviour is the same of the GSM and UMTS
case
GSM, UMTS and LTE (set the module in automatic 2G/3G/4G RAT with AT+URAT=4,1 or AT+URAT=4,2 or
AT+URAT=4,3): the user sets the ARFCN, the UARFCN and PSC, the EARFCN and the P-CID pair to makethe module enter tri mode. The module searches for any of the three locking cells and camps on the first cellfound. Reselections in idle mode are allowed to the other locking cells only. In connected mode the behaviouris the same of the GSM and UMTS case
SARA-G3 / LEON-G1
The UMTS and dual mode are not available.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
LTE, tri mode and any dual mode involving LTE are not available.
The +COPS=5 command can be used to determine the available BCCH ARFCN / UARFCN and PSC /EARFCN and P-CID numbers.
The set command can only be executed when the module is not registered and no registration attempt
is in progress.
If the +URAT mode is not compatible with the requested cell(s) type then the command will return an error
result code.
If the command is provided with an unsupported UARFCN then the command will return an error result
code and the previous configuration will be restored unless the current +URAT mode is not compatible,in which case the cell lock will be disabled.
+COPS=5 and +COPS=? shall not be used when the lock is enabled, because the results would beinconsistent.

7.30.2 Syntax
Type
Set

SyntaxResponse
AT+UCELLLOCK=<lock_mode>[,OK<BCCH_ARFCN>[,<band1900>[,<UARFCN>,<PSC>[,<EARFCN>,<PCID>]]]]

ExampleAT+UCELLLOCK=0OK
AT+UCELLLOCK=2,90
OK
AT+UCELLLOCK=2,,,10750,100
OK
AT+UCELLLOCK=2,700,1,10750,100
OK
AT+UCELLLOCK=2,,,10750,100,300,1

UBX-13002752 - R67

7 Network service

Page 150 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Read

AT+UCELLLOCK?

GSM/GPRS modules+UCELLLOCK: [<lock_result>,]<lock_mode>[,<BCCH_ARFCN>,<band1900>]

ExampleOK+UCELLLOCK: 0
OK

OK
HSPA modules+UCELLLOCK: [<lock_result>,<locked_RAT>,]<lock_mode>[,<BCCH_ARFCN>,<band1900>,<UARFCN>,<PSC>]OK
LTE modules+UCELLLOCK: 1,1,2,90,0,65535,
65535+UCELLLOCK: [<lock_result>,<locked_RAT>,]<lock_mode>[,OK<BCCH_ARFCN>,<band1900>,+UCELLLOCK: 1,2,2,65535,0,10750,<UARFCN>,<PSC>[,<EARFCN>,<P- 100
CID>]]OKOK+UCELLLOCK: 1,2,2,700,1,10750,100
OK+UCELLLOCK: 1,2,2,700,107500,100,300,1
Test

AT+UCELLLOCK=?

GSM/GPRS modules+UCELLLOCK: (list of supported<lock>s),(list of supported <BCCH_
ARFCN>s),(list of supported<band1900>s)
OK
HSPA modules+UCELLLOCK: (list of supported<lock>s),(list of supported <BCCH_
ARFCN>s),(list of supported<band1900>s),(list of supported<UARFCN>s),(list of supported<PSC>s)OK
LTE modules+UCELLLOCK: (list of supported<lock>s),(list of supported <BCCH_
ARFCN>s),(list of supported<band1900>s),(list of supported<UARFCN>s),(list of supported<PSC>s),(list of supported<EARFCN>s),(list of supported <PCID>s)URC

UBX-13002752 - R67

OK+UCELLLOCK: (0,2-5),(0-1023),(0,1)
OK+UCELLLOCK: (0,2-7),(0-1023),(0,1),(1537-10838),(0-511)
OK+UCELLLOCK: (0,2-7),(0-1023),(0,1),(1537-10838),(0-511),(0-9919),(0-50
3)
OK

OK
GSM/GPRS modules+UCELLLOCK: 1+UCELLLOCK: <lock_result>
HSDPA modules

OK+UCELLLOCK: 1,1+UCELLLOCK: <lock_result>,<locked_RAT>
LTE modules

OK+UCELLLOCK: <lock_result>,<locked_RAT>

OK

7 Network service+UCELLLOCK: 1,1

Page 151 of 1001

u-blox cellular modules - AT commands manual

7.30.3 Defined values
Parameter<lock_mode><BCCH_ARFCN><band1900><UARFCN>Type
NumberNumberNumberNumberDescription
Action configuration:• 0: lock disabled• 2: lock enabled without URC• 3: lock enabled with URC• 4: extended lock enabled without URC• 5: extended lock enabled with URC• 6: extended redirection lock enabled without URC• 7: extended redirection lock enabled with URC
Indicates on which cell (BCCH ARFCN) to perform the lock (range 0-1023 if <band1900> is 0; 512-810 if <band1900> is 1).
A value of 65535 is invalid and it is present in the read output if the ARFCN has notbeen set.
Indicates whether the given <BCCH_ARFCN> is part of band 1900 or not, to avoid
ambiguity between bands 1800 and 1900:• 0(default value): the given <BCCH_ARFCN> is not part of band 1900
• 1: the given <BCCH_ARFCN> is part of band 1900
Indicates the UARFCN to perform the lock on (range 1537-10838).
A value of 65535 is invalid and it is present in the read output if the UARFCN has notbeen set.

<PSC><EARFCN><P-CID><lock_result><locked_RAT>

NumberThis parameter is equivalent to <dl_frequency> parameter in +CGED and+UCELLINFO commands.
Indicates the Primary Scrambling Code of the locked cell (range 0-511).

Number

A value of 65535 is invalid and it is present in the read output if the PSC has not been
set.
Indicates the EARFCN to perform the lock on (range is 0-9919).

Number

A value of 65535 is invalid and it is present in the read output if the EARFCN has notbeen provided.
Indicates the Physical Cell Id of the locked cell (range 0-503).

Number

A value of 65535 is invalid and it is present in the read output if the P-CID has notbeen provided.
Result of the last issued lock:Number• 1: lock enabled and successful, camped on the requested cell
• 2: lock enabled but unsuccessful, the requested cell was not foundCurrent locked RAT:•••

1: GSM
2: UMTS
3: LTE

7.30.4 Notes••••

If <lock_mode>=0, the <BCCH_ARFCN>, <band1900>, <UARFCN> and <PSC>, <EARFCN> and <P-CID>
parameters are not used.
If <lock_mode> differs from 0, the <BCCH_ARFCN>, <UARFCN> + <PSC> or the <EARFCN> + <P-CID>
parameters are mandatory.
If <band1900> is issued, <BCCH_ARFCN> is mandatory.
The printed list of supported <UARFCN> reports only the theoretical minimum and maximum UARFCN
for readability sake. The supported band ranges and additional frequencies are product dependent. The
supported UARFCN list is the following (based on 3GPP TS 25.101 [51] ch 5.4.4 - Table 5.2):
Operating band
Band I
Band II

Frequency band
2100
1900

Min UARFCN
10562
9662

Max UARFCN
10838
9938

Band IV

1700

1537

1738

UBX-13002752 - R67

7 Network service

Additional UARFCNs
412, 437, 462, 487, 512, 537, 562,
587, 612, 637, 662, 687
1887, 1912, 1937, 1962, 1987, 20
12, 2037, 2062, 2087

Page 152 of 1001

u-blox cellular modules - AT commands manual

Operating band
Band V
Band VI
Band VIII•••

Min UARFCN
4357
4387
2937

Max UARFCN
4458
4413
3088

Additional UARFCNs
1007, 1012, 1032, 1037, 1087
1037, 1062-

Table 7: Supported UARFCN list
The printed list of supported <EARFCN>'s reports only the theoretical minimum and maximum EARFCN
for readability's sake. The supported band ranges and additional frequencies are product dependent. The
supported EARFCN list is the following (based on 3GPP TS 36.101 [78] ch 5.7.3 - Table 5.7.3-1):
Operating band
Band 1
Band 2
Band 3
Band 4
Band 5
Band 7
Band 8Band 17
Band 19
Band 20
Band 21•Frequency band
850
800
900

Frequency band
2100
1900
1800
1700
850
2600
900
700
800
800
1500

Min EARFCN
0
600
1200
1950
2400
2750
3450
5730
6000
6150
6450

Max EARFCN
599
1199
1949
2399
2649
3449
3799
5849
6149
6449
6599

Table 8: Supported EARFCN list
If <lock_mode>=0, the read command's information text response only displays the <lock_mode>parameter.
If <lock_result>=2, the module is not in normal mode of operation, and persist in OOC state until <lock_mode>=0 is set or camps on the selected <BCCH_ARFCN> or <UARFCN> and <PSC> or <EARFCN> and<P-CID> (in the latter case the URC with <lock_result>=2 is displayed).
If <lock_result>=2 and if the lock has been set two or more RATs then the <locked_RAT> is meaninglessand should not be considered.

TOBY-L2 / MPCI-L2• <lock_mode>=4, 5, 6 and 7 are not supported.
SARA-U2 / LISA-U2 / LISA-U1• <EARFCN> and <P-CID> are not supported.
• <locked_RAT>=3 is not supported.
SARA-G3 / LEON-G1• <lock_mode>=6 and 7 are not supported.
• <locked_RAT>, <EARFCN> and <P-CID>, <UARFCN>, <PSC> are not supported.

7.31 Wireless service selection +WS46+WS46
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.31.1 Description
Select the cellular service (Wireless Data Service; WDS) to operate with the MT according to PCCA STD-101[67]. PCCA calls the WDS-Side Stack Selection. The command may be used when the MT is asked to indicate
the wireless services in which it can operate.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statement

UBX-13002752 - R67

7 Network service

Page 153 of 1001

u-blox cellular modules - AT commands manualof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

7.31.2 Syntax
Type
Set

SyntaxAT+WS46=[<n>]Response
OK

ExampleAT+WS46=25

Read

AT+WS46?

+WS46: <n>OK+WS46: 25

Test

AT+WS46=?

OK+WS46: (list of supported <n>s)OK+WS46: (12,22,25)

OKOK

7.31.3 Defined values
Parameter<n>Type
NumberDescription
WDS-Side stack selection indication and may be:• 12: GERAN only (single mode GSM)
• 22: UTRAN only (single mode UMTS)• 25: GERAN, UTRAN and E-UTRAN• 28: E-UTRAN only (single mode LTE)• 29: GERAN and UTRAN• 30: GERAN and E-UTRAN• 31: UTRAN and E-UTRAN

7.31.4 Notes••

It is possible to configure the WDS-Side stack only when is not registered on the wireless service.
The +URAT command provides extended functionalities with respect to +WS46 command.

TOBY-L2 / MPCI-L2• The command returns the "OK" final result code and the current values but no action is actually
performed.
TOBY-R200• The factory-programmed value of <n> is 25.
LARA-R202 / LARA-R280 / TOBY-R202• <n>=12, 25, 29 and 30 are not supported.
• The factory-programmed value of <n> is 31.
LARA-R203 / LARA-R204 / LARA-R220• <n>=12, 22, 25, 29, 30 and 31 are not supported.
• The factory-programmed value of <n> is 28.
LARA-R211• <n>=22, 25, 29 and 31 are not supported.
• The factory-programmed value of <n> is 30.
SARA-U2 / LISA-U2 / LISA-U1• <n>=28, 29, 30, 31 are not supported.
• The factory-programmed value of <n> is 25 (GERAN and UTRAN (dual mode stack)).
SARA-U270-53S / SARA-U270-73S / SARA-U280• <n>=12, 25 are not supported.
• The factory-programmed value of <n> is 22.

UBX-13002752 - R67

7 Network service

Page 154 of 1001

u-blox cellular modules - AT commands manual

7.32 Service specific access control restriction status+CSSAC+CSSAC
Modules

TOBY-L4
LARA-R2 TOBY-R2
SyntaxPIN required
fullNo

Attributes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.32.1 Description
Provides the current status of the parameters for SSAC, <BFVoice>, <BFVideo>, <BTVoice> and <BTVideo>.
The AT command has no effect on the execution of SSAC. Refers to SSAC (Service Specific Access Control)
related information which is used by MMTEL application (see 3GPP TS 24.173 [79]).

7.32.2 Syntax
Type
ActionSyntaxAT+CSSAC

Test

AT+CSSAC=?

Response+CSSAC: <BFVoice>,<BFVideo>,<BTVoice>,<BTVideo>
OK
OK

ExampleOK

7.32.3 Defined values
Parameter<BFVoice>

Type
Number<BFVideo>

Number<BTVoice>

Number<BTVideo>

NumberDescription
Shows the barring factor for MMTEL voice and it is mapped to the
BarringFactorForMMTEL-Voice as in Table 9.
Shows the barring factor for MMTEL video and it is mapped to the
BarringFactorForMMTEL-Video as in Table 10.
Shows the barring timer for MMTEL voice and it is mapped to the
BarringTimeForMMTEL-Voice as in Table 11.
Shows the barring timer for MMTEL video and it is mapped to the
BarringTimeForMMTEL-Video as in Table 12.

7.32.4 Notes•<BFVoice>
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

BarringFactorForMMTEL-Voice as specified in 3GPP TS
24.173 [79]
0
0,05
0,1
0,15
0,2
0,25
0,3
0,4
0,5
0,6
0,7
0,75
0,8
0,85
0,9
0,95
1

Table 9: Value of BFVoice and its interpretation by MMTEL application

UBX-13002752 - R67

7 Network service

Page 155 of 1001

u-blox cellular modules - AT commands manual•<BFVideo>
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

BarringFactorForMMTEL-Video as specified in 3GPP TS
24.173 [79]
0
0,05
0,1
0,15
0,2
0,25
0,3
0,4
0,5
0,6
0,7
0,75
0,8
0,85
0,9
0,95
1

Table 10: Value of BFVideo and its interpretation by MMTEL application•<BTVoice>
0
1
2
3
4
5
6
7
8

BarringTimeForMMTEL-Voice as specified in 3GPP TS
24.173 [79]
0
4
8
16
32
64
128
256
512

Table 11: Value of BTVoice and its interpretation by MMTEL application•<BTVideo>
0
1
2
3
4
5
6
7
8

BarringTimeForMMTEL-Video as specified in 3GPP TS
24.173 [79]
0
4
8
16
32
64
128
256
512

Table 12: Value of BTVideo and its interpretation by MMTEL application

UBX-13002752 - R67

7 Network service

Page 156 of 1001

u-blox cellular modules - AT commands manual

7.33 Home zone reporting +UHOMEZR+UHOMEZR
Modules
Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.33.1 Description
Configures the home zone change event reporting. If reporting is enabled, the MT returns URC +UHOMEZR:<label> whenever the home zone is changed.

7.33.2 Syntax
Type
Set

SyntaxAT+UHOMEZR=<onoff>

Response
OK

ExampleAT+UHOMEZR=1

Read

AT+UHOMEZR?

+UHOMEZR: <onoff>

OK+UHOMEZR: 0

Test

AT+UHOMEZR=?

OK+UHOMEZR: (list of supported<onoff>s)

OK+UHOMEZR: (0-1)
OK

OK+UHOMEZR: <label>

URC

7.33.3 Defined values
Parameter<onoff>Type
Number<label>StringDescription• 0 (default value): disable home zone change event reporting• 1: enable home zone change event reporting
Zone label indication••"HOME": also possible as "home", dependent from network indication"CITY": zone label

7.34 Jamming detection +UCD
+UCD
Modules
Attributes

SARA-U2 LISA-U2 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialYes
NVM
No

Response time-Error reference+CME Error

7.34.1 Description
The feature consists in detecting, at radio resource level, an anomalous source of interference and signallingit to the client. The jamming condition occurs when simultaneously:•

The synchronization is lost (i.e. the MT is no longer camped on the serving cell and cannot select any othersuitable cell)• An interference is detected (i.e. the band scan reveals at least n carriers, with power level equal or higher
than a specified threshold, on which no synchronization is possible)
If <op_code> is set to 5, 6 and 7 an additional constraint to verify a jamming condition occurrence is added:• The synchronization is lost and the MT cannot select any other suitable cell of the "user-desired" PLMN.
If the synchronization is lost due to the detected interference, and the MT camps and/or registers on adifferent PLMN, the jamming condition is not cleared as long as the "user-desired" PLMN is not detected or
second condition (interference detected) is no longer true.
SARA-G4 / SARA-G3 / LEON-G1
The "user-desired" PLMN is implicitly defined as:

UBX-13002752 - R67

7 Network service

Page 157 of 1001

u-blox cellular modules - AT commands manual••

The manually selected PLMN (i.e. the <oper> parameter, of the AT+COPS=1,<format>,<oper>
command), when the AT+COPS=1 command is issued. After enabling the advanced 2G jamming
detection, AT+COPS=0 must be issued to switch back to the automatic network selection.
The Home PLMN (as read from the IMSI), when AT+COPS=0 is issued.

The jamming condition is cleared when any of the above mentioned statements does not hold. If the network
registration is recovered (e.g. the +CREG: 1,<lac>,<ci>,0 URC is issued), the jamming condition has to beconsidered no totally effective anymore (e.g. the module can register on the band not jammed anymore).
The command configures how jamming is reported. If activated, an unsolicited indication is issued when thejamming condition is entered or released. In particular, the set command configures the URC +UCD: <active>.
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G100-06S<desired_PLMN> is not supported.
<op_code>=2 returns the <active> value, if and only if the URC has been previously enabled. Otherwise anerror result code is provided.
<op_code>=2 does not change the stored <op_code> value.

7.34.2 Syntax
Type
SyntaxGeneral syntax
Set
AT+UCD=<op_code>[,<min_number_of_2G_carriers>,<rxlev_
threshold>,<min_number_of_
3G_carriers>,<rssi_threshold>[,<desired_PLMN>]]
Read
AT+UCD?

Response

Example[+UCD: <active>]

AT+UCD=3,,,10,20

OK

OK+UCD: <op_code>,<min_number_of_2G_carriers>,<rxlev_threshold>,<min_number_of_3G_carriers>,<rssi_threshold>+UCD: 4,10,20,11,25
OK

OK
Jamming disabling
Set
AT+UCD=0

OK

AT+UCD=0
OK

2G jamming detection
Set
AT+UCD=1,<min_number_of_2G_
carriers>,<rxlev_threshold>
Read

AT+UCD?

OK

AT+UCD=1,10,60+UCD: 1,<min_number_of_2G_
carriers>,<rxlev_threshold>

OK+UCD: 1,10,20
OK

OK
Jamming status
Set
AT+UCD=2+UCD: <active>

AT+UCD=2

OK+UCD: 0OK

3G jamming detection
Set
AT+UCD=3,,,<min_number_of_3G_
carriers>,<rssi_threshold>
Read

AT+UCD?

OK

AT+UCD=3,,,10,20+UCD: 3,,,<min_number_of_3G_
carriers>,<rssi_threshold>

OK+UCD: 3,,,11,25
OKOK
2G and 3G jamming detection
Set
AT+UCD=4,<min_number_of_2G_
carriers>,<rxlev_threshold>,<min_number_of_3G_carriers>,<rssi_
threshold>

UBX-13002752 - R67

OK

AT+UCD=4,12,18,10,25
OK

7 Network service

Page 158 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UCD?

Response+UCD: 4,<min_number_of_2G_
carriers>,<rxlev_threshold>,<min_number_of_3G_carriers>,<rssi_
threshold>

Example+UCD: 4,10,20,11,25
OK

OK
Advanced 2G jamming detection
Set
AT+UCD=5,<min_number_of_
2G_carriers>,<rxlev_threshold>,,,<desired_PLMN>
Read
AT+UCD?

OK

AT+UCD=5,30,35
OK+UCD: 5,<min_number_of_2G_
carriers>,<rxlev_threshold>,<desired_PLMN>+UCD: 5,10,20,"00115"
OK

OK
Advanced 3G jamming detection
Set
AT+UCD=6,,,<min_number_of_
3G_carriers>,<rssi_threshold>,<desired_PLMN>
Read
AT+UCD?

OK

AT+UCD=6,,,11,25,"22269"
OK+UCD: 6,,,<min_number_of_
3G_carriers>,<rssi_threshold>,<desired_PLMN>+UCD: 6,,,11,25,"22269"
OK

OK
Advanced 2G and 3G jamming detection
Set
AT+UCD=7,<min_number_of_2G_
carriers>,<rxlev_threshold>,<min_number_of_3G_carriers>,<rssi_
threshold>,<desired_PLMN>
Read
AT+UCD?

OK

AT+UCD=7,10,20,11,25,"310456"
OK+UCD: 7,<min_number_of_2G_
carriers>,<rxlev_threshold>,<min_number_of_3G_carriers>,<rssi_
threshold>,<desired_PLMN>+UCD: 7,10,20,11,25,"310456"
OK

OK
Test

AT+UCD=?

+UCD: (list of supported <op_
+UCD: (0-4),(1-172),(3-63),(1-136),(0code>s),(list of supported <min_76)
number_of_2G_carriers>s),(list ofOKsupported <rxlev_threshold>s),(listof supported <min_number_of_
3G_carriers>s),(<list of supported<rssi_threshold>s),(list of supported<desired_PLMN>s)OK+UCD: <active>

URC+UCD: 37.34.3 Defined values
Parameter<op_code>Type
Number<min_number_of_
2G_carriers><rxlev_threshold>

NumberUBX-13002752 - R67

NumberDescription
Mode of operation of the jamming detection. When enabled, the +UCD URC may begenerated:• 0 (factory-programmed value): disabled• 1: 2G jamming detection enabled• 2: interrogation of the <active> value• 3: 3G jamming detection enabled• 4: 2G and 3G jamming detection enabled• 5: advanced 2G jamming detection enabled• 6: advanced 3G jamming detection enabled• 7: advanced 2G and 3G jamming detection enabled
Number of minimum disturbing carriers. The range goes from 1 to 172. The factoryprogrammed value is 255.
Power level threshold for 2G carriers; see the 3GPP TS 05.08 [28]. The range goesfrom 3 to 63. The factory-programmed value is 63.

7 Network service

Page 159 of 1001

u-blox cellular modules - AT commands manual

Parameter<min_number_of_
3G_carriers><rssi_threshold><desired_PLMN><active>

Type
NumberDescription
Number of minimum disturbing carriers. The range goes from 1 to 136.

NumberStringNumberPower level threshold for 3G carriers. The range goes from 0 to 76.
"user-desired" PLMN in numeric format (MCC and MNC).
Jamming detection status:• 0: 2G jamming no longer detected• 1: detected the 2G jamming• 2: 3G jamming no longer detected• 3: detected the 3G jamming

7.34.4 Notes
SARA-U2 / LISA-U2 / LISA-U1• The command setting is not stored in NVM.
• The jamming detection can be enabled / disabled only on one AT interface at a time. Once disabled onthat AT interface, it can be enabled on a different one.
• The jamming detection can be independently enabled / disabled on 2G and 3G network.
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S / LISA-U1• <op_code>=5, <op_code>=6 and <op_code>=7 are not supported.
SARA-G4 / SARA-G3 / LEON-G1• <op_code>=3, <op_code>=4, <op_code>=6 and <op_code>=7 are not supported (thus <min_number_of_
3G_carriers>, <rssi_threshold> are also not present).
• The range of <min_number_of_2G_carriers> parameter is between 1 and 255. The factory-programmed
value is 255.
SARA-G4 / SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S /SARA-G350-00X / SARA-G350-01B / SARA-G350-01S / LEON-G1• The command setting is not stored in NVM.

7.35 Smart jamming detection +UJAD+UJADModules
Attributes

TOBY-L4
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

7.35.1 Description
The feature consists of detecting, at the application level, an anomalous source of interference or jammer
installed in the cellular network and signalling it to the client. The jamming condition occurs whensimultaneously:• The synchronization is lost (i.e. the MT is no longer camped on the serving cell and cannot select any othersuitable cell)• An interference is detected (i.e. the band scan reveals radio channels with power levels equal to or higher
than a specified threshold)• On all such carriers, no synchronization is possible
The jamming condition is cleared when any of the above mentioned statements does not hold.
The command automatically sets and adjusts the thresholds for jamming detection based on the environment(number of visible cells and signal levels). For this purpose, the feature periodically performs network scans
and signal level measurements on the entire band.
The feature works independently on the RAT. It is recommended to activate the feature while in full cellularfunctionality (i.e. +CFUN: 1) and in normal service (i.e. if the module is detached via AT+COPS=2, the smart
jamming detection algorithm does not start).
If the command is activated, an unsolicited indication is issued when the jamming condition is entered orreleased.

UBX-13002752 - R67

7 Network service

Page 160 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4
The jamming detection algorithm relies on 2G and 3G signal level measurements, therefore the featuredoes not work if the module is set into LTE single mode (e.g via +URAT AT command).
The read command returns the <active> value, if and only if the URC has been previously enabled.

7.35.2 Syntax
Type
Set

SyntaxAT+UJAD=<op_code>

Response
OK

ExampleAT+UJAD=1

Read

AT+UJAD?

+UJAD: <op_code>[,<active>,<AcT>]OK
If jamming detection disabled:+UJAD: 0

[...]
OK

Test

AT+UJAD=?

+UJAD: (list of supported <op_code>s)OK+UJAD: <active>,<AcT>

URC

OK
If jamming detection enabled:+UJAD: 1,0
OK+UJAD: (0-1)
OK+UJAD: 1

7.35.3 Defined values
Parameter<op_code>Type
Number<active>

Number

<AcT>

NumberDescription
Jamming detection operation mode. Allowed values:• 0 (default and factory-programmed value): smart jamming detection disabled• 1: smart jamming detection enabled; the +UJAD URC may be generated
Jamming detection status:• 0: jamming not detected• 1: jamming detected• 2: jamming unknown
Indicates the radio access technology:• 0: GSM• 7: LTE• 9: E-UTRAN (NB-S1 mode)

7.35.4 Notes•

An error result code is provided when attempting to enable/disable the smart jamming detection when
it is already enabled/disabled.

TOBY-L4• The command setting is not stored in the NVM.
• The <AcT> parameter is not supported, therefore the read command returns only one entry.

7.36 IMSI detach +UCSDETACH+UCSDETACH
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.36.1 Description
Dynamically performs an IMSI detach if the module is currently registered to the CS services.
CS services can be also disabled by using +CEMODE and +CGCLASS while the module is not registeredon the network.

UBX-13002752 - R67

7 Network service

Page 161 of 1001

u-blox cellular modules - AT commands manual

7.36.2 Syntax
Type
ActionSyntaxAT+UCSDETACH

Response
OK

Test

AT+UCSDETACH=?

OK

ExampleAT+UCSDETACH
OK

7.37 MNO configuration +UMNOCONF+UMNOCONF
Modules
Attributes

TOBY-L201 TOBY-L280-02S MPCI-L201 MPCI-L280-02S
LARA-R202 LARA-R203 LARA-R204 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
partial
No
NVM
No

Response time
Up to 3 min

Error reference+CME Error

7.37.1 Description
Automatically configures the module to be compliant to the requirements of various Mobile Network
Operators.
For specific operators like Verizon, MNO requirements are enforced by an internal connection manager
application.
TOBY-L2 / MPCI-L2
After setting a new configuration the module:• deregisters from the network, actually entering the airplane mode;• deletes the current PDP context configuration;• reconfigures the PDP context settings (e.g. APN of the initial EPS bearer);• configures the IMS service;• if necessary, reconfigures the appropriate UE radio capabilities (e.g. HSDPA class, frequency bands).
A reboot is mandatory only if the <MNO> parameter has changed; the <conf> bitmap is applied runtime.
Automatic reboot after a change in the MNO derived from the SIM card can be optionally enabled.
LARA-R202 / LARA-R203 / TOBY-R2
Follow this procedure to properly set up the configuration of a MNO:••••

Deregister the module from the network (AT+COPS=2 or perform a AT+CFUN=4 / AT+CFUN=1 cycle)
Issue AT+UMNOCONF=<MNO>
When using the Global Data (<MNO>=9) or Global Voice (<MNO>=10) profiles, the initial default bearer
should be properly configured with AT+CGDCONT command
Reboot the module (AT+CFUN=16) in order to apply the new configuration

LARA-R204
After setting a new configuration the module reconfigures the PDP context settings (e.g. APN of the initial
EPS bearer) and re-enables the IMS service. Reboot the module to apply the new configuration.
TOBY-L201 / MPCI-L201
On TOBY-L201-01S, TOBY-L201-02S-00, MPCI-L201-01S, MPCI-L201-02S-00 the BIP support is includedin Terminal Profile and the BIP client is started only in Verizon and regulatory configurations.
TOBY-L201 / MPCI-L201
When changing configuration from Verizon, check the current +URAT setting, that might have beensilently changed by the OMA-DM client.
LARA-R204
On LARA-R204-02B-00 upon roaming attach the UE follows Verizon Wireless requirement to have IMS
OFF and EPS attach with Class 3 APN, IPv4-only IP type. The following settings are required to send MO
SMS when roaming:••

AT+UICMGSMODE=1 to set the 3GPP mode for MO SMSAT+UISMS=0 to set the CS domain for MO SMSUBX-13002752 - R67

7 Network service

Page 162 of 1001

u-blox cellular modules - AT commands manual

When back to Verizon HPLMN the legacy Verizon attach configuration is automatically set but SMS
settings must be restored (if changed) with commands below:••

AT+UICMGSMODE=2 to set the 3GPP2 mode for MO SMSAT+UISMS=1 to set the PS domain for MO SMSTOBY-L2 / MPCI-L2
When the <MNO> parameter is set to automatic, the module derives the current MNO from the IMSI(<detected_MNO>) and, after the mandatory reboot triggered by the user, it:• applies the configuration implied by the current <detected_MNO> value,• starts the MNO detection algorithm, and• issues a URC any time the <detected_MNO> value changes.
After the URC has been issued, depending on <conf> parameter (bit 0), the module reboot can be either
automatic or manual:• If the <detected_MNO> value is valid, and the automatic power cycle is enabled (bit 0 of <conf>
parameter set to 1) then the module will autonomously reboot as if AT+CFUN=16 were entered. In thiscase the URC simply warns the user that the module is about to power cycle.
• If automatic power cycle is disabled, the URC warns the user that a module reboot is required in orderto have the correct configuration applied.
TOBY-L2 / MPCI-L2
If the <detected_MNO> value does not map to any of the pre-defined MNOs AT&T or Verizon, or Telstra,
the configuration applied after the reboot is the regulatory one.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

7.37.2 Syntax
Type
Set

SyntaxResponse
AT+UMNOCONF=<MNO>[,<conf>] OK

ExampleAT+UMNOCONF=1

Read

AT+UMNOCONF?

OK+UMNOCONF: 3,23

Test

AT+UMNOCONF=?

URC+UMNOCONF: <MNO>,<conf>[,<detected_MNO>]

OK

OK+UMNOCONF: (list of supported<mode>s),(list of supported<conf>s)+UMNOCONF: (0-3),(0-31)

OK+UMNOCONF: <MNO>,<conf>,<detected_MNO>+UMNOCONF: 1,7,0

OK

7.37.3 Defined values
Parameter<MNO>

UBX-13002752 - R67

Type
NumberDescription
Mobile Network Operator (MNO) configuration:• 0: regulatory.
o TOBY-L201 / MPCI-L201 / LARA-R204 - IMS service disabled, Verizon connection
manager disabled, all LTE and UMTS bands enabled, <conf> is ignored.
o TOBY-L280-02S / MPCI-L280-02S - IMS service disabled, all LTE and UMTS
bands enabled, <conf> is ignored.
o LARA-R202 / LARA-R203 / TOBY-R2 - The module is configured as voice
capable, all LTE and UMTS bands enabled. IMS service is enabled for both VoIP
and SMS over IP. The LTE initial default bearer (<cid>=1) is configured withempty APN.
• 1: automatic detection of MNO configuration based on IMSI
• 2: AT&T configuration. IMS service disabled, all supported LTE bands enabled

7 Network service

Page 163 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Descriptiono TOBY-L201 / MPCI-L201 - HSDPA category set to 14
o LARA-R202 / TOBY-R2 - HSDPA category set to 8
• 3: Verizon. IMS enabled (SMS only), Verizon connection manager enabled , LTEbands 4 and 13.
The Verizon connection manager will always ensure that the proper PDP contexts
are defined and active.
• 4: Telstra. IMS service disabled, all supported LTE bands enabled.
• 5: T-Mobile. IMS service enabled, all supported LTE bands enabled. The LTE initialdefault bearer (<cid>=1) is opportunely configured (the APN of <cid>=1 is set to"fast.t-mobile.com").
o LARA-R202-82B / TOBY-R200-42B / TOBY-R200-82B The module is configured
as data only with IMS disabled. The LTE initial default bearer (<cid>=1) is
opportunely configured (the APN of <cid>=1 is set to "fast.t-mobile.com").
• 8: USCC. The module is configured as data only, IMS service is enabled for SMS
services only, all supported LTE bands enabled (+URAT: 3), no support for UMTS or
GSM. The LTE initial default bearer (<cid>=1) is opportunely configured.
The USCC configuration is imposing +URAT: 3 (LTE) in order to make the
USCC SIM register in real network. The DTE is required to change +URAT
command setting in roaming scenarios in order to enable the other RATs, andshould get back to +URAT: 3 when returing on Home network.
• 9: Global Data Only. The module is configured as data only, all supported LTE
bands enabled. IMS service is enabled, and it will register automatically only if the
MNO does not support CS services over its LTE network (see +UIMSCFG commanddescription). The LTE initial default bearer (<cid>=1) is configured with empty APN.
• 10: Global Voice. The module is configured as voice capable, all supported LTE bands
enabled. IMS service is enabled for both VoIP and SMS over IP. The LTE initialdefault bearer (<cid>=1) is configured with empty APN.
Allowed values:• TOBY-L201 / MPCI-L201 - 0 (regulatory), 1 (automatic detection), 2 (AT&T), 3(Verizon). The default and factory-programmed value is 2.
• TOBY-L280-02S / MPCI-L280-02S - 0 (regulatory), 1 (automatic detection), 4(Telstra). The default and factory-programmed value is 4.
• LARA-R204 - 0 (regulatory), 3 (Verizon). The default and factory-programmed value
is 3.
• LARA-R202 / LARA-R203 / TOBY-R2 - 0 (regulatory), 2 (AT&T), 5 (T-Mobile). The
default and factory-programmed value is 2.
• LARA-R202-82B / TOBY-R200-82B - 0 (regulatory), 2 (AT&T), 5 (T-Mobile), 8(USCC), 9 (Global Data Only), 10 (Global Voice). The factory-programmed value is 2.
• TOBY-R200-42B - 0 (regulatory), 5 (T-Mobile), 8 (USCC), 9 (Global Data Only), 10(Global Voice). The factory-programmed value is 9.
<MNO>=0 (regulatory) is meant only for simulated laboratory conformance
testing, its usage in live network is deprecated.

<conf>

Number<detected_MNO>

NumberUnsigned integer representing a bitmask.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
See Table 13 for for the meaning of each bit.
Current MNO detected in automatic mode. Allowed values:• 0: test SIM/USIM (regulatory)• 1: detection error: the module keeps the current configuration (factory
configuration is regulatory) and automatic mode is disabled until the module isrebooted.
• 2: AT&T SIM/USIM• 3: Verizon SIM/USIM• 4: Telstra SIM/USIM• 5: T-Mobile SIM/USIM
Allowed values:• TOBY-L201 / MPCI-L201 - 0 (regulatory), 1 (automatic detection), 2 (AT&T), 3(Verizon).
• TOBY-L280-02S / MPCI-L280-02S - 0 (regulatory), 1 (automatic detection), 4(Telstra).
• LARA-R2 / TOBY-R2 - Not supported.

UBX-13002752 - R67

7 Network service

Page 164 of 1001

u-blox cellular modules - AT commands manual

7.37.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• A module reboot is needed to enable to IMS test mode when the Verizon connection manager is disabled(<conf>=11).
• Bit
Bit description
Value Remarks
012Power cycle configuration, effective only if <MNO> 0=1
1
A module reboot is not required to apply it.
Reserved.
Verizon connection manager configuration.
A module reboot is not required to apply it. The
Verizon connection manager is required for themodule operation. It can be disabled for debug
purposes or if the DTE has its own externalmanager. A change in this bit, allowed only if<MNO> = 3 or <MNO> = 1 and <detected_MNO>= 3, automatically triggers the restart of the
protocol stack.

0
1

Disabled
Automatic power cycle enabled (default andfactory-programmed value)
Stop Verizon connection manager
Start Verizon connection manager.

The
Verizonconnection
managerconfiguration must always be active if<MNO> = 0 or <MNO> = 3; otherwise themodule cannot register with the network.

3

4

TOBY-L201 / MPCI-L201
The default and factory-programmed value
is 1.
0
IMS test mode configuration.
1
A module reboot is required to apply it. Allowed
only if <MNO> = 3 or <MNO> = 1 and <detected_
MNO> = 3.
VZWINTERNET handling in Verizon connection
manager.

05

The manager will set the PDP context with <CID>= 1
8 to VZWINTERNET and it will automatically
activate it. Allowed only if <MNO> = 3 or <MNO>= 1 and <detected_MNO> = 3. A change in this bit
automatically triggers the restart of the protocol
stack.
0
UMTS handling configuration

6

The internal connection manager could try toactivate the Verizon context also in UMTS RAT
leading to a potential issue with roaming. Allowed 1
only if <MNO> = 3 or <MNO> = 1 and <detected_
MNO> = 3.
0
PLMN check
The PLMN check is performed before the LTE
registration and the +UCGDFLT APN is configured 1
based on the internal information:o7

If PLMN is Verizon (based on +UMNOPLMNlist) then the Verizon APN will be used basedon the current bitmap
o If PLMN is not recognized then the roaming
list is checked and APN is accordingly seto Otherwise the Verizon APN will be used as
default, and the user can manually override itwith +UCGDFLTAllowed only if <MNO> = 3 or <MNO> = 1 and<detected_MNO> = 3.
0
IPv6 tethering configuration in router mode

UBX-13002752 - R67

7 Network service

Disabled (default and factory-programmed value)
Start IMS test modeNot handled (default and factory-programmed
value).
Handled by Verizon connection manager.

Feature disabled (factory-programmed anddefault value): the UMTS is not handled. The
Verizon configuration will be handled in LTE only.
Feature enabled: try to activate current Verizon
configuration also on UMTS.
Feature enabled (factory-programmed anddefault value)
Feature disabled. The PLMN check is not
performed and it is assumed that each PLMN is
Verizon.

IPv6 tethering enabled (factory-programmed anddefault value)

Page 165 of 1001

u-blox cellular modules - AT commands manualBit

Bit description
Value Remarks
Enabling the feature; the module will start IPv6
1
IPv6 tethering disabled
NDP (Neighbor Discovery Protocol) negotiations
over the USB link for the IPv6 subnetwork
assigned to VZWINTERNET by the network,
regardless of +UBMCONF configuration. Allowed
only if <MNO> = 3 or <MNO> = 1 and <detected_
MNO> = 3.

1

The custom algorithm is used

Table 13: <conf> bitmask meaning
TOBY-L201 / MPCI-L201• The default and factory-programmed value of <conf> is 7.
• A module reboot is not needed if the value of <conf> parameter is set to 7, 15, 23, 39, 47 or 55 and it isconfigured with another one of these values.
• In Verizon configuration, it is necessary to set the correct date and time to be fully operational on
the network (OMA-DM transactions originated by the network might fail otherwise). This can be doneby means of +CCLK command or by enabling the automatic date and time zone update with +CTZU
command.
• In Verizon configuration (<MNO>=3) the following configuration are not stored in NVM:
o Automatic power cycle (bit 0 of <conf> parameter)o Verizon connection manager enabled (bit 2 of <conf> parameter)
TOBY-L280-02S / MPCI-L280-02S• The default and factory-programmed value of <conf> is 1.
• The module boots in airplane mode (+CFUN: 4) after having set the module in regulatory configuration(<MNO>=0) and performed a silent reset (AT+CFUN=16).
• If <MNO>=4 the radio access technology cannot be configured to LTE single mode (the <SelectedAcT>
parameter of +URAT AT command cannot be set to 3).
LARA-R202-02B / LARA-R203 / TOBY-R200-02B / TOBY-R202• Table 14 reports the configuration necessary to use IMS in non-AT&T scenarios.
Command
AT+UMNOCONF=2

Response
OK

AT+CFUN=16

OK

AT+CGDCONT=1,"IPV4V6",""

OK

AT+UIMSCFG=0,1,48,"YES;+g.3gpp.smsip;"
AT+UIMSCFG=0,1,160,0
AT+CFUN=16

OK
OK
OK

Description
Set the <AT&T> Mobile Network Operator (MNO)
configuration
Reboot the module in order to apply the new
configuration
Replace the attach APN with void value so that
LTE attach will work
Enable SIP flag of SMSoIP support
Exclude the check on ISIM availability
Reboot the module in order to apply the new
configuration

Table 14: Configuration necessary to use IMS in non-AT&T scenarios
The applied configuration is persistent between power cycles.
LARA-R204• If <MNO>= 3 only <conf> = 7 and 15 are supported.
• The default and factory-programmed value of <conf> is 7.
• If <MNO>=3 it is not possible to activate a secondary context. A secondary context can be activatedonly in regulatory configuration (<MNO>= 0).
• In Verizon configuration, it is necessary to set the correct date and time to be fully operational on
the network (OMA-DM transactions originated by the network might fail otherwise). This can be doneby means of +CCLK command or by enabling the automatic date and time zone update with +CTZU
command.
LARA-R202 / LARA-R203• The value of the <conf> parameter is ignored; it always reports 7.

UBX-13002752 - R67

7 Network service

Page 166 of 1001

u-blox cellular modules - AT commands manual

TOBY-R2• The command is not supported by TOBY-R200-02B-00 and TOBY-R202-02B-00.
• The value of the <conf> parameter is ignored; it always reports 7.

7.38 PLMN list extensions +UMNOPLMN+UMNOPLMN
Modules
Attributes

TOBY-L201 TOBY-L280 MPCI-L201 MPCI-L280
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

7.38.1 Description
Edit the PLMN list used by AT+UMNOCONF's MNO detection algorithm during the IMSI identification phase inautomatic MNO mode. It configures the mapping of the current detected MNO to one of the pre-defined MNO
values. It is possible to extend the PLMN list of these MNO:
• AT&T• Verizon• Telstra
The following actions are allowed:• Add a PLMN (or more) to the automatic MNO detection algorithm: this is possible only if it does not collidewith the current setting (no ambiguity shall arise); if some collisions happen, restore the command setting
to the factory-programmed configuration• Revert the mapping of one of the pre-defined MNO to its factory-programmed value with AT+UMNOPLMN=<detectable_MNO>
The maximum number of the entries in the PLMN table is 40. The information text response of the readcommand provide one line for each allowed <detectable_MNO>.
For each set command at most 10 ranges can be defined. It is possible to issue some set commands until the
PLMN list is filled.

7.38.2 Syntax
Type
Set

SyntaxAT+UMNOPLMN=<detectable_
MNO>[,<plmn_list>]

Read

AT+UMNOPLMN?

Test

AT+UMNOPLMN=?

Response
OK

ExampleAT+UMNOPLMN=2,"310.050"

OK+UMNOPLMN: <detectable_MNO>, +UMNOPLMN: 2,"310.030,310.150,<plmn_list>
310.170,310.280,310.380,310.410,310.560"[....]+UMNOPLMN: 3,"310.590,310.890,
OK
311.480"+UMNOPLMN: (list of supported<detectable_MNO>s),OK+UMNOPLMN: (2,3),
OKOK

7.38.3 Defined values
Parameter<detectable_MNO>

Type
Number<plmn_list>

StringDescription
Detected MNO to be configured (see AT+UMNOCONF). Allowed values:• 2: AT&T• 3: Verizon• 4: Telstra
PLMNs list. Same syntax of AT+USIMLCK's <pers_data> when <facility> ="PN" (network personalization).
The parameter is optional. If omitted then the factory PLMN list for the requested<detectable_MNO> will be restored.

UBX-13002752 - R67

7 Network service

Page 167 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description
The parameter format is: "MCC1.MNC1min[-MNC2max][,MCC2.MNC2min[MNC2max]...[,MCC10.MNC10min[-MNC10max]]".

7.38.4 Notes
TOBY-L201 / MPCI-L201• <detectable_MNO> = 4 not supported.
• If the detected MNO is Verizon, the PLMN list set with this command is also added to the internal
connection manager home list. The internal connection manager, after having recognized it as home, will
activate it.
• The factory-programmed value of <plmn_list> parameter for AT&T is "310.030,310.150,310.170,310.280,
310.380,310.410,310.560".
• The factory-programmed value of <plmn_list> parameter for Verizon is "310.590,310.890,311.480".
TOBY-L280 / MPCI-L280• <detectable_MNO> = 2 and 3 not supported.
• The factory-programmed value of <plmn_list> parameter for Telstra is "505.11,505.71,505.72,505.01,
530.04".

7.39 LTE category configuration +ULTECAT+ULTECAT
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

7.39.1 Description
Sets the module LTE category.
For a description of LTE categories see http://www.3gpp.org/keywords-acronyms/1612-ue-category or 3GPP
TS 36.306 [82].
The command is accepted only in normal operation mode, namely +CFUN=1. Reboot the module to apply the
new configuration.

7.39.2 Syntax
Type
Set

SyntaxAT+ULTECAT=<mode>[,<lte_category>]

Read

AT+ULTECAT?

Test

AT+ULTECAT=?

Response
OK

ExampleAT+ULTECAT=0,2

OK+ULTECAT: <mode>,<lte_category> +ULTECAT: 0,2
OK+ULTECAT: (list of supported<mode>s),(list of supported <lte_category>s)

OK+ULTECAT: (0,1),(1-4)
OKOK

7.39.3 Defined values
Parameter<mode>

Type
NumberDescription
Configures how to apply the LTE category. Allowed values:•<lte_category>

Number0 (factory-programmed value): use the factory-programmed LTE category
configuration. <lte_category> is meaningless with this configuration• 1: apply user category. The custom LTE category will be applied
LTE category. Allowed values:•

UBX-13002752 - R67

1: LTE category 1

7 Network service

Page 168 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 2: LTE category 2• 3: LTE category 3• 4 (default and factory-programmed values): LTE category 4

7.40 Edit Verizon wireless APN table +VZWAPNE+VZWAPNE
Modules
Attributes

TOBY-L201 MPCI-L201
LARA-R204
SyntaxPIN required
partialNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

7.40.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 thelast; it returns each APN entry in a new line.

7.40.2 Syntax
Type
Set

SyntaxAT+VZWAPNE=<wapn>,<apncl>,<apnni>,<apntype>,<apnb>,<apned>,<apntime>

Response
OK

Read

AT+VZWAPNE?

[+VZWAPNE: <apncl>,<apnni>,<apntype>,<apnb>,<apned>,<apntime> [..]]
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)

ExampleAT+VZWAPNE=1,1,"IMS","IPv6","LTE","Enabled",0OK+VZWAPNE: 1,"IMS","IPv4v6","LTE","Enabled",0+VZWAPNE: 2,"VZWADMIN","IPv4v6","LTE","Enabled",0OK+VZWAPNE: (0-4),(1-4),,("IPv6","IPv4v6"),("LTE"),("Enabled","Disabled"),(0-1023)
OKOK

7.40.3 Defined values
Parameter<wapn><apncl><apnni>Type
NumberNumberStringDescription
APN list entry
APN class
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<apnb>

String• "IPv6": IPv6 type
• "IPv4v6" (factory-programmed value): IPv4 and IPv6 type
APN bearer:

UBX-13002752 - R67

7 Network service

Page 169 of 1001

u-blox cellular modules - AT commands manual

ParameterType<apned>String<apntime>

NumberDescription• "LTE" (factory-programmed value): LTE bearer used
Enable/disable the APN:
• "Enabled" (factory-programmed value): APN enabled• "Disabled": APN disabled
APN inactivity timer value in minutes.
• TOBY-L2 / MPCI-L2 - The range goes from 0 to 5.
• LARA-R2 - The range goes from 0 to 1023.
The value '0' (factory-programmed value) sets the timer to infinity.

7.40.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2• <apncl>=7 is not supported.
TOBY-L201-01S / MPCI-L201-01S• Class 3 APN can be overwritten to any customer defined string. For other APN classes, only strings in
the list of supported <apnni>s are allowed.
TOBY-L201-01S / MPCI-L201-01S• The class 1 APN NI is "VZWIMS".
• <apncl>=6 is not supported.
LARA-R204• The VZWAPNE settings are also managed (can be read and written) over the air via OMA-DM.
TOBY-L201-02S / MPCI-L201-02S / LARA-R204• On LARA-R204-02B-00, LARA-R204-02B-01, TOBY-L201-02S-00, MPCI-L201-02S-00 <apncl>=6 is notsupported.
• On LARA-R204-02B-00, LARA-R204-02B-01, TOBY-L201-02S-00, MPCI-L201-02S-00 the class 1 APN
NI is "VZWIMS".

7.41 Read RSRP values +VZWRSRP+VZWRSRP
Modules
Attributes

TOBY-L201 MPCI-L201
LARA-R204
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.41.1 Description
Returns the RSRP (Reference Signal Received Power) values for all LTE cells which the module is measuring.

7.41.2 Syntax
Type
Read

SyntaxAT+VZWRSRP?

Response+VZWRSRP:

Example+VZWRSRP:[<cellID1>,<EARFCN1>,<RSRP1>[,<cellID2>,<EARFCN2>,<RSRP2>[,...]]]

000,2175,"-61.00"
OKOK

7.41.3 Defined values
Parameter<cellIDn><EARFCNn><RSRPn>UBX-13002752 - R67

Type
NumberNumberStringDescription
nth cell physical cell identifier in "xxx" format. The range goes from 0 to 503.
nth cell EARFCN in decimal format. The range goes from 0 to 65535.
nth cell RSRP value in dBm/15 kHz where the format is "-XX.XX".

7 Network service

Page 170 of 1001

u-blox cellular modules - AT commands manual

7.42 Read RSRQ values +VZWRSRQ+VZWRSRQ
Modules
Attributes

TOBY-L201 MPCI-L201
LARA-R204
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

7.42.1 Description
Returns the RSRQ (Reference Signal Received Quality) values for all the LTE cells which the module ismeasuring.

7.42.2 Syntax
Type
Read

SyntaxAT+VZWRSRQ?

Response+VZWRSRQ:

Example+VZWRSRQ:[<cellID1>,<EARFCN1>,<RSRQ1>[,<cellID2>,<EARFCN2>,<RSRQ2>[,...]]]

000,2175,"-11.00"
OKOK

7.42.3 Defined values
Parameter<cellID><EARFCN><RSRP>

Type
NumberNumberStringDescription
nth cell physical cell identifier in "xxx" format. The range goes from 0 to 503.
See <EARFCN>.
nth cell RSRP value in dBm/15 kHz where the format is "-XX.XX".

7.43 Closed Subscriber Group +UCSG+UCSG
Modules
Attributes

TOBY-L4
LARA-R202 LARA-R211 LARA-R280 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
partialNo
No
Yes

Response time
Up to 3 min

Error reference+CME Error

7.43.1 Description
Performs a manual or automatic selection of a CSG cell, fingerprint clean up (i.e. clean up of the information
pertaining to a CSG entity stored by the module) and queries for the currently selected CSG cell information.
• The set command registers to CSG (in manual or automatic mode) or performs fingerprint clean up.
• The test command returns available CSG networks (if any) and the list of modes supported by set
command.
Only manual CSG selection set command and test command are abortable.

7.43.2 Syntax
Type
Set

SyntaxResponse
AT+UCSG=<mode>[,<oper>[,<csg_ OK
id>]]

Read

AT+UCSG?

Test

AT+UCSG=?

UBX-13002752 - R67+UCSG: <csg_sel_cause>[,<csg_id>,<csg_type_record_no>,<hnb_record_no>,<hnb_name>,<oper>,<AcT>,<csg_id_list_type>]OK+UCSG: [list of supported (<csg_id>,<csg_type_record_no>,<hnb_record_no>,<hnb_name>,<oper>,

7 Network service

ExampleAT+UCSG=0OK+UCSG: 0
OK+UCSG: (2,0,0,"","00101",0,0),,(0-2)
OKPage 171 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Example<AcT>,<csg_id_list_type>)s],,(list of
supported <mode>s)OK

7.43.3 Defined values
Parameter<mode>

Type
Number<oper>

String<csg_id><csg_sel_cause>

NumberNumber<csg_type_record_no>Number<hnb_record_no>

Number<hnb_name><AcT>

StringNumber<csg_id_list_type>

NumberUBX-13002752 - R67

Description
Operation mode:• 0: automatic CSG selection mode. <oper> and <csg_id> are ignored, if present.
• 1: manual CSG selection mode. <oper> and <csg_id> are mandatory parameters.
• 2: clean up the information pertaining to a CSG entity stored by the module (i.e.
Fingerprint Clean Up). <oper> and <csg_id> are mandatory or optional parameters
depending on the following operations:o If both the parameters <oper> and <csg_id> are specified, then the specified
PLMN and CSG ID combination shall be deleted.
o If only <oper> is specified and <csg_id> is omitted, then all CSGs belonging to
the specified PLMN shall be deleted.
o If both <oper> and <csg_id> are omitted, then complete data (all CSGs and all
PLMNs) shall be deleted.
o If <oper> is omitted and <csg_id> is specified, then this is an error case.
This parameter can be a string with 5 or 6 character long numeric format:• If <oper> is 5 character long numeric format, then first 3 digits are considered as
MCC and next 2 digits are considered as MNC.
• If <oper> is 6 character long numeric format, then first 3 digits are considered as
MCC and next 3 digits are considered as MNC.
CSG identifier of the cell.
CSG selection cause:• 0: no selection cause, moved out of all CSG cell and CSG information should be
ignored• 1: selected by manual selection process• 2: selected by automatic selection process
Record number of numeric type based on EFCGST (3GPP TS 31.102 section 4.4.6.3[18]) where CSG type is stored. The value indicates if the CSG type information isavailable at this record number in EFCGST. If <csg_type_record_no>=0 then the CSG
type information is not available.
HNB record number at location EFHNBN (3GPP TS 31.102 section 4.4.6.4 [18]). Different
values can be:• 0: means the parameter <hnb_name> given is valid• >0: means the parameter <hnb_name> given is not valid and valid <hnb_name> ispresent at this record number in EFHNBNName of Home Node B
Indicates the radio access technology:• 0: GSM• 1: UMTS• 2: LTE
Type of list of <csg_id> (see the 3GPP 25.367 [116]):• 0: <csg_id> is not in white list
• 1: <csg_id> is in the operator list
• 2: <csg_id> is in the allowed list

7 Network service

Page 172 of 1001

u-blox cellular modules - AT commands manual

7.44 Network Friendly Mode (NFM) activation +UNFM+UNFM
Modules

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
NVM
No
+CME Error

Attributes

7.44.1 Description
Activates or deactivates the Network Friendly Mode (NFM) feature.
Generally an UE aggressively retries the registration procedure until it is successful and behaves similarly if
the PDP context activation procedure fails. This behaviour may cause signalling overload and consequently
prolonged network outage. To avoid these scenarios and provide a more efficient access to the network, theNFM feature controls the number of network accesses per service type over a configurable amount of time.
In case of appropriate network rejection error causes, also a back-off timer can be started: when the timer isrunning or the number of allowed accesses is reached, further attempts are denied and the +UUNFM URC, if
enabled, indicates the time remaining before a further attempt can be served. The back-off timer controls the
temporal spread of successive attempts to register to CS or PS services, to activate a PDP context and to send
SMS messages.
Some network rejection error causes require specific behaviours which NFM does not alter (see the 3GPP TS
24.008 [12]). Furthermore NFM blocks and counts only application requests.
When a set command is issued, all related timers and counters are reset and block conditions are cleared.
See the +UNFMCONF for the parameter configuration.
If a SIM card belonging to AT&T is used, the factory-programmed value <mode>=0 shall be used to avoid
conflicts with the Radio Policy Manager (RPM).
+URPM and +UNFM AT commands cannot be both active at the same time.

7.44.2 Syntax
Type
Set

SyntaxResponse
AT+UNFM=<mode>[,<enableURC>] OK

ExampleAT+UNFM=1

Read

AT+UNFM?

OK+UNFM: 0,0,0,0,0,0

Test

AT+UNFM=?

URC+UNFM: <mode>,<enableURC>,<residual_time_1>,<residual_time_2>,<residual_time_3>,<residual_
time_4>

OK

OK+UNFM: (list of supported<mode>s),(list of supported<enableURC>s)+UNFM: (0,1),(0,1)

OK+UUNFM: <type>[,<residual_time_n>]+UUNFM: 2,1600

OK

7.44.3 Defined values
Parameter<mode><enableURC><residual_time_n>

UBX-13002752 - R67

Type
NumberDescription
Indicates the action to perform:

Number• 0: (factory-programmed value): NFM deactivated• 1: NFM activatedConfigures the +UUNFM URC presentation:

Number• 0: (default and factory-programmed value): +UUNFM URC disabled• 1: +UUNFM URC enabledTime in seconds until the active block <type> (n=<type>) is cleared.

7 Network service

Page 173 of 1001

u-blox cellular modules - AT commands manual

Parameter<type>

Type
NumberDescription
Information type.
It indicates the block type that denied the application's request (see the+UNFMCONF):
•
•
•
•
•
•
•

0: CS back-off timer running
1: PS back-off timer running
2: PDP back-off timer running
3: SMS back-off timer running
4: <CS_REG> attempts reached
5: <PS_REG> attempts reached
6: <PDP_OK> attempts reached7.45 Network Friendly Mode (NFM) configuration+UNFMCONF+UNFMCONF
Modules

Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

7.45.1 Description
Configures the Network Friendly Mode (NFM) related parameters.
The parameters are grouped in different sets:• Back-off timer parameters: the timer follows a geometric sequence whose scale factor, common duration
and upper limit are configurable. The timer duration is reset to the scale factor at every successful
registration or PDP context activation• Basic parameters: they define the maximum numbers of CS and PS registration and PDP context activation
attempts in a given time interval
Back-off timer parameters are set to a predefined value; all the other parameters are by default disabled.
User defined parameter configurations are stored in NVM: to make them effective, either a power cycle or+UNFM=1 command is required.
The <op_code> parameter is not saved in NVM; the information text response to the read commandprovides the setting for all the <op_code> parameter values.

7.45.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UNFMCONF=<op_code>,.....
Back-off timer configuration
Set
AT+UNFMCONF=0,<scale_factor>,<common_ratio>,<upper_limit>
Basic parameter configuration
Set
AT+UNFMCONF=1,<CS_REG>,<time_interval>,<PS_REG>,<time_interval>,<PDP_OK>,<time_interval>
Read
AT+UNFMCONF?

Response
OK
OK

OK

AT+UNFMCONF=1,60,2,1920
OK+UNFMCONF: 0,<scale_factor>,<common_ratio>,<upper_limit>+UNFMCONF: 1,<CS_REG>,<time_interval>,<PS_REG>,<time_interval>,<PDP_OK>,<time_interval>

UBX-13002752 - R67

Example7 Network service+UNFMCONF: 0,60,2,7680+UNFMCONF: 1,10,1,10,1,10,1
OK

Page 174 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+UNFMCONF=?

Response
ExampleOK+UNFMCONF: (list of the supported +UNFMCONF: (0-1)<op_code>s)OKOK

7.45.3 Defined values
Parameter<op_code>Type
Number<scale_factor><common_ratio>

NumberNumber<upper_limit>

Number<CS_REG>

Number<time_interval>

Number<PS_REG>

Number<PDP_OK>

NumberDescription
Type of operation:• 0: back-off timer configuration parameter set• 1: basic parameter set
Back-off timer base in seconds, range 1 - 255 (the factory-programmed value is 60)
Multiplier factor of the geometrical sequence, range 1 - 255 (the factory-programmed
value is 2)
Back-off timer's maximum duration in seconds, range 0 - 86400 (0: back-off timer
disabled, the factory programmed value is 7680)
Maximum number of CS registration attempts per defined <time_interval>, range 0 255 (0: unlimited attempts). The factory-programmed value is 10.
Time interval in hours associated to the preceding parameter, range 0 - 24 (0:unlimited attempts). The factory-programmed value is 1.
Maximum number of PS registration attempts per defined <time_interval>, range 0 255 (0: unlimited attempts). The factory-programmed value is 10.
Maximum number of successful PDP context activation attempts per defined <time_interval>, range 0 - 255 (0: unlimited attempts). The factory-programmed value is 10.

7.45.4 Notes
Block typeBack-off timer

Associated network rejection error causes
IMSI unknown in HLR, illegal MS, IMEI not accepted, illegal ME, GPRS services not allowed, GPRS
services and non-GPRS services not allowed, device identity cannot be derived by network, MSC
temporarily unreachable, network failure, congestion, service option temporarily out of order,
protocol error unspecified, insufficient resources, unknown or missing APN, unknown PDP address,
authentication failed, activation rejected by GGSN, service option out of order, NSAPI already in use

Table 15: Network rejection error causes relation with block types

7.45.5 Notes•

The block types related to PDP activations and/or deactivations are based on the internal <cid> value,thus:
o if a <cid> is re-used, the internal counters are reset.
o +CGACT set command's syntax with omitted <cid> is not allowed.

7.46 Radio Policy Manager (RPM) activation +URPM+URPM
Modules

Attributes

TOBY-L4 TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L280-03A TOBY-L280-03S MPCI-L201-02S
LARA-R202 LARA-R203 LARA-R211 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

7.46.1 Description
Activates or deactivates the Radio Policy Manager (RPM) feature for SIM cards not belonging to AT&T network
operator.

UBX-13002752 - R67

7 Network service

Page 175 of 1001

u-blox cellular modules - AT commands manual

Generally an UE aggressively retries the registration procedure until it is successful and behaves similarly
in case the PDP context activation procedure fails. This behaviour may cause signalling overload andconsequently prolonged network outage. To avoid these scenarios and provide a more efficient access to the
network, the RPM feature controls the number of network accesses per service type over a fixed amountof time. For more details on the RPM feature see AT&T Device Requirements [48] and GSMA Connection
Efficiency [130].
Some network rejection error causes require specific behaviours which the RPM feature does not alter (see the
3GPP TS 24.008 [12]).
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
If a SIM card belonging to AT&T is inserted, <mode>=1 shall not be set to avoid altering the behavior of
the RPM feature that is autonomously enabled and configured by the module with AT&T SIM cards.
SARA-U2 / LISA-U2 / SARA-G3+URPM and +UNFM AT commands cannot be both active at the same time.

7.46.2 Syntax
Type
Set

Syntax
AT+URPM=<mode>

Response
OK

ExampleAT+URPM=1

Read

AT+URPM?

+URPM: <mode>

OK+URPM: 1

Test

AT+URPM=?

OK
OK+URPM: (list of supported <mode>s) +URPM: (0,1)
OKOK

7.46.3 Defined values
Parameter<mode>

Type
NumberDescription
Indicates the action to perform:• 0 (factory-programmed value): RPM feature deactivated• 1: RPM feature activated

7.46.4 Notes
TOBY-L200-02S / TOBY-L201-02S / TOBY-L210-02S / TOBY-L280-02S / MPCI-L201-02S• The command is not supported by TOBY-L200-03S-00, TOBY-L201-02S-00, TOBY-L210-03S-00,
TOBY-L210-03A-00, TOBY-L280-03S-00, MPCI-L201-02S-00.
LARA-R202-02B / LARA-R203 / LARA-R211 / TOBY-R200-02B / TOBY-R202• The
commandisnotsupportedby
LARA-R202-02B-00,
LARA-R202-02B-01,
LARA-R202-02B-02, LARA-R203-02B-00, LARA-R203-02B-01, LARA-R203-02B-02, LARA-R211-02B-00,
LARA-R211-02B-01, LARA-R211-02B-02, TOBY-R200-02B-00, TOBY-R200-02B-01, TOBY-R200-02B-02,
TOBY-R200-02B-03,
TOBY-R202-02B-00,
TOBY-R202-02B-01,
TOBY-R202-02B-02,
TOBY-R202-02B-03.

7.47 Radio Policy Manager (RPM) configuration +URPMCONF+URPMCONF
Modules

Attributes

TOBY-L4 TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L280-03A TOBY-L280-03S MPCI-L201-02S
LARA-R202 LARA-R203 LARA-R211 TOBY-R2
LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

7.47.1 Description
Configures the Radio Policy Manager (RPM) related parameters.
The parameters are grouped in different sets:

UBX-13002752 - R67

7 Network service

Page 176 of 1001

u-blox cellular modules - AT commands manual•••

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 PLMN SIM card based checkconfiguration: it sets PLMNs in MCC.MNC format, for which the RPM functionality will be active.
o TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - at most 5 PLMNs are set.
SIM cards belonging to AT&T are already included as the module adheres to AT&T Device Requirements[48]) and will not be displayed in the read command.
Current RPM configuration: the parameters can only be read
Default RPM parameter setting stored in the module: the parameters can only be read

7.47.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+URPMCONF=<op_code>,.....
PLMN SIM card based check configuration

Response

ExampleOK• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / LISA-U2
Set
AT+URPMCONF=0,<PLMN>,OK<PLMN>,<PLMN>,<PLMN>,<PLMN>

AT+URPMCONF=0,"222.88","FFF.FF","123.456","987.65","222.10"
OK• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / LISA-U2
Read
AT+URPMCONF?
+URPMCONF: 0,<PLMN>,<PLMN>, +URPMCONF: 0,"222.88","",<PLMN>,<PLMN>,<PLMN>"123.456","987.65","222.10"+URPMCONF: 1,<RPM_active>,+URPMCONF: 1,0,0,0,0,0,0,0,0,0,0,0<SIM_RPM_setting>,<N1>,<T1>,+URPMCONF: 2,1,20,60,60,30,60,30<F1>,<F2>,<F3>,<F4>,<LR1>,<LR2>,<LR3>
OK+URPMCONF: 2,<RPM_enabled_
flag_m>,<N1_m>,<T1_m>,<F1_m>,<F2_m>,<F3_m>,<F4_m>
Test

AT+URPMCONF=?

OK+URPMCONF: (list of the supported +URPMCONF: (0)<op_code>s)OKOK

7.47.3 Defined values
Parameter<op_code>Type
Number<PLMN>

String<RPM_active>

Number<SIM_RPM_setting> Number<N1>,<T1>,<F1>,
Number<F2>,<F3>,<F4>,<LR1>,<LR2>,<LR3><RPM_enabled_flag_ Numberm>,<N1_m>,<T1_m>,<F1_m>,<F2_m>,<F3_m>,<F4_m>

UBX-13002752 - R67

Description
Type of operation:• 0: PLMN SIM card based check configuration• 1: current RPM configuration
PLMN in MCC.MNC format. "FFF.FF" indicates empty PLMN; the range goes from 00
0.00 to 999.999. The factory-programmed value is empty.
Indicates the action to perform:• 0: RPM feature is currently not active• 1: RPM feature is currently active
Indicates whether the inserted SIM card contains RPM parameter setting:• 0: the inserted SIM card does not contain the RPM parameter setting• 1: the inserted SIM card contains the RPM parameter setting
See the Radio Policy Manager Requirements [130].

Default RPM parameter setting stored in the module. See the Radio Policy Manager
Requirements [130].

7 Network service

Page 177 of 1001

u-blox cellular modules - AT commands manual

7.47.4 Notes
TOBY-L200-02S / TOBY-L201-02S / TOBY-L210-02S / TOBY-L280-02S / MPCI-L201-02S• The command is not supported by TOBY-L200-03S-00, TOBY-L201-02S-00, TOBY-L210-03S-00,
TOBY-L210-03A-00, TOBY-L280-03S-00, MPCI-L201-02S-00.
LARA-R202-02B / LARA-R203 / LARA-R211 / TOBY-R200-02B / TOBY-R202• The
commandisnotsupportedby
LARA-R202-02B-00,
LARA-R202-02B-01,
LARA-R202-02B-02, LARA-R203-02B-00, LARA-R203-02B-01, LARA-R203-02B-02, LARA-R211-02B-00,
LARA-R211-02B-01, LARA-R211-02B-02, TOBY-R200-02B-00, TOBY-R200-02B-01, TOBY-R200-02B-02,
TOBY-R200-02B-03,
TOBY-R202-02B-00,
TOBY-R202-02B-01,
TOBY-R202-02B-02,
TOBY-R202-02B-03.

7.48 Device Aggresion Management configuration +UDAMCFG+UDAMCFG
Modules
Attributes

TOBY-L4006
LARA-R202 LARA-R203
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

7.48.1 Description
Enables/disables the device aggression management (DAM).

7.48.2 Syntax
Type
Set

SyntaxAT+UDAMCFG=<status>

Response
OK

Read

AT+UDAMCFG?

+UDAMCFG: <status>,6,5,5,60,30,
60

Test

AT+UDAMCFG=?

OK+UDAMCFG: (list of supported<status>s)

ExampleAT+UDAMCFG=1
OK+UDAMCFG: 1,6,5,5,60,30,60
OK+UDAMCFG: (0,1)
OKOK

7.48.3 Defined values
Parameter<status>Type
NumberDescription
DAM status. Allowed values:• 0: DAM disabled• 1 (factory-programmed value): DAM enabled

7.49 PLMN search configuration in Out Of Coverage+UDCONF=55+UDCONF=55
Modules
Attributes

SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
NVM
No
-

Error reference+CME Error

7.49.1 Description
Configures the PLMN search in Out Of Coverage (OOC) conditions for power saving purposes. The functionality
is disabled if both timers are set to zero.
Setting one timer to a positive value and the other to zero provides an error result code.

UBX-13002752 - R67

7 Network service

Page 178 of 1001

u-blox cellular modules - AT commands manual

If the configuration is changed when it is already active the new settings are applied at the next start of
the PLMN search timer.
The configuration does not apply to other types of PLMN search, e.g. in Limited Service or triggered by
the AT+COPS test command.

7.49.2 Syntax
Type
Set

SyntaxResponse
AT+UDCONF=55,<timer1>,<timer2> OK

ExampleAT+UDCONF=55,1,2

Read

AT+UDCONF=55+UDCONF: 55,<timer1>,<timer2>

OK
AT+UDCONF=55

OK+UDCONF: 55,1,2
OK

7.49.3 Defined values
Parameter<timer1>

Type
Number<timer2>

NumberDescription
Time interval after entering OOC during which the PLMN scan follows the default
platform scheme, in 10 s basis. The maximum value is 8640, indicating a time intervalof 24 hours. The factory-programmed value is 0 (feature disabled).
Time interval after entering OOC during which the PLMN scan is inhibited, in 10 sbasis. During this time interval the Out Of Coverage condition cannot be cleared,
unless the PLMN scan is triggered via AT+COPS test command. The maximum valueis 8640, indicating a time interval of 24 hours. The factory-programmed value is 0(feature disabled).

7.50 Purging of temporary mobile identities after SIM refresh+UDCONF=56+UDCONF=56
Modules
Attributes

TOBY-L4006
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

7.50.1 Description
Configures the cleaning of network provided temporary mobile identities used for NAS signaling after theoccurrence of a SIM refresh of Type UICC Reset or NAA Session Reset.
The command is persistent and requires a reboot to be stored to the NVM.

7.50.2 Syntax
Type
Set

SyntaxResponse
AT+UDCONF=56,<purge_identities_ OK
enabled>

Read

AT+UDCONF=56

OK

ExampleAT+UDCONF=56,0
OK+UDCONF: 56,<purge_identities_
enabled>OK

7.50.3 Defined values
Parameter<purge_identities_
enabled>UBX-13002752 - R67

Type
NumberDescription••

0: purging of temporary mobile identities not enabled
1 (factory-programmed value): purging of temporary mobile identities enabled

7 Network service

Page 179 of 1001

u-blox cellular modules - AT commands manual

7.51 Smart radio coverage manager configuration+UDCONF=57+UDCONF=57
Modules
Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A
SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

7.51.1 Description
Smart radio coverage manager is a feature that aims to reduce the power consumption in those cellularscenarios where the radio coverage or the NW conditions would cause an inefficient usage of power supply: thetypical use case is when the module, in limited service or in out of coverage, performs frequent PLMN scansor unsuccessful registration attempts cycles. If the feature is enabled, when the device cannot get a reliable
NW coverage or is not reachable for CS services for a user defined time interval, the cellular functionality is
automatically switched off and, after a user defined delay, re-enabled to react to possible changes in radio
coverage conditions.
The cellular functionality can be optionally switched off when the module often loses coverage for short periods,
e.g. at cell borders in static conditions: a user defined threshold can be imposed on the maximum numberof loss of coverage and cell selections events performed in sequence to prevent the module from bouncing
between normal service an no service conditions. Also in this case the cellular functionality is re-enabled after
the user defined period mentioned above.
The smart radio coverage manager can be activated by the application processor e.g. when it needs to enterits low power mode period, and shall be disabled when the power consumption constraints are relaxed (e.g.
when passing from battery power supply to DC power supply). It is recommended to use it in static conditions,because in mobility the device can often enter no coverage or limited service conditions (e.g. when driving ina tunnel): in these cases the application processor should re-start the cellular functionality when it detects an
unexpected change of +CFUN to airplane mode and must consider that the algorithm is still running, therefore
if the radio and service coverage is unchanged, the airplane mode can be entered again, unless the feature isdisabled (recommended setting).
It is also recommended to activate the feature while in full cellular functionality (i.e. +CFUN: 1) and either innormal service or at least 180 s after the previous action or AT command triggering CS registration (e.g. AT+COPS=0 or AT+CFUN=1 or switch on).
If the cellular functionality is switched off by the application processor via AT+CFUN=0 or AT+CFUN=4, thesmart radio coverage manager will periodically enable it. This restriction does not apply to +COPS, i.e. if themodule is detached via AT+COPS=2, the smart radio coverage manager algorithm does not start. Similarly,
the feature should not be used with invalid SIM cards that cause the CS registration to be rejected with apermanent reject cause (e.g. illegal MS): in these cases, the device will enter limited service due to subscription
restrictions and it must be reset in order to restart registration attempts; if the RPM feature is enabled, it will
eventually trigger an automatic reset (see +URPM).
The user defined values (timers and thresholds) can be changed any time, but it is recommended to configure
the value when the feature is disabled in order to be sure that the algorithm will run with the latest settings.
The feature is voice centric and shall not be enabled for data only applications, where CS services are disabledby the application processor (e.g. via AT+CGCLASS command) or by the NW.

7.51.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UDCONF=57,<func>[,<param1>[,<param2>]]
Feature enabling
Set
AT+UDCONF=57,0,<enable>

Response

ExampleOK

AT+UDCONF=57,0,1
OK

OK

AT+UDCONF=57,0,1
OKTimer configuration

UBX-13002752 - R67

7 Network service

Page 180 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+UDCONF=57,1[,<timer1>[,<timer2>]]

Response
OK

OK

Temporary loss of coverage de-bouncing configuration
Set
AT+UDCONF=57,2,<bounce_OKcount>,<interval>
Read

AT+UDCONF=57

ExampleAT+UDCONF=57,1,60,600

AT+UDCONF=57,2,30,60+UDCONF: 57,0,<enable>

OK+UDCONF: 57,0,1+UDCONF: 57,1,<timer1>,<timer2>+UDCONF: 57,1,60,600+UDCONF: 57,2,<bounce_count>,<interval>+UDCONF: 57,2,20,60
OKOK

7.51.3 Defined values
Parameter<func>

Type
NumberDescription<enable>Number<timer1>

Number<timer2>

Number<bounce_count>

Number<interval>

Number• 0: the algorithm is disabled (factory programmed value)• 1: the algorithm is enabled
Timer expressed in seconds. The range goes from 30 to 86400 (24 hours). Factory
programmed and default value is 30.
Timer expressed in seconds. The range goes from 300 to 864000 (240 hours).
Factory programmed and default value is 1800.
Number of changes between normal service and no service condition before
switching to airplane mode. Range goes from 10 to 100. Value 0 means that thedebouncing feature is disabled. Factory programmed and default value is 0.
Maximum time interval (in seconds) during which the change between normal service
and limited service/no coverage condition is considered an unexpected event and isused to increment the guard counter. When the guard counter reaches the <bounce_
count>, the cellular functionality is switched off for <timer1> + <timer2> seconds.
Range is 10 to 1800, factory programmed and default value is 20, suggested value for<interval> is slightly smaller than <timer1> value.

•••

0: enables or disable the algorithm
1: configures the timers of the algorithm
2: configures the de-bouncing algorithm

7.52 Set MNO profile +UMNOPROF+UMNOPROF
Modules
Attributes

TOBY-L4206
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

7.52.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 TOBY-L4 - by means of the AT+CFUN=15 AT command
After setting a new configuration the module reconfigures the PDP context settings (e.g. APN of the initial EPS
bearer).
Follow this procedure to restore the profile factory-programmed configuration:• TOBY-L4 - 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.

UBX-13002752 - R67

7 Network service

Page 181 of 1001

u-blox cellular modules - AT commands manual

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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statement of theimplemented 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.52.2 Syntax
Type
Set

SyntaxResponse
AT+UMNOPROF=<MNO>[,<reset>, OK<urc_notification_enabled>]

Read

AT+UMNOPROF?

Test

AT+UMNOPROF=?

+UMNOPROF: <MNO>[,[<MNO_
detected>],<reset>,<urc_
notification_enabled>]
OK+UMNOPROF: (list of supported<MNO>s)OK

ExampleAT+UMNOPROF=1,0,1
OK+UMNOPROF: 3
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

URC+UMNOPROF: <MNO>,<MNO_
detected>

OK+UMNOPROF: 1,2

7.52.3 Defined values
Parameter<MNO>

UBX-13002752 - R67

Type
NumberDescription
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• 39: SKT
• 90: global• 100: standard Europe• 101: standard Europe No-ePCO. The factory-programmed configuration of thisprofile is the same of the standard Europe profile (<MNO>=100), but the ePCO isdisabled.
• 201: GCF-PTCRB. This profile is meant only for conformance testing.
Allowed values depend on the module series:

7 Network service

Page 182 of 1001

u-blox cellular modules - AT commands manual

ParameterType<MNO_detected>

Number<reset>Number<urc_notification_
enabled>NumberDescription• TOBY-L4 - 0, 20 (factory-programmed value)
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.
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 shall be issued only if <MNO>=1.
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 shall be issued only if <MNO>=1.

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

TOBY-L4• If <MNO>=0 the profile selected is regulatory (for more details on profile capabilities, see the PICS
document of the device).
• The <MNO_detected>, <reset>, <urc_notification_enabled> parameters are not supported.
• The PIN insertion is not mandatory before the command execution.
• If the <MNO> parameter is set to NTT DoCoMo (<MNO>=20), the module operates as data only.

UBX-13002752 - R67

7 Network service

Page 183 of 1001

u-blox cellular modules - AT commands manual

8 IP Multimedia Subsystem (IMS)
8.1 Introduction
TOBY-L201 / MPCI-L201
The module has been certified for Verizon network operator with the required IMS configuration,
automatically set by AT+UMNOCONF command.
The IMS configuration can be modified through the +UIMSCONF AT command described in this section;in this case certification of the application device integrating the module could be not more valid.

8.2 Domain configuration for supplementary services +UISS+UISSModules
Attributes

LARA-R211
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

8.2.1 Description
Configures for performing query and set of supplementary services either in PS domain over IMS/XCAP (seeSupplementary services introduction) or in CS domain through CSFB to legacy RAT if supported.
The setting is stored to NVM and any change is effective immediately after the set command has completed.

8.2.2 Syntax
Type
Set

SyntaxAT+UISS=<ss_mode>

Response
OK

ExampleAT+UISS=1

Read

AT+UISS?

+UISS: <ss_mode>OK+UISS: 1

Test

AT+UISS=?

OK+UISS: (list of supported <ss_mode>s)OK+UISS: (0-2)
OKOK

8.2.3 Defined values
Parameter<ss_mode>Type
NumberDescription
Allowed values:• 0: SS transactions are sent only over XCAP
• 1 (factory-programmed value): SS transactions are sent via CSFB
• 2: SS transactions will go over XCAP if IMS is registered, over CSFB otherwise

8.2.4 Notes
LARA-R211• The command is not supported by LARA-R211-02B-00.

8.3 IMS client configuration +UIMSCFG+UIMSCFG
Modules
Attributes

LARA-R202 LARA-R203 LARA-R204 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

8.3.1 Description
Configures the IMS managed objects by means of proper keys that configure the corresponding functionality.

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 184 of 1001

u-blox cellular modules - AT commands manual

8.3.2 Syntax
Type
SyntaxGeneric syntax
Set / Read AT+UIMSCFG=<op_code>[,<num_of_Config_items>,<ImsConfig1>[,<data1>[,<ImsConfig2>[,<data2>[...]]]]]IMS setting configuration
Set
AT+UIMSCFG=0[,<num_of_Config_
items>,<ImsConfig1>[,<data1>[,<ImsConfig2>[,<data2>[...]]]]]IMS setting reading
Read
AT+UIMSCFG=1[,<num_of_
Config_items>,<ImsConfig1>[,<ImsConfig2>[...]]]

Response

ExampleOK

OK[+UIMSCFG :<ImsConfig1>,<data1> AT+UIMSCFG=1[+UIMSCFG :<ImsConfig2>,<data2> +UIMSCFG: 50,0[..]]]+UIMSCFG: 51,"ims"OK+UIMSCFG: 53,2
+UIMSCFG: 253,1
OK

Test

AT+UIMSCFG=?

+UIMSCFG: (list of supported<op_code>'s),(list of supported<ImsConfig>)+UIMSCFG: (0-1),(50,51,53,253)
OKOK

8.3.3 Defined values
Parameter<op_code>Type
Number<data>

Number /StringNumber<num_of_Config_
items><ImsConfig>

NumberDescription
Allowed values:• 0: sets/configures the corresponding <data> of the IMS configuration data
specified in <ImsConfig>. It can be used to set/configure more than one<ImsConfig>s. If the <ImsConfig> parameter is omitted, then the command will set
the default <data> of all <ImsConfig>s.
• 1: gets the configured <data> value of a specific IMS configuration data mentioned
by <ImsConfig>. It can be used to retrieve more than one <ImsConfig>s. If the<ImsConfig> parameter is omitted, then the command will return the <data> of all<ImsConfig>s.
Contains the numeric data if <ImsConfig> is a numeric parameter. Otherwise it willcontain the string data if <ImsConfig> is a string parameter.
Number of IMS configuration elements to be set or retrieved.
Allowed values:• 9: 3GPP_CONFERENCE_URI<data> is a string parameter and defines the Conference Factory URI. See
3GPP TS 24.166 [112], Conf_Factory_URI; it should be a null terminated string,the maximum size is 255. The default and factory-programmed value differ
depending on product version:o LARA-R211 - The default and factory-programmed value is "".
LARA-R211 - Configures the <data> parameter with the Conference Factory
URI of the MNO to enable multiparty calls over VoLTE.

•

UBX-13002752 - R67

LARA-R203 LARA-R202 LARA-R211 - If <data>="", the Conference Factory
URI is automatically generated with the following syntax: "sip:mmtel@conffactory.<domain>" where <domain> iso ims.mnc<mnc>.mcc<mcc>.3gppnetwork.org in case of no ISIM presento Specific operator domain if EF_DOMAIN is valid and present in ISIM
For more details see 3GPP 23.003 [95] chapter 13.10.
50: AUTOLOGIN_MODE<data> is an integer parameter and set the autologin mode of IMS. Allowed
values:o 0 (default value): AUTOLOGIN_NEVERo 1: AUTOLOGIN_ALWAYS

8 IP Multimedia Subsystem (IMS)

Page 185 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Descriptiono 2: AUTOLOGIN_HOME_NETWORKo 3: AUTOLOGIN_LTE_EPS_ONLY. IMS registration starts only if the MT
registers to LTE network with EPS services only (CS domain rejected with cause#18).
The factory-programmed value differs depending on the product version:o LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R200-02B / TOBY-R202 - The
factory-programmed value is 1 (AUTOLOGIN_ALWAYS).
o LARA-R204 - The factory-programmed value is 2 (AUTOLOGIN_HOME_
NETWORK).
o LARA-R204 - The factory-programmed value is 1 (AUTOLOGIN_ALWAYS) in
LARA-R204-02B-00.
o TOBY-R200-42B - The factory-programmed value is 3
• 51: APN_NAME<data> is a string parameter representing the IMS APN name to be used for
the VoLTE; it shall be a null terminated string. The maximum length is 255. The
default and factory-programmed value differ depending on product version:o LARA-R204 - The factory-programmed value is "IMS". On LARA-R204-02B-00 /LARA-R204-02B-01 the factory-programmed value is "VZWIMS".
o LARA-R204 - The default value is "ims".
o LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2 - The default and factoryprogrammed value is "ims".
• 53: PREFFERED_PDPTYPE<data> is an integer parameter and represents the preferred PDP type for IMS.
Allowed values:o 0: IPv4o 1: IPv6o 2 (default and factory-programmed value): IPv4v6• 162: IMSI_in_Contact_header<data> is an integer parameter and enables the insertion of the IMSI in the
SIP "contact" header. To apply the new setting the module must re-register tothe network (AT+COPS=2 / AT+COPS=0 or AT+CFUN=4 / AT+CFUN=1 or AT+CFUN=16). The flag is configured as per operator requirements, and it is also
updated by +UMNOCONF AT command. Allowed values are:o 0: IMSI not present in SIP "contact" headero 1: IMSI present in SIP "contact" header••

The default and factory-programmed value differs depending on product version:o LARA-R202 / LARA-R203 - The factory-programmed value is 1.
164: aSRVCC_configuration<data> is an integer parameter and enables/disables the aSRVCC support. To
apply the new setting the module must re-register to the network (AT+COPS=
2 / AT+COPS=0 or AT+CFUN=4 / AT+CFUN=1 or AT+CFUN=16). The flag isconfigured as per operator requirements, and it is also updated by +UMNOCONF
AT command (<mode>=0 (regulatory) or <mode>=2 (AT&T) or <mode>=
5 (T-Mobile) enable the feature). In order to be compliant with certification
requirements, the feature shall be enabled in AT&T and T-mobile configuration.
Allowed values are:o 0: aSRVCC call disabledo 1 (default and factory-programmed value): aSRVCC call enabled
200: XCAP_APN<data> is a string parameter and represents the APN name to be used forsupplementary service provisioning; it should be a null terminated string. The
maximum length is 255.
The factory-programmed value differs depending on product version:o LARA-R204 - The factory-programmed value is "NONE".
o LARA-R211 - The factory-programmed value is "ims".
o LARA-R202 / LARA-R203 / TOBY-R2 - The factory-programmed value is"nxtgenphone".
o LARA-R202 / LARA-R203 / LARA-R204 / LARA-R211 / TOBY-R2 - The default
value is "ims".
LARA-R211

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 186 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description
Configures the <data> parameter of <ImsConfig>=200 key with the APN
name of the MNO to enable supplementary services over VoLTE• 201: XCAP_ROOT_URI<data> is a string parameter and represents the Root URI of the XCAP server; itshould be a null terminated string. The "http//" prefix is required. The maximum
length is 255. The default and factory-programmed value is an empty string.
• 202: XCAP_AUTH_USER_NAME<data> is a string parameter and represents the username to be used for HTTP
authentication of XCAP requests; it should be a null terminated string. The
maximum length is 255. The default and factory-programmed value is an empty
string.
• 203: XCAP_AUTH_PASSWORD<data> is a string parameter and represents the user password to be used for
HTTP authentication of XCAP requests; it should be a null terminated string. The
maximum length is 255. The default and factory-programmed value is an empty
string.
• 204: XCAP_TRANSPORT_TYPE<data> is an integer parameter and represents the transport type to be used for
XCAP Requests. Allowed values:o 0 (default and factory-programmed value): TRANSPORT_HTTP
o 1: TRANSPORT_HTTPS
o 2: TRANSPORT_HTTPS_PREFFERED• 205: XCAP_Bearer_Deactivation_Timer<data> is an integer parameter and represents the time in seconds after
which IMS will automatically deactivate the XCAP bearer with APN defined by<ImsConfig>=200, if it has been activated by IMS itself (i.e. if it was not active
during Supplementary Services related AT command execution). According to
AT&T <CDR-LTE-1982> requirement (Supplementary Services Configuration),
the XCAP shall be used for supplementary services regardless the RAT and IMS
registration status. Allowed values:o The range goes from 0 to 65535
o 0: deactivates the XCAP bearer upon XCAP completiono 65535: never deactivates the XCAP bearero Default and factory-programmed value: 3• 253: SIP_URI_FORMAT<data> is an integer parameter and represents the URI format to be used forconverting MSISDN numbers into URI's. Allowed values:o 0: URI_NONE
o 1: URI_SIP
o 2: URI_TEL•

The default and factory-programmed value differs depending on product version:o LARA-R204 - The factory-programmed value is 2.
o LARA-R204 - The default value is 1.
o LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2 - The default and factoryprogrammed value is 1.
264: VoPS_registration<data> is an integer parameter and enables the VoPS support check. The IMS willregister only if VoPS is declared as supported by the network. Allowed values are:o 0: VoPS support check disabledo 1: VoPS support check enabled
The default and factory-programmed value differs depending on product version:o LARA-R204 - The default and factory-programmed value is 0.
o LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2 - The factory-programmed
value is 1.

•

UBX-13002752 - R67

The VoPS support can be checked via +CIREP AT command.
269: VoLTE_conference<data> is an integer parameter and configures the VoLTE conference
subscription event. Allowed values are:o 0: disable the subscription evento 1 (default and factory-programmed value): enable the subscription event

8 IP Multimedia Subsystem (IMS)

Page 187 of 1001

u-blox cellular modules - AT commands manual

8.3.4 Notes
LARA-R202 / LARA-R203 / TOBY-R2• Some keys are differently configured depending on the MNO set by means of +UMNOCONF AT command.
In the table below are listed the keys that are differently set in case the module is registered on AT&T
or T-Mobile MNO:
Key
9
200
269
353
354

AT&T
"sip:n-way_voice@one.att.net""nxtgenphone"
10
0

T-Mobile"sip:conference@volte.tmo.com""NONE"0
1
1

LARA-R202• If <ImsConfig>=50, then <data>=3 is not supported
LARA-R203• <ImsConfig>=164, 205 are not supported.
• If <ImsConfig>=50, then <data>=3 is not supported
TOBY-R2• <ImsConfig>=205, 269 are not supported.
• <ImsConfig>=162 is not supported by TOBY-R200-02B-01 and TOBY-R202-02B-01.
TOBY-R202• <ImsConfig>=164 is not supported.
• If <ImsConfig>=50, then <data>=3 is not supported
TOBY-R200• <ImsConfig>=164 is not supported.
TOBY-R200-02B• If <ImsConfig>=50, then <data>=3 is not supported
LARA-R204• <ImsConfig>=162, 164, 205 and 269 are not supported.
• If <ImsConfig>=50, then <data>=3 is not supported• <ImsConfig>=264 has not effect.
LARA-R211• The values corresponding to the key <ImsConfig>=9, 162, 200, 201, 202, 203, 204 must be properly
configured by the user.
• <ImsConfig>=164 and 205 are not supported.
• If <ImsConfig>=50, then <data>=3 is not supported• Configure the <ImsConfig>=200 in order to make XCAP work. The same APN used for internet trafficmust be used.

8.4 IMS client registration / deregistration in network+UIMSREG+UIMSREG
Modules
Attributes

LARA-R202 LARA-R203 LARA-R204 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

8.4.1 Description
Sends the registration/de-registration request to the network.
The AT+UIMSREG=0 command can be used during certification to trigger an IMS deregistration, but the IMS
automatic registration feature (AT+UIMSCFG=0,1,50,1 or AT+UIMSCFG=0,1,50,2) has higher priority: in case

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 188 of 1001

u-blox cellular modules - AT commands manualof LTE cell reselection the IMS registration will be restarted. When the IMS shall be steadily deregistered, issue
AT+UIMSCFG=0,1,50,0 before issuing AT+UIMSREG=0.
Only an IMS client session is possible at any given time. The user must first configure the session's
parameters using AT+UIMSCFG command before using AT+UIMSREG.
The final result code to the set command only implies that the request is success/failure. It does notguarantee the IMS client registration. The registration status of the IMS client is provided by means of
the +CIREG AT command.

8.4.2 Syntax
Type
Set

SyntaxAT+UIMSREG=<mode>

Response
OK

ExampleAT+UIMSREG=1

Test

AT+UIMSREG=?

+UIMSREG: (list of supported<mode>s)OK+UIMSREG: (0,1)
OKOK

8.4.3 Defined values
Parameter<mode>

Type
NumberDescription
Allowed values:• 0 (default value): deregister the IMS client from network• 1: register the IMS client to network

8.5 IMS configuration setting +UIMSCONF+UIMSCONF
Modules
Attributes

TOBY-L201 MPCI-L201
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

8.5.1 Description
Access several configuration and settings related to IP Multimedia Subsystem (IMS).

8.5.2 Syntax
Type
Set

Test

SyntaxAT+UIMSCONF=<key_name>[,<value>[,<more_values>]]AT+UIMSCONF=?

UBX-13002752 - R67

Response
OK

ExampleAT+UIMSCONF="KEY_IMS_PDP_APN","IMS",1OK
AT+UIMSCONF="KEY_MTU_SIZE",2500

OK+UIMSCONF: (list of+UIMSCONF: ("KEY_IMS_PDP_APN","KEY_
supported <key_name>s),,(list IMS_PDP_CID","KEY_IMS_PDP_TYPE","KEY_of supported <more_values>s) AUTH_TYPE_AKA","KEY_AUTH_TYPE_AKAV2","KEY_AUTH_TYPE_MD5","KEY_SEC_AGREE",
OK"KEY_XDM_URL","KEY_PASSWORD","KEY_
HOME_NETWORK_DOMAIN","KEY_PRIVATE_IDENTITY","KEY_PUBLIC_IDENTITY","KEY_CONFIG_SOFT_SIM","KEY_CONFIG_SOFT_
SIM_K", "KEY_CONFIG_SOFT_SIM_OP","KEY_PCSCF_SERVER_ADDRESS","KEY_DNS_SERVER","KEY_SIP_TIMER_T1","KEY_SIP_
TIMER_T2","KEY_SIP_TIMER_T4","KEY_SIP_
TIMER_TF","KEY_MTU_SIZE", "KEY_IMS_
CLIENT_PORT","KEY_REG_EXPIRES","KEY_
MAX_REG_EXPIRES","KEY_RETRY_BASE_
TIME","KEY_RETRY_MAX_TIME","KEY_REG_
BARRED_USER_ID","KEY_EXPLICIT_UNSUB_
REG_EVENT", "KEY_PCSCF_BACKOFF_

8 IP Multimedia Subsystem (IMS)

Page 189 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

ExamplePREFERENCE","KEY_SMSC_NUMBER","KEY_SMSC_URI","KEY_MO_SMS_FORMAT","KEY_MO_SMS_ENCODING","KEY_QOS_
PREFERENCE","KEY_PDP_BEARER_MODE","KEY_DOMAIN_PREFERENCE","KEY_SMS_
PREFERENCE","KEY_IMS_SUPPORT","KEY_
IMS_MWI_SUPPORT","KEY_IMS_SIGCOMP_SUPPORT","KEY_IMS_RAT"),,(0-3)
OK

8.5.3 Defined values
Parameter<key_name>

Type
StringDescription
Allowed configurations:
•
•

•

•

•

•

•

•

•

•

•

•

•

•

UBX-13002752 - R67"KEY_IMS_PDP_APN": IMS Access Point Name.
<value> type is a string parameter. The factory-programmed and default value is "IMS".
"KEY_IMS_PDP_CID": PDP context identifier to be used for IMS signalling protocols.
<value> is a numeric parameter in range [0-8], where 0 indicates that the target will use any
free PDP context identifier. The factory-programmed and default value is 0.
"KEY_IMS_PDP_TYPE": IMS PDP type.
<value> is a string parameter with these allowed values: "IPV4", "IPV6", "IPV4V6". The
factory-programmed and default value is "IPV4V6".
"KEY_AUTH_TYPE_AKA": configures the AKAv1 MD5 Digest Authentication. The Security
Agreement must be explicitly enabled with the related <key_name>.
<value> is a string parameter with these allowed values: "true", "false". The factoryprogrammed and default value is "true".
"KEY_AUTH_TYPE_AKAV2": configures the AKAv2 MD5 Digest Authentication. The Security
Agreement must be explicitly disabled with the related <key_name>.
<value> is a string parameter with these allowed values: "true","false". The factoryprogrammed and default value is "false".
"KEY_AUTH_TYPE_MD5": configures MD5 Digest Authentication. The Security Agreement
must be explicitly disabled with the related <key_name>.
<value> is a string parameter with these allowed values: "true","false". The factoryprogrammed and default value is "false".
"KEY_SEC_AGREE": configures the Security Agreement and IPsec.
<value> is a string parameter with these allowed values: "true","false". The factoryprogrammed and default value is "true".
"KEY_XDM_URL": URI of the HTTP server hosting the SS document. The URL shall include
the "http://" or the "https://" prefix.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
"KEY_PASSWORD": password for IMS MD5 Digest Authentication and XCAP Authentication.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
"KEY_HOME_NETWORK_DOMAIN": Home Domain/Realm. If not provided it will be read fromthe UICC.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
"KEY_PRIVATE_IDENTITY": private User ID for IMS Registration and XDM Authentication(IMPI). If not provided it will be read from UICC.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
"KEY_PUBLIC_IDENTITY": public User ID. It must be a SIP URI (IMPU). If not provided it will beread from the UICC.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
"KEY_CONFIG_SOFT_SIM": configures the Software SIM feature. If the UICC does notsupport the ISIM application, the feature will perform the AKA authentication with its own
K and OP values.
<value> is a string parameter with these allowed values: "true","false". The factoryprogrammed and default value is "false".
"KEY_CONFIG_SOFT_SIM_K": Software SIM secret K.

8 IP Multimedia Subsystem (IMS)

Page 190 of 1001

u-blox cellular modules - AT commands manual

ParameterType

UBX-13002752 - R67

Description<value> is a hex encoded string. The factory-programmed and default value is an empty
string.
• "KEY_CONFIG_SOFT_SIM_OP": Software SIM secret OP.
<value> is a hex encoded string. The factory-programmed and default value is an empty
string.
• "KEY_PCSCF_SERVER_ADDRESS": P-CSCF IP Address/Domain[:port] where port is optional.
If not provided it will read from PCO exchange during PDN creation, DHCP server or UICC inthat order. The IP address can be either IPV4 or IPV6. In case of IPV6 it must be enclosed insquare brackets []. E.g. [2001::1]:4060 where 2001::1 is the IPV6 address and 4060 is the port.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
• "KEY_DNS_SERVER": DNS IP address[:port] where port is optional. If the address is notprovided it will be read from PCO exchange during PDN creation, DHCP server or UICC in thatorder. In case of IPV6 it must be enclosed in square brackets []. E.g. [2001::1]:4060 where 20
01::1 is the IPV6 address and 4060 is the port.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
• "KEY_SIP_TIMER_T1": the Timer_T1 represents an estimate of the round trip time of the IMS
traffic (UE <-> P-CSCF).
<value> is a numeric parameter measured in milliseconds. The range is [1- 4294967295]
while the factory-programmed and default value depend on the +UMNOCONF command:
2000 if the <MNO> parameter is set to 0 (regulatory MNO), 3000 if the <MNO> parameteris set to 3 (Verizon).
• "KEY_SIP_TIMER_T2": the Timer_T2 represents an estimate for the maximum retransmit
interval for SIP non-INVITE requests and INVITE responses.
<value> is a numeric parameter measured in milliseconds. The range is [1-4294967295]
while factory-programmed and the default value is 16000.
• "KEY_SIP_TIMER_T4": the Timer_T4 represents an estimate for maximum lifetime of a SIP
message.
<value> is a numeric parameter measured in milliseconds. The range is [1-4294967295]
while the factory-programmed and default value is 17000.
• "KEY_SIP_TIMER_TF": the Timer_TF represents the timeout of a SIP non INVITE transaction,
defined in RFC3261.
<value> is a numeric parameter measured in milliseconds. The range is [1-4294967295] andthe default value 64000. Verizon typically uses a value of 30000.
• "KEY_MTU_SIZE": the Maximum Transmission Unit (MTU) size as expected by the network
operators to control the IMS message fragmentation.
<value> is a numeric parameter measured in bytes. The range is [0-65535] while thefactory-programmed and default value is 1500.
• "KEY_IMS_CLIENT_PORT": port used by the UE's SIP application.
<value> is a numeric parameter. The range is [200-65535]. The factory-programmed anddefault value is 5060.
• "KEY_REG_EXPIRES": IMS registration expiration time that will be requested.
<value> is a numeric parameter measured in seconds. The range is [1-4294967295] while
the factory-programmed and default value is 600000.
• "KEY_MAX_REG_EXPIRES": maximum IMS registration expiration time that will be
requested. On receiving a "423 interval too brief" response to a REGISTER, the next REGISTER
request will contain an expire value which will be the minimum between the input value andthe received response.
<value> is a numeric parameter measured in seconds. The range is [1-4294967295] while
the factory-programmed and default value is 600000.
• "KEY_RETRY_BASE_TIME": Retry Base Time used for the backoff timer.
<value> is a numeric parameter measured in seconds. The range is [1-2147483] while thefactory-programmed and default value is 30.
• "KEY_RETRY_MAX_TIME": Retry Max Time used for the backoff timer.
<value> is a numeric parameter measured in seconds. The range is [1-2147483] while thefactory-programmed and default value is 1800.
• "KEY_REG_BARRED_USER_ID": configures the Use Barred User ID in Registration and DeRegistration feature. If disabled the UE will use the default public user identity provided by
the network (first entry of the P-ASSOCIATED-URI header).
<value> is a string parameter with these allowed values: "true", "false". The factoryprogrammed and default value is "true".
• "KEY_EXPLICIT_UNSUB_REG_EVENT": controls the unsubscription of the Registration
Event Package during deregistration. This feature is required by Verizon.

8 IP Multimedia Subsystem (IMS)

Page 191 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description<value> is a string parameter with these allowed values: "true", "false". The factoryprogrammed and default value is "false".
• "KEY_PCSCF_BACKOFF_PREFERENCE": Backoff on P-CSCF change due to server failure.
The backoff is applied for each server of after the whole list has been tried.
<value> is a string parameter with these allowed values: "LIST" or "INDIVIDUAL". The
factory-programmed and default value is "LIST".
• "KEY_SMSC_NUMBER": SMSC phone number.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
• "KEY_SMSC_URI": SMSC URI. It should be a SIP or telephonic URI.
<value> is a string parameter. The factory-programmed and default value is an empty
string.
• "KEY_MO_SMS_FORMAT": SMS format to be used for Mobile Originated SMS.
<value> is a string parameter with these allowed values: "3gpp" or "3gpp2". The factoryprogrammed and default value is "3gpp".
• "KEY_MO_SMS_ENCODING": SMS encoding to be used for Mobile Originated SMS.
<value> is a string parameter with these allowed values: "gsm7", "ascii7", "ucs2". The
factory-programmed and default value is "gsm7".
• "KEY_QOS_PREFERENCE": QoS Precondition during SIP call set-up.
<value> is a string parameter with these allowed values: "AUTO" or "NONE". The factoryprogrammed and default value is "AUTO".
• "KEY_PDP_BEARER_MODE": QoS Allocation Mode determines whether the UE or the NW will
request the QoS reservation.
<value> is a string parameter with these allowed values: "UE", "NW","AUTO". The factoryprogrammed and default value is "AUTO". In "AUTO" mode the UE will initiate the QoS
allocation only if the NW does not.
• "KEY_DOMAIN_PREFERENCE": Domain Preference for the IMS Service Continuity feature.
<value> is a string parameter with these allowed values: "CS_ONLY", "PS_ONLY", "CS_PREF", "PS_PREF". The factory-programmed and default value is "PS_PREF".
• "KEY_SMS_PREFERENCE": preferred service used for MO SMS.
<value> is a string parameter with these allowed values: "IMS_PREF", "CS_PREF", "CS_ONLY", "PS_ONLY". The factory-programmed and default value is "IMS_PREF".
• "KEY_IMS_SUPPORT": configures the IMS support and registration.
<value> is a string parameter with the following allowed values: "true" or "false". The
factory-programmed and default value is "true".
• "KEY_IMS_MWI_SUPPORT": configures the MWI Event Package Support for IMS.
<value> is a string parameter with these allowed values: "true" or "false". The factoryprogrammed and default value is "true".
• "KEY_IMS_SIGCOMP_SUPPORT": configures the Signal Compression Support for IMS
Signaling feature.
<value> is a string parameter with these allowed values: "true" or "false". The factoryprogrammed and default value is "false".
• "KEY_IMS_RAT": configures the RAT allowed for IMS registration.
<value> is a string parameter with these allowed values:oo<more_values> Numeric"all": IMS will try to register on all the supported RATs
"lteonly" (factory-programmed value): IMS will try to register on LTE RAT only
Since Verizon configuration is LTE only then this key must be set to "lteonly" to prevent
useless IMS registration tries when in 3G (roaming).
• "KEY_IMS_SMS_SEND_OK_WRITE_UICC": allows the storing of SMSes correctly sent.
<value> is a string parameter with these allowed values: "true", "false". The factoryprogrammed and default value is "false".
• "KEY_IMS_SMS_SEND_NOK_WRITE_UICC": allows the storing of SMSes not sent due to
network errors.
<value> is a string parameter with these allowed values: "true", "false". The factoryprogrammed and default value is "false".
Sets the configuration update:•••

UBX-13002752 - R67

0 (default value): the input configuration is immediately set and saved to NVM
1: the configuration is saved to NVM; the IMS client will wait for other parameters to takeeffect. When inputting the final configuration command then <more_values> should be set
to zero for the whole configuration to take effect
2: the input configuration is immediately set but it is not saved to NVM

8 IP Multimedia Subsystem (IMS)

Page 192 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 3: the configuration is volatile; the IMS client will wait for other parameters to take effect.
When inputting the final configuration command then <more_values> should be set to zerofor the whole configuration to take effect8.5.4 Notes
TOBY-L201 / MPCI-L201• The "KEY_MO_SMS_FORMAT" configuration is not stored in NVM.

8.6 Read IMS configuration +UIMSRCONF+UIMSRCONF
Modules
Attributes

TOBY-L201 MPCI-L201
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

8.6.1 Description
Read configuration parameters related to IMS.

8.6.2 Syntax
Type
Set

Test

SyntaxAT+UIMSRCONF=<key_name>Response+UIMSRCONF: <value>

ExampleAT+UIMSRCONF="KEY_MTU_SIZE"OK+UIMSRCONF: 2500

AT+UIMSRCONF=?

+UIMSRCONF: (list of
supported <key_name>s)OK

OK+UIMSRCONF: ("KEY_IMS_PDP_APN","KEY_
IMS_PDP_CID","KEY_IMS_PDP_TYPE","KEY_
AUTH_TYPE_AKA","KEY_AUTH_TYPE_AKAV2","KEY_AUTH_TYPE_MD5","KEY_SEC_AGREE","KEY_XDM_URL","KEY_PASSWORD","KEY_
HOME_NETWORK_DOMAIN","KEY_PRIVATE_IDENTITY","KEY_PUBLIC_IDENTITY", "KEY_CONFIG_SOFT_SIM","KEY_CONFIG_SOFT_
SIM_K","KEY_CONFIG_SOFT_SIM_OP","KEY_PCSCF_SERVER_ADDRESS","KEY_DNS_SERVER","KEY_SIP_TIMER_T1","KEY_SIP_
TIMER_T2", "KEY_SIP_TIMER_T4","KEY_SIP_
TIMER_TF","KEY_MTU_SIZE","KEY_IMS_
CLIENT_PORT","KEY_REG_EXPIRES","KEY_
MAX_REG_EXPIRES","KEY_RETRY_BASE_
TIME","KEY_RETRY_MAX_TIME", "KEY_
REG_BARRED_USER_ID","KEY_EXPLICIT_UNSUB_REG_EVENT","KEY_PCSCF_BACKOFF_
PREFERENCE","KEY_SMSC_NUMBER","KEY_SMSC_URI","KEY_MO_SMS_FORMAT","KEY_MO_SMS_ENCODING", "KEY_QOS_
PREFERENCE","KEY_PDP_BEARER_MODE","KEY_DOMAIN_PREFERENCE","KEY_SMS_
PREFERENCE","KEY_IMS_SUPPORT","KEY_
IMS_MWI_SUPPORT","KEY_IMS_SIGCOMP_SUPPORT","KEY_IMS_RAT")
OK

8.6.3 Defined values
Parameter<key_name><value>UBX-13002752 - R67

TypeStringStringDescription
See the +UIMSCONF parameter description
See the +UIMSCONF parameter description

8 IP Multimedia Subsystem (IMS)

Page 193 of 1001

u-blox cellular modules - AT commands manual

8.7 IMS registration information +CIREG+CIREG
Modules
Attributes

TOBY-L201 MPCI-L201
LARA-R202 LARA-R203 LARA-R204 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

8.7.1 Description
Configures the IMS registration information. Depending on the <n> parameter value a URC can be issued when
the MT's IMS registration information changes:• +CIREGU: <reg_info> if <n>=1• +CIREGU: <reg_info>[,<ext_info>] if <n>=2
The read command provides the same information issued by the URC together with the current value of <n>parameter.

8.7.2 Syntax
Type
Set

SyntaxAT+CIREG=[<n>]Response
OK

Read

AT+CIREG?

OK+CIREG: <n>,<reg_info>[,<ext_info>] +CIREG: 1,1

Test

AT+CIREG=?

OK+CIREG: (list of supported <n>s)

OK+CIREG: (0,1)

OK+CIREGU: <reg_info>[,<ext_info>]

OK+CIREGU: 0

URC

ExampleAT+CIREG=1

8.7.3 Defined values
Parameter<n><reg_info><ext_info>

Type
NumberNumberNumberDescription
Configures the reporting of changes in the MT's IMS registration information:• 0: reporting URC disabled• 1: reporting URC +CIREGU: <reg_info> enabled• 2: extended reporting URC +CIREGU: <reg_info>,<ext_info> enabled
Indicates the IMS registration status. The MT is seen as registered as long as one ormore of its public user identities are registered with any of its contact addresses, see
3GPP TS 24.229 [81].
• 0: not registered• 1: registered
The parameter shows whether one or more of the public user identities are registered
Numeric value in hexadecimal format. The range goes from 1 to FFFFFFFF. It is a sumof hexadecimal values, each representing a particular IMS capability of the MT. The
MT can have IMS capabilities not covered by the below list. This parameter is notpresent if <reg_info>=0.
•

1: RTP-based transfer of voice according to MMTEL, see 3GPP TS 24.173 [79]. Thisfunctionality can not be indicated if the UE is not available for voice over PS, see
3GPP TS 24.229 [81]• 2: RTP-based transfer of text according to MMTEL, see 3GPP TS 24.173 [79]• 4: SMS using IMS functionality, see 3GPP TS 24.341 [80]
• 8: RTP-based transfer of video according to MMTEL, see 3GPP TS 24.173 [79]The hexadecimal values 10, 20, 40 and 80000 are reserved.
It shows the status of the MT's IMS capabilities. For <ext_info>, all relevant values
are always summarized and reported as a complete set of IMS capabilities in the
URC.

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 194 of 1001

u-blox cellular modules - AT commands manual

8.8 IMS network reporting +CIREP+CIREP
Modules
Attributes

LARA-R202 LARA-R203 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

8.8.1 Description
Enables or disables the reporting of SRVCC handover information (see 3GPP TS 24.237 [126]) and of IMS VoiceOver PS sessions indicator information, by means of these URCs:• +CIREPI: IMS Voice Over PS sessions (IMSVOPS) supported indication from the network• +CIREPH: Single Radio Voice Call Continuity (SRVCC) handover information

8.8.2 Syntax
Type
Set

SyntaxAT+CIREP=<reporting>Response
OK

ExampleAT+CIREP=1

Read

AT+CIREP?

+CIREP: <reporting>,<nwimsvops>

OK+CIREP: 1,1

Test

AT+CIREP=?

OK+CIREP: (list of supported<reporting>s)
OK+CIREPI: <nwimsvops>+CIREPH: <srvcch>

URC
URC

OK
+CIREP: (0,1)
OK+CIREPI: 1+CIREPH: 2

8.8.3 Defined values
Parameter<reporting>Type
Number<nwimsvops>

Number<srvcch>NumberDescription
Enables or disables reporting of changes in the IMS voice over PS session supported
indication received from the network and reporting of SRVCC handover information:• 0 (default value): reporting disabled• 1: reporting enabled
Gives the last IMS Voice Over PS session(IMSVOPS) supported indication received
from network:• 0: IMSVOPS support indication is not received from network, or is negative• 1: IMSVOPS support indication as received from network is positive
SRVCC handover information:• 0: PS to CS SRVCC handover has started in the CS domain ("Handover Command"indicating SRVCC received)• 1: PS to CS SRVCC handover successful ("Handover Complete" sent)• 2: PS to CS SRVCC handover cancelled ("Handover Failure" sent)• 3: PS to CS SRVCC handover, general non specific failure. It might be used e.g. in thecase of handover cancellation as specified in 3GPP TS 24.301 [68] subclause 6.6.2

8.8.4 Notes
LARA-R203• The +CIREPH URC is not issued.

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 195 of 1001

u-blox cellular modules - AT commands manual

8.9 Availability for SMS using IMS +CASIMS+CASIMS
Modules
Attributes

TOBY-L201 MPCI-L201
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

8.9.1 Description
Informs the MT whether the UE is currently available for SMS using IMS (see 3GPP TS 24.229 [81]).
The information can be used by the MT to determine the need to remain attached for non-EPS services, as
defined in 3GPP TS 24.301 [68].

8.9.2 Syntax
Type
Set

SyntaxAT+CASIMS=[<state>]

Response
OK

ExampleAT+CASIMS=1

Read

AT+CASIMS?

+CASIMS: <state>

OK+CASIMS: 1

Test

AT+CASIMS=?

OK+CASIMS: (list of supported<state>'s)

OK+CASIMS: (0,1)
OKOK

8.9.3 Defined values
Parameter<state>Type
NumberDescription
Status configuration:••

0 (default value): SMS using IMS is not available
1: SMS using IMS is available

8.10 UE's Mobility Management IMS Voice Termination+CMMIVT+CMMIVTModules
Attributes

LARA-R202 LARA-R203 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

8.10.1 Description
Sets the MT to perfom additional procedures as specified in 3GPP TS 24.008 [12] and 3GPP TS 24.301 [68] tosupport terminating access domain selection by the network.
The read command returns the setting, independent of the current serving cell capability and independent of
the current serving cell's access technology.
See 3GPP TS 24.167 [88], subclause 5.31 for the definition of the UE's mobility management IMS voice
termination values.

8.10.2 Syntax
Type
Set

SyntaxAT+CMMIVT=[<setting>]

Response
OK

ExampleAT+CMMIVT=2

Read

AT+CMMIVT?

+CMMIVT: <setting>OK+CMMIVT: 1

Test

AT+CMMIVT=?

OK+CMMIVT: (list of supported<setting>s)

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

OK+CMMIVT: (1-2)

Page 196 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

ExampleOK

8.10.3 Defined values
Parameter<setting>

Type
NumberDescription
Indicates the mobility management IMS voice termination preference of the UE:• 1 (default value): Mobility Management for IMS Voice Termination disabled• 2 (factory-programmed value): Mobility Management for IMS Voice Termination
enabled8.11 UE's voice domain preference E-UTRAN +CEVDP+CEVDP
Modules
Attributes

LARA-R202 LARA-R203 LARA-R211 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
Yes
NVM
No

Response time-Error reference+CME Error

8.11.1 Description
Sets the MT to operate according to the specified voice domain preference for mobile originated calls in
E-UTRAN. The read command returns the setting, independent of the current serving cell capability andindependent of the current serving cell's access technology. The technology used for mobile terminated calls
is selected by the network and therefore is independent from the +CEVDP setting.
See 3GPP TS 24.167 [88], subclause 5.27 for the definition for the UE's voice domain preference for
E-UTRAN.
Reboot the module (by issuing AT+CFUN=16) or perform a AT+CFUN=0 / AT+CFUN=1 cycle to apply the
new configuration.

8.11.2 Syntax
Type
Set

Syntax+CEVDP=[<setting>]

Response
OK

ExampleAT+CEVDP=2

Read

AT+CEVDP?

+CEVDP: <setting>

OK+CEVDP: 3

Test

AT+CEVDP=?

+CEVDP: (list of supported<setting>s)

OK+CEVDP: (1-4)
OKOK

8.11.3 Defined values
Parameter<setting>

Type
NumberDescription
UE voice domain preference. Allowed values:• 1: CS voice only
• 2: CS voice preferred, IMS PS voice as secondary• 3 (factory-programmed and default value): IMS PS voice preferred, CS voice as
secondary• 4: IMS PS voice only

8.11.4 Notes
LARA-R203• Only <setting>=4 (factory-programmed value) is supported.

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 197 of 1001

u-blox cellular modules - AT commands manual

8.12 Domain configuration for MO SMS messages +UISMS+UISMS
Modules
Attributes

LARA-R204
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

8.12.1 Description
Configures for routing the outgoing SMS messages either over IMS or not over IMS.
If the selected configuration is IMS, then IMS settings will have higher priority while sending messages, other
2G/3G settings for MO SMS (e.g. +CGSMS settings) will be ignored.

8.12.2 Syntax
Type
Set

SyntaxAT+UISMS=<mode>

Response
OK

ExampleAT+UISMS=1

Read

AT+UISMS?

+UISMS: <mode>

OK+UISMS: 1

Test

AT+UISMS=?

OK+UISMS: (list of supported<mode>s)OK+UISMS: (0-1)
OKOK

8.12.3 Defined values
Parameter<mode>

Type
NumberDescription
Allowed values:• 0: SMS messages are not sent over IMS• 1 (default value): SMS messages are preferably sent over IMS

8.13 MO SMS mode configuration +UICMGSMODE+UICMGSMODE
Modules
LARA-R204
SyntaxAttributes
full

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

8.13.1 Description
Configures the SMS mode to 3GPP or 3GPP2 for outgoing SMS messages. The command is supported when
SMS over IMS is enabled, see +UISMS.
The setting is also managed (can be read and written) over the air via OMA-DM.

8.13.2 Syntax
Type
Set

SyntaxAT+UICMGSMODE=<mode>

Response
OK

Test

AT+UICMGSMODE=?

+UICMGSMODE: (list of supported<mode>s)

ExampleAT+UICMGSMODE=2
OK+UICMGSMODE: (1,2)
OKOK

8.13.3 Defined values
Parameter<mode>

UBX-13002752 - R67

Type
NumberDescription
Allowed values:• 1: 3GPP mode

8 IP Multimedia Subsystem (IMS)

Page 198 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 2 (default and factory-programmed value): 3GPP2 mode

8.14 Send 3GPP2 SMS message +UCMGS3GPP2+UCMGS3GPP2
Modules
LARA-R204
SyntaxAttributes
full

PIN requiredNo

Settings saved Can be aborted
No
No

Response time Error reference
Up to 3 min (<1 +CME Errors for prompt ">"when present)

8.14.1 Description
Sends a message from a DTE to the network (SMS-SUBMIT) in 3GPP2 binary format. The command is similar
to +CMGS but only PDU mode is accepted. The PDU message length can be up to 256 bytes, the format is
specified in 3GPP2 C.S0015-0 [121].
An error result code is returned when SMS over IP network option is not set, see +UISMS.

8.14.2 Syntax
Type
Set

SyntaxAT+UCMGS3GPP2=<length>,<type><CR>

ResponseOK> 00000210020102000004070
2c616090d5c8c08250003200
000011e110539b4d069dc830
f3c7a74b7415b2f2d3eb7ee41d37a0
ad97969f5bf70 <Ctrl-Z><PDU><Ctrl-Z/ESC>

Test

ExampleAT+UCMGS3GPP2=57,1,<CR>

AT+UCMGS3GPP2=?

OK

8.14.3 Defined values
Parameter<length><type>

Type
NumberNumber<PDU>

StringDescription
PDU's length in octets
Allowed values:• 0: invalid• 1: point to point• 2: acknowledge• 3: broadcast
Protocol Data Unit: each 8-bit octet of the PDU must be written as two IRA character
long hexadecimal numbers, e.g. octet with integer value 42 must be written as two
characters 2A (IRA 50 and 65). The PDU format is specified in 3GPP2 C.S0015-0 [121].

8.15 Enable/disable the 3GPP2 SMS URC +UCMT3GPP2+UCMT3GPP2
Modules
Attributes

LARA-R204
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

8.15.1 Description
Enables or disables the +UCMT3GPP2 URC that indicates the reception of a new MT SMS in 3GPP2 format.
The URC is similar to +CMT (see the +CNMI AT command) but the syntax is different: see 3GPP2 C.S0015-0[121] for a full description of the 3GPP2 SMS messages.
If the TA-TE link is busy the URCs are buffered and then flushed, otherwise they are forwarded directly to the
TE.
3GPP2 SMS messages are not stored in the memory so always enable the +UCMT3GPP2 URC reception
in order to be notified of a new 3GPP2 SMS.

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 199 of 1001

u-blox cellular modules - AT commands manual

8.15.2 Syntax
Type
Set

SyntaxAT+UCMT3GPP2=<type>

Response
OK

Test

AT+UCMT3GPP2=?

+UCMT3GPP2: (list of supported<type>s)OK
Text mode (+CMGF=1):

URC+UCMT3GPP2: <message_id>,<oa>,<scts>,[<priority>],[<privacy>],[<callback_number>],<encoding>,[<status>],<type>[,<num_sms>,<part>,<reference>],<length><CR><LF><text>
PDU mode (+CMGF=0):+UCMT3GPP2: <length><CR><PDU>

ExampleAT+UCMT3GPP2=1
OK+UCMT3GPP2: (0-1)
OK+UCMT3GPP2: 56911,"+393290
284444","16/12/15,09:11:36",2,1,"+393290285555",9,,1,,,,4
Test+UCMT3GPP2: 360000021002020D80
85181899199A1A9B1B9C1C80080E0
0031000000107482F4194DEF830

8.15.3 Defined values
Parameter<type>

Type
Number<message_id><oa><scts><priority>

NumberStringStringNumber<privacy>

Number<callback_number><encoding>StringNumber<status>Number<type>

NumberUBX-13002752 - R67

Description
Allowed values:• 0 (default value): URC disabled• 1: URC enabled
Message Identifier
Originating address
Service center time stamp in format "yy/MM/dd,hh:mm:ss"
Priority:• 0: normal• 1: interactive• 2: urgent• 3: emergency
Privacy:• 0: not restricted• 1: restrictive• 2: confidential• 3: secret
Callback number
Text encoding:• 0: octet, unspecified• 2: ASCII7• 3: IA5• 4: UCS2• 7: Latin/Hebrew• 8: Latin (ISO 8859-1)• 9: GSM7
If the SMS encoding is different from the ones reported above, the message is always
displayed in PDU mode.
Consists of one hexadecimal digit. If present it indicates the message status or if an
SMS error has occurred.
Message type:• 0: reserved• 1: deliver• 2: submit• 3: cancellation• 4: delivery acknowledgment• 5: user acknowledgment

8 IP Multimedia Subsystem (IMS)

Page 200 of 1001

u-blox cellular modules - AT commands manual

ParameterType<num_sms><part><reference><length>NumberNumberNumberNumber<text>

String<PDU>

StringDescription• 6: read acknowledgment• 7: deliver report• 8: submit report
Total number of SMS
Fragment part number
Reference ID
Two meanings:• In text mode: number of characters• In PDU mode: PDU's length in octets
Text of the SMS converted in the current character set in use (see the +CSCS AT
command).
Protocol Data Unit: each 8-bit octet of the PDU must be written as two IRA character
long hexadecimal numbers, e.g. octet with integer value 42 must be written as two
characters 2A (IRA 50 and 65). The PDU format is specified in 3GPP2 C.S0015-0 [121].

8.15.4 Notes
LARA-R204• On LARA-R204-02B-00, LARA-R204-02B-01 only the PDU mode is supported.

UBX-13002752 - R67

8 IP Multimedia Subsystem (IMS)

Page 201 of 1001

u-blox cellular modules - AT commands manual

9 Device lock9.1 Enter PIN +CPIN+CPIN
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time< 10 sError reference+CME Error

9.1.1 Description
Enter PIN. If no PIN request is pending, the corresponding error code is returned. If a wrong PIN is given threetimes, the PUK must be inserted in place of the PIN, followed by the <newpin> which replaces the old pin in
the SIM.

9.1.2 Syntax
Type
Set

SyntaxAT+CPIN=<pin>[,<newpin>]Response
OK

ExampleAT+CPIN="0933"

Read

AT+CPIN?

+CPIN: <code>

OK+CPIN: SIM PIN

Test

AT+CPIN=?

OK
OK

OK

9.1.3 Defined values
Parameter<pin>, <newpin>

Type
StringDescription
4-to-8 characters long string of decimal digits.
If only PIN is required, <newpin> is not to be entered.
If PUK is required, <pin> must be the PUK and <newpin>, the new PIN code, must beentered as well.

<code>

String

•
•
•
•
•
•
•
•
•
•

READY: MT is not pending for any password
SIM PIN: MT is waiting SIM PIN to be given
SIM PUK: MT is waiting SIM PUK to be given
SIM PIN2: MT is waiting SIM PIN2 to be given
SIM PUK2: MT is waiting SIM PUK2 to be given
PH-NET PIN: MT is waiting network personalization password to be given
PH-NETSUB PIN: MT is waiting network subset personalization password to be
given
PH-SP PIN: MT is waiting service provider personalization password to be given
PH-CORP PIN: MT is waiting corporate personalization password to be given
PH-SIM PIN: MT is waiting phone to SIM/UICC card password to be given

9.1.4 Notes••

The command needs the SIM module to work correctly
If PIN is not inserted the following situation can occur:
Command
AT+CMEE=2
AT+COPS=0
AT+CMEE=0
AT+COPS=0•

Response
OK+CME ERROR: SIM PIN required
OK
ERROR

To change the PIN the user must use the AT+CPWD="SC",<old_pin>,<new_pin> command (see +CPWD
AT command for details). Example:
AT+CPWD="SC","1234","4321"

UBX-13002752 - R67

9 Device lockPage 202 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• After changing PIN (by means of +CPWD or D), the module does not require to insert the PIN if the PIN1
request is active and the PIN has not been yet inserted.
LARA-R2 / TOBY-R2• After changing PIN (by means of +CPWD or D), the module requires to insert the PIN if the PIN1 request
is active and the PIN has not been yet inserted.

9.2 Read remaining SIM PIN attempts +UPINCNT+UPINCNT
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

9.2.1 Description
Reads the remaining attempts for SIM PIN, SIM PIN2, SIM PUK, SIM PUK2 and some <lock_type>s.

9.2.2 Syntax
Type
ActionSyntaxAT+UPINCNT

Response
Example+UPINCNT: <PIN_attempts>,<PIN2_ +UPINCNT: 3,3,10,10
attempts>,<PUK_attempts>,
OK<PUK2_attempts>

Set

AT+UPINCNT=<lock_type>

OK+UPINCNT: <lock_type>,<Attempts_left>,<Timer_Penalty>

AT+UPINCNT=1+UPINCNT: 1,3,0

OK
Test

AT+UPINCNT=?

OK[+UPINCNT: (list of supported <lock_ OK
type>s)]OK

9.2.3 Defined values
Parameter<PIN_attempts><PIN2_attempts><PUK_attempts><PUK2_attempts><lock_type>

Type
NumberNumberNumberNumberNumber<Attempts_left><Timer_Penalty>

NumberNumberDescription
Number of remaining attempts to enter PIN
Number of remaining attempts to enter PIN2
Number of remaining attempts to enter PUK
Number of remaining attempts to enter PUK2
Allowed values:• 1: request number of remaining attempts to enter for PIN 1• 2: request number of remaining attempts to enter for PIN 2• 3: request number of remaining attempts to enter for PUK 1• 4: request number of remaining attempts to enter for PUK 2• 5: request number of remaining attempts to enter for Network Operator Lock
• 6: request number of remaining attempts to enter for Network-Subset Lock
• 7: request number of remaining attempts to enter for Service Provider Lock
• 8: request number of remaining attempts to enter for Corporate lock• 9: request number of remaining attempts to enter for IMSI lockNumber of attempts left before blocked (0 means blocked, or not used)
Provides the time in minutes to wait before the possible next tries

9.2.4 Notes•

The PIN insertion is not mandatory in the action command and in the set command for <PIN_attempts>=
1, 2, 3, 4.

TOBY-L2 / MPCI-L2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• The set command is not supported.

UBX-13002752 - R67

9 Device lockPage 203 of 1001

u-blox cellular modules - AT commands manual•

The information text response to the test command is not provided.

SARA-G4• The set and test command are not supported.

9.3 Facility lock +CLCK+CLCK
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time
full
Yes
No
Yes
Up to 3 min

Error reference+CME Error

9.3.1 Description
Locks, unlocks or interrogates an MT or a network facility <fac>. A password is normally needed to do suchactions. When querying the status of a network service (<mode>=2) the information text response for "notactive" case (<status>=0) is returned only if the service is not active for any <class>. Instead when querying
the status of a network service (<mode>=2) asking for a specific <class>, the DUT sends a generic request.
The command can be aborted if network facilities are set or interrogated.
For <fac> "PN", "PU", "PP", "PC" and "PS" only <mode>=0 and <mode>=2 (unlock and query status) arealways supported.
For <fac> "PN", "PU", "PP", "PC" and "PS" <mode>=1 (lock status) is supported only if proper re-activation
characteristic is enabled during personalization.

9.3.2 Syntax
Type
Set

SyntaxAT+CLCK=<fac>,<mode>[,<passwd>[,<class>]]

Response
OK

ExampleAT+CLCK="SC",1,"0933"

orOK+CLCK: <status>[,<class1>][...][+CLCK: <status>[,<class1>]]
Test

AT+CLCK=?

OK+CLCK: (list of supported <fac>s)OK+CLCK: ("SC","PN","PU","PP","PC","PS","FD","AO","OI","OX","AI","IR","AB","AG","AC")OK

9.3.3 Defined values
Parameter<fac>

UBX-13002752 - R67

TypeStringDescription
Facility values. Allowed values (for the applicability to the module see Table 16):• "SC": SIM (PIN enabled/disabled)• "PN": Network Personalisation (see the 3GPP TS 22.022 [27])• "PU": network sUbset Personalisation (see the 3GPP TS 22.022 [27])• "PP": service Provider Personalisation (see the 3GPP TS 22.022 [27])• "PC": Corporate Personalisation (see the 3GPP TS 22.022 [27])• "PS": SIM/USIM Personalisation (see the 3GPP TS 22.022 [27])• "FD": SIM fixed dialling phonebook feature
o TOBY-L2 / MPCI-L2 - PIN2 is required as <passwd>
o TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 - PIN2 is required if the PIN2 authentication has not been done during
the current session• "AO": BAR (Bar All Outgoing Calls)• "OI": BOIC (Bar Outgoing International Calls)

9 Device lockPage 204 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• "OX": BOIC-exHC(Bar Outgoing International Calls except to Home Country)• "AI": BAIC (Bar All Incoming Calls)• "IR": BIC-Roam (Bar Incoming Calls when Roaming outside the home country)• "AB": All Barring services (applicable only for <mode>=0)• "AG": All outGoing barring services (applicable only for <mode>=0)• "AC": All inComing barring services (applicable only for <mode>=0)• "CS": CNTRL (lock CoNTRoL surface (e.g. phone keyboard)) (see the 3GPP TS 27.0
07 [2])• "PF": Lock Phone to the very First inserted SIM/UICC card (see the 3GPP TS 27.00
7 [2])• "NT": Barr incoming calls from numbers Not stored to TA memory (see the 3GPP
TS 27.007 [2])• "NM": Barr incoming calls from numbers Not stored to MT memory (see 3GPP TS
27.007 [2])• "NS": Barr incoming calls from numbers Not stored to SIM/UICC memory (see the
3GPP TS 27.007 [2])• "NA": Barr incoming calls from numbers Not stored in any memory (see the 3GPP
TS 27.007 [2])<mode>

Number•••<status>Number<passwd>

String<class>Number• 0: not active• 1: active
Shall be the same as password specified for the facility from the MT user interface orwith the +CPWD command
Sum of numbers each representing a class of information. The default value is 7
(voice + data + fax):• 1: voice• 2: data• 4: FAX• 8: short message service• 16: data circuit sync
• 32: data circuit async• 64: dedicated packet access• 128: dedicated PAD access

0: unlock
1: lock
2: query status

9.3.4 Notes
Module series
TOBY-L4
TOBY-L2 / MPCI-L2
TOBY-L210-60S /MPCI-L210-60S /MPCI-L210-63S
LARA-R2 / TOBY-R2
SARA-U2 / LISA-U2
LISA-U1
SARA-G4
SARA-G3
LEON-G1

SCx
x
x

PN PU PP
x
x
x
x
x
x
x

PC PS FD AO OI
x
x
x
x
x
x
x
x
x
x
x

OX AI
x
x
x
x

IR
x
x

AB AG AC CS PF NT NM NS NA
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x

x

x

x

x

x

Table 16: Lock applicability (<fac> allowed values)
TOBY-L2 / MPCI-L2• Reboot the module to make effective the unlock configuration.
TOBY-L200 / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / MPCI-L200 / MPCI-L220• The FDN check for PS data calls is not supported.

UBX-13002752 - R67

9 Device lockPage 205 of 1001

u-blox cellular modules - AT commands manual

TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / MPCI-L200-00S / MPCI-L201 / MPCI-L210-00S• The FDN check for SMS is not supported.
TOBY-L201 / MPCI-L201• In AT&T configuration (see the +UMNOCONF AT command) the FDN check for PS data calls is notsupported.
TOBY-L210-62S / TOBY-L210-65S• <fac>="AO", "OI", "OX", "AI", "IR" are not allowed if the VoLTE service is not available.
LARA-R2 / TOBY-R2• Reboot the module to make effective the lock configuration for <fac>="PN", "PU", "PP", "PC" and "PS".

9.4 Change password +CPWD+CPWD
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
Yes

Response time
Up to 3 min

Error reference+CME Error

9.4.1 Description
Sets a new password for the facility lock function defined by the +CLCK AT command. The command isabortable if a character is sent to the DCE during the command execution.

9.4.2 Syntax
Type
Set

SyntaxAT+CPWD=<fac>,<oldpwd>,<newpwd>

Response
OK

ExampleAT+CPWD="SC","0933","0934"

Test

AT+CPWD=?

+CPWD: list of available (<fac>,<pwdlength>s)OK+CPWD: ("SC",8),("P2",8),("AO",4),("OI",4),("OX",4),("AI",4),("IR",4),("AB",4),("AG",4),("AC",4)OK

OK

9.4.3 Defined values
Parameter<fac><oldpwd><newpwd><pwdlength>

Type
StringStringStringNumberDescription"P2" SIM PIN2; see the +CLCK command description for other values
Old password
New password
Length of password (digits)

9.4.4 Notes•

If the PIN is blocked, an error result code will be provided when attempting to change the PIN code if the
PIN check is disabled through AT+CLCK command.

TOBY-L210-62S / TOBY-L210-65S• <fac>="AO", "OI", "OX", "AI", "IR" are not supported if the VoLTE service is not available (see +CIREG AT
command).
TOBY-L210-60S• <fac>="AO", "OI", "OX", "AI", "IR", "AB", "AG", "AC" and "NS" are not supported.
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.

UBX-13002752 - R67

9 Device lockPage 206 of 1001

u-blox cellular modules - AT commands manual

9.5 Custom SIM lock +USIMLCK+USIMLCK
Modules
Attributes

SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

9.5.1 Description
Allows locking the module to work only with user-defined sets of SIM cards (e.g. a subset of networks, with a
specified SIM card). According to the 3GPP TS 22.022 [27] there are different kinds of lock as follows:• Network• Network Subset• SIM• Service Provider (not supported)• Corporate (not supported)
The module is locked according to user needs even if the SIM card is not inserted or the PIN code is not provided.

9.5.2 Syntax
Type
Set

SyntaxAT+USIMLCK=<facility>,<pers_
data>,<pwd>,<status>

Response
OK

Test

AT+USIMLCK=?

+USIMLCK: (list of supported<facility>s),,,(list of supported<status>)

ExampleAT+USIMLCK="PN","222.01","12345678",1
OK+USIMLCK: ("PN","PU","PS"),,,(0-1)
OKOK

9.5.3 Defined values
Parameter<facility><pers_data>

Type
StringDescription
Personalization type, which can be:

String• "PN" Network personalization• "PU" Networks subset personalization• "PS" SIM/USIM personalization
Data for device personalization. The contents depend on the selected <facility>.
•

If <facility> is "PN":<pers_data> is in the format:"MCC1.MNC1min[-MNC2max][,MCC2.MNC2min[-MNC2max]... [,MCCn.MNCnmin[-MNCnmax]]"•

It contains a list of comma-separated pairs of MCCs and MNC ranges.
o SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - The maximum
number of MCC-MNC personalisations is 10
If <facility> is "PU":<pers_data> is in the format:"MCC1.MNC1min[-MNC2max][,MCC2.MNC2min[-MNC2max]... [,MCC10.MNC10min[-MNC10max]]:MSIN1[,MSIN2...[,MSIN10]]"
It contains a list of comma-separated pairs of MCCs+MNC ranges as above;a list of comma-separated MSIN(s) or ranges of MSINs is appended after the
MCC/MNC range using a ':' as separator. At most 10 personalizations can be
simultaneously configured.
MSINs can be written with wildcards ('*') with the syntax: [*[*]]D1[D2[...]] (onewildcard for each MSIN digit to skip) followed by one or more digits.
It is possible to use ranges of MSIN digits; in this case the minimum andmaximum values should have the same number of wildcard and the same numberof digits.

UBX-13002752 - R67

9 Device lockPage 207 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description
In addition it is possible to concatenate more MSIN ranges with the comma
separator (example: "123.456:56,**70-**72"). In this case all ranges must createa non empty set since MSIN comma separator behavior is an AND operator: an
empty set means that any SIM is accepted• If <facility> is "PS":<pers_data> contains a list of at most 10 IMSIs; the format of the string is: "IMSI1,
IMSI2,...,IMSIn"LISA-U200-00S / SARA-G3 / LEON-G1•••

If <facility> is "PN":<pers_data> contains at most 10 pairs of MCC and MNC
in the following format: "MCC.MNC" separated by colon:"MCC1.MNC1:MCC2.MNC2:...:MCCn.MNCn"
If <facility> is "PU":<pers_data> contains MCC + MNC + a list of at most 10 pairs of the digits 6
and 7 of IMSI; the format of the string is: "MCC.MNC:DD1:DD2:...:DDn" where
DDx represent the sixth and seventh digits of IMSI
If <facility> is "PS":<pers_data> contains a list of at most 10 IMSIs; the format of the string is:"IMSI1:IMSI2:...:IMSIn"<pwd>

StringPassword to enable/disable the personalization. The password length goes from 6 to
16 digits.

<status>Number••0: feature set but disabled
1: feature set and enabled

9.5.4 Notes
•
•
•

•

•

•

The current personalization status can be queried using the AT+CLCK command with the proper facilities<fac> and the query status mode <mode>=2.
At the end of command execution, the module is deregistered from network, reset and rebooted.
A maximum of 5 attempts are allowed if a wrong password is inserted during an unlock operation with
+CLCK command; after that, further unlock operations are blocked. The ME can still be used with theright SIM.
The following error result codes could be provided:
Verbose string+CME ERROR: invalid characters in text
string+CME ERROR: operation not allowed

Numeric code Meaning
25
An error is present in the <pers_data> format+CME ERROR: incorrect password

16

3

The user attempted the module personalization withan already active facility. An unlock operation must be
performed before. Alternatively, an internal driver error
occurred
The password format or length is wrong

If the SIM lock is disabled it is possible to enable the lock with AT+CLCK command providing neededparameters (<fac>, <mode>=1 and the password); otherwise the same personalization type can be
modified at any time by means of AT+USIMLCK command.
If the SIM lock is enabled the same personalization can be modified only if before it has been disabledthrough AT+CLCK command.

UBX-13002752 - R67

9 Device lockPage 208 of 1001

u-blox cellular modules - AT commands manual

10 Phonebook
10.1 Select phonebook memory storage +CPBS+CPBS
Modules

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialYes
No
No

Attributes

Response time
< 35 sError reference+CME Error

10.1.1 Description
Selects a phonebook memory storage for further use in phonebook related commands.
The information text response of the test command depends on SIM dependent parameters (e.g. "EC").

10.1.2 Syntax
Type
Set

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

ReadAT+CPBS?

Test

AT+CPBS=?

ExampleAT+CPBS="SM"OK+CPBS: <storage>[,<used>,<total>] +CPBS: "SM",25,150
OK+CPBS: (list of supported<storages>s)

OK+CPBS: ("SM","FD","LD","SN","EC","ON","BL")OK

OK

10.1.3 Defined values
Parameter<storage>

Type
String<password>

String<used><total>NumberNumberDescription
Phonebook memory storage:• "SM": SIM phonebook (depending on SIM card, it may not be available when the FDN
is enabled)• "AP": USIM application phonebook (depending on SIM card, it may not be available
when the FDN is enabled)• "FD": SIM fixed dialling phonebook (only valid with PIN2)• "LD": SIM last-dialling phonebook• "BN": SIM barred-dialling-number phonebook (only valid with PIN2)• "SN": SIM service-dialling-number phonebook (read only)• "EC": SIM emergency-call-codes phonebook (read only)• "ON": Own number phone-book (read/write); the content is also shown by +CNUM• "BL": Blacklist phonebook (delete only)• "EN": SIM/USIM (or MT) emergency number• "DC": MT dialed calls list (+CPBW may not be applicable for this storage)
For the values allowed by each module series, see Table 17.
PIN2-code required when selecting PIN2-code locked <storage>s above (e.g. "FD"), if
the PIN2 is applicable
Indicates the number of used locations in selected memory
Indicates the total number of locations in selected memory

10.1.4 Notes
Module series
TOBY-L4
TOBY-L2 / MPCI-L2

UBX-13002752 - R67

"SM"
•
•

"AP"
•
•

"FD"
•
•

"LD"
•
•

"BN"
•
•

10 Phonebook

"SN"
•
•

"EC"
•
•

"ON"
•
•

"BL"
•

"EN"
•

"DC"

Page 209 of 1001

u-blox cellular modules - AT commands manual

Module series"SM"
LARA-R211 / LARA-R204 / TOBY- •R2
LARA-R202 / LARA-R203 / LARA- •R220 / LARA-R280
SARA-U2 / LISA-U2 / LISA-U1•
SARA-G4•
SARA-G3 / LEON-G1
•

"AP"
•

"FD"
•

"LD"
•

"BN"
•

"SN"
•

•

•

•

•

•

•

•
•
•

•
•
•

•

•

•

•

•

"EC"

"ON"
•

"BL"
•

•
•
•
•

•
•
•

"EN"
•

"DC"

•
•
•
•

Table 17: Phonebook memory storage (<storage>) allowed values•<storage>="SM" and <storage>="AP" definitions from 3GPP TS 27.007 [2]:o "SM": SIM/UICC phonebook. In the currently selected card slot, if a SIM card is present or if a UICC
with an active GSM application is present, the EFADN under DFTelecom is selected. If a UICC with anactive USIM application is present, the global phonebook, DFPHONEBOOK under DFTelecom is selected.
o "AP": selected application phonebook. In the currently selected card slot, if a UICC with an active
USIM application is present, the application phonebook, DFPHONEBOOK under ADFUSIM is selected.

TOBY-L2 / MPCI-L2• The <password> parameter is required only for updating the PIN2-code locked <storage>s (see the+CPBW AT command) not for reading them (see the +CPBR or +CPBF AT commands).

10.2 Read phonebook entries +CPBR+CPBR
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialYes
No
No

Response time
< 35 sError reference+CME Error

10.2.1 Description
Returns phonebook entries in location number range <index1> ... <index2> from the current phonebook memorystorage selected with +CPBS. If <index2> is left out, only location <index1> is returned. Entry fields returned are:• location number <indexn>• phone number stored there <number> of format <type>• text <text> associated with the number• <group> indicating a group the entry may belong to (if the selected phonebook supports it)• <adnumber> an additional number (of format <adtype>) (if the selected phonebook supports it)• <secondtext> a second text field associated with the number (if the selected phonebook supports it)• <email> an email field (if the selected phonebook supports it)
No text lines are returned for empty (but available) locations.
If the set command is issued to retrieve an entry with an empty <number> from the phonebook:• TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - the entry is returned and the displayed<type> is always 0.
• SARA-G4 - the entry is returned and the actual stored <type> is displayed.
• SARA-G3 / LEON-G1 - the entry is returned only if the actual stored <type> is 128 or 129, otherwise an error
result code is provided.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The wildcard character (?) in the phone number of FDN is allowed.

UBX-13002752 - R67

10 Phonebook

Page 210 of 1001

u-blox cellular modules - AT commands manual

10.2.2 Syntax
Type
Set

SyntaxAT+CPBR=<index1>[,<index2>]

Response[+CPBR: <index1>,<number>,<type>,<text>[,<group>[,<adnumber>[,<adtype>[,<secondtext>[,<email>[,<sip_uri>[,<tel_uri>]]]]][...][+CPBR: <index2>,<number>,<type>,<text>[,<group>[,<adnumber>[,<adtype>[,<secondtext>[,<email>[,<sip_uri>[,<tel_uri>]]]]]]]

Test

AT+CPBR=?

ExampleAT+CPBR=1,4+CPBR: 1,"040123456",129,"RossiCarlo"+CPBR: 2,"040123457",129,"RossiMario"+CPBR: 4,"040123458",129,"RossiGiuseppe"
OK

OK+CPBR: (list of supported <index>s), +CPBR: (1-100),20,18<nlength>,<tlength>[,<glength>[,OK<alength>[,<slength>[,<elength>[,<siplength>[,<tellength>]]]]]]
OK

10.2.3 Defined values
Parameter<index1>, <index2>,<index><number><type><text><group><adnumber><adtype><secondtext><email><sip_uri>Type
NumberDescription
Range of location numbers of phonebook memory

StringNumberStringStringStringNumberStringStringString<tel_uri>

String<nlength><tlength><glength><alength><slength><elength><siplength><tellength>

NumberNumberNumberNumberNumberNumberNumberNumberPhone number of format <type>Type of address octet (see the 3GPP TS 24.008 [12] subclause 10.5.4.7)
Text associated with the phone number of maximum length <tlength>Group the phonebook entry may belong to, of maximum length <glength>
Additional phone number of format <adtype>Type of address octet (see the 3GPP TS 24.008 [12] subclause 10.5.4.7)
Second text associated with the number, of maximum length <slength>
Email of maximum length <elength>
Field of maximum length <siplength>; character set as specified by the +CSCS AT
commandPhone number of maximum length <tellength>; character set as specified by the+CSCS AT command
Maximum length of field <number>
Maximum length of field <text>
Maximum length of field <group>
Maximum length of field <adnumber>
Maximum length of field <secondtext>
Maximum length of field <email>Maximum length of field <sip_uri>
Maximum length of field <tel_uri>

10.2.4 Notes•

The <sip_uri>, <tel_uri>, <siplength> and <tellength> parameters are not supported.

SARA-G4 / SARA-G340 / SARA-G350 / LEON-G1• <group>, <adnumber>, <adtype>, <secondtext>, <email>, <glength>, <alength>, <slength>, <elength>
are not supported.

UBX-13002752 - R67

10 Phonebook

Page 211 of 1001

u-blox cellular modules - AT commands manual

10.3 Find phonebook entries +CPBF+CPBF
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialYes
No
No

Response time
< 35 sError reference+CME Error

10.3.1 Description
Returns the phonebook entries from the current phonebook memory storage (previously selected by +CPBS),
whose alphanumeric field <text> starts with string <findtext>.
Entry fields returned are:• location number <indexn>• phone number stored there <number> of format <type>• text <text> associated with the number• <group> indicating a group the entry may belong to (if the selected phonebook supports it)• <hidden> indicating if the entry is hidden (if the selected phonebook supports hidden entries)• <adnumber> an additional number (of format <adtype>) (if the selected phonebook supports it)• <secondtext> a second text field associated with the number (if the selected phonebook supports it)• <email> an email field (if the selected phonebook supports it)
The string <findtext> is case sensitive.

10.3.2 Syntax
Type
Set

SyntaxAT+CPBF=<findtext>

Response[+CPBF: <index1>,<number>,<type>,<text>[,<hidden>][,<group>[,<adnumber>[,<adtype>[,<secondtext>[,<email>[,<sip_uri>[,<tel_uri>]]]]]]]

ExampleAT+CPBF="u-blox"
OK

[...]
[+CPBF: <index2>,<number>,<type>,<text>[,<hidden>][,<group>[,<adnumber>[,<adtype>[,<secondtext>[,<email>[,<sip_uri>[,<tel_uri>]]]]]]]]]
Test

AT+CPBF=?

OK+CPBF: [<nlength>],[<tlength>][,<glength>[,<alength>[,<slength>[,<elength>[,<siplength>[,<tellength>]]]]]]+CPBF: 40,18
OKOK

10.3.3 Defined values
Parameter<index1>, <index2>,<index><number><type><findtext>,<text><group><hidden>UBX-13002752 - R67

Type
NumberDescription
Location numbers of phonebook memory

StringNumberStringStringNumberPhone number of format <type>Type of address octet (see the 3GPP TS 24.008 [12] subclause 10.5.4.7)
Maximum length <tlength>Group the phonebook entry may belong to, of maximum length <glength>
Indicates if the entry is hidden or not:• 0 (default value): phonebook entry not hidden• 1: phonebook entry hidden

10 Phonebook

Page 212 of 1001

u-blox cellular modules - AT commands manual

Parameter<adnumber><adtype><secondtext><email><sip_uri>

Type
StringNumberStringStringString<tel_uri>

String<nlength><tlength><glength><alength><slength><elength><siplength><tellength>

NumberNumberNumberNumberNumberNumberNumberNumberDescription
Additional phone number of format <adtype>Type of address octet (see the 3GPP TS 24.008 [12] subclause 10.5.4.7)
Second text associated with the number, of maximum length <slength>
Email of maximum length <elength>
Field of maximum length <siplength>; character set as specified by the +CSCS AT
commandPhone number of maximum length <tellength>; character set as specified by the+CSCS AT command
Maximum length of field <number>
Maximum length of field <text>
Maximum length of field <group>
Maximum length of field <adnumber>
Maximum length of field <secondtext>
Maximum length of field <email>Maximum length of field <sip_uri>
Maximum length of field <tel_uri>

10.3.4 Notes••

The <sip_uri>, <tel_uri>, <siplength> and <tellength> parameters are not supported.
The <hidden> parameter is not applicable, since "AP" phonebook is not supported by +CPBS command(see the 3GPP TS 27.007 [2]).

SARA-G4 / SARA-G340 / SARA-G350 / LEON-G1• <group>, <adnumber>, <adtype>, <secondtext>, <email>, <glength>, <alength>, <slength>, <elength>
are not supported.

10.4 Write phonebook entry +CPBW+CPBWModules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialYes
No
No

Response time
< 35 sError reference+CME Error

10.4.1 Description
Stores the phonebook entry in the current phonebook memory storage (selectable with +CPBS) at the location
specified by the <index> field. Other entry fields are:• the phone number <number> (in the <type> format)• <text> text associated with the number• <group> indicating a group the entry may belong to• <adnumber> an additional number (of format <adtype>)• <secondtext> a second text field associated with the number• <email> an email fieldIf all the fields are omitted, except for <index>, the corresponding phonebook entry is deleted. If the <index>
field is left out, but the <number> is given, the entry is written in the first free location in the current phonebook
memory storage.
If no phonebook entries are available the information text response of the test command will be +CPBW: 0<CR><LF>OK
If the <number> and the <type> parameters are omitted but the <index> and at least one other parameter isprovided (e.g. <AT+CPBW=<index>,,,<text>):

UBX-13002752 - R67

10 Phonebook

Page 213 of 1001

u-blox cellular modules - AT commands manual

•

•

•
•

TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200-03S / LISA-U200-04B / LISA-U200-83S / LISA-U201- an entry with no number and <type>=129 is stored in the phonebook. Providing an empty string "" insteadof omitting the <number> parameter is equivalent.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 - an entry with no number and <type>=255 is stored in the phonebook.
Providing an empty string "" instead of omitting the <number> parameter is equivalent.
SARA-G4 - the module returns an error result code.
SARA-G3 / LEON-G1 - the module returns an error result code. If instead of omitting the <number>parameter an empty string "" is provided, an entry with no number and <type>=128 is stored in thephonebook.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The wildcard character (?) in the phone number of FDN is allowed.
<group>, <adnumber>, <adtype>, <secondtext>, <email> parameters are not supported by 2G SIM; but
they could be supported by USIM. Not all the fields are always supported on the used USIM: to verify which
fields are supported see the test command.
When BL (blacklist) phonebook is selected, only <index>=0 is accepted.
The set command +CPBW is not applicable for the storages "SN", "EC" (read only storages), while it isapplicable to "LD" storage only to delete an item.

10.4.2 Syntax
Type
Set

SyntaxAT+CPBW=[<index>][,<number>[,<type>[,<text>[,<group>[,<adnumber>[,<adtype>[,<secondtext>[,<email>[,<sip_uri>[,<tel_uri>[,<hidden>]]]]]]]]]]]

Response[+CPBW: <written_index>]

ExampleAT+CPBW=5,"091137880",,"u-blox"

OK

OK
AT+CPBW=,"091137880",,"u-blox"

Read

AT+CPBW?

+CPBW: <written_index>

Test

AT+CPBW=?

+CPBW: 5

OK+CPBW: (list of supported<index>s),<nlength>,(list of
supported <type>s),<tlength>[,<glength>[,<alength>[,<slength>[,<elength>[,<siplength>[,<tellength>]]]]]]OK+CPBW: 1
OK+CPBW: (1-250),40,(129,145),18
OK

OK+CPBW: 0+CPBW: 0OKOK

10.4.3 Defined values
Parameter<index><number><type><text><group><adnumber><adtype><secondtext><email><hidden>UBX-13002752 - R67

Type
NumberStringNumberStringStringStringNumberStringStringNumberDescription
Location numbers of phonebook memory
Phone number of format <type>Type of address; default is 145 when dialling string includes '+', otherwise 129
Text associated with the number. The maximum length is <tlength>Group the phonebook entry may belong to, of maximum length <glength>
Additional phone number of format <adtype>Type of address; default is 145 when dialling string includes '+', otherwise 129
Second text associated with the number, of maximum length <slength>
Email of maximum length <elength>
Indicates if the entry is hidden or not:• 0 (default value): phonebook entry not hidden• 1: phonebook entry hidden

10 Phonebook

Page 214 of 1001

u-blox cellular modules - AT commands manual

Parameter<sip_uri>

Type
String<tel_uri>

String<nlength><tlength><glength><alength><slength><elength><siplength><tellength><written_index>

NumberNumberNumberNumberNumberNumberNumberNumberNumberDescription
Field of maximum length <siplength>; character set as specified by the +CSCS AT
commandPhone number of maximum length <tellength>; character set as specified by the+CSCS AT command
Maximum length of field <number>
Maximum length of field <text>
Maximum length of field <group>
Maximum length of field <adnumber>
Maximum length of field <secondtext>
Maximum length of field <email>Maximum length of field <sip_uri>
Maximum length of field <tel_uri>
Last location number <index> of the written phonebook entry

10.4.4 Notes••

The <sip_uri>, <tel_uri>, <siplength> and <tellength> parameters are not supported.
The <hidden> parameter is not applicable, since "AP" phonebook is not supported by +CPBS command(see the 3GPP TS 27.007 [2]).

TOBY-L2 / MPCI-L2• The <group> parameter is not saved in SIM.
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• An error result code is returned when trying to delete an empty entry.
SARA-U2 / LISA-U2 / LISA-U1• <written_index> is not supported; hence the information text response to the set command is empty(only the final result code is provided).
• The read command is not supported.
SARA-G4• <group>, <adnumber>, <adtype>, <secondtext>, <email>, <glength>, <alength>, <slength>, <elength>
are not supported.
• <written_index> is not supported; hence the information text response to the set command is empty(only the final result code is provided).
• The read command is not supported.
• The <type> parameter is ignored. If the <number> string includes '+' the <type> is automatically set to145, otherwise to 129.
SARA-G4 / SARA-G340 / SARA-G350 / LEON-G1• <group>, <adnumber>, <adtype>, <secondtext>, <email>, <glength>, <alength>, <slength>, <elength>
are not supported.
• <written_index> is not supported; hence the information text response to the set command is empty(only the final result code is provided).
• The read command is not supported.

10.5 Read/rename phonebook group +UPBGR+UPBGR
Modules
Attributes

SARA-U270-73S
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

10.5.1 Description
Reads the phonebook group name at the given location number <index> of EFGAS.

UBX-13002752 - R67

10 Phonebook

Page 215 of 1001

u-blox cellular modules - AT commands manual

Otherwise, if new name for <newgroup> group is provided, the command renames the phonebook group at thelocation specified by <index> of EFGAS.
The +UPBGR command (set and test) is not allowed for 2G SIM and is allowed for USIM only if EFGAS
and EFGRP are present in the inserted USIM (see the 3GPP TS 31.102 [18]) for current phonebook memorystorage (previously selected by +CPBS).

10.5.2 Syntax
Type
SyntaxRead group name command
Set
AT+UPBGR=<index>

Response

Example+UPBGR: <index>,<group>

AT+UPBGR=1

OK+UPBGR: 1,"group1name"
OK

Rename group command
Set
AT+UPBGR=<index>,<newgroup>

OK

AT+UPBGR=1,"newgroup1name"
OK

Test

AT+UPBGR=?

+UPBGR: (list of supported<index>'s),<glength>
OK

AT+UPBGR=?
+UPBGR: (1-6),24
OKor+CME ERROR: <error>

10.5.3 Defined values
Parameter<index><group>,<newgroup><glength>

UBX-13002752 - R67

Type
NumberStringDescription
Location identifier for group name in EFGAS
Phonebook group name of maximum length <glength>

NumberMaximum length of field <group>, <newgroup>

10 Phonebook

Page 216 of 1001

u-blox cellular modules - AT commands manual

11 Short Messages Service
11.1 Introduction
For a complete overview of SMS, see 3GPP TS 23.040 [8] and 3GPP TS 27.005 [15].
In case of errors all the SMS related AT commands return an error result code as defined in Appendix A.2.

11.1.1 Class 0 SMS
The storing of a class 0 SMS depends on the module series:• TOBY-L4 / TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S /MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280 / LARA-R2 / TOBY-R2 - allincoming SMSes stored in <mem3> (preferred memory for storing the received SMS, see +CPMS) withincreasing index.
• TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S - not stored.
• SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - only one incoming SMS stored in RAM (thelast received SMS, <index> parameter value 0).

11.1.2 <index> parameter range
The <index> parameter range depends on the memory storage type:
ME (ME message), SM ((U)SIM message) MT (ME + SM):• TOBY-L4
o Values between 1 and 4: SMS stored in ME.
o Values between 1 and n: SMS stored in SIM (n depends on SIM card used).
• TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S /MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G340 / SARA-G350 / LEON-G1
o Values between 1 and 300: SMS stored in ME.
o Values between 301 and (301 + (n-1)): SMS stored in SIM (n depends on SIM card used).
• TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S / SARA-G300 / SARA-G310 - values between 1 and n (ndepends on SIM card used).
• LARA-R2 / TOBY-R2
o Values between 1 and 100: SMS stored in ME.
o Values between 1 and n: SMS stored in SIM (n depends on SIM card used).
BM (Broadcast Message):• TOBY-L4 - Values between 1 and 4.
• TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S /MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280 / SARA-U2 / LISA-U2 / LISA-U1- values between 1 and 300: Cell Broadcast messages are stored only if there is at least an empty location
available in the BM memory (that is located in the file system).
• TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S - not stored.
• LARA-R2 / TOBY-R2 - Values between 1 and 10.
• SARA-G4 / SARA-G3 / LEON-G1 series - values between 1 and 5: Cell Broadcast messages are stored using
a circular buffer so they are always saved even if the BM memory (that is located in RAM) is full. Since the
Cell Broadcast messages are stored in RAM, they will be lost after a power-off or reset of the module.
SR (Status Report)• TOBY-L4 - Values between 1 and 4.

UBX-13002752 - R67

11 Short Messages Service

Page 217 of 1001

u-blox cellular modules - AT commands manual•••

TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S /MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280 / SARA-U2 / LISA-U2 / LISA-U1- values between 1 and 300: Status Report messages are stored only if there is at least an empty location
available in the SR memory (that is located in the file system).
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S / SARA-G4 / SARA-G3 / LEON-G1 - not stored.
LARA-R2 / TOBY-R2 - Values between 1 and 10.

11.1.3 Limitations
The following limitations apply related to the SMS usage:
Single SMS• 160 characters if <dcs>= "GSM 7 bit default alphabet data"• 140 octets if <dcs>= "8-bit data"• 70 UCS2 characters (2 bytes for each one) if <dcs>="16-bit uncompressed UCS2 data"
Concatenated SMS (where supported) - "8-bit reference number" type• 153 characters if <dcs>= "GSM 7 bit default alphabet data"• 134 octets if <dcs>= "8-bit data"• 67 UCS2 characters (2 bytes for each one) if <dcs>="16-bit uncompressed UCS2 data"
Concatenated SMS (where supported) - "16-bit reference number" type• The limits are the same as the "8-bit reference number" type, but are decreased by one unit.
A concatenated SMS can have as many as 255 parts.
TOBY-L4906-50A
The SMSes on ME memory are not saved in the NVM.
Concatenated MO SMS are supported by the following products:• TOBY-L201/MPCI-L201 only when the module is configured in Verizon mode by means of the+UMNOCONF AT command (<MNO>=3)• TOBY-L220/MPCI-L220

11.2 Select message service +CSMS+CSMS
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CMS Error

11.2.1 Description
Selects the <service> message service. It returns the types of messages supported by the MT.

11.2.2 Syntax
Type
Set

Read

Test

SyntaxAT+CSMS=<service>

AT+CSMS?

AT+CSMS=?

Response+CSMS: <mt>,<mo>,<bm>ExampleAT+CSMS=1

OK+CSMS: 1,1,1+CSMS: <service>,<mt>,<mo>,<bm>
OK+CSMS: (list of supported<service>s)

OK+CSMS: 0,1,1,1
OK+CSMS: (0-1)
OK

OK

UBX-13002752 - R67

11 Short Messages Service

Page 218 of 1001

u-blox cellular modules - AT commands manual

11.2.3 Defined values
Parameter<service>

Type
Number<mt>

Number<mo>Number<bm>

NumberDescription
Allowed values:• 0: see 3GPP TS 23.040 [8] and 3GPP TS 23.041 [9]; syntax of AT commands iscompatible with 3GPP TS 27.005 [15] phase 2; phase 2+ features may be supported
if no new command syntax is required• 1: see 3GPP TS 23.040 [8] and 3GPP TS 23.041 [9]; syntax of AT commands iscompatible with 3GPP TS 27.005 [15] phase 2+
Mobile terminated messages:• 0: not supported• 1: supported
Mobile originated messages:• 0: not supported• 1: supported
Broadcast messages:• 0: not supported• 1: supported

11.2.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• Set <service> to 1 to acknowledge an incoming message (either SMS or Status Report) with +CNMA AT
command.
• If <service> is changed from 1 to 0 and one or more parameters of the +CNMI command are in phase 2+,
switch the +CNMI parameters to phase 2 specific values before entering phase 2.

11.3 Preferred message storage +CPMS+CPMS
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
NVM
No

Response time
Up to 3 min

Error reference+CMS Error

11.3.1 Description
Selects memory storages <mem1>, <mem2> and <mem3>. If the chosen storage is supported by the MT but
not suitable, the +CMS ERROR: <err> error result code should be returned.
See the test command for the supported memory types for each memory storage.

11.3.2 Syntax
Type
Set

SyntaxAT+CPMS=<mem1>[,<mem2>[,<mem3>]]

Read

AT+CPMS?

Test

AT+CPMS=?

UBX-13002752 - R67

Response
ExampleAT+CPMS: <used1>,<total1>,
AT+CPMS="BM","SM","SM"<used2>,<total2>,<used3>,<total3>+CPMS: 0,5,0,50,0,50
OK
OK+CPMS: <mem1>,<used1>,<total1>, +CPMS: "MT",4,350,"MT",4,350,<mem2>,<used2>,<total2>,"MT",4,350<mem3>,<used3>,<total3>
OK
OK+CPMS: (list of supported+CPMS: ("MT","ME","SM","BM",<mem1>s),(list of supported"SR"),("MT","ME","SM"),("MT","ME",<mem2>s),(list of supported"SM")<mem3>s)OK
OK

11 Short Messages Service

Page 219 of 1001

u-blox cellular modules - AT commands manual

11.3.3 Defined values
Parameter<mem1>Type
String<mem2>

String<mem3>

String<used1><total1><used2><total2><used3><total3>

NumberNumberNumberNumberNumberNumberDescription
Memory used to read and delete messages. The supported values may vary:• "ME": ME message storage• "SM": (U)SIM message storage• "MT": "ME"+"SM", "ME" preferred• "BM": Broadcast Message storage• "SR": Status Report storage
The default value is the currently set value. The factory-programmed value depends
on the module series: see Notes for more details.
Memory used to write and send SMS. The supported values may vary:• "ME": ME message storage• "SM": (U)SIM message storage• "MT": "ME"+"SM", "ME" preferred
The default value is the currently set value. The factory-programmed value depends
on the module series: see Notes for more details.
Memory preferred to store the received SMS. The supported values may vary:• "ME": ME message storage• "SM": (U)SIM message storage• "MT": "ME"+"SM", "ME" preferred
The default value is the currently set value. The factory-programmed value depends
on the module series: see Notes for more details.
Number of used message locations in <mem1>
Total number of message locations in <mem1>
Number of used message locations in <mem2>
Total number of message locations in <mem2>
Number of used message locations in <mem3>
Total number of message locations in <mem3>

11.3.4 Notes•••

TOBY-L4 / TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S /MPCI-L201 / MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S / SARA-G300 / SARA-G310 - thefactory-programmed value is "SM", "SM" and "SM".
LARA-R2 / TOBY-R2 / SARA-G4 - the factory-programmed value is "ME", "ME" and "ME".
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-60S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 /MPCI-L200-02S / MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G340 / SARA-G350 / LEON-G1 - the factory-programmed value is"MT", "MT" and "MT".

TOBY-L4 / LARA-R2 / TOBY-R2• "MT" message storage is not supported.
TOBY-L4• The parameter setting is not saved in the NVM.
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• Only "SM" message storage is supported.
SARA-G4• The parameters setting is stored in the personal profile following the procedure described in the Saving
AT commands configuration section.
• "SR" is not supported.
SARA-G3 / LEON-G1• "SR" is not supported.
SARA-G300 / SARA-G310• "ME" and "MT" message storages are not supported.

UBX-13002752 - R67

11 Short Messages Service

Page 220 of 1001

u-blox cellular modules - AT commands manual

11.4 Preferred message format +CMGF+CMGF
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CMS Error

11.4.1 Description
Indicates to the MT which input and output format of messages shall be used.

11.4.2 Syntax
Type
Set

SyntaxAT+CMGF=[<mode>]

Response
OK

ExampleAT+CMGF=1

Read

AT+CMGF?

+CMGF: <mode>OK+CMGF: 1

Test

AT+CMGF=?

OKOK+CMGF: (list of supported <mode>s) +CMGF: (0-1)
OKOK

11.4.3 Defined values
Parameter<mode>

Type
NumberDescription
Indicates the format of messages used with send, list, read and write commands and
URCs resulting from receiving SMSes messages:• 0 (default and factory-programmed value): PDU mode
• 1: text mode

11.4.4 Notes
TOBY-L201-02S / MPCI-L201-02S• On TOBY-L201-02S-00, TOBY-L201-02S-01, MPCI-L201-02S-00, MPCI-L201-02S-01 the default value is 1
when the module is configured in Verizon mode (+UMNOCONF: 3,<conf>).
TOBY-L201-01S / MPCI-L201-01S• The default value is 1 when the module is configured in Verizon mode (+UMNOCONF: 3,<conf>).

11.5 Save settings +CSAS+CSAS
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CMS Error

11.5.1 Description
Saves active message service settings from the current active memory (RAM) to non-volatile memory (NVM).
The settings related to the +CSCA (the current SMSC address stored in RAM), +CSMP and +CSCB commands
are stored in a specific SMS profile (only one profile is available).

11.5.2 Syntax
Type
Set

SyntaxAT+CSAS[=<profile>]

Response
OK

Test

AT+CSAS=?

+CSAS: (list of supported<profile>s)

ExampleAT+CSAS
OK+CSAS: (0)OK

OK

UBX-13002752 - R67

11 Short Messages Service

Page 221 of 1001

u-blox cellular modules - AT commands manual

11.5.3 Defined values
Parameter<profile>

Type
NumberDescription
Specific SMS profile index where to store the active message settings. The factoryprogrammed value is 0.

11.6 Restore settings +CRES+CRES
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time< 10 sError reference+CMS Error

11.6.1 Description
Restores message service settings from a non-volatile memory (NVM) to the current active memory (RAM).
The settings related to the +CSCA (the SMSC address in the SIM card is also updated), +CSMP and +CSCB
commands are read from a specific SMS profile (only one profile is available).

11.6.2 Syntax
Type
Set

SyntaxAT+CRES[=<profile>]

Response
OK

Test

AT+CRES=?

OK+CRES: (list of supported <profile>s) +CRES: (0)OK

ExampleAT+CRES=0OK

11.6.3 Defined values
Parameter<profile>

Type
NumberDescription
Specific SMS profile index from where to read the message service settings

11.7 Show text mode parameters +CSDH+CSDHModules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CMS Error

11.7.1 Description
Controls whether detailed SMS header information is shown in text mode (see the +CMGF=1 commanddescription).
This affects the responses of the +CMGR, +CMGL, +CSMP, +CSCA AT commands and the +CMT, +CMTI,+CDS, +CDSI, +CBM, +CBMI (see +CNMI) URCs.

11.7.2 Syntax
Type
Set

SyntaxAT+CSDH=[<show>]

Response
OK

ExampleAT+CSDH=1

Read

AT+CSDH?

+CSDH: <show>

OK+CSDH: 0

Test

AT+CSDH=?

OK
OK+CSDH: (list of supported <show>s) +CSDH: (0-1)
OK

UBX-13002752 - R67

11 Short Messages Service

OK

Page 222 of 1001

u-blox cellular modules - AT commands manual

11.7.3 Defined values
Parameter<show>

Type
NumberDescription
Allowed values:• 0 (default): do not show detailed SMS header information• 1: show detailed SMS header information

11.8 New message indication +CNMI+CNMI
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CMS Error

11.8.1 Description
Selects the procedure to indicate the reception of a new SMS in case of the MT is active (the DTR signal is ON).
If the MT is inactive (the DTR signal is OFF), the message reception should be done as specified in 3GPP TS
23.038 [7].
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The SMSes of class 0 (normally displayed via MMI) are indicated on DTE via URC +CMTI: "SM",0 , wherein
0 represents an SMS without SIM-storage ("SM" indicates only that no other specific setting is needed
to read the SMS via AT+CMGR=0).
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280 / MPCI-L200-02S /MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280 / LARA-R2 / TOBY-R2
The SMSes of class 0 (normally displayed via MMI) are indicated on DTE via URC +CMTI: <mem3>,<index>
where <mem3> is the preferred memory for storing the received SMS and <index> is the first free storage
position in <mem3>.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length> parameters in the text mode +CMT URC aredisplayed only if +CSDH=1 is set.
The +UCMT URC notifies the SMS-DELIVER status for 3GPP2 Mobile Terminated SMSes; it is equivalent to+CMT but valid only for 3GPP2 SMS (i.e. 3GPP2 SMS over IMS received on Verizon MNO).

11.8.2 Syntax
Type
Set

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

Read

AT+CNMI?

Test

AT+CNMI=?

URC
URC+CNMI: <mode>,<mt>,<bm>,<ds>,<bfr>

ExampleAT+CNMI=1,1
OK+CNMI: 0,0,0,0,0

OK
OK+CNMI: (list of supported <mode>s), +CNMI: (0-2),(0-3),(0-3),(0-2),(0-1)(list of supported <mt>s),(list ofOKsupported <bm>s),(list of supported<ds>s),(list of supported <bfr>s)
OK+CMTI: <mem>,<index>
Text mode (+CMGF=1):+CMT: <oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]<CR><LF><data>
PDU mode (+CMGF=0):+CMTI: "SM",5+CMT: "+393475234652",,"14/11/21,
11:58:23+01"
Hello world+CMT: ,<length><CR><LF><pdu>

UBX-13002752 - R67

11 Short Messages Service

Page 223 of 1001

u-blox cellular modules - AT commands manual

Type
URC

SyntaxResponse
Text mode (+CMGF=1):+UCMT: <message_id>,<oa>,<scts>,[<priority>],[<privacy>],[<callback_number>],<encoding>,[<status>],[<num_sms>,<part>,<reference>],<length><CR><LF><text>
PDU mode (+CMGF=0):+UCMT: <pdu_
length><CR><LF><pdu>+CBMI: <mem>,<index>
Text mode (+CMGF=1):

URC
URC

+CBM: <sn>,<mid>,<dcs>,<page>,<pages><CR><LF><data>
PDU mode (+CMGF=0):+CBM: <length><CR><LF><pdu>+CDSI: <mem>,<index>
Text mode (+CMGF=1):

URC
URC

+CDS: <fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>
PDU mode (+CMGF=0):

Example+UCMT: 1,+1231241241,"18:02:28+0
8",,,,2,,,,,6
Hello!

+CBMI: "BM",48+CBM: 271,1025,1,1,1
The quick brown fox jumps over the
lazy dog 0123456789+CDSI: "MT",2+CDS: 6,202,"+393492323583",145,"14/07/25,13:07:16+02","14/07/25,
16:35:44+02",0+CDS: <length><CR><LF><pdu>

11.8.3 Defined values
Parameter<mode>

Type
Number<mt>

Number<bm>

Number<ds>

NumberUBX-13002752 - R67

Description
Controls the processing of URCs specified within this command:• 0 (default value): buffer URCs in the MT; if the MT buffer is full, the oldest indication
may be discarded and replaced with the new received indications (ring buffer)• 1 (factory-programmed value): discard indication and reject new received message
URCs when MT-DTE link is reserved; otherwise forward them directly to the DTE• 2: buffer URCs in the MT when the serial link is busy (e.g. data-transfer); otherwise
forward them directly to the DTE• 3: forward URCs directly to the TE. TA-TE link specific inband technique used toembed result codes and data when MT is in on-line data mode
Specifies the rules for managing the received SMS according the message's Data
Coding Scheme (DCS):• 0 (default and factory-programmed value): No SMS-DELIVER indications arerouted to the TE• 1: if SMS-DELIVER is stored in the MT, indication of the memory location is routed
to the DTE using the +CMTI URC• 2: SMS-DELIVER (except class 2 SMS) are routed directly to the DTE (but not savedin the module file system or SIM memory) using the +CMT URC. If MT has its own
display device then class 0 SMS and SMS in the message waiting indication group(discard message) may be copied to both MT display and to DTE. In this case MT
shall send the acknowledgement to the network. Class 2 SMSs and messages in themessage waiting indication group (storage message) result in indication as definedin <mt>=1• 3: Class 3 SMS-DELIVERs are routed directly to DTE using URCs defined in <mt>=
2. Messages of other data coding schemes result in indication as defined in <mt>=1
Specifies the rules for managing the received Cell Broadcast messages (CBM):• 0 (default and factory-programmed value): no CBM indications to the DTE• 1: if the CBM is stored in the MT, an indication of the used memory location is routed
to DTE using the +CBMI URC• 2: new CBMs are routed directly to the DTE using the +CBM URC• 3: class 3 CBMs are routed directly to DTE using URCs defined in <bm>=2. If CBM
storage is supported, messages of other classes result in indication as defined in<bm>=1
Specifies the rules for managing the Status Report messages:

11 Short Messages Service

Page 224 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

<bfr>

Number<mem><index><length>StringNumberNumber<pdu>

String<oa><scts><data>

StringStringString

<sn>
<mid>
<dcs>
<page><pages>
<fo>
<mr>
<ra>
<tora><dt>

NumberNumberNumberNumberNumberNumberNumberStringNumberString<st><message_id><priority>

NumberNumberNumberUBX-13002752 - R67

Description• 0 (default and factory-programmed value): no SMS-STATUS-REPORTs are routed
to the DTE• 1: SMS-STATUS-REPORTs are routed to the DTE using the +CDS URC• 2: if SMS-STATUS-REPORT is stored in the MT, the indication of the memory
location is routed to the DTE using the +CDSI URC
Controls the buffering of URCs:• 0 (default and factory-programmed value): MT buffer of URCs defined within thiscommand is flushed to the DTE when <mode> 1...3 is entered (OK final result codeshall be given before flushing the codes).
• 1: MT buffer of URCs defined within this command is cleared when <mode> 1...3 isenteredSame as defined in +CPMS Defined Values
Storage position
Two meanings:• in text mode: number of characters• in PDU mode: PDU's length in octets without the Service Center's address. In
example: 039121430100038166F6000004E374F80D: this is a PDU with Service
Center's number +1234, that generates the address 03912143 (4 octets). Thus inthis case <length>=13.
Protocol data unit: each 8-bit octet is presented as two IRA character longhexadecimal numbers, e.g. octet with integer value 42 is presented to TE as two
characters 2A (IRA 50 and 65)
Originator address
Service center time stamp in time-string format, see the <dt>
In the case of SMS: 3GPP TS 23.040 [8] TP-User-Data in text mode responses;
format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS command in 3GPP TS 27.0
07 [2]): ME/TA converts GSM alphabet into current TE character set according
to rules of Annex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of GSM
7 bit default alphabet into two IRA character long hexadecimal number (e.g.
character Æ (GSM 7 bit default alphabet 28) is presented as 1C (IRA 49 and 67))
• if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number (e.g. octet withinteger value 42 is presented to TE as two characters 2A (IRA 50 and 65))
In the case of CBS: 3GPP TS 23.041 [9] CBM Content of Message in text mode
responses; format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS in 3GPP TS 27.007 [2]): ME/
TA converts GSM alphabet into current TE character set according to rules ofAnnex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of the GSM 7
bit default alphabet into two IRA character long hexadecimal number• if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number
CBM serial number
CBM message identifier
Data Coding Scheme
CBM Page Parameter bits 4-7 in integer format as described in 3GPP TS 23.041 [9]CBM Page Parameter bits 0-3 in integer format as described in 3GPP TS 23.041 [9]First octet of the SMS TPDU (see 3GPP TS 23.040 [8])Message reference
Recipient address field
Type of address of <ra> - octet
Discharge time in format "yy/MM/dd,hh:mm:ss+zz"; the time zone is expressed insteps of 15 minutes. The range goes from -48 to +56
Status of a SMS STATUS-REPORT
Message-ID of the 3GPP2 SMS
3GPP2 priority:

11 Short Messages Service

Page 225 of 1001

u-blox cellular modules - AT commands manual

ParameterType<privacy>

Number<callback_number><encoding>StringNumber<num_sms><part><reference>

NumberNumberNumberDescription• 0: normal• 1: interactive• 2: urgent• 3: emergency
3GPP2 privacy:• 0: not restricted• 1: restrictive• 2: confidential• 3: secret
Callback number
Text encoding:• 0: octet, unspecified• 2: ASCII7• 3: IA5• 4: UCS2• 8: ISO 8859-1• 9: GSM7
Total number of SMS
Fragment part number
3GPP2 reference ID

11.8.4 Notes
TOBY-L2 / MPCI-L2• <mode> = 3 is not supported.
• The incoming SMS/CBM URC indications will be displayed only on the AT interface where the last +CNMI
command was set. As a general rule, the command should be issued by the DTE:o After start-up
o After using the Z and &F command (which reset the command configuration)o Whenever the incoming SMS URCs indications are requested on a different AT interface• When <mt> is not set to 0 the arrival of an SMS is notified by switching the RI line from OFF to ON for 1
s. This is done in respect to the RI line of all the AT interfaces.
• The RI line switches from OFF to ON state for 1 s both on the AT interface (USB, UART or MUX virtualchannel) and on the UART interface (regardless the selected AT command interface) when the +CNMI
AT command is issued (with <mt> not set to 0).
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• The RI line switching from OFF to ON for 1 s is only performed on the AT interface where the +CNMI
command is issued (with <mt> not set to 0).
• <bm> = 1 and <bm> = 3 are not supported.
• <ds> = 2 is not supported.
TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S / MPCI-L200-03S /MPCI-L210-03S / MPCI-L280-03S• On
TOBY-L200-03S-00,
TOBY-L210-03S-00,
TOBY-L210-03A-00,
TOBY-L280-03S-00,
MPCI-L200-03S-00, MPCI-L210-03S-00, MPCI-L280-03S-00 the UART RI line is switched as describedabove only in case <mt> is not set to 2.
TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S /MPCI-L200-02S / MPCI-L210-02S / MPCI-L210-60S / MPCI-L210-63S / MPCI-L220 / MPCI-L280-02S• The UART RI line is switched as described above only in case <mt> is not set to 2.
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G340 / SARA-G350 /LEON-G1• <mode> = 3 is not supported.
• The incoming SMS/CBM URC indications will be displayed only on the AT interface where the last +CNMI
command was set. As a general rule, the command should be issued by the DTE:o After start-up

UBX-13002752 - R67

11 Short Messages Service

Page 226 of 1001

u-blox cellular modules - AT commands manual••o After using the Z and &F command (which reset the command configuration)o Whenever the incoming SMS URCs indications are requested on a different AT interface
When <mt> is not set to 0 the arrival of an SMS is notified by switching the RI line from OFF to ON for 1
s. This is done in respect to the RI line of all the AT interfaces.
The +UCMT URC is not supported.

SARA-U2 / LISA-U2• The behaviour regarding the <mt> parameter configuration and the RI line described in the note above
can be configured via the +UDCONF=82 AT command (where this command is supported).
SARA-G300 / SARA-G310• <mode> = 3 is not supported.
• The incoming SMS/CBM URC indications will be displayed only on the AT interface where the last +CNMI
command was set. As a general rule, the command should be issued by the DTE:o After start-up
o After using the Z and &F command (which reset the command configuration)o Whenever the incoming SMS URCs indications are requested on a different AT interface• The +UCMT URC is not supported.

11.9 Incoming SMS/CBM indication via different AT interfaces+UDCONF=82+UDCONF=82
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

11.9.1 Description
Allows the module to provide SMS/CBM indications on different AT command interfaces.
Once the feature is enabled, the incoming SMS/CBM URC indications will be displayed on each AT commandinterface where the +CNMI AT command will be issued.
However, only the URCs' enable/disable status will be part of AT command interface properties; instead thetype of the URCs and the management of the incoming SMSs/CBMs (for instance "+CMTI: ..." instead of"+CMT: ...", so storing SMS instead of only displaying it) will be driven by the last +CNMI AT command issued(as usually happens also when the feature is disabled).
When the URC indications are disabled on a single AT command interface, by setting to 0 the +CNMI's <mode>parameter or by setting to 0 individually the +CNMI's parameters <mt>/<bm>/<ds>, actually they will bedisabled on all the AT command interfaces.
The way how the +CNMI values are loaded from the module Profile, during the start-up phase and by using
Z/&F AT commands, is not influenced by the AT command setting. This means that values will be applied only
to one AT command interface and the URCs' enable/disable status will be set to disabled to all the other ones.

11.9.2 Syntax
Type
Set

SyntaxAT+UDCONF=82,<CNMI_conf_
status>Read

AT+UDCONF=82

Response
OK

ExampleAT+UDCONF=82,0

OK+UDCONF: 82,<CNMI_conf_status> AT+UDCONF=82
OK+UDCONF: 82,1
OK

UBX-13002752 - R67

11 Short Messages Service

Page 227 of 1001

u-blox cellular modules - AT commands manual

11.9.3 Defined values
Parameter<CNMI_conf_
status>Type
NumberDescription
Enables / disables the incoming SMS/CBM indication via different AT commandinterfaces. Allowed values:• 0 (factory-programmed value): the incoming SMS/CBM URC indications will be
displayed only on the AT interface where the last +CNMI command was issued• 1: the incoming SMS/CBM indications via different AT interfaces is enabled. The
URC about the incoming SMS/CBM indications will be displayed on each AT
interface where the command +CNMI was issued.

11.10 Select service for MO SMS messages +CGSMS+CGSMS
Modules
Attributes

All products
Syntaxpartial

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

11.10.1 Description
Specifies the service (PS or CS) or service preference that the MT will use to send MO SMS messages.
In particular:•••

in 2G RAT, PS service means GPRS and CS service means transmission on GSM dedicated channels;
in 3G RAT, PS service means transmission on PS domain SRB (Signalling Radio Bearer) and CS service
means transmission on CS domain SRB; SRB can be mapped to several UMTS transport channels, e.g.
RACH/FACH or DCH;
in 4G RAT, PS service means IMS messaging on EPS bearers and CS service means transmission on SGs(Signalling Gateways).

11.10.2 Syntax
Type
Set

SyntaxAT+CGSMS=[<service>]

Response
OK

ExampleAT+CGSMS=1

Read

AT+CGSMS?

+CGSMS: <service>OK+CGSMS: 1

Test

AT+CGSMS=?

OK+CGSMS: (list of supported<service>s)OK+CGSMS: (0-3)
OKOK

11.10.3 Defined values
Parameter<service>

Type
NumberDescription
Service or service preference to be used:••••

0 (default value): PS
1 (factory-programmed value): CS
2: PS preferred (use CS if PS is not available)
3: CS preferred (use PS if CS is not available)

11.10.4 Notes
TOBY-L4• The command setting is not stored in NVM.
TOBY-L2 / MPCI-L2• The PIN insertion is mandatory before the command execution.
TOBY-L201 / MPCI-L201• The command setting is not stored in NVM.

UBX-13002752 - R67

11 Short Messages Service

Page 228 of 1001

u-blox cellular modules - AT commands manual

TOBY-L220-62S / MPCI-L220-62S• <service>=0 is not supported.

11.11 Read message +CMGR+CMGR
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time
<10 s

Error reference+CMS Error

11.11.1 Description
Returns the message with location value <index> from message storage <mem1> to the DTE.
The parameters <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>, <cdata> shall be displayed only if
AT+CSDH=1 is set.
The syntax AT+CMGR=0 allows to display an SMS class 0 if it is signalized to MT, because no MMI isavailable in the MT (see also the +CNMI AT command notes).
If the <index> value is out of range (it depends on AT+CPMS command setting) or it refers to an empty
position, then "+CMS ERROR: invalid memory index" error result code is returned.
LARA-R2 / TOBY-R2
It is possible to read SMSes in "ME" also without the PIN insertion (no access to SIM is required when<mem1>= "ME").

11.11.2 Syntax
Type
Set

Syntax
Text mode (+CMGF=1):
AT+CMGR=<index>

Response
SMS-DELIVER+CMGR: <stat>,<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]<data>OK
SMS-SUBMIT+CMGR: <stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<length>]

ExampleAT+CMGR=303+CMGR: "REC READ","+393488535999",,"07/04/05,18:0
2:28+08",145,4,0,0,"+393492000
466",145,93
You have a missed called. Free
information provided by youroperator.
OK<data>OK
SMS-STATUS-report+CMGR: <stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>OK
SMS-COMMAND+CMGR: <stat>,<fo>,<ct>[,<pid>,[<mn>],[<da>],[<toda>],<length>[<cdata>]]OK
CBM storage+CMGR: <stat>,<sn>,<mid>,<dcs>,<page>,<pages><data>PDU mode (+CMGF=0):
AT+CMGR=<index>

UBX-13002752 - R67

OK+CMGR: <stat>,[<alpha>],<length> AT+CMGR=1<pdu>+CMGR: 1,,40

OK

0791934329002000040
C9193230982661400008070

11 Short Messages Service

Page 229 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Test

AT+CMGR=?

OK

Example328045218018D4F29CFE0
6B5CBF379F87C4EBF41E4340
82E7FDBC3
OK

11.11.3 Defined values
Parameter<index><stat>

Type
NumberNumber<oa><alpha>StringString<scts><tooa>
<fo>
<pid>
<dcs>
<sca>
<tosca>StringNumberNumberNumberNumberStringNumber<length>Number<data>

String<da><toda><vp>

UBX-13002752 - R67

StringNumberNumberDescription
Storage position• 0: in PDU mode or "REC UNREAD" in text mode: received unread SMS• 1: in PDU mode or "REC READ" in text mode: received read SMS• 2: in PDU mode or "STO UNSENT" in text mode: stored unsent SMS• 3: in PDU mode or "STO SENT" in text mode: stored sent SMS
Originator address
Alphanumeric representation of <da> or <oa> corresponding to the entry found in thephonebook 3GPP TS 24.008 [12]. The parameter is not managed.
Service center time stamp in time-string format, see <dt>Type of address of <oa> - octet
First octet of the SMS TPDU (see 3GPP TS 23.040 [8])TP-Protocol-Identifier (default 0); see the 3GPP TS 23.040 [8]Data Coding Scheme
Service center address field
Type of address of <sca> - octet in Number format (for more details see the 3GPP TS
24.008 [12]); default 145 when string includes '+', otherwise default 129
Two meanings:• in text mode: number of characters• in PDU mode: PDU's length in octets without the Service Center's address. In
example 039121430100038166F6000004E374F80D: this is a PDU with Service
Center's number +1234, that generates the address 03912143 (4 octets). Thus inthis case <length> = 13.
In the case of SMS: 3GPP TS 23.040 [8] TP-User-Data in text mode responses;
format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see +CSCS command description): ME/
TA converts GSM alphabet into current TE character set according to rules ofAnnex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of GSM
7 bit default alphabet into two IRA character long hexadecimal number (e.g.
character Æ (GSM 7 bit default alphabet 28) is presented as 1C (IRA 49 and 67))
• if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number (e.g. octet withinteger value 42 is presented to TE as two characters 2A (IRA 50 and 65))
In the case of CBS: 3GPP TS 23.041 [9] CBM Content of Message in text mode
responses; format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see +CSCS command description): ME/
TA converts GSM alphabet into current TE character set according to rules ofAnnex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of the GSM 7
bit default alphabet into two IRA character long hexadecimal number• if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number
Destination address
Type of address of <da> - octet
Format depending of the <fo> setting:• Relative format: validity period starting from when the SMS is received by the
SMSC, in range 0-255 (default value 167); for more details see the 3GPP TS 23.040[8]

11 Short Messages Service

Page 230 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description<vp>
0 to 143

•

<mr>
<ra>
<tora><dt>

NumberStringNumberString

<st>
<ct>
<mn>
<cdata><sn><mid><page><pages><pdu>

NumberNumberNumberStringNumberNumberNumberNumberStringValidity period value(TP-VP + 1) x 5 minutes (i.e. 5 minutes
intervals up to 12 hours)
144 to 167
12 hours + ((TP-VP -143) x 30 minutes)
168 to 196(TP-VP - 166) x 1 day
197 to 255(TP-VP - 192) x 1 week
Absolute format: absolute time of the validity period termination in string format("yy/MM/dd,hh:mm:ss+zz") (see the 3GPP TS 23.040 [8]); the time zone isexpressed in steps of 15 minutes. The range goes from -48 to +56

Message reference
Recipient address field
Type of address of <ra> - octet
Discharge time in format "yy/MM/dd,hh:mm:ss+zz"; the time zone is expressed insteps of 15 minutes. The range goes from -48 to +56
Status of an SMS STATUS-REPORT
TP-Command-Type (default 0)
See the 3GPP TS 23.040 [8] TP-Message-Number in integer format
TP-Command-Data in text mode responses
CBM serial number
CBM message identifier
3GPP TS 23.041 [9] CBM Page Parameter bits 4-7 in integer format
3GPP TS 23.041 [9] CBM Page Parameter bits 0-3 in integer format
Protocol data unit: each 8-bit octet is presented as two IRA character longhexadecimal numbers, e.g. octet with integer value 42 is presented to TE as two
characters 2A (IRA 50 and 65)

11.11.4 Notes
SARA-G4• The <dt> parameter is in the format "yyyy/MM/dd,hh:mm:ss+zz".

11.12 New message acknowledgement to MT +CNMA+CNMA
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time
< 150 sError reference+CMS Error

11.12.1 Description
Confirms the reception of a new message (SMS-DELIVER or SMS-STATUS-REPORT) which is routed directly
to the TE (see the +CNMI command). This acknowledgement command shall be used when +CSMS parameter<service> equals 1. The MT shall not send another +CMT or +CDS (see the +CNMI command) unsolicited result
codes to the TE before the previous one is acknowledged. If the MT does not get acknowledgement withinrequired time (network timeout), the MT should respond as specified in 3GPP TS 24.011 [13] to the network.
The MT shall automatically disable routing to the TE by setting both <mt> and <ds> values of +CNMI to zero.
If the command is executed, but no acknowledgement is expected, or some other MT related error occurs, the+CMS ERROR: <err> error result code is returned.
In PDU mode, it is possible to send either positive (RP-ACK) or negative (RP-ERROR) acknowledgement to the
network. The <n> parameter defines which one will be sent. Optionally (when <length> is greater than zero) an
acknowledgement TPDU (SMS-DELIVER-REPORT for RP-ACK or RP-ERROR) may be sent to the network. The
entering of PDU is done similarly as specified in +CMGS command, except that the format of<ackpdu> is usedinstead of <pdu> (i.e. SMSC address field is not present). The PDU shall not be bounded by double quotes.

11.12.2 Syntax
Type
Set

Syntax
Text mode (+CMGF=1):

UBX-13002752 - R67

ResponseOK

11 Short Messages Service

ExampleAT+CNMA

Page 231 of 1001

u-blox cellular modules - AT commands manual

Type

Test

Syntax
AT+CNMA

Response

ExampleOK

PDU mode (+CMGF=0):
AT+CNMA[=<n>[,<length> [PDU isgiven<Ctrl-Z>/<ESC>]]]OK

AT+CNMA=1,5

AT+CNMA=?

Text mode (+CMGF=1):
OK
PDU mode (+CMGF=0):+CNMA: (list of supported <n>s)>0007000000 <Ctrl-Z>
OK
OK+CNMA: (0-2)
OKOK

11.12.3 Defined values
Parameter<n>Type
Number<length>NumberDescription
Allowed values:• 0: the command operates similarly as defined for the text mode
• 1: sends RP-ACK (or buffered result code received correctly)• 2: sends RP-ERROR (if PDU is not given, ME/TA shall send SMS-DELIVER-REPORTwith 3GPP TS 23.040 [8] TP-FCS value set to 'FF' (unspecified error cause))
PDU's length in octets without the Service Center's address

11.13 List message +CMGL+CMGLModules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time Error reference
Up to 3 min (<1 +CMS Errors for prompt ">"when present)

11.13.1 Description
Returns SMS messages with status value <stat> from message storage <mem1> to the DTE. If status of thereceived message is "received unread", status in the storage changes to "received read".
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Some SMS messages are displayed only when issuing AT+CSDH=1 (detailed SMS header information).

11.13.2 Syntax
Type
Set

Syntax
Text mode (+CMGF=1):
AT+CMGL[=<stat>]

Response
Command successful and
SMS-DELIVERs:+CMGL: <index>,<stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>]<data>[+CMGL: <index>,<stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>]<data>[...]]

ExampleAT+CMGL+CMGL: 303,"REC READ","+39340
1234999",,"08/08/06,10:01:38+08"
You have a missed called. Free
information provided by youroperator.
OK

OK
Command successful and
SMS-SUBMITs:+CMGL: <index>,<stat>,<da>,[<alpha>],[<toda>, <length>]<data>[+CMGL: <index>,<stat>,<da>,[<alpha>],[<toda>,<length>]<data>[...]]

UBX-13002752 - R67

11 Short Messages Service

Page 232 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
ExampleOK
Command successful and
SMS-STATUS-REPORTs:+CMGL: <index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>[+CMGL: <index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>[...]]OK
Command successful and
SMS-COMMANDs:+CMGL: <index>,<stat>,<fo>,<ct>[+CMGL: <index>,<stat>,<fo>,<ct>[...]]OK
Command successful and CBM
storage:+CMGL: <index>,<stat>,<sn>,<mid>,<page>,<pages><data>[+CMGL: <index>,<stat>,<sn>,<mid>,<page>,<pages>,<data>[...]]PDU mode (+CMGF=0):
AT+CMGL[=<stat>]

Test

AT+CMGL=?

OK
Command successful:+CMGL: <index>,<stat>,[<alpha>],<length>

AT+CMGL=1+CMGL: 305,1,,57 079193432900
1185440ED0D637396C7EBBCB0<pdu>
000909092708024802A050
003000303DEA0584CE60[+CMGL: <index>,<stat>,[<alpha>],
205D974791994769BDF3A90<length>]DB759687E9F534FD0DA2C9603419<pdu> [...]OK+CMGL: (list of supported <stat>s) +CMGL: ("REC UNREAD","RECREAD","STO UNSENT","STO SENT",
OK"ALL")
OK

11.13.3 Defined values
Parameter<stat>

Type
Number or
String<index><oa><alpha>NumberStringString<scts><tooa><length>StringNumberNumberUBX-13002752 - R67

Description
Number type in PDU mode (default value: 4), or string type in text mode (default
value: "ALL"); indicates the status of message in memory:• 0: in PDU mode or "REC UNREAD" in text mode: received unread SMS messages• 1: in PDU mode or "REC READ" in text mode: received read SMS messages• 2: in PDU mode or "STO UNSENT" in text mode: stored unsent SMS messages• 3: in PDU mode or "STO SENT" in text mode: stored sent SMS messages• 4: in PDU mode or "ALL" in text mode: all SMS messages
Storage position
Originator address
Alphanumeric representation of <da> or <oa> corresponding to the entry found in thephonebook 3GPP TS 24.008 [12]. The parameter is not managed.
Service center time stamp in time-string format; see the <dt> parameter
Type of address of <oa> - octet
Two meanings:• in text mode: number of characters• in PDU mode: PDU's length in octets without the Service Center's address. In
example 039121430100038166F6000004E374F80D: this is a PDU with Service
Center's number +1234, that generates the address 03912143 (4 octets). Thus inthis case <length> = 13.

11 Short Messages Service

Page 233 of 1001

u-blox cellular modules - AT commands manual

Parameter<data>Type
String<da><toda>
<fo>
<mr>
<ra>
<tora><dt>

StringNumberNumberNumberStringNumberString

<st>
<ct>
<sn>
<mid>
<page><pages><pdu>

NumberNumberNumberNumberNumberNumberString<dcs>

NumberDescription
This is the TP-User-Data in text mode; the decoding depends on the DCS (Data
Coding Scheme) and the FO (First Octect) of the SMS header 3GPP TS 23.040 [8];format:• if DCS indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS AT command description):
ME/TA converts GSM alphabet into current TE character set according to rulesof Annex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of GSM
7 bit default alphabet into two IRA character long hexadecimal number (e.g.
character Æ (GSM 7 bit default alphabet 28) is presented as 1C (IRA 49 and 67))
• if DCS indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number (e.g. octet withinteger value 42 is presented to TE as two characters 2A (IRA 50 and 65))
In the case of CBS: 3GPP TS 23.041 [9] CBM Content of Message in text mode
responses; format:• if DCS indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS AT command description):
ME/TA converts GSM alphabet into current TE character set according to rulesof Annex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of the GSM 7
bit default alphabet into two IRA character long hexadecimal number
if DCS indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each
8-bit octet into two IRA character long hexadecimal number
Destination address
Type of address of <da> - octet
First octet of the SMS TPDU (see 3GPP TS 23.040 [8])Message reference
Recipient address field
Type of address of <ra> - octet
Discharge time in format "yy/MM/dd,hh:mm:ss+zz"; the time zone is expressed insteps of 15 minutes. The range goes from -48 to +56
Status of an SMS STATUS-REPORT
TP-Command-Type (default 0)
CBM serial number
CBM message identifier
3GPP TS 23.041 [9] CBM Page Parameter bits 4-7 in integer format
3GPP TS 23.041 [9] CBM Page Parameter bits 0-3 in integer format
Protocol data unit: each 8-bit octet is presented as two IRA character longhexadecimal numbers, e.g. octet with integer value 42 is presented to TE as two
characters 2A (IRA 50 and 65)
Data Coding Scheme

11.14 Send message (+CMGS/+CMSS) set commands
conclusion configuration +UDCONF=13+UDCONF=13
Modules
Attributes

SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
NVM
No
-

Error reference+CME Error

11.14.1 Description
Allows +CMGS/+CMSS set commands to conclude the command execution before the SMS message has been
sent to the network, i.e. the final result code is returned before any transaction with network takes place.
The URC +UUCMSRES can be configured to have an indication if the sending was successful or not.

UBX-13002752 - R67

11 Short Messages Service

Page 234 of 1001

u-blox cellular modules - AT commands manual

11.14.2 Syntax
Type
Set

SyntaxAT+UDCONF=13,<sms_bitmap>

Response
OK

ExampleAT+UDCONF=13,3

Read

AT+UDCONF=13+UDCONF: 13,<sms_bitmap>

OK
AT+UDCONF=13

OK+UDCONF: 13,0

+UUCMSRES: <res>,<mr>OK+UUCMSRES: 0,41

URC

11.14.3 Defined values
Parameter<sms_bitmap>

Type
Number<res>

Number<mr>

NumberDescription
Bitmask representing the configuration of send message conclusion:• b0: enables/disables +CMGS/+CMSS set commands to issue the final result code
before the SMS message has been sent to the network. Allowed values:o 0 (factory-programmed value): does not provide the final result code before thetransaction with the network takes placeo 1: provides the final result code before the transaction with the network takesplace• b1: enables/disables the +UUCMSRES URC, which presents the SMS sending result(displayed only on the terminal where +CMGS/+CMSS has been issued). Allowed
values:o 0 (factory-programmed value): URC disabledo 1: URC enabled
SMS message sending result. Allowed values:• 0: no error• Other values: same as <err> in Appendix A.2
Message reference

11.15 Send message +CMGS+CMGS
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time Error reference
Up to 3 min (<1 +CMS Errors for prompt ">"when present)

11.15.1 Description
Sends a message from a DTE to the network (SMS-SUBMIT). The message reference value <mr> is returned to
the DTE for a successful message delivery. Optionally (when enabled by +CSMS AT command and the network
supports) <ackpdu> is returned. Values can be used to identify message upon unsolicited delivery status reportresult code. <Ctrl-Z> indicates that the SMS shall be sent, while <ESC> indicates aborting of the edited SMS.
The entered text/PDU is preceded by a ">" (Greater-Than sign) character, and this indicates that theinterface is in "text/PDU enter" mode. The DCD signal shall be in ON state while the text/PDU is entered.

11.15.2 Syntax
Type
Set

Syntax
Text mode (+CMGF=1):
AT+CMGS=<da>[,<toda>]<CR>

Response+CMGS: <mr>ExampleAT+CMGS="0171112233"<CR>

OK> This is the text<Ctrl-Z>> text is entered<Ctrl-Z/ESC>PDU mode (+CMGF=0):
AT+CMGS=<length><CR>+CMGS: 2+CMGS: <mr>[,<ackpdu>]
OK> PDU is given<Ctrl-Z/ESC>UBX-13002752 - R67

11 Short Messages Service

OK
AT+CMGS=13<CR>> 039121430100038166F600000
4E374F80D<Ctrl-Z>

Page 235 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Test

AT+CMGS=?

OK

Example+CMGS: 2
OK

11.15.3 Defined values
Parameter<da><toda><text><mr><length>Type
StringNumberStringNumberNumber<PDU>

String<ackpdu>StringDescription
Destination address
Type of address of <da> - octet
SMS String
Message reference
Two meanings:• in text mode: number of characters• in PDU mode: PDU's length in octets without the Service Center's address. In
example 039121430100038166F6000004E374F80D: is a PDU with Service Center's
number +1234, that generates the address 03912143 (4 octets). Thus in this case<length>=13.
Protocol Data Unit: each 8-bit octet of the PDU must be written as two IRA character
long hexadecimal numbers, e.g. octet with integer value 42 must be written as two
characters 2A (IRA 50 and 65)
See the 3GPP TS 23.040 [8] RP-User-Data element of RP-ACK PDU; the format issame as for <PDU> in case of SMS

11.15.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• The <ackpdu> parameter is not supported.

11.16 Write message to memory +CMGW+CMGW
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time
<10 s

Error reference+CMS Error

11.16.1 Description
Stores a message (SMS-DELIVER or SMS-SUBMIT) to memory storage <mem2> and returns the memory
location <index> of the stored message. <Ctrl-Z> indicates that the SMS shall be stored, while <ESC> indicatesaborting of the edited SMS.
The entered text/PDU is preceded by a ">" (Greater-Than sign) character, and this indicates that theinterface is in "text/PDU enter" mode. The DCD signal shall be in ON state while the text/PDU is entered.

11.16.2 Syntax
Type
Set

SyntaxResponse
Text mode (+CMGF=1):+CMGW: <index>
AT+CMGW[=<oa/da>[,<tooa/toda>[,OK<stat>]]]<CR>

ExampleAT+CMGW="091137880"<CR>> This is the text<Ctrl-Z>+CMGW: 303

text is entered<Ctrl-Z/ESC>PDU mode (+CMGF=0):+CMGW: <index>
AT+CMGW=<length>[,<stat>]<CR>OK
PDU is given<Ctrl-Z/ESC>

OK
AT+CMGW=13<CR>> 039121430100038166F600000
4E374F80D<Ctrl-Z>+CMGW: 303
OK

Test

AT+CMGW=?

UBX-13002752 - R67

OK

11 Short Messages Service

Page 236 of 1001

u-blox cellular modules - AT commands manual

11.16.3 Defined values
Parameter
<da>

Type
String<oa>

String<tooa>

Number<toda>

Number<stat>

Number or
String<text><index><length>StringNumberNumber<PDU>

StringDescription
TP-Destination-Address Address-Value field (see the 3GPP TS 23.040 [8]); BCD
numbers (or GSM 7 bit default alphabet characters) are converted to charactersof the currently selected TE character set (see the +CSCS AT command); type ofaddress given by <toda>
TP-Originating-Address Address-Value field (see the 3GPP TS 23.040 [8]); BCD
numbers (or GSM 7 bit default alphabet characters) are converted to charactersof the currently selected TE character set (see the +CSCS AT command); type ofaddress given by <tooa>
TP-Originating-Address Type-of-Address octet (see the 3GPP TS 24.011 [13]); see the<toda> parameter for the default value
TP-Destination-Address Type-of-Address octet (see the 3GPP TS 24.011 [13]); when
the first character of <da> is + (IRA 43) the default value is 145, otherwise it is 129)
Number type in PDU mode (default value: 2), or string type in text mode (default
value: "STO UNSENT"); it indicates the message status in memory:• 0: in PDU mode or "REC UNREAD" in text mode: received unread SMS messages• 1: in PDU mode or "REC READ" in text mode: received read SMS messages• 2: in PDU mode or "STO UNSENT" in text mode: stored unsent SMS messages• 3: in PDU mode or "STO SENT" in text mode: stored sent SMS messages
SMS string
Storage position
The parameter meaning depends on the message format:• In text mode: number of characters• In PDU mode: PDU's length in octets without the Service Center's address. In
example: 039121430100038166F6000004E374F80D is a PDU with Service Center's
number +1234, that generates the address 03912143 (4 octets). Thus in this case<length>=13.
Protocol Data Unit: each 8-bit octet of the PDU must be written as two IRA character
long hexadecimal numbers, e.g. an octet with integer value 42 must be written as two
characters 2A (IRA 50 and 65)

11.16.4 Notes
TOBY-L2 / MPCI-L2• The <stat> parameter is not supported.

11.17 Send message from storage +CMSS+CMSS
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time
Up to 3 min

Error reference+CMS Error

11.17.1 Description
Sends message with location value <index> from the preferred message storage <mem2> to the network(SMS-SUBMIT or SMS-COMMAND). If a new recipient address <da> is given for SMS-SUBMIT, it will be usedinstead of the one stored with the message. Reference value <mr> is returned to the DTE on successful
message delivery.

11.17.2 Syntax
Type
Set

Syntax
Text mode (+CMGF=1):

Response+CMSS: <mr>ExampleAT+CMSS=302

AT+CMSS=<index>[,<da>[,<toda>]] OK+CMSS: 3

PDU mode (+CMGF=0):+CMSS: <mr>

OK
AT+CMSS=302

AT+CMSS=<index>

OK+CMSS: 4

UBX-13002752 - R67

11 Short Messages Service

Page 237 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Test

AT+CMSS=?

OK

ExampleOK

11.17.3 Defined values
Parameter<index><da><toda><mr>

Type
NumberStringNumberNumberDescription
Storage position
Destination address
Type of address of <da> - octet
Message reference

11.18 Set text mode parameters +CSMP+CSMP
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
+CSAS
No

Response time< 10 sError reference+CMS Error

11.18.1 Description
Selects values for additional parameters needed when an SMS is sent to the network or placed in a storage
when text format message mode is selected. For more details see the 3GPP TS 23.038 [7] and the 3GPP TS
23.040 [8].

11.18.2 Syntax
Type
Set

SyntaxAT+CSMP=<fo>,<vp>[,<pid>[,<dcs>]]

Response
OK

ExampleAT+CSMP=17,167,0,0

Read

AT+CSMP?

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

OK+CSMP: 17,167,0,0

Test

AT+CSMP=?

OK
OK

OK

11.18.3 Defined values
Parameter
<fo>
<vp>

Type
NumberNumberDescription
First octet of the SMS TPDU (see 3GPP TS 23.040 [8])Format depending on the values of the bit3/bit4 of the <fo> (SMS-SUBMIT case):
Bit 3
0
0

Bit 4
0
1

1
1

0
1

•

FormatValidity period not present
Validity period present,
relative format
Reserved
Validity period present,
absolute format

Relative format: validity period, counted from when the SMS-SUBMIT is received by
the SMSC, in range 0-255 (the default value is 167); for more details see the 3GPPTS 23.040 [8]<vp>
0 to 143•

UBX-13002752 - R67

Validity period value(TP-VP + 1) x 5 minutes (i.e. 5 minutes
intervals up to 12 hours)
144 to 167
12 hours + ((TP-VP -143) x 30 minutes)
168 to 196(TP-VP - 166) x 1 day
197 to 255(TP-VP - 192) x 1 week
Absolute format: absolute time of the validity period termination in string format("yy/MM/dd,hh:mm:ss+zz") (see the 3GPP TS 23.040 [8]); the time zone isexpressed in steps of 15 minutes. The range goes from -48 to +56

11 Short Messages Service

Page 238 of 1001

u-blox cellular modules - AT commands manual

Parameter
<pid>
<dcs>

Type
NumberNumberDescription
TP-Protocol-Identifier (default value: 0); see the 3GPP TS 23.040 [8]Data Coding Scheme. The default value is 0

11.18.4 Notes
TOBY-L2 / MPCI-L2• The absolute format of the validity period is not supported.

11.19 Delete message +CMGD+CMGD
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
No
No

Response time
< 55 sError reference+CMS Error

11.19.1 Description
Deletes the message from the preferred message storage <mem1>, if <flag>=0 or not present, in location<index>. Otherwise the messages are deleted following the rules specified by <flag>.
If the <index> value is out of range (it depends on AT+CPMS command setting), then the "+CMS ERROR:
Invalid memory index" error result code is returned.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
When deleting a message from an empty location, the module returns the "OK" final result code.
LARA-R2 / TOBY-R2
It is possible to read SMSes in "ME" also without the PIN insertion (no access to SIM is required when<mem1>= "ME").

11.19.2 Syntax
Type
Set

SyntaxAT+CMGD=<index>[,<flag>]

Test

AT+CMGD=?

Response
OK

ExampleAT+CMGD=3

OK+CMGD: (list of supported+CMGD: (1-350),(0-4)<index>s),(list of supported <flag>s)OKOK

11.19.3 Defined values
Parameter<index><flag>

Type
NumberNumberDescription
Storage position
Deletion flag. If present, and different from 0, the <index> parameter is ignored:• 0 (default value): delete the message specified in <index>• 1: delete all the read messages from the preferred message storage, leaving unread
messages and stored mobile originated messages (whether sent or not) untouched• 2: delete all the read messages from the preferred message storage andsent mobile originated messages, leaving unread messages and unsent mobile
originated messages untouched• 3: delete all the read messages from the preferred message storage, sent andunsent mobile originated messages leaving unread messages untouched• 4: delete all the messages from the preferred message storage including unread
messages

11.19.4 Notes
SARA-G4 / SARA-G3 / LEON-G1• The "BM" memory entries cannot be deleted.

UBX-13002752 - R67

11 Short Messages Service

Page 239 of 1001

u-blox cellular modules - AT commands manual

11.20 Primary notification event reporting +CPNER+CPNER
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

11.20.1 Description
Configures the reporting of primary notification events when received from the network. Primary notification
events are used for Public Warning Systems like ETWS (Earthquake and Tsunami Warning Systems).
The UE will discard the duplicate primary notification.
The notification is considered a duplicate of the previous if it has equal <message_identifier> and <serial_
number> and arrives from the same PLMN. A primary notification message stored to detect duplication
is automatically cleared after three hours of not receiving any message.

11.20.2 Syntax
Type
Set

SyntaxAT+CPNER=<reporting>Response
OK

ExampleAT+CPNER=1

Read

AT+CPNER?

+CPNER: <reporting>OK+CPNER: 1

Test

AT+CPNER=?

OK+CPNER: (list of supported<reporting>s)

OK+CPNER: (0-1)
OK

OK+CPNERU: <message_identifier>,<serial_number>,<warning_type>

URC

11.20.3 Defined values
Parameter<reporting>Type
Number<message_
identifier><serial_number>

String<warning_type>

StringStringDescription
Configures the reporting of primary notification events:• 0 (factory-programmed value): primary notification events disabled• 1: primary notification events enabled
Hexadecimal character format. It contains the message identifier (2 bytes) of the
primary notification
Hexadecimal character format. It contains the serial number (2 bytes) of the primary
notification
Contains the warning type (2 bytes) of the primary notification.

11.21 Service center address +CSCA+CSCA
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
+CSAS
No

Response time< 10 sError reference+CMS Error

11.21.1 Description
Updates the SMSC address, through which mobile originated SMSes are transmitted. In text mode the setting
is used by send and write commands. In PDU mode the setting is used by the same commands, but only when
the length of SMSC address coded into <pdu> parameter equals zero.
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
This command sets the service center value both in the RAM (this value is actually the SMSC addressused) and in the SIM card. Through the read command the value of current service center stored in the
RAM is displayed. At the power on, the MT reads the SMSC address in the SIM card and the same value
is set in RAM.

UBX-13002752 - R67

11 Short Messages Service

Page 240 of 1001

u-blox cellular modules - AT commands manual

11.21.2 Syntax
Type
Set

SyntaxAT+CSCA=<sca>[,<tosca>]

Response
OK

ExampleAT+CSCA="0170111000",129

Read

AT+CSCA?

+CSCA: <sca>,<tosca>

OK+CSCA: "",129

Test

AT+CSCA=?

OK
OK

OK

11.21.3 Defined values
Parameter<sca><tosca>Type
StringStringDescription
Service center address.
Type of address of <sca> (for more details refer to 3GPP TS 24.008 [12]); the default
value is 145 when string includes '+', otherwise the default is 129.

11.22 Select cell broadcast message types +CSCB+CSCBModules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
+CSAS
No

Response time< 10 sError reference+CMS Error

11.22.1 Description
Selects which types of CBM's are to be received by the MT.

11.22.2 Syntax
Type
Set

SyntaxAT+CSCB=[<mode>[,<mids>[,<dcss>]]]

Response
OK

ExampleAT+CSCB=0,"1,5,10-11,40",""Read

AT+CSCB?

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

OK+CSCB: 0,"",""

Test

AT+CSCB=?

OK
OK+CSCB: (list of supported <mode>s) +CSCB: (0-1)
OKOK

11.22.3 Defined values
Parameter<mode>

Type
Number<mids>

String<dcss>

StringDescription
Allowed values:• 0 (default value and factory-programmed value): message types specified in<mids> and <dcss> accepted• 1: message types specified in <mids> and <dcss> not accepted
Contains all possible combinations of CBM message identifiers (<mid>). See the
3GPP TS 23.041 [9], chapter 9.4. When RAT is UMTS up to 2048 message identifiers
can be set; defining an exceeding combination will not cause an error result code andexceeding values will be ignored.
Contains all possible combinations of CBM data coding schemes (<dcs>). See the
3GPP TS 23.038 [7], chapter 5.

11.22.4 Notes•

If <mode>=0 and <mids> is an empty string, receiving of CB SMS is stopped.

TOBY-L4• When RAT is UMTS up to 2053 message identifiers can be set.

UBX-13002752 - R67

11 Short Messages Service

Page 241 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4006 / TOBY-L4106 / TOBY-L4206 / TOBY-L4906-01A / TOBY-L4906-51A• After the module boot issue the AT+CSCB=1 command before to perform some operations with +CSCB
AT command.
TOBY-L2 / MPCI-L2• The modules read on boot the files below from the USIM and they configure the CBM reception
accordingly:
o EFCBMID (Cell Broadcast Message Identifier for Data Download): this EF contains the message
identifier parameters which specify the type of content of the cell broadcast messages which are
to be passed to the USIM.
o EFCBMI (Cell Broadcast Message identifier selection): this EF contains the Message Identifier
Parameters which specify the type of content of the cell broadcast messages that the subscriber
wishes the UE to accept.
o EFCBMIR (Cell Broadcast Message Identifier Range selection): this EF contains ranges of cellbroadcast message identifiers that the subscriber wishes the UE to accept.
• The maximum number of <mids> is 30.
• These commands perform these actions:o AT+CSCB=0 enables all the indicationso AT+CSCB=1 disables all the indications• To activate a custom range of mids perform the following actions:1.
Power on the module, insert a valid SIM and insert its PIN (if needed).
2.
Read the current SIM configuration with AT+CSCB read command.
3.
Modify the configuration by adding or removing some <mids> and/or <dcss> ranges.
4.
Enabling or disabling the reception of all <mids> and <dcss> will be stored in NVM, but not in SIM
due to SIM data storage limitations.
5.
If the list must be modified after having enabled or disabled everything add or remove a <mids> or<dcss>, re-read the configuration with the AT+CSCB read command and then set it as needed.
LISA-U1• When RAT is UMTS up to 1024 message identifiers can be set.

11.23 Read concatenated message +UCMGR+UCMGR
Modules
Attributes

SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
<10 s

Error reference+CMS Error

11.23.1 Description
Returns the message with location value <index> from message storage <mem1> to the DTE and shows
additional information when the message is a segment of a concatenated one:
• SMS-DELIVER: the parameters <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length> shall be displayed
only if +CSDH=1 is set.
• SMS-SUBMIT: the parameters <toda>, <fo>, <pid>, <dcs>, <vp>, <sca>, <tosca>, <length> shall be
displayed only if +CSDH=1 is set.
• SMS-COMMAND: <pid>, <mn>, <da>, <toda>, <length>, <cdata> shall be displayed only if +CSDH=1 is set.
The syntax AT+UCMGR=0 allows to display an SMS class 0 if it is signalized to MT, because no MMI isavailable in the MT (see also the +CNMI AT command notes).
If the received message status is "received unread", the status in the storage changes to "received read".
The command is supported only for text mode (+CMGF=1).
If the <index> value is out of range (it depends on the preferred message storage, +CPMS command,
settings) or it refers to an empty position, then the "+CMS ERROR: invalid memory index" error result
code is returned.

UBX-13002752 - R67

11 Short Messages Service

Page 242 of 1001

u-blox cellular modules - AT commands manual

11.23.2 Syntax
Type
Set

SyntaxAT+UCMGR=<index>

Response
SMS-DELIVER+UCMGR: <stat>,<oa>,[<alpha>],<scts>[,<tooa>, <fo>,<pid>,<dcs>,<sca>,<tosca>,<length>][,<seq>,<max>,<iei>,<ref>]<data>OK
SMS-SUBMIT+UCMGR: <stat>,<da>,[<alpha>][<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<length>][,<seq>,<max>,<iei>,<ref>]ExampleAT+UCMGR=1+UCMGR: "REC READ","+393488535999",,"07/04/05,18:0
2:28+08",145,4,0,0,"+393492000
466",145,153,1,2,0,127
u-blox reserves all rights to thisdocument and the information
contained herein. Reproduction, use
or disclosure to third parties without
express permis
OK<data>OK
SMS-STATUS-report+UCMGR:<stat>,<fo>,<mr>,[<ra>],[<tora>]<scts><dt>,<st>OK
SMS-COMMAND+UCMGR: <stat>,<fo>,<ct>[,<pid>,[<mn>],[<da>],[<toda>],<length>[<cdata>]]OK
CBM storage+UCMGR: <stat>,<sn>,<mid>,<dcs>,<page>,<pages><data>
Test

AT+UCMGR=?

OK
OK

11.23.3 Defined values
Parameter<index><stat>

Type
NumberString<oa><alpha>StringString<scts><tooa>
<fo>
<pid>
<dcs>
<sca>
<tosca>StringNumberNumberNumberNumberStringNumber<length>
<seq>
<max>
<iei>

NumberNumberNumberNumberUBX-13002752 - R67

Description
Storage position
Indicates the status of message in memory:• "REC UNREAD": received unread SMS• "REC READ": received read SMS• "STO UNSENT": stored unsent SMS• "STO SENT": stored sent SMS
Originator address
Alphanumeric representation of <da> or <oa> corresponding to the entry found in thephonebook 3GPP TS 24.008 [12]. The parameter is not managed.
Service center time stamp in time-string format, refer to <dt>Type of address of <oa> - octet
First octet of the SMS TPDU (see 3GPP TS 23.040 [8])TP-Protocol-Identifier (default 0); see 3GPP TS 23.040 [8]Data Coding Scheme
Service center address field
Type of address of <sca> - octet in Number format (for more details see 3GPP TS
24.008 [12]); default 145 when string includes '+', otherwise default 129
Number of characters
Sequence number of the current short message (1-255)
Maximum number of short messages in the concatenated short message (1-255)
Information Element Identifier, the possible values are the following:• 0: Concatenated short messages, 8-bit reference number

11 Short Messages Service

Page 243 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

<ref>

Number<data>

String<da><toda><vp>

StringNumberNumberDescription• 8: Concatenated short messages, 16-bit reference number
Concatenated short message reference number:• 0-255: concatenated short messages, 8-bit reference number case• 0-65535: concatenated short messages, 16-bit reference number caseIn the case of SMS: 3GPP TS 23.040 [8] TP-User-Data in text mode responses;
format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS AT command description):
ME/TA converts GSM alphabet into current TE character set according to rulesof 3GPP TS 27.005 [15] Annex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of GSM
7 bit default alphabet into two IRA character long hexadecimal number (e.g.
character Æ (GSM 7 bit default alphabet 28) is presented as 1C (IRA 49 and 67))
• if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number (e.g. octet withinteger value 42 is presented to TE as two characters 2A (IRA 50 and 65))
In the case of CBS: 3GPP TS 23.041 [9] CBM Content of Message in text mode
responses; format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS AT command description):
ME/TA converts GSM alphabet into current TE character set according to rulesof 3GPP TS 27.005 [15] Annex Ao if TE character set is "HEX": ME/TA converts each 7-bit character of the GSM 7
bit default alphabet into two IRA character long hexadecimal number
if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number
Destination address
Type of address of <da> - octet
Format depending of the <fo> setting:• Relative format: validity period starting from when the SMS is received by the
SMSC, in range 0-255 (default value 167); for more details see 3GPP TS 23.040 [8]<vp>
0 to 143<mr><ra><tora><scts><dt>

NumberStringNumberStringString

<st>
<ct>
<mn>
<mid>
<cdata><sn><page><pages>NumberNumberNumberNumberStringNumberNumberNumberUBX-13002752 - R67

Validity period value(TP-VP + 1) x 5 minutes (i.e. 5 minutes
intervals up to 12 hours)
144 to 167
12 hours + ((TP-VP -143) x 30 minutes)
168 to 196(TP-VP - 166) x 1 day
197 to 255(TP-VP - 192) x 1 week
• Absolute format: absolute time of the validity period termination in string format("yy/MM/dd,hh:mm:ss+zz") (refer to 3GPP TS 23.040 [8]); the time zone isexpressed in steps of 15 minutes. The range goes from -48 to +56
Message reference
Recipient address field
Type of address of <ra> - octet
Service center time stamp in time-string format, refer to <dt>Discharge time in format "yy/MM/dd,hh:mm:ss+zz"; the time zone is expressed insteps of 15 minutes. The range goes from -48 to +56
Status of an SMS STATUS-REPORT
TP-Command-Type (default 0)
3GPP TS 23.040 [8] TP-Message-Number in integer format
CBM message identifier
TP-Command-Data in text mode responses
CBM serial number
3GPP TS 23.041 [9] CBM page parameter bits 4-7 in integer format
3GPP TS 23.041 [9] CBM page parameter bits 0-3 in integer format

11 Short Messages Service

Page 244 of 1001

u-blox cellular modules - AT commands manual

11.24 List concatenated message +UCMGL+UCMGL
Modules
Attributes

SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time Error reference
Up to 3 min (<1 +CMS Errors for prompt ">"when present)

11.24.1 Description
Returns SMS messages with status value <stat> from message storage <mem1> to the DTE and shows
additional information when the message is a segment of a concatenated one:
• SMS-DELIVER: the parameters <tooa>, <length> shall be displayed only if +CSDH=1 is set.
• SMS-SUBMIT: the parameters <toda>, <length> shall be displayed only if +CSDH=1 is set.
If status of the received message is "received unread", status in the storage changes to "received read".
The command is supported only for text mode (+CMGF=1).

11.24.2 Syntax
Type
Set

SyntaxAT+UCMGL[=<stat>]

Response
SMS-DELIVERs:+UCMGL: <index>,<stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>][,<seq>,<max>,<iei>,<ref>]<data>[+UCMGL: <index>,<stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>][,<seq>,<max>,<iei>,<ref>]<data>[...]]OK

ExampleAT+UCMGL+UCMGL: 304,"REC READ","+39340
1234999",,"08/08/06,10:01:38+08",
145,152,1,2,8,32767
u-blox reserves all rights to thisdocument and the information
contained herein. Reproduction, use
or disclosure to third parties without
express permi+UCMGL: 305,"REC READ","+39340
1234999",,"08/08/06,10:01:40+08",
145,29,2,2,8,32767
ssion is strictly prohibited.
OK

SMS-SUBMITs:+UCMGL: <index>,<stat>,<da>,[<alpha>],[<toda>, <length>][,<seq>,<max>,<iei>,<ref>]<data>[+UCMGL: <index>,<stat>,<da>,[<alpha>],[<toda>,<length>][,<seq>,<max>,<iei>,<ref>]<data>[...]]OK
SMS-STATUS-REPORTs:+UCMGL: <index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>[+UCMGL: <index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st> [...]]OK
SMS-COMMANDs:+UCMGL: <index>,<stat>,<fo>,<ct>[+UCMGL: <index>,<stat>,<fo>,<ct>[...]]OK

UBX-13002752 - R67

11 Short Messages Service

Page 245 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
CBM storage:+UCMGL: <index>,<stat>,<sn>,<mid>,<page>,<pages><data>

Example[+UCMGL: <index>,<stat>,<sn>,<mid>,<page>,<pages>,<data>[...]]
Test

AT+UCMGL=?

OK+UCMGL: (list of supported <stat>s) +UCMGL: ("REC UNREAD","RECREAD","STO UNSENT","STO SENT",
OK"ALL ")
OK

11.24.3 Defined values
Parameter<stat>Type
String<index><oa><alpha>NumberStringString<scts><tooa><length>
<seq>
<max>
<iei>

StringNumberNumberNumberNumberNumber<ref>

Number<data>

String<da>

UBX-13002752 - R67

StringDescription
Indicates the status of message in memory:• "REC UNREAD": received unread SMS messages• "REC READ": received read SMS messages• "STO UNSENT": stored unsent SMS messages• "STO SENT": stored sent SMS messages• "ALL": all SMS messages (default value)
Storage position
Originator address
Alphanumeric representation of <da> or <oa> corresponding to the entry found in thephonebook 3GPP TS 24.008 [12]. The parameter is not managed.
Service center time stamp in time-string format; refer to <dt>Type of address of <oa> - octet
Number of characters
Sequence number of the current short message (1-255)
Maximum number of short messages in the concatenated short message (1-255)
Information Element Identifier, the possible values are the following:• 0: concatenated short messages, 8-bit reference number• 8: concatenated short messages, 16-bit reference number
Concatenated short message reference number:• 0-255: concatenated short messages, 8-bit reference number case• 0-65535: concatenated short messages, 16-bit reference number caseIn the case of SMS: 3GPP TS 23.040 [8] TP-User-Data in text mode responses;
format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS AT command description):
ME/TA converts GSM alphabet into current TE character set according to rulesof 3GPP TS 27.005 Annex A [15]o if TE character set is "HEX": ME/TA converts each 7-bit character of GSM
7 bit default alphabet into two IRA character long hexadecimal number (e.g.
character Æ (GSM 7 bit default alphabet 28) is presented as 1C (IRA 49 and 67))
• if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number (e.g. octet withinteger value 42 is presented to TE as two characters 2A (IRA 50 and 65))
In the case of CBS: 3GPP TS 23.041 [9] CBM Content of Message in text mode
responses; format:• if <dcs> indicates that 3GPP TS 23.038 [7] GSM 7 bit default alphabet is used:
o if TE character set other than "HEX" (see the +CSCS AT command description):
ME/TA converts GSM alphabet into current TE character set according to rulesof 3GPP TS 27.005 [15] Annex A• if TE character set is "HEX": ME/TA converts each 7-bit character of the GSM 7 bit
default alphabet into two IRA character long hexadecimal number
if <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts
each 8-bit octet into two IRA character long hexadecimal number
Destination address

11 Short Messages Service

Page 246 of 1001

u-blox cellular modules - AT commands manual

Parameter<toda>
<fo>
<mr>
<ra>
<tora><dt>

Type
NumberNumberNumberStringNumberString

<st>
<ct>
<sn>
<mid>
<page><pages><dcs>

NumberNumberNumberNumberNumberNumberNumberDescription
Type of address of <da> - octet
First octet of the SMS TPDU (see 3GPP TS 23.040 [8])Message reference
Recipient address field
Type of address of <ra> - octet
Discharge time in format "yy/MM/dd,hh:mm:ss+zz"; the time zone is expressed insteps of 15 minutes. The range goes from -48 to +56
Status of an SMS STATUS-REPORT
TP-Command-Type (default 0)
CBM serial number
CBM message identifier
3GPP TS 23.041 [9] CBM Page Parameter bits 4-7 in integer format
3GPP TS 23.041 [9] CBM Page Parameter bits 0-3 in integer format
Data Coding Scheme

11.25 Send concatenated message +UCMGS+UCMGS
Modules
Attributes

SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time Error reference
Up to 3 min (<1 +CMS Errors for prompt ">"when present)

11.25.1 Description
Sends one segment of a concatenated message from a DTE to the network (SMS-SUBMIT). The message
reference value <mr> is returned to the DTE for a successful message delivery. <Ctrl-Z> indicates that the
SMS shall be sent, while <ESC> indicates aborting of the edited SMS.
The command is supported only for text mode (+CMGF=1).
The entered text is preceded by a ">" (Greater-Than sign) character, and this indicates that the interface
is in "text enter" mode. The DCD signal shall be in ON state while the text is entered.

11.25.2 Syntax
Type
Set

SyntaxResponse
AT+UCMGS=<da>,[<toda>],<seq>, +UCMGS: <mr><max>,<iei>,<ref><CR>OK
text is entered<Ctrl-Z/ESC>

ExampleAT+UCMGS="0171112233",,1,2,0,
127<CR>> u-blox reserves all rights to thisdocument and the information
contained herein. Reproduction, use
or disclosure to third parties without
express permis<Ctrl-Z>+UCMGS:2
OK
AT+UCMGS="0171112233",,2,2,0,
127<CR>> sion is strictly prohibited.<Ctrl-Z>+UCMGS:3
OK

Test

AT+UCMGS=?

OK

11.25.3 Defined values
Parameter<da>

UBX-13002752 - R67

TypeStringDescription
Destination address

11 Short Messages Service

Page 247 of 1001

u-blox cellular modules - AT commands manual

Parameter<toda>
<seq>
<max>
<iei>

<ref>

<text><mr>

Type
NumberNumberNumberNumberDescription
Type of address of <da> - octet
Sequence number of the current short message (1-255)
Maximum number of short messages in the concatenated short message (1-255)
Information Element Identifier, the possible values are the following:

Number• 0: Concatenated short messages, 8-bit reference number• 8: Concatenated short messages, 16-bit reference number
Concatenated short message reference number:

StringNumber

• 0-255: Concatenated short messages, 8-bit reference number case• 0-65535: Concatenated short messages, 16-bit reference number case
SMS String
Message reference

11.26 Write concatenated message to memory +UCMGW+UCMGW
Modules
Attributes

SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time< 10 sError reference+CMS Error

11.26.1 Description
Stores one segment of a concatenated message (SMS-DELIVER or SMS-SUBMIT) to memory storage<mem2> and returns the memory location <index> of the stored message. <Ctrl-Z> indicates that the SMS
shall be stored, while <ESC> indicates aborting of the edited SMS.
The command is supported only for text mode (+CMGF=1)
The entered text is preceded by a ">" (Greater-Than sign) character, and this indicates that the interface
is in "text enter" mode. The DCD signal shall be in ON state while the text is entered.

11.26.2 Syntax
Type
Set

SyntaxResponse
AT+UCMGW=[<oa/da>],[<tooa/+UCMGW: <index>
toda>],[<stat>],<seq>,<max>,<iei>,
OK<ref><CR>
text is entered<Ctrl-Z/ESC>

ExampleAT+UCMGW="091137880",,,1,2,8,32767<CR>> u-blox reserves all rights to thisdocument and the information
contained herein. Reproduction, use
or disclosure to third parties without
express permi<Ctrl-Z>+UCMGW:302
OK
AT+UCMGW="091137880",,,2,2,8,32767<CR>> ssion is strictly prohibited.<CtrlZ>+UCMGW:303
OK

Test

AT+UCMGW=?

OK

11.26.3 Defined values
Parameter<da>

UBX-13002752 - R67

TypeStringDescription
3GPP TS 23.040 [8] TP-Destination-Address Address-Value field in string format;
BCD numbers (or GSM 7 bit default alphabet characters) are converted to charactersof the currently selected TE character set (refer command +CSCS in 3GPP TS 27.007[2]; type of address given by <toda>

11 Short Messages Service

Page 248 of 1001

u-blox cellular modules - AT commands manual

Parameter
<oa>

Type
String<tooa>

Number<toda>

Number<stat>

String

<seq>
<max>
<iei>

NumberNumberNumber<ref>

Number<text><index>StringNumberDescription
3GPP TS 23.040 [8] TP-Originating-Address Address-Value field in string format;
BCD numbers (or GSM 7 bit default alphabet characters) are converted to charactersof the currently selected TE character set (refer command +CSCS chapter Chapter
4.10); type of address given by <tooa>
3GPP TS 24.011 [13] TP-Originating-Address Type-of-Address octet in integer format(default refer <toda>)
3GPP TS 24.011 [13] TP-Destination-Address Type-of-Address octet in integer format(when first character of <da> is + (IRA 43) default is 145, otherwise default is 129)
Indicates the status of message in memory:• "REC UNREAD": received unread SMS messages• "REC READ": received read SMS messages• "STO UNSENT": stored unsent SMS messages• "STO SENT": stored sent SMS messages (default value)
Sequence number of the current short message (1-255)
Maximum number of short messages in the concatenated short message (1-255)
Information Element Identifier, the possible values are the following:• 0: Concatenated short messages, 8-bit reference number• 8: Concatenated short messages, 16-bit reference number
Concatenated short message reference number:• 0-255: Concatenated short messages, 8-bit reference number case• 0-65535: Concatenated short messages, 16-bit reference number case
SMS String
Storage position

11.27 More messages to send +CMMS+CMMS
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
+CMS Error

11.27.1 Description
Controls the continuity of SMS relay protocol link. When enabled, multiple SMS messages can be sent much
faster as link is kept open.

11.27.2 Syntax
Type
Set

SyntaxAT+CMMS=[<mode>]

Response
OK

ExampleAT+CMMS=2

Read

AT+CMMS?

+CMMS: <mode>

OK+CMMS: 2

Test

AT+CMMS=?

OK+CMMS: (list of supported<mode>s)OK+CMMS: (0-2)
OKOK

11.27.3 Defined values
Parameter<mode>

UBX-13002752 - R67

Type
NumberDescription
Allowed values:• 0 (default value): disabled

11 Short Messages Service

Page 249 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 1: keep enabled until the time between the response of the latest message sendcommand (such as +CMGS) and the next send command exceeds 5 s, then close
the link and switch <mode> automatically back to 0
• 2: keep permanently enabled. The link is closed after each send sequence, but<mode> is not switched back to 0

11.28 Peek message +UCMGP+UCMGP
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
<10 s
+CMS Error

11.28.1 Description
Returns the message with location value <index> from message storage <mem1> to the DTE, the same as+CMGR does.
The SMS message is only 'peeked', i.e. its status is not forced to "received read SMS mode" after reading.
The syntax, defined values and remarks are the same as described for +CMGR.
The PIN verification is not required when the preferred memory storage is "ME".

11.28.2 Syntax
Type
Set

Syntax
Text mode (+CMGF=1):

Response(SMS-DELIVER)

ExampleAT+UCMGP=303

AT+UCMGP=<index>+UCMGP: <stat>,<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]+UCMGP: "REC UNREAD","+393488535999",,"07/04/05,18:0
2:28+08",145,4,0,0,"+393492000
466",145,93<data>OK(SMS-SUBMIT)+UCMGP: <stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<length>]

You have a missed called. Free
information provided by youroperator.
OK<data>OK(SMS-STATUS-report)+UCMGP: <stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>OK(SMS-COMMAND)+UCMGP: <stat>,<fo>,<ct>[,<pid>,[<mn>],[<da>],[<toda>],<length>[<cdata>]]OK(CBM storage)+UCMGP: <stat>,<sn>,<mid>,<dcs>,<page>,<pages><data>

UBX-13002752 - R67

11 Short Messages Service

Page 250 of 1001

u-blox cellular modules - AT commands manualType

SyntaxPDU mode (+CMGF=0):
AT+UCMGP=<index>

Response
OK+UCMGP: <stat>,[<alpha>],<length><pdu>
OK

ExampleAT+UCMGP=1+UCMGP: 0,,40
0791934329002000040C9193230
982
6614000080703280452180
18D4F29CF
E06B5CBF379F87C4EBF41E4340
82E7F
DBC3
OK

Test

AT+UCMGP=?

OK

11.28.3 Defined values
Parameter<index>Type
NumberDescription
Storage position

11.29 Message waiting indication +UMWI+UMWI
Modules

Attributes

TOBY-L4006 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

11.29.1 Description
Provides information regarding the Message Waiting Indication (MWI) third level method (3GPP defined in
3GPP TS 23.040 [8]) and CPHS method [53] following AT&T Device Requirements [48].
The set command enables / disables the URC presentation. The URCs are by default enabled.
MWI is based on specific EFs not present in all SIM cards. In case these EFs are not present, the informationtext response is an error result code ("+CME ERROR: operation not allowed" if +CMEE is set to 2) and no URCs
will be displayed.
The URCs are displayed in groups of variable number which depends on the EFs present in the SIM card
3GPP TS 31.102 [18] and Common PCN Handset Specification [53].

11.29.2 Syntax
Type
Set

SyntaxAT+UMWI=<mode>

Read

AT+UMWI?

Test

AT+UMWI=?

Response
OK

ExampleAT+UMWI=1

OK+UMWI: <mode>,<status>,<type>[, +UMWI: 1,0,1<count>]+UMWI: 1,0,2[+UMWI: <mode>,<status>,<type>[,+UMWI: 1,1,3,255<count>][...]]+UMWI: 1,0,4
OK
OK+UMWI: (list of supported <mode>s) +UMWI: (0-1)

URC

OK
OK
+UMWI: <status>,<type>[,<count>] +UMWI: 1,1,3

UBX-13002752 - R67

11 Short Messages Service

Page 251 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Example[+UMWI: <status>,<type>[,<count>] +UMWI: 1,2,5[...]]+UMWI: 1,3,255+UMWI: 0,4

11.29.3 Defined values
Parameter<mode>

Type
Number<status>Number<type>

Number<count>NumberDescription
Indicates whether the +UMWI URC is enabled or not:• 0: disable the +UMWI URC• 1 (factory-programmed value): enable the +UMWI URC
Indicator the status for the respective <type>:• 0: clear; no messages waiting• 1: set; messages waiting
Indicates the basic message indication type:• 1: Voice Message Waiting (third level method) or Voice Message Waiting on Line 1(CPHS method)• 2: Fax Message Waiting• 3: Electronic Mail Message Waiting• 4: Extended Message Type Waiting (i.e. see the 3GPP TS 23.038 [7])• 5: Video Message Waiting• 6: Voice Message Waiting on Line 2 (CPHS method)• 7: reserved for future use
Number of messages waiting for the respective <type>, range 1-255. 255 means thatthe number of waiting messages is unknown.

11.29.4 Notes•

If <status>=0, the <count> parameter is omitted.

11.30 Earthquake and Tsunami Warning System configuration+UETWCFG+UETWCFG
Modules
Attributes

LARA-R220
SARA-U201-63B
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

11.30.1 Description
Configures the reception of the Earthquake and Tsunami Warning System (ETWS) notifications. The
duplication detection is done based on 3GPP TS 23.041 [9].

11.30.2 Syntax
Type
Set

Read

SyntaxAT+UETWCFG=<PrimaryNtf>,<SecondaryNtf>,<SecondaryCfg>,<DuplicateNtf>
AT+UETWCFG?

Test

AT+UETWCFG=?

Response
OK

ExampleAT+UETWCFG=1,1,0,0
OK

AT+UETWCFG: <PrimaryNtf>,+UETWCFG: 1,1,0,0<SecondaryNtf>,<SecondaryCfg>,
OK<DuplicateNtf>+UETWCFG: (list of the supported +UETWCFG: (0,1),(0,1),(0,1),(0,1)<PrimaryNtf>s),(list of theOKsupported <SecondaryNtf>s),(list of
the supported <SecondaryCfg>s),(list of the supported<DuplicateNtf>s)
OK

UBX-13002752 - R67

11 Short Messages Service

Page 252 of 1001

u-blox cellular modules - AT commands manual

11.30.3 Defined values
Parameter<PrimaryNtf>

Type
Number<SecondaryNtf>

Number<SecondaryCfg>

Number<DuplicateNtf>

NumberDescription
Primary notification status:• 0: primary notification disabled• 1: primary notification enabled
Configures the reception of the secondary notification, independent of the receptionof the corresponding primary notification:• 0: disable the immediate reception of the secondary notification• 1: enable the immediate reception of the secondary notification
Configures the security configuration:• 0: security check disabled• 1: security check enabled
Configures the setting for ignoring duplicate notifications:• 0: ignore all duplicate notifications• 1: ignore duplicate secondary notifications

11.30.4 Notes
SARA-U201-63B• The command is not supported by SARA-U201-63B-00.

11.31 Start ETWS notifications +UETWNTFYSTART+UETWNTFYSTART
Modules
LARA-R220
SARA-U201-63B
SyntaxPIN required
Attributes
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

11.31.1 Description
Starts the ETWS warning notifications:• Primary Notification: is the information which is used specifically in the ETWS to notify users about themost urgent event in seconds rather than minutes, such as imminent occurrence of Earthquake.
• Secondary Notification: is the information which is used specifically in the ETWS to notify users about
supplementary information that is of lesser urgency such as instructions on what to do / where to get help,
for example, map to refuge facilities, time table of food distribution.
These information, in general, would be issued by the local government. The coding scheme decides the format
in which this URC is displayed. See <CbData> description below for more details.

11.31.2 Syntax
Type
Set

Read
Test

SyntaxResponse
AT+UETWNTFYSTART=
OK<WarningType>[,<NrRanges>[,<MidRangeLow_1>,<MidRangeHigh_
1>[,...<MidRangeLow_n>,<MidRangeHigh_n>]]]AT+UETWNTFYSTART?
AT+UETWNTFYSTART:<WarningType>
AT+UETWNTFYSTART=?

+UETWNTFYSTART: (list of the
supported <WarningType>s) [,(listof the supported <NrRanges>),(listof the supported <MidRangeLow_n>s),(list of the supported<MidRangeHigh_n>s)]

URC

OK+UETWPRIWARN: <SerialNo>,<MsgId>,<WarningTypePar>,<SecurityStatus>

UBX-13002752 - R67

11 Short Messages Service

ExampleAT+UETWNTFYSTART=5,1,40961,
40961
OK+UETWNTFYSTART: 5
OK+UETWNTFYSTART: (0-6),(1-100),(0-65535),(0-65535)
OK

Page 253 of 1001

u-blox cellular modules - AT commands manual

Type
URC

SyntaxResponse+UETWSECWARN: <SerialNo>,<MsgId>,<CodingScheme>,<CurrentPage>,<NoPages>,<CbData>

Example11.31.3 Defined values
Parameter<WarningType>Type
Number<NrRanges><MidRangeLow_n><MidRangeHigh_n><SerialNo>

NumberNumberNumberNumber<MsgId>Number<SecurityStatus>

Number

<CodingScheme>

Number<CurrentPage><NoPages><CbData>

NumberNumberString<WarningTypePar>

NumberUBX-13002752 - R67

Description
Sets the warning type when the ETWS is used. Allowed warning type values (see the
3GPP TS 23.041 [9]):• 0: only earthquake• 1: only tsunami• 2: both earthquake and tsunami• 3: test mode will be activated• 4: others• 5: MSG ID range list for non-test Message identifiers is used
• 6: MSG ID range list for Test Message identifiers is used
Number of message identifiers ranges
Message identifier low range
Message identifier high range
16-bit integer which identifies a particular CBS message (which may be one to fifteen
pages in length) from the source and type indicated by the Message Identifier andis altered every time the CBS message with a given Message Identifier is changed.
The two octets of the Serial Number field are divided into a 2-bit Geographical Scope(GS) indicator, a 10-bit Message Code and a 4-bit Update Number. The parameter isdefined in the 3GPP TS 23.041 [9].
The message identifier parameter identifies the source and type of the CBS message.
For example, "Automotive Association"(= source), "Traffic Reports" (= type) could
correspond to one value. A number of CBS messages may originate from the same
source and/or be of the same type. These will be distinguished by the Serial Number.
The Message Identifier is coded in binary. The parameter is defined in the 3GPP TS
23.041 [9].
Indicates brief ETWS security status. Allowed values:• 0: default, no security check done
• 1: security check passed• 2: no security parameters have been received• 3: security check failed
The parameter is defined in 3GPP TS 23.041 [9]Identifies the alphabet or coding employed for the message characters and message
handling at the MS/UE and is passed transparently from the CBC to the MS/UE. The
CBS Data Coding Scheme indicates the intended handling of the message at the MS,
the character set/coding, and the language (when applicable).
Any reserved codings shall be assumed to be the GSM 7 bit default alphabet (thesame as codepoint 00001111) by a receiving entity. This parameter is defined in the
3GPP TS 23.038 [7].
The current page number being displayed
Total number of pages within the message
The raw data of CBS will be unpacked and displayed in text format, in case the coding
scheme is decoded as English language (see the 3GPP TS 23.041 [9]). If not, the PDU
format of the data (each page) is output as below:+UETWSECWARN: <length><CR><LF><pdu>
Two bytes number in decimal format, that can be converted into hex format andinterpreted as per the 3GPP TS 23.041 [9]):• Octet 1, bit 1-7: warning type value• Octet 1, bit 0: emergency• Octet 2, bit 7: pop-up• Octet 2, bit 6-0: padding

11 Short Messages Service

Page 254 of 1001

u-blox cellular modules - AT commands manual

11.31.4 Notes•••

If <WarningType>=3 (test mode) is set while the ETWS notification reception has been already started
for another warning type, an error result code is returned.
Optional parameters <NrRanges>, <MidRangeLow_n> and <MidRangeHigh_n> can be entered only if the<WarningType> parameter is set to 5 or 6.
The <MidRangeLow_n> and <MidRangeHigh_n> parameters shall be input in decimal format e.g. for mid
value 0xa001 the command to be issued is AT+UETWNTFYSTART=5,1,40961,40961.

SARA-U201-63B• The command is not supported by SARA-U201-63B-00.
• <WarningType> values 5 and 6, as well as the optional parameters <NrRanges>, <MidRangeLow_n> and<MidRangeHigh_n>, are not supported.
• If no <WarningType> has been configured, the read command will return 255.

11.32 Stop ETWS notifications +UETWNTFYSTOP+UETWNTFYSTOP
Modules
LARA-R220
SARA-U201-63B
SyntaxPIN required
Attributes
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

11.32.1 Description
Stops the different ETWS warning notifications.

11.32.2 Syntax
Type
Set

SyntaxAT+UETWNTFYSTOP=<WarningType>

Response
OK

Test

AT+UETWNTFYSTOP=?

+UETWNTFYSTOP: (list of the
supported <WarningType>s)

ExampleAT+UETWNTFYSTOP=5
OK+UETWNTFYSTOP: (0-6,255)
OKOK

11.32.3 Defined values
Parameter<WarningType>Type
NumberDescription
Stops the corresponding warning type when used. The following values are allowed
and indicates these warning types (see the 3GPP TS 23.041 [9]):• 0: only earthquake• 1: only tsunami• 2: both earthquake and tsunami• 3: test mode
• 4: others• 5: MSG ID range list for non-test Message Identifiers• 6: MSG ID range list for Test Message Identifiers• 255: stops the ETWS warning reception for all warning type values

11.32.4 Notes
SARA-U201-63B• The command is not supported by SARA-U201-63B-00.

UBX-13002752 - R67

11 Short Messages Service

Page 255 of 1001

u-blox cellular modules - AT commands manual

12 Supplementary services
12.1 Introduction
Supplementary services (SS) allow to configure how the incoming or mobile originated voice calls are handled.
Cellular standards provide call related supplementary services (CRSS), that operate on calls while they are
active (e.g. performing call hold or merge of calls in a multi-party conversation), and others that imply asignalling session with the mobile network to perform query and set of the specific supplementary service (e.g.
call barring or call forwarding). Unstructured Supplementary Services Data (USSD) are mobile terminated ororiginated signalling transactions, where a binary string is transmitted to the network to retrieve informationon the subscription (e.g. residual credit) or sent from the NW to notify the subscriber of specific events.
On VoLTE capable modules, supplementary services operate on VoLTE calls in the same way they work on
legacy speech calls. Query and set of supplementary services are performed via XCAP (XML Configuration
Access Protocol), that is an HTTP-based service that uses a specific default EPS bearer on a specific XCAP APN(see +UIMSCFG, XCAP_APN value of <ImsConfig> parameter) to accomplish the query or the update of the SS.
Usually supplementary services via XCAP require IMS registration to be performed; if the device has not yet
successfully completed IMS registration, the SS is carried out via CSFB if 2G or 3G RAT is supported. USSD via
IMS are not supported on VoLTE capable modules and are carried out via CSFB if 2G or 3G RAT is supported.
LARA-R202 / TOBY-R200
On 2G and 3G networks, the supplementary services can be sent only if the network support XCAP, either
via an IMS context or CS domain.
LARA-R202 / LARA-R203 / TOBY-R200
On LTE networks, if the IMS is not yet available, the request will be routed to the CS domain on LTE.
LARA-R202
Supplementary services performed via XCAP do not require the module to be IMS registered.

12.2 Call forwarding +CCFC+CCFC
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
Yes

Response time
Up to 3 min

Error reference+CME Error

12.2.1 Description
Controls the call forwarding supplementary service. Registration, erasure, activation, deactivation and statusquery are supported.

12.2.2 Syntax
Type
Set

SyntaxAT+CCFC=<reason>,<mode>[,<number>[,<type>[,<class>[,<subaddr>[,<satype>[,<time>]]]]]]

ResponseOKorwhen <mode>=2+CCFC: <status>,<class1>[,<number>,<type> [,<subaddr>,<satype>[,<time>]]][+CCFC: <status>,<class2> [,<number>, <type>[,<subaddr>,<satype>[,<time>]]]]

ExampleRegistration:
AT+CCFC=0,3,"01711234"
OK
Query status:
AT+CCFC=2,2+CCFC: 1,1,"+3945112",145,"",,60
OK

OK

UBX-13002752 - R67

12 Supplementary services

Page 256 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+CCFC=?

Response+CCFC: (list of supported<reason>s)

Example+CCFC: (0-5)
OKOK

12.2.3 Defined values
Parameter<reason>Type
NumberDescription<mode>

Number<number><type><subaddr><satype>

StringNumberStringNumber<classx>

Number<time>

Number• 0: disable• 1: enable• 2: query status• 3: registration• 4: erasure
Phone number of forwarding address in <type> format
Type of address; default 145 when dialling string includes '+', otherwise 129
Subaddress; parameter currently ignored after syntax check
Type of subaddress; default 128 (TON/NPI unknown); parameter currently ignored
after syntax check
Sum of Numbers each representing a class of information (default 7 - voice (1), data
(2) and FAX (4) - or interpreted by network if not explicitly entered):• 1: voice• 2: data• 4: FAX• 8: SMS• 16: data circuit sync
• 32: data circuit async• 64: dedicated packet access• 128: dedicated PAD accessTime in seconds to wait before call is forwarded (default 60), but only when<reason>=2 (no reply) is enabled; the range goes from 5 to 30 s<status>Number

•
•
•
•
•
•

•
•

0: unconditional
1: mobile busy
2: no reply
3: not reachable
4: all call forwarding
5: all conditional call forwarding

0: not active
1: active

12.2.4 Notes•

When querying the status of a network service (<mode>=2) the response line for "not active" case(<status>=0) is returned only if the service is not active for any <class>. Hence when querying the statusof a network service (<mode>=2) asking for a specific <class>, the DUT sends a generic request instead.

TOBY-L2• In some cases on voice capable devices, it is not possible to disable call forwarding <reason> by meansof <mode>=0. In this case use <mode>=4.
TOBY-L210-62S / TOBY-L210-65S• The set command is not allowed if the VoLTE service is not available.
TOBY-L210-60S• The set command is not allowed.

UBX-13002752 - R67

12 Supplementary services

Page 257 of 1001

u-blox cellular modules - AT commands manual

12.3 Call waiting +CCWA+CCWA
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210-00S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-60S TOBY-L220 TOBY-L280 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialYes
No
Yes
Up to 3 min+CME Error

12.3.1 Description
Controls the Call Waiting supplementary service according to 3GPP TS 22.083 [29]. The activation,
deactivation and status query are supported. When querying the status of a network service (<mode>=2)
the information text response for 'not active' case (<status>=0) should be returned only if the service is not
active for any <class>. Instead when querying the status of a network service (<mode>=2) asking for a specific<class>, the DUT sends a generic request.
It is possible to abort the status query sending a character to the DCE during the command execution. If
enabled by <n> a URC is presented on TE when a call is signalled.

12.3.2 Syntax
Type
Set

SyntaxAT+CCWA=[<n>[,<mode>[,<class>]]]Response
OK

ExampleAT+CCWA=1,1,32

AT+CCWA=[<n>[,<mode>]]+CCWA: <status>,<class1>

OK
AT+CCWA=1,2[+CCWA: <status>,<class2>+CCWA: 1,1[...]]+CCWA: 1,4

OK+CCWA: 1,16
+CCWA: 1,32

Read

AT+CCWA?

+CCWA: <n>

OK+CCWA: 0

Test

AT+CCWA=?

OK+CCWA: (list of supported <n>s)

OK+CCWA: (0-1)

OK+CCWA: <number>,<type>,<class>,[<alpha>][,<CLI validity>[,<subaddr>,<satype>[,<priority>]]]OK+CCWA: "+393290286612",145,1,,0URC

12.3.3 Defined values
Parameter<n>Type
Number<mode>

Number<classx>

NumberUBX-13002752 - R67

Description
URC configuration:• 0 (default value): disabled• 1: enabled
If <mode> is not set, none request is sent to the network:• 0: disabled• 1 (default value): enabled• 2: query status
Sum of numbers each representing an information class:• 1: voice• 2: data; it comprises all those <classx> values between 16 and 128, that aresupported both by the network and the MS. This means, a setting made for<classx> to 2 applies to all remaining data classes (if supported). In addition, it ispossible to assign a different setting to a specific class. For example, call waiting
can be deactivated only for a specific data class. To understand which classes wereactually activated AT+CCWA=1,2 command should be executed

12 Supplementary services

Page 258 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 4: FAX• 8: SMS• 16: data circuit sync
• 32: data circuit async• 64: dedicated packet access• 128: dedicated PAD accessIf <classx> is not set and <mode> is 0 or 1 the default value is 3
The default value is 255 if <classx> is not set and <mode> is 2 e.g. it reports all activeclasses if any. If no class is active only classes 1 and 2 are reported as inactive:• +CCWA: 0,1• +CCWA: 0,2<status>Number<number><type><alpha>StringNumberString<CLI validity>

Number<subaddr><satype><priority>

StringNumberNumber• 0: not active• 1: active
Phone number of calling address in format specified by <type>Type of address
Optional string type alphanumeric representation of <number> corresponding to theentry found in phonebook; this parameter is not managed• 0: CLI valid• 1: CLI has been withheld by the originator• 2: CLI is not available
Subaddress of format specified by <satype>
Subaddress octet (see the 3GPP TS 24.008 [12] subclause 10.5.4.8)
Optional digit type parameter indicating that the eMLPP priority level of the incoming
call. The priority level values are as defined in eMLPP specification 3GPP TS 22.067[47].

12.3.4 Notes••

The call waiting is not handled in uniform mode among all the networks, even if the 3GPP TS 22.004[3] describes all needed specification: "The applicability of call waiting refers to the telecommunication
service of the active call and not of the waiting call. The incoming, waiting, call may be of any kind."
Nevertheless, the actual implementation of the service on the networks is different.
If a sum class is provided in the <classx> parameter the classes will be activated or deactivated in cardinalorder (minimum to maximum). If a class is not supported then the procedure ends and any remainingclass is not processed. To check which classes were actually activated AT+CCWA=1,2 command should
be done.

TOBY-L210-60S• The set command is not supported.
SARA-G3 / LEON-G1• If <classx> is not set and <mode> is 0 or 1 the default value is 1.
• if no class is active only class 1 is reported as inactive.
SARA-G4• If <classx> is not set and <mode> is 0 or 1 the default value is 1.
• If no class is active only class 1 is reported as inactive.
• <classx>= 2, 4, 8, 16, 32, 64 and 128 are not supported.

UBX-13002752 - R67

12 Supplementary services

Page 259 of 1001

u-blox cellular modules - AT commands manual

12.4 Calling line identification restriction +CLIR+CLIR
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partial
Yes
NVM
Yes

Response time Error reference
Up to 3 min (<1 +CME Errors for prompt ">"when present)

12.4.1 Description
Controls the Calling Line Identification Restriction (CLIR) supplementary service (3GPP TS 22.081 [30]).
The CLIR subscription, when the temporary mode is provisioned by the network, is overidden as a default
adjustment for all following outgoing calls (3GPP TS 22.081 [30] specifies how the network will act).

12.4.2 Syntax
Type
Set

SyntaxAT+CLIR=[<n>]Response
OK

ExampleAT+CLIR=2

Read

AT+CLIR?

+CLIR: <n>,<m>

OK+CLIR: 0,2

Test

AT+CLIR=?

OK+CLIR: (list of supported <n>s)

OK+CLIR: (0-2)

OKOK

12.4.3 Defined values
Parameter<n>Type
Number<m>

NumberDescription
Sets the adjustment for outgoing calls:• 0 (factory-programmed value): presentation indicator is used according to thesubscription of the CLIR service• 1: CLIR invocation• 2: CLIR suppression
Shows the subscriber CLIR status in the network:• 0: CLIR not provisioned• 1: CLIR provisioned in permanent mode
• 2: unknown• 3: CLIR temporary mode presentation restricted• 4: CLIR temporary mode presentation allowed

12.4.4 Notes
TOBY-L210-62S / TOBY-L210-65S• The set and read commands are not allowed if the VoLTE service is not available (see +CIREG AT
command).
TOBY-L210-60S• The set and read commands are not supported.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• The command setting is not stored in the NVM.

UBX-13002752 - R67

12 Supplementary services

Page 260 of 1001

u-blox cellular modules - AT commands manual

12.5 Calling line identification presentation +CLIP+CLIP
Modules

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
Yes

Attributes

Response time Error reference
Up to 3 min (<1 +CME Errors for prompt ">"when present)

12.5.1 Description
Controls the Calling Line Identification Presentation (CLIP) supplementary service, but it has no effect on theexecution of CLIP service in the network. When the CLI (Calling Line Identification) is enabled, the command
response is returned after every RING result code. The URC is displayed after RING if the CLI presentation at
the TE is enabled.

12.5.2 Syntax
Type
Set

SyntaxAT+CLIP=[<n>]Response
OK

ExampleAT+CLIP=1

Read

AT+CLIP?

+CLIP: <n>,<m>

OK+CLIP: 0,2

Test

AT+CLIP=?

OK+CLIP: (list of supported <n>s)

OK+CLIP: (0-1)

OK
OK+CLIP: <number>,<type>[,<subaddr>,<satype>[,<alpha>[,<CLI
validity>]]]URC

12.5.3 Defined values
Parameter<n>Type
Number<m>

Number<number><type><subaddr><satype><alpha>StringNumberStringNumberString<CLI validity>

NumberDescription
Optional parameter sets/shows the result code presentation in the TA:• 0 (default value): disable• 1: enable
Shows the subscriber CLIP service status in the network• 0: CLIP not provisioned• 1: CLIP provisioned• 2: unknown
Phone number of calling address in format specified by <type>.
Type of address octet.
Subaddress of format specified by <satype>.
Type of subaddress octet.
Optional string type alphanumeric representation of <number> corresponding to theentry found in phonebook; the parameter is not managed.
•••

0: CLI valid
1: CLI has been withheld by the originator
2: CLI is not available

12.5.4 Notes•

When CLI is not available (<CLI validity>=2), the <number> parameter shall be an empty string ("") and<type> value will not be significant. Nevertheless, the TA may return the recommended value 128 for<type> (TON/NPI unknown). When CLI has been withheld by the originator, (<CLI validity>=1) and the CLIP
is provisioned with the "override category" option (see the 3GPP TS 22.081 [30] and 3GPP TS 23.081 [31]),

UBX-13002752 - R67

12 Supplementary services

Page 261 of 1001

u-blox cellular modules - AT commands manual<number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type>as if the CLI was not available.
TOBY-L210-62S / TOBY-L210-65S• The set and read commands are not allowed if the VoLTE service is not available (see +CIREG AT
command).
TOBY-L210-60S• The set and read commands are not supported.

12.6 Connected line identification presentation +COLP+COLP
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
Yes

Response time
< 20 sError reference+CME Error

12.6.1 Description
Controls the COnnected Line identification Presentation (COLP) supplementary service (see the 3GPP TS
22.081 [30]), useful in case of call forwarding of the connected line. It enables a calling subscriber to get theconnected line identity (COL) of the called party, after setting up a mobile originated call. The command enables
or disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service
COLR in the network.
When enabled (and called subscriber allows), the IRC is sent from TA to TE before any +CR or V.25ter responses.
The read command provides the <n> status, and also triggers an interrogation of the provision status of the
COLP service according 3GPP TS 22.081 [30] (given in <m>).

12.6.2 Syntax
Type
Set

SyntaxAT+COLP=[<n>]Response
OK

ExampleAT+COLP=1

Read

AT+COLP?

+COLP: <n>,<m>

OK+COLP: 0,2

Test

AT+COLP=?

OK+COLP: (list of supported <n>s)

OK+COLP: (0-1)

OK+COLP: <number>,<type>[,<subaddr>,<satype>[,<alpha>]]

OK

IRC

12.6.3 Defined values
Parameter<n>Type
Number<m>

Number<number>, <type>,<subaddr>,<satype>, <alpha>

UBX-13002752 - R67

Description
Optional parameter sets/shows the result code presentation status to the TE:• 0 (default value): disable• 1: enable
Shows the subscriber COLP status in the network:• 0: COLP not provisioned• 1: COLP provisioned• 2: unknown (e.g. no network, etc.)
See +CLIP.

12 Supplementary services

Page 262 of 1001

u-blox cellular modules - AT commands manual

12.6.4 Notes
TOBY-L210-60S• The set and read commands are not supported.

12.7 Connected line identification restriction +COLR+COLR
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
Yes

Response time
< 20 sError reference+CME Error

12.7.1 Description
Refers to the COnnected Line identification Restriction (COLR) supplementary service that enables theconnected party to prevent presentation of its line identity to the calling party. According to 3GPP TS
22.081 [30] the activation and deactivation of COLR is only a result of provision / withdrawal. The command
allows only the interrogation of the current state of COLR service in the network. The set syntax is not allowed.

12.7.2 Syntax
Type
Read

SyntaxAT+COLR?

Response+COLR: <status>

Example+COLR: 2

AT+COLR=?

OK
OK

OK

Test

12.7.3 Defined values
Parameter<status>Type
NumberDescription
Shows the subscriber COLR service status in the network:• 0: COLR not provisioned• 1: COLR provisioned• 2: unknown

12.7.4 Notes
TOBY-L4 / LARA-R2 / TOBY-R2• The read command is not allowed. The set (action) syntax AT+COLR must be used instead: the set
command has no effect on the execution of the supplementary services COLR in the network; it only
triggers an interrogation of the activation status of the COLR supplementary service. The syntax of theinformation text response is unchanged (+COLR: <status>).
TOBY-L210-60S• The read command is not supported.

UBX-13002752 - R67

12 Supplementary services

Page 263 of 1001

u-blox cellular modules - AT commands manual

12.8 Advice of charge +CAOC+CAOC
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210-00S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L220 TOBY-L280 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialYes
NoNo< 10 s+CME Error

12.8.1 Description
Allows the subscriber to get the information about the call costs in home units using the advice of charge
supplementary service (3GPP TS 22.024 [33] and 3GPP TS 22.086 [32]). If it is enabled, the TE periodicallyreceives the URC containing the corresponding information.

12.8.2 Syntax
Type
Set

SyntaxAT+CAOC[=<mode>]

Response[+CAOC: <ccm>]

ExampleAT+CAOC=0

Read

AT+CAOC?

OK+CAOC: <mode>

OK+CAOC: 1

Test

AT+CAOC=?

OK
OK+CAOC: (list of supported <mode>s) +CAOC: (0-2)
OK+CCCM: <ccm>

URC

OK

12.8.3 Defined values
Parameter<mode>

Type
Number<ccm>

NumberDescription• 0: queries the CCM value• 1: deactivates the unsolicited reporting of CCM value• 2: activates the unsolicited reporting of CCM value
Current call meter indicated as a string in hexadecimal format

12.8.4 Notes
TOBY-L210-62S / TOBY-L210-65S• The set command is not allowed if the VoLTE service is not available.
TOBY-L210-60S• The set command is not allowed.
LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S / LISA-U1 / LEON-G100-06S• If the SIM card does not support the AoC, the CCM value is not updated and no URC is displayed.

UBX-13002752 - R67

12 Supplementary services

Page 264 of 1001

u-blox cellular modules - AT commands manual

12.9 Accumulated call meter +CACM+CACM
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

12.9.1 Description
Resets the advice of charge related accumulated call meter value in the SIM file EFACM. The ACM contains thetotal number of home units for both the current and preceding calls. The SIM PIN2 is required to reset the value.
If the EF is not available, the read command returns +CME ERROR: SIM failure (verbose result code).

12.9.2 Syntax
Type
Set

SyntaxAT+CACM=[<passwd>]

Response
OK

ExampleAT+CACM="0933"

Read

AT+CACM?

+CACM: <acm>

OK+CACM: "000000"

Test

AT+CACM=?

OK
OK

OK

12.9.3 Defined values
Parameter<passwd>
<acm>

Type
StringStringDescription
SIM PIN2 as string type
Accumulated call meter value similarly coded as <ccm> under +CAOC

12.9.4 Notes•

The command needs the SIM module to work correctly

12.10 Call meter maximum event +CCWE+CCWE
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

12.10.1 Description
Allows sending the +CCWV URC to the DTE, when enabled. The URC syntax is: +CCWV. The warning is issued
when approximately 30 s call time remains. It is also sent when starting a call if less than 30 s call time remains.

12.10.2 Syntax
Type
Set

SyntaxAT+CCWE=<mode>

Response
OK

ExampleAT+CCWE=1

Read

AT+CCWE?

+CCWE: <mode>

OK+CCWE: 0

UBX-13002752 - R67

12 Supplementary services

Page 265 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+CCWE=?

Response
ExampleOK
OK+CCWE: (list of supported <mode>s) +CCWE: (0-1)
OK
+CCWV

URC

OK

12.10.3 Defined values
Parameter<mode>

Type
NumberDescription••

0: call meter warning event disabled
1: call meter warning event enabled

12.11 Accumulated call meter maximum +CAMM+CAMM
Modules

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

Attributes

12.11.1 Description
Sets the advice of charge related accumulated call meter maximum value in the SIM file EFACMmax. The
ACMmax contains the maximum number of home units allowed to be consumed by the subscriber. When the
ACM reaches ACMmax, the calls are prohibited. The SIM PIN2 is required to set the value.
If the EF is not available, the read command returns +CME ERROR: SIM failure (verbose result code).

12.11.2 Syntax
Type
Set

SyntaxAT+CAMM=[<acmmax>[,<passwd>]]

Response
OK

ExampleAT+CAMM="000300","0933"

Read

AT+CAMM?

+CAMM: <acmmax>

OK+CAMM: "000300"

Test

AT+CAMM=?

OK
OK

OK

12.11.3 Defined values
Parameter<acmmax>

Type
String<passwd>

StringDescription
Contains the accumulated call meter maximum value similarly coded as <ccm> under+CAOC; value zero disables the ACMmax feature
Contains SIM PIN2

12.11.4 Notes•

The command needs the SIM module to work correctly

UBX-13002752 - R67

12 Supplementary services

Page 266 of 1001

u-blox cellular modules - AT commands manual

12.12 Price per unit and currency table +CPUC+CPUC
Modules

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Attributes

Settings saved Can be aborted
No
No

Response time< 10 sError reference+CME Error

12.12.1 Description
Sets the parameters of advice of charge related price per unit and the currency table in the SIM file EFPUCT.
The PUCT information can be used to convert the home units into the currency units. The PIN2 is required to
set the parameters.
If the EF is not available, the read command returns +CME ERROR: SIM failure (verbose result code).

12.12.2 Syntax
Type
Set

SyntaxAT+CPUC=<currency>,<ppu>[,<passwd>]

Response
OK

ExampleAT+CPUC="USD","0.20","0933"

Read

AT+CPUC?

+CPUC: <currency>,<ppu>

OK+CPUC: "USD","0.20"

Test

AT+CPUC=?

OK
OK

OK

12.12.3 Defined values
Parameter<currency><ppu><passwd>

Type
StringStringStringDescription
Contains the three-character currency code (e.g. "GBP", "EUR")
Contains the price per unit; the dot is used as a decimal separator
Contains SIM PIN2

12.13 Call related supplementary services +CHLD+CHLD
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialYes
NoNo< 20 s+CME Error

12.13.1 Description
Call hold and multiparty conversation (conference call). The calls can be put on hold, recovered, released or
added to the conversation.
The expected response time depends on the number of calls manipulated by the command (the current valuerefers to the manipulation of one call): in case of poor radio quality, disconnect, hold and retrieve procedures
triggered by the command might require several retransmissions at radio level, thus the expected responsetime shall be extended accordingly.

12.13.2 Syntax
Type
Set

SyntaxAT+CHLD=[<n>]Response
OK

ExampleAT+CHLD=2
OK

UBX-13002752 - R67

12 Supplementary services

Page 267 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+CHLD=?

Response+CHLD: (list of supported <n>s)

Example+CHLD: (0,1,1x,2,2x,3,4,4*,6,7,8)

OKOK

12.13.3 Defined values
Parameter<n>Type
NumberDescription
•
•
•
•
•
•
•
•
•

•
•
•

0: release all the held calls or set User Determined User Busy for a waiting call; ifboth exists then only the waiting call will be rejected
1: release all the active calls and accepts the other (held or waiting)
1x: release a specific call (x specific call number as indicated by +CLCC)
2: place all the active calls (if exist) on hold and accepts the other call (held or
waiting, if exist)
2x: place all the active calls on hold except the call x with which communication is
supported
3: adds a held call to the conversation
4: connects the two calls and disconnects the subscriber from both calls (Explicit
Call Transfer)
4*: call deflection (proprietary feature)
5: call completion of busy subscriber; this command syntax will be interpreted as anactivation request, if the network has previously offered the possibility to activate
this function
6: puts an active call on hold or an held call to active
7: disconnect the users in multiparty without accepting incoming call
8: release all the calls (active and held)

12.13.4 Notes
TOBY-L2 / MPCI-L2• The <n> parameter cannot be set to 4*.
• The <n> parameter is mandatory.
TOBY-L210-62S / TOBY-L210-65S• <n>=2 and 2x are not supported if the VoLTE service is not available (see +CIREG AT command).
TOBY-L210-60S• The set command is not supported.
LEON-G100-06S• In the set command the '=' character is not mandatory.

12.14 Call deflection +CTFR+CTFR
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
Up to 3 min+CME Error

12.14.1 Description
Allows the MT user to respond to an incoming call offered by the network by requesting call deflection, i.e.
redirection of this call to another number specified in the response. The call deflection is a supplementary
service applicable only to voice calls (teleservice 11).

UBX-13002752 - R67

12 Supplementary services

Page 268 of 1001

u-blox cellular modules - AT commands manual

12.14.2 Syntax
Type
Set

Syntax
AT+CTFR=<number>[,<type>[,<subaddr>[,<satype>]]]Response
OK

Test

AT+CTFR=?

OK

ExampleAT+CTFR="09113788"
OK

12.14.3 Defined values
Parameter<number><type><subaddr><satype>Type
StringNumberStringNumberDescription
Phone number
Type of address; default 145 when dialling string includes '+', otherwise 129
Subaddress; parameter currently ignored after syntax check
Type of subaddress; default 128 (TON/NPI unknown); parameter currently ignored
after syntax check12.14.4 Notes
TOBY-L210-60S• The set command is not supported.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• <type>, <subaddr>, <satype> parameters are not supported.

12.15 Supplementary service notifications +CSSN+CSSN
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

12.15.1 Description
Refers to supplementary service related network initiated notifications. When <n>=1 and a supplementary
service notification is received after a mobile originated call setup, the IRC is sent before any other Mobile
Originated call setup result codes. When <m>=1 and a supplementary service notification is received during acall, the URC is sent.

12.15.2 Syntax
Type
Set

SyntaxAT+CSSN=[<n>[,<m>]]Response
OK

ExampleAT+CSSN=0,0

Read

AT+CSSN?

+CSSN: <n>,<m>

OK+CSSN: 0,0

Test

AT+CSSN=?

IRC
URC

OK
OK
+CSSN: (list of supported <n>s),(list +CSSN: (0-1),(0-1)
of supported <m>s)OK
OK+CSSI: <code1>[,<index>]+CSSI: 4,1+CSSU: <code2>[,<index>[,+CSSU: 0<number>,<type>[,<subaddr>,<satype>]]]12.15.3 Defined values
Parameter<n>

UBX-13002752 - R67

Type
NumberDescription
Sets/shows the +CSSI result code presentation status

12 Supplementary services

Page 269 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

<m>

NumberDescription• 0: disabled (default value)• 1: enabled
Sets/shows the +CSSU result code presentation status••<code1>

Number<index><code2>

NumberNumber<number><type><subaddr>,<satype>

StringNumberString0: disabled (default value)
1: enabled• 0: unconditional call forwarding is active• 1: some of the conditional call forwardings are active• 2: call has been forwarded• 3: call is waiting• 4: this is a CUG call (<index> parameter is provided)• 5: outgoing calls are barred• 6: incoming calls are barred• 7: CLIR suppression rejected• 8: calls has been deflected
Refer +CCUG (Chapter 12.18)
•
•
•
•
•
•
•
•

0: this is a forwarded call (MT call setup)
1: this is a CUG call (<index> parameter is provided) (MT call setup)
2: call has been put on hold (during a voice call)
3: call has been retrieved (during a voice call)
4: multiparty call entered (during a voice call)
5: call on hold has been released - this is not an SS notification - (during a voice call)
6: forward check SS message received (can be received whenever)
7: call is being connected (alerting) with the remote party in alerting state in explicit
call transfer operation (during a voice call)• 8: call has been connected with the other remote party in explicit call transfer
operation (during a voice call or MT call setup)• 9: this is a deflected call (MT call setup)• 10: additional incoming call forwarded
Phone number, format specified by <type>Type of address octet
Not used

12.15.4 Notes
TOBY-L210-60S• The set command is not supported.

12.16 User to user signalling service 1 +CUUS1+CUUS1Modules
Attributes

TOBY-L2 MPCI-L2
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

12.16.1 Description
Allows the control of the User-to-User Signalling Supplementary Sevice 1 (UUS1) according to 3GPP TS
22.087 [26]. Parameters <message> and <UUIE> are used to activate/deactivate the implicit request of theUser-to-User Signalling Supplementary Service 1. When <message> and <UUIE> are both present the string
specified in <UUIE> is included as the value part of the User-to-User Information Element (as defined in
3GPP TS 24.008 [12]) into all subsequent messages of type <message>. If parameter <message> is present
but parameter <UUIE> is not present then the User-to-User Information Element shall not be present in
subsequent messages of type <message>.
<n> and <m> parameters are used to enable/disable the presentation of incoming User-to-User Information
Elements. When <n>=1 and a User-to-User Information is received after a mobile originated call setup or after
hanging up a call, IRC +CUUS1I: <message>,<UUIE> is sent to the DTE.

UBX-13002752 - R67

12 Supplementary services

Page 270 of 1001

u-blox cellular modules - AT commands manual

When <m>=1 and a User-to-User Information is received during a mobile terminated call setup or during a
remote party call hangup, URC +CUUS1U: <messageU>,<UUIE> is sent to the DTE.

12.16.2 Syntax
Type
Set

SyntaxAT+CUUS1=[<n>[,<m>[,<message>[,<UUIE>[,<message>[,<UUIE>[,...]]]]]]]
AT+CUUS1?

Read

Test

Response
OK

OK+CUUS1: <n>,<m>[,<message>,<UUIE> [,<message>,<UUIE>[,...]]]OK+CUUS1: (list of supported <n>s),(list of supported <m>s), (list of
supported <message>s), (list of
supported <messageI>s),(list of
supported <messageU>s)AT+CUUS1=?

ExampleAT+CUUS1=1,1,1,"7E0005123456"+CUUS1: 0,0
OK+CUUS1: (0,1),(0,1),(0-6),(0-4),(0-3)
OK

OK+CUUS1I: <messageI>,<UUIE>+CUUS1U: <messageU>,<UUIE>

IRC
URC

12.16.3 Defined values
Parameter<n><m><message><messageI><messageU>

Type
NumberDescription
Sets/shows the +CUUS1I result code presentation status in the MT

Number• 0: disable• 1: enable
Sets/shows the +CUUS1U result code presentation status in MT

Number• 0: disable• 1: enable
Type of message containing the outgoing User-to-User Information Element

Number• 0: ANY• 1: SETUP• 2: ALERT• 3: CONNECT• 4: DISCONNECT• 5: RELEASE• 6: RELEASE_COMPLETE
Type of message containing the intermediate User-to-User Information Element

Number• 0: ANY• 1: ALERT• 2: PROGRESS• 3: CONNECT (sent after +COLP if enabled)• 4: RELEASE
Type of message containing the unsolicited User-to-User Information Element••<UUIE>

Number0: ANY
1: SETUP (returned after +CLIP if presented, otherwise after every RING or +CRING(see the +CRC AT command))• 2: DISCONNECT• 3: RELEASE_COMPLETE
The User-to-User Information Element (as defined in 3GPP TS 24.008 [12]) in
hexadecimal character format (for hexadecimal format, see the +CSCS AT
command).

12.16.4 Notes•

If the MT does not distinguish the type of message containing the User-to-User Information Element, it
can use the value for ANY message.

UBX-13002752 - R67

12 Supplementary services

Page 271 of 1001

u-blox cellular modules - AT commands manual

TOBY-L210-60S• The set command is not supported.

12.17 Unstructured supplementary service data +CUSD+CUSD
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
Yes

Response time
Up to 3 min

Error reference+CME Error

12.17.1 Description
Control of Unstructured Supplementary Service Data (USSD) is according to 3GPP TS 22.090 [6]. Both networkand mobile initiated operations are supported. The parameter <n> disables/enables the URC presentation.
Value <n>=2 is used to cancel an ongoing USSD session. When <str> is given, a mobile initiated USSD-stringor a response USSD-string to a network initiated operation is sent to the network. The response USSD-stringfrom the network is returned in the URC +CUSD indicated above.

12.17.2 Syntax
Type
Set

SyntaxAT+CUSD=[<n>[,<str>[,<dcs>]]]Response[+CUSD: <m>[,<str>,<dcs>]]

ExampleAT+CUSD=1,"*100#",15

OK+CUSD: 2,"Residual credit: 7,87
Euro",15

Read

AT+CUSD?

+CUSD: <n>OK+CUSD: 0

Test

AT+CUSD=?

OK+CUSD: (list of supported <n>s)OK+CUSD: (0-2)

OK+CUSD: <m>[,<str>,<dcs>]

OK

URC

12.17.3 Defined values
Parameter<n>Type
Number

<str>
<dcs>

StringNumber<m>

NumberDescription• 0 (default value): result code presentation disabled• 1: result code presentation enabled• 2: session cancelled (not applicable to the read command response)
USSD-string converted in the current character set in use (see the +CSCS command)
Data coding scheme (see 3GPP TS 23.038 [7]) used for sending the USSD string. 1
byte in decimal format; valid values are 0-255. The default value is 15.
•
•
•
•
•

0: no further user action required
1: further user action required
2: USSD termination by network
4: operation not supported
5: network time out

12.17.4 Notes••••

Aborting the command is equivalent to send AT+CUSD=2, that ends the current USSD session.
When issuing a set command with <n>=1, the module waits for SS transaction to finish before issuing
the final result code (e.g. "OK").
After having sent a +CUSD request, it is recommended to refrain from sending another +CUSD request
until the URC of the first one has been received.
On all modules except SARA-U series, when starting a USSD transaction or replying to an incoming USSD,
the encoded USSD string cannot exceed 112 bytes; this implies that the input USSD string in e.g. default
charset "IRA" (see the +CSCS command) and default coding scheme =15 cannot exceed 128 characters

UBX-13002752 - R67

12 Supplementary services

Page 272 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2 / MPCI-L2 / SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S /LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• When starting a USSD transaction or replying to an incoming USSD, the encoded USSD string cannot
exceed 112 bytes; this implies that the input USSD string in e.g. default charset "IRA" (see the +CSCS
command) and default coding scheme =15 cannot exceed 128 characters
TOBY-L2 / MPCI-L2• When issuing a set command with <n>=1, the "OK" result code is usually returned before the URC (if any)
is issued.
TOBY-L210-60S• The set command is not supported.

12.18 Closed user group +CCUG+CCUG
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

12.18.1 Description
Enables subscribers to form closed user groups to and from which access is restricted (refer to 3GPP TS 22.085[38]). The command can be used to:••••

Activate/deactivate the control of the CUG information for all following calls
Select a CUG index
Suppress the outgoing access (OA). The OA allows a member of a CUG to place calls outside the CUG
Suppress the preferential CUG

12.18.2 Syntax
Type
Set

SyntaxResponse
AT+CCUG=[<n>[,<index>[,<info>]]] OK

ExampleAT+CCUG=1,2,1

Read

AT+CCUG?

+CCUG: <n>,<index>,<info>

OK+CCUG: 0,0,0

Test

AT+CCUG=?

OK[+CCUG: (list of supported <n>s),(list of supported <index>s),(list of
supported <info>s)]

OK+CCUG: (0-1),(0-10),(0-3)
OKOK

12.18.3 Defined values
Parameter<n>Type
NumberDescription••

0 (default value): CUG temporary disabled
1: CUG temporary enabled<index>Number••0..9: CUG index, (0 default value)
10: no index (preferred CUG taken from subscriber data)<info>

Number

••••0: no information (default value)
1: suppress OA
2: suppress preferential CUG
3: suppress OA and preferential CUG

UBX-13002752 - R67

12 Supplementary services

Page 273 of 1001

u-blox cellular modules - AT commands manual

12.18.4 Notes
TOBY-L2 / MPCI-L2• The response to the test command is "OK".
• If the set command with <n>=0 is sent the read command provides the default values.
• The default value of <index> parameter is 10.
TOBY-L210-60S• The set command is not supported.

12.19 Calling name presentation +CNAP+CNAP
Modules

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Attributes

Settings saved Can be aborted
No
Yes

Response time
< 20 sError reference+CME Error

12.19.1 Description
This command refers to the GSM/UMTS supplementary service CNAP (Calling Name Presentation, refer to
3GPP TS 22.096 [39]) that enables a called subscriber to get a calling name indication (CNI) of the calling party
when receiving a mobile terminated call. The set command enables or disables the CNI presentation. It has noeffect on the execution of the supplementary service CNAP in the network. When the presentation of the CNI
is enabled (and CNI is provided), the URC +CNAP: <name>,<CNI_validity> response is returned.

12.19.2 Syntax
Type
Set

Syntax
AT+CNAP=[<n>]Response
OK

ExampleAT+CNAP=0

Read

AT+CNAP?

+CNAP: <n>,<m>OK+CNAP: 0,2

Test

AT+CNAP=?

OK+CNAP: (list of supported <n>s)OK+CNAP: (0-1)

OK+CNAP: <calling_name>[,<CNI_
validity>]

OK+CNAP: "SubscriberName",0URC

12.19.3 Defined values
Parameter<n><m><calling_name><CNI_validity>

UBX-13002752 - R67

Type
NumberDescription
Sets the result code presentation

Number• 0: disabled (default value)• 1: enabled
Subscriber CNAP service status in the network

StringNumber• 0: CNAP not provisioned• 1: CNAP provisioned• 2: unknown
Calling party name••••

0: name presentation allowed
1: presentation restricted
2: name unavailable
3: name presentation restricted

12 Supplementary services

Page 274 of 1001

u-blox cellular modules - AT commands manual

12.19.4 Notes
TOBY-L210-60S• The set and read commands are not supported.

12.20 eMLPP priority registration and interrogation+CAEMLPP+CAEMLPP
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
< 20 s+CME Error

12.20.1 Description
Changes the default priority level of the user in the network. The requested priority level is checked against theeMLPP subscription of the user stored on the SIM card in EFeMLPP (see the 3GPP TS 51.011 [17] and 3GPP TS
31.102 [18]). If the user does not have subscription for the requested priority level an error result code is returned.
The read command triggers an interrogation of the provision of the maximum priority level which the service
subscriber is allowed to use and default priority level activated by the user. If the service is not provisioned, aresult code including the SS-Status parameter is returned.

12.20.2 Syntax
Type
Set

SyntaxAT+CAEMLPP=<priority>

Response
OK

Read

AT+CAEMLPP?

+CAEMLPP: <default_priority>,<max_priority>

Test

AT+CAEMLPP=?

ExampleAT+CAEMLPP=1
OK

OK
OK

OK

12.20.3 Defined values
Parameter<priority>

Type
Number<default_priority>

Number<max_priority>

NumberDescription
Indicates the default eMLPP priority level priority level to be activated in the network.
The priority level values are defined in eMLPP specification 3GPP TS 22.067 [47]Indicates the default eMLPP priority level priority level which is activated in the
network. The priority level values are defined in eMLPP specification 3GPP TS 22.067[47]
Indicates the maximum eMLPP priority level for which the service subscriber
has a subscription in the network. The priority level values are defined in eMLPP
specification 3GPP TS 22.067 [47]12.21 eMLPP subscriptions +CPPS+CPPS
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
+CME Error

12.21.1 Description
Returns all eMLPP priority subscriptions of the user stored on the SIM card in EFeMLPP (see the 3GPP TS 51.011[17] and the 3GPP TS 31.102 [18]). If no explicit priority level subscription is stored in EFeMLPP the final result
code OK is returned.

UBX-13002752 - R67

12 Supplementary services

Page 275 of 1001

u-blox cellular modules - AT commands manual

12.21.2 Syntax
Type
ActionSyntaxAT+CPPS

Response[+CPPS: <priority>[,<priority>[...]]]

ExampleAT+CPPS

AT+CPPS=?

OK
OK

OK

Test

12.21.3 Defined values
Parameter<priority>

Type
NumberDescription
eMLPP subscription to priority level {0,1,..,4} as defined in defined in eMLPP
specification 3GPP TS 22.067 [47]12.22 Automatic answer for eMLPP service +CAAP+CAAPModules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
+CME Error

12.22.1 Description
Edits the status of the priority level for the automatic answering for eMLPP stored on the SIM card in EFAAeM(see the 3GPP TS 51.011 [17] and 3GPP TS 31.102 [18]). If the user has no subscription to the priority level status
he wants to edit, an error result code is returned. The read command returns all enabled priority levels forautomatic answering for eMLPP stored on the SIM card or in EFAAeM. If no priority level is enabled for automatic
answering for eMLPP, the OK final result code is returned.

12.22.2 Syntax
Type
Set

SyntaxAT+CAAP=<priority>,<status>

Response
OK

ExampleAT+CAAP=0,1

Read

AT+CAAP?

[+CAAP: <priority>[,<priority>[...]]]OK
AT+CAAP?

Test

AT+CAAP=?

OK+CAAP: (list of supported<priority>s),(list of supported<status>s)OK+CAAP: (0-4),(0-1)
OKOK

12.22.3 Defined values
Parameter<priority>

Type
NumberDescription
eMLPP fast call set-up priority level {A,B,0,1,..,4} as defined in eMLPP specification
3GPP TS 22.067 [47].

<status>Number••UBX-13002752 - R67

0: <priority> for automatic answering disabled
1: <priority> for automatic answering enabled

12 Supplementary services

Page 276 of 1001

u-blox cellular modules - AT commands manual

13 Circuit switched data services
13.1 Introduction
For CSD services, it is advised to enable the XID negotiation using the configuration AT+CRLP=61,61,48,7.

13.2 Select bearer service type +CBST+CBST
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialNo
ProfileNo

Response time-Error reference+CME Error

13.2.1 Description
Selects the bearer service <name> with data rate <speed> and the connection element <ce> to use for data
calls.

13.2.2 Syntax
Type
Set

SyntaxAT+CBST=[<speed>[,<name>[,<ce>]]]

Response
OK

ExampleAT+CBST=5,0,1

Read

AT+CBST?

+CBST: <speed>,<name>,<ce>

OK+CBST: 14,0,1

Test

AT+CBST=?

OK+CBST: (list of supported<speed>s),(list of supported<name>s),(list of supported <ce>s)

OK+CBST: (0,4-7,12,14-16,68,70-71,75,
79-81,83-84,115-116,130-131,133-134),(0,1),(0-3)

OKOK

13.2.3 Defined values
Parameter<speed>UBX-13002752 - R67

Type
NumberDescription
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

0: autobauding
4: 2400 b/s (V.22bis) (RAT GSM only)
5: 2400 b/s (V.26ter) (RAT GSM only)
6: 4800 b/s (V.32)
7: 9600 b/s (V.32)
12: 9600 b/s (V.34) (only for UMTS RAT)
14: 14400 b/s (V.34) (only for UMTS RAT)
15: 19200 b/s (V.34) (only for UMTS RAT)
16: 28800 b/s (V.34) (only for UMTS RAT)
68: 2400 b/s (V110 or X.31 flag stuffing) (RAT GSM only)
70: 4800 b/s (V110 or X.31 flag stuffing)
71 (default and factory-programmed value): 9600 b/s (V110 or X.31 flag stuffing)
75: 14400 b/s (V110 or X.31 flag stuffing) (only for UMTS RAT)
79: 19200 b/s (V110 or X.31 flag stuffing) (only for UMTS RAT)
80: 28800 b/s (V110 or X.31 flag stuffing) (only for UMTS RAT)
81: 38400 b/s (V110 or X.31 flag stuffing) (only for UMTS RAT)
83: 56000 b/s (V110 or X.31 flag stuffing) (only for UMTS RAT)
84: 64000 b/s (X.31 flag stuffing) (only for UMTS RAT)
115: 56000 b/s (bit transparent) (only for UMTS RAT)
116: 64000 b/s (bit transparent) (only for UMTS RAT)
130: 28800 b/s (multimedia) (only for UMTS RAT)
131: 32000 b/s (multimedia) (only for UMTS RAT)

13 Circuit switched data services

Page 277 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<name>

NumberDescription• 133: 56000 b/s (multimedia) (only for UMTS RAT)
• 134: 64000 b/s (multimedia) (only for UMTS RAT)
Bearer service name•<ce>

Number0 (default and factory-programmed value): data circuit asynchronous (UDI or 3.1
kHz modem)• 1: data circuit synchronous (UDI or 3.1 kHz modem)
Connection element••••

0: transparent
1 (default and factory-programmed value): non-transparent
2: both, transparent preferred (RAT GSM only)
3: both, non-transparent preferred (RAT GSM only)

13.2.4 Notes••

Several <speed> values are allowed in GSM or UMTS RAT only: see the parameter's description for correct
settings.
The modules do not support all the parameter combinations listed in 3GPP TS 22.002 [46].

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• See Table 20 (in the +UDCONF=32 command description) for a more detailed list of the parameter
combinations supported.
SARA-G3• The default and factory-programmed value of <speed> is 7.
• These values of <speed> are not supported: 12, 14, 15, 16, 75, 79, 80, 81, 83, 84, 115, 116, 130, 131, 133 and 134.
• See Table 18 for a more detailed list of the parameter combinations supported.
LEON-G1• The default and factory-programmed value of <speed> is 7.
• These values of <speed> are not supported: 12, 14, 15, 16, 75, 79, 80, 81, 83, 84, 115, 116, 130, 131, 133 and 134.
• See Table 18 for a more detailed list of the parameter combinations supported.
SARA-G3 / LEON-G1
Connection typeTransfer capability type
Audio 3.1 kHz

Async transparent
UDI Data

Audio 3.1 kHz
Async non transparent
UDI Data

Async transparent
preferred

Audio 3.1 kHz
UDI Data

Async non transparent
preferred

Audio 3.1 kHz
UDI Data

AT+CBST
4,0,0
5,0,0
6,0,0
7,0,0
68,0,070,0,071,0,0
0,0,1
6,0,1
7,0,1
70,0,1
71,0,1
0,0,2
6,0,2
7,0,2
70,0,2
71,0,2
0,0,3
6,0,3
7,0,3
70,0,3
71,0,3Rate (bit/s)
2400
2400
4800
9600
2400
4800
9600
Autobauding
4800
9600
4800
9600
Autobauding
4800
9600
4800
9600
Autobauding
4800
9600
4800
9600

Type
V22 bisV26 ter
V32
V32
V110
V110
V110
Autobauding
V32
V32
V110
V110
Autobauding
V32
V32
V110
V110
Autobauding
V32
V32
V110
V110

Table 18: AT+CBST parameter combinations

UBX-13002752 - R67

13 Circuit switched data services

Page 278 of 1001

u-blox cellular modules - AT commands manual

13.3 Connection type groups configuration +UDCONF=32+UDCONF=32
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

13.3.1 Description
Enables/disables the connection type groups.
Meaning, availability and relationship of data connection types groups with AT+CBST parameters aredescribed in Table 20.

13.3.2 Syntax
Type
Set

SyntaxAT+UDCONF=32,<conn_type_groups_bitmap>

Read

AT+UDCONF=32

Response
OK

ExampleAT+UDCONF=32,1

OK+UDCONF: 32,<active_conn_type_ AT+UDCONF=32
groups_bitmap>,<configured_conn_+UDCONF: 32,1,1
type_groups_bitmap>
OKOK

13.3.3 Defined values
ParameterType<conn_type_groups_ Number
bitmap><active_conn_type_ Number
groups_bitmap><configured_conn_ Number
type_groups_
bitmap>Description
Bitmask representing the list of "connection type groups" supported after the reboot.
Valid range is 0-127 (equivalent to bits 0000000-1111111). The factory-programmed
bitmask is 127 (all the groups are supported).
See the Table 19 for the meaning of each bit. See the Notes for the meaning of eachgroup.
The currently active connection type groups, in the format described for <conn_type_groups_bitmap>
The list of the connection type groups that is supported after reboot, in the format
described for <conn_type_groups_bitmap>

13.3.4 Notes
Bit
0
1
2
3
4
5
6

Connection type group
UDI multimedia
UDI data
RDI
Audio 3.1 kHz
All sync transparent
All async transparent
All async non transparent

Table 19: Connection type group bit description•

The connection type groups 4, 5 and 6 partially include the groups 1, 2 and 3. Enabling a super-group
forces all sub-groups to be enabled; enabling a sub-group is possible even if the super-group is disabled.
The meaning of each data connection super-group is defined as follows:
Group

Transfer capability group

Async transparent

Audio 3.1 kHz

UBX-13002752 - R67

AT+CBST
4,0,0
5,0,0
6,0,0

Rate (bit/s)
2400
2400
4800

13 Circuit switched data services

Type
V22 bisV26 ter
V32

2G
•
•
•

3G

Page 279 of 1001

u-blox cellular modules - AT commands manual

Group

Transfer capability group

UDI data

Audio 3.1 kHz

Async non transparent

UDI data

Sync transparent

RDI data
UDI data
Audio 3.1 kHz
UDI data
RDI data
UDI data
UDI multimedia•

AT+CBST
7,0,0
16,0,068,0,070,0,071,0,0
0,0,1
4,0,1
5,0,1
6,0,1
7,0,1
12,0,1
14,0,1
15,0,1
16,0,1
68,0,1
70,0,1
71,0,175,0,1
79,0,180,0,1
81,0,1
83,0,1
84,0,1
16,1,083,1,0115,1,0
116,1,0
130,1,0
131,1,0133,1,0
134,1,0Rate (bit/s)
9600
28800
2400
4800
9600
Autobauding
2400
2400
4800
9600
9600
14400
19200
28800
2400
4800
9600
14400
19200
28800
38400
56000
64000
28800
56000
56000
64000
64000
64000
64000
64000

Type
V32
V34
V110
V110
V110
Autobauding
V22 bisV26 ter
V32
V32
V34
V34
V34
V34
V110
V110
V110
V110
V110
V110
V110
V110
FTM
V34
V110
bit transparent
bit transparent
multimedia
multimedia
multimedia
multimedia

2G
•

3G
•

•
•
•
•
•
•
•
•

•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

Table 20: Data connection groups: meaning, availability and relationship with AT+CBST parameters
If a call class is disabled then:o The outgoing calls are rejected when the ATD command is invoked (NO CARRIER is printed)
o The incoming calls are rejected by the stack and the user will receive no notification (e.g. no RING)

13.4 Circuit switched data (CSD) configuration +UCSD+UCSD
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

13.4.1 Description
Sets or gets the value of the specified parameter in a specific GSM circuit switched data (CSD) profile, or reads
the current values of all parameters of the given PSD profile, listing them in separated lines.
The parameter values set with this command are volatile, but the whole profile may be stored in NVM with
the AT+UCSDA command.
In the set command, if only the first two parameters are issued, the module returns the current settingof the corresponding remaining parameter. Otherwise only the "OK" result code is returned.
In the set command, if only the first parameter is issued, the module returns all the parameters of thegiven PSD profile, and lists them in separated lines.

UBX-13002752 - R67

13 Circuit switched data services

Page 280 of 1001

u-blox cellular modules - AT commands manual

13.4.2 Syntax
Type
Set

SyntaxSet command

Response
OK

Get

AT+UCSD=<profile_id>,<param_tag>,<param_val>
CSD Get command
AT+UCSD=<profile_id>,<param_tag>
CSD Get All command
AT+UCSD=<profile_id>

ExampleAT+UCSD=2,1,0
OK+UCSD: <profile_id>,<param_tag>,<param_val>

AT+UCSD=2,1+UCSD: 2,1,0

OK

OK+UCSD: <profile_id>,0,<param_val0
AT+UCSD=0>+UCSD: 0,0,"8001234564"........
+UCSD: 0,1,0
OK+UCSD: 0,2,"username"+UCSD: 0,4,"0.0.0.0"+UCSD: 0,5,"0.0.0.0"+UCSD: 0,6,0OK

13.4.3 Defined values
Parameter<profile_id><param_tag>

Type
NumberNumberDescription
CSD profile identifier, in range 0-6
•
•

•
•
•

•

•

0: Phone number - <param_val> is defined by a text string, such as "36912345678".
The factory-programmed value is an empty string.
1: Call type - <param_val> may be:o 0 (factory-programmed value): analog
o 1: ISDN
2: Username - <param_val> is the user name text string for the authentication
phase. The factory-programmed value is an empty string.
3: Password - <param_val> is the password text string for the authentication
phase. Note: the AT+UCSD Get command with <param_tag> = 3 is not allowed
4: DNS1 - <param_val> is the text string of the primary DNS address in dotted
decimal notation form (i.e. four numbers in range 0-255 separated by periods, like"xxx.yyy.zzz.www"). The factory-programmed value is "0.0.0.0".
5: DNS2 - <param_val> is the text string of the secondary DNS address in dotted
decimal notation form (i.e. four numbers in range 0-255 separated by periods, like"xxx.yyy.zzz.www"). The factory-programmed value is "0.0.0.0".
6: Timeout (RFU) - <param_val> represents the linger time: if there is nodata transfer for the given time-out, the call is hang-up). Note: currently
not implemented. Parameter 6 can be neither set nor retrieved. The factoryprogrammed value is 0.

13.5 Circuit switched data (CSD) action +UCSDA+UCSDA
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time
Up to 3 min

Error reference+CME Error

13.5.1 Description
Performs the requested action for the specified CSD profile.

13.5.2 Syntax
Type
Set

SyntaxAT+UCSDA=<profile_id>,<action>

Response
OK

ExampleAT+UCSDA=3,0
OK

UBX-13002752 - R67

13 Circuit switched data services

Page 281 of 1001

u-blox cellular modules - AT commands manual

Type
URC

SyntaxResponse+UUCSDD: <profile_id>

Example13.5.3 Defined values
Parameter<profile_id><action>Type
NumberNumberDescription
CSD profile identifier, in range 0-6
•
•
•
•
•

0: (Reset) clears the specified profile, resetting all parameters to their factoryprogrammed values
1: (Store) saves all parameters of the specified profile in NVM for future retrieval
2: (Load) reads all parameters of the specified profile from NVM
3: (Activate) performs end-to-end connection establishment for the specified CSD
profile, using its pre-defined parameters (i.e. service provider number)
4: (Deactivate) releases the GSM data call associated with the specified CSD profile

13.5.4 Notes••

Only one profile at a time can be associated with an active GSM call.
in case of remote disconnection of a GSM call associated to a CSD profile, the URC is sent to the TE to
inform the user, otherwise the user is in charge of connection release after usage.

13.6 Circuit switched network-assigned data +UCSND+UCSND
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

13.6.1 Description
Returns the current (dynamic) network-assigned value of the specified parameter of the active GSM data callassociated with the specified CSD profile.

13.6.2 Syntax
Type
Set

SyntaxAT+UCSND=<profile_id>,<param_tag>

Response
Example+UCSND: <profile_id>,<param_tag>, AT+UCSND=2,0<dynamic_param_val>+UCSND: 2,0,"151.9.78.170"
OKOK

13.6.3 Defined values
Parameter<profile_id><param_tag>

Type
NumberNumber<dynamic_param_val>

StringUBX-13002752 - R67

Description
CSD profile identifier, in range 0-6• 0: IP address: dynamic IP address assigned during context activation• 1: DNS1: dynamic primary DNS address• 2: DNS2: dynamic secondary DNS address
Value of the specified <param_tag>

13 Circuit switched data services

Page 282 of 1001

u-blox cellular modules - AT commands manual

13.7 Service class selection and identification +FCLASS+FCLASS
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partial
No
No
No

Response time-Error reference+CME Error

13.7.1 Description
Configures the operation mode (voice, data or FAX) of the MT.

13.7.2 Syntax
Type
Set

Syntax
AT+FCLASS=<class>

Response
OK

ExampleAT+FCLASS=2.0

Read

AT+FCLASS?

<n>

OK
0

Test

AT+FCLASS=?

OK(list of supported <class>s)

OK
(0,8)

OK

OK

13.7.3 Defined values
Parameter<class>Type
NumberDescription
Operation mode:• 0 (default value): data
• 2.0: reserved• 8: voice

13.7.4 Notes
TOBY-L4• <class>=8 (voice) is the unique supported value and it is the default value.
TOBY-L2• <class>=8 (voice) is the unique supported value and it is the default value.
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• The set command is not allowed while the read and the test command only return the "OK" final result
code.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The selected operation mode is only set for the following CS call.
LISA-U200-00S / LISA-U100 / LISA-U110• <class>=8 is not supported.
SARA-G340 / SARA-G350• <class>=2.0 is dedicated to FAX (service class 2).
SARA-G300 / SARA-G310• <class>=8 is not supported.
LEON-G1• <class>=2.0 is dedicated to FAX (service class 2).

UBX-13002752 - R67

13 Circuit switched data services

Page 283 of 1001

u-blox cellular modules - AT commands manual

13.8 Service reporting control +CR+CR
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
ProfileNo

Response time< 10 sError reference+CME Error

13.8.1 Description
Controls whether the intermediate result code is returned or not. If enabled, the intermediate result codeis transmitted when, during the connection negotiation, the MT has determined which speed and quality ofservice will be used, before any error control or data compression reports are transmitted, and before theintermediate result code CONNECT is transmitted.

13.8.2 Syntax
Type
Set

SyntaxAT+CR=[<mode>]

Response
OK

ExampleAT+CR=0

Read

AT+CR?

+CR: <mode>

OK+CR: 0

Test

AT+CR=?

OK+CR: (list of supported <mode>s)OK+CR: (0-1)

OK+CR: <serv>

OK

IRC

13.8.3 Defined values
Parameter<mode>

Type
Number<serv>

StringDescription• 0 (default value and factory-programmed value): disables reporting• 1: enables reporting
Service name••••

ASYNC: asynchronous transparent
REL ASYNC: asynchronous non-transparent (reliable)
REL SYNC: synchronous non-transparent (reliable)
SYNC: synchronous transparent

13.8.4 Notes•<serv>=REL ASYNC applies only for incoming or outgoing data calls.

13.9 Cellular result codes +CRC
+CRC
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
partialNo
ProfileNo

Response time-Error reference+CME Error

13.9.1 Description
Enables the detailed ring indication for the incoming calls. Instead of RING, the +CRING: <type> URC isdisplayed.

UBX-13002752 - R67

13 Circuit switched data services

Page 284 of 1001

u-blox cellular modules - AT commands manual

13.9.2 Syntax
Type
Set

SyntaxAT+CRC=[<mode>]

Response
OK

Read

AT+CRC?

+CRC: <mode>

Test

AT+CRC=?

OK+CRC: (list of supported <mode>s)

ExampleAT+CRC=0
OK

OK+CRING: <type>

URC+CRC: (0-1)
OK

13.9.3 Defined values
Parameter<mode>

Type
Number<type>

StringDescription• 0 (default value and factory-programmed setting): extended format disabled• 1: extended format enabled
Ring indication description:• ASYNC: asynchronous transparent• REL ASYNC: asynchronous non-transparent (reliable)• SYNC: synchronous transparent• REL SYNC: synchronous non-transparent (reliable)• FAX: facsimile (TS62)• VOICE: normal voice (TS11)• ALT VOICE / FAX: alternating voice/FAX, voice first (TS61)• ALT FAX / VOICE: alternating voice/FAX, FAX first (TS61)• GPRS <PDP_type>,<PDP_addr>,<L2P>,<APN>: GPRS network request for the PDP
context activation

13.9.4 Notes
TOBY-L4• <type>="ASYNC", "REL ASYNC", "SYNC", "REL SYNC", FAX", "ALT VOICE / FAX", "ALT FAX / VOICE","GPRS" are not supported.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• <type>="FAX", "ALT VOICE / FAX", "ALT FAX / VOICE", "GPRS" are not supported.
SARA-U201-63B / LISA-U200-62S• <type>=GPRS is supported. <PDP_type>, <PDP_addr>, <L2P>, <APN> are described in Parameter
definition.
SARA-G3• The <mode> parameter is mandatory.
SARA-G300 / SARA-G310• <type>="FAX", "ALT VOICE / FAX", "ALT FAX / VOICE", "GPRS" are not supported.
LEON-G1• The <mode> parameter is mandatory.
• <type>=GPRS is not supported.

UBX-13002752 - R67

13 Circuit switched data services

Page 285 of 1001

u-blox cellular modules - AT commands manual

13.10 Radio link protocol +CRLP+CRLP
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
ProfileNo

Response time-Error reference+CME Error

13.10.1 Description
Sets the radio link protocol (RLP) parameters used when non-transparent data-calls are originated.
The advised configuration for an optimal IOT performance is AT+CRLP=61,61,48,7.

13.10.2 Syntax
Type
Set

SyntaxAT+CRLP=[<iws>[,<mws>[,<T1>[,<N2>]]]]

Response
OK

ExampleAT+CRLP=61,61,48,6

Read

AT+CRLP?

+CRLP: <iws>,<mws>,<T1>,<N2>

OK+CRLP: 61,61,48,6

Test

AT+CRLP=?

OKOK+CRLP: (lists of supported <iws>),+CRLP: (0-61),(0-61),(39-255),(1-255)(lists of supported <mws>),(lists ofOKsupported <T1>),(lists of supported
<N2>)
OK

13.10.3 Defined values
Parameter
<iws>

Type
Number<mws>

Number

<T1>

Number

<N2>

NumberDescription
IWF (Interworking Function) to MT window size, range 0 - 61 (default and factoryprogrammed value: 61)
MT to IWF (Interworking Function) window size, range 0 - 61 (default and factoryprogrammed value: 61)
Acknowledgement timer T1, expressed in dozen of msec, range 39 - 255 (default andfactory-programmed value: 48)
Retransmission attempts, range 1 - 255 (default and factory-programmed value: 7)

13.10.4 Notes
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G350-00S /SARA-G350-00X / LEON-G100-06S• The default and factory-programmed value of <N2> is 6.
SARA-G3 / LEON-G1• The PIN insertion is not mandatory.

UBX-13002752 - R67

13 Circuit switched data services

Page 286 of 1001

u-blox cellular modules - AT commands manual

14 FAX class 2
14.1 Introduction
FAX commands are compliant with ITU_T recommendation V250 and V.25ter.
FAX service is carried out in five separate and consecutive phases:
•
•
•
•
•

Phase A: Call set-up
Phase B: Pre-message procedure for identifying and selecting the required facilities
Phase C: Message transmission
Phase D: Post-message procedure including end-of-message, confirmation and multi-document
procedures
Phase E: Call release14.2 Adaptive answer +FAA
+FAA
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.2.1 Description
Allows an adaptive answer of DCE depending on the parameter <value>.

14.2.2 Syntax
Type
Set
Read

SyntaxAT+FAA=<value>
AT+FAA?

ResponseOK<value>ExampleTest

AT+FAA=?

OK(range of <value>s)

(0-1)

OK

OK

14.2.3 Defined values
Parameter<value>Type
NumberDescription••

0: the DCE shall answer only as a Class 2 facsimile device
1: the DCE can automatically determine whether to answer as a facsimile DCE(in case of FAX call or alternate speech/fax call is detected) or as a data modem.
If a data modem is detected, the DCE shall operate as described in ITU-T
Recommendation T.32 par. 8.3.2.4.

14.3 Address & polling capabilities +FAP
+FAP
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.3.1 Description
Enables sending and receiving of SUB, SEP, and PWD frames.

14.3.2 Syntax
Type
Set

SyntaxAT+FAP=<sub>,<sep>,<pwd>

UBX-13002752 - R67

ResponseOK

14 FAX class 2

ExamplePage 287 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+FAP?

Response<sub>,<sep>,<pwd>

Test

AT+FAP=?

ExampleOK(range of <sub>s),(range of <sep>s), (0-1),(0-1),(0-1)(range of <pwd>s)OKOK

14.3.3 Defined values
Parameter
<sub>
<sep>
<pwd>

Type
NumberNumberNumberDescription
Subaddressing; default value: 0
Selective polling; default value: 0
Password; default value: 0

14.4 Buffer size +FBS
+FBS
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.4.1 Description
Allows the DCE to report the size of its data buffers for FAX services.

14.4.2 Syntax
Type
Read

SyntaxAT+FBS?

Response<tbs>,<rbs>ExampleOK

14.4.3 Defined values
Parameter
<tbs>
<rbs>

Type
NumberNumberDescription
Transmit buffer size, i.e. 2048 bytes
Receive buffer size, i.e. 2048 bytes

14.5 Data bit order +FBO
+FBO
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.5.1 Description
Controls the mapping between PSTN facsimile data and the DTE-DCE link. There are two options:••

Direct order: the first bit of each octet transferred on the DTE-DCE link is the first bit transferred on the
GSTN (General Switched Telephone Network) data carrier
Reversed order: the last bit of each octet transferred on the DTE-DCE link is the first bit transferred on the
GSTN data carrier

14.5.2 Syntax
Type
Set
Read

SyntaxAT+FBO=<value>
AT+FBO?

ResponseOK<value>ExampleOK

UBX-13002752 - R67

14 FAX class 2

Page 288 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+FBO=?

Response(range of <value>s)

Example
(0-3)

OK

OK

14.5.3 Defined values
Parameter<value>Type
NumberDescription••••

0: direct bit order
1: reverse bit order for T.4 messages
2: reverse bit order for HDLC messages
3: reverse bit order for both T.4 and HDLC messages

14.6 HDLC frame reporting +FBU
+FBUModules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.6.1 Description
Controls the DCE reporting of the contents of phase B and phase D HDLC frames to the DTE via intermediate
result codes +FHT and FHR, as they are sent and received, in addition to other responses.

14.6.2 Syntax
Type
Set
Read

SyntaxAT+FBU=<value>
AT+FBU?

ResponseOK<value>ExampleTest

AT+FBU=?

OK(range of <value>s)

(0-1)

OK

OK

14.6.3 Defined values
Parameter<value>Type
NumberDescription••

0: HDLC reporting disabled
1: HDLC reporting enabled

14.7 DS capabilities parameters +FCC
+FCC
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.7.1 Description
Allows the DTE to read and constrain the capabilities of the facsimile DCE based on the choices defined in table
2 of ITU-T Recommendation T.30. When any parameter is modified by the DTE via AT+FCC command, the DCE
shall set accordingly the current session parameters (controlled by the AT+FIS command).
All command parameters are optional; if a parameter is left blank, its value remains unchanged.

14.7.2 Syntax
Type
Set

Syntax
AT+FCC=[[[[[[[[[<vr>],<br>],<wd>],<ln>],<df>],<ec>],<bf>],<st>],<jp>]

UBX-13002752 - R67

ResponseOK

14 FAX class 2

ExamplePage 289 of 1001

u-blox cellular modules - AT commands manual

Type
Read

Syntax
AT+FCC?

Response<vr>,<br>,<wd>,<ln>,<df>,<ec>,<bf>,<st>,<jp>

Test

AT+FCC=?

OK(range of <vr>s),(range of <br>s),(range of <wd>s),(range of <ln>s),(range of <df>s),(range of <ec>s),(range of <bf>s),(range of <st>s),(range of <jp>s)

Example(0-1),(0-3),(0),(0-2),(0),(0),(0),(0-7),(0
)
OK

OK

14.7.3 Defined values
Parameter
<vr>
<br>
<wd>
<ln>
<df>
<ec>
<bf>
<st>
<jp>

Type
NumberNumberNumberNumberNumberNumberNumberNumberNumberDescription
Resolution in range 0-1
Bit rate in range 0-3
Page width in pixels; only 0 value allowed
Page length in range 0-2
Data compression format; only 0 value allowed
Error correction; only 0 value allowed
File transfer; only 0 value allowed
Scan time/line; in range 0-7
JPEG for colour and B&W; only 0 value allowed

14.8 Copy quality checking +FCQ
+FCQ
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.8.1 Description
Allows the control of copy quality checking and correction by a facsimile DCE.

14.8.2 Syntax
Type
Set
Read

Syntax
AT+FCQ=<rq>,<tq>
AT+FCQ?

ResponseOK<rq>,<tq>

ExampleTest

AT+FCQ=?

OK(range of <rq>s),(range of <tq>s)(0),(0)OKOK

14.8.3 Defined values
Parameter
<rq>

Type
Number<tq>

NumberUBX-13002752 - R67

Description
Controls copy quality checking and correction of data received from the remotestation and delivered to DTE
Controls copy quality checking and correction of image data received from the DTE
and sent to the remote station

14 FAX class 2

Page 290 of 1001

u-blox cellular modules - AT commands manual

14.9 Capability to receive data +FCR
+FCR
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.9.1 Description
Sets the capability to receive message data.

14.9.2 Syntax
Type
Set
Read

Syntax
AT+FCR=<value>
AT+FCR?

ResponseOK<value>ExampleTest

AT+FCR=?

OK(supported <value>)

(1)

OK

OK

14.9.3 Defined values
Parameter<value>Type
NumberDescription
Only value 1 allowed; DCE can receive message data. Bit 10 in the DIS or DTC frame will
be set14.10 Current session results +FCS
+FCS
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.10.1 Description
Allows displaying the current session results, either as a response to the read syntax or as an intermediate
result code during the execution of +FDT.

14.10.2 Syntax
Type
Read

Syntax
AT+FCS?

IRC
IRC

Response<vr>,<br>,<wd>,<ln>,<df>,<ec>,<bf>,<st>,<jp>

ExampleOK+FCS=<vr>,<br>,<wd>,<ln>,<df>,<ec>,<bf>,<st>,<jp>+FDCS=<vr>,<br>,<wd>,<ln>,<df>,<ec>,<bf>,<st>,<jp>14.10.3 Defined values
See +FCC.

UBX-13002752 - R67

14 FAX class 2

Page 291 of 1001

u-blox cellular modules - AT commands manual

14.11 DTE phase C response timeout +FCT
+FCTModules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.11.1 Description
Determines how long the DCE will wait for a command after having transmitted all available phase C data.

14.11.2 Syntax
Type
Set
Read

Syntax
AT+FCT=<value>
AT+FCT?

ResponseOK<value>ExampleTest

AT+FCT=?

OK(range of <value>s)(1-FF)

OKOK

14.11.3 Defined values
Parameter<value>Type
NumberDescription
Range 0x0-0xFF, in 1 second units. Default value: 0x1E (30) s

14.12 Receive data +FDR
+FDR
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.12.1 Description
Initiates data reception.

14.12.2 Syntax
Type
ActionSyntaxAT+FDR

Response
OK

Example14.13 Transmit Data +FDT
+FDT
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.13.1 Description
Prefixes data transmission. It requests the DCE to transmit a phase C page. It is issued at the beginning ofeach page in phase B or D.

14.13.2 Syntax
Type
ActionSyntaxAT+FDTUBX-13002752 - R67

ResponseOK

14 FAX class 2

ExamplePage 292 of 1001

u-blox cellular modules - AT commands manual

14.14 Phase C received EOL alignment +FEA
+FEA
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.14.1 Description
Controls optional octet-alignment of EOL markers in received T.4 data stream. It does not apply to T.6 data,or to any form of data.

14.14.2 Syntax
Type
Set
Read

SyntaxAT+FEA=<value>
AT+FEA?

ResponseOK<value>ExampleTest

AT+FEA=?

OK(supported <value>s)

(0)

OK

OK

14.14.3 Defined values
Parameter<value>Type
NumberDescription••

0: determines that T.4 EOL patterns are bit aligned (as received)
1: determines that the last received bits of T.4 EOL patterns are octet aligned by
the DCE, with necessary zero fill bits inserted (RFU)

14.15 Format conversion +FFC
+FFC
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.15.1 Description
Determines the DCE response to mismatches between the phase C data delivered after the +FDT commandand the data format parameters negotiated for the facsimile session. Currently no check or conversion is
supported.

14.15.2 Syntax
Type
Set
Read

SyntaxResponse
AT+FFC=<vrc>,<dfv>,<lnc>, <wdc> OK
AT+FFC?
<vrc>,<dfv>,<lnc>,<wdc>

Test

AT+FFC=?

ExampleOK(list of supported <vrc>s),(list of(0),(0),(0),(0)supported <dfv>s),(list of supported
OK<lnc>s),(list of supported <wdc>s)OK

14.15.3 Defined values
Parameter
<vrc>

Type
NumberDescription
vertical resolution format codes•••

UBX-13002752 - R67

0: ignored
1: enabled (RFU)
2: enabled for 1-D data (RFU)

14 FAX class 2

Page 293 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

<dfc>

NumberDescription• 3: enabled for 2-D data (RFU)
data format codes

Number• 0: ignored• 1: checking enabled (RFU)• 2: conversion (RFU)
page length format codes

Number• 0: ignored• 1: checking enabled (RFU)• 2: conversion for 1-D data (RFU)• 3: conversion enabled for 2-D data (RFU)
page with format codes

<lnc>

<wdc>

•
•
•

0: ignored
1: checking enabled (RFU)
2: conversion enabled (RFU)

14.16 Report file transfer diagnostic frame +FFD
+FFD
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.16.1 Description
This command has no parameters.

14.16.2 Syntax
Type
ActionSyntaxAT+FFD

Response
OK

Example14.17 Call termination status +FHS
+FHS
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.17.1 Description
indicates the cause of a hang-up; the cause is set by the DCE at the conclusion of a FAX session and reset to
0 at the beginning of phase A.

14.17.2 Syntax
Type
Read

SyntaxAT+FHS?

Response<value>ExampleOK

14.17.3 Defined values
Parameter<value>UBX-13002752 - R67

Type
NumberDescription
•
•
•
•
•
•

0x00: undefined
0x02: fax call cleared by the remote modem or the DTE
0x 11: Fax modem timed out in phase B
0x20: Unspecified transmitting phase B error
0x23: Invalid command received in transmitting phase B
0x40: Unspecified transmitting phase C error

14 FAX class 2

Page 294 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 0x43: Send fax data underflow• 0x70: Unspecified receiving phase B error• 0x50: Unspecified transmitting phase D error• 0xA0: Unspecified receiving phase D error

14.18 Procedure interrupt enable +FIE
+FIE
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.18.1 Description
Controls the procedure of interrupt handling.

14.18.2 Syntax
Type
Set
Read

SyntaxAT+FIE=<value>
AT+FIE?

ResponseOK<value>Test

AT+FIE=?

OK(range of <value>s)
OK+FET:<pmc>

IRC

Example(0-1)
OK

14.18.3 Defined values
Parameter<value>Type
Number<pmc>

NumberDescription•

0: procedure interrupt requests from the remote station are ignored and notreported to DTE• 1: procedure interrupt requests from the remote station are reported to DTE(allowed only on alternate speech/fax calls) as intermediate result code +FET
Post message command
•
•
•
•
•
•

0: MultiPage Signal - to indicate the end of a complete page of facsimile informationand the return to phase C upon receipt of a confirmation
1: End Of Message - to indicate the end of a complete page of facsimile information
and return to phase B
2: End Of Procedure - to indicate the end of a complete page of facsimile informationand proceeding to phase E upon receipt of a confirmation
3: same as 0, with return to phase B if operator intervention is accomplished
4: same as 1, with return to phase B if operator intervention is accomplished
5: same as 2, with return to phase B if operator intervention is accomplished14.19 Initialize facsimile parameters +FIP
+FIP
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.19.1 Description
Causes the DCE to initialize all Service Class Facsimile Parameters to the factory-programmed settings. It does
not change the +FCLASS setting. It should not be used when FAX connections are active.

UBX-13002752 - R67

14 FAX class 2

Page 295 of 1001

u-blox cellular modules - AT commands manual

14.19.2 Syntax
Type
Set
Read

SyntaxAT+FIP=[<value>]
AT+FIP?

Response
OK
0

ExampleTest

AT+FIP=?

OK(list of supported <value>s)

(0)

OK

OK

14.19.3 Defined values
Parameter<value>Type
NumberDescription
indicates the profile; only one profile is possible for <value>=0

14.20 Current session parameters +FIS
+FIS
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.20.1 Description
Allows the DTE to sense and constrain the capabilities of the current session. An intermediate result code may
also be sent to the DTE during fax calls to indicate current negotiated parameters.

14.20.2 Syntax
Type
Set
Read

Test

SyntaxResponse
AT+FIS=[[[[[[[[[<vr>],<br>], <wd>], OK<ln>],<df>],<ec>], <bf>],<st>],<jp>]
AT+FIS?
+FIS: <vr>,<br>,<wd>,<ln>,<df>,<ec>,<bf>,<st>,<jp>
OK+FIS: (range of <vr>s),(range of<br>s),(range of <wd>s), (range of<ln>s),((range of <df>s),(range of<ec>s), (range of <bf>s),(range of<st>s),(range of <jp>s)

AT+FIS=?

Example+FIS: (0-1),(0-3),(0),(0-2),(0),(0),(0),(0-7),(0)OK

OK+FIS=<vr>,<br>,<wd>,<ln>, <df>,<ec>,<bf>,<st>,<jp>IRC

14.20.3 Defined values
Parameter
<vr>
<br>
<wd>
<ln>
<df>
<ec>
<bf>
<st>
<jp>

UBX-13002752 - R67

Type
NumberNumberNumberNumberNumberNumberNumberNumberNumberDescription
Resolution, range 0-1
Bit rate, range 0-3
Page width in pixels; only 0 value allowed
Page length, range 0-2
Data compression format; only 0 value allowed
Error correction; only 0 value allowed
File transfer; only 0 value allowed
Scan time/line, range 0-7
JPEG for colour and B&W; only 0 value allowed

14 FAX class 2

Page 296 of 1001

u-blox cellular modules - AT commands manual

14.21 Inactivity timeout +FIT
+FIT
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.21.1 Description
Provides an inactivity timer which allows the DCE to break away from an unsuccessful connection attempt at
any stage of a facsimile transfer.

14.21.2 Syntax
Type
Set
Read

SyntaxAT+FIT=[<time>[,<action>]]
AT+FIT?

ResponseOK<time>,<action>

Test

AT+FIT=?

OK(range of <time>s),(supported<action>)Example(0-255),(0)OKOK

14.21.3 Defined values
Parameter<time><action>Type
NumberNumberDescription
Timer duration in seconds, range 0-255
Only value 0 possible, which means: when timer expire, the DCE shall clear the call.

14.22 Session termination +FKS, +FK+FK
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.22.1 Description
Causes the DCE to terminate the session in an orderly manner: if the DCE has an active, non-transmitting FAX
call, it will send a DCN message and hang up.

14.22.2 Syntax
Type
Set

SyntaxAT+FK<S>

Response
OK

Example14.23 Local ID string +FLI
+FLI
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.23.1 Description
Determines that DCE sends the ID frame if +FLI is not a zero-string.

14.23.2 Syntax
Type
Set

SyntaxAT+FLI=<local ID string>

UBX-13002752 - R67

ResponseOK

14 FAX class 2

ExamplePage 297 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+FLI?

Response<local ID string>

ExampleTest

AT+FLI=?

OK(range of char values)(20-7E)OK

OK

14.23.3 Defined values
Parameter<local ID string>Type
StringDescription
20 digit string; valid codes for characters are in the range 0x20-0x7E

14.24 Set flow control +FLO
+FLO
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.24.1 Description
Allows setting the flow control for communication via V.24 interface.

14.24.2 Syntax
Type
Set
Read

SyntaxAT+FLO=<value>
AT+FLO?

ResponseOK<value>ExampleTest

AT+FLO=?

OK(range of <value>s)

(0-2)

OK

OK

14.24.3 Defined values
Parameter<value>Type
NumberDescription
indicates the kind of flow control•••

0: DTE-DCE flow control is disabled
1: DTE-DCE flow control is DC1/DC3 (SW flow control)
2: DTE-DCE flow control is RTC/CTS (HW flow control)

14.25 Indicate document to poll +FLP
+FLP
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.25.1 Description
Indicates that a document is available for retrieval. By default the DTE has no document to poll.

14.25.2 Syntax
Type
Set
Read

SyntaxAT+FLP=<value>
AT+FLP?

ResponseOK<value>Test

AT+FLP=?

OK(range of <value>s)

(0)

OK

OK

UBX-13002752 - R67

14 FAX class 2

ExamplePage 298 of 1001

u-blox cellular modules - AT commands manual

14.25.3 Defined values
Parameter<value>Type
NumberDescription
only value 0 is allowed

14.26 Request manufacturer identification +FMI
+FMI
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

14.26.1 Description
Text string identifying the manufacturer.

14.26.2 Syntax
Type
ActionSyntaxAT+FMI

Response<manufacturer>

Exampleu-bloxAT+FMI=?

OK
OK

OK

Test

14.26.3 Defined values
Parameter<manufacturer>

Type
StringDescription
manufacturer name14.27 Request model identification +FMM
+FMM
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

14.27.1 Description
Text string identifying the model identification.

14.27.2 Syntax
Type
ActionSyntaxAT+FMM

Response<model>ExampleSARA-G350

AT+FMM=?

OK
OK

OK

Test

14.27.3 Defined values
Parameter<model>UBX-13002752 - R67

TypeStringDescription
Name of model

14 FAX class 2

Page 299 of 1001

u-blox cellular modules - AT commands manual

14.28 Request revision identification +FMR
+FMR
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

14.28.1 Description
Gives the firmware version of the module.

14.28.2 Syntax
Type
ActionSyntaxAT+FMR

Response<version>

Example07.11.00

AT+FMR=?

OK
OK

OK

Test

14.28.3 Defined values
Parameter<version>

Type
StringDescription
Firmware version

14.29 Minimum phase C speed +FMS
+FMS
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.29.1 Description
Limits the lowest negotiable speed for a fax session.

14.29.2 Syntax
Type
Set
Read

SyntaxAT+FMS=<value>
AT+FMS?

ResponseOK<value>ExampleTest

AT+FMS=?

OK(range of <value>s)

(0-3)

OK

OK

14.29.3 Defined values
Parameter<value>UBX-13002752 - R67

Type
NumberDescription••••

0: 2400 b/s (default)
1: 4800 b/s
2: 7200 b/s
3: 9600 b/s

14 FAX class 2

Page 300 of 1001

u-blox cellular modules - AT commands manual

14.30 Negotiation reporting +FNR
+FNR
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.30.1 Description
Controls the reporting of messages generated during T.30 phase B negotiations.

14.30.2 Syntax
Type
Set
Read

SyntaxAT+FNR=[<rpr>[,<tpr>[,<idr>[,<nsr>]]]]
AT+FNR?

Test

AT+FNR=?

Response
OK

Example<rpr>,<tpr>,<idr>,<nsr>OK(range of <rpr>s), (range of <tpr>),(range of <idr>s), (range of <nsr>s)(0-1),(0-1),(0-1),(0-1)
OKOK

14.30.3 Defined values
Parameter
<rpr>
<tpr>
<idr>
<nsr>

Type
NumberNumberStringStringDescription
Receiver parameters reporting: 0-1 (no-yes)
Transmitter parameters reporting: 0-1 (no-yes)
ID strings reporting: 0-1 (no-yes)
Non-standard frame FIF octet string +FNS

14.31 Non-standard frame FIF octet string +FNS+FNS
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.31.1 Description
Allows configuring the corresponding non-standard facilities frame. The command is not currently used.

14.31.2 Syntax
Type
Set
Read

SyntaxAT+FNS=<string>
AT+FNS?

ResponseOK<string>

ExampleTest

AT+FNS=?

OK(range of character codes)(20-7E)OK

OK

14.31.3 Defined values
Parameter<string>

UBX-13002752 - R67

TypeStringDescription
Characters in range 0x20-0x7E

14 FAX class 2

Page 301 of 1001

u-blox cellular modules - AT commands manual

14.32 NSF message data indication +FND
+FND
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.32.1 Description
Controls indication of non-standard facilities frames. The command is not currently used.

14.32.2 Syntax
Type
Set
Read

SyntaxAT+FND=<value>
AT+FND?

ResponseOK<value>ExampleTest

AT+FND=?

OK(range of <value>s)

(0-1)

OK

OK

14.32.3 Defined values
Parameter<value>Type
NumberDescription
range 0-1 (enabled/disabled).

14.33 Selective polling address +FPA
+FPA
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.33.1 Description
Sets the selective polling address. The DCE should send the numeric string contained in the +FPA at the times
specified in T.30, if the corresponding parameter is not a zero string. The command is not currently used.

14.33.2 Syntax
Type
Set

SyntaxResponse
AT+FPA=<selective polling address OK
string>ExampleAT+FPA="1234"

Read

AT+FPA?

<selective polling address string>OK"1234"

Test

AT+FPA=?

OK(range of character codes)OK(20-7E)OK

OK

14.33.3 Defined values
Parameter<selective polling
address string>

UBX-13002752 - R67

TypeStringDescription
20 digit string: values are in range 0x20-0x7E

14 FAX class 2

Page 302 of 1001

u-blox cellular modules - AT commands manual

14.34 Local polling ID string +FPI
+FPI
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.34.1 Description
Allows the DCE to send the ID frame if +FPI is not a null string. The command is not currently used.

14.34.2 Syntax
Type
Set
Read

SyntaxAT+FPI=<local polling ID string>
AT+FPI?

ResponseOK<local polling ID string>

ExampleTest

AT+FPI=?

OK(range of character codes)OK(20-7E)

OK

OK"1234"

14.34.3 Defined values
Parameter<local polling ID
string>Type
StringDescription
only null string "" is allowed

14.35 Packet protocol control +FPP
+FPP
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.35.1 Description
Allows controlling the packet protocol. The packet protocol is not currently supported.

14.35.2 Syntax
Type
Set
Read

SyntaxAT+FPP=[<value>]
AT+FPP?

ResponseOK<value>ExampleTest

AT+FPP=?

OK(supported <value>)

(0)

OK

OK

14.35.3 Defined values
Parameter<value>UBX-13002752 - R67

Type
NumberDescription
only value 0 allowed

14 FAX class 2

Page 303 of 1001

u-blox cellular modules - AT commands manual

14.36 Page status +FPS
+FPS
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.36.1 Description
Sets the post page response, in particular end-of-page status, to be sent to the remote part. During fax
transmission, post page response of the remote part is indicated to the DTE with an intermediate result code
+FPS.

14.36.2 Syntax
Type
Set
Read

SyntaxAT+FPS=[<value>]
AT+FPS?

ResponseOK<value>ExampleTest

AT+FPS=?

OK(range of <value>)

(1-5)

OK

OK

14.36.3 Defined values
Parameter<value>Type
NumberDescription
•
•
•
•
•

1: MCF, page good (default value)
2: RTN, page bad; retrain requested
3: RTP, page good; retrain requested
4: PIN, page bad; interrupt requested
5: PIP, page good; interrupt requested

14.37 Password parameter +FPW
+FPW
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.37.1 Description
Sets the password. The DCE sends the numeric string contained in +FPW at the times specified in T.30, if thecorresponding parameter is not a null string.

14.37.2 Syntax
Type
Set

SyntaxAT+FPW=<password string>Response
OK

ExampleAT+FPW="1234"

Read

AT+FPW?

"<password string>"

Test

AT+FPW=?

OK(range of <value>)"1234"OK

OK

OK

14.37.3 Defined values
Parameter<password string>

UBX-13002752 - R67

TypeStringDescription
Valid characters: 0-9, *, #, space

14 FAX class 2

Page 304 of 1001

u-blox cellular modules - AT commands manual

14.38 Receive quality thresholds +FRQ
+FRQModules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.38.1 Description
Allows making the "Copy Quality OK" decision using the command parameters. The command is not currently
used.

14.38.2 Syntax
Type
Set
Read

SyntaxAT+FRQ=<pgl>,<cbl>
AT+FRQ?

ResponseOK<pgl>,<cbl>

Test

AT+FRQ=?

OK(supported <pgl>),(supported <cbl>) (0),(0)OK

ExampleOK

14.38.3 Defined values
Parameter
<pgl>
<cbl>

Type
NumberNumberDescription
Percentage of good lines: only value 0 accepted
Consecutive bad lines: only value 0 accepted

14.39 Error correction mode retry count +FRY
+FRY
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.39.1 Description
Controls the retry counter in Error Correcting Mode. The command is not currently used.

14.39.2 Syntax
Type
Set
Read

SyntaxAT+FRY=[<value>]
AT+FRY?

ResponseOK<count>ExampleTest

AT+FRY=?

OK(range of <count>)(0-FF)

OKOK

14.39.3 Defined values
Parameter<value>UBX-13002752 - R67

Type
NumberDescription
In range 0-0xFF (0 if blank)

14 FAX class 2

Page 305 of 1001

u-blox cellular modules - AT commands manual

14.40 SubAddress parameter +FSA
+FSA
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.40.1 Description
Sets the subaddress. The DCE sends the numeric string configured via AT+FSA at the times specified in T.30,
if the corresponding parameter is not a null string.

14.40.2 Syntax
Type
Set

SyntaxResponse
AT+FSA=<destination SubAddress OK
string>ExampleAT+FSA="1234"

Read

AT+FSA?

"<destination SubAddress string>"

OK"1234"Test

AT+FSA=?

OK(range of character codes)OK(20-7E)

OK

OK

14.40.3 Defined values
ParameterType<destination
StringSubAddress string>

Description
20 digit string; allowed values: 0-9, *, #, space

14.41 Request to poll +FSP
+FSP
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

14.41.1 Description
This command indicates whether or not the DTE wants to poll. The command is not currently used.

14.41.2 Syntax
Type
Set
Read

SyntaxAT+FSP=[<value>]
AT+FSP?

ResponseOK<value>ExampleTest

AT+FSP=?

OK(supported <value>)

(0)

OK

OK

14.42 Fax intermediate result codes
14.42.1 Description
According to Recommendation T.32, Tab. 6, the following intermediate result codes are provided to the DTE
during fax calls.
IRC
+FCO
+FVO
+FHS

UBX-13002752 - R67

Meaning
Indicates connection with a fax terminal
Indicates transition to voice
Call terminated with status

14 FAX class 2

Page 306 of 1001

u-blox cellular modules - AT commands manual

IRC
+FCS
+FDCS
+FIS
+FTI
+FTSI
+FCI
+FCSI
+FET
+FPS
+FPTS
+FHT
+FHR

UBX-13002752 - R67

Meaning
Report the DCS frame information
Report the DCS frame information for speech/fax alternate calls
Report the DIS frame information
Report the remote (transmitting) ID, from TSI (Transmitting Subscriber
Identification) frame
Report the remote (transmitting) ID, from TSI (Transmitting Subscriber
Identification) frame for speech/fax alternate calls
Report the remote (called) ID, from CSI (Called Subscriber Identification)
Report the remote (called) ID, from CSI (Called Subscriber Identification forspeech/fax alternate calls)
Report post page message
Report received page status
Report received page status for speech/fax alternate calls
Report transmitted HDLC frames
Debug report received HDLC frames

14 FAX class 2

Page 307 of 1001

u-blox cellular modules - AT commands manual

15 V24 control and V25ter
15.1 Introduction
These commands, unless specifically stated, do not implement set syntax using "=", read ("?"), or test ("=?").
If such commands are used, the "+CME ERROR: unknown" or "+CME ERROR: 100" error result code is provided(depending on the +CMEE AT command setting).
SARA-G4 / SARA-G3 / LEON-G1
If the set, read or test syntax is used the "+CME ERROR: operation not supported" or "+CME ERROR: 4"
error result code is provided ("+CME ERROR: operation not allowed" or "+CME ERROR: 3" depending on
the +CMEE AT command setting.

15.2 Circuit 109 behavior &C&C
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.2.1 Description
Controls how the state of RS232 circuit 109 - Data Carrier Detect (DCD) - relates to the detection of received
line signal from the remote end.
LARA-R211 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-G450-01C / SARA-G340-02S /SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X
On the AUX UART interface the command is not effective.

15.2.2 Syntax
Type
ActionSyntaxAT&C[<value>]Response
OK

Example15.2.3 Defined values
Parameter<value>Type
NumberDescription
Indicates the behavior of circuit 109••

0: DCE always presents ON condition on circuit 109
1 (default value and factory-programmed value): circuit 109 changes in accordancewith the Carrier detect status; ON if the Carrier is detected, OFF otherwise

15.2.4 Notes•

See the corresponding module system integration manual for the DCD behavior during the initialization
phase of the module.

TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S• The command has not effect.

UBX-13002752 - R67

15 V24 control and V25ter

Page 308 of 1001

u-blox cellular modules - AT commands manual

15.3 Circuit 108/2 behavior &D&D
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.3.1 Description
Controls how the state of RS232 circuit 108/2 - Data Terminal Ready (DTR) - relates to changes from ON to
OFF condition during on-line data state.

15.3.2 Syntax
Type
ActionSyntaxAT&D[<value>]Response
OK

Example15.3.3 Defined values
Parameter<value>Type
NumberDescription
Allowed values:• 0: the DCE ignores circuit 108/2• 1 (default value and factory-programmed value): upon an ON-to-OFF transition of
circuit 108/2, the DCE enters online command state and issues the final result code
• 2: upon an ON-to-OFF transition of circuit 108/2, the DCE performs an orderly
cleardown of the call. The automatic answer is disabled while circuit 108/2 remains
OFF

15.3.4 ~+++ behavior
TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S
The ~+++ behavior in PSD &D is not supported.
••

A special meaning of the &D value is provided for the ~+++ sequence during a PSD data transfer with PPP
L2 protocol (this is outside the V25-ter specification scope). The ~+++ causes context deactivation during
a PSD data transfer session for the AT&D0 and AT&D2 value (the +++ return to on-line command mode isprovided for each &D value during a CSD data call)
A different implementation for the ~+++ is done with the &D1 value: the PSD data transfer is escaped andsystem returns in the on-line command state. The ATO command is used to resume the PSD data transfer
session
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
During the on-line command mode different AT commands can be sent but data calls in PSD on-line
command mode cannot be granted (issue the AT+CRC=1 command (where applicable) to identify the kindof call and reject data incoming calls if PSD is in the on-line command mode).
For more details, see the ITU-T Recommendation V250 [19], ITU-T V.25ter Recommendation [20] andITU-T V.32 Recommendation [21].
See the corresponding module system integration manual for the DTR behavior during the initialization
phase of the module.

15.3.5 DTR, +++ behavior
CSD data mode
Event
&D0
&D1

UBX-13002752 - R67

DTE sends escape sequence (e.g. +++)
DCE enters command mode
DCE enters command mode

15 V24 control and V25ter

DTR On to Off transition
No action
Switch to command mode

Page 309 of 1001

u-blox cellular modules - AT commands manual

CSD data mode
Event
&D2

DTE sends escape sequence (e.g. +++)
DCE enters command mode

DTR On to Off transition
Cleardown call

Table 21: CSD data mode
PSD data mode (PPP L2 protocol case)
Event
&D0
&D1
&D2

DTE sends ~+++
Context deactivation
DCE enters command mode
Context deactivation

DTR On to Off transition
No action
DCE enters command mode
Context deactivation

Table 22: PSD data mode

15.3.6 Notes••

The ON/OFF DTR transition in direct link forces the DCE into command mode. In case of AT&D0 the DTR
transition is ignored, also in direct link.
The escape sequence for the PSD data mode with a L2 protocol different from the PPP is not ~+++, andit could be not supported. For more information, see the S2 notes.

TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S• The command has not effect.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the DTR line is always considered to ON state (even if the AUX UART does notsupport the DTR line).
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-G450-01C / SARA-G340-02S /SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, the DTR line is always considered to ON state (even if the AUX UART does
not support the DTR line).

15.4 DSR override &S&S
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-60S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
MPCI-L200-02S MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L210-60S
MPCI-L210-63S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
fullNoProfileNo+CME Error

15.4.1 Description
Selects how the module will control RS232 circuit 107 - Data Set Ready (DSR).
LARA-R211 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-G450-01C / SARA-G340-02S /SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X
On the AUX UART interface the command is not effective.

15.4.2 Syntax
Type
ActionSyntaxAT&S[<value>]

UBX-13002752 - R67

ResponseOK

15 V24 control and V25ter

ExamplePage 310 of 1001

u-blox cellular modules - AT commands manual

15.4.3 Defined values
Parameter<value>Type
NumberDescription••

0: sets the DSR line to ON
1 (default value and factory-programmed value): sets the DSR line to ON in data
mode and to OFF in command mode

15.4.4 Notes•

See the corresponding module system integration manual for the DSR behavior during the initialization
phase of the module.

MPCI-L2• The command has no effect.

15.5 Flow control &K&K
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-60S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
MPCI-L200-02S MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L210-60S
MPCI-L210-63S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
fullNoProfileNo+CME Error

15.5.1 Description
Controls the flow control mechanism. The following settings are allowed:• No flow control• HW flow control also referred with RTS / CTS flow control• SW flow control also referred with XON / XOFF flow control

15.5.2 Syntax
Type
ActionSyntaxAT&K[<value>]Response
OK

Example15.5.3 Defined values
Parameter<value>Type
NumberDescription
•
•
•
•
•

0: disable DTE flow control
3 (default and factory-programmed value): enable the RTS/CTS DTE flow control
4: enable the XON/XOFF DTE flow control
5: enable the XON/XOFF DTE flow control
6: enable the XON/XOFF DTE flow control

15.5.4 Notes•

The command handling is the same for <value> parameter 4, 5 or 6.

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• On the UART interface, in case of +UPSV: 2, only &K0 (no flow control) is allowed.
• Set the <value> parameter of AT&K command to 0 (flow control disabled) or 4, 5 or 6 (software flow
control) when the RTS and CTS lines are not physically connected.
• The software flow control (XON/XOFF) setting is not allowed on the USB interfaces, on the SPI interface
and on a multiplexer channel. See the Multiple AT command interfaces for all the behavior differences inrespect to the supported interfaces.

UBX-13002752 - R67

15 V24 control and V25ter

Page 311 of 1001

u-blox cellular modules - AT commands manual••

The SW flow control (XON/XOFF) activation is only allowed in case of the text transmission: the binary
data cannot be transmitted because it may contain the special flow control characters (XON/XOFF).
When the software flow control (XON/XOFF) is used, the DC1 (XON, 0x11) and DC3 (XOFF, 0x13) characters
are reserved and therefore filtered (e.g. in SMS text mode these two characters can not be input).
Since the DTE-DCE communication relies on the correct reception of DC1/DC3 characters, the UART
power saving should be disabled on the module when the SW flow control is used. If the UART powersaving is active, the DC1/DC3 characters could be used to wake up the module's UART, and therefore lost.
In case a DC3 character (XOFF) is correctly received by module's UART and some data is waiting to betransmitted, the module is forced to stay awake until a subsequent DC1 character (XON) is received.

TOBY-L2• The command setting is not displayed in the AT&V information text response.
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280• On the UART interface, in case of +UPSV: 1, the SW flow control shall not be set (<value>=4, 5 and 6
shall not be used).
• On the UART interface, in case of +UPSV: 2, the SW flow control is also supported (<value>=4, 5 and 6
are allowed), but the HW flow control is still forbidden (<value>=3 is not allowed).
TOBY-L201 / TOBY-L210-60S• The SW flow control is not supported (<value>=4, 5 and 6 are not allowed).
TOBY-L200-00S / TOBY-L210-00S / MPCI-L2• The command has no effect.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the HW flow control is not supported (<value>=3 is not allowed).
• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the default and factory-programmed value for <value> is 0.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-G340-02S / SARA-G340-02X /SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, the HW flow control is not supported (<value>=3 is not allowed).
• On the AUX UART interface, the default and factory-programmed value for <value> is 0.
SARA-G4• <value>=4,5,6 are not supported.
• On the UART interface, in case of +UPSV: 2, only &K0 (no flow control) is allowed.
SARA-G450-01C• On the AUX UART interface, the HW flow control is not supported (<value>=3 is not allowed).
• On the AUX UART interface, the default and factory-programmed value for <value> is 0.

15.5.5 TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /SARA-G4 SW flow control enhancement for PSD data transfer with PPP L2
protocolLISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S
The SW flow control enhancement is not supported by these products.
The software flow control enhancement is only supported on the UART interface.
The standard implementation of the UART XON/XOFF flow control is limited to DTE-DCE communications
where the ASCII non-printable control characters are not transferred. This is an important limitation, since it is
not possible to use it in case of the generic binary data transfer. An extension to a PPP L2 protocol data transfer
has been done by exploiting the PPP octet stuffing procedure.
PPP Octet-stuffed framing and transparency
The PPP protocol implements an escape mechanism specified to allow control data such as XON/XOFF to betransparently transmitted over the link, and to remove spurious control data which may be injected into thelink by intervening hardware and software.

UBX-13002752 - R67

15 V24 control and V25ter

Page 312 of 1001

u-blox cellular modules - AT commands manual

The control escape octet is defined as binary 01111101 (hexadecimal 0x7d), most significant bit first. As aminimum, sending implementations must escape the flag sequence and control escape octets.
After Frame Check Sequence (FCS) computation, the transmitter examines the entire frame between thetwo flag sequences. Each flag sequence, control escape octet, and any octet which is flagged in the sending
Async-Control - Character-Map (ACCM), is replaced by a two octet sequence consisting of the control escapeoctet followed by the original octet exclusive-or'd with hexadecimal 0x20.
The receiving implementations must correctly process all the control escape sequences. On the reception, prior
to FCS computation, each octet with value less than hexadecimal 0x20 is checked. If it is flagged in the receiving
ACCM, it is simply removed (it may have been inserted by intervening data communications equipment). Eachcontrol escape octet is also removed, and the following octet is exclusive-or'd with hexadecimal 0x20, unless
it is the flag sequence (which aborts a frame).
ACCM negotiation for XON/XOFF chars during PPP LCP negotiation
The ACCM is negotiated in a LCP (Link Control Protocol, part of PPP protocol) configuration request. In
particular the LCP Option 02 is used.
This option is described in the RFC 1662 and has the following format.
| 02 | 06 | Async Control Character Map |This configuration option provides a method to negotiate the use of control character transparency on
asynchronous links.
The module by default would start in any case requesting an ACCM sets to 0x00000000, which is incompatible
with XON/XOFF flow control.
To overcome this situation, the ACCM negotiation handler should combine the value received in a
Configure-Nak via a logical bitwise OR operation with the last configure-request value it sent. This result should
then be sent in the next Configure-Request message. If a configure-request is received whose bit mask includes
cleared bits for characters that the local implementation knows to be problematic (perhaps by way of an
administrative option or some kind of hardware information), then it should send a Configure-Nak with theprior value modified to have these bits set.
Application to XON/XOFF flow control implementation in the module
The flow control characters DC1 and DC3 appears at arbitrary locations in the data stream received by themodule. The module with software flow control active during a PPP session, discards these characters after
modifying the flow control state (stopping or starting its own transmit process) and does not include them inany part of the received data or CRC calculation; in the transmitted data the module escapes the XON/XOFF
characters if they appear in the transmitted PPP frame. They are transmitted on the link as follows:
0x11 is encoded as 0x7d, 0x31. (XON)
0x13 is encoded as 0x7d, 0x33. (XOFF)
PPP ACCM negotiation in the module firmware is implemented in the following way:••

If the XON/XOFF flow control is active on the UART when the PPP is invoked, the requested ACCM is
0x000A0000
If the XON/XOFF flow control is not active on the UART when the PPP is invoked, the requested ACCM is
0x00000000

As soon as the LCP configuration phase is completed, the IPCP protocol (the network control protocol forestablishing and configuring Internet Protocol over a Point-to-Point Protocol link) can start; from this point
forward the negotiated ACCM are applied.
If SW flow control is enabled on the module, but the DTE requests a wrong ACCM setting (ACCM differs than
0x0A0000) the SW flow control is anyway effective during the data mode, that is the 0x11 and 0x13 is detectedduring data mode even if the ACCM is not properly set by the DTE during LCP configuration.

UBX-13002752 - R67

15 V24 control and V25ter

Page 313 of 1001

u-blox cellular modules - AT commands manual

15.6 DTE-DCE character framing +ICF
+ICF
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.6.1 Description
Sets the local serial port start-stop (asynchronous) character framing which is used in information interchange
between DCE and DTE. Value 0 corresponds to the auto-detect case (if autobauding is supported).
The following restrictions must be reminded:• If a data frame format refers to a frame without parity (ex. Format 3), the command is accepted, but
the parity value is ignored; it is returned by the AT+ICF read command (and displayed by AT&V) but
it has no meaning• The command setting is ignored when the AT command interface runs on the USB or on the SPI
interface

15.6.2 Syntax
Type
Set

SyntaxAT+ICF=[<format>[,<parity>]]

Response
OK

ExampleAT+ICF=3,1

Read

AT+ICF?

+ICF: <format>,<parity>

OK+ICF: 3,1

Test

AT+ICF=?

OK
OK+ICF: (list of supported <format>s), +ICF: (0-3,5),(0-1)(list of supported <parity>s)OKOK

15.6.3 Defined values
Parameter<format>Type
NumberDescription
•
•
•
•
•
•
•

0: auto detect
1: 8 data 2 stop
2: 8 data 1 parity 1 stop
3: 8 data 1 stop
4: 7 data 2 stops
5: 7 bit, 1 parity, 1 stop
6: 7 bit, 1 stop<parity>

Number••0: odd
1: even

15.6.4 Notes
TOBY-L2 / MPCI-L2• The PIN insertion is not mandatory before the command execution.
TOBY-L200-00S / TOBY-L210-00S / MPCI-L2• The command has no effect.
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L201 / TOBY-L210-02S /TOBY-L210-03A / TOBY-L210-03S / TOBY-L210-60S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 /TOBY-L280• Automatic frame recognition is not supported (<format> cannot be set to 0).
• The factory-programmed values are <format> = 3 and <parity> = 1.

UBX-13002752 - R67

15 V24 control and V25ter

Page 314 of 1001

u-blox cellular modules - AT commands manual

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• The PIN insertion is not mandatory before the command execution.
• The <format> parameter cannot be set to 4 and 6.
• If the parameters are omitted they are set to <format> = 3 and <parity> = 1.
• The factory-programmed values are <format> = 3 and <parity> = 1.
• Automatic frame recognition
If automatic baud rate detection (+IPR is set to 0) is enabled in the profile, the +ICF setting is not applied
at start-up, and the read command returns the current detected frame format only after detection.
o Automatic frame recognition is present together with automatic baud rate recognitiono Since automatic frame recognition is implemented as "one shot", the AT+ICF=0 answers OK as final
result code but does not switch the system to the automatic frame recognition and it does not takeany actions. The read command always returns the current value of the frame format and the valueof +ICF in the active profile is not changedo If automatic frame recognition is enabled, the read command returns the current (detected) frame
setting even if the current active profile provides +ICF=0. To change the frame format at the next
module power on issue the set command with the new setting and save it in the profileo The detectable frame configurations are: 7E1, 7O1, 8N1, 8E1, 8O1
o The stop bit number cannot be automatically recognized i.e. if the system is switched from the 8N2
to the autodetect feature and a 1 stop bit frame is provided at the serial port, the system can behave
unpredictably
LISA-U200-00S• Automatic frame recognition is not supported (<format> cannot be set to 0).
SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.
• The <format> parameter cannot be set to 4 and 6.
• If the parameters are omitted they are set to <format> = 0 and <parity> = 0.
• The factory-programmed values are <format> = 0 and <parity> = 0.
• Automatic frame recognition
Frame recognition can only be present in conjunction with autobauding recognition, i.e. the AT+ICF=0
command is effective only if AT+IPR is set to 0. In this case the AT+ICF? returns a 0 value.
o Outside the autobauding conditions the AT+ICF=0 answers OK as final result code but does notswitch the system to automatic frame recognition and it does not take any actions. In this scenario
the AT+ICF? command returns the current value of the frame format. The AT+IPR=0 command
instead forces the AT+ICF to 0o Under autobauding conditions, the AT+ICF command provided with a value different than 0
provides an error result code since it is not possible to specify a frame type in these autodetect
conditionso The stop bit number cannot be automatically recognized i.e. if the system is switched from the
8N2 to the autodetect feature and an 1 stop bit frame is provided at the serial port, the system canbehave unpredictably
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, automatic frame recognition is not supported (<format> cannot be setto 0).
• On the AUX UART interface: the default and factory-programmed value for <format> is 3; the default
and factory-programmed value for <parity> is 1.
SARA-G4• The PIN insertion is not mandatory before the command execution.
• <format>=0, 4, 5, 6 are not supported.
• The factory-programmed values are <format>= 3 and <parity>= 1.
SARA-G450-01C• On the AUX UART interface, automatic frame recognition is not supported (<format> cannot be setto 0).

UBX-13002752 - R67

15 V24 control and V25ter

Page 315 of 1001

u-blox cellular modules - AT commands manual•

On the AUX UART interface: the default and factory-programmed value for <format> is 3; the default
and factory-programmed value for <parity> is 1.

15.7 DTE-DCE local flow control +IFC
+IFC
Modules

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Attributes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.7.1 Description
Controls the operation of the local flow control between DTE and DCE used when the data are sent or received.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The SW flow control (XON/XOFF) activation is only allowed in case of the text transmission: the binary
data cannot be transmitted because it may contain the special flow control characters (XON/XOFF). For
the SW flow control enhancement, allowing its usage during a PSD call with PPP L2 protocol, see SW flow
control enhancement for PSD data transfer with PPP L2 protocol in the AT&K command description.
When the software flow control (XON/XOFF) is used, the DC1 (XON, 0x11) and DC3 (XOFF, 0x13) characters arereserved and therefore filtered (e.g. in SMS text mode these two characters can not be input).
Since the DTE-DCE communication relies on the correct reception of DC1/DC3 characters, the UART powersaving should be disabled on the module when SW flow control is used. If the UART power saving is active, theDC1/DC3 characters could be used to wake up the module's UART, and therefore lost. In case a DC3 character(XOFF) is correctly received by module's UART and some data is waiting to be transmitted, the module is forced
to stay awake until a subsequent DC1 character (XON) is received.
The software flow control (XON/XOFF) setting is not allowed on the USB interfaces, on the SPI interface
and on a multiplexer channel. See the Multiple AT command interfaces for all the behavior differences inrespect to the supported interfaces.

15.7.2 Syntax
Type
Set

SyntaxResponse
AT+IFC=[<DCE_by_DTE>[,<DTE_by_ OK
DCE>]]Read

AT+IFC?

Test+IFC: <DCE_by_DTE>,<DTE_by_
DCE>
OK+IFC: (list of supported <DCE_by_
DTE>),(list of supported <DTE_by_
DCE>s)

AT+IFC=?

ExampleAT+IFC=2,2
OK+IFC: 2,2
OK
+IFC: (0-2),(0-2)
OKOK

15.7.3 Defined values
Parameter<DCE_by_DTE>

Type
NumberDescription•••

0: none
1: DC1/DC3 on circuit 103 (XON/XOFF)
2 (default and the factory-programmed value): circuit 105 (RTS)<DTE_by_DCE>

Number

•••0: none
1: DC1/DC3 on circuit 104 (XON/XOFF)
2 (default and the factory-programmed value): circuit 106 (CTS)UBX-13002752 - R67

15 V24 control and V25ter

Page 316 of 1001

u-blox cellular modules - AT commands manual

15.7.4 Notes•<DCE_by_DTE> and <DTE_by_DCE> parameters must be provided with the same value in pairs (only (0,0), (1,1) and (2,2) are allowed. The other combinations are not allowed and the "+CME ERROR: operation
not allowed" error result code is returned).

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• On the UART interface, in case of +UPSV: 2, only +IFC=0,0 (no flow control) is allowed.
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280• On the UART interface, in case of +UPSV: 1, the SW flow control shall not be set (<DCE_by_DTE> and<DTE_by_DCE> shall not be set to 1).
• On the UART interface, in case of +UPSV: 2, the SW flow control is also supported (<DCE_by_DTE> and<DTE_by_DCE> can be set to 1), but the HW flow control is still forbidden (<DCE_by_DTE> and <DTE_
by_DCE> cannot be set to 2).
TOBY-L201 / TOBY-L210-60S• The SW flow control is not supported (<DCE_by_DTE> and <DTE_by_DCE> cannot be set to 1).
TOBY-L200-00S / TOBY-L210-00S / MPCI-L2• The command has no effect.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the HW flow control is not supported (<DCE_by_DTE> and <DTE_by_DCE> cannot
be set to 2).
• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the default and factory-programmed value for <DCE_by_DTE> and <DTE_by_
DCE> is 0.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• On the AUX UART interface, the HW flow control is not supported (<DCE_by_DTE> and <DTE_by_DCE>
cannot be set to 2).
• On the AUX UART interface, the default and factory-programmed value for <DCE_by_DTE> and <DTE_
by_DCE> is 0.
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, the HW flow control is not supported (<DCE_by_DTE> and <DTE_by_DCE>
cannot be set to 2).
• On the AUX UART interface, the default and factory-programmed value for <DCE_by_DTE> and <DTE_
by_DCE> is 0.
SARA-G4• On the UART interface, in case of +UPSV: 2, only +IFC=0,0 (no flow control) is allowed.
• <DCE_by_DTE>=1 is not supported.
• <DTE_by_DCE>=1 is not supported.
SARA-G450-01C• On the AUX UART interface, the HW flow control is not supported (<DCE_by_DTE> and <DTE_by_DCE>
cannot be set to 2).
• On the AUX UART interface, the default and factory-programmed value for <DCE_by_DTE> and <DTE_
by_DCE> is 0.

15.8 Set flow control \Q\Q
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-60S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280

UBX-13002752 - R67

15 V24 control and V25ter

Page 317 of 1001

u-blox cellular modules - AT commands manual\Q

Attributes

MPCI-L200-02S MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L210-60S
MPCI-L210-63S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

15.8.1 Description
Controls the operation of the local flow control between DTE and DCE. It is used when the data are sent or
received.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The SW flow control (XON/XOFF) activation is only allowed in case of the text transmission:
the binary data cannot be transmitted because it may contain the special flow control characters (XON/
XOFF).
For the SW flow control enhancement, allowing its usage during a PSD call with PPP L2 protocol, see
the SW flow control enhancement for PSD data transfer with PPP L2 protocol in the AT&K commanddescription.
When the software flow control (XON/XOFF) is used, the DC1 (XON, 0x11) and DC3 (XOFF, 0x13) characters arereserved and therefore filtered (e.g. in SMS text mode these two characters can not be input).
Since the DTE-DCE communication relies on the correct reception of DC1/DC3 characters, the UART powersaving should be disabled on the module when SW flow control is used. If the UART power saving is active, theDC1/DC3 characters could be used to wake up the module's UART, and therefore lost. In case a DC3 character(XOFF) is correctly received by module's UART and some data is waiting to be transmitted, the module is forced
to stay awake until a subsequent DC1 character (XON) is received.
The software flow control (XON/XOFF) setting is not allowed on the USB interfaces, on the SPI interface
and on a multiplexer channel. See the Multiple AT command interfaces for all the behavior differences inrespect to the supported interfaces.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
On the UART interface, in case of +UPSV: 2, only \Q0 (no flow control) is allowed.

15.8.2 Syntax
Type
Set

SyntaxAT\Q[<value>]Response
OK

ExampleAT\Q3
OK

15.8.3 Defined values
Parameter<value>Type
NumberDescription•••

0: no flow control
1: DC1/DC3 on circuit 103 and 104 (XON/XOFF)
3 (default value): DCE_by_DTE on circuit 105 (RTS) and DTE_by_DCE on circuit 10
6 (CTS)15.8.4 Notes
TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280• On the UART interface, in case of +UPSV=1, the SW flow control shall not be set (<value> shall not be
set to 1).
• On the UART interface, in case of +UPSV=2, the SW flow control is also supported (<value> can be set to1), but HW flow control is still forbidden (<value> cannot be set to 3).
TOBY-L201 / TOBY-L210-60S• The SW flow control is not supported (<value> cannot be set to 1).

UBX-13002752 - R67

15 V24 control and V25ter

Page 318 of 1001

u-blox cellular modules - AT commands manual

TOBY-L200-00S / TOBY-L210-00S / MPCI-L2• The command has no effect.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the HW flow control is not supported (<value> cannot be set to 3).
• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the default value for <value> is 0.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• On the AUX UART interface, the HW flow control is not supported (<value> cannot be set to 3).
• On the AUX UART interface, the default value for <value> is 0.
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, the HW flow control is not supported (<value> cannot be set to 3).
• On the AUX UART interface, the default value for <value> is 0.

15.9 UART data rate configuration +IPR
+IPR
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.9.1 Description
Specifies the data rate at which the DCE accepts commands on the UART interface. The full range of data
rates depends on HW or other criteria.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 / LEON-G1
When supported, the autobauding feature allows baud rate recognition by the DCE when it operates incommand mode.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
The command settings are ignored when the AT command interface runs either on the USB or on the SPI
interface. The DCE sends the "OK" final result code but the command will have no effect.

15.9.2 Syntax
Type
Set

SyntaxAT+IPR=[<rate>]

Response
OK

ExampleAT+IPR=9600

Read

AT+IPR?

+IPR: <rate>

OK+IPR: 9600

Test

AT+IPR=?

OK
OK+IPR: (list of supported+IPR: (0,2400,4800,9600,19200,
autodetectable <rate> values)[,(list 38400,57600,115200),()of fixed only <rate> values)]
OKOK

15.9.3 Defined values
Parameter<rate>

UBX-13002752 - R67

Type
NumberDescription
Allowed baud rates expressed in b/s (0, if present, means autobauding):• TOBY-L2 / MPCI-L2 - 0 (factory-programmed value), 9600, 19200, 38400, 57600,
115200 (default value), 230400, 460800, 921600• LARA-R2 / TOBY-R2 - 0 (factory-programmed value), 9600, 19200, 38400, 57600, 115200 (default value), 230400, 460800, 921600, 3000000, 3250000, 6000000,
6500000

15 V24 control and V25ter

Page 319 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• SARA-U2 / LISA-U2 - 0 (factory-programmed value), 1200, 2400, 4800, 9600, 1920
0, 38400, 57600, 115200 (default value), 230400, 460800, 921600• LISA-U200-00S / LISA-U1 - 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200(default and factory-programmed value), 230400, 460800, 921600• SARA-G4 / SARA-G3 / LEON-G1 - 0 (default and factory-programmed value), 2400
, 4800, 9600, 19200, 38400, 57600, 115200

15.9.4 Notes•

On the UART AT interface, after the reception of the "OK" result code for the +IPR command, the DTE
shall wait for at least 100 ms before issuing a new AT command; this is to guarantee a proper baud rate
reconfiguration.

TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S• The command has no effect.
LISA-U200-00S / LISA-U1• <rate>= 921600 cannot be set as fixed rate.
SARA-G450-01C / SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S /SARA-G350-02X• On the AUX UART interface, the automatic baud rate detection is not implemented (<rate>=0 is notsupported).
• On the AUX UART interface, the factory-programmed value for <rate> is 115200.

15.9.5 Autobauding description
TOBY-L2 / MPCI-L2
Only one shot automatic baud rate detection is implemented. If enabled, the module provides autobauding
capability only at module start-up, and keeps it active until a first recognition is completed. Later on, it works
at the fixed baud rate (the detected one).
• If automatic baud rate detection is set in the active memory profile, the baud rate is detected once at themodule power on.
• Since autobauding is implemented as "one shot" autobauding, any setting of AT+IPR=0 should be avoided;
the only exception is in case the autobauding setting has been replaced by a fixed rate setting in the stored
profile. In this case the module has started without autobauding and the host needs to reactivate it.
• If the module starts with the autobauding active, after the detection, the +IPR read command returns thedetected baud rate, while the +IPR value in the active profile (displayed as result of AT&V) does not change(it continues to be 0, otherwise the +IPR setting should be changed every time an AT command setting ischanged and the profile saved in the NVM via the AT&W command). As a result, the only way to change the+IPR value in the profile is by issuing an +IPR set command (e.g. AT+IPR=115200 sets a fixed rate on the
UART and determines a start-up at a fixed rate of 115200 b/s in case the active profile is saved via AT&W).
• After AT+IPR=0, the run-time configuration of the AT interface is updated (AT&V shows the new setting in
the active profile), but the setting is effective only at the next start-up (if and only if the active configuration
is saved in the stored AT profile).
• As a consequence of the previous point, if AT+IPR=0 is issued the +IPR read command continues to returnthe current set baud rate (and not the 0 value). This is an exception and it creates a discrepancy between
the value in the profile and the value returned by the +IPR read command, but it allows autobauding
re-activation and a coherent result of the +IPR read command.
• Autobauding values which can be detected are 9600, 19200, 38400, 57600, 115200, 230400, 460800,
921600 b/s. This range is the same of fixed rates baud rates. AT commands provided with a baud rate otherthan values declared, cannot be properly acquired and recognized by the module, and are discarded.
• If the system starts in autobauding (i.e. the +IPR is 0) the first "a" or "A" character provided to themodule detects the baud rate. For example the first command sent from the DTE at any rate can be: AT+CPIN="1234".
Characters different than "a" or "A" are ignored (even if they could be used for the detection), the detection
is considered failed, and it is retriggered. In this situation, all the data received before autobauding
retriggering is flushed (that is, completely ignored). Every two characters' string starting with 'A' or 'a' canbe used for the baud rate detection. But this is not a requirement violation, since it makes sense assumingthat a DTE application starts every communication with an "AT" or "at".

UBX-13002752 - R67

15 V24 control and V25ter

Page 320 of 1001

u-blox cellular modules - AT commands manual••o The echo is produced or not according to ATE configuration. The echo is only produced for a valid
detection sequence.
o The module generates a response for the DTE once the autobauding detection is successful, thecommand has been accepted and the command response is available. Therefore, even if the detection
was actually successful a certain amount of time before, it is only possible to assume that the detection
phase was successful after a response.
o If no response is received by the DTE after some time, it must retry (the timeout value should be
adjustable inside the DTE application). In any case it is suggested to use a very simple command as thefirst command, for which the execution time is short and almost constant (e.g. ATE).
If automatic baud rate detection is active, greeting text or URCs before baud rate detection are not sent but
buffered. They are sent as first data at the detected baud rate as soon as detection is completed (before
any echo of the command or response). The greeting text is sent at the specified baud rate only when thebaud rate setting in the profile is other than autobauding.
<rate>=0 does not affect the AT+ICF command (character framing configuration), since the automatic
frame recognition is not supported.

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
Only one shot automatic baud rate detection is implemented. If enabled, the module provides autobauding
capability only at module start-up, and keeps it active until a first recognition is completed. Later on, it works
at the fixed baud rate (the detected one).
• If automatic baud rate detection is set in the active memory profile, the baud rate is detected once at themodule power on• Since autobauding is implemented as "one shot" autobauding, any setting of AT+IPR=0 should be avoided;
the only exception is in case the autobauding setting has been replaced by a fixed rate setting in the stored
profile. In this case the module has started without autobauding and the host needs to reactivate it• If the module starts with the autobauding active, after the detection, the +IPR read command returns thedetected baud rate, while the +IPR value in the active profile (displayed as result of AT&V) does not change(it continues to be 0, otherwise the +IPR setting should be changed every time an AT command setting ischanged and the profile saved in the NVM via the AT&W command). As a result, the only way to change the+IPR value in the profile is by issuing an +IPR set command (e.g. AT+IPR=115200 sets a fixed rate on the
UART and determines a start-up at a fixed rate of 115200 b/s in case the active profile is saved via AT&W)• After AT+IPR=0, the run-time configuration of the AT interface is updated (AT&V shows the new setting in
the active profile), but the setting is effective only at the next start-up (if and only if the active configuration
is saved in the stored AT profile)• As a consequence of the previous point, if AT+IPR=0 the +IPR read command continues to return thecurrent set baud rate (and not the 0 value). This is an exception and it creates a discrepancy between
the value in the profile and the value returned by the +IPR read command, but it allows autobauding
re-activation and a coherent result of the +IPR read command• Autobauding values which can be detected are:o LARA-R2 / TOBY-R2 series - 9600, 19200, 38400, 57600, 115200, 230400 b/s
o SARA-U2 / LISA-U2 / LISA-U1 series - 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400 b/s
This means that baud rate 460800 and 921600 b/s cannot be automatically detected by DCE and must only
be set as a fixed rate (via +IPR AT command). AT commands provided with a baud rate other than values
declared, cannot be properly acquired and recognized by the module, and are discarded• If the system starts in autobauding (i.e. the <rate> parameter of +IPR is 0) the first "at" sequence provided
to the module detects the baud rate. For example the first command sent from the DTE at any rate canbe: AT+CPIN="1234"
Characters different than "AT" are ignored during the baud rate detection since the hardware detection
sequence is triggered on the "at" or "AT" sequence. "At" or "aT" sequences are invalid: both detection
characters must be small or capital:o The echo is produced or not according to ATE configuration. The echo is only produced for a valid
detection string and only after the detection completion, that is there will be a one character delay
between the received characters and the echo generation (the echo will start only after "at" or "AT"reception)o The echo is always "AT" regardless of the detection string sent by DTEo The module generates a response for the DTE once autobauding detection is successful, the commandhas been accepted and the command response is available. Therefore, even if the detection was actually

UBX-13002752 - R67

15 V24 control and V25ter

Page 321 of 1001

u-blox cellular modules - AT commands manual

•
•

•

•

successful a certain amount of time before, it is only possible to assume that the detection phase was
successful after a responseo If no response is received by the DTE after some time, it must retry (the timeout value should be
adjustable inside the DTE application). In any case it is suggested to use a very simple command as thefirst command, for which the execution time is short and almost constant (e.g. ATE)
If the UART power saving is enabled, the command for the baud rate detection should be sent to the DTE
before the module enters idle mode for the first time
Autobauding result can be unpredictable with spurious characters if power saving is entered and the flow
control is disabled. If the hardware flow control is present, the DTE can be synchronized with the powersaving cycle through the module CTS line i.e. the delivery of the "AT" sequence during the module wake up
can be granted by the DTE and power saving can be exited correctly. Disable the power saving if no hardware
flow control is set at start up
If automatic baud rate detection is active, greeting text or URCs before baud rate detection are not sent but
buffered. They are sent as first data at the detected baud rate as soon as detection is completed (before
any echo of the command or response). The greeting text is sent at the specified baud rate only when thebaud rate setting in the profile is other than autobauding<rate>=0 affects the AT+ICF command (character framing configuration). See the AT+ICF commanddescription for further limitations.

SARA-G3 / LEON-G1
The following notes related to autobauding must be reminded:• At the module power on the autobauding can be by default enabled (necessary to program the stored AT
profile with the baud rate parameter set to 0) or set with the AT+IPR=0 command if the DCE started witha fixed rate
• Autobauding values which can be discovered are the same of the fixing case i.e. 2400, 4800, 9600, 19200,
38400, 57600, 115200 b/s. AT commands provided with a baud rate other than values declared, cannot beproperly acquired and recognized by the module, and are discarded• If the system starts in autobauding (i.e. the <rate> parameter of +IPR is 0) the first "at" sequence provided
to the module detects the baud rate. For example the first command sent from the DTE at any rate canbe: AT+CPIN="1234"• Characters different than AT are ignored during the baud rate detection since the hardware detection
sequence is triggered on the "at" or "AT" sequence. "At" or "aT" sequences are invalid too, both of thedetection characters must be small or capital• Power saving is exited at the 'A' (or 'a') character of the autobauding sequence; power save state isre-entered again when the power saving timeout is elapsed, regardless if the baud detection is complete ornot. The 'T' (or 't') character does not reset the power saving timer; as a result if the detection completion
character is sent outside power save condition, it does not force to stay out of power saving state for thenumber of frames of power saving timer• Autobauding result can be unpredictable with spurious characters if the power saving is entered and theflow control is disabled (AT&K0). If the hardware flow control is present, the DTE can be synchronized withthe power saving cycle through the module CTS line i.e. the delivery of the "AT" sequence during the moduleawake can be granted by the DTE and the power saving can be exited in the proper way. It is recommended
to disable the power saving if no hardware flow control is used
• <rate>=0 affects the AT+ICF command (character framing configuration) too which <format> and <parity>
parameters are automatically switched to the 0 value. See the AT+ICF command description for further
limitations• When autobauding and echo are enabled (+IPR: 0, ATE1), there is an hardware loopback between UARTTXD and RXD lines until a "AT" (or "at") sequence detection. This means that all the characters before andincluding the "AT" (or "at") sequence will be retransmitted on the RXD line also if hardware flow control isenabled and the RTS line is OFF.
SARA-G4
The following notes related to autobauding must be reminded:• At the module power on the autobauding can be by default enabled (necessary to program the stored AT
profile with the baud rate parameter set to 0) or set with the AT+IPR=0 command if the DCE started witha fixed rate
• Autobauding values which can be discovered are the same of the fixing case i.e. 2400, 4800, 9600, 19200,
38400, 57600, 115200 b/s. AT commands provided with a baud rate other than values declared, cannot beproperly acquired and recognized by the module, and are discarded

UBX-13002752 - R67

15 V24 control and V25ter

Page 322 of 1001

u-blox cellular modules - AT commands manual••

In order to synchronyze the UART interface, issue the first AT command with the "AT" string in uppercase
Characters different than AT are ignored during the baud rate detection since the hardware detection
sequence is triggered on the "AT" sequence. "At" or "aT" sequences are invalid too, both of the detection
characters must be capital
Autobauding result can be unpredictable with spurious characters if the power saving is entered and theflow control is disabled (AT&K0). If the hardware flow control is present, the DTE can be synchronized withthe power saving cycle through the module CTS line i.e. the delivery of the "AT" sequence during the moduleawake can be granted by the DTE and the power saving can be exited in the proper way. It is recommended
to disable the power saving if no hardware flow control is used
The UART autobauding does not work when "wake-up via data reception" feature is enabled; if +IPR: 0,
when issuing AT+UPSV=1 or AT+UPSV=2 the module starts working at a fixed baud rate of 115'200 bit/s,
regardless of the baud rate previously recognized. So, if the desired baud rate is different from 115'200 bit/s, set the baud rate by means of +IPR AT command before setting +UPSV.

••

15.10 Return to on-line data state OO
Modules

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Attributes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

15.10.1 Description
Causes the DCE to return to online data state and issue a CONNECT intermediate result code on DTE.
ATO command is used to resume both circuit-switched and packet-switched data call. The resume is only
possible if the PPP L2 protocol is used.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
It is the complementary command to the escape sequence, or to the other actions (DTR ON to OFF
transition, see table in Circuit 108/2, +++ behavior for the different &D: summarizing tables) that cause
the DCE to switch from online data state to online command state.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
Depending on ATX command setting the CONNECT IRC can be properly configured in order to provide also
the data rate (CONNECT <text>).

15.10.2 Syntax
Type
ActionSyntaxATO

Response<response>

ExampleATO
CONNECT

15.10.3 Defined values
Parameter<response>

Type
StringDescription••

CONNECTNO CARRIER: the online data state cannot be resumed

15.10.4 Notes••

The command provides an error result code ("+CME ERROR: operation not allowed" if +CMEE is set to 2)
in the following cases:
o The DCE is not in online command stateo It is issued on a DCE different from the one in online command state
In case of PSD call, any data from the network (downlink data) received by the DCE during the on-line
command state is discarded. This means that after the O command and on-line data state resume, any
possible data loss has to be recovered by upper layer protocols (e.g. TCP).

UBX-13002752 - R67

15 V24 control and V25ter

Page 323 of 1001

u-blox cellular modules - AT commands manual

TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S• The command has not effect since the online command mode is not supported.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the command is not supported.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-G450-01C / SARA-G340-02S /SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, the command is not supported.

15.11 Escape character S2
S2Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.11.1 Description
Controls the decimal value of the ASCII character used as the escape character. A value greater than 127
disables the escape process, i.e. no escape character will be recognized. The escape sequence contains threeescape characters e.g. "+++".

15.11.2 Syntax
Type
Set

SyntaxATS2=<value>

Response
OK

ExampleATS2=43

Read

ATS2?

<value>

OK
043

OK

OK

15.11.3 Defined values
Parameter<value>Type
NumberDescription
Range 1 to 255. The answer to the read command is in "xxx" format. The default andthe factory-programmed value is 43 (ASCII '+').

15.11.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The following table shows how the ATS2 command works for different data call scenarios.
Data call command
AT+CGDATA="M-HEX",1L2 protocol
HEX

Description
u-blox specific

AT+CGDATA="M-RAW_IP",1 RAW-IP

PSD call: Transfer IP packet directly

AT+CGDATA="PPP",1PSD call: Same of ATD*99***1# (e.g. dialup)

PPP

ATS2 behavior
Escape sequence
detection is only done for+++ (plus carriage return).
ATS2 is not effective. No
timing constraints.
Break detection is notsupported
Escape sequence
detection is only done for ~+++. ATS2 is not effective.
There is not a timing
constraint (see the S12 AT
command) for ~+++ (+++ is incapsulated in a PPP
frame)

UBX-13002752 - R67

15 V24 control and V25ter

Page 324 of 1001

u-blox cellular modules - AT commands manual

Data call command
ATD1234

L2 protocol

Description
CSD call

AT+USODL=0AT+USOWR=0,3

PSD call: Direct Link mode
PSD call: AT socket (not transparent)

ATS2 behavior
The command is effective
if issued in both commandand online command mode
(where applicable)
The command is effective
Break detection is notsupported

Table 23: ATS2 handling for different data call scenarios
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.
TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S• The command has no effect.

15.12 Command line termination character S3S3Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.12.1 Description
Sets a value representing the decimal IRA5 value of the character recognized by the DCE from the DTE,
to terminate the incoming command line. It is also generated by the DCE as part of the header, trailer andterminator for result codes and information text, along with the S4 setting.

15.12.2 Syntax
Type
Set

SyntaxATS3=<value>

Response
OK

ExampleATS3=13

Read

ATS3?

<value>

OK
013

OK

OK

15.12.3 Defined values
Parameter<value>Type
NumberDescription
Range 0 to 127. The answer to the read command is in "xxx" format. The default andthe factory-programmed value is 13 (ASCII carriage return (CR, IRA5 0/13)).

15.12.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.

UBX-13002752 - R67

15 V24 control and V25ter

Page 325 of 1001

u-blox cellular modules - AT commands manual

15.13 Response formatting character S4S4Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.13.1 Description
Sets a value representing the decimal IRA5 value of the character generated by the DCE as part of the header,
trailer and terminator for result codes and information text, along with the S3 setting.

15.13.2 Syntax
Type
Set

SyntaxATS4=<value>

Response
OK

ExampleATS4=10

Read

ATS4?

<value>

OK
010

OK

OK

15.13.3 Defined values
Parameter<value>Type
NumberDescription
Range 0 to 127. The answer to the read command is in "xxx" format. The default andthe factory-programmed value is 10 (line feed (LF, IRA5 0/10)).

15.13.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.

15.14 Command line editing character S5
S5Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.14.1 Description
Sets a value representing the decimal IRA5 character recognized by the DCE as a request to delete from thecommand line the immediately preceding character.

15.14.2 Syntax
Type
Set

SyntaxATS5=<value>

Response
OK

ExampleATS5=8

Read

ATS5?

<value>

OK
008

OK

OK

UBX-13002752 - R67

15 V24 control and V25ter

Page 326 of 1001

u-blox cellular modules - AT commands manual

15.14.3 Defined values
Parameter<value>Type
NumberDescription
Range 0 to 127. The answer to the read command is in "xxx" format. The default andthe factory-programmed value is 8 (ASCII backspace (BS, IRA5 0/8)).

15.14.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.

15.15 Pause before blind dialling S6
S6Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

15.15.1 Description
Specifies the time in seconds that the DCE waits between connecting to the line and dialling, when the dial
tone is not implemented or enabled. The command is not applicable for signal based mobile phone software.

15.15.2 Syntax
Type
Set

SyntaxATS6=<value>

Response
OK

ExampleATS6=2

Read

ATS6?

<value>

OK
002

OK

OK

15.15.3 Defined values
Parameter<value>Type
NumberDescription
Range 2 - 10. The answer to the read command is in "xxx" format. The default value is
2 s.

15.15.4 Notes
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.

UBX-13002752 - R67

15 V24 control and V25ter

Page 327 of 1001

u-blox cellular modules - AT commands manual

15.16 Connection completion timeout S7
S7
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.16.1 Description
Specifies the time in seconds, that the DCE shall allow between either answering a call or completion of diallingand establishment of a connection with a remote site.

15.16.2 Syntax
Type
Set

SyntaxATS7=<value>

Response
OK

ExampleATS7=30

Read

ATS7?

<value>

OK
060

OK

OK

15.16.3 Defined values
Parameter<value>Type
NumberDescription
Range 1 - 255. The answer to the read command is in "xxx" format.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1 - The default and the factory-programmed value is
60 s

15.16.4 Notes
LARA-R2 / TOBY-R2• In case of a VoLTE call the connection completion timer does not start and these values will be applied:o VoLTE MT call: 50 s
o VoLTE MO call: 185 s• In case of alerting-SRVCC the connection completion timer starts accordingly the AT command setting.
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.

15.17 Command dial modifier time S8
S8Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

15.17.1 Description
Specifies the amount of time, in seconds, that the DCE shall pause during dialling, when a ',' (comma) dial
modifier is encountered in a dial string.
The command has no effect.

UBX-13002752 - R67

15 V24 control and V25ter

Page 328 of 1001

u-blox cellular modules - AT commands manual

15.17.2 Syntax
Type
Set

SyntaxATS8=<value>

Response
OK

ExampleATS8=4

Read

ATS8?

<value>

OK
002

OK

OK

15.17.3 Defined values
Parameter<value>Type
NumberDescription
Range 0 - 255. The answer to the read command is in "xxx" format. The default valueis 2.

15.17.4 Notes
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.

15.18 Automatic disconnect delay S10
S10Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

15.18.1 Description
Specifies the time in tenth of a second, that the DCE will remain connected to the line after the DCE has
indicated the absence of received line signal. Not supported for GSM but the OK response is returned.

15.18.2 Syntax
Type
Set

Syntax
ATS10=<value>

Response
OK

ExampleATS10=30

Read

ATS10?

<value>

OK
030

OK

OK

15.18.3 Defined values
Parameter<value>Type
NumberDescription
Range 1 - 254. Default: 1

15.18.4 Notes
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.

UBX-13002752 - R67

15 V24 control and V25ter

Page 329 of 1001

u-blox cellular modules - AT commands manual

15.19 Escape prompt delay (EPD) S12
S12Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

15.19.1 Description
Defines the maximum period, in fiftieths of a second, allowed between the reception of the last character ofthe sequence of three escape characters from the DTE and the sending of the OK result code to the DTE. If any
characters are detected during this time, the OK will not be sent.
Furthermore, the timeout is:•••

The minimum period, before the first character reception of the three escape character sequence, during
which no other character must be detected to accept it as a valid first character
The maximum period allowed between receipt of first, or second, character of the three escape character
sequence and receipt of the next
The minimum period, after the last character reception of the three escape character sequence, during
which no other character must be detected to accept the escape sequence as a valid one

15.19.2 Syntax
Type
Set

Syntax
ATS12=<value>

Response
OK

ExampleATS12=80

Read

ATS12?

<value>

OK
050

OK

OK

15.19.3 Defined values
Parameter<value>Type
NumberDescription
Range 0 - 255. The answer to the read command is in "xxx" format. The default value
is 50 (1 s)

15.19.4 Notes
SARA-G4 / SARA-G3 / LEON-G1• The <value> parameter is not mandatory.
TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S• The command has no effect.

15.20 Command echo E
E
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.20.1 Description
Controls whether or not the MT echoes characters received from the DTE during command state.

UBX-13002752 - R67

15 V24 control and V25ter

Page 330 of 1001

u-blox cellular modules - AT commands manual

15.20.2 Syntax
Type
Set

SyntaxATE[<value>]Response
OK

ExampleATE1
OK

15.20.3 Defined values
Parameter<value>Type
NumberDescription••

0: echo off
1 (default and the factory-programmed value): echo on

15.21 Result code suppression Q
Q
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.21.1 Description
Determines if DCE transmits result codes to the DTE or not. When result codes are being suppressed,
no portion of any intermediate, final or URC is transmitted. Information text transmitted in response tocommands is not affected by this setting.

15.21.2 Syntax
Type
Set

SyntaxATQ[<value>]Response
OK

ExampleATQ1
OK

15.21.3 Defined values
Parameter<value>Type
NumberDescription••

0 (default and the factory-programmed value): DCE transmits result codes
1: Result codes are suppressed and not transmitted

15.22 DCE response format V
V
Modules
Attributes

All products
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.22.1 Description
Control the contents of the header and trailer transmitted with result codes and information text responses.
It also determines whether the result code is transmitted in a numeric form or an alphabetic (or verbose) form.
The information text response is not affected by this setting. See Information text responses and result codesfor description of the result code formats.

15.22.2 Syntax
Type
Set

SyntaxATV[<value>]Response
OK

ExampleATV1
OK

UBX-13002752 - R67

15 V24 control and V25ter

Page 331 of 1001

u-blox cellular modules - AT commands manual

15.22.3 Defined values
Parameter<value>Type
NumberDescription••

0: DCE transmits limited headers, trailers and numeric text
1 (default and the factory-programmed value): DCE transmits full headers, trailers
and verbose response text

15.23 Result code selection and call progress monitoring
control X
X
Modules

Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
ProfileNo

Response time-Error reference+CME Error

15.23.1 Description
In a CS data call, determines how the DCE transmits to the DTE the CONNECT result code.

15.23.2 Syntax
Type
Set

Syntax
ATX[<value>]Response
OK

ExampleATX1
OK

15.23.3 Defined values
Parameter<value>Type
Number<speed>NumberDescription••

0: CONNECT result code is given upon entering online data state;
1-4: CONNECT <speed> result code is given upon entering online data state; (4 isthe default and the factory-programmed value)
Transfer speed for CSD calls configured via the CBST command

15.23.4 Notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.

15.24 Reset to default configuration Z
Z
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A TOBY-L2
MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

15.24.1 Description
Resets the DCE configuration into a known state; the reset includes the loading of the settings stored in the
profile identified by the <value> parameter, into the current profile, and the application of the settings.
When the command is issued, any CSD call in progress is released. In case of success, the result code is issued
using the format configuration (Q, V, S3, S4 commands) loaded from the requested profile. The other DCE
settings are applied after the result code has been sent.

UBX-13002752 - R67

15 V24 control and V25ter

Page 332 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
For more details on the settings stored in the profiles, see the Appendix
B.1.

15.24.2 Syntax
Type
ActionSyntaxATZ[<value>]Response
OK

Example15.24.3 Defined values
Parameter<value>Type
NumberDescription
Profile index, optional parameter. Allowed values:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1 - 0 (default value), 1

15.24.4 Notes
TOBY-L4• The command has not effect.

15.25 Set to factory defined configuration &F&F
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

15.25.1 Description
Resets the current profile to factory-programmed setting. Other NVM settings, not included in the profiles,
are not affected.
In case of success, the response is issued using the configuration of the result codes format (Q, V, S3, S4
AT commands) loaded from the factory-programmed profile. The other DCE settings are applied after the
response has been sent.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
For more details on the settings stored in the profiles, see the Parameters stored in profiles.

15.25.2 Syntax
Type
ActionSyntaxAT&F[<value>]Response
OK

Example15.25.3 Defined values
Parameter<value>Type
NumberDescription
Only 0 allowed

15.25.4 Notes
LARA-R204• The command also resets the Class 1 and Class 4 APN profiles to their factory-programmed values. See+VZWAPNE AT command.

UBX-13002752 - R67

15 V24 control and V25ter

Page 333 of 1001

u-blox cellular modules - AT commands manual

15.26 Store current configuration &W&W
Modules

Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

15.26.1 Description
Stores into one of the two RAM profile mirrors the current AT configuration of the DCE interface in which thecommand is issued. The profile is selected according to the AT command parameter value. For more details on
the AT command configuration saved in the profiles, refer to Appendix B.1.
The profile is updated with the RAM mirror only when the module is switched off using the +CPWROFF AT
command.

15.26.2 Syntax
Type
ActionSyntaxAT&W[<value>]Response
OK

Example15.26.3 Defined values
Parameter<value>Type
NumberDescription••

0 (default value): selects profile 0
1: selects profile 1

15.26.4 Notes
TOBY-L4• Only default profile 0 is supported, and only +COPS and S0 settings are stored to it.

15.27 Display current configuration &V&V
Modules

Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

15.27.1 Description
Reports a summary of the current configuration and of the stored user profiles.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Since not all configuration items are listed with this command, see the example below for the list of thedisplayed configuration items. Appendix
B.1 provides the complete list of the configuration items stored in the profiles.
TOBY-L4 / TOBY-L2 / LARA-R202 / LARA-R203 / LARA-R211 / LARA-R280 / TOBY-R2 / SARA-U2 /LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-04B / LISA-U200-52S / LISA-U200-62S /LISA-U200-83S / LISA-U201 / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U120 / LISA-U130 / SARA-G340 /SARA-G350 / LEON-G1
The command does not display audio parameters. Audio parameters can be displayed by thecorresponding read command (i.e. AT+UMGC?).

UBX-13002752 - R67

15 V24 control and V25ter

Page 334 of 1001

u-blox cellular modules - AT commands manual

15.27.2 Syntax
Type
ActionSyntaxAT&V

Response
ACTIVE PROFILE:

ExampleACTIVE PROFILE: &C1, &D1, &S1,
&K3, E1, Q0, V1, X4, S00:000, S0
List of commands stored in the
2:043, S03:013, S04:010, S05:00
active profile with the related values
8, S07:060, +CBST:007, 000, 001,
STORED PROFILE 0:+CRLP:061, 061, 048, 006, +CR:0
00, +CRC:000, +IPR:0, +COPS:0,0,
List of commands stored in the
FFFFF, +ICF:3,1, +UPSV: 0, +CMGF:0
profile 0 with the related values, +CNMI:1,0,0,0,0, +USTS: 0
STORED PROFILE 1:
STORED PROFILE 0: &C1, &D1, &S1,
List of commands stored in the&K3, E1, Q0, V1, X4, S00:000, S0
profile 1 with the related values
2:043, S03:013, S04:010, S05:00
8, S07:060, +CBST:007, 000, 001,
OK
+CRLP:061, 061, 048, 006, +CR:0
00, +CRC:000, +IPR:0, +COPS:0,0,
FFFFF, +ICF:3,1, +UPSV: 0, +CMGF:0, +CNMI:1,0,0,0,0, +USTS: 0
STORED PROFILE 1: &C1, &D1, &S1,
&K3, E1, Q0, V1, X4, S00:000, S0
2:043, S03:013, S04:010, S05:00
8, S07:060, +CBST:007, 000, 001,
+CRLP:061, 061, 048, 006, +CR:0
00, +CRC:000, +IPR:0, +COPS:0,0,
FFFFF, +ICF:3,1, +UPSV: 0, +CMGF:0, +CNMI:1,0,0,0,0, +USTS: 0
OK

15.27.3 Notes
TOBY-L4• The command shows the active profile and the single STORED PROFILE 0.
TOBY-L2 / MPCI-L2• The command shows the stored profiles that were used at boot. The RAM profile mirrors updated with
AT&W cannot be retrieved with this command.
• The current setting and the values stored in user profiles of +UPSV AT command are not present in theinformation text response.

15.28 Designate a default reset profile &Y&Y
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

15.28.1 Description
Selects which profile will be loaded at the next power on. The AT commands configuration from theloaded profile will be separately applied to each attached interface. At run time each interface will own theconfiguration as described in Appendix B.1. An error is returned if <value> is greater then 2, or NVM is notinstalled or is not operational.
For more details on the commands stored in the profiles, refer to Appendix B.1.

15.28.2 Syntax
Type
ActionSyntaxAT&Y[<value>]

UBX-13002752 - R67

ResponseOK

15 V24 control and V25ter

ExamplePage 335 of 1001

u-blox cellular modules - AT commands manual

15.28.3 Defined values
Parameter<value>Type
NumberDescription•••

0 (default value and factory-programmed value): selects profile 0
1: selects profile 1
2: selects the factory-programmed settings

15.29 Parity bit transmission over the air +UTPB+UTPBModules

Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SARA-G3
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
fullNoProfileNo+CME Error

15.29.1 Description
Configures the parity bit transmission over the air, for the data received from the DTE during a data call, when
the UART interface is programmed for 7-bit data format.
The parity bit transmission can only work if the 7 bit data, 1 parity bit, 1 stop bit character framing is set(and thus applies only to UART AT interfaces; see the +ICF command description).
The +UTPB command, like the +ICF command, is only effective on UART AT interface. On USB/SPI/MUX
AT interfaces the set command always returns the "OK" final result code and the read command always
returns 0. Furthermore, the command setting on USB/SPI/MUX AT interfaces has no effect on the UART
AT interface and on the AT profiles.
On AUX UART AT interface, the set command always returns the "OK" final result code and the readcommand always returns 0. Furthermore, the command setting on the AUX UART AT interface has noeffect on the UART AT interface and on the AT profiles.
The transmission of the parity bit only applies to Circuit Switched data calls or Socket Direct Link; in all
the other cases (e.g. PSD dial-up, file write in module FS, any other direct data transmission modes), theparity information is always filtered out.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
The transmission of the parity bit is furtherly restricted to only Circuit Switched data calls (no Socket
Direct Link).
The 7-bit UART configuration has not to be set if the MUX protocol over UART must be activated. Enabling
the parity bit transmission during MUX mode does not influence the data transfer, since the assumption
is that 7-bit format (7O1, 7E1) is not active. The module does not check if incompatible settings arerequested.

15.29.2 Syntax
Type
Set

SyntaxAT+UTPB=<n>

Response
OK

ExampleAT+UTPB=1

Read

AT+UTPB?

+UTPB: <n>

OK+UTPB: 1

Test

AT+UTPB=?

OK+UTPB: (list of supported <n>'s)

OK+UTPB: (0-1)

OKOK

15.29.3 Defined values
Parameter<n>

UBX-13002752 - R67

Type
NumberDescription•

0 (factory-programmed value): the parity bit is not transmitted over the air (MSBof the transmitted byte is always 0)

15 V24 control and V25ter

Page 336 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 1: the DCE transmits the parity bit over the air (MSB of the transmitted byte is left
untouched)15.29.4 Notes
•

•
•

•

It is possible to enable the transmission of the parity bit even if the frame format on the UART interface
is not 7 bit data, 1 parity bit; in such a case the configuration is only applied after the 7-bit format is set
on UART (via automatic recognition or +ICF command).
When the DCE's UART detects a parity error in the received data (received parity bit is different from thecalculated one) no specific action is taken, i.e. the data are always transmitted over the air.
When the parity bit over the air is enabled and the UART character format is 7O1, the default escapecharacter "+" (decimal value of ASCII character is 043) has the parity bit set to 1. This prevents DUT
on detecting the escape sequence. The user should change the value of escape character with ATS2
command to a value with parity bit set to 0 (for example character "#", ASCII decimal value 035).
In case of UART 7O1, 7E1 configuration, the data from the network to the DTE must be in the 7-bit format(each byte is binary data in the range 0x00.0x7F); any information carried in the bit at position 7 (bit 0 is
LSB, bit 7 is MSB) is ignored by the module, and in any case not transmitted to the DTE since it is replacedby parity information.

15.29.5 AT+UTPB=0 case diagramDTE

u-blox module

Mark

MSB

LSB
Space
Start
bit

7 data bits

Parity

Stop

bit

bit

One character

1

PARITY

6
MSB

5

4

3

2

1

0
LSB

FILTERING
2

0

3

6
MSB

5

4

3

2

1

0
LSB

NETWORK

Figure 2: AT+UTPB=0 case diagram

UBX-13002752 - R67

15 V24 control and V25ter

Page 337 of 1001

u-blox cellular modules - AT commands manual

15.29.6 AT+UTPB=1 case diagramDTE

u-blox module

Mark
MSB

LSB
Space
Start
bit

7 data bits

Parity
Stop
bit
bit

One character

1

PARITY

6
MSB

5

4

3

2

1

0
LSB

NO FILTERING
2

PARITY

6
MSB

5

4

3

2

1

0
LSB

NO PARITY BITMANIPULATON
3NETWORK

Figure 3: AT+UTPB=1 case diagram

UBX-13002752 - R67

15 V24 control and V25ter

Page 338 of 1001

u-blox cellular modules - AT commands manual

16 SIM management
16.1 Generic SIM access +CSIM+CSIM
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

16.1.1 Description
Allows direct control of the SIM by a distant application on the TE. This command transparently transmits the<command> to the SIM via the MT. The <response> is returned in the same manner to the TE.
The command needs the SIM module to work correctly.
It is recommended to wait some seconds after boot (or reset) before using the command.
TOBY-L2 / MPCI-L2
The PIN insertion is not mandatory before the command execution.

16.1.2 Syntax
Type
Set

SyntaxAT+CSIM=<length>,<command>

Test

AT+CSIM=?

Response+CSIM: <length>,<response>

ExampleAT+CSIM=14,"A0A40000027F20"

OK+CSIM: 4,"6E00"

OK

OK
OK

16.1.3 Defined values
Parameter<length><command>Type
NumberString<response>

StringDescription
Length of the characters sent to the TE in <command> or <response> parameters
Command passed on by MT to SIM in hex format; see the 3GPP TS 51.011 [17] andETSI TS 102 221 [73]Response to the command passed on by the SIM to the MT (3GPP TS 51.011 [17] andETSI TS 102 221 [73])16.2 Restricted SIM access +CRSM+CRSM
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time< 10 sError reference+CME Error

16.2.1 Description
Allows easy access to the SIM database. The set command transmits the SIM command and its required
parameters to the MT. The MT handles internally all SIM-MT interface locking and file selection routines. As
response to the command, the MT sends the actual SIM information parameters and response data. An error
result code may be returned when the command cannot be passed to the SIM, but the failure in the executionof the command in the SIM is reported in <sw1> and <sw2> parameters.
The expected response time shall be increased when using a remote SIM card via SAP and in case ofsimultaneous access to the SIM by another AT interface or by internal clients (e.g. BIP, IMS).
The command needs the SIM module to work correctly.
TOBY-L2 / MPCI-L2
The PIN insertion is not mandatory before the command execution.

UBX-13002752 - R67

16 SIM management

Page 339 of 1001

u-blox cellular modules - AT commands manual

16.2.2 Syntax
Type
Set

Test

SyntaxAT+CRSM=<command>[,<fileid>[,<P1>,<P2>,<P3>[,<data> [,<pathid>]]]]

Response
Example+CRSM: <sw1>,<sw2>[,<response>] AT+CRSM=176,28471,0,0,3

AT+CRSM=?

OK

OK+CRSM: 144,0,"989301770020
594178F2"
OKOK

16.2.3 Defined values
Parameter<command>Type
Number<fileid>

Number<P1>, <P2>, <P3>

Number<data>

String<pathid>

String<sw1>, <sw2>

NumberDescription
Allowed values:• 176: read binary• 178: read record• 192: get response• 214: update binary• 220: update record• 242: status• 203: retrieve data
• 219: set data
Identifies an elementary datafile on SIM. Mandatory for each command except
STATUS (e.g. 28423: meaning IMSI file (6F07)). For a complete description of
Elementary Files (EF), see 3GPP TS 31.102 [18].
Defines the request. These parameters are mandatory for each command, except
GET RESPONSE and STATUS. The values are described in 3GPP TS 51.011 [17] andETSI TS 102 221 [73].
Information which shall be written to the SIM (hexadecimal character format; see the+CSCS - string containing hexadecimal characters)
Contains the path of an elementary file on the SIM/UICC in hexadecimal format as
defined in ETSI TS 102 221 [73] (e.g. "7F205F70" in SIM and UICC case). The <pathid>
shall only be used in the mode "select by path from MF" as defined in ETSI TS 102 221[73].
Contains SIM information about the execution of the actual command and can be(more details in 3GPP TS 51.011 [17] and ETSI TS 102 221 [73]).
Status words examples for 2G SIM cards:• 0x90 0x00: normal ending of the command• 0x9F 0xXX: length XX of the response data
• 0x92 0x0X: command successful but after using an internal retry routine X times• 0x92 0x40: memory problem• 0x94 0x00: no EF selected• 0x94 0x02: out of range (invalid address)• 0x94 0x04: file ID not found; pattern not found• 0x94 0x08: file is inconsistent with the command• 0x98 0x02: no CHV initialized• 0x98 0x04: access condition not fullfiled / unsucc. CHV verify / authent.failed• 0x98 0x08: in contradiction with CHV status• 0x98 0x10: in contradiction with invalidation status• 0x98 0x40: unsucc. CHV-verif. or UNBLOCK CHV-verif. / CHV blocked /UNBL.blocked• 0x67 0xXX: incorrect parameter P3• 0x6A 0x81: function not supported• 0x6A 0x82: file not found• 0x6B 0xXX: incorrect parameter P1 or P2• 0x6D 0xXX: unknown instruction code given in the command• 0x6E 0xXX: wrong instruction class given in the command• 0x6F 0xXX: technical problem with no diagnostic given
Status words examples for 3G SIM cards:• 0x90 0x00: normal ending of the command

UBX-13002752 - R67

16 SIM management

Page 340 of 1001

u-blox cellular modules - AT commands manual

ParameterType<response>

StringDescription• 0x91 0xXX: length XX of the response data
• 0x63 0xCX: command successful but after using an internal retry routine X times• 0x62 0x00: no information given, state of non volatile memory unchanged• 0x64 0x00: no information given, state of non-volatile memory unchanged• 0x65 0x00: no information given, state of non-volatile memory changed• 0x65 0x81: memory problem• 0x67 0x00: wrong length• 0x69 0x85: conditions of use not satisfied• 0x69 0x86: command not allowed (no EF selected)• 0x69 0x82: security status not satisfied• 0x62 0x81: part of returned data may be corrupted• 0x6A 0x81: function not supported• 0x6A 0x82: file not found• 0x6A 0x83: record not found• 0x6B 0x00: wrong parameter(s) P1, P2• 0x6D 0x00: instruction code not supported or invalid• 0x6E 0x00: instruction code not supported or invalid• 0x6F 0x00: technical problem, no precise diagnosis
The response of successful completion of the command previously issued(hexadecimal character format; see the +CSCS). STATUS and GET RESPONSE
return data, which gives information about the current elementary datafield. This
information includes the type of file and its size (see the 3GPP TS 51.011 [17] and the
ETSI TS 102 221 [73]). After READ BINARY or READ RECORD command the requested
data will be returned. <response> is not returned after a successful UPDATE BINARYor UPDATE RECORD command.

16.2.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• <command>=203 and 219 are not supported.

16.3 Read the SIM language +CLAN+CLAN
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

16.3.1 Description
Reads the language from the SIM.
The read syntax will display the most preferred language from the preferred language list in:• TOBY-L4 - the EFELP/EFPL (3F00/2F05) file
• LARA-R2 / TOBY-R2 - the EFLI (3F00/7FFF/6F05) file.
• SARA-U2 / LISA-U2 / LISA-U1 - EFLP (3F00/7F20/6F05) file.

16.3.2 Syntax
Type
Set

SyntaxAT+CLAN=<code>

Response
OK

ExampleAT+CLAN="en"

Read

AT+CLAN?

+CLAN: <code>

OK+CLAN: "en"Test

AT+CLAN=?

OK
OK

UBX-13002752 - R67

16 SIM management

OK

Page 341 of 1001

u-blox cellular modules - AT commands manual

16.3.3 Defined values
Parameter<code>Type
StringDescription
It is a two-letter abbreviation of the language. The language codes, as defined in ISO
639, consists of two characters, e.g. "en", "it" etc16.3.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The set command is not supported.

16.4 Check for UICC card +UUICC+UUICC
Modules

Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

16.4.1 Description
Returns the type of application which is present on the ICC or UICC.

16.4.2 Syntax
Type
Read

SyntaxAT+UUICC?

Response+UUICC: <state>

Example+UUICC: 1

OK

OK

16.4.3 Defined values
Parameter<state>Type
NumberDescription•••

0: 2G SIM (SIM application present)
1: 3G SIM (USIM application present)
2: 4G SIM (USIM and ISIM applications present)

16.4.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• <state>=2 (4G SIM) is not supported.

16.5 Customer service profile +UCSP+UCSPModules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

16.5.1 Description
Reads the customer service profile (CSP) from the SIM. The CSP indicates the services that are user accessible.
The syntax +UCSP (if the <service_group> parameter is not issued) displays all the service groups.
If CSP information is not available on the SIM, the "+CME ERROR: SIM Failure" error result code is returned
when trying to interrogate all or one of the service groups.

UBX-13002752 - R67

16 SIM management

Page 342 of 1001

u-blox cellular modules - AT commands manual

16.5.2 Syntax
Type
Set

SyntaxAT+UCSP[=<service group>]

Response
Example+UCSP: <service_group>,<services> AT+UCSP=6[+UCSP: <service_group>,<services>+UCSP=6,10000000
OK[...]]TestOK+UCSP: (list of supported <service
group>s)AT+UCSP=?

+UCSP: (1-9,c0,d5)
OKOK

16.5.3 Defined values
Parameter<service_group><services>Type
NumberNumberDescription
Service group (1-9, c0, d5)Services of one service group in bit-format beginning with the most significant bit of
the service byte

16.6 SIM hot insertion configuration +UDCONF=50+UDCONF=50
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S
TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
MPCI-L200-02S MPCI-L200-03S MPCI-L201-02S MPCI-L210-02S MPCI-L210-03S MPCI-L220
MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

16.6.1 Description
Configures the SIM hot insertion feature. The feature enables the SIM interface upon detection of external SIM
card physical insertion / removal and behaves accordingly, triggering registration and deregistration.
The +CIEV URC (see +CMER AT command) and +CIND AT command notify the SIM card detection status.
The command setting is saved in NVM and will be effective at the next power on.

16.6.2 Syntax
Type
Set

SyntaxAT+UDCONF=50,<sim_hot_
insertion>

Read

AT+UDCONF=50

Response
OK

ExampleAT+UDCONF=50,1

OK+UDCONF: 50,<sim_hot_insertion> AT+UDCONF=50
OK+UDCONF: 50,1
OK

16.6.3 Defined values
ParameterType<sim_hot_insertion> Number

UBX-13002752 - R67

Description
SIM hot insertion setting. Allowed values:• 0 (factory-programmed value): SIM hot insertion disabled• 1: SIM hot insertion enabled

16 SIM management

Page 343 of 1001

u-blox cellular modules - AT commands manual

16.6.4 Notes
TOBY-L2 / MPCI-L2• If the SIM hot insertion feature is disabled, the +CIEV URC (see +CMER AT command) and +CIND AT
command report the SIM card detection status in relation to the bare level of the SIM detection pin,otherwise they provide the SIM hot insertion status.
• The SIM card detection feature detects the SIM card mechanical / physical presence displayed by means
of +CIEV URC (see +CMER AT command) and +CIND AT command. The +CPIN behaviour depends on thestatus of SIM hot insertion:o If SIM hot insertion is enabled the +CPIN setting is accordingly updatedo If SIM hot insertion is disabled and a SIM is inserted a +CFUN=19 / +CFUN=1 cycle (or a silent resetby means of +CFUN=15) is needed to update the +CPIN setting• SIM card detection and SIM hot insertion interoperability provides an overview between the two features
depending on +UGPIOC and +UDCONF=50 setting:<sim_hot_insertion>-+UGPIOC
Disabled

Disabled

EnabledEnabledEnabledRemarks
SIM card detection is disabled, "simind"
will return always 2 (see +CIND AT
command and +CIEV URC)
SIM cart detection status provided on
GPIO pin configured as SIM card detection+CIEV URC and +CIND AT commandprovide the SIM hot insertion status

Table 24: SIM card detection and SIM hot insertion interoperability
TOBY-L4• The SIM card detection status is based on the SIM state indications, sent by the protocol stack to theapplication layer, rather than on a physical GPIO pin.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• For the correct behavior of the SIM hot insertion feature, the SIM card detection feature (configurable bymeans of the +UGPIOC AT command where supported) must be enabled too.
• The SIM card detection status is notified by means of +CIEV URC (see +CMER AT command) and +CIND
AT command only if <sim_hot_insertion> of +UDCONF=50 AT command is enabled and a GPIO pin is
configured as SIM card detection (see +UGPIOC AT command). If the SIM hot insertion feature is notenabled then the "simind" parameter value of +CIEV URC and +CIND AT command is unpredictable (0,1 or 2).

16.7 UICC application discovery +CUAD+CUAD
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

16.7.1 Description
Asks the MT to discover what applications are available for selection on the UICC. According to ETSI TS 102.221[73], the ME shall access and read the EFDIR file in the UICC and return the values that are stored in its records.
Each record contains the AID and optionally application parameters of one of the applications available on the
UICC.
If the optional parameter(s) are requested and the EFDIR file is not present in the UICC, the <response>parameter shall be empty.

UBX-13002752 - R67

16 SIM management

Page 344 of 1001

u-blox cellular modules - AT commands manual

16.7.2 Syntax
Type
Set

SyntaxAT+CUAD[=<option>]
OK

Response+CUAD: <response>[,<active_
application>[,<AID>]]
OK

Test

AT+CUAD=?

+CUAD: (list of supported<option>s)

ExampleAT+CUAD=1+CUAD: 61124F10A0000000
871002FFFFFFFF89060400
FFFFFFFFFFFFFFFFFFFFFFFFFF9000,2,A000000087100
2FFFFFFFF89060400FF
OK+CUAD: (0,1)
OKOK

16.7.3 Defined values
Parameter<option>Type
Number<response>
String<active_application> Number<AID>

StringDescription• 0 (default value): no parameters requested in addition to <response>• 1: include <active_application>
Content of the EFDIR in hexadecimal format
Active application:• 0: no SIM or USIM active• 1: active application is SIM• 2: active application is USIM, followed by <AID>• 3: active application is ISIM, followed by <AID>
AID of active USIM in hexadecimal format

16.8 Open logical channel +CCHO+CCHOModules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

16.8.1 Description
Causes the MT to return <sessionid> to allow the TE to identify a channel that is being allocated by the currently
selected UICC, which is attached to ME. The currently selected UICC will open a new logical channel, select theapplication identified by the <dfname> received with this command and return a session Id as the response.
The ME shall restrict the communication between the TE and the UICC to this logical channel.
When the maximum number of logical channels have been opened (normally 3, 2 when the IMS client is active),the command provides an error result code.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
The <sessionid> is to be used when sending commands with +CRLA or +CGLA commands.

16.8.2 Syntax
Type
Set

SyntaxAT+CCHO=<dfname>Response+CCHO: <sessionid>
OK

ExampleAT+CCHO="A000000087100
4FF49FF0589"+CCHO: 11791
OK

Test

AT+CCHO=?

UBX-13002752 - R67

OK

16 SIM management

Page 345 of 1001

u-blox cellular modules - AT commands manual

16.8.3 Defined values
Parameter<dfname><sessionid>

Type
NumberNumberDescription
DF name, coded on 1 to 16 bytes, identifying the UICC application.
Session Id to be used to target a specific application on the smart card using logicalchannel mechanism.

16.9 Close logical channel +CCHC+CCHC
Modules

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

Attributes

16.9.1 Description
Asks the ME to close a communication session with the active UICC. The ME shall close the previously opened
logical channel. The TE will no longer be able to send commands on this logical channel. The UICC will close thelogical channel when receiving this command.

16.9.2 Syntax
Type
Set

SyntaxAT+CCHC=<sessionid>

Response+CCHC

ExampleAT+CCHC=11791

OK

+CCHC
OK

Test

AT+CCHC=?

OK

16.9.3 Defined values
Parameter<sessionid>

Type
NumberDescription
Session Id to be used to target a specific application on the smart card using logicalchannel mechanism.

16.10 Generic UICC logical channel access +CGLA+CGLA
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
+CME Error

16.10.1 Description
Transmits to the MT the <command> that shall be sent as it is to the selected UICC. In the same manner the
UICC <response> shall be sent back by the MT to the TA as it is.
The command allows a direct control of the currently selected UICC by an application on the TE. The TE shallthen take care of processing UICC information within the frame specified by GSM/UMTS networks.
Although the command allows the TE to take control over the UICC-MT interface, there are some functions of
the UICC-MT interface that logically do not need to be accessed from outside the TA/MT. Moreover, for security
reason the GSM network authentication should not be handled outside the TA/MT.

UBX-13002752 - R67

16 SIM management

Page 346 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
Compared to the +CRLA command, the definition of +CGLA allows TE to take more control over the
UICC-MT interface. The locking and unlocking of the interface may be done by a special <command> value
or automatically by TA/MT (by interpreting <command> parameter). If the TE application does not use theunlock command (or does not send a <command> causing automatic unlock) in a certain timeout value,
the MT may release the locking.
TOBY-L2 / MPCI-L2
The PIN insertion is not mandatory before the command execution.

16.10.2 Syntax
Type
Set

SyntaxAT+CGLA=<sessionid>,<length>,<command>

Test

AT+CGLA=?

Response+CGLA: <length>,<response>

ExampleOKOK

16.10.3 Defined values
Parameter<sessionid>

Type
Number<length>Number<command>

String<response>

StringDescription
Identifier of the session to be used to send the APDU commands to the UICC. It is
mandatory to send the commands to the UICC when targeting applications on thesmart card using a logical channel other than the default channel (channel "0").
Length of the characters that are sent to TE in <command> or <response> (twotimes the actual length of the command or response)
Command passed on by the MT to the UICC in the format as described in 3GPP TS
31.101 [72] (hexadecimal character format; see +CSCS AT command)
Response to the command passed on by the UICC to the MT in the format as
described in 3GPP TS 31.101 [72] (hexadecimal character format; see +CSCS AT
command)16.11 Restricted UICC logical channel access +CRLA+CRLA
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
No
+CME Error

16.11.1 Description
By using this command instead of +CGLA, the TE application has easier but more limited access to the UICC
database. The set command transmits to the MT the UICC <command> and its required parameters. The
MT internally handles, for the selected UICC, all the UICC-MT interface locking and file selection routines. As
response to the command, the MT sends the actual UICC information parameters and response data. An MT
error result code may be returned when the command cannot be passed to the UICC, but the failure in theexecution of the command in the UICC is reported in <sw1> and <sw2> parameters.
The expected response time shall be increased when using a remote SIM card via SAP and in case ofsimultaneous access to the UICC by another AT interface or by internal clients (e.g. BIP, IMS).
TOBY-L2 / MPCI-L2
The PIN insertion is not mandatory before the command execution.

UBX-13002752 - R67

16 SIM management

Page 347 of 1001

u-blox cellular modules - AT commands manual

16.11.2 Syntax
Type
Set

SyntaxAT+CRLA=<sessionid>,<command>[,<fileid>[,<P1>,<P2>,<P3>[,<data>[,<pathid>]]]]

Response
Example+CRLA: <sw1>,<sw2>[,<response>] AT+CRLA=11791,176,28419,0,0,256

AT+CRLA=?

OK

OK+CRLA: 144,0,800
D746573742E33677070
2E636F6DFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFF
OK

Test

16.11.3 Defined values
Parameter<sessionid>

Type
Number<command>Number<fileid>

Number

<P1>

Number

<P2>

Number

<P3>

Number<data>

String<pathid>

String<sw1>

Number<sw2>

Number<response>

StringUBX-13002752 - R67

Description
Identifier of the session to be used to send the APDU commands to the UICC. It is
mandatory to send commands to the UICC when targeting applications on the smart
card using a logical channel other than the default channel (channel "0").
Command passed on by the MT to the UICC, see the 3GPP TS 31.101 [72]:• 176: READ BINARY• 178: READ RECORD• 192: GET RESPONSE• 214: UPDATE BINARY• 220: UPDATE RECORD• 242: STATUS• 203: RETRIEVE DATA
• 219: SET DATA
Identifier of an elementary datafile on UICC. Mandatory for every command except
STATUS. The values are described in ETSI TS 102.221 [73]. The range depends on theactual UICCand is defined in 3GPP TS 31.101 [72].
Parameter passed on by the MT to the UICC. The values are described in 3GPP TS
31.101 [72]. Mandatory for every command except GET RESPONSE and STATUS.
Parameter passed on by the MT to the UICC. The values are described in 3GPP TS
31.101 [72]. Mandatory for every command except GET RESPONSE and STATUS.
Parameter passed on by the MT to the UICC. The values are described in 3GPP TS
31.101 [72]. Mandatory for every command except GET RESPONSE and STATUS.
Information which shall be written to the SIM (hexadecimal character format; see+CSCS AT command)
Contains the path of an elementary file on the UICC in hexadecimal format. Thisparameter shall only be used in the mode "select by path from current DF" as definedin ETSI TS 102.221 [73].
Information from the UICC about the execution of the actual command. Thisparameter is delivered to the TE in both cases, on successful or failed execution of
the command. For examples of Status Words, see the +CRSM AT command.
Additional information depending on <sw1>. This parameter is delivered to the TE
in both cases, on successful or failed execution of the command. For examples of
Status Words, see the +CRSM AT command.
Response of a successful completion of the command previously issued (hexadecimal
character format; see +CSCS). The STATUS and GET RESPONSE return data, which
gives information about the current elementary datafield. This information includes
the type of file and its size (see 3GPP TS 31.101 [72]). After the READ BINARY, READ
RECORD or RETRIEVE DATA command the requested data will be returned. The
parameter is not returned after a successful UPDATE BINARY, UPDATE RECORD or
SET DATA command.

16 SIM management

Page 348 of 1001

u-blox cellular modules - AT commands manual

16.12 SIM states reporting +USIMSTAT+USIMSTAT
Modules

Attributes

LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

16.12.1 Description
Configures the +UUSIMSTAT URC presentation. Based on the configuration, the URC is able to report the SIM
card initialization status, the phonebook initialization status and the REFRESH proactive command execution
result.
If <state> 9 and 10 are reported, update all SIM card related parameters cached in the DTE's application(e.g. the IMSI retrieved with +CIMI command).

16.12.2 Syntax
Type
Set

SyntaxAT+USIMSTAT=<mode>

Response
OK

ExampleAT+USIMSTAT=3

Read

AT+USIMSTAT?

+USIMSTAT: <mode>

OK+USIMSTAT: 3

Test

AT+USIMSTAT=?

OK+USIMSTAT: (list of supported<mode>s)OK+UUSIMSTAT: <state>

URC

OK+USIMSTAT: (0-7)
OK+UUSIMSTAT: 8

16.12.3 Defined values
Parameter<mode>

Type
Number<state>NumberDescription
Bitmask representing which indications the +UUSIMSTAT URC is allowed to report.
See Table 25 for the meaning of each bit. The factory-programmed value is 0.
•
•
•
•
•
•
•
•
•
•
•
•
•
•

0: SIM card not present
1: PIN needed
2: PIN blocked
3: PUK blocked
4: (U)SIM not operational
5: (U)SIM in restricted use (FDN or BDN active)
6: (U)SIM operational (registration may be initiated)
7: SIM phonebook ready to be used (when the SIM application is active)
8: USIM phonebook ready to be used (when the USIM application is active)
9: (U)SIM toolkit REFRESH proactive command successfully concluded
10: (U)SIM toolkit REFRESH proactive command unsuccessfully concluded
11: PPP connection active, (U)SIM toolkit REFRESH proactive command delayed till
PPP deactivation
12: voice call active, (U)SIM toolkit REFRESH proactive command delayed till callrelease
13: CSD call active, (U)SIM toolkit REFRESH proactive command delayed till callrelease16.12.4 Notes••<state>=9 and 10 will not be reported when dedicated (+CFUN=6) or raw (+CFUN=9) mode is active.
Table 25 provides the meaning of each bit with the corresponding state:
Bit0States reported
Reports the (U)SIM initialization status (<state>'s from 0 to 6 may be reported)

UBX-13002752 - R67

16 SIM management

Page 349 of 1001

u-blox cellular modules - AT commands manual

Bit
1
2

States reported
Reports the (U)SIM phonebook initialization status (<state>'s from 7 to 8 may be reported)
Reports the (U)SIM toolkit REFRESH proactive command execution result (<state>'s from 9 to 13 may bereported)

Table 25: <mode> bitmask meaning
SARA-U260-03S / SARA-U270-03A / SARA-U270-03S / SARA-U270-73S / SARA-U280-03S /LISA-U200-03S / LISA-U200-83S / LISA-U201-03A / LISA-U201-03S / LISA-U201-83S• <state>=11, 12 and 13 are not reported.
SARA-U270-53S• On SARA-U270-53S-00 <state>=11, 12 and 13 are not reported.

16.13 Answer To Reset contents +USIMATR+USIMATR
Modules
Attributes

LARA-R2 TOBY-R2
SARA-U201 SARA-U270-53S LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

16.13.1 Description
Returns the actual content of the ATR (Answer To Reset).

16.13.2 Syntax
Type
ActionSyntaxAT+USIMATR

Response+USIMATR: <atr>
OK

Example+USIMATR: "3B9E96803FC3A080
31E073FE211B630801140F9000D3"
OK

16.13.3 Defined values
Parameter
<atr>

Type
StringDescription
ATR contents, see the ETSI TS 102.221 [92].

16.13.4 Notes•

The command needs of the SIM to correctly work.

16.14 Perform SIM switch +XSIMSWITCH+XSIMSWITCH
Modules
TOBY-L4
SyntaxAttributes
full

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time
Up to 3 min

Error reference+CME Error

16.14.1 Description
Selects the SIM slot to be used to perform SIM switch operation. It shall be ensured that both SIM cards areinserted so that SIM switch works seamlessly.
The command automatically sets the MT to minimum functionality by deactivating CS / PS services and the
SIM card, changes the selected SIM slot and finally restores the original functionality status, without the need
to issue the +CFUN AT command.

16.14.2 Syntax
Type
Set

SyntaxAT+XSIMSWITCH=<sim_slot>

UBX-13002752 - R67

ResponseOK

16 SIM management

ExampleAT+XSIMSWITCH=1

Page 350 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Read

AT+XSIMSWITCH?

+XSIMSWITCH: <sim_slot>

Test

AT+XSIMSWITCH=?

OK+XSIMSWITCH: (list of supported<sim_slot>s)

ExampleOK+XSIMSWITCH: 1
OK+XSIMSWITCH: (0-1)
OKOK

16.14.3 Defined values
Parameter<sim_slot>

Type
NumberDescription••

UBX-13002752 - R67

0 (factory-programmed value): SIM slot 1 to be used (by default SIM slot 1 would be
the active slot)
1: SIM slot 2 to be used

16 SIM management

Page 351 of 1001

u-blox cellular modules - AT commands manual

17 SIM toolkit
17.1 Introduction
SIM Application Toolkit (STK) is the 3GPP standard feature that allows the Subscriber Identity Module (SIM) tohandle the DCE, also by giving commands such as displaying menus and/or asking for user input, and control
its access to the network.
Once the SIM toolkit interface has been enabled via AT+CFUN command, the DTE is notified SIM toolkit
commands and events and can interact with the SIM through appropriate STK AT commands.
SIM toolkit processing supports two modes: dedicated and raw. In dedicated mode, the DTE is notified of STK
commands and events after decoding; in raw mode the DTE receives the raw data as received from the SIM.
Only one mode can be enabled and function at a time.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
The activation of the SIM toolkit interface can be done with AT+CFUN=6 for enabling dedicated mode and
AT+CFUN=9 for enabling raw mode.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
After the activation of the SIM toolkit interface, the setup menu may be displayed via URC (+STKPRO,+UCATPROI or +URCATI depending on module and mode) when available from the SIM (immediately at
SIM initialization or after PIN insertion).
For more details on the command description and parameters, see 3GPP TS 51.014 [39].
The setup menu fetched from the SIM card may vary with the terminal profile supported by the MT, whichis affected by the capabilities of the module itself (e.g. speech): this implies that different u-blox modules
may display different setup menus with the same SIM card.
The commands in this section properly work only if the SIM toolkit interface has been activated by the
DTE. Otherwise the SIM toolkit processing will be blocked.
If an AT command related to the dedicated mode is used when the raw mode is enabled (and vice versa),
an error result code ("+CME ERROR: operation not allowed" if +CMEE is set to 2) is returned.
The STK commands related to the Bearer Independent Protocol, i.e. Open Channel, Close Channel, Receive
Data, Send Data, Get Channel Status and the events Data Available and Channel Status, are autonomously
managed by the device without the intervention from the TE, unless the dedicated mode is active and the OpenChannel command requires the user intervention (see ETSI TS 102 223 [42]).
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
In dedicated mode if the Alpha Identifier is present in the STK command, the +STKPRO or +UCATPRON
URC will be issued, depending on module.
In dedicated mode when the user intervention is required, the terminal response shall be entered via+STKTR or +UCATTR command in order to proceed with or to terminate the proactive session.
Where supported, the +UUBIP URC may be enabled to monitor the BIP session.

17.2 Terminal profile +STKPROF+STKPROF
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

17.2.1 Description
Allows reading and changing the terminal profile (list of SIM Application Toolkit facilities supported by theterminal, see ETSI TS 102 223 [42]) data stored in NVM and used only at the SIM initialization. The SIM card

UBX-13002752 - R67

17 SIM toolkit

Page 352 of 1001

u-blox cellular modules - AT commands manual

may use this information to filter the proactive commands sent to the module. This command does not actually
remove/add any functionality from/to the module.
The command can be used only if the SIM toolkit interface is enabled in dedicated mode.

17.2.2 Syntax
Type
Set

SyntaxAT+STKPROF=<length>,<data>

Response
OK

ExampleAT+STKPROF=2,"1F7F"

Read

AT+STKPROF?

+STKPROF: <length>,<data>

OK+STKPROF:17,"FFFFFFFF7F0300
DF7F00000000010A0003"

OK

OK
Test

AT+STKPROF=?

OK

17.2.3 Defined values
Parameter<length><data>

Type
NumberStringDescription
Length in bytes of data sent to DTE in <data>
Terminal profile data coded in hex format

17.2.4 Notes•<length> set to 0 forces a reset to the default terminal profile stored in the MT.

17.3 Proactive command in dedicated mode +STKPRO+STKPRO
Modules

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Attributes

Settings saved Can be aborted
No
No

Response time-Error reference-

17.3.1 Description
The test command displays the list of the proactive commands that need a response from the user/application
via +STKTR command. Only the test command syntax is allowed.
During the STK transactions, if the STK interface has been activated in dedicated mode, the URC +STKPRO
displays every proactive command.

17.3.2 Syntax
Type
Test

SyntaxAT+STKPRO=?

Response+STKPRO: (list of supported <proactive_cmd>s)OK

Example+STKPRO: (01,05,16,17,18,19,20,32,
33,34,35,36,37,38,40,52,53)
OK

Generic syntax
URC
RefreshURC
Set up event list
URC
Set up call
URC

+STKPRO: <proactive_cmd>,...
+STKPRO: 01,<type>,<number of files>,<files>+STKPRO: 05,<event_list>+STKPRO: 16,<number>,<subaddr>,<type>,<alpha_1>,<icon_id1>,<alpha_2>,<icon_id2>

Send SSUBX-13002752 - R67

17 SIM toolkit

Page 353 of 1001

u-blox cellular modules - AT commands manual

Type
URC

SyntaxResponse+STKPRO: 17,<ss_data>,<alpha>,<icon_id>,<ref_number>Send USSD
URC

Example+STKPRO: 18,<dcs>,<hex_string>,<alpha>,<icon_
id>,<ref_number>

Send SMS
URC
Send DTMF
URCPlay tone
URC+STKPRO: 19,<alpha>,<icon_id>,<ref_number>+STKPRO: 20,<alpha>,<icon_id>,<dtmf_string>+STKPRO: 32,<tone>,<unit>,<interval>,<alpha>,<icon_id>

Display textURC

+STKPRO: 33,<type>,<dcs>,<hex_string>,<icon_
id>,<imm_resp>

Get inkey
URC+STKPRO: 34,<type>,<dcs>,<hex_string>,<icon_
id>

Get input
URC+STKPRO: 35,<type>,<dcs>,<hex_string>,<max_rsp_len>,<min_rsp_len>,<default_text>,<icon_id>

Select itemURC

+STKPRO: 36,<type>,<alpha>,<item_id>,<total_
items>,<item_text>,<next_action>,<default_
item>,<icon_id>,<icon_id_list_element>

Set up menu
URC

+STKPRO: 37,<type>,<alpha>,<item_id>,<total_
items>,<item_text>,<next_action>,<icon_id>,<icon_id_list_element>

Provide local info
URC
Set up idle mode textURC
Run AT command
URC+STKPRO: 38,<type>+STKPRO: 40,<dcs>,<hex_string>,<icon_id>+STKPRO: 52,<type>,<alpha>,<icon_id>,<at_command>Language notification
URC
Open channel
URC

Close channel
URC+STKPRO: 53,<language>+STKPRO: 64,<type>,<alpha>,<icon_id>,<bearer_
type>,<bearer_parameters>,<buffer_size>,<network_access_name>,<login_dcs>,<login_text>,<password_dcs>,<password_text>,<transport_type>,<transport_port>,<destination_
address_type>,<destination_address>+STKPRO: 65,<type>,<channel_id>,<alpha>,<icon_
id>

Receive data
URC

+STKPRO: 66,<type>,<channel_id>,<alpha>,<icon_
id>,<channel_data_length>

Send data
URC+STKPRO: 67,<type>,<channel_id>,<alpha>,<icon_
id>,<channel_data>

17.3.3 Defined values
Parameter<proactive_cmd>

UBX-13002752 - R67

Type
NumberDescription
Proactive command (see ETSI TS 102 223 [42])17 SIM toolkit

Page 354 of 1001

u-blox cellular modules - AT commands manual

Parameter<alpha>, <alpha_1>,<alpha_2><default_text><dcs><default_item><dtmf_string>Type
StringDescription
Alpha identifier (used in several proactive commands, see ETSI TS 102 223 [42])StringNumberNumberStringDefault text for the GET INPUT command (see ETSI TS 102 223 [42])Data coding scheme
Indication of the default item (see ETSI TS 102 223 [42])
DTMF tones coded in BCD (same format as the dialling number string defined for
EFADN in 3GPP TS 51.011 [17])Bitmask representing the list of events. See the Table 26 for the meaning of each bit.
Hexadecimal string (the coding is specified in the <dcs> parameter)
Icon identifier<event list>
Number<hex_string>
String<icon_id>,<icon_id1>, Number<icon_id2><icon_id_list_
Numberelement><interval>
Number<imm_resp>
Number<item_id>
Number<item_text>
String<language>
String<max rsp len>
Number<min rsp len>
Number<next_action>
NumberItem icon identifier
Time duration in number of units
Immediate response
Identifier of an item within a list
Text string of item
Two bytes string indicating the language
Maximum response length
Minimum response length
Used only in menu related proactive commands ("set up menu" and "select item") for
each item. It gives the possible actions that will be initiated by the SIM Card in case of
selection by the user (see ETSI TS 102 223 [42])Called party number
Reference number
Called party subaddr
Supplementary services string
Command qualifier<number><ref_number><subaddr><ss_data><type><tone>

StringNumberStringStringNumberNumber<total_items><unit>

NumberNumber<at_command><bearer_type><bearer_parameters><buffer_size><network_access_name><transport_type><transport_port><destination_
address_type><destination_
address><channel_id>

StringNumberString• 0: minutes• 1: seconds• 2: tenth of seconds
AT command string
Bearer type (see ETSI TS 102 223 [42])Bearer parameters (see ETSI TS 102 223 [42])NumberStringBuffer size (see ETSI TS 102 223 [42])Network access name (see ETSI TS 102 223 [42])NumberNumberNumberTransport protocol type (see ETSI TS 102 223 [42])Port number type (see ETSI TS 102 223 [42])Type of address (see ETSI TS 102 223 [42])StringAddress (see ETSI TS 102 223 [42])NumberChannel identifier (see ETSI TS 102 223 [42])UBX-13002752 - R67• 01: dial tone
• 02: call subscriber busy
• 03: congestion• 04: radio path acknowledge• 05: radio path not available• 06: error / special information• 07: call waiting tone
• 08: ringing tone
• 10: general beep
• 11: positive acknowledgement tone
• 12: negative acknowledgement or error tone
Total number of the menu items

17 SIM toolkit

Page 355 of 1001

u-blox cellular modules - AT commands manual

Parameter<channel_data_
length><channel_data>

Type
NumberDescription
Channel data length (see ETSI TS 102 223 [42])StringChannel data (see ETSI TS 102 223 [42])17.3.4 Notes
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Event description
MT call
Call connected
Call disconnected
Location status
User activity
Idle screen available
Card reader status
Language selection
Browser termination
Data available
Channel status
Access Technology Change
Display parameters changed
Local connection
Network Search Mode Change
Browsing status

Table 26: Event list bit description
SARA-G3 / LEON-G1• <proactive_cmd>=52 is not supported.

17.4 Terminal response in dedicated mode +STKTR+STKTR
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.4.1 Description
In dedicated mode, it allows entering response to a SIM Toolkit proactive command displayed by the +STKPROURC.
If no response is entered, after a timeout of duration may range from 180 to 300 s, the module sends anautonomous terminal response to the SIM to complete the STK transaction; the result depends on the pending
proactive command and can be "Command performed successfully", "No response from user", "Command typenot understood by ME" or "Command data not understood by ME" (see 3GPP TS 51.014 [39]).
The command must be always entered, to terminate the pending STK session at the MT-DTE interface, andto be able to enter additional STK commands.
The set command syntax depends on the <proactive_cmd> value.

17.4.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+STKTR=<proactive_cmd>[,<type>][,<result>,<add_result>[,

UBX-13002752 - R67

Response

ExampleOK

AT+STKTR=1,0

17 SIM toolkit

Page 356 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse<reference_number>][,<last_cmd>][,<dcs>][,<hex string>]]

RefreshSet

ExampleOK

AT+STKTR=01,<result>[,<add_result>]Set up event list
Set
AT+STKTR=05,<result>
Set up call
Set
AT+STKTR=16,<result>[,<add_result>]Send SS
Set
AT+STKTR=17,<result>,<add_result>[,<reference_number>]Send USSD
Set
AT+STKTR=18,<result>,<add_result>[,<reference_number>]Send SMS
Set
AT+STKTR=19,<result>,<add_result>[,<reference_number>]Send DTMF
Set
AT+STKTR=20,<result>[,<add_result>]Play tone
Set
AT+STKTR=32,<result>,<add_result>Display text
Set
AT+STKTR=33,<result>,<add_result>Get inkey
Set
AT+STKTR=34,<result>,<add_result>,0,<dcs>,<hex_string>Get input
Set
AT+STKTR=35,<result>,<add_result>,0,<dcs>,<hex_string>
Select item
Set
AT+STKTR=36,<result>,<add_result>,0,<dcs>,<hex_string>Set up menu
Set
AT+STKTR=37,<result>,<add_result>Provide local info (language setting)
Set
AT+STKTR=38,<result>,<language>Set up idle mode text
Set
AT+STKTR=40,<result>,<add_result>Run AT command
Set
AT+STKTR=52,<result>,<add_result>,0,<dcs>,<hex_string>
Language notification
Set
AT+STKTR=53,<result>,<add_result>Open channel
Set
AT+STKTR=64,<result>

OK

Test

+STKTR: (list of supported<proactive_cmd> values)+STKTR: (01,05,16,17,18,19,20,32,33,
34,35,36,37,38,40,52,53)

OK

OK

AT+STKTR=?

UBX-13002752 - R67

OK
OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

17 SIM toolkit

Page 357 of 1001

u-blox cellular modules - AT commands manual

17.4.3 Defined values
Parameter<proactive_cmd><result>

Type
NumberNumber<add_result>

Number<reference_number> Number<dcs><hex_string>NumberString<language>

String<last_cmd>

NumberDescription
Proactive command (see ETSI TS 102 223 [42])
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

0: Command performed successfully
1: Command performed with partial comprehension
2: Command performed, with missing information
3: REFRESH performed with additional EFs read
4: Command performed successfully, but requested icon could not be displayed
5: Command performed, but modified by call control by SIM
6: Command performed successfully, limited service
7: Command performed with modification
16: Proactive SIM session terminated by the user
17: Backward move in the proactive SIM session requested by the user
18: No response from user
19: Help information required by the user
20: USSD or SS transaction terminated by the user
32: MT currently unable to process command
33: Network currently unable to process command
34: User did not accept the proactive command
35: User cleared down call before connection or network release
36: Action in contradiction with the current timer state
37: Interaction with call control by SIM, temporary problem
38: Launch Browser generic error
48: Command beyond MT's capabilities
49: Command type not understood by MT
50: Command data not understood by MT
51: Command number not known by MT
52: SS Return Error
53: SMS RP-ERROR
54: Error, required values are missing
55: USSD Return Error
56: MultipleCard commands error
57: Interaction with call control by SIM or MO short message control by SIM,
permanent problem• 58: Bearer Independent Protocol error
Additional information, required with specific result codes and/or proactive
commands
Number containing the indicated reference number; this parameter can be used only
in case of <proactive_cmd> related to SMS, SS, USSD
Data coding scheme
Each 8-bit octet is presented as two IRA character long hexadecimal numbers, e.g.
octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65).
The value depends on the indicated <dcs> value. The meaning of the parameter
depends on the proactive command:• Get input: the response string• Get inkey: the response character• Select item: identifier of an item within a list
• Run AT command: the response to the AT command requested by the SIM
Decimal value of the ISO 639 language code. E.g. German language is coded as "de" inISO 639. Thus 0x6465 has to be converted in decimal: <language>=25701
Obsolete parameter, to be set to 0

17.4.4 Notes•*0 stands for the obsolete parameter <last_cmd>.

SARA-U2 / LISA-U2 / LISA-U1• <reference_number> is not supported.

UBX-13002752 - R67

17 SIM toolkit

Page 358 of 1001

u-blox cellular modules - AT commands manual

SARA-G3 / LEON-G1• <proactive_cmd>=53 is not supported; in this case, the terminal response is automatically sent by theMT.

17.5 Proactive session status in dedicated mode +STKCNF+STKCNF
Modules

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1

17.5.1 Description
In dedicated mode, the URC +STKCNF displays the SIM card's toolkit application reply to a Terminal Responsecommand or an Envelope command.

17.5.2 Syntax
Type
URC

SyntaxResponse+STKCNF: <proactive_cmd>,<result>,<add_result>,<sw1>

Example+STKCNF: 37,0,255,144

17.5.3 Defined values
Parameter<proactive_cmd>

Type
Number<result><add_result>

NumberNumber<sw1>

NumberDescription
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

01: Refresh
02: More time
03: Poll interval
04: Polling off
05: Set up event list
16: Set up call
17: Send SS
18: Send USSD
19: Send SMS
20: Send DTMF
32: Play tone
33: Display text
34: Get inkey
35: Get input
36: Select item
37: Set up menu
38: Provide local info
39: Timer management
40: Set up idle mode text
52: Run AT command
53: Language notification
64: Open channel
65: Close channel
66: Receive data
67: Send data
68: Get channel status
129: Dummy value used to indicate that the response is relative to an ENVELOPE
commandGeneral result code (see ETSI TS 102 223 [42])Additional information code (see ETSI TS 102 223 [42]). If no additional information isavailable 255 is returned
Byte indicating the status of the UICC/SIM at the end of a command.
•

UBX-13002752 - R67

144: command executed successfully

17 SIM toolkit

Page 359 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• For other responses see 3GPP TS 51.011 [17]17.6 Bearer Independent Protocol status indication +UBIP+UBIPModules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S
TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
MPCI-L200-02S MPCI-L200-03S MPCI-L201-02S MPCI-L210-02S MPCI-L210-03S MPCI-L220
MPCI-L280
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

17.6.1 Description
Configures the Bearer Independent Protocol status indication, i.e. the +UUBIP URC presentation.
The channel status event provides information about the link status and its drop, therefore it is advisable
to enable it where available.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
Verify that the BIP related proactive commands and events are supported (see the +STKPROF and+UCATPROF AT commands).

17.6.2 Syntax
Type
Set

SyntaxAT+UBIP=<mode>

Response
OK

ExampleAT+UBIP=1

Read

AT+UBIP?

+UBIP: <mode>OK+UBIP: 0

Test

AT+UBIP=?

OKOK+UBIP: (list of supported <mode>'s) +UBIP: (0,1)
OK+UUBIP: <ev_cmd>,<val>

URC

OK+UUBIP: 10,261

17.6.3 Defined values
Parameter<mode>

Type
Number<ev_cmd>

Number<val>

NumberUBX-13002752 - R67

Description
Indicates whether the +UUBIP URC is enabled or not:• 0 (factory-programmed value): BIP status indication disabled• 1: BIP status indication enabled• 2: OPEN CHANNEL, CLOSE CHANNEL and CHANNEL STATUS EVENT statusindications enabled
Allowed values:• TOBY-L4 / TOBY-L200-03A / TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L280-03A / TOBY-L280-03S / MPCI-L201-02S - 0, 1, 2
• TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S /TOBY-L220 / TOBY-L280-02S / MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280 /LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3 - 0, 1
Indicates the event download's tag or proactive command's tag. Allowed values:• 10: Channel status event• 64: Open channel proactive command• 65: Close channel proactive command• 66: Receive data proactive command• 67: Send data proactive command
Indicates the channel status (in case of the event download channel status) or resultin case of a proactive command (see ETSI TS 102 223 [42])17 SIM toolkit

Page 360 of 1001

u-blox cellular modules - AT commands manual

17.6.4 Notes
TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S /MPCI-L201-02S• <mode>=2 is not supported by MPCI-L201-02S-00, TOBY-L200-03S-00, TOBY-L201-02S-00,
TOBY-L210-03A-00, TOBY-L210-03S-00, TOBY-L280-03S-00.

17.7 Default BIP APN configuration +UBIPAPN+UBIPAPN
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U201 LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

17.7.1 Description
Configures the default BIP APN which will be used when the Open Channel command does not include the
Network Access Name parameter or when the Network Access Name parameter is null.

17.7.2 Syntax
Type
Set

SyntaxAT+UBIPAPN=<APN>

Response
OK

ExampleAT+UBIPAPN="APN_name"Read

AT+UBIPAPN?

+UBIPAPN: <APN>OK+UBIPAPN: "APN_name"OKOK

17.7.3 Defined values
Parameter
<APN>

Type
StringDescription
Default Access Point Name for BIP service. The factory-programmed value is anempty string.

17.8 Envelope in dedicated mode +STKENV+STKENV
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.8.1 Description
With the SIM toolkit interface enabled in dedicated mode, it allows encoding and sending an STK envelopecommand to the SIM.

17.8.2 Syntax
Type
Set

Test

SyntaxAT+STKENV=<envelope_cmd>,<opt_ENV_data1>,<opt_ENV_
data2>
AT+STKENV=?

Response
OK

ExampleAT+STKENV=211,01
OK+STKENV: (list of supported<envelope_cmd>+STKENV: 211,214
OK

OK

UBX-13002752 - R67

17 SIM toolkit

Page 361 of 1001

u-blox cellular modules - AT commands manual

17.8.3 Defined values
Parameter<envelope_cmd>

Type
Number<opt_ENV_data1>

NumberDescription•

code 211 (0xD3): menu selection (<opt_ENV_data1> shall specify the item identifierof startup menu list)• code 214 (0xD6): event download (<opt_ENV_data1> shall specify the <event_list>,
in which only one event can be included)
Command code related parameters and can have the following values, depending on
the chosen envelope command:••<opt_ENV_data2>

NumberIf <envelope_cmd>=211, "item identifier"If <envelope_cmd>=214 (event list),o 4: user activity
o 5: idle screen available
o 7: language selection
o 8: browser termination
Meaning depends on the chosen envelope command:••

If <envelope_cmd>=211, "help requested" with the following encoding:o 0: help is not requestedo 1: help is requested
If <envelope_cmd>=214 and <opt_ENV_data1>=7, "currently used language in theDTE" (see AT+STKTR=38)

17.9 Call and short message control in dedicated mode
+STKCC+STKCC
Modules

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1

17.9.1 Description
In dedicated mode, the URC +STKCC reports indications of the call control and short message control by SIM(see 3GPP TS 51.014 [44]).

17.9.2 Syntax
Type
URC

SyntaxResponse
Example+STKCC: <cc_command>,<res_+STKCC: 1,0,"Calling","+3913456890
val>,<alpha>,<param1>[,<sc_addr>, "<ton_npi>,<dest_addr>]

17.9.3 Defined values
Parameter<cc_command>Type
Number<res_val>

Number<alpha><param1>

UBX-13002752 - R67

StringStringDescription• 1: set up call
• 2: send SS• 3: send USSD
• 4: send SMS
Call control result value•••

00: Allowed, no modification
01: Not allowed
02: Allowed with modification

•
•
•
•

Called party number if <cc_command>=1
Supplementary service string if <cc_command>=2
USSD control string if <cc_command>=3
Type of number and numbering plan if <cc_command>=4

17 SIM toolkit

Page 362 of 1001

u-blox cellular modules - AT commands manual

Parameter<sc_addr><ton_npi><dest_addr>

Type
StringNumberStringDescription
Service center address
Type of number and numbering plan
Destination address

17.10 Proactive command indication in raw mode +SATI+SATI
Modules

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1

17.10.1 Description
Communicates to the user the proactive command, in raw mode, coming from the SIM.
The module expects a terminal response to be sent; the user shall respond with AT+SATR for sending theterminal response.

17.10.2 Syntax
Type
URC

SyntaxResponse+SATI: <text>

Example+SATI: "D02081030
1250082028182050
C53544B2D4A617661436172648F0
30141411E020001"

17.10.3 Defined values
Parameter<text>Type
StringDescription
Raw proactive command data expressed in Hex value

17.11 Proactive command notification in raw mode +SATN+SATN
Modules

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1

17.11.1 Description
Sends the proactive command in raw mode to the user in case the module handles the proactive command.
For this URC, the module does not expect any terminal response from the user, since the terminal response to
SIM is autonomously sent by the device.

17.11.2 Syntax
Type
URC

SyntaxResponse+SATN: <text>

Example+SATN: "D01A81030
1100082028183050
A63616C6C696E672E2E2E860
38121F3"

17.11.3 Defined values
Parameter<text>

UBX-13002752 - R67

TypeStringDescription
Raw proactive command data expressed in Hex value

17 SIM toolkit

Page 363 of 1001

u-blox cellular modules - AT commands manual

17.12 Send terminal response in raw mode +SATR+SATR
Modules
Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.12.1 Description
In raw mode only, it is used to send the terminal response to the SIM after the URC +SATI has been received
by the user.

17.12.2 Syntax
Type
Set

SyntaxAT+SATR=<text>

Response
OK

ExampleAT+SATR="8103012400820
28281830100900101"
OK

17.12.3 Defined values
Parameter<text>Type
StringDescription
Raw terminal response data expressed in Hex value

17.13 Terminal response confirmation in raw mode +SATF+SATF
Modules

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1

17.13.1 Description
In raw mode, it provides the response to a terminal response (sent by the user or automatically by the module)
from the SIM.

17.13.2 Syntax
Type
URC

SyntaxResponse+SATF: <sw1>,<sw2>

Example+SATF: 144,017.13.3 Defined values
Parameter
<sw1>

Type
NumberDescription
Status of the last response
•
•

<sw2>

UBX-13002752 - R67

Number144 (0x90): command successfully executed
0: command to SIM was suppressed because of multiple terminal response or
wrong client
For other responses see 3GPP TS 51.011 [17].
The second status byte specifies additional information depending on <sw1>

17 SIM toolkit

Page 364 of 1001

u-blox cellular modules - AT commands manual

17.14 User confirmation for setup call in raw mode +SATD+SATD
Modules
Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.14.1 Description
In raw mode only, the set command is used for the user confirmation required by the SET UP CALL proactive
command. The user can accept the call or reject the call.
The set command is used as response to the +SATN URC sent to the user for SET UP CALL Proactive
command.

17.14.2 Syntax
Type
Set

SyntaxAT+SATD=<user_confirmation>

Response
OK

Test

AT+SATD=?

+SATD: (list of supported <user_
confirmation>'s)

ExampleAT+SATD=1
OK+SATD: (0,1)
OKOK

17.14.3 Defined values
Parameter
Type<user_confirmation> Number

Description••

0: reject the call
1: accept the call17.15 Envelope download in raw mode +SATE+SATE
Modules
Attributes

LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.15.1 Description
In raw mode, it sends the raw envelope data to the SIM.

17.15.2 Syntax
Type
Set

SyntaxAT+SATE=<text>

Response+SATE: <sw1>,<sw2>,<envelope_type>,<event_type>OK

ExampleAT+SATE="d30782020181900101"+SATE: 145,111,211,255
OK

17.15.3 Defined values
Parameter<text><sw1>

Type
StringNumberDescription
Raw envelope data expressed in Hex value
Status of the last response:
•

<sw2>

UBX-13002752 - R67

Number0: command to SIM was suppressed because of multiple terminal response or
wrong client• 144 (0x90): command successfully executed
For other responses see 3GPP TS 51.011 [18].
Specifies the additional information depending on <sw1>

17 SIM toolkit

Page 365 of 1001

u-blox cellular modules - AT commands manual

Parameter<envelope_type>

Type
Number<event_type>

NumberDescription• 211 (0xD3): menu selection• 214 (0xD6): event download
If <envelope_type>=214 (event list):•••

4: user activity
5: idle screen available
7: language selection

17.16 Call and Short Message Control in Raw Mode
+STKCTRLIND+STKCTRLIND
Modules
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
Attributes
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference-

17.16.1 Description
The test command lists the supported call and SMS control types.
In raw mode, the URC +STKCTRLIND is an unsolicited indication for control actions performed by the SIM on
mobile originated calls and short messages.

17.16.2 Syntax
Type
Test

SyntaxAT+STKCTRLIND=?

Response
Example+STKCTRLIND: (range of supported +STKCTRLIND: (0-3)<type>)
OK
OK"set up call" type:

URC+STKCTRLIND: 0,<result>,<alpha_id>,<destination_address>,<destination_address_type>"send SS" type:+STKCTRLIND: 1,<result>,<alpha_id>,<destination_address>,<destination_address_type>"send USSD" type:+STKCTRLIND: 2,<result>,<alpha_id>, <dcs>, <data>"send SMS" type:+STKCTRLIND: 3,<result>,<alpha_id>,<destination_address>,<destination_address_type>,<service_center_address>,<service_center_address_type>17.16.3 Defined values
Parameter<type>

Type
NumberDescription••••

0: setup call
1: send SS
2: send USSD
3: send SMS<result>

Number

•••0: the request is allowed without modifications
1: the request is not allowed. No action shall be performed
2: the request is modified, but allowed. The modified values shall be used

UBX-13002752 - R67

17 SIM toolkit

Page 366 of 1001

u-blox cellular modules - AT commands manual

ParameterType<alpha_id><destination_
address><destination_
address_type><service_center_address><service_center_address_type><dcs><data>

StringStringDescription• 254: the toolkit is busy. The request shall be repeated later without taking any
action in between• 255: error happened
Alpha identifier
Dialling number

NumberType of number and numbering plan

StringService center address

NumberType of number and numbering plan

NumberStringData Coding Scheme
USSD string

17.17 Terminal profile +UCATPROF+UCATPROF
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

17.17.1 Description
Allows reading and changing the current terminal profile (i.e. the list of SIM Application Toolkit facilities
supported by the terminal, see ETSI TS 102 223 [42]) sent to the SIM card; if the terminal profile has changed,
it is downloaded to the SIM card. Changes in the terminal profile are not persistent after reboot. The SIM card
may use this information to filter the proactive commands sent to the module. This command does not actually
remove/add any functionality from/to the module.

17.17.2 Syntax
Type
Set

SyntaxAT+UCATPROF=<length>,<data>

Response
OK

ExampleAT+UCATPROF=2,"1F7F"

Read

AT+UCATPROF?

+UCATPROF: <length>,<data>

OK+UCATPROF:17,"FFFFFFFF7F0300
DF7F00000000010A0003"

OK

OK
Test

AT+UCATPROF=?

OK

17.17.3 Defined values
Parameter<length><data>

Type
NumberStringDescription
Length in bytes of data sent to DTE in <data>
Terminal profile data coded in hexadecimal format

17.18 Proactive command indication in dedicated mode
+UCATPROI+UCATPROI
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

17.18.1 Description
In dedicated mode, during the STK transactions, the +UCATPROI URC displays proactive commands comingfrom the SIM that require a response from the user via +UCATTR command.

UBX-13002752 - R67

17 SIM toolkit

Page 367 of 1001

u-blox cellular modules - AT commands manual

The test command displays the list of such proactive commands. Only the test command syntax is allowed.

17.18.2 Syntax
Type
Test

SyntaxAT+UCATPROI=?

Generic syntax
URC
RefreshURC
Set up event list
URC
Set up call
URC
Play tone
URC
Display text
URC
Get inkey
URC
Get input
URC

Select item
URC

Set up menu
URC

Provide local info
URC
Set up idle mode textURC
Run AT command
URC
Language notification
URC
Open channel
URC

Response+UCATPROI: (list of supported <proactive_
cmd>s)

Example+UCATPROI: (01,05,16,32,33,34,35,
36,37,38,40,52,53,64)

OK

OK+UCATPROI: <proactive_cmd>,...
+UCATPROI: 01,<type>,<number of files>,<files>+UCATPROI: 05,<event_list>+UCATPROI: 16,<number>,<subaddr>,<type>,<alpha_1>, <icon_id1>,<alpha_2>,<icon_id2>+UCATPROI: 32,<tone>,<unit>,<interval>,<alpha>, <icon_id>+UCATPROI: 33,<type>,<dcs>,<hex_string>,<icon_id>, <imm_resp>+UCATPROI: 34,<type>,<dcs>,<hex_string>,<icon_id>+UCATPROI: 35,<type>,<dcs>,<hex_string>,<max_rsp_len>,<min_rsp_len>,<default_text>,<icon_id>+UCATPROI: 36,<type>,<alpha>,<item_id>,<total_items>, <item_text>,<next_action>,<default_item>,<icon_id>,<icon_id_list_
element>+UCATPROI: 37,<type>,<alpha>,<item_id>,<total_items>, <item_text>,<next_action>,<icon_id>,<icon_id_list_element>+UCATPROI: 38,<type>+UCATPROI: 40,<dcs>,<hex_string>,<icon_id>+UCATPROI: 52,<type>,<alpha>,<icon_id>,<at_command>+UCATPROI: 53,<language>+UCATPROI: 64,<alpha>17.18.3 Defined values
See +STKPRO.

17.18.4 Notes
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L210-00S• <proactive_cmd>=64 is not supported.

UBX-13002752 - R67

17 SIM toolkit

Page 368 of 1001

u-blox cellular modules - AT commands manual

17.19 Proactive command notification in dedicated mode
+UCATPRON+UCATPRON
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

17.19.1 Description
In dedicated mode, during the STK transactions, the +UCATPRON URC displays proactive commands comingfrom the SIM that do not require a response from the user.
The test command displays the list of such proactive commands. Only the test command syntax is allowed.

17.19.2 Syntax
Type
Test

SyntaxAT+UCATPRON=?

Response+UCATPRON: (list of supported <proactive_
cmd>s)

Example+UCATPRON: (17,18,19,20,37)
OKOK
Send SS
URC
Send USSDURC+UCATPRON: 17,<ss_data>,<alpha>,<icon_id>+UCATPRON: 18,<dcs>,<hex_string>,<alpha>,<icon_id>

Send SMS
URC
Send DTMF
URC+UCATPRON: 19,<alpha>,<icon_id>+UCATPRON: 20,<alpha>,<icon_id>,<dtmf_
string>Set up menu
URC

+UCATPRON: 37,<type>,<alpha>,<item_id>,<total_items>,<item_text>,<next_action>,<icon_id>,<icon_id_list_element>

17.19.3 Defined values
See +STKPRO.

17.20 Terminal response in dedicated mode +UCATTR+UCATTR
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.20.1 Description
In dedicated mode, it allows entering the response to a SIM Toolkit proactive command displayed by the+UCATPROI URC.
If no response is entered, after a timeout whose duration may range from 180 to 300 s, the module sends anautonomous terminal response to the SIM to complete the STK transaction; the result depends on the pending
proactive command and can be "Command performed successfully", "No response from user", "Command typenot understood by ME" or "Command data not understood by ME" (see 3GPP TS 51.014 [39]).
The command must be always entered, to terminate the pending STK session at the MT-DTE interface, andto be able to enter additional STK commands.
The set command syntax depends on the <proactive_cmd> value.

UBX-13002752 - R67

17 SIM toolkit

Page 369 of 1001

u-blox cellular modules - AT commands manual

17.20.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UCATTR=<proactive_cmd>[,<type>][,<result>,<add_result>[,<reference_number>][,<last_cmd>][,<dcs>][,<hex string>]]
RefreshSet
AT+UCATTR=01,<result>[,<add_result>]Set up event list
Set
AT+UCATTR=05,<result>
Set up call
Set
AT+UCATTR=16,<result>[,<add_result>]Play tone
Set
AT+UCATTR=32,<result>,<add_result>Display text
Set
AT+UCATTR=33,<result>,<add_result>Get inkey
Set
AT+UCATTR=34,<result>,<add_result>,0,<dcs>,<hex_string>Get input
Set
AT+UCATTR=35,<result>,<add_result>,0,<dcs>,<hex_string>
Select item
Set
AT+UCATTR=36,<result>,<add_result>,0,<dcs>,<hex_string>Set up menu
Set
AT+UCATTR=37,<result>,<add_result>Provide local info (language setting)
Set
AT+UCATTR=38,<type>,<language>Set up idle mode text
Set
AT+UCATTR=40,<result>,<add_result>Run AT command
Set
AT+UCATTR=52,<result>,<add_result>,0,<dcs>,<hex_string>
Language notification
Set
AT+UCATTR=53,<result>,<add_result>Open channel
Set
AT+UCATTR=64,<result>,<add_result>Response

ExampleOK

AT+UCATTR=1,0

Test+UCATTR: (list of supported<result>s)+UCATTR: (01,05,16,32,33,34,35,36,
37,38,40,52,53,64)

OK

OK

AT+UCATTR=?

OK

OK

OK
OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

17.20.3 Defined values
See +STKTR Defined values.

UBX-13002752 - R67

17 SIM toolkit

Page 370 of 1001

u-blox cellular modules - AT commands manual

17.20.4 Notes
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L210-00S• <proactive_cmd>=64 is not supported.

17.21 Proactive Session Status in Dedicated Mode +UCATCNF+UCATCNF
Modules

TOBY-L2 MPCI-L2

17.21.1 Description
In dedicated mode, the status of the STK proactive session is displayed using the +UCATCNF URC. The URC
comes out after the AT+UCATTR or the AT+UCATENV command has been issued.

17.21.2 Syntax
Type
URC

SyntaxResponse+UCATCNF: <proactive_cmd>,<result>,<add_result>,<sw1>

Example+UCATCNF: 37,0,255,144

17.21.3 Defined values
See +STKCNF Defined values.

17.22 Envelope in Dedicated Mode +UCATENV+UCATENV
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.22.1 Description
In dedicated mode, it allows encoding and sending an STK envelope command to the SIM.

17.22.2 Syntax
Type
Set

Test

SyntaxAT+UCATENV=<envelope_cmd>,<opt_ENV_data1>,<opt_ENV_
data2>
AT+UCATENV=?

Response
OK

ExampleAT+UCATENV=211,01
OK+UCATENV: (list of supported<envelope_cmd>+UCATENV: 211,214
OKOK

17.22.3 Defined values
See +STKENV Defined values.

17.23 Call and Short Message Control in Dedicated Mode
+UCATCC+UCATCC
Modules

TOBY-L2 MPCI-L2

17.23.1 Description
In dedicated mode, the indication of the call control and short message control by SIM (see 3GPP TS 51.014[39]) is performed using the +UCATCC URC.

UBX-13002752 - R67

17 SIM toolkit

Page 371 of 1001

u-blox cellular modules - AT commands manual

17.23.2 Syntax
Type
URC

SyntaxResponse
Example+UCATCC: <cc_command>,<res_+UCATCC: 1,0,"Calling",
val>,<alpha>,<param1>[,<sc_addr>, "+3913456890"<ton_npi>,<dest_addr>]

17.23.3 Defined values
See +STKCC Defined values.

17.24 Proactive Command Indication in Raw Mode +URCATI+URCATI
Modules

TOBY-L2 MPCI-L2

17.24.1 Description
During the STK transactions, the +URCATI URC displays proactive commands coming from the SIM that
require a response from the user in raw mode.
The module expects a terminal response to be sent; the user shall respond with AT+URCATR for sending theterminal response.
This URC may be issued only if the SIM toolkit interface is enabled in raw mode.

17.24.2 Syntax
Type
URC

SyntaxResponse+URCATI: <text>

Example+URCATI: "D020810
301250082028182050
C53544B2D4A617661436172648F0
30141411E020001"

17.24.3 Defined values
Parameter<text>Type
StringDescription
Raw proactive command data expressed in Hex value

17.25 Proactive Command Notification in Raw Mode +URCATN+URCATN
Modules

TOBY-L2 MPCI-L2

17.25.1 Description
Notifies the proactive command in raw mode to the user when the module autonomously handles the proactive
command.
For this URC, the module does not expect any terminal response from the user, since the terminal response to
the SIM is built within the module and automatically sent.

17.25.2 Syntax
Type
URC

SyntaxResponse+URCATN: <text>

Example+URCATN: "D01A810
301100082028183050
A63616C6C696E672E2E2E860
38121F3"

17.25.3 Defined values
Parameter<text>

UBX-13002752 - R67

TypeStringDescription
Raw proactive command data expressed in Hex value

17 SIM toolkit

Page 372 of 1001

u-blox cellular modules - AT commands manual

17.26 Terminal response in Raw Mode +URCATR+URCATR
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.26.1 Description
In raw mode, it allows entering the response to a SIM Toolkit proactive command displayed by the +URCATI
URC.
If no response is entered, after a timeout whose duration may range from 180 to 300 s, the module sends anautonomous terminal response to the SIM to complete the STK transaction; the result depends on the pending
proactive command and can be "Command performed successfully", "No response from user", "Command typenot understood by ME" or "Command data not understood by ME" (see 3GPP TS 51.014 [39]).
The command must be always entered, to terminate the pending STK session at the MT-DTE interface, andto be able to enter additional STK commands.
The set command syntax depend on the <proactive_cmd> value.

17.26.2 Syntax
Type
Set

Syntax
AT+URCATR=<text>

Response
OK

ExampleAT+URCATR="8103012400820
28281830100900101"
OK

17.26.3 Defined values
Parameter<text>Type
StringDescription
Raw terminal response data expressed in Hex value

17.27 Proactive Session Status in Raw Mode +URCATF+URCATF
Modules

TOBY-L2 MPCI-L2

17.27.1 Description
In raw mode, it provides the response received from the SIM to a terminal response (sent by the user or
automatically by the module) .

17.27.2 Syntax
Type
URC

SyntaxResponse+URCATF: <sw1>,<sw2>

Example+URCATF: 144,017.27.3 Defined values
See +SATF.

17.28 Envelope in Raw Mode +URCATE+URCATE
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time
< 20 sError reference+CME Error

17.28.1 Description
In raw mode, it sends the raw envelope data to the SIM and returns the result of the SIM instruction.

UBX-13002752 - R67

17 SIM toolkit

Page 373 of 1001

u-blox cellular modules - AT commands manual

17.28.2 Syntax
Type
Set

Syntax
AT+URCATE=<text>

Response
Example+URCATE: <sw1>,<sw2>,<envelope_ AT+URCATE="d3078202018190010
type>,<event_type>1"
OK+URCATE: 145,111,211,255
OK17.28.3 Defined values
Parameter<text><sw1>

Type
StringNumberDescription
Raw envelope data expressed in Hex value
Status of the last response:•<sw2><envelope_type>

NumberNumber<event_type>

Number0: command to SIM was suppressed because of multiple terminal response or
wrong client• 144 (0x90): command successfully executed
For other responses see 3GPP TS 51.011 [17].
Specifies the additional information depending on <sw1>• 211 (0xD3): menu selection• 214 (0xD6): event download
If <envelope_type>=214 (event list):• 4: user activity• 5: idle screen available• 7: language selection

17.29 Call and Short Message Control in Raw Mode +URCATCC+URCATCC
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

17.29.1 Description
In raw mode, +URCATCC is the unsolicited indication of call control and SMS control carried out by the SIM on
mobile originated service requests.

17.29.2 Syntax
Type
Test

Syntax
AT+URCATCC=?

URC

UBX-13002752 - R67

Response+URCATCC: (range of supported<type>)

Example+URCATCC: (0-3)
OKOK"set up call" type:+URCATCC: 0,<result>,<alpha_id>,<destination_address>,<destination_address_type>"send SS" type:+URCATCC: 1,<result>,<alpha_id>,<destination_address>,<destination_address_type>"send USSD" type:+URCATCC: 2,<result>,<alpha_id>,<dcs>,<data>"send SMS" type:+URCATCC: 3,<result>,<alpha_id>,<destination_address>,<destination_address_type>,<service_center_address>,<service_center_address_type>

17 SIM toolkit

Page 374 of 1001

u-blox cellular modules - AT commands manual

17.29.3 Defined values
Parameter<type>

Type
Number<result>

Number<alpha_id><destination_
address><destination_
address_type><service_center_address><service_center_address_type><dcs><data>

StringStringDescription
Allowed values:• 0: setup call
• 1: send SS• 2: send USSD
• 3: send SMS
Allowed values:• 0: the request is allowed without modifications• 1: the request is not allowed. No action shall be performed• 2: the request is modified, but allowed. The modified values shall be used
• 254: the toolkit is busy. The request shall be repeated later without taking any
action in between• 255: error happened
Alpha identifier
Dialling number

NumberType of number and numbering plan

StringService center address

NumberType of number and numbering plan

NumberStringData coding scheme
USSD string

17.30 User setting for proactive DTMF tone generation+UDTMF+UDTMF
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

17.30.1 Description
On a request from the SIM toolkit of proactive DTMF tone generation (SEND DTMF), the <mode> parameter
controls whether the request of DTMF tone generation is performed or it is not.
TOBY-L2 / MPCI-L2
The read command is not supported.

17.30.2 Syntax
Type
Set

SyntaxAT+UDTMF=<mode>

Response
OK

ExampleAT+UDTMF=1

Read

AT+UDTMF?

+UDTMF: <mode>

OK+UDTMF: 1

Test

AT+UDTMF=?

OK+UDTMF: (list of supported<mode>s)OK+UDTMF: (0-1)
OK

OK

UBX-13002752 - R67

17 SIM toolkit

Page 375 of 1001

u-blox cellular modules - AT commands manual

17.30.3 Defined values
Parameter<mode>

Type
NumberDescription
Indicates the working mode in relation to DTMF tone generation via SIM-TK. Allowed
values:••0: disable the DTMF tone generation (the terminal response is "Proactive SIM
session terminated by user")
1 (factory-programmed value): enable the DTMF tone generation (the terminal
response is encoded according to the result)17.31 Refresh delay events management +UDCONF=54+UDCONF=54
Modules
Attributes

SARA-U201 SARA-U270-53S
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

17.31.1 Description
If a REFRESH command is received while in a state where execution of the command would be unacceptable,
upsetting the current user operation (e.g. notification during a call that the IMSI has changed), the terminal
should inform the UICC using a negative TERMINAL RESPONSE (e.g. terminal currently unable to process
command).
In some cases it may be preferred to delay the command execution instead of sending a negative TR. For
example, if dedicated (+CFUN=6) / raw (+CFUN=9) is not enabled, when a REFRESH is fetched no indication issent to the DTE, and thus if the DCE is in connected state, the command will not be executed.
The <delay_events> setting with the addition of +USIMSTAT reporting permits the DTE to take action, e.g.
release a voice call, and consequently execute the REFRESH command.
During the certification process, the default configuration <delay_events>=8 is recommended.

17.31.2 Syntax
Type
Set

SyntaxAT+UDCONF=54,<delay_events>

Response
OK

ExampleAT+UDCONF=54,8

Read

AT+UDCONF=54+UDCONF: 54,<delay_events>

OK+UDCONF: 54,8

OKOK

17.31.3 Defined values
Parameter<delay_events>

Type
NumberDescription
Bitmap representing the events which will delay a REFRESH command instead ofsending a negative TERMINAL RESPONSE (e.g. terminal currently unable to process
command). See Table 27 for the meaning of each bit.
The factory-programmed value is 8.

17.31.4 Notes
•

•

Bit
0
1
2
3

Delay events
PPP connection active, (U)SIM toolkit REFRESH proactive command delayed till PPP deactivation
Voice call ongoing, (U)SIM toolkit REFRESH proactive command delayed till call release
CSD call ongoing, (U)SIM toolkit REFRESH proactive command delayed till call release
ENVELOPE, SMS-PP download

Table 27: <delay_events> bitmap meaning
If a PPP connection is active, and its delay bit is not set, the REFRESH command will be executed insteadof sending a negative TR.

UBX-13002752 - R67

17 SIM toolkit

Page 376 of 1001

u-blox cellular modules - AT commands manual

SARA-U270-53S• The command is not supported by SARA-U270-53S-00.

UBX-13002752 - R67

17 SIM toolkit

Page 377 of 1001

u-blox cellular modules - AT commands manual

18 Packet switched data services
18.1 PDP contexts and parameter definition
18.1.1 Primary and secondary PDP contexts
A PDP context can be either primary or secondary. In LTE, PS data connections are referred to as EPS bearers:
EPS bearers are conceptually equivalent to the legacy PDP contexts, which are often referred to for sake ofsimplicity. Similarly to a PDP context, the EPS bearer can be a default (primary) or dedicated (secondary) one.
The initial EPS bearer established during LTE attach procedure is actually a default EPS bearer. A secondary
PDP context uses the same IP address of a primary PDP context (the usual PDP context activated e.g. via
dial-up). The Traffic Flow Filters for such secondary contexts shall be specified according to 3GPP TS 23.060[10].
The typical usage of the secondary PDP contexts is in VoIP calls, where RTP (speech) packets are conveyed on
one PDP context (e.g. the primary one) with a given QoS (e.g. low reliability) whereas SIP signalling is routed ona different PDP context (e.g. the secondary one, with the same IP address but different port numbers) with amore reliable QoS.
A Traffic Flow Template (i.e. a filter based on port number, specifying relative flow precedence) shall be
configured for the secondary context to instruct the GGSN to route down-link packets onto different QoS flows
towards the TE.
TOBY-L2 / MPCI-L2
The TFT filter can be applied also on uplink packets: in this case the filter has a local scope, as it instructs
the MT to route a packet of a given source or destination address on a specific radio bearer to achieve
the negotiated QoS
PDP context typePrimary

Secondary

Activation procedure
Used to establish a logical connection through the network from the UE to the GGSN with a
specifically negotiated Quality of Service (QoS).
The UE initiates the PDP context activation: it changes the session management state to active,
creates the PDP context, obtains the IP address and reserves radio resources. After the activation,
the UE is able to send IP packets over the air interface.
Used to establish a second PDP context with the same IP address and the same APN as theprimary PDP context.
The two contexts may have different QoS profiles, which makes the feature useful for applications
that have different QoS requirements (e.g. IP multimedia); QoS is applied based on port number
addressing.

SARA-G4 / SARA-G3 / LEON-G1
The secondary PDP contexts are not supported.
TOBY-L2 / MPCI-L2
At most 8 PDP contexts can be theoretically defined and activated, both by the UE and the NW, as network
initiated PDP context activation is supported (and by default accepted) by the UE.
TOBY-L2 / MPCI-L2
At most 3 PDP contexts can be used with dial-up; further constraints may derive from the current
USB connectivity configuration, e.g. from the number of CDC-ACMs supporting AT interface (see the+UUSBCONF command description)).
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
At most 2 secondary PDP contexts may be associated to a primary PDP context and at most 2 secondary
PDP contexts can be activated, since the maximum number of PDP contexts, both normal and secondary,is always 3.

18.1.2 Multiple PDP contexts
Two PDP context types are defined:• "external" PDP context: IP packets are built by the DTE, the MT's IP instance runs the IP relay function only;

UBX-13002752 - R67

18 Packet switched data services

Page 378 of 1001

u-blox cellular modules - AT commands manual•"internal" PDP context: the PDP context (relying on the MT's embedded TCP/IP stack) is configured,established and handled via the data connection management AT commands.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G340 /SARA-G350 / LEON-G1
Refer to +UPSD, +UPSDA and +UPSND AT commands to configure and establish a PDP context (relying
on the MT's embedded TCP/IP stack).

Multiple PDP contexts are supported. The DTE can access these PDP contexts either alternatively throughthe physical serial interface, or simultaneously through the virtual serial ports of the multiplexer (multiplexing
mode MUX), with the following constraints:• Using the MT's embedded TCP/IP stack, only a internal PDP context is supported. This IP instance supports
up to 7 sockets;• The sum of active external and internal PDP contexts cannot exceed the maximum number of active PDP
contexts indicated in the <cid> parameter description;• Using external PDP contexts via dial-up, it is usually possible to have at most 3 PPP instances
simultaneously active.
SARA-G300 / SARA-G310
Multiple PDP contexts and internal PDP contexts are not supported.
LEON-G1
Using the MT's embedded TCP/IP stack, the IP instance supports up to 16 sockets.

18.1.3 Parameter definition
18.1.3.1 <APN>
The Access Point Name (APN) is a string parameter, which is a logical name, valid in the current PLMN's
domain, used to select the GGSN (Gateway GPRS Support Node) or the external packet data network to beconnected to. The APN can be omitted: this is the so-called "blank APN" setting that may be suggested by
network operators (e.g. to roaming devices); in this case the APN string is not included in the message sent
to the network.
The maximum length of the parameter is:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 99 characters (the maximum length of coded APN is 100 octets, see 3GPP TS 23.003 [95], subclause 9.1)
• SARA-G4 - 95 characters
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
An optional special code placed at the beginning of <APN> indicates the type of authentication handlingbetween the module and the network and may be:• CHAP: challenge handshake authentication protocol• PAP: personal authentication protocol• NOAUTH: authentication protocol not used
• code omitted: authentication protocol not used
An example for the usage of <APN> is:
AT+CGDCONT=1,"IP","CHAP:internet.t-d1.de"
The information text response to the +CGDCONT read command does not include the PAP: and CHAP:
prefixes in the APN string.
TOBY-L2 / MPCI-L2
The optional authentication special code is not supported. The +UAUTHREQ command should be used
after the context definition.
"Blank APN" is not supported in Verizon configuration (see +UMNOCONF) except for LTE attach. In other
RATs and for additional default EPS bearer activations, a non-empty APN shall be configured.
18.1.3.2 <cid>
PDP context identifier. A numeric parameter specifying a particular PDP context definition. This parameter isvalid only locally on the interface DTE-MT.

UBX-13002752 - R67

18 Packet switched data services

Page 379 of 1001

u-blox cellular modules - AT commands manual

The maximum number of definable and active PDP contexts depend(s) on the product version:3
Product
TOBY-L4006 / TOBY-L4106 / TOBY-L4206 / TOBY-L4906-01A /TOBY-L4906-51A
TOBY-L4906-50A
TOBY-L2 / MPCI-L2
LARA-R204
LARA-R202 / LARA-R203 / LARA-R211 / LARA-R220 / LARA-R280 /TOBY-R2
SARA-U2 / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S /LISA-U200-83S / LISA-U201-03A / LISA-U201-03S / LISA-U201-83S /LISA-U260-02S / LISA-U270-02S / LISA-U270-62S / LISA-U270-63S /LISA-U270-68S
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S /LISA-U270-01S / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
SARA-U201-63B / LISA-U200-62S

Max number of
Max number of active
definable PDP contexts PDP contexts
8
8
4
8
11
10

4
8
8
8

11

3

3

3

10

3

TOBY-L2 / MPCI-L2
When the local dial-up feature is available, it can be enabled using the PDP context identifier 100. This PDP
context identifier is not related with the cellular network PDP contexts/EPS bearers.
TOBY-L2 / MPCI-L2
When registering in LTE, <cid>= 4 is mapped to the initial default EPS bearer (see +UCGDFLT AT
command for details).
LARA-R2 / TOBY-R2
The <cid> of PDP contexts/EPS bearers defined by IMS, BIP and OMA-DM internal clients are definedin the range that goes from 31 to 50. Their parameters can be read but cannot be modified through AT
commands.
TOBY-L4 / LARA-R2 / TOBY-R2
When registering in LTE, <cid>= 1 is mapped to the initial default EPS bearer.
LARA-R202 / LARA-R203 / TOBY-R2
Check that the XCAP APN configuration is correct for the current network operator (see +UIMSCFG AT
command, key 200). If the XCAP APN is the same of the general purpose APN (i.e. APN for internet
connection), then configure the supplementary services before performing a dial-up. In case the dial-up
feature is already started, terminate it before to configure supplementary services AT commands. Thisis a requirement for products AT&T certified: supplementary services AT commands require XCAP tocorrectly run over the APN "nxtgenphone" (<cid>=1). In case the APN is reserved for dial-up feature the ATcommands will provide an error result code.
18.1.3.3 <PDP_addr>
String parameter identifying the MT in the IP-address space applicable to the PDP service. If the value is null oromitted (dynamic IP addressing), then a value may be provided by the DTE during the PDP startup procedureor, failing that, a dynamic address will be requested via DHCP. It can be read with the command AT+CGPADDRor AT+CGDCONT read command.
To request a static IP address, a fixed IP address shall be specified for the <PDP_addr> paramater of the+CGDCONT set command and the user shall not rely on PPP negotiation via IPCP CONFREQ option.
Depending on the IP-version, the <PDP_addr> consists of 4 octets (IPv4) or 16 octets (IPv6):• IPv4: "ddd.ddd.ddd.ddd"• IPv4v6: "ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd"• IPv6: "ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd"
TOBY-L4
In the IPv4v6 PDP address the IPv4 and IPv6 addresses are separated by an ".".

3

The maximum number of active PDP contexts may be limited by the MNO

UBX-13002752 - R67

18 Packet switched data services

Page 380 of 1001

u-blox cellular modules - AT commands manual

LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S /SARA-G350-00S / SARA-G350-00X / SARA-G350-01B / SARA-G350-01S / LEON-G1
The IPv6 stack for an external context is not supported: hence the IP-addresses for IPv4v6 and IPv6
protocols are not supported.
18.1.3.4 <PDP_type>
The Packet Data Protocol (PDP) type is a string parameter which specifies the type of packet data protocol:• "IP": Internet Protocol (IETF STD 5)• "NONIP": Non IP• "IPV4V6": virtual <PDP_type> introduced to handle dual IP stack UE capability (see the 3GPP TS 24.301 [68])TOBY-L201-01S / MPCI-L201-01SOn TOBY-L201-01S, TOBY-L201-02S-00, MPCI-L201-01S, MPCI-L201-02S-00 the "IPV4V6"
configuration is allowed only if the <MNO> parameter of AT+UMNOCONF command is set to Verizon
or regulatory only.
TOBY-L201-02S / MPCI-L201-02S
On TOBY-L201-02S-00, MPCI-L201-02S-00 the "IPV4V6" configuration is allowed only if the <MNO>
parameter of AT+UMNOCONF command is set to Verizon or regulatory only.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S /SARA-G350-00S / SARA-G350-00X / SARA-G350-01B / SARA-G350-01S / LEON-G1
The IPv6 stack for an external context is not supported: hence the "IPV4V6" value is not supported.
TOBY-L200-00S / TOBY-L200-02S / MPCI-L200
On TOBY-L200-02S, TOBY-L200-03S-00, MPCI-L200-00S, MPCI-L200-02S, MPCI-L200-03S-00 the
IPv6 stack for an external context is not supported: hence the "IPV4V6" value is not supported.

•

TOBY-L200-03S
On TOBY-L200-03S-00 the IPv6 stack for an external context is not supported: hence the "IPV4V6"
value is not supported.
"IPV6": Internet Protocol, version 6 (see RFC 2460)
TOBY-L201-01S / MPCI-L201-01SOn TOBY-L201-01S, TOBY-L201-02S-00, MPCI-L201-01S, MPCI-L201-02S-00 the "IPV6" configurationis allowed only if the <MNO> parameter of AT+UMNOCONF command is set to Verizon or regulatory
only.
TOBY-L201-02S / MPCI-L201-02S
On TOBY-L201-02S-00, MPCI-L201-02S-00 the "IPV6" configuration is allowed only if the <MNO>
parameter of AT+UMNOCONF command is set to Verizon or regulatory only.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S /SARA-G350-00S / SARA-G350-00X / SARA-G350-01B / SARA-G350-01S / LEON-G1
The IPv6 stack for an external context is not supported: hence the "IPV6" value is not supported.
TOBY-L200-00S / TOBY-L200-02S / MPCI-L200
The IPv6 stack for an external context is not supported: hence the "IPV6" value is not supported.

•

TOBY-L200-03S
On TOBY-L200-03S-00 the IPv6 stack for an external context is not supported: hence the "IPV6" value
is not supported.
SARA-U201-63B / LISA-U200-62S only - "PPP": Point to Point Protocol
TOBY-L210-62S / TOBY-L210-65S
Only a single data PDP context (both internal and external) is allowed: the parameter can be set to "IPV4"
only.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1<PDP_type>="NONIP" is not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 381 of 1001

u-blox cellular modules - AT commands manual

18.2 PPP LCP handshake behaviour
TOBY-L4
PPP is not supported.
When a data call is initiated by means of D* AT command, the module switches to PPP mode just after the
CONNECT intermediate result code. The first step of the PPP procedure is the LCP handshake, in this phase
the behaviour of module series differ between them.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The data call can be initiated also by the +CGDATA AT command setting "PPP" as <L2P> protocol.
Entering OnLine Command Mode (OLCM) during LCP handshake phase is strongly discouraged because
the handshake procedure could be broken and should be restarted from the beginning.
TOBY-L2 / MPCI-L2
The module starts sending the LCP configuration packets by its side (up to 10 retries every 1 s). If no valid LCP
response packet is received from the TE, the module drops the PDP context and returns the NO CARRIER final
result code.
LARA-R2 / TOBY-R2 / LISA-U270-62S / LISA-U270-63S / LISA-U270-68S
The module starts in PPP silent mode (wait the first LCP packet): if the TE does not starts the LCP handshakein between 1 s, the module starts sending the LCP configuration packets by its side (up to 10 retries every 6s). If none valid LCP response packet is received from the TE, the module drops the PDP context and returns
the NO CARRIER final result code.
SARA-U2 / LISA-U200 / LISA-U201 / LISA-U230 / LISA-U260 / LISA-U270-01S / LISA-U270-02S / LISA-U1
The module starts in PPP silent mode (wait the first LCP packet): if the TE does not starts the LCP handshakein between 1 s, the module starts sending the LCP configuration packets by its side (up to 10 retries every 1 s).
If none valid LCP response packet is received from the TE, the module drops the PDP context and returns the
NO CARRIER final result code.
SARA-G4 / SARA-G3 / LEON-G1
By default the module starts PPP in silent mode, waiting the first LCP packet coming from the TE. If a valid LCP
packet is received the module continues the LCP handshake by its side, otherwise it remains in wait state. If
the module is in wait state, it is possible to make it switch back to the AT command mode toggling the DTR line.
It is possible to disable the PPP silent mode by means of the +UDCONF=0 command. When the silent mode
is disabled, the module will start sending the LCP configuration packets (up to 10 retries every 6 s) just after
the CONNECT intermediate result code. If none valid LCP response packet is received from the TE, the module
will act like in silent mode.

18.3 Printing IP address format +CGPIAF+CGPIAF
Modules
Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.3.1 Description
Defines the printing format of IPv6 address parameters of the other AT commands. See RFC 4291 [74] fordetails of the IPv6 address format.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
The affected parameters are:
•
•
•
•
•

In +CGTFT and +CGTFTRDP the <remote_address_and_subnet_mask> parameter
In +CGDCONT the <PDP_addr> parameter
In +CGPADDR the <PDP_addr_1> and <PDP_addr_2> parameters
In +CGCONTRDP, the <local_address_and_subnet_mask>, <dns_prim_addr>, <dns_sec_addr>, <P_
CSCF_prim_addr> and <P_CSCF_sec_addr> parameters
In +CRC the <PDP_addr> parameter of URC GPRS <PDP_type>,<PDP_addr>[,<L2P>[,<APN>]]

UBX-13002752 - R67

18 Packet switched data services

Page 382 of 1001

u-blox cellular modules - AT commands manual

18.3.2 Syntax
Type
Set

Read

Test

SyntaxAT+CGPIAF=[<IPv6_
AddressFormat>[,<IPv6_
SubnetNotation>[,<IPv6_
LeadingZeros>[,<IPv6_
CompressZeros>]]]]
AT+CGPIAF?

Response
OK

ExampleAT+CGPIAF=1,1,1,1
OK+CGPIAF: <IPv6_AddressFormat>,<IPv6_SubnetNotation>,<IPv6_LeadingZeros>,<IPv6_
CompressZeros>+CGPIAF: 0,0,0,0
OK

OK+CGPIAF: (list of supported+CGPIAF: (0-1),(0-1),(0-1),(0-1)<IPv6_AddressFormat>s),OK(list of supported <IPv6_
SubnetNotation>s),(list of
supported <IPv6_LeadingZeros>s),(list of supported <IPv6_
CompressZeros>s)

AT+CGPIAF=?

OK

18.3.3 Defined values
Parameter<IPv6_
AddressFormat>

Type
Number<IPv6_
SubnetNotation>

Number<IPv6_
LeadingZeros>

Number<IPv6_
CompressZeros>

NumberDescription
Defines the IPv6 address format:• 0 (default value): IPv4-like dot-notation used. IP address and subnetwork mask if
applicable, are dot-separated• 1: IPv6-like colon-notation used. IP address and subnetwork mask if applicable andwhen given explicitly, are separated by a space
Defines the subnet-notation for <remote_address_and_subnet_mask>. The setting
does not apply if <IPv6_AddressFormat>=0:• 0 (default value): both IP address and subnet mask are explicitly stated, separated
by a space• 1: the printout format is applying / (forward slash) subnet-prefix Classless InterDomain Routing (CIDR)
Defines whether leading zeros are omitted or not. The setting does not apply if <IPv6_
AddressFormat>=0:• 0 (default value): leading zeros omitted• 1: leading zeros included
Defines whether 1-n instances of 16-bit-zero-values are replaced by only "::". Thisapplies only once. The setting does not apply if <IPv6_AddressFormat>=0:• 0 (default value): no zero compression• 1: use zero compression

18.3.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• The PIN insertion is not mandatory before the command execution.

18.4 PDP context definition +CGDCONT+CGDCONT
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
NVM / OP
No

Response time-Error reference+CME Error

18.4.1 Description
Defines the connection parameters for a PDP context, identified by the local context identification parameter<cid>. If the command is used only with parameter <cid>, the corresponding PDP context becomes undefined.

UBX-13002752 - R67

18 Packet switched data services

Page 383 of 1001

u-blox cellular modules - AT commands manual

Each context is permanently stored so that its definition is persistent over power cycles.
The command is used to set up the PDP context parameters for an external context, i.e. a data connection
using the external IP stack (e.g. Windows dial-up) and PPP link over the serial interface.
Usage of static i.e. user defined IP address is possible in UTRAN and GERAN but not in EUTRAN; to preventinconsistent addressing methods across various RATs, static IP addressing is not recommended for LTE
modules: 3GPP TS 23.060 [10] Rel.8 and later releases specify that a UE with EUTRAN/UTRAN/GERAN
capabilities shall not include a static PDP address in PDP context activation requests.
The information text response to the read command provides the configuration of all the PDP context / EPS
bearers that have already been defined. The test command returns a different row for each <PDP_type> value
supported by the module.
TOBY-L2 / MPCI-L2
Use the +UCGDFLT AT command to set the connection parameters of the initial default bearer.
Since dial-up supports only IPv4 connectivity, the defined IPv6 EPS bearers / PDP contexts will not be used.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
After the PDP context activation, the information text response to the read command provides theconfiguration negotiated with the network (similarly to +CGTFTRDP and +CGCONTRDP AT commands).
TOBY-L4 / LARA-R2 / TOBY-R2
The read command shows PDP contexts/EPS bearers defined by IMS, BIP and OMA-DM internal clients
but they cannot be defined, modified or undefined with the set command.
It is forbidden to define a PDP context having the same APN used by the IMS internal client, e.g. on
TOBY-R2 and LARA-R202 / LARA-R203 / LARA-R211 the APN shall be different from "ims" or "IMS" and on
LARA-R204 the APN shall be different from "VZWIMS" or "IMS".
LARA-R204
In Verizon Configuration and when attached to Roaming PLMN the Class 3 APN will be defined with <PDP_
type>=IPv4-only at <cid>=1, as per Verizon specifications. Such EPS attach bearer shall then be used fordata connectivity. This is not valid on LARA-R204-02B-00, LARA-R204-02B-01.

18.4.2 Syntax
Type
Set

SyntaxAT+CGDCONT=[<cid>[,<PDP_
type>[,<APN>[,<PDP_addr>[,<d_comp>[,<h_comp>[,<IPv4AddrAlloc>[,<emergency_
indication>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>]]]]]]]]]]]

Response
OK

ExampleIPv4 example
AT+CGDCONT=1,"IP","APN_name","1.2.3.4",0,0OK
IPv4v6 example
AT+CGDCONT=1,"IPV4V6","APN","0.0.0.0 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0OKIPv6 example
AT+CGDCONT=1,"IPV6","APN","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0

Read

AT+CGDCONT?

OK+CGDCONT: <cid>,<PDP_type>,+CGDCONT: 1,"IP","web.omnitel.it",<APN>,<PDP_addr>,<d_comp>,"91.80.140.199",0,0<h_comp>[,<IPv4AddrAlloc>,
OK<emergency_indication>[,<P-CSCF_
discovery>,<IM_CN_Signalling_Flag_
Ind>[,<NSLPI>]]][+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp>[,<IPv4AddrAlloc>,<emergency_indication>[,<P-CSCF_
discovery>,<IM_CN_Signalling_Flag_
Ind>[,<NSLPI>]]]]OK

UBX-13002752 - R67

18 Packet switched data services

Page 384 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+CGDCONT=?

Response+CGDCONT: (list of supported<cid>s),<PDP_type>,,,(list of
supported <d_comp>s),(list of
supported <h_comp>s)[,(list of
supported <IPv4AllocAddr>s),(list of supported <emergency_
indication>s)[,(list of supported<P-CSCF_discovery>s),(list of
supported <IM_CN_Signalling_
Flag_Ind>s)[,(list of supported<NSLPI>s)]]]Example+CGDCONT: (1-3),"IP",,,(0-2),(0-4)+CGDCONT: (1-3),"IPV6",,,(0-2),(0-4)
OK[+CGDCONT: (list of supported<cid>s),<PDP_type>,,,(list of
supported <d_comp>s),(list of
supported <h_comp>s)[,(list of
supported <IPv4AllocAddr>s),(list of supported <emergency_
indication>s)[,(list of supported<P-CSCF_discovery>s),(list of
supported <IM_CN_Signalling_
Flag_Ind>s)[,(list of supported<NSLPI>s)]]]]
OK

18.4.3 Defined values
Parameter<cid><PDP_type><APN><PDP_addr><d_comp>Type
NumberStringStringNumberNumber<h_comp>Number

<IPv4AddrAlloc>

Number<emergency_
indication>

Number<request_type>

Number<P-CSCF_discovery> Number

UBX-13002752 - R67

Description
See <cid>. The default value is 1.
See <PDP_type>. The default value is "IP".
See <APN>. The default value is "" (blank APN).
See <PDP_addr>. The default value is "0.0.0.0"
PDP data compression; it can have the values:• 0 (default value): off• 1: on (predefined compression type i.e. V.42bis data compression)• 2: V.42bis data compression• 3: V.44
PDP header compression; it can have the values:• 0 (default value): off• 1: on (predefined compression type, i.e. RFC1144)• 2: RFC1144• 3: RFC2507• 4: RFC3095<h_comp>: the available head-compressions are dependent on configuration of
the stack (configured via features in the stack)Controls how the MT/TA requests to get the IPv4 address information:• 0 (default value): IPv4 Address Allocation through NAS Signalling• 1: IPv4 Address Allocated through DHCP
Indicates whether the PDP context is for emergency bearer services or not:• 0 (default value): PDP context is not for emergency bearer services• 1: PDP context is for emergency bearer services
Indicates the type of PDP context activation request for the PDP context:• 0: PDP context is for new PDP context establishment or for handover from a non3GPP access network (how the MT decides whether the PDP context is for new PDP
context establishment or for handover is implementation specific)• 1: PDP context is for emergency bearer services• 2 (default value): PDP context is for new PDP context establishment• 3: PDP context is for handover from a non-3GPP access network
Influences how the MT/TA requests to get the P-CSCF address, see 3GPP TS 24.229[81] annex B and annex L:

18 Packet switched data services

Page 385 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<IM_CN_Signalling_ Number
Flag_Ind><NSLPI>

Number<secure_PCO>

Number

<IPv4_MTU_
discovery>

Number<Local_Addr_Ind>

NumberDescription• 0 (default value): preference of P-CSCF address discovery not influenced by+CGDCONT• 1: preference of P-CSCF address discovery through NAS Signalling• 2: preference of P-CSCF address discovery through DHCP
Shows whether the PDP context is for IM CN subsystem-related signalling only or not:• 0: PDP context is not for IM CN subsystem-related signalling only
• 1: PDP context is for IM CN subsystem-related signalling only
Indicates the NAS signalling priority requested for the corresponding PDP context:• 0 (default value): indicates that the PDP context has to be activated with the value
for the low priority indicator configured in the MT.
• 1: indicates that the PDP context has to be activated with the value for the low
priority indicator set to "MS is not configured for NAS signalling low priority".
The MT utilises the NSLPI information provided as specified in 3GPP TS 24.301 [68]and 3GPP TS 24.008 [12].
Specifies if security protected transmission of PCO is requested or not (applicable for
EPS only):• 0 (default value): Security protected transmission of PCO is not requested.
• 1: Security protected transmission of PCO is requested.
Influences how the MT/TA requests to get the IPv4 MTU size:• 0 (default value): Preference of IPv4 MTU size discovery not influenced by+CGDCONT.
• 1: Preference of IPv4 MTU size discovery through NAS signalling.
Indicates to the network whether or not the MS supports local IP address in TFTs:• 0 (default value): indicates that the MS does not support local IP address in TFTs.
• 1: indicates that the MS supports local IP address in TFTs.

18.4.4 Notes
Additional examples:
Command

Response

AT+CGDCONT=?

+CGDCONT: (1-3),"IP",,,(0),(0-1)

Description
Configure the error result code
format by means of the +CMEE
AT command
Test command

AT+CGDCONT=4,"IP","internet"
AT+CGDCONT=2,"IP","internet"
AT+CGDCONT=1,"IP","STATREAL"
AT+CGDCONT=3,"IP","tim.ibox.it"

OK+CME ERROR: operation not allowed
OK
OK
OK

Define out of range PDP contexts
Define allowed PDP contexts
Define allowed PDP contexts
Define allowed PDP contexts+CME ERROR: operation not allowed+CGDCONT: 2,"IP","internet","0.0.0.0",0,0

TOBY-L2 / MPCI-L2
This step is not applicable.
Define out of range PDP contexts
Read command

AT+CGDCONT=253,"IP","internet"
AT+CGDCONT?

+CGDCONT: 1,"IP","STATREAL","0.0.0.0",0,0+CGDCONT: 3,"IP","tim.ibox.it","0.0.0.0",0,0OK

TOBY-L2 / MPCI-L2• <d_comp>=3 is not supported.
• The <NSLPI> parameter is not supported.
• The module automatically accepts the Mobile Terminated contexts/bearers.
• The <cid> of a mobile terminated context/bearer is assigned following the rules below:
o Primary context (2G/3G) or default bearer (4G): first <cid> not defined in the ordered list = [4, 3, 2,
1, 8, 7, 6, 5].
o Secondary context (2G/3G) or dedicated bearer (4G): first <cid> not defined in the ordered list = [8,7, 6, 5, 1, 2, 3, 4].

UBX-13002752 - R67

18 Packet switched data services

Page 386 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / LARA-R2 / TOBY-R2• <d_comp>=1, 2, 3 are not supported.
• The command setting are stored in the NVM at the module switch off.
• The module automatically accepts Mobile Terminated PDP contexts/EPS bearers.
• The <NSLPI> parameter is not supported.
• <P-CSCF_discovery>=2 is not supported.
TOBY-L4• The <cid> parameter is mandatory for the AT+CGDCONT set command.
• The static IP address set with +CGDCONT is ignored in all RATs and overwritten with the IP address
assigned by the network.
LARA-R2 / TOBY-R2• The static IP address set with +CGDCONT, which is used in the Activate PDP Context Request message
in 2G and 3G, in 4G is overwritten with the IP address assigned by network during the LTE attach or
EPS default bearer activation.
TOBY-L4106 / TOBY-L4206 / TOBY-L4906 / LARA-R204 / LARA-R211 / LARA-R220 / LARA-R280 /TOBY-R200-42B• When registering in LTE, the initial default EPS bearer is mapped to <cid>=1 and by default it isconfigured as follows:o <APN>=""o <PDP_addr>="0.0.0.0 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"
o <PDP_type>="IPV4V6"
TOBY-L4006 / LARA-R202 / LARA-R203 / TOBY-R200-02B / TOBY-R200-82B / TOBY-R202• The factory-programmed settings of the initial default EPS bearer mapped to <cid>=1 are:o <APN>="nxtgenphone"o <PDP_addr>="0.0.0.0 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"
o <PDP_type>="IPV4V6"
LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 / LARA-R280 / TOBY-R2• <h_comp>=1, 2, 3 and 4 are not supported.
LARA-R204• In VZW mode (see +UMNOCONF command), the settings of the initial default EPS bearer mapped to<cid>= 1 is automatically selected among the entries of the APN table (see +VZWAPNE read command)
depending on the IMS service status (IMS test mode active or inactive, IMS registration successful ornot).
SARA-U2 / LISA-U2 / LISA-U1• <d_comp>=3 is not supported.
• <IPv4AddrAlloc>, <emergency_indication>, <P-CSCF_discovery>, <IM_CN_Signalling_Flag_Ind> and<NSLPI> parameters are not supported.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270• If <APN> is not specified the value "apn" is assumed.
• To omit the APN, i.e. to use the so-called "blank APN" setting, leave undefined the PDP context
associated to <cid>=1 and use it to dial-up a PPP connection.
SARA-G3 / LEON-G1• The <APN> default value is "apn"• <d_comp>=1, 2, 3 are not supported (<d_comp>=1 may be accepted, but no compression is performed).
• <h_comp>=2, 3 and 4 are not supported.
• The context's setting is not permanently stored in NVM.
• It is possible to omit the APN by specifying the <cid> and the <PDP_type> only.
• <IPv4AddrAlloc>, <emergency_indication>, <P-CSCF_discovery>, <IM_CN_Signalling_Flag_Ind> and<NSLPI> parameters are not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 387 of 1001

u-blox cellular modules - AT commands manual

LEON-G1• If only the parameter <cid> is set, the corresponding PDP context is not undefined.
SARA-G4• The <cid> parameter is mandatory.
• <d_comp>=1, 2, 3 are not supported (<d_comp>=1 may be accepted, but no compression is performed).
• <h_comp>=2, 3 and 4 are not supported.
• The context's setting is not permanently stored in NVM.
• It is possible to omit the APN by specifying the <cid> and the <PDP_type> only.
• <IPv4AddrAlloc>, <emergency_indication>, <P-CSCF_discovery>, <IM_CN_Signalling_Flag_Ind> and<NSLPI> parameters are not supported.

18.5 Protocol configuration options configuration +UPCO+UPCO
Modules
Attributes

TOBY-L4
LARA-R2 TOBY-R2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.5.1 Description
Manages the protocol configuration options (PCO) of PDP contexts/EPS bearers. It provides the following
functionality:• Configuration of the PCO sent to the network when a PDP context is activated;• Retrieval of the PCO negotiated with the network, that can configure or modify them both in values and in
types;• Notification via URC of the availability of new PCO information from the network (due to network initiated
PDP context modification for the <cid>). The modified PCO can be queried using the get option.

18.5.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UPCO=<op_code>,[.....]

Response

Example[+UPCO:<cid>[,<Tag>,<Number_of_values>,<Value>[,<Value>]....
[,<Tag>,<Number_of_values>,<Value>[,<Value>]....]]]

OK
Configure PCO information (to be sent to network)
Set
AT+UPCO=1,<cid>[,[<protocol_conf_ OK
options>][,[<pcscfIPv6_addr_req>][,[<ImCN>][,[<DnsIPv6Addr_req>][,[<ms_nw_req_bearer_ctrl_ind>][,[<dsm_ipv6_home_agent_addr_req>][,[<dsm_ipv6_home_nw_prefi_req>][,[<dsm_ipv6v4_home_agent_addr_req>][,[<ip_addr_alloc_nas_
signalling>][,[<ipv4_addr_alloc_
dhcpv4>][,[<pcscf_ipv4_addr_req>][,[<dns_server_ipv4_addr_req>][,[<msisdn_req>][,[<ifom_support_req>][,<ipv4_mtu_req>]]]]]]]]]]]]]]]
Read PCO information (received from network)
Read
AT+UPCO=2,<cid>[+UPCO:<cid>[,<Tag>,<Number_of_values>,<Value>[,<Value>]....
[,<Tag>,<Number_of_values>,<Value>[,<Value>]....]]]

AT+UPCO=2,1+UPCO: 1,0,1,12,0,1,0,11,1,""
OK

OK
Enable PCO modification URC (initiated from network)

UBX-13002752 - R67

18 Packet switched data services

Page 388 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+UPCO=3

Response
OK

ExampleAT+UPCO=3
OK

Disable PCO modification URC (initiated from network)
Set
AT+UPCO=4
OK

AT+UPCO=4
OK

Test

AT+UPCO=?

+UPCO: (list of supported <op_code>s)OK+UPCOI: <cid>

URC+UPCO: (1-4)
OK+UPCOI: 1

18.5.3 Defined values
Parameter<op_code>Type
Number<cid><protocol_conf_
options>

NumberString<pcscfIPv6_addr_
req>

Number<ImCN>

Number

<DnsIPv6Addr_req> Number<ms_nw_req_bearer_ Number
ctrl_ind><dsm_ipv6_home_
Numberagent_addr_req>

NumberNumberBoolean indicating IPv4 address allocation via DHCPv4

NumberBoolean indicating P-CSCF IPv4 Address Request. This is as per P-CSCF Server
Discovery. See 3GPP TS 29.061 [113] V8.7.0.
Boolean indicating DNS Server IPv4 Address Request. This is as per DNS Server
Discovery. See 3GPP TS 29.061 [113] V8.7.0.
Boolean indicating MSISDN Request. This is as per MSISDN notification procedure.
See 3GPP 24.008 [12] Sec 6.4.
Boolean indicating IFOM (IP Flow Mobility and Seamless Offload) support request
Boolean indicating IPv4 MTU (Maximum Transmission Unit) request

NumberNumber<ifom_support_req> Number<ipv4_mtu_req>
NumberUBX-13002752 - R67

When this string is set with some data, the Boolean's in the +UPCO set command
are neglected.
Boolean indicating IM CN Subsystem Signaling Flag, where the PDP context is to be
used for IMS Signaling purpose. This is as per 3GPP 27.060 [16] Sec. 13.4.
Boolean indicating DNS Server IPv6 Address Request. This is as per DNS Server
Discovery. See 3GPP TS 29.061 [113] V8.7.0.
MS Support of Network Requested Bearer Control Indicator
Boolean indicating DSMIPv6 Home Agent Address Request. This is for obtaining theIPv6 address corresponding to a DSMIPv6 HA address (see 3GPP TS 24.303 [114] and3GPP TS 24.327 [115]).
Boolean indicating DSMIPv6 Home Network Prefix Request. This is for obtaining theIPv6 Home Network Prefix (see 3GPP TS 24.303 [114] and 3GPP TS 24.327 [115]).
Boolean indicating DSMIPv6 IPv4 Home Agent Address Request. This is for obtaining
the IPv4 address corresponding to a DSMIPv6 IPv4 Home Agent address (see 3GPP
TS 24.303 [114] and 3GPP TS 24.327 [115]).
Boolean indicating IP address allocation via NAS signalling<dsm_ipv6_home_
Numbernw_prefi_req><dsm_ipv6v4_home_ Number
agent_addr_req><ip_addr_alloc_nas_
signalling><ipv4_addr_alloc_
dhcpv4><pcscf_ipv4_addr_
req><dns_server_ipv4_
addr_req><msisdn_req>

Description
Defines the command mode to configure the PCO properties:• 1: set the PCO properties for a specific <cid>; the PCO will be used in PDP context
activation• 2: get the PCO properties for a specific <cid>, i.e. the PCO of a PDP context received
from the NW in TNV (Tag Name Value) format• 3: enable +UPCOI indication• 4: disable +UPCOI indication
PDP context id for which the PCO properties are to be set or fetched
String in hexadecimal format containing Configuration protocol options list's
Container Information from MS to Network. The string is basically a hexadecimal
representation from octet w+1 of Protocol configuration options IE (see 3GPP TS
24.008 [12] Protocol configuration options, Table 10.5.154 for more details) and up to
the last byte of Configuration protocol options list. The first 3 bytes of the Protocol
configuration options IE are added by the cellular protocols. The maximum length is
250 characters.
Boolean indicating the P-CSCF IPv6 Address Request. This is as per P-CSCF Server
Discovery. See 3GPP TS 29.061 [113] V8.7.0. s a boolean indicating MS support of
Network Requested Bearer Control indicator.

18 Packet switched data services

Page 389 of 1001

u-blox cellular modules - AT commands manual

Parameter
<Tag>

Type
Number<Number_of_values> String

Description•

0: <ImCN_Tag> indicates IM CN signaling. If present the <value> in the TNV has
information about IM CN Subsytem signaling flag information.
• 1: <PolCtrlRejCode> indicates DSMIPv6 IPv4 Home Agent Address Request. Thisis for obtaining the IPv4 address corresponding to a DSMIPv6 IPv4 Home Agentaddress (see 3GPP TS 24.303 [114] and 3GPP TS 24.327 [115]).
• 2: <BearerControlMode_Tag> is the bearer control mode.
• 3: <DSMIPv6Haar_Tag> is the DSMIPv6 Home agent address.
• 4: <DSMIPv6v4Haar_Tag> is the DSMIPv6 IPv4 Home agent address.
• 5: <DSMIPv6Hnpr_Tag> is the Home network prefix address.
• 6: <DnsIpv4addr_Tag> is the DNS server IPv4 address. This will include primary andsecondary DNS IPv4 addresses. <Value> field contains Primary IPv4 address as thefirst value parameter. Subsequent values if present (<Number_of_values> > 1) willcontain the secondary IPv4 addresses.
• 7: <DnsIPv6Addr_Tag> is the DNS address of the server(IPv6). This will include
primary and secondary DNS IPv6 addresses. <Value> field contains Primary IPv6
address as the first value parameter. Subsequent values if present (<Number_of_
values> > 1) will contain the secondary IPv6 addresses.
• 8: <PcscfIPv4_addr_Tag> is the P-CSCF IPv4 address. This will include primary andsecondary P-CSCF IPv4 addresses. <Value> field contains Primary IPv4 address as
the first value parameter. Subsequent values if present (<Number_of_values> > 1)
will contain the secondary IPv4 addresses.
• 9: <PcscfIPv6_addr_Tag> is the P-CSCF IPV6 address. This will include primary andsecondary P-CSCF IPv6 addresses. <Value> field contains Primary IPv6 address as
the first value parameter. Subsequent values if present (<Number_of_values> > 1)
will contain the secondary IPv6 addresses.
• 10: <MSISDN_Tag> is the MSISDN info.
• 11: <pco_container_Tag> is a hexadecimal string representation of the Network
Operator Specific Container Information containing only information related tocontainer ID FF00H to FFFFH provided by the Network to the MS. See the 3GPP
24.008 v9 [12] section 10.5.6.3 (Table 10.5.154,Network to MS direction)• 12: <ifom_support_flag_Tag> represents the IP Flow Mobility and Seamless
offloading support flag.
• 13: <ipv4_mtu_info_Tag> represents the IPv4 MTU content.
IPv6 address obtained on LTE will be prefixed with a constant 8 byte address"FE.80.00.00.00.00.00.00" if network has not provided.
In the TNV, it indicates how many <Value> parameters corresponding to <Tag> arepresent. The parameters will be comma-separated.

18.6 IPv6 configuration +UDCONF=66+UDCONF=66
Modules
Attributes

TOBY-L2 MPCI-L2
SARA-U2 LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
NVM
No
-

Error reference+CME Error

18.6.1 Description
Configures the IPv6 support. If <IPv6_conf>=3 (IPv6 interface identifier randomization) it is mandatory toprovide the <IID_mode> parameter.
If IPv6 is not supported, also IPv4v6 is not supported.
The configuration will be effective at the next module power-on.

18.6.2 Syntax
Type
SyntaxIPv6 configuration
Set
AT+UDCONF=66,<IPv6_conf>

Response

ExampleOK

AT+UDCONF=66,1
OK

UBX-13002752 - R67

18 Packet switched data services

Page 390 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UDCONF=66

Response+UDCONF: 66,<IPv6_conf>

ExampleAT+UDCONF=66

OK+UDCONF: 66,0OK
IPv6 IID is used by IPSS/TRECK during Neighbor Discovery Protocol (NDP) for Router Solicitation (RS)Set
AT+UDCONF=66,3,<IID_mode>
OK
AT+UDCONF=66,3,1
Read

AT+UDCONF=66,3+UDCONF: 66,3,<IID_mode>

OK
AT+UDCONF=66,3

OK+UDCONF: 66,3,1
OK

18.6.3 Defined values
Parameter<IPv6_conf>

Type
Number<IID_mode>

NumberDescription
IPv6 support enable / disable. Allowed values:• 0: IPv6 support disabled• 1 (factory-programmed value): IPv6 support enabled; IPv6 stateless address
autoconfiguration is available only for LTE (the Router Solicitation is transmitted
at EPS bearer activation)• 2: IPv6 support enabled; IPv6 stateless address autoconfiguration is available
for every RAT (the Router Solicitation is transmitted at PDP context/EPS bearer
activation)• 3: IPv6 interface identifier (IID) randomization
IID randomization mode. Allowed values:• 0 (default value): use the network assigned interface identifier (IID). During the IPv6
configuration the IID is received from the network• 1: use a random IID. According the <AT&T> device requirements 13340 [48] (CDRCDS-183, IPv6 Addressing) a random IID shall be used

18.6.4 Notes
TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03A /TOBY-L280-03S• <IPv6_conf>=3 is not supported.
TOBY-L200-03S / TOBY-L210-03S / TOBY-L280-03S• <IPv6_conf>=2 is not supported by TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L280-03S-00.
TOBY-L200-03S• On TOBY-L200-03S-00 the factory-programmed value of <IPv6_conf> parameter is 0.
TOBY-L201-02S / MPCI-L201-02S• <IPv6_conf>=2, 3 are not supported.
• On TOBY-L201-02S-00, MPCI-L201-02S-00 the factory-programmed value of <IPv6_conf> parameter is
0 in AT&T AT+UMNOCONF configuration, 1 in Verizon.
TOBY-L201-01S / MPCI-L201-01S• <IPv6_conf>=2, 3 are not supported.
• The factory-programmed value of <IPv6_conf> parameter is 0 in AT&T AT+UMNOCONF configuration,
1 in Verizon.
TOBY-L210-62S / TOBY-L210-65S• <IPv6_conf>=2, 3 are not supported.
• The factory-programmed value of <IPv6_conf> parameter is 0.
• If <IPv6_conf>=0 the IPv6 only is disabled while the IPv4v6 protocol remains enabled.
TOBY-L200-00S / TOBY-L200-02S / TOBY-L210-60S / MPCI-L200 / MPCI-L210-60S / MPCI-L210-63S• <IPv6_conf>=2, 3 are not supported.
• The factory-programmed value of <IPv6_conf> parameter is 0.

UBX-13002752 - R67

18 Packet switched data services

Page 391 of 1001

u-blox cellular modules - AT commands manual

TOBY-L210-00S / TOBY-L210-02S / TOBY-L220 / TOBY-L280-02S / MPCI-L210-00S / MPCI-L210-02S /MPCI-L210-03S / MPCI-L220 / MPCI-L280• <IPv6_conf>=2, 3 are not supported.
SARA-U2 / LISA-U2• The factory-programmed value of <IPv6_conf> parameter is 0.
• <IPv6_conf>=2, 3 are not supported.

18.7 Packet switched data configuration +UPSD+UPSD
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo+UPSDANo+CME Error

18.7.1 Description
Sets or reads all the parameters in a specific packet switched data (PSD) profile. The command is used to set
up the PDP context parameters for an internal context, i.e. a data connection using the internal IP stack andrelated AT commands for sockets.
To set all the parameters of the PSD profile a set command for each parameter needs to be issued.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The parameter values set with this command are volatile, but the whole profile can be stored in NVM with
AT+UPSDA=1 command.
In the read command, if only the first parameter is issued, the module returns all the parameters of thegiven PSD profile, and lists them in separated lines.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
The PSD profile configured through the +UPSD AT command is mapped to a <cid> context identifier in the+CGDCONT table (<cid> 8 by default). The mapping between the +UPSD profile and the corresponding<cid> can be configured through <param_tag> = 100. For more details, see Notes.

18.7.2 Syntax
Type
Set

SyntaxAT+UPSD=<profile_id>,<param_tag>,<param_val>

Response
OK

Read

AT+UPSD=<profile_id>,<param_tag>+UPSD: <profile_id>,<param_tag>,<param_val>

ExampleAT+UPSD=0,1,"apn.provider.com"
OK
AT+UPSD=0,1+UPSD: 0,1,"apn.provider.com"

OK
AT+UPSD=<profile_id>

OK+UPSD: <profile_id>,0,<param_val0 AT+UPSD=0>+UPSD: 0,0,0+UPSD: <profile_id>,1,<param_+UPSD: 0,1,"apn.provider.com"
val1>...
+UPSD: 0,2,"username"+UPSD: <profile_id>,x,<param_valx>+UPSD: 0,4,"0.0.0.0"
OK...
+UPSD: 0,19,0
OK

UBX-13002752 - R67

18 Packet switched data services

Page 392 of 1001

u-blox cellular modules - AT commands manual

18.7.3 TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 Defined values
Parameter<profile_id>

Type
Number<param_tag>

NumberUBX-13002752 - R67

Description
PSD profile identifier. Allowed values:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 - 0-6
Allowed values:• 0: protocol type - the allowed values of <param_val> parameter are:o 0 (default value): IPv4o 1: IPv6
o 2: IPv4v6 with IPv4 preferred for internal sockets
o 3: IPv4v6 with IPv6 preferred for internal sockets• 1: APN - <param_val> defines the APN text string, e.g. "apn.provider.com"; themaximum length is 99. The default value is an empty string.
• 2: username - <param_val> is the user name text string for the authentication
phase. The default value is an empty string. The maximum length is 64 characters.
• 3: password - <param_val> is the password text string for the authentication phase.
Note: the AT+UPSD read command with <param_tag> = 3 is not allowed and theread all command does not display it. The maximum length is 64 characters.
• 4: DNS1 - <param_val> is the text string of the primary DNS address. IPv4 DNS
addresses are specified in dotted decimal notation form (i.e. four numbers in
range 0-255 separated by periods, e.g. "xxx.yyy.zzz.www"). IPv6 DNS addresses
are specified in standard IPv6 notation form (2001:DB8:: address compression isallowed). The default value is "0.0.0.0".
• 5: DNS2 - <param_val> is the text string of the secondary DNS address. IPv4
DNS addresses are specified in dotted decimal notation form (i.e. four numbers
in range 0-255 separated by periods, e.g. "xxx.yyy.zzz.www"). IPv6 DNS addresses
are specified in standard IPv6 notation form (2001:DB8:: address compression isallowed). The default value is "0.0.0.0".
• 6: authentication - the <param_val> parameter selects the authentication type:o 0 (default value): noneo 1: PAPo 2: CHAPo 3: automatic selection of authentication type (none/CHAP/PAP)• 7: IP address - <param_val> is the text string of the static IP address given by the
ISP in dotted decimal notation form (i.e. four numbers in range 0-255 separated byperiods, e.g. "xxx.yyy.zzz.www"). The default value is "0.0.0.0". Note: IP address set
as "0.0.0.0" means dynamic IP address assigned during PDP context activation• 8: data compression - the <param_val> parameter refers to the default parameter
named <d_comp> and selects the data compression type:o 0 (default value): offo 1: predefined, i.e. V.42biso 2: V.42bis• 9: header compression - the <param_val> parameter refers to the default
parameter named <h_comp> and selects the header compression type:o 0 (default value): offo 1: predefined, i.e. RFC1144
o 2: RFC1144
o 3: RFC2507
o 4: RFC3095• 100: map the +UPSD profile to the specified <cid> in the +CGDCONT table.
o 0: map the current profile to default bearer PDP ID
o 1: map the current profile to <cid> 1
o 2: map the current profile to <cid> 2
o 3: map the current profile to <cid> 3
o 4: map the current profile to <cid> 4
o 5: map the current profile to <cid> 5
o 6: map the current profile to <cid> 6
o 7: map the current profile to <cid> 7
o 8: map the current profile to <cid> 8
Allowed values:• TOBY-L2 / MPCI-L2 - 0, 1, 100

18 Packet switched data services

Page 393 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• LARA-R2 / TOBY-R2 - 0, 1, 4, 5, 100

18.7.4 SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 DefinedvaluesParameter<profile_id><param_tag>

Type
NumberNumberDescription
PSD profile identifier, in range 0-6
•

•
•
•

•

•

•

•

•

•

•

•

UBX-13002752 - R67

0: protocol type - the allowed values of <param_val> parameter are:o 0 (default value): IPv4o 1: IPv6
o 2: IPv4v6 with IPv4 preferred for internal sockets
o 3: IPv4v6 with IPv6 preferred for internal sockets
1: APN - <param_val> defines the APN text string, e.g. "apn.provider.com"; themaximum length is 99. The default value is an empty string
2: username - <param_val> is the user name text string for the authentication
phase. The default value is an empty string. The maximum length is 64 characters.
3: password - <param_val> is the password text string for the authentication phase.
Note: the AT+UPSD read command with <param_tag> = 3 is not allowed and theread all command does not display it. The maximum length is 64 characters.
4: DNS1 - <param_val> is the text string of the primary DNS address. IPv4 DNS
addresses are specified in dotted decimal notation form (i.e. four numbers in
range 0-255 separated by periods, e.g. "xxx.yyy.zzz.www"). IPv6 DNS addresses
are specified in standard IPv6 notation form (2001:DB8:: address compression isallowed). The default value is "0.0.0.0".
5: DNS2 - <param_val> is the text string of the secondary DNS address. IPv4
DNS addresses are specified in dotted decimal notation form (i.e. four numbers
in range 0-255 separated by periods, e.g. "xxx.yyy.zzz.www"). IPv6 DNS addresses
are specified in standard IPv6 notation form (2001:DB8:: address compression isallowed). The default value is "0.0.0.0".
6: authentication - the <param_val> parameter selects the authentication type:o 0 (default value): noneo 1: PAPo 2: CHAPo 3: automatic selection of authentication type (none/CHAP/PAP)
7: IP address - <param_val> is the text string of the static IP address given by the
ISP in dotted decimal notation form (i.e. four numbers in range 0-255 separated byperiods, e.g. "xxx.yyy.zzz.www"). The default value is "0.0.0.0". Note: IP address set
as "0.0.0.0" means dynamic IP address assigned during PDP context activation
8: data compression - the <param_val> parameter refers to the default parameter
named <d_comp> and selects the data compression type:o 0 (default value): offo 1: predefined, i.e. V.42biso 2: V.42bis
9: header compression - the <param_val> parameter refers to the default
parameter named <h_comp> and selects the header compression type:o 0 (default value): offo 1: predefined, i.e. RFC1144
o 2: RFC1144
o 3: RFC2507
o 4: RFC3095
10: QoS precedence - the <param_val> parameter selects the precedence class:o 0 (default value): subscribedo 1: higho 2: normalo 3: low
11: QoS delay - the <param_val> parameter selects the delay class:o 0 (default value): subscribedo 1: class 1
o 2: class 2
o 3: class 3

18 Packet switched data services

Page 394 of 1001

u-blox cellular modules - AT commands manual

Parameter

UBX-13002752 - R67

Type

Descriptiono 4: best effort• 12: QoS reliability - the <param_val> parameter selects the reliability class:o 0 (default value): subscribedo 1: class 1 (Interpreted as class 2)
o 2: class 2 (GTP Unack, LLC Ack and Protected, RLC Ack)o 3: class 3 (GTP Unack, LLC Unack and Protected, RLC Ack)o 4: class 4 (GTP Unack, LLC Unack and Protected, RLC Unack)o 5: class 5 (GTP Unack, LLC Unack and Unprotected, RLC Unack)o 6: class 6 (Interpreted as class 3)• 13: QoS peak rate - the <param_val> parameter selects the peak throughput inrange 0-9. The default value is 0.
• 14: QoS mean rate - the <param_val> parameter selects the mean throughput inrange 0-18, 31. The default value is 0.
• 15: minimum QoS precedence - the <param_val> parameter selects the acceptablevalue for the precedence class:o 0 (default value): subscribedo 1: higho 2: normalo 3: low• 16: minimum QoS delay - the <param_val> parameter selects the acceptable value
for the delay class:o 0 (default value): subscribedo 1: class 1
o 2: class 2
o 3: class 3
o 4: best effort• 17: minimum QoS reliability - the <param_val> parameter selects the minimum
acceptable value for the reliability class:o 0 (default value): subscribedo 1: class 1 (Interpreted as class 2)
o 2: class 2 (GTP Unack, LLC Ack and Protected, RLC Ack)o 3: class 3 (GTP Unack, LLC Unack and Protected, RLC Ack)o 4: class 4 (GTP Unack, LLC Unack and Protected, RLC Unack)o 5: class 5 (GTP Unack, LLC Unack and Unprotected, RLC Unack)o 6: class 6 (Interpreted as class 3)• 18: minimum QoS peak rate - the <param_val> parameter selects the acceptablevalue for the peak throughput in range 0-9. The default value is 0.
• 19: minimum QoS mean rate - the <param_val> parameter selects the acceptablevalue for the mean throughput in range 0-18, 31. The default value is 0.
• 20: 3G QoS delivery order - the <param_val> parameter selects the acceptable value
for the delivery order:o 0 (default value): subscribedo 1: enableo 2: disable• 21: 3G QoS erroneous SDU delivery - the <param_val> parameter selects theacceptable value for the erroneous SDU delivery:o 0 (default value): subscribedo 1: no detectiono 2: enableo 3: disable• 22: 3G QoS extended guaranteed downlink bit rate - <param_val> is the value forthe extended guaranteed downlink bit rate in kb/s. The default value is 0.
• 23: 3G QoS extended maximum downlink bit rate - <param_val> is the value for theextended maximum downlink bit rate in kb/s. The default value is 0.
• 24: 3G QoS guaranteed downlink bit rate - <param_val> is the value for theguaranteed downlink bit rate in kb/s. The default value is 0.
• 25: 3G QoS guaranteed uplink bit rate - <param_val> is the value for the guaranteed
uplink bit rate in kb/s. The default value is 0.

18 Packet switched data services

Page 395 of 1001

u-blox cellular modules - AT commands manual

Parameter

UBX-13002752 - R67

Type

Description• 26: 3G QoS maximum downlink bit rate - <param_val> is the value for the maximum
downlink bit rate in kb/s. The default value is 0.
• 27: 3G QoS maximum uplink bit rate - <param_val> is the value for the maximum
uplink bit rate in kb/s. The default value is 0.
• 28: 3G QoS maximum SDU size - <param_val> is the value for the maximum SDU
size in octets. The default value is 0.
• 29: 3G QoS residual bit error rate - <param_val> selects the acceptable value for the
residual bit error rate:o 0 (default value): subscribedo 1: 5E2
o 2: 1E2
o 3: 5E3
o 4: 4E3
o 5: 1E3
o 6: 1E4
o 7: 1E5
o 8: 1E6
o 9: 6E8• 30: 3G QoS SDU error ratio - <param_val> selects the acceptable value for the SDU
error ratio:o 0 (default value): subscribedo 1: 1E2
o 2: 7E3
o 3: 1E3
o 4: 1E4
o 5: 1E5
o 6: 1E6
o 7: 1E1• 31: 3G QoS signalling indicator - <param_val> selects the acceptable value for thesignalling indicator:o 0 (default value): subscribedo 1: signalling indicator 1• 32: 3G QoS source statistics descriptor - <param_val> selects the acceptable value
for the source statistics descriptor:o 0 (default value): subscribedo 1: source statistics descriptor 1• 33: 3G QoS traffic class - <param_val> selects the acceptable value for the trafficclass:o 0 (default value): subscribedo 1: conversationalo 2: streamingo 3: interactive
o 4: background• 34: 3G QoS traffic priority - <param_val> selects the acceptable value for the traffic
priority:o 0 (default value): subscribedo 1: priority 1o 2: priority 2
o 3: priority 3• 35: 3G QoS transfer delay - <param_val> is the value for the transfer delay inmilliseconds. The default value is 0.
• 36: 3G minimum QoS delivery order - <param_val> selects the acceptable value forthe delivery order:o 0 (default value): subscribedo 1: enableo 2: disable• 37: 3G minimum QoS erroneous SDU delivery - <param_val> selects the acceptablevalue for the erroneous SDU delivery:o 0 (default value): subscribed

18 Packet switched data services

Page 396 of 1001

u-blox cellular modules - AT commands manual

Parameter

UBX-13002752 - R67

Type

Descriptiono 1: no detectiono 2: enableo 3: disable• 38: 3G minimum QoS extended guaranteed downlink bit rate - <param_val> is thevalue for the extended guaranteed downlink bit rate in kb/s. The default value is 0.
• 39: 3G minimum QoS extended maximum downlink bit rate - <param_val> is thevalue for the extended maximum downlink bit rate in kb/s. The default value is 0.
• 40: 3G minimum QoS guaranteed downlink bit rate - <param_val> is the value forthe guaranteed downlink bit rate in kb/s. The default value is 0.
• 41: 3G minimum QoS guaranteed uplink bit rate - <param_val> is the value for theguaranteed uplink bit rate in kb/s. The default value is 0.
• 42: 3G minimum QoS maximum downlink bit rate - <param_val> is the value for the
maximum downlink bit rate in kb/s. The default value is 0.
• 43: 3G minimum QoS maximum uplink bit rate - <param_val> is the value for the
maximum uplink bit rate in kb/s. The default value is 0.
• 44: 3G minimum QoS maximum SDU size - <param_val> is the value for the
maximum SDU size in octets. The default value is 0.
• 45: 3G minimum QoS residual bit error rate - <param_val> selects the acceptablevalue for the residual bit error rate:o 0 (default value): subscribedo 1: 5E2
o 2: 1E2
o 3: 5E3
o 4: 4E3
o 5: 1E3
o 6: 1E4
o 7: 1E5
o 8: 1E6
o 9: 6E8• 46: 3G minimum QoS SDU error ratio - <param_val> selects the acceptable value
for the SDU error ratio:o 0 (default value): subscribedo 1: 1E2
o 2: 7E3
o 3: 1E3
o 4: 1E4
o 5: 1E5
o 6: 1E6
o 7: 1E1• 47: 3G minimum QoS signalling indicator - <param_val> selects the acceptablevalue for the signalling indicator:o 0 (default value): subscribedo 1: signalling indicator 1• 48: 3G minimum QoS source statistics descriptor - <param_val> selects theacceptable value for the source statistics descriptor:o 0 (default value): subscribedo 1: source statistics descriptor 1• 49: 3G minimum QoS traffic class - <param_val> selects the acceptable value forthe traffic class:o 0 (default value): subscribedo 1: conversationalo 2: streamingo 3: interactive
o 4: background• 50: 3G minimum QoS traffic priority - <param_val> selects the acceptable value forthe traffic priority:o 0 (default value): subscribedo 1: priority 1o 2: priority 2

18 Packet switched data services

Page 397 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Descriptiono 3: priority 3• 51: 3G Minimum QoS transfer delay - <param_val> is the value for the transfer delay
in milliseconds. The default value is 0.

18.7.5 Notes
TOBY-L2 / MPCI-L2• If <param_tag>= 100 (profile to <cid> mapping) the <param_val> default value is 8 (map the current
profile to <cid> 8) and <param_val>=0 is not supported.
• The authentication parameters can be configured by means of the +UAUTHREQ AT command. All theother advanced parameters (e.g. QoS) can be configured using the standard 3GPP AT commands. In bothcases the <cid> to be used shall be the one mapped to the +UPSD profile (through <param_tag> = 100).
• If the default <cid> mapping needs to be changed, modify it prior to any other configuration.
LARA-R2 / TOBY-R2• Set the APN by means of +UPSD AT command before to use <param_tag>=100.
• If <param_tag>= 100 (profile to <cid> mapping) the <param_val> default value is 8 (map the current
profile to <cid> 8) and <param_val>=0 is not supported.
• The authentication parameters can be configured by means of the +UAUTHREQ AT command. All theother advanced parameters (e.g. QoS) can be configured using the standard 3GPP AT commands. In bothcases the <cid> to be used shall be the one mapped to the +UPSD profile (through <param_tag> = 100).
LARA-R203 / LARA-R204 / LARA-R211 / TOBY-R2• LARA-R203-02B-00,
LARA-R203-02B-01,
LARA-R204-02B-00,
LARA-R204-02B-01,
LARA-R211-02B-00,
TOBY-R200-02B-00,
TOBY-R200-02B-01,
TOBY-R200-02B-02,
TOBY-R202-02B-00, TOBY-R202-02B-01, TOBY-R202-02B-02 do not support <param_tag>=4, 5.
SARA-U2 / LISA-U2 / LISA-U1• For the description of the QoS parameters, see 3GPP TS 22.060 [41] and 3GPP TS 23.060 [10].
• Only the IPv4 protocol type for an internal context is supported; hence if <param_tag> = 0 (IP type),<param_val>= 1 (IPv6), 2 (IPv4v6 with IPv4 preferred) and 3 (IPv4v6 with IPv6 preferred) are not supported.
• If <param_tag>=4 or 5, IPv6 DNS address is not supported.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270• If <param_tag>=6, <param_val>=3 (automatic selection of authentication type) is not supported.
LISA-U1• If <param_tag>=6, <param_val> can only assume the value 2 (CHAP).
• If <param_tag>=6, <param_val>=3 (automatic selection of authentication type) is not supported.
SARA-G340 / SARA-G350 / LEON-G1• For the description of the QoS parameters, see 3GPP TS 22.060 [41] and 3GPP TS 23.060 [10].
• For <param_tag> = 0 (IP type), values 1 (IPv6), 2 (IPv4v6 with IPv4 preferred) and 3 (IPv4v6 with IPv6
preferred) are not supported.
• The maximum length of <param_val> is 30 if <param_tag> is equal to 2 or 3.
• If <param_tag>=4 or 5, IPv6 DNS address is not supported.
• If <param_tag>=6, <param_val>=3 (automatic selection of authentication type) is not supported.
• If <param_tag>=8, <param_val>=2 is not supported.
• If <param_tag>=9, <param_val>=2, 3 and 4 are not supported.
• If <param_tag>=12 (or 17) and <param_val>=1 means GTP Ack, LLC Ack and Protected, RLC Ack.
• If <param_tag>=12 (or 17) <param_val>=6 is not supported.
• The values of <param_tag> greater than 19 are not supported.
SARA-G4• For the description of the QoS parameters, see 3GPP TS 22.060 [41] and 3GPP TS 23.060 [10].
• For <param_tag> = 0 (IP type), value 3 (IPv4v6 with IPv6 preferred) is not supported.
• The maximum length of <param_val> is 30 if <param_tag> is equal to 2 or 3.

UBX-13002752 - R67

18 Packet switched data services

Page 398 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•
•
•
•

If <param_tag>=4 or 5, IPv6 DNS address is not supported.
If <param_tag>=6, <param_val>=3 (automatic selection of authentication type) is not supported.
If <param_tag>=8, <param_val>=2 is not supported.
If <param_tag>=9, <param_val>=2, 3 and 4 are not supported.
If <param_tag>=12 (or 17) and <param_val>=1 means GTP Ack, LLC Ack and Protected, RLC Ack.
If <param_tag>=12 (or 17) <param_val>=6 is not supported.
The values of <param_tag> greater than 19 are not supported.

18.8 Packet switched data action +UPSDA+UPSDA
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNoNo
Yes
Up to 3 min+CME Error

18.8.1 Description
Performs the requested action for the specified PSD profile.
The command can be aborted. When a PDP context activation (<action>=3) or a PDP context deactivation(<action>=4) is aborted, the +UUPSDA URC is provided. The <result> parameter indicates the operation result.
Until this operation is not completed, another set command cannot be issued.
The +UUPSDD URC is raised when the data connection related to the provided PSD profile is deactivated either
explicitly by the network (e.g. due to prolonged idle time) or locally by the module after a failed PS registration
procedure (e.g. due to roaming) or a user required detach (e.g. triggered by AT+COPS=2).
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
The PSD profile configured through the +UPSD AT command is mapped to a <cid> in the +CGDCONT table(<cid> 8 by default).
If the <cid> has been already activated through the +CGACT command (or if the context is enabled bydefault in LTE network), it is not mandatory to trigger the +UPSDA activation command (this action isstill suggested).
If the activation command is triggered for an already active data context, no new activation will be
performed.
It is strongly discouraged a mixed use of +UPSDA and +CGACT commands for the internal profile
activation.
TOBY-L2 / MPCI-L2
The command cannot be aborted.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
The +UUPSDA URC is always raised when the PSD profile is activated.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
When a <profile_id> is mapped to and already active <cid>, the activation command (<action>=3) may faildue to the following situations:
1.

2.

The APN configured with +UPSD does not match the the mapped <cid>'s APN (see +CGDCONT AT
command). When this error is detected, the final result code will be "+CME ERROR: 4000" if CMEE=
1 or "+CME ERROR: APN configuration mismatch" if +CMEE=2
The protocol type specified with the +UPSD AT command does not match with the PDP type of the
mapped <cid> configured through the +CGDCONT AT command. To avoid this error, apply these
mapping rules:• +UPSD protocol type 0 maps to +CGDCONT PDP type "IP"• +UPSD protocol type 1 maps to +CGDCONT PDP type "IPV6"• +UPSD protocol types 2 and 3 map to +CGDCONT PDP type "IPV4V6"

UBX-13002752 - R67

18 Packet switched data services

Page 399 of 1001

u-blox cellular modules - AT commands manual

When this error is detected, the final result code will be "+CME ERROR: 4001" if +CMEE=1 or "+CME
ERROR: IP type configuration mismatch" if +CMEE=2
LARA-R2 / TOBY-R2
During the activation command (<action>=3) an error result code is provided when the PDP type specified
with the +UPSD AT command (e.g. "IPV4V6") does not match with the PDP type assigned by the network(e.g. "IPV4"). In this case change the PDP type or rely on the +CGACT AT command to establish the PDP
context/EPS bearer.

18.8.2 Syntax
Type
Set

SyntaxAT+UPSDA=<profile_id>,<action>

Response
OK

ExampleAT+UPSDA=2,1
OK

URC
URC

+UUPSDD: <profile_id>+UUPSDA: <result>[,<ip_addr>]

18.8.3 Defined values
Parameter<profile_id><action>Type
NumberNumberDescription
PSD profile identifier, in range 0-6
•
•
•
•
•

<result>

Number<ip_addr>

String0: reset; it clears the specified profile resetting all the parameters to their factoryprogrammed values
1: store; it saves all the parameters in NVM
2: load: it reads all the parameters from NVM
3: activate; it activates a PDP context with the specified profile, using the current
parameters
4: deactivate; it deactivates the PDP context associated with the specified profile••

0: action successful
Different values mean an unsuccessful action (the codes are listed in the Appendix
A.1)
The IP address assigned to the activated PDP context.

18.8.4 Notes
•
•

•
•

Only one profile can be activated at the same time. The PDP context activation on more than one profileat the same time is not supported.
The number of PDP contexts defined with AT+CGDCONT plus the number of contexts activated with
+UPSDA cannot exceed three. Any further request to define a context with AT+CGDCONT or to activate
a context with +UPSDA generates an error result code.
In case of remote deactivation of the PDP context associated with a PSD profile, the URC is sent to the
TE to inform the user, otherwise the user should deactivate the PDP context after the usage.
In case of PDP deactivation (triggered by either network or the user) all the sockets that have been createdwill automatically be closed.

SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• If the activation command is triggered for an already active data context, no new activation will be
performed and the new activation command returns an error result code. If the deactivation command istriggered for a not active data context, the deactivation command returns an error result code.
• The command shall not be aborted before the expected maximum response time of 180 s or before the+UUPSDA URC (if supported) has been received. If aborted, the requested procedure (e.g. the PS data call
activation or deactivation) will not be stopped, hence it will not be possible for the application processor
to clearly understand when it is finished. The information about the active PDP context may also be polled
by means of the +UPSND AT command, where supported.
• The <ip_addr> parameter in +UUPSDA URC is not present.
SARA-U2 / LISA-U2 / LISA-U1• If the <action>=3 (activate) the <cid> of the PDP context is set to 31 or a subsequent number if a BIP
session is ongoing.

UBX-13002752 - R67

18 Packet switched data services

Page 400 of 1001

u-blox cellular modules - AT commands manual

LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S / LISA-U1• The command cannot be aborted.
• The +UUPSDA URC is not supported.
SARA-G340 / SARA-G350 / LEON-G1• If the <action>=3 (activate) the <cid> of the PDP context is set to 4.
LEON-G100-06S• The command cannot be aborted.
• The +UUPSDA URC is not supported.
• In case of PDP deactivation (triggered by either network or the user), it is up to the user or theapplication to close all the sockets that have been created and are still open.

18.9 Packet switched network-assigned data +UPSND+UPSND
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

Attributes

18.9.1 Description
Returns the current (dynamic) network-assigned or network-negotiated value of the specified parameter forthe active PDP context associated with the specified PSD profile.

18.9.2 Syntax
Type
Set

SyntaxAT+UPSND=<profile_id>,<param_tag>

Response
Example+UPSND: <profile_id>,<param_tag>, AT+UPSND=2,0<dynamic_param_val>+UPSND: 2,0,"151.9.78.170"
OKOK

18.9.3 Defined values
Parameter<profile_id><param_tag>

Type
NumberNumberDescription
PSD profile identifier, in range 0-6
Index representing a network-assigned or network-negotiated parameter:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

UBX-13002752 - R67

0: IP address: dynamic IP address assigned during PDP context activation;
1: DNS1: dynamic primary DNS address;
2: DNS2: dynamic secondary DNS address;
3: QoS precedence: network assigned precedence class of the QoS;
4: QoS delay: network assigned delay class of the QoS;
5: QoS reliability: network assigned reliability class of the QoS;
6: QoS peak rate: network assigned peak rate value of the QoS;
7: QoS mean rate: network assigned mean rate value of the QoS
8: PSD profile status: if the profile is active the return value is 1, 0 otherwise
9: 3G QoS delivery order
10: 3G QoS erroneous SDU delivery
11: 3G QoS extended guaranteed downlink bit rate
12: 3G QoS extended maximum downlink bit rate
13: 3G QoS guaranteed downlink bit rate
14: 3G QoS guaranteed uplink bit rate
15: 3G QoS maximum downlink bit rate
16: 3G QoS maximum uplink bit rate

18 Packet switched data services

Page 401 of 1001

u-blox cellular modules - AT commands manual

ParameterType<dynamic_param_val>

StringDescription• 17: 3G QoS maximum SDU size
• 18: 3G QoS residual bit error rate
• 19: 3G QoS SDU error ratio• 20: 3G QoS signalling indicator• 21: 3G QoS source statistics descriptor• 22: 3G QoS traffic class• 23: 3G QoS traffic priority• 24: 3G QoS transfer delay
Network-assigned or network-negotiated value of the parameter specified in<param_tag>

18.9.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• The supported <param_tag>s are:o 0: IP address queryo 8: PSD profile status
SARA-G4 / SARA-G340 / SARA-G350 / LEON-G1• The values of <param_tag> greater than 8 are not supported.

18.10 Read PDP context DNS information +UDCONF=11+UDCONF=11
Modules
Attributes

SARA-U201 LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

18.10.1 Description
Returns the DNS server IP addresses (the secondary one will be provided only if assigned by the network) for
all active PDP contexts.
In case the <PDP_type>="IPV4V6", for each <cid> two rows will be printed: the first one will contain the
IPv4 DNS addresses, the second one the IPv6 DNS addresses.

18.10.2 Syntax
Type
Read

SyntaxAT+UDCONF=11

Response[+UDCONF: 11,<cid>,<DNS_prim_
addr>[,<DNS_sec_addr>][+UDCONF: 11,<cid>,<DNS_prim_
addr>[,<DNS_sec_addr>]

ExampleAT+UDCONF=11+UDCONF: 11,1,"192.168.209.199","192.168.209.200"[...]]]+UDCONF: 11,2,"192.168.209.199","192.168.209.200"

OKOK

18.10.3 Defined values
Parameter<cid><DNS_prim_addr><DNS_sec_addr>

UBX-13002752 - R67

Type
NumberStringStringDescription
See <cid>
IP address of the primary DNS server
IP address of the secondary DNS server

18 Packet switched data services

Page 402 of 1001

u-blox cellular modules - AT commands manual

18.11 Dynamic DNS request +UDNS+UDNS
Modules

TOBY-L4
LARA-R2 TOBY-R2
SyntaxPIN required
full
Yes

Attributes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.11.1 Description
Enables / disables a dynamic DNS (Domain Name Service) request before the PDP context/EPS bearer
activation. After the activation of the PS data connection (triggered e.g. via +CGACT, dial-up, +UPSDA, or
established during the LTE attach procedure), the DNS addresses of all activated PDP contexts/EPS bearers
are listed in the information text response to the read command. Also the defined but not active contexts arelisted; in this case the DNS addresses are "0.0.0.0".
The factory programmed behavior is to request DNS addresses of the same PDP type of the related <cid>. If
the PDP type is not configured, no PCO will be sent and thus no DNS servers will be configured. For example,
on an IPv4 configured PDP context, IPv4 DNS address will be requested to the network.
Additional DNS configurations can be retrieved / configured with the +UPCO AT command.

18.11.2 Syntax
Type
Set

SyntaxAT+UDNS=<cid>,<mode>

Response
OK

Read

AT+UDNS?

[+UDNS: <cid>,<primary_DNS>,<secondary_DNS>

ExampleAT+UDNS=1,1
OK+UDNS: 2,"8.8.8.8","8.8.4.4"
OK[+UDNS: <cid>,<primary_DNS>,<secondary_DNS>[...]]]Test

AT+UDNS=?

OK+UDNS: (list of supported <cid>s),(list of supported <mode>s)+UDNS: (1-11),(0-3)
OKOK

18.11.3 Defined values
Parameter<cid><mode>Type
StringNumber<primary_DNS>

String<secondary_DNS>

StringDescription
See <cid>.
Allowed values:• 0: disable the dynamic DNS request• 1: enable the dynamic DNS request (IPv4)• 2: enable the dynamic DNS request (IPv6)• 3: enable the dynamic DNS request (IPv4v6)
IP address of the primary DNS server. See <PDP_addr> for a detailed parameter
description. The default DNS address is "0.0.0.0".
IP address of the secondary DNS server. See <PDP_addr> for a detailed parameter
description. The default DNS address is "0.0.0.0".

18.11.4 Notes•

The IPv6 address obtained on the LTE network will be prefixed with a constant 8 byte address"FE.80.00.00.00.00.00.00" if the network has not been provided.

TOBY-L4• The IPv4 DNS request are contained in the IPCP component (Primary and Secondary DNS server) and in
the PCO component, while the IPv6 DNS request is contained in the PCO component.

UBX-13002752 - R67

18 Packet switched data services

Page 403 of 1001

u-blox cellular modules - AT commands manual•

The +UDNS AT command is typically used to add options. However, on the bases of the following DNS
request transition table, the option NO_TYPE can be used to remove all DNS requests of the related <cid>.
Current DNS request
NO_TYPE
IPv4
IPv6
IPv4v6

IPv4 (IN)IPv4
IPv4
IPv4v6
IPv4v6

IPv6 (IN)IPv6
IPv4v6IPv6
IPv4v6

IPv4v6 (IN)IPv4v6
IPv4v6
IPv4v6
IPv4v6

NO_TYPE (IN)
NO_TYPENO_TYPENO_TYPENO_TYPE

Table 28: DNS request transition table

18.12 Quality of service profile (requested) +CGQREQ+CGQREQ
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.12.1 Description
Allows the DTE to specify the QoS (Quality of Service) profile requested from the Network during the PDP
context activation procedure. The set command specifies the QoS profile for the context identified by the <cid>parameter. When set command is used with only <cid> parameter, it sets all requested QoS parameters forthe given profile to their default value 0 (subscribed QoS).
The command defines a PDP context having <PDP_type> set to "IP", <apn> set to "" and with the specified<cid>, if a PDP context with the specified <cid> was not already defined by +CGDCONT AT command.
TOBY-L4 / TOBY-L2 / MPCI-L2
After the PDP context activation, the information text response to the read command provides theconfiguration negotiated with the network (similarly to +CGTFTRDP and +CGCONTRDP AT commands).
If not specified the following values are assumed:• <cid>:1• <precedence>: 0• <delay>: 0• <reliability>: 0• <peak>: 0• <mean>: 0

18.12.2 Syntax
Type
Set

Read

Test

SyntaxResponse
AT+CGQREQ=[<cid>[,OK<precedence>[,<delay>[,reliability>[,<peak>[,<mean>]]]]]]
AT+CGQREQ?
+CGQREQ: <cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>
AT+CGQREQ=?

OK+CGQREQ: <PDP_type>,(list of
supported <precedence>s),(listof supported <delay>s),(list of
supported <reliability>s), (listof supported <peak>s),(list of
supported <mean>s)

ExampleAT+CGQREQ=1,1,1,1,1,1
OK+CGQREQ: 1,1,1,1,1,1
OK+CGQREQ: "IP",(0-3),(0-4),(0-5),(09),(0-18,31)
OK[+CGQREQ: <PDP_type>,(list of
supported <precedence>s),(listof supported <delay>s),(list of
supported <reliability>s), (listof supported <peak>s),(list of
supported <mean>s)]

UBX-13002752 - R67

18 Packet switched data services

Page 404 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse[...]]

ExampleOK

18.12.3 Defined values
Parameter<cid><PDP_type><precedence>

Type
NumberStringNumber<delay>Number<reliability><peak><mean>

NumberNumberNumberDescription
See <cid>
See <PDP_type>
Precedence class (for the description see the +UPSD command description), it canassume the values:• 0: network subscribed• 1: high priority• 2: normal priority• 3: low priority
Delay class according to 3GPP TS 24.008 [12] (QoS) (for the description see the+UPSD command description).
Reliability class (see the +UPSD command description).
Peak throughput class (for the description see the +UPSD command description).
Mean throughput class (for the description see the +UPSD command description).

18.12.4 Notes
SARA-G4• The <cid> parameter is mandatory.
• Define the <cid> context by means of the +CGDCONT AT command before to issue the +CGQREQ set
command.
• The information text response to the read command provides the status of all the <cid> contexts
including also the not defined contexts.

18.13 Quality of service profile (minimum acceptable)+CGQMIN+CGQMIN
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.13.1 Description
DTE specifies a minimum acceptable QoS (Quality of Service) profile which is checked by the MT against thenegotiated QoS profile returned by the network during the PDP context activation procedure.
The set command specifies a QoS profile for the context identified by the <cid> parameter. The QoS profile
consists in a set of parameters, each one is configurable. When the set command is used with only <cid>parameter, the minimum acceptable QoS profile for the given context is undefined. In this case no check is
made against the negotiated QoS profile during PDP context activation.
The command defines a PDP context having <PDP_type> set to "IP", <apn> set to "" and with the specified<cid>, if a PDP context with the specified <cid> was not already defined by +CGDCONT AT command.
If not specified the following values are assumed:• <cid>: 1• <precedence>: 3• <delay>: 4• <reliability>: 5• <peak>: 1• <mean>: 1

UBX-13002752 - R67

18 Packet switched data services

Page 405 of 1001

u-blox cellular modules - AT commands manual

18.13.2 Syntax
Type
Set

SyntaxResponse
AT+CGQMIN=[<cid>[,OK<precedence>[,<delay>[,reliability>[,<peak>[,<mean>]]]]]]
AT+CGQMIN?
+CGQMIN: <cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>

Read

Test

OK
+CGQMIN: <PDP_type>,(list of
supported <precedence>s),(listof supported <delay>s),(list of
supported <reliability>s), (listof supported <peak>s),(list of
supported <mean>s)

AT+CGQMIN=?

ExampleAT+CGQMIN=1,1,1,1,1,1
OK+CGQMIN: 1,1,1,1,1,1
OK+CGQMIN: "IP",(0-3),(0-4),(0-5),(0-9),(0-18,31)
OK[+CGQMIN: <PDP_type>,(list of
supported <precedence>s),(listof supported <delay>s),(list of
supported <reliability>s), (listof supported <peak>s),(list of
supported <mean>s)[...]]
OK

18.13.3 Defined values
Parameter<cid><PDP_type><precedence>

Type
NumberStringNumber<delay>Number<reliability><peak><mean>

NumberNumberNumberDescription
See <cid>
See <PDP_type>
Precedence class (for the description see the +UPSD command description), it canassume the values:• 0: network subscribed• 1: high priority• 2: normal priority• 3: low priority
Delay class according to 3GPP TS 24.008 [12] (QoS) (for the description see the+UPSD command description).
Reliability class (see the +UPSD command description).
Peak throughput class (for the description see the +UPSD command description).
Mean throughput class (for the description see the +UPSD command description).

18.14 GPRS attach or detach +CGATT+CGATT
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
Yes

Response time
Up to 3 min

Error reference+CME Error

18.14.1 Description
Register (attach) the MT to, or deregister (detach) the MT from the GPRS service. After this command the MTremains in AT command mode. If the MT is already in the requested state (attached or detached), the commandis ignored and OK result code is returned. If the requested state cannot be reached, an error result code isreturned. The command can be aborted if a character is sent to the DCE during the command execution. Any
active PDP context will be automatically deactivated when the GPRS registration state changes to detached.
The user should not enter colliding requests (e.g. AT+CGATT=1 and AT+CGATT=0) on different
communication ports, because this might cause interoperability issues in case overlapping attach anddetach requests are not handled by the network, and could result in an unpredictable registration
state. Similarly, when notified of a mobile terminated GPRS detach event (e.g. via +CGEV URC), it is

UBX-13002752 - R67

18 Packet switched data services

Page 406 of 1001

u-blox cellular modules - AT commands manual

recommended to wait a few seconds before entering AT+CGATT=0 in order to let the pending attach
procedure (automatically triggered by the module in most cases) successfully end.
TOBY-L4 / LARA-R202 / LARA-R211 / LARA-R280 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1
If MT is configured in class "B" (see the +CGCLASS AT command) and the GSM registration has not
yet been performed, AT+CGATT=1 triggers both GSM and GPRS registration. If the command is aborted
before the PS registration has ended, the CS registration is completed and the MT goes into class "CC".
The deregistration action is carried out even if the command is aborted.

18.14.2 Syntax
Type
Set

SyntaxAT+CGATT=[<state>]

Response
OK

ExampleAT+CGATT=1

Read

AT+CGATT?

+CGATT: <state>

OK+CGATT: 1

Test

AT+CGATT=?

OK+CGATT: (list of supported<state>s)

OK+CGATT: (0-1)
OKOK

18.14.3 Defined values
Parameter<state>Type
NumberDescription
Indicates the state of GPRS attachment:• 0: detached• 1 (default value): attached18.14.4 Notes
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• Unless the MS is detached from GPRS service due to a previously performed GPRS detach, the set
command with <state>=1 triggers a user reselection. In this case a search for the HPLMN or a higher
order PLMN is triggered (for more details see +COPS and 3GPP TS 23.122 [56]).

18.15 Configure the auto attach to PS domain on power on+UCGATT+UCGATT
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

18.15.1 Description
Configures the auto attach to PS domain at the module power on. The PS attach will be triggered in case theuser requires data connectivity. When PDP contexts have been disabled by the module or by the network, thedevice automatically performs the PS detach.
The configuration of the auto attach is stored in the NVM and will be effective at the next power on.
When <mode>=0, the UE will not register on LTE RAT because CS only registration is not supported by the
LTE standard (see +CEMODE command description). On 2G and 3G RAT, the UE will perform registration
on CS domain only.

18.15.2 Syntax
Type
Set

SyntaxAT+UCGATT=<mode>

Response
OK

ExampleAT+UCGATT=1
OK

UBX-13002752 - R67

18 Packet switched data services

Page 407 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UCGATT?

Response+UCGATT: <mode>

Example+UCGATT: 1

Test

AT+UCGATT=?

OK+UCGATT: (list of supported<mode>s)OK+UCGATT: (0-1)
OKOK

18.15.3 Defined values
Parameter<mode>

Type
NumberDescription
Auto attach configuration:• 0: auto attach to PS domain at switch on is disabled• 1 (factory-programmed value): auto attach to PS domain at switch on is enabled

18.15.4 Notes
TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03A /TOBY-L280-03S / MPCI-L200-03S / MPCI-L210-03S / MPCI-L280-03S• The automatic PS detach when all PDP contexts have been deactivated is not supported.

18.16 PDP context activate or deactivate +CGACT+CGACT
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
Yes

Response time
Up to 40-150 s(see below)

Error reference+CME Error

18.16.1 Description
Activates or deactivates the specified PDP context. After the command, the MT remains in AT command mode.
If any context is already in the requested state, the state for the context remains unchanged. If the required
action cannot succeed, an error result code is returned. If the MT is not GPRS attached when the activation ofa PDP context is required, the MT first performs a GPRS attach and then attempts to activate the specified
context.
The maximum expected response time is different whenever the activation or the deactivation of a PDP context
is performed (150 s and 40 s respectively).
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The command can be aborted if a character is sent to the DCE during the command execution: if a PDP
context activation on a specific <cid> was requested, the PDP context deactivation is performed; if amultiple PDP context activation was requested, it is aborted after the pending PDP context activation has
finished.
The deactivation action is carried out even if the command is aborted.
Note that:• TOBY-L4 / LARA-R2 / TOBY-R2 - After having aborted the PDP context activation, the command line is not
immediately returned.
• SARA-U2 / LISA-U2 - After having aborted the PDP context activation, the command line is immediately
returned but the procedure to activate the context is still running and will be completed.
LARA-R2 / TOBY-R2
The read command shows PDP contexts/EPS bearers defined by IMS, BIP and OMA-DM internal clients
but they cannot be activated or deactivated.
TOBY-L4 / LARA-R2 / TOBY-R2
The usage of AT+CGACT=0 without specifying the <cid> parameter is deprecated because it candeactivate also PDP contexts / EPS bearer used by internal clients e.g. BIP and OMA-DM.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1

UBX-13002752 - R67

18 Packet switched data services

Page 408 of 1001

u-blox cellular modules - AT commands manual

AT+CGACT command (both in successful and unsuccessful case) triggers signalling attempts whose
number is internally counted by the SW and limited based on MNO specific thresholds. The AT&T RPM
feature (see also the +URPM AT command) and the Verizon configuration (see the +UMNOCONF AT
command) might cause the AT command to return an error result code when the maximum number ofattempts has been reached. In these cases, the command might become available again after a while.

18.16.2 Syntax
Type
Set

SyntaxAT+CGACT=[<status>[,<cid>[,...]]]

Response
OK

Read

AT+CGACT?

[+CGACT: <cid>,<status>[+CGACT: <cid>,<status>[...]]]OK+CGACT: (list of supported<status>s)

Test

AT+CGACT=?

ExampleAT+CGACT=1,1
OK+CGACT: 1,1
OK+CGACT: (0-1)
OKOK

18.16.3 Defined values
Parameter<status>Type
Number<cid>

NumberDescription
Indicates the state of PDP context activation:• 0: deactivated• 1: activated
See <cid>.

18.16.4 Notes
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• If <cid> is not defined, the command activates or deactivates all the defined PDP contexts.
• The number of PDP contexts defined with AT+CGDCONT plus the number of contexts activated with AT+UPSDA should not exceed the maximum number of definable PDP contexts (e.g. 3 or 11): in that caseany further request to define a context with AT+CGDCONT or to activate a context with AT+UPSDA will
generate an error result code.
• Do not issue this command to configure internal PDP contexts (see +UCSD, +UCSDA and +UCSND AT
commands for establishing a CSD connection and +UPSD, +UPSDA and +UPSND AT commands forestablishing a PSD connection).
LARA-R204• In Verizon configuration (+UMNOCONF: 7), the <cid> parameter shall always be specified when
activating a context, otherwise an error result code is provided.
SARA-G300 / SARA-G310• As the module supports one active PDP context, if more than one PDP context is defined, a request to
activate all defined PDP contexts with <status>=1 and omitted <cid> generates an error result code.
LEON-G100-06S• The command cannot be aborted.
TOBY-L2 / MPCI-L2• If <cid> is not defined, the command activates or deactivates all the defined PDP contexts.
• The number of PDP contexts defined with AT+CGDCONT plus the number of contexts activated with AT+UPSDA should not exceed the maximum number of definable PDP contexts (e.g. 3 or 11): in that caseany further request to define a context with AT+CGDCONT or to activate a context with AT+UPSDA will
generate an error result code.
• Do not issue this command to configure internal PDP contexts (see +UPSD, +UPSDA and +UPSND AT
commands for establishing a PSD connection).
• The AT+CGACT=0 command returns an error result code in LTE network.
• If <cid> parameter is out of range (<cid>=0 or greater than 8), the command activates or deactivates all
the defined PDP contexts.

UBX-13002752 - R67

18 Packet switched data services

Page 409 of 1001

u-blox cellular modules - AT commands manual

TOBY-L210-62S / TOBY-L210-65S• A single data PDP context is allowed.

18.16.5 Examples
Examples of usage of +CGDCONT, +CGACT, +CGPADDR command:
Command sent by the DTE
AT+CMEE=2

DCE response
OK

AT+COPS=0
AT+COPS?

OK+COPS: 0,0,"vodafone IT"

AT+CGDCONT=1,"IP","web.omnitel.it"
AT+CGDCONT=3,"IP","internet"
AT+CGDCONT=2,"IP","mms.vodafone.it"
AT+CGDCONT?

OK
OK
OK
OK

Description
Set the verbose error result
codes

Define several PDP contexts+CGDCONT: 1,"IP","web.omnitel.it","0.0.0.0",0,0Read PDP contexts+CGDCONT: 3,"IP","internet","0.0.0.0",0,0+CGDCONT: 2,"IP","mms.vodafone.it","0.0.0.0",0,0
AT+CGACT=1,1
AT+CGPADDR=1

OK
OK+CGPADDR: 1, "91.80.104.82"

AT+CGPADDR=2

OK+CGPADDR: 2, "0.0.0.0"

AT+CGPADDR=3

OK+CGPADDR: 3, "0.0.0.0"

AT+CGDCONT?

OK+CGDCONT: 1,"IP","web.omnitel.it","91.80.104.82",0,0

Activate the PDP context 1
Show address of the PDP
context 1
Show the address of PDP
context 2
Show the address of PDP
context 3+CGDCONT: 3,"IP","internet","0.0.0.0",0,0+CGDCONT: 2,"IP","mms.vodafone.it","0.0.0.0",0,0
AT+CGACT=0,1

OK
OK

AT+CGDCONT?

+CGDCONT: 1,"IP","web.omnitel.it","0.0.0.0",0,0

Deactivate the PDP context
1+CGDCONT: 3,"IP","internet","0.0.0.0",0,0+CGDCONT: 2,"IP","mms.vodafone.it","0.0.0.0",0,0
AT+CGACT=1

OK
OK

AT+CGDCONT?

+CGDCONT: 1,"IP","web.omnitel.it","91.80.101.207",0,0

Activate all of defined PDP
contexts+CGDCONT: 3,"IP","internet","83.225.114.136",0,0+CGDCONT: 2,"IP","mms.vodafone.it","10.159.135.60",
0,0
AT+CGPADDR=1

OK+CGPADDR: 1, "91.80.101.207"

AT+CGPADDR=2

OK+CGPADDR: 2, "10.159.135.60"

AT+CGACT=0

OK
OK

AT+CGPADDR=2+CGPADDR: 2, "0.0.0.0"
OK

UBX-13002752 - R67

18 Packet switched data services

Show the address of PDP
context 1
Show the address of PDP
context 2
Deactivate all of defined
PDP contexts
Show the address of PDP
context 2Page 410 of 1001

u-blox cellular modules - AT commands manual

Command sent by the DTE
AT+CGPADDR=3

DCE response+CGPADDR: 3, "0.0.0.0"

AT+CGDCONT?

OK+CGDCONT: 1,"IP","web.omnitel.it","0.0.0.0",0,0

Description
Show the address of PDP
context 3+CGDCONT: 3,"IP","internet","0.0.0.0",0,0+CGDCONT: 2,"IP","mms.vodafone.it","0.0.0.0",0,0
OK
OK+CGDCONT: 1,"IP","web.omnitel.it","0.0.0.0",0,0

AT+CGACT=1,2
AT+CGDCONT?

Activate the PDP context 2+CGDCONT: 3,"IP","internet","0.0.0.0",0,0+CGDCONT: 2,"IP","mms.vodafone.it","10.153.123.229",
0,0
OK
OK
+CGDCONT: 1,"IP","web.omnitel.it","0.0.0.0",0,0

AT+CGACT=1,3
AT+CGDCONT?

Activate PDP context 3+CGDCONT: 3,"IP","internet","83.225.171.77",0,0+CGDCONT: 2,"IP","mms.vodafone.it","10.153.123.229",
0,0
OK
OK
Activate the PDP context 1+CGDCONT: 1,"IP","web.omnitel.it","91.80.175.163",0,0

AT+CGACT=1,1
AT+CGDCONT?

+CGDCONT: 3,"IP","internet","83.225.171.77",0,0+CGDCONT: 2,"IP","mms.vodafone.it","10.153.123.229",
0,0
AT+CGACT=0

OK
OK

AT+CGDCONT?

+CGDCONT: 1,"IP","web.omnitel.it","0.0.0.0",0,0

Deactivate all of defined
PDP contexts+CGDCONT: 3,"IP","internet","0.0.0.0",0,0+CGDCONT: 2,"IP","mms.vodafone.it","0.0.0.0",0,0OK

18.17 Control ESM cause 52 handling +UDCONF=12+UDCONF=12
Modules
Attributes

LARA-R202 LARA-R203 LARA-R220 LARA-R280 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted
full
No
NVM
No

Response time-Error reference+CME Error

18.17.1 Description
Enables / disables additional context establishment when SM cause 52 is reported on an IPv4v6 context
activation.
When a new IPv4IPv6 (<PDP_type>="IPV4V6") context activation is requested by means of the +CGACT
command the network might respond with ESM CAUSE 52 (Single Address Bearer only allowed). In thiscase the module will automatically establish a new PDP context with the same properties but with themissing PDP IP type.

18.17.2 Syntax
Type
Set

SyntaxAT+UDCONF=12,<value>

Response
OK

ExampleAT+UDCONF=12,1

Read

AT+UDCONF=12+UDCONF: 12,<value>

OK
AT+UDCONF=12

UBX-13002752 - R67

18 Packet switched data services

Page 411 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example+UDCONF: 12,1
OK

18.17.3 Defined values
Parameter<value>Type
NumberDescription
Allowed values:• 0: disables the additional context activation• 1 (factory-programmed value): enables the additional context activation

18.18 Manual response to a network request for PDP context
activation +CGANS+CGANS
Modules

TOBY-L4
LARA-R2 TOBY-R2
SARA-U201-63B LISA-U200-62S
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Attributes

Response time
Up to 150 s

Error reference+CME Error

18.18.1 Description
Requests the MT to respond to a network request for the packet domain PDP context activation which has
been indicated to the TE by the RING or +CRING URC.
This command is not equivalent to issuing a +CGDATA or +CGACT command after having received a+CRING URC: +CGDATA or +CGACT would not command the MT to acknowledge the network request
indicated by the +CRING URC but would trigger a new independent PDP context activation.

18.18.2 Syntax
Type
Set

SyntaxAT+CGANS=[<response>,[<L2P>,[<cid>]]]

Response
OK

ExampleAT+CGANS=1

Test

AT+CGANS=?

+CGANS: (list of supported<response>s),(list of supported<L2P>s)OK+CGANS: (0,1),("PPP","M-OPT-PPP","M-HEX","M-RAW_IP","M-PPPRELAY")

OK

OK

18.18.3 Defined values
Parameter<response>Type
Number<L2P>

String<cid>

NumberDescription
Response action. Allowed values:• 0 (default value): reject the request• 1: accept and request the PDP context activation
Layer 2 protocol to be used between the DTE and MT; allowed values:• "PPP" (default value)• "M-HEX"• "M-RAW_IP"• "M-OPT-PPP"• SARA-U201-63B / LISA-U200-62S only - "M-PPP-RELAY"
The application on the remote side must support the selected protocol as well.
See <cid>

18.18.4 Notes•

Typically only AT+CGANS=0 or AT+CGANS=1 are needed: the MT will automatically handle the remaining
parameters.

UBX-13002752 - R67

18 Packet switched data services

Page 412 of 1001

u-blox cellular modules - AT commands manual••

If the <L2P> parameter value is unacceptable to the MT, the MT shall return an error result code.
Otherwise, the MT issues the CONNECT IRC and enters V.250 online data state. If the <L2P> is omitted
then the MT will default it to "PPP" if the <PDP_type>="IP" or to "M-PPP-RELAY" if the <PDP_type>="PPP".
If no <cid> is given or if there is no matching context definition, the MT will attempt to activate thecontext using the values for <PDP_type> and <PDP_addr> provided by the network, together with anyother relevant information known to the MT. If the activation is successful, data transfer may proceed.

SARA-U201-63B / LISA-U200-62S• The maximum number of network initiated PDP contexts that can be accepted is 1.
TOBY-L2 / MPCI-L2• Only <L2P>="PPP" value is supported. There is no support for IPv6 over PPP (PPPv6).
SARA-G3 / LEON-G1• <L2P>= "M-OPT-PPP" is not supported.

18.19 Automatic response to a network request for PDP
context activation +CGAUTO+CGAUTO
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U201-63B LISA-U200-62S
SyntaxPIN required
Settings saved Can be aborted
full
Yes
No
No

Response time-Error reference+CME Error

18.19.1 Description
Disables or enables an automatic positive or negative response (auto-answer) to the reception of a
NW-initiated request PDP context activation message. It also provides the control over the use of the V.250
basic commands +CGDATA or S0, A and H for the handling network requests for a PDP context activation. The
setting does not affect the issuing of the RING or +CRING URCs.

18.19.2 Syntax
Type
Set

SyntaxAT+CGAUTO=[<action>]

Response
OK

ExampleAT+CGAUTO=0

Read

AT+CGAUTO?

+CGAUTO: <action>OK+CGAUTO: 1

Test

AT+CGAUTO=?

OK+CGAUTO: (list of supported<action>s)OK+CGAUTO: (0-4)
OKOK

18.19.3 Defined values
Parameter<action>Type
NumberDescription
Auto-answer action. The allowed values are:
•
•
•
•
•

0 (default value): turn off the automatic response for Packet Domain only
1: turn on the automatic response for Packet Domain only
2: modem compatibility mode, Packet Domain only
3 (factory-programmed value): modem compatibility mode, Packet Domain andcircuit switched calls
4: turn on the automatic negative response for Packet Domain only

18.19.4 Notes••

If <action>=0 the packet domain network requests are manually accepted or rejected by +CGANS
commands.
If <action>=1 the packet domain network requests are automatically accepted.

UBX-13002752 - R67

18 Packet switched data services

Page 413 of 1001

u-blox cellular modules - AT commands manual

•

•

•

If <action>=2 the automatic acceptance of the packet domain network requests is controlled by the S0command. The manual control uses the A and H commands, respectively, to accept and reject the packet
domain requests (+CGANS may also be used). The incoming circuit switched calls can be neither manually
nor automatically answered.
For <action>=3 automatic acceptance of both packet domain network requests and incoming circuit
switched calls is controlled by the S0 command. The manual control uses the A and H commands,
respectively, to accept and reject the packet domain requests (+CGANS may also be used).
For <action>=4 the packet domain network requests are automatically rejected.

LARA-R2 / TOBY-R2• The factory-programmed value of <action> parameter is 1.

18.20 Enter data state +CGDATA+CGDATA
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time Error reference
Up to 3 min (<1 +CME Errors for prompt ">"when present)

18.20.1 Description
Causes the MT to set up a data communication channel between the DTE and the PDP network. For the u-blox
specific L2 modes M-HEX and M-RAW_IP, this means performing a GPRS attach and one or more PDP context
activations, if not already done.
If the parameters are accepted (and optionally the PDP context is successfully activated), the MT displays the
CONNECT IRC on the DTE and enters the online data mode, thus allowing data transfer. Other commands
following +CGDATA in the command line will be processed. When the data transfer is completed, the MT
re-enters into command mode and the final result code is displayed on DTE.
In case of error the final result code NO CARRIER or +CME ERROR: <error> is displayed.
If not specified, value 1 is assumed for <cid>.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The session is terminated sending ~+++, which may cause the deactivation, if active, of the PDP context
depending on DTR line status, i.e. on the AT&D setting (see ~+++ behavior and DTR, +++ behavior). Whenusing M-HEX as L2 protocol and AT&D2 is used, the channel is switched back to command mode but the
PDP context remains active.
When using PPP as L2 protocol, no GPRS attach and no PDP context activation are performed until the
PPP on the DTE side starts communication with the PPP on the MT side.
The M-HEX L2 protocol (AT+CGDATA="M-HEX",1) can be used as follows:<int: counter> <int: length[1-1500]> <hex-sequence>[0-9a-fA-F]
cid=<int: cid>+++<CR>
The following table shows some examples:
Example1 200<CR>
5 5<CR>
1 5 31 32 33 34 35<CR>
1 5 1 2 3 4 05<CR>
1 10 31 Q<CR>
cid=2

UBX-13002752 - R67

Description
Send 1 packet with 200 0x2B (fill character)
Send 5 packets with 5 0x2B (fill character)
Send 1 packet with the given contents
Send 1 packet with the given contents
Send 1 packet with 10 0x31
Send packets on cid 2 (this requires two active PDP contexts and the M-HEX L2
protocol entered on <cid> = 1

18 Packet switched data services

Page 414 of 1001

u-blox cellular modules - AT commands manual

Example+++Description
Leave the online mode

A packet is sent if one of the following conditions is met:
• the length field is terminated with <CR>
• the length value is equal to # characters of hex-sequence and it is terminated with <CR>
• the input is terminated with a character not equal to a hex digit and <CR>
The PIN insertion is not mandatory for the local dial-up, started with <cid> set to 100.
This syntax of the command is mainly used to perform regulatory and conformance testing.

18.20.2 Syntax
Type
Set

SyntaxAT+CGDATA=[<L2P>[,<cid>]]

Response
CONNECT

ExampleAT+CGDATA="PPP",1

Test

AT+CGDATA=?

(data transfer starts)+CGDATA: (list of supported<L2P>s)CONNECT+CGDATA: ("PPP","M-HEX","MRAW_IP","M-OPT-PPP")

OK

OK

18.20.3 Defined values
Parameter
<L2P>

Type
StringDescription
Layer 2 protocol to be used between the DTE and MT; allowed values:• "PPP" (default value)• "M-HEX"• "M-RAW_IP"• "M-OPT-PPP"• SARA-U201-63B / LISA-U200-62S only - "M-PPP-RELAY"
The application on the remote side must support the selected protocol as well.

<cid>

NumberSee <cid>.

18.20.4 Notes••

The cid command, which has not to be confused with the <cid> parameter, can be used while in data
mode for switching to a PDP context already active.
The cid command accepts as parameter a <cid> value corresponding to a PDP context already active andhas to be typed in lower-case.

TOBY-L2 / MPCI-L2• Only <L2P>="PPP" value is supported. There is no support for IPv6 over PPP (PPPv6).
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L210-00S /MPCI-L210-60S / MPCI-L210-63S• The OLCM is not supported.
TOBY-L210-62S / TOBY-L210-65S• A single data PDP context is allowed.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the command is not supported.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• On the AUX UART interface, the command is not supported.
SARA-G4• Only <L2P>= "PPP" value is supported.
SARA-G450-01C• On the AUX UART interface, the command is not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 415 of 1001

u-blox cellular modules - AT commands manual

SARA-G3 / LEON-G1• <L2P>= "M-OPT-PPP" is not supported.
• The module does not start in PPP silent mode.
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, the command is not supported.

18.20.5 Usage of +CGDATA command
Command sent by DTE
AT+CMEE=2
AT&D0
AT+CGDCONT=1,"IP","web.omnitel.it"
AT+CGDCONT=2,"IP","internet"
AT+CGACT=1,2
AT+CGDATA="M-HEX",1

DCE response
OK
OK
OK
OK
OK
CONNECT

1 100

DATA

cid=2
~+++

OK
OK
NO CARRIER

Description
Use verbose error result codes
Define two PDP contexts
Activate PDP context 2
Activate PDP context 1 and establish mandatory
L2 protocol between DTE and MT
Send one packet of 100 bytes
Switch to the already activated context 2
Only the first activated context or the last used isclosed18.21 Enter PPP state/GPRS dial-up D*
D*
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time
Up to 3 min

Error reference+CME Error

18.21.1 Description
The V.24 dial command "D", similar to the command with the syntax AT+CGDATA="PPP",<cid>, causes the
MT to perform the necessary actions to establish the communication between the DTE and the external PDP
network through the PPP protocol. This can include performing a PS attach and, if the PPP server on the
DTE side starts communication, PDP context activation on the specified PDP context identifier (if not already
requested by means of +CGATT and +CGACT commands).
If the command is accepted and the preliminary PS procedures have succeeded, the "CONNECT" intermediate
result code is returned, the MT enters the V.25ter online data state and the PPP L2 protocol between the MT
and the DTE is started.
The data session is terminated by one of the following events:• sending ~+++.
• via a DTR transition from ON to OFF.
• sending an LCP Terminate Request.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
For more details, see the Table 22.

18.21.2 TOBY-L2 / MPCI-L2 Local dial-up
If used with <cid>= 100, this command can enable the local dial-up, that establishes a PPP communication
between the DTE and the module through a serial interface (UART, MUX, or CDC-ACM). In this case an active
PDP context is not needed since the DTE is assigned a private IP address.
The local dial-up feature is enabled by performing a dial-up on <cid>= 100. It establishes a PPP communication
between the DTE and the module through a serial interface (UART, MUX, or CDC-ACM). An IP link is created

UBX-13002752 - R67

18 Packet switched data services

Page 416 of 1001

u-blox cellular modules - AT commands manualby assigning private IP addresses to the endpoints. An active PDP context is not needed. The IP traffic is
automatically routed by the module, thus allowing the DTE to communicate with:• the internet through an active PDP context (at least one PDP context/EPS bearer is needed for the IP
connectivity). By default, the first PDP context activated is used to convey the data;• a device connected to the Virtual Ethernet over USB (RNDIS/CDC-ECM);• devices (STA) connected to the Wi-Fi access point (AP) of the cellular module (see Wi-Fi section).
The feature has been studied to work in router mode.
In general no defined / no active context is required to use local dial-up. The local dial-up is in any case able tocommunicate with the interfaces connected to the module IP stack, as for example RNDIS and Wi-Fi interfaces.
The local dial-up feature does not support the OnLine Command Mode (OLCM). Furthermore the DTR ON to
OFF transition and the ~+++ cannot be used to terminate the local dial-up (the procedure described in ~+++
behavior in PSD &D is not applicable).
The PIN insertion is not mandatory for the local dial-up feature.
The local dial-up feature supports only IPv4 connectivity.

18.21.3 Syntax
Type
Set

SyntaxResponse
ATD[<dialing_type_char>]*<dialing_ CONNECT
number>[*[<address>][*[<L2P>](data transfer starts)[*[<cid>]]]]#

ExampleATD*99***1#
CONNECT

18.21.4 Defined values
ParameterType<dialing_type_char> String<dialing_number><address><L2P>

NumberString<cid>

NumberDescription
Optional (legacy) "T" or "P" character indicating the tone dialing or pulse dialing
respectively
List all the supported values
IgnoredLayer 2 protocol to be used between the DTE and MT; allowed values:• "PPP" (default value)• "M-HEX"• "M-RAW_IP"• "M-OPT-PPP"• SARA-U201-63B / LISA-U200-62S only - "M-PPP-RELAY"
The application on the remote side must support the selected protocol as well.
See <cid>

18.21.5 Notes••••

Dial-up with PAP/CHAP authentication is not supported on an already active PDP context that was
activated without authentication.
The context identifier <cid> is mapped to 1 if not specified.
The GPRS dial-up command maps to AT+CGDATA="PPP",<cid>.
If FDN is enabled and FDN check for PS data call is supported by the module, to perform a GPRS dial-up
one of the following entries must be stored in the FDN phonebook: *99#, *99*#, *99**# or *99***#.

TOBY-L2 / MPCI-L2• Only <L2P>="PPP" value is supported. There is no support for IPv6 over PPP (PPPv6). Performing a dial-up
on a IPv6 EPS bearer/PDP context (see +CGDCONTAT command) the command will provide an error result
code and the IP connectivity will not be established.
• Dial-up on an already active <cid> context identifier is not supported if the current AT+UUSBCONF
command setting enables the virtual Ethernet device, since it could disrupt an already active
communication over the USB link. To use the required <cid> the user should manually deactivate it with
AT+CGACT first.

UBX-13002752 - R67

18 Packet switched data services

Page 417 of 1001

u-blox cellular modules - AT commands manual•

The above limitation does not apply to the 'Fairly back-compatible' AT+UUSBCONF configuration. At theend of the PPP session the <cid> will be deactivated regardless of its previous status, if possible: if themodule is registered in LTE network then the last active <cid> context identifier cannot be deactivated.

TOBY-L200-00S / TOBY-L210-00S / MPCI-L200-00S / MPCI-L210-00S• The local dial-up feature is not supported.
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the command is not supported.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• On the AUX UART interface, the command is not supported.
SARA-G4 / SARA-G3 / LEON-G1• <L2P>= "M-OPT-PPP" is not supported.
SARA-G450-01C / SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S /SARA-G350-02X• On the AUX UART interface, the command is not supported.

18.22 Show PDP address +CGPADDR+CGPADDR
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.22.1 Description
Returns a list of PDP addresses for the specified context identifiers. Only defined PDP contexts are displayed.
If the <cid> parameter is omitted, the addresses for all defined contexts are returned.

18.22.2 Syntax
Type
Set

Test

SyntaxAT+CGPADDR=[<cid>[,<cid> [,...]]]

Response+CGPADDR: <cid>,<PDP_addr>

ExampleAT+CGPADDR=1[+CGPADDR: <cid>,<PDP_addr>+CGPADDR: 1,"1.2.3.4"[...]]

OK

OK+CGPADDR: [(list of defined <cid>s)] +CGPADDR: 1,3

AT+CGPADDR=?

OK

OK

18.22.3 Defined values
Parameter<cid><PDP_addr>

Type
NumberNumberDescription
See <cid>
See <PDP_addr>

18.23 GPRS MS class configuration +CGCLASS+CGCLASS
Modules
Attributes

All products
Syntaxfull

PIN required
Yes

Settings saved Can be aborted
No
No

Response time
Up to 3 min

Error reference+CME Error

18.23.1 Description
Forces the detach/attach to the disabled/enabled service.

UBX-13002752 - R67

18 Packet switched data services

Page 418 of 1001

u-blox cellular modules - AT commands manual

The read command gives the current class which does not depend on user settings but on the current
registration state (e.g. on a CS cell only, class CC is returned).
The dial-up connection is not allowed if the module class was set to CC by means of this command.
If the module class was not forced to CC by the user, the dial-up connection is allowed even if the module is notregistered for PS services (e.g. AT+CGATT=0 was entered), as it will trigger a PS registration beforehand.

18.23.2 Syntax
Type
Set

SyntaxAT+CGCLASS=[<class>]

Response
OK

ExampleAT+CGCLASS="B"

Read

AT+CGCLASS?

+CGCLASS: <class>OK+CGCLASS: "B"

Test

AT+CGCLASS=?

OK+CGCLASS: (list of supported<class>s)OK+CGCLASS: ("A","B","CC","CG")OK

OK

18.23.3 Defined values
Parameter<class>Type
StringDescription
GPRS mobile class••••"A" (default value in Iu mode): class-A mode of operation (A/Gb mode), or CS/PS
mode of operation (Iu mode) (highest mode of operation)"B" (default value in A/Gb mode): class B mode of operation (the MT can operate inboth circuit-switched and packet-switched services but not simultaneously)"CC": class CC mode of operation (the MT can operate only in circuit-switched
service)"CG": class CG mode of operation (the MT can operate only in packet-switched
service)18.23.4 Notes••<class>="A" is only supported when in Iu mode.
When in Iu mode (i.e. UMTS RAT), class A and class B have equivalent meanings (both CS and PS services
supported). When in A/Gb mode (i.e. GSM RAT), class-A mode operation is not supported.

TOBY-L2 / MPCI-L2• If the module is set to "CG" class with +CGCLASS command, the manual selection of a forbidden PLMN
shall be triggered with +UCGOPS command; the AT+COPS=1 command cannot be issued for this purpose.
• To change the module class it is needed to deregister it from network e.g. with AT+COPS=2, change theclass type and again register the module on the network.
SARA-G4• To change the module class it is needed to deregister it from network e.g. with AT+COPS=2, change theclass type and again register the module on the network.
• <class>="A" and "CG" are not supported.
SARA-G3 / LEON-G1• To change the module class it is needed to deregister it from network e.g. with AT+COPS=2, change theclass type and again register the module on the network.
• <class>="A" is not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 419 of 1001

u-blox cellular modules - AT commands manual

18.24 GPRS MS class configuration at start up +UCGCLASS+UCGCLASS
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
partialYes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

18.24.1 Description
Sets the startup class. If the class is set to CS only, before activating a PDP context it is necessary to trigger
a PS attach via +CGATT=1 or to change the class to B.
The current MS class will be stored in NVM and used at the next module power on.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

18.24.2 Syntax
Type
Set

SyntaxAT+UCGCLASS=<class>

Response
OK

ExampleAT+UCGCLASS="CC"

Read

AT+UCGCLASS?

+UCGCLASS: <class>OK+UCGCLASS: "B"

Test

AT+UCGCLASS=?

OK+UCGCLASS: (list of supported<class>s)OK+UCGCLASS: ("B","CC")OK

OK

18.24.3 Defined values
Parameter<class>Type
StringDescription••"B" (factory-programmed value): MS class B (the MT supports both circuit-switchedand packet-switched services)"CC": MS class C (the MT supports only circuit switched services)

18.24.4 Notes••

If "CC" is selected, the network selection (+COPS AT command) triggers a registration only for CS
services.
If "CC" is selected, +CGATT=1 forces the registration for PS services (i.e. +UCGCLASS' setting is ignored)

TOBY-L2 / MPCI-L2• The PIN insertion is not mandatory.

UBX-13002752 - R67

18 Packet switched data services

Page 420 of 1001

u-blox cellular modules - AT commands manual

18.25 Device class setting +UCLASS+UCLASS
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

18.25.1 Description
Changes the module's GPRS and EDGE multislot classes (if GPRS and EDGE are supported).
The new configuration cannot be applied if the module is registered on the network for PS services: in thiscase, before changing the multislot class, the user must first trigger a GPRS detach (e.g. via AT+COPS=2 or
AT+CGATT=0); the new multislot class is used starting from the successive GPRS attach. The new multislotclasses are also stored to NVM and used at the next module power on.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.
If <ms_class_GPRS>=0 the default values are set for all the parameters, regardless of the otherparameter settings.

18.25.2 Syntax
Type
Set

Read

SyntaxAT+UCLASS=<ms_class_GPRS>[,<ms_class_EGPRS>[,<ms_class_
DTM_GPRS>[,<ms_class_DTM_
EGPRS>]]]
AT+UCLASS?

Test

AT+UCLASS=?

Response
OK

ExampleAT+UCLASS=10
OK+UCLASS: <ms_class_GPRS>[,<ms_ +UCLASS: 12,12,11,11class_EGPRS>[,<ms_class_DTM_
OKGPRS>[,<ms_class_DTM_EGPRS>]]]OK+UCLASS: (list of supported <ms_class_GPRS>s)[,(list of supported<ms_class_EGPRS>s)[,(list of
supported <ms_class_DTM_
GPRS>s)[,(list of supported <ms_class_DTM_EGPRS>s)]]]+UCLASS: (0-12),(0-12),(0-11),(0-11)
OKOK

18.25.3 Defined values
Parameter<ms_class_GPRS>UBX-13002752 - R67

Type
NumberDescription
GPRS multislot class defined according to 3GPP TS 05.02 [38]:• TOBY-L2 / MPCI-L2 - The allowed values are 0, 10 and 12. The factory-programmed
value is 12• LARA-R2 / TOBY-R2 - The allowed range is 1-12, 30-33, 35-38. The factoryprogrammed value is 33• SARA-U2 / LISA-U2 / LISA-U1 - The allowed range is 0-12. The factory-programmed
value is 12• LISA-U200-00S - The allowed range is 0-33. The factory-programmed value is 12• SARA-G3 / LEON-G1 - The allowed range is 0-10. The factory-programmed value is10• SARA-G4 - The allowed range is 0-12. The factory-programmed value is 12

18 Packet switched data services

Page 421 of 1001

u-blox cellular modules - AT commands manual

ParameterType<ms_class_EGPRS> Number<ms_class_DTM_
GPRS>

Number<ms_class_DTM_
EGPRS>

NumberDescription
EGPRS multislot class defined according to 3GPP TS 05.02 [38]. The default value isthe value set in <ms_class_GPRS>.
• TOBY-L2 / MPCI-L2 - The allowed values are 0, 10 and 12. The factory-programmed
value is 12• LARA-R2 / TOBY-R2 - The allowed range is 1-12, 30-33, 35-38. The factoryprogrammed value is 33• SARA-U2 / LISA-U2 / LISA-U1 - The allowed range is 0-12. The factory-programmed
value is 12• LISA-U200-00S - The allowed range is 0-33. The factory-programmed value is 12• SARA-G4 / SARA-G3 / LEON-G1 - Not supported
DTM GPRS multislot class defined according to 3GPP TS 05.02 [38]. Default value isthe value set in <ms_class_GPRS>.
• LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 / LARA-R280 /TOBY-R200-02B / TOBY-R200-82B / TOBY-R202 - The allowed range is 0, 5, 9, 11,
31-33, 36-38. The factory-programmed value is 33• LARA-R211 / TOBY-R200-42B - The allowed range is 0, 5, 9, 11, 31-33, 36-38. The
factory-programmed value is 0
• SARA-U2 / LISA-U2 - The allowed range is 0-11. The factory-programmed value is 11• TOBY-L2 / MPCI-L2 / LISA-U200-00S / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 Not supported
DTM EGPRS multislot class defined according to 3GPP TS 05.02 [38]. The default
value is the value set in <ms_class_GPRS>.
• LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 / LARA-R280 /TOBY-R200-02B / TOBY-R200-82B / TOBY-R202 - The allowed range is 0, 5, 9, 11,
31-33, 36-38. The factory-programmed value is 33• LARA-R211 / TOBY-R200-42B - The allowed range is 0, 5, 9, 11, 31-33, 36-38. The
factory-programmed value is 0
• SARA-U2 / LISA-U2 - The allowed range is 0-11. The factory-programmed value is 11• TOBY-L2 / MPCI-L2 / LISA-U200-00S / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 Not supported

18.25.4 Notes••

In the set command <ms_class_GPRS>=0 is used to set the maximum supported values.
The GPRS, EGPRS, DTM GPRS and DTM EGPRS multislot classes cannot be independently chosen (someconfigurations are not valid and an error result code is reported: "+CME ERROR: operation not supported"
if +CMEE is set to 2). See the following tables:
Type
E/GPRSDTM E/GPRS

Valid values(1-12)
5, 9,11

Maximum value
12
11

Default value
12
11

Table 29: Multislot classes: valid, maximum and default values for each type
GPRS multislot class(1-12)
30
31
32
33

EGPRS multislot class valid values(1-12)
30, 32, 33
31
30, 32, 33
30, 32, 33

Table 30: EGPRS multislot classes valid values relative to the selected GPRS multislot class
DTM EGPRS/GPRS multislot class
5
9
11

EGPRS/GPRS multislot class valid values(1-12)(1-12)(1-12)

Table 31: EGPRS/GPRS multislot classes valid values relative to the selected DTM EGPRS/GPRS
multislot class

UBX-13002752 - R67

18 Packet switched data services

Page 422 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2 / MPCI-L2• The <ms_class_GPRS>=0 command sets the maximum allowed values.
LISA-U1• The <ms_class_EGPRS> parameter in the set command is mandatory.
• If <ms_class_GPRS>=0 the default values are not set for all the parameters.
LISA-U200-00S• If <ms_class_GPRS>=0 the maximum supported values are set for all parameters, regardless of thesecond parameter's settings.
• If <ms_class_GPRS>=0 the default values are not set for all the parameters.
SARA-G4 / SARA-G3 / LEON-G1• <ms_class_GPRS>=7 is not allowed.
• If <ms_class_GPRS>=0 the default values are not set for all the parameters.

18.26 Packet switched event reporting +CGEREP+CGEREP
Modules
Attributes

All products
Syntaxpartial

PIN required
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.26.1 Description
Configures sending of URCs from MT to the DTE, in case of certain events occurring in the packet switched MTor the network. By means of the <mode> parameter, it is possible to control the processing of the URCs codes
specified within this command. The <bfr> parameter allows to control the effect on buffered codes when the<mode> parameter is set to 1 (discard URCs when V.24 link is reserved) or 2 (buffer URCs in the MT when linkreserved and flush them to the DTE when the link becomes available).

18.26.2 Syntax
Type
Set

SyntaxAT+CGEREP=[<mode>[,<bfr>]]

Response
OK

ExampleAT+CGEREP=1,1

Read

AT+CGEREP?

+CGEREP: <mode>,<bfr>

OK+CGEREP: 0,0

Test

AT+CGEREP=?

URC

UBX-13002752 - R67

OK
OK+CGEREP: (list of supported+CGEREP: (0-2),(0-1)<mode>s),(list of supported <bfr>s)
OK
OK+CGEV: ME PDN ACT <cid>[,+CGEV: NW CLASS "CC"<reason>[,<cid_other>]]+CGEV: ME ACT <p_cid>,<cid>,<event_type>+CGEV: ME PDN DEACT <cid>+CGEV: ME DEACT <PDP_type>,<PDP_addr>,[<cid>]+CGEV: ME DEACT,<p_cid>,<cid>,0+CGEV: ME DEACT <p_cid>,<cid>,<event_type>+CGEV: ME MODIFY <cid>,<change_reason>,<event_type>+CGEV: ME DETACH+CGEV: ME CLASS <class>+CGEV: NW PDN ACT <cid>[,<reason>]+CGEV: NW ACT <p_cid>,<cid>,<event_type>+CGEV: NW PDN DEACT <cid>

18 Packet switched data services

Page 423 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Example+CGEV: NW DEACT <p_cid>,<cid>,0+CGEV: NW DEACT <p_cid>,<cid>,<event_type>+CGEV: NW DEACT <PDP_type>,<PDP_addr>,[<cid>]+CGEV: NW MODIFY <cid>,<change_reason>,<event_type>+CGEV: NW DETACH+CGEV: NW CLASS <class>+CGEV: VZW_SUBS_ACTION_NORMAL (0) - No restriction to data
traffic+CGEV: REJECT <PDP_type>,<PDP_
addr>+CGEV: NW REACT <PDP_type>,<cid>+CGEV: NW ACT <PDP_type>,<cid>

18.26.3 Defined values
Parameter<mode>

Type
Number<bfr>

Number<cid><reason>NumberNumber<cid_other>

Number<p_cid>Number<event_type>

Number<change_reason>

Number<PDP_type><PDP_addr><class>NumberNumberStringUBX-13002752 - R67

Description
Controls the processing of URCs specified within this command. Allowed values:• 0 (default value): buffer URCs in the MT; if the buffer is full the oldest ones will bediscarded• 1: discard URCs when V.24 link is reserved (online); otherwise forward them directly
to the DTE• 2: buffer URCs in the MT when link reserved (online) and flush them to the DTE when
the link becomes available; otherwise forward them directly to the DTE
Controls the effect on buffered codes when <mode> 1 or 2 is entered. Allowed values:• 0 (default value): MT buffer of URCs defined within this command is cleared when<mode> 1 or 2 is entered• 1: MT buffer of URCs defined within this command is flushed to the DTE when<mode> 1 or 2 is entered (OK is given before flushing the codes)
See <cid>
Indicates whether the reason why the context activation request for PDP type IPv4v6
was not granted:• 0: IPv4 only allowed• 1: IPv6 only allowed• 2: single address bearers only allowed• 3: single address bearers only allowed and MT initiated context activation for asecond address type bearer was not successful
Indicates whether the context identifier allocated by MT for an MT initiated context
of a second address type
Numeric parameter that identifies the particular PDP context definition, specified
using +CGDCONT, to which a secondary PDP context definition will be associatedusing +CGDSCONT.
This parameter is only locally valid on the interface TE-MT.
Indicates whether the event is informational or whether the TE has to acknowledge it:• 0: informational event• 1: information request: acknowledgement required
Indicates what kind of change occurred:• 1: TFT only changed• 2: QoS only changed• 3: both TFT and QoS changed
See <PDP_type>
See <PDP_addr>
GPRS mobile class. Allowed values:• "A": class A mode of operation (A/Gb mode), or CS/PS mode of operation (Iu mode)(highest mode of operation)

18 Packet switched data services

Page 424 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• "B": class B (circuit-switched and packet-switched data alternatively supported)• "CG": class C (one service only) in GPRS mode
• "CC": class C (one service only) in circuit-switched (GSM) mode

18.26.4 Notes
TOBY-L4• The detach indication shall be used also for local deactivation of any PDP context/EPS bearer.
TOBY-L2 / MPCI-L2• The PIN insertion is not mandatory.
• <class>= "A" is not supported.
• It is possible to issue the command without "=".
SARA-G4 / SARA-G3 / LEON-G1• <class>= "A" is not supported.

18.26.5 Explanation of URCs
URC
+CGEV: ME PDN ACT <cid>[,<reason>[,<cid_other>]]+CGEV: ME ACT <p_cid>,<cid>,<event_type>+CGEV: ME PDN DEACT <cid>+CGEV: ME DEACT <PDP_type>,<PDP_addr>,[<cid>]+CGEV: ME DEACT,<p_cid>,<cid>,0+CGEV: ME DEACT <p_cid>,<cid>,<event_type>+CGEV: ME MODIFY <cid>,<change_reason>,<event_type>+CGEV: ME DETACH+CGEV: ME CLASS <class>+CGEV: NW PDN ACT <cid>[,<reason>]+CGEV: NW ACT <p_cid>,<cid>,<event_type>+CGEV: NW PDN DEACT <cid>

UBX-13002752 - R67

Remarks
The MT has activated a primary context.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The network has responded to a MT initiated secondary
context activation.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The MT has forced a primary context deactivation.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The MT has forced a context deactivation.
TOBY-L2 / MPCI-L2
Not supported.
The UE has forced a secondary context deactivation.
TOBY-L2 / MPCI-L2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1
Not supported.
The MT has forced a secondary context deactivation.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The MT has forced a context modification.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The mobile station has forced a GPRS detach
The mobile station has forced a change of MT class; thehighest available class is reported.
The network has activated a primary context.
TOBY-L2 / MPCI-L2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1
Not supported.
The network has forced a secondary context activation.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The network has forced a primary context deactivation.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1

18 Packet switched data services

Page 425 of 1001

u-blox cellular modules - AT commands manual

URC+CGEV: NW DEACT <p_cid>,<cid>,0+CGEV: NW DEACT <p_cid>,<cid>,<event_type>+CGEV: NW DEACT <PDP_type>,<PDP_addr>,[<cid>]+CGEV: NW MODIFY <cid>,<change_reason>,<event_type>+CGEV: NW DETACH+CGEV: NW CLASS <class>+CGEV: VZW_SUBS_ACTION_NORMAL (0) - No
restriction to data traffic+CGEV: REJECT <PDP_type>,<PDP_addr>+CGEV: NW REACT <PDP_type>,<cid>+CGEV: NW ACT <PDP_type>,<cid>Remarks
Not supported.
The network has forced a secondary context deactivation.
TOBY-L2 / MPCI-L2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1
Not supported.
The network has forced a secondary context deactivation.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1
Not supported.
The network has forced a context deactivation.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
Not supported.
The network has forced a context modification.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The network has forced a GPRS detach
The network has forced a change of MT class (e.g. due toservice detach); the highest available class is reported.
No restriction to data traffic. The URC is provided only on
Verizon network.
TOBY-L200 / TOBY-L210 / TOBY-L220 / TOBY-L280 /MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280 /LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1
Not supported.
The context activation is rejected.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The network has forced a context re-activation.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.
The network has forced a context activation.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Not supported.

18.27 GPRS network registration status +CGREG+CGREG
Modules

Attributes

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialYes
No
No+CME Error

18.27.1 Description
Configures the GPRS network registration information. Depending on the <n> parameter value, a URC can beissued:• +CGREG: <stat> if <n>=1 and there is a change in the GPRS network registration status in GERAN/UTRAN• +CGREG: <stat>[,<lac>,<ci>[,<AcT>,<rac>]] if <n>=2 and there is a change of the network cell in GERAN/UTRAN

UBX-13002752 - R67

18 Packet switched data services

Page 426 of 1001

u-blox cellular modules - AT commands manual

The parameters <lac>, <ci>, <AcT>, <rac> 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 <AcT>, if available, are returned only when<n>=2 and the MT is registered with the network.
When <n>=2, in UMTS RAT, unsolicited location information can be received if the network sends theUTRAN 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.
If the GPRS MT also supports circuit mode services in GERAN/UTRAN and/or EPS services in E-UTRAN,
the +CREG / +CEREG commands return the registration status and location information for thoseservices.
SARA-G4
The command setting is stored in the personal profile following the procedure described in the Saving AT
commands configuration section.

18.27.2 Syntax
Type
Set

SyntaxAT+CGREG=[<n>]Response
OK

ExampleAT+CGREG=1

Read

AT+CGREG?

If <n>=0 or 1:

OK+CGREG: 0,4+CGREG: <n>,<stat>OKOK
If <n>=2:+CGREG: 2,1,"61EF","7D58A3",2,"14"+CGREG: <n>,<stat>[,<lac>,<ci>[,<AcT>,<rac>]]
Test

AT+CGREG=?

URC

OK

OK
+CGREG: (list of supported <n>s)+CGREG: (0-2)

OK
If <n>=1:

OK+CGREG: 1+CGREG: <stat>If <n>=2:+CGREG: 1,"4E54","44A5"+CGREG: <stat>[,<lac>,<ci>[,<AcT>,<rac>]]

18.27.3 Defined values
Parameter<n>Type
NumberDescription<stat>

Number

•
•
•
•
•
•
•

<lac>

StringUBX-13002752 - R67•••

0 (default value and factory-programmed value): network registration URC disabled
1: network registration URC enabled
2: network registration and location information URC enabled

0: not registered, the MT is not currently searching an operator to register to
1: registered, home network
2: not registered, but MT is currently searching a new operator to register to
3: registration denied
4: unknown (e.g. out of GERAN/UTRAN coverage)
5: registered, roaming
8: attached for emergency bearer services only (see 3GPP TS 24.008 [12] and 3GPP
TS 24.301 [68] that specify the condition when the MS is considered as attached
for emergency bearer services) (applicable only when <AcT> indicates 2,4,5,6)
Two bytes location area in hexadecimal format; it is optionally provided in the URC
and in the response to the read command if <n>=2. The value FFFF means that thecurrent <lac> value is invalid.

18 Packet switched data services

Page 427 of 1001

u-blox cellular modules - AT commands manual

Parameter
<ci>

Type
String<AcT>

Number<rac>

StringDescription
From 2 to 4 bytes cell ID in hexadecimal format; it is optionally provided in the URC
and in the response to the read command if <n>=2. The value FFFFFFFF means thatthe current <ci> value is invalid.
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• 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 <AcT> value is invalid
Allowed values:• TOBY-L4 / TOBY-L200 / TOBY-L210 / TOBY-L280 / MPCI-L200 / MPCI-L210 /MPCI-L280 / TOBY-R200 / SARA-U201 / SARA-U260 / SARA-U270-00S /SARA-U270-00X / SARA-U270-03A / SARA-U270-03S / LISA-U2 - 0, 2, 3, 4, 5, 6
• TOBY-L201 / TOBY-L220-02S / MPCI-L201 / MPCI-L220-02S / LARA-R202 /LARA-R280 / TOBY-R202 / SARA-U270-53S / SARA-U270-73S / SARA-U280 - 2, 4,
5, 6• LARA-R211 - 0, 3
• LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - parameter not supported
One byte routing area in hexadecimal format

18.27.4 Notes••

The DTE application should set a reasonable timer (10 s) when receiving the +CGREG: 3 URC, since thismight be due to the fact that the LTE registration was rejected (SIM not enabled for LTE RAT, wrong APN
during the initial default bearer set-up in the EPS attach procedure and other temporary reject causes).
If the device does not support 2G or 3G RAT, the command will report only <stat>=0, 2 and 4.

TOBY-L4• The PIN insertion is not mandatory before the command execution.
• The URC does not notify access technology information changes that might change in polling; see the+UREG AT command to monitor the RAT changes.
TOBY-L2 / MPCI-L2• The PIN insertion is not mandatory before the command execution.
• The information text response to the read command and the URC will assume these values in these
conditions:o During the initial network searching at the module power-on, the <stat> parameter is 2
o If the module is PS attached to the GSM/UMTS home network, the <stat> parameter is 1
o If the module is registered to E-UTRAN, the <stat> parameter is 4
o In out of coverage state, the <stat> parameter is 4
• <stat>= 8 is not supported.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The PIN insertion is not mandatory before the command execution.
LISA-U1• <rac> parameter is not supported.
SARA-G4 / SARA-G3 / LEON-G1• The PIN insertion is not mandatory before the command execution.
• If GPRS is enabled and +CREG and +CGREG URCs are both enabled too, once the module is registeredand attached then the two URCs are sent out quite at the same time.
• <rac> parameter is not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 428 of 1001

u-blox cellular modules - AT commands manual

SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G1• Equivalent HPLMN for <stat>=1 is not supported: <stat>=5 is indicated in this case.

18.28 Extended Packet Switched network registration status
+UREG
+UREG
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.28.1 Description
Reports the network or the device PS (Packet Switched) radio capabilities.
When the device is not in connected mode, the command reports the network PS (Packet Switched) radio
capabilities of the PLMN where the device is attached to.
When the device is in connected mode, the command reports the PS radio capabilities the device has been
configured.
The set command enables / disables the URC +UREG, generated whenever it is enabled and the capabilities
change.
The read command can be used to query the current PS radio capabilities.

18.28.2 Syntax
Type
Set

Syntax
AT+UREG=<n>

Response
OK

ExampleAT+UREG=1

Read

AT+UREG?

+UREG: <n>,<state>

OK+UREG: 0,3

Test

AT+UREG=?

OK+UREG: (list of supported <n>'s)

OK+UREG: (0-1)

OK+UREG: <state>

OK+UREG: 3

URC

18.28.3 Defined values
Parameter<n>Type
NumberDescription••

0: network registration attach status URC disabled
1: network registration attach status URC +UREG enabled<state>Number

•
•
•
•
•
•
•
•
•
•

0: not registered for PS service
1: registered for PS service, RAT=2G, GPRS available
2: registered for PS service, RAT=2G, EDGE available
3: registered for PS service, RAT=3G, WCDMA available
4: registered for PS service, RAT=3G, HSDPA available
5: registered for PS service, RAT=3G, HSUPA available
6: registered for PS service, RAT=3G, HSDPA and HSUPA available
7: registered for PS service, RAT=4G
8: registered for PS service, RAT=2G, GPRS available, DTM available
9: registered for PS service, RAT=2G, EDGE available, DTM available

18.28.4 Notes
TOBY-L2 / MPCI-L2• <state>= 8 and 9 are not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 429 of 1001

u-blox cellular modules - AT commands manual•

The information text response to the read command and the URC will assume these values in these
conditions:o During the initial network searching at the module power on the <state> parameter is 0
o If the module is registered to E-UTRAN the <state> parameter is 7
o In the out of coverage state the <state> parameter is 0

LISA-U200-00S / LISA-U1• <state>= 8 and 9 are not supported.

18.29 Manual deactivation of a PDP context H
H
Modules

TOBY-L4 TOBY-L200 TOBY-L201 TOBY-L210 TOBY-L220-02S TOBY-L280 MPCI-L200 MPCI-L201
MPCI-L210 MPCI-L220-02S MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G450-01C SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 20 s+CME Error

Attributes

18.29.1 Description
Deactivates an active PDP context with PPP L2 protocol in online command mode. The MT responds with afinal result code. For a detailed description, see the H command description. For additional information about
OLCM, see the AT command settings .
In GPRS online command mode, entered by typing the escape sequence "+++" or "~+++" (see &D), the ATH
command is needed to terminate the connection. Alternatively, in data transfer mode, DTE originated
DTR toggling or PPP disconnection may be used.

18.29.2 Syntax
Type
ActionSyntaxATH

Response
OK

Example18.30 PDP context modify +CGCMOD+CGCMOD
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
partialYes

Settings saved Can be aborted
No
No

Response time
Up to 40 s

Error reference+CME Error

18.30.1 Description
This execution command is used to modify the specified PDP context(s) with respect to QoS profiles and TFT's.
After the command is complete, the MT returns to the V.25 online data state. If the requested modification
for any specified context cannot be achieved, an error result code is returned. If no <cid>s are specified, theactivation form of the command modifies all the active contexts.

18.30.2 Syntax
Type
Set

SyntaxAT+CGCMOD=[<cid>[,<cid>[,,...]]]

Response
OK

Test

AT+CGCMOD=?

+CGCMOD: (list of <cid>s withactive contexts)

ExampleAT+CGCMOD=1
OK

OK

UBX-13002752 - R67

18 Packet switched data services

Page 430 of 1001

u-blox cellular modules - AT commands manual

18.30.3 Defined values
Parameter
<cid>

Type
NumberDescription
See <cid>.

18.30.4 Notes
TOBY-L4• The information text response to the test command lists all the defined <cid> contexts.
TOBY-L2 / MPCI-L2• When changing the QoS of a dedicated EPS/secondary PDP context, TFT settings shall be re-enforced
via +CGTFT before issuing the +CGCMOD AT command.

18.31 3G Quality of service profile (requested) +CGEQREQ+CGEQREQ
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
partialYes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.31.1 Description
Allows the TE to specify the QoS profile that is used when the MT sends an Activate PDP Context Request
message to the network. The set command specifies a profile for the context identified by the <cid>. The
specified profile will be stored in the MT and sent to the network only at activation or MS-initiated modificationof the related context. The command is actually an extension of the commands +CGDCONT and +CGDSCONT.
The QoS profile consists of a number of parameters, each of which may be set to a separate value. The special
form +CGEQREQ=<cid> causes the requested profile related to <cid> to become undefined.
The command defines a PDP context having a <PDP_type> set to "IP", <apn> set to "" and with thespecified <cid>, if a PDP context with the specified <cid> was not already defined by +CGDCONT AT
command.
TOBY-L4 / TOBY-L2 / MPCI-L2
After the PDP context activation, the information text response to the read command provides theconfiguration negotiated with the network (similarly to +CGTFTRDP and +CGCONTRDP AT commands).

18.31.2 Syntax
Type
Set

Read

SyntaxResponse
ExampleAT+CGEQREQ=[<cid>[,<Traffic_
OK
AT+CGEQREQ=1,2,64,64,,,0,320,class>[,<Maximum_bitrate_"1E4","1E5",1,,3,0,0
UL>[,<Maximum_bitrate_DL>[,OK<Guaranteed_bitrate_UL>[,<Guaranteed_bitrate_DL>[,<Delivery_order>[,<Maximum_
SDU_size>[,<SDU_error_ratio>[,<Residual_bit_error_ratio>[,<Delivery_of_erroneous_SDUs>[,<Transfer_delay>[,<Traffic_
handling_priority> [,<Source_
statistics_descriptor> [,<Signalling_
indication>]]]]]]]]]]]]]]
AT+CGEQREQ?
+CGEQREQ: <cid>,<Traffic_+CGEQREQ: 1,2,5760,5760,0,0,0,150
class>,<Maximum_bitrate_0,"1E4","1E5",0,1000,1,0,0
UL>,<Maximum_bitrate_DL>,
OK<Guaranteed_bitrate_UL>,<Guaranteed_bitrate_DL>,<Delivery_order>,<Maximum_SDU_
size>,<SDU_error_ratio>,<Residual_
bit_error_ratio>,<Delivery_of_

UBX-13002752 - R67

18 Packet switched data services

Page 431 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
erroneous_SDUs>,<Transfer_delay>,<Traffic_handling_priority>,<Source_statistics_descriptor>,<Signalling_indication>

Example[+CGEQREQ: <cid>,<Traffic_
class>,<Maximum_bitrate_
UL>,<Maximum_bitrate_DL>,<Guaranteed_bitrate_UL>,<Guaranteed_bitrate_DL>,<Delivery_order>,<Maximum_SDU_
size>,<SDU_error_ratio>,<Residual_
bit_error_ratio>,<Delivery_of_
erroneous_SDUs>,<Transfer_delay>,<Traffic_handling_priority>,<Source_statistics_descriptor>,<Signalling_indication>[...]]Test

OK+CGEQREQ: <PDP_type>,(list of+CGEQREQ: "IP",(0-4),(1-63 in 1 kbps
supported <Traffic_class>s),(liststeps, 64-568 in 8 kbps steps, 576of supported <Maximum_bitrate_
8640 in 64 kbps steps),(1-63 in 1
UL>s),(list of supported <Maximum_ kbps steps, 64-568 in 8 kbps steps,
bitrate_DL>s),(list of supported
576-8640 in 64 kbps steps, 8700<Guaranteed_bitrate_UL>s),
16000 in 100 kbps steps),(1-63 in 1
(list of supported <Guaranteed_kbps steps, 64-568 in 8 kbps steps,
bitrate_DL>s),(list of supported
576-8640 in 64 kbps steps),(1-63 in 1
<Delivery_order>s),(list of supported kbps steps, 64-568 in 8 kbps steps,<Maximum_SDU size>s),(list of
576-8640 in 64 kbps steps, 8700supported <SDU_error_ratio>s),(list 16000 in 100 kbps steps),(0-1),(10of supported <Residual_bit_error_
1500,1502,1510,1520),("1E6","1E5",
ratio>s),(list of supported <Delivery_ "1E4","1E3","7E3","1E2","1E1"),("6E8",
of_erroneous_SDUs>s),(list of"1E6","1E5","1E4","5E3","4E3","1E3",
supported <Transfer_delay>s),(list "5E2","1E2"),(0-2),(10-150 in 10 msof supported <Traffic_handling_
steps, 200-950 in 50 ms steps, 100
priority>s)0-4000 in 50 ms steps),(0-3),(0-1),(0-1)[+CGEQREQ: <PDP_type>,(list of
supported <Traffic_class>s),(listOKof supported <Maximum_bitrate_UL>s),(list of supported <Maximum_
bitrate_DL>s),(list of supported<Guaranteed_bitrate_UL>s),(list of supported <Guaranteed_
bitrate_DL>s),(list of supported<Delivery_order>s),(list of supported<Maximum_SDU_size>s),(list of
supported <SDU_error_ratio>s),(listof supported <Residual_bit_error_
ratio>s),(list of supported <Delivery_of_erroneous_SDUs>s),(list of
supported <Transfer_delay>s),(listof supported <Traffic_handling_priority>s),(list of supported<Source_statistics_descriptor>s),(list of supported <Signalling_
indication>s)

AT+CGEQREQ=?

[...]]
OK

18.31.3 Defined values
Parameter<cid><PDP_type>

UBX-13002752 - R67

Type
NumberStringDescription
See <cid>
See <PDP_type>

18 Packet switched data services

Page 432 of 1001

u-blox cellular modules - AT commands manual

Parameter<Traffic_class>Type
Number<Maximum_bitrate_UL>

Number<Maximum_bitrate_DL>

Number<Guaranteed_bitrate_UL>

Number<Guaranteed_bitrate_DL>

Number<Delivery_order>

Number<Maximum_SDU_size>

Number<SDU_error_ratio>

StringUBX-13002752 - R67

Description
Indicates the application type for which the UMTS bearer service is optimized(see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: conversational• 1: streaming• 2: interactive• 3: background• 4: subscribed value
Indicates the maximum number of kb/s delivered to UMTS (up-link traffic) at
an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the maximum number of kb/s delivered by UMTS (down-link traffic)
at an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the guaranteed number of kb/s delivered to UMTS (up-link traffic) at
an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the guaranteed number of kb/s delivered by UMTS (down-linktraffic) at an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates whether the UMTS bearer shall provide in-sequence SDU (Service
Data Unit) delivery or not (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: no• 1: yes• 2: subscribed value
Indicates the maximum allowed SDU (Service Data Unit) size in octets (see the
3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: subscribed value• Range 10-1500 in steps of 10 octets• 1502• 1510• 1520Indicates the target value for the fraction of SDUs (Service Data Unit) lost or
detected as erroneous. SDU error ratio is defined only for conforming traffic(see the 3GPP TS 24.008 [12], subclause 10.5.6.5). The value is specified as'mEe', e.g. a target SDU error ratio of 1*10-6 would be specified as '1E6':• "1E6": 1*10-6• "1E5": 1*10-5

18 Packet switched data services

Page 433 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<Residual_bit_error_ratio>

String<Delivery_of_erroneous_
SDUs>

Number<Transfer_delay>

Number

<Traffic_handling_priority> Number<Source_statistics_
descriptor>

Number<Signalling_indication>

NumberDescription• "1E4": 1*10-4• "1E3": 1*10-3• "7E3": 7*10-3• "1E2": 1*10-2• "1E1": 1*10-1• "0E0": subscribed value
Indicates the target value for the undetected bit error ratio in the delivered
SDUs (Service Data Unit). If no error detection is requested, the parameter
indicates the bit error ratio in the delivered SDUs (see the 3GPP TS 24.008[12], subclause 10.5.6.5). The value is specified as 'mEe', e.g. a target SDU error
ratio of 5*10-2 would be specified as '5E2':• "6E8": 6*10-8• "1E6": 1*10-6• "1E5": 1*10-5• "1E4": 1*10-4• "5E3": 5*10-3• "4E3": 4*10-3• "1E3": 1*10-3• "5E2": 5*10-2• "1E2": 1*10-2• "0E0": subscribed value
Indicates whether SDUs (Service Data Unit) detected as erroneous shall bedelivered or not (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: no• 1: yes• 2: no detect• 3 (default value): subscribed value
Indicates the target time, in milliseconds, between a request to transfer an
SDU (Service Data Unit) at an application processor and its delivery at theother application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 10-150 in steps of 10• Range 200-950 in steps of 50• Range 1000-4000 in steps of 100
Specifies the relative importance for handling of all SDUs (Service Data Unit)belonging to the UMTS bearer compared to the SDUs of other bearers (see the
3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: subscribed• 1: priority level 1• 2: priority level 2• 3: priority level 3
Specifies the characteristics of the source of the submitted SDUs for a PDP
context:• 0 (default value): characteristics of the SDUs unknown• 1: characteristics of the SDUs correspond to a speech source
Specifies signaling content of submitted SDUs for a PDP context:• 0 (default value): PDP context is not optimized for signalling• 1: PDP context is optimized for signalling <PDP_type>18.31.4 Notes
•

•
•
•

If <Maximum_bitrate_UL>, <Maximum bitrate DL>, <Guaranteed_bitrate_UL>, <Guaranteed_bitrate_
DL>, <Maximum_SDU_size> and <Transfer_delay> parameters are set outside the allowed range, anerror message will be provided. If the value is selected within the allowed range, it is rounded to the closest
allowed value according to the specified steps.
If <Traffic_class>=0 (conversational) or <Traffic_class>=1 (streaming), <Maximum_bitrate_UL>,<Maximum_bitrate_DL>, <Guaranteed_bitrate_UL> and <Guaranteed_bitrate_DL> must be provided.
If <Traffic_class>=0 (conversational) or <Traffic_class>=1 (streaming), <Source_statistics_descriptor>
must be provided.
If <Traffic_class>=2 (interactive), <Signalling_indication> must be provided.

UBX-13002752 - R67

18 Packet switched data services

Page 434 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4• <Traffic_class>=4, <Delivery_of_erroneous_SDUs>=3, <Delivery_order>=2 are not supported.
LISA-U1• <Source_statistics_descriptor> and <Signalling_indication> are not supported.

18.32 3G Quality of service profile (minimum acceptable)+CGEQMIN+CGEQMIN
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.32.1 Description
This command allows the TE to specifiy a minimum acceptable profile, which is checked by the MT against thenegotiated profile returned in the Activate/Modify PDP Context Accept message. The set command specifies a
profile for the context identified by the <cid>. The specified profile will be stored in the MT and checked against
the negotiated profile only at activation or MS initiated modification of the related context. This commandis actually an extension to the commands +CGDSCONT and +CGDCONT. The special form of this command+CGEQMIN=<cid> causes the minimum acceptable profile for context number <cid> to become undefined. No
check is made against the negotiated profile.
The command defines a PDP context having <PDP_type> set to "IP", <apn> set to "" and with the specified<cid>, if a PDP context with the specified <cid> was not already defined by +CGDCONT AT command.

18.32.2 Syntax
Type
Set

Read

SyntaxResponse
ExampleAT+CGEQMIN=[<cid>[,<Traffic_
OK
AT+CGEQMIN=1,2,5760,7168,0,0,0,
class>[,<Maximum_bitrate_1480,"1E3","1E5",2,1000,1,0,0
UL>[,<Maximum_bitrate_DL>[,OK<Guaranteed_bitrate_UL>[,<Guaranteed_bitrate_DL>[,<Delivery_order>[,<Maximum_
SDU_size>[,<SDU_error_ratio>[,<Residual_bit_error_ratio>[,<Delivery_of_erroneous_SDUs>[,<Transfer_delay>[,<Traffic_
handling_priority>[,<Source_
statistics_descriptor> [,<Signalling_
indication>]]]]]]]]]]]]]]]
AT+CGEQMIN?
+CGEQMIN: <cid>,<Traffic_+CGEQMIN: 1,2,5760,7168,0,0,0,
class>,<Maximum_bitrate_1480,"1E3","1E5",2,1000,1,0,0
UL>,<Maximum_bitrate_DL>,
OK<Guaranteed_bitrate_UL>,<Guaranteed_bitrate_DL>,<Delivery_order>,<Maximum_SDU_
size>,<SDU_error_ratio>,<Residual_
bit_error_ratio>,<Delivery_of_
erroneous_SDUs>,<Transfer_delay>,<Traffic_handling_priority>,<Source_statistics_descriptor>,<Signalling_indication>[+CGEQMIN: <cid>,<Traffic_
class>,<Maximum_bitrate_
UL>,<Maximum_bitrate_DL>,<Guaranteed_bitrate_UL>,<Guaranteed_bitrate_DL>,<Delivery_order>,<Maximum_

UBX-13002752 - R67

18 Packet switched data services

Page 435 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
ExampleSDU_size>,<SDU_error_ratio>,<Residual_bit_error_ratio>,<Deliveryof erroneous SDUs>,<Transfer_delay>,<Traffic_handling_priority>,<Source_statistics_descriptor>,<Signalling_indication>[...]]Test

OK+CGEQMIN: <PDP_type>,(list of+CGEQMIN: "IP",(0-3),(1-63 in 1 kbps
supported <Traffic_class>s),(liststeps, 64-568 in 8 kbps steps, 576of supported <Maximum_bitrate_
8640 in 64 kbps steps),(1-63 in 1
UL>s),(list of supported <Maximum_ kbps steps, 64-568 in 8 kbps steps,
bitrate_DL>s),(list of supported
576-8640 in 64 kbps steps, 8700<Guaranteed_bitrate_UL>s),
16000 in 100 kbps steps),(1-63 in 1
(list of supported <Guaranteed_kbps steps, 64-568 in 8 kbps steps,
bitrate_DL>s),(list of supported
576-8640 in 64 kbps steps),(1-63 in 1
<Delivery_order>s),(list of supported kbps steps, 64-568 in 8 kbps steps,<Maximum_SDU_size>s),(list of
576-8640 in 64 kbps steps, 8700supported <SDU_error_ratio>s),(list 16000 in 100 kbps steps),(0-1),(10of supported <Residual_bit_error_
1500,1502,1510,1520),("1E6","1E5",
ratio>s),(list of supported <Delivery_ "1E4","1E3","7E3","1E2","1E1"),("6E8",
of_erroneous_SDUs>s),(list of"1E6","1E5","1E4","5E3","4E3","1E3",
supported <Transfer_delay>s),(list "5E2","1E2"),(0-2),(10-150 in 10 msof supported <Traffic_handling_
steps, 200-950 in 50 ms steps, 100
priority>s)0-4000 in 50 ms steps),(0-3),(0-1),(0-1)[+CGEQMIN: <PDP_type>,(list of
supported <Traffic_class>s),(listOKof supported <Maximum_bitrate_UL>s),(list of supported <Maximum_
bitrate_DL>s),(list of supported<Guaranteed_bitrate_UL>s),(list of supported <Guaranteed_
bitrate_DL>s),(list of supported<Delivery_order>s),(list of supported<Maximum_SDU_size>s),(list of
supported <SDU_error_ratio>s),(listof supported <Residual_bit_error_
ratio>s),(list of supported <Delivery_of_erroneous_SDUs>s),(list of
supported <Transfer_delay>s),(listof supported <Traffic_handling_priority>s),(list of supported<Source_statistics_descriptor>s),(list of supported <Signalling_
indication>s)

AT+CGEQMIN=?

[...]]
OK

18.32.3 Defined values
Parameter<cid><PDP_type><Traffic_class>Type
NumberStringNumber<Maximum_bitrate_UL>

NumberUBX-13002752 - R67

Description
See <cid>
See <PDP_type>
Indicates the application type for which the UMTS bearer service is optimized(see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: conversational• 1: streaming• 2: interactive• 3: background• 4: subscribed value
Indicates the maximum number of kb/s delivered to UMTS (up-link traffic) at
an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):

18 Packet switched data services

Page 436 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<Maximum_bitrate_DL>

Number<Guaranteed_bitrate_UL>

Number<Guaranteed_bitrate_DL>

Number<Delivery_order>

Number<Maximum_SDU_size>

Number<SDU_error_ratio>

String<Residual_bit_error_ratio>

StringUBX-13002752 - R67

Description• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the maximum number of kb/s delivered by UMTS (down-link traffic)
at an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the guaranteed the maximum number of kb/s delivered to UMTS
(up-link traffic) at an application processor (see the 3GPP TS 24.008 [12],subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the guaranteed number of kb/s delivered by UMTS (down-linktraffic) at an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates whether the UMTS bearer shall provide in-sequence SDU (Service
Data Unit) delivery or not (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: no• 1: yes• 2: subscribed value
Indicates the maximum allowed SDU (Service Data Unit) size in octets (see the
3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: subscribed value• Range 10-1500 in steps of 10 octets• 1502• 1510• 1520Indicates the target value for the fraction of SDUs (Service Data Unit) lost or
detected as erroneous. SDU error ratio is defined only for conforming traffic(see the 3GPP TS 24.008 [12], subclause 10.5.6.5). The value is specified as'mEe', e.g. a target SDU error ratio of 1*10-6 would be specified as '1E6':• "1E6": 1*10-6• "1E5": 1*10-5• "1E4": 1*10-4• "1E3": 1*10-3• "7E3": 7*10-3• "1E2": 1*10-2• "1E1": 1*10-1• "0E0": subscribed value
Indicates the target value for the undetected bit error ratio in the delivered
SDUs (Service Data Unit). If no error detection is requested, the parameter
indicates the bit error ratio in the delivered SDUs (see the 3GPP TS 24.008

18 Packet switched data services

Page 437 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<Delivery_of_erroneous_
SDUs>

Number<Transfer_delay>

Number

<Traffic_handling_priority> Number<Source_statistics_
descriptor>

Number<Signalling_indication>

NumberDescription[12], subclause 10.5.6.5). The value is specified as 'mEe', e.g. a target SDU error
ratio of 5*10-2 would be specified as '5E2':• "6E8": 6*10-8• "1E6": 1*10-6• "1E5": 1*10-5• "1E4": 1*10-4• "5E3": 5*10-3• "4E3": 4*10-3• "1E3": 1*10-3• "5E2": 5*10-2• "1E2": 1*10-2• "0E0": subscribed value
Indicates whether SDUs (Service Data Unit) detected as erroneous shall bedelivered or not (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: no• 1: yes• 2: no detect• 3 (default value): subscribed value
Indicates the target time, in milliseconds, between a request to transfer an
SDU (Service Data Unit) at an application processor and its delivery at theother application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 10-150 in steps of 10• Range 200-950 in steps of 50• Range 1000-4000 in steps of 100
Specifies the relative importance for handling of all SDUs (Service Data Unit)belonging to the UMTS bearer compared to the SDUs of other bearers (see the
3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: subscribed• 1: priority level 1• 2: priority level 2• 3: priority level 3
Specifies the characteristics of the source of the submitted SDUs for a PDP
context:• 0 (default value): characteristics of the SDUs unknown• 1: characteristics of the SDUs correspond to a speech source
Specifies signaling content of submitted SDUs for a PDP context:• 0 (default value): PDP context is not optimized for signalling• 1: PDP context is optimized for signalling18.32.4 Notes•••

If <Maximum_bitrate_UL>, <Maximum bitrate DL>, <Guaranteed_bitrate_UL>, <Guaranteed_bitrate_
DL>, <Maximum_SDU_size> and <Transfer_delay> parameters are set outside the allowed range, anerror message will be provided. If the value is selected within the allowed range, it is rounded to the closest
allowed value according to the specified steps.
If <Traffic_class>=0 (conversational) or <Traffic_class>=1 (streaming), <Maximum_bitrate_UL>,<Maximum bitrate DL>, <Guaranteed_bitrate_UL>, <Guaranteed_bitrate_DL>, <Source_statistics_
descriptor> must be provided.
If <Traffic_class>=2 (interactive), <Signalling_indication> must be provided.

TOBY-L4• <Traffic_class>=4, <Delivery_of_erroneous_SDUs>=3, <Delivery_order>=2 are not supported.
• The default value of <Traffic_class> and <Delivery_of_erroneous_SDUs> parameters is 0.
LISA-U1• <Source_statistics_descriptor> and <Signalling_indication> are not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 438 of 1001

u-blox cellular modules - AT commands manual

18.33 3G Quality of Service Profile (negotiated) +CGEQNEG+CGEQNEG
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.33.1 Description
This command allows the TE to retrieve the negotiated QoS profiles returned in the Activate PDP Context
Accept message. The execution command returns the negotiated QoS profile for the specified <cid>s. The QoS
profile consists of a number of parameters, each of which may have a separate value.

18.33.2 Syntax
Type
Set

SyntaxAT+CGEQNEG=[<cid>[,<cid>[,...]]]

Response
Example+CGEQNEG: <cid>,<Traffic_
AT+CGEQNEG=1
class>,<Maximum_bitrate_+CGEQNEG: 1,2,5760,7168,0,0,0,
UL>,<Maximum_bitrate_DL>,
1480,"1E3","1E5",2,1000,1,0,0<Guaranteed_bitrate_UL>,<Guaranteed_bitrate_DL>,OK<Delivery_order>,<Maximum_SDU_
size>,<SDU_error_ratio>,<Residual_
bit_error_ratio>,<Delivery_of_
erroneous_SDUs>,<Transfer_delay>,<Traffic_handling_priority>,<Source_statistics_descriptor>,<Signalling_indication>[+CGEQNEG: <cid>,<Traffic_
class>,<Maximum_bitrate_
UL>,<Maximum_bitrate_DL>,<Guaranteed_bitrate_UL>,<Guaranteed_bitrate_DL>,<Delivery_order>,<Maximum_SDU_
size>,<SDU_error_ratio>,<Residual_
bit_error_ratio>,<Delivery_of_
erroneous_SDUs>,<Transfer_delay>,<Traffic_handling_priority>,<Source_statistics_descriptor>,<Signalling_indication>[...]]Test

OK+CGEQNEG: (list of <cid>s
associated with active contexts)

AT+CGEQNEG=?

+CGEQNEG: (1)OKOK

18.33.3 Defined values
Parameter<cid><Traffic_class>Type
NumberNumber<Maximum_bitrate_UL>

NumberUBX-13002752 - R67

Description
See <cid>
Indicates the application type for which the UMTS bearer service is optimized(see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: conversational• 1: streaming• 2: interactive• 3: background• 4: subscribed value
Indicates the maximum number of kb/s delivered to UMTS (up-link traffic) at
an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1

18 Packet switched data services

Page 439 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<Maximum_bitrate_DL>

Number<Guaranteed_bitrate_UL>

Number<Guaranteed_bitrate_DL>

Number<Delivery_order>

Number<Maximum_SDU_size>

Number<SDU_error_ratio>

String<Residual_bit_error_ratio>

StringUBX-13002752 - R67

Description• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the maximum number of kb/s delivered by UMTS (down-link traffic)
at an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the guaranteed number of kb/s delivered to UMTS (up-link traffic) at
an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates the guaranteed number of kb/s delivered by UMTS (down-linktraffic) at an application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 1-63 in steps of 1
• Range 64-568 in steps of 8
• Range 576-8640 in steps of 64• Range 8700-16000 in steps of 100• Range 17000-128000 in steps of 1000
• Range 130000-256000 in steps of 2000
Indicates whether the UMTS bearer shall provide in-sequence SDU (Service
Data Unit) delivery or not (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: no• 1: yes• 2: subscribed value
Indicates the maximum allowed SDU (Service Data Unit) size in octets (see the
3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: subscribed value• Range 10-1500 in steps of 10 octets• 1502• 1510• 1520Indicates the target value for the fraction of SDUs (Service Data Unit) lost or
detected as erroneous. SDU error ratio is defined only for conforming traffic(see the 3GPP TS 24.008 [12], subclause 10.5.6.5). The value is specified as'mEe', e.g. a target SDU error ratio of 1*10-6 would be specified as '1E6':• "1E6": 1*10-6• "1E5": 1*10-5• "1E4": 1*10-4• "1E3": 1*10-3• "7E3": 7*10-3• "1E2": 1*10-2• "1E1": 1*10-1• "0E0": subscribed value
Indicates the target value for the undetected bit error ratio in the delivered
SDUs (Service Data Unit). If no error detection is requested, the parameter
indicates the bit error ratio in the delivered SDUs (see the 3GPP TS 24.008[12], subclause 10.5.6.5). The value is specified as 'mEe', e.g. a target SDU error
ratio of 5*10-2 would be specified as '5E2':

18 Packet switched data services

Page 440 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<Delivery_of_erroneous_
SDUs>

Number<Transfer_delay>

Number

<Traffic_handling_priority> Number<Source_statistics_
descriptor>

Number<Signalling_indication>

NumberDescription• "6E8": 6*10-8• "1E6": 1*10-6• "1E5": 1*10-5• "1E4": 1*10-4• "5E3": 5*10-3• "4E3": 4*10-3• "1E3": 1*10-3• "5E2": 5*10-2• "1E2": 1*10-2• "0E0": subscribed value
Indicates whether SDUs (Service Data Unit) detected as erroneous shall bedelivered or not (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: no• 1: yes• 2: no detect• 3 (default value): subscribed value
Indicates the target time, in milliseconds, between a request to transfer an
SDU (Service Data Unit) at an application processor and its delivery at theother application processor (see the 3GPP TS 24.008 [12], subclause 10.5.6.5):• Range 10-150 in steps of 10• Range 200-950 in steps of 50• Range 1000-4000 in steps of 100
Specifies the relative importance for handling of all SDUs (Service Data Unit)belonging to the UMTS bearer compared to the SDUs of other bearers (see the
3GPP TS 24.008 [12], subclause 10.5.6.5):• 0: subscribed• 1: priority level 1• 2: priority level 2• 3: priority level 3
Specifies the characteristics of the source of the submitted SDUs for a PDP
context:• 0: characteristics of the SDUs unknown• 1: characteristics of the SDUs correspond to a speech source
Specifies signaling content of submitted SDUs for a PDP context:• 0: PDP context is not optimized for signalling• 1: PDP context is optimized for signalling18.33.4 Notes
TOBY-L4• <Traffic_class>=4, <Delivery_of_erroneous_SDUs>=3, <Delivery_order>=2 are not supported.

18.34 Define secondary PDP context +CGDSCONT+CGDSCONT
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.34.1 Description
Configures the PDP context parameter values for a secondary PDP context, identified by the local context
identification parameter <cid>, associated to a primary PDP context identified by the local context
identification parameter <p_cid>:• The <p_cid> parameter is mandatory when a secondary context is newly defined.
• The <p_cid> parameter can be omitted only when the context is already defined; in this case the PDP context
identified by <cid> becomes undefined.

UBX-13002752 - R67

18 Packet switched data services

Page 441 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4 / TOBY-L2 / MPCI-L2
After the PDP context activation, the information text response to the read command provides theconfiguration negotiated with the network (similarly to +CGTFTRDP and +CGCONTRDP AT commands).

18.34.2 Syntax
Type
Set

Read

SyntaxAT+CGDSCONT=[<cid>[,<p_cid>[,<d_comp>[,<h_comp>[,<IM_CN_
Signalling_Flag_Ind>]]]]]
AT+CGDSCONT?

Response
OK

ExampleAT+CGDSCONT=2,1
OK+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>[,<IM_CN_
Signalling_Flag_Ind>]+CGDSCONT: 2,1,0,0,0
OK[+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>[,<IM_CN_
Signalling_Flag_Ind>][...]]Test

OK+CGDSCONT: (list of supported+CGDSCONT: (1-8),(4,8),(0-2),(0-2),<cid>s),(list of <cid>s for defined(0-1)
primary contexts),(list of supportedOK<d_comp>s),(list of supported <h_comp>s)[,(list of supported <IM_
CN_Signalling_Flag_Ind>)]

AT+CGDSCONT=?

OK

18.34.3 Defined values
Parameter<cid><p_cid>Type
NumberNumber<d_comp>Number<h_comp>Number<IM_CN_Signalling_ Number
Flag_Ind>

Description
See <cid>
Numeric parameter that identifies the particular PDP context definition, specified
using +CGDCONT, to which a secondary PDP context definition will be associatedusing +CGDSCONT.
This parameter is only locally valid on the interface TE-MT.
PDP data compression; it can have the values:• 0 (default value): off• 1: on (predefined compression type i.e. V.42bis data compression)• 2: V.42bis data compression
PDP header compression; it can have the values:• 0 (default value): off• 1: on (predefined compression type, i.e. RFC1144)• 2: RFC1144• 3: RFC2507• 4: RFC3095<h_comp>: the available head-compressions is depending on configuration of thestack (configured via features in the stack)Shows whether the PDP context is for IM CN subsystem-related signalling only or not:• 0: PDP context is not for IM CN subsystem-related signalling only
• 1: PDP context is for IM CN subsystem-related signalling only

18.34.4 Notes
LARA-R2 / TOBY-R2• <d_comp>=1, 2 are not supported.
LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 / LARA-R280 / TOBY-R202• <h_comp>= 1, 2, 3 and 4 are not supported.
SARA-U2 / LISA-U2 / LISA-U1• <IM_CN_Signalling_Flag_Ind> parameter is not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 442 of 1001

u-blox cellular modules - AT commands manual

SARA-G3 / LEON-G1• <d_comp>=1, 2 are not supported (<d_comp>=1 may be accepted, but no compression is performed).
• <h_comp>= 2, 3 and 4 are not supported.

18.35 UE modes of operation for EPS +CEMODE+CEMODE
Modules
Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
full
Yes

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

18.35.1 Description
Sets the MT to operate according to the specified mode of operation for EPS, see 3GPP TS 24.301 [68]. If therequested operation mode is not supported, an error result code is returned.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

18.35.2 Syntax
Type
Set

SyntaxAT+CEMODE=[<mode>]

Response
OK

ExampleAT+CEMODE=1

Read

AT+CEMODE?

+CEMODE: <mode>

OK+CEMODE: 1

Test

AT+CEMODE=?

OK+CEMODE: (list of supported<mode>'s)

OK+CEMODE: (0-3)
OKOK

18.35.3 Defined values
Parameter<mode>

Type
NumberDescription
Mode configuration:• 0: PS mode 2 of operation. The UE registers only to EPS services, and the UE's usage
setting is "data centric"• 1 (default and factory-programmed value for voice capable devices): CS/PS mode
1 of operation. The UE registers to both EPS and non-EPS services, and the UE's
usage setting is "voice centric"• 2 (default and factory-programmed value for voice not-capable devices): CS/PS
mode 2 of operation. The UE registers to both EPS and non-EPS services, and theUE's usage setting is "data centric"• 3: PS mode 1 of operation. The UE registers only to EPS services, and the UE's usage
setting is "voice centric"

18.35.4 Notes••

A UE set to "Data centric" does not disable the E-UTRAN capability if voice services cannot be obtained.
Upon receiving combined EPS/IMSI attach accept or combined TA/LA Update accept with "SMS-only"
indication, a data centric UE stays in the current RAT and is not allowed to use CSFB. Upon receiving
combined EPS/IMSI attach accept or combined TA/LA Update accept with "CSFB Not Preferred"
indication, a data centric UE stays in the current RAT and is allowed to use CSFB.
A UE set to "Voice centric" shall always try to ensure that Voice service is possible. A CSFB and an IMS/
CS-voice capable UE set to "Voice centric" unable to obtain voice service in E-UTRAN (e.g. CSFB and IMS
voice are not supported or the configured preferences on how to handle voice services prevent usage of

UBX-13002752 - R67

18 Packet switched data services

Page 443 of 1001

u-blox cellular modules - AT commands manual

any available voice services), shall disable the E-UTRAN capability, which results in re-selecting GERANor UTRAN. The E-UTRAN capability is re-enabled by the UE under the conditions described in 3GPP TS
24.301 [68].
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• The PIN insertion is not mandatory before the command execution.
• If +CEMODE is set to EPS-only (<mode>=0 or <mode>=3) the +CGCLASS command setting is
automatically updated to class "CG".
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / TOBY-L220-62S / MPCI-L200-00S /MPCI-L201 / MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S / MPCI-L220-62S / LARA-R204 /LARA-R220• <mode>=1 and 3 are not supported.
LARA-R203 / LARA-R220• The factory-programmed value of <mode> is 2.

18.36 EPS network registration status +CEREG+CEREG
Modules
Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.36.1 Description
Configures the network registration URC related to EPS domain. The URC assumes a different syntax
depending on the network and the <n> parameter:• +CEREG: <stat> when <n>=1 and there is a change in the MT's EPS network registration status in E-UTRAN• +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>]] when <n>=2 and there is a change of the network cell in EUTRAN• +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]] when <n>=3 and the value of<stat> changes• +CEREG:<stat>[,[<tac>],[<ci>],[<AcT>][,,[,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]]
when <n>=4 if there is a change of the network cell in E-UTRAN• +CEREG:<stat>[,[<tac>],[<ci>],[<AcT>][,[<cause_type>],[<reject_cause>][,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]] when <n>=5 and the value of <stat> changes
The parameters <AcT>, <tac>, <rac_or_mme>, <ci>, <cause_type>, <reject_cause>, <Assigned_Active_Time>and <Assigned_Periodic_TAU> are provided only if available.
The read command returns always at least the mode configuration (<n>), the EPS registration status (<stat>).
The location parameters <tac>, <rac_or_mme>, <ci> and <AcT>, if available, are returned only when <n>=2,<n>=3, <n>=4 or <n>=5 and the MT is registered with the network. The parameters <cause_type>, <reject_cause>, if available, are returned when <n>=3 or <n>=5. The PSM related parameter <Assigned_Active_
Time> is returned only when <n>=4 or <n>=5, the MT is registered with the network and PSM is granted by
the network. The <Assigned_Periodic_TAU> parameter is returned only if when <n>=4 or <n>=5, the MT isregistered with the network, PSM is granted by the network and an extended periodic TAU value (T3412_ext)
is assigned.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
If the EPS MT in GERAN/UTRAN/E-UTRAN also supports circuit mode services and/or GPRS services,
the +CREG / +CGREG set and read command result codes apply to the registration status and location
information for those services.

18.36.2 Syntax
Type
Set

SyntaxAT+CEREG=[<n>]Response
OK

Read

AT+CEREG?

OK+CEREG: <n>,<stat>[,[<tac>],[<ci>], +CEREG: 2,1,"3a9b","0000c33d",7[<AcT>[,[<cause_type>],[<reject_OK

UBX-13002752 - R67

18 Packet switched data services

ExampleAT+CEREG=1

Page 444 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Examplecause>][,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]]]

Test

AT+CEREG=?

OK+CEREG: (list of supported <n>s)+CEREG: (0-3)

OK
OK+CEREG: <stat>[,[<tac>],[<ci>],+CEREG: 1,"3a9b","0000c33d",7[<AcT>][,[<cause_type>],[<reject_cause>][,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]]

URC

18.36.3 Defined values
Parameter<n>Type
NumberDescription
Mode configuration:• 0: network registration URC disabled• 1: network registration URC +CEREG: <stat> enabled• 2: network registration and location information URC +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>]] enabled• 3: network registration, location information and EMM cause value
information URC +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]] enabled• 4: PSM, network registration and location information information
URC+CEREG:<stat>[,[<tac>],[<ci>],[<AcT>][,,[,[<Assigned_Active_Time>[,<Assigned_Periodic_TAU>]]]]] enabled• 5: PSM, network registration, location information and EMM cause
value information URC +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,[<cause_type>],[<reject_cause>][,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]]
enabledAllowed values:• TOBY-L4 / LARA-R2 / TOBY-R2 - 0 (default value), 1, 2
• TOBY-L2 / MPCI-L2 - 0 (default value), 1, 2, 3

<stat>

Number

<tac>
<ci>
<AcT>

StringStringNumber<cause_type>

Number<reject_cause>

Number

EPS registration status:• 0: not registered• 1: registered, home network• 2: not registered, but the MT is currently trying to attach or searching an operator
to register to• 3: registration denied• 4: unknown (e.g. out of E-UTRAN coverage)• 5: registered, roaming• 8: attached for emergency bearer services only (see 3GPP TS 24.008 [12] and 3GPP
TS 24.301 [68] that specify the condition when the MS is considered as attached
for emergency bearer services)
Two bytes tracking area code in hexadecimal format
Four bytes E-UTRAN cell-id in hexadecimal format
Access technology of the serving cell:• 7: E-UTRAN (see 3GPP TS 44.060 [69] that specifies the System Information
messages which give the information about whether the serving cell supports
EGPRS)• 8: E-UTRAN EC-GSM-IoT (A/Gb mode)• 9: E-UTRAN Cat NB1Allowed values:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 - 7<reject_cause> type:• 0: indicates that <reject_cause> contains an EMM cause value, see 3GPP TS 24.30
1 [68] Annex A• 1: indicates that <reject_cause> contains a manufacture-specific cause
Allowed values:• TOBY-L2 / MPCI-L2 - 0
Cause of the failed registration. The value is of type as defined by <cause_type>

UBX-13002752 - R67

18 Packet switched data services

Page 445 of 1001

u-blox cellular modules - AT commands manual

Parameter<Assigned_Active_
Time>

Type
String<Assigned_Periodic_ String
TAU><rac_or_mme>

StringDescription
One byte in an 8 bit format. Assigned Active Time value (T3324) allocated to the UE.
The assigned Active Time value is coded as one byte (octet 3) of the GPRS Timer
2 information element coded as bit format (e.g. "00100100" equals 4 minutes). For
the coding and the value range, see the GPRS Timer 2 IE in 3GPP TS 24.008 table 10.5.163/3GPP TS 24.008 [12]. See also 3GPP TS 23.682 [128], 3GPP TS 23.060 [10]) and
3GPP TS 23.401 [129].
One byte in an 8 bit format. Assigned extended periodic TAU value (T3412_ext)
allocated to the UE. The assigned extended periodic TAU value is coded as one byte
(octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000
111" equals 70 hours). For the coding and the value range, see the GPRS Timer 2 IE in
3GPP TS 24.008 table 10.5.163a/3GPP TS 24.008 [12]. See also 3GPP TS 23.682 [128]and 3GPP TS 23.401 [129].
RAC (Routing Area Code) or MME Code (Mobile Management Entity) in hexadecimalformat18.36.4 Notes
TOBY-L4 / LARA-R2 / TOBY-R2• If <stat>=0 the MT is not registered and it does not search an operator to register to.
TOBY-L2 / MPCI-L2• <stat>= 8 is not supported.
• If <stat>=0 the MT is not registered and it does not search an operator to register to.
• The information text response to the read command and the URC will assume these values in these
conditions:o During the initial network searching at the module power on the <stat> parameter is 2
o If the module is PS attached to the GSM/UMTS home network the <stat> parameter is 4
o If the module is registered to E-UTRAN the <stat> parameter is 1
o In the out of coverage state the <stat> parameter is 4

18.37 Delete non-active PDP contexts +CGDEL+CGDEL
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.37.1 Description
Removes the indicated PDP context and removes all the associated data related to the indicated PDP contexts
that are not activated. The AT command does not delete or remove the information for activated PDP contexts.
The removed PDP context is listed by the <+CGDEL: cid> IRC.
If the <cid> parameter points to a primary PDP context, the PDP context will be deleted together with all thelinked secondary PDP contexts if none of the PDP contexts are activated.
If the <cid> parameter points to a secondary PDP context, the PDP context will be deleted if it is not activated.
If the parameter <cid> is omitted, all the primary PDP contexts that are not activated or that have any
activated secondary PDP contexts will be removed and all secondary PDP contexts that are not activatedwill be removed. The associated data of all the deleted PDP contexts will be removed, and the removed
PDP context are listed by the +CGDEL: <cid>[,<cid>,...]] IRC.
TOBY-L2 / MPCI-L2
The command removes the associated PDP context data that can be set by the AT commands+CGDCONT, +CGDSCONT, +CGTFT, +CGEQREQ, +CGEQMIN and +CGEQOS. For an attempt to delete
PDP context(s) which would violate these rules, an error result code is returned.

18.37.2 Syntax
Type
Set

SyntaxAT+CGDEL=[<cid>]

UBX-13002752 - R67

Response+CGDEL: <cid>[,<cid>[,...]]

18 Packet switched data services

ExampleAT+CGDEL=2

Page 446 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example+CGDEL: 2

Test

AT+CGDEL=?

OK

OK
OK

18.37.3 Defined values
Parameter
<cid>

Type
NumberDescription
See <cid>

18.38 Traffic flow template read dynamic parameters+CGTFTRDP+CGTFTRDP
Modules
Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.38.1 Description
Returns the relevant information about traffic flow template for an active secondary or non secondary PDP
context specified by <cid> together with the additional network assigned values when established by the
network.
The test command returns a list of <cid>s associated with active secondary and non secondary contexts.
If the parameter <cid> is omitted, the relevant information for all active secondary non secondary PDP
contexts is returned.
The parameters of both network and MT/TA initiated PDP contexts will be returned.

18.38.2 Syntax
Type
Set

SyntaxAT+CGTFTRDP=[<cid>]Response
Example[+CGTFTRDP: <cid>,<packet_filter_ AT+CGTFTRDP=2
identifier>,<evaluation_precedence_+CGTFTRDP: 2,1,1,"8.9.10
index>,<remote_address_and_.11.255.255.0.0",0,0.65535,0.65535,
subnet_mask>,<protocol_number_
0,0,0,0,0,"1.2.12.11.255.255.0.0"(ipv4)/next_header_(ipv6)>,<local_
port_range>,<remote_port_range>, OK<ipsec_security_parameter index(spi)>,<type_of_service_(tos)(ipv4)_
and_mask/traffic_class_(ipv6)_
and_mask>,<flow_label(ipv6)>,<direction>,<NW_packet_filter_
Identifier>,<local_address_and_subnet_mask>][+CGTFTRDP: <cid>,<packet_filter_
identifier>,<evaluation_precedence_index>,<remote_address_and_subnet_mask>,<protocol_number_(ipv4)/next_header_(ipv6)>,<local_
port_range>,<remote_port_range>,<ipsec_security_parameter index(spi)>,<type_of_service_(tos)(ipv4)_
and_mask/traffic_class_(ipv6)_
and_mask>,<flow_label(ipv6)>,<direction>,<NW_packet_filter_
Identifier>,<local_address_and_subnet_mask>[...]]

UBX-13002752 - R67

18 Packet switched data services

Page 447 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+CGTFTRDP=?

Response
OK+CGTFTRDP: (list of <cid>s
associated with active contexts)

Example+CGTFTRDP: 1,2
OKOK

18.38.3 Defined values
Parameter<cid><packet_filter_identifier>Type
NumberNumberDescription
See <cid>
Packet filter:• Range: 1 - 8
Evaluation precedence index that is unique within all TFTs
associated with the PDP contexts that share the same PDP
address:• Range: 0-255 (from highest evaluation precedence to lowest
evaluation precedence)Specifies the remote address and subnet mask attribute of avalid packet filter. Consists of dot-separated numeric (0-255)
parameters on the form:• "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
• "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16" for IPv6
Specifies the Protocol Number / Next Header attribute of a valid
packet filter. It shall contain either an IPv4 Protocol Number oran IPv6 Next Header value.
• Range: 0 -255
Specifies the destination port range attribute of a valid packet
filter:• The range goes from 0 to 65535
Specifies the source port range attribute of a valid packet filter:• The range goes from 0 to 65535
IPSec SPI attribute of a valid packet filter which is a 32-bit field.
• Range: 0x00000000 - 0xFFFFFFFF
dot-separated numbers on the form "t.m" that specifies theType of Service / Traffic Class and Mask attribute of a valid
packet filter. It shall contain either an IPv4 TOS octet or an IPv6
Traffic Class octet along with a mask defining which of the 8bits should be used for matching.
• Range: 0-65535
Specifies the Flow Label attribute of a valid packet filter. It isonly valid for IPv6.
• Range: 0x00000 - 0xFFFFF
Specifies the transmission direction in which the packet filter
shall be applied:• 0: Pre Release 7 TFT Filter (see 3GPP TS 24.008 [12], table 10.5.162)• 1: uplink• 2: downlink• 3: bidirectional (used for uplink and downlink)
The value range is from 1 to 16. In LTE the value is assigned by
the network when the dedicated EPS bearer is established.
Specifies the local address and subnet mask attribute of avalid packet filter. Consists of dot-separated numeric (0-255)
parameters on the form:• "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
• "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16" for IPv6

<evaluation_precedence_index>

Number<remote_address_and_subnet_mask>

String<protocol_number_(ipv4)/next_header_(ipv6)>

Number<local_port_range>

Number<remote_port_range>

Number<ipsec_security_parameter index_(spi)>

String<type_of_service_(tos)(ipv4)_and_mask/
traffic_class_(ipv6)_and_mask>

String<flow_label(ipv6)>

String<direction>

Number<NW_packet_filter_Identifier>Number<local_address_and_subnet_mask>

StringUBX-13002752 - R67

18 Packet switched data services

Page 448 of 1001

u-blox cellular modules - AT commands manual

18.38.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• <local_address_and_subnet_mask> is not supported .

18.39 Configure the authentication parameters of a PDP/EPS
bearer +UAUTHREQ+UAUTHREQ
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G4 SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialYes
NVM
No+CME Error

18.39.1 Description
Configures the authentication parameters of a defined PDP/EPS bearer. The authentication parameters will
be sent during the context activation phase as a protocol configuration options (PCO) information element.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
When <auth_type>=3 is set, AT+CGACT=1,<cid> may trigger at most 3 PDP context activation requests
for <cid> to the protocol stack. The first request for <cid> is done with no authentication. If the PDP
context activation fails, a second attempt is triggered with PAP authentication. If the second PDP context
activation fails, a third attempt is triggered with CHAP authentication. These 3 PDP context activation
requests are not to be confused with the effective number of request PDP context activations sent to the
network (see the 3GPP TS 24.008 [12]).
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The command returns an error result code if the input <cid> is already active or not yet defined.

18.39.2 Syntax
Type
Set

SyntaxAT+UAUTHREQ=<cid>,<auth_type>,<username>,<password>

Response
OK

Test

AT+UAUTHREQ=?

+UAUTHREQ: (list of supported<cid>s),(list of supported <auth_type>s)[,,]

ExampleAT+UAUTHREQ=1,1,"user","pass"
OK+UAUTHREQ: (1-8),(0-2),,
OKOK

18.39.3 Defined values
Parameter<cid><auth_type>

Type
NumberNumber<username>

StringUBX-13002752 - R67

Description
See <cid>.
Configure the authentication:• 0: no authentication• 1: PAP• 2: CHAP• 3: automatic selection of authentication type (none/CHAP/PAP)
Allowed values:• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3 - 0, 1, 2, 3
• TOBY-L4 / TOBY-L2 / MPCI-L2 / SARA-G4 - 0, 1, 2
Username. The default value is an empty string:• TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - The maximum length is 64.
• TOBY-L2 / MPCI-L2 - The maximum length is 50.
• SARA-G4 - The maximum length is 20.
• SARA-G3 - The maximum length is 32.

18 Packet switched data services

Page 449 of 1001

u-blox cellular modules - AT commands manual

Parameter<password>

Type
StringDescription
Password. The default value is an empty string:• TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - The maximum length is 64.
• TOBY-L2 / MPCI-L2 - The maximum length is 50.
• SARA-G4 - The maximum length is 20.
• SARA-G3 - The maximum length is 32.

18.39.4 Notes•

In a PPP dial-up scenario, the authentication parameters set by the +UAUTHREQ command are
overwritten whenever the host provides a new setting via the PPP authentication protocol (PAP or CHAP).

TOBY-L4• The <username> and <password> parameters must be set to an empty string if the authentication type
is not set (<auth_type>=0).
TOBY-L2 / MPCI-L2• The <username> and <password> parameters must be set to an empty string or omitted if theauthentication type is not set (<auth_type>=0).
• The command setting is not saved in NVM.
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S• In a PPP dial-up scenario, the authentication parameters set by the +UAUTHREQ command are notoverwritten when the host provides a new setting via the PPP authentication protocol (PAP or CHAP).
LARA-R2 / TOBY-R2• The <username> and <password> parameters must be set to an empty string if the authentication type
is not set (<auth_type>=0).
• <auth_type>=3 settings is not effective for the initial default EPS bearer established during the LTE
attach.
LARA-R202 / LARA-R203 / LARA-R204 / LARA-R211 / TOBY-R2• TOBY-R200-02B-00,
TOBY-R202-02B-00,
TOBY-R200-02B-01,
TOBY-R202-02B-01,
LARA-R202-02B-00, LARA-R203-02B-00, LARA-R204-02B-00, LARA-R211-02B-00 do not save thecommand setting in NVM.
SARA-U2 / LISA-U2 / SARA-G3• The <username> and <password> parameters must be set to an empty string if the authentication type
is not set (<auth_type>=0).
• The command setting is not saved in NVM.
SARA-G4• The <username> and <password> parameters must be set to an empty string if the authentication type
is not set (<auth_type>=0).
• The command setting is not saved in NVM.
• The command set authentication type only on network side and not on PPP side too (in case of dial-up),
so eventual authentication settings provided via PPP does not override parameters set by +UAUTHREQ.
On the PPP side:o SARA-G450-01C - no authentication and PAP authentication are supported. By default noauthentication is set.
o SARA-G450-00C - no authentication and PAP authentication are supported. By default PAP
authentication is set.

UBX-13002752 - R67

18 Packet switched data services

Page 450 of 1001

u-blox cellular modules - AT commands manual

18.40 Send custom packets over a context +UTGSINK+UTGSINK
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.40.1 Description
Sends the required number of packets over a context identified by <cid>. The packet content is hardcoded andis a series of '*' characters.
No check is performed on <cid>'s status: the context must be activated before issuing the command.
The sending process is not guaranteed, and might depend on channel conditions and internal protocols status.

18.40.2 Syntax
Type
Set

SyntaxAT+UTGSINK=[[<cid>][,<packet_
size>][,<packet_count>]]

Response
OK

ExampleAT+UTGSINK=1,1400,10
OK
AT+UTGSINK=1,1200
OK
AT+UTGSINK=4

Test

AT+UTGSINK=?

+UTGSINK: (list of supported<cid>s),(list of supported <packet_
size>s),(list of supported <packet_
count>s)OK+UTGSINK: (1-8),(1-1500),(1-50)
OKOK

18.40.3 Defined values
Parameter
<cid>

Type
NumberDescription
Context identifier.

<packet_size><packet_count>

NumberNumber

The range goes from 1 to 8. The default value is 1.
Packet size in bytes. The range goes from 1 to 1500. The default value is 1
Number of packets to send. The range goes from 1 to 50. The default value is 1

18.41 Define EPS quality of service +CGEQOS+CGEQOSModules
Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.41.1 Description
Allows the TE to specify the EPS quality of service parameters <cid>, <QCI>, <DL_GBR>, <UL_GBR>, <DL_
MBR> and <UL_MBR> for a PDP context or traffic flows (see 3GPP TS 24.301 [68] and 3GPP TS 23.203 [71]).
When in UMTS/GPRS the MT applies a mapping function to UTMS/GPRS quality of service.
The read command returns the current settings for each defined QoS.
TOBY-L4 / TOBY-L2 / MPCI-L2
After the PDP context activation, the information text response to the read command provides theconfiguration negotiated with the network (similarly to +CGTFTRDP and +CGCONTRDP AT commands).
The set command +CGEQOS=<cid> causes the values for context number <cid> to become undefined.

UBX-13002752 - R67

18 Packet switched data services

Page 451 of 1001

u-blox cellular modules - AT commands manual

18.41.2 Syntax
Type
Set

SyntaxResponse
AT+CGEQOS=[<cid>[,<QCI>[,<DL_ OK
GBR>,<UL_GBR>[,<DL_MBR>,<UL_
MBR>]]]]Read

AT+CGEQOS?

ExampleAT+CGEQOS=1,1,2500,7000,2500,
7000

OK[+CGEQOS: <cid>,<QCI>,[<DL_+CGEQOS: 1,1,2500,7000,2500,7000
GBR>,<UL_GBR>],[<DL_MBR>,<UL_OK
MBR>]][+CGEQOS: <cid>,<QCI>,[<DL_
GBR>,<UL_GBR>],[<DL_MBR>,<UL_
MBR>][...]]Test

OK+CGEQOS: (list of supported<cid>s),(list of supported <QCI>s),(list of supported <DL_GBR>s),(list of supported <UL_GBR>s),(listof supported <DL_MBR>s),(list of
supported <UL_MBR>s)

AT+CGEQOS=?

+CGEQOS: (1-8),(0-9),(0-5000),(021000),(0-5000),(0-21000)
OKOK

18.41.3 Defined values
Parameter
<cid>
<QCI>

Type
NumberNumber<DL_GBR>

Number<UL_GBR>

Number<DL_MBR>

Number<UL_MBR>

NumberDescription
See <cid>.
Specifies a class of EPS QoS (see 3GPP TS 24.301 [68]):• 0: QCI is selected by network• 1-4: value range for guaranteed bit rate traffic flows• 5-9: value range for non-guaranteed bit rate traffic flows• 128-254: value range for Operator-specific QCIs
Indicates DL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).
Indicates UL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).
Indicates DL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).
Indicates UL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).

18.42 EPS quality of service read dynamic parameters+CGEQOSRDP+CGEQOSRDP
Modules
TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
Attributes
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.42.1 Description
Returns the quality of service parameters <QCI>, <DL_GBR>, <UL_GBR>, <DL_MBR> and <UL_MBR> of theactive secondary or non secondary PDP context associated to the provided context identifier <cid>.
The test command returns a list of <cid>s associated with secondary or non secondary active PDP contexts.
The parameters of both network and MT/TA initiated PDP contexts will be returned.
If the parameter <cid> is omitted, the quality of service parameters for all the secondary and non
secondary active PDP contexts are returned.

UBX-13002752 - R67

18 Packet switched data services

Page 452 of 1001

u-blox cellular modules - AT commands manual

18.42.2 Syntax
Type
Set

SyntaxAT+CGEQOSRDP=[<cid>]Response
Example[+CGEQOSRDP: <cid>,<QCI>,[<DL_ AT+CGEQOSRDP=1
GBR>,<UL_GBR>],[<DL_MBR>,<UL_+CGEQOSRDP: 1,7,0,0,0,0,0,0
MBR>],[<DL_AMBR>,<UL_AMBR>]]
OK[+CGEQOSRDP: <cid>,<QCI>,[<DL_
GBR>,<UL_GBR>],[<DL_MBR>,<UL_
MBR>],[<DL_AMBR>,<UL_AMBR>][...]]Test

OK+CGEQOSRDP: (list of <cid>s
associated with active contexts)

AT+CGEQOSRDP=?

+CGEQOSRDP: 1
OKOK

18.42.3 Defined values
Parameter
<cid>
<QCI>

Type
NumberNumber<DL_GBR>

Number<UL_GBR>

Number<DL_MBR>

Number<UL_MBR>

Number<DL_AMBR>

Number<UL_AMBR>

NumberDescription
See <cid>.
Specifies a class of EPS QoS (see 3GPP TS 24.301 [68]):• 0: QCI is selected by network• 1-4: value range for guaranteed bit rate traffic flows• 5-9: value range for non-guaranteed bit rate traffic flows• 65-66: value range for guaranteed bit rate traffic flows• 69-70: value range for non-guaranteed bit rate traffic flows• 128-254: value range for operator-specific QCIs
Indicates DL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).
Indicates UL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).
Indicates DL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).
Indicates UL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in
kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [68]).
Indicates DL APN aggregate maximum bit rate (MBR) (see 3GPP TS 24.301 [68]). The
value is expressed in kb/s.
Indicates UL APN aggregate maximum bit rate (MBR) (see 3GPP TS 24.301 [68]). The
value is expressed in kb/s.

18.42.4 Notes
TOBY-L2 / MPCI-L2• If the parameter <cid> is omitted, issue the AT+CGEQOSRDP command (without "=").

18.43 Secondary PDP context read dynamic parameters+CGSCONTRDP+CGSCONTRDP
Modules
TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
Attributes
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.43.1 Description
Returns the <p_cid>, <bearer_id> and <IM_CN_Signalling_Flag_Ind> parameters for an active secondary PDP
context having the context identifier <cid>. The test command returns the list of <cid>s associated with active
secondary PDP contexts.

UBX-13002752 - R67

18 Packet switched data services

Page 453 of 1001

u-blox cellular modules - AT commands manual

If the parameter <cid> is omitted, the relevant information for all active secondary PDP contexts isreturned.
The parameters for UE initiated and network initiated PDP contexts are returned.
In EPS, the Traffic Flow parameters are returned.

18.43.2 Syntax
Type
Set

SyntaxAT+CGSCONTRDP=[<cid>]Response[+CGSCONTRDP: <cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_
Flag_Ind>]][+CGSCONTRDP: <cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_
Flag_Ind>]

ExampleAT+CGSCONTRDP=2+CGSCONTRDP: 2,1,6,0OK[...]]Test

OK+CGSCONTRDP: (list of active
secondary PDP contexts)

AT+CGSCONTRDP=?

+CGSCONTRDP: 2
OKOK

18.43.3 Defined values
Parameter<cid><p_cid>Type
NumberNumber<bearer_id>

Number<IM_CN_Signalling_ Number
Flag_Ind>

Description
See <cid>
Numeric parameter that identifies the particular PDP context definition, specified
using +CGDCONT, to which a secondary PDP context definition will be associatedusing +CGDSCONT.
This parameter is only locally valid on the interface TE-MT.
Bearer identification, i.e. the EPS bearer in EPS and the NSAPI in UMTS/GPRS. The
allowed range goes from 5 to 16.
Shows whether the PDP context is for IM CN subsystem-related signalling only or not:••0: PDP context is not for IM CN subsystem-related signalling only
1: PDP context is for IM CN subsystem-related signalling only

18.44 UE's usage setting for EPS +CEUS+CEUS
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.44.1 Description
Sets the MT to operate according to the specified UE's usage setting for EPS, as defined in 3GPP TS 24.301 [68].
The read command returns the usage setting set by the TE.
The test command is used for requesting information on the supported MT settings.

18.44.2 Syntax
Type
Set

SyntaxAT+CEUS=[<setting>]

Response
OK

ExampleAT+CEUS=1

Read

AT+CEUS?

+CEUS: <setting>OK+CEUS: 1

Test

AT+CEUS=?

OK+CEUS: (list of supported<setting>s)

UBX-13002752 - R67

18 Packet switched data services

OK+CEUS: (0,1)
OK

Page 454 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example18.44.3 Defined values
Parameter<setting>

Type
NumberDescription
Configure the UE usage setting:••

0: voice centric
1 (default value): data centric

18.44.4 Notes•

See 3GPP TS 23.221 [70] for the definition of the "voice centric" and "data centric" usage settings.

TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / TOBY-L220-62S / MPCI-L200-00S /MPCI-L201 / MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S / MPCI-L220-62S• The <setting> parameter cannot be set to 0.

18.45 PDP context read dynamic parameters +CGCONTRDP+CGCONTRDP
Modules
TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SyntaxPIN required
Attributes
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.45.1 Description
Returns the relevant information <bearer_id>, <APN>, <local_addr_and_subnet_mask>, <gw_addr>, <DNS_
prim_addr>, <DNS_sec_addr>, <P-CSCF_prim_addr>, <P-CSCF_sec_addr>, <IM_CN_Signalling_Flag_Ind>,<LIPA_indication>, <IPv4_MTU> and <WLAN_offload> for an active non secondary PDP context with thecontext identifier <cid>.
If the MT indicates more than two IP addresses of P-CSCF servers or more than two IP addresses of DNS
servers, multiple lines of information per <cid> will be returned.
A set command with an undefined <cid> provides an error result code.
If the parameter <cid> is omitted, the relevant information for all active non secondary PDP contexts isreturned.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
If the MT has dual stack capabilities, for each <cid> will be printed two different rows: the first one willcontain the IPv4 parameters, in the second one the IPv6 parameters.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2
The IPv6 addresses notation depends on the +CGPIAF setting.

18.45.2 Syntax
Type
Set

SyntaxAT+CGCONTRDP[=<cid>]Response
Example[+CGCONTRDP: <cid>,<bearer_id>, AT+CGCONTRDP=1<APN>[,<local_addr_and_subnet_+CGCONTRDP: 1,0,"web.omnitel.it",mask>[,<gw_addr>[,<DNS_prim_"109.113.62.238.255.255.255.255",
addr>[,<DNS_sec_addr>[,<P-CSCF_"109.113.62.201","83.224.70.77",
prim_addr>[,<P-CSCF_sec_addr>[,"83.224.70.54",,,,0,0,0,0<IM_CN_Signalling_Flag_Ind>[,<LIPA_indication>[,<IPv4_MTU>[,OK<WLAN_offload>[,<Local_Addr_
Ind>]]]]]]]]]]]][+CGCONTRDP: <cid>,<bearer_id>,<APN>[,<local_addr_and_subnet_mask> [,<gw_addr>[,<DNS_prim_
addr>[,<DNS_sec_addr>[,<P-CSCF_

UBX-13002752 - R67

18 Packet switched data services

Page 455 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
prim_addr>[,<P-CSCF_sec_addr>[,<IM_CN_Signalling_Flag_Ind>[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_offload>[,<Local_Addr_
Ind>]]]]]]]]]]]

Example[...]]Test

AT+CGCONTRDP=?

OK+CGCONTRDP: (list of active non
secondary PDP contexts)+CGCONTRDP: 1
OKOK

18.45.3 Defined values
Parameter
<cid>
<APN>
<bearer_id>

Type
NumberStringNumber<local_addr_and_subnet_mask>

String<gw_addr>

String<DNS_prim_addr>
String<DNS_sec_addr>
String<P-CSCF_prim_
Stringaddr><P-CSCF_sec_addr> String<IM_CN_Signalling_ Number
Flag_Ind><LIPA_indication>

Number

<IPv4_MTU><WLAN_offload>

NumberNumber<Local_Addr_Ind>

NumberUBX-13002752 - R67

Description
See <cid>.
See <APN>.
Identifies the bearer, i.e. the EPS bearer in EPS and the NSAPI in UMTS/GPRS. The
range goes from 5 to 16.
IP address and subnet mask of the MT. The string is given as dot-separated numeric(0-255) parameters on the form:• "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
• "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16" for IPv6
Gateway address of the MT. The string is given as dot-separated numeric (0-255)
parameters.
IP address of the primary DNS server.
IP address of the secondary DNS server.
IP address of the primary P-CSCF server.
IP address of the secondary P-CSCF server.
Shows whether the PDP context is for IM CN subsystem-related signalling only or not:• 0: PDP context is not for IM CN subsystem-related signalling only
• 1: PDP context is for IM CN subsystem-related signalling only
Indicates that the PDP context provides connectivity using a LIPA PDN connection.
This parameter cannot be set by the TE:• 0: indication not received that the PDP context provides connectivity using a LIPAPDN connection• 1: indication received that the PDP context provides connectivity using a LIPA PDN
connection
Provides the IPv4 MTU size in octets.
Indicates whether the traffic can be offloaded using the specified PDN connection
via a WLAN or not. This refers to bits 1 and 2 of the WLAN offload acceptability IE as
specified in 3GPP TS 24.008 [12] subclause 10.5.6.20. Allowed values:• 0: offloading the traffic of the PDN connection via a WLAN when in S1 mode or whenin Iu mode is not acceptable• 1: offloading the traffic of the PDN connection via a WLAN when in S1 mode is
acceptable, but not acceptable in Iu mode
• 2: offloading the traffic of the PDN connection via a WLAN when in Iu mode is
acceptable, but not acceptable in S1 mode
• 3: offloading the traffic of the PDN connection via a WLAN when in S1 mode or whenin Iu mode is acceptable
Indicates whether or not the MS and the network support local IP address in TFTs
(see 3GPP TS 24.301 [68] and 3GPP TS 24.008 [12] subclause 10.5.6.3). Allowed
values:• 0: indicates that the MS or the network or both do not support local IP address in
TFTs• 1: indicates that the MS and the network support local IP address in TFTs

18 Packet switched data services

Page 456 of 1001

u-blox cellular modules - AT commands manual

18.45.4 Notes
TOBY-L2 / MPCI-L2• <IPv4_MTU>, <WLAN_offload> and <Local_Addr_Ind> parameters are not supported.
TOBY-L4 / LARA-R2 / TOBY-R2• The <cid> parameter is mandatory.
• <IPv4_MTU>, <WLAN_offload> and <Local_Addr_Ind> parameters are not supported.

18.46 Configure the initial EPS bearer / PDP context+UCGDFLT+UCGDFLT
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

18.46.1 Description
Configures the initial PDP context, i.e. sets the configuration of the PDN activated at attach time in LTE
network. The configuration can be optionally saved in NVM.
Once registered, the initial default bearer will obtain a <cid> context identifier by the rules described in AT+CGDCONT command. The active context configuration will be available through standard 3GPP TS 27.007 [2]AT commands, by using this <cid> context identifier.
The AT+CGDCONT command cannot be used to define the initial PDP context even though a valid <cid> isassigned at its activation.
If the module is already registered to a LTE network the user is required to:• Deregister with AT+CFUN=4• Change the initial PDP context configuration with AT+UCGDFLT• Register again with AT+CFUN=1 (the MT is set now to full functionality, the registration will start if manualor automatic registration was previously set)
In case <cid>=4 has been already defined via +CGDCONT (to be avoided), the <cid> for the initial default
EPS bearer will be selected in the following order [3,2,1,5,6,7,8]. It is recommended to leave <cid>=4
undefined.
The DNS request parameters, <dns_v6> and <dns_v4> are aligned / linked with the <PDP_type>parameter.

18.46.2 Syntax
Type
Set

Read

SyntaxResponse
AT+UCGDFLT=<nvm_mode>[,OK<PDP_type>[,<APN>[,<emg_ind>[,<ipcp_req>[,<pcscf_v6>[,<imcn_
sig>[,<dns_v6>[,<nw_bear>[,<dsm_
v6_ha>[,<dsm_v6_pref>[,<dsm_
v6_ha_v4>[,<ip_via_nas>[,<ip_via_dhcp>[,<pcscf_v4>[,<dns_v4>[,<msisdn>[,<ifom>[,<v4mtu>[,<local_tft>[,<auth_type>[,<auth_user>[,<auth_pass>[,<vendor_
specific>[,<NSLPI>]]]]]]]]]]]]]]]]]]]]]]]]
AT+UCGDFLT?
+UCGDFLT: <PDP_type>,<APN>,<emg_ind>,<ipcp_req>,<pcscf_v6>,<imcn_sig>,<dns_v6>,<nw_bear>,<dsm_v6_ha>,<dsm_v6_pref>,<dsm_v6_ha_v4>,<ip_via_nas>,<ip_
via_dhcp>,<pcscf_v4>,<dns_v4>,<msisdn>,<ifom>,<v4mtu>,<local_
tft>,,,<vendor_specific>,<NSLPI>UBX-13002752 - R67

18 Packet switched data services

ExampleAT+UCGDFLT=1,"IPV4V6","IMS"OK+UCGDFLT: "IPV4V6","IMS",0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,,,"FF00
FF01FF02FFFF"
OK

Page 457 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+UCGDFLT=?

Response
OK
For each <PDP_type>:+UCGDFLT: (list of supported<nvm_mode>s),<PDP_type>,,(listof supported <emg_ind>s),(listof supported <ipcp_req>s),(listof supported <pcscf_v6>s),(listof supported <imcn_sig>s),(listof supported <dns_v6>s),(list of
supported <nw_bear>s),(list of
supported <dsm_v6_ha>s),(listof supported <dsm_v6_pref>s),(list of supported <dsm_v6_ha_v4>s),(list of supported <ip_via_nas>s),(list of supported <ip_via_dhcp>s),(list of supported <pcscf_v4>s),(list of suppored <dns_v4>s),(list of supported <msisdn>s),(list of supported <ifom>s),(listof supported <v4mtu>s),(list of
supported <local_tft>s),(list of
supported <auth_type>s),,,[,(list of
supported <NSLPI>s)]

Example+UCGDFLT: (0-1),"IP",,(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(02),,,+UCGDFLT: (0-1),"IPV6",,(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(01),(0-2),,,+UCGDFLT: (0-1),"IPV4V6",,(0-1),(01),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(01),(0-1),(0-1),(0-1),(0-1),(0-1),(0-1),(01),(0-1),(0-2),,,
OK

[..]
OK

18.46.3 Defined values
Parameter<nvm_mode>

Type
Number<PDP_type><APN><emg_ind>

StringStringNumber<ipcp_req>

Number<pcscf_v6>

Number<icmn_sig>

Number<dns_v6>

Number<nw_bear><dsm_v6_ha><dsm_v6_pref><dsm_v6_ha_v4><ip_via_nas>

NumberNumberNumberNumberNumberUBX-13002752 - R67

Description
State configuration:• 0: set the initial PDP configuration without saving it in NVM• 1: set and save the initial PDP configuration
Configures the PDP context type. The default type is "IP".
Configures the PDN's APN name. The default value is "".
Indicates whether the context is for emergency bearer services or not:• 0 (default value): PDP context is not for emergency bearer services• 1: PDP context is for emergency bearer services
PCO option related to IPCP. See 3GPP TS 24.008 [12] ch. 10.5.6.3:• 0 (default value): request disabled• 1: request enabled
PCO option related to P-CSCF IPv6 server discovery. See 3GPP TS 24.008 [12] ch. 10.5.6.3:• 0 (default value): request disabled• 1: request enabled
PCO option related to IM-CN subsystem signalling bearer. See 3GPP TS 24.008 [12]ch. 10.5.6.3:• 0 (default value): request disabled• 1: request enabled
PCO option related to DNSv6 server discovery. See 3GPP TS 24.008 [12] ch. 10.5.6.3:• 0 (default value): request disabled• 1: request enabled
Reserved for future use
Reserved for future use
Reserved for future use
Reserved for future use
PCO option related to IP address assignation via NAS signalling. See 3GPP TS 24.008[12] ch. 10.5.6.3:• 0: request disabled• 1 (default value): request enabled

18 Packet switched data services

Page 458 of 1001

u-blox cellular modules - AT commands manual

Parameter<ip_via_dhcp>

Type
Number<pcscf_v4>

Number<dns_v4>

Number<msisdn><ifom><v4mtu><local_tft><auth_type>

NumberNumberNumberNumberNumber<auth_user>

String<auth_pass>

String<vendor_specific>

String<NSLPI>

NumberDescription
PCO option related to IP address assignation via DHCP. See 3GPP TS 24.008 [12] ch.
10.5.6.3:• 0 (default value): request disabled• 1: request enabled
PCO option related to P-CSCF IPv4 server discovery. See 3GPP TS 24.008 [12] ch. 10.5.6.3:• 0 (default value): request disabled• 1: request enabled
PCO option related to DNSv4 server discovery. See 3GPP TS 24.008 [12] ch. 10.5.6.3:• 0: request disabled• 1 (default value): request enabled
Reserved for future use
Reserved for future use
Reserved for future use
Reserved for future use
Configure the authentication:• 0 (default value): no authentication• 1: PAP• 2: CHAP
Username. The maximum length is 50 characters, the default value is the NULL
string.
Password. The maximum length is 50 characters, the default value is the NULL
string.
Vendor specific PCO. If given, the string must be "" or a combination of hexadecimal
digit quadruplets d.d.d.d in range [FF00-FFFF]. Allowed examples:• "FF00"• "FF00FF01FF02FFFF"• "FF00FFFF"• ""The default value is the empty string "", which disables the PCO.
Indicates the NAS signalling priority requested for the corresponding PDP context:• 0 (default value): indicates that the PDP context has to be activated with the value
for the low priority indicator configured in the MT.
• 1: indicates that the PDP context has to be activated with the value for the low
priority indicator set to "MS is not configured for NAS signalling low priority".
The MT utilises the provide NSLPI information as specified in 3GPP TS 24.301 [68]and 3GPP TS 24.008 [12].

18.46.4 Notes
TOBY-L2 / MPCI-L2• The <NSLPI> parameter is not supported.
TOBY-L200 / TOBY-L201 / MPCI-L200 / MPCI-L201• The factory-programmed value of <APN> parameter is "broadband" (AT&T).
TOBY-L210-00S / TOBY-L210-02S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L210-60S / TOBY-L220 /TOBY-L280 / MPCI-L210 / MPCI-L220 / MPCI-L280• The factory-programmed value of <APN> parameter is an empty string.
TOBY-L210-62S / TOBY-L210-65S• The factory-programmed value of <APN> parameter is "4gsmartphone"; <APN> parameter cannot be
set to an empty string.
• A single data PDP context is allowed; hence the <PDP_type> parameter can be set only to "IP".

UBX-13002752 - R67

18 Packet switched data services

Page 459 of 1001

u-blox cellular modules - AT commands manual

18.47 Always-On mode parameters settings +CGPERMSET+CGPERMSET
Modules
LISA-U270-62S LISA-U270-63S LISA-U270-68S
SyntaxPIN required
Settings saved Can be aborted
Attributes
full
No
No
No

Response time-Error reference+CME Error

18.47.1 Description
Sets the APN, user ID, password and the Keep Alive timer for the Always-On mode. If the command sets theparameter value out of the allowed range, an ERROR result code is returned whatever is the configuration of+CMEE command.
For sake of simplicity in <cid> management, <cid> uniquely identifies a PDP context within the module. Such
PDP context may be defined either with +CGPERMSET or with +CGDCONT command and no check is internallydone in SW on which cid has been configured with which command. This assures large flexibility in handlingthe 11 definable PDP contexts. It is recommended to exploit the whole cid range and to assign Always on PDP
contexts and other PDP contexts different <cid> values.

18.47.2 Syntax
Type
Set
Read

SyntaxAT+CGPERMSET=<cid>,<apn>,<id>,<pwd>[,<time>]
AT+CGPERMSET?

Test

AT+CGPERMSET=?

Response
OK

ExampleAT+CGPERMSET: <cid>,<apn>,<id>,<pwd>,<time>OK+CGPERMSET: (list of supported<cid>s),,,,(list of supported <time>s)OK

18.47.3 Defined values
Parameter
<cid>
<APN>
<id>
<pwd>
<time>

Type
NumberStringStringStringNumberDescription
See Chapter 18.1.3.2
See Chapter 18.1.3.1
User ID to be used in Always-On mode
Password to be used in Always-On mode
Value expressed in minutes of Keep Alive Time to be used in Always-On mode
The range goes from 60 to 600. The default value is 120 (min)18.48 Always-On mode settings +CGPERMACT+CGPERMACT
Modules
LISA-U270-62S LISA-U270-63S LISA-U270-68S
SyntaxPIN required
Settings saved Can be aborted
Attributes
full
No
No
No

Response time-Error reference+CME Error

18.48.1 Description
Sets the Always-On mode / On-Demand mode. A protocol level error causes the issuing of the+ALWAYSONERROR URC. If the command sets the parameter value out of the allowed range, an ERROR result
code is returned whatever is the configuration of +CMEE command.

18.48.2 Syntax
Type
Set
Read

SyntaxAT+CGPERMACT=<cid>,<mode>
AT+CGPERMACT?

Response
OK
AT+CGPERMACT: <cid>,<mode>

ExampleOK

UBX-13002752 - R67

18 Packet switched data services

Page 460 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+CGPERMACT=?

Response
Example+CGPERMACT: (list of supported<cid>s),(list of supported <mode>s)
OK+ALWAYSONERROR

URC

OK

18.48.3 Defined values
Parameter<cid><mode>

Type
NumberNumberDescription
See Chapter 18.1.3.2
Mode set for the module••

0: On-Demand mode
1: Always-On mode

18.49 Always-On mode check state +CGPERMSTATE+CGPERMSTATE
Modules
LISA-U270-62S LISA-U270-63S LISA-U270-68S
SyntaxPIN required
Settings saved Can be aborted
Attributes
full
No
No
No

Response time-Error reference+CME Error

18.49.1 Description
Returns the Always-On state on which the module currently belongs.

18.49.2 Syntax
Type
Read

SyntaxAT+CGPERMSTATE?

Response
ExampleAT+CGPERMSTATE: <cid>,<mode> If the On-Demand mode is disabled:
OK+CGPERMSTATE: ,0
OK
Otherwise:+CGPERMSTATE: 1,0
OK

Test

AT+CGPERMSTATE=?

+CGPERMSTATE: (list of supported<cid>s),(list of supported <state>s)OK

18.49.3 Defined values
Parameter<cid><state>Type
NumberNumberDescription
See Chapter 18.1.3.2
State to which the module belongs
•
•
•
•
•

UBX-13002752 - R67

0: On-Demand mode state
1: Always-On active state
2: Always-On stand-by state
3: Always-On pending state
4: other unknown state

18 Packet switched data services

Page 461 of 1001

u-blox cellular modules - AT commands manual

18.50 Traffic flow template +CGTFT+CGTFT
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.50.1 Description
Allows the TE to specify a packet filter (PF) for a traffic flow template (TFT) that is used in the gateway GPRS
support node (GGSN) for routing of down-link packets onto different QoS flows towards the TE (see the 3GPPTS 23.060 [10] and 3GPP TS 24.008 [12]). A TFT is identified by a <packet filter identifier> and each packet filter
also has an <evaluation precedence index>. The set command specifies a Packet Filters to be added to the TFT
stored in the MT and used for the context identified by <cid>. This command is effectively an extension of the+CGDCONT and +CGDSCONT AT commands that shall be issued previously.
The syntax +CGTFT=<cid> causes all of the Packet Filters in the TFT for the specified <cid> to become
undefined.
Not all the parameters combinations are allowed in a Packet Filter, some may coexist but others are mutually
exclusive. The possible combinations are specified in 3GPP TS 23.060 [10].
TOBY-L4 / TOBY-L2 / MPCI-L2
After the PDP context activation, the information text response to the read command provides theconfiguration negotiated with the network (similarly to +CGTFTRDP and +CGCONTRDP AT commands).
A valid packet filter must contain a unique identifier and a unique evaluation precedence index within
all TFTs for one PDP address. The network will reject the activation of a secondary PDP context if thecorresponding packet filter contains an identifier or an evaluation precedence index which is not unique
within all TFTs for one PDP address.

18.50.2 Syntax
Type
Set

Read

SyntaxResponse
ExampleAT+CGTFT=[<cid>,<packet_filter_ OK
AT+CGTFT=2,1,1,"10
identifier>,<evaluation_precedence_
9.115.183.216.255.255.0.0"
index>[,<remote_address_and_OKsubnet_mask>[,<protocol_number_(ipv4)-next_header_(ipv6)>[,<destination_port_range>[,<source_
port_range>[,<ipsec_security_
parameter_index_(spi)>[,<type_of_service_(tos)_(ipv4)_and_masktraffic_class_(ipv6)_and_mask>[,<flow_label (ipv6)>[,<direction>[,<local_address_and_subnet_mask>]]]]]]]]]]]
AT+CGTFT?
+CGTFT: <cid>,<packet_filter_+CGTFT: 2,1,1,"10
identifier>,<evaluation_precedence_ 9.115.183.216.255.255.0.0",0,"0.0","0index>,<remote_address_and_.0",00000000,"0.0",00000
subnet_mask>,<protocol_number_OK(ipv4)-next_header_(ipv6)>,<destination_port_range>,<source_
port_range>,<ipsec_security_
parameter_index_(spi)>,<type_of_service_(tos)_(ipv4)_and_masktraffic_class_(ipv6)_and_mask>,<flow label (ipv6)>,<direction>,<local_address_and_subnet_mask>[+CGTFT: <cid>,<packet_filter_
identifier>,<evaluation_precedence_index>,<remote_address_and_subnet_mask>,<protocol_number_

UBX-13002752 - R67

18 Packet switched data services

Page 462 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Example(ipv4)-next_header_(ipv6)>,<destination_port_range>,<source_
port_range>,<ipsec_security_
parameter_index_(spi)>,<type_of_service_(tos)_(ipv4)_and_masktraffic_class_(ipv6)_and_mask>,<flow_label (ipv6)>,<direction>,<local_address_and_subnet_mask>[...]]Test

AT+CGTFT=?

OK+CGTFT: <PDP_type>,(list+CGTFT: IP,(1-16),(0of supported <packet_filter_
255),("0.0.0.0.0.0.0.0identifier>s),(list of supported
255.255.255.255.255.255.255.255"),<evaluation_precedence_index>s), (0-255),("0.0-65535.65535"),(list of supported <remote_address_ ("0.0-65535.65535"),(000000
and_subnet_mask>s),(list of
00-ffffffff),("0.0-255.255"),(00
supported <protocol_number_
000-FFFFF),("0.0.0.0.0.0.0.0(ipv4)-next_header_(ipv6)>s),(list255.255.255.255.255.255.255.255")
of supported <destination_port_
OK
range>s),(list of supported <source_
port_range>s),(list of supported<ipsec_security_parameter_index_(spi)>s),(list of supported <type_of_service_(tos)_(ipv4)_and_mask-traffic_class_(ipv6)_and_mask>s),(list of supported <flow_
label (ipv6)>s),(list of supported<direction>s),(list of supported<local_address_and_subnet_mask>s)[+CGTFT: <PDP_type>,(listof supported <packet_filter_
identifier>s),(list of supported<evaluation_precedence_index>s),(list of supported <source_address_
and_subnet_mask>s),(list of
supported <protocol_number_(ipv4)-next_header_(ipv6)>s),(listof supported <destination_port_
range>s),(list of supported <source_
port_range>s),(list of supported<ipsec_security_parameter_index_(spi)>s),(list of supported <type_of_service_(tos)_(ipv4)_and_mask-traffic_class_(ipv6)_and_mask>s),(list of supported <flow_
label (ipv6)>s),(list of supported<direction>s),(list of supported<local_address_and_subnet_mask>s)[...]]
OK

18.50.3 Defined values
Parameter<cid><PDP_type><packet_filter_identifier>Type
NumberStringNumberDescription
See <cid>
See <PDP_type>
Packet filter:• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 - Range:
1-16• SARA-U2 / LISA-U2 / LISA-U1 - Range: 1-8

UBX-13002752 - R67

18 Packet switched data services

Page 463 of 1001

u-blox cellular modules - AT commands manual

Parameter<evaluation_precedence_index>

Type
Number<remote_address_and_subnet_mask>

String<protocol_number_(ipv4)-next_header_(ipv6)>

Number<destination_port_range>

String<source_port_range>

String<ipsec_security_parameter_index_(spi)>

Number<type_of_service_(tos)_(ipv4)_and_masktraffic_class_(ipv6)_and_mask>

String<flow_label(ipv6)>

Number<direction>

Number<local_address_and_subnet_mask>

StringDescription
Evaluation precedence index that is unique within all TFTs
associated with the PDP contexts that share the same PDP
address:• Range: 0-255 (from highest evaluation precedence to lowest
evaluation precedence)Specifies the remote address and subnet mask attribute of avalid packet filter. Consists of dot-separated numeric (0-255)
parameters on the form:• "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
• "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16" for IPv6
Specifies the Protocol Number / Next Header attribute of a valid
packet filter. It shall contain either an IPv4 Protocol Number oran IPv6 Next Header value:• Range: 0-255
String parameter given as dot-separated numbers on the form
"f.t" that specifies the destination port range attribute of avalid packet filter:• Range: 0-65535
Dot-separated numbers on the form "f.t" that specifies thesource port range attribute of a valid packet filter:• Range: 0-65535
IPSec SPI attribute of a valid packet filter which is a 32-bit field:• Range: 00000000-FFFFFFFF
Dot-separated numbers on the form "t.m" that specifies theType of Service / Traffic Class and Mask attribute of a valid
packet filter. It shall contain either an IPv4 TOS octet or an IPv6
Traffic Class octet along with a mask defining which of the 8bits should be used for matching.
• Range: 0-255
Specifies the Flow Label attribute of a valid packet filter. It shallcontain an IPv6 flow label, which is a 20-bit field. It only is valid
for IPv6.
• Range: 00000-FFFFF
Specifies the transmission direction in which the packet filter
shall be applied:• 0: Pre Release 7 TFT Filter (see 3GPP TS 24.008 [12], table 10.5.162)• 1: uplink• 2: downlink• 3: bidirectional (used for uplink and downlink)
Specifies the local address and subnet mask attribute of avalid packet filter. Consists of dot-separated numeric (0-255)
parameters on the form:• "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
• "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16" for IPv6

18.50.4 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2• The <local_address_and_subnet_mask> parameter is not supported .
LISA-U2 / LISA-U1• The <local_address_and_subnet_mask> parameter is not supported .
• The read command's information text response does not display the <source_address_and_subnet_mask> parameter entirely in dotted notation, i.e. characters [ and ] are used to separate subnet maskfrom source address.
• <flow_label(ipv6)>=00000 is only supported.

UBX-13002752 - R67

18 Packet switched data services

Page 464 of 1001

u-blox cellular modules - AT commands manual

LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1• The IPv6 stack for an external context is not supported: hence the IPv6 version is not supported.

18.51 Read counters of sent or received PSD data +UGCNTRD+UGCNTRD
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
full
Yes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.51.1 Description
Allows reading the counters for total sent / received bytes for each defined context.
For each active <cid> one result code line is provided by the DCE.
Only if the specific PDP context parameter values for a PDP context are set.
The sent / received bytes are the gross payload evaluated by the protocol stack, therefore they comprise
the TCP and IP header bytes and the packets used to open and close the TCP connection.

18.51.2 Syntax
Type
ActionSyntaxAT+UGCNTRD

Response+UGCNTRD: <cid>,<sent_sess_bytes>,<received_sess_bytes>,<sent_total_bytes>,<received_
total_bytes>

ExampleAT+UGCNTRD+UGCNTRD: 1,100,0,100,0OK[[...]+UGCNTRD: <cid>,<sent_sess_bytes>,<received_sess_bytes>,<sent_total_bytes>,<received_
total_bytes>]]
Test

AT+UGCNTRD=?

OK
OK

18.51.3 Defined values
Parameter<cid><sent_sess_bytes><received_sess_bytes><sent_total_bytes><received_total_
bytes>

UBX-13002752 - R67

Type
NumberNumberNumberDescription
Local PDP context identifier; the range goes from 0 to 255.
Sent bytes for the current PSD session.
Received GPRS session bytes for the current PSD session.

NumberNumberTotal sent bytes.
Total received bytes.

18 Packet switched data services

Page 465 of 1001

u-blox cellular modules - AT commands manual

18.52 Set/reset counter of sent or received PSD data
+UGCNTSET+UGCNTSET
Modules

Attributes

TOBY-L4
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
partialYes

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

18.52.1 Description
Allows setting the counter for total sent/received bytes for each defined context to zero or any other offset
value.
Whenever the total counter for a <cid> is set (to zero or a certain value), the session counter for this <cid>will be set to zero.
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
If <cid>=0 than the total counter for every defined context is set to zero. The offset parameters are
ignored in this case.

18.52.2 Syntax
Type
Set

Test

SyntaxAT+UGCNTSET=<cid>,[<total_
bytes_sent_offset>,<total_bytes_
received_offset>]
AT+UGCNTSET=?

Response
OK

ExampleAT+UGCNTSET=0,20,20
OK+UGCNTSET: (range of <cid>s),(range of <total_bytes_sent_
offset>),(range of <total_bytes_
received_offset>)+UGCNTSET: (0-255),(02147483646),(0-2147483646)
OKOK

18.52.3 Defined values
Parameter
<cid>

Type
Number<total_bytes_sent_
offset><total_bytes_
received_offset><sim_id>

NumberNumberNumberDescription
Local PDP context identifier:• TOBY-L4 - the range goes from 0 to 4
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 - the range goesfrom 0 to 255• LEON-G1 - the range goes from 0 to 3
Long number containing the offset of total sent bytes used for counting in the range
0-0x7FFFFFFE.
Long number containing the offset of total received bytes used for counting in therange 0-0x7FFFFFFE.
SIM identity. Only value 0 is supported.

18.52.4 Notes
LEON-G1• It is not possible to set the counters of the internal PDP contexts.
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• The <sim_id> parameter is not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 466 of 1001

u-blox cellular modules - AT commands manual

18.53 Uplink user data plane configuration +UDCONF=9+UDCONF=9
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

18.53.1 Description
Enables or disables the uplink user data plane. When the uplink data traffic is disabled, the module will not beable to transmit data to the cellular network.
In bridge mode the uplink packets are forwarded to the active EPS bearer/PDP context based on the packet
source IP address. When the source IP address does not match to the IP address of any active EPS bearers/PDP
context, the module will drop the packet. This uplink data plane filtering can be disabled with <UUDP_enable>=
2. The filter can be disabled only in bridge mode. The filter will be restored after the system reboot when themodule is set in router mode (for more details, see the AT+UBMCONF command).
Only primary EPS bearer/PDP contexts are suitable for the transmission.
The IP range source based routing in bridge mode forwards the packets through the specified EPS bearer/PDP
context on the basis of the packet source IP address. When no rule is specified the packets are dropped.
The VLAN source based routing in bridge mode forwards the packets through the specified EPS bearer/PDP
context on the basis VLAN ID of the packet received by the RNDIS interface. When no rule is specified thepackets are dropped.
The settings related to <UUDP_enable>=0, <UUDP_enable>=1 or 2 are applied at run time, saved in the NVM
and remain valid also after the module reboot.
The settings related to <UUDP_enable>=3 or 4 are applied at run time and not saved in the NVM.
The AT command does not affect the functionality of the +UTGSINK AT command.

18.53.2 Syntax
Type
SyntaxGeneral syntax
Set
AT+UDCONF=9,<UUDP_enable>[,<tag_cmd>[,<cid>,<ip_address>,<subnet_mask>]]
Read
AT+UDCONF=9[,<UUDP_enable>,<tag_cmd>]

Response

ExampleOK

AT+UDCONF=9,1

Read+UDCONF: 9,<UUDP_enable>

OK
AT+UDCONF=9

OK+UDCONF: 9,1

OK+UDCONF: 9,<UUDP_enable>[,<tag_ AT+UDCONF=9
cmd>[,<cid>,<ip_address>,<subnet_+UDCONF: 9,1
mask>]]
OK
OK
Uplink user data plane enable / disable (<UUDP_enable>=0, 1, 2)
Set
AT+UDCONF=9,<UUDP_enable>
OK
AT+UDCONF=9,1
AT+UDCONF=9

OK
Add rule to the IP range source based routing
Set
AT+UDCONF=9,3,0,<cid>,<ip_address>,<subnet_mask>

OK

AT+UDCONF=9,3,0,3,"192.168.3.120","255.255.255.192"
OK

Delete rule to the IP range source based routing
Set
AT+UDCONF=9,3,1,<cid>,<ip_OKaddress>,<subnet_mask>

AT+UDCONF=9,3,1,3,"192.168.3.120","255.255.255.192"
OK

Delete all rules of the IP range source based routing
Set
AT+UDCONF=9,3,9OK

UBX-13002752 - R67

18 Packet switched data services

AT+UDCONF=9,3,9Page 467 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

List all rules of the IP range source based routing
Read
AT+UDCONF=9,3,8[+UDCONF: 9,3,8,<cid>,<ip_address>,<subnet_mask>[...]]
OK
Add rule to the VLAN source based routing
Set
AT+UDCONF=9,4,0,<cid>,<vlan_id> OK

ExampleOK
AT+UDCONF=9,3,8+UDCONF: 9,3,8,3,"192.168.3.120","255.255.255.192"
OK
AT+UDCONF=9,4,0,3,"3001"
OK

Delete rule to the VLAN source based routing
Set
AT+UDCONF=9,4,1,<cid>,<vlan_id> OK

AT+UDCONF=9,4,1,3,"3001"
OK

Delete all rules of the VLAN source based routing
Set
AT+UDCONF=9,4,9OK

AT+UDCONF=9,4,9OK

List all rules of the VLAN source based routing
Read
AT+UDCONF=9,4,8[+UDCONF: 9,4,8,<cid>,<vlan_id>

AT+UDCONF=9,4,8[...]]+UDCONF: 9,4,8,3,"3002"

OKOK

18.53.3 Defined values
Parameter<UUDP_enable>

Type
Number<tag_cmd>

Number<cid><ip_address><subnet_mask><vlan_id>

NumberStringStringStringDescription
Configures the uplink user data plane feature:• 0: uplink user data plane disabled• 1 (factory-programmed value): uplink user data plane enabled• 2: uplink user data plane filter disabled• 3: IP range source based routing for bridge mode
• 4: VLAN source based routing for bridge mode
Allowed values:• TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S /TOBY-L280-03A / TOBY-L280-03S - 0, 1, 2, 3. See Notes for more details.
• TOBY-L200-00S / TOBY-L200-02S / TOBY-L201 / TOBY-L210-00S /TOBY-L210-02S / TOBY-L210-60S / TOBY-L210-62S / TOBY-L210-65S /TOBY-L220 / TOBY-L280-02S / MPCI-L2 - 0, 1
Configures the source based routing:• 0: add rule
• 1: delete rule
• 8: list all rules• 9: delete all rules
Context indentifier
IPv4/IPv6 address
IPv4/IPv6 subnet mask
VLAN ID of the 802.1Q protocol

18.53.4 Notes
TOBY-L200-03S / TOBY-L210-03S / TOBY-L280-03S• <UUDP_enable>=2 is not supported by TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L280-03S-00.
• <UUDP_enable>=3 is not supported by TOBY-L200-03S-01, TOBY-L210-03S-01, TOBY-L210-03S-34,
TOBY-L280-03S-01, TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L280-03S-00.
• <UUDP_enable>=4 is not supported by TOBY-L200-03S-01, TOBY-L210-03S-01, TOBY-L210-03S-34,
TOBY-L280-03S-01, TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L280-03S-00.

UBX-13002752 - R67

18 Packet switched data services

Page 468 of 1001

u-blox cellular modules - AT commands manual

TOBY-L200-03A / TOBY-L210-03A / TOBY-L280-03A• <UUDP_enable>=3 is not supported by TOBY-L200-03A-00, TOBY-L210-03A-01, TOBY-L210-03A-01,
TOBY-L280-03A-01.
TOBY-L200-03A / TOBY-L210-03A / TOBY-L280-03A• <UUDP_enable>=4 is not supported by TOBY-L200-03A-00, TOBY-L210-03A-01, TOBY-L210-03A-01,
TOBY-L280-03A-01.

18.53.5 Examples
Command

Response

AT+UDCONF=9,2
OK
Add two rules
AT+UDCONF=9,3,0,2,"192.168.1.100 OK","255.255.255.0"
AT+UDCONF=9,3,0,5,"192.168.2.10", OK"255.255.255.192"
AT+UDCONF=9,3,8+UDCONF: 9,3,8,2,"192.168.1.100","255.255.255.0"

Description
Define and activate context identifiers 2
and 5.
Disable the uplink filter.
Add rule 1.
Add rule 2.
List all defined rules: 2 rules are present.

+UDCONF: 9,3,8,5,"192.168.2.10","255.255.255.192"
OK
Delete one rule
AT+UDCONF=9,3,1,2,"192.168.1.100 OK","255.255.255.0"
AT+UDCONF=9,3,8+UDCONF: 9,3,8,5,"192.168.2.10","255.255.255.192"
OK
AT+UDCONF=9,3,1,5,"192.168.2.10", OK"255.255.255.192"
AT+UDCONF=9,3,8OK
Add two rules
AT+UDCONF=9,3,0,5,"192.168.2.10", OK"255.255.255.192"
AT+UDCONF=9,3,0,7,"192.168.3.10", OK"255.255.255.192"
AT+UDCONF=9,3,8+UDCONF: 9,3,8,5,"192.168.2.10","255.255.255.192"

Delete rule 1.
List all defined rules: one rule is present.

Delete rule 2.
List all defined rules: no rules present.
Add rule 1.
Add rule 2.
List all defined rules: 2 rules are present.

+UDCONF: 9,3,8,7,"192.168.3.10","255.255.255.192"
OK
Delete all rules
AT+UDCONF=9,3,9OK
AT+UDCONF=9,3,8
OK
Packet transmission on context identifier 2

Considering that the IP address of the
RNDIS interface is 192.168.1.100/24 (see+UIPCONF AT command).
Enable IPDUMP to monitor on which
context identifier the packets aretransmitted.
Define and activate context identifiers 1
and 2.
With the rule the packets are trasmitted
on context identifier 2. Without therule the packets are trasmitted on thefirst active context identifier (context
identifier 1).

AT+UDCONF=9,3,0,2,"192.168.1.100 OK","255.255.255.0"

UBX-13002752 - R67

Delete all defined rules.
List all defined rules: no rules present.

18 Packet switched data services

Page 469 of 1001

u-blox cellular modules - AT commands manual

Command

Response

AT+UDCONF=9,2
Add two rules
AT+UDCONF=9,4,0,2,"3001"
AT+UDCONF=9,4,0,5,"3002"
AT+UDCONF=9,4,8

OK

Description
Define and activate context identifiers 2
and 5.
Disable the uplink filter.

OK
OK+UDCONF: 9,4,8,2,"3001"

Add rule 1.
Add rule 2.
List all defined rules: 2 rules are present.

+UDCONF: 9,4,8,5,"3002"
OK
Delete one rule
AT+UDCONF=9,4,1,2,"3001"
AT+UDCONF=9,4,8
AT+UDCONF=9,4,1,5,"3002"
AT+UDCONF=9,4,8
Add two rules
AT+UDCONF=9,4,0,5,"3001"
AT+UDCONF=9,4,0,7,"3002"
AT+UDCONF=9,4,8

OK+UDCONF: 9,4,8,5,"3002"

Delete rule 1.
List all defined rules: one rule is present.

OK
OK
OK

Delete rule 2.
List all defined rules: no rules present.

OK
OK+UDCONF: 9,4,8,5,"3001"

Add rule 1.
Add rule 2.
List all defined rules: 2 rules are present.

+UDCONF: 9,4,8,7,"3002"
OK
Delete all rules
AT+UDCONF=9,4,9OK
AT+UDCONF=9,4,8
OK
Packet transmission on context identifier 2

AT+UDCONF=9,3,0,2,"3001"

Delete all defined rules.
List all defined rules: no rules present.
Considering that the VLAN of the RNDISinterface is 3001. The RNDIS of the hosthas defined two IP addresses. One ofthem is defined for a virtual LAN with
VLAN ID 3001.
Enable IPDUMP to monitor on which
context identifier the packets aretransmitted.
Define and activate context identifiers 1
and 2.
With the rule the packets with VLAN ID
3001 are trasmitted on context identifier
2. Without the rule the packets are
dropped.

OK

18.54 Feature Group Indicators (FGI) settings +UFGI+UFGI
Modules

Attributes

TOBY-L4 TOBY-L200-03A TOBY-L200-03S TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S
TOBY-L210-65S TOBY-L280-03A TOBY-L280-03S MPCI-L200-03S MPCI-L210-03S MPCI-L280-03S
LARA-R2 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

18.54.1 Description
Displays the contents of the FGI bits stored on the module that are reported during the LTE registration to the
network as part of the UE-EUTRA-Capability information element. The description of each bit can be found in
3GPP TS 36.331 [87], Annex B.

UBX-13002752 - R67

18 Packet switched data services

Page 470 of 1001

u-blox cellular modules - AT commands manual

18.54.2 Syntax
Type
Read

Syntax
AT+UFGI?

Response
Example+UFGI: <FGI>,<FGI_rel9>,<FGI_rel10 +UFGI: 4291821242,3229614080,340
>
7872
OK

OK

18.54.3 Defined values
Parameter
<FGI>

Type
Number<FGI_rel9>

Number<FGI_rel10>

NumberDescription
32 bits number that describes bits 1-32 of featureGroupIndicators. The leftmost bit
represents index 1 in the field featureGroupIndicators.
32 bits number that describes bits 33-64 of featureGroupIndRel9Add. The leftmost
bit represents index 33 in the field featureGroupIndRel9Add.
32 bits number that describes bits 101-132 of featureGroupIndRel10Add. The leftmost
bit represents index 101 in the field featureGroupIndRel10Add.

18.54.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• <FGI_rel10> is not supported.

UBX-13002752 - R67

18 Packet switched data services

Page 471 of 1001

u-blox cellular modules - AT commands manual

19 System features
19.1 Firmware installation +UFWINSTALL+UFWINSTALL
Modules
TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U200-83S LISA-U201-04B
LISA-U201-83S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
No
No
FW Install Error

19.1.1 Description
Triggers the FW installation procedure, starting from the file (update binary file) stored in the module filesystem. It could be used as a part of implementation of the FOTA procedure. The command causes a SW
system reset with network deregistration.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
During the update process, the device cannot be used to make calls, even emergency calls. The updateprocess is fault tolerant, even if the battery is suddenly removed.
At the end of a successful installation, the main firmware software boots up, NVM and profiles data are
set to the factory-programmed values of the new firmware version and the SIM is reset (the PIN will be
required if enabled).
Once the command has been sent correctly, the FW resets and at the next boot-up, the FW install will
start.
In case of power loss during the install phase, at the next module wake-up a fault is detected and themodule remains in Firmware Install Mode until the end of the procedure (install terminated).
The command syntax differs depending on the module: see the corresponding subsection for the correctcommand handling.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
The firmware can be updated using either the UART interface with configurable baud rate (only one port
is available) or the USB interface with configurable USB instance.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
During the update operations, the +UUFWINSTALL URC displays the progress indication and the result
operation on the interface chosen via the +UFWINSTALL command. When the FW update is completed,
a URC will notify the final result of the operation.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
For more details, see the Firmware Update Application Note [169].
TOBY-L4
The firmware can be updated over the USB CDC-ACM interface by means of the +UDWNFILE AT
command. After downloading the update file, the FW installation AT command can be postponed evenafter a module reboot.

19.1.2 TOBY-L4 syntax
Type
Set

Syntax
AT+UFWINSTALL

Response
OK

Test
URC

AT+UFWINSTALL=?

OK+UUFWINSTALL: <status_install>

UBX-13002752 - R67

19 System features

ExampleAT+UFWINSTALL
OK
OK

Page 472 of 1001

u-blox cellular modules - AT commands manual

19.1.3 TOBY-L4 defined values
Parameter<status_install>Type
Number/StringDescription
Provide the installation start message ("REBOOT" string) and the update result code
(see Firmware install final result codes).

19.1.4 TOBY-L2 / MPCI-L2 syntax
Type
Set

Syntax
AT+UFWINSTALL=<md5>Response
OK
UFWINSTALL REBOOT

ExampleAT+UFWINSTALL=a07a553420
1b2e42dd2d964920e57319
OK

Test

AT+UFWINSTALL=?

OK

UFWINSTALL REBOOT
OK

19.1.5 TOBY-L2 / MPCI-L2 defined values
Parameter
<md5>

Type
NumberDescription
32 hexadecimal number

19.1.6 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 syntax
Type
Set

Syntax
AT+UFWINSTALL=<filename>[,<Serial_Port_Number>[,<BaudRate>]]

Test

AT+UFWINSTALL=?

Response
OK

OK+UFWINSTALL: "filename",(list of+UFWINSTALL: "filename",(0,1,4-6),
supported <Serial_Port_Number>s), (19200,38400,57600,115200,23040(list of supported <BaudRate>s)0,460800,921600)
OK+UUFWINSTALL: <progress_
install>

URC

ExampleAT+UFWINSTALL="update_FW_90_to_91.upd",1,115200

OK

19.1.7 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 defined values
Parameter<filename>

Type
String<Serial_Port_
Number>Number<BaudRate>

NumberUBX-13002752 - R67

Description
The update filename from version 0 to version 1 which has been previously
downloaded in FS. The update file can have different extension
Serial interface where the progress percentage and the information text responses
will be sent:• 0: no info will be shown• 1: UART interface• 4: USB1• 5: USB2• 6: USB3
If omitted, the command will take as default value for <Serial_Port_Number> the port
where the command is issued.
Available baud rates expressed in b/s:
• 19200• 38400• 57600• 115200• 230400• 460800• 921600• 3000000• 3250000• 6000000• 6500000

19 System features

Page 473 of 1001

u-blox cellular modules - AT commands manual

Parameter<progress_install>Type

NumberDescription
When a USB interface is selected, the parameter has no effect in the FW installconfiguration.
If omitted, the command will take as default value for <BaudRate> the baud rate of
the port where the command is issued.
Provide the installation progress from 1 to 100 and the update result (seeFWINSTALL error result codes).

19.1.8 Notes
TOBY-L4• Store the update file into the module before starting the FW installation with the +UFWINSTALL AT
command. The procedure for storing is up to the user (via +UDWNFILE AT command).
• The +UFWINSTALL AT command checks only for the presence of the update file. Consistency checks
are done during the update procedure. If checks fail, the update file is left in the module file system anda proper URC with the error result code is issued after the final reboot (see Firmware install final result
codes).
• After the command is issued, the module reboots and starts the FW installation process which will takeabout 3-4 minutes long. During the update process, the module reboots multiple times. No intermediate
result codes are issued on the terminal during this phase.
• At the end of the FW update process the module reboots again with the new firmware installed; NVM,
profiles and the file system are restored to the factory-programmed values.
• The final result code will be issued on all the available interfaces after the FW update success or failure.
• If the FW update is successful, the update file is removed.
TOBY-L2 / MPCI-L2• After the command is issued, the module reboots and starts the install process which will take about
1 minute long. No result codes are issued on the terminal during this phase. At the end of the updateprocess the module reboots again with the new firmware installed, NVM, profiles and the file system
restored to the factory-programmed values.
• If the <md5> parameter is provided correctly (32 hex digits), then the check is done with the update filestored in the module.
• If the <md5> parameter is provided incorrectly (less digits, more digits, or at least one not hex digits),
then the install will not be started, and the module will exit from Firmware Install Mode and the actual
will continue to run. A proper error result code will be issued on the same channel where the commandhas been sent.
• Store the update file into the module cache folder before starting the install with +UFWINSTALL.
Otherwise the "update file not found" error result code is issued. The procedure for storing is up to theuser (via +UFTPC, +UHTTPC or +UDWNFILE). These commands erase the cache content before storing
the new update file.
• This command is not available if the encryption is enabled by means of the +USECCFG AT command. For
further information, see the +UFWSINSTALL AT command.
TOBY-L200-02S / TOBY-L201-01S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 /TOBY-L280 / MPCI-L200 / MPCI-L201-01S / MPCI-L210 / MPCI-L220 / MPCI-L280• The download of the FOTA file can be performed only by means of +UFTPC AT command.
TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A / TOBY-L210-03S / MPCI-L201-02S• On TOBY-L200-03S-00, TOBY-L201-02S-00, TOBY-L210-03S-00, TOBY-L210-03A-00 and
MPCI-L201-02S-00 products, the download of the FOTA file can be performed only by means of+UFTPC AT command.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• Store the update file into the module file system before starting the install with +UFWINSTALL.
Otherwise the "FFS file not found" error result code is issued. The procedure for FS storing is up to the user
(via FTP, +UDWNFILE). When the new FW has been installed, the user can optionally delete the "filename"using the file system AT commands (for more details see the +UDELFILE).
Command
AT+UFWINSTALL="update_
FW_90_to_91.upd",1,115200

UBX-13002752 - R67

Response

Description
The "OK" final result code is printed out just before theFW reset.

19 System features

Page 474 of 1001

u-blox cellular modules - AT commands manual

Command

Response+UUFWINSTALL: 1+UUFWINSTALL: 2+UUFWINSTALL: 3+UUFWINSTALL: 4....
+UUFWINSTALL: 9+UUFWINSTALL: 12+UUFWINSTALL: 15....
+UUFWINSTALL: 99+UUFWINSTALL: 100+UUFWINSTALL: 128

Description

The progression of installation is incremental (thesubsequent increment of <progress_install> can be
more than 1).

The installation is done when the percentage ends with+UUFWINSTALL: 100.
The last URC with a value greater than 100 indicatesthe update operation result (e.g. 128 means operation
completed with success (for more details see the
FWINSTALL error result codes).

Table 32: +UFWINSTALL example
SARA-U2 / LISA-U2• <BaudRate>= 3000000, 3250000, 6000000, 6500000 are not supported.

19.2 Firmware update Over AT (FOAT) +UFWUPD+UFWUPD
Modules

Attributes

TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference
FOAT Error

19.2.1 Description
Triggers the firmware update using the Xmodem or Xmodem-1k protocol.
The command syntax differs depending on the module series: see the corresponding subsection for the correctcommand handling.
The errors (data corruption, data loss, etc.) during the Update phase are internally handled by the Xmodem
protocol itself; for more details about the error result codes, see FOAT error result codes.
If no data comes to the module after having issued the AT+UFWUPD command, up to ten NACK are sent
and then Firmware Update Mode is dropped out coming back to normal mode; the FW is unchanged andstill useable (ERROR1).
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
NVM parameters and profiles (if affected by the update process) are set to the factory-programmed
values.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
For more details, see the u-blox Firmware Update Application Note [169].

19.2.2 TOBY-L2 / MPCI-L2 description
The FW update over AT commands is performed by means of a BIN file officially released by u-blox. To start
the process, the proper MD5 signature is needed.
Use the proper released file (*.bin) for Xmodem (128) or Xmodem-1k (1024) and use as <md5> value theMD5 signature of the file (*.zip) used with +UFWINSTALL AT command.
Maximum errors allowed (timeout, bad data) is 10, after that Xmodem exits with this error result code:

UBX-13002752 - R67

19 System features

Page 475 of 1001

u-blox cellular modules - AT commands manual

ERROR1TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S
If 10 errors are provided, the Xmodem exits with these strings:"too many errors; giving up"
ERROR1At the end of the download procedure, the module reboots and starts the update process which will take about
1 minute long. No result codes are issued on the terminal during this phase. At the end of the update process,the module reboots again with the new firmware installed, NVM, profiles and the file system restored to thefactory-programmed values.
Once the update file has been downloaded, if the <md5> parameter is provided correctly (32 hex digits), thenthe MD5 check is performed.
If the <md5> parameter is provided incorrectly (less digits, more digits, or at least one not hex digits), then thedownload will not be started, and the module will exit from Firmware Update Mode and the current FW will bestarted. A proper error result code will be issued on the same channel where the command has been sent.
In case of power loss during the update phase, at the next module wake-up a fault is detected and the module
remains in Firmware Update Mode expecting that the upload restarts from Xmodem handshake.
If the FW download ends with an ERROR1 condition, the module exits from Firmware Update Mode and returns
to normal mode since the FW is still unchanged and usable (FW not corrupted by previous download process).
TOBY-L200-00S / TOBY-L210-00S /MPCI-L210-60S / MPCI-L210-63S
The <md5> parameter is not mandatory.

TOBY-L210-60S/

MPCI-L200-00S/

MPCI-L210-00S/

19.2.3 TOBY-L2 / MPCI-L2 syntax
Type
Set

Syntax
AT+UFWUPD=<md5>Response+UFWUPD: ONGOING
CCC...
OK
UFWUPD REBOOT

ExampleAT+UFWUPD=a07a553420
1b2e42dd2d964920e57319+UFWUPD: ONGOING
CCC...
OK
UFWUPD REBOOT

19.2.4 TOBY-L2 / MPCI-L2 defined values
Parameter
<md5>

Type
NumberDescription
32 hexadecimal number

19.2.5 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 description
Depending on the <filetype> parameter and the corresponding file format, the update will affect:•••

Module firmware: the firmware can be updated only using the file in fls format
NVM and profiles: they are reset to the factory-programmed values using either the file in dffs or in fls
format
FS: it is updated only using the file in dffs format
In case of power loss during the update, at the next module wake-up a fault is detected and the module
remains in Firmware Update Mode expecting that the upgrade restarts from the Xmodem handshake;
the FW is corrupted and useless (ERROR2).
If the FW upgrade ends with an ERROR condition, the module remains in Firmware Update Mode expectingthat the upgrade restarts from the Xmodem handshake; the FW is corrupted and useless (ERROR2).
LARA-R2 / TOBY-R2 / SARA-U201-03A / SARA-U201-03B / SARA-U201-03X / SARA-U201-63B /LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S

UBX-13002752 - R67

19 System features

Page 476 of 1001

u-blox cellular modules - AT commands manual

The file in fls format contains the File System image. Any <filetype> value of the +UFWUPD command
which involves the file system update will require the fls file.
SARA-G4 / SARA-G3
The NVM and the profiles are not updated with the file in dffs format.
LEON-G1
The file in fls and dffs formats do not allow updating the NVM and the profiles.

19.2.6 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 syntax
Type
Set

SyntaxResponse
AT+UFWUPD=<filetype>[,<speed>] +UFWUPD: ONGOING

ExampleAT+UFWUPD=0(Sent at new baud rate, if specified) +UFWUPD: ONGOING

Test

AT+UFWUPD=?

CCC<NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK>

CCC<NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK>OK+UFWUPD: (list of supported<filetype>s),(list of supported<speed>s)

OK+UFWUPD: (0-2),(115200,230400,
460800,921600)
OKOK

19.2.7 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 defined values
Parameter<filetype>

Type
Number<speed>NumberDescription
Download type:• 0: firmware image update (*.fls file)• 1: File System image update (*.dffs or *.fls file)• 2: firmware and File System image update (*.fls file)
Baud rate in b/s. Allowed values:• 115'200 (default value)• 230'400• 460'800• 921'600• 3'000'000• 3'250'000• 6'000'000• 6'500'000

19.2.8 SARA-G4 description
Depending on the <filetype> parameter and the corresponding file format, the update will affect:••

Module firmware: the firmware can be updated only using the file in pack format
FS: it is updated only using the file in pack format
In case of power loss during the update, at the next module wake-up a fault is detected and the module
remains in Firmware Update Mode expecting that the upgrade restarts from the Xmodem handshake;
the FW is corrupted and useless (ERROR2).
If the FW upgrade ends with an ERROR condition, the module remains in Firmware Update Mode expectingthat the upgrade restarts from the Xmodem handshake; the FW is corrupted and useless (ERROR2).

19.2.9 SARA-G4 syntax
Type
Set

SyntaxResponse
AT+UFWUPD=<filetype>[,<speed>] +UFWUPD: ONGOING

ExampleAT+UFWUPD=0(Sent at new baud rate, if specified) +UFWUPD: ONGOING

UBX-13002752 - R67

19 System features

Page 477 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+UFWUPD=?

Response
CCC<NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK>

ExampleCCC<NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK><NACK>OK+UFWUPD: (list of supported<filetype>s),(list of supported<speed>s)

OK+UFWUPD: (0-1),(115200,230400,
460800,921600)
OKOK

19.2.10 SARA-G4 defined values
Parameter<filetype>

Type
Number<speed>NumberDescription
Download type:• 0: firmware image update (*.pack file)• 1: firmware and File System image update (*.pack file)
Baud rate in b/s. Allowed values:• 115'200 (default value)• 230'400• 460'800• 921'600

19.2.11 Notes
TOBY-L2 / MPCI-L2• This command is not available if the encryption is enabled by means of the +USECCFG AT command. For
further information, see the +UFWSINSTALL AT command.
LARA-R2 / TOBY-R2• If <filetype>=2 make sure the file contains both the firmware and file system images.
LARA-R211• The FW update process is not allowed on the AUX UART interface (not supported by
LARA-R211-02B-00, LARA-R211-02B-01 and LARA-R211-02B-02).
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• <speed>=3'000'000, 3'250'000, 6'000'000, 6'500'000 are not supported.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• The FW update process is not allowed on the AUX UART interface.
SARA-U260 / SARA-U270 / SARA-U280 / LISA-U200-00S / LISA-U200-03S / LISA-U200-83S /LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U1 / LEON-G1• <filetype>=2 is not supported.
SARA-G3• The FW update process is not allowed on the AUX UART interface (where present).
• <filetype>=2 is not supported.
SARA-G300 / SARA-G310• <filetype>=1 is not supported.
SARA-G450-01C• The FW update process is not allowed on the AUX UART interface.

UBX-13002752 - R67

19 System features

Page 478 of 1001

u-blox cellular modules - AT commands manual

19.3 Firmware installation with signature verification+UFWSINSTALL+UFWSINSTALL
Modules
TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A
TOBY-L280-03S MPCI-L201-02S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
No
No
FW installwith signature
verification Error+CME Error

19.3.1 Description
Triggers the FW installation procedure with encrypted signature verification, starting from the file (update
binary file) stored in the module file system. Provides basic facilities required to implement a FOTA procedure
with elevated security by means of encrypted signature verification.
During the FW installation procedure, the module:• Verifies the encrypted signature of the FW update file (update binary file) stored in the module file system.
The signature verification procedure is as follows:o The <usecmng_iname> indicated certificate or public key is used to decrypt the <base64_signature>signature and retrieve the SHA-256 digest (DIGEST_1).
o A SHA-256 digest (DIGEST_2) is generated from the FW update file (update binary file) stored in the filesystem.
o The two digests (DIGEST_1 and DIGEST_2) are compared and if match the signature is successfully
verified.
o If any of the described steps fails the signature verification procedure fails and the "signature
verification error, update failed" error result code will be reported.
• Checks and handles syntax, input parameters and signature verification errors in the following way:o The new FW is not installed and the old FW is not modified in any way.
o The module regains the AT command mode functionality and continues to respond to AT commands.
• Executes a SW system reset with network de-registration.
• Does not issue any result codes or provides any progress information on the terminal.
• Withholds the possibility to make any sort of calls (even emergency calls).
• Executes a SW reboot (once concluded the FW installation procedure) and boots with the new firmware
installed, NVM, profiles and the file system restored to the factory-programmed setting.
• Takes about 60 s to complete the FW installation procedure.
• Remains in FW Installation Mode until the FW installation procedure is successfully concluded. The FW
installation procedure:o is fault tolerant; restarts the FW installation procedure at next boot if a fault is detected during the FW
installation procedure.
o is power loss tolerant; restarts the FW installation procedure at next power on if a power loss occurred
during the FW installation procedure.
FW installation procedure prerequisites:• A FW update file (update binary file) stored in the module file system. Store the update file into
the module file system folder before starting the FW installation procedure with +UFWSINSTALL
otherwise the "update file not found" error result code is reported. The procedure for storing the update
file in file system is up to the user (via +UFTPC, +UHTTPC or +UDWNFILE). These commands erase
the old before storing the new update file.
• A signature verification certificate or signature verification public key imported by means of the+USECMNG AT command.
• A base64 encoded signature string generated from the FW update file being installed using theSHA-256 digest and RSA algorithm.
This command is only available if the encryption is enabled with the use of +USECCFG AT command. If theencryption is disabled the +UFWSINSTALL AT command will provide an error result code (CME ERROR: 4 /UBX-13002752 - R67

19 System features

Page 479 of 1001

u-blox cellular modules - AT commands manual

CME ERROR: not supported); only +UFWINSTALL or +UFWUPD AT commands shall be issued to performa FW installation procedure.
TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S /MPCI-L201-02S
The command is not supported by TOBY-L200-03S-00, TOBY-L201-02S-00, TOBY-L210-03S-00,
TOBY-L210-03A-00, TOBY-L280-03S-00, MPCI-L201-02S-00.

19.3.2 Syntax
Type
Set

Syntax
AT+UFWSINSTALL=<usecmng_
iname>,<base64_signature>

Response
OK
UFWSINSTALL REBOOT

ExampleAT+UFWSINSTALL="vc_iname" ,"UExFQVNFXO5PVEVfVEhBVF9U0
SElTXlTXOFfQkFTRV82NF9FTkN0
PREVEX1NJRO5BVFVSRV9FWEF0
NUExFX1dISUNIX1dJTExfTk9UX1N0UQVJUX1RIRV9GSVJNVOFSRV9V0
UERBVEVfUFJPQOVTU19CVVRfV0
OlMTF9QUk9EVUNFXOFOX1ZFUkl0
GQOFUSU9OXOVSUk9SXOVWRU05fVOhFTl9VUOVEX1dJVEhfQV9W0
QUxJRF9DRVJUSUZJQOFURV9B0
TkRfQV9WQUJRF9GSVJNVOFSR0
V9VUERBVEVfRklMRV9TVE9SR0
URfSU5fVEhFIFJJROhUXOZJTR0
fQV9W=="OK

Test

AT+UFWSINSTALL=?

OK

UFWSINSTALL REBOOTAT+UFWSINSTALL=?
OK

19.3.3 Defined values
Parameter<usecmng_iname>

Type
String<base64_signature> String

Description
USECMNG internal name - unique identifier of an imported certificate or public key
which will be used for signature verification (max. length 200 chars).
BASE64 encoded SHA-256 RSA encrypted digital signature of the FW update filestored in file system.

19.4 Antenna detection +UANTR+UANTR
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

19.4.1 Description
Measures the DC component of load of the cellular antenna (the GPS antenna is RFU). The antenna load isexpressed in kOhm.

19.4.2 Syntax
Type
Set

SyntaxAT+UANTR=[<antenna_id>]

Response+UANTR: <antenna_id>,<antenna_load>

ExampleAT+UANTR=0+UANTR: 0,10

OK

UBX-13002752 - R67

19 System features

Page 480 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Test

AT+UANTR=?

+UANTR: (list of supported<antenna_id>s)

ExampleOK+UANTR: (0)OKOK

19.4.3 Defined values
Parameter<antenna_id>

Type
Number<antenna_load>

NumberDescription
Antenna identifier (optional parameter):• 0 (default value): cellular antenna• 1: GPS antenna (RFU)
Measured value in kOhm of the antenna load with a resolution of 1 kOhm. The range
goes from -1 to 53 (only integer values can be assumed), where:• -1: open circuit• 0: short circuit• 1: 1 kOhm (minimum limit of the measurement range)• ...
• 53: 53 kOhm (maximum limit of the measurement range)

19.4.4 Notes••

The load resistor values below the minimum limit of 1 kOhm are identified as short circuit (<antenna_load>=0), while values above the maximum limit of 53 kOhm are identified as open circuit (<antenna_load>=-1).
The reported value could differ from the real resistance value of the diagnostic resistor mounted inside
the antenna assembly due to antenna cable length, antenna cable capacity and the measurement
method.

19.5 RX antenna selection +UANT+UANTModules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S
TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
MPCI-L200-02S MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

19.5.1 Description
Allows user to select the active antenna receiver path. The user can activate the primary antenna receiver only,
the secondary antenna receiver only, or both antenna receiver paths together. The command can be used forthe execution of receiver sensitivity measurements like the Total Isotropic Sensitivity (TIS) test. The commandexecution does not affect the antenna transmitting path.

19.5.2 Syntax
Type
Set

SyntaxAT+UANT=<setting>,<value>

Response
OK

Test

AT+UANT=?

+UANT: (list of supported<setting>s),(list of supported<value>s)

ExampleAT+UANT=0,1
OK+UANT: (0),(0-2)
OKOK

19.5.3 Defined values
Parameter<setting>

UBX-13002752 - R67

Type
NumberDescription
Setting type:

19 System features

Page 481 of 1001

u-blox cellular modules - AT commands manual

ParameterType<value>NumberDescription• 0: RX path selection
Selects which antenna RX path to use:
• 0: both antennas• 1: primary antenna RX path only
• 2: secondary antenna RX path only

19.5.4 Notes•

To be sure to perform a test in a reliable starting condition, it is suggested to issue AT+CFUN=15 (silent
reset) command before each test.

TOBY-L2 / MPCI-L2• The module must be connected on a 3G network or registered on an LTE network, otherwise an error
result code is returned• The PIN insertion is mandatory.
TOBY-L4 / LARA-R202 / LARA-R280 / TOBY-R2• Select the antenna when the module is deregistered from network and the 3G diversity is disabled.
• Re-enable the RX diversity after the tests.
LARA-R203 / LARA-R204 / LARA-R211 / LARA-R220• Select the antenna when the module is deregistered from network.
• Re-enable the RX diversity after the tests.

19.6 Rx diversity +URXDIV+URXDIV
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S
TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
MPCI-L200-02S MPCI-L200-03S MPCI-L201-02S MPCI-L210-02S MPCI-L210-03S MPCI-L220
MPCI-L280
LARA-R202 LARA-R280 TOBY-R2
LISA-U230
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

19.6.1 Description
Controls the Rx diversity and 2G Downlink Advanced Receiver Performance (DARP) during runtime. The
features can be enabled or disabled during operation. Specifying the 2G DARP is optional.
For more details, see 3GPP TS 25.101 [51] and 3GPP TS 45.005 [52].
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

19.6.2 Syntax
Type
Set

Syntax
AT+URXDIV=<RxDiv>[,<DARP>]

Response
OK

ExampleAT+URXDIV=1,3

Read

AT+URXDIV?

+URXDIV: <RxDiv>,<DARP>OK+URXDIV: 1,3

Test

AT+URXDIV=?

OK+URXDIV: (list of supported<RxDiv>s),(list of supported<DARP>s)OK+URXDIV: (0-1),(1-3)
OK

OK

UBX-13002752 - R67

19 System features

Page 482 of 1001

u-blox cellular modules - AT commands manual

19.6.3 Defined values
Parameter<RxDiv>Type
Number<DARP>

NumberDescription
Rx diversity configuration. Allowed values:• 0: Rx diversity disabled• 1 (factory-programmed value): Rx diversity enabled
DARP phase and mode. Allowed values:• 1: DARP phase I• 2: DARP phase II - traffic only
• 3 (default and factory-programmed value): DARP phase II - always on

19.6.4 Notes••

It is possible to set the parameters only if the module is not registered with the network.
The diversity receiver is provided to improve the quality and reliability of the wireless link on all operating
bands except 2G DCS 1800.

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• The <DARP> parameter is not supported.
• DARP phase II is not supported.

19.7 ADC read command +UADC+UADC
Modules
Attributes

LEON-G1
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

19.7.1 Description
Reads the current value of the specified ADC, given in milliVolt. The parameters range is shown in the responseto the test command if ADC are supported; if no ADC is supported by the module, an error result code isreturned.

19.7.2 Syntax
Type
Read

Test

SyntaxAT+UADC=<adc_id>

AT+UADC=?

Response+UADC: <adc_id>,<adc_val>

ExampleAT+UADC=0

OK+UADC: 0,480+UADC: (range of <adc_id>s)

OK+UADC: (0-1)

OKOK

19.7.3 Defined values
Parameter<adc_id>Type
Number<adc_val>

NumberUBX-13002752 - R67

Description
ADC identifier. Allowed values:• LEON-G1
o 0: ADC1
Current ADC value measured on the specified ADC pin; the range goes from 0 to 1920
mV.

19 System features

Page 483 of 1001

u-blox cellular modules - AT commands manual

19.8 End user test +UTEST+UTEST
Modules

Attributes

TOBY-L4 TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time
Up to 1 s

Error reference+CME Error

19.8.1 Description
Enables the module testing on the RF parts and all the digital pins.
The usage of this command shall be restricted to controlled (shielded chamber/box) environments andfor test purposes only.
u-blox assumes no responsibility for the inappropriate use of this command.

19.8.2 RF test description
Sets the module in non-signalling (or test) mode, or returns to the signalling (or normal) mode.
In test/non-signalling mode, the module switches off the protocol stack for performing single tests which could
not be performed during signalling mode.
Improper usage of this command on a real network could disturb other users and the network itself.
When entering the test mode, it is possible to sequentially trigger the following actions for testing purposes(also depending on the RATs supported by the module):• 2G transmission of a GSM burst sequence on the desired channel and power level (only one time slot
configuration is available)• 2G transmission of an 8-PSK modulation burst sequence on the desired channel and power level (only one
time slot configuration is available)• 3G transmission of a WCDMA signal on the desired channel and power level• 4G transmission of an LTE SC-FDMA OFDM signal (5 MHz bandwidth) in the desired channel in the FDD
band and power level• 4G transmission of LTE SC-FDMA OFDM signal (5 MHz bandwidth) in the desired channel in TDD band andpower level• Receiving signal detection and RF level measurement on the desired 2G, 3G or 4G (LTE) channel• Receiving signal detection at diversity or secondary antenna input and RF level measurement on the desired
2G, 3G or 4G (LTE) channel
The <mode>, <RX_channel>, <RX_time_interval>, <receiver_path>, <TX_channel>, <power_control_level>, <training_sequence>, <modulation_mode>, <TX_time_interval> parameters setting is not stored
in the NVM.
TOBY-L2 / MPCI-L2
The receiving signal detection at the secondary antenna is limited to only the 3G and 4G channels.
The command only accepts the parameter set supported by the specific module version. When an
unsupported parameter is issued, an error result code will be provided ("+CME ERROR: operation notsupported" or "+CME ERROR: 4" depending on the +CMEE AT command setting).
The execution of these actions is performed in non-signalling mode. In non-signalling mode:• The module only accepts +UTEST commands
In normal mode:• The only allowed +UTEST command is the AT+UTEST=1 used to enable the testing interface• All other +UTEST commands return an error result code ("+CME ERROR: operation not allowed" or "+CME
ERROR: 3" depending on the +CMEE AT command setting)
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1

UBX-13002752 - R67

19 System features

Page 484 of 1001

u-blox cellular modules - AT commands manual

The module must not be registered with the network (+COPS: 2) before entering the non-signalling mode,otherwise an error result code ("+CME ERROR: operation not allowed" or "+CME ERROR: 3" depending on
the +CMEE AT command setting) is provided.
TOBY-L2 / MPCI-L2
A network deregistration is not needed, as the AT+UTEST=1 command deactivates the protocol stack
before entering the non-signalling mode.
When the module exits from the test mode, the network status before entering this mode will be restored.
The +CMEE command can only be set in normal mode.
To return to the normal mode, perform one of these actions:• a module reset• power off the module• send AT+UTEST=0 (depending on the module series, a reboot could be automatically performed)
When the module returns the normal mode, the network registration status stored in the profile will be
restored.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
See the End User Test Application Note [174] for further test command examples and more information
on module reboot.

19.8.3 Syntax
Type
SyntaxGeneric syntax
Set
AT+UTEST=<mode>[,[<param_val1>][,[<param_val2>][,[<param_val3>][,[<param_val4>][,[<param_val5>]]]]]]

Response

Example[+UTEST: [<param_val1>,<param_ AT+UTEST=0val2>][,<param_val3>][,<param_OKval4>,<param_val5>][,<min>,<avg>,<max>]]OKEntering normal mode
Set
AT+UTEST=0OK

AT+UTEST=0
OK

Entering non-signalling mode
Set
AT+UTEST=1

OK

AT+UTEST=1
OK

RX test mode
Set
AT+UTEST=2[,[<RX_channel>][,[<RX_time_interval>][,[<receiver_
path>]]]]+UTEST: <RX_channel>,<RX_time_ AT+UTEST=2,124,250
interval>,<receiver_path>,<min>,+UTEST: 124,250,0,-80,-80,-80<avg>,<max>
OKOK

TX test mode
Set
AT+UTEST=3[,[<TX_channel>][,+UTEST: <TX_channel>,<power_
AT+UTEST=3,32,7,5[<power_control_level>][,[<training_ control_level>,<training_sequence>,+UTEST: 32,7,5,1,1000
sequence>][,[<modulation_mode>][, <modulation_mode>,<TX_time_[<TX_time_interval>]]]]]]
interval>
OK
OK
Antenna dynamic tuner configuration mode
Set
AT+UTEST=4,<ant_tuner_enable>+UTEST: 4,<ant_tuner_enable>

AT+UTEST=4,1

OK+UTEST: 4,1
OK

Read
Test

AT+UTEST?

+UTEST: <mode>+UTEST: 1

AT+UTEST=?

OK+UTEST: (list of supported<mode>s)OK+UTEST: (0-3)
OK

OK

UBX-13002752 - R67

19 System features

Page 485 of 1001

u-blox cellular modules - AT commands manual

19.8.4 Defined values
Parameter<mode>

Type
Number<RX_channel>
Number<RX_time_interval> Number<receiver_path>
Number<TX_channel>
Number<power_control_
Numberlevel><training_sequence> Number<modulation_mode> Number<TX_time_interval> Number<ant_tuner_enable> Number<param_valx>

NumberDescription
Test mode setting:• 0: the module returns to the normal mode
• 1: the module enters non-signalling mode
• 2: RX test mode (measuring the antenna level estimation of the received RF signal)• 3: TX test mode (GSMK/8-PSK burst or transmission in 3G bands)• 4: antenna dynamic tuner configuration mode (enable/disable antenna dynamic
tuner control)
For the parameter description and its range, see Notes.
For the parameter description and its range, see Notes.
For the parameter description and its range, see Notes.
For the parameter description and its range, see Notes.
For the parameter description and its range, see Notes.
For the parameter description and its range, see Notes.
For the parameter description and its range, see Notes.
For the parameter description and its range, see Notes.
Enable/disable antenna dynamic tuner control. Allowed values:• 0 (factory-programmed value): antenna dynamic tuner control disabled• 1: antenna dynamic tuner control enabled
Supported content depends on related <mode> (details are given above).

19.8.5 Notes
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• <mode>=4 (antenna dynamic tuner configuration mode) is not supported.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1• Check the corresponding module data sheet for the list of supported bands and Radio AccessTechnologies (RAT).
• RX mode setting (<mode>=2)
Parameter
Description<RX_channel> Channel

Range
0 ÷ max
value ofsupportedband

Default Notes
32
RX channel 2G RAT: for 850, 900, 1800 bands the value
corresponds to ARFCN while for 1900 band an offset of
32768 is added.
o [0-124]: GSM 900 MHz
o [128-251]: GSM 850 MHz
o [512-885]: DCS 1800 MHz
o [975-1023]: EGSM 900 MHz
o [33280-33578]: PCS 1900 MHz (corresponding to
ARFCN 512-810 range in band 1900)
RX channel 3G RAT: the value corresponds to UARFCN
except for band 19 where an offset of 20000 is added,
additional channels available in some 3G bands are notsupported.
o [1537-1738]: band 4 (1700 MHz)o [2937-3088]: band 8 (900 MHz)o [4357-4458]: band 5 (850 MHz)o [4387-4413]: band 6 (800 MHz)o [20712-20763]: band 19 (800 MHz)o [9662-9938]: band 2 (1900 MHz)o [10562-10838]: band 1 (2100 MHz)o [10050-10125]: TD-SCDMA band 34 (2000 MHz)o [9400-9600]: TD-SCDMA band 39 (1900 MHz)RX channel 4G RAT: the value corresponds to EARFCN
with an offset of 100000.

UBX-13002752 - R67

19 System features

Page 486 of 1001

u-blox cellular modules - AT commands manual

Parameter

Description

Range

Default Notes<RX_channel> range LTE band[100000-100599]
FDD 1[100600-101199]
FDD 2[101200-101949]
FDD 3[101950-102399]
FDD 4[102400-102649]
FDD 5[102650-102749]
FDD 6[102750-103449]
FDD 7[103450-103799]
FDD 8[103800-104149]
FDD 9[104150-104749]
FDD 10[104750-104949]
FDD 11[105010-105179]
FDD 12[105180-105279]
FDD 13[105280-105379]
FDD 14[105730-105849]
FDD 17[105850-105999]
FDD 18[106000-106149]
FDD 19[106150-106449]
FDD 20[106450-106599]
FDD 21[106600-107399]
FDD 22[107500-107699]
FDD 23[107700-108039]
FDD 24[108040-108689]
FDD 25[108690-109039]
FDD 26[109210-109659]
FDD 28[109660-109769]
FDD 29[109770-109869]
FDD 30[109870-109919]
FDD 31[109920-110359]
FDD 32[136000-136199]
FDD 33[136200-136349]
TDD 34[136350-136949]
TDD 35[136950-137549]
TDD 36[137550-137749]
TDD 37[137750-138249]
TDD 38[138250-138649]
TDD 39[138650-139649]
TDD 40[139650-141589]
TDD 41[141590-143589]
TDD 42[143590-145589]
TDD 43[145590-146589]
TDD 44[165536-166435]
FDD 65[166436-167335]
FDD 66[167336-167535]
FDD 67[167536-167835]
FDD 68[167836-168335]
FDD 69[168336-168585]
FDD 70[168586-168935]
FDD 71[170366-170545]
FDD 85

EARFCN range[0-599][600-1199][1200-1949][1950-2399][2400-2649][2650-2749][2750-3449][3450-3799][3800-4149][4150-4749][4750-4949][5010-5179][5180-5279][5280-5379][5730-5849][5850-5999][6000-6149][6150-6449][6450-6599][6600-7399][7500-7699][7700-8039][8040-8689][8690-9039][9210-9659][9660-9769][9770-9869][9870-9919][9920-10359][36000-36199][36200-36349][36350-36949][36950-37549][37550-37749][37750-38249][38250-38649][38650-39649][39650-41589][41590-43589][43590-45589][45590-46589][65536-66435][66436-67335][67336-67535][67536-67835][67836-68335][68336-68585][68586-68935][70366-70545]

Table 33: <RX_channel> parameter range
The "+CME ERROR: operation not supported" or"+CME ERROR: 4" error result code will be provided in

UBX-13002752 - R67

19 System features

Page 487 of 1001

u-blox cellular modules - AT commands manual

ParameterTime<receiver_path>

Antenna diversity 0 ÷ 1<min>Minimum
antenna RF level
estimation
Averageantenna RF level
estimation
Maximum
antenna RF level
estimation

<max>

•

Range

<RX_time_interval>

<avg>

•

Description

Default Notes
these cases (depending on the +CMEE AT commandsetting):o A value not belonging to the above ranges is
set
o The RX channel parameter value belongs to anon-supported RAT (2G or 3G or 4G RAT) orband

1 ÷ 600000 1000

The default channel will be equal to 32 if the GSM
RAT is supported, in the other cases it will be thesame as the central channel of the lower LTE bandsupported by the module.
Time interval for RX test expressed in ms

See Notes

TOBY-L2 / MPCI-L2
The range goes from 50 ms to 600000 ms.
Receiver path:o 0: main / primary antennao 1: diversity / secondary antenna
The parameter is available only if supported, otherwise
an error result code will be provided ("+CME ERROR:
operation not supported" or "+CME ERROR: 4" dependingon the +CMEE AT command setting)Expressed in dBm

See Notes

Expressed in dBm

See Notes

Expressed in dBm0

RF level estimation range:o SARA-G3 / LEON-G1 - The range is [-100 ÷ -20] in 2G RAT.
o TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - The range is [-100 ÷ -20] in 2G and[-90 ÷ -20] in 3G / 4G RAT.
o TOBY-L2 / MPCI-L2 - The range is [-100 ÷ -30] in 2G RAT and [-90 ÷ -30] in 3G / 4G RAT.
TX mode setting (<mode>=3)
Parameter
Description<TX_channel> Tx channel

Range
0 ÷ max
value ofsupportedband

Default Notes
32
TX channel 2G RAT: for 850, 900, 1800 bands the value
corresponds to ARFCN while for 1900 band an offset of
32768 is added.
o [0-124]: GSM 900 MHz
o [128-251]: GSM 850 MHz
o [512-885]: DCS 1800 MHz
o [975-1023]: EGSM 900 MHz
o [33280-33578]: PCS 1900 MHz (corresponding to
ARFCN 512-810 range in band 1900)
TX channel 3G RAT: the value corresponds to UARFCN
except for the band 19 where an offset of 20000 is added,
additional channels available in some 3G bands are notsupported.
o [1312-1513]: band 4 (1700 MHz)o [2712-2863]: band 8 (900 MHz)o [4132-4233]: band 5 (850 MHz)o [4162-4188]: band 6 (800 MHz)o [20312-20363]: band 19 (800 MHz)o [9262-9538]: band 2 (1900 MHz)o [9612-9888]: band 1 (2100 MHz)o [10050-10125]: TD-SCDMA band 34 (2000 MHz)o [9400-9600]: TD-SCDMA band 39 (1900 MHz)UBX-13002752 - R67

19 System features

Page 488 of 1001

u-blox cellular modules - AT commands manual

Parameter

Description

Range

Default Notes
TX channel 4G RAT: the value corresponds to EARFCN
with an offset of 100000.
<TX_channel> range LTE band
[118000-118599]
FDD 1[118600-119199]
FDD 2[119200-119949]
FDD 3[119950-120399]
FDD 4[120400-120649]
FDD 5[120650-120749]
FDD 6[120750-121449]
FDD 7[121450-121799]
FDD 8[121800-122149]
FDD 9[121800-122149]
FDD 10[122750-122949]
FDD 11[123010-123179]
FDD 12[123180-123279]
FDD 13[123730-123849]
FDD 17[123850-123999]
FDD 18[124000-124149]
FDD 19[124150-124449]
FDD 20[124450-124599]
FDD 21[124600-125399]
FDD 22[125500-125699]
FDD 23[125700-126039]
FDD 24[126040-126689]
FDD 25[126690-127039]
FDD 26[127040-127209]
FDD 27[127210-127659]
FDD 28[127660-127759]
FDD 30[127760-127809]
FDD 31[136200-136349]
TDD 34[137750-138249]
TDD 38[138250-138649]
TDD 39[138650-139649]
TDD 40[139650-141589]
TDD 41[231072-231971]
FDD 65[231972-232671]
FDD 66[232672-232971]
FDD 68[232972-233121]
FDD 70[233122-233471]
FDD 71[234002-234181]
FDD 85

EARFCN range[18000-18599][18600-19199][19200-19949][19950-20399][20400-20649][20650-20749][20750-21449][21450-21799][21800-22149][21800-22149][22750-22949][23010-23179][23180-23279][23730-23849][23850-23999][24000-24149][24150-24449][24450-24599][24600-25399][25500-25699][25700-26039][26040-26689][26690-27039][27040-27209][27210-27659][27660-27759][27760-27809][36200-36349][37750-38249][38250-38649][38650-39649][39650-41589][131072-131971][131972-132671][132672-132971][132972-133121][133122-133471][134002-134181]

Table 34: <TX_channel> parameter range
The "+CME ERROR: operation not supported" or"+CME ERROR: 4" error result code will be provided inthese cases (depending on the +CMEE AT commandsetting):o A value not belonging to the above ranges is
set
o The TX channel parameter value belongs to anon-supported RAT (2G or 3G or 4G RAT) orband
Avoid channels that would put the TX waveform
outside the band due to SC-FDMA modulation
bandwidth.

UBX-13002752 - R67

19 System features

Page 489 of 1001

u-blox cellular modules - AT commands manual

Parameter

Description

Range<power_control_level>

Power controllevel-56 ÷ 24

Default Notes
The default channel will be equal to 32 if the GSM
RAT is supported, in the other cases it will be thesame as the central channel of the lower LTE bandsupported by the module.
5
For 2G RAT: PCL (power control level). The allowed
values depend on the related <TX_channel> value: lower
numbers means higher power level.
o [0-19]: GSM 850 and 900, if <power_control_level>is less than 5 the handling is the same for <power_
control_level>=5o [0-15]: DCS 1800 and PCS 1900
In case <modulation_mode> is set to 2 (8-PSK
modulation) the range is as below. Other values are valid
but behave as the indicated level:o [0-19]: GSM 850 and 900 if <power_control_level>is less than 8 the handling is the same for <power_
control_level>=8o [0-15]: DCS 1800 and PCS 1900; if <power_control_level> is less than 2 the handling is the same for<power_control_level>=2
For 3G RAT: absolute output power [dBm]o [-56 ÷ 24] for all the bands
For 4G RAT: absolute output power [dBm]o [-40 ÷ 24] for all the bands
Only the values indicated in the above ranges arevalid, otherwise an error result code will be provided("+CME ERROR: operation not supported" or "+CME
ERROR: 4" depending on the +CMEE AT commandsetting).

<training_sequence>

Training
sequence

0÷7

5

TOBY-L2 / MPCI-L2
The minimum value of the output power level<power_control_level> is -50 dBm in 3G mode.
Training sequence to be used (to be changed only in caseof link with network simulator, else use default)
In 3G / 4G RAT the values is unused.

<modulation_
mode>

Modulation mode 1 ÷ 2

1Modulation mode:o 1: GMSK normal modulation including the training
sequenceo 2: 8-PSK normal modulation including the training
sequence
In 3G / 4G RAT the parameter is ignored.
LTE SC-FDMA OFDM modulation (5 MHz
bandwidth), FDD, is automatically set using for <TX_
channel> an EARFCN value.

<TX_time_interval>Time

0 ÷ 600000 1000

The LTE Cat.M1 SC-FDMA OFDM modulation (1.4
MHz bandwidth), FDD, is automatically set using an
EARFCN value for the <TX_channel> parameter.
Time interval for TX test expressed in ms
o 0: burst sequence is continuously transmitted. In
this case the command will immediately returnthe information text response. The command line
will be immediately available for any +UTEST
command. Provide AT+UTEST=1 command tostop the burst sequence transmission, any other+UTEST commands can be set and the current
sequence transmission is stopped.
TOBY-L2 / MPCI-L2
The range goes from 50 ms to 600000 ms.

UBX-13002752 - R67

19 System features

Page 490 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2 / MPCI-L2• During the continuous TX mode tests, it is not possible to change the technology: in this case the testing
must be stopped by the command AT+UTEST=1 or by forcing the module to transmit for a limited timeinterval, and the RAT correctly configured. After that, the continuous TX mode tests can be restarted.

19.8.6 RF test description examples
In RX mode test command examples the information text response is issued after the timeout configuredin the set command.
Command
AT+UTEST=2

Response+UTEST: 32,1000,-89,-88,-87
OK

AT+UTEST=2,885,5000+UTEST: 885,5000,-66,-65,-65
OK

AT+UTEST=2,10562,2000+UTEST: 10562,2000,-60,-60,-59
OK

AT+UTEST=2,10562+UTEST: 10562,1000,0,-85,-85,-85
OK

AT+UTEST=2,65,3000,0+UTEST: 65,3000,0,-63,-62,-62
OK

AT+UTEST=2,4357,,1+UTEST: 4357,1000,1,-51,-51,-51
OK

AT+UTEST=2,102174,500,0+UTEST: 102174,500,0,-71,-70,-70
OK

AT+UTEST=2,105230,,1+UTEST: 105230,1000,1,-72,-71,-70
OK

AT+UTEST=2,109690,,0+UTEST: 109690,1000,0,-52,-51,-50
OK

AT+UTEST=2,109690,,1+UTEST: 109690,1000,1,-52,-51,-50
OK

Description
The module measures the antenna RX levelat RX channel 32 band GSM 900 for 1 s
interval.
In the example -89,-88,-87 are theantenna RF level estimation: thenumbers are just an example.
The module measures the antenna RX levelat RX channel 885 band DCS 1800 for 5 s
interval.
The module measures the antenna RX
level at RX channel 10562 band B1 for 2 s
interval on the main antenna path.
The module measures the antenna RX levelat RX channel 10562 band B1 for 1 s intervalon the main antenna path.
The module measures the antenna RX levelat RX channel 65 band GSM 900 for 3 s
interval on the main antenna path.
The module measures the antenna RX levelat RX channel 4357 band B5 for 1 s intervalon the diversity antenna path.
The module measures the antenna RX levelat RX channel 2174 band FDD 4 for 0.5 s
interval on the primary antenna path.
The module measures the antenna RX levelat RX channel 5230 band FDD 13 for 1 s
interval on the secondary antenna path.
The module measures the antenna RX levelat RX channel 9690 band FDD 29 for 1 s
interval on the primary antenna path.
The module measures the antenna RX levelat RX channel 9690 band FDD 29 for 1 s
interval on the secondary antenna path.

Table 35: RX mode test command examples
Command
AT+UTEST=3,32,7,5

Response+UTEST: 32,7,5,1,1000
OK

AT+UTEST=3,65,8,,2,5000+UTEST: 65,8,5,2,5000
OK

AT+UTEST=3,660,,,,0+UTEST: 660,5,5,1,0
OK

UBX-13002752 - R67

19 System features

Description
The module will transmit for 1 s interval 1
slot burst sequence at TX channel 32 GSM
900 at PCL 5 using training sequence 5
and normal GMSK modulation.
The module will transmit for 5 s interval 1
slot burst sequence at TX channel 65 GSM
900 at PCL 8 (gamma 6, 27 dBm) using
training sequence 5 and normal 8-PSK
modulation.
The module will transmit continuously 1
slot burst sequence at TX channel 660
DCS 1800 at PCL 5 using training sequence
5 and normal GMSK modulation.

Page 491 of 1001

u-blox cellular modules - AT commands manual

Command
AT+UTEST=3,9612,22,,,2000

Response+UTEST: 9612,22,5,1,2000
OK

AT+UTEST=3,120399,15,,,3000+UTEST: 120399,15,5,1,3000
OK

AT+UTEST=3,123230,-10,,,0+UTEST: 123230,-10,5,1,0
OK

Description
The module will transmit for 2 s interval at
TX channel 9612 band B1 at 22 dBm power
level using WCDMA modulation.
The module transmits for 3 s interval
at TX channel 20399 band FDD 4 at 15
dBm power level using SC-FDMA OFDM
modulation 5 MHz bandwidth.
The module continuously transmits at
TX channel 23230 band FDD 13 at -10
dBm power level using SC-FDMA OFDM
modulation 5 MHz bandwidth.

Table 36: TX mode test command examples

19.8.7 Digital pins testing description
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S / SARA-U260-00S / SARA-U270-00S /SARA-U270-00X / SARA-U280-00S / LISA-U200-00S / LISA-U200-01S / LISA-U200-02S /LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270 / SARA-G300 / SARA-G310 /SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S / LEON-G1
The feature is not supported.
Defines the commands to perform some verifications on all the digital pins of the u-blox cellular modules.
These pins can be considered as generic digital input / output pins; it is possible to configure one pin as a digital
output with "high" logic level and then verify the voltage level present. Conversely, it is possible set a pin asa digital input, externally apply a "high" or "low" logic level and then check if the module is able to correctly
measure the voltage level applied.
After the execution of the AT+UTEST=10,5 command, it is possible to externally apply a voltage level to theenabled input pins and / or measure the voltage level on the pins configured as digital input.
These commands are intended for production to check the correct digital pins behavior, detect possible
soldering or functional problems and can be executed only in non-signalling mode (otherwise the "+CME
ERROR: operation not allowed" or "+CME ERROR: 3" error result code - depending on the +CMEE AT
command setting - is issued without performing any operations).
Do not exceed the values reported in the Generic Digital Interface section of the module data sheet
when testing a pin as a digital input pin, since stressing the device above the listed ratings may cause apermanent damage of the module.
The <op_code>, <bit_padding>, <pin_seq> parameters setting is not stored in the NVM.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
See the End user test application note [174] and the corresponding module data sheet for the list of pins
available for testing and their levels characteristics and further test command examples.

19.8.8 Syntax
Type
SyntaxDigital pins testing generic syntax
Set
AT+UTEST=10,<op_code>[,[<bit_
padding>]<pin_seq>]

Response

ExampleOK

AT+UTEST=10,3,"0000001000000
300"
OK

Original configuration restoring
Set
AT+UTEST=10,0

OK

AT+UTEST=10,0OK

Pins set definition
Set
AT+UTEST=10,2,[<bit_
padding>]<pin_seq>

OK

AT+UTEST=10,2,"0000000C30000
0003000"
OK

UBX-13002752 - R67

19 System features

Page 492 of 1001

u-blox cellular modules - AT commands manualType
SyntaxPins configuration
Set
AT+UTEST=10,3,[<bit_
padding>]<pin_seq>

Response

ExampleOK

AT+UTEST=10,3,"0000000420000
0001000"
OK

Output pins definition
Set
AT+UTEST=10,4,[<bit_
padding>]<pin_seq>

OK

AT+UTEST=10,4,"00000000100000
002000"OK

Digital testing execution
Set
AT+UTEST=10,5

OK

AT+UTEST=10,5
OK

Digital value measurement
Set
AT+UTEST=10,6<bit_padding>]<pin_seq>

AT+UTEST=10,6

OK00000004100000003000
OK

Read

AT+UTEST?

+UTEST: <mode>+UTEST: 1

Test

AT+UTEST=?

OK+UTEST: (list of supported<mode>s)OK+UTEST: (0-3)
OKOK

19.8.9 Defined values
Parameter<op_code>Type
Number[<bit_
Numberpadding>]<pin_seq>

UBX-13002752 - R67

Description
Test mode setting:• 0: exits the test interface and restores the pins to the original configuration• 2: defines a set of pins that will be tested and initializes these pins to be readyfor testing. The original pins configuration is kept for final restore. In the [<bit_
padding>]<pin_seq> parameter use this notation to represent each module pin
with its binary digit:
o 0: the pin will not be testedo 1: the pin will be tested (as digital input or output)• 3: configures the logical pins previously enabled for testing as output or input; thecommand has effect only if AT+UTEST=10,2 has been previously issued.
In case a non enabled pin is set as digital input or output, the command does not
return an error and the setting is not applied. In the [<bit_padding>]<pin_seq>
parameter use this notation to represent each module pin with its binary digit:
o 0: the pin will be set as an output
o 1: the pin will be set as an input• 4: configures the value of the output pins under testing; the command has effectonly if AT+UTEST=10,3 has been previously issued; The command is not mandatory
if there are no output pins to configure. In the [<bit_padding>]<pin_seq> parameter
use this notation to represent each module pin with its binary digit:
o 0: the pin will output a "low" logic levelo 1: the pin will output a "high" logic level• 5: applies the setting change defined with <op_code>= 2 / 3 / 4 and triggers theexecution of the digital testing. Digital testing of the pins is possible only after the
execution of the AT+UTEST=10,5 command.
• 6: returns the logic value of pins under testing (both input and output); in the [<bit_
padding>]<pin_seq> parameter use this notation to represent each module pin
with its binary digit:
o 0: "low" logic digital level measured at the module pino 1: "high" logic digital level measured at the module pin
Sequence of hexadecimal digits containing the pin information and the action to
execute:19 System features

Page 493 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /SARA-G3 - See the Notes and the End user test application note [174] for detailed
number description

19.8.10 Notes•

Consider these steps to construct the [<bit_padding>]<pin_seq> sequence:o Consider the total number of the module's pins available- TOBY-L4 / TOBY-L2 / MPCI-L2 / TOBY-R2 - 92 pins
- LARA-R2 - 68 pins
- SARA-U2 / SARA-G3 - 64 pins
- LISA-U2 - 76 pinso When a non-testable pin is selected, the command does not return an error result code but the value is
not considered and not applied.
o The status of the n-th pin will be represented by the corresponding n-th bit; see the <op_code>
description for the notation of each mode settingo Convert each group of four binary digits into its hexadecimal representationo TOBY-L2 / LISA-U2 - Add one 0 digit at the beginning of the sequence to complete the resulting sequenceof hexadecimal values with 0 padding
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
See the End user test application note [174] and the corresponding module data sheet for the list ofpins available for testing and their levels characteristics and further test command examples.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• An example of the AT commands sequence to test the digital pins is reported below.
Command

Response

Description
Configure the formatting of the error result code bymeans of +CMEE AT command
Deregister the module from the network
The module enters the test mode
The command puts the module in Interface initialised
state; the command saves the pins status to restore itat the end of the test.

AT+COPS=2
OK
AT+UTEST=1
OK
AT+UTEST=10,2,"000007F400 OK
C000D83F00"

AT+UTEST=10,3,"0000049400 OK
4000C01800"

AT+UTEST=10,4,"0000036000 OK
8000182700"

AT+UTEST=10,5

OK

AT+UTEST=10,6000007F400C000D83F00
OK

UBX-13002752 - R67

Pins enabled for testing: DSR, RI, DCD, DTR, RTS, CTS,
GPIO1, GPIO2, GPIO3, GPIO4, I2S1_RXD/GPIO6, I2S1_TXD/
GPIO7, GPIO5, I2S1_CLK/GPIO8, I2S1_WA/GPIO9, SPI_SCLK/GPIO10, SPI_MOSI/GPIO11, SPI_MISO/GPIO12, SPI_SRDY/GPIO13, SPI_MRDY/GPIO14
Pins configuration:o DTR, RTS, GPIO3, GPIO4, I2S1_RXD/GPIO6, GPIO5,
I2S1_CLK/GPIO8, SPI_MOSI/GPIO11, SPI_MRDY/
GPIO14 as input
o DSR, RI, DCD, CTS, GPIO1, GPIO2, I2S1_TXD/
GPIO7, I2S1_WA/GPIO9, SPI_SCLK/GPIO10, SPI_MISO/GPIO12, SPI_SRDY/GPIO13 as output
Digital logic value of the output pins:o DSR, RI, DCD, CTS, GPIO1, GPIO2, I2S1_TXD/
GPIO7, I2S1_WA/GPIO9, SPI_SCLK/GPIO10, SPI_MISO/GPIO12, SPI_SRDY/GPIO13 set to "high".
Configurations made by AT+UTEST=10,2; AT+UTEST=
10,3 and AT+UTEST=10,4 are executed.
Logic digital value measured at modules pins:o DSR, RI, DCD, DTR, RTS, CTS, GPIO1, GPIO2, GPIO3,
GPIO4, I2S1_RXD/GPIO6, I2S1_TXD/GPIO7, GPIO5,
I2S1_CLK/GPIO8, I2S1_WA/GPIO9, SPI_SCLK/GPIO10, SPI_MOSI/GPIO11, SPI_MISO/GPIO12, SPI_SRDY/
GPIO13, PI_MRDY/GPIO14: "high" level detected

19 System features

Page 494 of 1001

u-blox cellular modules - AT commands manual

Command
AT+UTEST=0

Response
OK

Description
Module exits from the test mode and normal pin
configuration is restored.

Table 37: Digital pins test command examples
The digital pins can be configured as many times as needed by the testing process; AT+UTEST=10,2
command is not needed any more as the DUT is already in Interface initialized state.

19.9 Smart temperature supervisor +USTS+USTS
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A TOBY-L200-02S
TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L201-02S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
ProfileNo+CME Error

19.9.1 Description
Enables/disables the Smart Temperature Supervisor feature.
When the feature is enabled the internal temperature is measured via the internal temperature sensor:• If the measured value goes over the t+1 threshold or below the t-1 threshold a URC will be issued to notify awarning: the module is still in a valid and good working condition.
• If the measured value goes over the t+2 threshold or below the t-2 threshold a URC will be issued to notify
the dangerous working condition. After the notification the device will start the shutting down procedure
to avoid damaging itself.
The +UUSTS URC will be also issued after having enabled the feature indication (by means of <mode>= 1 or<mode>= 2) and at the module power-on (if the feature indication is enabled).
The shut-down procedure is performed only if <mode>=1 (notified by a URC) or <mode>=3 (without
notification).
For security reasons the shutdown is suspended in case of emergency call in progress. In this case thedevice will switch off at the call termination: a URC will be sent to notify this.
SARA-U2 / LISA-U200-03S / LISA-U200-04B / LISA-U200-83S / LISA-U201
The shut-down procedure will start 3 s after the "dangerous working condition" URC has been issued. If
emergency calls have not yet been disconnected by the user by means of the ATH command, after this 3s timer they will be released by the module itself before starting the shutdown procedure.
If the feature is disabled (<mode>= 0 and <mode>= 2) there is no embedded protection against not allowed
temperature working conditions.
For more details on Smart Temperature Supervisor feature and the thresholds definition, see thecorresponding module system integration manual.

19.9.2 Syntax
Type
Set

SyntaxAT+USTS=<mode>

Response
OK

ExampleAT+USTS=0

Read

AT+USTS?

+USTS: <mode>

OK+USTS: 0

Test

AT+USTS=?

OK
OK+USTS: (list of supported <mode>s) +USTS: (0-2)

URC

UBX-13002752 - R67

OK+UUSTS: <mode>,<event>

19 System features

OK+UUSTS: 1,1

Page 495 of 1001

u-blox cellular modules - AT commands manual

19.9.3 Defined values
Parameter<mode>

Type
Number<event>NumberDescription
Enables / disables the smart temperature mode:• 0 (default value and factory-programmed value): smart temperature featuredisabled• 1: smart temperature feature enabled; the indication by means of the +UUSTS URC
and shutting down (if needed) are performed• 2: smart temperature indication enabled; the +UUSTS URC will be issued to notify
the Smart Temperature Supervisor status• 3: smart temperature feature enabled with no indication; the shutdown (if needed)
is performed, but without a URC notification
Allowed values:• TOBY-L4 - 1, 3 (default value and factory-programmed value)• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1 - 0 (default value and factory-programmed value),1, 2Provides the event status:• -2: temperature below t-2 threshold• -1: temperature below t-1 threshold• 0: temperature inside the allowed range - not close to the limits• 1: temperature above t+1 threshold• 2: temperature above the t+2 threshold• 10: timer expired and no emergency call is in progress, shutdown phase started• 20: emergency call ended, shutdown phase started• 100: error during measurement

19.9.4 Notes
TOBY-L4• No time delay between t+2 warning and shutdown phase.
• Reboot the module to apply the new <mode> parameter configuration.
• <event>=100 is not supported.
LEON-G1• <event>=100 is not supported.

19.10 MSPR profile handling configuration +UDCONF=40+UDCONF=40
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L280
LARA-R211 TOBY-R200
SARA-U201 SARA-U260 SARA-U270 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B
LISA-U200-52S LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

19.10.1 Description
The multi-slot transmission power can be reduced according to the 3GPP specifications and set to a defined
threshold.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

UBX-13002752 - R67

19 System features

Page 496 of 1001

u-blox cellular modules - AT commands manual

In 3G mode (i.e. UMTS radio access), the maximum output power cannot be set through the AT command, but
is automatically set by the module according to the UE Maximum Power Reduction for the nominal maximum
output power with HS-DPCCH and E-DCH defined by 3GPP specifications.
In 2G mode (i.e. GPRS and EDGE radio access), the maximum output power in GMSK or 8-PSK multi-slot
configuration can be set by selecting the active multi-slot power reduction profile within the available profiles
defined in Table 38 according to 3GPP specifications.
The maximum output power in GMSK or 8-PSK multislot configuration depends on the active MSPR profile set
by the AT command and the number of active Tx slots set by the network, as described in Table 38:
Active Tx slots
1
2
3
4

MSPR profile 0
0
3
4,8
6

MSPR profile 1
0
1
2,8
4

MSPR profile 2
0
0
0,8
2

MSPR profile 30000Table 38: Power reduction (dBm)
TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
The changes in the user defined power reduction are effective after reboot.

19.10.2 Syntax
Type
Set

SyntaxResponse
AT+UDCONF=40,<GMSK_profile>[, OK<8PSK_profile>]

Read

AT+UDCONF=40+UDCONF: 40,<GMSK_profile>,<8PSK_profile>
OK

ExampleAT+UDCONF=40,2,3
OK
AT+UDCONF=40+UDCONF: 40,2,2
OK

19.10.3 Defined values
Parameter<GMSK_profile>Type
Number<8PSK_profile>NumberDescription
User defined power reduction: MSPR GMSK profile (range 0-3). The factoryprogrammed value is 2.
User defined power reduction: MSPR 8-PSK profile (range 0-3). This parameter is
optional: if omitted, the MSPR 8-PSK profile is not affected. The factory-programmed
value is 2.
The parameter is significant only for cellular modules supporting 8-PSK in uplink.

19.10.4 Notes•

For AT&T certification: the 8-PSK MSPR profile should be limited to values 2 and 3.

TOBY-L2 / MPCI-L2• The command setting is volatile and not stored in NVM.
• The module reverts back to the default MSPR profile after a network detach operation (e.g. using AT+COPS=2).

UBX-13002752 - R67

19 System features

Page 497 of 1001

u-blox cellular modules - AT commands manual

19.11 Data channel configuration +UDATACHANNEL+UDATACHANNEL
Modules
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SyntaxPIN required
Attributes
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

19.11.1 Description
Configures the serial interface over which CS or PS data shall be routed during a data connection (initiated by
the ATD or AT+CGDATA commands), after the CONNECT intermediate result code has been received.
As a factory-programmed setting, the data is routed on the same channel where the connection is established.
The channels are identified by a string made up of a trailing forward slash followed by the device type nameand a numerical index, separated by a forward slash. For example:• "/USBCDC/0" is the 1st USB AT command interface• "/tyCo/0" is the UART AT command interface• "/tyCo/2" is the SPI AT command interface• "/mux/1" is the 2nd multiplexer AT command interface (channel)
The MUX channels are available only if the mux is activated.
Channel identifier"/tyCo/0""/tyCo/2""/USBCDC/0""/USBCDC/1""/mux/1""/mux/2"

Description
UART
SPI
USB channel #0
USB channel #1
MUX channel #1
MUX channel #2

Table 39: Examples of channel's identification string
Only AT command interfaces are valid channels. An error result code will be provided if the referenced
channels are not AT command interfaces (e.g. SAP channel) or they are not active / available.
See the corresponding module system integration manual for details about the available AT commandinterfaces in each product. See also +CMUX command description for the list of the available AT command
MUX channels in each product.

19.11.2 Syntax
Type
Set

Test

SyntaxAT+UDATACHANNEL=<mode>,<csd_psd_flag>,<ctrl-tid-path>[,<tid-path>[,<connect_flag>]]
AT+UDATACHANNEL=?

Response[+UDATACHANNEL: <mode>]
OK

ExampleAT+UDATACHANNEL=1,1,"/mux/1","/
mux/2",0OK+UDATACHANNEL: (list of+UDATACHANNEL: (0-2),(0-1),(0-1)
supported <mode>s),(list ofOKsupported <csd_psd_flag>'s),(list of
supported <connect_flag>'s)
OK

19.11.3 Defined values
Parameter<mode>

Type
NumberDescription•••

0 (factory-programmed value): disable the routing
1: enable the routing
2: query current setting for the type of data specified by <csd_psd_flag> and thechannel referenced by <ctrl-tid-path>; the <tid-path> must not be set.

<csd_psd_flag>

Number••0: configure the channel for a CSD connection
1: configure the channel for a PSD connection

UBX-13002752 - R67

19 System features

Page 498 of 1001

u-blox cellular modules - AT commands manual

Parameter<ctrl-tid-path><tid-path><connect_flag>

Type
StringStringNumberDescription
Interface for which the data routing mechanism shall be enabledInterface to which a data call shall be routed••

0: reporting on the data channel disabled (neither CONNECT nor NO CARRIER
result codes are reported)
1 (default value): reporting on the data channel enabled (CONNECT and NOCARRIER result codes are reported)

19.11.4 Notes•••

The information text response for the set command is only provided if a query status is issued (<mode>=2)<ctrl-tid-path> or <tid-path> parameters cannot refer to UART and MUX channels at the same time,since MUX channels are established over UART.
In case <ctrl-tid-path> or <tid-path> parameters refer to a MUX channel, the corresponding MUXchannel shall be available when the command is issued (that is MUX protocol active and MUX channel
established). Otherwise an error result code is reported. Furthermore, when the data connection is
initiated, the MUX channel referred by <tid-path> shall be already established.

19.12 RING line handling +URING+URING
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

19.12.1 Description
Configures the RING line handling of the UART interface for other events besides the usual ones, that is theincoming call indication (RING) (linked to the "RING" URC) and the incoming SMS indication (linked to the +CMT
and the +CMTI URCs).
The RING line will be asserted when one of the configured events occurs and it remains asserted for 1 s unless
another configured event happens (in this case the 1 s timer will be started again). Same behavior will be applied
if the events are the incoming call or the incoming SMS.

19.12.2 Syntax
Type
Set

Syntax
AT+URING=<mode>

Response
OK

ExampleAT+URING=1

Read

AT+URING?

+URING: <mode>

OK+URING: 1

Test

AT+URING=?

OK+URING: (list of the supported<mode>s)OK+URING: (0-3)
OKOK

19.12.3 Defined values
Parameter<mode>

UBX-13002752 - R67

Type
NumberDescription
Configures the RING line handling:• 0 (factory-programmed value): feature disabled (RING line is asserted only on
incoming call and incoming SMS)

19 System features

Page 499 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 1: RING line asserted for all the URCs
• 2: RING line asserted for all the incoming data (PPP, sockets in Direct Link mode,
FTP in Direct Link mode)• 3: RING line asserted for all URCs and all incoming data (PPP, sockets in Direct Link
mode, FTP in Direct Link mode)

19.12.4 Notes
TOBY-L4• <mode>=1 asserts the RING line for each response, not only for URCs.
• <mode>=2, 3 are not supported.

19.13 CTS line state in case of disabled HW flow control +UCTS+UCTS
Modules

Attributes

LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G4 SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

19.13.1 Description
Configures the CTS line's state (module's output) of the UART interface in case the HW flow control is notenabled. Instead, if the HW flow control is enabled, the CTS line's state is the result of power saving and flow
control conditions.

19.13.2 Syntax
Type
Set

SyntaxAT+UCTS=<mode>

Response
OK

ExampleAT+UCTS=1

Read

AT+UCTS?

+UCTS: <mode>

OK+UCTS: 1

Test

AT+UCTS=?

OK+UCTS: (list of the supported<mode>s)OK+UCTS: (0-1)
OKOK

19.13.3 Defined values
Parameter<mode>

Type
NumberDescription
Configures the CTS line state of the UART interface:••

0 (factory-programmed value): set the CTS line to the ON state (output low) in caseof SW or no flow control.
1: set the CTS line to the OFF state (output high) in case of SW or no flow control.

19.13.4 Notes•

Regardless the AT interface where the command is issued (UART, SPI, USB), it always has effect on the
UART CTS line behavior.

UBX-13002752 - R67

19 System features

Page 500 of 1001

u-blox cellular modules - AT commands manual

19.14 PPP/LCP silent mode configuration +UDCONF=0+UDCONF=0
Modules
Attributes

SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

19.14.1 Description
Configures the advanced settings for the PPP/LCP silent mode. It means that it is possible to configure whether
the module must wait for the first LCP frame or send the first LCP frame while establishing a PPP connection.

19.14.2 Syntax
Type
Set

SyntaxAT+UDCONF=0,<ppp_lcp_silent_mode>

Response
OK

Read

AT+UDCONF=0+UDCONF: 0,<ppp_lcp_silent_
mode>
OK

ExampleAT+UDCONF=0,0OK
AT+UDCONF=0+UDCONF: 0,0OK

19.14.3 Defined values
Parameter<ppp_lcp_silent_
mode>

Type
NumberDescription
Enables/disables the PPP-LCP silent mode. Allowed values:• 0: silent mode disabled, the module sends the first LCP frame• 1 (factory-programmed value): silent mode enabled, the module waits for the otherend to start first

19.15 F-DPCH/enhanced F-DPCH configuration +UDCONF=60+UDCONF=60
Modules

Attributes

TOBY-L2 MPCI-L2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

19.15.1 Description
Configures the F-DPCH/enhanced F-DPCH support.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

19.15.2 Syntax
Type
Set

SyntaxAT+UDCONF=60,<F-DPCH_
EnhancedF-DPCH_enable>

Response
OK

Read

AT+UDCONF=60+UDCONF: 60,<F-DPCH_
EnhancedF-DPCH_enable>
OK

UBX-13002752 - R67

19 System features

ExampleAT+UDCONF=60,0
OK
AT+UDCONF=60+UDCONF: 60,1
OK

Page 501 of 1001

u-blox cellular modules - AT commands manual

19.15.3 Defined values
Parameter<F-DPCH_
EnhancedF-DPCH_
enable>Type
NumberDescription
CPC's UL discontinuous DPCCH transmission support enabled / disabled:•••

0: both F-DPCH and Enhanced F-DPCH are disabled
1: only F-DPCH enabled
2 (factory-programmed value): both F-DPCH and Enhanced F-DPCH enabled

19.15.4 Notes
LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S• The factory-programmed value of <F-DPCH_EnhancedF-DPCH_enable> is 0.

19.16 USB profiles configuration +UUSBCONF+UUSBCONF
Modules

Attributes

TOBY-L2 MPCI-L2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

19.16.1 Description
The following terminology will be adopted for the +UUSBCONF command description:•

USB function: a USB capability such as RNDIS, UMS (USB Mass Storage), CDC-ECM, etc. It is implemented
within a device class.
• USB profile: a set of available USB functions (where available means that the function is presented to thehost during the enumeration process), e.g. RNDIS plus CDC-ACM. An identifier (product id, PID) is assigned
for each profile.
• USB product: a set of USB profiles, sharing the same PID, one active at a time. It is possible to switch among
USB profiles within the same USB product.
Each u-blox cellular module consists of one or more USB products from the point of view of the USB
configuration context. Each USB product includes a certain amount of USB profiles. Each USB profile includes
a certain amount of USB endpoints, depending on the overall USB functions of the USB profile.
The command configures the active USB profile. The USB profile selection is performed by the specificationof the USB product category, the network USB function (when available), and the audio over USB function
configuration (enable/disable, when available).
The USB profile switch is not performed run-time. The settings are saved in NVM at the module power
off; the new configuration will be effective at the subsequent module reboot.

19.16.2 Syntax
Type
Set

SyntaxResponse
AT+UUSBCONF=[<id>[,<network>[, OK<audio>]]]Read

AT+UUSBCONF?

Test

AT+UUSBCONF=?

UBX-13002752 - R67+UUSBCONF: <id>,<network>,<audio>,<pid>

ExampleAT+UUSBCONF=0,"AUTO",0OK+UUSBCONF: 0,"RNDIS",0,"0x1144"

OK
OK+UUSBCONF: (<id> (Corresponding +UUSBCONF: (0 ("6 CDC-ACM"),(""),
USB functions (string) for <id>),()),(2 ("NETWORK, 3 CDC-ACM"),(list of the supported <network>s("ECM"),()),(3 ("NETWORK, 1 CDCfor <id>),(list of the supported
ACM"),("RNDIS"),())<audio> values for <id>))[, <id>,
OK(Corresponding USB functions(string) for <id>),(list of the
supported <network>s for <id>),(listof the supported <audio> values for<id>)[,...] ]19 System features

Page 502 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example19.16.3 Defined values
Parameter
<id>

Type
Number

<network>

StringDescription
USB product category number; see Notes for the allowed values and their detailed
description
USB network function

Number• "AUTO": network autodetection• "ECM": CDC-ECM device class• "NCM": CDC-NCM device class• "MBIM": MBIM device class• "RNDIS": RNDIS device class
Audio over USB function configuration

String• 0: audio over USB disabled• 1: audio over USB enabled
String in HEX format with 0x prefix, showing the identifier (PID) of the current profile.

<audio><pid>

Assigned range for PID is 0x1102-0x1FFF.

19.16.4 Notes
•
•
•

•

<network> value is only considered if the <id> category includes a network USB function.
<audio> value is only considered if the <id> category includes a audio over USB function.
When the <id> category does not include a network USB function or an audio over USB function, theinformation text response of the read command is an empty string and an empty value for <network>and <audio> respectively.
Table 40 lists the USB product category associated to a <id>.
<id>0

USB Product category
Fairly back-compatible:

1

It is a configuration similar to the one implemented in the u-blox LISA-U series, where only
CDC-ACMs and, if present, a specific USB function for diagnostic log (e.g. CDC-DIAG) areavailable.
Fairly back-compatible plus audio:2

It is like the "Fairly back-compatible", but audio over USB function is available; audio over USB
function can be enabled or disabled within the same PID.
Low/Medium throughput:
It is a configuration including a Network USB function, a certain number of CDCs-ACM and,if present, a specific USB for the diagnostic log (e.g. CDC-DIAG). Audio over USB is available,
but it can be enabled or disabled.

3

The presence of several USB functions limits the reachable data transfer throughput.
High throughput:

12

It is like the "Low/Medium throughput", but only 1 CDC-ACM is available. High throughput
data rate can be reached only if the audio over USB function is disabled.
Low/Medium throughput plus SAP:
It is a configuration including a Network USB function, a certain number of CDCs-ACM and,if present, a specific USB for the diagnostic log (e.g. CDC-DIAG). SAP over USB is available on
the first CDC-ACM, but it can be enabled or disabled.

13

The presence of several USB functions limits the reachable data transfer throughput.
High throughput plus SAP:
It is like the "High throughput", but only 1 CDC-ACM dedicated to SAP communication.
AT commands can be issued only over the UART interface.

Table 40: USB product configuration
TOBY-L2 / MPCI-L2• <network>="AUTO", "MBIM", "NCM" are not supported.

UBX-13002752 - R67

19 System features

Page 503 of 1001

u-blox cellular modules - AT commands manual••

The <audio> parameter is not supported.
The allowed USB configurations are listed as follows:
Command
AT+UUSBCONF=0
AT+UUSBCONF=2

PID
0x11410x1143Available USB functions
6 CDC-ACM
CDC-ECM (only) + 3 CDC-ACM

RemarkAT+UUSBCONF=2,"ECM"
AT+UUSBCONF=30x1146RNDIS (only) + 1 CDC-ACM

Default and factory-programmed
value

AT+UUSBCONF=3,"RNDIS"AT+UUSBCONF=120x1143
AT+UUSBCONF=12,"ECM"
AT+UUSBCONF=13

0x1146

CDC-ECM (only) + 1 CDC-ACM (SAP)+ 2 CDC-ACM (AT)RNDIS (only) + 1 CDC-ACM (SAP)

AT+UUSBCONF=13,"RNDIS"

Table 41: Supported USB functions
TOBY-L200-00S / TOBY-L200-02S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-02S / TOBY-L210-60S /TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S / MPCI-L200-00S / MPCI-L200-02S /MPCI-L201 / MPCI-L210-00S / MPCI-L210-02S / MPCI-L210-60S / MPCI-L210-63S / MPCI-L220 /MPCI-L280-02S• <id>=12 and 13 are not supported.
SARA-U2 / LISA-U2• <network>="AUTO", "RNDIS", "MBIM", "NCM" are not supported.
• The <audio> parameter is not supported.
• The allowed USB configurations are listed as follows:
Command
AT+UUSBCONF=0

PID
0X1102Available USB functions
7 CDC-ACM

AT+UUSBCONF=20x1104

CDC-ECM (only) + 4 CDC-ACM

RemarkDefault and factory-programmed
value

AT+UUSBCONF=2,"ECM"

Table 42: Supported USB functions

19.17 Serial interfaces configuration selection +USIO+USIO
Modules

Attributes

LARA-R211
SARA-U201-04A SARA-U201-04B SARA-U201-04X
SARA-G450-01C SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

19.17.1 Description
Selects the serial interfaces' configuration.
The configuration affects how an available (either physical or logical) serial interface is used, i.e. the meaningof the data flowing over it. Possible usages are:
• Modem interface (AT command)• Trace interface (diagnostic log)
• Raw interface (e.g. GPS/GNSS tunnelling or SAP)
• Digital audio interface• NoneA set of configurations, that considers all the available serial interfaces' and their associated usage, is called+USIO's configuration variant.
The serial interfaces' configuration switch is not performed run-time. The settings are saved in NVM; thenew configuration will be effective at the subsequent module reboot.

UBX-13002752 - R67

19 System features

Page 504 of 1001

u-blox cellular modules - AT commands manual

A serial interface might not support all the usages. For instance, UART cannot be used as digital audio
interface.
SARA-G4
The command setting is stored in the personal profile following the procedure described in the Saving AT
commands configuration section.

19.17.2 Syntax
Type
Set

SyntaxAT+USIO=<requested_variant>Response
OK

Read

AT+USIO?

+USIO: <requested_variant>,*<active_variant>

Test

AT+USIO=?

OK+USIO: Variant=<requested_variant>: [AT=<AT_interface>;][GNSS=<GNSS_interface>;][TRACE=<Trace_interface>;][DIGITAL AUDIO=<Digital_audio_
interface>] [+USIO: Variant=<requested_variant>: [AT=<AT_
interface>;][GNSS=<GNSS_
interface>;][TRACE=<Trace_interface>;][DIGITAL AUDIO=<Digital_audio_interface>] [...]]OK

ExampleAT+USIO=1
OK+USIO: 1, *1
OK+USIO: Variant=0: AT="UART"; AT="AUX UART"; TRACE="EXT UART"+USIO: Variant=1: AT="UART";
TRACE="AUX UART"; DIGITAL
AUDIO="I2S"+USIO: Variant=2: AT="UART"; AT="AUX UART"; DIGITAL AUDIO="I2S"+USIO: Variant=3: AT="UART";
GNSS="AUX UART"; TRACE="EXTUART"+USIO: Variant=4: AT="UART";
GNSS="AUX UART"; DIGITAL
AUDIO="I2S"
OK

19.17.3 Defined values
ParameterType<requested_variant> Number<active_variant>Number<AT_interface><GNSS_interface><Trace_interface><Digital_audio_
interface>

StringStringStringStringDescription
Requested (stored in NVM for next boot) configuration variant (range 0-255). The
factory-programmed value is 1.
Active (currently used) configuration variant (range 0-255). The factory-programmed
value is 1.
Serial interface configured for AT commands
Serial interface configured for GNSS tunnelling
Serial interface configured for diagnostic log
Serial interface configured for digital audio

19.17.4 Notes•

Table 43 explains the meaning of <AT_interface>, <GNSS_interface>, <Trace_interface>, <Digital_audio_
interface>.
<AT_interface>, <GNSS_interface>, Serial interface description<Trace_interface>, <Digital_audio_
interface>"UART"
Main UART:"AUX UART"

It is the full featured UART (9-wire), used as main interface to the host.
Auxiliary UART:"EXT UART"

It is the general purpose UART (3-wire or 5-wire), with limited v.24 features.
External UART:"USB"

It is not a real UART, but the SPI interface is used to communicate with an
external chip providing SPI to UART conversion. Basically, it is limited todiagnostic log.
USB CDC-ACM or Network over USB:

UBX-13002752 - R67

19 System features

Page 505 of 1001

u-blox cellular modules - AT commands manual<AT_interface>, <GNSS_interface>, Serial interface description<Trace_interface>, <Digital_audio_
interface>
USB CDC-ACM is a virtual UART, providing simulated v.24 features over a USB
interface.
"I2S"

Network over USB is a virtual network interface providing diagnostic logging.
I2S interface:"SPI"

It can be used for the digital audio. See the Chapter 23 for the required
configurations.
SPI interface:"SDIO"

It is limited to diagnostic log.
SDIO interface:
It is limited to diagnostic log.

Table 43: Serial interfaces
LARA-R211• The command is not supported by LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02.
• In case <active_variant> is 2, 4, 5 or 6, the GNSS tunneling is not possible (even if a USB interface isprovided), since the I2C lines for the communication with a GNSS are not available (they are used for the
AUX UART). In this configuration:o I2C devices shall not be connected to the I2C lines.
o There are limitations in the usage of +UGPS, +UI2CO and +UEXTDCONF AT commands.
• The allowed configurations are listed as follows:<active_variant>
0 (factoryprogrammed
value)
1
2
3
4
5
6

AT instance 1

AT instance 2 AT instance 3

AT instance 4

AT instance 5

Diagnostic log

UART

USB1

USB2

USB3

-

USB6

USB1
UART
UART
UART
UART
AUX UART

USB2
USB1
USB1
AUX UART
USB1
USB1

USB3
USB2
USB2
USB1
USB2
USB2

USB3
USB3
USB2
USB3
USB3

-

UART
AUX UART

USB3
-

USB6
AUX UART
UART

Table 44: Supported USIO variants
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• USB profiles are not considered in this description. A generic USB indication is used. For details on theUSB profiles's configurations refer to the +UUSBCONF AT command.
• AUX UART is only available in case <active_variant> is 4, 5 or 6. In case <active_variant> is 4, both UART
and AUX UART are AT commands's interfaces.
• In case <active_variant> is 4, 5 or 6, the GNSS tunneling is not possible (even if a USB interface isprovided), since the I2C lines for the communication with a GNSS are not available (they are used for the
AUX UART). In this configuration:o I2C devices shall not be connected to the I2C lines.
o There are limitations in the usage of +UGPS, +UI2CO and +UEXTDCONF AT commands.
• The allowed (including MUX protocol) configurations are listed as follows:<active_variant>
0 (factoryprogrammed
value)1

UBX-13002752 - R67

AT
instance 1
UART

Not
available

AT
AT
Diagnostic log Mux protocol
instance 2 instance 3
Not
USB
USB
UART
available(COMBINEDTRACE)
Not
USB
UART
Not available
available(BASEBANDTRACE)

19 System features

Digital audio
I2S

GNSS
tunneling
USB

I2S

USB

Page 506 of 1001

u-blox cellular modules - AT commands manual<active_variant>
2
3

4

5

6

AT
instance 1
Not
available
UART

AT
instance 2
NotavailableNotavailable

AT
Diagnostic log Mux protocol
instance 3
USB
UART (3G_FW- Not available
TRACE)USB
USB
UART(BASEBANDTRACE and3G_FWTRACE)UARTAUX UART USB
USB
UART(COMBINEDTRACE)
UART
Not
USB
AUX UART
UART
available(BASEBANDTRACE)AUX UART Not
USB
UART
Not available
available(BASEBANDTRACE)

Digital audio
I2S

GNSS
tunneling
USB

I2S

USB

I2S

USB

I2S

USB

I2S

USB

Table 45: Supported USIO variants
SARA-G3• For information about the <Trace_interface>="EXT UART" configuration, see the module system
integration manual• <Digital_audio_interface>="I2S" and <Trace_interface>="EXT UART" are not supported at the same time,since they share the module's same pins
• The allowed (including MUX protocol) configurations are listed as follows:<active_variant>
0

AT instance 1

AT instance 2 Diagnostic log

Mux protocol

Digital audio

UART

AUX UART

UART

Not available

1 (factoryprogrammed
value)
2
3

UART

Not available

EXT UART (via
SPI interface,
using the I2S
pins)
AUX UART

GNSS
tunneling
Not available

UART

I2S

Not available

UART
UART

AUX UART
Not available

UART
UART

I2S
Not available

Not available
AUX UART

4

UART

Not available

Not available
EXT UART (via
SPI interface,
using the I2S
pins)
Not available

UART

I2S

AUX UART

Table 46: Supported USIO variants
SARA-G450-01C• The serial interfaces' configuration switch is performed run-time.
• The allowed (including MUX protocol) configurations are listed as follows:<active_variant>
0
1 (factoryprogrammed
value)
2
3
4

AT instance 1

AT instance 2 Diagnostic log

Mux protocol

Digital audio

UART
UART

AUX UARTAUX UARTFT UART
FT UART

UART
UART

Not available
Not available

GNSS
tunneling
Not available
Not available

UART
UART
UART

AUX UART
Not available
Not available

FT UART
FT UART
FT UART

UART
UART
UART

Not available
Not available
Not available

Not available
AUX UARTAUX UART

Table 47: Supported USIO variants

UBX-13002752 - R67

19 System features

Page 507 of 1001

u-blox cellular modules - AT commands manual

19.18 USB disable/enable selection and status +UDCONF=78+UDCONF=78
Modules
Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L210-03A TOBY-L210-03S TOBY-L210-65S TOBY-L280-03A
TOBY-L280-03S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Full
No
No
No
< 200 ms
+CME Error

19.18.1 Description
Disables and enables the USB interface at PHY level allowing the interface to enter power saving D2 state withUSB D+ and D- to low level, thus avoiding to process a USB reset request. When in disabled state, if USB D+ isexternally forced to high level the target exits D2 state for the +UPSV timeout period, but then re-enters powersave D2 state again. Rather, if USB D- is externally forced to high level this is interpreted as Data-K resume
signalling and the target exits power save until USB D- remains high.
The read command provides the current USB status is reported.
Disabling the USB causes any higher level Control Model (CDC-ACM, CDC-NCM) to be lost, along withapplication connections. The connection shall be explicitely re-estabilished after the USB interface isre-enabled via AT+UDCONF=78,1 command.
TOBY-L2 / MPCI-L2
The VBUS signal is not monitored, then the USB physical disconnection cannot be distinguished fromUSB suspended state, so both are reported as SUSPENDED. Rather, an USB disconnection due to USB
disable is reported as DISCONNECTED.
The CONNECTED state is not stable and forwards to the CONFIGURED state in hundred of milliseconds.
It can be seen only occasionally immediately after a physical USB connection.
To re-enable a previously disabled USB, issue the AT+UDCONF=78,1 command on the UART interface. If
power save is in use, the UART communication require hardware handshake or expected character loss
should be handled by application properly.

19.18.2 Syntax
Type
Set

SyntaxAT+UDCONF=78,<disable_enable>

Response
OK

ExampleAT+UDCONF=78,0

Read

AT+UDCONF=78+UDCONF: 78,<usb_state>

OK+UDCONF: 78,"CONFIGURED"OK

OK

19.18.3 Defined values
Parameter<disable_enable>

Type
Number<usb_state>

StringDescription
Connection state set. Allowed values:• 0: USB interface disabled• 1: USB interface enabled
Current connection state of the USB interface. Allowed values:• "DISCONNECTED": the USB interface was set in disabled state• "CONNECTED": the USB interface is in enabled state but not still enumerated• "CONFIGURED": the USB interface is connected and enumerated, ready to use• "SUSPENDED": the USB interface is disconnected or in suspended state

19.18.4 Notes
TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L210-65S /TOBY-L280-03A / TOBY-L280-03S• The command is not supported by TOBY-L200-03A-01, TOBY-L200-03S-00, TOBY-L200-03S-01,
TOBY-L210-03A-00, TOBY-L210-03A-01, TOBY-L210-03S-00, TOBY-L210-03S-01, TOBY-L210-03S-34,
TOBY-L210-65S-00, TOBY-L280-03A-01, TOBY-L280-03S-00, TOBY-L280-03S-01.

UBX-13002752 - R67

19 System features

Page 508 of 1001

u-blox cellular modules - AT commands manual

19.19 Establish ECM data connection +UCEDATA+UCEDATA
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
Yes
No
Yes
Up to 3 min+CME Error

19.19.1 Description
Establishes a data communication between the TE and the network over the CDC-ECM interface. This may
include a GPRS attach and a PDP context activation. In case of error, an error result code is displayed. The
requested PDP context cannot be already active. When the data transfer is completed, the ECM connection
can be released by deactivating the corresponding PDP context via the AT+CGACT command.

19.19.2 Syntax
Type
Set

SyntaxAT+UCEDATA=<cid>,<ecm_id>

Response
OK

ExampleAT+UCEDATA=1,0

Read

AT+UCEDATA?

+UCEDATA: [(<cid>,<ecm_id>)]

OK+UCEDATA: (1,0)[+UCEDATA: (<cid>,<ecm_id>)]OK[...]]]
Test

OK+UCEDATA: (list of the supported+UCEDATA: (1-11),(0-2)<cid>s),(list of the supported <ecm_
OK
id>s)

AT+UCEDATA=?

OK

19.19.3 Defined values
Parameter<cid><ecm_id><error>Type
NumberNumberNumberDescription
Specifies a particular PDP context definition. The range goes from 1 to 11.
Specifies the CDC-ECM interface. The range goes from 0 to 2.
These error result codes will be provided if +CMEE is set to 2:
•
•
•
•

•

"+CME ERROR: operation not supported": an incorrect number of parameters isprovided or the parameter values are out of range"+CME ERROR: CDC-ECM is not available": the CDC-ECM connectivity is notpresent (e.g. because of the current AT+UUSBCONF command configuration)"+CME ERROR: GPRS context busy": the <cid> refers to an already active PDP
context"+CME ERROR: CDC-ECM is busy": the data communication between the TE
and the network over the CDC-ECM interface specified by <ecm_id> is alreadyestablished"+CME ERROR: No DHCP Packets received from the DTE": the data communication
between the TE and the network over the CDC-ECM interface cannot beestablished because of a DHCP issue in the TE side

19.19.4 Notes••

The command can be used only if a CDC-ECM interface is present in the active AT+UUSBCONF command
configuration.
IP and DNS addresses are provided to the TE by the network via the DHCP protocol. The module
implements a DHCP server, and the TE shall implement a DHCP client. A 25 s timer is used to allow
command completion (with error result code), in case the DHCP client is not implemented or not
responding.

SARA-U2 / LISA-U2• Only <ecm_id>=0 is supported, since only one CDC-ECM interface is available (see the AT+UUSBCONF
command description).

UBX-13002752 - R67

19 System features

Page 509 of 1001

u-blox cellular modules - AT commands manual•

CONNECT and NO CARRIER result codes are never sent on the AT interface where the command isissued, because the interface does not enter data mode. For this reason, it is still possible to establish
a data connection on the same AT interface (e.g. PPP dial-up), if the CDC-ECM data communication
is established. As a consequence of missing indications on the AT interface, the TE is informed about
the CDC-ECM data communication release by means of specific indications provided by the CDC-ECM
interface (e.g. media disconnection indication).

19.20 Start, stop and configure the OMA-DM client +UOMADM+UOMADM
Modules

Attributes

TOBY-L4006
LARA-R202 LARA-R203 TOBY-R200-02B TOBY-R200-82B TOBY-R202
SARA-U201
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

19.20.1 Description
Starts, stops and configures the OMA-DM client configuration.
For more information on OMA-DM, see OMA-DM specs [110].
It is necessary to set the correct date and time to be fully operational on the network. This can be doneby means of +CCLK command or by enabling the automatic date and time zone update with +CTZU
command.

19.20.2 Syntax
Type
Set

Test

SyntaxAT+UOMADM=<mode>[,<sessionID>,<serverInfo>,<encoding_option>,<certinfo_
dynamic>,<certtype>]
AT+UOMADM=?

Response
OK

ExampleAT+UOMADM=1
OK+UOMADM: (list of supported<mode>'s)+UOMADM: (0-2)
OKOK

19.20.3 Defined values
Parameter<mode>

Type
NumberDescription
Indicates whether the start or stop the OMA-DM client:•<sessionID><serverInfo><encoding_option>

NumberStringNumber<certinfo_dynamic> String<certtype>
NumberUBX-13002752 - R67

0: stop the OMA-DM client. <sessionID>, <serverInfo>, <encoding_option>,<certinfo_dynamic>, <certtype> must not be specified.
• 1: start the OMA-DM client. <sessionID>, <serverInfo>, <encoding_option>,<certinfo_dynamic>, <certtype> must not be specified.
• 2: configure the OMA-DM client. <sessionID>, <serverInfo>, <encoding_option>,<certinfo_dynamic>, <certtype> must be specified.
Specifies the OMA-DM session ID.
Specifies the OMA-DM server URL and port type.
Specifies the encoding used for communicating with the OMA-DM server. Allowed
values:• 0: unspecified• 1: WBXML• 2: XMLSpecifies the certificate used for communicating with the OMA-DM server.
Specifies the type of certificate used for communicating with the OMA-DM server.
Allowed values:• 0: DER• 1: PEM• 2: P7B• 2: PFX

19 System features

Page 510 of 1001

u-blox cellular modules - AT commands manual

19.20.4 Notes
LARA-R203• The command is not supported by LARA-R203-02B-34.

19.21 OMA-DM alert +UOMADMALERT+UOMADMALERTModules
TOBY-L4006
LARA-R202 LARA-R203 TOBY-R200-02B TOBY-R200-82B TOBY-R202
SARA-U201
SyntaxPIN required
Settings saved Can be aborted Response time
Attributes
full
No
No
No
~400s
(dependingon network
connectivity)

Error reference+CME Error

19.21.1 Description
Allows the Host Device SW to initiate or to stop an OMA-DM session sending a generic alert to the OMA-DM
server.
If successful, the +UOMADMALERT: 0 information text response is provided.
For more information on OMA-DM, see OMA-DM specs [110].

19.21.2 Syntax
Type
Set

SyntaxAT+UOMADMALERT=<mode>[,<alert_name>,<alert_type>,<alert_
URI>]

Response+UOMADMALERT: <result_code>
OK

ExampleAT+UOMADMALERT=1,"dummy","org.openmobilealliance.dm.
firmwareupdate.devicerequest","./
DevDetail/SwV"+UOMADMALERT: 0
OK
AT+UOMADMALERT=0OK
AT+UOMADMALERT=1,"dummy2","wrong","./DevDetail/SwV"

Test

AT+UOMADMALERT=?

+UOMADMALERT: (list of
supported <mode>'s)

ERROR+UOMADMALERT: (0,1)
OKOK

19.21.3 Defined values
Parameter<mode>

Type
NumberDescription
Specifies whether to start or stop an OMA-DM alert session:•<alert_name><alert_type>

StringString<alert_URI>

String<result_code>

NumberUBX-13002752 - R67

0: stops a client initiated OMA-DM generic alert session. <alert_name>, <alert_
type> and <alert_URI> must not be specified.
• 1: starts a client initiated OMA-DM generic alert session. <alert_name>, <alert_
type> and <alert_URI> must all be specified.
String indicating the OMA-DM generic alert identifier. This parameter is ignored.
The "Type" parameter of a Generic Alert. It must be a reverse domain name URN
specifying the media type of the content information in the Data element.
The "LocURI" parameter of a Generic Alert. Normally, it should hold the URI pointing
to a node in the DM Tree.
Return code for the alert notification procedure. Only 0 (success) is supported.

19 System features

Page 511 of 1001

u-blox cellular modules - AT commands manual

19.21.4 Notes
LARA-R203• The command is not supported by LARA-R203-02B-34.

19.22 OMA-DM repository access +UOMADMREP+UOMADMREP
Modules
TOBY-L4006
LARA-R202 LARA-R203 LARA-R204 TOBY-R200-02B TOBY-R200-82B TOBY-R202
SARA-U201
SyntaxPIN required
Settings saved Can be aborted Response time
Attributes
full
No
NVM
No
-

Error reference+CME Error

19.22.1 Description
Allows a direct interaction with the OMA-DM repository. The set command is used to set/read the value to thecorresponding node path. The +UUOMADMREP URC indicates a node content has been modified.
The node path (or URI) is case sensitive.
For writing into the DM tree, the URI of a leaf (terminal) node URI has to be specified. For reading, if
an internal (non-terminal) node is specified, then a double quoted, slash-separated list of sub-nodes isdisplayed.
The ODIS (OMA-DM IMEI Sync) nodes which should be set by an external application once (e.g. at firstboot) are:• ./DevDetail/Ext/HostMan• ./DevDetail/Ext/HostMod• ./DevDetail/Ext/HostSwV• ./DevDetail/Ext/HostID
These values are stored in NVM. The module automatically attempts to notify the OMA-DM server thatthese nodes have been changed.
The ./DevDetail/Ext/HostID node can be written but cannot be read.
For more information on OMA-DM, see OMA-DM specs [110].

19.22.2 Syntax
Type
SyntaxResponse
Generic syntax
AT+UOMADMREP=<access_mode>, OK<node_URI>[,<leaf_node_data>]
Writing values into the DM tree
Set
AT+UOMADMREP=1,<node_URI>,
OK<leaf_node_data>

ExampleAT+UOMADMREP=1,"./DevInfo/
Lang","Italian"OK
Reading values and structure from the DM tree
Read
AT+UOMADMREP=0,<node_URI>+UOMADMREP: <node_URI>,<node_ AT+UOMADMREP=0,"./DevInfo"
data>+UOMADMREP: "./DevInfo","Ext/OK
Mod/Man/Lang/DmV/DevId"
OK
AT+UOMADMREP=0,"./DevInfo/
Lang"+UOMADMREP: "./DevInfo/Lang","Italian"
OK
Test

AT+UOMADMREP=?

UBX-13002752 - R67+UOMADMREP: (list of supported<mode>'s)

19 System features+UOMADMREP: (0-1)
OKPage 512 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK+UUOMADMREP: <node_URI>,<leaf_node_data>

URC

Example+UUOMADMREP: "./DevInfo/Lang","Italian"19.22.3 Defined values
Parameter<access_mode>

Type
Number<node_URI>

String<node_data>

StringDescription
Indicates what action is to be perfomed• 0: read command; it returns the contents of a node
• 1: write command; it replaces the contents of a node
Path (URI) to the node in the OMA-DM tree. If the node is a leaf, the contents of thenode is displayed. If the node is internal, a quoted, comma separated list of sub-nodes
is displayed.
Contents of the OMA-DM node, if it is a leaf (terminal) node.
List of the sub-nodes, if it is an internal (non-terminal) node.

<leaf_node_data>

String

The factory-programmed value for these ODIS nodes is:• ./DevDetail/Ext/HostMan: "HMAN1"• ./DevDetail/Ext/HostMod: "HMOD1"• ./DevDetail/Ext/HostSwV: "HSW1"• ./DevDetail/Ext/HostID: "HUID1"
Contents of the leaf (terminal) node of the DM tree.
It must not be specified when reading (<access_mode>=0).
It must be specified when writing (<access_mode>=1).

19.22.4 Notes
LARA-R2 / TOBY-R2• The +UUOMADMREP URC is not supported.
LARA-R203• The command is not supported by LARA-R203-02B-34.
TOBY-R2• On TOBY-R202-02B-00 and TOBY-R200-02B-00 the "HostPlasmaID" node name is used in place of"HostID", and can be read out.
• On TOBY-R202-02B-00 and TOBY-R200-02B-00 the factory-programmed value for the nodes ./DevDetail/Ext/HostMan, ./DevDetail/Ext/HostMod, ./DevDetail/Ext/HostSwV and ./DevDetail/Ext/
HostPlasmaID is an empty string• On TOBY-R202-02B-00 and TOBY-R200-02B-00 the OMA-DM server is not automatically notified ofchanges to ODIS nodes. The notification can be manually triggered with the +UOMADMALERT AT
command.
SARA-U201• To use this command, enable first the OMA-DM client by means of the +UOMADM=1 AT command.
• The +UUOMADMREP URC indicates that a node content has been modified (either locally, via this ATcommand, or remotely via OMA-DM protocol).
SARA-U201-03A / SARA-U201-03B / SARA-U201-03X / SARA-U201-63B• The "HostPlasmaID" node name is used in place of "HostID", and can be read out.
• The factory-programmed value for the nodes ./DevDetail/Ext/HostMan, ./DevDetail/Ext/HostMod, ./DevDetail/Ext/HostSwV and ./DevDetail/Ext/HostPlasmaID is an empty string• The OMA-DM server is not automatically notified of changes to ODIS nodes. The notification can be
manually triggered with the +UOMADMALERT AT command.

UBX-13002752 - R67

19 System features

Page 513 of 1001

u-blox cellular modules - AT commands manual

19.23 Enable/disable OMA-DM unsolicited status messages+UOMASTAT+UOMASTAT
Modules

Attributes

TOBY-L4006 TOBY-L201-02S MPCI-L201-02S
LARA-R202 LARA-R203 LARA-R204 TOBY-R200-02B TOBY-R200-82B TOBY-R202
SARA-U201
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

19.23.1 Description
To enable/disable OMA-DM unsolicited status messages.

19.23.2 Syntax
Type
Set

SyntaxAT+UOMASTAT=<mode>

Response
OK

ExampleAT+UOMASTAT=1

Read

AT+UOMASTAT?

+UOMASTAT: <mode>

OK+UOMASTAT: 0

Test

AT+UOMASTAT=?

OK+UOMASTAT: (list of supported<mode>'s)
OK+UUOMASTAT: <SessionType>,<State>,<Error>

URC

OK+UOMASTAT: (0,1)
OK+UUOMASTAT: 1,0,0

19.23.3 Defined values
Parameter<mode>

Type
Number<SessionType>

Number<State>Number<Error>NumberDescription
Indicates whether the +UUOMASTAT URC is enabled or not:• 0 (factory-programmed value): OMA-DM status indication disabled• 1: OMA-DM status indication enabled
Indicates the OMA-DM Session Type or the Data Connection Setup phase. Allowed
values:• 0: Data Connection Setup• 1: DM Session• 2: Download Session
If <SessionType> is 0 (Data Connection Setup), it indicates the Data Connection
Setup phase (See Table 50 below for specific values). Otherwise, it indicates the
OMA-DM Session State. Allowed values:• 0: session started• 1: session completed successfully• 2: session aborted
Indicates the OMA-DM Error Code or Data Connection Setup Error Code. 0 means
successful (no error). See Table 48, Table 49 and Table 50 below and below for moredetails

19.23.4 Notes
OMA-DM Error Codes• For DM sessions (<SessionType> is 1), if <State> is 1 (session completed successfully), the <Error>
is the Response Status Code from the SyncML protocol (see SyncML Representation Protocol,
OMA-TS-SyncML-RepPro-V1_2_2-20090724-A, from [132]), with ranges 100-999. Other error codes orcode ranges may represent an internal error.
Error code02

UBX-13002752 - R67

Meaning
Success.
Invalid input.

19 System features

Page 514 of 1001

u-blox cellular modules - AT commands manual

Error code
16
17
18
19
32
101
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
300
301
302
303
304
305
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425

UBX-13002752 - R67

Meaning
Unspecified error.
Memory error.
Routine called when not allowed or bad parameters.
VDM_run called with non-resume trigger when suspended.
SyncML message protocol or version error.
In progress.
OK. The SyncML command completed successfully.
Item added. The requested item was added.
Accepted for processing.
Non-authoritative response.
No content.
Reset content. The source SHOULD update their content.
Partial content.
Conflict resolved with merge.
Conflict resolved with client's command "winning".
Conflict resolved with duplicate.
Delete without archive.
Item not deleted. The requested item was not found.
Authentication accepted.
Chunked item accepted and buffered.
Operation cancelled.
Not executed.
Atomic roll back OK.
Multiple choices.
Moved permanently. The requested target has a new URI.
Found.
See other. The requested target can be found at another URI.
Not modified.
Use proxy.
Bad request.
Invalid credentials.
Paymentneeded.
Forbidden.
Not found. The requested target was not found.
Command not allowed.
Optional feature not supported.
Missing credentials.
Request timeout.
Conflict.
Gone.
Size REQUIRED.
Incomplete command.
Request entity too large.
URI too long.
Unsupported media type or format.
Requested size too big.
Retry later.
Already exists.
Conflict resolved with server data.
Device full.
Unknown search grammar.
Bad CGI Script.
Soft-delete conflict.
Size mismatch.
Permission Denied.

19 System features

Page 515 of 1001

u-blox cellular modules - AT commands manual

Error code
426
427
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
516
517
8194
16896
16897
16898
16899
16900
16901
16902
16903
16944
24576
24577
24578
24579
24580
24581
24582
24583
24584
24585
24586
24587
24588
24589
24590
24591
24592
24593
24594
24595
24596
24597
24598
24599
24833
24834

UBX-13002752 - R67

Meaning
Partial item not accepted.
Item Not empty. Parent cannot be deleted since it contains children.
Command failed.
Command not implemented.
Bad gateway.
Service unavailable.
Gateway timeout.
DTD Version not supported.
Processing error.
Atomic failed.
Refresh REQUIRED.
Reserved for future use.
Data store failure. An error occurred while processing the request.
Server failure.
Synchronization failed.
Protocol Version not supported.
Operation cancelled.
Atomic roll back failed.
Atomic response too large to fit.
RTK workspace buffer too small
Failed to create database
Failed to open database
Failed to insert data to database
Failed to update data to database
Failed to select data from database
Failed to delete data from database
Failed to purge data from database
Failed to upgrade the database schema
Bad Message from server
Supplied buffer is too small
Badly formatted input
Tree node already exists
Tree node is missing
Parent node is missing
Error in leaf node
Leaf node expected
Unknown property
Attempt made to delete a permanent nodeNot allowed by AccessType
Client aborted
Client access denied
Partial write of external data not allowed
Write of external data not allowed at this time
May not replace
Persistent storage read error
Persistent storage write error
Authentication failure
Access denied by ACL
External data value is not readable
External data value is not writable
Node not registered for execute
Tree open error
Tree commit error
Missing start message command
Missing status command

19 System features

Page 516 of 1001

u-blox cellular modules - AT commands manual

Error code
24835
24837
24838
24839
24840
24841
24842
24843
24845
24846
25088
25089
25090
25091
25092
25093
25094
25095
25096
25097
25104
25105
25106
25107
25108
25109
25344
25345
25346
25347
25348
25349
25350
25351
25352
25408
25472
25599
25601
25602
25604
25605
25606
25607
25608
25609
25856
32769
32770
32771
32772
32773

Meaning
Optional feature not implemented
Alert - options parsing error
Alert - not enough items
Alert - not enough data
No data
Alert - user cancelled or aborted
Alert - too many choices passed to implementation
Alert - server has sent a session-abort alert
Data is too long to pass back as a large object
Command status code is failed
Notification - message has invalid length
Notification - message has invalid digest
Boot message has invalid digest
Could not get NSS for bootstrap
Could not get PIN for bootstrap
Bad bootstrap PIN length
Bad bootstrap SEC value
Bad bootstrap MAC
Bad bootstrap message
Bad bootstrap profile
Bad trigger reason
Notification - message contains unsupported version info
Bootstrap not currently allowed
Non-DM Bootstrap message
Download object too large
Bad Nia Format
Unsupported protocol
Mismatched reply: XML received when WBXML sent or vice-versa
General fatal transport error
General non-fatal transport error (can be retried)
Socket timeout transport error
General socket non-fatal (retriable) socket error
HTTP result wasn't found
HTTP result bad request
HTTP result internal server error
HTTP error
Start range of vendor specified transport errors
End range of vendor specified transport errors
Internal error
Error accessing MO external storage
User cancelled update or download
Could not initiate update client
Download URL is malformed or bad
Error while parsing Download Descriptor
ETag changed, 412 returned because of If-match
Error while parsing Download Descriptor - descriptor size is 0
A call to a vDirect Mobile API is out of sync
Error accessing registry
Shutting down - cannot enqueue triggers or timed events
Out of Bounds - an array was accessed out of bounds
Download package cannot be removed
Error accessing storage

Table 48: Typical SyncML Error codes for completed sessions•

For DM sessions (<SessionType> is 1), if <State> is 2 (session aborted), the <Error> may be:

UBX-13002752 - R67

19 System features

Page 517 of 1001

u-blox cellular modules - AT commands manual

Error code2
3
4

Meaning
Internal error
Memory error
Usage error

Table 49: OMA-DM Error codes for aborted sessions
Data Connection Setup results• If <SessionType> is 0, the <Error> may take different meanings according to <State>. Unless noted
differently, 0 means successful and -1 is the generic error code.
State N.
0
1

Meaning
Received a defined PDP context
Defined a new PDP context

2
3
4

Activated a PDP Context
Connected a PDP Context
Received the Protocol
Configuration Options (PCO)
Settings
Received the Negotiated DNS
No specific error code.
properties of a PDP context
Received the negotiated IP address No specific error code.
of a PDP context
Creation of an create a IP Stack• 1: Network Interface Creation failure (handler error).
Network Interface• 2: Network Interface Creation/Request in progress.
• 3: Invalid Parameters.
• 4: Network Interface Creation failure.
• 5:
Network
Interface
Createdbut
AutoConfiguration failure.
Retrieved the state of a PDP
Same as 1: above.
context
Notification received from IP Stack• 1: Network Interface is down.
• 2: IPv6 Auto Address Configuration Success.
• 3: IPv4 Auto Address Configuration Success.
• 4: DNS Address Configuration Success.
• 5: SIP Address Configuration Success.
• 6: IPv4 Auto Address Configuration Failure.
• 7: IPv6 Auto Address Configuration Success.
• 8: DNS Address Configuration Success.
• 9: SIP Address Configuration Success.

5
6
7

8
9

Possible error codes and meaning
Notice this phase can be repeated several times.
• -150: SM FDN Check Failed• -151: MBMS Capabilities Insufficient• -152: Activation Rejected Bcm Violation• -153: SM No Response Timeout• -154: MS Internal Failure
Other error codes are described in 3GPP TS 24.008 [12],under 10.5.3.6 (Reject cause -- General Reject Cause), 10.5.6.6 (SM cause), Table 9.9.4.4.1 (ESM cause information
element).
Same as 1: above.
Same as 1: above.
The number is the actual PDP Context identifier for which
the PCO settings have been received.

Table 50: Data Connection Setup Error codes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2• The Data Connection Setup phase is not shown, so <SessionType> cannot be 0
LARA-R203• The command is not supported by LARA-R203-02B-34.

UBX-13002752 - R67

19 System features

Page 518 of 1001

u-blox cellular modules - AT commands manual

19.24 Internal temperature monitor +UTEMP+UTEMP
Modules
Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
partial
No
No
No-

Error reference+CME Error

19.24.1 Description
Returns the values of internal temperature sensors of the specified unit.
The command handling (sensors position and command syntax) depends on the module series:• TOBY-L4 - The temperature measurement is performed by the following sensors:o NTC sensors near to the oscillator (XO) and to the RF transceiver IC
o One sensor near the Power Management Multi Channel IC (PMIC)o Six sensors available in baseband core (BB)19.24.2 Syntax
Type
Set

SyntaxAT+UTEMP=<unit>

Response
OK

Read

AT+UTEMP?

+UTEMP: <xo_temp>,<rf_temp>,<pmic_temp>,<bb0_temp>,<bb1_
temp>,<bb2_temp>,<bb3_temp>,<bb4_temp>,<bb5_temp>

Test

AT+UTEMP=?

ExampleAT+UTEMP=0OK+UTEMP: 31,30,31,36597,36597,
37175,29272,35449,37175
OK

OK+UTEMP: (list of supported <unit>)+UTEMP: (0-1)

OKOK

19.24.3 Defined values
Parameter<unit>

Type
Number<xo_temp>

Number<rf_temp>

Number<pmic_temp>

Number<bb0_temp>, <bb1_ Number
temp>, <bb2_temp>,<bb3_temp>, <bb4_
temp>, <bb5_temp>

UBX-13002752 - R67

Description
Select the measurement unit for value representation:• 0: values in tenth of Celsius degrees returned• 1: values in tenth of Fahrenheit degrees returned
Fetched the value of XO temperature of the selected measurement unit; the allowed
range depends on the measurement unit:• Celsius degrees: [-40; 140]
• Fahrenheit degrees: [-40; 284]
• 655355: no valid temperature measure is available
Fetched the value of transceiver temperature of the selected measurement unit; theallowed range depends on the measurement unit:• Celsius degrees: [-40; 140]
• Fahrenheit degrees: [-40; 284]
• 655355: no valid temperature measure is available
Fetched value of PMIC temperature of the selected measurement unit; the allowed
range depends on the measurement unit:• Celsius degrees: [-40; 140]
• Fahrenheit degrees: [-40; 284]
• 655355: no valid temperature measure is available
Fetched the value in BB temperature in mills of the selected measurement unit:• Celsius degrees: [-40000; 140000]• Fahrenheit degrees: [-40000; 284000]• 655355: no valid temperature measure is available

19 System features

Page 519 of 1001

u-blox cellular modules - AT commands manual

19.25 Restore factory configuration +UFACTORY+UFACTORY
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G4 SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
5s
+CME Error

19.25.1 Description
Force, at the next module boot, the restore of the factory configuration for FS and/or NVM.
When the command is issued, a flag is written into the NVM: no action is done and it will be triggered to be
executed only at the next module boot. If, before the next boot, the triggered operation must be deleted, thenit is possible to issue the command with parameter 0,0.

19.25.2 Syntax
Type
Set

SyntaxResponse
AT+UFACTORY=<fs_op>,<nvm_op> OK

ExampleAT+UFACTORY=0,1

Read

AT+UFACTORY?

OK+UFACTORY: 0,1

Test

AT+UFACTORY=?

+UFACTORY: <fs_op>,<nvm_op>

OK
OK+UFACTORY: (list of supported <fs_ +UFACTORY: (0-2),(0-2)op>s),(list of supported <nvm_op>s)OKOK

19.25.3 Defined values
Parameter<fs_op>Type
Number<nvm_op>NumberDescription
FS factory restore type:• 0 (factory-programmed value): no factory restore• 1: FS flash sectors erased• 2: all files stored in FS deleted
NVM factory restore type:• 0 (factory-programmed value): no factory restore• 1: NVM flash sectors erased• 2: for internal use only

19.25.4 Notes
TOBY-L4• Depending on the volume of user files stored in the module, the next boot could be delayed by at mostone or two seconds.
• <fs_op>=1 is not supported.
TOBY-L2 / MPCI-L2• Depending on the volume of user files stored in the module, the next boot could be delayed by at mostone or two seconds.
• <fs_op>=1 is not supported.
TOBY-R2• The +URXDIV command setting is not affected by +UFACTORY NVM restore option (<nvm_op>=1),
therefore it needs to be specifically reverted to its factory-programmed setting, if previously changed.

UBX-13002752 - R67

19 System features

Page 520 of 1001

u-blox cellular modules - AT commands manual

SARA-U2 / LISA-U2• Depending on <fs_op> and <nvm_op> values, the next module boot could be delayed. Table 51 lists delaysof each operation.
Parameter<fs_op><nvm_op>•

Value Delay
1
2 minutes
2
No delay (but background garbage collector process needs to run).
If the garbage collector has not had enough time to be executed, then it will be executedat the next power-off/reset, which will take a longer time. If the FS is completely full, thenthe garbage collector takes about 2 minutes.
12s

Table 51: Module boot timing
The +URXDIV command setting is not affected by the +UFACTORY NVM restore option (<nvm_op>=1),
therefore it needs to be specifically reverted to its factory-programmed setting, if previously changed.

SARA-G3• <fs_op>=2 is not supported.
• If <fs_op>=1 the SMSes stored in the ME message storage are deleted.
• The settings of these commands are restored to the factory-programmed settings by means of the<fs_op>=1: +UCSD, +ICF, +UPSD, +UGAOF, +UGAOP, +UGGGA, +UGGLL, +UGGSA, +UGGSV, +UGPRF,+UGRMC, +UGZDA, +UGSRV, +ULOCCELL, +ULOCGNSS.
• Depending on <fs_op> and <nvm_op> values, the next module boot could be delayed.
Parameter<fs_op><nvm_op>

Value Delay
1
9s
1
-

Table 52: SARA-G3 boot timing
SARA-G4• <fs_op>=2 is not supported.
• <nvm_op>=2 is not supported.
• If <fs_op>=1 the SMSes stored in the ME message storage are deleted.
• The settings of these commands are restored to the factory-programmed settings by means of the <fs_
op>=1: +ICF, +UPSD.

19.26 NVM RAM mode management +UDCONF=110+UDCONF=110
Modules
TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
Attributes
full
No
NVM
No
-

Error reference+CME Error

19.26.1 Description
Sets the NVM RAM mode for AT command settings stored in NVM.
In RAM mode, an AT command with settings in NVM does not write changes on physical flash, but on RAM
mirror only. Write in flash is performed by a dedicated AT command +UNVMW.
When NVM setting manager of a specified AT group commands is configured to operate in RAM mode, thefollowing AT commands are available for the synchronization of RAM mirror, NVM and factory-programmed
values:• +UNVMW commits NVM settings from RAM to NVM,
• +UNVMR resets the RAM settings from NVM and apply them run-time.
• +UNVMF restores the factory settings into NVM at reboot,
The AT groups are product-specific.
RAM mode is useful for customer devices not requiring NVM capabilities on u-blox module (example: audio
settings are configured at each boot by the application processor).

UBX-13002752 - R67

19 System features

Page 521 of 1001

u-blox cellular modules - AT commands manual

In order to apply the new NVM RAM mode the module needs to be rebooted.

19.26.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UDCONF=110,<at_group>,<mode>Read

AT+UDCONF=110

Response

ExampleOK

AT+UDCONF=110,"audio",1

OK+UDCONF: 110,<at_group>,<mode> AT+UDCONF=110
OK+UDCONF: 110,"audio",(0-2)
OK

Audio configuration
Set
AT+UDCONF=110,"audio",<mode>

OK

AT+UDCONF=110,"audio",1

Read+UDCONF: 110,"audio",<mode>

OK
AT+UDCONF=110,"audio"

OK+UDCONF: 110,"audio",1

AT+UDCONF=110,"audio"OK

19.26.3 Defined values
Parameter<at_group>

Type
String<mode>

NumberDescription
AT group:• "audio"; group has factory-programmed value 1 for <mode> parameter.
Mode. Allowed values:• 0: NVM mode
• 1: RAM mode
• 2: reserved

19.26.4 Notes•

To list all the AT commands that belong to a specific group use AT+UDCONF=?. Example output:+UDCONF: 110,"audio","+CLVL,+CRSL,+UMGC,+USGC,+UMSEL,+UMAFE,+USAFE,+UI2S,+USPM"

19.27 NVM configuration management commit +UNVMW+UNVMW
Modules
Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

19.27.1 Description
Commits RAM configuration changes to NVM.
This command should be used in RAM mode of operation. See +UDCONF=110 on details about
configuration operation mode and changing it.

19.27.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UNVMW=<class>

Response

ExampleOK

AT+UNVMW="audio"

Test+UNVMW: (list of supported<class>es)

AT+UNVMW=?

OK+UNVMW: ("audio")
OK

OK

UBX-13002752 - R67

19 System features

Page 522 of 1001

u-blox cellular modules - AT commands manual

19.27.3 Defined values
Parameter<class>Type
StringDescription
Class:• "audio": audio configuration

19.27.4 Notes
TOBY-L4• <class>="audio": digital I2S settings are written to NVM only when the digital profile is active.

19.28 NVM configuration management reset +UNVMR+UNVMR
Modules
Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

19.28.1 Description
Resets RAM configuration from NVM and applies it.
This command should be used in RAM mode of operation. See +UDCONF=110 on details about
configuration operation mode and changing it.

19.28.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UNVMR=<class>

Response

ExampleOK

AT+UNVMR="audio"

Test+UNVMR: (list of supported<class>es)

AT+UNVMR=?

OK+UNVMR: ("audio")OKOK

19.28.3 Defined values
Parameter<class>Type
StringDescription
Class:• "audio": audio configuration

19.29 NVM configuration management factory restore+UNVMF+UNVMF
Modules
Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

19.29.1 Description
Restores the factory-programmed configuration.
Reboot the module in order to apply the new configuration.
See +UDCONF=110 on details about configuration operation mode and changing it.

19.29.2 Syntax
Type
SyntaxGeneric syntax

UBX-13002752 - R67

Response

19 System features

ExamplePage 523 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+UNVMF=<class>

Response
OK

Test

AT+UNVMF=?

+UNVMF: (list of supported<class>es)

ExampleAT+UNVMF="audio"
OK+UNVMF: ("audio")OKOK

19.29.3 Defined values
Parameter<class>Type
StringDescription
Class:• "audio": audio configuration

19.30 KT remote reset KTCFUN
KTCFUN
Modules
Attributes

SARA-U270-53S
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time< 10 sError reference+CME Error

19.30.1 Description
This KT specific AT command selects the level of facility in the MT.

19.30.2 Syntax
Type
Set

SyntaxKTCFUN=[<fac>]

Response
KTCFUN: <result>

Test

ATKTCFUN=?

KTCFUN: OK
KTCFUN: (list of supported <fac>s) KTCFUN: (1-4)
OK

ExampleATKTCFUN=4

OK

19.30.3 Defined values
Parameter<fac><result>

Type
NumberDescription
Facility to set. Allowed values:

String• 1: online mode
• 2: offline mode
• 3: low power mode; this setting does not have effect• 4 (factoru-programmed value): reset
If the command success, the "KTCFUN: OK" is returned

19.31 KT reading quality information KTDEVSTATKTDEVSTAT
Modules
Attributes

SARA-U270-53S
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

19.31.1 Description
This KT specific AT command retrieves quality information elements from the MT.
In the information text response the strings are not enclosed within double quotes.
The command needs of the SIM to correctly work.

UBX-13002752 - R67

19 System features

Page 524 of 1001

u-blox cellular modules - AT commands manual

19.31.2 Syntax
Type
ActionSyntaxATKTDEVSTAT

Response
KTDEVSTAT:<qmv>,<rssi>,<rscp>,<e/i>,<tx>,<apn>,<qos>,<br>,<srvc>,<ss>,<cs>,<freq>,<rat>,<psc>,<d/n>,<ver>,<imei>,<iccid>
OK

ExampleKTDEVSTAT:1.1.9,-95,-106,-11,-98,
biz.ktfwing.com,5760/42000,0,2,2,
1,2100,HSPA,49,SARA-U270,23.41,
352253060016648,8939010000
1253978700
OK

19.31.3 Defined values
Parameter<qmv><rssi><rscp><ec/io>
<tx>
<apn>

Type
StringNumberNumberNumberNumberStringDescription
Quality Management Version, fixed value 1.1.9
Received Signal Strength Indication, value expressed in dBm, range (-118 ~ -26)
Received Signal Code Power, value expressed in dBm, range (-115 ~ -40)Signal to Noise ratio, value expressed in dBm, range (-32 ~ 0)
Tx power level, value expressed in dBm, range (-50 ~ -33)
Access Point Name, maximum length 30 characters. Only the APN set for CID 3 isshown. Value is displayed if it matches one of the following APNs:<qos>

String<br><srvc>

NumberNumber• bizauth.ktfwing.com• publicip.ktfwing.com• biz.ktfwing.com• Custom APN set with KTUBXCONF AT command
Quality of Service, maximum length 12 bytes. The value represents a string with thevalues of maximum uplink/downlink bit rate assigned by the network
Block Error Rate, value in range (0 ~ 100)Service status, value in range (0 ~ 4)

Number• 0: No service• 1: Limited service• 2: Service available• 3: Limited regional service• 4: Power save or deep sleep
Socket state, value in range (0 ~ 10)

Number• 0: None, initial state• 1: Data access connecting• 2: Data access connected• 3: TCP access connecting• 4: TCP access connected• 5: TCP access terminating• 6: TCP access terminated• 7: Data access terminating• 8: Data access terminated• 9: DNS reading• 10: DNS reading complete
Call state, value in range (-1 ~ 4)

NumberString• -1: None
• 1: Idle (no call)• 2: Dialling• 3: Incoming call
• 4: BusyFrequency Channel Number
Radio access technology. Value expressed as string. Possible values are:

<ss>

<cs>

<freq>
<rat>

•
•
•
•
•

UBX-13002752 - R67

GSM
GPRS
EGPRS
UMTS
HSDPA

19 System features

Page 525 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

<psc>
<d/n>
<ver>
<imei><iccid>NumberStringStringStringStringDescription• HSUPA• HSPA• LTE (not applicable for 3G modules)
Primary Scrambling Code, value in range (0 ~ 511)
Device Name, maximum length 20 characters. The module model name.
Device Version, maximum length 20 characters. The module firmware version
International Mobile Equipment Identity, maximum length 15.
Integrated Circuit Card Identifier, maximum length 20.

19.31.4 Notes••

The APN to be used for FOTA connection shall be configured to CID 3
On the reception of SMS PUSH of type Modem Quality Information (SMS text = *147359*12358*2*,IP_
ADDRESS,PORT) the module needs to activate and internal data context in order to send an HTTP POST
request to the FOTA server. The APN and authentication parameters SHALL be configured with the+UPSD command on the profile id 3. The configuration shall also be stored into NVM with the +UPSDA=3,1
command, in order to make possible for the module to load the data connection configuration when it isrequired.

19.32 KT configuration command KTUBXCONFKTUBXCONF
Modules
Attributes

SARA-U270-53S
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

19.32.1 Description
This command let the user specify the telephone number of the inserted SIM card and an optional APN to berecognized as valid for KT FOTA connection.

19.32.2 Syntax
Type
Set

SyntaxResponse
ATKTUBXCONF=<phone_number>[, OK<fota_apn>]

ExampleATKTUBXCONF="1030000000","custom.kt.fota.apn"

Read

ATKTUBXCONF?

KTUBXCONF:<phone_number>,<fota_apn>

OK
KTUBXCONF:"1030000000","custom.kt.fota.apn"

Test

ATKTUBXCONF=?

KTUBXCONF:(list of supported
params)OK

OK
ATKTUBXCONF=?
KTUBXCONF:"phone_number","fota_apn"
OK

19.32.3 Defined values
Parameter<phone_number><fota_apn>

UBX-13002752 - R67

TypeStringStringDescription
Customer phone number
Additional APN to be recognized as valid for KT FOTA connection on CID 3. See also
ATKTDEVSTAT

19 System features

Page 526 of 1001

u-blox cellular modules - AT commands manual

19.33 Reject international calls KTUCALLREJKTUCALLREJ
Modules
Attributes

SARA-U270-53S
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

19.33.1 Description
Enables/disables the automatic rejection of incoming international calls.
The set command may be issued only when a South Korean SIM card (MCC=450) is inserted.

19.33.2 Syntax
Type
Set

SyntaxATKTUCALLREJ=<mode>

Response
OK

ExampleATKTUCALLREJ=1

Read

ATKTUCALLREJ?

KTUCALLREJ: <mode>

OK
KTUCALLREJ: 1

Test

ATKTUCALLREJ=?

OK
KTUCALLREJ: (list of supported<mode>s)OK
KTUCALLREJ: (0-1)
OKOK

19.33.3 Defined values
Parameter<mode>

Type
NumberDescription
Indicates the rejection configuration:••

0 (factory-programmed value): rejection disabled
1: rejection enabled

19.33.4 Notes
Prefix
001
002
005
006
00755
003YY
007YY
009

Description
KT
LGU+
SKB
SK TelLink
Onse Telecom
Special Category Telecommunications Operator including SB Interactive
Special Category Telecommunications Operator including SB Interactive
Company with no Identification Number

Table 53: Prefixes which force a calling party number to be recognized as an international number

19.34 Request KT OTA opening *KTF*OPENING*KTF*OPENING
Modules
SARA-U270-53S
SyntaxPIN required
Attributes
full
Yes

Settings saved Can be aborted
No
No

Response time
Up to 3 min

Error reference+CMS Error

19.34.1 Description
KT proprietary AT command, which sends a specific SMS message (containing IMSI, ICCID, IMEI, etc.) to initiate
KT's OTA opening procedure.

UBX-13002752 - R67

19 System features

Page 527 of 1001

u-blox cellular modules - AT commands manual

19.34.2 Syntax
Type
Set

SyntaxAT*KTF*OPENING

Response
OK

ExampleAT*KTF*OPENING
OK

19.35 Display the current UMTS environment KTUUMTSENVKTUUMTSENV
Modules
SARA-U270-53S
SyntaxPIN required
Attributes
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

19.35.1 Description
Displays the UMTS environment parameters when available.
If the module is not camped only the "OK" final result code is immediately issued.

19.35.2 Syntax
Type
ActionSyntaxATKTUUMTSENV

Response[KTUUMTSENV: <uarfcn>,<utran_
band>,<psc>,<mcc>,<mnc>,<lac>,<rac>,<ci>,<nom>,<rrc_state>,<drx_cycle_len> <rssi>,<rscp>,<ecio>,<tx_pow>,<ktf_tx_adjust>,<bler>,<mm_service_state>,<mm_
reject_cause>,<gmm_service_state>,<gmm_reject_cause>]

ExampleKTUUMTSENV: 10638,2100,83,222,
1,61325,0,52d2388,2,0,128,-92,-25,5,19,-62,0,5,0,5,0OKOK

19.35.3 Defined values
Parameter<uarfcn><utran_band>

<psc>
<mcc>
<mnc>
<lac>
<rac>
<ci>
<nom>

<rrc_state><drx_cycle_len><rssi><rscp>

UBX-13002752 - R67

Type
NumberNumberDescription
UTRAN Absolute Radio Frequency Channel Number (UARFCN)UTRAN band:

NumberNumberNumberNumberNumberNumberNumber• 900: band VIII
• 2100: band I
Primary Scrambling Code (range 0-511)
Mobile Country Code range (0 - 999)
Mobile Network Code (range 0 - 999)
Location Area Code (range 0 - 65535)
Routing Area Code (range 0 - 65535)
Cell Identity in hexadecimal format (range 0h - FFFFh)
Network Operation Mode:

Number• 1: network mode of operation I• 2: network mode of operation II• 3: network mode of operation III
RRC state:

NumberNumberNumber• 0: CELL DCH• 1: CELL FACH
• 2: CELL PCH• 3: URA PCH• 4: IDLE• 5: IDLE CCCH
DRX cycle length
Received Signal Strength Indication
Received Signal Code Power

19 System features

Page 528 of 1001

u-blox cellular modules - AT commands manual

Parameter<ecio><tx_pow><ktf_tx_adjust>Type
NumberNumberNumber<bler>
Number<mm_service_state> Number<mm_reject_cause> Number<gmm_service_
Numberstate><gmm_reject_cause>

NumberDescription
Signal to noise ratio
Tx power level
KTF_Tx_Adjust = Tx_Pwr + PathLoss -Node-B UL RSSI (-103 dBm) + TX Constant(21.5
dBm)
Block Error Rate (range 1 - 100)
MM service state• 1: no network available• 2: search for network• 3: emergency calls only
• 4: limited service• 5: full service• 6: PLMN list available• 7: disabled
MM reject cause received (see the 3GPP TS 24.008 [12])GMM service state• 1: no network available• 2: search for network• 4: limited service• 5: full service• 7: disabled• 8: detached• 9: no GPRS cell
• 10: suspended
GMM reject cause received (see the 3GPP TS 24.008 [12])19.36 Last gasp configuration +ULGASP+ULGASP
Modules
Attributes

SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SARA-G450-01C
SyntaxPIN required
Settings saved Can be aborted Response time
partialNo
NVM
No< 10 sError reference+CME Error

19.36.1 Description
Enables/disables and configures the last gasp feature. The application is automatically triggered by a properly
configured GPIO (see GPIO Introduction, <gpio_mode>=19). The feature supports the sending of a predefinedlast notification in case of power outage, just before the power goes off. It is assumed that the cellular module
is registered to the network when the alarm is triggered; however the command just configures the feature
so it is possible to issue it also if PIN is not inserted. It is possible to enable/disable the +UULGASP URC to be
notified about the operation result.
This AT command must be issued after a proper configuration of the GPIO via the +UGPIOC command.
Otherwise, if +UGPIOC is issued after +ULGASP, the last gasp will work only after a reboot.
The parameters will be set to the values stored in the NVM in case they are omitted in the set command.

19.36.2 Syntax
Type
Set

SyntaxAT+ULGASP=<GPIO_mode>[,[<text>],[<msg_format>],[<tel_number>],[<profile_id>],[<IP_protocol>],[<IP_addr:PORT>],[<method>],[<max_pow_red>],[<urc_enable>]]UBX-13002752 - R67

Response
OK

ExampleAT+ULGASP=0,"Power_loss",0,"+39347123456",3,6,"192.168.100.20:8080",2,,OK

19 System features

Page 529 of 1001

u-blox cellular modules - AT commands manual

Type
Read

Test

SyntaxAT+ULGASP?

AT+ULGASP=?

Response+ULGASP: <GPIO_mode>,<text>,<msg_format>,<tel_number>,<profile_ID>,<IP_protocol>,<IP_
addr:PORT>,<method>,<max_pow_red>,<urc_enable>

OK

OK+ULGASP: (list of supported <GPIO_ +ULGASP: (0-2),,(0-1),,(0-6),(6,17),,(0mode>'s),,(list of supported <msg_ -3),(0,1),(0,1)
format>'s),,(list of supportedOK<profile_id>'s),(list of supported<IP_protocol>'s),,(list of supported<method>'s),(list of supported<max_pow_red>'s),(list of supported<urc_enable>'s)
OK+UULGASP: <result>,<bearer>

URC

Example+ULGASP: 0,"Power_loss",0,"+39347123456",3,6,"192.168.100.20:8080",2,0,1+UULGASP: 0,1

19.36.3 Defined values
Parameter<GPIO_mode>

Type
Number<text>

String<msg_format>

Number<tel_number>

String<profile_id><IP_protocol>

NumberNumber<IP_addr:PORT>

String<method>

Number<max_pow_red>

Number<urc_enable>

Number<result>

NumberUBX-13002752 - R67

Description
Select the interrupt trigger. Allowed values:• 0 (factory-programmed value): trigger disabled; the following arguments will beignored• 1: falling edge
• 2: rising edge
The string that will be sent upon GPIO movement. Text or binary format can beselected with the <msg_format> parameter. When the text format is selected, amaximum of 160 ASCII characters is allowed. When the binary format is selected,
every 8-bit octet of the message must be written as two IRA character longhexadecimal numbers, e.g. an octet with integer value 42 (i.e. 0x2A) must be written
as a string of two characters "2A" (IRA 50 and 65).
The factory-programmed value is "Last Gasp".
Format of the <text> parameter. Allowed values:• 0 (factory-programmed value): text
• 1: binary
Destination number of the SMS, it is mandatory if <method> is 0 or 2.
Factory-programmed value: empty string.
PSD profile identifier, in range 0-6. See +UPSD AT command.
IP protocol used for socket connection. Allowed values:• 6: TCP• 17 (factory-programmed value): UDP
IPv4 server address with the socket port, it is mandatory if <method> is different
from 0 (SMS sending).
Factory-programmed value: empty string.
Notification method, it is the way the application send out the <text message>; incase of fail of the preferred bearer the second one is used. Allowed values:• 0 (factory-programmed value): send SMS• 1: use IP (TCP or UDP) connection• 2: SMS preferred• 3: IP (TCP or UDP) preferred
Maximum power reduction. Allowed values:• 0 (factory-programmed value): no power reduction• 1: 3 dB power reduction for UMTS bands (3G RAT); 2 dB power reduction for GSM
bands (2G RAT)
Flag determining if the URC is to be issued or not. Allowed values:• 0 (factory-programmed value): disabled• 1: enabled
Operation result. Allowed values:• 0: success• 1: generic fail

19 System features

Page 530 of 1001

u-blox cellular modules - AT commands manual

Parameter<bearer>Type
NumberDescription
Notification used bearer. Allowed values:• 0: SMS• 1: IP (TCP or UDP) connection

19.36.4 Notes
SARA-U2 / LISA-U2 / SARA-G4• The <msg_format> and <text> parameters must be either both specified or both omitted.
• Store in NVM (by means of +UPSDA AT command) the profile defined via +UPSD AT command in orderto enable the message via IP (<method>=1 or 3).

UBX-13002752 - R67

19 System features

Page 531 of 1001

u-blox cellular modules - AT commands manual

20 Power management
20.1 Power saving control (Power SaVing) +UPSV+UPSVModules

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A TOBY-L2 MPCI-L2
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G3 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
ProfileNo+CME Error

Attributes

20.1.1 TOBY-L4 Description
Sets the USB and Ethernet power saving configuration, but it has a global effect on the module power saving
configuration:• If the power saving is disabled (+UPSV: 0), the module remains always in the S0 state.
• If the power saving is enabled (+UPSV: 1), the module enters the S3 state whenever possible after command
defined timeouts. To enter the S3 state the USB interface must be in suspended or disconnected state, theEthernet interface must be in suspended state, too, and air interface must be idle;
After the Ethernet autosuspend timeout since the last Ethernet RX/TX activity, TCP connections are frozen
and the Ethernet interface enters the suspended low power state. To exit this state an Ethernet magic packet
Wake-on-LAN (WoL) shall be explicitly sent by the host side. Else the driver can wake up the Ethernet interface
by ioctl command DWC_ETH_QOS_RUNTIME_RESUME = 63 system call by any application on the module side.
All parameters are optional, thus not modify them, but at least one parameter shall be specified as well when
the command is issued, i.e. AT+UPSV=,, (with an Ethernet PHY interface) or AT+UPSV=, are illegal.
The AT command setting is stored in the NVM and persistent through reboot and power cycles.
Syntax changes may occur if the Ethernet PHY detection changes at the module boot time: if no external
Ethernet PHY is detected (not installed or just not supplied), the <autosuspend> parameter is notapplicable. Dynamic changes after the boot time are not handled.

20.1.2 TOBY-L4 Syntax
Type
Set

SyntaxResponse
AT+UPSV=[<mode>],[<Timeout>][, OK[<autosuspend>]]

Read

AT+UPSV?

Test

AT+UPSV=?

+UPSV: <mode>,<Timeout>,<autosuspend>

ExampleAT+UPSV=1,2000,30000
OK+UPSV: 1,5000,30000

OK
OK+UPSV: (list of supported <mode>s), +UPSV: (0-1),(200-300000),(200-30(list of supported <Timeout>s),(list 0000)
of supported <autosuspend>s)OKOK

20.1.3 TOBY-L4 Defined values
Parameter<mode>

Type
Number<Timeout>

NumberUBX-13002752 - R67

Description
Power saving configuration. Allowed values:• 0: disabled• 1 (default and factory-programmed value): enabled
If <mode>=1 and active mode entered, it provides in milliseconds the guard period forthe system to enter the S3 state after the USB interface entered the suspended or
disconnected state, Ethernet entered the suspended state and air interface is idle.
The parameter is always accepted but significant only when <mode>=1.

20 Power management

Page 532 of 1001

u-blox cellular modules - AT commands manual

ParameterType<autosuspend>

NumberDescription
The range goes from 200 ms to 300000 ms (5 minutes); the default and factoryprogrammed value is 5000 ms.
Provides the guard period in milliseconds for the Ethernet to enter the suspended
state after last RX/TX packet was sent.
The parameter is not applicable if no external Ethernet PHY exists. The parameter isalways accepted but significant only when <mode>=1.
The range goes from 200 ms to 300000 ms (5 minutes); the default and factoryprogrammed value is 30000 ms.

20.1.4 TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 Description
Sets the UART power saving configuration, but it has a global effect on the module power saving configuration:• If the power saving is disabled (+UPSV: 0), the UART interface is always enabled and the module does notenter idle mode
• If the power saving is enabled (+UPSV: 1), the UART interface is cyclically enabled and the module entersidle mode automatically whenever possible• If the power saving is controlled by the UART RTS line (+UPSV: 2), the UART interface is enabled and themodule does not enter idle mode as long as the UART RTS line state is ON• If the power saving is controlled by the UART DTR line (+UPSV: 3), the UART interface is enabled and themodule does not enter idle mode as long as the UART DTR line state is ON

20.1.5 TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 Syntax
Type
Set

SyntaxAT+UPSV=<mode>[,<Timeout>]

Response
OK

ExampleAT+UPSV=1,3000

Read

AT+UPSV?

+UPSV: <mode>[,<Timeout>]

OK+UPSV: 1,3000

Test

AT+UPSV=?

OKOK+UPSV: (list of supported <mode>s), +UPSV: (0-3),(40-65000)(list of supported <Timeout>s)OKOK

20.1.6 TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 Defined values
Parameter<mode>

Type
NumberDescription
Power saving configuration. Allowed values:• 0 (default and factory-programmed value): disabled• 1: enabledo The UART is re-enabled from time to time to allow the DTE to transmit, andthe module switches from idle to active mode in a cyclic way. If during theactive mode any data is received, the UART (and the module) is forced to stay"awake" for a time specified by the <Timeout> parameter. Any subsequent data
reception during the "awake" period resets and restarts the "awake" timer• 2: power saving is controlled by UART RTS line:o If the RTS line state is set to OFF, the power saving mode is allowedo If the RTS line state is set to ON, the module shall exit from power saving mode
<mode>=2 is allowed only if the HW flow control has been previously disabledon the UART interface (e.g. with AT&K0), otherwise the command returns anerror result code (+CME ERROR: operation not allowed if +CMEE is set to 2).

•

UBX-13002752 - R67

With <mode>=2 the DTE can start sending data to the module without risk ofdata loss after having asserted the UART RTS line (RTS line set to ON state).
3: power saving is controlled by UART DTR line:o If the DTR line state is set to OFF, the power saving mode is allowedo If the DTR line state is set to ON, the module shall exit from power saving mode

20 Power management

Page 533 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description<mode>=3 is allowed regardless the flow control setting on the UART
interface. In particular, the HW flow control can be set on UART during thismode.

•<Timeout>

NumberWith <mode>=3 the DTE can start sending data to the module without risk ofdata loss after having asserted the UART DTR line (DTR line set to ON state).
4: reserved.

If <mode>=1 and active mode entered, it provides the guard period of no reception ofcharacters on the UART interface before entering idle mode again. It is expressed in
GSM frames (4.615 ms)• The range goes from 40 to 65000 (approximately from 184 ms to 300 s); the default
value is 2000 GSM frames (ca 9.2 s)• This parameter is accepted only if <mode>=1

20.1.7 Notes•

For a detailed explanation of modules' operating modes, modules and interfaces behavior in reference tothe +UPSV command setting, see the corresponding system integration manual.

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• <mode>= 1, <mode>= 2 and <mode>= 3 are applicable only in reference to the UART interface, even if thecommand is accepted by all the serial interfaces (physical and MUX virtual interfaces). If the command isissued on USB/SPI/MUX channel, all the memory profiles are accordingly updated, but the setting is only
applied to the UART interface.
• <mode>= 2 requires the disabling of the HW flow control only on the UART interface. The other serialinterfaces can request the <mode>=2 for the UART regardless their flow control configuration.
TOBY-L2• If an active, i.e. not suspended, USB connection exists, the module cannot enter power saving.
• In case of <mode>=1, there is no periodic CTS ON/OFF cycle but rather less regular CTS ON/OFF
transitions.
• In case of <mode>=1, the UART interface is disabled after the <Timeout> parameter time, since thecommand result code is issued.
• In case of <mode>=2, the following handling is implemented:
o When RTS line is set to ON state by the DTE, the behavior is the same of <mode>=0.
o When RTS line is set to OFF state by the DTE the CTS line is hold in OFF state, hence DTE to DCE
communication shall be suspended.
• In case of <mode>=3, the following handling is implemented:
o When DTR line is set to ON state by the DTE, the behavior is the same of <mode>=0.
o When DTR line is set to OFF state by the DTE the CTS line is hold in OFF state, hence DTE to DCE
communication shall be suspended.
• The current command setting is automatically stored in NVM after the command issuing and it is not
managed in the memory profile. As a result, if the flow control configuration is not saved in the memory
profile, a wrong power saving behavior can happen at the next boot, in this scenario:o Power saving mode controlled by UART RTS line (<mode>=2) is applied.
o DTE-DCE local flow control set to the default setting (HW flow control), because it was the storedconfiguration (in the memory profile that has been loaded).
o RTS line set to OFF state by the DTE.
In this configuration, the module is not allowed to send any data as long as the RTS line is set to OFF
state, because the flow control "stop" condition forbids it. Therefore, in case <mode>=2 is selected, it
is important to save the flow control configuration via the AT&W command before any module reset or
power-off. The suggested procedure to be performed once is:o Set the "no flow control" configuration (via AT&K0, or AT+IFC=0,0 or AT\Q0 AT commands)o Set the +UPSV <mode>=2
o Save the flow control configuration into the proper RAM profile mirror via the AT&W AT commando Update the stored profile in the NVM via +CPWROFF AT command
At the next boot, the configuration will be consistent.

UBX-13002752 - R67

20 Power management

Page 534 of 1001

u-blox cellular modules - AT commands manual•

For the same reason (+UPSV is not managed as part of the memory profile configuration), thecommands AT&V, AT&W, ATZ and AT&F do not handle the +UPSV command's configuration

TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280• In case of <mode>=1, the UART SW flow control (&K4 &K5 &K6, +IFC=1,1, \Q1) shall not be used.
TOBY-L201 / TOBY-L210-60S• In case <mode>=2 is set, the following handling is implemented:
o When RTS line is set to ON state by the DTE, the behavior is the same of <mode>=0.
o When RTS line is set to OFF state by the DTE the behavior is the same of <mode>=1.
• In case <mode>=3 is set, the following handling is implemented:
o When DTR line is set to ON state by the DTE, the behavior is the same of <mode>=0.
o When DTR line is set to OFF state by the DTE the behavior is the same of <mode>=1.
TOBY-L200-00S / TOBY-L210-00S / MPCI-L2• Since the UART interface is not supported, the command only configures the module power saving andthe <Timeout> parameter has no effect.
• The command behaviour with <mode>=2 and <mode>=3 is the same of <mode>=1 (but the <Timeout>parameter is not accepted).
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• Since these series are equipped with other serial interfaces besides the UART (e.g. USB, SPI), there aresome interactions among the power saving mechanisms implemented by the different interfaces. See
the corresponding module's system integration manual for a detailed description.
For power consumption minimization, a DTE could require to set <mode>=1 or <mode>=2 or <mode>=3(more likely 2 or 3), even if the UART is not used (or even connected). In this condition, the autobauding
should be disabled on the UART interface. Otherwise, the +UPSV setting could be not allowed on theother available AT interfaces (e.g. USB) (an error result code is returned). If the UART interface is notaccessible, the autobauding can be disabled on UART only by change the +IPR configuration from value
0 (autobauding) to a different value on the stored memory profile, that is according with the proceduredescribed in Appendix B.3 applied on the other available AT interfaces (e.g. USB). If this procedure
cannot be performed, the +UPSV <mode>=1 or <mode>=2 or <mode>=3 can be set on other available
AT interfaces on the condition that the module UART has not pending data to send (that is URCs or thegreeting text, since the UART is not used by the DTE). Basically, this can be possible only if the +UPSV
command is issued as the first command after the module boot.
• In case of <mode>=1, the UART interface is immediately disabled after the command result code isissued.
LARA-R211• There is an extended behaviour in case both UART and AUX UART (not supported by
LARA-R211-02B-00, LARA-R211-02B-01 and LARA-R211-02B-02) are configured as AT interfaces (see+USIO AT command).
The command can be issued on either UART or AUX UART interface, and it has a global effect.
o If power saving is disabled (+UPSV: 0), both UART and AUX UART interfaces are always enabled
and the module does not enter idle mode.
o If power saving is enabled (+UPSV: 1), both UART and AUX UART interfaces are cyclically enabled
and the module enters idle mode automatically whenever possible. The enabling is synchronous,
and the interfaces share the same <Timeout> parameter configuration. The description provided
for UART interface is fully applicable to AUX UART interface but with one restriction: during theidle mode sending data via the AUX UART does not wake up the UART and the module.
o If power saving is controlled by the UART RTS line (+UPSV: 2), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART RTS line state is ON.
The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART RTS line
(since AUX UART is not equipped with the RTS line).
o If power saving is controlled by the UART DTR line (+UPSV: 3), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART DTR line state is ON.

UBX-13002752 - R67

20 Power management

Page 535 of 1001

u-blox cellular modules - AT commands manual

The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART DTR line
(since AUX UART is not equipped with the DTR line).
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• There is an extended behaviour in case both UART and AUX UART are configured as AT interfaces (formore details, see +USIO AT command).
The command can be issued on either UART or AUX UART interface, and it has a global effect.
o If power saving is disabled (+UPSV: 0), both UART and AUX UART interfaces are always enabled
and the module does not enter idle mode.
o If power saving is enabled (+UPSV: 1), both UART and AUX UART interfaces are cyclically enabled
and the module enters idle mode automatically whenever possible. The enabling is synchronous,
and the interfaces share the same <Timeout> parameter configuration. The description provided
for UART interface is fully applicable to AUX UART interface but with one restriction: during theidle mode sending data via the AUX UART does not wake up the UART and the module.
o If power saving is controlled by the UART RTS line (+UPSV: 2), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART RTS line state is ON.
The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART RTS line
(since AUX UART is not equipped with the RTS line).
o If power saving is controlled by the UART DTR line (+UPSV: 3), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART DTR line state is ON.
The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART DTR line
(since AUX UART is not equipped with the DTR line).
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S / LISA-U1• <mode>=3 is not supported.
SARA-G4 / SARA-G3• In case of <mode>=1, the UART interface is disabled after the <Timeout> parameter time, since thecommand result code is issued.
• <mode>=3 is not supported.
SARA-G4• The UART autobauding does not work when "wake-up via data reception" feature is enabled; if +IPR:
0, when issuing AT+UPSV=1 or AT+UPSV=2 the module starts working at a fixed baud rate of 115'200
bit/s, regardless of the baud rate previously recognized. So, if the desired baud rate is different from115'200 bit/s, set the baud rate by means of +IPR AT command before setting +UPSV.
SARA-G450-01C• There is an extended behaviour in case both UART and AUX UART are configured as AT interfaces (formore details, see +USIO AT command).
The command can be issued on either UART or AUX UART interface, and it has a global effect.
o If power saving is disabled (+UPSV: 0), both UART and AUX UART interfaces are always enabled
and the module does not enter idle mode.
o If power saving is enabled (+UPSV: 1), both UART and AUX UART interfaces are cyclically enabled
and the module enters idle mode automatically whenever possible. The enabling is synchronous,
and the interfaces share the same <Timeout> parameter configuration. The description provided
for UART interface is fully applicable to AUX UART interface.
o If power saving is controlled by the UART RTS line (+UPSV: 2), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART RTS line state is ON.
The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART RTS line
(since AUX UART is not equipped with the RTS line).
o If power saving is controlled by the UART DTR line (+UPSV: 3), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART DTR line state is ON.
The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART DTR line
(since AUX UART is not equipped with the DTR line).

UBX-13002752 - R67

20 Power management

Page 536 of 1001

u-blox cellular modules - AT commands manual

SARA-G300 / SARA-G310• If a valid reference clock signal is not provided to the EXT32K input pin, the <mode>=1 and <mode>=
2 does not change the power saving configuration of the UART and the module: the UART is always
enabled and the module does not enter idle mode as for <mode>=0.
SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S• If <mode>=2 the CTS line follows the module power saving state if RTS is set to OFF.
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• There is an extended behaviour in case both UART and AUX UART are configured as AT interfaces (formore details, see +USIO AT command).
The command can be issued on either UART or AUX UART interface, and it has a global effect.
o If power saving is disabled (+UPSV: 0), both UART and AUX UART interfaces are always enabled
and the module does not enter idle mode.
o If power saving is enabled (+UPSV: 1), both UART and AUX UART interfaces are cyclically enabled
and the module enters idle mode automatically whenever possible. The enabling is synchronous,
and the interfaces share the same <Timeout> parameter configuration. The description provided
for UART interface is fully applicable to AUX UART interface.
o If power saving is controlled by the UART RTS line (+UPSV: 2), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART RTS line state is ON.
The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART RTS line
(since AUX UART is not equipped with the RTS line).
o If power saving is controlled by the UART DTR line (+UPSV: 3), the UART and AUX UART interfaces
are enabled and the module does not enter idle mode as long as the UART DTR line state is ON.
The description provided for the UART interface is fully applicable to the AUX UART interface,
just keeping in mind that the power saving of both interfaces is controlled by the UART DTR line
(since AUX UART is not equipped with the DTR line).
LEON-G1• In case of <mode>=1, the UART interface is disabled after the <Timeout> parameter time, since thecommand result code is issued.
• If <mode>=2 the CTS line follows the module power saving state if RTS is set to OFF.
• <mode>=3 is not supported.

UBX-13002752 - R67

20 Power management

Page 537 of 1001

u-blox cellular modules - AT commands manual

21 GPIO
21.1 Introduction
The section describes the AT commands used to configure the GPIO pins provided by u-blox cellular modules.

21.1.1 GPIO functions

*
*
*
*
*
*

*
*
*
*
*
*

*

*

*

*

*

*

*

*

*
*
*

*

*
*

*
*
*

*

*

*

*

*

*

*

*

*

9 10 11 12 13 14 15 16 18 19 20 21 22 23 24 25 26 27 28 29 30 32 255
*4
*
*
* * *
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*7 * * *** * * *
*
*

*

*
*

Pad disabled

*
*
*
*
*
*

32.768 kHz output*

DTR mode for power saving control*

External GNSS time stamp of external interrupt*

External GNSS time pulse*

Antenna dynamic tuning*

Hardware flow control (RTS, CTS)*

LwM2M pulse*

Fast and safe power-off*

Time stamp of external interrupt*

Time pulse modem*

Time pulse GNSS*

External GNSS antenna / LNA control*

Last gasp**

Ring indicator

* *
* *
*5 *6
* *
* *

Wi-Fi enable

8

*
*
*
*
*
*
*
*
*
*
*

7
*
*
*
*
*
*
*
*
*
*
*
*

UART (DSR, DTR, DCD and RI) interface

1
*
*
*
*
*
*
*
*
*
*
*
*

SPI serial interface

0
*
*
*
*
*
*
*
*
*
*
*
*

Master clock generation**

I2S digital audio interface**

Module operating mode indication

6

Module status indication

Jamming detection indication

5

GSM Tx burst indication

External GNSS RTC sharing

4

Headset detection

External GNSS data ready3

SIM card detection

External GNSS supply enable

2

Input

TOBY-L4
TOBY-L2
TOBY-L201-02S
LARA-R202
LARA-R203
LARA-R204
LARA-R211
LARA-R220
LARA-R280
TOBY-R2
SARA-U2
SARA-U201-04A /SARA-U201-04B /SARA-U201-04X
LISA-U200-04B /LISA-U201-04B
LISA-U2
LISA-U2 "00"
LISA-U1
SARA-G450-01C
SARA-G450-00C
SARA-G340 /SARA-G350
LEON-G1

Output<gpio_mode>

Network status indication

On u-blox cellular modules, GPIO pins can be opportunely configured as general purpose input or output.
Moreover GPIO pins of u-blox cellular modules can be configured to provide custom functions via +UGPIOC
AT command. The custom functions availability can vary depending on the u-blox cellular modules series andversion: see Table 54 for an overview of the custom functions supported by u-blox cellular modules.

*
*

*

*
*

*
*
*
*
*
*
*

Table 54: GPIO custom functions overview

4

only RI
Not supported by TOBY-R200-02B-00 and TOBY-R202-02B-00
6
Not supported by TOBY-R200-02B-00 and TOBY-R202-02B-00
7
Not supported by SARA-U270-53S, SARA-U270-73S and SARA-U280

5

UBX-13002752 - R67

21 GPIO

Page 538 of 1001

u-blox cellular modules - AT commands manual

The configuration of the GPIO pins (i.e. the setting of the parameters of the +UGPIOC AT command) is savedin the NVM and used at the next power-on.

21.1.2 GPIO mapping
The number of available GPIO pins and their mapping can vary depending on the u-blox cellular modules series
and version. The GPIOs mapping for different u-blox cellular modules is reported in the following tables.
See the corresponding module system integration manual for the functions supported by each GPIO.
21.1.2.1 TOBY-L4 GPIO mapping<gpio_id>11

Pin name
RI

Pin number
11

Factory-programmed function
UART RI

21
22
24
25
60

GPIO1
GPIO2
GPIO3
GPIO4
GPIO5

21
22
24
25
60

Pin disabled
Pin disabled
Pin disabled
Pin disabled
SIM card detection

61
248
247

GPIO6
GPIO7
GPIO8

61
248
247

Pin disabled
Pin disabled
Pin disabled

Remarks
Only pin 11 can be configured for"UART RI line" functionality
Only pin 60 can be configured for"SIM card detection" functionality-

Table 55: TOBY-L4 series GPIO mapping
21.1.2.2 TOBY-L2 GPIO mapping<gpio_id>10

Pin name
DSR

Pin number
10

11

RI

11

12

DCD

12

13

DTR

13

21
22
24
25
50

GPIO1
GPIO2
GPIO3
GPIO4
I2S_WA

21
22
24
25
50

51

I2S_TXD

51

52

I2S_CLK

52

53

I2S_RXD

53

60

GPIO5

60

61

GPIO6

61

Factory-programmed function
UART DSR

Remarks
Only pin 10 can be configured for"UART DSR line" functionality
UART RI
Only pin 11 can be configured for"UART RI line" functionality
UART DCD
Only pin 12 can be configured for"UART DCD line" functionality
UART DTR
Only pin 13 can be configured for"UART DTR line" functionality
Wi-Fi enable
Pin disabled
Pin disabled
General purpose output (low)
I2S word alignment input/output Only pin 50 can be configured for"I2S word alignment input/output"functionality
I2S transmit data output
Only pin 51 can be configured
for "I2S transmit data output"functionality
I2S clock input/output
Only pin 52 can be configured
for "I2S clock input/output"functionality
I2S receive data output
Only pin 53 can be configured
for "I2S receive data input"functionality
SIM card detection
Only pin 60 can be configured for"SIM card detection" functionality
Master clock generation
Only pin 61 can be configured
for "master clock generation"functionality

Table 56: TOBY-L2 series GPIO mapping

UBX-13002752 - R67

21 GPIO

Page 539 of 1001

u-blox cellular modules - AT commands manual

21.1.2.3 TOBY-L201-02S GPIO mapping<gpio_id>
21
22
24
25
50
51
52
53
60

Pin name
GPIO1
GPIO2
GPIO3
GPIO4
I2S_WAI2S_TXDI2S_CLKI2S_RXD
GPIO5

Pin number
21
22
24
25
50
51
52
53
60

Factory-programmed function
Wi-Fi enable
Pin disabled
Pin disabled
General purpose output (low)Pin disabled
Pin disabled
Pin disabled
Pin disabled
SIM card detection

61

GPIO6

61

Pin disabled

Remarks
Only pin 60 can be configured for"SIM card detection" functionality-

Table 57: TOBY-L201-02S series GPIO mapping
21.1.2.4 TOBY-R2 GPIO mapping<gpio_id>21
22

Pin name
GPIO1
GPIO2

Pin number
21
22

24

GPIO3

24

25
50

GPIO4
I2S_WA

25
50

51

I2S_TXD

51

52

I2S_CLK

52

53

I2S_RXD

53

60

GPIO5

60

Factory-programmed function
Pin disabled
External GNSS supply enable

Remarks
If "External GNSS supply enable" isnot supported the pin is by default
set to "Pin disabled"
External GNSS data ready
Only pin 23 can be configured
for "External GNSS data ready"functionality. If "External GNSS
data ready" is not supported the pin
is by default set to "Pin disabled"
General purpose output (low)
I2S word alignment input/output Only pin 50 can be configured for"I2S word alignment input/output"functionality
I2S transmit data output
Only pin 51 can be configured
for "I2S transmit data output"functionality
I2S clock input/output
Only pin 52 can be configured
for "I2S clock input/output"functionality
I2S receive data output
Only pin 53 can be configured
for "I2S receive data input"functionality
SIM card detection
Only pin 60 can be configured for"SIM card detection" functionality

Table 58: TOBY-R2 series GPIO mapping
21.1.2.5 LARA-R2 GPIO mapping<gpio_id>16
23

Pin name
GPIO1
GPIO2

Pin number
16
23

24

GPIO3

24

25
34

GPIO4
I2S_WA

25
34

UBX-13002752 - R67

Factory-programmed function
Pin disabled
External GNSS supply enable

Remarks
If "External GNSS supply enable" isnot supported the pin is by default
set to "Pin disabled"
External GNSS data ready
Only pin 23 can be configured
for "External GNSS data ready"functionality. If "External GNSS
data ready" is not supported the pin
is by default set to "Pin disabled"
General purpose output (low)
I2S word alignment input/output Only pin 34 can be configured for"I2S word alignment input/output"functionality

21 GPIO

Page 540 of 1001

u-blox cellular modules - AT commands manual<gpio_id>35

Pin name
I2S_TXD

Pin number
35

Factory-programmed function
I2S transmit data output

36

I2S_CLK36

I2S clock input/output

37

I2S_RXD

37

I2S receive data output

42

GPIO5

42

SIM card detection

Remarks
Only pin 35 can be configured
for "I2S transmit data output"functionality
Only pin 36 can be configured
for "I2S clock input/output"functionality
Only pin 37 can be configured
for "I2S receive data input"functionality
Only pin 60 can be configured for"SIM card detection" functionality

Table 59: LARA-R2 series GPIO mapping
21.1.2.6 LISA-U2 GPIO mapping<gpio_id>20
21
23

Pin name
GPIO1
GPIO2
GPIO3

Pin number
20
21
23

Factory-programmed function
Pad disabled
External GNSS supply enable
External GNSS data ready

24

GPIO4

24

GNSS RTC sharing

51

GPIO5

51

SIM card detection

39

I2S1_RXD / GPIO639

2nd I2S receive data input

40

I2S1_TXD / GPIO740

2nd I2S transmit data output

53

I2S1_CLK / GPIO853

2nd I2S clock input/output

54

I2S1_WA / GPIO954

2nd I2S word alignment input/
output55

SPI_SCLK / GPIO1055

SPI Serial Clock Input

56

SPI_MOSI / GPIO11

56

SPI Data Line Input

57

SPI_MISO / GPIO1257

SPI Data Line Output

58

SPI_SRDY / GPIO13

58

SPI Slave Ready Output

59

SPI_MRDY / GPIO14

59

SPI Master Ready Input

Remarks

Only pin 23 can be configured for"External GNSS data ready" and"Last gasp" functionalities
Only pin 24 can be configured
for "External GNSS RTC sharing"
functionality
Only pin 51 can be configured for"SIM card detection" functionality
Only pin 39 can be configured
for 2nd "I2S receive data input"functionality
Only pin 40 can be configured for2nd "I2S transmit data output"functionality
Only pin 53 can be configured
for 2nd "I2S clock input/output"functionality
Only pin 54 can be configured for2nd "I2S word alignment input/
output" functionality
Only pin 55 can be configured for"SPI Serial Clock Input" functionality
Only pin 56 can be configured for"SPI Data Line Input" functionality
Only pin 57 can be configured for"SPI Data Line Output" functionality
Only pin 58 can be configured
for "SPI Slave Ready Output"functionality
Only pin 59 can be configured
for "SPI Master Ready Input"functionality

Table 60: LISA-U2 series (except LISA-U200-00S) GPIO mapping
21.1.2.7 LISA-U200-00S GPIO mapping<gpio_id>
20
21
23
24

Pin name
GPIO1
GPIO2
GPIO3
GPIO4

UBX-13002752 - R67

Pin number
20
21
23
24

Factory-programmed function
Pad disabled
Pad disabled
Pad disabled
Pad disabled

21 GPIO

Remarks

Page 541 of 1001

u-blox cellular modules - AT commands manual<gpio_id>51

Pin name
GPIO5

Pin number
51

Factory-programmed function
SIM card detection

39
40
53
54

I2S1_RXD / GPIO6
I2S1_TXD / GPIO7
I2S1_CLK / GPIO8I2S1_WA / GPIO9

39
40
53
54

Pad disabled
Pad disabled
Pad disabled
Pad disabled

Remarks
Only pin 51 can be configured for"SIM card detection" functionality

Table 61: LISA-U200-00S GPIO mapping
21.1.2.8 LISA-U1 GPIO mapping<gpio_id>20
21
23

Pin name
GPIO1
GPIO2
GPIO3

Pin number
20
21
23

Factory-programmed function
Pad disabled
External GNSS supply enable
External GNSS data ready

24

GPIO4

24

External GNSS RTC sharing

51

GPIO5

51

SIM card detection

Remarks

Only pin 23 can be configured for"GNSS data ready" functionality
Only pin 24 can be configured for"GNSS RTC sharing" functionality
Only pin 51 can be configured for"SIM card detection" functionality

Table 62: LISA-U1 series GPIO mapping
21.1.2.9 SARA-U2 GPIO mapping<gpio_id>
16
23
24

Pin name
GPIO1
GPIO2
GPIO3

Pin number
16
23
24

25

GPIO4

25

42

SIM_DET

42

37

I2S_RXD

37

35

I2S_TXD

35

36

I2S_CLK

36

34

I2S_WA

34

Factory-programmed function
Pad disabled
External GNSS supply enable
External GNSS data readyRemarks

Remarks

Only pin 24 can be configured for"GNSS data ready" and "Last gasp"
functionalities
External GNSS RTC sharing
Only pin 25 can be configured for"GNSS RTC sharing" functionality
SIM card detection
Only pin 42 can be configured for"SIM card detection" functionality
I2S receive data input
Only pin 37 can be configured
for "I2S receive data input"functionality
I2S transmit data output
Only pin 35 can be configured
for "I2S transmit data output"functionality
I2S clock input/output
Only pin 36 can be configured
for "I2S clock input/output"functionality
I2S word alignment input/output Only pin 34 can be configured for"I2S word alignment input/output"functionality

Table 63: SARA-U2 GPIO mapping
21.1.2.10 SARA-G450-01C GPIO mapping<gpio_id>
16
23
24

Pin name
GPIO1
GPIO2
GPIO3

Pin number
16
23
24

Factory-programmed function
Pad disabled
External GNSS supply enable
Pad disabled

25

GPIO4

25

Pad disabled

Only pin 24 can be configured for"32.768 kHz output" functionality

Table 64: SARA-G450-01C GPIO mapping

UBX-13002752 - R67

21 GPIO

Page 542 of 1001

u-blox cellular modules - AT commands manual

21.1.2.11 SARA-G450-00C GPIO mapping<gpio_id>
16
23
24

Pin name
GPIO1
GPIO2
GPIO3

Pin number
16
23
24

Factory-programmed function
Pad disabled
Pad disabled
Pad disabled

25

GPIO4

25

Pad disabled

Remarks

Only pin 24 can be configured for"32.768 kHz output" functionality

Table 65: SARA-G450-00C GPIO mapping
21.1.2.12 SARA-G3 GPIO mapping<gpio_id>
16
23
24

Pin name
GPIO1
GPIO2
GPIO3

Pin number
16
23
24

Factory-programmed function
Pad disabled
External GNSS supply enable
External GNSS data ready

25

GPIO4

25

External GNSS RTC sharing

Remarks

Only pin 24 can be configured for"GNSS data ready" functionality
Only pin 25 can be configured for"GNSS RTC sharing" functionality

Table 66: SARA-G350 / SARA-G340 GPIO mapping
21.1.2.13 LEON-G1 GPIO mapping<gpio_id>18

Pin name
HS_DET

Pin number
18

Factory-programmed function
Headset detection

20
21
23

GPIO1
GPIO2
GPIO3

20
21
23

Pad disabled
External GNSS supply enable
External GNSS data ready

24

GPIO4

24

External GNSS RTC sharing

Remarks
Only pin 18 can be configured for"Headset detection" functionality

Only pin 23 can be configured for"GNSS data ready" functionality
Only pin 24 can be configured for"GNSS RTC sharing" functionality

Table 67: LEON-G1 series GPIO mapping
21.1.2.14 Additional notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G340 / SARA-G350 / LEON-G1
The "External GNSS supply enable", "External GNSS data ready" and "External GNSS RTC sharing"
functions can be handled by the +UGPS and the +UGPRF AT commands to manage the u-blox GNSS
receiver connected to the cellular module and the embedded GPS aiding.
LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-04B / LISA-U200-52S / LISA-U200-62S /LISA-U200-83S / LISA-U201 / LISA-U230 / LISA-U260 / LISA-U270
The AT+UGPIOC=xx,255 or AT+UGPIOC=xx,0 or AT+UGPIOC=xx,1 commands (where xx= 55, 56, 57, 58,59) cannot be sent over SPI interface (the "+CME ERROR: GPIO busy" error result code is reported). Thisis because these commands disable the SPI interface.
When the GPIOs 10-14 need to be switched from tristate (<gpio_mode>=255) or GPIO output (<gpio_
mode>=0) or GPIO input (<gpio_mode>=1) to SPI functionality (<gpio_mode>=13), a power cycle (reset) is
required for the changes to take effect.
TOBY-L4 / TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
When SIM card detection functionality is enabled, the status is reported by +CIND AT command.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
Both the SIM hot insertion detection feature (configurable through the +UDCONF=50 AT command where
supported) and the SIM card detection feature must be enabled to allow a correct implementation of thesefeatures.
See the corresponding module system integration manual for the complete overview of all allowed
configurations.

UBX-13002752 - R67

21 GPIO

Page 543 of 1001

u-blox cellular modules - AT commands manual

21.1.3 Network status indication
When a GPIO pin is configured to provide network status indication, its progress depends on the CS network
registration state (see +CREG) and on the module transmission state:• No service: indicates no network coverage or not registered state• Registered home network 2G: indicates registered state on home network in 2G RAT• Registered home network 3G: indicates registered state on home network in 3G RAT• Registered home network NB1 / NB2: indicates registered state on home network in NB1 / NB2• Registered roaming 2G: indicates registered state with visitor 2G network (roaming in 2G RAT)• Registered roaming 3G: indicates registered state with visitor 3G network (roaming in 3G RAT)• Registered roaming NB1 / NB2: indicates registered state with visitor NB1 / NB2 network (roaming in NB1 /NB2)• Data transmission: indicates voice or data call active either in 2G, 3G or 4G RAT• Data transmission roaming: indicates voice or data call active either in 2G, 3G or 4G RAT with visitor network
SARA-U2
If the module is in CG class, the PS network registration state determines the network status indication;otherwise the GPIO pin progress depends on the CS network registration state.
The following figures report the allowed progresses for GPIO pin set as network indication: VH and VL values
are provided in the corresponding module data sheet in the "Generic Digital Interfaces pins" section.
21.1.3.1 No service (no network coverage or not registered)• Continuous Output / Low
Voltage

VH

VL

Time

Figure 4: GPIO pin progress for no service
21.1.3.2 Registered home network 2G• Cyclic Output / High for 100 ms, Output / Low for 2 s
Voltage

VH

VL

Time

2s
100
ms

Figure 5: GPIO pin progress for registered home network 2G
21.1.3.3 Registered home network 3G• Cyclic Output / High for 50 ms, Output / Low for 50 ms, Output / High for 50 ms, Output / Low for 2 s

UBX-13002752 - R67

21 GPIO

Page 544 of 1001

u-blox cellular modules - AT commands manual

Voltage

VH

VL

Time

2s
50
ms

Figure 6: GPIO pin progress for registered home network 3G
21.1.3.4 Registered home network NB1 / NB2• Cyclic Output / High for 100 ms, Output / Low for 30 s
Voltage

VH

VL

Time

30 s
100
ms

Figure 7: GPIO pin progress for registered home network NB1 / NB2
21.1.3.5 Registered roaming 2G• Cyclic Output / High for 100 ms, Output / Low for 100 ms, Output / High for 100 ms, Output / Low for 2 s
Voltage

VH

VL

Time

2s
100 msFigure 8: GPIO pin progress for registered roaming 2G
21.1.3.6 Registered roaming 3G• Cyclic Output / High for 50 ms, Output / Low for 50 ms, Output / High for 50 ms, Output / Low for 100 ms

UBX-13002752 - R67

21 GPIO

Page 545 of 1001

u-blox cellular modules - AT commands manual

Voltage

VH

VL

Time
50
ms

50
ms

Figure 9: GPIO pin progress for registered roaming 3G
21.1.3.7 Registered roaming NB1 / NB2• Cyclic Output / High for 100 ms, Output / Low for 100 ms, Output / High for 100 ms, Output / Low for 30 s
Voltage

VH

VL

Time

30 s
100 msFigure 10: GPIO pin progress for registered roaming NB1 / NB2
21.1.3.8 Data transmission• Continuous Output / High
Voltage

VH

VL

Time

Figure 11: GPIO pin progress for data transmission
21.1.3.9 Data transmission roaming• Cyclic Output / High for 800 ms, Output / Low for 200 ms

UBX-13002752 - R67

21 GPIO

Page 546 of 1001

u-blox cellular modules - AT commands manual

Voltage

VH

Time

VL
800 ms200 msFigure 12: GPIO pin progress for data transmission roaming
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The data transmission roaming is not supported.
TOBY-L2 / LARA-R2 / TOBY-R2
When registered on 4G (LTE) network, the GPIO pin progress is the same as for data transmission (Figure11) because a PDP context/EPS bearer is available.

21.1.4 Module status indication
When a GPIO pin is configured to provide module status indication, its progress depends on the current module
status (power-off mode, i.e. module switched off, versus idle, active or connected mode, i.e. module switchedon):• Output / High, when the module is switched on (any operating mode during module normal operation: idle,
active or connected mode)• Output / Low, when the module is switched off (power-off mode)

21.1.5 Module operating mode indication
When a GPIO pin is configured to provide module operating mode indication, its progress depends on thecurrent module operating mode (the low power idle mode versus active or connected mode):• Output / High, when the module is in active or connected mode
• Output / Low, when the module is in idle mode (that can be reached if the power saving is enabled by the+UPSV AT command)

21.1.6 SARA-G3 Jamming detection
SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S
The jamming detection mode is not supported.
When a GPIO pin is configured to provide the jamming detection functionality, its progress depends on the+UCD configuration. If the jamming detection reporting is not configured by +UCD there is no progress on thejamming detection GPIO pin and it remains in the default state (GPIO output VL).
If the +UCD AT command is opportunely configured to report the jamming detection, the corresponding GPIO
pin has the following output progress:• Jamming ON: GPIO Output / High (VH)
• Jamming OFF: GPIO Output / Low (VL)
VH and VL values are provided in the corresponding module data sheet in the "Generic Digital Interfaces pins"
section.

UBX-13002752 - R67

21 GPIO

Page 547 of 1001

u-blox cellular modules - AT commands manual

21.2 GPIO select configuration command +UGPIOC+UGPIOC
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
NVM
No< 10 s+CME Error

21.2.1 Description
Configures the GPIOs pins as input, output or to handle a custom function. When the GPIOs pins are configured
as output pin, it is possible to set the value.
The test command provides the list of the supported GPIOs, the supported functions and the status of all the
GPIOs.
Not all the GPIO functions can be assigned to each GPIO pin. If the configuration is not allowed, an error
result code will be returned (error result code 1502 - "+CME ERROR: Select GPIO mode error").
The following custom functions cannot be simultaneously configured on 2 GPIOs:• Network status indication• External GNSS supply enable• External GNSS data ready• External GNSS RTC sharing• Jamming detection indication• SIM card detection• Headset detection• GSM Tx burst indication• Module status indication• Module operating mode indication• Ring indicator• Last gasp
• External GNSS antenna / LNA control• Time pulse GNSS
• Time pulse modem• Time stamp of external interrupt• Fast and safe power-off• External GNSS time pulse• External GNSS time stamp of external interrupt• DTR mode for power saving control• 32.768 kHz output
LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-04B / LISA-U200-52S / LISA-U200-62S /LISA-U200-83S / LISA-U201 / LISA-U230 / LISA-U260 / LISA-U270
The AT+UGPIOC=xx,255 or AT+UGPIOC=xx,0 or AT+UGPIOC=xx,1 commands (where xx= 55, 56, 57, 58,59) cannot be sent over the SPI interface (the error result code "+CME ERROR: GPIO busy" is reported).
This is because these commands disable the SPI interface.
For more details regarding the custom functions supported by the u-blox cellular modules and thefactory-programmed settings, see GPIO functions and GPIO mapping.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
To make available the GPIO set as "External GNSS supply enable" mode it is needed to stop supplying
GNSS receiver with the AT+UGPS=0 command.
TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G340 / SARA-G350
The list of the <gpio_id> with the related <gpio_mode> is not provided in the test command.

UBX-13002752 - R67

21 GPIO

Page 548 of 1001

u-blox cellular modules - AT commands manual

21.2.2 Syntax
Type
Set

Read

SyntaxAT+UGPIOC=<gpio_id>,<gpio_
mode>[,<gpio_out_val>\<gpio_in_
pull>]
AT+UGPIOC?

Response
OK

ExampleAT+UGPIOC=20,0,1
OK+UGPIOC:+UGPIOC:<gpio_id>,<gpio_mode>

20,0[<gpio_id>,<gpio_mode>

21,3[....]]

23,255

OK

24,25542,7

Test

AT+UGPIOC=?

+UGPIOC: (list of supported <gpio_id>),(list of supported <gpio_
mode>),(list of supported <gpio_
out_val>\<gpio_in_pull>)

OK+UGPIOC: (20,21,23,24,42),(0-5,7,9,255),(0-2)
OK[<gpio_id1>,<gpio_mode>...
<gpio_idN>,<gpio_mode>]OK

21.2.3 Defined values
Parameter<gpio_id><gpio_mode>

Type
NumberDescription
GPIO pin identifier: pin number

NumberSee the GPIO mapping for the available GPIO pins, their mapping and factoryprogrammed values on different u-blox cellular modules series and product version.
Mode identifier: configured function
See the GPIO functions for custom functions supported by different u-blox cellular
modules series and product version.
Allowed values:• 0: output• 1: input• 2: network status indication• 3: external GNSS supply enable• 4: external GNSS data ready• 5: external GNSS RTC sharing• 6: jamming detection indication• 7: SIM card detection• 8: headset detection• 9: GSM Tx burst indication• 10: module status indication• 11: module operating mode indication• 12: I2S digital audio interface• 13: SPI serial interface• 14: master clock generation• 15: UART (DSR, DTR, DCD e RI) interface• 16: Wi-Fi enable• 18: ring indicator• 19: last gasp
• 20: external GNSS antenna / LNA control enable• 21: time pulse GNSS
• 22: time pulse modem• 23: time stamp of external interrupt• 24: fast and safe power-off

UBX-13002752 - R67

21 GPIO

Page 549 of 1001

u-blox cellular modules - AT commands manual

ParameterType<gpio_out_val>

Number

<gpio_in_pull>NumberDescription• 25: LwM2M pulse• 26: hardware flow control (RTS, CTS)
• 27: antenna dynamic tuning• 28: external GNSS time pulse• 29: external GNSS time stamp of external interrupt• 30: DTR mode for power saving control• 32: 32.768 kHz output• 255: pad disabled
GPIO output value (for output function <gpio_mode>=0 only):• 0 (default value): low• 1: high
GPIO input value (for input function <gpio_mode>=1 only):• 0 (default value): no resistor activated• 1: pull up resistor active• 2: pull down resistor active

21.2.4 Notes
TOBY-L2• I2S_WA, I2S_TXD, I2S_CLK, I2S_RXD pins can be configured as I2S digital interface. If not all these pins
are set in "I2S digital audio interface" mode, the +USPM command attempting to switch the audio pathfrom NULL path mode to I2S mode will return the "+CME ERROR: operation not allowed" error result code.
On the other side, if the audio path is already set as I2S by +USPM command, the +UGPIOC command
trying to reconfigure the GPIO mode on any of the I2S pins, will return the "+CME ERROR: GPIO busy" error
result code. By default the audio path is I2S, to use I2S pins as GPIO, the I2S interface must be disabled
setting the audio path to NULL path mode by command +USPM command.
• GPIO6 pin can be configured as master clock generation. If this pin is not set in "master clock generation"mode, the +UMCLK command attempting to enable the master clock (<mode> parameter not set to 0)
will return the "+CME ERROR: operation not allowed" error result code. On the other side, if the clock
generation is already enabled by AT+UMCLK command, the +UGPIOC command trying to reconfigure the
GPIO mode on GPIO6, will return the "+CME ERROR: GPIO busy" error result code: issue the AT+UMCLK=0
command before the GPIO6 mode reconfiguration.
LARA-R2 / TOBY-R2• <gpio_in_pull>=2 is not supported.
• I2S_WA, I2S_TXD, I2S_CLK, I2S_RXD pins can be configured as I2S digital interface. If not all these pins
are set in "I2S digital audio interface" mode, the +USPM command attempting to switch the audio path
path from NULL path mode to I2S mode will return the "+CME ERROR: operation not allowed" error
result code. On the other side, if the audio path is already set as I2S by +USPM command, the +UGPIOC
command trying to reconfigure the GPIO mode on any of the I2S pins, will return the "+CME ERROR: GPIO
busy" error result code. By default the audio path is I2S, to use I2S pins as GPIO, the I2S interface must
be disabled setting the audio path to NULL path mode by command +USPM command.
SARA-U2• GPIO6 - GPIO9 pins can be configured as I2S digital interface. If not all these pins are set in "I2S digitalaudio interface" mode, the +USPM command attempting to switch the audio path on I2S will return the"+CME ERROR: operation not allowed" error result code. On the other side, if the audio path is already set
as I2S by +USPM command, the +UGPIOC command trying to reconfigure the GPIO mode on any of the
I2S pins, will return the "+CME ERROR: GPIO busy" error result code. By default the audio path is I2S, touse I2S pins as GPIO, the I2S interface must be disabled setting audio path to 'Null' path by command+USPM command.
• <gpio_in_pull> is not supported. It is pulled none by default for input function <gpio_mode>=1.
LISA-U2• GPIO6 - GPIO9 pins can be configured as I2S1 digital interface. If not all these pins are set in "I2S digitalaudio interface" mode, the +USPM command attempting to switch the audio path on I2S1 will return the"+CME ERROR: operation not allowed" error result code. On the other side, if the audio path is already set
as I2S1 by +USPM command, the +UGPIOC command trying to reconfigure the GPIO mode on any the I2S1
pins, will return the "+CME ERROR: GPIO busy" error result code.
• <gpio_in_pull> is not supported. It is pulled none by default for input function <gpio_mode>=1.

UBX-13002752 - R67

21 GPIO

Page 550 of 1001

u-blox cellular modules - AT commands manual

LISA-U1• <gpio_in_pull> is not supported. It is pulled none by default for input function <gpio_mode>=1.
LEON-G1• <gpio_in_pull> is not supported. It is pulled none by default for input function <gpio_mode>=1.
• The read command is not supported.

21.3 GPIO read command +UGPIOR+UGPIOR
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

21.3.1 Description
Reads the current value of the specified GPIO pin, no matter whether it is configured as input or output (seethe +UGPIOC AT command to define the GPIO function). The parameters range is shown in the informationtext response to the test command.

21.3.2 Syntax
Type
Set

SyntaxAT+UGPIOR=<gpio_id>

Test

AT+UGPIOR=?

Response+UGPIOR: <gpio_id>,<gpio_val>

ExampleAT+UGPIOR=20

OK+UGPIOR: 20,0

+UGPIOR: (list of supported <gpio_
id>s)

OK
+UGPIOR: (20, 21)OKOK

21.3.3 Defined values
Parameter<gpio_id><gpio_val>

Type
NumberDescription
GPIO pin identifier: pin number

NumberSee the GPIO mapping for the available GPIO pins, their mapping and factoryprogrammed values on different u-blox cellular modules series and version.
GPIO value. Allowed values are 0 and 1.

21.3.4 Notes•

The set command works only if the <gpio_mode> parameter of the +UGPIOC AT command is set to 0 or 1.

UBX-13002752 - R67

21 GPIO

Page 551 of 1001

u-blox cellular modules - AT commands manual

21.4 GPIO set command +UGPIOW+UGPIOW
Modules

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

Attributes

21.4.1 Description
Sets ("writes") the output of the specified GPIO pin, but only if it is configured in output function (see the+UGPIOC AT command to set the pin as output).

21.4.2 Syntax
Type
Set

SyntaxResponse
AT+UGPIOW=<gpio_id>,<gpio_out_ OK
val>

Test

AT+UGPIOW=?

ExampleAT+UGPIOW=20,1

OK+UGPIOW: (list of supported <gpio_ +UGPIOW: (20, 21),(0-1)id>s),(list of supported <gpio_out_
OKval>s)
OK

21.4.3 Defined values
Parameter<gpio_id><gpio_out_val>

Type
NumberDescription
GPIO pin identifier: pin number

NumberSee the GPIO mapping for the available GPIO pins, their mapping and factoryprogrammed values on different u-blox cellular modules series and version.
GPIO value. Allowed values are 0 and 1.

21.4.4 Notes•

The set command works only if the <gpio_mode> parameter of the +UGPIOC AT command is set to 0.

UBX-13002752 - R67

21 GPIO

Page 552 of 1001

u-blox cellular modules - AT commands manual

22 File System
22.1 File tags
22.1.1 Description
File system commands have the optional <tag> parameter that allows the user to specify a file type when afile system AT command is issued, to inform the system what to do with it. Application specific files must be
saved with the correct type tag, otherwise they are treated as common user files.

*
*
*
*
*
*
*
*
*
*
*
*

"MNO"

"XLWM2M"*"CALLSRV_EXT""AUDIO_EXT"*"GNSS""FOTA_EXT"*"PROFILE""ECALL_EXT"TOBY-L4
TOBY-L2
MPCI-L2
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-60S
MPCI-L200-00S / MPCI-L201 / MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S
LARA-R2
TOBY-R2
SARA-U2
LISA-U2
LISA-U1
SARA-G340 / SARA-G350
SARA-G4
LEON-G1"AUDIO""USER"

Module"FOAT"

The file tag applicability depends on the module series: see Table 68 for the allowed tags supported by theinterested product. An overview about each file tag is provided in Table 69.

***

Table 68: Tag applicabilities to module series
Tag"USER"

Name
User file system

Specification
This is the default type if the <tag> parameter is omitted in file system AT
commands. All generic files can be stored in this manner.
Example: AT+UDWNFILE="foobar",25,"USER" is the same as AT"FOAT"FOAT file system"AUDIO"

Audio parameters"ECALL_EXT"

eCall controller
configurationand custom eCall
prompts+UDWNFILE="foobar",25

This tag is used to specify the file type as a firmware update package. It willplace the firmware update package in the proper file cache to be used later by
the +UFWINSTALL command.
This tag is used to store audio calibration file "audio_gain_calibration<X>.xml"
and "voice<X>.nvm" in the selected profile <X>=0,1. The profile is stored into
NVM by using ATZ<X>.
The "audio_gain_calibration<X>.xml" and "voice<X>.nvm" files can be overwritten with AT&W<X> command.
This tag is used to read, download and delete the eCall controller configuration(see the eCall implementation in u-blox cellular modules application note [180])or download and delete custom eCall prompts (see the eCall Prompts section).
Reading and downloading commands use a dedicated channel of the USB CDCACM interface.
To download the eCall controller configuration or custom eCall prompts in themodule, use the +UDWNFILE command.
To read the eCall controller configuration from the module, use the +URDFILE
command.

UBX-13002752 - R67

22 File System

Page 553 of 1001

u-blox cellular modules - AT commands manual

Tag

Name

"FOTA_EXT"

Firmware for FOTA
procedure
Audio configuration"AUDIO_EXT"

Specification
To delete eCall controller configuration or custom eCall prompts from themodule, use the +UDELFILE command.
This tag has to be used to store the firmware file for the FOTA procedure using
a dedicated channel of the USB CDC-ACM interface.
This tag is used to read or download audio configuration (see Audio parameters
tuning section). The audio configuration file includes the NVM settings of thefollowing AT commands (where applicable):• +CLVL AT command• +CRSL AT command• +UI2S AT command• +UMAFE AT command• +USAFE AT command• +UMSEL AT command• +UMGC AT command• +USGC AT command• +USPM AT command• +UTI AT command
To download the audio configuration in the module, use the +UDWNFILE
command.

"PROFILE""GNSS""CALLSRV_EXT"

To read configuration from the module, use the +URDFILE command.
This tag refers to the profile files that can be loaded on to the module tosupport Mobile Network Operators (MNOs) specific configurations. For moredetails on the profiles, see the +UMNOPROF command. The +URDFILE and+ULSTFILE AT commands are not allowed with this tag, the user can only
download or delete these files.
GNSS files
This tag has to be used to store the firmware file for the internal GNSS receiver.
Emergency Call
This tag is used to manage the Emergency Call Number List (ECNL) file stored
Number List (ECNL) in NVM. All numbers in the list will be treated as emergency numbers whenmanagement
dialled and will result in disabling the thermal daemon software shut-down.
Some notes about ECNL:• If eCall is enabled, the ECNL list is not used and call is treated as any normal
call.
• Conflict manager will not manage these calls, meaning no ongoing calls will
be dropped.
• Maximum allowed numbers in the ECNL list is 20. Numbers after 20 will beignored.
• Reboot is required to reload the ECNL list after download.
Profile files

File should be composed by text lines consisting of 'type','number' lines that end
with carriage return where 'type' is a type of the number in 'number' according
to one of the formats supported by 3GPP TS 24.008 [12] sub-clause 10.5.4.7).
All numbers that start with '00' should be stored with '+' instead in order tokeep only one occurrence for international number. In order to manage numbers
properly the configuration file should contain the number with international
prefix and without it.
Example of a two line ECNL file:2,+390123456789"XLWM2M""MNO"

UBX-13002752 - R67

2,390123456789

LwM2M object script This tag is used to read or store Lua files defining a LwM2M object for
files
use by the LwM2M client. The file specified with the "XLWM2M" can be
only downloaded completely (see +UDWNFILE AT command), deleted(see +UDELFILE AT command), fully or partially read (see +URDFILE or+URDBLOCK) and queried (see +ULSTFILE AT command).
ICCID and MCC/MNC This tag refers to the files containing the ICCID and MCC/MNC MNO lists used
MNO listsby the SIM ICCID/IMSI selection (see the +UMNOPROF AT command). The
file specified with the "MNO" tag can be downloaded to the module (see the+UDWNFILE AT command), deleted (see the +UDELFILE AT command), fully or
partially read (see the +URDFILE or +URDBLOCK AT commands) and queried(see the +ULSTFILE AT command). Depending on the file name (<filename>)

22 File System

Page 554 of 1001

u-blox cellular modules - AT commands manual

Tag

Name

Specification
the file contains the ICCID and MCC/MNC MNO lists. The allowed file names
are:• "iccid_list": SIM Issuer Identifier Number (IIN) list. The list format is:
MNO1%iccid1%iccid2%MNO2%iccid3%iccid4...%MNOn%iccidm. By
factory-programmed configuration no iccid_list file is stored in the module
file system.
• "mno_list":
MCC
and
MNC
list.
The
list
format:
MNO1%mcc1mnc1%mcc2mnc2%MNO2%mcc3mnc3...%MNOn%mcckmnck.
By factory-programmed configuration the following mno_list file is stored in
the module file system:

ATT%310150%310170%310410%310560%311180%310030%310280%310950%313100%312670%313110%313120%313130%313140%313790%VZW%310890%311480%311270%310010%310012%310013%310590%310890%310910%311110%311270%311271%311272%311273%311274%311275%311276%311277%311278%311279%311280%311281%311282%311283%311284%311285%311286%311287%311288%311289%311390%311480%311481%311482%311483%311484%311485%311486%311487%311488%311489

Allowed MNO1,..., MNOn values for both iccid_list and mno_list files are:
• ATT: AT&T
• VZW: Verizon
The maximum entries number in the MCC/MNC list and ICCID list is 126 and thefile overall maximum size is 1024 bytes.

Table 69: Tag meanings
TOBY-L4
The <tag> parameter is mandatory.

22.2 Download file +UDWNFILE+UDWNFILE
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

22.2.1 Description
Stores (writes) a file into the file system:• The stream of bytes can be entered after the '>' prompt has been provided to the user. The file transfer isterminated exactly when <size> bytes have been entered and either "OK" final result code or an error result
code is returned. The feed process cannot be interrupted i.e. the command mode is re-entered once theuser has provided the declared the number of bytes.
• If the file already exists, the data will be appended to the file already stored in the file system.
• If the data transfer stops, after 20 s the command is stopped and the "+CME ERROR: FFS TIMEOUT" error
result code (if +CMEE=2) is returned.
• If the module shuts down during the file storing, all bytes of the file will be deleted.
• If an error occurs during the file writing, the transfer is aborted and it is up to the user to delete the file.
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
The available free memory space is checked before starting the file transfer. If the file size exceeds theavailable space, the "+CME ERROR: NOT ENOUGH FREE SPACE" error result code will be provided (if+CMEE: 2).

UBX-13002752 - R67

22 File System

Page 555 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
If the HW flow control is disabled (AT&K0), a data loss could be experienced. So the HW flow control usage
is strongly recommended.
TOBY-L4
The '>' prompt after which the stream of bytes can be entered will be provided to the user on a dedicatedchannel of the USB CDC-ACM interface.
If the command is issued on the AT interface over an IP connection, the DTE will send the binary data over
the TCP connection to the DCE.
The DTE monitors the TCP data port for the binary data transfer (for more details on the TCP/IP
port configuration, see the <tcp_data_port> parameter of the +UIFCONF AT command). After theestablishment of the TCP connection from the DTE to the specific port, the DTE will start the file transfer.
The '>' prompt is not provided to the user on the AT interface over an IP connection. The DCE will closethe connection when the specific amount of data is received, or an error result code occurs. Once the ATcommand is issued, the DCE will listen on the specific port and will close it after the timeout expiration(20 s). The DCE will close the TCP connection, if no data are received for 30 s.

22.2.2 Syntax
Type
Set

SyntaxResponse
AT+UDWNFILE=<filename>,<size>[, OK<tag>]><text>

ExampleAT+UDWNFILE="filename",36,"USER">The 36 downloaded bytes of the file!
OK

Download audio configuration
Set
AT+UDWNFILE=<filename>,<size>, OK"AUDIO_EXT"

AT+UDWNFILE="audioconfig",4873,"AUDIO_EXT"
OK

22.2.3 Defined values
Parameter<filename><size>Type
StringNumber<tag>

String<text>

StringDescription
File name. For file system file name and data size limits see File system limits.
File size expressed in bytes. For file system file name and data size limits see Filesystem limits.
Optional parameter that specifies the application file type. FILE TAGS table lists theallowed <tag> strings. For more details on specific limitations, see Notes.
Stream of bytes.

22.2.4 Notes••

Issue the AT+ULSTFILE=1 command to retrieve the available user space in the file system.
Two files with different types can have the same name, i.e. AT+UDWNFILE="testfile",20,"USER" and AT+UDWNFILE="testfile",43,"AUDIO".

TOBY-L4• The supported tags are "FOTA_EXT", "AUDIO_EXT", "CALLSRV_EXT" and "ECALL_EXT".
• "FOTA_EXT" tag:o The string set with the <filename> parameter is ignored.
o The command is used to store the firmware file to be used for the FW installation procedure.
• "AUDIO_EXT" tag:o The tag is used to download the audio configuration file (audioconf file).
o Current active audio configuration can be obtained using the +URDFILE AT command.
o After successful download, the audio configuration is validated. If it is not valid, the configuration
is not applied and the downloaded file is deleted.
o After successful application, the module needs to be restarted to activate the configuration.
o The downloaded file is deleted after the processing is done.
• "CALLSRV_EXT" tag:

UBX-13002752 - R67

22 File System

Page 556 of 1001

u-blox cellular modules - AT commands manual•o The string set with the <filename> parameter is ignored.
o The command is used to store the ECNL(Emergency Call Number List) file to be used for dialed
numbers treated as emergency calls.
"ECALL_EXT" tag:o The tag is used to download the eCall controller configuration or the eCall prompts. For more details
on downloading the eCall prompts, see the eCall Prompts section.

TOBY-L2 / MPCI-L2• If the file already exists, the file will be overwritten.
• The special filename "update.zip" is used for the FW update file. The usage of this filename will write
the file to a different FS partition where it cannot be retrieved by file system AT commands. Do not use"update.zip" for any user data.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 / LEON-G1• The <tag> parameter is not supported.
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S• If the file already exists, the file will be overwritten.
LISA-U1• The <tag> parameter is not supported.
• If the file already exists, the file will be overwritten.
• If the module shuts down during the file storing, all the bytes successfully sent to the module will be
stored.

22.3 List files information +ULSTFILE+ULSTFILE
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

22.3.1 Description
Retrieves some information about the FS. Depending on the specified <op_code>, it can print:•••

List of files stored into the FS
Remaining free FS space expressed in bytes
Size of the specified file expressed in bytes
The available free space on FS in bytes reported by the command AT+ULSTFILE=1 is the theoretical freespace including the space occupied by the hidden and temporary files which are not displayed by the AT+ULSTFILE=0.

22.3.2 TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G3 / LEON-G1 syntax
Type
SyntaxGeneric syntax
Set
AT+ULSTFILE=[<op_code>[,<param1>[,<param2>]]]

Response

Example+ULSTFILE: [<param3>,...[,<paramN>]]
OK

List of files stored into the FS
Set
AT+ULSTFILE=[0[,<tag>]]+ULSTFILE: [<filename1>[,<filename2>[,...[,<filenameN>]]]]OK

UBX-13002752 - R67

AT+ULSTFILE=+ULSTFILE: "filename1","filename2"
OK

22 File System

Page 557 of 1001

u-blox cellular modules - AT commands manualType

SyntaxRemaining free FS space expressed in bytes
Set
AT+ULSTFILE=1[,<tag>]

Response
See notes below

Example+ULSTFILE: <free_fs_space>

AT+ULSTFILE=1

OK+ULSTFILE: 236800

See notes below

OK
Size of the specified fileSet
AT+ULSTFILE=2,<filename>[,<tag>]+ULSTFILE: <file_size>

AT+ULSTFILE=2,"filename"OK+ULSTFILE: 784
OK

22.3.3 Defined values
Parameter<op_code>Type
Number<tag><filename1>,..,<filenameN><free_fs_space><file_size><param1>

StringStringNumberNumberNumber /StringNumber /String<param2>

Description
Allowed values are:• 0 (default value): lists the files belonging to <tag> file type
• 1: gets the free space for the specific <tag> file type
• 2: gets the file size expressed in bytes, belonging to <tag> type (if specified)
Specifies the application file type. FILE TAGS table lists the allowed <tag> strings.
File name. For file system file name and data size limits see File system limits.
Available free space on FS in bytes.
Size of the file specified with the <filename> parameter.
Type and supported content depend on related <op_code> (details are given above).
Type and supported content depend on related <op_code> (details are given above).

22.3.4 Notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The <tag> parameter is not supported.

22.4 Read file +URDFILE+URDFILE
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

22.4.1 Description
Retrieves a file from the file system.
TOBY-L4
The stream of file bytes will be provided to the user on a dedicated channel of the USB CDC-ACM interface.
If the command is issued on the AT interface over an IP connection, the DCE will send the binary data over
the TCP connection to the DTE.
The DTE monitors the TCP data port for the binary data transfer (for more details on the TCP/IP
port configuration, see the <tcp_data_port> parameter of the +UIFCONF AT command). After theestablishment of the TCP connection from the DTE to the specific port, the DCE starts the file transfer.
The '>' prompt is not provided to the user on the AT interface over an IP connection. The DCE will close theconnection when the specific amount of data is transmitted, or an error result code occurs. Once the AT

UBX-13002752 - R67

22 File System

Page 558 of 1001

u-blox cellular modules - AT commands manualcommand is issued, the DCE will listen on the specific port and will close it after the timeout expiration(20 s). The DCE will close the TCP connection, if no data are received for 30 s.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
During the command execution, if the DTE stops reading any data from the module (using flow control
mechanisms) for 5 s or more, the command could be aborted by the module, and an error result code isreturned. In case the DTE is not able to sustain the data flow and to avoid the HW flow control intervention
for long time, the use of the +URDBLOCK AT command is recommended.

22.4.2 Syntax
Type
Set

Syntax
AT+URDFILE=<filename>[,<tag>]

Response+URDFILE: <filename>,<size>,<data>OK

ExampleAT+URDFILE="filename"+URDFILE: "filename",36,"thesebytes are the data of the file"OK

22.4.3 Defined values
Parameter<filename>
<tag>

Type
StringString<size><data>

NumberStringDescription
File name. For file system file name and data size limits, see File system limits.
The optional parameter <tag> specifies a different application file type. FILE TAGS
table lists the allowed <tag> strings.
File size, in bytes.
File content.

22.4.4 Notes•

The returned file data is displayed as an ASCII string of <size> characters in the range [0x00,0xFF]. At
the end of the string, <CR><LF> are provided for user convenience and visualization purposes.

TOBY-L4• The <tag> parameter is mandatory.
• The syntax of the information text response to the set command is +URDFILE: <size>. Then the user
should start receiving <size> bytes of file data on a dedicated channel of the USB CDC-ACM interface. At
the completion the OK final result code is displayed.
• The supported tags are "AUDIO_EXT", "CALLSRV_EXT" and "ECALL_EXT".
• "AUDIO_EXT" tag:o It is used to read the audio configuration file by setting the <filename> parameter to "audioconfig".
• "CALLSRV_EXT" tag:o The string set with the <filename> parameter is ignored.
o The command is used to read the ECNL(Emergency Call Number List) from file in NVM.
• "ECALL_EXT" tag:o It is used to read the eCall controller configuration file by setting the <filename> parameter to"ecallconfig". For more details, see the eCall implementation in u-blox cellular modules applicationnote [180].
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3• The <tag> parameter is not supported.
LEON-G1• The <tag> parameter is not supported.
• The filename is not enclosed within double quotes.

UBX-13002752 - R67

22 File System

Page 559 of 1001

u-blox cellular modules - AT commands manual

22.5 Partial read file +URDBLOCK+URDBLOCK
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

22.5.1 Description
Retrieves a file from the file system.
Differently from +URDFILE command, this command allows the user to read only a portion of the file,
indicating the offset and amount of bytes.

22.5.2 Syntax
Type
Set

Syntax
AT+URDBLOCK=<filename>,<offset>,<size>[,<tag>]

Response+URDBLOCK: <filename>,<size>,<data>OK

ExampleAT+URDBLOCK="filename",0,20+URDBLOCK: "filename",20,"thesebytes are the "OK

22.5.3 Defined values
Parameter<filename><offset><size><data><tag>

Type
StringNumberNumberStringStringDescription
File name. For file system file name and data size limits see File system limits.
Offset in bytes from the beginning of the file.
Number of bytes to be read starting from the <offset>.
Content of the file read.
The optional parameter <tag> specifies a different application file type. FILE TAGS
table lists the allowed <tag> strings.

22.5.4 Notes•••

The returned file data is displayed as an ASCII string of <length> characters in the range [0x00,0xFF]. At
the end of the string, <CR><LF> are provided for user convenience and visualization purposes.
In case a size larger than the whole file size is required the command returns the file size only, indicating
the amount of bytes read.
In case an offset larger than the whole file size is required, the "+CME ERROR: FFS file range" error result
code is triggered.

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The <tag> parameter is not supported.
SARA-G4 / SARA-G3 / LEON-G1• The <tag> parameter is not supported.
• The <filename> is not enclosed in double quotes in the information text response of the set command.

22.6 Delete file +UDELFILE+UDELFILE
Modules

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A

UBX-13002752 - R67

22 File System

Page 560 of 1001

u-blox cellular modules - AT commands manual+UDELFILE
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

Attributes

22.6.1 Description
Deletes a stored file from the file system.
If <filename> file is not stored in the file system the following error result code will be provided: "+CME
ERROR: FILE NOT FOUND".

22.6.2 Syntax
Type
Set

SyntaxResponse
AT+UDELFILE=<filename>[,<tag>] OK

ExampleAT+UDELFILE="filename","USER"
OK

22.6.3 Defined values
Parameter<filename>
<tag>

Type
StringStringDescription
File name. For file system file name and data size limits see File system limits.
The optional parameter <tag> specifies a different application file type. FILE TAGS
table lists the allowed <tag> strings.

22.6.4 Notes
TOBY-L4• The <tag> parameter is mandatory.
• The supported tags are "FOTA_EXT", "CALLSRV_EXT" and "ECALL_EXT".
• "FOTA_EXT" tag:o The string set with the <filename> parameter is ignored.
o The currently stored firmware file used for FW installation procedure will be deleted.
• "CALLSRV_EXT" tag:o The string set with the <filename> parameter is ignored.
o The command is used to delete the ECNL(Emergency Call Number List) file stored in NVM.
• "ECALL_EXT" tag:o The tag is used to delete the eCall controller configuration or the eCall prompts. For more details ondeleting the eCall prompts, see the eCall Prompts section.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The <tag> parameter is not supported.
SARA-G4 / SARA-G3 / LEON-G1• The <tag> parameter is not supported.
• The command immediately returns the "OK" final result code but the actual erasing is completed inbackground, and the freed space is not immediately available.

22.7 File system limits
22.7.1 Allowed characters in filenames
A filename cannot contain the following characters: / * : % | " < > ?

UBX-13002752 - R67

22 File System

Page 561 of 1001

u-blox cellular modules - AT commands manual

22.7.2 Limits
Here below are listed the maximum file name length, the maximum data size of the file system and the
maximum number of files for the u-blox cellular modules.
Maximum file name length:• LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - 47 characters• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200 / LISA-U201 - 248 characters
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S
MPCI-L210-60S / MPCI-L210-63S
The file system AT commands are not supported.

/

MPCI-L200-00S/

MPCI-L210-00S/

SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S
The maximum file name length is 47 characters.
TOBY-L4
The <filename> parameter is ignored.
Maximum file size:• TOBY-L4 / TOBY-L2 / MPCI-L2 / SARA-U260 / SARA-U270 / SARA-U280 - 5242880 bytes• LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S /LISA-U200-83S / LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270- 5242880 bytes• SARA-U201 - 19808256 bytes• LISA-U200-04B / LISA-U201-04B - 19562496 bytes• LARA-R2 / TOBY-R2 - File size limited by the available file system space retrieved by +ULSTFILE=1
command• LISA-U1 - 1458176 bytes• SARA-G4 - 315904 bytes• SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X - 692532 bytes• SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S / LEON-G1 - 1048575 bytes
Maximum number of files:• TOBY-L4 - The maximum number of files that can be stored is 1.
• TOBY-L2 / MPCI-L2 - The theoretical maximum number of files that can be stored is 1714.
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U1 - The theoretical maximum number of files that can be stored is1100.
• LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S /LISA-U200-83S / LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 The theoretical maximum number of files that can be stored is 1100.
• LISA-U200-04B / LISA-U201-04B - The theoretical maximum number of files that can be stored is 9263.
• SARA-G340 / SARA-G350 / LEON-G1 - The theoretical maximum number of files that can be stored is 135.
• SARA-G4 - The theoretical maximum number of files that can be stored is 617.
The theoretical maximum file size and the maximum number of files also includes system, hidden andtemporary files whose number is not statically predictable, so the actual numbers can be less than stated.

UBX-13002752 - R67

22 File System

Page 562 of 1001

u-blox cellular modules - AT commands manual

23 Audio interface
This section describes a set of u-blox proprietary AT commands to be used for the audio features configuration:•••+USPM command sets the audio path
+UI2S command configures I2S interfaces+UPAR, +USAR, +UPLAYFILE, +URECFILE, +USTOPFILE, +UAPLAY, +UAREC, +UTGN, +URNG, +UMSM
commands manage players• +UMCLK, +UEXTDCONF manage the external codec or other external audio IC• +UDCONF=30 configures allowed speech codecs• +UDCONF=33 sets volume or disables waiting call tone
• +UMAAT command checks the external hardware audio path
Audio parameters tuning section describes commands for the audio parameters tuning.
eCall section describes commands specific for eCall.
DTMF section describes commands specific for DTMF detection and generation.
Other standard commands available for audio configuration are listed as follows: +CALM, +CRSL, +CLVL,+CMUT, +VTD, +VTS, +UVTS.
The <silent> parameter in +CALA command refers to the alarm tone.

23.1 Audio path mode setting +USPM+USPM
Modules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R204 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

23.1.1 Description
Sets the audio path mode enabling the different audio paths (audio uplink and downlink) of the module fordifferent use cases. For example, the uplink path can be switched from the handset microphone to the headset
microphone and the downlink path can be switched from the handset earpiece to the loudspeaker.
Besides the routing via analog or digital interface, the uplink and downlink paths are characterized by a set ofaudio parameters (gains, digital filters, echo canceller parameters). The uplink paths and downlink paths canbe configured through the set of commands described in the Audio parameters tuning section.
The command is used to choose the uplink and downlink path used.
Only one single uplink path and one single downlink path can be used. Parallel paths are not managed.

23.1.2 TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G3 / LEON-G1 syntax
Type
Set

Read

Test

SyntaxResponse
ExampleAT+USPM=<main_uplink>,<main_ OK
AT+USPM=1,1,0,0
downlink>,<alert_sound>,<headset_
OK
indication>[,<vmic_ctrl>]
AT+USPM?
+USPM: <main_uplink>,<main_+USPM: 0,0,0,0,2
downlink>,<alert_sound>,<headset_
OK
indication>,<vmic_ctrl>
AT+USPM=?

UBX-13002752 - R67

OK+USPM: (list of supported <main_
uplink>s),(list of supported <main_

23 Audio interface+USPM: (0-9,255),(0-9,255),(0),(0),(2)

Page 563 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
downlink>s),(list of supported<alert_sound>s),(list of supported<headset_indication>s),(list of
supported <vmic_ctrl>s)

ExampleOKOK

23.1.3 TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G3 / LEON-G1 defined values
Parameter<main_uplink>

Type
Number<main_downlink>

Number<alert_sound>Number<headset_
indication>

Number<vmic_ctrl>

NumberDescription
Specifies the audio input path used for speech. See Notes for the allowed and default
values.
Specifies the audio output path used for speech. See Notes for the allowed anddefault values.
Specifies whether the alert sounds in idle mode are played on the main downlink
path (same downlink path as speech; see <main_downlink> parameter) or on the
loudspeaker:• 0: main downlink path
• 1: loudspeaker
See Notes for the allowed and default values.
Specifies if the speech path is switched on the headset or not when the headset isinserted:• 0: the headset plug insertion is not indicated to the module; thus the module does
not change automatically the speech audio path and leaves it as specified in <main_
uplink>, <main_downlink> parameters• 1: the headset plug insertion is indicated to the module and thus the module
automatically switches the speech audio path to headset mode (headset
microphone for uplink and headset earpiece for downlink). The indication is carriedby the rising edge of HS_DET signal, thus HS_DET pin should be connected tothe audio headset connector. For more details about this connection, see thecorresponding System Integration Manual. When the headset plug is removed, an
opposite falling edge will be generated and the module will automatically switch
back to the main audio path (<main_uplink>, <main_downlink>).
See Notes for allowed and default values.
Specifies the control mode for microphones voltage supply (VMIC).
• 0: VMIC is synchronously switched on/off with the microphone amplifier; i.e. while
the module is idle or is using the I2S input line, the microphone amplifiers and VMIC
are switched off• 1: VMIC is switched always on• 2: VMIC is switched always off
See Notes for allowed and default values.

23.1.4 TOBY-L4 syntax
Type
Set

SyntaxAT+USPM=<audio_path>,<profile_type>

Response
OK

Read

AT+USPM?

+USPM: <audio_path>,<profile_
type>

Test

OK
+USPM: (list of supported <audio_path>s),(list of supported <profile_type>s)AT+USPM=?

ExampleAT+USPM=1,1
OK+USPM: 0,0
OK+USPM: (0-1),(0-4)
OKOK

23.1.5 TOBY-L4 defined values
Parameter<audio_path>

UBX-13002752 - R67

Type
NumberDescription
Specifies the audio path.

23 Audio interface

Page 564 of 1001

u-blox cellular modules - AT commands manual

ParameterType<profile_type>

NumberDescription
See Notes for allowed and default values.
Specifies the profile for selected audio path.
See Notes for allowed and default values.

23.1.6 Notes
TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.
• Allowed and default values for parameters:o <audio_path>:- 0 (factory-programmed value): analog audio path
- 1: digital audio patho <profile_type>:- 0 (factory-programmed value): headset profile- 1: handsfree profile- 2: flat profile- 3: custom 0 profile- 4: custom 1 profile• The audio path should not be changed from analog to digital and vice versa during an active call as
it will result in unpredictable behaviour.
• When audio path mode is changed, the following configurations are applied:o configuration for I2S (if using digital audio path see +UI2S for details, if analog - configuration ispredefined)o configuration for microphone analog and digital gains (for details see +UMAFE)o configuration for speaker analog and digital gains (for details see +USAFE)o configuration for the active microphone for the analog audio path (for details see +UMSEL)
o configuration for the digital gain scal_i2s_in of the i2s port (for details see +UMGC)
o configuration for the digital gain scal_i2s_out of the i2s port (for details see +USGC)o configuration for uplink voice muting is unmuted (for details see +CMUT)• Flat profile has all audio path processing blocks disabled.
• Custom profiles are available for customer customization.
TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S• Allowed and default values for parameters:o <main_uplink>- 0: uplink path 0 via I2S- 1 (factory-programmed value): uplink path 1 via I2S- 2: uplink path 2 via I2S- 3: uplink path 3 via I2S- 4: uplink path 4 via I2S- 255: null path; no audio interface is enabledo <main_downlink>- 0: downlink path 0 via I2S- 1 (factory-programmed value): downlink path 1 via I2S- 2: downlink path 2 via I2S- 3: downlink path 3 via I2S- 4: downlink path 4 via I2S- 255: null path; no audio interface is enabledo <alert_sound>- 0 (factory-programmed value): main downlink patho <headset_indication>- 0 (factory-programmed value): not consideredo <vmic_ctrl>

UBX-13002752 - R67

23 Audio interface

Page 565 of 1001

u-blox cellular modules - AT commands manual•••- 2 (default value): VMIC is switched always off
The <main_uplink> path 255 can be combined only with the <main_downlink> path 255. This is the
NULL path mode. When selected, audio is disabled and I2S pins can be reconfigured. Parameters <alert_sound>, <headset_indication> and <vmic_ctrl> are not considered in this mode.
The <main_uplink> paths from 0 to 4 can be combined only with the <main_downlink> path with the sameindex (I2S is used).
The I2S pins are the GPIO pins (GPIO6-GPIO9). If not all these pins are set in "I2S digital audio interface"mode (see the AT+UGPIOC command, <gpio_mode>=12), the +USPM command attempting to switch
the audio path from NULL mode to I2S mode will return a "+CME ERROR: operation not allowed" error
result code. On the other side, if the audio path is already set as I2S by the +USPM command, the+UGPIOC command trying to reconfigure the GPIO mode on any I2S pin will return a "+CME ERROR: GPIO
busy" error result code. To configure GPIO6-GPIO9 in any mode other than "I2S digital audio interface",
the +USPM command must previously switch the audio path in NULL path mode (<main_uplink>=255,<main_downlink>=255).

TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03A /TOBY-L280-03S• Allowed and default values for parameters:o <main_uplink>- 0: handset profile via I2S path
- 1 (factory-programmed value): hands-free profile via I2S path
- 2: headset (with earpiece and microphone) profile via I2S path
- 3: headset(with external microphone) profile via I2S path
- 4: car hands-free profile via I2S path
- 255: null path; no audio interface is enabled
For profile tuning, see TOBY-L2 series Audio Application Note [181]o <main_downlink>- 0: handset profile via I2S path
- 1 (factory-programmed value): hands-free profile via I2S path
- 2: headset (with earpiece and microphone) profile via I2S path
- 3: headset(with external microphone) profile via I2S path
- 4: car hands-free profile via I2S path
- 255: null path; no audio interface is enabled
For profile tuning, see TOBY-L2 series Audio Application Note [181]o <alert_sound>- 0 (factory-programmed value): main downlink patho <headset_indication>- 0 (factory-programmed value): not consideredo <vmic_ctrl>- 2 (default value): VMIC is switched always off• <main_uplink>=4
and<main_downlink>=4
arenot
supportedby
TOBY-L200-03S-00,
TOBY-L210-03S-00, TOBY-L210-03A-00 and TOBY-L280-03S-00.
• The <main_uplink> path 255 can be combined only with the <main_downlink> path 255. This is the
NULL path mode. When selected, audio is disabled and I2S pins can be reconfigured. Parameters <alert_sound>, <headset_indication> and <vmic_ctrl> are not considered in this mode.
• The <main_uplink> paths from 0 to 4 can be combined only with the <main_downlink> path with the sameindex (I2S is used).
• The I2S pins are the GPIO pins (GPIO6-GPIO9). If not all these pins are set in "I2S digital audio interface"mode (see the AT+UGPIOC command, <gpio_mode>=12), the +USPM command attempting to switch
the audio path from NULL mode to I2S mode will return a "+CME ERROR: operation not allowed" error
result code. On the other side, if the audio path is already set as I2S by the +USPM command, the+UGPIOC command trying to reconfigure the GPIO mode on any I2S pin will return a "+CME ERROR: GPIO
busy" error result code. To configure GPIO6-GPIO9 in any mode other than "I2S digital audio interface",
the +USPM command must previously switch the audio path in NULL path mode (<main_uplink>=255,<main_downlink>=255).

UBX-13002752 - R67

23 Audio interface

Page 566 of 1001

u-blox cellular modules - AT commands manual

LARA-R2 / TOBY-R2 / SARA-U2• Allowed and default values for parameters:o <main_uplink>- 0: uplink path 0 via I2S- 1 (default value): uplink path 1 via I2S- 2: uplink path 2 via I2S- 3: uplink path 3 via I2S- 4: uplink path 4 via I2S- 255: null path; no audio interface is enabledo <main_downlink>- 0: downlink path 0 via I2S- 1 (default value): downlink path 1 via I2S- 2: downlink path 2 via I2S- 3: downlink path 3 via I2S- 4: downlink path 4 via I2S- 255: null path; no audio interface is enabledo <alert_sound>- 0 (default value): main downlink patho <headset_indication>- 0 (default value): not consideredo <vmic_ctrl>- 2 (default value): VMIC is switched always off• The uplink path 255 (null path) can be combined only with the <main_downlink> path 255. This is
the NULL path mode. In this audio path mode, no audio path is ever enabled and the I2S pin can bereconfigured. Parameters <alert_sound>, <headset_indication and <vmic_ctrl> are not considered in thismode.
• For I2S profile settings, it is recommended to set same index 0 to 4 for <main_uplink> and <main_
downlink> (<main_uplink> = <main_downlink>). Other combinations are deprecated.
• The profile 4 is reserved for hands-free application. The factory-programmed settings are suitable forhands-free devices. For this profile tuning, see the SARA-U2 Audio Interface Application Note [184].
• The I2S pins are the GPIO pins (GPIO6-GPIO9). If not all these pins are set in "I2S digital audio interface"mode (see the AT+UGPIOC command, <gpio_mode>=12), the +USPM command attempting to switch theaudio path from NULL mode to I2S mode will return a "+CME ERROR: operation not allowed" error result
code. On the other side, if the audio path is already set as I2S by the +USPM command, the +UGPIOC
command trying to reconfigure the GPIO mode on any I2S pin will return a "+CME ERROR: GPIO busy" error
result code. To configure GPIO6-GPIO9 in any mode other than "I2S digital audio interface", the +USPM
command must have been previously used to switch the audio path in NULL path mode (<main_uplink>=
255, <main_downlink>=255).
LISA-U2• Allowed and default values for parameters:o <main_uplink>- 0: uplink path 0 via I2S- 1 (default value): uplink path 1 via I2S- 2: uplink path 2 via I2S- 3: uplink path 3 via I2S- 4: uplink path 4 via I2S- 5: uplink path 5 via I2S1
- 6: uplink path 6 via I2S1
- 7: uplink path 7 via I2S1
- 8: uplink path 8 via I2S1
- 9: uplink path 9 via I2S1
o <main_downlink>- 0: downlink path 0 via I2S- 1 (default value): downlink path 1 via I2S

UBX-13002752 - R67

23 Audio interface

Page 567 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•
•

- 2: downlink path 2 via I2S- 3: downlink path 3 via I2S- 4: downlink path 4 via I2S- 5: downlink path 5 via I2S1
- 6: downlink path 6 via I2S1
- 7: downlink path 7 via I2S1
- 8: downlink path 8 via I2S1
- 9: downlink path 9 via I2S1
o <alert_sound>- 0 (default value): alert sounds are played on main downlink patho <headset_indication>- 0 (default value): headset indication is not consideredo <vmic_ctrl>- 2 (default value): VMIC is switched always off
For I2S profile settings, it is recommended to set same index 0 to 4 for <main_uplink> and <main_
downlink> (<main_uplink> = <main_downlink>). Other combinations are deprecated.
The <main_uplink> paths from 0 to 4 can be combined with the <main_downlink> paths from 0 to 4 (I2S
is used).
The <main_uplink> paths from 5 to 9 can be combined with the <main_downlink> paths from 5 to 9 (I2S1
is used).
The profile 4 is reserved for hands-free application. The factory-programmed settings are suitable forhands-free devices. For this profile tuning, see the LISA-U2 Audio Interface Application Note [183].
The I2S1 pins are the GPIO pins (GPIO6-GPIO9). If not all these pins are set to "I2S digital audio interface"mode (see the AT+UGPIOC command, <gpio_mode>=12), the command attempting to switch the audio
path on I2S1 will return a "+CME ERROR: operation not allowed" error result code. On the other side, if theaudio path is already set to I2S1 by the +USPM command, the +UGPIOC command trying to reconfigure
the GPIO mode on any I2S1 pin will return a "+CME ERROR: GPIO busy" error result code.

LISA-U1• Allowed and default values for parameters:o <main_uplink>- 0: (pins MIC_P, MIC_N)- 1 (default value): headset microphone (pins: MIC_P, MIC_N)- 2: I2S input line (pin I2S_RXD)- 4: hands-free microphone (pins: MIC_P, MIC_N)o <main_downlink>- 0: normal earpiece (pins: SPK_N, SPK_P)- 1 (default value): mono headset (pins: SPK_N, SPK_P)- 3: loudspeaker (pins: SPK_N, SPK_P)- 4: I2S output line (pin I2S_TXD)
o <alert_sound>- 0 (default value): alert sounds are played on the main downlink patho <headset_indication>- 0 (default value): headset indication is not consideredo <vmic_ctrl>- 2 (default value): VMIC is switched always off• The following table summarizes the allowed combination of parameters <main_uplink> and <main_
downlink> (<alert_sound>, <headset_indication> must always be set to 0):
Uplink\Downlink
0 - Handset
1 - Headset
2 - I2S input
3 - Unused
4 - Hands-free mic

UBX-13002752 - R67

0 - Earpiecexx

1 - Mono headsetxx

2 - Unused

3 - Loudspeakerxx

2

4 - I S outputxxx

23 Audio interface

xPage 568 of 1001

u-blox cellular modules - AT commands manual

SARA-G340 / SARA-G350• Allowed and default values for parameters:o <main_uplink>- 0 (default value): handset microphone (pins: MIC_P, MIC_N, MIC_BIAS, MIC_GND)- 1: headset microphone (pins: MIC_P, MIC_N, MIC_BIAS, MIC_GND)- 2: I2S input line (pin I2S_RXD)- 4: hands-free microphone (pins: MIC_P, MIC_N, MIC_BIAS, MIC_GND)o <main_downlink>- 0 (default value): normal earpiece (pins: SPK_N, SPK_P)- 1: mono headset (pins: SPK_N, SPK_P)- 3: loudspeaker (pins: SPK_N, SPK_P)- 4: I2S output line (pin I2S_TXD)
o <alert_sound>- 0 (default value): alert sounds are played on the main downlink patho <headset_indication>- 0 (default value): headset indication is not consideredo <vmic_ctrl>- 0 (default value): VMIC is switched on/off• The following table summarizes the allowed combination of parameters <main_uplink> and <main_
downlink> (<alert_sound>, <headset_indication> must always be set to 0):
Uplink\Downlink
0 - Handset
1 - Headset
2 - I2S input
3 - Unused
4 - Hands-free mic

0 - Earpiecexx

1 - Mono headsetxx

2 - Unused

3 - Loudspeakerxx

2

4 - I S output

x
x

x

x

LEON-G1• Allowed and default values for parameters:o <main_uplink>- 0 (default value): handset microphone (pins: MIC_BIAS1, MIC_GND1)- 1: headset microphone (pins: MIC_BIAS2, MIC_GND2)- 2: I2S input line (pin I2S_RXD)o <main_downlink>- 0 (default value): normal earpiece (pins: HS_P, GND)
- 1: mono headset (pins: HS_P, GND)
- 3: loudspeaker (pins: SPK_P, SPK_N)- 4: I2S output line (pin I2S_TXD)
o <alert_sound>- 0: alert sounds are played on the main downlink path
- 1 (default value): alert sounds are played on loudspeakero <headset_indication>- 0: headset indication is not considered- 1 (default value): headset indication is consideredo <vmic_ctrl>- 0 (default value): VMIC is switched on/off- 1: VMIC is always on- 2: VMIC is always off• The following table summarizes the allowed combination of parameters <main_uplink>, <main_
downlink>, <alert_sound>, <headset_indication>:
Allowed values
0, 0, 0, 1
0, 0, 1, 1
0, 0, 0, 0

UBX-13002752 - R67

UplinkHandsetHandsetHandset

Downlink
Earpiece
Earpiece
Earpiece

23 Audio interface

Alert onMain path
Loudspeaker
Main path

Headset indication
Considered
Considered
Not considered

Page 569 of 1001

u-blox cellular modules - AT commands manual

Allowed values
0, 0, 1, 0
0, 3, 0, 0
0, 3, 0, 1
0, 1, 0, 0
1, 1, 0, 0
1, 0, 0, 0
1, 0, 1, 0
1, 3, 0, 0
2, 4, 0, 0

UplinkHandsetHandsetHandsetHandsetHandsetHandsetHandsetHandsetI2S input

Downlink
Earpiece
Loudspeaker
Loudspeaker
Mono headset
Mono headset
Earpiece
Earpiece
Loudspeaker
I2S output

Alert onLoudspeaker
Main path
Main path
Main path
Main path
Main path
Loudspeaker
Main path
Main path

Headset indication
Not considered
Considered
Not considered
Not considered
Not considered
Not considered
Not considered
Not considered
Not considered2

23.2 I S digital interface mode +UI2S+UI2SModules

Attributes

TOBY-L4 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

23.2.1 Description

Configures the I2S digital audio interface to be used when digital audio paths are chosen (see the +USPM
command description, <main_uplink>=I2S RX, <main_downlink>=I2S TX).
The I2S TX and RX data lines can be connected to two different access points of the uplink and downlink audio
path (see the module audio block diagram in the Audio parameters tuning introduction).
The digital audio interface is I2S.
The I2S interface can be configured either in Master or in Slave mode through the <I2S_Master_Slave>parameter:• In Master mode, the module generates the WA (word alignment) and CLK (clock) signals• In Slave mode, the remote device must generate the WA (word alignment) and CLK (clock) signals
The sample rate of transmitted and received words is configurable through the <I2S_sample_rate> parameter.
Furthermore synchronization between data, clock and word alignment lines can be configured in different
modes through the <I2S_mode> parameter:• PCM modes (short synchronization signal)• Normal I2S modes (long synchronization signal)
For details about I2S technical features in PCM and Normal I2S mode, see the system integration manual forthe corresponding module.
The physical I2S port is composed of 4 pins. The signals are:
• I2S_WA (Word Alignment): output signal in Master mode, input signal in Slave mode; it synchronizes thedata word; the WA cycle frequency is <I2S_sample_rate>, while WA cycle timing depends on the mode (seePCM modes, PCM modes timing diagrams, Normal I2S modes and Normal I2S modes timing diagrams)• I2S_TXD (Transmitted Data): output signal; sequence of data bits, most significant bit transmitted first.
Each word is 16 bits long, in 2's complement format with the configured I2S sample rate
• I2S_CLK (Clock): output signal in Master mode, input signal in Slave mode; it synchronizes the bits
composing the data words; CLK frequency and edge synchronization with TXD/RXD signals depends on<I2S_mode> and the configured I2S sample rate. See PCM modes and Normal I2S modes• I2S_RXD (Received Data): input signal; sequence of data bits, most significant bit read first. Each word is
16 bits long, in 2's complement format with the configured I2S sample rate
The I2S pins are mapped in the following way:

UBX-13002752 - R67

23 Audio interface

Page 570 of 1001

u-blox cellular modules - AT commands manual

Product
TOBY-L4
TOBY-L2
TOBY-R2
LARA-R2
LISA-U2 (first interface)
LISA-U2 (second interface)
LISA-U1
SARA-U2
SARA-G3
LEON-G1

I2S_WA
50
50
50
34
41
54 (pin: I2S1_WA)
41
34
34
26

I2S_TXD
51
51
51
35
42
40 (pin: I2S1_TXD)
42
35
35
27

I2S_CLK
52
52
52
36
43
53 (pin: I2S1_CLK)
43
36
36
28

I2S_RXD
53
53
53
37
44
39 (pin: I2S1_RXD)
44
37
37
29

2

Table 70: I S pins mapping on u-blox cellular modules

23.2.2 Syntax
Type
Set

Read

SyntaxResponse
AT+UI2S=<I2S_mode>,<I2S_port>, OK<I2S_clk_wa>[,<I2S_sample_rate>[,<I2S_Master_Slave>]]
AT+UI2S?
+UI2S: <I2S_mode>,<I2S_port>,<I2S_clk_wa>,<I2S_sample_rate>,<I2S_Master_Slave>[...]

ExampleAT+UI2S=10,1,1,5,1
OK+UI2S: 4,1,1,4,1+UI2S: 10,3,1,5,0OK(for all the I2S interfaces)
Test

AT+UI2S=?

OK+UI2S: (list of supported <I2S_
mode>s),(list of supported <I2S_
port>s),(list of supported <I2S_
clk_wa>)[,(list of supported <I2S_
sample_rate>),(list of supported<I2S_Master_Slave>)]+UI2S: (0-13),(1,3),(0-1),(0-8),(0-1)
OKOK

23.2.3 Defined values
Parameter<I2S_mode>

Type
Number<I2S_port>

NumberDescription
Specifies I2S configurable modes: PCM modes (short synchronization signal) andnormal I2S modes (long synchronization signal) are available. The allowed values are(0-13, 20-23) as described in PCM modes, Normal I2S modes:• See PCM modes, Normal I2S modes for modes available on each connection pointand for their settings• See the PCM modes timing diagrams and Normal I2S modes timing diagrams forthe signals timing
Specifies the I2S physical port (I2S or I2S1) and its connection in the internal audio
processing path (I2Sx or I2Sy connection points) when the digital path is selected
as audio path (see the AT+USPM command). I2S connections points positions are
showed in the audio paths block diagram in Audio parameters tuning introduction.
The allowed values are:
• 1: I2S is connected to I2Sx connection point• 2: I2S is connected to I2Sy connection point• 3: I2S1 is connected to I2Sx connection point• 4: I2S1 is connected to I2Sy connection point
I2Sx connection point is parallel to the analog audio front end. In this case thedigital audio path is comparable with the analog audio paths (see the AT+USPM
command)
I2Sy connection point is nearer to the codec in the audio path. While using
this access point the audio path is not affected by some audio controls as
digital filters (+UUBF, +UDBF), digital gains (+UMGC, +USGC), sidetone (+USTN);
furthermore some audio resources as tone generator (+UTGN), info tones (e.g.

UBX-13002752 - R67

23 Audio interface

Page 571 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description
free tone, connection tone, low battery alarm), players (ringer on incoming call,alarm and tunes generated by +UPAR command) are not available on the I2Sy
connection point
Volume control (+CLVL) and hands-free algorithm (+UHFP) are active for bothconnection points.

<I2S_clk_wa>

Number<I2S_sample_rate>

Number<I2S_Master_Slave> Number

The analog gains in the +USGC and +UMGC commands are unused for bothconnection points.
Specifies when CLK and WA signals are active. The allowed values are:
• 0: dynamic mode. CLK and WA outputs are active and only running when the audio
path is active (audio samples are read on RX line and written on TX line). After theaudio path is disabled (i.e. a call is hang up), CLK and WA are disabled too• 1: continuous mode. CLK and WA outputs are always active and running if the+USPM current setting implies the <I2S_port> usage, even when the module is idle
and the audio path is disabled (no audio data written on TX line, no audio data readon RX line). This implies the module cannot enter power saving mode
I2S sample rate (frame rate). This is the frequency of the word set and received by the
I2S interface. The words are synchronized by the WA (word alignment) signal. Thus
the <I2S_sample_rate> parameter matches with the frequency of WA signal. The
allowed values are:
• 0: 8 kHz sampling rate
• 1: 11.025 kHz sampling rate
• 2: 12 kHz sampling rate
• 3: 16 kHz sampling rate
• 4: 22.05 kHz sampling rate
• 5: 24 kHz sampling rate
• 6: 32 kHz sampling rate
• 7: 44.1 kHz sampling rate
• 8: 48 kHz sampling rate
• 9: 96 kHz sampling rate
• 10: 192 kHz sampling rate
Indicates the Master/Slave mode of I2S interface. The allowed values are:
• 0: Master mode. CLK, WA, TX are output signals generated by the module. RX is an
input signal• 1: Slave mode. Only TX signal is an output signal generated by the module. CLK, WA,
RX are input signals and must be generated by the remote device.

23.2.4 Notes
TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.
• <I2S_mode>=20, 21, 22 and 23 are not supported.
• <I2S_port>=2, 3 and 4 are not supported.
• <I2S_clk_wa>=1 is not supported.
• Table 71 describes the allowed combinations of <I2S_mode> and <I2S_port>
I2Sx connection of I2S
I2Sy connection of I2SI2Sx connection of I2S1
I2Sy connection of I2S1

PCM modes(0-1)
Not supported
Not supported
Not supported

2

Normal I S modes(2-13)
Not supported
Not supported
Not supported

2

•

•

Table 71: I S modes
If an incorrect number of parameters is provided, if the parameter value is out of range, or if the digitalprofile is not active, the error result code "+CME ERROR: operation not supported" will be provided if+CMEE is set to 2:
o Changing the I2S settings during voice activity is not recommended.
The default values are as follows:o I2S: <I2S_mode>=0, <I2S_port>=1, <I2S_clk_wa>=0, <I2S_sample_rate>=0, <I2S_Master_Slave>=0

UBX-13002752 - R67

23 Audio interface

Page 572 of 1001

u-blox cellular modules - AT commands manual••

The settings are stored in NVM and are part of audio configuration which can be downloaded to target
using +UDWNFILE and read from target using +URDFILE.
The command settings are applied at the module boot, after the command execution and when the profile
is changed to digital one with +USPM AT command.

TOBY-L2• <I2S_mode>=0, 1, 10, 11, 12 and 13 are not supported.
• <I2S_port>=2 and 4 are not supported.
• Table 72 describes the allowed combinations of <I2S_mode> and <I2S_port><I2S_port>
I2Sx connection of I2S
I2Sy connection of I2SI2Sx connection of I2S1
I2Sy connection of I2S1

PCM modes(20-23)
Not supported
Not supported
Not supported

2

Normal I S modes(2-9)
Not supported
Not supported
Not supported

2

•

•
•

•

Table 72: I S modes<I2S_sample_rate>=1, 2, 4, 5, 6, 7, 8, 9 and 10 are not supported (only the 8 and 16 kHz sampling rates
are supported). <I2S_sample_rate>=0 is supported only on the audio path 4 (see the <main_uplink> and<main_downlink> parameters in +USPM AT command)<I2S_Master_Slave>=1 (slave mode) is not supported.
If an incorrect number of parameters is provided or the parameter value is out of range, the error result
code "+CME ERROR: operation not supported" will be provided if +CMEE is set to 2:
o Changing the I2S settings during voice activity is not recommended. Reboot the module (+CFUN=16)
after having changed I2S settings.
o The command returns an error result code if I2S pins are already allocated by another resource
The factory-programmed values are as follows:o I2S: <I2S_mode>=21, <I2S_port>=1, <I2S_clk_wa>=0, <I2S_sample_rate>=3, <I2S_Master_Slave>=0

LARA-R2 / TOBY-R2 / SARA-U2• <I2S_mode>=20, 21, 22 and 23 are not supported.
• <I2S_port>=2, 3 and 4 are not supported.
• <I2S_sample_rate>=9 and 10 are not supported• Table 73 describes the allowed combinations of <I2S_mode> and <I2S_port>
I2Sx connection of I2S
I2Sy connection of I2SI2Sx connection of I2S1
I2Sy connection of I2S1

PCM modes(0-1)
Not supported
Not supported
Not supported

2

Normal I S modes(2-13)
Not supported
Not supported
Not supported

2

•

•

Table 73: I S modes
If an incorrect number of parameters is provided or the parameter value is out of range, the error result
code "+CME ERROR: operation not supported" will be provided if +CMEE is set to 2:
o The command returns an error result code when the audio path is in digital mode. This is because
the I2S settings cannot be changed when the audio path is configured to use this interface. It isnecessary to disable the digital audio path switching the audio path to NULL path mode (see the+USPM AT command), configure the I2S interface, and then re-select the digital path (see the+USPM AT command).
o The command returns an error result code if I2S pins are already allocated by another resource
The factory-programmed values are as follows:o <I2S_mode>=1, <I2S_port>=1, <I2S_clk_wa>=0, <I2S_sample_rate>=3, <I2S_Master_Slave>=0

LISA-U2• A second digital audio interface (I2S1) is also available.
• <I2S_mode>=20, 21, 22 and 23 are not supported.
• <I2S_port>=2 and 4 are not supported.
• <I2S_sample_rate>=9 and 10 are not supported

UBX-13002752 - R67

23 Audio interface

Page 573 of 1001

u-blox cellular modules - AT commands manual•

Table 74 describes the allowed combinations of <I2S_mode> and <I2S_port><I2S_port>
I2Sx connection of I2S
I2Sy connection of I2SI2Sx connection of I2S1
I2Sy connection of I2S1

PCM modes(0-1)
Not supported(0-1)
Not supported

2

Normal I S modes(2-13)
Not supported(2-13)
Not supported

2

•

•

Table 74: I S modes
If an incorrect number of parameters is provided or the parameter value is out of range, the error result
code "+CME ERROR: operation not supported" will be provided if +CMEE is set to 2:
o The command returns an error result code when the <I2S_port> specified is used by the current
audio path (<I2S_port>=3; +USPM: 8,7,0,0). The I2S settings cannot be changed when the audio
path is configured to use this interface. It is necessary to change the audio path by the +USPM AT
command to a configuration not using the <I2S_port>, configure the <I2S_port> by +UI2S, and thenre-select the +USPM mode using the <I2S_port> specified.
o The command returns an error result code if I2S pins are already allocated by another resource
The factory-programmed values are as follows:o I2S: <I2S_mode>=1, <I2S_port>=1, <I2S_clk_wa>=0, <I2S_sample_rate>=3, <I2S_Master_Slave>=0o I2S1: <I2S_mode>=1, <I2S_port>=3, <I2S_clk_wa>=0, <I2S_sample_rate>=3, <I2S_Master_Slave>=
0

LISA-U1• <I2S_mode>=20, 21, 22 and 23 are not supported.
• <I2S_port>=2, 3 and 4 are not supported.
• <I2S_sample_rate>=9 and 10 are not supported• Table 75 describes the allowed combinations of <I2S_mode> and <I2S_port>
I2Sx connection of I2S
I2Sy connection of I2SI2Sx connection of I2S1
I2Sy connection of I2S1

PCM modes(0-1)
Not supported
Not supported
Not supported

2

Normal I S modes(2-13)
Not supported
Not supported
Not supported

2

•

•

Table 75: I S modes
If an incorrect number of parameters is provided or the parameter value is out of range, the error result
code "+CME ERROR: operation not supported" will be provided if +CMEE is set to 2:
o The command returns an error result code when the audio path is in digital mode (+USPM: 2,4,0,0).
This is because the I2S settings cannot be changed when the audio path is configured to use thisinterface. It is necessary to disable the digital audio path switching to analog path (e.g.: by command
AT+USPM=0,0,0,0; see the +USPM AT command), configure the I2S interface, and then re-selectthe digital path by command AT+USPM=2,4,0,0 (see the +USPM AT command).
o The command returns an error result code if I2S pins are already allocated by another resource
The factory-programmed values are as follows:o <I2S_mode>=0, <I2S_port>=1, <I2S_clk_wa>=0, <I2S_sample_rate>=0, <I2S_Master_Slave>=0

SARA-G340 / SARA-G350• <I2S_mode>=20, 21, 22 and 23 are not supported.
• The <I2S_sample_rate> and <I2S_Master_Slave> parameters are not supported.
• <I2S_port>=2, 3 and 4 are not supported.
• Table 76 describes the allowed combinations of <I2S_mode> and <I2S_port>
I2Sx connection of I2S
I2Sy connection of I2SI2Sx connection of I2S1
I2Sy connection of I2S1

PCM modes(0-1)
Not supported
Not supported
Not supported

2

Normal I S modes(2-13)
Not supported
Not supported
Not supported

2•

Table 76: I S modes<I2S_Master_Slave>=1 (slave mode) is not supported.

UBX-13002752 - R67

23 Audio interface

Page 574 of 1001

u-blox cellular modules - AT commands manual••

If an incorrect number of parameters is provided or the parameter value is out of range, the error result
code "+CME ERROR: operation not supported" will be provided if +CMEE is set to 2:
o The command returns an error result code when the audio path is in digital mode (+USPM: 2,4,0,0).
This is because the I2S settings cannot be changed when the audio path is configured to use thisinterface. It is necessary to disable the digital audio path switching to analog path (e.g.: by command
AT+USPM=0,0,0,0; see the +USPM AT command), configure the I2S interface, and then re-selectthe digital path by command AT+USPM=2,4,0,0 (see the +USPM AT command).
o The command returns an error result code if I2S pins are already allocated by another resource
The factory-programmed values are as follows:o <I2S_mode>=1, <I2S_port>=1, <I2S_clk_wa>=0

LEON-G1• <I2S_mode>=20, 21, 22 and 23 are not supported.
• <I2S_port>=3 and 4 are not supported.
• Table 77 describes the allowed combinations of <I2S_mode> and <I2S_port>
PCM modes(0-1)
Not supported
Not supported
Not supported

I2Sx connection of I2S
I2Sy connection of I2SI2Sx connection of I2S1
I2Sy connection of I2S1

2

Normal I S modes
Not supported(2-13)
Not supported
Not supported

2

•
•
•

•

Table 77: I S modes
The <I2S_sample_rate> and <I2S_Master_Slave> parameters are not supported.
<I2S_Master_Slave>=1 (slave mode) is not supported.
If an incorrect number of parameters is provided or the parameter value is out of range, the error result
code "+CME ERROR: operation not supported" will be provided if +CMEE is set to 2:
o The command returns an error result code when the audio path is in digital mode (+USPM: 2,4,0,0).
This is because the I2S settings cannot be changed when the audio path is configured to use thisinterface. It is necessary to disable the digital audio path switching to analog path (e.g.: by command
AT+USPM=0,0,0,0; see the +USPM AT command), configure the I2S interface, and then re-selectthe digital path by command AT+USPM=2,4,0,0 (see the +USPM AT command)o The command returns an error result code if I2S pins are already allocated by another resource
The factory-programmed values are as follows:o <I2S_mode>=4, <I2S_port>=2, <I2S_clk_wa>=1

23.2.5 PCM modes (short synchronization signal)
Mode
0

CLK EDGE for TX
RISING

CLK EDGE for RX
FALLINGWA pulse length
2 clks1

RISINGFALLING

1 clk

20

RISINGFALLING

2 clks21

RISINGFALLING

1 clk

22

FALLINGRISING

2 clks23

FALLINGRISING

1 clk

UBX-13002752 - R67

23 Audio interface

CLK frequency
18*<I2S_sample_
rate>
17*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_rate>

WA frequency<I2S_sample_rate><I2S_sample_rate><I2S_sample_rate><I2S_sample_rate><I2S_sample_rate><I2S_sample_rate>

Page 575 of 1001

u-blox cellular modules - AT commands manual

23.2.6 PCM modes timing diagrams
WA (PCM mode 0): pulse is 2 bits wide; 18 clocks / WA cycle

TXD (PCM mode 0): After synchronization bit (0), MSB is transmitted twice and Word is aligned on WA falling edge

WA (PCM mode 1): pulse is 1 bits wide; 17 clocks / WA cycle

TXD (PCM mode 1): After synchronization bit (0), word is aligned on WA falling edge

WA (PCM mode 20): pulse is 2 bits wide; 32 clocks / WA cycle

TXD (PCM mode 20): After synchronization bit (0), word is aligned on WA falling edge

WA (PCM mode 21): pulse is 1 bits wide; 32 clocks / WA cycle

TXD (PCM mode 21): After synchronization bit (0), word is aligned on WA falling edge

A single transmitted word is marked in grey. MSB is marked darker.
Since RXD bits are read on the falling edge of CLK signal, the RXD word slot starts half bit delayed respect TXD
word slot.
Relation between WA and CLK edge for PCM mode is:

UBX-13002752 - R67

23 Audio interface

Page 576 of 1001

u-blox cellular modules - AT commands manual

WA

CLK

2

23.2.7 Normal I S modes (long synchronization signal)
23.2.7.1 TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
Mode CLK edge for CLK edge for MSB delay TX channel
TX
RX
2
FALLINGRISING
1 bit
WA LOWRX channel CLK frequency

WA frequency

WA LOW

3

RISINGFALLING

1 bit

WA LOW

WA LOW

4

FALLINGRISING

0 bit

WA LOW

WA LOW

5

RISINGFALLING

0 bit

WA LOW

WA LOW

6

FALLINGRISING

1 bit

WA HIGH

WA HIGH

7

RISINGFALLING

1 bit

WA HIGH

WA HIGH

8

FALLINGRISING

0 bit

WA HIGH

WA HIGH

9

RISINGFALLING

0 bit

WA HIGH

WA HIGH

10

FALLINGRISING

1 bit

WA HIGH & LOW WA HIGH

11

RISINGFALLING

1 bit

WA HIGH & LOW WA HIGH

12

FALLINGRISING

0 bit

WA HIGH & LOW WA HIGH

13

RISINGFALLING

0 bit

WA HIGH & LOW WA HIGH

<I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate>

32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>

23.2.7.2 TOBY-L2
Mode CLK edge for CLK edge for MSB delay TX channel
TX
RX
2
RISINGFALLING
2 bit
WA HIGHRX channel CLK frequency

WA frequency

WA HIGH

3

RISINGFALLING

2 bit

WA HIGH

WA HIGH

4

FALLINGRISING

1 bit

WA HIGH

WA HIGH

5

RISINGFALLING

1 bit

WA HIGH

WA HIGH

6

RISINGFALLING

2 bit

WA LOW

WA LOW

7

RISINGFALLING

2 bit

WA LOW

WA LOW

8

FALLINGRISING

1 bit

WA LOW

WA LOW

9

RISINGFALLING

1 bit

WA LOW

WA LOW<I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate><I2S_sample_
rate>

UBX-13002752 - R67

23 Audio interface

32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>
32*<I2S_sample_
rate>

Page 577 of 1001

u-blox cellular modules - AT commands manual223.2.8 Normal I S modes timing diagrams
23.2.8.1 TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
WA (all normal modes)

TXD timeslot (Normal mode 2-3): 1 bit delay; channel on WA low

TXD timeslot (Normal mode 4-5): 0 bit delay; channel on WA low

TXD (Normal mode 6-7): 1 bit delay; channel on WA high

TXD (Normal mode 8-9): 0 bit delay; channel on WA high

TXD (Normal mode 10-11): 1 bit delay; channel on WA high and low

TXD (Normal mode 12-13): 0 bit delay; channel on WA high and low

A single transmitted word is marked in grey. MSB is marked darker.
Since RXD bits are read on the opposite edge of CLK signal respect TXD bits, the RXD word slot starts half bit
delayed respect TXD word slot.
Relation between WA and CLK edge for Normal I2S depends on mode:
WAWA

CLK (modes 3, 5, 7, 9, 11, 13)

CLK (modes 2, 4, 6, 8, 10)23.2.8.2 TOBY-L2
A single transmitted word is marked in grey. MSB is marked darker.

UBX-13002752 - R67

23 Audio interface

Page 578 of 1001

u-blox cellular modules - AT commands manual

WA (all normal modes)

TXD (Normal mode 2-3): 2 bit delay; channel on WA high

TXD (Normal mode 4-5): 1 bit delay; channel on WA high

TXD timeslot (Normal mode 6-7): 2bit delay; channel on WA low

TXD timeslot (Normal mode 8-9): 1bit delay; channel on WA low

23.3 Play audio resource +UPAR+UPAR
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

23.3.1 Description
Starts the playback of the pre-defined tone of the selected audio resource.

23.3.2 Syntax
Type
Set

SyntaxAT+UPAR=<audio_resource>,<tone_id>,<nof_repeats>

Test

AT+UPAR=?

Response
OK

ExampleAT+UPAR=0,1,0OK+UPAR: (list of supported <audio_+UPAR: (0-2),(0-66),(0-255)
resource>s),(list of supportedOK<tone_id>s),(list of supported <nof_repeats>s)OK

UBX-13002752 - R67

23 Audio interface

Page 579 of 1001

u-blox cellular modules - AT commands manual

23.3.3 Defined values
Parameter<audio_resource>

Type
Number<tone_id>

Number<nof_repeats>

Number<error>NumberDescription
Specifies the audio resource. Allowed values:• 0: tone generator• 1: MIDI player• 2: audio loop for test purposes. Use this command to generate an audio loop
between the uplink and downlink current path (+USPM) when not in a call. Use thesidetone command (+USTN) for the loop amount configuration. For the uplink to
downlink loop on call use sidetone (+USTN) command only
Specifies the pre-defined tone id to be played; the supported values depend by<audio_resource> values according to the Notes
Specifies the number of repeats. Allowed values:• 0: infinite loop
• n: n repeats
The "+CME ERROR: operation not supported" error result code will be provided inthese cases (if +CMEE is set to 2):• An incorrect number of parameters is provided• The parameter values are out of range

23.3.4 Notes
TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• Allowed values for tone generator are:
Id
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

•

Tone
DTMF 0
DTMF 1DTMF 2
DTMF 3
DTMF 4
DTMF 5
DTMF 6
DTMF 7
DTMF 8
DTMF 9DTMF hash
DTMF asterix
key tone 1
key tone 2
key tone 3
key tone 4
key tone 5
service tone 0
service tone 1
service tone 2
service tone 3
service tone 4
service tone 5
service tone 6
service tone 7

Id
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

Tone
service tone 8
service tone 9
service tone 10
service tone 11
service tone 12
service tone 13
service tone 14
service tone 15
service tone 16
service tone 17
service tone 18
service tone 19
service tone 20
service tone 21
service tone 22
service tone 23
service tone 24
service tone 25
service tone 26
service tone 27
service tone 28
melody 0
melody 1
melody 2
melody 3

Id
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72

Tone
melody 4
melody 5
melody 6
melody 7
melody 8
melody 9
melody 10
melody 11
melody 12
melody 13
melody 14
melody 15
melody 16
melody 17
melody 18
service tone 29
service tone 30
Audio tone 300 Hz
Audio tone 500 Hz
Audio tone 1000 Hz
Audio tone 2000 Hz
Audio tone 3000 Hz
Audio tone 3400 Hz

Table 78: Allowed pre-defined tones
Allowed values for <audio_resource>=1 (MIDI player) are:
Id
0
1
2
3

Ringing tone
ring
baroquecaribic
jamesbond

UBX-13002752 - R67

Id
5
6
7
8

Ringing tone
ramp spmidi
mozart imel
wheneverimperialmarch

23 Audio interface

Page 580 of 1001

u-blox cellular modules - AT commands manual

Id
4

•
•
•

•

Ringing tone
moonstar

Id

Ringing tone

Table 79: Allowed ringing tones
MIDI Melodies are the same selectable as ringer by +URNG command.
<tone_id> and <nof_repeats> are unused when <audio_resource>= 2 (audio loop).
The ringer on an incoming call, the alarm tones (+CALA) and service tones (e.g.: Call Waiting tone) havethe priority on the audio player (+UPAR). If they are not muted and must be played, the audio player(+UPAR) is stopped. Incoming call ringer and service tones can be muted by +CALM command (see notes),
alarm tones can be muted by <silent> parameter in +CALA command.
During fast start / stop test sequence a queue overflow might occur, in this case an error result code(+CME ERROR: memory full) is returned.

TOBY-L2• <audio_resource>=0 (TONE generator) only the DTMF tones are supported.
• <audio_resource>=1 (MIDI player) is not supported.
• <tone_id>=67 .. 72 are not supported.
• Dual streaming (simultaneous playing of tones and audio files) is not supported: the tone generator
should not be executed if the audio player is already active (+UPLAYFILE)• During a speech call the pre-defined tone is not mixed with speech; the speech is muted while the tone
is playing.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• <audio_resource>=1 (MIDI player) is not supported.
• The SMS tones have the priority on audio player (+UPAR). If they must be played, the audio player(+UPAR) is stopped. SMS tones can be muted by +CALM, +UMSM commands.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-01S /LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270• <tone_id>=67 .. 72 are not supported.
LISA-U1• <audio_resource>=2 (audio loop for test purposes) is not supported.
• <tone_id>=67 .. 72 are not supported.
SARA-G3 / LEON-G1• The audio player (+UPAR) has the priority on SMS tones. If a player is active, SMS tones are not played.
SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S• <tone_id>=67 .. 72 are not supported.
LEON-G1• <audio_resource>=2 (audio loop for test purposes) is not supported.
• <tone_id>=67 .. 72 are not supported.
SARA-G4• <audio_resource>=1 (MIDI player) is not supported.
• Dual streaming (simultaneous playing of tones and audio files) is not supported: the +UPLAYFILE AT
command returns the "+CME ERROR: operation not supported" error result code, if the +UPAR AT
command is running with any <audio_resource>. The +UPLAYFILE AT command is stopped when the+UPAR AT command is started.
• Allowed values for tone generator are:
Id
0
1
2
3
4
5

Tone
DTMF 0
DTMF 1DTMF 2
DTMF 3
DTMF 4
DTMF 5UBX-13002752 - R67

23 Audio interface

Page 581 of 1001

u-blox cellular modules - AT commands manual

Id
6
7
8
9
10
11
12
13
14
15

Tone
DTMF 6
DTMF 7
DTMF 8
DTMF 9DTMF A
DTMF B
DTMF CDTMF DDTMF hash
DTMF asterix

Table 80: Allowed pre-defined tones

23.4 Stop audio resource +USAR+USAR
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

23.4.1 Description
Stops the playback of the selected audio resource.

23.4.2 Syntax
Type
Set

SyntaxAT+USAR=<audio_resource>

Response
OK

Test

AT+USAR=?

+USAR: (list of supported <audio_
resource>s)

ExampleAT+USAR=0
OK+USAR: (0-2)
OKOK

23.4.3 Defined values
Parameter<audio_resource>

Type
Number<error>NumberDescription
Specifies the audio resource. Allowed values:• 0: DSP tone generator• 1: MIDI player• 2: audio loop for test purposes. Use this command to stop an audio loop between
uplink and downlink current path (+USPM).
The "+CME ERROR: operation not supported" error result code will be provided inthese cases (if +CMEE is set to 2):• An incorrect number of parameters is provided• The parameter values are out of range

23.4.4 Notes•

During fast start / stop test sequence a queue overflow might occur, in this case an error result code(+CME ERROR: memory full) is returned.

TOBY-L2• <audio_resource>=1 (MIDI player) is not supported.
• The command AT+USAR=0 stops the tone generated by the +UPAR or +UTGN AT commands.

UBX-13002752 - R67

23 Audio interface

Page 582 of 1001

u-blox cellular modules - AT commands manual

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• <audio_resource>=1 (MIDI player) is not supported.
LISA-U1• <audio_resource>=2 (audio loop for test purposes) is not supported.
SARA-G3• The command AT+USAR=0 stops the tone generated by the +UPAR or +UTGN AT commands.
SARA-G4• <audio_resource>=1 (MIDI player) is not supported.
• The command AT+USAR=0 stops the tone generated by the +UPAR.
LEON-G1• <audio_resource>=2 (audio loop for test purposes) is not supported.
• The command AT+USAR=0 stops the tone generated by the +UPAR or +UTGN AT commands.

23.5 Play audio file +UPLAYFILE+UPLAYFILE
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

23.5.1 Description
Play the specified audio file stored in the file system. The audio signal from the player can be routed to uplinkand downlink path. For more details about file system description see the File System Introduction.
Player supports playing of 8 or 16kHz files. See <filename> parameter.
Player supports configuration as ringer and answering machine. See <user_conf> parameter.
After having issued the command and played the requested file, one of these URCs is provided:• +UPLAYFILE: the player reaches the end of the file and the player is stopped.
• +UPLAYFILE STOPPED: the player is stopped before reaching the end of the file.
Player can be stopped before the end of file by AT+USTOPFILE command.

23.5.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UPLAYFILE=<filename>[,<path>[,user_conf]]

Response

ExampleOK

AT+UPLAYFILE="pcmfile.16khz",1OK

Start playing in a loop
Set
AT+UPLAYFILE=<filename>,<path>,0OK

Start playing a file
Set
AT+UPLAYFILE=<filename>[,<path>[,1]]OK

Configure ringer
Set
AT+UPLAYFILE=<filename>,<path>,2

OK

Disable ringer
Set
AT+UPLAYFILE="",,2

UBX-13002752 - R67

AT+UPLAYFILE="pcmfile.16khz",1,0
OK
AT+UPLAYFILE="pcmfile.16khz"
OK
AT+UPLAYFILE="pcmfile.16khz",0,2
OK

OK

23 Audio interface

AT+UPLAYFILE="",,2

Page 583 of 1001

u-blox cellular modules - AT commands manualType

Syntax

Display ringer configuration
Set
AT+UPLAYFILE=<filename>,<path>,102

Response

ExampleOK+UPLAYFILE: <filename>,<path>

AT+UPLAYFILE="",,102

OK+UPLAYFILE: "pcmfile.16khz",1OK

Configure answering machine
Set
AT+UPLAYFILE=<filename>,<path>,3
Disable answering machine
Set
AT+UPLAYFILE="",,3

OK

AT+UPLAYFILE="pcmfile.16khz",1,3
OK

OK

AT+UPLAYFILE="",,3
OK

Display answering machine configuration
Set
AT+UPLAYFILE=<filename>,<path>,103+UPLAYFILE: <filename>,<path>

AT+UPLAYFILE="",,103

OK+UPLAYFILE: "pcmfile.16khz",1Read+UPLAYFILE: <playstatus>+UPLAYFILE: 0

OK+UPLAYFILE+UPLAYFILE STOPPEDOK

OKAT+UPLAYFILE?

URC
URC

23.5.3 Defined values
Parameter<filename>

Type
String<path>

Number<user_conf>

Number<playstatus>

Number<error>NumberDescription
Specifies the audio resource file name to be played. For the PCM raw file format, thesampling rate is specified with file extension:• *.16khz: file with 16 kHz sampling rate
• any other extension or no extension: file with 8 kHz sampling rate
Specifies the audio path on which to play the file:• 0 (default value): play on downlink path
• 1: play on uplink path
Specifies play and configuration options:• 0: Play in a loop
• 1 (default value): Play once
• 2: Configure ringer. To disable the ringer, parameter <filename> has to be set to "",while parameter <path> is ignored and can be set to any of the allowed values.
• 3: Configure answering machine. To disable the answering machine, parameter<filename> has to be set to "", while parameter <path> is ignored and can be set toany of the allowed values.
• 102: Display ringer configuration. Parameters <filename> and <path> are ignoredand can be set to any of the allowed values .
• 103: Display answering machine configuration. Parameters <filename> and <path>
are ignored and can be set to any of the allowed values.
Play status:• 0: no file is playing• 1: the file is playing
These error result codes will be provided if +CMEE is set to 2:• "+CME ERROR: operation not supported": an incorrect number of parameters isprovided or the parameter values are out of range• "+CME ERROR: FILE NOT FOUND": the <filename> file is not present in the filesystem

23.5.4 Notes•

If the <path> parameter is not supported the audio signal is only routed from the player to the downlink
path.

UBX-13002752 - R67

23 Audio interface

Page 584 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2• The <path> and <user_conf> parameters are not supported.
• ".16khz" extension in <filename> is ignored.
• The +CRSL command selects the player volume; if +CRSL is set to 0 or +CALM is set to 1, the +UPLAYFILE
command returns an error result code (+CME ERROR: operation not supported).
• Modules support the WAV audio format. The storage format of audio data must be: 8/16 kHz sample rate,
signed 16 bits PCM, little endian, mono.
• Dual streaming (simultaneous playing of tones and audio files) is not supported: the tone generator
should not be executed if the audio player is already active (+UTGN, +UPAR).
• The command provides an error result code ("+CME ERROR: operation not allowed" if +CMEE=2) if the<mode> parameter of +UDTMFD AT command differs from 0.
LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 / LARA-R280 / TOBY-R2 / SARA-U201-03A /SARA-U201-03B / SARA-U201-03X / SARA-U201-63B / SARA-U260 / SARA-U270 / SARA-U280 /LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S /LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270• The <path> and <user_conf> parameters are not supported.
• ".16khz" extension in <filename> is ignored.
• The player volume is affected by <Mix_afe> and <Scal_Rec> parameters (see the +USGC command).
• Modules support the PCM audio file. The storage format of PCM audio files must be: 8 kHz sample rate,
signed 16 bits, little endian, mono.
LARA-R211• The PCM audio files are supported. The storage format of PCM audio files must be: 8/16 kHz sample rate,
signed 16 bits, little endian, mono.
• The <path> and <user_conf> parameters are not supported by LARA-R211-02B-00, LARA-R211-02B-01,
LARA-R211-02B-02.
• On LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02 ".16khz" extension in <filename> isignored.
• On LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02 the player volume is affected by <Mix_afe> and <Scal_Rec> parameters (see the +USGC command).
• LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02 support the PCM audio file. The storage
format of PCM audio files must be: 8 kHz sample rate, signed 16 bits, little endian, mono.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B / LISA-U201-04B• Modules support the PCM audio file. The storage format of PCM audio files must be: 8/16 kHz sample
rate, signed 16 bits, little endian, mono.
LISA-U1• The <path> and <user_conf> parameters are not supported.
• ".16khz" extension in <filename> is ignored.
• If +CRSL is set to 0, the audio file player is muted, otherwise +CRSL does not change the volume of theaudio file player. The player volume is changed by <Mix_afe>, <Scal_Rec> and <Analog_gain> parameters(see the +USGC command).
• Modules support the PCM audio file. The storage format of PCM audio files must be: 8 kHz sample rate,
signed 16 bits, little endian, mono.
SARA-G4• The +CRSL command selects the player volume.
• If the command is issued during a voice call, the module returns an error result code.
• The <path> and <user_conf> parameters are not supported.
• The +UPLAYFILE URC is not supported.
• The PCM and the ARM audio files are not supported.
• Modules support the WAV audio format; the <filename> parameter extension must be ".wav". The
storage format of audio data must be: 8/11.025/16/22.050/24/32/44.100/48 kHz sample rate, signed 16
bits PCM, little endian, mono.
• Dual streaming (simultaneous playing of tones and audio files) is not supported: the +UPLAYFILE
AT command returns the "+CME ERROR: operation not supported" error result code, if the +UPAR

UBX-13002752 - R67

23 Audio interface

Page 585 of 1001

u-blox cellular modules - AT commands manual

AT command is running with any audio resource (see the +UPAR AT command, <audio_resource>
parameter). The +UPLAYFILE AT command is stopped when the +UPAR AT command is started.
SARA-G3• The <path> and <user_conf> parameters are not supported.
• ".16khz" extension in <filename> is ignored.
• The +CRSL command selects the player volume; if +CRSL is set to 0 or +CALM is set to 1, the +UPLAYFILE
command returns an error result code (+CME ERROR: operation not supported). The player volume is alsochanged by <Scal_Rec> and <Analog_gain> parameters (see the +USGC command).
• Modules support the AMR audio file. The storage format of AMR encoded audio content must becompliant to RFC3267 [44].
• The +UPLAYFILE and the +UPLAYFILE STOPPED URCs are not supported.
• The command cannot be used during an eCall activity; in that case an error result code is provided ("+CME
ERROR: operation not supported" if +CMEE=2).
LEON-G1• The <path> and <user_conf> parameters are not supported.
• ".16khz" extension in <filename> is ignored.
• The +CRSL command selects the player volume; if +CRSL is set to 0 or +CALM is set to 1, the +UPLAYFILE
command returns an error result code (+CME ERROR: operation not supported). The player volume is alsochanged by <Scal_Rec> and <Analog_gain> parameters (see the +USGC command).
• Modules support the AMR audio file. The storage format of AMR encoded audio content must becompliant to RFC3267 [44].
• The URC (+UPLAYFILE STOPPED) is not supported.

23.6 Record audio file +URECFILE+URECFILE
Modules
Attributes

LARA-R211
SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
Up to 10 s

Error reference+CME Error

23.6.1 Description
Records an audio file to the file system. For more details about file system description see the File System
Introduction. The audio signal can be recorded on both uplink and downlink path in 8 or 16 kHz.
• On the uplink path, the file is recorded from the microphone.
• On the downlink path, the file is recorded from received speech.
After issuing the command following URCs are provided:• +URECFILE: <path>,<event>: event occurred on specific path (started, stopped, timer expired).
• +UURECFILEE: <path>,<error_code>: error occurred when recording a file.
The recorder can be stopped during recording using the +USTOPFILE command, specifying parameter<resource> as recorder.
The recorder supports 8 kHz and 16 kHz raw PCM files. See <filename> parameter.
The recorder will overwrite the file if it already exists.

23.6.2 Syntax
Type
Set

SyntaxResponse
AT+URECFILE=<filename>,<path>, OK<duration>

Read

AT+URECFILE?

URCs
URC

UBX-13002752 - R67

ExampleAT+URECFILE="pcmfile.16khz",0,10+URECFILE: <state>

OK+URECFILE: 0

OK

OK+UURECFILE: <path>,<event_code> +UURECFILE: 1,0

23 Audio interface

Page 586 of 1001

u-blox cellular modules - AT commands manual

Type
URC

SyntaxResponse+UURECFILEE: <path>,<error_
code>

Example+UURECFILEE: 1,5

23.6.3 Defined values
Parameter<filename>

Type
String<path>

Number<duration>

Number<state>Number<event_code>

Number<error>Number<error_code>

NumberDescription
File name for recording PCM raw 16 bit file on file system. The sampling rate is
specified with file extension:• *.16khz: file with 16 kHz sampling rate
• Any other extension or no extension: file with 8 kHz sampling rate
Specifies the audio path on which to record the file:• 0: record on the downlink path
• 1: record on the uplink path
• 2: record uplink and downlink path
Duration of recording in seconds:• 0: infinite recording (has to be stopped manually with +USTOPFILE command)• 1-65536: allowed number of seconds
Recorder state returned on read request:• 0: recorder idle
• 1: recorder active
Unsolicited event codes returned by +UURECFILE when specific events happen:• 0: recording started• 1: recording stopped• 2: recording paused (Not applicable to this command)• 3: recording timer expired
This error result code will be provided if +CMEE is set to 2:• "+CME ERROR: Operation not allowed": <op_code> was not valid for the current
state of the recorder
An error has occurred during recording:• 0: resource is not available (file <filename> could not be opened for writing)• 1: device is not available (device driver is busy)• 2: unexpected internal message received by recorder state machine• 3: internal error has occurred, recovery will be attempted• 4: audio frames were missed in the last second of recording (cause could be lackof empty space). Error will appear after each second of recording where missing
frames were detected.
• 5: file system out of space• 6: file system error

23.6.4 Notes
SARA-U2 / LISA-U2• The module supports raw PCM audio format. The storage format of PCM audio files is: 8/16 kHz sample
rate, signed 16 bits, little endian, mono.
• Recording and playing in parallel is supported.
• Recording can consume a lot of space on file system. If the recorder runs out of space it will generate anerror and stop.
LISA-U2• The recorded file is created up-front. If there is not enough space in the file system the operation will
return the +UURECFILEE URC (0 - resource is not available).
• If the recording is manually stopped, the recording will be silent from that point forward (the file willkeep full size).
• Trying to record over existing file will return the +UURECFILEE URC (0 - resource is not available).
LARA-R211• The command is not supported by LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02.
• <duration>=0 is not supported.

UBX-13002752 - R67

23 Audio interface

Page 587 of 1001

u-blox cellular modules - AT commands manual••

The recorded file is created up-front. If there is not enough space in the file system the operation will
return the +UURECFILEE URC (5 - file system out of space).
Trying to record over existing file will return the +UURECFILEE URC (0 - resource is not available).

23.7 Stop audio file +USTOPFILE+USTOPFILE
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

23.7.1 Description
Stop the audio file reproduction.
A URC is provided after the AT+USTOPFILE command correctly stopped the file.

23.7.2 Syntax
Type
ActionSyntaxAT+USTOPFILE[=<resource>]

Response
OK

ExampleAT+USTOPFILE
OK

URC
URC

+UPLAYFILE STOPPED+UURECFILE: <path>,1

23.7.3 Defined values
Parameter<resource>

Type
Number<path>

NumberDescription
Specifies the audio resource to stop:• 0 (default value): audio player (see +UPLAYFILE)• 1: audio recorder (see +URECFILE)
Specifies the audio path on which the recording was stopped:• 0: stopped recording on the downlink path
• 1: stopped recording on the uplink path

23.7.4 Notes
TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U201-03A / SARA-U201-03B / SARA-U201-03X / SARA-U201-63B /SARA-U260 / SARA-U270 / SARA-U280 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1• Parameter <resource> is not supported.
SARA-G4• <resource>=1 (audio recorder) is not supported.
• The +UURECFILE URC is not supported.
SARA-G340 / SARA-G350 / LEON-G1• The URCs are not available.

UBX-13002752 - R67

23 Audio interface

Page 588 of 1001

u-blox cellular modules - AT commands manual

23.8 Play audio file +UAPLAY+UAPLAY
Modules
Attributes

LARA-R211
SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

23.8.1 Description
Plays an audio file from the file system. For more details about file system description see the File System
Introduction. The audio signal from the player can be played on both uplink and downlink paths with possibility
to mix with speech and other sources using <mix> parameter.
On the uplink path, the played file is not affected by speech enhancement and is injected just before Radiotransmission. Played file does not feedback through side tone.
On the downlink path, the played file is injected just after Radio receive.
After issuing the command, the following URCs are provided:• +UUAPLAY: <path>,<event>: an event (started, stopped, paused) occurred on specific path
• +UUAPLAYE: <path>,<error_code>: an error occurred while playing a file.
The player can be stopped and paused during play using the <op_code> parameter.
Player supports 8 kHz and 16 kHz raw PCM files. See <filename> parameter.

23.8.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UAPLAY=<path>,<op_code>[,<filename>[,<mix>]]

Response

ExampleOK

AT+UAPLAY=0,0OK

Start playing
Set
AT+UAPLAY=<path>,0,<filename>[, OK<mix>]

AT+UAPLAY=0,0,"pcmfile.16khz"
OK+UUAPLAY: 0,0(playing)+UUAPLAY: 0,1

Stop playing
Set
AT+UAPLAY=<path>,1

OK

AT+UAPLAY=1,1
OK+UUAPLAY: 1,1

Pause playing
Set
AT+UAPLAY=<path>,2

OK

AT+UAPLAY=0,2
OK+UUAPLAY: 0,2

Read
Read

AT+UAPLAY=<path>+UAPLAY: <path>,<state>

AT+UAPLAY=1

OK+UAPLAY: 1,0
OK

URCs
URC
URC

UBX-13002752 - R67+UUAPLAY: <path>,<event_code>+UUAPLAYE: <path>,<error_code>

23 Audio interface+UUAPLAY: 1,0+UUAPLAYE: 1,2

Page 589 of 1001

u-blox cellular modules - AT commands manual

23.8.3 Defined values
Parameter<path>

Type
Number<op_code>

Number<filename>

String<mix>

Number<state>Number<event_code>

Number<error>Number<error_code>

NumberDescription
Specifies the audio path on which to play the file:• 0: play on the downlink path
• 1: play on the uplink path
Play operation:• 0: start/resume playing• 1: stop playing• 2: pause playing
File name of PCM raw 16 bit file on file system. The sampling rate is specified with fileextension:• *.16khz: file with 16 kHz sampling rate
• any other extension or no extension: file with 8 kHz sampling rate
Mixing of audio:• 0 (default value): all other sources muted• 1: played file mixed with other sources
Player state returned on read request:• 0: player idle
• 1: player active• 2: player paused
Unsolicited event codes returned by +UUAPLAY when specific events happen:• 0: playing started• 1: playing stopped• 2: playing paused
These error result codes will be provided if +CMEE is set to 2:• "+CME ERROR: FFS file not found": the <filename> file is not present in the filesystem• "+CME ERROR: Operation not allowed": <op_code> was not valid for the current
state of the player
An error has occurred during playing:• 0: resource is not available (file <filename> could not be opened for reading)• 1: device is not available (device driver is busy)• 2: unexpected internal message received by player state machine• 3: internal error has occurred, recovery will be attempted• 4: audio frames were missed in the last second of playing (cause could be lack of
empty space). Error will appear after each second of playing where missing frames
were detected.

23.8.4 Notes
SARA-U2 / LISA-U2• Module supports raw PCM audio format. The storage format of PCM audio files must be: 8/16 kHz sample
rate, signed 16 bits, little endian, mono.
• Dual streaming (simultaneous playing of tones and audio files) is supported (+UTGN, +UPAR). Playing inparallel with +UPLAYFILE is supported.
• Playing of 16 kHz PCM audio file on Narrow-band call or 8 kHz PCM audio file on Wide-band call will resultin distorted audio.
• Using player in eCall is not possible.
LISA-U2• Resume playing is not supported.
LARA-R211• The command is not supported by LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02.
• Resume playing is not supported.

UBX-13002752 - R67

23 Audio interface

Page 590 of 1001

u-blox cellular modules - AT commands manual

23.9 Record audio file +UAREC+UAREC
Modules
Attributes

LARA-R211
SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
partial
No
No
No-

Error reference+CME Error

23.9.1 Description
Records an audio file to the file system. For more details about file system description see the File System
Introduction. The audio signal can be recorded on both uplink and downlink paths.
• On the uplink path, the file is recorded just before Radio transmission.
• On the downlink path, the file is recorded just after Radio receive.
After issuing the command following URCs are provided:• +UUAREC: <path>,<event>: event occurred on specific path (started, stopped, paused, timer expired).
• +UUARECE: <path>,<error_code>: error occurred when recording a file.
The recorder can be stopped and paused during recording using the <op_code> parameter.
The recorder supports 8 kHz and 16 kHz raw PCM files. See <filename> parameter.
The user has an option of timed recording by means of the <duration> parameter.
There is an option of call triggered recording. See <trigger> parameter.
The recorder will overwrite the file if it already exists.

23.9.2 Syntax
Type
SyntaxResponse
Generic syntax
Set
AT+UAREC=<path>,<op_code>[,OK<filename>,<duration>[,<trigger>]]Start recording
Set
AT+UAREC=<path>,0,<filename>,<duration>[,<trigger>]

OK

ExampleAT+UAREC=0,1
OK
AT+UAREC=0,0,"pcmfile.16khz",10OK+UUAREC: 0,0(10 seconds elapsed)+UUAREC: 0,3
AT+UAREC=0,0,"pcmfile.16khz",0,1
OK
RING
ATA
+UUAREC: 0,0(record until manual stop, calldisconnect or file system full)+UUARECE: 0,4+UUAREC: 0,2

Stop recording
Set
AT+UAREC=<path>,1

OK

AT+UAREC=0,1
OK+UUAREC: 0,1

Pause recording
Set
AT+UAREC=<path>,2

OK

AT+UAREC=0,2
OK

UBX-13002752 - R67

23 Audio interface

Page 591 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Example+UUAREC: 0,2

Read

AT+UAREC=<path>+UAREC: <path>,<state>

AT+UAREC=1

OK+UAREC: 1,3
OK

URCs
URC
URC

+UUAREC: <path>,<event_code>+UUARECE: <path>,<error_code>+UUAREC: 1,0+UUARECE: 1,2

23.9.3 Defined values
Parameter<path>

Type
Number<op_code>

Number<filename>

String<duration>

Number<trigger>

Number<state>Number<event_code>

Number<error>Number<error_code>

NumberUBX-13002752 - R67

Description
Specifies the audio path on which to record the file:• 0: record on the downlink path
• 1: record on the uplink path
Record operation:• 0: start/resume recording• 1: stop recording• 2: pause recording
File name for recording PCM raw 16 bit file on file system. The sampling rate is
specified with file extension:• *.16khz: file with 16 kHz sampling rate
• any other extension or no extension: file with 8kHz sampling rate
Timed recording:• 0: recording is not time limited• 1-65536: recorder will record for the number of seconds specified or until a stop is
received
Trigger for starting/stopping recording on a audio call connect or disconnect:• 0 (default value): call trigger is disabled. Recording will start immediately• 1: call trigger is enabled. Recording will start when audio call is connected and stop
when audio call is disconnected (or stop command received)Recorder state returned on read request:• 0: recorder idle
• 1: recorder active• 2: recorder paused• 3: recorder waiting for call connected trigger• 4: recorder waiting for call disconnected trigger
Unsolicited event codes returned by +UUAREC when specific events happen:• 0: recording started• 1: recording stopped• 2: recording paused• 3: recording timer expired
This error result code will be provided if +CMEE is set to 2:• "+CME ERROR: Operation not allowed": <op_code> was not valid for the current
state of the recorder
An error has occurred during recording:• 0: resource is not available (file <filename> could not be opened for writing)• 1: device is not available (device driver is busy)• 2: unexpected internal message received by recorder state machine• 3: internal error has occurred, recovery will be attempted• 4: audio frames were missed in the last second of recording (cause could be lackof empty space). Error will appear after each second of recording where missing
frames were detected.
• 5: file system out of space• 6: file system error

23 Audio interface

Page 592 of 1001

u-blox cellular modules - AT commands manual

23.9.4 Notes
SARA-U2 / LISA-U2• The module supports raw PCM audio format. The storage format of PCM audio files must be: 8/16 kHz
sample rate, signed 16 bits, little endian, mono.
• Recording and playing in parallel is supported.
• Recording of 16 kHz PCM audio file on a Narrow-band call or 8 kHz PCM audio file on a Wide-band call will
result in distorted audio recording.
• Recording can consume a lot of space on file system. If the recorder runs out of space it will generate anerror and stop.
• Using trigged recording in combination with the duration will result in timed recording where timer starts
on trigger (call connect). Recording will stop after <duration> seconds. If the recording is paused in
between, the timer will continue for remained amount of time after resume.
• Using DTMF detection and recorder at the same time is not possible.
• Using recorder in eCall is not possible.
LISA-U2• <op_code>=2 is not supported.
• <duration>=0 is not supported.
• The recorded file is created up-front. If there is not enough space in the file system the operation will
return the +UUARECE URC (0 - resource is not available).
• If recording is manually stopped, the recording will be silent from that point forward (the file will keep
full size).
• Trying to record over existing file will return the +UUARECE URC (0 - resource is not available).
LARA-R211• The command is not supported by LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02.
• <op_code>=2 is not supported.
• <duration>=0 is not supported.
• The recorded file is created up-front. If there is not enough space in the file system the operation will
return the +UUARECE URC (0 - resource is not available).
• If recording is manually stopped, the recording will be silent from that point forward (the file will keep fullsize).
• Trying to record over existing file will return the +UUARECE URC (0 - resource is not available).

23.10 Tone generator +UTGN+UTGN
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

23.10.1 Description
Starts a tone on the module tone generator. The frequency, duration and volume of the tone must be set.

23.10.2 Syntax
Type
Set

SyntaxAT+UTGN=<freq>,<duration>,<volume>[,<UplinkSending>]

Test

AT+UTGN=?

Response
OK

ExampleAT+UTGN=1000,1000,100,1

OK+UTGN: (list of supported <freq>s), +UTGN: (300-3400),(50-1360),(1-10(list of supported <duration>s),(list 0),(0-2)
OK

UBX-13002752 - R67

23 Audio interface

Page 593 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponseof supported <volume>s)[,(list of
supported <UplinkSending>s)]

ExampleOK

23.10.3 Defined values
Parameter<freq>

Type
Number<duration>

Number<volume>Number<UplinkSending>Number<error>NumberDescription
Frequency of the sinus waveform in Hz for the tone generator:• TOBY-L2 - The range goes from 50 to 7000
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The
range goes from 300 to 3400
Duration of the tone in milliseconds:• TOBY-L2 - The range of permitted values is from 20 to 8000 in steps of multiples
of 20. If the parameter is set to a value that is not a multiple of 20, it will be rounded
down to the nearest multiple-of-20 value. E.g., if the user sets the parameter to 115,
the generated tone duration will be 100 ms.
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - The range goes from 50 to 1360
• LISA-U1 - The range goes from 10 to 1360
• SARA-G3 / LEON-G1 - The range goes from 10 to 8000
Volume for the tone generator:• TOBY-L2 - The range goes from 1 to 37, where 1 means -36 dB, 37 means 0 dB.
Increasing step is 1 dB (e.g.: 30 means -7 dB)• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The
range goes from 1 to 100; volume 1 means muted. Increasing step is 0.25 dB
Enables/disables the connection of the tone generator to uplink and/or downlinkpath:• 0 (default value): the tone is sent only on downlink path
• 1: the tone is sent only on uplink path
• 2: the tone is sent both on downlink and uplink path
The "+CME ERROR: operation not supported" error result code will be provided inthese cases (if +CMEE is set to 2):• An incorrect number of parameters is provided• The parameter values are out of range

23.10.4 Notes
•
•
•

•

The tone playing can be stopped by means of the set command: AT+UTGN=0,0,0. If no tone is playing anerror result code (+CME ERROR: operation not supported) is returned.
If the "silent mode" is enabled (+CALM=1) the +UTGN command returns an error result code (+CME
ERROR: operation not supported).
The ringer on an incoming call, the alarm tones (+CALA) and service tones (e.g.: Call Waiting tone) havethe priority on the tone generator (+UTGN). If they are not muted and must be played, the tone generator(+UTGN) is stopped. An incoming call ringer and service tones can be muted by +CALM command (seenotes), alarm tones can be muted by <silent> parameter in +CALA command.
During fast start / stop test sequence a queue overflow might occur, in this case an error result code(+CME ERROR: memory full) is returned.

TOBY-L2• The command AT+UTGN=0,0,0 stops the tone generated by the +UPAR or +UTGN AT commands.
• Dual streaming (simultaneous playing of tones and audio files) is not supported: the tone generator
should not be executed if the audio player is already active (+UPLAYFILE)• During a speech call the pre-defined tone is not mixed with speech; the speech is muted while the tone
is playing.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• The SMS tones have the priority on the tone generator (+UTGN). If they must be played, the tone
generator (+UTGN) is stopped. SMS tones can be muted by +CALM, +UMSM commands.

UBX-13002752 - R67

23 Audio interface

Page 594 of 1001

u-blox cellular modules - AT commands manual

SARA-G3 / LEON-G1• The tone generator (+UTGN) has the priority on SMS tones. If tone generator is active, SMS tones are
not played.
• The command AT+UTGN=0,0,0 stops the tone generated by the +UPAR or +UTGN AT commands.

23.11 Ringing tone selection +URNG+URNG
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

Attributes

23.11.1 Description
Allows the user to select one out of a set of predefined ringers.

23.11.2 Syntax
Type
Set

Syntax
AT+URNG=<rng_id>

Response
OK

ExampleAT+URNG=5

Read

AT+URNG?

+URNG: <rng_id>

OK+URNG: 0

Test

AT+URNG=?

OK+URNG: (list of supported <rng_
id>s)

OK
+URNG: (0-18)
OKOK

23.11.3 Defined values
Parameter<rng_id><rng_name_x><error>Type
NumberNumberNumberDescription
Ringer identifier currently selected; the factory-programmed value is 0
Name of the ringer saved in the module
If an incorrect number of parameters is provided or the parameter value is out ofrange the error result code "+CME ERROR: operation not supported" will be provided

23.11.4 Notes
SARA-G340 / SARA-G350 / LEON-G1• The test command is:+URNG:
0 - <rng_name_1>
1 - <rng_name_2>...
rng_max_num - <rng_name_n>•OK
If <rng_id> value is not allowed the error result code "+CME ERROR: Wrong ringer identifier" will be
provided.

UBX-13002752 - R67

23 Audio interface

Page 595 of 1001

u-blox cellular modules - AT commands manual

23.12 SMS alert sound mode (Message Sound Muting) +UMSM+UMSM
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

23.12.1 Description
Mutes the signalling sound of SMS on the MT.

23.12.2 Syntax
Type
Set

SyntaxAT+UMSM=<mode>

Response
OK

ExampleAT+UMSM=0

Read

AT+UMSM?

+UMSM: <mode>

OK+UMSM: 0

Test

AT+UMSM=?

OK+UMSM: (list of supported<mode>s)OK+UMSM: (0-1)
OKOK

23.12.3 Defined values
Parameter<mode>

Type
Number<error>NumberDescription• 0 (default value): normal mode (the signalling sound of SMS on the MT is not muted)• 1: silent mode (the signalling sound of SMS on the MT is muted)
If an incorrect number of parameters is provided or the parameter value is out ofrange the error result code "+CME ERROR: operation not supported" will be provided if+CMEE is set to 2.

23.13 Master clock control +UMCLK+UMCLK
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

23.13.1 Description
Enables or disables the master clock output signal. This is mainly designed to feed the master clock input ofan external audio codec. For more details see the corresponding module system integration manual.
The available output pin configurations are:
• Disabled, set as tristate• Pin output low• Generate 13 MHz clock• Generate 26 MHz clock
Depending on the <enabling_mode> parameter value, the configuration can be applied as soon as thecommand is issued, or as soon as there is an audio activity (i.e. a digital audio interface is enabled).

UBX-13002752 - R67

23 Audio interface

Page 596 of 1001

u-blox cellular modules - AT commands manual

23.13.2 Syntax
Type
Set

SyntaxAT+UMCLK=[<mclk_mode>[,<enabling_mode>]]

Read

AT+UMCLK?

Test

AT+UMCLK=?

Response
OK

ExampleAT+UMCLK=1,1

OK+UMCLK: <mclk_mode>,<enabling_ +UMCLK: 1,1
mode>
OK
OK
+UMCLK: (list of supported+UMCLK: (0-3),(0-1)<mclk_mode>s),(list of supportedOK<enabling_mode>s)OK

23.13.3 Defined values
Parameter<mclk_mode>

Type
Number<enabling_mode>

NumberDescription
CODEC_CLK pin setting:• 0 (default and factory-programmed value): disabled pin; 3-state with pull down
resistor• 1: pin output steady low• 2: codec master clock at 13 MHz• 3: codec master clock at 26 MHz
Specifies when the <mclk_mode> is enabled on CODEC_CLK pin• 0 (default and factory-programmed value): "Audio dependent" mode•

<mclk_mode> is applied to the CODEC_CLK pin only when the audio path is active(audio samples are read on the I2S_RX line and written on the I2S_TX line). Whenthe audio path is disabled (i.e. at call end), then the CODEC_CLK pin is disabledtoo (3-state with pull-down resistor)
1: "Continuous" mode

<mclk_mode> is applied to the CODEC_CLK pin as soon as the AT command isissued, even when the module is in idle and the audio path is disabled (no audio
data written on I2S_TX line, no audio data read on I2S_RX line)
When <mclk_mode>=0 (pin disabled) and <enabling_mode>=0 ("Audio dependent"mode), the CODEC_CLK pin is disabled both when audio path is enabled or disabled.
In this case "Audio dependent" mode matches with "Continuous" mode (the command
AT+UMCLK=0,0 and AT+UMCLK=0,1 are equivalent).

23.13.4 Notes••••

If <mclk_mode>= 1 ("Continuous" mode) the actual clock generation occurs within 10 ms of the command
issuing.
When the power saving is enabled (i.e. AT+UPSV=1) and the module is in the power saving state, themaster clock is disabled even if it is set to "Continuous" mode (+UMCLK=<mclk_mode>,1).
The command setting is stored in the NVM, but it can be recovered by means of AT+UMCLK= (with noparameters).
If the external audio codec (Maxim MAX9860) is enabled by +UEXTDCONF: 0,1 (i.e.: <device_id>=0 and<configuration_enable>=1) this forces the setting codec master clock at 13 MHz, in "Audio dependent"
mode (i.e. +UMCLK=2,0) at boot time. Thus current setting of +UMCLK in NVM will be overwritten at themodule boot time. In this case, disable the master clock at 13 MHz, the AT+UMCLK=0 command must
be explicitly issued after every startup.

TOBY-L2• The GPIO6 pin provides the master clock output signal if configured as "Master clock output" by AT+UGPIOC command.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• The CODEC_CLK pin provides the master clock output signal.

UBX-13002752 - R67

23 Audio interface

Page 597 of 1001

u-blox cellular modules - AT commands manual

23.14 External device configuration +UEXTDCONF+UEXTDCONF
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

23.14.1 Description
LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 / LISA-U270
To be used if and only if the I2C lines are biased high by external pull-ups providing proper circuit connection
to an external audio codec.
Configures an external device, e.g. an audio codec, at the boot time. The setting (on / off) and the configuration
string for each supported device is stored in NVM and applied at each module power-on.
The information text response to the read command lists all the configured devices in separated lines.
The only supported external device is the Maxim MAX9860 audio codec. See Maxim datasheet [55].

23.14.2 Syntax
Type
Set

SyntaxAT+UEXTDCONF=<device_id>[,<configuration_enable>[,<hex_data>]]

Response
OK

Read

AT+UEXTDCONF?

+UEXTDCONF: <device_0>,<configuration_enable0>,<hex_
data0>[[...]+UEXTDCONF: <device_N>,<configuration_enableN>,hex_
dataN>]

Test

AT+UEXTDCONF=?

ExampleAT+UEXTDCONF=0,1,"0000000010
1E3F040000063300250000008A"
OK+UEXTDCONF: 0,0,"0000000010
1E3F040000063300500000008A"+UEXTDCONF: 1,0,"0000000010
1E3F040000064400250000008A"+UEXTDCONF: 2,1,"0000000010
1E3F0400000655006A0000008A"

OK
OK+UEXTDCONF: (list of supported+UEXTDCONF: (0),(0,1),"hex data"<device_id>s),(list of supportedOK<configuration_enable>s),"hex data"
OK

23.14.3 Defined values
Parameter<device_id>

Type
NumberDescription
Device identifier. Allowed value:• 0 (factory-programmed value): Maxim MAX9860 audio codec, connected via I2C.
When enabled, at every start-up the module sets the external codec master clock
at audio dependent 13 MHz (corresponding to the command AT+UMCLK=2,0) andconfigures the external codec via I2C, see Notes below.
Codec Maxim MAX9860 is available on u-blox evaluation boards.
Setting AT+UEXTDCONF=0,1 forces at every start-up +UMCLK: 2,0 in NVM. To
undo / remove this setting, explicitly issue the AT+UMCLK=0 command after
every start-up with +UEXTDCONF: 0,1. Setting back by means of the command
AT+UEXTDCONF=0,0 the clock (+UMCLK) is not automatically forced back to 0.
To fully disable the codec use this AT command sequence:• AT+UMCLK=0,0• AT+UEXTDCONF=0,0• AT+CFUN=16

UBX-13002752 - R67

23 Audio interface

Page 598 of 1001

u-blox cellular modules - AT commands manual

Parameter<configuration_
enable>Type
Number<hex_data>

String<error>StringDescription
Enables/disables the autoconfiguration of the specified external device:• 0 (default and factory-programmed value): disabled• 1: enabled
External device configuration expressed in bytes in hexadecimal format.
For <device_id>=0 (Maxim MAX9860 audio codec): the string must be composed of
18 bytes in hexadecimal format, the first being 0x00, otherwise an error result code("+CME ERROR: operation not supported" if +CMEE is set to 2) will be provided. At
every module's start-up the specified bytes sequence is sent, via I2C, for the external
codec configuration.
• The first byte (0x00) is the address of the first register of the codec to be written(address 0x00).
• The following 17 bytes are the values to be written in the codec's register 0x00 to
0x10 (for the meaning of bytes and the writing in the codec's registers, see Maxim
MAX9860 datasheet [55].
The default and factory-programmed value of <device_id>=0 is "00000000101E3F040000063300500000008A".
If an incorrect number of parameters is provided or the parameter values are out ofrange the error result code "+CME ERROR: operation not supported" will be provided if+CMEE is set to 2.

23.14.4 Notes•

Examples:Command / Action
Meaning
AT+UEXTDCONF=0,1,"00000000101E3F040000063300 The <hex_data> parameter is stored in the NVM.
250000008A
Program and enable the external audio codec after the
AT+CFUN=16
module reset.
AT+UEXTDCONF=0,1
The <hex_data> parameter value stored in the NVM
remains unchanged.
AT+CFUN=16
Program and enable the external audio codec after themodule reset.
AT+UEXTDCONF=0,1,""
The <hex_data> parameter is restored in the NVM to thefactory-programmed value ("00000000101E3F0400000
AT+CFUN=1663300500000008A").

AT+UMCLK=0,0

Program and enable the external audio codec after themodule reset.
Program and enable the external audio codec at the next
module reboot.
Disable the master clock.

AT+UEXTDCONF=0,0

Disable the external audio codec at next module boot.

AT+CFUN=16
AT+UMCLK=0,0

Reset the module.
Disable the master clock.

AT+UEXTDCONF=0,0

Disable the external audio codec at next module boot.

AT+CPWROFF

Power off the module.

Switch off/on the general power supply of evaluation
board.

Power on.

AT+UMCLK=0,0

Stop the codec clock after the module reboot.

AT+UEXTDCONF=0,1;+CPWROFF

If the module and the external audio codec device
are powered separately (e.g.: on EVK), and therefore
codec setup is not reset, this procedure has be used fordisabling the external audio codec.
AT+UEXTDCONF=0,1,"0000000000000000000000000 Reprogram the external audio codec to init state at the00000000000";+CFUN=16
next module start-up.
If the module and the external audio codec device are
powered separately (e.g.: EVK), and therefore codec
setup is not reset,this is an alternative procedure fordisabling the external audio codec without powering off.

UBX-13002752 - R67

23 Audio interface

Page 599 of 1001

u-blox cellular modules - AT commands manual

TOBY-L2• The <hex_data> parameter is not supported.
• Behavior for +UEXTDCONF: 0,1: Maxim MAX9860 audio codec is programmed dynamically via I2C
commands every time the audio path is enabled, according to gains stored in file audio_gain_
calibration.xml. The +UVGC AT command can configure the settings. For more details, see TOBY-L2
series Audio Application Note [181].
SARA-U2 / LISA-U2• The <hex_data> parameter is not supported. The configuration for each supported device is hard-codedin the firmware.
• Behavior for +UEXTDCONF: 0,1: when module is powered on, it configures the external codec in equivalentmode to the following AT command sequence:
Command
AT+UI2CO=1,0,0,0x10,0Meaning
Open the I2C logical channel (connected to the external
codec).
AT+UI2CW="00000000101E3F2400000633004A00000 Send, via I2C, the specified byte sequence. Data are
08A",18
written in the external codec registers for codec
configuration (for the meaning of bytes and the writingin the codec's registers, see Maxim MAX9860 datasheet[55]).
o LISA-U200-01S / LISA-U200-02S / LISA-U200-52S /LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270 - This command is issued: AT+UI2CW="00000000108F20240000103300250000008A",18.
o SARA-U201-04A/
SARA-U201-04B/
SARA-U201-04X / LISA-U200-04B / LISA-U201-04B- This command is issued: AT+UI2CW="00000000
101E3F040000063300500000008A",18.
AT+UI2CW="049E",2Send, via I2C, the specified byte sequence (for external
codec configuration).
AT+UI2CC
Close the I2C logical channel.

SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• In case the AUX UART is enabled (that is the active +USIO variant is 4,5 or 6), since the I2C lines are
not available, the command immediately provides an error result code ("+CME ERROR: 3" if +CMEE=1
or "+CME ERROR: operation not allowed" if +CMEE=2).
LARA-R2 / TOBY-R2• Behavior for +UEXTDCONF: 0,1: when module is powered on, it configures the external codec in equivalentmode to the following AT command sequence:
Command
AT+UI2CO=1,0,0,0x10,0
AT+UI2CW=<hex_data>,18

AT+UI2CW=<hex_data_reg4>,2

AT+UI2CC

Meaning
Open the I2C logical channel (connected to the external
codec).
Read the <hex_data> configuration bytes from NVM
and send, via I2C, the byte sequence (for external codec
configuration).
Data are written in the external codec registers for codec
configuration (for the meaning of bytes and the writingin the codec's registers, see Maxim MAX9860 datasheet[55]).
Set high, via I2C, bit7 in register 0x04 of codec (<hex_
data_reg4> is "04xx", with xx byte is obtained setting highbit 7 in value reserved for codec's register 0x04 in <hex_data>; for the meaning of bytes, see Maxim MAX9860
datasheet [55]).
Close the I2C logical channel.

LARA-R211• In case the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02) is enabled (that is the active +USIO variant is 2,4,5 or 6), since the I2C lines are notavailable, the command immediately provides an error result code ("+CME ERROR: 3" if +CMEE=1 or"+CME ERROR: operation not allowed" if +CMEE=2).

UBX-13002752 - R67

23 Audio interface

Page 600 of 1001

u-blox cellular modules - AT commands manual

23.15 Speech codec information +USPEECHINFO+USPEECHINFO
Modules
TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L4906-01A TOBY-L4906-51A
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
Attributes
full
No
No
No
-

Error reference+CME Error

23.15.1 Description
Provides the speech codec related information and enables the corresponding +UUSPEECHINFO URC. The
URC is issued each time the speech codec changes.

23.15.2 Syntax
Type
Set

SyntaxAT+USPEECHINFO=<mode>

Response
OK

ExampleAT+USPEECHINFO=1

Read

AT+USPEECHINFO?

+USPEECHINFO: <mode>OK+USPEECHINFO: 1

Test

AT+USPEECHINFO=?

+USPEECHINFO: (list of supported<mode>s)OK+UUSPEECHINFO: <type>

URC

OK+USPEECHINFO: (0,1)
OK+UUSPEECHINFO: 0

23.15.3 Defined values
Parameter<mode>

Type
Number<type>

StringUBX-13002752 - R67

Description
Allowed values:• 0 (default value): disables the reporting of speech codec when it changes• 1: enables the speech codec reporting through the +UUSPECHINFO URC
Speech codec. Allowed values:• 0: codec GSM Full Rate (13.0 kb/s)• 1: codec GSM Half Rate (5.6 kb/s)• 2: codec GSM Enhanced Full Rate (12.2 kb/s)• 3: codec Full Rate Adaptive Multi-Rate• 4: codec Half Rate Adaptive Multi-Rate• 5: codec UMTS Adaptive Multi-Rate• 6: codec UMTS Adaptive Multi-Rate 2• 7: codec TDMA Enhanced Full Rate
• 8: codec PDC Enhanced Full Rate
• 9: codec Full Rate Adaptive Multi-Rate Wideband• 10: codec UMTS Adaptive Multi-Rate Wideband• 11: codec OHR Adaptive Multi-Rate• 12: codec OFR Adaptive Multi-Rate Wideband• 13: codec OHR Adaptive Multi-Rate Wideband

23 Audio interface

Page 601 of 1001

u-blox cellular modules - AT commands manual

23.16 Speech codec configuration +UDCONF=30+UDCONF=30
Modules

Attributes

TOBY-L4006 TOBY-L4106 TOBY-L4206 TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S
TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S
TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SARA-G340 SARA-G350 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

23.16.1 Description
Configures the allowed speech codec to be presented to the network during a voice call setup.
The supported codec list may vary for each product. The <supported_codec_bitmap> must be checked before
making any change.
The command does not affect VoLTE calls.
The new setting is saved in NVM and is immediately used.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

23.16.2 Syntax
Type
Set

SyntaxAT+UDCONF=30,<codec_bitmap>

Response
OK

Read

AT+UDCONF=30+UDCONF: 30,<active_codec_
bitmap>,<supported_codec_
bitmap>OK

ExampleAT+UDCONF=30,31
OK
AT+UDCONF=30+UDCONF: 30,31,255
OK

23.16.3 Defined values
Parameter<codec_bitmap>

Type
NumberDescription
Bitmask representing the list of available speech codecs to be presented to the
network during voice call setup. The supported speech codecs and the corresponding
bit in the bitmask are listed as follows:• 0: Full Rate Adaptive Multi-Rate (FR AMR)
• 1: GSM Enhanced Full Rate (12.2 kb/s) (GSM EFR)
• 2: GSM Full Rate (13.0 kb/s) (GSM FR)• 3: Half Rate Adaptive Multi-Rate (HR AMR)
• 4: GSM Half Rate (5.6 kb/s) (GSM HR)• 5: Full Rate Adaptive Multi-Rate WideBand (FR AMR WB)• 6: reserved• 7: reserved• 8: reserved• 9: UMTS Adaptive Multi-Rate (UMTS AMR)
• 10: UMTS Adaptive Multi-Rate 2 (UMTS AMR 2)• 11: UMTS Adaptive Multi-Rate WideBand (UMTS AMR WB)
GSM Full Rate must be always presented to the network, thus is always implicitly set.
See Table 81 for the meaning of each bit and codec availability.

UBX-13002752 - R67

23 Audio interface

Page 602 of 1001

u-blox cellular modules - AT commands manual

Parameter<active_codec_
bitmap><supported_codec_
bitmap>Type
NumberDescription
The currently active codecs, in the format described for <codec_bitmap>

Number

The list of currently supported codecs, in the format described for <codec_bitmap>

23.16.4 Notes
Bit
TOBY-L4
TOBY-L2
LARA-R202
LARA-R203
LARA-R211
LARA-R280
TOBY-R200
TOBY-R202
SARA-U2
SARA-U270-53S
LISA-U2
SARA-G3
LEON-G1

11
•
•
•

10
•
•
•

9

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•

8

7

6

•
•

5
•
•

4
•
•

3
•
•

2
•
•

1
•
•

0
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

Table 81: Speech codec bit availability on modules•

On product supporting 2G RAT the bit 2 (GSM Full Rate) in the <codec_bitmap> parameter is always
implicitly set to 1.

TOBY-L4• The factory-programmed value of <active_codec_bitmap> is 3135 (110000111111).
TOBY-L2• The factory-programmed value of <active_codec_bitmap> is 3647.
LARA-R211• The factory-programmed value of <active_codec_bitmap> is 63.
TOBY-R200• The factory-programmed value of <active_codec_bitmap> is 3647.
LARA-R202 / LARA-R280 / TOBY-R202• The factory-programmed value of <active_codec_bitmap> is 3584.
SARA-U2 / LISA-U2• The factory-programmed value of <active_codec_bitmap> is 3135.
SARA-U270-53S• The factory-programmed value of <active_codec_bitmap> is 1567, i.e. UMTS Adaptive Multi-Rate 2 is
not active.
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S• The bit 2 (GSM Full Rate) in <codec_bitmap> can be set to 0.
SARA-G340 / SARA-G350 / LEON-G1• The factory-programmed value of <active_codec_bitmap> is 31.

UBX-13002752 - R67

23 Audio interface

Page 603 of 1001

u-blox cellular modules - AT commands manual

23.17 Waiting call tone configuration +UDCONF=33+UDCONF=33
Modules
Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A TOBY-L280-03S
MPCI-L200-03S MPCI-L210-03S MPCI-L280-03S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

23.17.1 Description
Configures the volume or disables the waiting call tone locally generated.
The tone is generated during a voice call, when a second incoming call is in progress.
The new setting is saved in NVM and is immediately used at the next incoming call.

23.17.2 Syntax
Type
Set

SyntaxAT+UDCONF=33,<tone_volume>

Response
OK

ExampleAT+UDCONF=33,2

Read

AT+UDCONF=33+UDCONF: 33,<tone_volume>

OK
AT+UDCONF=33

OK+UDCONF: 33,2
OK

23.17.3 Defined values
Parameter<tone_volume>

Type
NumberDescription
Volume of the waiting call tone (the factory-programmed value is 4):• 0: waiting call supervisory tone disabled• 1-5: waiting call supervisory tone volume

23.18 Hardware audio path test +UMAAT+UMAAT
Modules
Attributes

TOBY-L4
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time<2s

Error reference+CME Error

23.18.1 Description
Generates a tone with specified frequency and amplitude while recording from microphone with a specified
bitrate and duration. Audio samples will be then automatically uploaded to the host once recording is done.
This command is used for hardware audio path test where the output from codec is redirected to themicrophone input which records the tone, usually the quality of this audio loop is then analyzed by an external
post-processing of the recorded samples.
The recording samples are returned in a WAV file ("WAV recording data") as a stream of bytes in a response
syntax similar to +URDFILE. Approximate size of the response can be calculated in bytes as:
2 * duration * sample_rate / 1000
The external codec must be already configured before using this command, for example by issuing+UEXTDCONF command (which enables automatically +UMCLK too).

23.18.2 Syntax
Type
Set

SyntaxResponse
AT+UMAAT=<frequency>,<sample_ +UMAAT: <size>,<data>
rate>,<duration>,<amplitude>[,OK<mic_id>]

ExampleAT+UMAAT=440,8000,600,5000+UMAAT: 12332,"WAV recording
data"
OK

UBX-13002752 - R67

23 Audio interface

Page 604 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+UMAAT=?

Response+UMAAT: (list of supported<frequency>s),(list of supported<sample_rate>s),(list of supported<duration>s),(list of supported<amplitude>s),(list of supported<mic_id>s)

Example+UMAAT: (100-3900),(8000,16000),(20-3000),(0-32767),(1,2)
OKOK

23.18.3 Defined values
Parameter<frequency>

Type
Number<sample_rate>

Number<duration>

Number<amplitude>

Number<mic_id>

Number<size><data>

NumberStringDescription
Frequency of the tone generated, in Hz:• TOBY-L4 - The allowed range is 100-3900 Hz.
Sample rate used for recording, in Hz:• TOBY-L4 - The allowed values are 8000 Hz and 16000 Hz.
Duration of the recording, in milliseconds:• TOBY-L4 - The allowed range is 20-3000 ms.
Amplitude of the tone generated:• TOBY-L4 - The allowed range is 0-32767.
Microphone ID used to select the microphone to do the recording:• 1 (default value): AMIC1 is used
• 2 : AMIC2 is used
Recorded sample size, in bytes
Recording content

23.18.4 Notes
TOBY-L4• The syntax of the information text response to the set command is +UMAAT: <size>. Then the user
should start receiving <size> bytes of file data on a dedicated channel of the USB CDC-ACM interface. At
the completion the "OK" final result code is displayed. The AT terminal is blocked until all data is sent.

UBX-13002752 - R67

23 Audio interface

Page 605 of 1001

u-blox cellular modules - AT commands manual

24 Audio parameters tuning
24.1 Introduction
All audio-featured u-blox modules integrate a speech processing system, which is a set of voiceband filters
required for transducer equalisation (external microphone and speaker), and a Speech Enhancement System(SES) dedicated to echo cancellation and noise reduction. The speech processing system has to be tuned byOEMs with respect to their audio set-up and use case (e.g. in-vehicle hands-free system) and tuned parameters
stored in the selected audio path (for more details, see the +USPM AT command).
Each path includes a set of parameters that are loaded by the audio driver in the speech processing system;
for example, the uplink path can include the microphone gain that can be different for handset or headset
microphone path.
For each audio path, the configuration of the uplink and downlink audio paths parameters is possible by meansof the following AT commands (where supported):Gain control:• AT+UMGC: microphone gain control• AT+USGC: speaker gain control• AT+USTN: sidetone• AT+UMAFE: microphone gains on analog front end (when an internal audio codec is supported)• AT+USAFE: speaker gains on analog front end (when an internal audio codec is supported)
Transducers equalisation (microphone, speaker):• AT+UUBF: uplink biquad filters• AT+UDBF: downlink biquad filters
Speech enhancement algorithms control and tuning for hands-free systems:• AT+UHFP: basic tuning (basic parameters of Speech Enhancement System (SES) in uplink)• AT+UTI: extended tuning (full control of Speech Enhancement System (SES) in uplink and downlink)
Some products present a different interface for gain control, transducers equalisation and algorithms tuning(where supported):• AT+UAPT: audio parameter tuning• AT+UVGC: volume gain control of external Maxim MAX9860 audio codec (connected via I2C)
The audio parameters configuration for all the audio paths can be stored in one of the two available user profiles
in NVM by AT&W command (where supported) or alternatively stored immediately by the AT command in thenon volatile memory (check the "Settings Saved" attribute of each command to know the storing modality ituses).
The audio parameters in the user profiles in NVM are managed by commands AT&W (it saves in profile 0 or
profile 1), AT&F (it resets to the factory profile), AT&Y (it selects user profile to be used after hardware reset),and ATZ (it reloads the user profile).
Setting of +UAPT and +UVGC, where supported, can also be stored in one of the two available user profiles in
NVM and recovered.
The AT&V command does not display the audio parameters settings. The audio parameters can be displayedby the corresponding read command, for example AT+UMGC?.
See the following subsections for an explanation of the audio path relations and position in the audio paths ofparts affected by audio parameters.

UBX-13002752 - R67

24 Audio parameters tuning

Page 606 of 1001

u-blox cellular modules - AT commands manual

24.1.1 TOBY-L2

I2S_RXD

To
Radio TX

HPF

EC

NS

RES

EQ

AGC

DRC

LPF
Volume &Mute

CNG

I2S_TXD

LPF
PCM
PlayerVolume& Mute

DRC

AGC

Tone
Generator

EQ

HPF

NS

From
Radio RXTOBY-L2 legend:
EC = Echo Cancellation
RES = Residual Echo Suppression
NS = Noise Suppression
LPF = Low Pass Filter
HPF = High Pass Filter
EQ = Equalizer
AGC = Additional Gain Control
DRC = Dynamic Range Compression
CNG = Comfort Noise Generator

Figure 13: TOBY-L2 series audio paths
•

•
•
•

•

•

The management and parameters tuning of audio paths can be configured by means of the following AT
commands:
o +UAPT (Audio Parameter Tuning): audio parameters management for all the signal processing blocks:- High Pass Filter (HPF)- Echo Cancellation (EC)
- Noise Suppression (NS)- Residual Echo Suppression (RES)- Equalizer (EQ)
- Additional Gain Control (AGC)- Dynamic Range Compression (DRC)- Low Pass Filter (LPF)
o +USPM (Set Path Mode)o +UVGC (Volume Gain Control): gains of external Maxim MAX9860 audio codec (connected via I2C
interface)o +CLVL(Loudspeaker Volume Level): sets the downlink Volume & Mute
Sidetone must be generated by the external codec connected via I2C interface). For sidetone control on
Maxim MAX9860 audio codec, see +UVGC (Volume Gain Control).
The audio parameters configuration for all the audio paths can be stored in the user profiles by AT&W. The
audio parameters configuration can be restored to factory-programmed values by AT&F.
The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The module supports the following speech codecs for UMTS:
o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The tone generator generates the tones (see +UTGN command) and the pre-defined tones (see +UPAR
command), the alarm tone (see +CALA command). The PCM player (see +UPLAYFILE command) is usedby the ringer tones on an incoming call and SMS reception tone. See also +CRSL command and +CALM
command.

UBX-13002752 - R67

24 Audio parameters tuning

Page 607 of 1001

u-blox cellular modules - AT commands manual

24.1.2 TOBY-L4

Figure 14: TOBY-L4 series audio analog path

Figure 15: TOBY-L4 series audio digital path•

The management and parameters tuning of audio paths and profiles can be configured by means of thefollowing interfaces:o +UTI- FIR/IIR equalizers for microphones and loudspeakers (FIR/IIR)- Echo Cancellation (EDL, NLF, AEC)
- Noise Suppressors in uplink/downlink (NR, Spatial noise SNS, Wind noise WNR, Traffic noise TNR)
- Residual Echo Suppressors (SER, AGC)
- Beamformer (BMF)- Dynamic Range Processors (Companders) in uplink/downlink (DRP)- Ambient Noise Adapter (ANA)- Gain scal_speech_out_cal_offset/scal_speech_in_offset on Uplink/Downlink path
- Gains scal_i2s_in_offset/scal_i2s_out_offset on I2S1/I2S2- Gain Control on downlink (GLC)- Comfort Noise Injectors (CNI)o +USPM (Set Path Mode)o +UMSEL (Select microphone AMIC1/AMIC2 on analog path)o +UMAFE (Microphone gains analog_gain,adc_gain control on analog path)o +USAFE (Speaker gains analog_gain,dac_gain_coarse/fine control on analog path)o +UMGC (Microphone gain scal_i2s_in control on I2S interface)o +USGC (Speaker gain scal_i2s_out control on I2S interface)

UBX-13002752 - R67

24 Audio parameters tuning

Page 608 of 1001

u-blox cellular modules - AT commands manual•••o +CLVL (Downlink Speech Level control by scal_speech_in)o +CMUT (Uplink Speech Muting control by scal_speech_out_cal)
The audio parameters configuration for all the audio paths can be stored in the user profiles by +UTI. The
audio parameters configuration can be restored to factory-programmed values by +UTIThe module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The module supports the following speech codecs for UMTS:
o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)

24.1.3 LARA-R2 / TOBY-R2
LARA-R204 / LARA-R220
The audio interface is not supported.

Figure 16: LARA-R211 audio paths

UBX-13002752 - R67

24 Audio parameters tuning

Page 609 of 1001

u-blox cellular modules - AT commands manual

Figure 17: TOBY-R2 / LARA-R202 / LARA-R203 / LARA-R280 / LARA-R281 / LARA-R211-02B-00 /LARA-R211-02B-01 / LARA-R211-02B-02 audio paths
•

•
•
•

•

•
•
•
•
•
•
•

Allowed values for audio path tuning:o <uplink_path_num>- 0: uplink path 0 via I2S- 1: uplink path 1 via I2S- 2: uplink path 2 via I2S- 3: uplink path 3 via I2S- 4: uplink path 4 via I2S
o <downlink_path_num>- 0: downlink path 0 via I2S- 1: downlink path 1 via I2S- 2: downlink path 2 via I2S- 3: downlink path 3 via I2S- 4: downlink path 4 via I2S
For downlink path, biquad filters 1-4 are used with speech codec at 8 kHz sampling rate, filters 1-5 are usedwith speech codec at 16 kHz sampling rate.
For uplink path, uplink biquad filters 5-8 are used if the I2S sampling rate is 16 kHz, uplink biquad filters 1-4
for all the others I2S sampling rates.
The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The module supports the following speech codecs for UMTS:
o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The +CLVL command sets the downlink Speech level
The +UDBF command sets the biquad filters (EQ) on the downlink path.
A noise reduction (NR) block reduces the noise on the downlink speech.
The <scal_rec> parameter in +USGC command controls the Scal_Rec digital gain.
The <digital_gain> parameter in +UMGC command controls the Scal_Mic digital gain.
The +UUBF command sets the biquad filters (EQ) on the uplink path.
The +UHFP command controls the Speech Enhancement System (SES), for easy tuning.

UBX-13002752 - R67

24 Audio parameters tuning

Page 610 of 1001

u-blox cellular modules - AT commands manual•••

The +UTI command controls the Speech Enhancement System (SES) in uplink and downlink.
The +USTN command controls the Sidetone.
The tone generator generates the tones (see +UTGN command), the pre-defined tones and MIDI melodies(see +UPAR command), the alarm tone (see +CALA command), the ringer tones on an incoming call,
SMS reception tone and the service tones (e.g.: Call Waiting tone). They are affected by the <Scal_Rec>
digital gain (see +USGC command). The PCM player (see +UPLAYFILE command) is affected by <Mix_afe>
parameter (see +USGC command). See also +CRSL command and +CALM command.

24.1.4 SARA-U2

Figure 18: Audio paths of SARA-U2 "04" product versions

UBX-13002752 - R67

24 Audio parameters tuning

Page 611 of 1001

u-blox cellular modules - AT commands manual

Figure 19: Audio paths of SARA-U2 "00", "03", "53", "63", "73" product versions
•

•
•
•

•

•
•
•
•
•
•
•
•

Allowed values for audio path tuning:o <uplink_path_num>- 0: uplink path 0 via I2S- 1: uplink path 1 via I2S- 2: uplink path 2 via I2S- 3: uplink path 3 via I2S- 4: uplink path 4 via I2S
o <downlink_path_num>- 0: downlink path 0 via I2S- 1: downlink path 1 via I2S- 2: downlink path 2 via I2S- 3: downlink path 3 via I2S- 4: downlink path 4 via I2S
For downlink path, biquad filters 1-4 are used with speech codec at 8 kHz sampling rate, filters 1-5 are usedwith speech codec at 16 kHz sampling rate.
For uplink path, uplink biquad filters 5-8 are used if the I2S sampling rate is 16 kHz, uplink biquad filters 1-4
for all the others I2S sampling rates.
The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The module supports the following speech codecs for UMTS:
o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The +CLVL command sets the downlink Speech level
The +UDBF command sets the biquad filters (EQ) on the downlink path.
A noise reduction (NR) block reduces the noise on the downlink speech.
The <scal_rec> parameter in +USGC command controls the Scal_Rec digital gain.
The <digital_gain> parameter in +UMGC command controls the Scal_Mic digital gain.
The +UUBF command sets the biquad filters (EQ) on the uplink path.
The +UHFP command controls the Speech Enhancement System (SES), for easy tuning.
The +UTI command controls the Speech Enhancement System (SES) in uplink and downlink.

UBX-13002752 - R67

24 Audio parameters tuning

Page 612 of 1001

u-blox cellular modules - AT commands manual••

The +USTN command controls the Sidetone.
The tone generator generates the tones (see +UTGN command), the pre-defined tones and MIDI melodies(see +UPAR command), the alarm tone (see +CALA command), the ringer tones on an incoming call,
SMS reception tone and the service tones (e.g.: Call Waiting tone). They are affected by the <Scal_Rec>
digital gain (see +USGC command). The PCM player (see +UPLAYFILE command) is affected by <Mix_afe>
parameter (see +USGC command). See also +CRSL command and +CALM command.

24.1.5 LISA-U2

Figure 20: Audio paths of LISA-U2 "04" product versions

Figure 21: Audio paths of LISA-U2 "00", "01", "02", "03", "52", "62", "63", "68", "82", "83" product versions

UBX-13002752 - R67

24 Audio parameters tuning

Page 613 of 1001

u-blox cellular modules - AT commands manual

•

•
•
•

•

•
•
•
•
•
•
•
•
•

Allowed values for audio path tuning:o <uplink_path_num>- 0: uplink path 0 via I2S- 1: uplink path 1 via I2S- 2: uplink path 2 via I2S- 3: uplink path 3 via I2S- 4: uplink path 4 via I2S- 5: uplink path 5 via I2S1
- 6: uplink path 6 via I2S1
- 7: uplink path 7 via I2S1
- 8: uplink path 8 via I2S1
- 9: uplink path 9 via I2S1
o <downlink_path_num>- 0: downlink path 0 via I2S- 1: downlink path 1 via I2S- 2: downlink path 2 via I2S- 3: downlink path 3 via I2S- 4: downlink path 4 via I2S- 5: downlink path 5 via I2S1
- 6: downlink path 6 via I2S1
- 7: downlink path 7 via I2S1
- 8: downlink path 8 via I2S1
- 9: downlink path 9 via I2S1
For downlink path, biquad filters 1-4 are used with speech codec at 8 kHz sampling rate, filters 1-5 are usedwith speech codec at 16 kHz sampling rate.
For uplink path, uplink biquad filters 5-8 are used if the I2S sampling rate is 16 kHz, uplink biquad filters 1-4
for all the others I2S sampling rates.
The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The module supports the following speech codecs for UMTS:
o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The +CLVL command sets the downlink Speech level.
The +UDBF command sets the biquad filters (EQ) on the downlink path.
A noise reduction (NR) block reduces the noise on the downlink speech.
The <scal_rec> parameter in +USGC command controls the Scal_Rec digital gain.
The <digital_gain> parameter in +UMGC command controls the Scal_Mic digital gain.
The +UUBF command sets the biquad filters (EQ) on the uplink path.
The +UHFP command controls the Speech Enhancement System (SES).
The +USTN command controls the Sidetone.
The tone generator generates the tones (see +UTGN command), the pre-defined tones and MIDI melodies(see +UPAR command), the alarm tone (see +CALA command), the ringer tones on an incoming call,
SMS reception tone and the service tones (e.g.: Call Waiting tone). They are affected by the <Scal_Rec>
digital gain (see +USGC command). The PCM player (see +UPLAYFILE command) is affected by <Mix_afe>
parameter (see +USGC command). See also +CRSL command and +CALM command.

UBX-13002752 - R67

24 Audio parameters tuning

Page 614 of 1001

u-blox cellular modules - AT commands manual

24.1.6 LISA-U120 / LISA-U130

Figure 22: LISA-U1 series audio paths
•

•
•

•

•
•
•
•
•
•
•

Allowed values for audio path tuning:o <uplink_path_num>- 0: handset microphone (pins: MIC_P, MIC_N)- 1: headset microphone (pins: MIC_P, MIC_N)- 2: I2S input line (pin I2S_RXD)- 4: hands-free microphone (pins: MIC_P, MIC_N)o <downlink_path_num>- 0: normal earpiece (pins: SPK_N, SPK_P)- 1: mono headset (pins: SPK_N, SPK_P)- 3: loudspeaker (pins: SPK_N, SPK_P)- 4: I2S output line (pin I2S_TXD)
For both uplink and downlink paths, biquad filters 1-4 are used with speech codec at 8 kHz sampling rate,
filters 1-5 are used with speech codec at 16 kHz sampling rate.
The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The module supports the following speech codecs for UMTS:
o NB-AMR speech codec (8 kHz sampling rate)o WB-AMR speech codec (16 kHz sampling rate)
The +CLVL command sets the downlink Speech Level
The +UDBF command sets the biquad filters (DBF) on the downlink path.
The +USGC command controls the Scal_Rec digital gain and the HS (headset) analog gain.
The +UMGC command controls the Scal_Mic digital gain and the Microphone analog gain.
The +UUBF command controls the biquad filters (UBF) on the uplink path.
The +UHFP command controls the Speech Enhancement System (SES).
The +USTN command controls the Sidetone.

24.1.7 SARA-G4
SARA-G450-00C
The audio interface is not supported.

UBX-13002752 - R67

24 Audio parameters tuning

Page 615 of 1001

u-blox cellular modules - AT commands manual

Figure 23: SARA-G4 series audio paths•••

The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)
The +CLVL AT command sets the downlink Speech level and the downlink Ringer level
The +CRSL AT command sets the downlink Speech level, the downlink Ringer level and the Players level(+UPAR, +UPLAYFILE)

24.1.8 SARA-G340 / SARA-G350

Figure 24: SARA-G3 series audio paths•

Allowed values for audio path tuning:o <uplink_path_num>- 0: handset microphone (pins: MIC_P, MIC_N, MIC_BIAS, MIC_GND)- 1: headset microphone (pins: MIC_P, MIC_N, MIC_BIAS, MIC_GND)- 2: I2S input line (pin I2S_RXD)- 4: hands-free microphone (pins: MIC_P, MIC_N, MIC_BIAS, MIC_GND)o <downlink_path_num>- 0: normal earpiece (pins: SPK_N, SPK_P)

UBX-13002752 - R67

24 Audio parameters tuning

Page 616 of 1001

u-blox cellular modules - AT commands manual

•

•
•
•
•
•
•
•
•

- 1: mono headset (pins: SPK_N, SPK_P)- 3: loudspeaker (pins: SPK_N, SPK_P)- 4: I2S output line (pin I2S_TXD)
The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o All these codecs are based on a 8 kHz sampling rate, thus all the biquad filters work at 8 kHz samplingrate.
The +CLVL command sets the downlink Speech Level
The +UDBF command sets the biquad filters (DBF) on the downlink path.
The +USGC command controls the Scal_Rec and Gain_out digital gains and the SPK analog gain.
The +UMGC command controls the Scal_Mic digital gain and the Uplink analog gain.
The +UUBF command controls the biquad filters (UBF) on the uplink path.
The +UHFP command controls the Speech Enhancement System (SES).
The +USTN command controls the Sidetone.
The tone generator generate the tones (see the +UTGN command), the pre-defined tones (see the +UPAR
command), the alarm tone (see the +CALA command), the SMS reception tone and service tones (e.g.:
Call Waiting tone). They are affected by <Gain_out>, <Scal_Rec> and <Analog_gain> parameters (see the+USGC command). The MIDI melodies (see the +UPAR command) and ringer tones on an incoming callare generated by the MIDI player and their volume is affected by <Mix_afe> parameter (see the +USGC
command). The AMR player (see the +UPLAYFILE command) is affected by <Gain_out>, <Scal_Rec> and<Analog_gain> parameters (see the +USGC command). See also +CRSL command and +CALM command.

24.1.9 LEON-G1
I2S_RXD

I2Sx RXMIC1
MIC2

I2Sy RX

SwitchMultiplexer

ADC

UplinkAnalog Gain

SwitchUBF 1
Scal_Mic
Digital Gain

UBF 2

SwitchTo
Radio TX

Hands-Free

Tone
Generator

Sidetone

SPK_P/N
SPK
Analog
Gain
HS_P

DAC

Switch

DBF 2

DBF 1

Scal_Rec
Digital Gain

Gain_Out
Digital Gain

I2Sx TX

SwitchI2S_TXD

Mix_AFE
Digital Gain

SpeechLevel
AMR
PlayerMIDI Player

HS_P
Analog Gain

FromRadio RX

SwitchI2Sy TX

Legend:UBF = Uplink Biquad Filter
DBF = Downlink Biquad Filter

Figure 25: LEON-G1 series audio paths•

Allowed values for audio path tuning:o <uplink_path_num>- 0: handset microphone (pins: MIC_BIAS1, MIC_GND1)- 1: headset microphone (pins: MIC_BIAS2, MIC_GND2)- 2: I2S input line (pin I2S_RXD)
o <downlink_path_num>- 0: normal earpiece (pins: HS_P, GND)
- 1: mono headset (pins: HS_P, GND)
- 3: loudspeaker (pins: SPK_P, SPK_N)

UBX-13002752 - R67

24 Audio parameters tuning

Page 617 of 1001

u-blox cellular modules - AT commands manual

•

•
•
•
•
•
•
•
•

- 4: I2S output line (pin I2S_TXD)
The module supports the following speech codecs for GSM:
o Full Rate speech codec (8 kHz sampling rate)o Enhanced Full Rate speech codec (8 kHz sampling rate)o Half Rate speech codec (8 kHz sampling rate)o NB-AMR speech codec (8 kHz sampling rate)o All these codecs are based on a 8 kHz sampling rate, thus all the biquad filters work at 8 kHz samplingrate.
The +CLVL command sets the downlink Speech Level
The +UDBF command sets the biquad filters (DBF) on the downlink path.
The +USGC command controls Scal_Rec and Gain_out digital gains, the HS_P (Headset) and the SPK(speaker) analog gains.
The +UMGC command controls the Scal_Mic digital gain and the Uplink analog gain.
The +UUBF command controls the biquad filters (UBF) on the uplink path.
The +UHFP command controls the Speech Enhancement System (SES).
The +USTN command controls the Sidetone.
The tone generator generate the tones (see the +UTGN command), the pre-defined tones (see the +UPAR
command), the alarm tone (see the +CALA command), the SMS reception tone and service tones (e.g.:
Call Waiting tone). They are affected by <Gain_out>, <Scal_Rec> and <Analog_gain> parameters (see the+USGC command). The MIDI melodies (see the +UPAR command) and ringer tones on an incoming callare generated by the MIDI player and their volume is affected by <Mix_afe> parameter (see the +USGC
command). The AMR player (see the +UPLAYFILE command) is affected by <Gain_out>, <Scal_Rec> and<Analog_gain> parameters (see the +USGC command). See also +CRSL command and +CALM command.

24.1.10 Notes
The tone generator can be routed toward downlink and/or uplink path by <UplinkSending> parameter of+UTGN command.
The audio parameters in the factory-programmed profile are stored in static NVM and the user cannot change
them.
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G340 / SARA-G350•••

Some parameters present on LEON-G1 series are not available but they are still maintained in thecommand for backward compatibility. In this case the 'NA' string appears in the information text
response to the test command; the NA parameter is not stored in the NVM.
E.g.:
AT+USGC?
+USGC:Path 0:NA,0,8192,16384,NA
The range of some parameters is extended respect to LEON-G1 series:
E.g: <filter_number> in +UUBF, +UDBF commands.
Some commands support new parameters. In this case these parameters are optional, for backward
compatibility.
E.g.:<ec_nr_coeff_real> in +UHFP command.

LARA-R2 / TOBY-R2••

Some parameters present on LEON-G1 series are not available but they are still maintained in thecommand for backward compatibility. In this case the 'NA' string appears in the information text
response to the test command; the NA parameter is not stored in the NVM.
E.g.:
AT+USGC?
+USGC:Path 0:NA,0,8192,16384,NA
The range of some parameters is extended respect to LEON-G1 series:

UBX-13002752 - R67

24 Audio parameters tuning

Page 618 of 1001

u-blox cellular modules - AT commands manual•

E.g: <filter_number> in +UUBF, +UDBF commands.
Some commands support new parameters. In this case these parameters are optional, for backward
compatibility.
E.g.:<ec_nr_coeff_real> in +UHFP command.

The speech level is active on call only (no effect on PCM player if not in call).

24.2 Microphone gain (Microphone Gain Control) +UMGC+UMGC
Modules

Attributes

TOBY-L4
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
ProfileNo+CME Error

24.2.1 Description
Configures the uplink path gain.
The command syntax differs between different module series.
See Chapter 24.1 for the position of amplifiers in the audio path.
Not all the paths are supported. Check the allowed <uplink_path_num> values in the test command
response.
Any change in the gain on uplink or downlink path impacts on the amount of echo fed back from the
speaker to the microphone. This means that performance of EC algorithm could change and parameters
could need to be changed to better fit new gain on uplink or downlink path. See the +UHFP commanddescription.

24.2.2 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 syntax
Type
Set

SyntaxAT+UMGC=<uplink_path_num>,<analog_gain>,<digital_gain>

Response
OK

ExampleAT+UMGC=1,12,16000

Read

AT+UMGC?

+UMGC:

OK+UMGC:Path <uplink_path_num>:

Path 0:<analog_gain>,<digital_gain>

10,9384[...]

Path 1:(for all the supported paths)

12,8192

OK

Path 2:6,8192

Test

AT+UMGC=?

+UMGC: (list of supported <uplink_
path_num>s),(list of supported<analog_gain>s),(list of supported<digital_gain>s)

OK+UMGC: (0-9),(0-14),(0-32767)
OK

OK

UBX-13002752 - R67

24 Audio parameters tuning

Page 619 of 1001

u-blox cellular modules - AT commands manual

24.2.3 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 defined values
ParameterType<uplink_path_num> Number<analog_gain><digital_gain>

NumberNumberDescription
Specifies the uplink path where the gains must be configured.
For uplink paths range and physical meaning, see the product specific section in the
Chapter 24.1:• LARA-R2 / TOBY-R2 series - Chapter 24.1.3• SARA-U2 series - Chapter 24.1.4• LISA-U2 series - Chapter 24.1.5• LISA-U120 / LISA-U130 - Chapter 24.1.6• SARA-G340 / SARA-G350 - Chapter 24.1.8• LEON-G1 series - Chapter 24.1.9
Gain for analog audio front end amplifier:• Range: 0 - 14 (0=0 dB; 14=42 dB; 3 dB/step)
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
The parameter is not available: 'NA' is provided in the test command.
Gain for Scal_mic digital amplifier:• Range: 0 - 32767 (8192=0 dB; 32767=12 dB; linear)

24.2.4 TOBY-L4 syntax
Type
Set

SyntaxAT+UMGC=<digital_level_index>

Response
OK

ExampleAT+UMGC=90

Read

AT+UMGC?

+UMGC: <digital_level_index>

OK+UMGC: 90

Test

AT+UMGC=?

OK
OK+UMGC: (list of supported <digital_ +UMGC: (0-100)
level_index>es)OKOK

24.2.5 TOBY-L4 defined values
ParameterType<digital_level_index> Number

Description
Digital gain of scal_i2s_in:• Range: 0 - 100 (0=mute; 100=+6 dB; the step size is 0.5 dB (e.g.: 88 means 0 dB)• The factory-programmed value is 88.

24.2.6 Notes
TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.
• Controls the digital gain scal_i2s_in of the i2s port (see Chapter 24.1.2) for the currently active audio pathmode (i.e. the combination of an audio path and audio profile selected by +USPM). The gain is available
for each audio path mode.
• When the user selects the audio path mode +USPM, the digital gain scal_i2s_in of the i2s port connectedto the audio path for that profile type is used.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• <analog_gain> is unused and not mandatory. If not omitted, a value belonging to the range must be
provided in the set command. 'NA' is provided in the information text response to the read command.
• The factory-programmed values for all the paths are set to NA (<analog_gain> parameter) and 8192(<digital_gain>).
LISA-U120 / LISA-U130• The factory-programmed values are set as follows:o Path 0: <analog_gain>=12 and <digital_gain>=8192.
o Path 1: <analog_gain>=12 and <digital_gain>=8192.

UBX-13002752 - R67

24 Audio parameters tuning

Page 620 of 1001

u-blox cellular modules - AT commands manualo Path 2: <analog_gain>=6 and <digital_gain>=8192.
o Path 4: <analog_gain>=13 and <digital_gain>=8192.
SARA-G340 / SARA-G350• The factory-programmed values are set as follows:o Path 0: <analog_gain>=10 and <digital_gain>=8192.
o Path 1: <analog_gain>=10 and <digital_gain>=8192.
o Path 2: <analog_gain>=6 and <digital_gain>=8192.
o Path 4: <analog_gain>=10 and <digital_gain>=8192.
LEON-G1• <uplink_path_num>=4 is not supported.
• The factory-programmed values are set as follows:o Path 0: <analog_gain>=10 and <digital_gain>=9384.
o Path 1: <analog_gain>=12 and <digital_gain>=8192.
o Path 2: <analog_gain>=6 and <digital_gain>=8192.

24.3 Speaker Gain (Speaker Gain Control) +USGC+USGC
Modules

Attributes

TOBY-L4
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
ProfileNo+CME Error

24.3.1 Description
Configures the audio downlink path gain.
The command syntax differs between different module series.
See Chapter 24.1 for the position of amplifiers in the audio path.
Not all the paths are supported, see +USPM command description for the supported paths.
Any change in the gain on uplink or downlink path impacts on the amount of echo fed back from the
speaker to the microphone. This means that performance of EC algorithm could change and parameters
could need to be changed to better fit new gain on uplink or downlink path. See the +UHFP commanddescription).

24.3.2 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 syntax
Type
Set

Read

SyntaxResponse
AT+USGC=<downlink_path_num>[, OK<SPK_analog_gain>],<HS_analog_
gain>,<scal_rec>,<Mix_afe>[,<Gain_
out>]
AT+USGC?
+USGC:Path <downlink_path_num>:

ExampleAT+USGC=0,6,6,16000,16000,2200
0OK+USGC:Path 0:<SPK_analog_gain>,<HS_analog_
6,6,16000,16000,22000
gain>,<scal_rec>, <Mix_afe>,<Gain_
Path 1:
Out>
6,0,8192,16384,10240[...]
Path 3:(for all the supported path)
0,6,8192,16384,8191
OK
Path 4:UBX-13002752 - R67

24 Audio parameters tuning

Page 621 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Test

AT+USGC=?

+USGC: (list of supported<downlink_path_num>s),(list of
supported <SPK_analog_gain>s),(list of supported <HS_analog_
gain>s),(list of supported <scal_
rec>s),(list of supported <Mix_afe>s),(list of supported <Gain_
out>s)

Example6,6,8192,16384,8191
OK+USGC: (0-9),(0-6),(0-6),(0-32767),(0-32767),(0-32767)
OKOK

24.3.3 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 /LEON-G1 defined values
Parameter<downlinkpath_
num>

Type
Number<SPK_analog_gain> Number<HS_analog_gain>

Number<scal_rec>Number<Mix_afe>

Number<Gain_out>

NumberDescription
Specifies the downlink path where the gains must be configured.
For downlink paths range and physical meaning, see the product specific section in
the Chapter 24.1:• LARA-R2 / TOBY-R2 series - Chapter 24.1.3• SARA-U2 series - Chapter 24.1.4• LISA-U2 series - Chapter 24.1.5• LISA-U120 / LISA-U130 - Chapter 24.1.6• SARA-G340 / SARA-G350 - Chapter 24.1.8• LEON-G1 series - Chapter 24.1.9
Gain of analog audio amplifier for SPK_P/SPK_N outputs:• LEON-G1 series - the range goes from 0 to 6 (-3 dB/step; 0=+9 dB to 6=-9 dB)• SARA-G340 / SARA-G350 - the range goes from 0 to 5 (-3 dB/step; 0=+9 dB to 5=-6 dB)
Gain of analog audio amplifier for SPK_P/SPK_N outputs:• LISA-U120 / LISA-U130 / LEON-G1 series - the range goes from 0 to 6 (-3 db/step;
0=0 dB to 6= -18 dB)
Gain of the Scal_rec digital amplifier (speech and tone generator):• Range: 0 - 32767 (8192=0 dB; 32767=12 dB; linear)
Gains of the Mix_afe digital amplifier (synthesizers):• Range: 0 - 32767 (16384=0 dB; 32767=6 dB; linear)Gain of the Gain_Out digital amplifier (speech):• Range: 0 - 32767 (8192=0 dB; 32767=12 dB; linear)

24.3.4 TOBY-L4 syntax
Type
Set

SyntaxAT+USGC=<digital_level_index>

Response
OK

ExampleAT+USGC=90

Read

AT+USGC?

+USGC: <digital_level_index>

OK+USGC: 90

Test

AT+USGC=?

OK+USGC: (list of supported <digital_level_index>es)

OK+USGC: (0-100)
OKOK

24.3.5 TOBY-L4 defined values
ParameterType<digital_level_index> Number

UBX-13002752 - R67

Description
Digital gain of the scal_i2s_out:• Range: 0 - 100 (0=mute; 100=+6 dB; the step size is 0.5 dB (e.g.: 88 means 0 dB)• The factory-programmed value is 88.

24 Audio parameters tuning

Page 622 of 1001

u-blox cellular modules - AT commands manual

24.3.6 Notes
TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.
• Controls the digital gain scal_i2s_out of the i2s port (see Chapter 24.1.2) for the currently active audio pathmode (i.e. the combination of an audio path and audio profile selected by +USPM). The gain is available
for each audio path mode.
• When the user selects the audio path mode with +USPM, the digital gain scal_i2s_out of the i2s port
connected to the audio path for that profile type is used.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• <SPK_analog_gain>, <HS_analog_gain> and <Gain_out> are unused and not mandatory. If not omitted,
a value belonging to the range must be provided in the set command. 'NA' is provided in the informationtext response to the read command.
• The factory-programmed values are set as follows:o <SPK_analog_gain> not available for all the paths.
o <HS_analog_gain> not available for all the paths.
o <scal_rec>= 8192 for all the paths.
o <Mix_afe>= 16384 for all the paths.
o <Gain_out> not available for all the paths.
LISA-U1• <SPK_analog_gain> and <Gain_out> are unused and not mandatory. 'NA' is provided in the test
command.
• The factory-programmed values are set as follows:o <SPK_analog_gain> not available for all the paths.
o <HS_analog_gain>= 0 for the path 0, <HS_analog_gain>= 1 for the path 1, <HS_analog_gain>= 0 for
the path 3, <HS_analog_gain>= 3 for the path 4.
o <scal_rec>= 8192 for all the paths.
o <Mix_afe>= 16384 for all the paths.
o <Gain_out> not available for all the paths.
SARA-G340 / SARA-G350• <HS_analog_gain> and <Mix_afe> are unused and not mandatory. 'NA' is provided in the test command.
• The factory-programmed values are set as follows:o <SPK_analog_gain>=3 for path 0, 1, 3 and <SPK_analog_gain>=5 for path 4.
o <HS_analog_gain>=3 for path 0, 1, 3 and <SPK_analog_gain>=0 for path 4.
o <scal_rec>= 8192 for all the paths.
o <Mix_afe>= 16384 for all the paths.
o <Gain_out>= 8192 for all the paths.
LEON-G1• The factory-programmed values are set as follows:o <SPK_analog_gain>=6 for path 0, 1, 4 and <SPK_analog_gain>=0 for path 3.
o <HS_analog_gain>=1 for path 0, <HS_analog_gain>=0 for path 1, <HS_analog_gain>=6 for path 3
and 4.
o <scal_rec>= 8192 for all the paths.
o <Mix_afe>= 16384 for all the paths.
o <Gain_out>= 8192 for path 0, <Gain_out>= 10240 for path 1, <Gain_out>= 8191 for path 3 and 4.

UBX-13002752 - R67

24 Audio parameters tuning

Page 623 of 1001

u-blox cellular modules - AT commands manual

24.4 Sidetone configuration +USTN+USTN
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
fullNoProfileNo+CME Error

Attributes

24.4.1 Description
Configure the sidetone gain for a specific downlink path. The sidetone is a part of the user's speech on uplink
path that should be listened on downlink path by the user himself to have perception the call is on.
Not all the paths are supported, see +USPM for the supported paths.
See Chapter 24.1 for the position of sidetone gain in the audio path.

24.4.2 Syntax
Type
Set

SyntaxAT+USTN=<downlink_path_num>,<sidetone_gain>

Response
OK

ExampleAT+USTN=1,1000

Read

AT+USTN?

+USTN:OK+USTN:Path <downlink_path_num>:

Path 0:<sidetone_gain>

2249[...] (all the supported paths)

Path 1:

OK

2249.......

Test

AT+USTN=?

+USTN: (list of supported<downlink_path_num>s),(list of
supported <sidetone_gain>s)OK+USTN: (0-9),(0-32767)
OKOK

24.4.3 Defined values
Parameter<downlink_path_
num>

Type
Number<sidetone_gain>

NumberDescription
Specifies the downlink path where the sidetone must be configured.
For downlink paths range and physical meaning, see the product specific section in
the Chapter 24.1:• LARA-R2 / TOBY-R2 series - Chapter 24.1.3• SARA-U2 series - Chapter 24.1.4• LISA-U2 series - Chapter 24.1.5• LISA-U120 / LISA-U130 - Chapter 24.1.6• SARA-G340 / SARA-G350 - Chapter 24.1.8• LEON-G1 series - Chapter 24.1.9.
Gain for sidetone digital amplifier:• Range: 0 - 32767: (16384=0 dB; 32767=6 dB; linear)
The factory-programmed value is 512 for all the downlink paths.

24.4.4 Notes
LISA-U120 / LISA-U130 / SARA-G340 / SARA-G350• The factory-programmed value is 512 for the downlink path 0 and 1.
• The factory-programmed value is 0 for the downlink path 3 and 4.

UBX-13002752 - R67

24 Audio parameters tuning

Page 624 of 1001

u-blox cellular modules - AT commands manual

LEON-G1• The factory-programmed value is 2249 for the downlink path 0 and 1.
• The factory-programmed value is 0 for the downlink path 3 and 4.

24.5 Uplink Digital Filters (Uplink Biquad Filters) +UUBF+UUBF
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
ProfileNo+CME Error

24.5.1 Description
Sets the digital audio filters parameters for a specific uplink path.
See Chapter 24.1 for the position of the filters in the audio path.
Not all the paths are supported, see +USPM command description for the supported paths.

24.5.2 Syntax
Type
Set

SyntaxAT+UUBF=<uplinkpath_num>,<filter_number>,<a1>,<b1>,<a2>,<b2>,<a0>

Response
OK

Read

AT+UUBF?

+UUBF:OK+UUBF:Path <uplinkpath_num>:

Path 0:Filter1: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter1: a1:0, b1:0, a2:0, b2:0, a0:32767Filter2: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter2: a1:0, b1:0, a2:0, b2:0, a0:32767Filter3: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter3: a1:0, b1:0, a2:0, b2:0, a0:32767Filter4: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter4: a1:0, b1:0, a2:0, b2:0, a0:32767[...]Filter5: a1:0, b1:0, a2:0, b2:0, a0:32767(for all the supported paths)
OK

ExampleAT+UUBF=0,1,-13915,2249,4377,325,23450

Filter6: a1:0, b1:0, a2:0, b2:0, a0:32767Filter7: a1:0, b1:0, a2:0, b2:0, a0:32767Filter8: a1:0, b1:0, a2:0, b2:0, a0:32767[repeated for each path]

Test

AT+UUBF=?

OK+UUBF: (list of supported+UUBF: (0-9),(1-8),(-32768:32767),<uplinkpath_num>s),(list of(-32768:32767),(-32768:32767),(supported <filter_number>s),(list of 32768:32767),(-32768:32767)
supported <a1>s),(list of supported
OK<b1>s),(list of supported <a2>s),(list of supported <b2>s),(list of
supported <a0>s)
OK

UBX-13002752 - R67

24 Audio parameters tuning

Page 625 of 1001

u-blox cellular modules - AT commands manual

24.5.3 Defined values
ParameterType<uplink_path_num> Number

Description
Specifies the uplink path where the digital filters must be configured.
For uplink paths range and physical meaning, see the product specific section in the
Chapter 24.1:• LARA-R2 / TOBY-R2 series - Chapter 24.1.3• SARA-U2 series - Chapter 24.1.4• LISA-U2 series - Chapter 24.1.5• LISA-U120 / LISA-U130 - Chapter 24.1.6• SARA-G340 / SARA-G350 - Chapter 24.1.8• LEON-G1 series - Chapter 24.1.9<filter_number>

Number<a1>,<b1>,<a2>,<b2>,<a0>

Number•

LARA-R2 / TOBY-R2 series - Four digital biquad filters in cascade are available foreach uplink path. See Chapter 24.1.3 for the filter position. Filters 5-8 are used if22
the I S sampling rate is 16 kHz. Filters 1-4 are used if the I S sampling rate is otherthan 16 kHz.
• SARA-U2 series - Four digital biquad filters in cascade are available for each uplink
path. See Chapter 24.1.4 for the filter position. Filters 5-8 are used if the I2S
sampling rate is 16 kHz. Filters 1-4 are used if the I2S sampling rate is other than
16 kHz.
• LISA-U2 series - Four digital biquad filters in cascade are available for each uplink
path. See Chapter 24.1.5 for the filter position. Filters 5-8 are used if the I2S
sampling rate is 16 kHz. Filters 1-4 are used if the I2S sampling rate is other than
16 kHz.
• LISA-U1 series - Four digital biquad filters in cascade are available for each uplink
path. See Chapter 24.1.6 for the filter position. Filters 1-4 are used for Narrow Band
speech (8 kHz sampling rate i.e. with HR, FR, EFR, NB-AMR codec). Filters 1-5 areused for Wide Band speech (16 kHz sampling rate i.e. with WB-AMR). The range
goes from 1 to 8.
• SARA-G340 / SARA-G350 - Two digital biquad filters in cascade are available foreach uplink path (Filter1, Filter2). See Chapter 24.1.8 for the filter position. The
range goes from 1 to 2.
• LEON-G1 series - Two digital biquad filters in cascade are available for each uplink
path (Filter1, Filter2). See Chapter 24.1.9 for the filter position. The range goes from
1 to 2.
Biquad filter coefficients. The range goes from -32768 to 32767.
The factory-programmed value for a1, b1, a2 and b2 is 0 and for a0 is 32767.

24.5.4 Notes
The biquad filter transfer function is

A0 + 2A 1 z-1 + A2 z-2
H(z)=1 + 2B 1 z-1 + B 2 z-2with coefficients A0, A1, A2, B1, B2 in the range -1:1
The command parameters are filter coefficients scaled in the range that goes from -32768 to 32767• <a1>=32767 * A1
• <b1>=32767 * B1
• <a2>=32767 * A2
• <b2>=32767 * B2
• <a0>=32767 * A0
For the computation of the coefficients, consider the corresponding sampling rate for each product (according
to speech codec in use, as explained in Chapter 24.1).
Example: set both headset microphone filters to all pass:In this case the biquad filter transfer function is: H(z)=1

UBX-13002752 - R67

24 Audio parameters tuning

Page 626 of 1001

u-blox cellular modules - AT commands manual

Then the coefficients are• A0=1• A1=A2=B1=B2=0
Thus parameters are: <a1>=0, <b1>=0, <a2>=0, <b2>= 0, <a0>=32767
Commands are:••

AT+UUBF=1,1,0,0,0,0,32767
AT+UUBF=1,2,0,0,0,0,32767

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• 16 kHz sampling rate for <filter_number>= (5-8). These filters are used if the I2S sampling rate is 16 kHz.
• Same sampling rate of I2S in use, for <filter_number>= (1-4). These filters are used if the I2S sampling
rate is other than 16 kHz.
LISA-U120 / LISA-U130• 8 kHz sampling rate for <filter_number>= (1-4). These filters are used when speech codec is HR, FR, EFR
or NB-AMR (speech sampling rate is 8 kHz), thus filters are 'Narrow Band' (0 - 4 kHz).
• 16 kHz sampling rate for <filter_number>= (5-8). These filters are used when speech codec is WB-AMR(speech sampling rate is 16 kHz), thus filters are 'Wide Band' (0 - 8 kHz).
SARA-G340 / SARA-G350 / LEON-G1• 8 kHz sampling rate. Filters are 'Narrow Band' (0 - 4 kHz)
LEON-G1• <uplink_path_num>=4 is not supported.
• The factory-programmed values are as follows:o Path 0:- Filter1: a1=-13915, b1=2249, a2=4377, b2=-325, a0=23450- Filter2: a1=21682, b1=-2312, a2=17984, b2=-15517, a0=32767
o Path 1:- Filter1: a1=-29322, b1=-29141, a2=29322, b2=26240, a0=29322- Filter2: a1=29322, b1=29141, a2=29322, b2=26240, a0=29322
o Path 2:- Filter1: a1=0, b1=0, a2=0, b2=0, a0=32767- Filter2: a1=0, b1=0, a2=0, b2=0, a0=32767

24.6 Downlink Digital Filters (Downlink Biquad Filters) +UDBF+UDBF
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
fullNoProfileNo+CME Error

24.6.1 Description
Configures the digital audio filters parameters for a specific downlink path.
See Chapter 24.1 for the position of the filters in the audio path.
Not all paths are supported, see +USPM command description for the supported paths.

24.6.2 Syntax
Type
Set

SyntaxAT+UDBF=<downlinkpath_num>,<filter_number>,<a1>,<b1>,<a2>,<b2>,<a0>

UBX-13002752 - R67

Response
OK

ExampleAT+UDBF=0,1, -13915,2249,4377,325,23450
OK

24 Audio parameters tuning

Page 627 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UDBF?

Response+UDBF:

Example+UDBF:Path <downlinkpath_num>:

Path 0:Filter1: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter1: a1:0, b1:0, a2:0, b2:0, a0:32767Filter2: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter2: a1:0, b1:0, a2:0, b2:0, a0:32767Filter3: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter3: a1:0, b1:0, a2:0, b2:0, a0:32767Filter4: a1:<a1>, b1:<b1>, a2:<a2>,b2:<b2>, a0:<a0>

Filter4: a1:0, b1:0, a2:0, b2:0, a0:32767[...] (for all the supported paths)

Filter5: a1:0, b1:0, a2:0, b2:0, a0:32767

OK

Filter6: a1:0, b1:0, a2:0, b2:0, a0:32767Filter7: a1:0, b1:0, a2:0, b2:0, a0:32767Filter8: a1:0, b1:0, a2:0, b2:0, a0:32767[repeated for each path]
Test

OK+UDBF: (list of supported+UDBF: (0-9),(1-8),(-32768:32767),<downlinkpath_num>s),(list of(-32768:32767),(-32768:32767),(supported <filter_number>s),(list of 32768:32767),(-32768:32767)
supported <a1>s),(list of supported
OK<b1>s),(list of supported <a2>s),(list of supported <b2>s),(list of
supported <a0>s)

AT+UDBF=?

OK

24.6.3 Defined values
Parameter<downlinkpath_
num>

Type
Number<filter_number>

NumberDescription
Specifies the downlink path where the digital filters must be configured.
For downlink paths range and phisical meaning, see the product specific section in
the Chapter 24.1:• LARA-R2 / TOBY-R2 series - Chapter 24.1.3• SARA-U2 series - Chapter 24.1.4• LISA-U2 series - Chapter 24.1.5• LISA-U120 / LISA-U130 - Chapter 24.1.6• SARA-G340 / SARA-G350 - Chapter 24.1.8• LEON-G1 series - Chapter 24.1.9
•

•

•

•

UBX-13002752 - R67

LARA-R2 / TOBY-R2 series - four digital biquad filters in cascade are available foreach downlink path. See the Chapter 24.1.3 for the filter position. Filters 1-4 are used
for Narrow Band speech (8 kHz sampling rate i.e. with HR, FR, EFR, NB-AMR codec).
Filters 1-5 are used for Wide Band speech (16 kHz sampling rate i.e. with WB-AMR).
The range goes from 1 to 8.
SARA-U2 series - four digital biquad filters in cascade are available for eachdownlink path. See the Chapter 24.1.4 for the filter position. Filters 1-4 are used for
Narrow Band speech (8 kHz sampling rate i.e. with HR, FR, EFR, NB-AMR codec).
Filters 1-5 are used for Wide Band speech (16 kHz sampling rate i.e. with WB-AMR).
The range goes from 1 to 8.
LISA-U2 series - four digital biquad filters in cascade are available for each downlink
path. See the Chapter 24.1.5 for the filter position. Filters 1-4 are used for Narrow
Band speech (8 kHz sampling rate i.e. with HR, FR, EFR, NB-AMR codec). Filters 1-5
are used for Wide Band speech (16 kHz sampling rate i.e. with WB-AMR). The range
goes from 1 to 8.
LISA-U1 series - four digital biquad filters in cascade are available for each downlink
path. See the Chapter 24.1.6 for the filter position. Filters 1-4 are used for Narrow

24 Audio parameters tuning

Page 628 of 1001

u-blox cellular modules - AT commands manual

ParameterType<a1>,<b1>,<a2>,<b2>,<a0>

NumberDescription
Band speech (8 kHz sampling rate i.e. with HR, FR, EFR, NB-AMR codec). Filters 1-5
are used for Wide Band speech (16 kHz sampling rate i.e. with WB-AMR). The range
goes from 1 to 8.
• SARA-G340 / SARA-G350 series - two digital biquad filters in cascade are available
for each uplink path (Filter1, Filter2). See the Chapter 24.1.8 for the filter position.
The range goes from 1 to 2.
• LEON-G1 series - two digital biquad filters in cascade are available for each uplink
path (Filter1, Filter2). See the Chapter 24.1.9 for the filter position. The range goesfrom 1 to 2.
Biquad filter coefficient. The range goes from -32768 to 32767.
The factory-programmed value for a1, b1, a2 and b2 is 0 and for a0 is 32767.

24.6.4 Notes
The biquad filter transfer function is

A0 + 2A 1 z-1 + A2 z-2
H(z)=1 + 2B 1 z-1 + B 2 z-2with coefficients A0, A1, A2, B1, B2 in the range -1:1
Command parameters are filter coefficients scaled in the range that goes from -32768 to 32767• <a1>=32767 * A1
• <b1>=32767 * B1
• <a2>=32767 * A2
• <b2>=32767 * B2
• <a0>=32767 * A0
For the computation of the coefficients, consider the following sampling rate for each product (according tospeech codec in use, as explained in Chapter 24.1).
Example: set both loudspeaker filters to all pass:In this case the biquad filter transfer function is: H(z)=1Then the coefficients are• A0=1• A1=A2=B1=B2=0
Thus parameters are: <a1>=0, <b1>=0, <a2>=0, <b2>=0, <a0>=32767
Commands are:••

AT+UDBF=3,1,0,0,0,0, 32767
AT+UDBF=3,2,0,0,0,0, 32767

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1• 8 kHz sampling rate for <filter_number>= (1-4). These filters are used when speech codec is HR, FR, EFR
or NB-AMR (speech sampling rate is 8 kHz), thus filters are 'Narrow Band' (0 - 4 kHz).
• 16 kHz sampling rate for <filter_number>= (5-8). These filters are used when speech codec is WB-AMR(speech sampling rate is 16 kHz), thus filters are 'Wide Band' (0 - 8 kHz).
SARA-G340 / SARA-G350• 8 kHz sampling rate. Filters are 'Narrow Band' (0 - 4 kHz)
LEON-G1• 8 kHz sampling rate. Filters are 'Narrow Band' (0 - 4 kHz)• The factory-programmed values are as follows:o Path 0:- Filter1: a1=0, b1=0, a2=0, b2=0, a0=32767

UBX-13002752 - R67

24 Audio parameters tuning

Page 629 of 1001

u-blox cellular modules - AT commands manual- Filter2: a1=0, b1=0, a2=0, b2=0, a0=32767
o Path 1:- Filter1: a1=-29322, b1=-29141, a2=29322, b2=26240, a0=29322- Filter2: a1=29322, b1=29141, a2=29322, b2=26240, a0=29322
o Path 3:- Filter1: a1=0, b1=0, a2=0, b2=0, a0=32767- Filter2: a1=0, b1=0, a2=0, b2=0, a0=32767
o Path 4:- Filter1: a1=0, b1=0, a2=0, b2=0, a0=32767- Filter2: a1=0, b1=0, a2=0, b2=0, a0=32767

24.7 Hands-Free Parameters (Hands-Free Parameters) +UHFP+UHFP
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
ProfileNo+CME Error

24.7.1 Description
Sets the parameters that control the hands-free audio application for a specific uplink path. The hands-free
application consists of:• Echo Canceller (EC)• Automatic Gain Control (AGC)• Noise Reduction (NR)The corresponding module audio application note describes in detail the HF algorithm tuning.
Any change in the gain on uplink or downlink path impacts on the amount of echo fed back from the
speaker to the microphone. This means that performance of Hands-Free / EC algorithm could change andparameters could need to be changed to better fit new gain on uplink or downlink path
The command syntax differs between different module series. In Chapter 24.7.2 and Chapter 24.7.4 thedifferent descriptions are provided.

24.7.2 LEON-G1 syntax
Type
Set

Read

SyntaxResponse
AT+UHFP=<uplink_path_num>,OK<hf_algorithm_init>,<hf_algorithm_
restart>,<step_width>,<lms_length>,<lms_offset>,<block_length>,<rxtx_relation>,<add_atten>,<min_atten>,<max_atten>,<nr_sw_2>,<nr_u_fak_0>,<nr_u_
fak>
AT+UHFP?
+UHFP:Path <uplink_path_num>: HF_
algorithm_init:<hf_algorithm_
init>, HF_Algorithm_Restart:<hf_algorithm_restart>, Step_
Width:<step_width>, LMS_
Length:<lms_length>,LMS_
Offset:<lms_offset>, Block_Length:<block_length>, RXTX_
Relation:<rxtx_relation>,
Add_Atten:<add_atten>, Min_
Atten:<min_atten>, Max_UBX-13002752 - R67

24 Audio parameters tuning

ExampleAT+UHFP=1,0x01FD,0x016E,2200,250,3,5,150,0,0,500,4096,16384,
16384
OK

+UHFP:Path 0:
HF_algorithm_init:0x01fd, HF_
Algorithm_Restart:0x016e, Step_
Width:2200, LMS_Length:250,
LMS_Offset:3, Block_Length:5,
RXTX_Relation:150,
Add_Atten:0, Min_Atten:0, Max_
Atten:500, NR_sw_2:4096, NR_u_
fak_0:16384, NR_u_fak:16384
Path 1:Page 630 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Atten:<max_atten>, NR_sw_2:<nr_sw_2>,NR_u_fak_0:<nr_u_fak_0>,
NR_u_fak:<nr_u_fak>[...](for all the supported paths)
OK

ExampleHF_algorithm_init:0x01fd, HF_
Algorithm_Restart:0x016e, Step_
Width:2200, LMS_Length:250,
LMS_Offset:3, Block_Length:5,
RXTX_Relation:150,
Add_Atten:0, Min_Atten:0, Max_
Atten:500, NR_sw_2:4096, NR_u_
fak_0:16384, NR_u_fak:16384
Path 2:
HF_algorithm_init:0x01fd, HF_
Algorithm_Restart:0x016e, Step_
Width:2200, LMS_Length:250,
LMS_Offset:8, Block_Length:5,
RXTX_Relation:150,
Add_Atten:0, Min_Atten:0, Max_
Atten:500, NR_sw_2:4096, NR_u_
fak_0:16384, NR_u_fak:16384
OK

Test

AT+UHFP=?

+UHFP: (list of supported <uplink_ +UHFP: (0-2),(0x0000-0x01FF),(0x0path_num>s),(list of supported <hf_ 000-0x01FF),(0:32767),(2:400),(0:40
algorithm_init>s),(list of supported 0),(2,4,5,8),(-960:+960),(0:960),(0<hf_algorithm_restart>s),(list of:960),(0:960),(0:32767),(0:16384),(0supported <step_width>s),(list of:16384)
supported <lms_length>s),(list ofOKsupported <lms_offset>s), (list of
supported <block_length>s),(listof supported <rxtx_relation>s),(listof supported <add_atten>s),(listof supported <min_atten>s),(listof supported <max_atten>s),(listof supported <nr_sw_2>s),(list of
supported <nr_u_fak_0>s),(list of
supported <nr_u_fak>s)OK

24.7.3 LEON-G1 defined values
ParameterType<uplink_path_num> Number<hf_algorithm_init> Number<hf_algorithm_
restart>UBX-13002752 - R67

NumberDescription• 0: handset_mic• 1: headset_mic• 2: I2S_rx
The SWITCH parameter controls the activity and the initialization of the EC, AGC, NR
blocks:• Bit #0 set: Echo Canceller (EC) initialization• Bit #1 set: EC restart (without coefficient initialization)• Bit #2 set: EC on• Bit #3 set: EC adaptation on• Bit #4 set: noise reduction initialization• Bit #5 set: noise reduction on• Bit #6 set: noise reduction works with additional AGC• Bit #7 set: automatic Gain Control (AGC) initialization• Bit #8 set: AGC on
Setting the bits is not mutually exclusive; more than one bit can be set at the sametime.
• Range: 0x0000 to 0x01FF (hexadecimal format only)• The factory-programmed value is 0x01fd for all the uplink paths.
This bit mask allows to restart the activity of the EC, AGC, NR blocks without
initialization. For the bit map see the <hf_algorithm_init>. It is used when thealgorithm is automatically restarted by the driver (i.e. after an handover)• Range: 0x0000 to 0x01FF (hexadecimal format only)

24 Audio parameters tuning

Page 631 of 1001

u-blox cellular modules - AT commands manual

ParameterType<step_width>

NumberDescription• The factory-programmed value is 0x016e for all the uplink paths.
The higher this value, the faster the echo characteristic gets adapted
Limit: <step_width>*<block_length>=2*32767
Range: 0 to 32767<lms_length>

Number

The factory-programmed value is 2200 for all the uplink paths.
Maximum impulsive response of the FIR filter considered by the adaptive LMS
algorithm, in samples. (Max time length: 400*Ts=50 ms)
Limit:
2<= <lms_length>+<lms_offset><=400 (DSP memory limit)
Range: 2 to 400<lms_offset><block_length>

NumberNumber

The factory-programmed value is 250 for all the uplink paths.
This parameter is used by the LMS adaptation algorithm and indicates the expected
delay of the echo after the RX signal, in samples
Range: 0 to 400. The factory-programmed value is 3 (for the uplink path 0 and 1) and
8 (for the uplink path 2).
LMS coefficient adaptation block length. The higher this number, the slower but
more accurate the adaptation converges
Allowed values are: 2, 4, 5, 8

<rxtx_relation>

Number

The factory-programmed value is 5 for all the uplink paths.
Checks the power relation between Rx (loudspeaker) and Tx (microphone) signals
to recognize the double talk condition from the echo condition. The system isconsidered to be in double talk condition when the TX power (mic signal) is higherthat the maximum expected echo power:
Tx(dB) > Rx (dB) - RxTx(dB) with RxTx(dB)=<rxtx_relation>*3/32
This is the most critical parameter in hands-free. Values typical for handset are in
range 50 to 150. For backspeaker: -100 to -400. When in double talk, the adaptation of
FIR and AGC are suspended.
Range: -960 to 960<add_atten>

Number<min_atten>

Number<max_atten>

Number<nr_sw_2>

Number<nr_u_fak_0>

Number<nr_u_fak>

NumberUBX-13002752 - R67

The factory-programmed value is 150 for all the uplink paths.
When AGC decides to attenuate, <add_atten> is added to the calculated attenuation• Attenuation Level(dB)=3/32* <add_atten>• Range: 0 to 960
The factory-programmed value is 0 for all the uplink paths.
Minimal attenuation of the mic signal allowed for the AGC:
• Attenuation Level (dB)=3/32* <min_atten>• Range: 0 to 960
The factory-programmed value is 0 for all the uplink paths.
Maximal attenuation of the mic signal allowed for the AGC:
• Attenuation Level (dB)=3/32* <max_atten>• Range: 0 to 960
The factory-programmed value is 500 for all the uplink paths.
Max NR attenuation. Linear; 32767 means 1 (0 dB):
• Ex. 16384= 0.5 = -6 dB• Range: 0 to 32767
The factory-programmed value is 4096 for all the uplink paths.
Factor of NR in the band 0 (0 Hz - 250 Hz):• Linear; 16384 means 1 (0 dB)• Range: 0 to 16384
The factory-programmed value is 16384 for all the uplink paths.
Factor of NR in the bands 1 to 7 (250 Hz - 3750 Hz):• Linear; 16384 means 1 (0 dB)• A factor lower than 1 causes a better NR but also speech distortion and loweringof SLR.
• Range: 0 to 16384

24 Audio parameters tuning

Page 632 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description
The factory-programmed value is 16384 for all the uplink paths.

24.7.4 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 syntax
Type
Set

Read

SyntaxResponse
AT+UHFP=<uplink_path_num>,<hf_ OK
algorithm_init>[,<hf_algorithm_
restart>[,<step_width>[,<lms_length>[,<lms_offset>[,<block_length>[,<rxtx_relation>]]]]]],<add_atten>,<min_atten>,<max_atten>,<nr_sw_2>,<nr_u_fak_0>,<nr_u_fak>[,<ec_
block_length>[,<ec_nr_coeff_
real>[,<ec_nr_coeff_complex1>[,<ec_nr_coeff_complex2>[,<ec_
nr_coeff_complex3>[,<ec_nr_
coeff_complex4>[,<ec_nr_coeff_
complex5>]]]]]]])
AT+UHFP?
+UHFP:Path <uplink_path_num>:

ExampleAT+UHFP=1,0x01Fd,,,,,,,0,50,450,80
00,7000,7000,4,220,220,220,100,10
0,100
OK

+UHFP:Path 0:

HF_algorithm_init:<hf_algorithm_
HF_algorithm_init:0x01fd, HF_
init>, HF_Algorithm_Restart:NA,
Algorithm_Restart:NA, Step_
Step_Width:NA, LMS_Length:NA, Width:NA, LMS_Length:NA, LMS_LMS_Offset:NA, Block_Length:NA, Offset:NA, Block_Length:NA, RXTX_
RXTX_Relation:NA,Add_Atten:<add_ Relation:NA,
atten>, Min_Atten:<min_atten>,
Add_Atten:0, Min_Atten:0, Max_
Max_Atten:<max_atten>, NR_sw_
Atten:500, NR_sw_2:8192, NR_u_2:<nr_sw_2>,NR_u_fak_0:<nr_u_
fak_0:7500, NR_u_fak:7500,
fak_0>, NR_u_fak:<nr_u_fak>,</p> <p><ec_block_length>,<ec_
EC_block_length:2, EC_nr_coeff_
nr_coeff_real>, <ec_nr_coeff_
real:100, EC_nr_coeff_complex1:100,
complex1>,<ec_nr_coeff_complex2>, EC_nr_coeff_complex2:100,<ec_nr_coeff_complex3>,
EC_nr_coeff_complex3:60, EC_nr_<ec_nr_coeff_complex4>,<ec_nr_
coeff_complex4:60, EC_nr_coeff_
coeff_complex5>
complex5:60

Test

AT+UHFP=?

UBX-13002752 - R67[...][...] (for all the supported paths)(for all the supported paths)

OK

OK+UHFP: (list of supported <uplink_ +UHFP: (0-9),(0x0000-0x07FF),(0x0path_num>s),(list of supported <hf_ 000-0x07FF),(0:32767),(2:400),(0:40
algorithm_init>s),(list of supported 0),(2,4,5,8),(-960:960),(-960:960),(0<hf_algorithm_restart>s),(list of:960),(0:960),(0:32767),(0:16384),(0supported <step_width>s),(list of:16384),(1,2,4,5,8),(2:2000),(1:1000),
supported <lms_length>s),(list of(1:1000),(1:1000),(1:1000),(1:1000)
supported <lms_offset>s),(list ofOKsupported <block_length>s),(listof supported <rxtx_relation>s),(list of supported <add_atten>s),(list of supported <min_atten>s),(list of supported <max_atten>s),(list of supported <nr_sw_2>s),(listof supported <nr_u_fak_0>s),(listof supported <nr_u_fak>s),(list of
supported <ec_block_length>s),(list of supported <ec_nr_coeff_
real>s),(list of supported <ec_nr_
coeff_complex1>s),(list of supported<ec_nr_coeff_complex2>s),(list of supported <ec_nr_coeff_
complex3>s),(list of supported<ec_nr_coeff_complex4>s),

24 Audio parameters tuning

Page 633 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse(list of supported <ec_nr_coeff_
complex5>s),

ExampleOK

24.7.5 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 definedvaluesParameterType<uplink_path_num> Number<hf_algorithm_init> Number

UBX-13002752 - R67

Description
Specifies the uplink path where the hands free parameters must be configured.
For uplink paths range and physical meaning, see the product specific section in thechapter introduction:• LARA-R2 / TOBY-R2 - Chapter 24.1.3• SARA-U2 - Chapter 24.1.4• LISA-U2 - Chapter 24.1.5• LISA-U120 / LISA-U130 - Chapter 24.1.6• SARA-G340 / SARA-G350 - Chapter 24.1.8
The SWITCH parameter controls the activity and initialization of the EC, AGC, NR
blocks:• LARA-R2 / TOBY-R2 - Range: 0x0000 to 0x07FF (hexadecimal format only)o Bit #0 set: unusedo Bit #1 set: unusedo Bit #2 set: Echo Canceller (EC) initialization and ono Bit #3 set: unusedo Bit #4 set: unusedo Bit #5 set: Noise Reduction initialization and ono Bit #6 set: unusedo Bit #7 set: unusedo Bit #8 set: Automatic Gain Control (AGC) initialization and ono Bit #9 set: unusedo Bit #10 set: Spectral Echo Reduction (SER) initialization and on
o The factory-programmed value is 0x0124 for the uplink paths 0,1,2,3 and 0x0
524 for the path 4.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Range: 0x0000 to 0x07FF (hexadecimal format only)o Bit #0 set: unusedo Bit #1 set: unusedo Bit #2 set: Echo Canceller (EC) initialization and ono Bit #3 set: unusedo Bit #4 set: unusedo Bit #5 set: Noise Reduction initialization and ono Bit #6 set: unusedo Bit #7 set: unusedo Bit #8 set: Automatic Gain Control (AGC) initialization and ono Bit #9 set: unusedo Bit #10 set: Spectral Echo Reduction (SER) initialization and on
o The factory-programmed value is 0x0124 for the uplink paths 0,1,2,3 and 0x0
524 for the path 4.
• SARA-U2 / LISA-U2 - Range: 0x0000 to 0x07FF (hexadecimal format only)o Bit #0 set: unusedo Bit #1 set: unusedo Bit #2 set: Echo Canceller (EC) initialization and ono Bit #3 set: unusedo Bit #4 set: unusedo Bit #5 set: Noise Reduction initialization and ono Bit #6 set: unusedo Bit #7 set: unusedo Bit #8 set: Automatic Gain Control (AGC) initialization and ono Bit #9 set: unused

24 Audio parameters tuning

Page 634 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Descriptiono Bit #10 set: Spectral Echo Reduction (SER) initialization and on
o The factory-programmed value is 0x0124 for all the uplink paths.
• LISA-U1 - Range: 0x0000 to 0x07FF (hexadecimal format only)o Bit #0 set: Echo Canceller (EC) initializationo Bit #1 set: EC restart (without coefficient initialization)o Bit #2 set: EC ono Bit #3 set: unusedo Bit #4 set: noise reduction initializationo Bit #5 set: noise reduction ono Bit #6 set: unusedo Bit #7 set: Automatic Gain Control (AGC) initializationo Bit #8 set: AGC ono Bit #9 set: dynamic Echo Suppression INITo Bit #10 set: dynamic Echo Suppression ACTIVEo The factory-programmed value is 0x01fd for all the uplink paths.
• SARA-G340 / SARA-G350 - Range: 0x0000 to 0x3FFF (hexadecimal format only)o Bit #0 set: Echo Canceller (EC) initializationo Bit #1 set: EC restart (without coefficient initialization)o Bit #2 set: EC ono Bit #3 set: noise reduction initializationo Bit #4 set: noise reduction ono Bit #5 set: dynamic Echo Suppression INITo Bit #6 set: dynamic Echo Suppression ACTIVEo Bit #7 set: automatic Gain Control (AGC) initializationo Bit #8 set: AGC ono Bit #9 set: reconfigureo Bit #10 set: unusedo Bit #11 set: unusedo Bit #12 set: Spectral Echo Reduction (SER) Initializationo Bit #13 set: SER ono The factory-programmed value is 0x31fd for all the uplink paths.
Setting the bits is not mutually exclusive; more than one bit can be set at the sametime.

<hf_algorithm_
restart>

NumberNot Available. 'NA' is provided in the test command<step_width>

Number<lms_length>

Number<lms_offset>

Number<block_length>

Number<rxtx_relation>

Number<add_atten>

NumberUBX-13002752 - R67

In the set command, the range is checked but the value is not used
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - the range goes from 0x0000
to 0x07FF (hexadecimal format only)• SARA-G340 / SARA-G350 - the range goes from 0x0000 to 0x03FF (hexadecimalformat only)
Not Available. 'NA' is provided in the test command.
• In the set command, the range is checked but the value is not used
• Range: 0 to 32767
Not Available. 'NA' is provided in the test command.
• In the set command, the range is checked but the value is not used
• Range: 2 to 400
Not Available. 'NA' is provided in the test command.
• In the set command, the range is checked but the value is not used
• Range: 0 to 400
Not Available. 'NA' is provided in the test command.
• In the set command, the range is checked but the value is not used
• Allowed values: 2, 4, 5, 8
Not Available. 'NA' is provided in the test command.
• In the set command, the range is checked but the value is not used
• Range : -960 to 960
When AGC decides to attenuate, <add_atten> is added to the calculated attenuation.
• Range: -960 to 960

24 Audio parameters tuning

Page 635 of 1001

u-blox cellular modules - AT commands manual

ParameterType<min_atten>

Number<max_atten>

Number<nr_sw_2>

Number<nr_u_fak_0>

Number<nr_u_fak>

NumberUBX-13002752 - R67

Description• LARA-R2 / TOBY-R2 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X /LISA-U200-04B / LISA-U201-04B - Attenuation Level(dB)=0,2*<add_atten>. The
factory-programmed value is 0 on the uplink paths 0, 1, 2, 3 and 15 on the path 4.
• SARA-U2 / LISA-U2 - Attenuation Level(dB)=0,2*<add_atten>. The factoryprogrammed value is 0 for all the uplink paths.
• LISA-U1 - Attenuation Level(dB)=0,05*<add_atten>. The factory-programmed
value is 0 on the uplink path 0, 1 and 2 and 50 on the uplink path 4.
• SARA-G340 / SARA-G350 - Attenuation Level(dB)=0,05*<add_atten>. The factoryprogrammed value is 0 for all the uplink paths.
Minimal attenuation of the mic signal allowed for the AGC.
• Range: 0 to 960• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - Attenuation Level(dB)=0,2*<min_atten>. The factory-programmed value is 0 for all the uplink paths.
• LISA-U1 - Attenuation Level(dB)=0,05*<min_atten>. The factory-programmed
value is 0 on the uplink path 0, 1 and 2 and 100 on the uplink path 4.
• SARA-G340 / SARA-G350 - Attenuation Level(dB)=0,05*<min_atten>. The factoryprogrammed value is 0 for all the uplink paths.
Maximal attenuation of the mic signal allowed for the AGC.
• Range: 0 to 960• LARA-R2 / TOBY-R2 - Attenuation Level(dB)=0,2*<max_atten>. The factoryprogrammed value is 480 on the uplink paths 0, 1, 2, 3 and is 191 on path 4.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Attenuation Level(dB)=0,2* <max_atten>. The factoryprogrammed value is 500 on the uplink paths 0, 1, 2, 3 and is 191 on path 4.
• SARA-U2 / LISA-U2 - Attenuation Level(dB)=0,2*<max_atten>. The factoryprogrammed value is 500 for all the uplink paths.
• LISA-U1 - Attenuation Level(dB)=0,05*<max_atten>. The factory-programmed
value is 500 for all the uplink paths.
• SARA-G340 / SARA-G350 - Attenuation Level(dB)=0,05*<max_atten>. The
factory-programmed value is 588 for all the uplink paths.
Maximum NR attenuation. Linear; 32767 means 1 (0 dB).
• Ex. 16384= 0.5 = -6 dB• Range: 0 to 32767• LARA-R2 / TOBY-R2 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X /LISA-U200-04B / LISA-U201-04B - The factory-programmed value is 8192 on the
uplink paths 0, 1, 2, 3 and is 6000 on path 4.
• SARA-U2 / LISA-U2 / LISA-U1 / SARA-G340 / SARA-G350 - The factoryprogrammed value is 8192 for all the uplink paths.
Factor of NR in the band 0 (0 Hz - 500 Hz).
• Linear; 16384 means 1 (0 dB)• Range: 0 to 16384• LARA-R2 / TOBY-R2 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X /LISA-U200-04B / LISA-U201-04B - The factory-programmed value is 7500 on the
uplink paths 0, 1, 2, 3 and is 4500 on path 4.
• SARA-U2 / LISA-U2 - The factory-programmed value is 0 for all the uplink paths.
• LISA-U1 - The factory-programmed value is 7500 for all the uplink paths.
• SARA-G340 / SARA-G350 - The factory-programmed value is 16384 for all the
uplink paths.
Factor of NR in the higher bands (-f > 500 Hz).
• Linear; 16384 means 1 (0 dB)• A factor lower than 1 causes a better NR but also speech distortion and loweringof SLR.
• Range: 0 to 16384• LARA-R2 / TOBY-R2 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X /LISA-U200-04B / LISA-U201-04B - The factory-programmed value is 7500 on the
uplink paths 0, 1, 2, 3 and is 5000 on path 4.
• SARA-U2 / LISA-U2 / LISA-U1 - The factory-programmed value is 7500 for all the
uplink paths.
• SARA-G340 / SARA-G350 - The factory-programmed value is 16384 for all the
uplink paths.

24 Audio parameters tuning

Page 636 of 1001

u-blox cellular modules - AT commands manual

Parameter<ec_block_length><ec_nr_coeff_real>Type
NumberNumber<ec_nr_coeff_
complex1>

Number<ec_nr_coeff_
complex2>

Number<ec_nr_coeff_
complex3>

NumberUBX-13002752 - R67

Description
LMS coefficient adaptation block length. The higher this number, the slower but
more accurate the adaptation converges.
Allowed values are: 1, 2, 4, 5, 8:• LARA-R2 / TOBY-R2 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X /LISA-U200-04B / LISA-U201-04B - The factory-programmed value is 2 for the uplink
paths 0, 1, 2, 3 and is 1 for the path 4.
• SARA-U2 / LISA-U2 / LISA-U1 / SARA-G340 / SARA-G350 - The factoryprogrammed value is 2 for all the uplink paths.
Number of coefficients of the filter in the sub-band EC, for real sub band (in Narrow
Band mode: 0-0.8 kHz in Wide Band mode: 0-0.73 kHz)• LARA-R2 / TOBY-R2 - Range: 2 to 2000. The factory-programmed value is 100 for
all the uplink paths.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Range: 2 to 2000. The factory-programmed value is 100 for the
uplink paths 0, 1, 2, 3 and is 150 for the path 4.
• SARA-U2 / LISA-U2 - Range: 2 to 2000. The factory-programmed value is 100 for all
the uplink paths.
• LISA-U1 - Range: 2 to 1100. The factory-programmed value is 100 on the uplink path0, 1 and 2 and 220 on the uplink path 4.
• SARA-G340 / SARA-G350 - Range: 0 to 1100. The factory-programmed value is 10
0 for all the uplink paths.
The following limits must be considered:• LARA-R2 / TOBY-R2 - <ec_nr_coeff_real>+2*(<ec_nr_coeff_complex1>+<ec_nr_
coeff_complex2> +<ec_nr_coeff_complex3>+ <ec_nr_coeff_complex4>+<ec_nr_
coeff_complex5>) <2000• SARA-U2 / LISA-U2 / LISA-U1 - <ec_nr_coeff_real>+2*(<ec_nr_coeff_complex1>+<ec_nr_coeff_complex2> +<ec_nr_coeff_complex3>+ <ec_nr_coeff_complex4>+<ec_nr_coeff_complex5>) <2000• SARA-G340 / SARA-G350 - <ec_nr_coeff_real>+2*(<ec_nr_coeff_complex1>+<ec_
nr_coeff_complex2>) <1100
Number of coefficients of the filter in the sub-band EC, for complex sub band 1 (inNarrow Band mode: 0.8-2.4 kHz; in Wide Band mode: 0.73-2.18 kHz)• LARA-R2 / TOBY-R2 - Range: 1 to 1000. The factory-programmed value is 100 for all
the uplink paths.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Range: 1 to 1000. The factory-programmed value is 100 for the
uplink paths 0, 1, 2, 3 and is 150 for the path 4.
• SARA-U2 / LISA-U2 - Range: 1 to 1000. The factory-programmed value is 100 for all
the uplink paths.
• LISA-U1 - Range: 1 to 1100. The factory-programmed value is 100 on the uplink path0, 1 and 2 and 220 on the uplink path 4.
• SARA-G340 / SARA-G350 - Range: 0 to 1100. The factory-programmed value is 10
0 for all the uplink paths.
See the <ec_nr_coeff_real> parameter description for the limit value.
Number of coefficients of the filter in the sub-band EC, for complex sub band 2 (inNarrow Band mode: 2.4-4 kHz; in Wide Band mode: 2.18-3.64 kHz)• LARA-R2 / TOBY-R2 - Range: 1 to 1000. The factory-programmed value is 100 for all
the uplink paths.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Range: 1 to 1000. The factory-programmed value is 100 for the
uplink paths 0, 1, 2, 3 and is 150 for the path 4.
• SARA-U2 / LISA-U2 - Range: 1 to 1000. The factory-programmed value is 100 for all
the uplink paths.
• LISA-U1 - Range: 1 to 1100. The factory-programmed value is 100 on the uplink path0, 1 and 2 and 220 on the uplink path 4.
• SARA-G340 / SARA-G350 - Range: 0 to 1100. The factory-programmed value is 10
0 for all the uplink paths.
See the <ec_nr_coeff_real> parameter description for the limit value.
Number of coefficients of the filter in the sub-band EC, for complex sub band 3 (inNarrow Band mode: ignored; in Wide Band mode: 3.64-5.09 kHz)

24 Audio parameters tuning

Page 637 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• LARA-R2 / TOBY-R2 - Range: 1 to 1000. The factory-programmed value is 60 on the
uplink paths 0,1,2,3 and is 100 on path 4.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Range: 1 to 1000. The factory-programmed value is 60 for the
uplink paths 0, 1, 2, 3 and is 136 for the path 4.
• SARA-U2 / LISA-U2 - Range: 1 to 1000. The factory-programmed value is 60 for all
the uplink paths.
• LISA-U1 - Range: 1 to 1100. The factory-programmed value is 60 for all the uplink
paths.
On SARA-G340 / SARA-G350 series the parameter is not in use and is set to its
default/factory-programmed value (0).

<ec_nr_coeff_
complex4>

NumberSee the <ec_nr_coeff_real> parameter description for the limit value.
Number of coefficients of the filter in the sub-band EC, for complex sub band 4 (inNarrow Band mode: ignored; in Wide Band mode: 5.09-6.56 kHz)• LARA-R2 / TOBY-R2 - Range: 1 to 1000. The factory-programmed value is 60 on the
uplink paths 0, 1, 2, 3 and is 100 on path 4.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Range: 1 to 1000. The factory-programmed value is 60 for the
uplink paths 0, 1, 2, 3 and is 136 for the path 4.
• SARA-U2 / LISA-U2 - Range: 1 to 1000. The factory-programmed value is 60 for all
the uplink paths.
• LISA-U1 - Range: 1 to 1100. The factory-programmed value is 60 for all the uplink
paths.
On SARA-G340 / SARA-G350 series the parameter is not in use and is set to its
default/factory-programmed value (0).

<ec_nr_coeff_
complex5>

NumberSee the <ec_nr_coeff_real> parameter description for the limit value.
Number of coefficients of the filter in the sub-band EC, for complex sub band 5 (inNarrow Band mode: ignored; in Wide Band mode: 6.56-8 kHz)• LARA-R2 / TOBY-R2 - Range: 1 to 1000. The factory-programmed value is 60 on the
uplink paths 0, 1, 2, 3 and is 100 on path 4.
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B - Range: 1 to 1000. The factory-programmed value is 60 for the
uplink paths 0, 1, 2, 3 and is 136 for the path 4.
• SARA-U2 / LISA-U2 - Range: 1 to 1000. The factory-programmed value is 60 for all
the uplink paths.
• LISA-U1 - Range: 1 to 1100. The factory-programmed value is 60 for all the uplink
paths.
On SARA-G340 / SARA-G350 series the parameter is not in use and is set to its
default/factory-programmed value (0).
See the <ec_nr_coeff_real> parameter description for the limit value.

24.7.6 Notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G340 / SARA-G350• Parameters <ec_nr_coeff_complex3>, <ec_nr_coeff_complex4> and <ec_nr_coeff_complex5> are used
only in Wide Band speech (16 kHz sampling rate i.e. with WB-AMR codec) and ignored in Narrow Band
speech (8 kHz sampling rate i.e. with HR, FR, EFR, NB-AMR codec). For the supported speech codec seenotes in Chapter 24.1.
• Not all paths are supported, see +USPM for the supported paths.
• <hf_algorithm_restart>, <step_width>, <lms_length>, <lms_offset>, <block_length>, <rxtx_relation>
parameters are maintained for back compatibility with LEON-G series; they are not used and optional.
• Examples:o SWITCH =0x01FD =bin 000111111101 means EC initialized and on, Noise reduction initialized and on,
Automatic Gain Control initialized and on
o SWITCH =0x0000 means EC, AGC and NR all off.
LARA-R2 / TOBY-R2 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B• Parameters for <uplink_path_num>=0, 1, 2, 3 are indicated for using in a handset or headset device.

UBX-13002752 - R67

24 Audio parameters tuning

Page 638 of 1001

u-blox cellular modules - AT commands manual•

Default parameters for <uplink_path_num>=4 are indicated for using in a speakerphone device. Select<uplink_path_num> by +USPM command.

SARA-G350• Parameters <ec_block_length> and <ec_nr_coeff_real> are mandatory.
LEON-G1• Examples:o SWITCH =0x01FD =bin 000111111101 means EC initialized and on, EC adaptation on, noise reduction
initialized and on, Automatic Gain Control initialized and on, used with NR.
o SWITCH =0x016E =bin 000101101110 means EC on, EC adaptation on, EC restart noise reduction on,
Automatic Gain Control on and working with NR.
o SWITCH =0x0000 means EC, AGC and NR all off.
o Calculation of <lms_offset>;
Sample period T= 1/8000 s= 125 µs Loudspeaker to mic distance on a phone: L= 10 cm
Sound velocity V=340 m/s Delay of echo: D =L/V = 0.1/ 340 = 294 µs
Number of samples=D/T= 2.35 --> LMS_OFFSET =2

24.8 Audio parameters tuning +UAPT+UAPT
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
ProfileNo+CME Error

24.8.1 Description
Audio signals are processed by signal processing blocks available on the audio paths (see block diagram in
TOBY-L2 series audio paths).
Each signal processing block (e.g.: Echo Cancellation, Residual Echo Suppression) is characterized by a set ofaudio parameters.
The command provides an interface for tuning the audio parameters and performs these tasks:• Reload (<op_code>=0): the voice parameters and configuration are retrieved from the module memory into
the signal processing blocks in the DSP. This operation can take place both in voice idle or active states.
• Get processing block identifiers (<op_code>=5): queries the available/existing blocks and their enable statein the affected audio path. The related information text response returns the processing block identifiers
and the corresponding enable-state for each available block.
• Modify a processing block state (<op_code>=6): modifies the state of a processing block in a requested
input or output audio path with a new value.
• Get parameters list (<op_code>=7): queries the parameter values in a requested input or output audio path,
processing block and rate (8 kHz or 16 kHz). The related information text response returns a list which
includes the parameter values.
• Modify parameters (<op_code>=8): modifies parameters (one or more) of a processing block with newvalues.
• Modify parameters (<op_code>=11): enables/disables the parameters range check when entering "Modify
parameters" command.

24.8.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UAPT=<op_code>[,<param1>,<param2>,<param3>[,<param4>,<param5>[,<param6>,<param7>,<param8>,...]]]
Load audio parameters
Set
AT+UAPT=0

UBX-13002752 - R67

Response

ExampleOK

AT+UAPT=8,0,0,1,3,0,0,7,1,4096,0,0,4096,0,0OKOK

24 Audio parameters tuning

AT+UAPT=0

Page 639 of 1001

u-blox cellular modules - AT commands manualType

SyntaxGet processing blocks states
Set
AT+UAPT=5,<profile>,<app>,<direction>

Response

ExampleOK+UAPT:

AT+UAPT=5,3,0,0<blockID>,<enableState>+UAPT:[...] (for all the supported block
identifier on current profile, path)

2,1

OK

3,0
4,1
5,1
6,1
7,1
OK

Modify processing block state
Set
AT+UAPT=6,<profile>,<app>,<direction>,<blockID>,<enableState>
Get parameters list
Set
AT+UAPT=7,<profile>,<app>,<direction>,<blockID>,<rate>

OK

AT+UAPT=6,0,0,1,3,0
OK+UAPT:

AT+UAPT=7,0,0,1,3,0<parameterOffset>,<paramValue>+UAPT:[...] (for all the supported
parameters in the requested<blockID>)

0,1

OK

1,40962,03,04,40965,0
6,0OKModify parameters
Set
AT+UAPT=8,<profile>,<app>,<direction>,<blockID>,<rate>,<parameterOffset>,<numOfParams>,<newValue1>[,<newValue2>,<newValue3>, ..]Enable/disable parameters range check
Set
AT+UAPT=11,<enableCheck>
Read

AT+UAPT=11

OK

AT+UAPT=8,0,0,1,3,0,0,7,1,4096,0,0,4096,0,0
OK

OK

AT+UAPT=11,0+UAPT:11,<enableCheck>

OK
AT+UAPT=11

OK+UAPT: 11,1
OK

Test

AT+UAPT=?

+UAPT: 0

AT+UAPT=?

+UAPT: 5,(list of supported<profile>'s),(list of supported<app>'s),(list of supported<direction>'s)+UAPT: 0+UAPT: 6,(list of supported<profile>'s),(list of supported<app>'s),(list of supported<direction>'s),(list of supported<blockID>'s),(list of supported<enableState>'s)+UAPT: 7,(0-4),(0),(0-1),(0-8),(0-1)+UAPT: 5,(0-4),(0),(0-1)+UAPT: 6,(0-4),(0),(0-1),(0-8),(0-1)+UAPT: 8,(0-4),(0),(0-1),(0-8),(0-1),(0-30),(1-31),(-32768:32767),...
+UAPT: 11,(0,1)
OK+UAPT: 7,(list of supported<profile>'s),(list of supported<app>'s),(list of supported

UBX-13002752 - R67

24 Audio parameters tuning

Page 640 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse<direction>'s),(list of supported<blockID>'s),(list of supported<rate>'s)

Example+UAPT: 8,(list of supported<profile>'s),(list of supported<app>'s),(list of supported<direction>'s),(list of supported<blockID>'s),(list of supported<rate>'s),(list of supported<parameterOffset>'s),(list of
supported <numOfParams>'s),(listof supported <newValue1>'s),...
+UAPT: 11,(list of supported<enableCheck>'s)
OK

24.8.3 Defined values
Parameter<op_code>Type
Number<profile>

Number<app>

Number<direction>

Number<blockID>

Number<enableState>

Number<rate>

Number<parameterOffset><numOfParams>

NumberNumberUBX-13002752 - R67

Description
Allowed values:• 0 ("reloads"): reloads voice parameters and configurations from the memory.
• 5 ("get list of available processing blocks identifiers and their state"): queries
available/existing blocks and their state (enable/disabled) in a given profile andapplication pair and a given path (RX or TX)• 6 ("modify a processing state"): modifies block's state (enable/disable) in a profile
and application pair element with a new value.
• 7 ("get parameters value list"): queries the parameter values in a requested profile
and application pair element and a given path, moduIeID and rate (8 kHz or 16 kHz).
• 8 ("modify block's parameters value"): modifies processing block parameters (1 ormore) with new values.
• 11 ("parameters range check"): enables/disables parameters range check whenentering "modify block's parameters value" command (<op_code>=8).
Acoustic profile. It identifies the set of parameters loaded from memory in the
speech processing blocks when an audio path is enabled. See <main_uplink>, <main_
downlink> description in +USPM AT command.
Application. Allowed value:• 0: speech
Audio path direction. Allowed values:• 0: TX path (input)• 1: RX path (output)
Signal processing block identifier. (See block diagram in TOBY-L2 series audio paths).
Allowed values:• 0: Echo Cancellation ("EC")• 1: Residual Echo Suppression ("RES")• 2: Noise Suppression ("NS")• 3: Low Pass Filter ("LPF")• 4: High Pass Filter ("HPF")• 5: Equalizer ("EQU")• 6: Additional Gain Control ("AGC")• 7: Dynamic Range Compression ("DRC")• 8: Microphone Levels ("ML")State. Allowed values:• 0: processing block state is disabled• 1: processing block state is enabledRate. Allowed values:• 0: 8 kHz• 1: 16 kHz
Offset of the affected parameter
Number of affected parameters, starting from the one specified by<parameterOffset>.

24 Audio parameters tuning

Page 641 of 1001

u-blox cellular modules - AT commands manual

Parameter<paramValue>

Type
NumberDescription
Value of parameter. See TOBY-L2 Audio Application Note [181] for the ranges anddefault values of parameters.

NumberEnable/disable parameters value check. Allowed values:• 0: disabled, parameters range is not checked; only values between -32767 and+32767 are allowed• 1: (default value) enabled<newValue1><newValue2>[...]<enableCheck>24.8.4 Notes
TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220-02S /TOBY-L280-02S• <op_code>=11 is not supported.
TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S• <op_code>=11 is not supported by TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L210-03A-00,
TOBY-L280-03S-00.

24.9 Audio parameters tuning +UTI
+UTI
Modules

Attributes

TOBY-L4
LARA-R211
SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
partialNo
ProfileNo-

Error reference-

24.9.1 Description
Provides an interface for tuning the full set of parameters of the speech enhancement system, configurable
for each supported audio path.
See the speech enhancement system diagrams in• SARA-U2 / LISA-U2 "04" product versions - Speech processing blocks and audio paths• TOBY-L4 series - Speech processing blocks and audio paths• LARA-R211 product variant - Speech processing blocks and audio paths
The Extended Audio Tuning Application Note is available on request.

24.9.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UTI=<cmd_string>Response

ExampleOK

AT+UTI="uhfpw:0"
OK

24.9.3 Defined values
Parameter<cmd_string>Type
StringDescription
Product specific UTI command string.

24.9.4 Notes
LARA-R211• The command is not supported by LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02.

UBX-13002752 - R67

24 Audio parameters tuning

Page 642 of 1001

u-blox cellular modules - AT commands manual

24.10 Volume gain control +UVGC+UVGCModules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
fullNoProfileNo+CME Error

Attributes

24.10.1 Description
Sets the gain of the uplink and downlink path and the sidetone (feedback from uplink to downlink path) on theexternal voice codec Maxim MAX9860, if connected.
Any change in the gain on uplink or downlink path impacts on the amount of echo fed back fromthe speaker to the microphone. This means that the EC algorithm performance could change and theparameters could need to be changed to better fit the new gain on uplink or downlink path. See the +UAPT
command description).

24.10.2 Syntax
Type
Set

SyntaxAT+UVGC=<componentID>,<gainID>,<gainValue>

Response
OK

ExampleAT+UVGC=0,2,30

Read

AT+UVGC=<componentID>,<gainID>+UVGC: <gainApplied>OK
AT+UVGC=0,3

OK+UVGC: 4

Test

AT+UVGC=?

OK+UVGC: (list of supported+UVGC: (0),(0-3),(-99999:+99999)<componentID>'s),(list of supportedOK<gainID>'s),(list of supported<gainValue>'s)
OK

24.10.3 Defined values
Parameter<componentID><gainID><gainValue>

Type
NumberNumberNumber<gainApplied>

NumberDescription
0: external codec Maxim MAX9860
See Table 82 for the allowed gain control.
See Table 82 for the allowed gain value available on each gain control. The range goesfrom -99999 to +99999
See Table 82 for the applied gain values corresponding to each gain control. The
values is expressed in dB.

24.10.4 Notes
In Table 82 the name of the gain controls refer to the Maxim MAX9860 voice codec datasheet.
<gainID>
0Gain control name
DVA (DAC Level Adjust on Maxim MAX9860 codec)<gainApplied>
Resolution: 1 dB/step. The default and factoryprogrammed value is -5 dB
Mute if <gainValue> < -90
3 dB if <gainValue> > 3

1

DVST (Sidetone Level on Maxim MAX9860 codec)<gainValue> dB otherwise
Resolution: 2 dB/step. The default and factoryprogrammed value is OFF
OFF if <gainValue> < -60
0 dB if <gainValue> > 0<gainValue> rounded to higher even number (dB),otherwise

UBX-13002752 - R67

24 Audio parameters tuning

Page 643 of 1001

u-blox cellular modules - AT commands manual<gainID>
2

Gain control name
PAM (Microphone Preamplifier on Maxim MAX9860
codec)<gainApplied>
The default and factory-programmed value is 20 dB
OFF if 0 < <gainValue>
0 dB if 0 =< <gainValue> < 10
20 dB if 10 =< <gainValue> < 25

3

PGAM (Microphone Amplifier on Maxim MAX9860
codec)

30 dB if <gainValue> >= 25
Resolution: 1 dB/step. The default and factoryprogrammed value is 4 dB
0 dB if <gainValue> < 0
20 dB if <gainValue> > 20
<gainValue> dB otherwise

Table 82: Gain controls
See the block diagram in Figure 26 for position of controls in the audio chain.
External Codec
Maxim MAX 8960

TOBY-L2

To
Radio TX

I2S_RXD
MIC

PAM

PGAM

ADC

HPF

EC

NS

DVST

SPK

DAC

DVA

RES

EQ

AGC

DRC

LPF
Volume &Mute

CNG

I2S_TXD

Maxim MAX 8960 codec legend:
DVA = DAC Level Adjust
DVST = Sidetone Level
PAM = Microphone Preamplifier
PGAM = Microphone Amplifier

LPF
Volume& Mute

PCM
Player

DRC

AGC

EQ

Tone
Generator

HPF

NS

From
Radio RXTOBY-L2 legend:
EC = Echo Cancellation
RES = Residual Echo Suppression
NS = Noise Suppression
LPF = Low Pass Filter
HPF = High Pass Filter
EQU = Equalizer
AGC = Additional Gain Control
DRC = Dynamic Range Compression
CNG = Comfort Noise Generator

Figure 26: External codec controls

24.11 Microphone analog and digital gains +UMAFE+UMAFE
Modules
Attributes

TOBY-L4
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

24.11.1 Description
Controls the microphone analog and digital gains for the currently active audio path mode. The gains areavailable for each analog profile type and are stored in NVM.
When the user selects the profile type with +USPM, the microphone gains for that profile type are used.

24.11.2 Syntax
Type
Set

SyntaxAT+UMAFE=<analog_gain>,<adc_
gain>Response
OK

Read

AT+UMAFE?

+UMAFE: <analog_gain>,<adc_
gain>

ExampleAT+UMAFE=10,4
OK+UMAFE: 4,2
OK

OK

UBX-13002752 - R67

24 Audio parameters tuning

Page 644 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+UMAFE=?

Response+UMAFE: (list of supported<analog_gain>s),(list of supported<adc_gain>s)

Example+UMAFE: (0-30),(0-7)
OKOK

24.11.3 Defined values
Parameter<analog_gain>

Type
Number<adc_gain>

NumberDescription
The range goes from 0 to 30. The factory-programmed value is 4.
• 0 means -6 dB, 4 means 0 dB, 30 means 39 dB.
• The step size is 1.5 dB (e.g.: 20 means 24 dB).
The range goes from 0 to 7:• 0: -6 dB• 1: -2.5 dB• 2 (factory-programmed value): 0 dB
• 3: 3.5 dB• 4: 6 dB• 5: 9.5 dB• 6: 12 dB• 7: 15.5 dB

24.11.4 Notes•

If the command is issued when the active audio path selected by +USPM AT command is not analog, thecommand returns with "+CME ERROR: operation not allowed" error result code (if +CMEE is set to 2).

TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.
TOBY-L4906-50A• The <analog_gain> parameter range goes from 0 to 26: 0 means 0 dB, 26 means 39 dB. The step sizeis 1.5 dB (e.g.: 20 means 30 dB). The factory-programmed value is 0.

24.12 Speaker analog and digital gains +USAFE+USAFE
Modules
Attributes

TOBY-L4
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

24.12.1 Description
Controls speaker analog and digital gains for the currently active audio path mode. The gains are available foreach analog profile type and are stored in NVM.
When the user selects the profile type with +USPM, the speaker gains for that profile type are used.

24.12.2 Syntax
Type
Set

SyntaxResponse
AT+USAFE=<earpiece_gain>,<dac_ OK
coarse_gain>,<dac_fine_gain>

Read

AT+USAFE?

Test

AT+USAFE=?

UBX-13002752 - R67+USAFE: <earpiece_gain>,<dac_coarse_gain>,<dac_fine_gain>

ExampleAT+USAFE=4,4,3
OK+USAFE: 4,4,3

OK
OK+USAFE: (list of supported+USAFE: (0-8),(0-6),(0-3)<earpiece_gain>s),(list of supported
OK<dac_coarse_gain>s),(list of
supported <dac_fine_gain>s)

24 Audio parameters tuning

Page 645 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example24.12.3 Defined values
Parameter<earpiece_gain>

Type
NumberDescription
The range goes from 0 to 8. The factory-programmed value is 4 (0 dB).

<dac_coarse_gain>

Number0 means -12 dB, 8 means 12 dB and the step size is 3 dB.
The range goes from 0 to 6. The factory-programmed value is 4 (0 dB).

<dac_fine_gain>

Number0 means mute, 6 means 12 dB and the step size is 6 dB (e.g.: 2 means -12 dB).
The range goes from 0 to 3. The factory-programmed value is 3 (0 dB).
0 means -4.5 dB, 3 means 0 dB and the step size is 1.5 dB (e.g.: 2 means -1.5 dB).

24.12.4 Notes•

If command is issued when active audio path selected by +USPM is not analog, the command returns
with error "+CME ERROR: operation not allowed" (if +CMEE is set to 2).

TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.

24.13 Microphone select +UMSEL+UMSEL
Modules
Attributes

TOBY-L4
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

24.13.1 Description
Allows the configuration of the active microphone for audio front ends (analog or digital paths) supporting 2
microphones.
The command selects the microphone of the active audio path, configured by means of the +USPM AT
command.

24.13.2 Syntax
Type
Set

SyntaxAT+UMSEL=<mic_id>

Response
OK

ExampleAT+UMSEL=1

Read

AT+UMSEL?

+UMSEL: <mic_id>

OK+UMSEL: 1

Test

AT+UMSEL=?

OK+UMSEL: (list of supported <mic_
id>s)

OK
+UMSEL: (1-2)
OKOK

24.13.3 Defined values
Parameter<mic_ic>

UBX-13002752 - R67

Type
NumberDescription
Specifies microphones to use on active path. Allowed and default values for <mic_id>
parameter for each audio path:• Analog path:o 1 (factory-programmed value): AMIC1 selectedo 2: AMIC2 selected• Digital path:o Command not allowed

24 Audio parameters tuning

Page 646 of 1001

u-blox cellular modules - AT commands manual

24.13.4 Notes
TOBY-L4• The command setting can be stored in NVM or NVM RAM mirror, which is controlled by +UDCONF=110
AT command.

UBX-13002752 - R67

24 Audio parameters tuning

Page 647 of 1001

u-blox cellular modules - AT commands manual

25 DNS
DNS service requires the user to define and activate a connection profile, either PSD or CSD.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
See +UPSD, +UPSDA and +UPSND AT commands for establishing a PSD connection.
SARA-G3 / LEON-G1
See +UCSD, +UCSDA and +UCSND AT commands for establishing a CSD connection.
When these command report an error which is not a +CME ERROR, the error class and code is provided through+USOER AT command.

25.1 Resolve name / IP number through DNS +UDNSRN+UDNSRN
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 120 s
TCP/UDP/IP
Error

25.1.1 Description
Translates a domain name to an IP address or an IP address to a domain name by using an available DNS. There
are two available DNSs, primary and secondary. The network usually provides them after a GPRS activation ora CSD establishment. They are automatically used in the resolution process if available. The resolver will use
first the primary DNS, otherwise if there is no answer, the second DNS will be involved.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The user can replace each network provided DNS by setting its own DNS for a PSD context by means of
the +UPSD AT command. If a DNS value different from "0.0.0.0" is provided, the user DNS will replace thecorrespondent network-provided one. Usage of the network provided DNSs is recommended.
SARA-G3 / LEON-G1
The user can replace each network provided DNS by setting its own DNS for a CSD context by means of
the +UCSD AT command. If a DNS value different from "0.0.0.0" is provided, the user DNS will replace thecorrespondent network-provided one. Usage of the network provided DNSs is recommended.
The DNS resolution timeout depends on the number of DNS servers available to the DNS resolution
system. The response time for the DNS resolution is estimated in case 8 servers are used to perform thistask.
Pay attention to the DNS setting for the different profiles since the user DNS can be put into action if thecorresponding profile is activated (if the user sets a DNS for a profile, and a different profile is activated,
the user DNS has no action and the network DNS is used if available).

25.1.2 Syntax
Type
Set

SyntaxAT+UDNSRN=<resolution_type>,<domain_ip_string>[,<async>]

Response+UDNSRN: <resolved_ip_address>

ExampleAT+UDNSRN=0,"www.google.com"

OK+UDNSRN: "216.239.59.147"

or

OK
AT+UDNSRN=0,"www.google.com",1+UDNSRN: <resolved_domain_
name>
OK

UBX-13002752 - R67

OK+UUDNSRN: "216.239.59.147"
AT+UDNSRN=0,"www.google.com",
0

25 DNS

Page 648 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse+UUDNSRN: <result_code>[,<resolved_ip_address>]+UUDNSRN: <result_code>[,<resolved_domain_name>]+UUDNSRN: -1

URC

Example+UDNSRN: "216.239.59.147"
OK+UUDNSRN: 0,"216.239.59.147"+UUDNSRN: 0,"somedomain.com"+UUDNSRN: -1

25.1.3 Defined values
Parameter<resolution_type>

Type
Number<async>Number<resolved_ip_
address><resolved_domain_name><result_code>

StringDescription
Type of resolution operation:• 0: domain name to IP address• 1: IP address to domain name (host by name)
Domain name (<resolution_type>=0) or the IP address in (<resolution_type>=1) to beresolved
Asynchronous DNS resolution flag. Allowed values:• 0 (default value): the final result code is returned only once the DNS response isavailable, locking the AT interface until the DNS activity is running• 1: a final result code (OK or an error result code) is returned immediately unlocking
the AT interface and making it available for the execution of other AT commands.
Once the result of DNS resolution becomes available, it is notified to the AT
interface through the +UUDNSRN URC
Resolved IP address corresponding to the specified domain name

StringResolved domain name corresponding to the provided IP address

NumberResult code of DNS resolution:• 0: no error• -1: DNS resolution failed. In this case the <resolved_ip_address> or the <resolved_
domain_name> fields are not present<domain_ip_string> String

25.1.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U201-03A / SARA-U201-03B / SARA-U201-03X /SARA-U201-63B / SARA-U260 / SARA-U270 / SARA-U280 / LISA-U200-00S / LISA-U200-01S /LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S / LISA-U201-03A /LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G340 /SARA-G350 / LEON-G1• The <async> parameter and the +UUDNSRN URC are not available.
SARA-G4• The <async> parameter and the +UUDNSRN URC are not available.
• <resolution_type>=1 is not supported.
• The information text response to the set command provide also the resolution operation as follow:+UDNSRN: <resolution_type>,<resolved_ip_address>.

UBX-13002752 - R67

25 DNS

Page 649 of 1001

u-blox cellular modules - AT commands manual

25.2 Dynamic DNS update +UDYNDNS+UDYNDNS
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
- (except URC)
+CME Error

25.2.1 Introduction
The IP address assigned to a module by the network provider is often dynamic; this means the IP addresschanges every time a PDP context is enabled.
This could be a problem when it is needed to identify an internet host with a domain name, because they areusually used with static IP address that never changes (or rarely changes).
To solve this problem, the dynamic DNS services provide a way to assign a domain name to a host that owns
a dynamic IP address, but they require a client that sends the latest IP given by the network to these services,
to update their DNS tables.
With the +UDYNDNS command u-blox cellular modules can access to dynamic DNS services.
This functionality is disabled by default, but once configured and enabled it automatically sends updates tothe configured Dynamc DNS service every time the module IP address change. The functionality only works forinternal PDP context (see Multiple PDP contexts).

25.2.2 Description
Sets up the dynamic DNS client functionality. This command is part of the internal TCP/IP stack so it only works
for internal PDP contexts (managed by +UPSD and +UPSDA command; see the Multiple PDP contexts).
The command configuration is stored into the NVM: if enabled, it automatically works after a reboot.
The following dynamic DNS providers are supported:• TZO.com• DynDNS.org• DynDNS.it• No-IP.org• DNSDynamic.org
During the service subscription phase the dynamic DNS provider gives a domain name, a username and apassword that the AT application will use later.
If the DYNDNS client is enabled when an internal PDP connection is already active, the DYNDNS client starts
working on the next PDP context activation.
This functionality is only available for the PDP context enabled with +UPSDA command.
Before changing the dynamic DNS client configuration it is required to stop (deactivate) it. Any attempt
to reconfigure an already running DNS client raises an error.
The dynamic DNS update is not allowed during the first 60 s after module power on. If a PDP connection
is established before this time, a URC notifies that the update has been delayed. In this case the update
is performed once the 60 s are elapsed.
The dynamic DNS protocol does not allow more than one update every 60 s, anyhow the module's DYNDNS
client will respect specific timing rules depending on the selected provider policies.
Due to the various caches involved in the DNS resolution process, the time since the DNS update is done
until it is available for a user, can significantly change among different internet providers.

UBX-13002752 - R67

25 DNS

Page 650 of 1001

u-blox cellular modules - AT commands manual

25.2.3 Syntax
Type
Set

SyntaxResponse
AT+UDYNDNS=<on_off>[,<service_ OK
id>,<domain_name>,<username>,<password>]

ExampleEnable the dynamic DNS client
using the TZO DNS service and thedomain name "remote001.tzo.net".
AT+UDYNDNS=1,0,"remote00
1.tzo.net","dummy_username","dummy_password"
OK
Disable the dynamic DNS client:
AT+UDYNDNS=0

Read

AT+UDYNDNS?

Test

AT+UDYNDNS=?

+UDYNDNS: <on_off>,<service_id>,<domain_name>,<username>,<password>OK+UDYNDNS: (list of supported <on_off>),(list of supported <service_id>),<domain_name>,<username>,<password>)
OK+UUDYNDNS: <status>,<code>

URC

OK+UDYNDNS: 1,0,"remote00
1.tzo.net","dummy_username","dummy_password"OK+UDYNDNS: (0-1),(0-4),"domain_name","username","password"OK+UUDYNDNS: 1,025.2.4 Defined values
Parameter<on_off>Type
Number<service_id>

Number<domain_name>

StringDescription
Enable / disable the dynamic DNS client:• 0 (factory-programmed value): disable the client• 1: enable the client
Indicates which dynamic DNS service provider to use:
• 0 (factory-programmed value): TZO.com• 1: DynDNS.org• 2: DynDNS.it• 3: No-IP.org• 4: DynamicDNS.org
Mandatory parameter with <on_off>=1, not allowed with <on_off>=0.
Indicates which domain name should be associated with the module IP address. The
dynamic DNS service provider provides this value.
Maximum length: 64 bytes.
Mandatory parameter with <on_off>=1, not allowed with <on_off>=0.

<username>

String

The factory-programmed value is an empty string.
The username used for the client authentication.
Maximum length: 64 characters.
Mandatory parameter with <on_off>=1, not allowed with <on_off>=0.

<password>

String

The factory-programmed value is an empty string.
The password used for the client authentication.
Maximum length: 32 characters.
Mandatory parameter with <on_off>=1, not allowed with <on_off>=0.

<status>UBX-13002752 - R67

Number

The factory-programmed value is an empty string.
This is the internal status of the dynamic DNS client. Each time the internal statuschanges or there is an error the URC +UUDYNDNS is issued:• 0: client inactive/stopped• 1: client enabled/active• 2: DNS update successfully executed• 3: DNS update failed

25 DNS

Page 651 of 1001

u-blox cellular modules - AT commands manual

ParameterType<code>

NumberDescription• 4: DNS update delayed• 5: No DNS update is required• 6: Self deactivation: the dynamic DNS client will stop due to internal error or
DynDNS protocol specification
This is the code returned by the +UUDYNDNS URC. The meaning of the <code>value is described in Dynamic DNS unsolicited indication codes (see Dynamic DNS
unsolicited indication codes).

25.2.5 Notes••

In case of self deactivation (+UUDYNDNS status = 6), the client is disabled (saving the disabled setting
into the NVM); the customer has then to identify the cause (usually bad configuration of the client) andmanually re-activate it. After a self deactivation it is always required to re-activate the client.
If UDYNDNS is enabled and properly configured an +UUDYNDNS URC (+UUDYNDNS: 1,0) will be displayed
at the "system power on" on AT terminal. The +UUDYNDNS URC (+UUDYNDNS: 1,0) notifies that the
UDYNDNS service is enabled and that an dynamic IP address update will occur when an Internal PDP
context will be activated or when an Internal PDP context IP address will change.

TOBY-L2 / MPCI-L2• The +UUDYNDNS URC (i.e. +UUDYNDNS: 1,0) is not displayed at the "system power on" on USB connected
AT terminals.

25.2.6 DynDNS client behavior in case of error
When the error result code is in range 1-10 and 100-108 the client waits for 60 s before allowing any update
operation.
In all the other cases (error in range from 40 to 57) the following behaviors are applied:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3 - For TZO.com:
DynDNS client error code
40
41
45
53
55
46
54
56
57

•

Provider error code
200
304
401
403
414
405
407
415
480

Client action
Next update will be possible after 60 s
Next update will be possible after 10 minutes
Client self deactivation
Client self deactivation
Next update will be possible after 60 s
Client self deactivation
Client self deactivation
Client self deactivation
Next update will be possible after 24 hours

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3 - For DynDNS.org, DynDNS.it,
No-IP.org and DNSDynamic.org:
DynDNS client error code
40
41
45
47
42
43
44
48
46
49
50
51
52

UBX-13002752 - R67

Provider error code
good
nochg
badauth!donator
notfqdnnohostnumhostabuse
badagent
dnserr911
badsys!yoursClient action
Next update will be possible after 60 s
Next update will be possible after 10 minutes
Next update will be possible after 24 hours
Next update will be possible after 24 hours
Client self deactivation
Client self deactivation
Client self deactivation
Client self deactivation
Client self deactivation
Next update will be possible after 30 minutes
Next update will be possible after 30 minutes
Client self deactivation
Client self deactivation

25 DNS

Page 652 of 1001

u-blox cellular modules - AT commands manual

26 Internet protocol transport layer
26.1 Introduction
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
Before using TCP/IP services, a connection profile must be defined and activated. The sockets can be
managed independently and simultaneously over the same bearer (either PSD or CSD). AT commands forboth reading and writing data on sockets are provided and the URC notifies the external application ofincoming data and transmission result, no need for polling.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
See +UPSD, +UPSDA and +UPSND AT commands for establishing a PSD connection.
SARA-G3 / LEON-G1
See +UCSD, +UCSDA and +UCSND AT commands for establishing a CSD connection.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
When these commands report an error result code which is not a +CME ERROR, the error code can bequeried using the +USOER or +USOCTL (specifying the socket ID and with <param_id>=1) AT commands.
The maximum number of sockets that can be managed depends on the module series:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 - 7• LEON-G1 - 16
TOBY-L2 / MPCI-L2
Check the module is in bridge mode (+UBMCONF: 1 / +UDPDP: 1) before issuing any internet suite AT
commands.
The UDP protocol has not any flow control mechanism and packets might be lost in the following
scenarios:• No network signal is available• Unreliable radio interface (e.g. mobility in GPRS, where cell reselections can lead to data loss, that canbe contrasted with the usage of LLC ack reliability QoS parameter
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1
Some network operators close dynamic NATs after few minutes if there is no activity on the connection(no data transfer in the period). To solve this problem enable the TCP keep alive options with 1 minutedelay (see the +USOSO AT command).
When both TCP and UDP socket are used at the same time at the maximum throughput (downlink anduplink at the maximum allowed baud rate) it is possible to lose some incoming UDP packets due to internalbuffer limitation. A possible workaround is provided as follows:• If it is possible, adopt an application layer UDP acknowledge system• On LEON-G1 series, stop sending TCP packet (and check with the +USOCTL command that theoutgoing buffer is empty) when expecting to receive UDP data
LEON-G1
IP dotted notation does not support a leading 0 in an IP address (e.g. IP = 010.128.076.034 is not supported,
10.128.76.34 is supported).
LEON-G1
The +UPING command uses the TCP/IP resources in an exclusive way. All the other TCP/IP operations
executed after the execution of the +UPING AT command will wait for the execution of this command.

26.2 IPv4/IPv6 addressing
26.2.1 Introduction
The section describes the IP addressing formats and IP address rules used by TCP/IP UDP/IP enabledapplications.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 653 of 1001

u-blox cellular modules - AT commands manual

26.2.2 IPv4
Format:• 32 bits long in dot-decimal notation (without leading 0 notation).
• All the decimal numbers must be in range 0-255.
• The dot-octal notation is not supported.
• The dot-hexadecimal notation is not supported.
Examples:IPv4 address254.254.254.254
010.228.76.34
257.228.76.34
0010.0344.0114.0042
0x10.0xE4.0x4C.0x22

Remarks
Valid address
Invalid address; first decimal number prefixed with a leading zero
Invalid address; first decimal number greater than 255
Invalid address; dot-octal notation; decimals given as octal numbers
Invalid address; dot-hexadecimal notation; decimals given as
hexadecimal numbers

Table 83: IPv4 address format examples

26.2.3 IPv6
Format:• 128 bits long represented in 8 groups of 16 bits each.
• The 16 bits of a group are represented as 2 concatenated hexadecimal numbers.
• The groups are separated by a colon character (:).
• The leading 0 in a group is supported.
• A group containing 4 zeros can be abbreviated with one 0.
• Continuous groups (at least 2) with zeroes can be replaced with a double colon (::).
• The double colon can appear only once in an IPv6 address.
Examples:IPv6 address
2001:0104:0000:0000:0000:0104:0000:0000
2001:104:0000:0000:0000:104:0000:0000
2001:104:0:0:0:104:0:0
2001:104::104:0:0

Remarks
Full version, with leading zeros
Abbreviated version, leading zero abbreviation
Abbreviated version, zero group abbreviation
Abbreviated version, one double colon abbreviation

Table 84: IPv6 address format examples
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The internet suite applications do not support the IPv6 address format.
The following AT commands support the IPv6 address format:• Dynamic DNS update: +UDYNDNS• Connect Socket: +USOCO• SendTo command: +USOST• Receive From command: +USORF• Set Listening Socket: +USOLI• IP Change Notification: +UIPCHGN• FTP service configuration: +UFTP• HTTP control: +UHTTP
For packet switched services AT commands (i.e. PDP_addr in +CGDCONT) the format is specified in thecorresponding command section.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 654 of 1001

u-blox cellular modules - AT commands manual

26.3 Create Socket +USOCR+USOCR
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

Attributes

26.3.1 Description
Creates a socket and associates it with the specified protocol (TCP or UDP), returns a number identifying thesocket. Such command corresponds to the BSD socket routine:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G340 /SARA-G350 - Up to 7 sockets can be created.
• LEON-G1 - Up to 16 sockets can be created
It is possible to specify the local port to bind within the socket in order to send data from a specific port. The
bind functionality is supported for both TCP and UDP sockets.
The socket creation operation can be performed only after the PDP context activation on one of thedefined profiles.

26.3.2 Syntax
Type
Set

Test

SyntaxAT+USOCR=<protocol>[,<local_
port>]

Response+USOCR: <socket>

ExampleAT+USOCR=17

OK+USOCR: 2

AT+USOCR=?

+USOCR: (list of supported<protocol>s),(list of supported<local_port>s)OK+USOCR: (6,17),(1-65535)
OKOK

26.3.3 Defined values
Parameter<protocol>

Type
Number<local_port>

Number<socket>NumberDescription• 6: TCP• 17: UDP
Local port to be used while sending data. The range goes from 1 to 65535. If theparameter is omitted it will be set to 0; in this case a random port will be used while
sending data.
Socket identifier to be used for any future operation on that socket.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15

26.3.4 Notes
TOBY-L2 / MPCI-L2• The information text response to the test command does not provide the <local_port> parameter.
SARA-G3• The test command is not supported.
LISA-U1• The bind functionality is supported only for UDP sockets.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 655 of 1001

u-blox cellular modules - AT commands manual

LEON-G1• The socket creation operation can be performed even if the PDP context has not been activated.
• The test command is not supported.
• The bind functionality is supported only for UDP sockets.

26.4 SSL/TLS/DTLS mode configuration on TCP/UDP socket+USOSEC+USOSEC
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201-02S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G4 SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 120 s
+CME Error

Attributes

26.4.1 Description
Enables or disables the use of SSL/TLS/DTLS connection (where supported) on a TCP/UDP socket. The
configuration of the SSL/TLS/DTLS properties is provided with an SSL/TLS/DTLS profile managed by
USECMNG.
The <usecmng_profile_id> parameter is listed in the information text response to the read command only if
the SSL/TLS/DTLS is enabled on the interested socket.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The command is applicable only with TCP sockets.
The enable or disable operation can be performed only after the socket has been created with +USOCR
AT command.
The SSL/TLS/DTLS is supported only with +USOCO command (socket connect command). The SSL/TLS/
DTLS is not supported with +USOLI command (socket set listen command is not supported and the+USOSEC settings will be ignored).

26.4.2 Syntax
Type
Set

Read

SyntaxAT+USOSEC=<socket>,<ssl_tls_
dtls_status>[,<usecmng_profile_
id>]
AT+USOSEC=<socket>

Response
OK

ExampleAT+USOSEC=0,1,1
OK+USOSEC: <socket>,<ssl_tls_dtls_
status>[,<usecmng_profile_id>]

AT+USOSEC=0+USOSEC: 0,1,1

OK
Test

OK
+USOSEC: (list of supported+USOSEC: (0-6),(0,1),(0-4)<socket>s),(list of supported <ssl_
OK
tls_dtls_status>s),(list of supported<usecmng_profile_id>s)

AT+USOSEC=?

OK

26.4.3 Defined values
Parameter<socket>Type
NumberDescription
Socket identifier defined by the AT+USOCR command.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G340 / SARA-G350 - The range goes from 0 to 6.

<ssl_tls_dtls_
status>Number•UBX-13002752 - R67

0 (default value): disable the SSL/TLS/DTLS on the socket.

26 Internet protocol transport layer

Page 656 of 1001

u-blox cellular modules - AT commands manual

ParameterType<usecmng_profile_id>NumberDescription• 1: enable the socket security; a USECMNG profile can be specified with the<usecmng_profile_id> parameter.
Defines the USECMNG profile which specifies the SSL/TLS/DTLS properties to be
used for the SSL/TLS/DTLS connection. The range goes from 0 to 4. If no profile is set
a default USECMNG profile is used (see USECMNG section).

26.4.4 Notes
TOBY-L201-02S / MPCI-L201-02S• The command is not supported by TOBY-L201-02S-00, MPCI-L201-02S-00.

26.5 Set socket option +USOSO+USOSO
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.5.1 Description
Sets the specified standard option (type of service, local address re-use, linger time, time-to-live, etc.) for the
specified socket, like the BSD setsockopt routine.
Issue a set command to set each parameter.

26.5.2 Syntax
Type
Set

SyntaxResponse
AT+USOSO=<socket>,<level>,<opt_ OK
name>,<opt_val>[,<opt_val2>]

Test

AT+USOSO=?

+USOSO: (list of supported<socket>s),(list of supported<level>s)

ExampleAT+USOSO=2,6,1,1
OK+USOSO: (0-6),(0,6,65535)
OKOK

26.5.3 Defined values
Parameter<socket>Type
Number<level>NumberUBX-13002752 - R67

Description
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Allowed values:• 0: IP protocol<opt_name> for IP protocol level may be:o 1: type of service (TOS)<opt_val>: 8 bitmask that represents the flags of IP TOS. The range is 0-255(the default value is 0). For more information, see the RFC 791 [24]o 2: time-to-live (TTL)<opt_val>: unsigned 8 bit value representing the TTL. The range is 0-255 (thedefault value is 255)
• 6: TCP protocol<opt_name> for TCP protocol level may be:o 1: no delay option; do not delay send to coalesce packets;<opt_val>: numeric parameter, it enables/disables the "no delay" option:

26 Internet protocol transport layer

Page 657 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description- 0 (default value): disabled- 1: enabledo 2: keepidle option: send keepidle probes when it is idle for <opt_val> milliseconds<opt_val>: signed 32 bit numeric parameter representing the milliseconds for"keepidle" option. The range is 0-2147483647. The default value is 7200000 (2hours)• 65535: socket<opt_name> for socket level options may be:o 4: local address re-use.
<opt_val>: numeric parameter, it configures the "local address re-use" option.
- 0 (default value): disabled- 1: enabledo 8: keep connections alive.
<opt_val>: numeric parameter, it configures "keep connections alive" option.
- 0 (default value): disabled- 1: enabled
o 32: sending of broadcast messages.
<opt_val>: numeric parameter, it configures "sending of broadcast
messages".
- 0 (default value): disabled- 1: enabledo 128: linger on close if data present.
<opt_val>: numeric parameter, it configures the "linger" option.
- 0 (default value): disabled- 1: enabled<opt_val2>: signed 16 bit numeric parameter, it sets the linger time, the range
goes from 0 to 32767 in milliseconds. The default value is 0.
o 512: local address and port re-use.
<opt_val>: numeric parameter, it configures the "local address and port reuse".
- 0 (default value): disabled- 1: enabled<opt_name>

Number<opt_val>

Number<opt_val2>

NumberType and supported content depend on the related <level> parameter value (details
are given above).
Type and supported content depend on the related <level> parameter value (details
are given above).
Type and supported content depend on the related <level> parameter value (details
are given above).

26.5.4 Notes
TOBY-L2 / MPCI-L2• It is not possible to change the settings of bit 6 and 7 for Type of Service (<level>=0 and <opt_name>=
1, i.e. AT+USOSO=0,0,1,<opt_val>).
SARA-G3 / LEON-G1• The test command is not supported.
SARA-G4• If <level>= 65535, <opt_name>= 512 is not supported.
• The range of the linger time (<opt_val2> parameter) goes from 0 to 65535 s.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 658 of 1001

u-blox cellular modules - AT commands manual

26.6 Get Socket Option +USOGO+USOGO
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.6.1 Description
Retrieves the specified standard option (type of service, local address re-use, linger time, time-to-live, etc) for
the specified socket, like the BSD getsockopt routine.

26.6.2 Syntax
Type
Set

Test

SyntaxResponse
AT+USOGO=<socket>,<level>,<opt_ +USOGO: <opt_val>[,<opt_val2>]
name>
OK
AT+USOGO=?

+USOGO: (list of supported<socket>s),(list of supported<level>s)

ExampleAT+USOGO=0,0,2+USOGO: 255
OK+USOGO: (0-6),(0,6,65535)
OKOK

26.6.3 Defined values
Parameter<socket>Type
NumberDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15<level>Number•••UBX-13002752 - R67

0: IP Protocol<opt_name> for IP protocol level may be:o 1: type of service<opt_val>: 8 bit mask that represents the flags of IP TOS. For more
information see the RFC 791 [24]. The range is 0-255. The default value is 0
o 2: time-to-live<opt_val>: unsigned 8 bit value representing the TTL. The range is 0-255. The
default value is 0.
6: TCP Protocol<opt_name> for TCP protocol level may be:o 1: no delay option: do not delay send to coalesce packets<opt_val>: numeric parameter, it enables/disables the "no delay" option- 0 (default value): disabled- 1: enabledo 2: keepidle option: send keepidle probes when idle for <opt_val> milliseconds<opt_val>: signed 32 bit number value representing the milliseconds for"keepidle" option. The range 0-2147483647. The default value is 7200000 (2hours)
65535: socket<opt_name> for the socket level options may be:o 4: local address re-use<opt_val>: numeric parameter, it configures the "local address re-use" option:- 0 (default value): disabled- 1: enabledo 8: keep connections alive

26 Internet protocol transport layer

Page 659 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description<opt_val>: numeric parameter, it configures the "keep connections alive"
option:- 0 (default value): disabled- 1: enabled
o 32: sending of broadcast messages<opt_val>: numeric parameter, it configures the "sending of broadcast
messages":- 1: enabled- 0 (default value): disabledo 128: linger on close if data present<opt_val>: numeric parameter, it sets on/off the "linger" option.
- 0 (default value): disabled- 1: enabled<opt_val2>: signed 16 bit numeric value, linger time, the range goes from 0 to
32767 in milliseconds. The default value is 0.
o 512: local address and port re-use<opt_val>: numeric parameter, it enables/disables "local address and port reuse":- 0 (default value): disabled- 1: enabled

26.6.4 Notes
SARA-G3• The test command is not supported.
SARA-G4• If <level>= 65535, <opt_name>= 512 is not supported.
• The range of the linger time (<opt_val2> parameter) goes from 0 to 65535 s.
LEON-G1• The test command is not supported.

26.7 Close Socket +USOCL+USOCL
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
No
No< 1 s (except+CME Error
URC)

26.7.1 Description
Closes the specified socket, like the BSD close routine. In case of remote socket closure the user is notified
via the URC.
By default the command blocks the AT command interface until the the completion of the socket close
operation. By enabling the <async_close> flag, the final result code is sent immediately. The following+UUSOCL URC will indicate the closure of the specified socket.

26.7.2 Syntax
Type
Set

SyntaxAT+USOCL=<socket>[,<async_
close>]

UBX-13002752 - R67

ResponseOK

26 Internet protocol transport layer

ExampleAT+USOCL=2
OK

Page 660 of 1001

u-blox cellular modules - AT commands manual

Type
Test

SyntaxAT+USOCL=?

Response+USOCL: (list of supported<socket>s)
OK+UUSOCL: <socket>

URC

Example+USOCL: (0-6),(0-1)
OK+UUSOCL: 2

26.7.3 Defined values
Parameter<socket>Type
Number<async_close>

NumberDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Asynchronous close flag. The flag has effect for TCP connections only. Allowed
values:• 0 (default value): the operation result is returned only once the result of the TCP
close becomes available, locking the AT interface until the connection closes.
• 1: the final result code is returned immediately unlocking the AT interface andmaking it available for the execution of other AT commands. Once the result of TCP
close becomes available, it is notified to the AT interface through the +UUSOCL
URC.

26.7.4 Notes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The <async_close> parameter is not supported.
SARA-G3 / LEON-G1• The test command is not supported.

26.8 Get Socket Error +USOER+USOER
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
TCP/UDP/IP
Error +CME
Error

Attributes

26.8.1 Description
Retrieves the last error occurred in the last socket operation, stored in the BSD standard variable error.

26.8.2 Syntax
Type
ActionSyntaxAT+USOER

Response+USOER: <socket_error>

Example+USOER: 104

OKOK

26.8.3 Defined values
Parameter<socket_error>

Type
NumberDescription
Code of the last error occurred in a socket operation. The allowed values are listed inAppendix A.8•

UBX-13002752 - R67

0: no error

26 Internet protocol transport layer

Page 661 of 1001

u-blox cellular modules - AT commands manual

26.9 Connect Socket +USOCO+USOCO
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partialNo
No
No< 120 s
+CME Error

Attributes

26.9.1 Description
Establishes a peer-to-peer connection of the socket to the specified remote host on the given remote port, likethe BSD connect routine. If the socket is a TCP socket, the command will actually perform the TCP negotiation(3-way handshake) to open a connection. If the socket is a UDP socket, this function will just declare the remote
host address and port for later use with other socket operations (e.g. +USOWR, +USORD). This is important
to note because if <socket> refers to a UDP socket, errors will not be reported prior to an attempt to write orread data on the socket.
The estimated response time depends also by the DNS resolution. For further details about the estimatedresponse time related to the DNS resolution, see the +UDNSRN AT command.

26.9.2 Syntax
Type
Set

SyntaxAT+USOCO=<socket>,<remote_addr>,<remote_port>[,<async_
connect>]

Response
OK

ExampleAT+USOCO=3,"151.63.16.9",1200
OK
AT+USOCO=2,"151.63.16.9",8200,1
OK+UUSOCO: 2,0
AT+USOCO=2,"151.63.16.9",8230,0

Test

AT+USOCO=?

+USOCO: (list of supported<socket>s),"remote_host",(list of
supported <remote_port>s),(list of
supported <async_connect>s)
OK+UUSOCO: <socket>,<socket_
error>URC

OK+USOCO: (0-6),"remote_host",(165535),(0-1)
OK+UUSOCO: 2,026.9.3 Defined values
Parameter<socket>Type
Number<remote_addr>

String<remote_port><async_connect>

NumberNumberUBX-13002752 - R67

Description
Socket identifier to be used for any future operation on that socket.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Remote host IP address or domain name of the remote host. For IP address format
reference see the IP addressing.
Remote host port, in range 1-65535
Asynchronous connect flag. The flag has effect for TCP connections only. Allowed
values:• 0 (default value): the operation result is returned only once the TCP connection isestablished, locking the AT interface until the connection activity is running• 1: the final result code is returned immediately unlocking the AT interface andmaking it available for the execution of other AT commands. Once the result of
TCP connection becomes available, it is notified to the AT interface through the+UUSOCO URC.

26 Internet protocol transport layer

Page 662 of 1001

u-blox cellular modules - AT commands manual

Parameter<socket_error>

Type
NumberDescription
Code of the last error occurred in a socket operation. The allowed values are listed inAppendix A.8:
• 0: no error, connection successful

26.9.4 Notes•

In case of the socket connection with the asynchronous flag:o the socket will be closed if a further +USOCO AT command is issued before having received the+UUSOCO URC of the first AT command.
o it is not possible to connect a second socket before the reception of the +UUSOCO URC related tothe pending socket connection.

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U201-03A / SARA-U201-03B / SARA-U201-03X /SARA-U201-63B / SARA-U260 / SARA-U270 / SARA-U280 / LISA-U200-00S / LISA-U200-01S /LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S / LISA-U201-03A /LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G340 /SARA-G350 / LEON-G1• The <async_connect> parameter and the +UUSOCO URC are not available.
TOBY-L2 / MPCI-L2• If the +UPSD command sets the PSD profile protocol type to IPv6, an IPv6 address shall be used for the
remote host IP address parameter.
SARA-G3 / LEON-G1• The test command is not supported.

26.10 Write socket data +USOWR+USOWR
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No
<1s
+CME Error

26.10.1 Description
Writes the specified amount of data to the specified socket, like the BSD write routine, and returns the numberof bytes of data actually written. The command applies to UDP sockets too, after a +USOCO command.
There are three kinds of syntax:• Base syntax normal: writing simple strings to the socket, some characters are forbidden• Base syntax HEX: writing hexadecimal strings to the socket, the string will be converted in binary data andsent to the socket; see the AT+UDCONF=1 command description to enable it• Binary extended syntax: mandatory for writing any character in the ASCII range [0x00, 0xFF]
Some notes about the TCP socket:• If no network signal is available, the TCP packets are enqueued until the network will become available
again. If the TCP queue is full the +USOWR command will return an error result code. To get the lastsocket error use the +USOCTL=1 command. If the error code returned is 11, it means that the queueis full.
• If the connection is closed by the remote host, the +UUSOCL URC is not sent until all received data isread using the AT+USORD command. If AT+USOWR command is used in this situation, an error result
code is returned. See also the Notes section about the specific product behavior• If the connection is closed by the remote host and binary interface started with AT+USOWR commandis still waiting for data, an error result code is returned indicating that the binary interface was closed.
After the error result code a +UUSOCL URC is reported indicating that the socket was closed.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 663 of 1001

u-blox cellular modules - AT commands manual

Some notes about the UDP socket:• Due to the UDP specific AT commands, it is preferred to use the +USOST command to send data via
UDP socket. This command does not require the usage of +USOCO before sending data.
• If no network signal is available, out going UDP packet may be lost.
The information text response indicates that data has been sent to lower level of protocol stack. This is
not an indication of an acknowledgment received by the remote server the socket is connected to.

26.10.2 Syntax
Type
SyntaxBase syntax
Set
AT+USOWR=<socket>,<length>,<data>

Response

Example+USOWR: <socket>,<length>

AT+USOWR=3,12,"Hello world!"

OK+USOWR: 3,12OK

Binary syntax
Set
AT+USOWR=<socket>,<length>@<data>AT+USOWR=3,16+USOWR: <socket>,<length>@16 bytes of data

OK

+USOWR: 3,16
OK

Test

AT+USOWR=?

+USOWR: (list of supported<socket>s),(list of supported<length>s),"HEX data"+USOWR: (list of supported<socket>s),(list of supported<length>s),"data"+USOWR: (0-6),(0-512),"HEX data"+USOWR: (0-6),(0-1024),"data"+USOWR: (0-6),(0-1024)
OK+USOWR: (list of supported<socket>s),(list of supported<length>s)OK

26.10.3 Defined values
Parameter<socket>Type
Number<length>Number<data>

StringDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Number of data bytes to write:• Base syntax normal mode: range 1-1024• Base syntax HEX mode: range 1-512• Binary extended syntax: range 1-1024
Data bytes to be written. Not all of the ASCII charset can be used.

26.10.4 Notes•••

For base syntax:
o The value of <length> and the actual length of <data> must match
For base syntax HEX mode:o Only the ASCII characters 0-9, A-F and a-f are allowed.
o The length of the <data> parameter must be two times the <length> parameter.
For binary syntax:
o After the command is sent, the user waits for the @ prompt. When it appears the stream of bytes
can be provided. After the specified amount of bytes has been sent, the system provides the final
result code. The feed process cannot be interrupted i.e. the return in the command mode can beeffective only when the number of bytes provided is the declared one.
o After the @ prompt reception, wait for a minimum of 50 ms before sending data.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 664 of 1001

u-blox cellular modules - AT commands manual•o The binary extended syntax is the only way for the system to accept control characters as data; for
the AT command specifications 3GPP TS 27.005 [15], characters like <CR>, <CTRL-Z>, quotation
marks, etc. have a specific meaning and they cannot be used like data in the command itself. The
command is so extended with a specific acceptance state identified by the @ prompt.
o This feature can be successfully used when there is need to send a byte stream which belongs to a
protocol that has any kind of characters in the ASCII range [0x00,0xFF].
o In binary mode the module does not display the echo of data bytes.
o Binary syntax is not affected by HEX mode option.
For <data> parameter not all of the ASCII charset can be used.

TOBY-L2 / LEON-G1• TCP socket: A write operation performed when the remote host has closed its part of the TCP connection(FIN packet received by the module) - but there is still data to be read from the socket - is accepted. Thisbehavior differs from LISA-U2 / SARA-U2 series, where this operation returns an error. It is suggested toread all the socket data before triggering a write command, to avoid this situation.
SARA-G3 / LEON-G1• The range of <length> parameter iso Base syntax normal mode: 0-512
o Base syntax HEX mode: 0-250• The test command is not supported.
LEON-G1• For the binary syntax in binary mode the module displays the echo of data bytes.

26.11 SendTo command (UDP only) +USOST+USOST
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
<1s
+CME Error

26.11.1 Description
Writes the specified amount of data to the remote address, like the BSD sendto routine, and returns thenumber of bytes of data actually written. It can be applied to UDP sockets only. This command allows the reuseof the same socket to send data to many different remote hosts.
There are three kinds of syntax:• Base syntax normal: writing simple strings to the socket, there are characters which are forbidden.
• Base syntax HEX: writing hexadecimal strings to the socket, the string will be converted in binary data andsent to the socket. To enable it, see the AT+UDCONF=1 command description.
• Binary extended syntax: mandatory for writing any character in the ASCII range [0x00, 0xFF].
It is strongly recommended using this command to send data while using UDP sockets. It is also
recommended avoiding the +USOCO AT command usage with UDP socket.
If no network signal is available, outcoming UDP packet may be lost.
The information text response to the test command provides the information about the bynary extended
syntax only where supported.

26.11.2 Syntax
Type
SyntaxBase syntax

UBX-13002752 - R67

Response

26 Internet protocol transport layer

ExamplePage 665 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+USOST=<socket>,<remote_addr>,<remote_port>,<length>,<data>,[<seq_no>]

Response+USOST: <socket>,<length>
OK

ExampleAT+USOST=3,"151.9.34.66",449,16,"16 bytes of data"+USOST: 3,16
OK

Binary syntax
Set
AT+USOST=<socket>,<remote_addr>,<remote_port>,<length>@<data>AT+USOST=3,"151.9.34.66",449,16+USOST: <socket>,<length>@16 bytes of data

After the"@" prompt <length> bytes
OKof data are entered+USOST: 3,16
OK

Test

AT+USOST=?

+USOST: (list of supported<socket>s),"remote_host",(list of
supported <remote_port>s),(listof supported <length>s),(list of
supported <seq_no>s),"HEX data"+USOST: (list of supported<socket>s),"remote_host",(list of
supported <remote_port>s),(listof supported <length>s),(list of
supported <seq_no>s),"data"+USOST: (1-8),"remote_host",(165535),(1-512),(1-255),"HEX data"+USOST: (1-8),"remote_host",(165535),(1-1024),(1-255),"data"
OK[+USOST: (list of supported<socket>s),"remote_host",(list of
supported <remote_port>s),(list of
supported <length>s)]
OK+UUSOST: <socket>,<seq_no>,<UDP_result>

URC+USOST: 3,1,1

26.11.3 Defined values
Parameter<socket>Type
Number<remote_addr>

String<remote_port><length>NumberNumber<data><seq_no><UDP_result>

StringNumberNumberDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Remote host IP address or domain name of the remote host. For IP address format
reference, see the IP addressing.
Remote host port, in range 1-65535
Number of data bytes to write:• Base syntax normal mode: range 1-1024• Base syntax HEX mode: range 1-512• Binary syntax mode: range 1-1024
Data bytes to be written (not all of the ASCII charset can be used)
Sequence number of UDP packet, in range 1-255. The default value is 1.
Supported values:• 0: fail• 1: success26.11.4 Notes••

For base syntax:
o The value of <length> and the actual length of <data> must matcho For base syntax HEX mode, only ASCII characters 0-9, A-F and a-f are allowed. The length of the<data> parameter must be two times the <length> parameterFor binary syntax:
o After the command is sent, the user waits for the @ prompt. When it appears the stream of bytes
can be provided. After the specified amount of bytes has been sent, the system returns with final

UBX-13002752 - R67

26 Internet protocol transport layer

Page 666 of 1001

u-blox cellular modules - AT commands manual

o

o
o
o

result code. The feed process cannot be interrupted i.e. the return in the command mode can beeffective only when the number of bytes provided is the declared one
That binary extended syntax is the only way for the system to accept control characters as data; for
the AT command specifications [15], characters like <CR>, <CTRL-Z>, quotation marks, etc. havea specific meaning and they cannot be used like data in the command itself. The command is so
extended with a specific acceptance state identified by the @ prompt
This feature can be successfully used when there is need to send a byte stream which belongs to a
protocol that has any kind of characters in the ASCII range [0x00,0xFF]
In binary mode the module does not display the echo of data bytes
Binary syntax is not affected by HEX mode option

TOBY-L2 / MPCI-L2• The <seq_no> parameter and the +UUSOST URC are not supported.
• If the +UPSD command sets the PSD profile protocol type to IPv6, an IPv6 address shall be used for the
remote host IP address.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4• The <seq_no> parameter and the +UUSOST URC are not supported.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270 / LISA-U1• For <remote_addr> parameter only IP address is allowed.
SARA-G3 / LEON-G1• The <seq_no> parameter and the +UUSOST URC are not supported.
• For <remote_addr> parameter only IP address is allowed.
• The range of <length> parameter iso Base syntax: 0-512
o Base syntax HEX mode: 0-250• The test command is not supported.
LEON-G1• For the binary syntax in binary mode the module displays the echo of data bytes.

26.12 Read Socket Data +USORD+USORD
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 1 s (except+CME Error
URC)

26.12.1 Description
Reads the specified amount of data from the specified socket, like the BSD read routine. This command canbe used to know the total amount of unread data.
For the TCP socket type the URC +UUSORD: <socket>,<length> notifies the data bytes available for reading,either when buffer is empty and new data arrives or after a partial read by the user.
For the UDP socket type the URC +UUSORD: <socket>,<length> notifies that a UDP packet has been received,
either when buffer is empty or after a UDP packet has been read and one or more packets are stored in thebuffer.
In case of a partial read of a UDP packet +UUSORD: <socket>,<length> will show the remaining number of databytes of the packet the user is reading.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 667 of 1001

u-blox cellular modules - AT commands manual

If the UART interface of the application processor has a RX FIFO of only 1 character, it is highly
recommended to set the <length> parameter lower than 64.
(about UDP socket) Due to the UDP specific AT command, it is preferred to use the +USORF command
to read data from UDP socket. +USORF command does not require the usage of +USOCO before readingdata.
When applied to UDP active sockets if the UDP socket is not set in listening mode (see +USOLI) it will not
be possible to receive any packet if a previous write operation is not performed.
If the HEX mode is enabled (refer to AT+UDCONF=1 command) the received data will be displayed using
an hexadecimal string.

26.12.2 Syntax
Type
Set

SyntaxAT+USORD=<socket>,<length>

Test

AT+USORD=?

Response
Example+USORD: <socket>,<length>,<data AT+USORD=3,16
in the ASCII [0x00,0xFF] range>+USORD: 3,16,"16 bytes of data"
OK
OK+USORD: (list of supported+USORD: (0-6),(0-1024)<socket>s),(list of supportedOK<length>s)OK+UUSORD: <socket>,<length>

URC+UUSORD: 3,16

26.12.3 Defined values
Parameter<socket>Type
Number<length>Number<data>

StringDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Number of data bytes• to read stored in buffer, in range 0-1024 in the set command• read from buffer, in range 0-1024• stored in buffer for the URC
Data bytes to be read

26.12.4 Notes
•

•

•
•

The returned data may be any ASCII character in the range [0x00,0xFF] i.e. control characters. The
starting quotation marks shall not be taken into account like data; the first byte of data starts after
the first quotation marks. Then the other characters are provided for a <length> amount. An application
should rely on the <length> info to count the received number of characters (after the starting quotation
marks) especially if any protocol control characters are expected.
If an application deals with letter and number characters only i.e. all of the expected characters areoutside the [0x00, 0x1F] range and are not quotation marks, the AT+USORD response quotation marks
can be assumed to identify the start and the end of the received data packet. Always check <length> toidentify the valid data stream.
If the number of data bytes requested to be read from the buffer is bigger than the number of bytes
stored in the buffer only the available amount of data bytes will be read.
When <length>= 0, the command returns the total amount of data present in the network buffer.
Example: 23 unread bytes in the socket.
AT+USORD=3,0+USORD: 3,23
OK•

If the HEX mode is enabled, the length of <data> will be 2 times <length>.

SARA-G3 / LEON-G1• The test command is not supported.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 668 of 1001

u-blox cellular modules - AT commands manual

26.13 Receive From command (UDP only) +USORF+USORF
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 1 s (except+CME Error
URC)

26.13.1 Description
Reads the specified amount of data from the specified UDP socket, like the BSD recvfrom routine. The URC+UUSORF: <socket>,<length> (or also +UUSORD: <socket>,<length>) notifies that new data is available forreading, either when new data arrives or after a partial read by the user for the socket. This command can also
return the total amount of unread data.
This command can be applied to UDP sockets only, and it can be used to read data after both +UUSORD and+UUSORF unsolicited indication.
If the HEX mode is enabled (see +UDCONF=1) the received data will be displayed using an hexadecimalstring.

26.13.2 Syntax
Type
Set

SyntaxAT+USORF=<socket>,<length>

Test

AT+USORF=?

Response+USORF: <socket>,<remote_ip_
addr>,<remote_port>,<length>,<data in the ASCII [0x00,0xFF]
range>OK+USORF: (list of supported<socket>s),(list of supported<length>s)OK+UUSORF: <socket>,<length>

URC

ExampleAT+USORF=3,16+USORF: 3,"151.9.34.66",2222,16,"16
bytes of data"
OK+USORF: (0-6),(0-1024)
OK+UUSORF: 3,16

26.13.3 Defined values
Parameter<socket>Type
Number<remote_ip_addr><remote_port><length>StringNumberNumber<data>

StringDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Remote host IP address. For IP address format reference see the IP addressing.
Remote host port, in range 1-65535
Number of data bytes:• to read stored in buffer, in range 0-1024 in the set command.
• read from buffer, in range 0-1024.
• stored in buffers for the URC.
Data bytes to be read

26.13.4 Notes•

Each packet received from the network is stored in a separate buffer and the command is capable to read
only a packet (or e portion of it) at time. This means that if <length> is greater than the packet size, thecommand will return a maximum amount of data equal to the packet size, also if there are other packets
in the buffer. The remaining data (i.e. the remaining UDP packets) can be read with further reads.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 669 of 1001

u-blox cellular modules - AT commands manual

•

•

•

The returned data may have any kind of ASCII character in the range [0x00,0xFF] i.e. control characterstoo. The starting quotation marks shall not be taken into account like data; the first byte of data starts
after the first quotation marks. Then the other characters are provided for a <length> amount. At theend of the length byte stream, another quotation marks followed by <CR><LF> are provided for userconvenience and visualization purposes. An application should rely on the <length> info to count thereceived number of characters (after the starting quotation marks) especially if any protocol control
characters are expected.
If an application deals with letter and number characters only i.e. all of the expected characters areoutside the [0x00, 0x1F] range and are not quotation marks, the AT+USORD response quotation marks
can be assumed to identify the start and the end of the received data packet, anyway the <length> fieldusage to identify the valid data stream is recommended.
When <length>= 0, the command returns the total amount of data present in the network buffer.
Example: 23 unread bytes in the socket.
AT+USORF=3,0+USORF: 3,23
OK•

If the HEX mode is enabled, the length of <data> will be 2 times <length>.

TOBY-L2 / MPCI-L2• If the +UPSD command sets the PSD profile protocol type to IPv6, an IPv6 address will be reported in the
remote host IP address.
• The +UUSORD URC does report the length of next packet in UDP RX buffer only (and not the total amountof received data present in the UDP RX buffer for the specified socket).
SARA-G3 / LEON-G1• The test command is not supported.

26.14 Set Listening Socket +USOLI+USOLI
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 1 s (except+CME Error
URC)

26.14.1 Description
Sets the specified socket in listening mode on the specified port of service, waiting for incoming connections(TCP) or data (UDP):• For TCP sockets, incoming connections will be automatically accepted and notified via the
URC +UUSOLI: <socket>,<ip_address>,<port>,<listening_socket>,<local_ip_address>,<listening_port>,
carrying the connected socket identifier, the remote IP address and port.
• For UDP sockets, incoming data will be notified via URC +UUSORF: <listening_socket>,<length>. To know
from which remote IP address and port the data is coming from, use the AT+USORF command.

26.14.2 Syntax
Type
Set

SyntaxAT+USOLI=<socket>,<port>

Response
OK

ExampleTCP sockets
AT+USOLI=2,1200
OK+UUSOLI: 3,"151.63.16.7",1403,2,"82.89.67.164",1200

UBX-13002752 - R67

26 Internet protocol transport layer

Page 670 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

ExampleUDP sockets
AT+USOLI=0,1182
OK

Test

AT+USOLI=?

+USOLI: (list of supported<socket>s),(list of supported<port>s)OK+UUSOLI: <socket>,<ip_address>,<port>,<listening_socket>,<local_
ip_address>,<listening_port>+UUSORF: <listening_socket>,<length>

URC
(TCP)
URC
(UDP)

+UUSORF: 0,1024+USOLI: (0-6),(1-65535)
OK+UUSOLI: 3,"151.63.16.7",1403,0,"82.89.67.164",200+UUSORF: 1,967

26.14.3 Defined values
Parameter<socket>Type
Number<port>

Number<ip_address>

String<listening_socket>

Number<local_ip_address>

String<listening_port>

Number<length>NumberDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Port of service, range 1-65535. Port numbers below 1024 are not recommended since
they are usually reserved
Remote host IP address (only in URC +UUSOLI). For IP address format reference see
the IP addressing.
Socket identifier specified within the AT+USOLI command, indicates on which
listening socket the connection has been accepted (only in +UUSOLI URC)
TE IP address (only in +UUSOLI URC). For IP address format reference see the IP
addressing.
Listening port that has accepted the connection. This port is specified within the AT+USOLI command (only in +UUSOLI URC)
Data length received on the UDP listening socket (only in +UUSORF unsolicitedindication). In order to know the sender IP address and port, use the AT+USORF
command.

26.14.4 Notes•

In case of notification via the URC +UUSOLI <port> is intended as the remote port.

TOBY-L2 / MPCI-L2• If the +UPSD command sets the PSD profile protocol type to IPv6, an IPv6 address shall be reported in
the remote host and TE IP address.
SARA-G3 / LEON-G1• The test command is not supported.

26.15 Firewall control +UFRW+UFRW
Modules
Attributes

LEON-G1
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

26.15.1 Description
Enables/disables internal firewall and controls filtering settings (i.e. define IP white list). When enabled, IPconnections are accepted only if the IP address belongs to the defined IP white list.
The firewall applies for incoming connections only (i.e. listening sockets set by means of +USOLI
command).

UBX-13002752 - R67

26 Internet protocol transport layer

Page 671 of 1001

u-blox cellular modules - AT commands manual

26.15.2 Syntax
Type
Set

Syntax
AT+UFRW=<action>[,<white_ip_
addr_mask>]

Response
OK

Read

AT+UFRW?

+UFRW: <firewall_status>[,<white_
ip_addr_mask1>[,<white_ip_addr_
mask2>[,...]]]

Test

AT+UFRW=?

ExampleAT+UFRW=0
OK

OK+UFRW: (list of supported<action>s)+UFRW: (0-4)
OKOK

26.15.3 Defined values
Parameter<action>Type
Number<white_ip_addr_mask>String<firewall_status>

NumberDescription•

0: disable internal firewall. The parameter <white_ip_addr_mask> is not allowed inthis case: if present error message will be returned• 1: enable internal firewall. The parameter <white_ip_addr_mask> is not allowed inthis case: if present error message will be returned• 2: add specified IP address mask to firewall white list. The parameter <white_ip_
addr_mask> is mandatory. The maximum size of firewall white list is 10 IP addressmasks: up to 10 different IP address masks can be added to firewall white list.
• 3: remove specified IP address mask from firewall white list. The parameter <white_
ip_addr_mask> is mandatory• 4: clear firewall white list. The parameter <white_ip_addr_mask> is not allowed inthis case: if present error message will be returned
white IP address mask to be applied to remote end IP address to decide if toaccept or not the remote connection. The IP address mask is made up of 4 bytes of
information expressed as four numbers in range 0-255 separated by periods (e.g.
"xxx.yyy.zzz.www"). An incoming connection attempt from the remote end IP address<incoming_ip_addr> is accepted if matching the following criterium for at least one of
the IP address masks in the firewall white list: <incoming_ip_addr> & <white_ip_addr_
mask> == <incoming_ip_addr>••

0: disabled
1: enabled

26.16 HEX mode configuration +UDCONF=1+UDCONF=1
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.16.1 Description
Enables/disables the HEX mode for +USOWR, +USOST, +USORD and +USORF AT commands.

26.16.2 Syntax
Type
Set

SyntaxAT+UDCONF=1,<hex_mode_
disable>Response
OK

ExampleAT+UDCONF=1,0

Read

AT+UDCONF=1+UDCONF: 1,<hex_mode_disable>

OK
AT+UDCONF=1

OK+UDCONF: 1,1

UBX-13002752 - R67

26 Internet protocol transport layer

Page 672 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

ExampleOK

26.16.3 Defined values
ParameterType<hex_mode_disable> Number

Description
Enables/disables the HEX mode for +USOWR, +USOST, +USORD and +USORF AT
commands. Allowed values:• 0 (factory-programmed value): HEX mode disabled• 1: HEX mode enabled

26.17 Set socket in Direct Link mode +USODL+USODL
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
<1s
+CME Error

26.17.1 Description
Establishes a transparent end to end communication with an already connected TCP or UDP socket via theserial interface. The data can be sent to the socket and can be received via the serial interface: the HW flow
control usage is strongly recommended to avoid data loss.
The transparent TCP/UDP connection mode can be exited via the +++ sequence, entered after at least 2s of suspension of transmission to the port. The socket will remain connected and communication can bere-established any time.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The +UDCONF=5, +UDCONF=6, +UDCONF=7, +UDCONF=8 commands allow the configuration of UDP
and TCP direct link triggers.
When using Direct Link with UDP sockets, if no network signal is available, outgoing UDP packet may be
lost.

26.17.2 Syntax
Type
Set

SyntaxAT+USODL=<socket>

Response
CONNECT

Test

AT+USODL=?

+USODL: (list of supported<socket>s)

ExampleAT+USODL=0
CONNECT+USODL: (0-6)
OKOK

26.17.3 Defined values
Parameter<socket>Type
NumberDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15

26.17.4 Notes
LARA-R211• On the AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02), the command is not supported.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 673 of 1001

u-blox cellular modules - AT commands manual

SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• On the AUX UART interface, the command is not supported.
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S• The +UDCONF=2 and +UDCONF=3 commands allow the UDP direct link configuration.
LISA-U1• During a 3G connection on the UART interface, the data rate must be at least 115200 b/s.
• The +UDCONF=2 and +UDCONF=3 commands allow UDP direct link configuration.
SARA-G450-01C• On the AUX UART interface, the command is not supported.
SARA-G3• The test command is not supported.
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• On the AUX UART interface, the command is not supported.
LEON-G1• The UDP Direct Link is not supported.
• The test command is not supported.

26.17.5 Enhanced Direct Link
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S / LISA-U1 / LEON-G1
Not supported.
The enhanced DL functionality allows the user set up to three kinds of trigger for data transmission:• Timer Trigger• Data Length Trigger• Character Trigger
The triggers can be applied independently to each socket. A socket may be set with more than one trigger.
The trigger must be set after the socket creation and before switching to direct link mode.
By default Timer Trigger and Data Length Trigger are enabled for UDP sockets.
By default no triggers are enabled for TCP sockets.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
See the +UDCONF=5, +UDCONF=6, +UDCONF=7, +UDCONF=8 commands description for thetransmission triggers configuration.
26.17.5.1 Timer Trigger (TT)The user can configure a timeout for sending the data. The timer starts every time a character is read from theserial interface. When the timer expires, buffered data is sent.
The timer range is between 100 and 120000 ms.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The special value 0 (zero) means that the timer is disabled. By default the timer trigger is disabled for TCP
sockets and enabled with a value of 500 ms for UDP sockets.
The +UDCONF=5 command can configure the timer trigger.
26.17.5.2 Data Length Trigger (DLT)The user can configure a maximum buffered data length to reach before sending the data. When this length
is reached the data is sent.
The minimum data length is 3, the maximum data length is 2048 bytes for TCP and 1472 bytes for UDP.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
If the data length is set to 0 (zero) the trigger is disabled (every data chunk received from the serial port
is immediately sent to the network). By default the data length trigger is disabled for TCP sockets andset to 1024 for UDP sockets.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 674 of 1001

u-blox cellular modules - AT commands manual

The +UDCONF=6 command can configure the data length trigger.
26.17.5.3 Character Trigger (CT)The user can configure a character that will trigger the data transmission. When the character is detected thedata (including the trigger character) is sent.
If the specified character is -1, the character trigger is disabled.
By default it is disabled for both TCP and UDP sockets.
The +UDCONF=7 command can configure the character trigger.
26.17.5.4 Combined Triggers
The user can enable multiple triggers together. The triggers work with an OR logic. This means that the first
trigger reached fires the data transmission.
26.17.5.5 About serial data chunks
A data chunk is the amount of data that SIO recognizes as a single data transmission.
If the baud rate is lower than 115200 b/s the time to receive 255 characters is always calculated withtimings for 115200 b/s.
SARA-G4 / SARA-G340 / SARA-G350 / LEON-G1• A data transmission starts when the first byte is received and it finishes when no data is received in thetime required for the reception of 255 bytes at the current serial port speed.
26.17.5.6 Data from the network
The data received from the network is immediately forwarded to the serial interface.
26.17.5.7 Congestion timer
The congestion timer represents the time after which, in case of network congestion, the module exits fromdirect link.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 - The timer range is
between 1000 and 720000 ms, the special value 0 (zero) means that the timer is disabled. By default thecongestion timer is set to 60000 (60 s) for both TCP and UDP sockets. The +UDCONF=8 command canconfigure the congestion timer.

26.18 UDP Direct Link Packet Size configuration +UDCONF=2+UDCONF=2
Modules
Attributes

LISA-U200-00S LISA-U200-01S LISA-U230 LISA-U260-01S LISA-U270-01S LISA-U1
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

26.18.1 Description
Set the packet size for the UDP direct link packet.

26.18.2 Syntax
Type
Set

SyntaxAT+UDCONF=2,<socket_id>,<packet_size>

Read

AT+UDCONF=2,<socket_id>

Response
OK

ExampleAT+UDCONF=2,1,1024

OK+UDCONF: 2,<socket_id>,<packet_ AT+UDCONF=2,1
size>+UDCONF: 2,1,1024
OKOK

26.18.3 Defined values
Parameter<socket_id>

UBX-13002752 - R67

Type
NumberDescription
Socket identifier; used when changing the UDP Direct Link settings:

26 Internet protocol transport layer

Page 675 of 1001

u-blox cellular modules - AT commands manual

ParameterType<packet_size>

NumberDescription• LISA-U2 / LISA-U1 - The range goes from 0 to 6.
Packet size (in bytes) for UDP direct link; valid range is 100-1472; the factoryprogrammed value is 1024 bytes

26.19 UDP Direct Link Sending timer configuration+UDCONF=3+UDCONF=3
Modules
Attributes

LISA-U200-00S LISA-U200-01S LISA-U230 LISA-U260-01S LISA-U270-01S LISA-U1
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
-

Error reference+CME Error

26.19.1 Description
Configures the UDP direct link set sending timer.

26.19.2 Syntax
Type
Set

SyntaxAT+UDCONF=3,<socket_id>,<sending_timer_timeout>

Read

AT+UDCONF=3,<socket_id>

Response
OK

ExampleAT+UDCONF=3,1,1000

OK+UDCONF: 3,<socket_id>,<sending_ AT+UDCONF=3,1
timer_timeout>+UDCONF: 3,1,1000
OKOK

26.19.3 Defined values
Parameter<socket_id>

Type
Number<sending_timer_
timeout>

NumberDescription
Socket identifier; used when changing the UDP Direct Link settings:• LISA-U2 / LISA-U1 - The range goes from 0 to 6.
Sending timer (in milliseconds) for UDP direct link; valid range is 100-120000; thedefault value is 1000 ms

26.20 Timer Trigger configuration for Direct Link +UDCONF=5+UDCONF=5
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S
SARA-G4 SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.20.1 Description
Sets the timer trigger of the interested socket identifier for the data transmission enhanced Direct Link.

26.20.2 Syntax
Type
Set

SyntaxAT+UDCONF=5,<socket_id>,<timer_trigger>

Response
OK

Read

AT+UDCONF=5,<socket_id>+UDCONF: 5,<socket_id>,<timer_
trigger>

ExampleAT+UDCONF=5,0,500
OK
AT+UDCONF=5,0+UDCONF: 5,0,500

OK

UBX-13002752 - R67

26 Internet protocol transport layer

Page 676 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

ExampleOK

26.20.3 Defined values
Parameter<socket_id>

Type
Number<timer_trigger>

NumberDescription
Socket identifier; used when changing the UDP Direct Link settings:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - The range goes from 0 to 6.
Enhanced Direct Link sending timer trigger (in milliseconds); valid range is 0 (trigger
disabled), 100-120000;• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - the factory-programmed value is 500 ms for UDP, 0 ms for TCP.

26.21 Data Length Trigger configuration for Direct Link
+UDCONF=6+UDCONF=6
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S
SARA-G4 SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.21.1 Description
Sets the data length trigger of the interested socket identifier for the data transmission enhanced Direct Link.

26.21.2 Syntax
Type
Set

SyntaxResponse
AT+UDCONF=6,<socket_id>,<data_ OK
length_trigger>

Read

AT+UDCONF=6,<socket_id>+UDCONF: 6,<socket_id>,<data_
length_trigger>
OK

ExampleAT+UDCONF=6,0,1024
OK
AT+UDCONF=6,0+UDCONF: 6,0,1024
OK

26.21.3 Defined values
Parameter<socket_id>

Type
Number<data_length_
trigger>NumberUBX-13002752 - R67

Description
Socket identifier; used when changing the UDP Direct Link settings:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - The range goes from 0 to 6.
Enhanced Direct Link data length trigger in bytes, valid range is 0, 3-1472 for UDP and
0, 3-2048 for TCP, the factory-programmed value is 1024 for UDP, 0 for TCP, 0 means
trigger disabled.

26 Internet protocol transport layer

Page 677 of 1001

u-blox cellular modules - AT commands manual

26.22 Character trigger configuration for Direct Link
+UDCONF=7+UDCONF=7
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S
SARA-G4 SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.22.1 Description
Sets the character trigger of the interested socket identifier for the data transmission enhanced Direct Link.

26.22.2 Syntax
Type
Set

SyntaxAT+UDCONF=7,<socket_id>,<character_trigger>

Response
OK

Read

AT+UDCONF=7,<socket_id>+UDCONF: 7,<socket_id>,<character_trigger>
OK

ExampleAT+UDCONF=7,0,13
OK
AT+UDCONF=7,0+UDCONF: 7,0,13
OK

26.22.3 Defined values
Parameter<socket_id>

Type
Number<character_trigger> Number

Description
Socket identifier; used when changing the Direct Link settings:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - The range goes from 0 to 6.
Enhanced Direct Link character trigger, the value represents the ASCII code (in base10) of the character to be used as character trigger. The allowed range is -1, 0-255, thefactory-programmed value is -1; -1 means trigger disabled.

26.23 Congestion timer configuration for Direct Link
+UDCONF=8+UDCONF=8
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S
SARA-G4 SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.23.1 Description
Sets the congestion timer of the interested socket identifier for the data transmission enhanced Direct Link.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 678 of 1001

u-blox cellular modules - AT commands manual

26.23.2 Syntax
Type
Set

SyntaxAT+UDCONF=8,<socket_id>,<congestion_timer>

Response
OK

Read

AT+UDCONF=8,<socket_id>+UDCONF: 8,<socket_id>,<congestion_timer>
OK

ExampleAT+UDCONF=8,0,120000
OK
AT+UDCONF=8,0+UDCONF: 8,0,120000
OK

26.23.3 Defined values
Parameter<socket_id>

Type
Number<congestion_timer> Number

Description
Socket identifier; used when changing the Direct Link settings.
Valid range is 0-6
Enhanced Direct Link congestion timer (in milliseconds); valid range is 0, 1000-72000
0; the factory-programmed value is 60000, 0 means trigger disabled

26.24 Direct Link disconnect DSR line handling +UDCONF=10+UDCONF=10
Modules

Attributes

LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

26.24.1 Description
The Direct Link functionality changes the DSR line state according to the &S configuration. If the &S
configuration = 1 (default and factory programmed value), DSR line transitions will occur as follows:• From LOW to HIGH when the module enters into Direct Link mode
• From HIGH to LOW when the module exits from Direct Link mode
The +UDCONF=10 command allows to configure the behaviour of the DSR line when the module exits from
Direct Link. In fact, the transition (from HIGH to LOW) can be configured to occur prior to or after the outputof the "<CR><LF>DISCONNECT<CR><LF>" string.
This command has no effect when the &S configuration = 0.

26.24.2 Syntax
Type
Set

SyntaxAT+UDCONF=10,<dl_dsr_line_
behaviour>

Response
OK

Read

AT+UDCONF=10+UDCONF: 10,<dl_dsr_line_
behaviour>OK

ExampleAT+UDCONF=10,1
OK
AT+UDCONF=10+UDCONF: 10,1
OK

26.24.3 Defined values
Parameter<dl_dsr_line_
behaviour>

UBX-13002752 - R67

Type
NumberDescription
Behaviour of the DSR transition when the module exits from Direct Link. Allowed
values:• 0 (default value): DSR line transition (HIGH to LOW) is performed after the outputof the "<CR><LF>DISCONNECT<CR><LF>" string• 1: DSR line transition (HIGH to LOW) is performed before (~20 ms) the output of the"<CR><LF>DISCONNECT<CR><LF>" string

26 Internet protocol transport layer

Page 679 of 1001

u-blox cellular modules - AT commands manual

26.25 Socket control +USOCTL+USOCTL
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

Attributes

26.25.1 Description
Allows interaction with the low level socket layer.

26.25.2 Syntax
Type
Set

SyntaxResponse
AT+USOCTL=<socket>,<param_id> +USOCTL: <socket>,<param_id>,<param_val>[,<param_val2>]
OK

Test

AT+USOCTL=?

+USOCTL: (list of supported<socket>s),(list of supported<param_id>s)

ExampleAT+USOCTL=0,2+USOCTL: 0,2,38
OK+USOCTL: (0-6),(0-4,10-11)
OKOK

26.25.3 Defined values
Parameter<socket>Type
Number<param_id>

Number<param_val>

Number /StringDescription
Socket identifier.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G340 / SARA-G350 - The range goes from 0 to 6.
• LEON-G1 - The range goes from 0 to 15
Control request identifier. Possible values are:
• 0: query for socket type
• 1: query for last socket error• 2: get the total amount of bytes sent from the socket• 3: get the total amount of bytes received by the socket• 4: query for remote peer IP address and port
• 10: query for TCP socket status (only TCP sockets)• 11: query for TCP outgoing unacknowledged data (only TCP sockets)• 5-9, 12-99: RFU
This value may assume different means depending on the <param_id> parameter.
If <param_id>=0, <param_val> can assume these values:• 6 TCP socket• 17: UDP socket
If <param_id>=1, <param_val> can assume these values:• N: last socket error
If <param_id>=2, <param_val> can assume these values:• N: the total amount (in bytes) of sent (acknowledged + unacknowledged) data
If <param_id>=3, <param_val> can assume these values:• N: the total amount (in bytes) of received (read) data
If <param_id>=4, <param_val> can assume these values:• A string representing the remote peer IP address expressed in dotted decimal form
If <param_id>=10, <param_val> can assume these values:• 0: the socket is in INACTIVE status (it corresponds to CLOSED status defined in
RFC793 "TCP Protocol Specification" [90])UBX-13002752 - R67

26 Internet protocol transport layer

Page 680 of 1001

u-blox cellular modules - AT commands manual

ParameterType<param_val2>

NumberDescription• 1: the socket is in LISTEN status• 2: the socket is in SYN_SENT status• 3: the socket is in SYN_RCVD status• 4: the socket is in ESTABILISHED status• 5: the socket is in FIN_WAIT_1 status• 6: the socket is in FIN_WAIT_2 status• 7: the sokcet is in CLOSE_WAIT status• 8: the socket is in CLOSING status• 9: the socket is in LAST_ACK status• 10: the socket is in TIME_WAIT status
If <param_id>=11, <param_val> can assume these values:• N: the total amount of outgoing unacknowledged data
This value is present only when <param_id> is 4. It represents the remote peer IP port.
For IP address format reference see the IP addressing.

26.25.4 Notes
TOBY-L2 / MPCI-L2• If the +UPSD command sets the PSD profile protocol type to IPv6, an IPv6 address shall be reported in
the remote peer IP address.
SARA-G3 / LEON-G1• The test command is not supported.

26.26 IP Change Notification +UIPCHGN+UIPCHGN
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-01S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SARA-G4 SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

26.26.1 Description
Enable, disables or forces the IP change notification (CN) functionality. This command only works for internal
PDP context activation.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
See +UPSD, +UPSDA and +UPSND AT commands for establishing a PSD connection.
SARA-G3
See +UCSD, +UCSDA and +UCSND AT commands for establishing a CSD connection.
The IP CN notifies a remote server about changes in the module IP address.
The following information is delivered to the destination server:• Current IP address of the module• IMEI of the module (optional)• IMSI of the inserted SIM card (optional)• Username (optional)• MD5 hash of user password (hex format) (optional)• Custom information (up to 128 bytes)
The notification is sent via a HTTP GET request.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 681 of 1001

u-blox cellular modules - AT commands manual

The GET request format is the following:
GET /<path>?myip=<ip>&imei=<imei>&imsi=<imsi>&user=<username>&pass=<md5paswd>&cust=<cust_info> HTTP/1.0{CRLF}
Host: <domain_name>{CRLF}
User-Agent: u-blox IP Change Notification Agent 1.0{CRLF}{CRLF}<ip>, <imei> (if enabled) and <imsi> (if enabled) fields inside the HTTP request are automatically inserted by
the module, <domain_name>, <path>, <username>, <password> and <cust_info> fields must be provided by
the application through the +UIPCHGN AT command.
{CRLF} is a placeholder for hexadecimal character 0x0D (CR) and 0x0A (LF).
The HTTP response from the server is parsed to recognize the HTTP response code and the text between the<ipchgn_r> and the </ipchgn_r> tags inside the response body. This text is not mandatory and can be freely
customized by the customer (up to 64 printable characters).
A real world example follows:
Request (from the module)
GET/modemipnotify.php?myip=123.56.214.2&imei=992237050009739&imsi=992105301545971&user=test_user&pass=
16ec1ebb01fe02ded9b7d5447d3dfc65&cust=Product%3A+Tracker+v.1.0 HTTP/1.0{CRLF}
Host: somedomain.com {CRLF}
User-Agent: u-blox IP Change Notification Agent 1.0{CRLF}{CRLF}

Where
Field
server
path
myip
imei
imsi
user
pass

Content
somedomain.com
modemipnotify.php
123.56.214.2
992237050009739
992105301545971
test_user
16ec1ebb01fe02ded9b7d5447d3dfc65

cust_info

Product%3A+Tracker+v.1.0

Comment
Specified via +UIPCHGN AT command
Specified via +UIPCHGN AT command

Specified via +UIPCHGN AT command
MD5 hash of "test_password"Specified
via +UIPCHGN AT command
URL encoding of the string "Product:
Tracker v.1.0". Specified via +UIPCHGN
AT command

Response (from the server)
HTTP/1.0 200 OK {CRLF}
Content-Type: text/html {CRLF}
Content-Length: 31 {CRLF}
Connection: close {CRLF}{CRLF}<ipchgn_r>IP_UPDATED</ipchgn_r>

UBX-13002752 - R67

26 Internet protocol transport layer

Page 682 of 1001

u-blox cellular modules - AT commands manual

Another real world example (without custom information, username and password):
GET/modemipnotify.php?myip=123.56.214.2&imei=992237050009739&imsi=992105301545971&user=&pass=&cust=
HTTP/1.0{CRLF}
Host: somedomain.com {CRLF}
User-Agent: u-blox IP Change Notification Agent 1.0{CRLF}{CRLF}

Where:
Field
server
path
myip
imei
imsi
user
pass
cust_info

Content
somedomain.com
modemipnotify.php
123.56.214.2
992237050009739
992105301545971

Comment(empty)(empty)(empty)Response (from the server)
HTTP/1.0 200 OK {CRLF}
Content-Type: text/html {CRLF}
Content-Length: 31 {CRLF}
Connection: close {CRLF}{CRLF}<ipchgn_r>IP_UPDATED</ipchgn_r>

Password hashing and URL encoding are performed by the module, so parameters < password> and<cust_info> must be inserted in plain text in the +UIPCHGN command (See command parameters below).
The command configuration is stored in the NVM; if enabled, the command automatically works after a reboot
and the +UUIPCHGN: 0 URC is sent to all terminals in this case.
If the IP CN feature is enabled, the notification is performed at each PDP context activation. If the client isenabled when a PDP connection is already active, it starts to update IP address on the next PDP context
activation.
The custom information field (< cust_info >) is URL encoded into the HTTP request, this means that the
final custom information inside the HTTP GET request may be longer than 128 bytes.
The IP CN feature only works for PDP connections configured and enabled by +UPSD and +UPSDA
command.
The username and password are not compulsory, but it is encouraged to use them for security reasons.

26.26.2 Syntax
Type
Set

SyntaxResponse
AT+UIPCHGN=<action>[,<server>, OK<port>,<path>,<send_imei>,<send_
imsi>,<username>,<password>,<cust_info>]

ExampleTo enable the IP CN feature:
AT+UIPCHGN=1,"somedomain.com",
80,"modemipnotify.php",1,1,"test_user","test_password","Product:
Tracker v.1.0"
OK
To force another IP CN to theremote server (CN must be
previously enabled):

UBX-13002752 - R67

26 Internet protocol transport layer

Page 683 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

ExampleAT+UIPCHGN=2
OK
To disable the IP CN feature:
AT+UIPCHGN=0

Read

AT+UIPCHGN?

Test

AT+UIPCHGN=?

OK+UIPCHGN: <status>[,<server>,+UIPCHGN: 1,"somedomain.com",<port>,<path>,<send_imei>,<send_ 80,"/modemipnotify.php",1,1,"test_imsi>,<username>,<password>,user","test_password","Product:<cust_info>]
Tracker v.1.0"
OK+UIPCHGN: (list of supported<action>s),<server>,(list of
supported <port>s),<path>,(listof supported <send_imei>s),(list of supported <send_imsi>s),<username>,<password>,<cust_info>)OK+UUIPCHGN: <code>[,<reply_str>]

URC

OK+UIPCHGN: (0 2),"server",(1 65535),"path",(0 1),(0 1),"username","password","cust_info"
OK+UUIPCHGN: 200,"IP_UPDATED"

26.26.3 Defined values
Parameter<action>Type
Number<server>StringDescription
Disable / Enable / Force the Update of IP CN feature• 0 (factory-programmed value): disable the feature• 1: enable the feature• 2: force IP notification update
Note: < action > = 2 could be used when the +UUIPCHGN URC returns a code different
from 200.
Indicates the remote host to which the HTTP GET request must be sent to notify the
IP change event.
It can be either a domain name (e.g. "somedomain.com") or an IP address in numericformat (e.g. "173.194.35.145"), always between double quotes.
Maximum length: 64 characters<port>

NumberMandatory parameter with < action>=1, ignored with < action>=0 or < action>=2
Indicates the server port to which the HTTP GET request must be sent.
Valid range: from 1 to 65535<path>

StringMandatory parameter with < action> =1, ignored with < action> =0 or < action> =2
Indicates the server path to be used inside the HTTP GET request. The insertion of
the starting "/" is not mandatory (the software automatically adds it if omitted). The
string must be enclosed between double quotes.
Maximum length: 64 characters<username>

StringMandatory parameter with < action> =1, ignored with < action> =0 or < action> =2
Indicates the username to be sent inside the HTTP request. The string must be
enclosed between double quotes.
Max length: 64 characters
Mandatory parameter with < action> =1, ignored with < action> =0 or < action> =2<send_imei>

Number<send_imsi>

NumberUBX-13002752 - R67

If no username is required, this parameter must be inserted as empty string ("")
Indicates if the notification must send the modem IMEI inside the notification HTTP
GET request• 0: do not send IMEI
• 1: send IMEI
Mandatory parameter with < action> =1, ignored with < action> =0 or < action> =2
Indicates if the notification must send the modem IMSI inside the notification HTTP
GET request

26 Internet protocol transport layer

Page 684 of 1001

u-blox cellular modules - AT commands manual

ParameterType<password>

StringDescription
Valid range: 0-1• 0: do not send IMSI
• 1: send IMSI
Mandatory parameter with < action> =1, ignored with < action> =0 or < action> =2
Indicates the password whose MD5 hash is to be sent inside the HTTP request. The
string must be enclosed between double quotes.
Maximum length: 32 characters
Mandatory parameter with <action>=1, ignored with <action>=0 or <action>=2<cust_info>

StringIf no password is required, this parameter must be inserted as empty string ("")
Indicates the custom information to send inside the HTTP GET request. The string
must be enclosed between double quotes.
Maximum length: 128 characters
Mandatory parameter with <action>=1, ignored with <action>=0 or <action>=2<status>Number<code>

Number

If no custom information is required, this parameter must be inserted as empty
string ("")
This value indicates the status of the IP CN feature• 0: disabled• 1: enabledThis is the code returned by the +UUIPCHGN URC. Values lower than 100 should beinterpreted as internal error, see UUIPGHGN Error.
<code> values greater than 100 must be interpreted as HTTP server response code.
If error is not present the code returned by the +UUIPCHGN should be 200.

<reply_str>

String

The +UUIPCHGN: 0 URC is sent to all terminals at boot if the IP CN feature is enabledfrom a previous working session.
This is the text inserted between the <ipchgn_r> and </ipchgn_r> tags into the
response body from the server. The string is enclosed between double quotes.
The maximum length of this string is 64 bytes; if the server sends a longer string, it
will be truncated.
The parameter is only provided when the information is present in the HTTP response
from the remote server and not if an internal error occurred.

26.27 Socket Always On +USOAO+USOAO
Modules

Attributes

SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SARA-G4 SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
- (except URC)
+CME Error

26.27.1 Description
Allows the configuration of the Socket Always On feature.
The Socket Always On (SAO) causes the module to try establishing an automatic Direct Link (DL) IP connection(or to start listening on an IP port, and in case establish a DL connection) over the UART interface as soon as
the module is powered on, so that "dumb" terminals (equipments without the logic to send AT commands andparse the responses) can directly use an IP connection.
The Direct Link connection used by SAO cannot be established over the USB or SPI physical interfaces but over
the UART physical interface only.
SAO may work in "client" and "server" modes:• Client mode: the module establishes a Direct Link IP connection with a defined remote server• Server mode: the module waits for an incoming connection request on a defined IP port; when an acceptableremote client is recognized, the Direct Link is established

UBX-13002752 - R67

26 Internet protocol transport layer

Page 685 of 1001

u-blox cellular modules - AT commands manual

For client mode, the user must specify these parameters:• Internal PDP profile to be used for GPRS connection• Destination host IP number or hostname• Destination host port
For server mode, the user must specify these parameters:• Internal PDP profile to be used for GPRS connection• Listening port
• White list of remote hosts (optional)
If the feature is enabled, it starts working at the next module power on.
SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
When using SAO in server mode and the network dynamically assigns an IP address (which is most often
the case), then it is advisable to enable also the IP Change Notification feature to inform a remote server
about the assigned IP address. See the +UIPCHGN command description.
When using SAO in server mode, the network dynamically assigns an IP address and the remote client
uses an IP hostname rather than a numerical IP address to connect to the module, then it is advisable toenable the dynamic DNS feature. See the +UDYNDNS command description.
The Direct Link connection used by SAO is affected by the triggers (as specified in Enhanced Direct Link).
If they are not explicitly modified, the default triggers will apply.
26.27.1.1 Usage example
A usage example for client mode configuration follows:
AT command
PSD connection settings
AT+UPSD=0,1,"your.apn"

Comment
Configures the APN for internal PDP profile 0; "your.apn" isan example
Stores the parameters of PDP profile 0 to NVM

AT+UPSDA=0,1
Socket Always On configuration
AT+USOAO=1,0
AT+USOAO=2,0
AT+USOAO=3,"somehost.somedomain.com"
AT+USOAO=4,8084
AT+USOAO=0,1
AT+CPWROFF+UUSOAOC: "122.26.56.55",8084

Sets PDP profile 0 as default connection to be activatedafter module start-up
Sets client mode
Sets the remote host for the TCP connection. The value canalso be an IP address.
Sets the remote port for the TCP connection
Enables the Socket Always On functionality.
Shuts down the module. On the next boot the functionality is
active.
After modem start-up (wait around 15 s)
This is a notification of the connection establishment to
the remote host. The IP address shown is the IP address
got after the DNS resolution of the hostname. The IP shown
here is for example purpose only. The module is connectedin direct link mode (the data sent to the UART port isforwarded to the network and vice-versa). If the connection
drops, it is automatically re establishedA usage example for server mode configuration follows:
AT command
PSD connection settings
AT+UPSD=0,1,"your.apn"
AT+UPSDA=0,1
Socket Always On configuration
AT+USOAO=1,0
AT+USOAO=2,1
AT+USOAO=4,2000

UBX-13002752 - R67

Comment
Configures the APN for internal PDP profile 0; "your.apn" isan example
Stores the parameters of PDP profile 0 to NVM
Sets PDP profile 0 as default connection to be activatedafter module start up
Sets server mode
Sets the listening port

26 Internet protocol transport layer

Page 686 of 1001

u-blox cellular modules - AT commands manual

AT command
AT+USOAO=20,"143.22.33.0"
AT+USOAO=21,"143.22.33.1"
AT+USOAO=0,1

AT+UIPCHGN=1,"somedomain.com",80,"modemipnotify.php",1,1,"test_user","test_password"
AT+CPWROFF+UUIPCHGN: 200,"msg"+UUSOAOL: "151.22.34.66",2000+UUSOAOC: "143.22.33.1",5996

Comment
Sets the first host in white list (optional, up to 10 host can be
added)
Sets the second host in white list (optional, up to 10 host canbe added)
Enables the Socket Always On functionality. If any of theprevious settings is not performed the command returns
error.
Configures the IP Change notification feature (optional
but recommended for server mode). Refer to +UIPCHGN
command description for details
Shuts down the module. On the next boot the functionality is
active.
After module start-up (wait around 15 s)
IP Change Notification result (it is not be prompted if IPchange notification is disabled)
Notifies the Socket Always On is enabled in server mode andlistening on IP 151.22.34.66 and port 2000
A new connection is accepted
Notifies a new connection has been accepted from IP
143.22.33.01 and port 5996. Now it is possible to exchange
data with the remote host. The data sent to the UART port
is forwarded to the network and vice-versa.
If the remote host disconnects, the modem keeps in DL
mode waiting for new incoming connections (which are notnotified)

The module never exits from direct link mode; if the remote client disconnects or the network is no longer
available, the connection will be re-established automatically and transparently.
In order for SAO to work, the following conditions must be true:• the SIM PIN must be disabled, or the right PIN must be provided via the +USOAO=10 sub-command• the UART must be correctly configured for speed (see the +IPR) and flow control (see the +IFC)• the PSD connection parameters must be configured with the +UPSD command and stored in NVM• the automatic or manual network registration must be enabled (see +COPS command description).
If any of the SAO settings are wrong (e.g. setting the server mode when using UDP protocol), the SAO canbe enabled but will not start.
When connected in server mode, if a new connection from an acceptable client address is received, thecurrent connection is silently dropped and the new one is accepted.
When the module boots with SAO enabled, the PSD and TCP/IP commands cannot be reliably used (theirfunctionalities are being used by the SAO). The only safe option is to disable SAO and reboot (with AT+USOAO=0,0 and AT+CPWROFF).
When the module boots with SAO enabled, the MUX protocol (see +CMUX command description) mustnot be enabled on UART interface.

26.27.2 Syntax
Type
SyntaxSocket Always On generic syntax
Set
AT+USOAO=<op_code>,<param1>

Response

ExampleOK

AT+USOAO=0,1

Read+USOAO: <op_code>,<param1>

OK+USOAO: 0,1

AT+USOAO=<op_code>

OK

OK

Enable/disable Socket Always On
Set
AT+USOAO=0,<enable>

OK

AT+USOAO=0,1

Read+USOAO: 0,<enable>OK+USOAO: 0,0OK

OK

AT+USOAO=0

UBX-13002752 - R67

26 Internet protocol transport layer

Page 687 of 1001

u-blox cellular modules - AT commands manualType
SyntaxPSD connection setting
Set
AT+USOAO=1,<profile_id>

Response

ExampleOK

AT+USOAO=1,5

Read+USOAO: 1,<profile_id>

OK+USOAO: 1,6

AT+USOAO=1

OK

OK

Client or server mode configuration
Set
AT+USOAO=2,<server_mode>

OK

AT+USOAO=2,0

Read+USOAO: 2,<server_mode>OK+USOAO: 2,0

AT+USOAO=2

OK

OK

Remote host (for client mode) configuration
Set
AT+USOAO=3,<remote_host>OK

AT+USOAO=3,"www.remotehost.it"

Read+USOAO: 3,<remote_host>OK+USOAO: 3,"www.remotehost.it"

AT+USOAO=3

OK

OK

IP port number configuration
Set
AT+USOAO=4,<ip_port>

OK

AT+USOAO=4,8088

Read+USOAO: 4,<ip_port>

OK+USOAO: 4,8088

AT+USOAO=4

OK

OK

IP protocol configuration
Set
AT+USOAO=5,<protocol>

OK

AT+USOAO=5,17

Read+USOAO: 4,<protocol>

OK+USOAO: 5,17

AT+USOAO=5

OKOKSIM PIN configuration
Set
AT+USOAO=10,<pin>

OK

AT+USOAO=10,"123456"

Read+USOAO: 10,********OK+USOAO: 10,********

AT+USOAO=10

OK
Set the i-th element of the white list of IP addresses (i=0..9)
Set
AT+USOAO=20+i,<client_address> OK
Read

AT+USOAO=20+i

Test

AT+USOAO=?

URC
URC

(listening URC)
(connection URC)OK
AT+USOAO=22,"123.156.0.2"+USOAO: 20+i,<client_address>

OK+USOAO: 22,"123.156.0.2"

OK

OK+USOAO: (list of supported <op_code>'s)+USOAO: (0-5,10,20-29)

OK
OK+UUSOAOL: <local_ip>,<local_port> +UUSOAOL: "151.22.34.66",2000+UUSOAOC: <remote_ip>,<remote_ +UUSOAOC: "122.26.56.55",8084
port>

26.27.3 Defined values
Parameter<op_code>

UBX-13002752 - R67

Type
NumberDescription
Identifier of the meaning of the next parameter(s). Allowed values/ranges are: 0-5, 10
and 20-29. Meanings:• 0: enable/disable the socket always on feature• 1: configure the default PSD connection• 2: client/server mode
• 3: remote host (for client mode only)• 4: remote host port for client mode or local listening port for server mode
• 5: socket type: UDP (for client mode only) or TCP

26 Internet protocol transport layer

Page 688 of 1001

u-blox cellular modules - AT commands manual

ParameterType<enable>Number<profile_id>

Number<server_mode>

Number<remote_host>

String<ip_port>

NumberDescription• 10: SIM PIN• 20-29: white list items (for server mode only)
Configures the Socket Always On feature at the next power on:• 0 (factory-programmed value): feature disabled• 1: feature enabledThis is the same <profile_id> used in +UPSD command. Range between 0 and 6. The
factory-programmed value is 0.
Defines the client or server module behavior. Allowed values:• 0 (factory-programmed value): client mode
• 1: server mode
The remote server IP address or hostname to connect to while in client mode. Thisvalue is ignored for server configuration. The factory-programmed value is an empty
string ("").
In client mode it represents the remote port to connect to.
In server mode it represents the local port on which the module must wait incoming
connection.

<protocol>

Number<pin>

String

The range 1-65535. The factory-programmed value is 2000.
Protocol type to be used for socket creation. Allowed values:• 6 (factory-programmed value): TCP• 17: UDP (not valid for server mode)
SIM PIN: 4-to-8 characters long string of decimal digits. It is used if the SIM requires
it and only if there are 3 attempts left.
If empty, no PIN is attempted. The factory-programmed value is an empty string (noPIN).

<client_address>

String<local_ip><local_port>

StringNumber<remote_ip><remote_port>

StringNumber<param1>

Number

The PIN cannot be revealed - the read command AT+USOAO=10 only returns a stringof asterisks "********".
An entry in the "white list" of remote clients IP addresses, in quoted numericalformat (e.g. "123.45.67.89"). If the list is non-empty (i.e. it does not contain only null
addresses), only connection requests from the listed addresses is accepted. An
empty IP address ("0.0.0.0") is a null address.
The factory-programmed value is an empty IP address.
Local IP address. Only used in +UUSOAOL URC (when the module is in server mode).
Local IP port. Range between 1 and 65535. Used only in +UUSOAOL URC (when themodule is in server mode).
IP address of the remote host connected to the module. Used in +UUSOAOC URCs.
IP port of the remote host connected to the module. Range between 1 and 65535.
Used in +UUSOAOC URCs
Type and supported content depend on the related <op_code> parameter; see the<op_code> specification.

26.27.4 Notes•••+UUSOAOL and +UUSOAOC URCs are displayed only if the socket always on connection is active.
+UUSOAOL URC is only displayed if socket always on is set in server mode.
Only the UART interface displays +UUSOAOL and +UUSOAOC.

UBX-13002752 - R67

26 Internet protocol transport layer

Page 689 of 1001

u-blox cellular modules - AT commands manual

27 Device and data security
27.1 Data security
27.1.1 Introduction
27.1.1.1 SSL/TLS/DTLS
SSL/TLS/DTLS (where supported) provides a secure connection between two entities using TCP/UDP socket
for communication (i.e. HTTP/FTP server and HTTP/FTP client).
The SSL/TLS/DTLS with digital certificates support provides different connection security aspects:• Server authentication: use of the server certificate verification against a specific trusted certificate or atrusted certificates list;• Client authentication: use of the client certificate and the corresponding private key;
• Data security and integrity: data encryption and Hash Message Authentication Code (HMAC) generation.
The security aspects used in the current connection depend on the SSL/TLS/DTLS configuration and features
supported by the communicating entities.
u-blox cellular modules support all the described aspects of SSL/TLS/DTLS security protocol with these AT
commands:• AT+USECMNG: import, removal, list and information retrieval of certificates or private keys;• AT+USECPRF: configuration of USECMNG (u-blox SECurity MaNaGement) profiles used for an SSL/TLS/
DTLS connection.
The USECMNG provides a default SSL/TLS/DTLS profile which cannot be modified. The default USECMNG
profile provides the following SSL/TLS/DTLS settings:
Setting
Value
Certificates validation level
Level 0
Minimum SSL/TLS/DTLS version Any
Cipher suite
Trusted root certificate internal
name
Expected server host-name
Client certificate internal name
Client private key internal name
Client private key password
Pre-shared key
Server certificate pinning
Server certificate pinning level

Automatic"" (none)

Meaning
The server certificate will not be checked or verified.
The server can use any of the TLS1.0/TLS1.1/TLS1.2/DTLS1.2 versions
for the connection.
The cipher suite will be negotiated in the handshake process.
No certificate will be used for the server authentication.

"" (none)"" (none)"" (none)"" (none)"" (none)"" (none)
Level 0No server host-name is expected.
No client certificate will be used.
No client private key will be used.
No client private key password will be used.
No pre-shared key key password will be used.
No server certificate will be used.
No server certificate will be used.

For the configuration of the settings listed above, see the +USECPRF AT command.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The secure re-negotiation is currently not supported, and if mandated by the server the SSL/TLS/DTLS
connection will fail with a generic SSL/TLS/DTLS handshake alert.

UBX-13002752 - R67

27 Device and data security

Page 690 of 1001

u-blox cellular modules - AT commands manual

27.1.2 SSL/TLS certificates and private keys manager +USECMNG+USECMNG
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201-02S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G4 SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

27.1.2.1 Description
Manages the X.509 certificates and private keys with the following functionalities:• Import of certificates and private keys
• List and information retrieval of imported certificates and private keys
• Removal of certificates and private keys
• MD5 calculation of imported certificate or private key
For more details on X.509 certificates and private keys see RFC 5280 [191].
The number and the format of the certificates and the private keys accepted depend on the module series:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 - certificates andprivate keys both in DER (Distinguished Encoding Rules) and in PEM (Privacy-Enhanced Mail) format
are accepted. If the provided format is PEM, the imported certificate or private key will be automaticallyconverted in DER format for the internal storage. It is also possible to validate certificates and private keys.
Up to 16 certificates or private keys can be imported.
The certificates and private keys are kept in DER format and are not retrievable (i.e. cannot be downloaded
from the module); for data validation purposes an MD5 hash string of the stored certificate or private key(stored in DER format) can be retrieved.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The SSL/(D)TLS connection can be successfully performed only if keys with at least 512-bit size and/or
certificates generated with at least 512-bit key size are used.
Data for certificate or private key import can be provided with a stream of byte similar to +UDWNFILE orfrom a file stored on the FS.
When using the stream of byte import functionality:• If the data transfer is stopped before its completion, a guard timer of 20 s will ensure the terminationof the data transmission. In this case the prompt will switch back in AT command mode and an error
result code will be returned.
• If the module shuts down during the data transfer, all the bytes are discarded.
• If any error occurs during the data transfer, all bytes are discarded.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
Enable the RTS/CTS DTE flow control (see &K command description) before to import a stream of bytes.
All the imported certificates or private keys are listed if the type of the security data is omitted.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The imported certificates and private keys are:•••

NOT PERSISTED (deleted) after the module FW is upgraded using +UFWINSTALL or +UFWUPD AT
commands.
PERSISTED after a factory reset using +UFACTORY AT command.
NOT PERSISTED after the module FW is upgraded using EasyFlash.

TOBY-L2 / MPCI-L2
The imported certificates and private keys are:•PERSISTED after the module FW is upgraded using +UFWINSTALL, +UFWSINSTALL or +UFWUPD
AT commands.

UBX-13002752 - R67

27 Device and data security

Page 691 of 1001

u-blox cellular modules - AT commands manual• PERSISTED after a factory reset using +UFACTORY AT command.
• NOT PERSISTED after the module FW is upgraded using EasyFlash.
For more details on product specific limitations, see Notes.
The USECMNG import command supports only X.509 certificate format.
The X.509 certificate DN (Distinguished Name) is composed of value fields which uniquely define an entity
being authenticated. For security reasons some limitations (related to DN fields) described below areapplied:• The USECMNG import functionality allows the following DN value fields:
o commonName (http://oid-info.com/get/2.5.4.3)
o serialNumber (http://oid-info.com/get/2.5.4.5)
o countryName (http://oid-info.com/get/2.5.4.6)
o localityName (http://oid-info.com/get/2.5.4.7)
o stateOrProvinceName (http://oid-info.com/get/2.5.4.8)
o organizationName (http://oid-info.com/get/2.5.4.10)
o organizationalUnitName (http://oid-info.com/get/2.5.4.11)
o userID (http://oid-info.com/get/0.9.2342.19200300.100.1.1)
o domainComponent (http://oid-info.com/get/0.9.2342.19200300.100.1.25)
o pkcs9_emailAddress (http://oid-info.com/get/1.2.840.113549.1.9.1)
o pkcs9_unstructuredName (http://oid-info.com/get/1.2.840.113549.1.9.2)• The import of an X.509 certificate with DN containing other value fields (not in the above list) will resultin an import error (error result code: USECMNG invalid certificate/key format).
27.1.2.2 Syntax
Type
SyntaxResponse
Generic syntax:
ActionAT+USECMNG=<op_code>,OK[<type>[,<internal_name>[,<param1>[,<param2>]]]]
Import a certificate or private key from serial I/O:
ActionAT+USECMNG=0,<type>,<internal_ >name>,<data_size>[,<password>]
Start transfer of data ...
+USECMNG: 0,<type>,<internal_name>,<md5_string>
OK

Example-AT+USECMNG=0,0,"AddTrustCA",
1327>-----BEGIN CERTIFICATE----(...other certificate data bytes...)+USECMNG: 0,0,"AddTrustCA","77107370ec4db40a0
8a6e36a64a1435b"
OK

Import a certificate or private key from a file stored on FS:
ActionAT+USECMNG=1,<type>,<internal_ +USECMNG: 1,<type>,<internal_name>,<filename>[,<password>]name>,<md5_string>
OK

AT+USECMNG=1,0,"AddTrustCA","addtrust.cert"+USECMNG: 1,0,"AddTrustCA","7710
7370ec4db40a08a6e36a64a1435b"
OK

Remove an imported certificate or private key:
ActionAT+USECMNG=2,<type>,<internal_ OK
name>
List imported certificates or private keys:
Read
AT+USECMNG=3[,<type>]<cert_type>,<internal_name>[,<common_name>,<expiration_date>]...
OK

AT+USECMNG=2,0,"AddTrustCA"
OK
AT+USECMNG=3"CA","AddTrustCA","AddTrust
External CA Root","2020/05/30""CA","GlobalSignCA","GlobalSign","2029/03/18""CC","JohnDoeCC","GlobalSign","20
10/01/01"

UBX-13002752 - R67

27 Device and data security

Page 692 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Example"PK","JohnDoePK"OK

Retrieve the MD5 of an imported certificate or private key:
Read
AT+USECMNG=4,<type>,<internal_ +USECMNG: 4,<type>,<internal_
name>name>,<md5_string>
OK

AT+USECMNG=4,0,"AddTrustCA"+USECMNG: 4,0,"AddTrustCA","77107370ec4db40a0
8a6e36a64a1435b"
OK

Test

AT+USECMNG=?

+USECMNG: (list of supported <op_ +USECMNG: (0-4),(0-2)
code>s),(list of supported <type>s)OKOK

27.1.2.3 Defined values
Parameter<op_code>Type
Number<type>

Number<cert_type>

String<internal_name>

String<data_size>

NumberUBX-13002752 - R67

Description
Type of operation:• 0: import a certificate or a private key (data provided by the stream of byte)• 1: import a certificate or a private key (data provided from a file on FS)• 2: remove an imported certificate or private key• 3: list imported certificates or private keys
• 4: retrieve the MD5 of an imported certificate or private key
Type of the security data:• 0: trusted root CA (certificate authority) certificate• 1: client certificate• 2: client private key• 3: server certificate• 4: signature verification certificate• 5: signature verification public key
Allowed values:• TOBY-L200-03A / TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L280-03A / TOBY-L280-03S / MPCI-L201-02S - 0, 1, 2, 3,
4, 5• TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S /TOBY-L220 / TOBY-L280-02S / MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280- 0, 1, 2• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 - 0, 1, 2
Type of the security data in verbose format:• "CA": trusted root CA (certificate authority) certificate• "CC": client certificate• "PK": client private key• "SC": server certificate• "VC": signature verification certificate• "PU": signature verification public key
Allowed values:• TOBY-L200-03A / TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L280-03A / TOBY-L280-03S / MPCI-L201-02S - "CA", "CC","PK", "SC", "VC", "PU"• TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S /TOBY-L220 / TOBY-L280-02S / MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280- "CA", "CC", "PK"• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 - "CA", "CC", "PK"
Unique identifier of an imported certificate or private key. If an existing name is usedthe data will be overridden.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - The maximum length is 200 characters.
Size in bytes of a certificate or private key being imported.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - The maximum allowed size is 8192 bytes.

27 Device and data security

Page 693 of 1001

u-blox cellular modules - AT commands manual

Parameter<password>

Type
String<filename>

String<md5_string><common_name>

StringString<expiration_date>

String<param1>

Number/StringNumber/String<param2>

Description
Decryption password; applicable only for PKCS8 encrypted client private keys. The
maximum length is 128 characters.
Name of the FS file containing the certificate or private key data to be imported.
• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - The maximum allowed file size is 8192 bytes.
MD5 formatted string.
Certificate subject (issued to) common name; applicable only for trusted root andclient certificates.
Certificate expiration (valid to date); applicable only for trusted root and clientcertificates.
Type and supported content depend on the related <op_code> parameter; see the<op_code> specification.
Type and supported content depend on the related <op_code> parameter; see the<op_code> specification.

27.1.2.4 Notes
TOBY-L201-02S / MPCI-L201-02S• The command is not supported by TOBY-L201-02S-00 and MPCI-L201-02S-00.
TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S /MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280• The USECMNG parameter <password> is not supported.
• The import of the following client private key formats is not supported:o PKCS1 RSA formatted encrypted private keyo PKCS8 unencrypted private keyo PKCS8 encrypted private key• The imported certificates and private keys are:o NOT PERSISTED (deleted) after the module FW is upgraded using +UFWINSTALL,+UFWSINSTALL or +UFWUPD AT commands.
TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S• On TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L210-03A-00, TOBY-L280-03S-00 the parameters:o <type>= 3, 4, 5 are not supported.
o <cert_type>= "SC","VC","PU" are not supported.
• On TOBY-L200-03S-00, TOBY-L210-03A-00, TOBY-L210-03S-00, TOBY-L280-03S-00 the USECMNG
parameter <password> is not supported as well as the import of the following client private key formats:o PKCS1 RSA formatted encrypted private keyo PKCS8 unencrypted private keyo PKCS8 encrypted private key• On TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L210-03A-00, TOBY-L280-03S-00 the imported
certificates and private keys are:o NOT PERSISTED (deleted) after the module FW is upgraded using +UFWINSTALL,+UFWSINSTALL or +UFWUPD AT commands.
LARA-R2 / TOBY-R2• The import of the following client private key formats is not supported:o PKCS1 RSA formatted encrypted private key• When importing non-encrypted PKCS8 or PKCS1 private keys the USECMNG parameter <password> isignored.
SARA-U201-03A / SARA-U201-03B / SARA-U201-03X / SARA-U201-63B / SARA-U260 / SARA-U270-00X /SARA-U270-03A / SARA-U270-03S / SARA-U270-53S / SARA-U270-73S / SARA-U280-03S /LISA-U200-03S / LISA-U200-83S / LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / SARA-G3• The USECMNG parameter <password> is not supported.
• The import of the following client private key formats is not supported:o PKCS1 RSA formatted encrypted private keyo PKCS8 unencrypted private keyo PKCS8 encrypted private key

UBX-13002752 - R67

27 Device and data security

Page 694 of 1001

u-blox cellular modules - AT commands manual

SARA-G4• The USECMNG parameter <password> is not supported.
• The import of the following client private key formats is not supported:o PKCS1 RSA formatted encrypted private keyo PKCS8 encrypted private key

27.1.3 SSL/TLS/DTLS security layer profile manager +USECPRF+USECPRF
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201-02S MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G4 SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

27.1.3.1 Description
Manages security profiles for the configuration of the following SSL/TLS/DTLS connections properties:• Certificate validation level:o Level 0: no certificate validation; the server certificate will not be checked or verified. No additional
certificates are needed.
o Level 1: certificate validation against a specific or a list of imported trusted root certificates.
o Level 2: certificate validation with an additional URL integrity check (the server certificate common
name must match the server hostname).
o Level 3: certificate validation with an additional check on the certificate validity date.
CA certificates should be imported with the +USECMNG AT command• Minimum SSL/TLS/DTLS version to be used:
o Any
o TLS 1.0
o TLS 1.1
o TLS 1.2
o DTLS 1.2• Cipher suite to be configured using the following methods:
o Legacy cipher suite to be used. See Syntax description and Table 85 for the supported cipher suites.
o Additional cipher suite to be used with Internet Assigned Numbers Authority (IANA) enumeration set
command. See Syntax description and Table 85 for the supported cipher suites.
o List of cipher suites to be used is configured with add / remove commands and using IANA enumeration.
See Syntax description and Table 85 for the supported cipher suites.
For the applicability of cipher suite depending on the module series, see Cipher suites applicability.
Cipher suite configuration methods are exclusive and the last configured method is used.

•

•
•
•

The cipher suite configuration read command response is related to the selected cipher suite type, see
Syntax description for more details.
Certificate to be used for server and mutual authentication:o The trusted root certificate. The CA certificate should be imported with the +USECMNG AT command.
o The client certificate that should be imported with the +USECMNG AT command.
o The client private key that should be imported with the +USECMNG AT command.
o The server certificate that should be imported with the +USECMNG AT command.
Expected server hostname, when using certificate validation level 2 or 3.
Password for the client private key, if it is password protected.
Pre-shared key used for connection. Defines a pre-shared key and key-name (PSK), when a TLS_PSK_*
cipher suite is used.

UBX-13002752 - R67

27 Device and data security

Page 695 of 1001

u-blox cellular modules - AT commands manual••

SNI (Server Name Indication). SNI is a feature of SSL/TLS which uses an additional SSL/TLS extension
header to specify the server name to which the client is connecting to. The extension was introduced tosupport the certificate handling used with virtual hosting provided by the various SSL/TLS enabled servers
mostly in cloud based infrastructures. With the SNI a server has the opportunity to present a different
server certificate (or/and whole SSL/TLS configuration) based on the host indicated by the SNI extension.
When SNI is not used the modules might receive a non host specific SSL/TLS configuration (version/cipher
suites/certificate) when used with virtual hosts.
(D)TLS session resumption. The session resumption feature allows to reuse the secure session data inorder to reestablish a SSL/(D)TLS secure session. Since the secure session data are available, the SSL/
(D)TLS handshake is not performed during the session resumption. Once the session resumption featureis enabled, the session resumption type (provided by the server) and the secure session data (negotiatedduring the SSL/(D)TLS handshake) are displayed via +USECPRF URC message. The session resumption
feature configuration and secure session data are not stored in the NVM, hence the session resumption
may be performed until power cycle.
To set all the parameters in security profile, a set command for each <op_code> needs to be issued (e.g.
certificate validation level, minimum SSL/TLS/DTLS version, ...).
To reset (set to factory-programmed value) all the parameters of a specific security profile, issue the AT+USECPRF=<profile_id> command.

27.1.3.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+USECPRF=<profile_id>[,<op_code>[,<param_val1>[,<param_val2>[,<param_val3>]]]]Read
AT+USECPRF=<profile_id>,<op_
code>

URC

Response

ExampleOK

AT+USECPRF=0,0,0
OK+USECPRF: <profile_id>,<op_code>, AT+USECPRF=0,0<param_val1>+USECPRF: 0,0,0
OK
OK+UUSECPRF: <profile_id>,<op_+USECPRF: 0,13,1,0
code>[,<param_val1>[,<param_OKval2>[,<param_val3>]]]
OK

Legacy cipher suite selection
Set
AT+USECPRF=<profile_id>,2,<legacy_cs>

OK

AT+USECPRF=0,2,2OK

Cipher suite selection using IANA enumeration
Set
AT+USECPRF=<profile_id>,2,99,
OK<iana_b1>,<iana_b2>

AT+USECPRF=0,2,99,"C0","2B"

OK+USECPRF: <profile_id>,2,99,<iana_ AT+USECPRF=0,2
b1>,<iana_b2>+USECPRF: 0,2,99,"C0","2B"
OK
OK
Add/remove of IANA cipher suite to the configured cipher suites list
Set
AT+USECPRF=<profile_id>,2,100,
OK
AT+USECPRF=0,2,100,"C0","2A",0<iana_b1>,<iana_b2>,<operation>OK
Add an IANA cipher suite to the configured cipher suites list
Set
AT+USECPRF=<profile_id>,2,100,
OK
AT+USECPRF=0,2,100,"C0","2A",0<iana_b1>,<iana_b2>,0OK
Remove an IANA cipher suite from the configured cipher suites list
Set
AT+USECPRF=<profile_id>,2,100,
OK
AT+USECPRF=0,2,100,"C0","2B",1<iana_b1>,<iana_b2>,1
OK
Read the list of configured cipher suites
Read
AT+USECPRF=<profile_id>,2+USECPRF: <profile_id>,2,100,
AT+USECPRF=0,2<list of configured cipher suites+USECPRF: 0,2,100,"C02A;C02C"
separated by ";">
OK
OK
Read

AT+USECPRF=<profile_id>,2

UBX-13002752 - R67

27 Device and data security

Page 696 of 1001

u-blox cellular modules - AT commands manualType
SyntaxPre-shared key configuration
Set
AT+USECPRF=<profile_id>,8,<preshared_key>[,<string_type>]

Response

ExampleOK

AT+USECPRF=0,8,"0sFpZ0AZqE0
N6Ti9s0qt40ZP5Eqx"
OK

Pre-shared key identity configuration
Set
AT+USECPRF=<profile_id>,9,OK<preshared_key_id>[,<string_type>]

AT+USECPRF=0,9,"0ceEZ0AZqP0
K60i9o04xz0ZP8zyu0Eqx"
OK

Server certificate pinning
Set
AT+USECPRF=<profile_id>,12,OK<server_certificate>,<pinning_level>(D)TLS session resumption generic syntax
Set
AT+USECPRF=<profile_id>,13,OK<tag>,<param_val1>[,<param_val2>]Read
AT+USECPRF=<profile_id>,13,<tag> +USECPRF: <profile_id>,13,<tag>,<param_val1>[,<param_val2>]

AT+USECPRF=0,12,"my_srv_cert",0OK
AT+USECPRF=0,13,0,1
OK
AT+USECPRF=0,13,0+USECPRF: 0,13,0,1

OK

OK+UUSECPRF: <profile_id>,13,<tag>, +USECPRF: 0,13,1,0<param_val1>[,<param_val2>]
OK
OK

URC

(D)TLS session resumption status
Set
AT+USECPRF=<profile_id>,13,0,<sess_status>
Read

AT+USECPRF=<profile_id>,13,0(D)TLS session resumption session type
Set
AT+USECPRF=<profile_id>,13,1,<sess_type>

OK

AT+USECPRF=0,13,0,1

OK+USECPRF: <profile_id>,13,0,<sess_ AT+USECPRF=0,13,0
status>+USECPRF: 0,13,0,1
OK
OK
OK

AT+USECPRF=0,13,1,0

OK+USECPRF: <profile_id>,13,1,<sess_ AT+USECPRF=0,13,1
type>+USECPRF: 0,13,1,0
OK
OK
URC
+UUSECPRF: <profile_id>,13,1,+UUSECPRF: 0,13,1,0<sess_type>(D)TLS session resumption session data having session ID as session resumption type
Set
AT+USECPRF=<profile_id>,13,2,
OK
AT+USECPRF=0,13,2,"VWY5UENs0<session_id_base64>,<master_
Hh3VWR1MjB2WTVMYVZ5TTdE0
secret_base64>
WpMeWZWeHo=","SHVSODByUit0
My9OMEtIT2ZsVVFRcUsyTkdvaz0
nWVFhRzdQZUpndG9IMzN4ZTBo"
ReadAT+USECPRF=<profile_id>,13,1

Read

AT+USECPRF=<profile_id>,13,2+USECPRF: <profile_id>,13,2,<session_id_base64>,<master_
secret_base64>
OK

OK
AT+USECPRF=0,13,2+USECPRF: 0,13,2,"VWY5UENs0
Hh3VWR1MjB2WTVMYVZ5TTdE0
WpMeWZWeHo=","SHVSODByUit0
My9OMEtIT2ZsVVFRcUsyTkdvaz0
nWVFhRzdQZUpndG9IMzN4ZTBo"

OK+UUSECPRF: 0,13,2,"VWY5UENs0
Hh3VWR1MjB2WTVMYVZ5TTdE0
WpMeWZWeHo=","SHVSODByUit0
My9OMEtIT2ZsVVFRcUsyTkdvaz0
nWVFhRzdQZUpndG9IMzN4ZTBo"(D)TLS session resumption session data having encrypted session ID with local encryption as session resumption type
URC

UBX-13002752 - R67+UUSECPRF: <profile_id>,13,2,<session_id_base64>,<master_
secret_base64>

27 Device and data security

Page 697 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+USECPRF=<profile_id>,13,12,<encrypted_session_data>,<enc_session_data_size>

Response
OK

Read

AT+USECPRF=<profile_id>,13,12+USECPRF: <profile_id>,13,12,<encrypted_session_data>,(0-203)
OK

URC

Test

+UUSECPRF: <profile_id>,13,12,<encrypted_session_data>,(0-203)

AT+USECPRF=?

+USECPRF: (list of supported<profile_id>s),(list of supported<op_code>s)

ExampleAT+USECPRF=0,13,12,"AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh/
Ljgstf1cLaEO2D8IMbxHcQlGfhVxC0
in6aGVlSJGBWCAAKJo6Qw5Q+ugXaRZFquG0
O69WeHnPRBkcwY2SN4bwnDbyR+709i0pt2nlaYMSCL77MAA=",156
OK
AT+USECPRF=0,13,12+USECPRF: 0,13,12,"AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh/
Ljgstf1cLaEO2D8IMbxHcQlGfhVxC0
in6aGVlSJGBWCAAKJo6Qw5Q+ugXaRZFquG0
O69WeHnPRBkcwY2SN4bwnDbyR+709i0pt2nlaYMSCL77MAA=",156
OK+UUSECPRF: 0,13,12,"AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh/
Ljgstf1cLaEO2D8IMbxHcQlGfhVxC0
in6aGVlSJGBWCAAKJo6Qw5Q+ugXaRZFquG0
O69WeHnPRBkcwY2SN4bwnDbyR+709i0pt2nlaYMSCL77MAA=",156+USECPRF: (0-4),(0-13)
OKOK

27.1.3.3 Defined values
Parameter<profile_id><op_code>Type
Description
Number USECMNG security profile identifier, in range 0-4; if it is not followed by other parameters the
profile settings will be reset (set to factory-programmed value).
Number • 0: certificate validation level; allowed values for <param_val1> (number):o 0 (factory-programmed value): level 0 - No validation; the server certificate will not bechecked or verified. The server in this case is not authenticated.
o 1: level 1 - Root certificate validation without URL integrity check. The server certificate will
be verified with a specific trusted certificates or with each of the imported trusted root
certificates.
o 2: level 2 - Root certificate validation with URL integrity check. Level 1 validation with anadditional URL integrity check.
o 3: level 3 - Root certificate validation with check of certificate validity date. Level 2
validation with an additional check of certificate validity date.
• 1: SSL/TLS/DTLS version to use; allowed values for <param_val1>(number):o 0 (factory-programmed value): any; server can use any version for the connection.
o 1: TLSv1.0; connection allowed only to TLS/SSL servers which support TLSv1.0
o 2: TLSv1.1; connection allowed only to TLS/SSL servers which support TLSv1.1
o 3: TLSv1.2; connection allowed only to TLS/SSL servers which support TLSv1.2• 2: cipher suite; allowed values for <legacy_cs> (number) legacy cipher suites are listed inTable 85. The factory-programmed value for <legacy_cs> is 0. For <legacy_cs>=0 a list ofdefault cipher suites is proposed at the beginning of handshake process, and a cipher suite
will be negotiated among the cipher suites proposed in the list. For <legacy_cs>=99 the cipher
suite selection is performed with IANA enumeration, <iana_b1> and <iana_b2> are strings
containing the 2 bytes that compose the IANA enumeration, see Table 85. For <legacy_cs>=
100 the list of cipher suites is configured using IANA enumeration, <iana_b1> and <iana_b2>
are strings containing the 2 bytes that compose the IANA enumeration, see Table 85.
The cipher suite configuration read command response is related to the selected cipher
suite type. In the case of <legacy_cs>=99 the configured <byte_1> and <byte_2> are

UBX-13002752 - R67

27 Device and data security

Page 698 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description
reported in the information text response to the read command. In the case of <legacy_cs>=100 a ";" separated list with configured cipher suites is reported in the informationtext response to the read command.
For <legacy_cs>=100, when all added cipher suites are removed the cipher suite is
automatically set to 0 (factory-programmed value).

•

•

•

•

•

•

•

•

•

•

UBX-13002752 - R67

For the applicability of default cipher suite lists depending on the module series, see
Cipher suites applicability.
3: trusted root certificate internal name;o <param_val1> (string) is the internal name identifying a trusted root certificate; themaximum length is 200 characters. The factory-programmed value is an empty string.
4: expected server hostname;o <param_val1> (string) is the hostname of the server, used when certificate validation levelis set to Level 2; the maximum length is 256 characters. The factory-programmed value isan empty string.
5: client certificate internal name;o <param_val1> (string) is the internal name identifying a client certificate to be sent to theserver; the maximum length is 200 characters. The factory-programmed value is an empty
string.
6: client private key internal name;o <param_val1> (string) is the internal name identifying a private key to be used; themaximum length is 200 characters. The factory-programmed value is an empty string.
7: client private key password;o <param_val1> (string) is the password for the client private key if it is password protected;
the maximum length is 128 characters. The factory-programmed value is an empty string.
8: pre-shared key;o <preshared_key> (string) is the pre-shared key used for connection; the factoryprogrammed value is an empty string. The accepted string type and length depends on the<string_type> value.
o <string_type> (number) defines the type and the maximum length of the <preshared_key>
string. Allowed values for <string_type>:- 0 (default value): <preshared_key> is an ASCII string and its maximum length is 64
characters- 1: <preshared_key> is an hexadecimal string and its maximum length is 128 characters9: pre-shared key identity;o <preshared_key_id> (string) is the pre-shared key identity used for connection; the factoryprogrammed value is an empty string. The accepted string type and length depends on the<string_type> value.
o <string_type> (number) defines the type of the <preshared_key_id> string. Allowed values
for <string_type>:- 0 (default value): <preshared_key_id> is an ASCII string and its maximum length is 128
characters- 1: <preshared_key_id> is an hexadecimal string and its maximum length is 256
characters
10: SNI (Server Name Indication);o <param_val1> (string) value for the additional negotiation header SNI (Server Name
Indication) used in SSL/TLS connection negotiation; the maximum length is 128
characters. The factory-programmed value is an empty string.
11: PSK key and PSK key identity generated by RoT (Root of trust); allowed values for <param_val1> (number):o 0 (factory-programmed value): OFF - The PSK and PSK key ID are NOT generated by RoT
o 1: ON - The PSK and PSK key ID are generated by RoT in the process of SSL/TLS connection
negotiation
12: server certificate pinning;o <server_certificate> (string) internal name identifying a certificate configured to be
used for server certificate pinning; the maximum length is 200 characters. The factoryprogrammed value is an empty string.
o <pinning_level> (number) defines the certificate pinning information level. Allowed values
for <pinning_level>- 0: pinning based on information comparison of received and configured certificate
public key- 1: pinning based on binary comparison of received and configured certificate public key

27 Device and data security

Page 699 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description- 2: pinning based on binary comparison of received and configured certificate• 13: (D)TLS session resumption
Allowed values:• TOBY-L200-03A / TOBY-L200-03S / TOBY-L201 / TOBY-L210-03A / TOBY-L210-03S /TOBY-L280-03A / TOBY-L280-03S / MPCI-L201 - 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12• TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 /TOBY-L280-02S - 0, 1, 2, 3, 4, 5, 6, 8, 9, 12• MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280 - 0, 1, 2, 3, 4, 5, 6, 8, 9
• LARA-R202 / LARA-R203 / LARA-R211 / LARA-R220 / LARA-R280 / TOBY-R2 - 0, 1, 2, 3, 4, 5,
6, 7, 8, 9, 10• LARA-R204 - 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-U201-63B / LISA-U200-04B /LISA-U201-04B - 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10• SARA-U201-03A / SARA-U201-03B / SARA-U201-03X - 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
• SARA-U260-03S / SARA-U270-03A / SARA-U270-03S / SARA-U270-53S / SARA-U270-73S /SARA-U280 / LISA-U200-03S / LISA-U200-83S / LISA-U201-03A / LISA-U201-03S /LISA-U201-83S - 0, 1, 2, 3, 4, 5, 6, 8, 9
• SARA-G4 / SARA-G3 - 0, 1, 2, 3, 4, 5, 6, 8, 9

<legacy_cs><iana_b1><iana_b2><operation>

Number Legacy cipher suite enumeration
StringFirst byte of IANA cipher suite enumeration
StringSecond byte of IANA cipher suite enumeration
Number Operation to execute when using <legacy_cs>=100 configuration using a list of IANA
enumeration. Allowed values for <operation>:• 0: add cipher suite defined by <iana_b1> and <iana_b2> to the list
• 1: remove cipher suite defined by <iana_b1> and <iana_b2> from the list
<tag>
Number Configures the (D)TLS session resumption. Allowed values:• 0: session resumption status• 1: session resumption type
• 2: session resumption data when the session resumption type is session ID• 12: session resumption data for when the session resumption type is encrypted session ID withlocal encryption<sess_status> Number (D)TLS session resumption status. Allowed values:• 0 (factory-programmed value): disabled• 1: enabled<sess_type>
Number (D)TLS session resumption type. Allowed values:• 0: session ID• 10: encrypted session ID with local encryption<session_id_
Stringbase64 encoded session ID value. The maximum length is 48 characters.
base64><master_Stringbase64 encoded session master key. The maximum length is 64 characters.
secret_base64><encrypted_
Stringbase64 encoded session ID value encrypted with local encryption. The maximum length is 203
session_data>characters<enc_session_ Number length of base64 encoded session ID value encrypted with local encryption.
data_size><param_val1> String
Type and supported content depend on related <op_code> (details are given above)<param_val2> String
Type and supported content depend on related <op_code> (details are given above)<param_val3> String
Type and supported content depend on related <op_code> (details are given above)

27.1.3.4 Notes
TOBY-L2 / MPCI-L2• If <op_code>=2 (cipher suite) the <legacy_cs>=100 (cipher suite list configuration using IANA
enumeration) is not supported.
• If <op_code>=8 (pre-shared key) the <string_type> parameter is not supported. The <preshared_key>
parameter is an ASCII string (maximum length 64 characters).
• If <op_code>=9 (pre-shared key identity) the <string_type> parameter is not supported. The <preshared_
key_id> parameter is an ASCII string (maximum length 128 characters).

UBX-13002752 - R67

27 Device and data security

Page 700 of 1001

u-blox cellular modules - AT commands manual

TOBY-L201-02S / MPCI-L201-02S• The command is not supported by TOBY-L201-02S-00 and MPCI-L201-02S-00.
TOBY-L200 / TOBY-L210 / TOBY-L280 / MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280
MPCI-L200-02S / MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L220 / MPCI-L280• If <op_code>=2 (cipher suite) the <legacy_cs>=99 (cipher suite selection using IANA enumeration) is
not supported.
TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S• <op_code>=7 (client private key password), 10 (SNI), 12 (server certificate pinning) are not supported
by TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L210-03A-00, TOBY-L280-03S-00.
• If <op_code>=2 (cipher suite) the <legacy_cs>=99 (cipher suite selection using IANA enumeration) is
not supported by TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L280-03S-00, TOBY-L210-03A-00.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3• If <op_code>=2 (cipher suite) the <legacy_cs>=99 (cipher suite selection using IANA enumeration) is notsupported.
• If <op_code>=2 (cipher suite) the <legacy_cs>=100 (cipher suite list configuration using IANA
enumeration) is not supported.
• If <op_code>=8 (pre-shared key) the <string_type> parameter is not supported. The <preshared_key>
parameter is an ASCII string (maximum length 64 characters).
• If <op_code>=9 (pre-shared key identity) the <string_type> parameter is not supported. The <preshared_
key_id> parameter is an ASCII string (maximum length 128 characters).
LARA-R202 / LARA-R203 / LARA-R211 / LARA-R220 / LARA-R280 / TOBY-R2• <op_code>=10
(SNI)
is
not
supportedby
TOBY-R200-02B-00,
TOBY-R200-02B-01,
TOBY-R200-02B-02,
TOBY-R200-02B-03,
TOBY-R202-02B-00,
TOBY-R202-02B-01,
TOBY-R202-02B-02,
TOBY-R202-02B-03,
LARA-R202-02B-00,
LARA-R202-02B-01,
LARA-R202-02B-02,
LARA-R203-02B-00,
LARA-R203-02B-01,
LARA-R203-02B-02,
LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02, LARA-R220-62B-00, LARA-R220-62B-01,
LARA-R220-62B-02,
LARA-R280-02B-00,
LARA-R280-02B-01,
LARA-R280-02B-02,
LARA-R280-02B-03.
SARA-U201-63B• <op_code>=10 (SNI) is not supported by SARA-U201-63B-00 and SARA-U201-63B-01.
SARA-U260-03S / SARA-U270-03A / SARA-U270-03S / SARA-U270-53S / SARA-U270-73S /SARA-U280-03S / LISA-U200-03S / LISA-U200-83S / LISA-U201-03A / LISA-U201-03S /LISA-U201-83S• The <op_code>=3 (trusted root certificate internal name) with a specific Root CA internal nameis supported for certificates issued directly from Root certificate authorities without intermediate
certificate authorities. For the certificates issued by intermediate authorities the <param_val>
parameter should be omitted.
• The SSL/TLS security profile does not support the configuration of SNI (Server Name Indication) SSL/
TLS negotiation headers.
27.1.3.5 List of the supported cipher suites
Cipher suite

Cipher suite name

IANA code
0x00000x000A
0x00130x00150x00160x001A
0x001B
0x002F0x0032

TLS_NULL_WITH_NULL_NULL
TLS_RSA_WITH_3DES_EDE_CBC_SHA
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
TLS_DHE_RSA_WITH_DES_CBC_SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_DH_anon_WITH_DES_CBC_SHA
TLS_DH_anon_WITH_3DES_EDE_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_DSS_WITH_AES_128_CBC_SHA

UBX-13002752 - R67

27 Device and data security

Legacycipher suite
configuration

IANA enumeration
cipher suite
configuration<legacy_cs><iana_b1>
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"

5

1

<iana_b2>
"00"
"0A"
"13"
"15"
"16"
"1A"
"1B"
"2F"
"32"

Page 701 of 1001

u-blox cellular modules - AT commands manual

Cipher suite

Cipher suite name

IANA code
0x00330x00340x00350x00390x003A
0x003C
0x003D0x00400x00410x00450x00670x006B
0x006C
0x006D
0x00840x00880x008A
0x008B
0x008C0x008D
0x008E0x008F0x00900x00910x00920x00930x00940x00950x009C0x009D
0x009E0x009F
0x00A80x00A90x00AA
0x00AB
0x00AC
0x00AD
0x00AE
0x00AF
0x00B20x00B30x00B60x00B70x00BA
0x00BE
0x00C00x00C40xC0020xC0030xC0040xC005

TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_DH_anon_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_DH_anon_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
TLS_DH_anon_WITH_AES_128_CBC_SHA256
TLS_DH_anon_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
TLS_PSK_WITH_RC4_128_SHA
TLS_PSK_WITH_3DES_EDE_CBC_SHA
TLS_PSK_WITH_AES_128_CBC_SHA
TLS_PSK_WITH_AES_256_CBC_SHA
TLS_DHE_PSK_WITH_RC4_128_SHA
TLS_DHE_PSK_WITH_3DES_EDE_CBC_SHA
TLS_DHE_PSK_WITH_AES_128_CBC_SHA
TLS_DHE_PSK_WITH_AES_256_CBC_SHA
TLS_RSA_PSK_WITH_RC4_128_SHA
TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA
TLS_RSA_PSK_WITH_AES_128_CBC_SHA
TLS_RSA_PSK_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_PSK_WITH_AES_128_GCM_SHA256
TLS_PSK_WITH_AES_256_GCM_SHA384
TLS_DHE_PSK_WITH_AES_128_GCM_SHA256
TLS_DHE_PSK_WITH_AES_256_GCM_SHA384
TLS_RSA_PSK_WITH_AES_128_GCM_SHA256
TLS_RSA_PSK_WITH_AES_256_GCM_SHA384
TLS_PSK_WITH_AES_128_CBC_SHA256
TLS_PSK_WITH_AES_256_CBC_SHA384
TLS_DHE_PSK_WITH_AES_128_CBC_SHA256
TLS_DHE_PSK_WITH_AES_256_CBC_SHA384
TLS_RSA_PSK_WITH_AES_128_CBC_SHA256
TLS_RSA_PSK_WITH_AES_256_CBC_SHA384
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256
TLS_ECDH_ECDSA_WITH_RC4_128_SHA
TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA

UBX-13002752 - R67

27 Device and data security

Legacycipher suite
configuration

IANA enumeration
cipher suite
configuration<legacy_cs><iana_b1>
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"00"
"C0"
"C0"
"C0"
"C0"

3

2
4

8
6
7

11
9
10

16
17

18
19
12
13

14
15

<iana_b2>
"33"
"34"
"35"
"39"
"3A"
"3C"
"3D"
"40"
"41"
"45"
"67"
"6B"
"6C"
"6D"
"84"
"88"
"8A"
"8B"
"8C"
"8D"
"8E"
"8F"
"90"
"91"
"92"
"93"
"94"
"95"
"9C"
"9D"
"9E"
"9F"
"A8"
"A9"
"AA"
"AB"
"AC"
"AD"
"AE"
"AF"
"B2"
"B3"
"B6"
"B7"
"BA"
"BE"
"C0"
"C4"
"02"
"03"
"04"
"05"

Page 702 of 1001

u-blox cellular modules - AT commands manual

Cipher suite

Cipher suite name

Legacycipher suite
configuration

IANA code
0xC0070xC0080xC0090xC00A
0xC00C
0xC00D
0xC00E
0xC00F
0xC0100xC0110xC0120xC0130xC0140xC0170xC0180xC0190xC0230xC0240xC0250xC0260xC0270xC0280xC0290xC02A
0xC02B
0xC02C
0xC02D
0xC02E
0xC02F
0xC0300xC0310xC0320xC0330xC0340xC0350xC0360xC0370xC0380xC0720xC0730xC0740xC0750xC0760xC0770xC0780xC0790xC07A
0xC07B
0xC07C
0xC07D<legacy_cs>
TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
20
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
21
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
22
TLS_ECDH_RSA_WITH_RC4_128_SHA
TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_NULL_SHA
TLS_ECDHE_RSA_WITH_RC4_128_SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
23
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
24
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
25
TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA
TLS_ECDH_anon_WITH_AES_128_CBC_SHA
TLS_ECDH_anon_WITH_AES_256_CBC_SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
26
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
27
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
28
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
29
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA25630
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
31
TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
32
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
33
TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_PSK_WITH_RC4_128_SHA
TLS_ECDHE_PSK_WITH_3DES_EDE_CBC_SHA
TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA
TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA
TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA256
TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_CBC_
SHA256
TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_CBC_SHA384
TLS_ECDH_ECDSA_WITH_CAMELLIA_128_CBC_SHA256
TLS_ECDH_ECDSA_WITH_CAMELLIA_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384
TLS_ECDH_RSA_WITH_CAMELLIA_128_CBC_SHA256
TLS_ECDH_RSA_WITH_CAMELLIA_256_CBC_SHA384
TLS_RSA_WITH_CAMELLIA_128_GCM_SHA256
TLS_RSA_WITH_CAMELLIA_256_GCM_SHA384
TLS_DHE_RSA_WITH_CAMELLIA_128_GCM_SHA256
TLS_DHE_RSA_WITH_CAMELLIA_256_GCM_SHA384

UBX-13002752 - R67

27 Device and data security

IANA enumeration
cipher suite
configuration<iana_b1>
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"

<iana_b2>
"07"
"08"
"09"
"0A"
"0C"
"0D"
"0E"
"0F"
"10"
"11"
"12"
"13"
"14"
"17"
"18"
"19"
"23"
"24"
"25"
"26"
"27"
"28"
"29"
"2A"
"2B"
"2C"
"2D"
"2E"
"2F"
"30"
"31"
"32"
"33"
"34"
"35"
"36"
"37"
"38"
"72"

"C0"

"73"

"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"

"74"
"75"
"76"
"77"
"78"
"79"
"7A"
"7B"
"7C"
"7D"

Page 703 of 1001

u-blox cellular modules - AT commands manual

Cipher suite

Cipher suite name

IANA code
0xC0860xC0870xC0880xC0890xC08A
0xC08B
0xC08C
0xC08D
0xC08E
0xC08F
0xC0900xC091
0xC0920xC0930xC0940xC0950xC0960xC0970xC0980xC0990xC09A
0xC09B
0xC09C
0xC09D
0xC09E
0xC09F
0xC0340xC0350xC0360xC0370xC0380xC0A00xC0A1
0xC0A20xC0A30xC0A40xC0A50xC0A6
0xC0A70xC0A80xC0A90xC0AA
0xC0AB
0xC0AC
0xC0AD
0xC0AE
0xC0AF
0xCCA80xCCA90xCCAA

TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_GCM_
SHA256
TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_GCM_
SHA384
TLS_ECDH_ECDSA_WITH_CAMELLIA_128_GCM_SHA256
TLS_ECDH_ECDSA_WITH_CAMELLIA_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_CAMELLIA_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_CAMELLIA_256_GCM_SHA384
TLS_ECDH_RSA_WITH_CAMELLIA_128_GCM_SHA256
TLS_ECDH_RSA_WITH_CAMELLIA_256_GCM_SHA384
TLS_PSK_WITH_CAMELLIA_128_GCM_SHA256
TLS_PSK_WITH_CAMELLIA_256_GCM_SHA384
TLS_DHE_PSK_WITH_CAMELLIA_128_GCM_SHA256
TLS_DHE_PSK_WITH_CAMELLIA_256_GCM_SHA384
TLS_RSA_PSK_WITH_CAMELLIA_128_GCM_SHA256
TLS_RSA_PSK_WITH_CAMELLIA_256_GCM_SHA384
TLS_PSK_WITH_CAMELLIA_128_CBC_SHA256
TLS_PSK_WITH_CAMELLIA_256_CBC_SHA384
TLS_DHE_PSK_WITH_CAMELLIA_128_CBC_SHA256
TLS_DHE_PSK_WITH_CAMELLIA_256_CBC_SHA384
TLS_RSA_PSK_WITH_CAMELLIA_128_CBC_SHA256
TLS_RSA_PSK_WITH_CAMELLIA_256_CBC_SHA384
TLS_ECDHE_PSK_WITH_CAMELLIA_128_CBC_SHA256
TLS_ECDHE_PSK_WITH_CAMELLIA_256_CBC_SHA384
TLS_RSA_WITH_AES_128_CCM
TLS_RSA_WITH_AES_256_CCM
TLS_DHE_RSA_WITH_AES_128_CCM
TLS_DHE_RSA_WITH_AES_256_CCM
TLS_ECDHE_PSK_WITH_3DES_EDE_CBC_SHA
TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA
TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA
TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA256
TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA384
TLS_RSA_WITH_AES_128_CCM_8
TLS_RSA_WITH_AES_256_CCM_8
TLS_DHE_RSA_WITH_AES_128_CCM_8
TLS_DHE_RSA_WITH_AES_256_CCM_8
TLS_PSK_WITH_AES_128_CCM
TLS_PSK_WITH_AES_256_CCM
TLS_DHE_PSK_WITH_AES_128_CCM
TLS_DHE_PSK_WITH_AES_256_CCM
TLS_PSK_WITH_AES_128_CCM_8
TLS_PSK_WITH_AES_256_CCM_8
TLS_PSK_DHE_WITH_AES_128_CCM_8
TLS_PSK_DHE_WITH_AES_256_CCM_8
TLS_ECDHE_ECDSA_WITH_AES_128_CCM
TLS_ECDHE_ECDSA_WITH_AES_256_CCM
TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8
TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8
TLS_ECDHE_RSA_WITH_CHACHA20_POL1305_SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POL1305_
SHA256
TLS_DHE_RSA_WITH_CHACHA20_POL1305_SHA256

UBX-13002752 - R67

27 Device and data security

Legacycipher suite
configuration

IANA enumeration
cipher suite
configuration<legacy_cs><iana_b1> <iana_b2>
"C0"
"86"
"C0"

"87"

"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"C0"
"CC"
"CC"

"88"
"89"
"8A"
"8B"
"8C"
"8D"
"8E"
"8F"
"90"
"91"
"92"
"93"
"94"
"95"
"96"
"97"
"98"
"99"
"9A"
"9B"
"9C"
"9D"
"9E"
"9F"
"34"
"35"
"36"
"37"
"38"
"A0"
"A1"
"A2"
"A3"
"A4"
"A5"
"A6"
"A7"
"A8"
"A9"
"AA"
"AB"
"AC"
"AD"
"AE"
"AF"
"A8"
"A9"

"CC"

"AA"

Page 704 of 1001

u-blox cellular modules - AT commands manual

Cipher suite

Cipher suite name

IANA code
0xCCAB
0xCCAC
0xCCAD
0xCCAE

Legacycipher suite
configuration

IANA enumeration
cipher suite
configuration<legacy_cs><iana_b1>
"CC"
"CC"
"CC"
"CC"

TLS_PSK_WITH_CHACHA20_POL1305_SHA256
TLS_ECDHE_PSK_WITH_CHACHA20_POL1305_SHA256
TLS_DHE_PSK_WITH_CHACHA20_POL1305_SHA256
TLS_RSA_PSK_WITH_CHACHA20_POL1305_SHA256<iana_b2>
"AB"
"AC"
"AD"
"AE"

Table 85: Supported cipher suite

27.1.4 Data encryption configuration +USECCFG+USECCFG
Modules
Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A
TOBY-L280-03S MPCI-L201-02S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

27.1.4.1 Description
Configures and enables the password encryption for the stored security data managed by +USECMNG AT
command. The factory-programmed configuration is encryption disabled, a password must be entered in orderto enable the encryption.
After the enabling of the data encryption the +UFWINSTALL and +UFWUPD AT commands will provide
an error result code (CME ERROR: 4 / CME ERROR: not supported); only +UFWSINSTALL AT command
can be issued to perform a FW installation procedure.
The process of enabling encryption is irreversible: it is not possible to disable encryption or modify theentered password after having enabled the encryption. All certificates which were imported (with the+USECMNG AT command before the encryption was enabled) can not be used after the encryption isenabled and can be removed.
27.1.4.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+USECCFG=<op_code>[,<param1>[,<param2>]]
Read

AT+USECCFG=<op_code>

Response

ExampleOK

AT+USECCFG=0,1,"my_pwd"

OK+USECCFG: <op_code>,<param1>[, AT+USECCFG=0<param2>]+USECCFG: 0,0
OK
OK

Encryption configuration
Set
AT+USECCFG=0,1,<password>

OK

AT+USECCFG=0,1,"my_password"

Read+USECCFG: 0,<encyption_status>

OK
AT+USECCFG=0

OK+USECCFG: 0,1

AT+USECCFG=0

OK
Test

AT+USECCFG=?

+USECCFG: (list of supported <op_ +USECCFG: (0),(0-1)
code>s),(list of supported <param1>
OKvalues)OK

27.1.4.3 Defined values
Parameter<op_code>Type
Number<password><encyption_
status>StringNumberUBX-13002752 - R67

Description• 0: configure encryption
Password; the maximum accepted length is 128 characters. It is used for encrypting data.
•

0 (factory-programmed value): encryption disabled

27 Device and data security

Page 705 of 1001

u-blox cellular modules - AT commands manual

ParameterType<param1><param2>

NumberStringDescription• 1: encryption enabled
Content depends on the related <op_code> parameter (see above).
Content depends on the related <op_code> parameter (see above).

27.1.4.4 Notes
TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S /MPCI-L201-02S• The command is not supported by TOBY-L200-03S-00, TOBY-L201-02S-00, TOBY-L210-03S-00,
TOBY-L210-03A-00, TOBY-L280-03S-00, MPCI-L201-02S-00.

27.1.5 AT+USECMNG command example
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
Here below is reported an example with a PEM encoded trusted root certificate.
Command
Response
Description
Step 1: Import a trusted root certificate using the stream of byte similar to +UDWNFILEAT+USECMNG=0,0,"ThawteCA", >Start the data transfer using the1516
stream of byte.
PEM encoded trusted root
+USECMNG: 1,0,"ThawteCA","8ccadc0
Input PEM formatted trusted root
certificate data.
b22cef5be72ac411a11a8d812"
certificate data bytes. Output MD5hash string of the stored trusted
OKroot certificate DER.
Step 2: List all available certificates and private keys
AT+USECMNG=3
CA, "ThawteCA","thawte Primary Root CA", List all available certificates and"2036/07/17"
private keys.
OK
Step 3: Set the security profile 2 validation level to trusted root
AT+USECPRF=2,0,1
OK

Security profile 2 has the validationlevel set to trusted root.
Step 4: Set the security profile 2 trusted root certificate to the CA certificate imported as "ThawteCA"
AT+USECPRF=2,3,"ThawteCA"
OK
Security profile 2 will use the CA
certificate imported as "ThawteCA"
for server certificate validation.
Step 5: Use the configured USECMNG profile 2 with the UHTTP application
AT+UHTTP=0,1,"www.ssl_tls_
OK
Configure the UHTTP server name.
test_server.com"
AT+UHTTP=0,6,1,2
OK
Enable the SSL/TLS for the UHTTP
profile #0 and specify the SSL/TLS
security profile 2.
AT+UHTTPC=0,1,"/","https.resp" OK
Execute the HTTP GET command.
+UUHTTPCR: 0,1,1
HTTP GET URC response.

In the above example the following PEM encoded trusted certificate is used:-----BEGIN CERTIFICATE----MIIEIDCCAwigAwIBAgIQNE7VVyDV7exJ9C/ON9srbTANBgkqhkiG9w0BAQUFADCBqTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDHRoYXd0ZSwgSW5jLjEoMCYGA1UECxMf
Q2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjE4MDYGA1UECxMvKGMpIDIw
MDYgdGhhd3RlLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxHzAdBgNVBAMTFnRoYXd0ZSBQcmltYXJ5IFJvb3QgQ0EwHhcNMDYxMTE3MDAwMDAwWhcNMzYw
NzE2MjM1OTU5WjCBqTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDHRoYXd0ZSwgSW5j
LjEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjE4MDYG
A1UECxMvKGMpIDIwMDYgdGhhd3RlLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNl
IG9ubHkxHzAdBgNVBAMTFnRoYXd0ZSBQcmltYXJ5IFJvb3QgQ0EwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQCsoPD7gFnUnMekz52hWXMJEEUMDSxuaPFs
W0hoSVk3/AszGcJ3f8wQLZU0HObrTQmnHNK4yZc2AreJ1CRfBsDMRJSUjQJib+ta
3RGNKJpchJAQeg29dGYvajig4tVUROsdB58Hum/u6f1OCyn1PoSgAfGcq/gcfomk
6KHYcWUNo1F77rzSImANuVud37r8UVsLr5iy6S7pBOhih94ryNdOwUxkHt3Ph1i6
Sk/KaAcdHJ1KxtUvkcx8cXIcxcBn6zL9yZJclNqFwJu/U30rCfSMnZEfl2pSy94J
NqR32HuHUETVPm4pafs5SSYeCaWAe0At6+gnhcn+Yf1+5nyXHdWdAgMBAAGjQjBA

UBX-13002752 - R67

27 Device and data security

Page 706 of 1001

u-blox cellular modules - AT commands manual

MA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7W0XP
r87Lev0xkhpqtvNG61dIUDANBgkqhkiG9w0BAQUFAAOCAQEAeRHAS7ORtvzw6WfU
DW5FvlXok9LOAz/t2iWwHVfLHjp2oEzsUHboZHIMpKnxuIvW1oeEuzLlQRHAd9mz
YJ3rG9XRbkREqaYB7FViHXe4XI5ISXycO1cRrK1zN44veFyQaEfZYGDm/Ac9IiAX
xPcW6cTYcvnIc3zfFi8VqT79aie2oetaupgf1eNNZAqdE8hhuvU5HIe6uL17In/2/qxAeeWsEG89jxt5dovEN7MhGITlNgDrYyCZuen+MwS7QcjBAvlEYyCegc5C09Y/
LHbTY5xZ3Y+m4Q6gLkH3LpVHz7z9M/P2C2F+fpErgUfCJzDupxBdN49cOSvkBPB7
jVaMaA==-----END CERTIFICATE-----

27.1.6 Notes
Due to significant memory fingerprint of an SSL/TLS connection, the number of concurrent SSL/TLS
connections is limited. The USECMNG and the underlying SSL/TLS infrastructure allows 4 concurrent SSL/
TLS connections (i.e. 4 HTTPS requests or 2 HTTPS and 2 FTPS request).
SARA-G4 / SARA-G3
The USECMNG and the underlying SSL/TLS infrastructure allows 2 concurrent SSL/TLS connections (i.e.
2 HTTPS requests or 1 HTTPS and 1 FTPS request).

27.1.7 Cipher suite applicability
27.1.7.1 Cipher suite applicability accordingly to the modules
This section provides a list of cipher suites that are available on the series modules. The allowed cipher suites
can be selected when <op_code>=2 (cipher suite) with:• the <legacy_cs> parameter• the <legacy_cs>=99 specifying <iana_b1> and <iana_b2> parameters• the <legacy_cs>=100 specifying <iana_b1> and <iana_b2> parameters
For proper <legacy_cs> value, see the +USECPRF AT command.
The cipher suites marked with (D) are the default cipher suites that are proposed to the server when <op_code>=2 (cipher suite) and <legacy_cs>=0. The secure connection will be established if the server supports atleast one of the proposed cipher suites.
TOBY-L200 / TOBY-L210 / TOBY-L220 / TOBY-L280 / MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280
TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S /MPCI-L200-02S / MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S / MPCI-L210-63S / MPCI-L220 /MPCI-L280• TOBY-L200-03S-00 / TOBY-L210-03S-00 / TOBY-L280-03S-00 / TOBY-L210-03A-00
The allowed cipher suites are presented in the following list:• (0x002F) TLS_RSA_WITH_AES_128_CBC_SHA (D)• (0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256 (D)• (0x0035) TLS_RSA_WITH_AES_256_CBC_SHA (D)• (0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256 (D)• (0x000A) TLS_RSA_WITH_3DES_EDE_CBC_SHA (D)• (0x008C) TLS_PSK_WITH_AES_128_CBC_SHA (D)• (0x008D) TLS_PSK_WITH_AES_256_CBC_SHA (D)• (0x008B) TLS_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA (D)• (0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA (D)• (0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x00AE) TLS_PSK_WITH_AES_128_CBC_SHA256 (D)• (0x00AF) TLS_PSK_WITH_AES_256_CBC_SHA384 (D)• (0x00B6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 (D)• (0x00B7) TLS_RSA_PSK_WITH_AES_256_CBC_SHA384 (D)TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03A /TOBY-L280-03S
The allowed cipher suites are presented in the following list:

UBX-13002752 - R67

27 Device and data security

Page 707 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

(0x000A) TLS_RSA_WITH_3DES_EDE_CBC_SHA (D)(0x0015) TLS_DHE_RSA_WITH_DES_CBC_SHA (D)(0x0016) TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (D)(0x001A) TLS_DH_anon_WITH_DES_CBC_SHA (D)(0x001B) TLS_DH_anon_WITH_3DES_EDE_CBC_SHA (D)(0x002F) TLS_RSA_WITH_AES_128_CBC_SHA (D)(0x0033) TLS_DHE_RSA_WITH_AES_128_CBC_SHA (D)(0x0034) TLS_DH_anon_WITH_AES_128_CBC_SHA (D)(0x0035) TLS_RSA_WITH_AES_256_CBC_SHA (D)(0x0039) TLS_DHE_RSA_WITH_AES_256_CBC_SHA (D)(0x003A) TLS_DH_anon_WITH_AES_256_CBC_SHA (D)(0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256 (D)(0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256 (D)(0x0067) TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (D)(0x006B) TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (D)(0x006C) TLS_DH_anon_WITH_AES_128_CBC_SHA256 (D)(0x006D) TLS_DH_anon_WITH_AES_256_CBC_SHA256 (D)(0x008B) TLS_PSK_WITH_3DES_EDE_CBC_SHA (D)(0x008C) TLS_PSK_WITH_AES_128_CBC_SHA (D)(0x008D) TLS_PSK_WITH_AES_256_CBC_SHA (D)(0x008F) TLS_DHE_PSK_WITH_3DES_EDE_CBC_SHA (D)(0x0090) TLS_DHE_PSK_WITH_AES_128_CBC_SHA (D)(0x0091) TLS_DHE_PSK_WITH_AES_256_CBC_SHA (D)(0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA (D)(0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA (D)(0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA (D)(0x00A8) TLS_PSK_WITH_AES_128_GCM_SHA256 (D)(0x00A9) TLS_PSK_WITH_AES_256_GCM_SHA384 (D)(0x00AA) TLS_DHE_PSK_WITH_AES_128_GCM_SHA256 (D)(0x00AB) TLS_DHE_PSK_WITH_AES_256_GCM_SHA384 (D)(0x00AC) TLS_RSA_PSK_WITH_AES_128_GCM_SHA256 (D)(0x00AD) TLS_RSA_PSK_WITH_AES_256_GCM_SHA384 (D)(0x00AE) TLS_PSK_WITH_AES_128_CBC_SHA256 (D)(0x00AF) TLS_PSK_WITH_AES_256_CBC_SHA384 (D)(0x00B2) TLS_DHE_PSK_WITH_AES_128_CBC_SHA256 (D)(0x00B3) TLS_DHE_PSK_WITH_AES_256_CBC_SHA384 (D)(0x00B6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 (D)(0x00B7) TLS_RSA_PSK_WITH_AES_256_CBC_SHA384 (D)(0xC003) TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA (D)(0xC004) TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA (D)(0xC005) TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA (D)(0xC008) TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA (D)(0xC009) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (D)(0xC00A) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (D)(0xC00D) TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA (D)(0xC00E) TLS_ECDH_RSA_WITH_AES_128_CBC_SHA (D)(0xC00F) TLS_ECDH_RSA_WITH_AES_256_CBC_SHA (D)(0xC012) TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (D)(0xC013) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (D)(0xC014) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (D)(0xC017) TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA (D)(0xC018) TLS_ECDH_anon_WITH_AES_128_CBC_SHA (D)(0xC019) TLS_ECDH_anon_WITH_AES_256_CBC_SHA (D)UBX-13002752 - R67

27 Device and data security

Page 708 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

(0xC023) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (D)(0xC024) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (D)(0xC025) TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 (D)(0xC026) TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 (D)(0xC027) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (D)(0xC028) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (D)(0xC029) TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 (D)(0xC02A) TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 (D)(0xC02B) TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (D)(0xC02C) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (D)(0xC02D) TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 (D)(0xC02E) TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 (D)(0xC02F) TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (D)(0xC030) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (D)(0xC031) TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 (D)(0xC032) TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 (D)(0xC0AE) TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 (D)TOBY-L201 / MPCI-L201
TOBY-L201-02S / MPCI-L201-02S
The allowed cipher suites are presented in the following list:• (0x000A) TLS_RSA_WITH_3DES_EDE_CBC_SHA (D)• (0x0015) TLS_DHE_RSA_WITH_DES_CBC_SHA (D)• (0x0016) TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (D)• (0x001A) TLS_DH_anon_WITH_DES_CBC_SHA (D)• (0x001B) TLS_DH_anon_WITH_3DES_EDE_CBC_SHA (D)• (0x002F) TLS_RSA_WITH_AES_128_CBC_SHA (D)• (0x0033) TLS_DHE_RSA_WITH_AES_128_CBC_SHA (D)• (0x0034) TLS_DH_anon_WITH_AES_128_CBC_SHA (D)• (0x0035) TLS_RSA_WITH_AES_256_CBC_SHA (D)• (0x0039) TLS_DHE_RSA_WITH_AES_256_CBC_SHA (D)• (0x003A) TLS_DH_anon_WITH_AES_256_CBC_SHA (D)• (0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256 (D)• (0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256 (D)• (0x0067) TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (D)• (0x006B) TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (D)• (0x006C) TLS_DH_anon_WITH_AES_128_CBC_SHA256 (D)• (0x006D) TLS_DH_anon_WITH_AES_256_CBC_SHA256 (D)• (0x008B) TLS_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x008C) TLS_PSK_WITH_AES_128_CBC_SHA (D)• (0x008D) TLS_PSK_WITH_AES_256_CBC_SHA (D)• (0x008F) TLS_DHE_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x0090) TLS_DHE_PSK_WITH_AES_128_CBC_SHA (D)• (0x0091) TLS_DHE_PSK_WITH_AES_256_CBC_SHA (D)• (0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA (D)• (0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA (D)• (0x00A8) TLS_PSK_WITH_AES_128_GCM_SHA256 (D)• (0x00A9) TLS_PSK_WITH_AES_256_GCM_SHA384 (D)• (0x00AA) TLS_DHE_PSK_WITH_AES_128_GCM_SHA256 (D)• (0x00AB) TLS_DHE_PSK_WITH_AES_256_GCM_SHA384 (D)• (0x00AC) TLS_RSA_PSK_WITH_AES_128_GCM_SHA256 (D)• (0x00AD) TLS_RSA_PSK_WITH_AES_256_GCM_SHA384 (D)• (0x00AE) TLS_PSK_WITH_AES_128_CBC_SHA256 (D)UBX-13002752 - R67

27 Device and data security

Page 709 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

(0x00AF) TLS_PSK_WITH_AES_256_CBC_SHA384 (D)(0x00B2) TLS_DHE_PSK_WITH_AES_128_CBC_SHA256 (D)(0x00B3) TLS_DHE_PSK_WITH_AES_256_CBC_SHA384 (D)(0x00B6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 (D)(0x00B7) TLS_RSA_PSK_WITH_AES_256_CBC_SHA384 (D)(0xC003) TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA (D)(0xC004) TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA (D)(0xC005) TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA (D)(0xC008) TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA (D)(0xC009) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (D)(0xC00A) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (D)(0xC00D) TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA (D)(0xC00E) TLS_ECDH_RSA_WITH_AES_128_CBC_SHA (D)(0xC00F) TLS_ECDH_RSA_WITH_AES_256_CBC_SHA (D)(0xC012) TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (D)(0xC013) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (D)(0xC014) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (D)(0xC017) TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA (D)(0xC018) TLS_ECDH_anon_WITH_AES_128_CBC_SHA (D)(0xC019) TLS_ECDH_anon_WITH_AES_256_CBC_SHA (D)(0xC023) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (D)(0xC024) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (D)(0xC025) TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 (D)(0xC026) TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 (D)(0xC027) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (D)(0xC028) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (D)(0xC029) TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 (D)(0xC02A) TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 (D)(0xC02B) TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (D)(0xC02C) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (D)(0xC02D) TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 (D)(0xC02E) TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 (D)(0xC02F) TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (D)(0xC030) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (D)(0xC031) TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 (D)(0xC032) TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 (D)(0xC0AE) TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 (D)SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3
The allowed cipher suites are presented in the following list:• (0x002F) TLS_RSA_WITH_AES_128_CBC_SHA (D)• (0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256 (D)• (0x0035) TLS_RSA_WITH_AES_256_CBC_SHA (D)• (0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256 (D)• (0x000A) TLS_RSA_WITH_3DES_EDE_CBC_SHA (D)• (0x008C) TLS_PSK_WITH_AES_128_CBC_SHA (D)• (0x008D) TLS_PSK_WITH_AES_256_CBC_SHA (D)• (0x008B) TLS_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA (D)• (0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA (D)• (0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x00AE) TLS_PSK_WITH_AES_128_CBC_SHA256 (D)• (0x00AF) TLS_PSK_WITH_AES_256_CBC_SHA384 (D)• (0x00B6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 (D)UBX-13002752 - R67

27 Device and data security

Page 710 of 1001

u-blox cellular modules - AT commands manual•(0x00B7) TLS_RSA_PSK_WITH_AES_256_CBC_SHA384 (D)LARA-R202 / LARA-R203 / LARA-R204 / TOBY-R2
The available cipher suites are presented in the following list:• (0x002F) TLS_RSA_WITH_AES_128_CBC_SHA (D)• (0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256 (D)• (0x0035) TLS_RSA_WITH_AES_256_CBC_SHA (D)• (0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256 (D)• (0x000A) TLS_RSA_WITH_3DES_EDE_CBC_SHA (D)• (0x008C) TLS_PSK_WITH_AES_128_CBC_SHA (D)• (0x008D) TLS_PSK_WITH_AES_256_CBC_SHA (D)• (0x008B) TLS_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA (D)• (0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA (D)• (0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x00AE) TLS_PSK_WITH_AES_128_CBC_SHA256 (D)• (0x00AF) TLS_PSK_WITH_AES_256_CBC_SHA384 (D)• (0x00B6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 (D)LARA-R211 / LARA-R220 / LARA-R280• LARA-R211-02B-00 / LARA-R211-02B-01 / LARA-R211-02B-02 / LARA-R220-62B-00 / LARA-R220-62B-01 /LARA-R220-62B-02 / LARA-R280-02B-00 / LARA-R280-02B-01 / LARA-R280-02B-02 / LARA-R280-02B-03
The available cipher suites are presented in the following list:• (0x002F) TLS_RSA_WITH_AES_128_CBC_SHA (D)• (0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256 (D)• (0x0035) TLS_RSA_WITH_AES_256_CBC_SHA (D)• (0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256 (D)• (0x000A) TLS_RSA_WITH_3DES_EDE_CBC_SHA (D)• (0x008C) TLS_PSK_WITH_AES_128_CBC_SHA (D)• (0x008D) TLS_PSK_WITH_AES_256_CBC_SHA (D)• (0x008B) TLS_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA (D)• (0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA (D)• (0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x00AE) TLS_PSK_WITH_AES_128_CBC_SHA256 (D)• (0x00AF) TLS_PSK_WITH_AES_256_CBC_SHA384 (D)• (0x00B6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 (D)LARA-R211 / LARA-R220 / LARA-R280
The available cipher suites are presented in the following list:• (0x002F) TLS_RSA_WITH_AES_128_CBC_SHA (D)• (0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256 (D)• (0x0035) TLS_RSA_WITH_AES_256_CBC_SHA (D)• (0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256 (D)• (0x000A) TLS_RSA_WITH_3DES_EDE_CBC_SHA (D)• (0x008C) TLS_PSK_WITH_AES_128_CBC_SHA (D)• (0x008D) TLS_PSK_WITH_AES_256_CBC_SHA (D)• (0x008B) TLS_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA (D)• (0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA (D)• (0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA (D)• (0x00AE) TLS_PSK_WITH_AES_128_CBC_SHA256 (D)• (0x00AF) TLS_PSK_WITH_AES_256_CBC_SHA384 (D)• (0x00B6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 (D)• (0x00B7) TLS_RSA_PSK_WITH_AES_256_CBC_SHA384• (0x00A8) TLS_PSK_WITH_AES_128_GCM_SHA256

UBX-13002752 - R67

27 Device and data security

Page 711 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

(0x00A9) TLS_PSK_WITH_AES_256_GCM_SHA384(0x00AC) TLS_RSA_PSK_WITH_AES_128_GCM_SHA256(0x00AD) TLS_RSA_PSK_WITH_AES_256_GCM_SHA384(0xC008) TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA(0xC009) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA(0xC00A) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA(0xC012) TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA(0xC013) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA(0xC014) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA(0xC023) TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256(0xC024) TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384(0xC027) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256(0xC028) TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384(0xC02B) TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256(0xC02C) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384(0xC02F) TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256(0xC030) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

UBX-13002752 - R67

27 Device and data security

Page 712 of 1001

u-blox cellular modules - AT commands manual

28 FTP
Proprietary u-blox AT commands. FTP AT commands set can be used for sending and receiving files over
the available bearer, transparently retrieving and storing them in the file system. Standard file and directory
management operations on the remote FTP server are as well possible. PSD or CSD connection must be
activated before using FTP client services.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
See +UPSD, +UPSDA and +UPSND AT commands for establishing a PSD connection.
SARA-G3 / LEON-G1
See +UCSD, +UCSDA and +UCSND AT commands for establishing a CSD connection.
Basically, two AT commands are necessary for an FTP client service: one AT command (+UFTP) to configure
the FTP profile, a second AT command to execute a specific FTP command (+UFTPC). The final result of an FTP
command will be notified through the +UUFTPCR URC whereas data will be provided through +UUFTPCD URC.
When these commands report an error which is not a +CME ERROR, the error code can be queried using the+UFTPER AT command.

28.1 FTP service configuration +UFTP+UFTP
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

28.1.1 Description
Sets up a parameter for FTP service, or resets a parameter to its factory-programmed value. The set/reset
command needs to be executed for each single <op_code>. The read command returns the current setting of
all the FTP parameters, one per line (i.e. the FTP profile). The FTP parameter values set with this command are
all volatile (not stored in non-volatile memory).
If the set command is issued without <param1> parameter, the corresponding <op_code> parameter isreset to the default value.

28.1.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UFTP=<op_code>[,<param1>[,<param2>]]
FTP server IP address
Set
AT+UFTP=0[,<IP_address>]

Response

ExampleOK

AT+UFTP=7,21
OK

OK

AT+UFTP=0,"192.168.1.0"
OK

FTP server name
Set
AT+UFTP=1[,<server_name>]

OK

AT+UFTP=1,"ftp.server.com"
OK

Username
Set
AT+UFTP=2[,<username>]

OK

AT+UFTP=2,"user_test"
OK

Password
Set
AT+UFTP=3[,<password>]

OK

AT+UFTP=3,"PWD"
OK

UBX-13002752 - R67

28 FTP

Page 713 of 1001

u-blox cellular modules - AT commands manualType
Account
Set

SyntaxResponse

ExampleAT+UFTP=4[,<account>]

OK

AT+UFTP=4,"test"
OK

Inactivity timeout
Set
AT+UFTP=5[,<timeout>]

OK

AT+UFTP=5,21
OK

FTP mode
Set
AT+UFTP=6[,<FTP_mode>]

OK

AT+UFTP=6,1
OK

FTP server port
Set
AT+UFTP=7[,<FTP_server_port>]

OK

AT+UFTP=7,30
OK

FTP control connection security
Set
AT+UFTP=8[,<FTP_secure>[,<USECMNG_profile>]]Timer trigger configuration for Direct Link
Set
AT+UFTP=9,<timer_trigger>

OK

AT+UFTP=8,1,2
OK

OK

AT+UFTP=9,500
OK

Data length trigger configuration for Direct Link
Set
AT+UFTP=10,<data_length_trigger> OK

AT+UFTP=10,1024
OK

Character trigger configuration for Direct Link
Set
AT+UFTP=11,<character_trigger>
OK

AT+UFTP=11,13
OK

FTP data connection security
Set
AT+UFTP=12[,<FTP_secure>[,<USECMNG_profile>]]

OK

Read

+UFTP: 0,<IP_address>+UFTP: 0,"216.239.59.147"+UFTP: 1,<server_name>+UFTP: 1,""

+UFTP: 2,<username>+UFTP: 2,"username"+UFTP: 4,<account>+UFTP: 4,"account"+UFTP: 5,<timeout>+UFTP: 5,0+UFTP: 6,<FTP_mode>+UFTP: 6,0+UFTP: 7,<FTP_server_port>+UFTP: 7,21

+UFTP: 8,<FTP_secure>[,<USECMNG_profile>]+UFTP: 8,0

AT+UFTP?

AT+UFTP=12,1,2
OK+UFTP: 9,<timer_trigger>+UFTP: 10,<data_length_trigger>+UFTP: 11,<character_trigger>

Test

AT+UFTP=?

+UFTP: 9,500+UFTP: 10,1024+UFTP: 11,13+UFTP: 12,0

+UFTP: 12,<FTP_secure>[,<USECMNG_profile>]

OK

OK+UFTP: (list of supported <param_tag>s)+UFTP: (0-11)
OKOK

28.1.3 Defined values
Parameter<op_code>

UBX-13002752 - R67

TypeStringDescription
FTP parameter:• 0: FTP server IP address

28 FTP

Page 714 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type<IP_address>

String<server_name>

String<username>

String<password>

String<account>

String<timeout>

Number<FTP_mode>

Number<FTP_server_port>

Number<FTP_secure>

Number<USECMNG_profile> Number<timer_trigger>

Number<data_length_
Numbertrigger><character_trigger> Number<param1>

Number /String<param2>

Number /StringUBX-13002752 - R67

Description• 1: FTP server name• 2: FTP username• 3: FTP password• 4: FTP additional user account• 5: FTP inactivity timeout period• 6: FTP mode
• 7: remote FTP server listening port
• 8: control connection security• 9: timer trigger• 10: data length trigger• 11: character trigger• 12: data connection security
Allowed values:• TOBY-L200 / TOBY-L201-02S / TOBY-L210 / TOBY-L220 / TOBY-L280 /MPCI-L200 / MPCI-L201-02S / MPCI-L210 / MPCI-L220 / MPCI-L280 / LARA-R2 /TOBY-R2 - 0, 1, 2, 3, 4, 5, 6, 7, 8
• TOBY-L201-01S / MPCI-L201-01S - 0, 1, 2, 3, 4, 5, 6, 7
• SARA-U2 / LISA-U2 / LISA-U1 - 0, 1, 2, 3, 4, 5, 6, 7, 8
• SARA-G4 / SARA-G340-01S / SARA-G340-02S / SARA-G340-02X /SARA-G350-01B / SARA-G350-01S / SARA-G350-02A / SARA-G350-02S /SARA-G350-02X - 0, 1, 2, 3, 4, 5, 6, 7, 8
• SARA-G340-00S / SARA-G350-00S / SARA-G350-00X / LEON-G1 - 0, 1, 2, 3, 4, 5, 6, 7
FTP server IP address. The default value is an empty string. For IP address format
reference see the IP addressing.
FTP server name (e.g. "ftp.server.com"). The maximum length is 128 characters. The
default value is an empty string.
User name (the maximum length is 30 characters) for the FTP login procedure. The
default value is an empty string.
Password (the maximum length is 30 characters) for the FTP login procedure. The
default value is an empty string.
Additional user account (if required) for the FTP login procedure. The maximum
length is 30 characters. The default value is an empty string.
Inactivity timeout period in seconds. The range goes from 0 to 86400 s; 0 means notimeout (the FTP session will not be terminated in the absence of incoming traffic).
The default value is 30 s.
FTP mode:• 0 (default value): active• 1: passive
Remote FTP server listening port; it must be a valid TCP port value. The range goesfrom 1 to 65535; the default value is 21.
Enables / disables the secure option of FTP client service:• 0 (default value): no SSL encryption• 1: enable SSL encryption of FTP (control connection or data connection). Only the
explicit FTPS mode is supported.
USECMNG profile (number). Defines the USECMNG profile which specifies the SSL/
TLS properties to be used for the SSL/TLS connection. The range goes from 0 to 4. If
no profile is set a default USECMNG profile is used (see USECMNG section).
Enhanced direct link sending timer trigger (in milliseconds); valid range is 0 (factoryprogrammed value), 100-120000; 0 means trigger disabled.
Enhanced direct link data length trigger in bytes, valid range is 0 (factoryprogrammed value), 3-2048; 0 means trigger disabled.
Enhanced direct link character trigger, the value represents the ASCII code (in base 10) of the character to be used as character trigger. The allowed range is -1, 0-255, thefactory-programmed value is -1; -1 means trigger disabled.
Type and supported content depend on related <op_code> (details are given above).
If <param1> is not specified the value of the corresponding parameter <op_code> isreset to default value.
Type and supported content depend on related <op_code> (details are given above).
If <param2> is not specified the value of the corresponding parameter <op_code> isreset to default value.

28 FTP

Page 715 of 1001

u-blox cellular modules - AT commands manual

28.1.4 Notes
•
•
•

•

The information text response to the read command does not display the password.
The FTP server IP address and the FTP server name are mutually exclusive. If value for <op_code>=0 is
specified by user, then value for <op_code>=1 is reset or vice versa.
Some network operators do not allow incoming connections. Due to these limitations introduced by
network operators it is possible to encounter problems using FTP active mode. If the FTP active mode
fails to exchange files, try the passive mode to solve the problem.
Some network operators do not allow FTPS. In this case the +UFTPC=1 command (FTP login) will returna failure response via +UUFTPCR URC after an SSL timeout of 30 s.

TOBY-L2 / MPCI-L2• <timer_trigger>, <data_length_trigger> and <character_trigger> parameters are not supported.
• If the PSD profile protocol type is set to IPv6 (see the +UPSD AT command description), the IP addressof the FTP server must be in IPv6 format.
TOBY-L201-02S / MPCI-L201-02S• <op_code>=8 is not supported by TOBY-L201-02S-00, MPCI-L201-02S-00.
LARA-R2 / TOBY-R2• <timer_trigger>, <data_length_trigger> and <character_trigger> parameters are not supported.
• If the PSD profile protocol type is set to IPv6 (see the +UPSD AT command description), the IP addressof the FTP server must be in IPv6 format.
• During connection to FTP remote server (via FTP login command) the FTP profile parameters cannot bechanged or reset to factory-programmed values until disconnection takes place (FTP logout). Only <op_code>=5 (inactivity timeout), and <op_code>=6 (FTP mode), can be updated while the FTP connection is
on the go.
SARA-U2 / LISA-U2 / LISA-U1• <timer_trigger>, <data_length_trigger> and <character_trigger> parameters are not supported.
• During connection to FTP remote server (via FTP login command) the FTP profile parameters cannot bechanged or reset to factory-programmed values until disconnection takes place (FTP logout). Only <op_code>=5 (inactivity timeout), and <op_code>=6 (FTP mode), can be updated while the FTP connection is
on the go.
SARA-U260 / SARA-U270 / SARA-U280 / LISA-U200-00S / LISA-U200-01S / LISA-U200-02S /LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S / LISA-U201-03A /LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1• The <USECMNG_profile> parameter is not supported.
SARA-G4 / SARA-G3 / LEON-G1• <timer_trigger>, <data_length_trigger> and <character_trigger> parameters are not supported.
SARA-G340-01S / SARA-G350-01B / SARA-G350-01S• The server IP or name shall be inserted prior to the SSL encryption option (<op_code>=8).
• The <USECMNG_profile> parameter is not supported.

UBX-13002752 - R67

28 FTP

Page 716 of 1001

u-blox cellular modules - AT commands manual

28.2 FTP command +UFTPC+UFTPC
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

28.2.1 Description
Triggers the FTP actions corresponding to the <op_code> parameter. The final result code indicates if sending
the command request to the FTP process was successful or not. The +UUFTPCR (FTP command result) URC
returns to the user the final result of the FTP command previously sent with +UFTPC. As well, the +UUFTPCD
FTP unsolicited data URC provides the data requested by the user (e.g. file or directory lists) and received fromthe FTP server.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
If the SSL option is enabled and the network operator does not allow FTPS, the +UUFTPCR URC notifies
the command failure after an SSL timeout of 30 s.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1
The +UUFTPCD URC is displayed only on the AT terminal that issued the +UFTPC related command.
TOBY-L2 / MPCI-L2 / SARA-U260 / SARA-U270 / SARA-U280 / LISA-U200-00S / LISA-U200-01S /LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S / LISA-U201-03A /LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G4 / SARA-G340 /SARA-G350 / LEON-G1
FTPC data commands use the extended EPSV/EPRT which supports IPv6 adressing. If the FTP server
implementation of the EPSV/EPRT commands response is non-standard the FTPC data commands fail.
The timing before the +UUFTPCR URC is issued on the AT terminal also depends by the DNS resolution.
For further details about the estimated response time related to the DNS resolution, see the +UDNSRNAT command.

28.2.2 Syntax
Type
SyntaxResponse
General syntax
Set
AT+UFTPC=<op_code>[,<param1>[, OK<param2>[,<param3>]]]
FTP logout
Set
AT+UFTPC=0

OK

ExampleAT+UFTPC=4,"data.zip","data.zip"
OK
AT+UFTPC=0OK

FTP login
Set
AT+UFTPC=1

OK

AT+UFTPC=1
OK

Delete the file from the FTP server
Set
AT+UFTPC=2,<file_name>

OK

AT+UFTPC=2,"mytest"
OK

Rename a file of FTP server
Set
AT+UFTPC=3,<file_name>,<new_file_name>

OK

AT+UFTPC=3,"old_name","final_
name"
OK

Retrieve the file from the FTP server
Set
AT+UFTPC=4,<remote_file_name>, OK<local_file_name>[,<retrieving_mode>]

UBX-13002752 - R67

AT+UFTPC=4,"data.zip","data.zip"
OK

28 FTP

Page 717 of 1001

u-blox cellular modules - AT commands manualType
SyntaxResponse
Store the file on the FTP server
Set
AT+UFTPC=5,<local_file_name>,OK<remote_file_name>[,<number_of_
byte>]

ExampleAT+UFTPC=5,"data.zip","data.zip",
30
OK

Retrieve a file from the FTP server using direct link mode
Set
AT+UFTPC=6,<remote_file_name>[, OK<number_of_byte>]

AT+UFTPC=6,"data.zip",30

Send a file to the FTP server using the direct link mode
Set
AT+UFTPC=7,<remote_file_name>[, OK<number_of_byte>]

AT+UFTPC=7,"data.zip",30

OK

OK

Change the working directory to the specified one
Set
AT+UFTPC=8,<directory_name>
OK

AT+UFTPC=8,"data_folder"OK

Create a directory on the FTP host
Set
AT+UFTPC=10,<directory_name>

OK

AT+UFTPC=10,"new_data_folder"OK

Remove the directory from the remote FTP server
Set
AT+UFTPC=11,<directory_name>
OK

AT+UFTPC=11,"data_folder"
OK

Information of a file or a directory
Set
AT+UFTPC=13[,<file_directory_name>]OK

List the file names in a specified directory
Set
AT+UFTPC=14[,<file_directory_name>]

OK

Retrieve the FOTA update file
Set
AT+UFTPC=100,<remote_file_name>[,<fw_download_status>]

OK

Test

AT+UFTPC=?

AT+UFTPC=13,"data_folder"
OK
AT+UFTPC=14,"data.zip"
OK
AT+UFTPC=100,"data.zip"+UFTPC: (list of supported <op_code>s)OK
URC+UUFTPCD: <op_code>,<ftp_data_
len>,<ftp_data>
URC+UUFTPCR: <op_code>,<ftp_
result>[,<md5_sum>]
Status during the FOTA update file transfer (<op_code>=100)
URC+UUFTPCR: 100,<stored_byte> /<total_byte>

OK+UFTPC: (0-5,8,10,11,13,14,100)
OK+UUFTPCD: 13,16,"16 bytes of data"+UUFTPCR: 1,1+UUFTPCR: 100,202752 / 1103692

28.2.3 Defined values
Parameter<op_code>

UBX-13002752 - R67

Type
NumberDescription
FTP command request. Allowed values:• 0: FTP logout; terminates the FTP session by performing a logout.
• 1: FTP login; connects to the FTP server using the parameters of the current FTP
profile (set via AT+UFTP command).
• 2: deletes the file from the FTP server.
• 3: renames the file. This AT command just sends requests to the FTP process.
• 4: retrieves the file from the FTP server.
• 5: stores the file on the FTP server.
• 6: retrieves a file from the FTP server using direct link mode. This command handles
the initial steps of the FTP protocol for retrieving a file; after that it will establish
a transparent end to end communication with the data connection TCP socket via
the serial interface. After the CONNECT result code, the file content will be directly

28 FTP

Page 718 of 1001

u-blox cellular modules - AT commands manual

ParameterType<file_name>

String<new_file_name>
String<remote_file_name> String<local_file_name>

String<retrieving_mode>

Number<number_of_byte>

Number<directory_name>

String<file_directory_
name>String<fw_download_
status>Number<ftp_data_len><ftp_data>

NumberString<ftp_result>

Number<md5_sum>

String<param1>

StringUBX-13002752 - R67

Description
sent to the serial interface. When the data transfer is completed, the module willautomatically exit from direct link mode (no need to send +++ sequence).
• 7: sends a file to the FTP server using the direct link mode. This command handles
the initial steps of the FTP protocol for sending a file; after that it will establish atransparent end to end communication with the data connection TCP socket via
the serial interface. After the CONNECT result code, the user can send the filecontent via the serial interface. Once finished, the user must wait at least 2 s before
sending the +++ sequence to switch off the direct link mode. This operation may
take a few seconds because the command also handles the final steps of the FTP
protocol.
• 8: changes the working directory to the specified one.
• 9: RFU.
• 10: creates a directory on the FTP host.
• 11: removes the directory from the remote FTP server.
• 12: RFU.
• 13: information of a file or a directory. The URC +UUFTPCD returns the informationof the specified file or directory from the FTP server.
• 14: lists the file names in a specified directory. The URC +UUFTPCD returns the listof the file names received from FTP server. If the directory name is omitted, the listof the files names of current working directory is requested.
• 100: retrieves the FOTA update file. The downloaded file will not be accessible to theuser. The +UUFTPCR URC will display the MD5 checksum of the downloaded file.
File name to be deleted/renamed from the FTP host. For the limit of the length of thestring, see Command line.
New file name. For the limit of the length of the string, see Command line.
Remote file name to be retrieved from the FTP host or stored in it. The maximum
parameter length is 256 characters.
Local file name (module file system) text string to be stored/sent on the file system.
For the limit of the length of the string, see the File system limits.
Allowed values:• 0 (default value): the file is retrieved from beginning.
• 1: restart the data retrieving from the last data received during the previous
download interrupted due to error.
Represents the number of bytes already sent to the FTP server or received from it.
• During a file retrieval the server writes the file from the offset indicated with thisparameter.
• During a file storing the server sends the data from the value indicated with thisparameter.
Directory name on the FTP server. For the limit of the length of the string, see
Command line.
Path file/directory name to be listed. If not specified, the current directory list isrequested. For the limit of the length of the string, see Command line.
• <param1> optional parameter; the text string of the path (file or directory) to bename listed. If not specified, the list of the files names of current working directory
is requested.
Manages the firmware package download status:• if omitted trigger the firmware package download from an FTP server• 0: cancel the firmware package download from an FTP server• 1: resume the firmware package download from an FTP server
Amount of data in bytes
Data available from the FTP server in the ASCII [0x00,0xFF] range. The starting
quotation mark shall not be taken into account like data, the first byte of data starts
after the first quotation mark. The total number of bytes is <ftp_data_len>. At theend of the byte stream, another quotation mark is provided for user convenience andvisualization purposes.
Allowed values:• 0: fail• 1: successMD5 checksum of the FOTA update file downloaded via +UFTPC=100 AT command.
This parameter is issued only for +UFTPC=100 AT command.
Content depend on related <op_code> (details are given above)

28 FTP

Page 719 of 1001

u-blox cellular modules - AT commands manual

Parameter<param2><param3><stored_byte><total_byte>

Type
StringStringNumberNumberDescription
Content depend on related <op_code> (details are given above)
Content depend on related <op_code> (details are given above)
Amount of stored bytes
Amount of total bytes of the FOTA update file to be stored

28.2.4 Notes•

If <op_code>=6 the user must switch off the direct link mode (sending +++ to the serial interface) when
the data stream is finished. This operation may take up to 10 s because the command also handles the
final steps of the FTP protocol.

TOBY-L2 / MPCI-L2• The <fw_download_status> parameter is not supported.
• The+UUFTPCR: 100,<stored_byte> / <total_byte> URC is not supported.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• <op_code>=100 is not supported.
• The <md5_sum> parameter is not supported.
LISA-U200-00S / LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S / LISA-U1 /SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S / LEON-G1• <number_of_byte> is not supported if <op_code>=6 or <op_code>=7.

28.3 FTP error +UFTPER+UFTPER
Modules

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error
Appendix A.9.1

Attributes

28.3.1 Description
This command retrieves the error class and code of the last FTP operation.

28.3.2 Syntax
Type
ActionSyntax
AT+UFTPER

Response+UFTPER: <error_class>,<error_
code>

Example+UFTPER: 1,1
OKOK

28.3.3 Defined values
Parameter<error_class><error_code>

UBX-13002752 - R67

Type
NumberNumberDescription
Value of error class. Values are listed in Appendix A.9.
Value of class-specific error code (reply code if <error_class> is 0). The values arelisted in Appendix A.9.1.

28 FTP

Page 720 of 1001

u-blox cellular modules - AT commands manual

29 HTTPThe section describes the u-blox proprietary AT commands that can be used for sending requests to a remote
HTTP server, receiving the server response and transparently storing it in the file system. The supported
methods are: HEAD, GET, DELETE, PUT, POST file and POST data. A PSD or CSD connection must be activatedbefore using HTTP AT commands.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
See +UPSD, +UPSDA and +UPSND AT commands for establishing a PSD connection.
SARA-G3 / LEON-G1
See +UCSD, +UCSDA and +UCSND AT commands for establishing a CSD connection.
When these commands report an HTTP error, the error code can be queried using the +UHTTPER AT command.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / LEON-G1
If using CellLocate® and HTTP commands HTTP profiles in the range 1-3 must be used.

29.1 HTTP control +UHTTP+UHTTP
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

29.1.1 Description
Configures, reads or resets (to the factory-programmed values) the HTTP application profile parameters. Up
to 4 different HTTP profiles can be defined. To set all the parameters in an HTTP profile a set command foreach <op_code> needs to be issued.
The configured HTTP profile parameters are not saved in the non volatile memory.
The read command has two possible usages. The functionality of the command differs with the numberof command parameters issued:• Only the first command parameter (<profile_id>) issued: the module resets all the profile parameters(to the factory-programmed values) for the profile specified with <profile_id>• Only the first and second command parameters used (<profile_id>, <op_code>): the module returns
the current value of the profile parameter specified with <op_code> and related to the profile specified
with <profile_id>

29.1.2 Syntax
Type
SyntaxResponse
Generic syntax
Set
AT+UHTTP=<profile_id>,<op_OK
code>,<param_val>[,<param_val1>]
Read

AT+UHTTP=<profile_id>,<op_code> +UHTTP: <profile_id>,<op_code>,<param_val>[,<param_val1>]OK

AT+UHTTP=2,0,"125.24.51.133"
OK
AT+UHTTP=2,0+UHTTP: 2,0,"125.24.51.133"
OK

HTTP server IP address
Set
AT+UHTTP=<profile_id>,0,<HTTP_ OK
server_IP_address>

UBX-13002752 - R67

ExampleAT+UHTTP=2,0,"125.24.51.133"
OK

29 HTTP

Page 721 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UHTTP=<profile_id>,0

Response+UHTTP: <profile_id>,0,<HTTP_
server_IP_address>
OK

HTTP server name
Set
AT+UHTTP=<profile_id>,1,<HTTP_
server_name>
Read

AT+UHTTP=<profile_id>,1

Read

AT+UHTTP=<profile_id>,2+UHTTP: 2,0,"125.24.51.133"
OK

OK

AT+UHTTP=2,1,"www.u-blox.com"+UHTTP: <profile_id>,1,<HTTP_
server_name>
OK

Username
Set
AT+UHTTP=<profile_id>,2,<username>ExampleAT+UHTTP=2,0

OK
AT+UHTTP=2,1+UHTTP: 2,1,"www.u-blox.com"
OK

OK

AT+UHTTP=2,2,"my_user"

OK+UHTTP: <profile_id>,2,<username> AT+UHTTP=2,2
OK+UHTTP: 2,2,"my_user"
OK

Password
Set
AT+UHTTP=<profile_id>,3,<password>
Read

AT+UHTTP=<profile_id>,3OK

AT+UHTTP=2,3,"pwd"

OK+UHTTP: <profile_id>,3,<password> AT+UHTTP=2,3
OK+UHTTP: 2,3,"pwd"
OK

Authentication type
Set
AT+UHTTP=<profile_id>,4,<HTTP_ OK
authentication>
Read

AT+UHTTP=<profile_id>,4AT+UHTTP=2,4,1+UHTTP: <profile_id>,4,<HTTP_
authentication>
OK

AT+UHTTP=<profile_id>,5

AT+UHTTP=2,5,30+UHTTP: <profile_id>,5,<HTTP_
port>
OK

AT+UHTTP=<profile_id>,6

Read

AT+UHTTP=<profile_id>,9+UHTTP: 2,5,30

AT+UHTTP=2,6,1+UHTTP: <profile_id>,6,<HTTP_
secure>[,<USECMNG_profile>]
OK

HTTP add custom request headers
Set
AT+UHTTP=<profile_id>,9,<custom_request_header>

OK
AT+UHTTP=2,5
OK

HTTP secure option
Set
AT+UHTTP=<profile_id>,6,<HTTP_ OK
secure>[,<USECMNG_profile>]
Read+UHTTP: 2,4,1
OK

HTTP server port
Set
AT+UHTTP=<profile_id>,5,<HTTP_ OK
port>
Read

OK
AT+UHTTP=2,4

OK
AT+UHTTP=2,6+UHTTP: 2,6,1
OK

OK

AT+UHTTP=2,9,"0:hdr0:val0"+UHTTP: <profile_id>,9,<custom_
request_header>
OK

OK
AT+UHTTP=2,9+UHTTP: 2,9,"0:hdr0:val0"
OK

Read

AT+UHTTP=<profile_id>

OK

Test

AT+UHTTP=?

OK+UHTTP: (list of supported <profile_ +UHTTP: (0-3),(0-9)id>s),(list of supported <op_code>s)OK

UBX-13002752 - R67

AT+UHTTP=2

29 HTTP

Page 722 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example29.1.3 Defined values
Parameter<profile_id><op_code>Type
NumberNumber<HTTP_server_IP_
address><HTTP_server_
name>

String<username>

String<password>

String<HTTP_
authentication>

Number<HTTP_port>

Number<HTTP_secure>

NumberString<USECMNG_profile> Number<custom_request_
header>String<param_val>

Number /StringUBX-13002752 - R67

Description
HTTP profile identifier, in range 0-3• 0: HTTP server IP address;• 1: HTTP server name;• 2: username• 3: password• 4: authentication type
• 5: HTTP server port
• 6: HTTP Secure option (SSL encryption)• 7: HTTP request timeout• 8: reserved for internal use only
• 9: HTTP add custom request headers
HTTP server IP address; The factory-programmed value is an empty text string. For IP
address format reference see the IP addressing.
HTTP server name (e.g. "http.server.com"). The factory-programmed value is anempty text string. The maximum length is:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1 - 128 characters
User name; the maximum length is 30 characters; it is used for the HTTP login
procedure if the authentication is used. The factory-programmed value is an empty
text string.
Password; the maximum length is 30 characters; it is used for the HTTP login
procedure if the authentication is used. The factory-programmed value is an empty
text string.
HTTP authentication method; the allowed values are:• 0 (factory-programmed value): no authentication• 1: basic authentication (the password and username must be set)
HTTP server port; range 1-65535. It means the HTTP server port to be used in a HTTP
request; the factory-programmed value is 80.
HTTP Secure option (SSL encryption). It enables or disables the HTTPS (SSL securedconnection for HTTP application) usage:• 0 (factory-programmed value): HTTPS (SSL encryption) disabled and the HTTP
server port set to 80• 1: HTTPS (SSL encryption) enabled and the HTTP server port set to 443; an
USECMNG profile can be specified with an additional parameter.
Defines the USECMNG profile which specifies the SSL/TLS properties to be used
for the SSL/TLS connection. The range goes from 0 to 4. If no profile is set a default
USECMNG profile is used
Sets/clears the custom request header (string); the custom header option follows
a defined format "hdr_id:hdr_name:hdr_value"; the hdr_id is a number in the range[0-4]; the hdr_name and hdr_value are strings having a maximum length of 64
characters (see examples below).
• "0:hdr0:val0": set header 0 with name hdr0 and value val0
• "0:": clear header 0• "1:hdr1:val1": set header 1 with name hdr1 and value val1
• "1:": clear header 1• "2:hdr2:val2": set header 2 with name hdr2 and value val2
• "2:": clear header 2• "3:hdr3:val3": set header 3 with name hdr3 and value val3
• "3:": clear header 3• "4:hdr4:val4": set header 4 with name hdr4 and value val4
• "4:": clear header 4
The following character is not allowed in the <custom_request_header> parameter:• 0x3A (:)
Type and supported content depend on the related <op_code> parameter; details are
given above

29 HTTP

Page 723 of 1001

u-blox cellular modules - AT commands manual

Parameter<param_val1>

Type
Number /StringDescription
Type and supported content depend on the related <op_code> parameter; details are
given above.

29.1.4 Notes•

HTTP server IP address and HTTP server name are mutually exclusive. If the HTTP server IP address is
specified by the user, then the value for the HTTP server name is reset, or vice versa.

TOBY-L2 / MPCI-L2 / SARA-U201-03A / SARA-U201-03B / SARA-U201-03X / SARA-U201-63B /SARA-U260 / SARA-U270 / SARA-U280 / LISA-U200-00S / LISA-U200-01S / LISA-U200-02S /LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S / LISA-U201-03A / LISA-U201-03S /LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G340-00S / SARA-G340-01S /SARA-G350-00S / SARA-G350-00X / SARA-G350-01B / SARA-G350-01S / SARA-G350-02X / LEON-G1• <op_code>=9 (HTTP add custom request headers) is not supported.
LARA-R2 / TOBY-R2 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / LISA-U200-04B /LISA-U201-04B / SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S• The read command for <op_code>=9 (HTTP add custom request headers) is not supported.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2• If the +UPSD command sets the PSD profile protocol type to IPv6, an IPv6 address shall be used forparameter HTTP server IP address.
TOBY-L201-01S / MPCI-L201-01S• <op_code>=6 (HTTP Secure option) is not supported.
TOBY-L201-02S / MPCI-L201-02S• <op_code>=6 (HTTP Secure option) is not supported by TOBY-L201-02S-00, MPCI-L201-02S-00.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270 / LISA-U1 / SARA-G340-01S / SARA-G350-01B / SARA-G350-01S• <USECMNG_profile> parameter is not supported.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / SARA-G340-01S /SARA-G350-01B / SARA-G350-01S / LEON-G1• When HTTP Secure option is enabled, the default HTTP port is automatically set to 443. If the port ismanually set (with the <op_code>=5) to a custom port other than 80 prior to enabling the secure option
the custom port setting will not be modified.
SARA-G340-00S / SARA-G350-00S / SARA-G350-00X / LEON-G1• <op_code>=6 (HTTP Secure option) is not supported.

29.2 HTTP advanced control+UHTTPAC+UHTTPAC
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G4 SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

29.2.1 Description
Configures, reads or resets (to the factory-programmed values) the HTTP application profile advanced
parameters.
The configured HTTP profile advanced parameters are not saved in the non volatile memory.

UBX-13002752 - R67

29 HTTP

Page 724 of 1001

u-blox cellular modules - AT commands manual

29.2.2 Syntax
Type
Set

SyntaxAT+UHTTPAC=<profile_id>,<param_tag>,<key>,<value>

Response
OK

ExampleAT+UHTTPAC=0,0,0,"UBLX_SESSION_COOKIE_0"

Read

AT+UHTTPAC=<profile_id>,<param_tag>,<key>+UHTTPAC: <profile_id>,<param_tag>,<key>,<value>
OK

Test

AT+UHTTPAC=?

+UHTTPAC: (list of supported<profile_id>s),(list of supported<param_tag>s),(list of supported<key>s)OK
AT+UHTTPAC=0,0,0+UHTTP: 0,0,0,"UBLX_SESSION_COOKIE_0"
OK+UHTTPAC: (0-3),(0),(0-3)
OKOK

29.2.3 Defined values
Parameter<profile_id><param_tag>

Type
NumberNumber<key>

Number/StringNumber/String<value>Description
HTTP profile identifier, in range 0-3•

0: HTTP request COOKIES; manage request COOKIES sent to the HTTP server.
o <key>: index of the cookie (number); range 0-3. Identifies the cookie to be readif <value> is omitted or configured if <value> is a valid string.
o <value>: value of the cookie (string); the maximum length is 256 characters. The
cookie values respect the following rules:- Empty string (""): the cookie will be cleared and will not be present in therequest;- Simple one-value cookie: the cookie will be set and sent in the request;- Complex multi-value cookie: the cookies will be set and sent in the request.
The multiple cookies must be separated by a left-attached semicolon(";")
and a space(" ");Content depends on the related <param_tag> (see above).
Content depends on the related <param_tag> (see above).

29.2.4 Examples and use cases
In this section some +UHTTPAC AT command examples and use cases are listed.
Command
Example 1
AT+UHTTPAC=0,0,0,""Example 2
AT+UHTTPAC=0,0,0,"SIMPLE_COOKIE"
Example 3
AT+UHTTPAC=0,0,0,"COMPLEX_COOKIE; COMPLEX_COOKIE"UBX-13002752 - R67

Response

Description

OK

Clear the HTTP request cookie at index 0.

OK

Set a simple HTTP request cookie at index 0.

OK

Overwrite the HTTP request cookie at index
0 with a complex cookie.

29 HTTP

Page 725 of 1001

u-blox cellular modules - AT commands manual

29.3 HTTP command +UHTTPC+UHTTPC
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

29.3.1 Description
Triggers the HTTP command specified with <http_command> parameter, using the HTTP application profile
parameters (previously set up by +UHTTP AT command), specified with <profile_id>. The response indicates
if sending the command request to HTTP process was successful or not. The final result of HTTP command
will be returned to the user via the +UUHTTPCR URC.
The timing before the +UUHTTPCR URC is issued on the AT terminal also depends by the DNS resolution.
For further details about the estimated response time related to the DNS resolution, see the +UDNSRNAT command.

29.3.2 Syntax
Type
SyntaxResponse
Generic syntax
Set
AT+UHTTPC=<profile_id>,<http_OKcommand>,<path>,<filename>[,<param1>[,<param2>[,<param3>]]]HEAD command
Set
AT+UHTTPC=<profile_id>,0,<path>, OK<filename>ExampleAT+UHTTPC=0,1,"/path/file.html","responseFilename"
OK
AT+UHTTPC=0,0,"/path/file.html","responseFilename"OK

GET command
Set
AT+UHTTPC=<profile_id>,1,<path>, OK<filename>

AT+UHTTPC=0,1,"/path/file.html","responseFilename"
OK

DELETE command
Set
AT+UHTTPC=<profile_id>,2,<path>, OK<filename>

AT+UHTTPC=0,2,"/path/file.html","responseFilename"OK

PUT command
Set
AT+UHTTPC=<profile_id>,3,<path>, OK<filename>,<filesystem_name>[,<HTTP_content_type>[,<user_
defined_content_type>]]

AT+UHTTPC=0,3,"/path/
file.html","responseFilename","filesystemName"

POST file command
Set
AT+UHTTPC=<profile_id>,4,<path>, OK<filename>,<filesystem_name>,<HTTP_content_type>[,<user_
defined_content_type>]

AT+UHTTPC=0,4,"/path/
file.html","responseFilename","filesystemName",0OK

OK

POST data command
Set
AT+UHTTPC=<profile_id>,5,OK<path>,<filename>,<data>,<HTTP_
content_type>[,<user_defined_
content_type>]
GET FOTA update file

UBX-13002752 - R67

AT+UHTTPC=0,5,"/path/file.html","responseFilename","data",0OK

29 HTTP

Page 726 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+UHTTPC=<profile_id>,100,<path>

Response
OK

Test

AT+UHTTPC=?

+UHTTPC: (list of supported<profile_id>s),(list of supported<http_command>s)OK

OK+UUHTTPCR: <profile_id>,<http_command>,<http_result>[,<http_status_code>,<md5_sum>]

URC

ExampleAT+UHTTPC=0,100,"/path/file.html"+UHTTPC: (0-3),(0-5),100OK+UUHTTPCR: 0,1,1

29.3.3 Defined values
Parameter<profile_id><http_command>Type
NumberNumber<path>

String<filename>

String<filesystem_name> String<HTTP_content_
type>

Number<user_defined_
content_type><data>

Number<param1><param2><param3><http_result>

StringNumberStringNumberString<http_status_code> Number<md5_sum>

UBX-13002752 - R67

StringDescription
HTTP profile identifier, in range 0-3
•
•
•
•
•
•

0: HEAD command; issue an HEAD request to the HTTP server
1: GET command; perform a GET request to the HTTP server
2: DELETE command; send a DELETE request to the HTTP server
3: PUT command; perform a PUT request to the HTTP server.
4: POST a file command; issue a POST request for sending a file to the HTTP server
5: POST data command; send a POST request to the HTTP server using the data
specified in <data> parameter• 100: GET FOTA update file; download the FOTA update file
Path of HTTP server resource; the maximum length is:• TOBY-L2 / MPCI-L2 / LARA-R202-02B / LARA-R203 / LARA-R204 / LARA-R211 /LARA-R220 / LARA-R280 / TOBY-R200-02B / TOBY-R200-42B / TOBY-R202 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - 128 characters• LARA-R202-82B / TOBY-R200-82B - 1024 characters
Filename where the HTTP server response will be stored. If the file already exists, itwill be overwritten. If the parameter is an empty string (""), the default "http_last_
response_<profile_id>" filename will be used. For file system file name and data size
limits see File system limits.
File system filename representing the file system filename to be sent to the HTTP
server within the POST / PUT request. For file system file name and data size limits
see File system limits.
HTTP Content-Type identifier. It represents the HTTP Content-Type identifier.
Allowed values:• 0: application/x-www-form-urlencoded• 1: text/plain• 2: application/octet-stream• 3: multipart/form-data• 4: application/json (supported only for PUT and POST file command)• 5: application/xml• 6: user defined with <user_defined_content_type>
Used only when <HTTP_content_type>=6 (user defined Content-Type). The
maximum length is 64 characters.
It represents the data to be sent to the HTTP server with the POST request. The
maximum length is 128 bytes. The data must be formatted according to the ContentType specified in <HTTP_content_type> parameter.
Content depends on the related <http_command> (see above).
Content depends on the related <http_command> (see above).
Content depends on the related <http_command> (see above).
• 0: fail• 1: success
HTTP status code reported in the server response header after a GET FOTA update
file request. This parameter is issued only for AT+UHTTPC=<profile_id>,100,<path>
AT command.
MD5 checksum of the FOTA update file. This parameter is issued only for AT+UHTTPC=<profile_id>,100,<path> AT command.

29 HTTP

Page 727 of 1001

u-blox cellular modules - AT commands manual

29.3.4 Notes•••

The +UHTTPC command has a default timeout setting set to 180 s. The timeout is counted from the last
successful network read or send operation performed by the HTTP application, so in a real timeout casethe application might be executing a command more than 180 s.
The data string must not exceed the maximum length of 128 bytes.
If <http_command>=4 (POST a file) and the <HTTP_content_type>=3 (multipart/form-data), then themodule automatically encapsulates the file content in the following multipart/form-data HTTP request:--U1Blox2Http3Unique4Boundary5\r\nContent-Disposition: form-data; name="file_post"; filename="<user_defined_content_type>"\r\nContent-Length: <length of file specified with <user_defined_content_type>>\r\nContent-Type: application/octet-stream\r\n\r\n<content of file specified with <user_defined_content_type>>\r\n--U1Blox2Http3Unique4Boundary5--\r\n\r\n•The response headers string (headers received in the HTTP response) must not exceed the maximum
length of 256 bytes.

TOBY-L200-02S / TOBY-L201-01S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 /TOBY-L280-02S / MPCI-L200 / MPCI-L201-01S / MPCI-L210 / MPCI-L220 / MPCI-L280 / LARA-R2 /TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• <http_command> = 100 is not supported.
TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S /MPCI-L201-02S• <http_command>=100
isnotsupportedby
TOBY-L200-03S-00,
TOBY-L201-02S-00,
TOBY-L210-03A-00, TOBY-L210-03S-00, TOBY-L280-03S-00 and MPCI-L201-02S-00.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U230 / LISA-U260 /LISA-U270 / LISA-U1 / SARA-G340-00S / SARA-G350-00S / SARA-G350-00X / LEON-G1• <HTTP_content_type>= 4, 5 and 6 are not supported.
LISA-U200-62S• <HTTP_content_type>= 6 is not supported.
SARA-G340-01S / SARA-G350-01B / SARA-G350-01S• <HTTP_content_type>= 6 is not supported.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270 / LISA-U1 / SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / LEON-G1• HTTP parameters <HTTP_content_type> and <user_defined_content_type> are not supported for PUT
command.

UBX-13002752 - R67

29 HTTP

Page 728 of 1001

u-blox cellular modules - AT commands manual

29.4 HTTP protocol error +UHTTPER+UHTTPER
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201 TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S
MPCI-L200-03S MPCI-L201 MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U2 LISA-U1
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error
Appendix A.9

29.4.1 Description
Retrieves the error class and code of the latest HTTP operation on the specified HTTP profile.

29.4.2 Syntax
Type
Set

SyntaxAT+UHTTPER=<profile_id>

Response+UHTTPER: <profile_id>,<error_class>,<error_code>
OK

ExampleAT+UHTTPER=1+UHTTPER: 1,0,0OK

29.4.3 Defined values
Parameter<profile_id><error_class><error_code>

UBX-13002752 - R67

Type
NumberNumberNumberDescription
HTTP profile identifier, in range 0-3
List of the allowed values is available in Appendix A.9
Value of class-specific error codes (reply code if class is 0). When <error_class>=10(wrong HTTP API usage), the allowed <error_code>; values are listed in Appendix A.9.2

29 HTTP

Page 729 of 1001

u-blox cellular modules - AT commands manual

30 SMTPu-blox proprietary SMTP AT commands provide the capability of sending text mails over the available data
connection, with support of some header fields and attachments transparently retrieved from the file system.
A PSD or CSD connection must be activated before using SMTP AT commands: refer to +UCSD, +UCSDA and+UCSND AT commands for establishing a CSD connection and to +UPSD, +UPSDA and +UPSND AT commands
for establishing a PSD connection.
When these commands report an error which is not a +CME ERROR, the error code can be queried using the+USMTPER AT command.

30.1 SMTP control +USMTP+USMTP
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference+CME Error

30.1.1 Description
Sets up the necessary parameters for SMTP service, or resets parameters to the factory-programmed value.
A set command for each <param_tag> needs to be issued to configure the SMTP setting. The read command
returns the current setting of all the SMTP parameters except for the password, one per line (i.e. the SMTP
profile).
The SMTP parameter values specified with this command are all volatile (not stored in non-volatile memory).
In the set command, if only the first parameter is issued, the module resets the parameter to thefactory-programmed value.

30.1.2 Syntax
Type
SyntaxSMTP control generic syntax
Set
AT+USMTP=<op_code>[,<param1>[,<param2>]]

Response

ExampleOK

AT+USMTP=0,"151.9.37.66"
OK

SMTP server IP address
Set
AT+USMTP=0[,<SMTP_server_
address>]

OK

SMTP server name
Set
AT+USMTP=1[,<SMTP_server_
name>]OK

AT+USMTP=0,"151.9.37.66"
OK
AT+USMTP=1,"smtp.mail.yahoo.com"
OK

SMTP username
Set
AT+USMTP=2[,<username>]

OK

AT+USMTP=2,"myusername"
OK

SMTP password
Set
AT+USMTP=3[,<password>]

OK

AT+USMTP=3,"mypassword"
OK

SMTP authentication type
Set
AT+USMTP=4[,<authentication>]

OK

AT+USMTP=4,1
OK

SMTP inactivity timeout
Set
AT+USMTP=5[,<inactivity_
timeout>]

OK

AT+USMTP=5,50
OK

SMTP time zone

UBX-13002752 - R67

30 SMTP

Page 730 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxResponse
AT+USMTP=6[,<hour_differential>, OK<minute_differential>]

SMTP client port
Set
AT+USMTP=7,<port>

OK

ExampleAT+USMTP=6,3,30
OK
AT+USMTP=7,9025
OK

Read

AT+USMTP?

+USMTP: 0,<SMTP_server_
address>+USMTP: 1,<SMTP_server_name>+USMTP: 2,<username>+USMTP: 4,<authentication>+USMTP: 5,<inactivity_timeout>+USMTP: 6,<hour_differential>,<minute_differential>+USMTP: 7,<port>

Test

AT+USMTP=?

+USMTP: 0,"69.147.102.58"+USMTP: 1,""+USMTP: 2,"username"+USMTP: 4,1+USMTP: 5,0+USMTP: 6,0,0+USMTP: 7,9025
OK

OK+USMTP: (list of supported <param_ +USMTP: (0-7)
tag>s)
OKOK

30.1.3 Defined values
Parameter<op_code>Type
NumberDescription
Type of operation:<SMTP_server_
address><SMTP_server_
name><username>

String• 0: SMTP server IP address• 1: SMTP server name• 2: username• 3: password• 4: authentication type
• 5: inactivity timeout• 6: time zone, used for the date header field of mails• 7: SMTP port configuration
Represents the SMTP server IP address expressed in dotted decimal notation form

<password>

String<authentication>

NumberStringString<inactivity_timeout> Number<hour_differential><minute_differential><port><param_val1><param_val2>

UBX-13002752 - R67

NumberNumberNumberRepresents the string of SMTP server name (e.g. "smtp.server.com"). The maximum
length is 128 characters
Represents the user name (the maximum length is 30 characters) for the SMTP login
procedure if the authentication is used
Represents the password (the maximum length is 30 characters) for the SMTP login
procedure if the authentication is used
SMTP authentication method (if any):• 0 (default value): no authentication• 1: plain authentication• 2: login authentication
Inactivity timeout period expressed in seconds, from 0 to 86400 s. 0 means notimeout (the SMTP session will not be terminated in the absence of incoming traffic);
the default value is 30 s
Represents the value of hour differential, in range [-12; 12] (the default value is 0)
Represents the value of minute differential, in range [0; 59] (the default value is 0).
This is a mandatory parameter if <op_code>=6 and <hour_differential> is specified.
The port used by the SMTP client, in range [1; 65535] (the default value is 25).
Type and content depend on <op_code> parameter (see details above). If theparameter is not specified, the value for the corresponding <op_code> is reset
Type and content depend on related <op_code> parameter (see details above)

30 SMTP

Page 731 of 1001

u-blox cellular modules - AT commands manual

30.1.4 Notes•<op_code>=0 and <op_code>=1 are mutually exclusive. If <param_val1> value for <op_code>=0 is
specified by the user, then value for <op_code>=1 is reset or viceversa.

SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G1• The <port> parameter is not supported. The default port (25) is used.

30.2 SMTP mail control +USMTPM+USMTPM
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time
<1s

Error reference+CME Error

30.2.1 Description
Sets (or resets) the necessary parameters for envelope and body of a mail for the subsequent transmission via
SMTP protocol. To configure the settings for envelope and body of mail the set command needs to be issued
for each <op_code>.
In the set command, if none parameter is issued, the module resets all the internal SMTP buffers to create a
new mail.

30.2.2 Syntax
Type
SyntaxResponse
ActionAT+USMTPM
OK
SMTP mail control generic syntax
Set
AT+USMTPM=<op_code>,<param_ OK
val1>[,<param_val2>,<param_val3>]

ExampleOK
AT+USMTPM=0,"ugo.rossi@ublox.com"
OK

SMTP mail sender address
Set
AT+USMTPM=0,<mail_sender>

OK

AT+USMTPM=0,"ugo.rossi@ublox.com"
OK

SMTP "Reply-To" field
Set
AT+USMTPM=1,<reply_to>

OK

AT+USMTPM=1,"ugo.rossi@ublox.com"
OK

SMTP mail receiver address
Set
AT+USMTPM=2,<mail_receiver>

OK

AT+USMTPM=2,"ugo.rossi@ublox.com"
OK

SMTP mail subject
Set
AT+USMTPM=3,<mail_subject>

OK

AT+USMTPM=3,"This is the
subject"
OK

SMTP mail text
Set
AT+USMTPM=4,<mail_text>

OK

AT+USMTPM=0,"This is the text"
OK

SMTP attachment
Set
AT+USMTPM=5,<mail_attachment_file_name>,<mail_attachment_media_type>,<mail_attachment_media_sub-type>
SMTP enhanced mode
Set
AT+USMTPM=6

UBX-13002752 - R67

OK

AT+USMTPM=5,"screenshot.jpg",2,
"jpg"
OK

OK

AT+USMTPM=630 SMTP

Page 732 of 1001

u-blox cellular modules - AT commands manualType

Syntax@<mail_text><Ctrl-Z>

Response

Test

AT+USMTPM=?

+USMTPM: (list of supported <op_code>s)Example@<mail text><Ctrl-Z>
OK+USMTPM: (0-5)
OKOK

30.2.3 Defined values
Parameter<op_code>Type
Number<mail_sender>

String<reply_to>

String<mail_receiver>

String<mail_subject>

String<mail_text>

String<mail_attachment_
file_name><mail_attachment_
media_type>

String<mail_attachment_
media_sub-type><param_val1>

String<param_val2><param_val3>

NumberStringNumberStringDescription•••

0: set the mail sender address
1: set the "Reply-To" field
2: add the mail receiver. Up to 10 different recipient addresses can be added for eachnew mail• 3: set the mail subject• 4: set the mail text
• 5: add an attachment. The attachment must be a file stored in the file system andaccessible by the SMTP client. Up to 10 attachments can be added for each new
mail• 6: set the mail text in enhanced mode: it is possible to write text messages up to4096 bytes. After having issued the AT+USMTPM=6 command a '@' prompt will
be displayed. After this prompt it is possible to write the mail text. To finish the
input send the special character Ctrl-Z (0x1A). Anyway if the total length of 4096
characters is reached, the command automatically exits from the input mode
Mandatory parameter representing the text string of the sender address. It must bein the form "local_part@domain" and not exceed 64 characters
Mandatory parameter representing the text string of the address which reply should
be sent to. It must be in form "local_part@domain" and not exceed 64 characters
Mandatory parameter representing recipient address text string. It must be in form
"local_part@domain" and not exceed 64 characters.
Mandatory parameter representing the text string of the mail subject. The parametermust not exceed the maximum length of 64 bytes.
Mandatory parameter representing the text string of the mail text. The parametermust not exceed the maximum length of 512 bytes.
Mandatory parameter representing the attachment file nameMandatory parameter of the media type. Allowed values:• 0: undefined media type
• 1: text media type
• 2: image media type
• 3: audio media type
• 4: video media type
• 5: application media type<param_val3> mandatory parameter, text string of media sub-type
Type and content depend on <op_code> (see details above). If <param_val1> is not
specified, the value for the corresponding <op_code> is reset
Type and content depend on related <op_code> (see details above)
Type and content depend on related <op_code> (see details above)

30.2.4 Notes•

In case <mail_attachment_media_type>= 0 (undefined media type), the empty string ("") can be used as
input value for <mail_attachment_media_sub-type> parameter.

UBX-13002752 - R67

30 SMTP

Page 733 of 1001

u-blox cellular modules - AT commands manual

30.3 SMTP command +USMTPC+USMTPC
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time
<1s

Error reference+CME Error

30.3.1 Description
Triggers the SMTP action corresponding to <smtp_command> parameter. The response indicates if sending
the command request to SMTP process was successful or not. The final SMTP command result will be notified
to the user via the +UUSMTPCR URC.

30.3.2 Syntax
Type
Set

SyntaxAT+USMTPC=<smtp_command>

Response
OK

Test

AT+USMTPC=?

+USMTPC: (list of supported<smtp_command>s)OK+UUSMTPCR: <smtp_command>,<smtp_result>[,<reject_rcpt_
addr1>[,<reject_rcpt_addr2>[,...]]]URC

ExampleAT+USMTPC=1
OK+USMTPC: (0-2)
OK+UUSMTPCR: 1,1

30.3.3 Defined values
Parameter<smtp_command>Type
Number<smtp_result>

NumberDescription•

0: SMTP quit; terminates the SMTP session issueing a QUIT command, then closes
the TCP connection with the SMTP server.
• 1: SMTP connect; using the parameters of current SMTP profile (set via AT+USMTP
command) connects to the SMTP server via TCP, reads its greeting and sends the
HELO command, after which the handshake is complete, and the SMTP client isready for sending mails.
• 2: Send mail; sends the previously prepared mail (set up via AT+USMTPM
command) to the connected SMTP server via the MAIL - RCPT - DATA commands
sequence.
Result code of SMTP operation•••<reject_rcpt_addrN> String

0: Failure
1: Success
2: Partial success; this result code can be returned after AT+USMTPC=2 command(Send mail), when the mail has been delivered to some of the specified recipients
only. In this case the list of mail addresses of rejected recipients follows.
Rejected recipient N, in the form "local_part@domain", in case the final result of AT+USMTPC=2 command (Send mail) is a Partial success.

30.4 SMTP error +USMTPER+USMTPER
Modules
Attributes

SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted
full
No
No
No

Response time-Error reference
SMTP Errors+CME Error

30.4.1 Description
Retrieves the error class and code of the last SMTP operation.

UBX-13002752 - R67

30 SMTP

Page 734 of 1001

u-blox cellular modules - AT commands manual

30.4.2 Syntax
Type
Set

SyntaxAT+USMTPER

Response+USMTPER: <error_class>,<error_
code>
OK

ExampleAT+USMTPER+USMTPER: 0,0OK

30.4.3 Defined values
Parameter<error_class><error_code>

UBX-13002752 - R67

Type
NumberNumberDescription
Value of error class; see Appendix A.9
Value of class-specific error code (reply code if class is 0). The allowed values arelisted in Appendix A.9.3

30 SMTP

Page 735 of 1001

u-blox cellular modules - AT commands manual

31 Ping
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3 / LEON-G1
The ping service requires the user to define and activate a connection profile before executing the +UPING
command. See +UPSD, +UPSDA and +UPSND AT commands for establishing a PSD connection.
SARA-G3 / LEON-G1
The ping service requires the user to define and activate a connection profile before executing the +UPING
command. See +UCSD, +UCSDA and +UCSND AT commands for establishing a CSD connection.

31.1 Ping command +UPING+UPING
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SARA-G4 SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

31.1.1 Description
The ping command is the common method to know if a remote host is reachable on the internet.
The ping functionality is based on the ICMP protocol (Internet Control Message Protocol), it is part of theInternet Protocol Suite as defined in RFC 792 [45]. ICMP messages are typically generated in response to errors
in IP datagrams or for diagnostic / routing purposes.
The ping command sends an ICMP echo request to the remote host and waits for its ICMP echo reply. If theecho reply packet is not received, it might mean that the remote host is not reachable.
The ping command could be used also to measure e.g. the RTT (Round Trip Time, the time needed by a packet
to go to the remote host and come back) and the TTL (Time To Live, it is a value to understand how many
gateway a packet has gone through).
The AT+UPING allows the user to execute a ping command from the module to a remote peer. The results ofthe ping command execution is notified by means of these URCs:• +UUPING: it reports the +UPING command result when no error occurred.
• +UUPINGER: it is raised if an error is occurred while processing the +UPING command. The URC reports thecode of occurred error (see Ping error codes to get the meanings of the error result codes).
Some network operators may disallow ICMP packets traffic on their network, this means that the +UPING
command may not work.
Some remote hosts might not reply to ICMP echo request for security reasons (e.g. firewall settings).
Some remote hosts might not reply to ICMP echo request if the data size of the echo request is too big.
If a remote peer does not reply to an ICMP echo request, it does not mean that for sure the peer cannot
be reached in another way.

31.1.2 Syntax
Type
Set

SyntaxResponse
AT+UPING=<remote_host>[,<retry_ OK
num>,<p_size>,<timeout>,<ttl>]

Test

AT+UPING=?

UBX-13002752 - R67+UPING: "remote_host",(list of
supported <retry_num>),(listof supported <p_size>),(list of

31 Ping

ExampleAT+UPING="www.google.com"
OK+UPING: "remote_host",(1-64),(41460),(10-60000),(1-255)
OK

Page 736 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
supported <timeout>),(list of
supported <ttl>)
OK+UUPING: <retry_num>,<p_size>,<remote_hostname>,<remote_ip>,<ttl>,<rtt>+UUPINGER: <error_code>

URC

URC

Example+UUPING: 1,32,"www.l-google.com","72.14.234.104",55,768+UUPINGER: 12

31.1.3 Defined values
Parameter<remote_host>Type
String<retry_num>

Number<p_size>

Number<timeout>

Number<ttl>

Number<remote_hostname> String<remote_ip><rtt>

StringNumber<error_code>

NumberDescription
IP address (dotted decimal representation) or domain name of the remote host:• Maximum length: 128 characters
Indicates how many times iterate the ping command:• Range: 1-64
• Default value: 4Size in bytes of the echo packet payload:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 / LEON-G1 - The range goes from 4 to 1460. The default value is 32.
The maximum time in milliseconds to wait for a echo reply response:• Range: 10-60000• Default value: 5000
The value of TTL to be set for the outgoing echo request packet. In the URC it
provides the TTL value received in the incoming packet:• Range: 1-255• Default value: 32
String representing the domain name (if available) of the remote host. It thisinformation is not available, it will be an empty string (i.e. "").
String representing the remote host IP address in dotted decimal form.
RTT value, the time elapsed in milliseconds before receiving the echo reply response
from the remote host.
The error occurred while processing the +UPING command. See Ping error codes forthe list of the allowed error result codes.

31.1.4 Notes•••

If the +UUPING URC reports <rtt> = -1 the timeout is elapsed (no response received).
If the first +UUPING URC reports <rtt> = -2 the TTL used in the ping request is too low.
Some network operators may return an ICMP time exceeded message when the remote host is notreachable. In these cases the first +UUPING URC reports <rtt> = -1 and the subsequent +UUPING URC
report <rtt> = -2.

SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G1• The first +UUPING URC reporting <rtt> = -2 is not supported. As a consequence a TTL too low hint is notavailable.
LEON-G1• The command uses the TCP/IP resources in an exclusive way. All the other TCP/IP operations executed
after the execution of the +UPING command will wait for the execution of this command.

UBX-13002752 - R67

31 Ping

Page 737 of 1001

u-blox cellular modules - AT commands manual

31.2 ICMP echo reply configuration +UDCONF=4+UDCONF=4
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220 MPCI-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SARA-G4 SARA-G340 SARA-G350
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

31.2.1 Description
Enables/disables the ICMP echo reply (ping response).
Not all the network operators allow the ping traffic on their network.

31.2.2 Syntax
Type
Set

SyntaxResponse
AT+UDCONF=4,<icmp_echo_reply> OK

ExampleAT+UDCONF=4,1

Read

AT+UDCONF=4+UDCONF: 4,<icmp_echo_reply>

OK
AT+UDCONF=4

OK+UDCONF: 4,1
OK

31.2.3 Defined values
Parameter<icmp_echo_reply>Type
NumberDescription
Enables or disables the ping response when a remote host performs a ping request to
the module••

UBX-13002752 - R67

0: ping response disabled (the module does not reply to remote pings)
1 (factory-programmed value): ping response enabled (the module replies to remotepings)

31 Ping

Page 738 of 1001

u-blox cellular modules - AT commands manual

32 Positioning
32.1 NMEA
u-blox cellular modules support reading NMEA strings from the GNSS receiver through AT commands.
Before being able to read a specific NMEA string, it is necessary to activate the storage of the last value of thatparticular NMEA string. If storing a particular NMEA string was not activated, the information text responseto the query will be "0,NULL". The last value of a specific NMEA string is saved in RAM and is made available
even after the GNSS receiver switch off.
The NMEA standard differentiates between GPS, GLONASS, GALILEO, BeiDou and multi-GNSS receivers using
a different 'Talker ID'. Depending upon device model and system configuration, the u-blox receiver could output
messages using any one of these Talker IDs.
By default, the receivers configured to support GPS, SBAS and QZSS use the 'GP' Talker ID, receivers configured
to support GLONASS use the 'GL' Talker ID, receivers configured to support BeiDou use the 'GB' Talker ID,
receivers configured to support GALILEO use the 'GA' Talker ID and receivers configured for any combinationsof multiple GNSS use the 'GN' Talker ID.
Even if the NMEA specification indicates that the GGA message is GPS specific, u-blox receivers support theoutput of a GGA message for each of the Talker IDs.
As a factory-programmed setting, the cellular modules configure the GNSS receiver through AT+UGPS
AT command to not provide the NMEA sentences.
When reading an NMEA message, if the response value is "1,Not available" then the storing of the NMEA
string is activated but this information has not been still sent to the user, if this persist check that therelative NMEA message is enabled. To enable it use the +UGUBX command (for further information see
the UBX-CFG-MSG message in the u-blox GNSS protocol specification).

32.2 AssistNow services
Users would ideally like GNSS receivers to provide accurate position information the moment they are turned
on. With standard GNSS receivers there can be a significant delay in providing the first position fix, principally
because the receiver needs to obtain data from several satellites and the satellites transmit that data slowly.
Under adverse signal conditions, data downloads from the satellites to the receiver can take minutes, hours
or even fail altogether.
GNSS AT commands provides the means for delivering assistance data to u-blox receivers obtained from theu-blox AssistNow Online or AssistNow Offline services.
AssistNow Online is u-blox' end-to-end Assisted GNSS (A-GNSS) solution for use cases that have access to
the Internet. Data supplied by the AssistNow Online service can be directly uploaded to a u-blox receiver tosubstantially reduce Time To First Fix (TTFF), even under poor signal conditions.
AssistNow Offline service is targeted at use cases that only have occasional Internet access and so cannot
use AssistNow Online. AssistNow Offline speeds up Time To First Fix (TTFF), typically to considerably lessthan 10 s. Cellular modules using AssistNow Offline download data from the AssistNow Offline service when an
Internet connection is available. Data are stored locally to the cellular module file system and are subsequently
uploaded to a u-blox receiver, so that it can estimate the positions of the satellites, when no better data isavailable. Using these estimates will not provide as accurate a position fix as if current ephemeris data is used,
but it will allow much faster TTFFs in nearly all cases.
Both the AssistNow Online and Offline services use a simple, stateless, HTTP interface. Therefore, they workon all standard mobile communication networks that support Internet access.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
AssistNow Online service also supports an alternative UDP interface. +UGAOP AT command allow UDP
protocol configuration.
UDP protocol for the AssistNow Online service is deprecated.

UBX-13002752 - R67

32 Positioning

Page 739 of 1001

u-blox cellular modules - AT commands manual

Both the AssistNow Online and Offline services are only available for use by u-blox customers. To use theservices, customers will need to obtain an authorization token from u-blox. This token must be issued as aparameter of +UGSRV AT command.
AssistNow Autonomous feature provides a functionality similar to AssistNow Offline without the need fora host and a connection. Based on a broadcast ephemeris downloaded from the satellite the receiver canautonomously generate an accurate satellite orbit representation («AssistNow Autonomous data») that is
usable for navigation much longer than the underlying broadcast ephemeris was intended for.
Local Aiding feature provides a functionality so that u-blox receivers is instructed to dump the current stateof their internal navigation database to the cellular module file system. This information is sent back to thereceiver (e.g. after a period when the receiver was turned off) restoring the database to its former state, andthus allows the receiver to restart rapidly. Local aiding feature does not need for a access to the Internet.
The +UGPS AT command allows the activation/deactivation of AssistNow Online, Offline, Autonomous andLocal Aiding features.
The AssistNow Offline and AssistNow Autonomous features are exclusive and should not be used at thesame time. Every satellite will be ignored by AssistNow Autonomous if there is AssistNow Offline data
available for it.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
Legacy not concurrent GNSS system receivers (u-blox 7 and older) can still take advantage of u-blox'
end-to-end Assisted GPS (A-GPS) by means of +UGAOP (for AssistNow Online) and +UGAOF (forAssistNow Offline) AT commands. These commands are deprecated.
Table 86 summarizes the GNSS AT commands related with AssistNow services:
AT command AssistNow Online
AssistNow Offline
AssistNow Autonomous Local Aiding+UGPS
Enable/disable the feature Enable/disable the feature Enable/disable the feature Enable/disable the feature+UGAOP
Configure UDP for A-GPS(deprecated)+UGAOF
Configure HTTP for AGPS (deprecated)+UGSRV
Configure HTTP for AConfigure HTTP for AGNSSGNSS+UGAOS

Configure Auth Token for
A-GNSS
Force AssistNow Online
data download request

Configure Auth Token for
A-GNSS
Force AssistNow Offline Force AssistNow
data download request
Autonomous operation

Download/Upload of local
aiding data from/to GNSS
receiver to cellular module

Table 86: AssistNow services Overview

32.3 GNSS
32.3.1 GNSS power management +UGPS+UGPSModules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

32.3.1.1 Description
Switches on or off a u-blox GNSS receiver connected to the cellular module via a dedicated DDC (I2C)
interface. For more details about the connection between cellular module and u-blox GNSS receiver, see thecorresponding module system integration manual.

UBX-13002752 - R67

32 Positioning

Page 740 of 1001

u-blox cellular modules - AT commands manual

Furthermore the command sets the aiding type to be used to enhance GNSS performance, e.g. decreasing
Time To First Fix (TTFF). The supported aiding types are: Local aiding, AssistNow Online, AssistNow Offline,
AssistNow Autonomous.
For a more detailed description on aiding modes and possible suggestions, please see AssistNow services.
LEON-G1
The AssistNow Offline enables AID-ALPSRV UBX message on all the GNSS communication ports.
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / LEON-G1
If using CellLocate® and HTTP commands, the HTTP profiles in the range 1-3 must be used.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
To establish a PSD connection see the +UPSD, +UPSDA and +UPSND AT commands.
SARA-G3 / LEON-G1
To establish a CSD connection see the +UCSD, +UCSDA and +UCSND AT commands.
The AssistNow Autonomous feature may be not fully supported on all Multi-GNSS receivers. For moredetails on AssistNow Autonomous feature see the corresponding u-blox-GNSS receiver description.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
For a more detailed description on aiding modes and possible suggestions, see the GNSS Implementation
application note [171].
It is possible to combine different aiding modes: to enable them the sum of the <mode> value of the interested
aiding modes is needed (e.g.: aiding <aid_mode>=3 means local aiding plus AssistNow Offline). Moreover it isalso possible to switch from one aiding mode to another one without powering off the GNSS receiver. If thefollowing sequence is provided (AT+UGPS=1,1 and then AT+UGPS=1,5) at the beginning the GNSS receiver will
power on with local aiding support and after the second command will be added the AssistNow Online. Afterthe second command the local aiding is not restarted, therefore the +UUGIND URC for it will not be sent again.
u-blox concurrent GNSS receivers can acquire and track satellites from more than one GNSS system atthe same time. The <GNSS_systems> parameter configures the GNSS receiver into the required mode ofoperation. It is possible to combine different GNSS systems depending on the receivers capability to receive
several carrier frequencies. See the corresponding GNSS receiver data sheet for the supported GNSS systems.
If the Assisted GNSS unsolicited indication is enabled, the +UUGIND URC will provide the current activatedcombinations of systems.
32.3.1.2 Syntax
Type
Set

SyntaxAT+UGPS=<mode>[,<aid_mode>[,<GNSS_systems>]]

Response
OK

Read

AT+UGPS?

+UGPS: <mode>[,<aid_mode>[,<GNSS_systems>]]

Test

AT+UGPS=?

ExampleAT+UGPS=1,0,1
OK+UGPS: 1,0,1

OK
OK+UGPS: (list of supported <mode>s), +UGPS: (0-1),(0-15),(1-127)(list of supported <aid_mode>),(listOKof supported <GNSS_systems>)
OK

32.3.1.3 Defined values
Parameter<mode>

Type
Number<aid_mode>

NumberUBX-13002752 - R67

Description• 0 (default value): GNSS receiver powered off• 1: GNSS receiver powered on
Supported aiding modes; the parameter is mandatory if <mode>=1; all these allowed
values can be combined together:• 0 (default value): no aiding• 1: automatic local aiding• 2: AssistNow Offline• 4: AssistNow Online• 8: AssistNow Autonomous

32 Positioning

Page 741 of 1001

u-blox cellular modules - AT commands manual

Parameter<GNSS_systems>

Type
NumberDescription
Bitmask for combining the supported GNSS types; the parameter is optional and theallowed values can be combined together. The default value is 3 (GPS+SBAS):• 1: GPS• 2: SBAS• 4: Galileo• 8: BeiDou• 16: IMES
• 32: QZSS
• 64: GLONASS

32.3.1.4 Notes• If <GNSS_systems> type is not supported by the GNSS receiver, the set command turns on the GNSS
receiver with built-in supported type. The current <GNSS_systems> can be queried by means of the readcommand or the +UUGIND URC.
• An error result code is provided in the following cases:o <mode>, <aid_mode> or <GNSS_systems> values are out of rangeo <mode> is set to 1 without <aid_mode> valueo Attempt to power off the GNSS when it is already off
o The value of <aid_mode> to be set is equal to the current GNSS aiding mode and the value of<GNSS_systems> to be set is equal to the last requested <GNSS_systems>
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
LARA-R211• In case the AUX UART (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and LARA-R211-02B-02)
is enabled (that is the active +USIO variant is 4,5 or 6), since the I2C lines are not available, the command
immediately provides an error result code in case of <mode> set to 1 ("+CME ERROR: 3" if +CMEE: 1 or"+CME ERROR: operation not allowed" if +CMEE: 2).
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• In case the AUX UART is enabled (that is the active +USIO variant is 4,5 or 6), since the I2C lines are notavailable, the command immediately provides an error result code in case of <mode> set to 1 ("+CME
ERROR: 3" if +CMEE: 1 or "+CME ERROR: operation not allowed" if +CMEE: 2).
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G350-00S /SARA-G350-00X / LEON-G1• The parameter <GNSS_systems> is not supported.

32.3.2 Assisted GNSS unsolicited indication +UGIND+UGIND
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

32.3.2.1 Description
Enables or disables sending of URCs from MT to TE in the case of GNSS aiding operations. The <mode>parameter controls the processing of URCs specified within this command.
The URC returns the result of an assisted GNSS operation. This information is sent to all the interfaces. The
URC is provided only if one or more aiding modes are enabled (for more details see the +UGPS and +UGAOP
command descriptions).
There can be more than a +UUGIND URC for a single aiding operation: the +UUGIND is reported for each error.
For instance if the local aiding is enabled and there are no space left in the file system after +UGPS=0, there
will be an error for every failure writing on FFS.

UBX-13002752 - R67

32 Positioning

Page 742 of 1001

u-blox cellular modules - AT commands manual

The commands +UGAOS=0 and +UGAOS=1 both relate to the GNSS local aiding, so the unsolicited message
will be +UUGIND=1,x in both cases.
Local aiding and AssistNow Autonomous will produce URC both after GNSS power on and before GNSS power
off because some data are transferred from the GNSS receiver to the cellular module.
If the connected GNSS receiver is Multi-GNSS then an additional +UUGIND=0,<GNSS_systems> URC for thecurrently activated GNSS systems is displayed.
LEON-G1
The URCs during GNSS power down phase are generated between the power off command (+UGPS=0)
and the actual switch off (OK result code).
32.3.2.2 Syntax
Type
Set

SyntaxAT+UGIND=<mode>

Response
OK

ExampleAT+UGIND=1

Read

AT+UGIND?

+UGIND: <mode>OK+UGIND: 1

Test

AT+UGIND=?

OK+UGIND: (list of supported<mode>'s)

URC

OK+UGIND: (0-1)
OK

OK
Current activated GNSS system:+UUGIND: 0,3+UUGIND: 0,<GNSS_systems>
GNSS aiding status:+UUGIND: 4,5+UUGIND: <aid_mode>,<result>32.3.2.3 Defined values
Parameter<mode>

Type
Number<aid_mode>

Number<GNSS_systems>

Number<result>

NumberUBX-13002752 - R67

Description
URC configuration:• 0 (default value): disabled• 1: enabled
Provides the supported aiding mode:• 0: GNSS system(s)• 1: automatic local aiding• 2: AssistNow Offline• 4: AssistNow Online• 8: AssistNow Autonomous
Current activated GNSS types; the allowed values can be combined together:• 1: GPS• 2: SBAS• 4: Galileo• 8: BeiDou• 16: IMES
• 32: QZSS
• 64: GLONASS
Represents the result of the aiding operation:• 0: No error• 1: Wrong URL (for AssistNow Offline)• 2: HTTP error (for AssistNow Offline)• 3: Create socket error (for AssistNow Online)• 4: Close socket error (for AssistNow Online)• 5: Write to socket error (for AssistNow Online)• 6: Read from socket error (for AssistNow Online)• 7: Connection/DNS error (for AssistNow Online)• 8: File system error• 9: Generic error• 10: No answer from GNSS (for local aiding and AssistNow Autonomous)

32 Positioning

Page 743 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 11: Data collection in progress (for local aiding)• 12: GNSS configuration failed (for AssistNow Autonomous)• 13: RTC calibration failed (for local aiding)• 14: feature not supported (for AssistNow Autonomous)• 15: feature partially supported (for AssistNow Autonomous)• 16: authentication token missing (required for aiding for u-blox M8 and futureversions)

32.3.2.4 Notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1• The command setting is not stored in the NVM.
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.

32.3.3 GNSS profile configuration +UGPRF+UGPRF
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

32.3.3.1 Description
Configures the data flow to and from a u-blox GNSS receiver connected to the cellular module. The data flow
is possible to and from the:• UART (via multiplexer)• USB (or alternatively AUX UART)• Over the air to a remote host: To send data over the air an internet connection must be active and there
must be at least one free TCP socket (the GNSS shares the socket pool with the other applications). Setting
up an Internet connection and network registration is not part of this command and must be handled by
the user separately from this command.
• Into a file on the cellular module: A file with GNSS data can be accessed via +ULSTFILE command. The filename is automatically chosen by the cellular module as a unique ID based on date and time or a further
incremental number (e.g. "GPS_200910061500" or "GPS_20091006_001" according to the used cellular
module). When the files size reaches 500 kB the file is closed and no more data is saved. It is possible tosave further data by restarting the GNSS (this will create a new file)
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
To establish a PSD connection see the +UPSD, +UPSDA and +UPSND AT commands.
SARA-G3 / LEON-G1
To establish a CSD connection see the +UCSD, +UCSDA and +UCSND AT commands.
It is possible to send GNSS data to multiple destinations at the same time by summing the <GNSS_I/O_
configuration> values of each required destinations (e.g. if AT+UGPRF=6 the data will be sent on multiplexerand stored in a file in the file system).
The messages to be output by the u-blox GNSS receiver need to be activated separately with UBX-CFG-MSG
configuration messages according to the GNSS receiver protocol specification.
It is not possible to select the GNSS data flow to and from USB (or alternatively AUX UART) and multiplexer
concurrently.
The configuration of the GNSS profile must be performed only when GNSS is switched off, otherwise anerror result code will be displayed.

UBX-13002752 - R67

32 Positioning

Page 744 of 1001

u-blox cellular modules - AT commands manual

32.3.3.2 Syntax
Type
Set

Read

Test

SyntaxAT+UGPRF=<GNSS_I/O_
configuration>[,<IP Port>,<server
address string>]
AT+UGPRF?

Response
OK

OK+UGPRF: <GNSS_I/O_
configuration>,<IP port>,<server
address string>OK+UGPRF: (list of supported<GNSS_I/O_configuration>),(listof supported <IP port>),<server
address string>

AT+UGPRF=?

ExampleAT+UGPRF=0+UGPRF: 0,0,""OK+UGPRF: (0-127),(0-65535),"addr"
OKOK

32.3.3.3 Defined values
Parameter<GNSS_IO_
configuration>

Type
Number<IP port>

Number<server address
string>StringDescription
•
•
•
•
•
•
•
•
•
•

0: no data flow to multiplexer, file or IP address
1: GNSS data flow to and from USB (or alternatively AUX UART)
2: GNSS data flow to and from multiplexer
4: GNSS data flow saved to file
8: GNSS data flow over the air to an Internet host
16: GNSS data ready function
32: GNSS RTC sharing function
64: reserved
128: reset the GNSS after the GNSS power on (see AT+UGPS command description)
256: use the auxiliary GNSS receiver instead of the default one. If the feature is notprovided then an error result code will be displayed
Allowed values:• LARA-R2 / TOBY-R2 - 0 (factory-programmed value), 1, 2, 4, 8, 16, 64• SARA-U201-03A / SARA-U201-03B / SARA-U201-03X / SARA-U260 / SARA-U270 /SARA-U280 / LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S /LISA-U200-62S / LISA-U200-83S / LISA-U201-03A / LISA-U201-03S /LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G340-00S /SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S / LEON-G1 - 0 (factory-programmed value), 1, 2, 4, 8, 16, 32, 64• SARA-U201-04A / SARA-U201-04B / SARA-U201-04X / SARA-U201-63B /LISA-U200-04B / LISA-U201-04B / SARA-G340-02S / SARA-G340-02X /SARA-G350-02A / SARA-G350-02S / SARA-G350-02X - 0 (factory-programmed
value), 1, 2, 4, 8, 16, 32, 64, 128• SARA-G4 - 0 (factory-programmed value), 1, 2, 4, 8
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S /SARA-G350-02X
On SARA-G340-02S-00, SARA-G340-02X-00, SARA-G350-02S-00, SARA-G350-02X-00, SARA-G350-02A-00, SARA-G350-02A-01 the allowed values are - 0(factory-programmed value), 1, 2, 4, 8, 16, 32, 64.
IP port of the server where the GNSS data are sent (default and factory-programmed
value: 0). If GNSS data flow over the air is enabled the parameter is mandatory
otherwise is forbidden.
Address string of the server where the GNSS data are sent (default and factoryprogrammed value: ""). If GNSS data flow over the air is enabled the parameter ismandatory otherwise is forbidden. The address could be provided in both URL or IP
format and the maximum length of the string is 47 characters.

32.3.3.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.

UBX-13002752 - R67

32 Positioning

Page 745 of 1001

u-blox cellular modules - AT commands manual

LARA-R211• AUX UART interface (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02) cannot be configured as GNSS tunneling. See +USIO command description for
details.
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• AUX UART interface cannot be configured as GNSS tunneling. See +USIO command description for
details.
SARA-G4• The command setting is not stored in the NVM.
• The GNSS data flow on the multiplexer channel is only in output toward the cellular module; the input to
the GNSS receiver is not supported.
• The set GNSS channel (multiplexer or the AUX UART interface) accepts AT commands towards thecellular module.
• The USB interface is not supported.
• Configure the AUX UART interface as GNSS tunnelling interface to support the GNSS data flow over it (inthe active +USIO variant), before the GNSS receiver is switched on (by means of +UGPS AT command).
For more details, see the +USIO command description.
SARA-G340 / SARA-G350• The GNSS data flow on the multiplexer channel is only in output toward the cellular module; the input to
the GNSS receiver is not supported.
• The USB interface is not supported.
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S / SARA-G350-02X• Configure the AUX UART interface as GNSS tunnelling interface to support the GNSS data flow overit (in the active +USIO variant), before the GNSS receiver is switched on (by means of +UGPS AT
command). For more details, see the +USIO command description.
LEON-G1• The server address string parameter accepts only IP address in dotted notation, thus it has a maximum
length of 15 characters.
• A delay time of at least 3 s after the power on is required before issuing this command.
• The USB interface is not supported.
• UBX-AID messages are not passed over the multiplexer if AssistNow Online, AssistNow Offline or Local
Aiding is enabled (see AT+UGPS command description).

32.3.4 Aiding server configuration +UGSRV+UGSRV
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G450-01C SARA-G340-01S SARA-G340-02S SARA-G340-02X SARA-G350-01B SARA-G350-01S
SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
NVM
No+CME Error

32.3.4.1 Description
Configures the network connection to a Multi GNSS Assistance (MGA) server. The configuration is saved in
NVM and applied at the next GNSS power cycle. By default, the cellular module connects to u-blox' primary
MGA server; if the connection fails then the cellular module connects to u-blox' secondary MGA server. The set
command registers a token for gathering assistance data from MGA servers.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
Once a token is set it cannot be cleared so that registered hostnames in +UGAOP and +UGAOF commands
are discarded.
Setting up Internet connection and network registration is not part of this command and must be handled
by the user separately to this command.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3

UBX-13002752 - R67

32 Positioning

Page 746 of 1001

u-blox cellular modules - AT commands manual

See +UPSD, +UPSDA and +UPSND AT commands for establishing a PSD connection.
SARA-G3
See +UCSD, +UCSDA and +UCSND AT commands for establishing a CSD connection.
For more details about Multi GNSS Assistance (MGA) feature please refer to AssistNow services.
32.3.4.2 Syntax
Type
Set

SyntaxResponse
AT+UGSRV=[<mga_primary_OK
server>],[<mga_secondary_server>],<auth_token>[,<days>[,<period>[,<resolution>[,<GNSS_types>[,<mode>[,<datatype>]]]]]]Read

AT+UGSRV?

Test

AT+UGSRV=?

+UGSRV: <mga_primary_server>,<mga_secondary_server>,<auth_token>,<days>,<period>,<resolution>,<GNSS_types>,<mode>,<datatype>OK+UGSRV: <mga_primary_server>,<mga_secondary_server>,<auth_token>,(list of supported <days>s),(list of supported <period>s),(listof supported <resolution>s),(listof supported <GNSS_types>s),(list of supported <mode>s),(list of
supported <datatype>s)

ExampleAT+UGSRV="celllive1.services.u-blox.com","celllive2.services.u-blox.com","123456789abcdefghijklm",14,4,1,65,
0,1OK+UGSRV: "cell-live1.services.ublox.com","celllive2.services.u-blox.com","123456789abcdefghijklm",14,4,1,65,
0,1OK+UGSRV: "srv1","srv2","token",(1,2,3,
5,7,10,14),(1-5),(1-3),(1,64,65),(0-2),(0
-15)
OK

OK

32.3.4.3 Defined values
Parameter<mga_primary_server>Type
String<mga_secondary_
server>String<auth_token><days>

StringNumber<period>

Number<resolution>

Number<GNSS_types>

Number<mode>

NumberUBX-13002752 - R67

Description
Host name of the primary MGA server; the maximum length is 254 characters.
Empty string is not allowed. The default and factory-programmed value is "celllive1.services.u-blox.com". If the primary MGA server is omitted, the current stored
value is preserved.
Host name of the secondary MGA server; the maximum length is 254 characters.
Empty string is not allowed. The default and factory-programmed value is "celllive2.services.u-blox.com". If the secondary MGA server is omitted, the current stored
value is preserved.
Authentication Token for MGA server access.
The number of days into the future the Offline data for u-blox 7 and previous version
should be valid for. The allowed values are: 1, 2, 3, 5, 7, 10 and 14. The default andfactory-programmed value is 14.
The number of weeks into the future the Offline data for u-blox M8 should be validfor. The range of the allowed values goes from 1 to 5. The default and factoryprogrammed value is 4.
Resolution of offline data for u-blox M8. Allowed values:• 1 (default and factory-programmed value): every day• 2: every other day• 3: every third day
Bitmask for combining the desired GNSS for the (offline) aiding• 1: GPS• 64: GLONASS
The default and factory-programmed value is all (65). If the parameter is omitted, thecurrent stored value is preserved.
Mode of operation of AssistNow Online data management• 0 (default and factory-programmed value): AssistNow Online data are downloaded
at GNSS receiver power up• 1: AssistNow Online data automatically kept alive

32 Positioning

Page 747 of 1001

u-blox cellular modules - AT commands manual

ParameterType<datatype>

NumberDescription• 2: manual AssistNow Online data download
Bitmask for combining the desired data types for the (online) aiding• 0: time• 1: position• 2: ephemeris• 4: almanac• 8: auxiliary• 16: ephemeris of satellites which are likely to be visible from the position estimatedby current registered network. This flag has no effect if the ephemeris flag is set
to 0.
The default and factory-programmed value is all aidings without filter on visible
satellites (15)32.3.4.4 Notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200-03S / LISA-U200-83S / LISA-U201-03A / LISA-U201-03S /LISA-U201-83S / SARA-G3• <datatype>=16 is not supported.
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / SARA-G340-01S /SARA-G340-02S / SARA-G340-02X / SARA-G350-01B / SARA-G350-01S / SARA-G350-02A /SARA-G350-02S / SARA-G350-02X• The <mga_primary_server> parameter is mandatory.
SARA-G4• The <mga_primary_server> parameter is mandatory.
• The <mga_primary_server> factory-programmed value is "lscellapi.services.u-blox.com", and it is the only
supported MGA server.
• <datatype>=16 is not supported. The filtering on visible satellites is always done by default.

32.3.5 AssistNow Online configuration +UGAOP+UGAOP
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

32.3.5.1 Description
Configures the network connection to an AssistNow Online server. Use of this command is only necessary ifchanges to the factory-programmed configuration are required.
As GNSS shares the socket pool with the other applications, to execute AssistNow Online the cellular module
will try to open a new socket without dropping any opened socket, if there is no socket available then the GNSS
will start and no aiding operation is performed. By default, the cellular module connects to the u-blox' AssistNow
Online server. The access to a proxy server is possible.
Setting up Internet connection and network registration is not part of this command and must be handled
by the user separately to this command.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
To establish a PSD connection see the +UPSD, +UPSDA and +UPSND AT commands.
SARA-G3 / LEON-G1
To establish a CSD connection see the +UCSD, +UCSDA and +UCSND AT commands.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
Where supported, it is preferred to use the +UGSRV AT command.

UBX-13002752 - R67

32 Positioning

Page 748 of 1001

u-blox cellular modules - AT commands manual

For more details about AssistNow Online feature please refer to AssistNow services.
32.3.5.2 Syntax
Type
Set

SyntaxAT+UGAOP=<hostname>,<server_
port>,<latency>,<mode>

Response
OK

ExampleAT+UGAOP="eval1-les.services.ublox.com",46434,1000,0

Read

AT+UGAOP?

+UGAOP: <hostname>,<server_
port>,<latency>,<mode>OK+UGAOP: "eval1-les.services.ublox.com",46434,1000,0OKOK

32.3.5.3 Defined values
Parameter<hostname>

Type
String<server_port><latency>

NumberNumber<mode>

NumberDescription
Host name of the server (factory-programmed value: eval1-les.services.u-blox.com);the maximum length is 47 characters
Value in the range 0 - 65535. (factory-programmed value: 46434)
Expected network latency value from AssistNow Online server to client, inmilliseconds. The range goes from 0 to 3600 ms. (factory-programmed value: 1000ms)
Mode of operation of AssistNow Online data management• 0 (factory-programmed value): AssistNow Online data are downloaded at GNSS
receiver power up• 1: AssistNow Online data automatically kept alive• 2: manual AssistNow Online data download

32.3.5.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
LEON-G1• A delay time of at least 3 s after the power on is required before issuing this command.

32.3.6 AssistNow Offline configuration +UGAOF+UGAOF
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

32.3.6.1 Description
Configures the network connection to an AssistNow Offline server. Use of this command is only necessary ifchanges to the factory-programmed configuration are required.
As GNSS shares the socket pool with the other applications, to execute AssistNow Offline the cellular module
will try to open a new socket without dropping any opened socket, if there is no socket available then the GNSS
will start and no aiding operation is performed. By default, the cellular module connects to the 14 day file on
the u-blox' AssistNow Offline server.
Setting up Internet connection and network registration is not part of this command and must be handled
by the user separately from this command.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G3
Where supported, it is preferred to use the +UGSRV AT command.
For more details about AssistNow Offline feature please refer to AssistNow services.

UBX-13002752 - R67

32 Positioning

Page 749 of 1001

u-blox cellular modules - AT commands manual

32.3.6.2 Syntax
Type
Set

SyntaxAT+UGAOF=<file_url>,<reserved>,<retry timeout>,<max_retry_attempts>

Response
OK

ExampleAT+UGAOF="http://alp.u-blox.com/
current_14d.alp",0,1,3

Read

AT+UGAOF?

+UGAOF: <file_url>,0,<retry
timeout>,<max_retry_attempts>

OK+UGAOF: "http://alp.u-blox.com/
current_14d.alp",0,1,3

OKOK

32.3.6.3 Defined values
Parameter<file_url>

TypeString<Reserved><Retry Timeout>

Number<max_retry_attempts>

NumberDescription
URL of AssistNow Offline file (the maximum length is 255 characters including"http://"). Allows choosing the size/validity of the file. The factory-programmed value
is http://alp.u-blox.com/current_14d.alp
RFU
Timeout in minutes after a failed download for the next download attempt (0 ... 999)
(factory-programmed value: 1)
Maximum number of attempts in case of failed download (0-5); the factoryprogrammed value is 3.

32.3.6.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
LEON-G1• A delay time of at least 3 s after the power on is required before issuing this command.

32.3.7 GNSS aiding request command +UGAOS+UGAOS
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

Attributes

32.3.7.1 Description
Triggers the manual download of AssistNow Online and AssistNow Offline data from the configured server incase automatic AssistNow operation is not enabled. The command returns only when the received data fromthe server are valid or an error occurs.
The command is also used to trigger the manual upload of local aiding data (e.g. ephemeris, almanac, last
position, time, etc) from a u-blox GNSS receiver prior to shutting it down and to restore it into the receiver after
the power up of the GNSS receiver (for more details refer to command +UGPS, Chapter 32.3.1).
32.3.7.2 Syntax
Type
Set

SyntaxAT+UGAOS=<aid_mode>

Test

AT+UGAOS=?

Response
OK

ExampleAT+UGAOS=0OK
AT+UGAOS: (list of supported <aid_ +UGAOS: (0-8)
mode>s)OKOK

32.3.7.3 Defined values
Parameter<aid_mode>

UBX-13002752 - R67

Type
NumberDescription••

0: Upload of local aiding data from GNSS receiver to cellular module
1: Download of local aiding data from the cellular module to the GNSS receiver

32 Positioning

Page 750 of 1001

u-blox cellular modules - AT commands manual

Parameter

Type

Description• 2: AssistNow Offline file download request (file loaded into cellular module)• 4: AssistNow Online data download request (data loaded into the GNSS receiver).
This is only needed if AssistNow Online is not used with automatic operation• 8: AssistNow autonomous• Other values are reserved for future use

32.3.7.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.

32.3.8 Send of UBX string +UGUBX+UGUBX
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

Attributes

32.3.8.1 Description
Sends UBX protocol messages, embedded in an AT command, to a u-blox GNSS receiver. The command istransparent, that is the data is sent to the GNSS receiver without any check: it is up to the user to control if
the UBX data is valid. The checksum in +UGUBX command string is ignored, this is calculated when the data
is sent to the GNSS receiver.
When the GNSS receiver is off the UBX string is saved in cellular module RAM and, later, passed to the GNSS
as configuration for "GNSS data ready" function when the GNSS receiver is used. This message is used only if
the GNSS receiver HW is unknown (newer than the cellular module FW). In this case the UBX checksum bytes
must be filled correctly.
It is recommended to not send UBX messages to reset the GNSS receiver while it is in use, this willcause a misalignment between the configuration of the cellular module and the one of the GNSS receiver.
Furthermore it is recommended to not configure the GNSS power saving with the "GNSS data ready"active, because the GNSS receiver could send wrong reading requests to the cellular module.
UBX messages of "input" type do not provide back information messages to the cellular module. In thiscase the information text response to set command is +UGUBX: "no message" followed by the final resultcode.
32.3.8.2 Syntax
Type
Set

SyntaxAT+UGUBX=<UBX_string>Response+UGUBX: <UBX_string_response>
OK

ExampleAT+UGUBX="B56206010800010600
010000000017DA"+UGUBX: "B5620501020006010F38"
OK

32.3.8.3 Defined values
Parameter<UBX_string>Type
String<UBX_string_
response>

StringUBX-13002752 - R67

Description
UBX message in hexadecimal format. The messages can include spaces to simplify
copy/paste from u-center separated with spaces, e.g. AT+UGUBX="B5 62 06 01 08 0
0 01 06 00 01 00 00 00 00 17 DA" (this is important when copying messages from ucenter).
• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- For the limit of the length of the string, see Command line.
The response message depends by the request sent: query/poll UBX messages will
return the requested data in hexadecimal format, while the configuration message
will return the corresponding acknowledge or not-acknowledge. See the UBX protocol
specification

32 Positioning

Page 751 of 1001

u-blox cellular modules - AT commands manual

32.3.8.4 Notes••

If a +UGUBX command triggers multiple strings answer only a single UBX string is returned. E. g. polling
GPS Aiding Ephemeris Data (AID-EPH) is done by sending a single message to the receiver but returns
32 messages; only the first one is sent to AT interface.
The answer can be split in multiple information text responses all starting with "+UGUBX:".

LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S /LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1• The command can only be used when the GNSS is used from the AT interface (power on by AT+UGPS=1,x).
LISA-U200-01S / LISA-U230 / LISA-U260-01S / LISA-U270-01S• During hybrid positioning the command is used to configure "GNSS data ready" function.
LEON-G1• The command can only be used when the GNSS is used from the AT interface (power on by AT+UGPS=1,x).

32.3.9 GNSS indications timer +UGTMR+UGTMR
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

Attributes

32.3.9.1 Description
Sets the date and time format. With the <time_zone> parameter is possible to set the time zone value; thetime and the date will be updated as the local time. With the action command is possible to synchronize the
UTC timing.
32.3.9.2 Syntax
Type
Set

SyntaxAT+UGTMR=<time_zone>

Response
OK

ExampleAT+UGTMR=-1

Read

AT+UGTMR?

+UGTMR: <time_zone>OK+UGTMR: -1

Test

AT+UGTMR=?

OK+UGTMR: (list of supported <time_zone>s)OK+UGTMR: (-96 - 96)
OKOK

32.3.9.3 Defined values
Parameter<time_zone>

Type
NumberDescription
Indicates the time zone value set by the user; the module can provide an error result
code if the offset has not been calculated. The factory-programmed time zone valueis 0.
• -96, 96: defined range

32.3.9.4 Notes• The time zone is expressed in quarters of hour.
• The time is updated with the current UTC time plus the time zone and the time zone is unchanged, forexample:Command
AT+UGTMR=-36

UBX-13002752 - R67

Response
OK

Remarks
The command returns the "OK" final result
code and sets the new date and time if the

32 Positioning

Page 752 of 1001

u-blox cellular modules - AT commands manual

Command

Response

Remarks
GNSS has this information, otherwise a genericerror result code is returned.

AT+CCLK?

+CCLK: "12/05/23,21:54:21+00"

LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The <time_zone> parameter range goes from -48 to 48.
LEON-G1• The command returns the "OK" final result code in case the GNSS has no time information, but in thiscase the date and time are not updated.
• The <time_zone> parameter range goes from -48 to 48.

32.3.10 Get GNSS time and date +UGZDA+UGZDA
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 10 s+CME Error

Attributes

32.3.10.1 Description
Enables/disables the storing of the last value of NMEA $ZDA messages, and get the current messaging state.
If the <state> parameter is enabled, the last value of NMEA $ZDA messages can be retrieved with the readcommand even when the GNSS is switched off.
The NMEA $ZDA messages are volatile.
32.3.10.2 Syntax
Type
Set

SyntaxAT+UGZDA=<state>

Response
OK

ExampleAT+UGZDA=1Read

AT+UGZDA?

+UGZDA: <state>,<$ZDA msg>

OK
+UGZDA: 1,$GPZDA,142351.00,12,12,
2013,00,00*66

OK

OK+UGZDA: 0,NULL
Test

AT+UGZDA=?

+UGZDA: (list of supported<state>s)OK+UGZDA: (0-1)
OKOK

32.3.10.3 Defined values
Parameter<state>Type
Number<$ZDA msg>

StringDescription• 0 (factory-programmed value): disable the NMEA $ZDA messages• 1: enable the NMEA $ZDA messages
NMEA $ZDA messages or "Not available" if the NMEA string is enabled, but thisinformation has not been still sent to the user.

32.3.10.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The command setting is not stored in the NVM.

UBX-13002752 - R67

32 Positioning

Page 753 of 1001

u-blox cellular modules - AT commands manual

32.3.11 Get GNSS fix data +UGGGA+UGGGA
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 10 s+CME Error

Attributes

32.3.11.1 Description
Enables/disables the storing of the last value of NMEA $GGA messages, and gets the current messaging state.
If the <state> parameter is enabled, the last value of NMEA $GGA messages can be retrieved with the readcommand even when the GNSS is switched off.
The NMEA $GGA messages are volatile.
32.3.11.2 Syntax
Type
Set

SyntaxAT+UGGGA=<state>

Response
OK

ExampleAT+UGGGA=1

Read

AT+UGGGA?

+UGGGA: <state>,<$GGA msg>

OK
+UGGGA: 1,$GPGGA,142351.00,,,,,0,0
0,99.99,,,,,,*66

OK

OK+UGGGA: 0,NULL
Test

AT+UGGGA=?

+UGGGA: (list of supported<state>s)OK+UGGGA: (0-1)
OKOK

32.3.11.3 Defined values
Parameter<state>Type
Number<$GGA msg>

StringDescription• 0 (factory-programmed value): to disable the NMEA $GGA messages• 1: to enable the NMEA $GGA messages
NMEA $GGA messages or "Not available" if the NMEA string is enabled, but thisinformation has not been still sent to the user.

32.3.11.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The command setting is not stored in the NVM.

32.3.12 Get geographic position +UGGLL+UGGLL
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 10 s+CME Error

32.3.12.1 Description
Enables/disables the storing of the last value of NMEA $GLL messages, and gets the current messaging state.
If the <state> parameter is enabled, the last value of NMEA $GLL messages can be retrieved with the readcommand even when the GNSS is switched off.

UBX-13002752 - R67

32 Positioning

Page 754 of 1001

u-blox cellular modules - AT commands manual

The NMEA $GLL messages are volatile.
32.3.12.2 Syntax
Type
Set

SyntaxAT+UGGLL=<state>

Response
OK

ExampleAT+UGGLL=1

Read

AT+UGGLL?

+UGGLL: <state>,<$GLL msg>

OK
+UGGLL: 1,$GPGLL,,,,,142351.00,V,
N*4A

OK

OK
+UGGLL: 0,NULL
Test

AT+UGGLL=?

+UGGLL: (list of supported<state>s)OK+UGGLL: (0-1)
OKOK

32.3.12.3 Defined values
Parameter<state>Type
Number<$GLL msg>

StringDescription• 0 (factory-programmed value): to disable the NMEA $GLL messages• 1: to enable the NMEA $GLL messages
NMEA $GLL messages or "Not available" if the NMEA string is enabled, but thisinformation has not been still sent to the user.

32.3.12.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The command setting is not stored in the NVM.

32.3.13 Get number of GNSS satellites in view +UGGSV+UGGSV
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 10 s+CME Error

32.3.13.1 Description
Enable/disables the storing of the last value of NMEA $GSV messages, and gets the current messaging state.
If the <state> parameter is enabled, the last value of NMEA $GSV messages can be retrieved with the readcommand even when the GNSS is switched off.
The NMEA $GSV messages are volatile.
32.3.13.2 Syntax
Type
Set

SyntaxAT+UGGSV=<state>

Response
OK

ExampleAT+UGGSV=1

Read

AT+UGGSV?

+UGGSV: <state>,<$GSV msg>

OK
+UGGSV: 1,$GPGSV,3,1,11,03,67,298,
22,06,88,149,29,07,06,302,,08,05,
332,25*73

OK$GPGSV,3,2,11,09,02,334,25,14,02,
141,,15,10,041,43,16,46,209,16*7D$GPGSV,3,3,11,18,48,066,35,21,26,0
70,35,27,80,314,25*40

UBX-13002752 - R67

32 Positioning

Page 755 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Example$GLGSV,1,1,03,73,13,248,,74,23,298,
20,75,09,348,19*51
OK+UGGSV: 0,NULL

Test

AT+UGGSV=?

+UGGSV: (list of supported<state>s)OK+UGGSV: (0-1)
OKOK

32.3.13.3 Defined values
Parameter<state>Type
Number<$GSV msg>

StringDescription• 0 (factory-programmed value): to disable the NMEA $GSV messages• 1: to enable the NMEA $GSV messages
NMEA $GSV messages or "Not available" if the NMEA string is enabled, but thisinformation has not been still sent to the user.

32.3.13.4 Notes• Since the $GSV message reports satellite information, the output of the different GNSS systems is not
combined, but it is reported in sequence as in the example above with GPS and GLONASS.
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The command setting is not stored in the NVM.

32.3.14 Get recommended minimum GNSS data +UGRMC+UGRMC
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 10 s+CME Error

32.3.14.1 Description
Enable/disables the storing of the last value of NMEA $RMC messages, and gets the current messaging state.
If the <state> parameter is enabled, the last value of NMEA $RMC messages can be retrieved with the readcommand even when the GNSS is switched off.
The NMEA $RMC messages are volatile.
32.3.14.2 Syntax
Type
Set

SyntaxAT+UGRMC=<state>

Response
OK

ExampleAT+UGRMC=1

Read

AT+UGRMC?

+UGRMC: <state>,<$RMC msg>

OK
+UGRMC: 1,$GPRMC,142351.00,V,,,,,,,121213,,,N*7F

OK

OK+UGRMC: 0,NULL
Test

AT+UGRMC=?

+UGRMC: (list of supported<state>s)OK+UGRMC: (0-1)
OK

OK

UBX-13002752 - R67

32 Positioning

Page 756 of 1001

u-blox cellular modules - AT commands manual

32.3.14.3 Defined values
Parameter<state>Type
Number<$RMC msg>

StringDescription• 0 (factory-programmed value): to disable the NMEA $RMC messages• 1: to enable the NMEA $RMC messages
NMEA $RMC messages or "Not available" if the NMEA string is enabled, but thisinformation has not been still sent to the user.

32.3.14.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The command setting is not stored in the NVM.

32.3.15 Get course over ground and ground speed +UGVTG+UGVTG
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 10 s+CME Error

Attributes

32.3.15.1 Description
Enables/disables the storing of the last value of NMEA $VTG messages, and gets know the current messaging
state. If the <state> parameter is enabled, the last value of NMEA $VTG messages can be retrieved with theread command even when the GNSS is switched off.
The NMEA $VTG messages are volatile.
32.3.15.2 Syntax
Type
Set

SyntaxAT+UGVTG=<state>

Response
OK

ExampleAT+UGVTG=1Read

AT+UGVTG?

+UGVTG: <state>,<$VTG msg>

OK
+UGVTG: 1,$GPVTG,,,,,,,,,N*30

OK

OK+UGVTG: 0,NULL

Test

AT+UGVTG=?

+UGVTG: (list of supported<state>s)

OK+UGVTG: (0-1)
OKOK

32.3.15.3 Defined values
Parameter<state>Type
Number<$VTG msg>

StringDescription• 0 (factory-programmed value): to disable the NMEA $VTG messages• 1: to enable the NMEA $VTG messages
NMEA $VTG messages or "Not available" if the NMEA string is enabled, but thisinformation has not been still sent to the user.

32.3.15.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The command setting is not stored in the NVM.

UBX-13002752 - R67

32 Positioning

Page 757 of 1001

u-blox cellular modules - AT commands manual

32.3.16 Get satellite information +UGGSA+UGGSA
Modules

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 10 s+CME Error

Attributes

32.3.16.1 Description
Enables/disables the storing of the last value of NMEA $GSA messages, and gets the current messaging
state. If <state> parameter is enabled, the last value of NMEA $GSA messages can be retrieved with the readcommand even when the GNSS is switched off.
The NMEA $GSA messages are volatile.
32.3.16.2 Syntax
Type
Set

SyntaxAT+UGGSA=<state>

Response
OK

ExampleAT+UGGSA=1Read

AT+UGGSA?

+UGGSA: <state>,<$GSA msg>

OK
+UGGSA: 1,$GPGSA,A,1,,,,,,,,,,,,,99.99,
99.99,99.99*30

OK

OK+UGGSA: 0,NULL
Test

AT+UGGSA=?

+UGGSA: (list of supported<state>s)OK+UGGSA: (0-1)
OKOK

32.3.16.3 Defined values
Parameter<state>Type
Number<$GSA msg>

StringDescription• 0 (factory-programmed value): to disable the NMEA $GSA messages• 1: to enable the NMEA $GSA messages
NMEA $GSA messages or "Not available" if the NMEA string is enabled, but thisinformation has not been still sent to the user.

32.3.16.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-G4• The command setting is not stored in the NVM.

32.4 CellLocate and hybrid positioning
32.4.1 Ask for localization information +ULOC+ULOC
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 10 s+CME Error

32.4.1.1 Description
Requests cellular module to provide the location data; the location can be determined using:

UBX-13002752 - R67

32 Positioning

Page 758 of 1001

u-blox cellular modules - AT commands manual•••

GNSS receiver
CellLocate® (location based on network cells data)
Combination of both technologies (hybrid)

The final result code indicates if sending the command request to the localization information process was
successful or not. The URC is issued to provide the requested information via +ULOC set command.
The GNSS interface and CellLocate® can be used at the same time: if the GNSS sensor is reserved to anotherinterface an error result code is provided ("+CME ERROR: GPS busy" if +CMEE: 2).
It is possible to configure the hybrid positioning through +ULOCGNSS and +ULOCCELL AT commands even if
it is running: the parameters are stored in NVM and will be applied at the next +ULOC command.
If the +ULOC command is sent while a previous +ULOC activity is still in progress the previous activity isaborted, the available position is immediately output and the next +ULOC request is served.
The data connection cannot be immediately dropped at the +ULOC timeout expiration. This could lead toa delay in the expected response time.
Depending on the aiding chosen, a data connection could be required; see the AT+UGPS commanddescription.
If no position is available (no GNSS coverage, no network information and no previous data available) thenthe <lat> latitude and <long> longitude will be set to '0'.
If the previous position degradated by the elapsed time satisfies the desired accuracy then the sensor '0'
is reported in the information text response.
If multi-hypothesis is required the GNSS solution and the CellLocate® solutions are reported, if available.
If no GNSS or CellLocate® solutions are present, the previous position degradated is used instead.
If a valid GNSS fix with an accuracy below the required value (<accuracy>) occurs before the end of the
network scan, the GNSS-only solution will be available, even if multi-hypothesis has been required.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
The location by means of CellLocate® requires an active data context: for more details about the activationof a PSD context, see +UPSD, +UPSDA and +UPSND AT commands.
SARA-G3 / LEON-G1
The location by means of CellLocate® requires an active data context: for more details about the activationof a CSD context, see +UCSD, +UCSDA and +UCSND AT commands.
32.4.1.2 Syntax
Type
Set

Read

Test

SyntaxAT+ULOC=<mode>,<sensor>,<response_type>,<timeout>,<accuracy>[,<num_hypothesis>]
AT+ULOC?

AT+ULOC=?

URC

Response
OK

OK+ULOC: <mode>,<sensor>,<response_type>,<timeout>,<accuracy>,<num_hypotesis>+ULOC: 2,3,1,0,20,0
OK

OK+ULOC: (list of supported <mode>s), +ULOC: (0-2),(0-3),(0-2),(1-999),(1(list of supported <sensor>s),(list999999),(1-16)
of supported <response_type>s),OK(list of supported <timeout>s),(listof supported <accuracy>s),(list of
supported <num_hypotesis>s)OK
If <response_type>=0:+UULOC: <date>,<time>,<lat>,<long>,<alt>,<uncertainty>
If <response_type>=1:+UULOC: <date>,<time>,<lat>,<long>,<alt>,<uncertainty>,<speed>,<direction>,<vertical_acc>,<sensor_used>,<SV_used>,

UBX-13002752 - R67

ExampleAT+ULOC=2,3,0,120,1

32 Positioning+UULOC: 13/04/2011,09:54:51.000,
45.6334520,13.0618620,49,1+UULOC: 25/09/2013,10:13:29.000,
45.7140971,13.7409172,266,17,0,0,18,
1,6,3,9Page 759 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
Example<antenna_status>,<jamming_
status>If <response_type>=2, <sensor_+UULOC: 1,2,1,08/04/2015,09:0
used>= 1 and <num_hypothesis>=N: 2:32.000,45.7141652,13.7410666,
266,47,0,0,40,3,0,0+UULOC: <sol>,<num>,<sensor_
used>,<date>,<time>,<lat>,<long>,<alt>,<uncertainty>,<speed>,<direction>,<vertical_acc>,<SV_used>,<antenna_status>,<jamming_status>
If <response_type>=2, <sensor_+UULOC: 2,2,2,08/04/2015,09:0
used> = 2 and <num_hypothesis>= 2:19.000,45.7140665,13.7411681,0,N:
45.7240260,13.7511276,113,10,0,50,45.7240260,13.7511276,143,41,0,95+UULOC: <sol>,<num>,<sensor_
used>,<date>,<time>,<lat>,<long>,<alt>,<lat50>,<long50>,<major50>,<minor50>,<orientation50>,<confidence50>[,<lat95>,<long95>,<major95>,<minor95>,<orientation95>,<confidence95>]
If <response_type>=2, <sensor_+UULOC: 1,1,0,08/04/2015,09:0
used>= 0:
3:45.000,45.7140290,13.7410695,0,32+UULOC: <sol>,<num>,<sensor_
used>,<date>,<time>,<lat>,<long>,<alt>,<uncertainty>

32.4.1.3 Defined values
Parameter<mode>

Type
Number<sensor>Number<response_type>

Number<timeout><accuracy><num_hypothesis>

NumberNumberNumber<date><time><lat><long><alt><uncertainty><speed><direction><vertical_acc><sensor_used>

StringStringStringStringNumberNumberNumberNumberNumberNumber8
9Description• 0: reserved• 1: reserved• 2: single shot position
Sensor selection: it is possible to combine different sensors summing <sensor>
values of the selected sensors:• 0: use the last fix in the internal database and stop the GNSS receiver• 1: use the GNSS receiver for localization• 2: use cellular CellLocate® location information
Type of response:• 0: standard (single-hypothesis) response• 1: detailed (single-hypothesis) response• 2: multi-hypotheses response
Timeout period in seconds (1 - 999)
Target accuracy in meters (1 - 999999)
Maximum desired number of responses from CellLocate® (up to 16): multiple
positions followed by their ellipsoidal uncertainties. This value has to be increasedby 1 (GNSS solution) to get the maximum number of possible solutions. This optionalparameter can be used only if <response_type>=2. The default value is 1.
GPS date8 (DD/MM/YY) of the estimated position
GPS time8 (hh:mm:ss.sss) of the estimated position
Estimated latitude, in degrees
Estimated longitude, in degrees
Estimated altitude, in meters9
Estimated 50% confidence level error, in meters (0 - 20000000)
Speed over ground m/s9
Course over ground in degree (0 deg - 360 deg)(9)Vertical accuracy, in meters9
Sensor used for the position calculation

Coming either from the CellLocate® server or the GNSS receiver (GPS time)
only for GNSS positioning, 0 in case of CellLocate®

UBX-13002752 - R67

32 Positioning

Page 760 of 1001

u-blox cellular modules - AT commands manual

Parameter<SV_used>
<sol>
<num>
<lat50>/<lat95><long50>/<long95><major50>/<major95><minor50>/<minor95><orientation50>/<orientation95><confidence50>/<confidence95><antenna_status>

Type
NumberNumberNumberStringStringNumberDescription
Number of satellite used to calculate the position9
Solution index (between 1 and <num>)
Total number of the available hypotheses (less than or equal to <num_hypothesis>)
Estimated latitude (50/95% confidence levels), in degrees
Estimated longitude (50/95% confidence levels), in degrees
Semi-major axis of the ellipse (50/95% confidence levels), in meters

NumberSemi-minor axis of the ellipse (50/95% confidence levels), in meters

NumberOrientation of the ellipse (50/95% confidence levels), in degrees

Number50/95% confidence levels, in percentage

Number<jamming_status>

NumberAntenna status (0 - 4)(9). For more details see the u-blox GNSS receiver protocol
specification
Jamming status9. For more details see the u-blox GNSS receiver protocol
specification

32.4.1.4 Notes
•

•
•
•

If AssistNow Online aiding data has been configured by means of the <aiding> parameter of +ULOCGNSS
AT command, the +ULOC request using <sensor>=1 (GNSS receiver only) can provide a +UULOC URC
reporting a CellLocate solution (<sensor_used>=2). This can happen if:
o a GNSS fix is not available.
o the CellLocate solution is more accurate (i.e. CellLocate solution's uncertainty is better than the
GNSS's one).
If <sensor>=1 (use the GNSS receiver for localization), <response_type>>=2 (multi-hypotheses response)is not supported.
The <jamming_status> value must be ignored if the jamming is disabled through +ULOCGNSS command.
The <date>, <time>, <lat>, <long> values are not enclosed in double quotes in the URC.

LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-U260-00S / SARA-U270-00S / SARA-U270-00X / SARA-U280-00S / LISA-U200-00S /LISA-U200-01S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U230 / LISA-U260 /LISA-U270 / LISA-U1 / SARA-G3• The <num_hypothesis> parameter is not supported.
SARA-G4• The <num_hypothesis> parameter is not supported.
• <response_type>=2 and 255 are not supported.
LEON-G1• The GNSS receiver is not stopped if the <sensor> is set to 0.
• The GNSS interface and CellLocate® are mutually exclusive; if a +ULOC request is sent when the GNSS
is already started with +UGPS the command will return an error result code ("+CME ERROR: Invalid
operation with GPS ON" if +CMEE is set to 2) and vice versa ("+CME ERROR: Invalid operation with LOC
running" if +CMEE is set to 2). When the +ULOC command has been triggered also +UGAOP, +UGAOF,+UGAOS, +UGUBX AT commands will report an error result code, but it is possible to query NMEA strings.
• An error result code will be provided if the hybrid configuration is performed when the hybrid positioning
is running.
• The cellular module date and time is not used in the answer, so if no sensor is available these fields arefilled with '0'.
• The <num_hypothesis> parameter is not supported.

UBX-13002752 - R67

32 Positioning

Page 761 of 1001

u-blox cellular modules - AT commands manual

32.4.2 Localization information request status unsolicited indication+ULOCIND+ULOCIND
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G450-01C SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

32.4.2.1 Description
Configures sending of URCs from MT to TE in the case of +ULOC operations. The URC provides the result of
the steps of an +ULOC operation.
32.4.2.2 Syntax
Type
Set

SyntaxAT+ULOCIND=<mode>

Response
OK

ExampleAT+ULOCIND=1Read

AT+ULOCIND?

+ULOCIND: <mode>

OK+ULOCIND: 1

Test

AT+ULOCIND=?

OK+ULOCIND: (list of supported<mode>'s)

URC

OK+ULOCIND: (0-1)
OK

OK+UULOCIND: <step>,<result>+UULOCIND: 1,0OKOK

32.4.2.3 Defined values
Parameter<mode>

Type
Number<step>

Number<result>

NumberDescription
URC configuration:• 0 (default value): disabled• 1: enabled
Informs the user about the operation in progress:• 0: network scan start• 1: network scan end• 2: requesting data to the server• 3: received data from the server• 4: sending feedback to the server
Represents the result of the aiding operation:• 0: no error• 1: wrong URL• 2: HTTP error• 3: create socket error• 4: close socket error• 5: write to socket error• 6: read from socket error• 7: connection/DNS error• 8: authentication token missing or wrong (required for aiding for u-blox M8 andfuture versions)• 9: generic error• 10: user terminated• 11: no data from server

32.4.2.4 Notes
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 / SARA-G3• The command setting is not stored in the NVM.

UBX-13002752 - R67

32 Positioning

Page 762 of 1001

u-blox cellular modules - AT commands manual

LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.

32.4.3 Specify the device autonomous solution +ULOCAID+ULOCAID
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

32.4.3.1 Description
The user has the possibility to specify its state (position and velocity) at a given time to select one of themulti-hypothesis provided in the previous +ULOC request (<sol> parameter) or to insert a location estimate
provided by other sensors. These information will be sent to the server with the next +ULOC command.
This command influences the amount of data exchanged with the server.
If the parameters of the autonomous solution have to be specified (<index> = 0), the RTC time must havea correct value prior to using the +ULOCAID command.
Speed and direction parameters can be inserted (optionally) also if one of the multi-hypotheses has been
selected (<index> > 0). Default values are those contained in the hypothesis selected (equal to 0 for
CellLocate® solutions).
32.4.3.2 Syntax
Type
SyntaxResponse
Location estimate from other sensors
Set
AT+ULOCAID=0,<date>,<time>,OK<lat>,<long>,<major>,<minor>,<orientation>[,<speed>,<direction>]
Read

AT+ULOCAID?

ExampleAT+ULOCAID=0,"10/03/2015","11:37:32.000","45.23456","11.12345",
1300,789,34,34,121

OK+ULOCAID: <index>,<date>,<time>, If <speed> and <direction> set:<lat>,<long>,<major>,<minor>,+ULOCAID: 0,"10/03/2015",<orientation>[,<speed>,<direction>]"11:37:32.000","45.23456","11.12345",
OK
1300,789,34,34,121
OK
If <speed> and <direction>
unknown:+ULOCAID: 0,"10/03/2015","11:37:32.000","45.23456","11.12345",
1300,789,34
OK

Location estimate from hypothesis selected (<index> greater than 0)
Set
AT+ULOCAID=<index>[,,,,,,,,
OK<speed>,<direction>]If <speed> and <direction>
unknown:
AT+ULOCAID=1
OK
If <speed> and <direction> set:
AT+ULOCAID=1,,,,,,,,34,121

Read

AT+ULOCAID?

OK+ULOCAID: <index>,<date>,<time>, If <speed> and <direction><lat>,<long>,<major>,<minor>,
unknown:<orientation>[,<speed>,<direction>]+ULOCAID: 1,"0/0/0","0:0:0.000","0.0OK000000","0.0000000",0,0,0
OK

UBX-13002752 - R67

32 Positioning

Page 763 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

ExampleIf <speed> and <direction> set:
+ULOCAID: 1,"0/0/0","0:0:0.000","0.0000000","0.0000000",0,34,121

Test

OK
+ULOCAID: (list of supported+ULOCAID: (0-17),"","","","",(0-63000<index>s),(list of supported00),(0-6300000),(0-179),(0-255),(0<date>s),(list of supported <time>), 359)
(list of supported <lat>),(list ofOKsupported <long>),(list of supported<major>),(list of supported<minor>),(list of supported<orientation>),(list of supported<speed>s),(list of supported<direction>s)

AT+ULOCAID=?

OK

32.4.3.3 Defined values
Parameter<index>Type
Number<date><time><lat><long><major><minor><orientation><speed><direction>

StringStringStringStringNumberNumberNumberNumberNumberDescription
Multi-hypotesis index:• 0: location estimate from other sensors (following fields are used)• n: index of the previous CellLocate solution
Date (DD/MM/YY) of the estimated position.
Time (hh:mm:ss.sss) of the estimated position.
Estimated latitude expressed in degrees.
Estimated longitude expressed in degrees.
Semi-major axis of the uncertainty ellipse in meters.
Semi-minor axis of the uncertainty ellipse in meters.
Orientation of the semi-major axis of the ellipse in degrees.
Estimated speed in meters per second. Default value is 0.
Direction of the motion in degrees. Default value is 0.

32.4.3.4 Notes
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.

32.4.4 GNSS sensor configuration +ULOCGNSS+ULOCGNSS
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

32.4.4.1 Description
Configures the GNSS sensor that can be used with the +ULOC AT command.
32.4.4.2 Syntax
Type
Set

SyntaxAT+ULOCGNSS=<aiding>[,<psv_
mode>[,<minSV>[,<minCNO>[,<ini_3d_fix>[,<staticHoldMode>[,<SBAS>[,<jamming>[,<antenna>[,<BBthreshold>[,<CWthreshold>[,<GNSS_system>[,<reserved1>[,<reserved2>]]]]]]]]]]]]]

UBX-13002752 - R67

Response
OK

ExampleAT+ULOCGNSS=15
OK

32 Positioning

Page 764 of 1001

u-blox cellular modules - AT commands manual

Type
Read

Test

SyntaxAT+ULOCGNSS?

Response+ULOCGNSS: <aiding>,<psv_
mode>,<minSV>,<minCNO>,<ini_3d_fix>,<staticHoldMode>,<SBAS>,<jamming>,<antenna>,<BBthreshold>,<CWthreshold>,<GNSS_system>,<reserved1>,<reserved2>

Example+ULOCGNSS: 15,1,6,8,0,1,1,1,1,1,1,0,0
,0
OK

OK
+ULOCGNSS: (list of supported+ULOCGNSS: (0-15),(0-1),(3-32),(0<aiding>),(list of supported <psv_50),(0-1),(0-255),(0-1),(0-1),(0-2),(0mode>),(list of supported <minSV>), 15),(0-31),(1-127),(0),(0)(list of supported <minCNO>),(listOKof supported <ini_3d_fix>),(list of
supported <staticHoldMode>),(list of supported <SBAS>),(listof supported <jamming>),(listof supported <antenna>),(list of
supported <BBthreshold>),(list of
supported <CWthreshold>),(list of
supported <GNSS_system>),(0),(0)AT+ULOCGNSS=?

OK

32.4.4.3 Defined values
Parameter<aiding>

Type
Number<psv_mode>

Number<minSV>

Number•<minCNO>

Number•<ini_3d_fix>

Number<staticHoldMode>

Number<SBAS>

Number<jamming>

Number<antenna>

Number<BBthreshold>

NumberUBX-13002752 - R67

Description
GNSS aiding mode configuration; it is possible the combination of different aiding
modes: to enable more aiding modes it is needed to sum the <mode> value of theinterested aiding modes:• 1: local aiding (including RTC sharing)• 2: AssistNow Offline• 4: AssistNow Online• 8: AssistNow Autonomous
All the modes (15) are enabled as a factory programmed setting.
Power Save Mode (UBX-CFG-RXM):• 0 (factory-programmed value): disabled• 1: enabled
Minimum number of satellites for navigation (UBX-CFG-NAVX5). The range goesfrom 3 to 32. (factory-programmed value: 3)

Minimum satellite signal level for navigation (UBX-CFG-NAVX5). The range goesfrom 0 to 50. (factory-programmed value: 7)
Initial Fix must be 3D flag (UBX-CFG-NAVX5):• 0 (factory-programmed value): disabled• 1: enabled
Static Hold Mode (UBX-CFG-NAV5). The range goes from 0 to 255 cm/s. (factoryprogrammed value: 0).
If the parameter is omitted, the Static Hold Mode threshold will not be configured to
GNSS.
SBAS configuration:• 0 (factory-programmed value): disabled• 1: enabled
Jamming indicator (UBX-CFG-ITFM):• 0 (factory-programmed value): disabled• 1: enabled
Antenna setting:• 0 (factory-programmed value): unknown• 1: passive• 2: active
Broadband jamming detection threshold (dB) (UBX-CFG- ITFM). The range goes from0 to 15. (factory-programmed value: 0)

32 Positioning

Page 765 of 1001

u-blox cellular modules - AT commands manual

Parameter<CWthreshold>

Type
Number<GNSS_systems>

Number<Reserved1><Reserved2>

NumberNumberDescription
Continuous wave jamming detection threshold (dB) (UBX-CFG- ITFM). The range goesfrom 0 to 31. (factory-programmed value: 0)
Bitmask for combining the supported GNSS types; the parameter is optional and theallowed values can be combined together (e.g. 3 means GPS+SBAS):• 1 (factory-programmed value): GPS• 2: SBAS• 4: Galileo• 8: BeiDou• 16: IMES
• 32: QZSS
• 64: GLONASS
0 (reserved value)
0 (reserved value)

32.4.4.4 Notes• To enable SBAS system opportunely configure both <SBAS> and <GNSS_systems> parameters.
• If a parameter is omitted, the current set value is kept.
• For more details on parameter description see the corresponding u-blox-GNSS receiver description.
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
LISA-U200-01S / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S /LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 /SARA-G300 / SARA-G310 / SARA-G340-00S / SARA-G350-00S / SARA-G350-00X / LEON-G1• The <GNSS_systems> parameter can only assume the value 0 (factory-programmed value).

32.4.5 Configure cellular location sensor (CellLocate®) +ULOCCELL+ULOCCELL
Modules

Attributes

LARA-R202 LARA-R203 LARA-R211 LARA-R220 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270 LISA-U1
SARA-G450-01C SARA-G340 SARA-G350 LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

32.4.5.1 Description
Configures the Cellular location sensor (CellLocate®) used with the +ULOC command.
This command influences the amount of data exchanged with the server.
32.4.5.2 Syntax
Type
Set

Read

Test

SyntaxAT+ULOCCELL=<scan_mode>[,<reserved1>[,<reserved2>[,<reserved3>[,<reserved4>[,<reserved5>]]]]]
AT+ULOCCELL?

AT+ULOCCELL=?

UBX-13002752 - R67

Response
OK

ExampleAT+ULOCCELL=0OK+ULOCCELL: <scan_mode>,<reserved1>,<reserved2>,<reserved3>,<reserved4>,<reserved5>
OK+ULOCCELL: (list of supported<scan_mode>s),(list of supported<reserved1>),(list of supported<reserved2>),(list of supported<reserved3>),(list of supported<reserved4>),(list of supported<reserved5>)

32 Positioning+ULOCCELL: 0,0,"","",0,0OK+ULOCCELL: (0-1),(0),"","",(0),(0)OKPage 766 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example32.4.5.3 Defined values
Parameter<scan_mode>

Type
Number<reserved1><reserved2><reserved3><reserved4><reserved5>

NumberStringStringNumberNumberDescription
Network scan mode:• 0 (factory-programmed value): normal• 1: deep scan
RFU
RFU"" (reserved value)
0 (reserved value)
0 (reserved value)

32.4.5.4 Notes
LARA-R202 / LARA-R203 / LARA-R211 / LARA-R220 / LARA-R280 / TOBY-R2• Only the normal scan is supported (<scan_mode>= 0).
LARA-R211 / TOBY-R200-02B / TOBY-R202• The command is not supported by LARA-R211-02B-00, TOBY-R200-02B-00 and TOBY-R202-02B-00.
SARA-U2 / LISA-U2• If the module is registered on 3G RAT, the <scan_mode> setting will be ignored and a deep scan will be
performed.
SARA-G4• <scan_mode>=1 is not supported.

32.5 UTIME
32.5.1 Ask for time information +UTIME+UTIME
Modules
Attributes

SARA-U201-04A SARA-U201-04B SARA-U201-04X LISA-U200-04B LISA-U201-04B
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
No
No
< 10 sError reference+CME Error

32.5.1.1 Description
Requests the cellular module to provide time information; the time can be determined using:• Local RTC• GNSS receiver• CellLocate® (location based on network cells data)• Combination of GNSS receiver and CellLocate® (hybrid)
The final result code indicates if sending the command request was successful or not. The URC is issued toprovide the requested information via the +UTIME set command.
The time information is also provided as a time pulse from a GPIO pin (to be configured as output via the+UGPIOC AT command).
The GNSS interface and CellLocate® can be used at the same time: if the GNSS sensor is reserved for anotherinterface, an error result code is provided ("+CME ERROR: GPS busy" if +CMEE: 2).
32.5.1.2 Syntax
Type
Set

SyntaxAT+UTIME=<mode>,<sensor>[,<latency>]

Response
OK

Read

AT+UTIME?

+UTIME: <mode>,<sensor>,<latency>

UBX-13002752 - R67

32 Positioning

ExampleAT+UTIME=2,3
OK+UTIME: 2,3,1000
OK

Page 767 of 1001

u-blox cellular modules - AT commands manualType

SyntaxTest

AT+UTIME=?

Response
OK+UTIME: (list of supported<mode>s),(list of supported<sensor>s),(range of supported<latency>)
OK+UUTIME: <date>,<time>,<milliseconds>,<accuracy>,<source>

URC

Example+UTIME: (0-2),(0-3),(1-60000)
OK

If <source>=1:+UUTIME: 13/04/2011,09:54:51,
123.456789,0.000083000,1
If <source>=2:+UUTIME: 13/04/2011,09:54:51,
123.456789,1.500000000,2
If <source>=1 and 2 available:+UUTIME: 13/04/2011,09:54:51,
123.456789,1.500000000,2+UUTIME: 13/04/2011,09:54:52,
234.567891,0.000083000,1

32.5.1.3 Defined values
Parameter<mode>

Type
Number<sensor>Number<latency><date><time><milliseconds>

NumberStringStringNumber<accuracy><source>

NumberNumberDescription
Allowed values:• 0: reserved• 1: reserved• 2: single shot position
Sensor selection: it is possible to combine different sensors summing <sensor>
values of the selected sensors:• 0: use the local RTC propagated time
• 1: use the GNSS receiver for timing• 2: use CellLocate® service information• 3: use the combined GNSS receiver and CellLocate® service information for timing
Network latency in milliseconds (1 - 60000). The default value is 1000.
Date10 (DD/MM/YY) of the estimated position
Time10 (hh:mm:ss) of the day
Fractional part of the time information, in milliseconds. Six decimal values areprovidedAccuracy of the time information, in seconds. Nine decimal values are provided
Sensor used:• 0: local RTC propagated time
• 1: GNSS receiver• 2: CellLocate® service information

32.5.1.4 Notes
SARA-U2 / LISA-U2• The <date>, <time> values are not enclosed in double quotes in the URC.
• Configure GPIO1 (pin number 16) as output pin to provide the time information as a time pulse on GPIO pin.

10Time information from GNSS can be expressed in GPS time or UTC time depending on the GNSS
version:• u-blox 6: GPS time
• u-blox 7: UTC time/GPS time (depending on the configured time base via +UGUBX)• u-blox M8: UTC time
Time information from CellLocate® server is expressed in UTC time.

UBX-13002752 - R67

32 Positioning

Page 768 of 1001

u-blox cellular modules - AT commands manual

33 Location Services
The Location Services (LCS) reference model allows an LCS Client (which may or may not reside in a TargetUE) to interact with an LCS server in order to obtain location information for one or more target UEs. Suchinformation is obtained via a positioning function between the LCS server and the Target UE. See 3GPP TS
22.071 [85].
LCS can be invoked by the network (e.g. during an emergency call) or by the user through the AT commands
described in this section. The position of the device is calculated either by network based on the GNSS
measurements reported by the device, or by the device itself. To speed up such measurements, a location
server provides the mobile with GNSS assistance data, that otherwise should have been downloaded from thesatellites e.g. rough location, GPS satellites to look for, Doppler frequencies, etc. This allows fast position fixes,
increases sensitivity and reduces module power consumption.
Generally two modes of A-GPS (Assisted GPS) can be distinguished:
MS-Assisted: only pseudo-range values are measured by the GPS system and returned to the network; theposition estimation is done within the network and can be reported to the device if it has started the location
request;• MS-Based: the network provides aiding for fast satellite acquisition to the GPS through the cellular control
plane, i.e. via signalling messages. The position estimate is done by the device's GPS system and returnedto the network or used locally if the device has started the location request.
Standalone poitioning means that no assistance is involved: GPS will work autonomously.
•

The LCS feature is linked to the GNSS architecture, but there is no correlation between LCS AT commands and
GNSS AT commands. Since they use the same resource, in case of collisions LCS services have higher priority.
The implementation of the LCS AT commands follows the 3GPP standard defined by 3GPP TS 27.007 [2].
SARA-U2 / LISA-U2
The LCS feature is by factory-programmed disabled. After having enabled it through the +UDCONF=70
AT command, a module reset is needed; after that it is possible to issue the other LCS AT commands.
If the LCS feature is disabled an error result code will be provided after the issuing of the LCS AT
commands.

33.1 LCS positioning capabilities configuration +UDCONF=70+UDCONF=70
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

33.1.1 Description
Configures the LCS positioning capabilities types enabling the standalone, MS-Based and MS-Assisted. It is
possible to simultaneously enable them or only a subset.
The setting is saved in NVM and the new configuration will be effective at the next power on.
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 [65], 3GPP TS 34.121-2 [66], 3GPP TS 36.521-2 [93] and 3GPP TS 36.523-2 [94], is a statementof the implemented and supported capabilities and options of a device. If the user changes the commandsettings during the certification process, the PICS of the application device integrating a u-blox cellular
module must be changed accordingly.

33.1.2 Syntax
Type
Set

SyntaxAT+UDCONF=70,<positioning_capabilities>

UBX-13002752 - R67

Response
OK

ExampleAT+UDCONF=70,1
OK

33 Location Services

Page 769 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UDCONF=70

Response+UDCONF: 70,<positioning_capabilities>
OK

ExampleAT+UDCONF=70+UDCONF: 70,1
OK

33.1.3 Defined values
Parameter<positioning_capabilities>

Type
NumberDescription
Bitmask of LCS positioning capabilities. The allowed range is 0-7 (equivalent to bits 000-111). See Table 87 for a complete list of the combinations supported. The factoryprogrammed bitmask is 0 (i.e. all the capabilities are disabled)

33.1.4 Notes
Bit
0
1
2

Positioning capability type
Standalone
MS-Based
MS-Assisted

Table 87: Positioning capabilities bitmask explanation

33.2 Mobile originated location request +CMOLR+CMOLR
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

33.2.1 Description
Initiates/terminates a mobile originated location request (MO-LR) and configures the +CMOLRN URC.
The URC reporting provides the location information in the format of NMEA strings <NMEA-string>.
Additional information about positioning can be found in 3GPP TS 25.305 [75]. If positioning data cannot beprovided at the expiring of timeout defined by the <timeout> parameter, the +CMOLRE URC is provided. See
the Appendix A.12 for possible <err> values.
The <hor-acc-set>, <hor-acc>, <ver-req>, <ver-acc-set>, <ver-acc> and <vel-req> parameters can be used torequest a specific accuracy of the MO-LR response.
The parameters <hor-acc> and <ver-acc> are only applicable if, respectively, <hor-acc-set> and <ver-acc-set>
are set to 1. In addition, <ver-acc> is applicable only if <ver-req> is set to 1.
It is not allowed to start multiple requests (every request must either have completed, having generated
a URC, or be terminated with +CMOLR=0).
Every request can be terminated only from the AT interface on which it was initiated.
The URC +UUGIND=0,256 (meaning "GPS ownership lost") indicates the successful start up of an alreadyactivated GPS device.

33.2.2 Syntax
Type
Set

SyntaxResponse
AT+CMOLR=<enable>[,<method>[, OK<hor-acc-set>[,<hor-acc>[,<ver-req>[,<ver-acc-set>[,<veracc>[,<vel-req>[,<rep-mode>[,<timeout>[,<interval>[,<shaperep>[,<plane>[,<NMEA-rep>[,<third-party-address>[,<resp-timecategory>]]]]]]]]]]]]]]]

UBX-13002752 - R67

33 Location Services

ExampleAT+CMOLR=1
OK

Page 770 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+CMOLR?

Test

AT+CMOLR=?

Response
Example+CMOLR: <enable>,<method>,+CMOLR: 0,0,0,,0,,,0,0,0,,,0,"","",0<hor-acc-set>,[<hor-acc>],<verOK
req>,[<ver-acc-set>],[<ver-acc>],<vel-req>,<rep-mode>,<timeout>,[<interval>],<shape-rep>,[<plane>],[<NMEA-rep>],[<third-partyaddress>],<resp-time-category>
OK+CMOLR: (list of supported<enable>s),(list of supported<method>s),(list of supported<hor-acc-set>s),(list of supported<hor-acc>s),(list of supported<ver-req>s),(list of supported<ver-acc-set>s),(list of supported<ver-acc>s),(list of supported<vel-req>s),(list of supported<rep-mode>s),(list of supported<timeout>s),(list of supported<interval>s),(list of supported<shape-rep>s),(list of supported<plane>s),(list of supported <resptime-category>s)
OK+CMOLRN: <NMEA-string>

URC+CMOLR: (0,1),(0,1,4,5),(0,1),(0-127),(0,1),(0,1),(0-127),(0-4),(0),(1-65535),(1-65535),(),0,(0,1)
OK+CMOLRN: "$GPRMC,235947.000,V,0000.0000,N,00000.0000,E,,,041299,,*1D"

33.2.3 Defined values
Parameter<enable>Type
Number<method>

Number<hor-acc-set>

Number<hor-acc>

Number<ver-req>

Number<ver-acc-set>

Number<ver-acc>

Number<vel-req>

NumberUBX-13002752 - R67

Description
Configures the reporting location as a result of a MO-LR. Allowed values:• 0: reporting and positioning disabled. At boot time the reporting is disabled.
• 1: enable the NMEA strings reporting through +CMOLRN URC
Lack of data when timeout occurs is indicated by +CMOLRE URC
Sets the positioning type. Only one positioning type can be enabled at any given time.
Allowed values for MO-LR:• 0 (default value): unassisted GPS. Autonomous GPS only, no use of assistance data
• 1: Assisted GPS (see Chapter 33.2.4)• 4: basic self location (the network determines the position technology)• 5: transfer to third party. The parameters <shape-rep> and <NMEA-rep> areirrelevant (any values are accepted and disregarded). The third party address isgiven in the parameter <third-party-address> (see Chapter 33.2.4)
Horizontal accuracy presence:• 0 (default value): not set/specified• 1: set in parameter <hor-acc>
Requested accuracy as horizontal uncertainty exponent (see the 3GPP TS 23.032 [76]subclause 6.2). The value range is 0-127. The default value is 127, which means thatthe uncertainty radius is 10 x [(1.1)127 - 1] ~ 1800 km.
Vertical coordinate (altitude) request flag:• 0 (default value): not requested; a 2D location fix is acceptable. The parameters<ver-acc-set> and <ver-acc> do not apply• 1: requested; a 3D location fix is required
Vertical accuracy presence:• 0 (default value): not set/specified• 1: set in parameter <ver-acc>
Requested accuracy as vertical uncertainty exponent (see the 3GPP TS 23.032 [76]subclause 6.4). The value range is 0-127. The default value is 127, which means thatthe uncertainty radius is 10 x [(1.1)127 - 1] ~ 1800 km.
Requested velocity type (see the 3GPP TS 23.032 [76] subclause 8.6):• 0 (default value): velocity not requested

33 Location Services

Page 771 of 1001

u-blox cellular modules - AT commands manual

ParameterType<rep-mode>

Number<timeout>

Number<interval><shape-rep><plane>NumberNumberNumber<NMEA-rep>

String<third-partyaddress>

String<NMEA-string>

String<resp-timecategory>

NumberDescription• 1: horizontal velocity requested• 2: horizontal velocity and vertical velocity requested• 3: horizontal velocity with uncertainty requested• 4: horizontal velocity with uncertainty and vertical velocity with uncertainty
requested
Reporting mode. The <timeout> parameter specifies the timeout for the MO-LR
response request. Allowed value:• 0: single report
Indicates how long the MS will wait for a response after a MO-LR. The value range isin seconds from 1 to 65535.
For GNSS measurements, the allowed values are 1, 2, 4, 8, 16, 32, 64 and 128 (default
value). All other values are truncated to these figures.
This parameter is ignored.
Ignored.
The parameter specifies which communication mode is used for MO-LR. Allowed
value:• 0 (default value): control plane
Specifies possible restrictions in supported NMEA strings. The supported NMEA
strings are specified as a comma separated values inside one string. If the parameteris omitted or an empty string is given, no restrictions apply and all NMEA strings aresupported. The default value is that all strings are supported. (Example: "$GPRMC,$GPGSA,$GPGSV")
The parameter is applicable to reporting to third party only, and specifies the address
to the third party. This parameter is mandatory when <method> value is set to 5,otherwise it is ignored
String type in UTF-8. This parameter provides an NMEA-string as defined in IEC 61162[86]. This parameter shall not be subject to conventional character conversion as per+CSCS
The NMEA string is enclosed in double quotes, without the trailing <CR><LF>
characters
Response time category of a location request. Allowed values are:
• 0: low delay• 1 (default value): delay tolerant

33.2.4 Notes••

For the methods that require assistance data, the assistance data obtained from the network is used fora UE-based GPS location procedure
If <method>=5 (Transfer to third party) the lack of data at each timeout is not indicated by +CMOLRE
URC if reporting to third party is specified

33.3 Mobile terminated location request notification +CMTLR+CMTLR
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

33.3.1 Description
Configures the Mobile Terminated Location Request (MT-LR) notifications to the TE by an unsolicited result
code (URC) through the parameter <subscribe>. It is possible to enable notification of MT-LR performed overthe control plane. Relevant location request parameters are provided in the +CMTLR URC. This URC is reported
upon arrival of a Mobile Terminated Location Request. To differentiate multiple requests, every request is givena different <handle-id>. This parameter is used when allowing or denying location disclosure with +CMTLRA.

UBX-13002752 - R67

33 Location Services

Page 772 of 1001

u-blox cellular modules - AT commands manual

33.3.2 Syntax
Type
Set

SyntaxAT+CMTLR=<subscribe>

Response
OK

ExampleAT+CMTLR=1

Read

AT+CMTLR?

+CMTLR: <subscribe>

OK+CMTLR: 1

Test

AT+CMTLR=?

OK+CMTLR: (list of supported<subscribe>s)OK+CMTLR: (0-1)
OK

OK+CMTLR: <handle-id>,<notificationtype>,<location-type>,[<clientexternal-id>],[<client-name>][,<plane>]URC

33.3.3 Defined values
Parameter<subscribe>

Type
NumberDescription
Configures the subscription for MT-LR notifications:<handle-id>

Number<notification-type>

Number• 0: reporting and positioning notifications disabled• 1: notifications of MT-LR over control plane subscribed
ID associated with each MT-LR used to distinguish specific request in case ofmultiple requests. The value range is 1-255
Information about the user's privacy:•<location-type><client-external-id><client-name><plane>Number

0: the subscription may stipulate that positioning the user by a third party isallowed and the network may choose to inform the user as a matter of courtesy• 1: locating the user is allowed if the user ignores the notification• 2: locating the user is forbidden if the user ignores the notification
Indicates what type of the location is requested:

StringStringNumber• 0: current location• 1: current or last known location• 2: initial location
Indicates the external client where the location information is sent to (if required)
The string identifying the external client requesting the user's location
The parameter specifies whether the MT-LR came over control plane:•

0: control plane

33.4 Mobile terminated location request disclosure allowance+CMTLRA+CMTLRA
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

33.4.1 Description
Allows or disallows the disclosure of the location of the TE as a result of a former MT-LR.

33.4.2 Syntax
Type
Set

SyntaxResponse
AT+CMTLRA=<allow>,<handle_id> OK

ExampleAT+CMTLRA=1,1

Test

AT+CMTLRA=?

OK+CMTLRA: (0,1),(1-255)

UBX-13002752 - R67+CMTLRA: (list of supported<allow>s),(list of supported<handle_id>s)

33 Location Services

OK

Page 773 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

Example33.4.3 Defined values
Parameter<allow>

Type
Number<handle_id>

NumberDescription
Configures the allowance for location disclosure:• 0: location disclosure allowed• 1: location disclosure not allowed
ID associated with each MT-LR used to distinguish specific request in case ofmultiple requests. The value is given in +CMTLR. The value range is 1-255

33.4.4 Notes•

No error result code is reported if an invalid <handle_id> is used, as long as it is in the range 1-255

33.5 Report mobile originated location request error+CMOLRE+CMOLRE
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

33.5.1 Description
Configures the verbose format of the result code +CMOLRE: <err> as an indication of an error relating to thefunctionality for the mobile originated location request (MO-LR) error reporting format. When enabled, the MT
related verbose error cause is given.

33.5.2 Syntax
Type
Set

SyntaxAT+CMOLRE=[<verbose_mode_
enable>]Read

AT+CMOLRE?

Test

AT+CMOLRE=?

Response
OK

OK+CMOLRE: <verbose_mode_enable> +CMOLRE: 1
OK+CMOLRE: (list of supported<verbose_mode_enable>s)
OK+CMOLRE: <err>

URC

ExampleAT+CMOLRE=1

OK+CMOLRE: (0,1)
OK
If <verbose_mode_enable>=0+CMOLRE: 2
If <verbose_mode_enable>=1+CMOLRE: Not enough satellites

33.5.3 Defined values
Parameter<verbose_mode_
enable>Type
Number<err>

Number or
stringUBX-13002752 - R67

Description• 0 (default value): disabled. The error code is in expressed in numeric format• 1: enabled. The error code is presented with verbose text strings
Error numeric code or textual description. See the appendix Appendix A.12

33 Location Services

Page 774 of 1001

u-blox cellular modules - AT commands manual

33.6 LCS event notification +ULCSEVT+ULCSEVT
Modules
Attributes

SARA-U201 SARA-U260-03S SARA-U270-03A SARA-U270-03S SARA-U270-53S SARA-U270-73S
SARA-U280-03S LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

33.6.1 Description
Configures the reporting of LCS events via the +UULCSEVT URC.
This is a test command, used for getting informations on LCS internals for debugging purposes. It does
not affect the behaviour of LCS or GPS.
The positioning related parameters display invalid values when no fix has been calculated.

33.6.2 Syntax
Type
Set

SyntaxAT+ULCSEVT=<event_reporting_enable>Response
OK

Read

AT+ULCSEVT?

+ULCSEVT: <event_reporting_enable>Test

AT+ULCSEVT=?

OK+ULCSEVT: (list of supported<event_reporting_enable>s)

ExampleAT+ULCSEVT=1
OK+ULCSEVT: 1
OK+ULCSEVT: (0,1)

OK
OK+UULCSEVT: <AcT>,<latitude>,+UULCSEVT: 2,45.713745,13.740721,<longitude>,[<altitude>],310,,"15/05/18,12:20:06",7221,32062,[<uncertainty>],<time>,<T1>,<T2>, 2
<T3>

URC

33.6.3 Defined values
Parameter<event_reporting_enable>Type
Number

<AcT>

Number<latitude><longitude><altitude><uncertainty><time>

NumberNumberNumberNumberString<T1>

Number

<T2>

Number

<T3>

NumberUBX-13002752 - R67

Description• 0 (default value): URC disabled• 1: URC enabled
Indicates the radio access technology:• 0: GSM• 2: UTRAN• 7: LTE
Degrees of latitude from -90 to 90 in decimal format
Degrees of longitude from -180 to 180 in decimal format
Altitude in meters
Uncertainty in meters from 0 to 1800000 m
GPS time in the format "yy/MM/dd,hh:mm:ss", where characters indicate year (twolast digits), month, day, hour, minutes, seconds.
Time in milliseconds from dialling an emergency call to assistance data reception
from the network.
Time in milliseconds from assistance data reception from the network to when the
protocol stack receives the fix data from the GPS.
Time in milliseconds from when the protocol stack receives the fix data from the GPS
to when the fix data is sent to the network.

33 Location Services

Page 775 of 1001

u-blox cellular modules - AT commands manual

34 DTMF
34.1 DTMF detection +UDTMFD+UDTMFD
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280 MPCI-L200-02S MPCI-L200-03S
MPCI-L210-02S MPCI-L210-03S MPCI-L220-02S MPCI-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S LISA-U200-62S
LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S LISA-U270-63S
LISA-U270-68S
SARA-G450-01C SARA-G340 SARA-G350 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

34.1.1 Description
Enables/disables the DTMF detector and, independently for each specific AT terminal, the related URCs.
During a voice call, the DTMF detector recognizes the presence of DTMF tones in the RX voice channel. The
tones are generated by remote party by e.g. digit press on a DTMF keypad.
The +UUDTMFD URC returns the recognized DTMF digits (set {0-9,#,*A,B,C,D}).
Once enabled, the DTMF detector is automatically started at the next call set-up confirmation and stopped atcall drop or when it is explicitly disabled.
If the DTMF detector is enabled, the In-Band Modem engine is reserved thus the eCall and other In-Band Modem
applications are not available. For more details see the eCall section.
If the In-Band Modem engine is reserved by other In-Band Modem applications, the command immediately
provides an error result code ("+CME ERROR: 3" if +CMEE: 1 or "+CME ERROR: operation not allowed" if +CMEE:
2).
URCs are issued at any DTMF digit detection, if the URCs have been enabled on the specific terminal.
QUICK START: AT+UDTMFD=1,2 (start in robust mode).
Issue the enabling command before the call set-up, otherwise the detector is not started.
For the complete description of the DTMF detection functionality see the corresponding module audio
application note.

34.1.2 Syntax
Type
Set

Read

Test

SyntaxAT+UDTMFD=<urc_en>[,<mode>[,<att_cfg>[,<threshold>[,<immunity>[,<max_int>[,<sd_cfg>]]]]]]
AT+UDTMFD?

AT+UDTMFD=?

Response
OK

ExampleAT+UDTMFD=1,2
OK+UDTMF: <urc_en>,<mode>,<att_cfg>,<threshold>,<immunity>,<max_int>,<att>,<sd_cfg>+UDTMFD: 1,2,4,100,14,2,4,3
OK

OK+UDTMFD: (list of supported <urc_ +UDTMFD: (0-1),(0-10),(0-15),(100-10
en>'s),(list of supported <mode>'s), 000),(0-20),(1-255),(0-6)(list of supported <att_cfg>'s),(listOKof supported <threshold>'s),(listof supported <immunity>'s),(listof supported <max_int>'s),(list of
supported <sd_cfg>'s)
OK

UBX-13002752 - R67

34 DTMF

Page 776 of 1001

u-blox cellular modules - AT commands manual

Type
URC
URC

SyntaxResponse+UUDTMFD: <DTMF>+UUDTMFDE: <errid>

Example+UUDTMFD: #+UUDTMFD: 1

34.1.3 Defined values
Parameter<urc_en>Type
Number<mode>

Number<att_cfg>

Number<threshold><immunity><max_int>

UBX-13002752 - R67

NumberNumberNumberDescription
URC generation on the current terminal:• 0 (factory-programmed value): disabled• 1: enabled
DTMF detector configuration:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200-02S /LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S /LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U260 / LISA-U270 /SARA-G4 / SARA-G3 / LEON-G1
o 0 (factory-programmed value): disabledo 1: enabled/restarted in normal modeo 2: enabled/restarted in robust modeo 3-10: reserved• LISA-U200-04B / LISA-U201-04B
o 0 (factory-programmed value): disabledo 1: not supportedo 2: enabled/restarted for short tones
o 3: enabled/restarted for long toneso 4-10: reserved
Attenuation applied on the signal at decoder input to manage arithmetic operations.
The range goes from 0 to 15, 6 dB attenuation each step:• TOBY-L2 / MPCI-L2 / LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 /LARA-R280 / TOBY-R2 / SARA-U2 / LISA-U200-02S / LISA-U200-03S /LISA-U200-52S / LISA-U200-62S / LISA-U200-83S / LISA-U201-03A /LISA-U201-03S / LISA-U201-83S / LISA-U260 / LISA-U270 / SARA-G3 / LEON-G1 The factory-programmed value is 4 (24 dB attenuation)• LARA-R211 / LISA-U200-04B / LISA-U201-04B - The factory-programmed value is 3
(18 dB attenuation)
LARA-R211
On LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02 the factoryprogrammed value is 4 (24 dB attenuation).
Numeric threshold to detect DTMF tones. The range goes from 100 to 10000:• TOBY-L2 / MPCI-L2 / LARA-R211 / LISA-U200-04B / LISA-U201-04B - The factoryprogrammed value is 800• LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 / LARA-R280 / TOBY-R2 /SARA-U2 / LISA-U200-02S / LISA-U200-03S / LISA-U200-52S / LISA-U200-62S /LISA-U200-83S / LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U260 /LISA-U270 / SARA-G3 / LEON-G1 - The factory-programmed value is 400
LARA-R211
On LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02 the factoryprogrammed value is 400.
Speech immunity level. The higher the level, the higher the immunity to speech. The
range goes from 0 (minimum immunity) to 20 (maximum immunity).
• TOBY-L2 / MPCI-L2 / LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 /LARA-R280 / TOBY-R2 / SARA-U2 / LISA-U200-02S / LISA-U200-03S /LISA-U200-52S / LISA-U200-62S / LISA-U200-83S / LISA-U201-03A /LISA-U201-03S / LISA-U201-83S / LISA-U260 / LISA-U270 / SARA-G3 / LEON-G1 The factory-programmed value is 14• LARA-R211 - The factory-programmed value is 5
• LISA-U200-04B / LISA-U201-04B - The factory programmed value is 8
LARA-R211
On LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02 the factoryprogrammed value is 14.
Maximum interruption that a detected DTMF tone may have, such that it is stillinterpreted as a single digit. In multiples of 20 ms; the range goes from 1 to 255. The
factory-programmed value is 2 (40 ms).

34 DTMF

Page 777 of 1001

u-blox cellular modules - AT commands manual

Parameter
<att>

Type
Number<DTMF><errid>Character
Number<sd_cfg>

NumberDescription
Actual attenuation applied on the signal at decoder input. The starting value is <att_cfg>. If an arithmetic overflow occurs, it is automatically increased.
Detected DTMF digits; from the set {0-9,#,*,A-D}.
DTMF error code:• 1: arithmetic overflow• 2: audio driver error
Enables/disables the speech discriminator (SD), the analysis of the stationarity (AS)and the noise reduction (NR) algorithms:• LISA-U200-04B / LISA-U201-04B
o 0: SD disabledo 1: SD enabled / NR disabledo 2: SD enabled / NR enabledo 3: SD enabled / NR enabled and configuredo 4: SD and AS enabled / NR disabledo 5: SD and AS enabled / NR enabledo 6 (factory programmed value): SD and AS enabled / NR enabled and configured• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200-02S /LISA-U200-03S / LISA-U200-52S / LISA-U200-62S / LISA-U200-83S /LISA-U201-03A / LISA-U201-03S / LISA-U201-83S / LISA-U260 / LISA-U270 /SARA-G3 / LEON-G1 - The parameter is not supported.

34.1.4 Notes••••

The maximum interruption <max_int> also represents the expected minimum pause between two DTMF
tones.
The detector running in robust mode is less prone to false detections and more sensitive to speech
distortions caused by e.g. low bit-rate AMR codec.
The factory-programmed value of command parameters is set at each module start up.
If the optional parameters are omitted the settings are left unchanged.

TOBY-L2 / MPCI-L2• If <mode>=1 or 2 the command provides an error result code ("+CME ERROR: operation not allowed" if+CMEE: 2) if +UPLAYFILE is playing an audio file.
• <errid>=2 is not supported.
LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2• The DTMF detection is functional during VoLTE calls, RTP events are detected and +UUDTMFD URC isissued, but audio tones are not audible.
SARA-U2 / LISA-U2• <errid>=2 is not supported.
SARA-G4• The <sd_cfg> parameter is not supported.
• The <att_cfg>, <threshold>, <immunity> and <max_int> parameters cannot be configured by means of
the set command.
SARA-G340 / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B / SARA-G350-01S /SARA-G350-02S / SARA-G350-02X / LEON-G1• <errid>=2 is not supported.
SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S / LEON-G1• The <mode> parameter is mandatory.

UBX-13002752 - R67

34 DTMF

Page 778 of 1001

u-blox cellular modules - AT commands manual

34.2 DTMF generation +UDTMFG+UDTMFG
Modules
Attributes

LARA-R211
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

34.2.1 Description
Plays DTMF tones on the uplink or downlink path. DTMF tones are injected just before the AMR encoder on
the uplink path (tones are not affected by speech enhancement system) or after AMR decoder on the downlink
path (tones are affected by speech enhancement system).
Supported DTMF tones are:• tones '0' - '9',
• tones '*' and '#',
• tones 'A' - 'D'.
The tones are pre-generated using 8 kHz sample rate and are played from the ROM. A single DTMF tone canlast from 40 ms to 1000 ms, the gap duration between the tones can last from 0 ms to 1000 ms. Both durations
need to be multiple of 20 ms. The length of all combined tones and gaps that can be queued at any time is up
to 100 s. This means that when already playing DTMF tones, the client is limited by the amount of the tones
yet to be played.
When the tone generator is already active it can handle new start generation commands if the limit of 100 s will
not be breached. If the duration of the tones already in the generation queue and the ones in the new commandexceed 100 s the command will be rejected, however tones already in the queue will still play to the end.
Stopping tone generation will clear all the tones in the generation queue yet to be played.
If the In-Band Modem resource is reserved by other In-Band Modem applications, the command immediately
provides an error result code ("+CME ERROR: 3" if +CMEE: 1 or "+CME ERROR: operation not allowed" if +CMEE:2).
By default the tone generation does not return URCs.

34.2.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UDTMFG=<op_code>[,<param1>[,<param2>,<param3>]]

Response

ExampleOK

AT+UDTMFG=0

Read+UDTMFG: <op_code>,<param1>

OK+UDTMFG: 3,1

OK

OK

OK

AT+UDTMFG=0

Stop
Set

AT+UDTMFG=<op_code>

AT+UDTMFG=0

OK
Start
Set

AT+UDTMFG=1,<tones>,<tone_
duration>,<gap_duration>

OK

AT+UDTMFG=1,"0123456789ABCD#*",100,80
OK

URC
Set

AT+UDTMFG=3,<urc_ctrl>

OK

AT+UDTMFG=3,1

Read

AT+UDTMFG=3+UDTMFG: 3,<urc_ctrl>

OK+UDTMFG: 3,1

OK

OK

OK

AT+UDTMFG=4,1

Feature control
Set
AT+UDTMFG=4,<feat_ctrl>

OK
VolumeUBX-13002752 - R67

34 DTMF

Page 779 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+UDTMFG=5,<volume>

Response
OK

ExampleAT+UDTMFG=5,70

Read

AT+UDTMFG=5+UDTMFG: 5,<volume>OK+UDTMFG: 5,70

OK

OK

Test

AT+UDTMFG=?

+UDTMFG: (list of supported <op_code>s)+UDTMFG: (0-1,3-5)

OK+UUDTMFG: <event>+UUDTMFGE: <error>

URC
URC

OK
+UUDTMFG: 0+UUDTMFGE: 1

34.2.3 Defined values
Parameter<op_code>Type
Number<tones>String<tone_duration>

Number<gap_duration>

Number<urc_ctrl>

Number<feat_ctrl>

Number<volume>Number<event>Number<error>Number<param1>

Number<param2>

Number<param3>

NumberDescription
DTMF generator command:• 0: stop the DTMF generator (remove all tones from the queue)• 1: start the DTMF generator or add tones to the queue• 2: reserved• 3: read or set the DTMF generator URC control• 4: DTMF generator feature control• 5: read or set the DTMF generator volume
DTMF tones to play. Valid tones are:• '0' - '9'• 'A' - 'D'• '*' and '#'Duration of each tone in milliseconds. Allowed values:• 40-1000: it has to be a multiple of 20 ms
Duration of the gap between the tones in milliseconds. Allowed values:• 0-1000: it has to be a multiple of 20 ms
URC control:• 0 (factory-programmed value): URCs are disabled• 1: URCs are enabled
Specifies the feature control:• 0 (factory-programmed value): disable the feature• 1: enable the feature on uplink• 2: enable the feature on downlink
DTMF tone generator volume. Allowed values:• 0-100: the factory-programmed value is 100
Event URC:
• 0: DTMF generation finished
Error URC:
• 1: internal error (recovery was successful)• 2: internal error (recovery failed, restart necessary)
Type and supported content depend on the related <op_code> parameter; see the<op_code> specification
Type and supported content depend on the related <op_code> parameter; see the<op_code> specification
Type and supported content depend on the related <op_code> parameter; see the<op_code> specification

34.2.4 Notes
LARA-R211• The command is not supported by LARA-R211-02B-00, LARA-R211-02B-01, LARA-R211-02B-02.

UBX-13002752 - R67

34 DTMF

Page 780 of 1001

u-blox cellular modules - AT commands manual

34.3 Local and in-band DTMF tone generation configuration+UDCONF=31+UDCONF=31
Modules

Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S
TOBY-L210-62S TOBY-L210-65S TOBY-L220-02S TOBY-L280
LARA-R202 LARA-R203 LARA-R211 LARA-R280 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

34.3.1 Description
Configures the DTMF tone generation.
The local and in-band DTMF tone generation applies to user-required tones only, i.e. started via AT+VTS
and AT+UVTS commands and not by SIM Toolkit application (aka proactive DTMF tones).

34.3.2 Syntax
Type
Set

SyntaxAT+UDCONF=31,<local_tone_
generation>

Response
OK

Read

AT+UDCONF=31+UDCONF: 31,<local_tone_
generation>
OK

ExampleAT+UDCONF=31,1
OK
AT+UDCONF=31+UDCONF: 31,1OK

34.3.3 Defined values
Parameter<local_tone_
generation>

Type
NumberDescription
Local DTMF tone generation enable / disable:•••

0 (factory-programmed value): Local and In-band DTMF tone generation disabled
1: Local DTMF tone generation enabled
2: In-band DTMF tone generation enabled

34.3.4 Notes
TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2• <local_tone_generation>=2 is not supported.
SARA-G3• <local_tone_generation>=1 is not supported.

UBX-13002752 - R67

34 DTMF

Page 781 of 1001

u-blox cellular modules - AT commands manual

35 eCall35.1 Introduction
eCall (emergency Call) specification [59] standardizes the transfer of a set of 140 bytes of data, called Minimum
Set of Data (MSD) during an emergency voice call to a Public Safety Answering Point (PSAP). According to
3GPP specifications, the eCall In-band Modem (eIM) of the In-Vehicle System (IVS) immediately transmits the
MSD after the call setup; the MSD is received by the eIM of the PSAP.
In the call setup message the IVS Network Access Device (NAD) shall set the "Service Category" information(IE) according to ETSI TS 122 101 [57]. This eCall "flag" enables a serving "Mobile Switching Centre" (MSC) that
supports this functionality, to differentiate between speech only Teleservice 12 emergency calls and eCalls.
Additionally the MSC may also be able to discriminate between Manually Initiated eCalls and Automatically
Initiated eCalls.
When the IVS eIM is in activated state, during the call, the eIM receiver starts monitoring link messages from
PSAP eIM by analyzing the audio stream on the downlink speech channel. Once the link with PSAP eIM isestablished, the IVS eIM enters the so-called data-mode: the IVS microphone and loudspeaker are muted andthe eIM starts the MSD transfer. After the data transfer is completed, either successfully or with errors, the
IVS switches from data-mode into voice-mode: the microphone and the loudspeaker are un-muted and thevoice call between IVS and PSAP proceeds normally. The IVS eIM enters idle-mode and monitors new incoming
messages from PSAP eIM.
The eCall standard introduces specific mobility management procedures to be implemented in the IVS NAD.
In particular, the IVS NAD is configured at boot time by a valid, eCall-enabled SIM/USIM to work either in "eCall
only" mode or in normal mode.
More precisely, the eCall feature is a Release 10 feature that can be enabled on the USIM by NMO. If a USIM iseCall enabled (e.g. service n. 89 is active), the FDN and SDN services may also be used to define how the MS
will work, i.e. either as an eCall only device or as eCall-enabled device.
In particular, if the FDN service is enabled and activated, the MS acts as eCall-only device and the FDN
phonebook contains 2 entries which are the test and reconfiguration numbers. Only these two numbers canbe dialed in addition to the Manually Initiated and Automatically Initiated emergency calls.
If the MS acts as an eCall-enabled device, the SDN service is activated and the SDN phonebook contains thetest and reconfiguration numbers in its last 2 entries.
If a MS is equipped with a SIM which is not eCall enabled, it can be set to eCall-only and eCall-enabled device
via the +UECALLSTAT command. In this case, and if the FDN or SDN phonebooks are not properly configured,
test and reconfiguration numbers may be specified via the +UDCONF=90 command.

35.1.1 About eCall AT commands
The 3GPP eCall feature is implemented and controlled by AT interface through a set of dedicated AT
commands:
•

•

•
•
•
•
•

AT+UECALLDATA: used too activate the eIM, passing the MSD datao update the MSD during the emergency callo enable the eIM feature, reserving In-band modem audio resources for eCallo enable unsolicited indications
AT+UECALLVOICE: used too configure the microphone / speaker switching handlingo control and monitor microphone and speaker switching
AT+UECALLSTAT: used to check the eCall SIM configuration / force a configuration (eCall only mode)
AT+UDCONF=90: used to set the eCall and InBM test configuration
AT+UECALLTYPE: used to configure the eCall flag or Test eCall
AT+CECALL: used to trigger a Manually Initiated eCall, a Automatically Initiated eCall, a Test or a
Reconfiguration call
+UUECALLDATA: eIM status indications

UBX-13002752 - R67

35 eCallPage 782 of 1001

u-blox cellular modules - AT commands manual••+UUECALLVOICE: microphone/loudspeaker status indications
AT+UECALLCFG: used too set eCall audio path mode

35.2 eIM sends and receives data +UECALLDATA+UECALLDATA
Modules
TOBY-L4106
SARA-U201 SARA-U270 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S
LISA-U270-63S LISA-U270-68S
SARA-G340 SARA-G350 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
partial
No
No
No+CME Error

35.2.1 Description
Activates the IVS eIM for a single emergency call (eCall session) and provides the IVS eIM with the MSD totransfer. If the activation command is issued when there is no call ongoing, the eIM is armed, i.e. the MSD
is prepared for transmission. The eIM is then automatically activated as soon as the call setup indication isreceived. The eIM can be armed/activated once per eCall session. Further activations immediately provide anerror result code.
The eIM can be activated in PULL or PUSH mode. In PUSH mode, the IVS eIM sends the INITIATION signal torequest to PSAP to pull the MSD, i.e. it asks the PSAP to send the "SEND MSD" signal. In PULL mode, the IVS
eIM waits for START signal sent from the PSAP.
The command can also be used for terminating the eIM: the last +UECALLDATA activation command isaborted.
The command serves also to update the IVS eIM with new MSD data. The update command can be issued at
any time during the eCall session and may or may not force an eIM reset.
Read and set commands other than the enable/disable the eCall feature (<op_code>=4) are available only
if the eCall feature is turned on.
The terms "SEND MSD", "INITIATION" and "application layer ACK" (AL-ACK), mentioned in EN 16062 [58],correspond to the START signal sent by PSAP to IVS, the START signal sent by IVS to PSAP and thehigher-layer ACK (HL-ACK), mentioned in 3GPP TS 26.267 [59].

35.2.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UECALLDATA=<op_code>[,<param1>[,<data>]]
In-Band Modem abort
Set
AT+UECALLDATA=0

Response

ExampleOK

AT+UECALLDATA=1,0,"4D5344"
OK

OK

AT+UECALLDATA=0
OK

eCall In-Band Modem activation
Set
AT+UECALLDATA=1,<PUSH_
PULL>,<data>OK

MSD update
Set
AT+UECALLDATA=2,<update_mode>,<data>

OK

URC enabling
Set
AT+UECALLDATA=3,<urc_state>

AT+UECALLDATA=1,0,"4D5344"
OK
AT+UECALLDATA=2,1,"4D5344"
OK

OK

AT+UECALLDATA=3,1
OK

eCall feature enabling

UBX-13002752 - R67

35 eCallPage 783 of 1001

u-blox cellular modules - AT commands manual

Type
Set

SyntaxAT+UECALLDATA=4,<eCall_
enabling>

Response
OK

ExampleAT+UECALLDATA=4,1
OK

HLAP data timers status configuration
Set
AT+UECALLDATA=5,<data_timer>, OK<timer_status>

AT+UECALLDATA=5,0,1

HLAP data timers value configuration
Set
AT+UECALLDATA=6,<data_timer>, OK<timer_value>

AT+UECALLDATA=6,0,20000

Read+UECALLDATA: 0,1

Test

AT+UECALLDATA?

OK

OK+UECALLDATA: <state>,<urc_
state>
OK+UECALLDATA: (list of supported<op_code>s),(list of supported<param1>s)

AT+UECALLDATA=?

OK+UECALLDATA: (0-4),(0-2)
OK

OK+UUECALLDATA: <urc_id>[,<data>] +UUECALLDATA: 7,"0B"

URC

35.2.3 Defined values
Parameter<op_code>Type
Number<PUSH_PULL>

Number<data>

String<update_mode>

Number<urc_state>

Number<eCall_enabling>

Number<state>Number<data_timer>

Number<timer_status>

Number<timer_value>

Number<urc_id>

NumberUBX-13002752 - R67

Description
Operation to perform:• 0: abort. The In-Band Modem is terminated• 1: arm/activate eCall In-Band Modem (eIM)• 2: update MSD• 3: enable/disable URCs
• 4: enable/disable the eCall feature• 5: enable/disable timer T9• 6: configure timer T9Specifies the PULL/PUSH mode:• 0: PULL mode
• 1: PUSH mode
MSD to be sent. Each byte is coded with two characters in hex notation. It shall not
exceed 280 characters (140 bytes).
Specifies the update mode:• 0: update in idle only
• 1: immediate update / force eIM reset
URCs current state:• 0 (factory-programmed value): URCs disabled• 1: URCs enabled without IVS events (without URCs with id 11-19)• 2: all URCs enabled••

0 (factory-programmed value): eCall feature disabled
1: eCall feature enabled. URCs are automatically enabled (same as AT+UECALLDATA=3,1)
eIM current state:• 0: off• 1: armed/active
Data timers:• 0: T9 timer
Configures the status of T9 HLAP timer. Allowed values:• 0: timer disabled• 1 (factory-programmed value): timer enabled
Timer value expressed in milliseconds. The factory-programmed value is:• 3600000 ms (1 hour) for T9 timer
Specifies the event type:• 0: MSD correctly sent, HL-ACK check bits received and recorded.

35 eCallPage 784 of 1001

u-blox cellular modules - AT commands manual

ParameterType<param1>

NumberDescription<data>: four information bits received through HL-ACKs, returned within single
byte hex data (e.g.: +UUECALLDATA: 0,"0B" -> 0xB: 4 information bits)• 1: eIM lost synchronization with PSAP
• 2: T6 or T7 timer expired (MSD transfer marked as failure)• 3: reserved• 4: eIM is terminated: T9 timer expired• 5: eIM is terminated: audio error• 6: eIM is terminated: fatal error• 7: eIM is terminated: call drop
• 8: generic eIM error• 11: IVSEVENT_SENDINGSTART: eIM starts sending the INITIATION signal (only in
PUSH mode). Also indicates that the call set-up is completed• 12: IVSEVENT_SENDINGMSD: "SEND MSD" signal received, eIM starts sending
MSD• 13: IVSEVENT_RESTARTMSD: "SEND MSD" signal received too often, assume
PSAP sync failure• 14: IVSEVENT_CONTROLSYNC: IVS eIM is synchronizing with PSAP eIM• 15: IVSEVENT_CONTROLLOCK: IVS eIM is synched with PSAP eIM• 16: IVSEVENT_LLACKRECEIVED: 2. link-layer ACK received and recorded• 17: IVSEVENT_HLACKRECEIVED: 2. higher-layer ACK received and recorded• 18: IVSEVENT_IDLEPOSTRESET: IVS eIM is idling after a full reset. Reset is done
after the sync loss, due to e.g. end of PSAP transmission• 19: IVSEVENT_IDLEPOSTSTART: IVS eIM transmitter is idling after thetransmission of the INITIATION signal (PUSH mode)• 20: MSD update request received. MSD update deferred since the IVS is currently
transmitting• 21: MSD update done. The IVS transmitter is ready to send the new MSD at next
PULL request• 22: MSD update request cannot be processedType and supported content depend on the related <op_code> parameter; see the<op_code> specification.

35.2.4 Notes
TOBY-L4• eCall feature, URC enabling, T9 status configuration and T9 value configuration are part of the eCallcontroller configuration which is stored in the NVM. At the module boot, the eCall controller is configured
according to stored values.
• The URC enabling is a global setting, so all clients will get the same events based on it.
• The IVS eIM activation is effective for multiple eCall sessions. The last provided MSD is used wheneverrequired.
• While the eIM is activated all speech handling is done by the eCall controller (even if dialling a normal callusing the ATD command.
• While the eIM is activated all incoming calls are treated as calls from the emergency call center.
• When T9 timer expires it deactivates the eIM.
• If T9 expires when call is in progress, it is prolonged until call is dropped.
• When call is dropped and T9 is disabled, eIM is aborted.
• <urc_id>=19 is not supported.
• <urc_id>=2 indicates the expiry of T5, T6 or T7 (MSD transfer marked as failure).
SARA-U2 / LISA-U2 / SARA-G3 / LEON-G1• <op_code>=5 and 6 are not supported.
• <urc_id>=4 is not supported.

UBX-13002752 - R67

35 eCallPage 785 of 1001

u-blox cellular modules - AT commands manual

35.3 IVS eIM voice control +UECALLVOICE+UECALLVOICE
Modules
TOBY-L4106
SARA-U201 SARA-U270 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S
LISA-U270-63S LISA-U270-68S
SARA-G340 SARA-G350 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
partial
No
No
No+CME Error

35.3.1 Description
Configures the control and/or controls the TX and RX voice path connections to voice resources (microphoneand loudspeaker respectively) and to eIM transmitter (eIM receiver is not affected by the control). The
command serves to handle the switching11 of the voice resources according to BS EN 16062 [58], in particular
to configure the HLAP timers to operate according to HLAP specifications [58], Annex A, Table of Timings.
With this command, it is possible to implement the voice control following several strategies:• Internal handling: eIM handles voice path connections in normal eCall transactions and, with HLAP timers,in abnormal eCall transactions. See the Voice control internal handling for details• External handling: the application processor exclusively handles voice path connections. The internal
handling must be disabled before the eCall session is started• Mixed handling: eIM and application processor share handling of voice path connections
Read and set commands are available only if the eCall feature is turned on.
The internal handling can be enabled / disabled during the eCall.
Table 88 summarizes the impact of the voice resource switching on the voice path connections:
Voice resource
Microphone

StatusUn-muted
Muted

Loudspeaker

Un-muted
Muted

Description
The microphone is connected to the TX voice path. The eIM transmitter isdisconnected from the TX voice path
The microphone is disconnected from the TX voice path. The eIM transmitter isconnected to the TX voice path
Both the loudspeaker and the eIM receiver are connected to the RX voice path
The loudspeaker is disconnected from the RX voice path. The eIM transmitter isconnected to the RX voice path

Table 88: Voice path connections as function of the microphone/loudspeaker status
The microphone and eIM transmitter are exclusively connected to the TX voice path, while the eIM receiver isalways connected to the RX voice path (always listening to PSAP). Of course, eIM can be connected to the voice
paths only if armed/activated (see the +UECALLDATA command).
Loudspeaker switches do not affect the eIM functionality.
The command groups six operations:
1.
Internal voice resource control configuration
When the internal voice control is enabled, the eIM takes care to perform microphone/loudspeakerswitching during a normal or abnormal eCall transaction. Switching during the normal eCall transaction
is operated at pre-defined internal control points. Some of the control points are configurable, i.e. they
can be enabled or not to perform the switching (see control points configuration).In particular (NCF: notconfigurable):• NCF - the microphone and loudspeaker are muted at call set-up• SP0 - the loudspeaker is muted at call set-up and un-muted after 5 s• MP0 - the microphone is muted as soon as the eIM transmitter starts sending INITIATION signal• MP1 - the microphone is muted as soon as the eIM transmitter starts sending MSD• SP1 - the loudspeaker is muted as soon as the eIM transmitter starts sending MSD
11

A switch performs a muting of un-muted voice resource or vice versa

UBX-13002752 - R67

35 eCallPage 786 of 1001

u-blox cellular modules - AT commands manual

•
•
•
•
•
•
•

MP2 - the microphone is un-muted as soon as the eIM receiver receives an LL-ACK message
SP2 - TH internal timer is started as soon as the eIM receiver receives a HL-ACK message and theloudspeaker un-muted at expiration
MP3 - the microphone is un-muted as soon as the eIM receiver receives a HL-ACK message
SP3 - the loudspeaker is un-muted as soon as the eIM goes in idle after reset
MP4 - the microphone is un-muted as soon as the eIM goes in idle after reset
MP5 - the microphone is un-muted as soon as the eIM transmitter goes in idle after sending
INITIATION signal
MP6 - the microphone is un-muted as soon as the eIM transmitter stops sending INITIATION signal
because of reception of SEND MSD signal

Abnormal eCall transactions are handled by T5, T6 and T7 timers. Enabled internal voice control is a
pre-requisite for timers to operate.
For more details see Voice control internal handling.
TOBY-L4
The internal voice control is not available. The handling of speech during a normal or abnormal eCalltransaction is generally performed on IVS URC events (see the +UECALLDATA Defined Values),
according to the Table 89:
Event / IVS event
Microphone mute
IVSEVENT_SENDINGSTART ON
IVSEVENT_SENDINGMSD ON
IVSEVENT_RESTARTMSD ON
IVSEVENT_CONTROLLOCK ONIVSEVENT_LLACKRECEIVEDIVSEVENT_HLACKRECEIVED

Loudspeaker mute Timers
ON
Start T5 timer
Start T7 timer
ON

Stop T5 timer
Start T6 timer, stop T7 timer
Start TU timer, un-mute
microphone and speaker at
expiration, stop all timers.
All timers stopped

IVSEVENT_IDLEPOSTRESET

Table 89: eIM handling of Microphone/loudspeaker switches. Call set-up notification event isexternally available as +UCALLSTAT: 1,0 URC
Abnormal eCall transactions are handled by T5, T6 and T7 timers.
nd

2.

3.
4.

5.
6.

The purpose of TU timer is to keep the loudspeaker muted while HL-ACKs are received after the 2(recorded) HL-ACK. TU timer is not configurable through AT. The timer is 450 ms and is restarted
after each recorded HL-ACK.
Voice resource mute/un-mute command
This command mutes/un-mutes the microphone or loudspeaker (regardless of voice control
configuration). It also provides the voice resource muted/un-muted state.
URC enabling - indications of a voice resource switch
This command enables/disables URCs providing loudspeaker/microphone switching notifications.
Internal control points configuration
This command enables/disables the internal control points MP0-MP6 for microphone and control points
SP0-SP2 for loudspeaker switching operations.
HLAP timers status configuration
This command enables/disables timers T5, T6 and T7.
HLAP timers value configuration
This command configures expiry value of timers T5, T6 and T7.

35.3.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UECALLVOICE=<op_code>,<param1>,<param2>

UBX-13002752 - R67

Response

ExampleOK

35 eCallPage 787 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UECALLVOICE=<op_code>,<param1>

Response+UECALLVOICE: <op_code>,<param1>,<param2>

OK
Internal voice control
Set
AT+UECALLVOICE=1,<res_id>,<on_ OK
off_ctrl>
Read

AT+UECALLVOICE=1,<res_id>

Voice resource mute/un-mute
Set
AT+UECALLVOICE=2,<res_id>,<mute_unmute>
Read

AT+UECALLVOICE=2,<res_id>

AT+UECALLVOICE=1,0,1

OK+UECALLVOICE: 1,<res_id>,<on_off_ AT+UECALLVOICE=1,0
ctrl>+UECALLVOICE: 1,0,1
OK
OK
OK

AT+UECALLVOICE=2,0,1+UECALLVOICE: 2,<res_id>,<res_state>OK

URC enabling
Set
AT+UECALLVOICE=3,<res_id>,<urc_state>
Read

AT+UECALLVOICE=3,<res_id>

Read

AT+UECALLVOICE=4,<res_id>

OK

Read

AT+UECALLVOICE=5,<timer>

HLAP timers value configuration
Set
AT+UECALLVOICE=6,<timer>,<timer_value>
Read

AT+UECALLVOICE=6,<timer>

Prompt configuration
Set
AT+UECALLVOICE=7,<prompt_
configuration>
Test

AT+UECALLVOICE=?

URC

UBX-13002752 - R67+UECALLVOICE: 2,0,1

AT+UECALLVOICE=3,1,0+UECALLVOICE: 3,<res_id>,<urc_
state>

OK
AT+UECALLVOICE=3,1+UECALLVOICE: 3,1,0
OK

OK

AT+UECALLVOICE=4,1,15+UECALLVOICE: 4,<res_id>,<resource_bitmask>
OK

HLAP timers status configuration
Set
AT+UECALLVOICE=5,<timer>,<timer_status>

OK
AT+UECALLVOICE=2,0
OK

OKInternal control points configuration
Set
AT+UECALLVOICE=4,<res_id>,<resource_bitmask>

ExampleOK
AT+UECALLVOICE=4,1+UECALLVOICE: 4,1,15
OK

OK

AT+UECALLVOICE=5,1,1

OK+UECALLVOICE: 5,<timer>,<timer_ AT+UECALLVOICE=5,0
status>+UECALLVOICE: 5,0,1
OK
OK
OK

AT+UECALLVOICE=6,0,5000

OK+UECALLVOICE: 6,<timer>,<timer_ AT+UECALLVOICE=6,0
value>+UECALLVOICE: 6,0,5000
OK
OK
OK

AT+UECALLVOICE=7,1
OK+UECALLVOICE: (list of supported<op_code>s)
OK+UUECALLVOICE: <res_id>,<res_state>

35 eCall+UECALLVOICE: (1-6)
OK+UUECALLVOICE: 1,1

Page 788 of 1001

u-blox cellular modules - AT commands manual

35.3.3 Defined values
Parameter<op_code>Type
Number<res_id>

Number<on_off_ctrl>

Number<mute_unmute>

Number<urc_state>

Number<res_state>

Number<resource_bitmask> Number<timer>Number<timer_status>

Number<timer_value>

Number<prompt_
configuration>

NumberUBX-13002752 - R67

Description
Type of operation:• 1: enable/disable internal voice resource control (by eIM)• 2: mute/un-mute voice resource• 3: enable/disable/query URC generation for specific voice resource• 4: configure internal control points of a voice resource• 5: enable/disable timers T5, T6 and T7• 6: configure timers T5, T6 and T7• 7: configure prompts
Voice resource identifier:• 0: microphone• 1: loudspeaker
Flag to enable or disable the eIM internal control of voice resource:• 0: disabled• 1 (factory-programmed value): enabled
Flag to mute or un-mute the voice resource. Allowed values:• 0: mute• 1: unmute
Flag to enable or disable URCs on voice resource status:• 0 (factory-programmed value): disabled (do not receive URCs when resource statuschanges)• 1: enabled (receive URCs when resource status changes)
Voice resource state. Allowed values:• 0: muted (microphone / loudspeaker disconnected)• 1 (factory-programmed value): un-muted (microphone / loudspeaker connected)
Bitmask representing the internal control points to be enabled. Allowed values:• For the microphone (<res_id>=0) the bitmask is composed by 7 bits.
o Bit #0 set: MP0 control point enabled (factory-programmed value: disabled)o Bit #1 set: MP1 control point enabled (factory-programmed value: enabled)o Bit #2 set: MP2 control point enabled (factory-programmed value: enabled)o Bit #3 set: MP3 control point enabled (factory-programmed value: enabled)o Bit #4 set: MP4 control point enabled (factory-programmed value: disabled)o Bit #5 set: MP5 control point enabled (factory-programmed value: disabled)o Bit #6 set: MP6 control point enabled (factory-programmed value: disabled)
Range: 0 to 127 (decimal format only). Factory-programmed value: 14• For the loudspeaker (<res_id>=1) the bitmask is composed by 4 bits.
o Bit #0 set: SP0 control point enabled (factory-programmed value: disabled)o Bit #1 set: SP1 control point enabled (factory-programmed value: enabled)o Bit #2 set: SP2 control point enabled (factory-programmed value: enabled)o Bit #3 set: SP3 control point enabled (factory-programmed value: disabled)
Range: 0 to 15 (decimal format only). Factory-programmed value: 6Timers:• 0: T5 timer• 1: T6 timer• 2: T7 timer
Configures the status of T5, T6 or T7 HLAP timers. Allowed values:• 0: timer disabled• 1 (factory-programmed value): timer enabled
Timer value expressed in milliseconds. The factory-programmed values are:• T5 timer: 5000 ms• T6 timer: 5000 ms• T7 timer: 20000 ms
Range: 1000 to 60000 (decimal format only).
Configures the prompt configuration. The allowed values are:
• 0: prompts disabled• 1 (factory-programmed value): default system prompts• 2: custom defined prompts (see Prompts)

35 eCallPage 789 of 1001

u-blox cellular modules - AT commands manual

Parameter<param1>

Type
Number<param2>

NumberDescription
Type and supported content depend on the related <op_code> parameter:• <op_code>=1: type is <res_id>• <op_code>=2: type is <res_id>• <op_code>=3: type is <res_id>• <op_code>=4: type is <res_id>• <op_code>=5: type is <timer>• <op_code>=6: type is <timer>
Type and supported content depend on the related <op_code> parameter:• <op_code>=1: type is <on_off_ctrl>• <op_code>=2: type is <mute_unmute>• <op_code>=3: type is <urc_state>• <op_code>=4: type is <resource_bitmask>• <op_code>=5: type is <timer_status>• <op_code>=6: type is <timer_value>

35.3.4 Notes
TOBY-L4• <op_code>=1, 2, 5 and 6 are not supported.
• The internal voice control handling is not configurable.
• Prompt configuration and URC enabling are part of the Call controller configuration which is stored in the
NVM. At the module boot, the eCall controller is configured according to stored values.
• The URC enabling is a global setting, so all clients will get the same events based on it.
SARA-U2 / LISA-U2 / SARA-G3 / LEON-G1• <op_code>=7 is not supported.
SARA-U270-00S / LISA-U200-02S / LISA-U200-52S / LISA-U200-62S / LISA-U260 / LISA-U270 /LISA-U120 / LISA-U130 / SARA-G340-00S / SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G100-07S / LEON-G100-08S• <op_code>=4, 5 and 6 are not supported.

35.3.5 Voice control internal handlingWith voice control internal handling, the eIM performs the microphone and/or loudspeaker switches.
Microphone and loudspeaker switches or loudspeaker un-muting timer start-up generally occur at IVS URC
events (see the +UECALLDATA Defined Values), according to the Table 90:
Event / IVS event

Microphone muteCall setup notification

NCF

IVSEVENT_SENDINGSTARTIVSEVENT_SENDINGMSDIVSEVENT_LLACKRECEIVEDIVSEVENT_HLACKRECEIVED

MP0
MP1

IVSEVENT_IDLEPOSTRESETIVSEVENT_IDLEPOSTSTARTeIM transmitter interrupts the
INITIATION signal since sync
has been detected (internal
event)

Microphone un-mute Loudspeaker mute
NCF,SP0

Loudspeaker
un-muteSP0: Start 5 s timer,
un-mute at expiration

SP1
MP2
MP3

MP4
MP5
MP6

SP2: Start TH
timer, un-mute at
expiration. Timervalue is 1.2 s in fast
modulation mode,
2.4 s in robust
modulation mode
SP3

Table 90: eIM handling of Microphone/loudspeaker switches. Call set-up notification event is externallyavailable as +UCALLSTAT: 1,0 URC

UBX-13002752 - R67

35 eCallPage 790 of 1001

u-blox cellular modules - AT commands manual

Microphone switches are performed within high-priority 3GPP eIM execution thread.
The purpose of SP2 - TH timer is to keep, during a normal eCall transaction, the loudspeaker muted forthe duration of 3 HL-ACKs that are received after the 2nd (recorded) HL-ACK. TH timer is not configurable
through AT.
SP0 5 s timer un-mutes only the loudspeaker, while the programmable T5 timer reconnects both themicrophone and loudspeaker.

35.3.6 Prompts
TOBY-L4
When prompts are enabled (factory or custom prompts configuration - using AT+UECALLSTAT=7, four
different prompts are supported:• ecall_prompt_dialing.pcm: the dialing prompt starts playing on dialling indication,• ecall_prompt_msd_sending.pcm: the start sending MSD prompt starts playing when START message is
received from PSAP,• ecall_prompt_call_end.pcm: the call disconnect prompt starts playing on disconnect indication,• ecall_prompt_call_incoming.pcm: the incoming call prompt starts playing on an incoming call.
Prompts can be downloaded to the module using the +UDWNFILE AT command and deleted using the+UDELFILE AT command. Both AT commands use the "ECALL_EXT" tag (for details, see File tags).
When downloading or deleting prompts, use the exact file name (i.e. "ecall_prompt_dialing.pcm") or the
prompt will not be accepted.
If custom prompts are configured and prompts are missing, factory-programmed prompts will be used.
The prompt configuration is part of the eCall controller configuration which is stored in the NVM. At the module
boot, the eCall controller is configured according to stored values.
Prompts have to be in following audio format:• PCM raw (without header),• Single channel (mono),• 16 kHz sample rate,• Signed 16-bit little-endian encoding.
If a wrong audio format is set, distorted prompts will be heard.
Configuration of the prompts should not be done between an ongoing call as that will result in unexpectedbehaviour.

35.4 eCall configuration +UECALLSTAT+UECALLSTAT
Modules
TOBY-L4106
SARA-U201 SARA-U270 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S
LISA-U270-63S LISA-U270-68S LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
partialYes
No
No+CME Error

35.4.1 Description
LISA-U120 / LISA-U130
The command is supported with partial functionality and a limited range for testing purposes only.
According to EN 16062 [58], eCall configuration of an eCall-enabled IVS must automatically be read from a valid
SIM/USIM that supports the provision of the eCall service (i.e. valid eCall USIM, according to 3GPP TS 31.102[18]).
The eCall-enabled SIM can be configured only for eCall (referred in EN 16062 [58] as "eCall only"), or a
combination of eCall and commercial service provision (referred in 3GPP TS 26.267 [59] as "eCall without

UBX-13002752 - R67

35 eCallPage 791 of 1001

u-blox cellular modules - AT commands manualregistration restrictions"). In particular, an IVS NAD configured in eCall only mode boots up with network
registration restriction, i.e. the IVS NAD does not perform the standard mobility management procedures.
In case IVS NAD is configured as eCall only, the MS class is implicitly set to GSM only, i.e. no GPRS service
is available by default.
This command serves to:• Read the eCall configuration from the SIM• Force the module with a not valid eCall SIM configuration to eCall only or eCall without registration
restriction (for testing purposes)
Enabling and disabling eCall only mode with registration restriction (also by restoring SIM settings) can only
be performed if the module is unregistered.
The use of +UECALLSTAT set command with valid eCall SIMs is not allowed.
If the module does not support the +CECALL AT command, the state switches can only be performed if
the module is not registered on the network.

35.4.2 Syntax
Type
Set
Read
Test

SyntaxAT+UECALLSTAT=<cmd>
AT+UECALLSTAT?

Response
OK+UECALLSTAT: <state>

ExampleAT+UECALLSTAT=?

OK+UECALLSTAT: (list of supported<cmd>s)

OK+UECALLSTAT: (0-3)+UECALLSTAT: 1

OK

OK

35.4.3 Defined values
Parameter
<cmd>

Type
Number<state>NumberDescription
Allowed values:• 0: force to not valid eCall SIM (not eCall-enabled)• 1: force eCall only with registration restriction• 2: force eCall without registration restriction• 3: restore SIM/USIM settings (read from SIM)
Allowed values:• 0: not valid eCall SIM present (not eCall-enabled)• 1: eCall only with registration restriction• 2: eCall without registration restriction

35.4.4 Notes
TOBY-L4• <cmd>=0 and 2 are not supported.

35.5 eCall and InBM test configuration +UDCONF=90+UDCONF=90
Modules

Attributes

TOBY-L4106
SARA-U201 SARA-U270 LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X LEON-G100-07S
LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

35.5.1 Description
Configures some eCall parameters. It is available in eCall Release 3 and sets the following functionalities:•

eCall test number

UBX-13002752 - R67

35 eCallPage 792 of 1001

u-blox cellular modules - AT commands manual•••

eCall reconfiguration number
T3242 timer duration
T3243 timer duration
eCall settings cannot be stored to NVM to prevent fake SIM usage.

35.5.2 Syntax
Type
SyntaxeCall generic syntax
Set
AT+UDCONF=90,<op_code>,<param1>[,<number>]
Read
AT+UDCONF=90,<op_code>

Response

ExampleOK
AT+UDCONF: 90,<op_code>,<param1>[,<number>]OK

eCall test number
Set
AT+UDCONF=90,1,<ToN>,<number>OK

AT+UDCONF=90,1,129,"02338456"

Read+UDCONF: 90,1,<ToN>,<number>

OK
AT+UDCONF=90,1

OK+UDCONF: 90,1,129,"1234"

AT+UDCONF=90,1

OK
eCall reconfiguration number
Set
AT+UDCONF=90,2,<ToN>,<number>OK

AT+UDCONF=90,2,129,"1234"

Read+UDCONF: 90,2,<ToN>,<number>

OK
AT+UDCONF=90,2

OK+UDCONF: 90,2,129,"1234"

AT+UDCONF=90,2

OK
eCall T3242 timer duration
Set
AT+UDCONF=90,11,<timer_
duration>

OK

AT+UDCONF=90,11,43200

Read+UDCONF: 90,11,<timer_duration>

OK
AT+UDCONF=90,11

OK+UDCONF: 90,11,43200

AT+UDCONF=90,11

OK
eCall T3243 timer duration
Set
AT+UDCONF=90,12,<timer_
duration>

OK

AT+UDCONF=90,12,43200

Read+UDCONF: 90,12,<timer_duration>

OK
AT+UDCONF=90,12

OK+UDCONF: 90,12,43200

AT+UDCONF=90,12OK

35.5.3 Defined values
Parameter<op_code><ToN><number>Type
NumberDescription
Class of eCall/IBM parameter (values lower than 10 corresponds to the USIM settings,
NAD settings otherwise). Allowed values:

Number• 1: eCall test number• 2: eCall reconfiguration number• 11: T3242 timer duration• 12: T3243 timer duration
Specifies the type of address octet <ToN>:

String• 145: international number, i.e. when dialling string starts with '+'• 129: national coded number, otherwise
eCall Test or Reconfiguration number.
•

UBX-13002752 - R67

Number in string format <number>. The default value is "".

35 eCallPage 793 of 1001

u-blox cellular modules - AT commands manual

Parameter<timer_duration>

Type
Number<param1>

NumberDescription
Specifies the 32-bit timer duration defined in seconds. The value 0 is not supported.
The default value is 43200 (12 hours)
Type and supported content depend on the related <op_code> parameter; see the<op_code> specification

35.5.4 Notes•••

If it is not specified with the set command, Test and Reconfiguration numbers are retrieved from FDN or
SDN entries, if the USIM is a valid eCall enabled USIM
If it is specified with the set command, <number> overwrites the USIM eCall Test or Reconfiguration
number retrieved from FDN or SDN entries, if any
If <ToN>= 145, the number specified with <number> shall start with "+"SARA-G3• The test command is not supported.
LEON-G1• The test command is not supported.

35.6 eCall type +UECALLTYPE+UECALLTYPE
Modules
SARA-U201 SARA-U270 LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U260-02S LISA-U270-02S LISA-U270-62S
LISA-U270-63S LISA-U270-68S LISA-U120 LISA-U130
SARA-G340 SARA-G350 LEON-G100-07S LEON-G100-08S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
No
No
+CME Error

35.6.1 Description
Sets the emergency call service category, i.e. the "eCall flag". According to ETSI TS 122 101 [57] and 3GPP
TS 24.008 [12], an eCall can be either Manually Initiated (MIeC, Manually Initiated eCall) or Automatically
Initiated (AIeC, Automatically Initiated eCall), which is configured through specific eCall flag bits. If none ofsuch bits is set, the Mobile Switching Centre (MSC) supporting eCall functionality will operate a speech-only
TS12 emergency call.
The "eCall flag" is included in the call set-up message whenever the emergency number is dialed (with"ATD112;").
This command also configures the system to perform Test or Reconfiguration eCalls, according to 3GPP TS
51.010-1 [60], section 26.9.6a. When performing "ATD112;", the Test or Reconfiguration numbers read from theeCall Test USIM/SIM will be respectively dialed.
The default eCall type (<type_of_eCall>=0) cannot be changed if the USIM is not eCall enabled or if the eCall
status has not been forced to eCall enabled via AT+UECALLSTAT command.
The combination of +UECALLTYPE set command and ATD112; trigges an eCall to the network, and functionallycomplies with the 3GPP eCall initiation command +CECALL.
If the eCall is disabled (see the +UECALLSTAT command), the set command returns the error result code +CME
ERROR: 3 (Operation not allowed).
If the module supports +CECALL AT command, the +UECALLTYPE is set to zero after the eCall of theselected type has been released. This reduces the possibility that eCalls are originated accidentally.
If the module supports +CECALL AT command, the set command with <type_of_eCall> 3 or 4 returns theerror result code +CME ERROR: 1806 if test or reconfiguration numbers are not available or not properly
encoded.

35.6.2 Syntax
Type
Set

SyntaxResponse
AT+UECALLTYPE=<type_of_eCall> OK

UBX-13002752 - R67

35 eCallExamplePage 794 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UECALLTYPE?

Response+UECALLTYPE: <type_of_eCall>

Example+UECALLTYPE: 1

Test

AT+UECALLTYPE=?

OK+UECALLTYPE: (list of supported<type_of_eCall>s)

OK+UECALLTYPE: (0-4)
OKOK

35.6.3 Defined values
Parameter<type_of_eCall>Type
NumberDescription
•
•
•
•
•

0 (factory-programmed value): speech only TS12
1: Emergency Service Category Value (MIeC) (octet 3) Bit 6=1
2: Emergency Service Category Value (AIeC) (octet 3) Bit 7=1
3: Test eCall; use eCall Test number
4: Reconfiguration eCall; use eCall Reconfiguration number

35.6.4 Notes
LISA-U120 / LISA-U130• The command is supported with partial functionality and a limited range for testing purposes only.

35.7 Initiate eCall +CECALL+CECALL
Modules

Attributes

TOBY-L4106
SARA-U201 SARA-U270 LISA-U200-03S LISA-U200-04B LISA-U200-83S LISA-U201
SARA-G340-02S SARA-G340-02X SARA-G350-02A SARA-G350-02S SARA-G350-02X LEON-G1
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

35.7.1 Description
According to ETSI TS 127 007 [64], the set command triggers an eCall to the network. Based on theconfiguration selected, it can be used to either trigger a test call, a reconfiguration call, a manually initiatedeCall or an automatically initiated eCall.
The read command returns the type of eCall currently in progress, if any. If an eCall is not in progress, the readcommand returns the error result code +CME ERROR: 3 (Operation not allowed).
The test command returns the supported values and ranges.
The command behavior depends on whether a valid eCall USIM is used or not.
••Valid eCall USIM: the command fails when the test/reconfiguration calls are started and there is no valid
test/reconfiguration number on the eCall USIM. The +UDCONF=90 command can overwrite the test/
reconfiguration numbers values read from the USIM (see +UDCONF=90, eCall/InBM test configuration).
The +UDCONF=90 values are volatile: they are lost at next power on or reset.
Not Valid eCall USIM: starting an eCall via +CECALL AT command with a not eCall USIM is possible,
provided that the eCall status has been enabled via +UECALLSTAT AT command. In addition, the test andreconfiguration numbers should be provided through +UDCONF=90 command. Otherwise, +CECALL AT
command fails if a test/reconfiguration call is started.

35.7.2 Syntax
Type
Set

SyntaxAT+CECALL=<type_of_eCall>

Response
OK

ExampleAT+CECALL=1

Read

AT+CECALL?

+CECALL: <type_of_eCall>

OK+CECALL: 1

Test

AT+CECALL=?

OK
OK+CECALL: (list of supported <type_ +CECALL: (0-3)
of_eCall>s)

UBX-13002752 - R67

35 eCallPage 795 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

ExampleOK

35.7.3 Defined values
Parameter<type_of_eCall>Type
NumberDescription••••

0: test call
1: reconfiguration call
2: manually initiated eCall (MIeC)
3: automatically initiated eCall (AIeC)

35.7.4 Notes••

The set command is functionally equivalent to the combination of +UECALLTYPE and ATD112.
The set command with <type_of_eCall> 0 or 1 returns the error result code +CME ERROR: 1806 if test orreconfiguration numbers are not available or not properly encoded.

35.8 eCall audio path mode setting +UECALLCFG+UECALLCFG
Modules
Attributes

TOBY-L4106
Syntaxfull

PIN requiredNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

35.8.1 Description
Sets the audio path and profile used for eCall sessions. The audio path and profile switch is done automaticallywhen eCall starts. On eCall session end, the audio path and profile are restored. The setting is stored in NVM
so it can only be done once.
When eCall session is active +USPM command will not show correct information and should not be used.
When the In-Band Modem is enabled by the +UECALLDATA AT command the eCall session becomes active.
The eCall session is active until the In-Band Modem is aborted (either manually using the +UECALLDATA AT
command or on T9 HLAP timer expiry).
The parameters and behaviour of the command for the audio path configuration are the same as for the +USPM
AT command.
Setting of the audio profile parameters inside an eCall session is allowed, but when the session ends the
profile will be restored to the one before the session and all the updated settings will be lost.

35.8.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UECALLCFG=<op_code>,<param1>,<param2>
Read
AT+UECALLCFG=<op_code>

Response

ExampleOK+UECALLCFG: <op_code>,<param1>,<param2>
OK

Path configuration
Set
AT+UECALLCFG="path",<audio_path>,<profile_type>
Read

AT+UECALLCFG="path"

Test

AT+UECALLCFG=?

OK

AT+UECALLCFG="path",0,1

OK+UECALLCFG: "path",<audio_path>, AT+UECALLCFG="path"<profile_type>+UECALLCFG: "path",0,1
OK
OK+UECALLCFG: (list of supported<op_code>s)+UECALLCFG: ("path")
OK

OK

UBX-13002752 - R67

35 eCallPage 796 of 1001

u-blox cellular modules - AT commands manual

35.8.3 Defined values
Parameter<op_code>Type
String<audio_path>

Number<profile_type>

Number<param1>

Number<param2>

NumberUBX-13002752 - R67

Description
Type of operation:• "path": set the eCall configuration path
Specifies the audio path used for an eCall session:• 0 (factory-programmed and default value): analog audio path
• 1: digital audio path
Specifies the profile for the selected audio path:• 0 (factory-programmed and default value): headset profile• 1: hands-free profile• 2: flat profile• 3: custom 0 profile• 4: custom 1 profile
Type and supported content depend on the related <op_code> parameter:• <op_code>=path: type is <audio_path>
Type and supported content depend on the related <op_code> parameter:• <op_code>=path: type is <profile_type>

35 eCallPage 797 of 1001

u-blox cellular modules - AT commands manual236 I C36.1 Introduction

The I2C AT commands support communication with more than one connected device via one of the controllers,
but require opening and closing a logical channel for each connected device. Only one logical channel at a time
can be opened.
The availability and hardware description of the I2C interfaces are out of the scope of this document andare described in a separate document. Refer to the corresponding module System Integration Manual.
The procedure for communicating with two different devices is:• Open the logical channel for device1 (with AT+UI2CO)• Read/write to/from device1 (with AT+UI2CR, AT+UI2CW and +UI2CREGR)• Close the logical channel for device1 (with AT+UI2CC)• Open the logical channel for device2 (with AT+UI2CO)• Read/write to/from device2 (with AT+UI2CR, AT+UI2CW and +UI2CREGR)• Close the logical channel for device2 (with AT+UI2CC)
Once the controller has been configured, it is possible to start I2C communication (read/write) with I2C slave
peripherals.
The I2C controllers available on the u-blox cellular modules module work only in Master Mode so they canbe connected to slave devices only.
In case of a controller/device malfunction, the command's response is only "ERROR".

2

36.2 I C open logical channel +UI2CO+UI2CO
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A TOBY-L200-02S
TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S
TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

36.2.1 Description

Changes the hardware and logical configuration of the selected I2C controller.
It is only possible to configure the I2C controller in Master Mode.
This command selects:• The controller available in the u-blox cellular module• The bus mode type• The bit rate
• The address size (7-10 bit address)• The slave device address
Once the selected controller has been configured, a logical channel between it and the selected slave device is
set up and there is no need to further specify it. All the following I2C write, read and close commands refer tothe currently opened logical channel. It is not possible to use the I2C write, read and open commands for writing
or reading to/from a different slave device without first closing the I2C logical channel.

UBX-13002752 - R67

36 I2C

Page 798 of 1001

u-blox cellular modules - AT commands manual

36.2.2 Syntax
Type
Set

Test

SyntaxResponse
AT+UI2CO=<I2C_controller_OK
number>,<bus_mode>,<bit_rate>,<device_address>,<address_width>
AT+UI2CO=?
+UI2CO: (list of supported <I2C_
controller_number>s),(list of
supported <bus_mode>s),(list of
supported <bit_rate>),(<device_address> range),(list of supported<address_width>s)

ExampleAT+UI2CO=1,0,0,0x42,0
OK+UI2CO: (1),(0-1),(0-1),(0x000-0x3FF),(0-1)
OKOK

36.2.3 Defined values
Parameter<I2C_controller_
number>Type
Number<bus_mode>

Number<bit_rate>

Number<device_address>

Hex number<address_width>

NumberDescription
I2C HW controller to use:
• 1: controller 1
I2C bus mode type:• 0: Bus Mode Standard (0 - 100 kbaud)• 1: Bus Mode Fast (0 - 400 kbaud)
I2C bit rate:• 0: 100 kb/s
• 1: 400 kb/s
Device address in HEX format• TOBY-L4 / TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - The range goesfrom 0x0000 to 0xFFFF.
I2C size of the controller address:• 0: 7 bit address• 1: 10 bit address

36.2.4 Notes
LARA-R211• In case the AUX UART (not supported by LARA-R211-02B-00, LARA-R211-02B-01 and LARA-R211-02B-02)
is enabled (that is the active +USIO variant is 2,4,5 or 6), since the I2C lines are not available, the command
immediately provides an error result code in case of <mode> set to 1 ("+CME ERROR: 3" if +CMEE=1 or"+CME ERROR: operation not allowed" if +CMEE=2).
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X• In case the AUX UART is enabled (that is the active +USIO variant is 4,5 or 6), since the I2C lines are notavailable, the command immediately provides an error result code in case of <mode> set to 1 ("+CME
ERROR: 3" if +CMEE=1 or "+CME ERROR: operation not allowed" if +CMEE=2).

236.3 I C write to peripheral +UI2CW+UI2CW
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A TOBY-L200-02S
TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S
TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

36.3.1 Description

Writes the HEX data to the I2C slave device of the current logical channel. The HEX data formats are without
0x prefix (see example).

UBX-13002752 - R67

36 I2C

Page 799 of 1001

u-blox cellular modules - AT commands manual

36.3.2 Syntax
Type
Set

SyntaxResponse
AT+UI2CW=<hex_data>,<nof_byte_ OK
to_write>

ExampleAT+UI2CW="0011AABBCCDDEEFF",
8

Test

AT+UI2CW=?

OK+UI2CW: "data", (1-100)+UI2CW: (byte to write),(range of
supported <nof_byte_to_write>)OKOK

36.3.3 Defined values
Parameter<hex_data>

Type
String<nof_bytes_to_write>

NumberDescription
Hex data sequence without prefix 0x, enclosed in double quotes, to be written to the
I2C slave device
Number of byte to write to the slave I2C device. Range: 1-100

236.4 I C read from peripheral +UI2CR+UI2CR
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A TOBY-L200-02S
TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S
TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

36.4.1 Description

Reads <nof_bytes_to_read> of data from the I2C slave device of the current logical channel and prints them in
HEX format in separate rows.

36.4.2 Syntax
Type
Read

Test

SyntaxAT+UI2CR=<nof_bytes_to_read>

AT+UI2CR=?

Response+UI2CR: <index_1>: <byte_1>

ExampleAT+UI2CR=3[+UI2CR: <index_n>: <byte_n>+UI2CR: 0: 0xA3[..]]

+UI2CR: 1: 0x0F

OK

+UI2CR: 2: 0xDB

+UI2CR: (list of supported <nof_byte_to_read>s)OK+UI2CR: (1-100)
OKOK

36.4.3 Defined values
ParameterType<nof_bytes_to_read> Number<index1>,...,<index_ Numbern><byte_1>,...,<byte_n> Number

UBX-13002752 - R67

Description
Number of bytes to read from the slave I2C device:• TOBY-L4 / TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - The range goesfrom 1 to 100.
Index of the byte being printed.
n-th byte of the data, in hex mode (unquoted, prefixed by 0x).

36 I2C

Page 800 of 1001

u-blox cellular modules - AT commands manual236.5 I C read from peripheral register +UI2CREGR+UI2CREGR
Modules

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A TOBY-L200-02S
TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S
TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

Attributes

36.5.1 Description

Reads <nof_bytes_to_read> of data from the slave register of the I2C slave device of the current logical channel
and prints them in HEX format in separate rows.

36.5.2 Syntax
Type
Read

SyntaxResponse
AT+UI2CREGR=<register_address>, +UI2CREGR: <index_1>: <byte_1><nof_bytes_to_read>[+UI2CREGR: <index_n>: <byte_n>

Test

AT+UI2CREGR=?

ExampleAT+UI2CREGR=0x42,3+UI2CREGR: 0: 0xA3[..]]

+UI2CREGR: 1: 0x0F

OK

+UI2CREGR: 2: 0xDB

+UI2CREGR: (list of supported<register_address>s),(list of
supported <nof_bytes_to_read>s)OK+UI2CREGR: (0x00-0xFF),(1-100)
OKOK

36.5.3 Defined values
ParameterType<register_address> Number<nof_bytes_to_read> Number<index1>,...,<index_ Numbern><byte_1>,...,<byte_n> Number

Description
Device address in HEX format
Number of bytes to read from the slave I2C register.
• TOBY-L4 / TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - The range goesfrom 1 to 100.
Index of the byte being printed.
n-th byte of the data, in hex mode (unquoted, prefixed by 0x).

2

36.6 I C close logical channel +UI2CC+UI2CC
Modules

Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A TOBY-L200-02S
TOBY-L200-03A TOBY-L200-03S TOBY-L210-02S TOBY-L210-03A TOBY-L210-03S TOBY-L210-62S
TOBY-L210-65S TOBY-L220 TOBY-L280
LARA-R2 TOBY-R2
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

36.6.1 Description

Closes the I2C logical channel being used.
The logical channel must be closed before opening a new one.

UBX-13002752 - R67

36 I2C

Page 801 of 1001

u-blox cellular modules - AT commands manual

36.6.2 Syntax
Type
ActionSyntaxAT+UI2CC

Response
OK

ExampleAT+UI2CC

Test

AT+UI2CC=?

OK

OK
OK

UBX-13002752 - R67

36 I2C

Page 802 of 1001

u-blox cellular modules - AT commands manual

37 SAP
37.1 Introduction
The SIM Access Profile (SAP) allows communication between a device electrically connected to a SIM module(SAP Server) and a device using that SIM (SAP Client). The SAP details are specified in the BluetoothSpecification "SIM Access Profile - Interoperability Specification" [67].
u-blox modules support SAP client functionalities using a serial connection to transport the SAP messages
defined in the SAP specification: in SAP Client mode, the u-blox cellular module uses a remote SIM, whichis physically present in the SAP server, to perform all SIM-related operations; the local SIM card, directly
connected to the module (U)SIM interface, is not accessed.
At power on SAP is disabled in the u-blox cellular module i.e. the local SIM card (directly connected to the module(U)SIM interface) is used. It is possible to enter SAP client mode and switch to using a remote SIM via AT
commands. At any time, either the local or remote SIM is exclusively used; this is transparent to AT clients: forexample when interrogating the IMSI with +CIMI, the result always refers to the "current" SIM: the local SIM's
IMSI if SAP is not active or the remote SIM's IMSI if SAP Client mode is active.
URCs are provided to inform the user about the state of both local and remote SIM when SAP mode is active:••

The +UUSAPREMOTE URC reports information related to the "remote" SIM
The +UUSAPLOCAL URC reports information related to the local SIM card directly connected to the module(U)SIM interface
For more details see Chapter 37.3.
Table 91 shows which indications are to be expected in case of local or remote SIM events (hot removal/
insertion):
Event
Local SIM removal/insertion
Remote SIM removal/insertion

SAP client not active+CIEV: 12,<value>-

SAP client active+UUSAPLOCAL: <sim_present>+UUSAPREMOTE: <sim_present>

Table 91: SIM indications and SAP
For further details about SAP implementation, see the corresponding module system integration manual.
u-blox cellular modules do not act as SAP server.

37.2 SAP mode activation +USAPMODE+USAPMODE
Modules

Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A TOBY-L280-03S
MPCI-L200-03S MPCI-L210-03S MPCI-L280-03S
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

37.2.1 Description
Configures the SAP connection mode:• Local SIM: the local SIM is used, the SAP is not active• SAP client: the module acts as an SAP client, a remote SIM is used
It is not possible to change the SAP mode during a call or with an active PDP context.
When entering the SAP client mode, the SAP communication takes place in a separate dedicated serial
channel, according to the <format> indication (currently only binary mode is supported).
The command can only be invoked from a USB or a MUX AT channel.
When invoked from a USB channel, the dedicated serial channel for SAP is USB channel.

UBX-13002752 - R67

37 SAP

Page 803 of 1001

u-blox cellular modules - AT commands manual

When invoked from a MUX channel, the dedicated serial channel for SAP is MUX channel.
TOBY-L2 / MPCI-L2
The SAP MUX channel is not available.
The SAP client mode can be activated only if the AT+UUSBCONF configuration is set to 0, 12 or 13.
The communication between SAP client and server follows the "Connect" procedure (as specified by SAP
specification [54]), which uses the <beacon> parameter.
The actual switch between local and remote SIM takes place only when a connection has been establishedbetween SAP client and the SAP server. The value of the SAP mode returned by the read command does notchange as long as the connection is active.
The SAP client mode terminates when:• The SAP connection fails (communication lost, unrecoverable error, unsuccessful connect negotiation)• The SAP server commands a disconnection• The AT command to move back to local SIM mode is received
The SAP client mode activation may result in an error result code if an SAP connection cannot be established.
See the Appendix A.1 for the allowed error result codes.

37.2.2 Syntax
Type
Set

SyntaxAT+USAPMODE=<sap_mode>[,<format>[,<beacon>]]Response
OK

Read

AT+USAPMODE?

+USAPMODE: <sap_mode>

Test

AT+USAPMODE=?

ExampleAT+USAPMODE=0
OK
AT+USAPMODE=1,0,6

OK+USAPMODE: (list of supported<sap_mode>s),(list of supported<format>s),(list of supported<beacon>s)

OK+USAPMODE: 0
OK+USAPMODE: (0,1),0,(0-65535)
OKOK

37.2.3 Defined values
Parameter<sap_mode>

Type
Number<format>Number<beacon>NumberDescription
Specifies the SAP mode. Allowed values:• 0 (default value): internal SIM (SAP disabled)• 1: SAP client
Specifies the SAP communication format. This parameter can be set only if <sap_mode> is 1 or 2. Allowed values:• 0 (default value): binary; SAP messages are exchanged transparently in binary
formatPeriod in seconds between consecutive CONNECT_REQ messages during the"Connect" procedure. This parameter can be set only if <sap_mode>= 1. 0 means one
shot sending. The default value is 6 s. The allowed range is [0-65535].

37.2.4 Notes
TOBY-L200-03A / TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03A /TOBY-L280-03S / MPCI-L200-03S / MPCI-L210-03S / MPCI-L280-03S• The AT+CFUN=15 command issued in the SAP client mode (+USAPMODE: 1) will disable the remote SIM
connection and restart the protocol stack on the local SIM card.
• The AT+CFUN=19 command shall not be issued in the SAP client mode (+USAPMODE: 1); the command
can be used in the local SIM mode (+USAPMODE: 0) only.
• The SAP client mode shall not be activated if the local SIM card has been disabled (i.e. in +CFUN: 19).
SARA-U2 / LISA-U2• The AT+CFUN=15 command shall not be issued in the SAP client mode (+USAPMODE: 1).

UBX-13002752 - R67

37 SAP

Page 804 of 1001

u-blox cellular modules - AT commands manual

37.3 SAP mode indications +USAPIND+USAPIND
Modules

Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A TOBY-L280-03S
MPCI-L200-03S MPCI-L210-03S MPCI-L280-03S
SARA-U2 LISA-U200-01S LISA-U200-02S LISA-U200-03S LISA-U200-04B LISA-U200-52S
LISA-U200-62S LISA-U200-83S LISA-U201 LISA-U230 LISA-U260 LISA-U270
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

37.3.1 Description
Enables or disables the URCs generation for the SAP mode status change indication (+UUSAPMODE) and thedetection of a local SIM (+UUSAPLOCAL) when SAP client is active.
At the module power-up, the URCs are disabled.

37.3.2 Syntax
Type
Set

SyntaxAT+USAPIND=<ind_mode>

Response
OK

ExampleAT+USAPIND=0

ReadAT+USAPIND?

+USAPIND: <ind_mode>

OK+USAPIND: 0

Test

AT+USAPIND=?

OK+USAPIND: (list of supported <ind_mode>s)OK+UUSAPMODE: <sap_mode>+UUSAPLOCAL: <sim_present>

URC
URC

OK
+USAPIND: (0,1)
OK+UUSAPMODE: 0+UUSAPLOCAL: 0

37.3.3 Defined values
Parameter<ind_mode>

Type
Number<sap_mode>

Number<sim_present>

NumberDescription
Specifies whether SAP-related URCs are enabled or disabled. Allowed values:• 0 (default value): disabled• 1: enabled
Specifies which SAP mode is currently used. Allowed values:• 0 (default value): internal SIM (SAP disabled)• 1: SAP client• 2: SAP server
Specifies the status of locally attached SIM. Allowed values:• 0: local SIM is present• 1: local SIM is not present

37.3.4 Notes•

The +UUSAPMODE: 0 URC is issued in case of a disconnection between SAP client and server. After any
request if no response is received within 15 s, the SAP client is closed, the +UUSAPMODE: 0 URC is issued
and the module switches to the local SIM.

UBX-13002752 - R67

37 SAP

Page 805 of 1001

u-blox cellular modules - AT commands manual

38 Networking
38.1 System networking modes
38.1.1 TOBY-L4 / TOBY-L2 / MPCI-L2 Router mode
In router mode, the IP termination of each packet data context is on the module, which acts as a router. The
DTE will send its packet to the module which will then use its routing table to perform the routing of the packet
over the right context.
The DHCP server can be configured within +UIPCONF AT command. The DHCP server will provide to theconnected hosts the configuration of the private network provided by the module. Only the IPv4 address isallowed.
TOBY-L2 / MPCI-L2
For more details on the router mode configuration, see the +UBMCONF AT command.
38.1.1.1 IPv4
• The DTE will configure its DHCP client over its virtual Ethernet interface and it will assign a private IP and
DNS configuration. No public IP address is assigned• The DTE will access the packet data network using the NAT procedure• For each active packet data context the module creates an internal IP interface• In case of multiple packet data contexts (each with an assigned IP address), the module will apply thefollowing routing rules by checking destination IP address of each uplink packet:
o If the address belongs to the IP subnet of one of the active contexts, then the packet will be sent overthat linko In all other cases, the packet will be sent over the context which has been activated first (i.e. the default
gateway)
In case of multiple contexts the first activated context should be the one associated to the public Internet.
38.1.1.2 IPv6
TOBY-L200 / TOBY-L210 / TOBY-L220 / TOBY-L280 / MPCI-L200 / MPCI-L210 / MPCI-L220 / MPCI-L280
The IPv6 protocol is not supported in router mode.
TOBY-L201 / MPCI-L201
The IPv6 in router mode is supported only in Verizon configuration. In this configuration only one data
default bearer with IPv6 addressing is supported. See +UMNOCONF for further details.
TOBY-L4
IPv6 is not supported.
In general terms, the global connectivity configuration of the network node shall be performed automaticallyby the IPv6 network through the use of IPv6 Neighbor Discovery Protocol (NDP).
If the mobile network supports the IPv6 auto-configuration then the following steps are performed:• The Router Advertisement (RA) sent from the mobile network is forwarded to the USB virtual Ethernet
interface of the DTE. The Router Advertisement holds the prefix of the activated default bearer.
• The DTE processes the RA message and configures its global address and its routing rules. If the procedure
is correctly completed then the host is provided with a global IPv6 address and with the IPv6 address (global
or local) of the next-hop router.
• Optionally the RA message can provide DNS server addresses. If present then the DTE shall apply the DNS
configuration, otherwise the DTE should perform manual configuration.

38.1.2 TOBY-L2 / MPCI-L2 Bridge mode
In bridge mode, the IP termination of each context is on the DTE. The module will act as a bridge and forward
the IP packets based on the source address.
The DHCP server can be set by means of the the parameters +UBMCONF <bridge_dhcp_server> and <dhcp_
cid> parameters. The DHCP server in bridge mode will be activated only on the <dhcp_cid>. At the EPS bearer/

UBX-13002752 - R67

38 Networking

Page 806 of 1001

u-blox cellular modules - AT commands manual

PDP context activation the module will receive the IP configuration from the cellular network. It will use thereceived IP configuration to properly set the parameters of the DHCP server. The host will receive within
the DHCP protocol the correct configuration to obtain connectivity. The IP configuration consists of the IP
address of the activated EPS bearer/PDP context, the IP address of the gateway needed by the host to set theconnectivity, and the list of DNS servers provided by the cellular network (additionally a fallback DNS server isprovided). After the PDP context activation it is suggested for the DTE to perform a DHCP request to obtainthe updated IP configuration.
The user must set the right source address in the IP headers to drive the module's routing over the rightcontext.
For more details on the bridge mode configuration, see the +UBMCONF AT command.
38.1.2.1 IPv4
• The module does not run any DHCP/DNS server and it does not perform any NAT procedure• The routing over multiple contexts is done by the module by source IP detection• For each active context the module creates an IP interface (which takes care of replying to ARP requests);
the IP address of such interface can be retrieved via the +UIPADDR AT command• For each active context the DTE should manually configure its USB virtual ethernet interface in order too Retrieve the associated public IP address via the +CGDCONT AT command and assign it as IP alias
o Retrieve the module's local configuration of the bridged interface (IP address and subnet mask) with the+UIPADDR AT command and add the required routing rules• The module will perform routing over contexts using the IP alias set by the DTE
38.1.2.2 IPv6
In general terms, the global connectivity configuration of the network node shall be performed automaticallyby the IPv6 network through the use of IPv6 Neighbor Discovery Protocol (NDP).
•••The DTE will create its own link local address for the virtual Ethernet interface
The module will do the same. Its address can be retrieved with the +UIPCONF AT command
For each active context the module will not create any virtual interface
o The DTE will receive RA (Routing Advertisement) messages and it will be able to configure its global
addresso The module will perform routing over contexts using the IP alias set by the DTE
The DTE should prevent the transmission of any NS (Neighbor Solicitment).

38.2 Change the boot mode configuration +UBMCONF+UBMCONF
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
partialNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

38.2.1 Description
Changes the system networking mode and configures the DHCP service in bridge mode. The chosenconfiguration is stored in NVM and will be applied after a reboot.
For more details on the networking architecture, see the System networking modes section.
The PPP with IPv6 is not supported.
The configuration can be reverted to its factory-programmed value with AT+UBMCONF=.

38.2.2 Syntax
Type
Set

SyntaxAT+UBMCONF=[<networking_mode>[,<bridge_dhcp_server>[,<dhcp_cid>]]]UBX-13002752 - R67

Response
OK

ExampleAT+UBMCONF=1
OK

38 Networking

Page 807 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UBMCONF?

Test

AT+UBMCONF=?

Response
Example+UBMCONF: <networking_mode>[, +UBMCONF: 1<bridge_dhcp_server>,<dhcp_cid>]
OK
OK+UBMCONF: (list of supported+UBMCONF: (1-2),(0,1),(1-8)<networking_mode>s)[,(list ofOKsupported <bridge_dhcp_server>s),(list of supported <dhcp_cid>s)]OK

38.2.3 Defined values
ParameterType<networking_mode> Number<bridge_dhcp_
server>Number<dhcp_cid>

NumberDescription
Networking operating mode of the RNDIS interface:• 1 (default and factory-programmed value): router mode
• 2: bridge mode
For more details, see System networking modes.
DHCP server configuration:• 0 (default and factory-programmed value): disabled• 1: enabledThis parameter is ignored for <networking_mode>=1.
Context identifier (CID) used by the DHCP server: the default and factoryprogrammed value for the preferred CID is 4. This parameter is ignored for<networking_mode>=1.

38.2.4 Notes
TOBY-L200-00S / TOBY-L200-02S / TOBY-L201 / TOBY-L210-00S / TOBY-L210-02S / TOBY-L210-60S /TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S / MPCI-L2• The <bridge_dhcp_server> and <dhcp_cid> parameters are not supported.
TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S• The <bridge_dhcp_server> and <dhcp_cid> parameters are not supported by TOBY-L200-03S-00,
TOBY-L210-03S-00, TOBY-L210-03A-00, TOBY-L280-03S-00.

38.3 Configure the Ethernet over USB IP network +UIPCONF+UIPCONF
Modules
Attributes

TOBY-L4 TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

38.3.1 Description
Configures the IPv4 network of the Ethernet over USB interfaces. The user can configure the module's IPv4
address, subnet mask, DHCP server's IPv4 address range.
The changes are stored in NVM and they need a reboot to be applied.
The user should manually renew the DHCP configuration (host side) if any change is made to the DHCP server
configuration.
The DHCP configuration will be ignored when operating in bridge mode.
The configuration can be reverted to its factory-programmed values with AT+UIPCONF=.

38.3.2 Syntax
Type
Set

SyntaxResponse
AT+UIPCONF=[<ipv4_address>,OK<subnet_mask>,<dhcp_ipv4_start>,<dhcp_ipv4_end>[,<dhcp_status>]]UBX-13002752 - R67

38 Networking

ExampleAT+UIPCONF="192.168.2.1","255.255.255.0","192.168.2.100","192.168.2.100",0Page 808 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Read

AT+UIPCONF?

Test

AT+UIPCONF=?

ExampleOK+UIPCONF: <ipv4_address>,+UIPCONF: "192.168.1.1",<subnet_mask>,<dhcp_ipv4_start>, "255.255.255.0","192.168.1.10<dhcp_ipv4_end>,<ipv6_link_local_ 0","192.168.1.100","FE80
address>[,<dhcp_status>]::58FC:54FF:FE00:CB45/64",1OK+UIPCONF:OK+UIPCONF:

OK

OK

38.3.3 Defined values
Parameter<ipv4_address>

Type
String<subnet_mask>

String<dhcp_ipv4_start>

StringDescription
Private IPv4 address of the Ethernet over USB interface. The IPv4 address consists of
4 octets: "ddd.ddd.ddd.ddd":• TOBY-L4 - The default and factory-programmed value is 192.168.2.16.
• TOBY-L2 / MPCI-L2 - The default and factory-programmed value is "192.168.1.1".
The subnet mask consists of 4 octets: "ddd.ddd.ddd.ddd". The default and factoryprogrammed value is "255.255.255.0".
DHCP IPv4 start of address range.

StringThe IPv4 address consists of 4 octets: "ddd.ddd.ddd.ddd":• TOBY-L4 - The default and factory-programmed value is "192.168.2.100"• TOBY-L2 / MPCI-L2 - The default and factory-programmed value is "192.168.1.100"
DHCP IPv4 end of address range.

<dhcp_ipv4_end><ipv6_link_local_
address>

String<dhcp_status>

NumberThe IPv4 address consists of 4 octets: "ddd.ddd.ddd.ddd":• TOBY-L4 - The default and factory-programmed value is 192.168.2.150• TOBY-L2 / MPCI-L2 - The default and factory-programmed value is "192.168.1.100"
Link Local IPv6 address of the Ethernet over USB. It consists of 8 groups of four
hexadecimal digits representing 2 octets. The groups are separated by colons.
Leading zero suppression and zero compression maybe applied. The network prefix iswritten in CIDR notation, by appending a slash and the needed decimal digits to the
IPV6 address.
Manage the embedded DHCP server status; allowed values:• 0: DHCP server disabled• 1: DHCP server enabled
The default and factory-programmed value is 1.

38.3.4 Notes•

The <dhcp_ipv4_start> and <dhcp_ipv4_end> parameters must belong to the virtual Ethernet interface's
IPv4 subnet.

TOBY-L2 / MPCI-L2• The <dhcp_status> parameter is not supported.

38.4 Interface configuration +UIFCONF+UIFCONF
Modules
Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
partial
No
NVM
No
-

Error reference+CME Error

38.4.1 Description
Configures the IP settings of a network interface (except for the cellular network interfaces). The settings are
related to the configuration of the IP address, network mask, DHCP server service, and of the AT interface overthe IP connection. The command can be used to retrieve the MAC address and the operating system interface
name.
The changes are stored in NVM and they need a reboot to be applied.

UBX-13002752 - R67

38 Networking

Page 809 of 1001

u-blox cellular modules - AT commands manual

38.4.2 Syntax
Type
SyntaxResponse
Generic syntax
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK<cmd_tag>[,< ... cmd_specific_
params ... >]Read
AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: [< ... cmd_specific_<cmd_tag>[,< ... cmd_specific_
params ... >]params ... >]OKInterface status configuration
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
0,<interface_status>
Read

ExampleAT+UIFCONF=0,0,1,0,"192.168.1.1"
OK
AT+UIFCONF=0,0,1,0+UIFCONF: "125.24.51.133"
OK
AT+UIFCONF=1,0,0,1

AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_status>
0
OK

OK
AT+UIFCONF=1,0,0+UIFCONF: 1
OKInterface IPv4 address configuration
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
1,0,<interface_IP_address>
Read

AT+UIFCONF=1,0,1,0,"192.168.90.60"

OK
AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_IP_address> AT+UIFCONF=1,0,1,0
1,0OK+UIFCONF: "192.168.90.60"
OKInterface IPv4 netmask configuration
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
1,1,<interface_IP_netmask>
Read

AT+UIFCONF=1,0,1,1,"255.255.255.0"

OK
AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_IP_netmask> AT+UIFCONF=1,0,1,1
1,1
OK+UIFCONF: "255.255.255.0"
OKInterface IPv4 configuration apply
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
1,100

AT+UIFCONF=1,0,1,100
OKInterface IPv4 DHCP server status configuration
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
3,0,<interface_DHCP_server_
status_conf>
Read
AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_DHCP_
3,0
server_status_conf>
OK

AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_DHCP_
3,1
server_range_begin_conf>
OK

AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_DHCP_
3,2
server_range_end_conf>
OK

UBX-13002752 - R67

AT+UIFCONF=1,0,3,0+UIFCONF: 1

AT+UIFCONF=1,0,3,1,"192.168.90.10
0"OK
AT+UIFCONF=1,0,3,1+UIFCONF: "192.168.90.100"
OKInterface IPv4 DHCP server range end configuration
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
3,2,<interface_DHCP_server_range_
end_conf>
Read

OK

OK

Interface IPv4 DHCP server range begin configuration
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
3,1,<interface_DHCP_server_range_
begin_conf>
Read

AT+UIFCONF=1,0,3,0,1

AT+UIFCONF=1,0,3,2,"192.168.90.150"
OK
AT+UIFCONF=1,0,3,2+UIFCONF: "192.168.90.150"
OK

38 Networking

Page 810 of 1001

u-blox cellular modules - AT commands manualType
SyntaxResponse
Interface IPv4 DHCP server configuration apply
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
3,100
AT interface over an IP connection configuration
Set
AT+UIFCONF=<iftype>,<ifnumber>, OK
90,<terminal_id>[,<tcp_control_
port>,<tcp_data_port>]
Read
AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <tcp_control_port>,
90,<terminal_id><tcp_data_port>
OK

ExampleAT+UIFCONF=1,0,3,100
OK
AT+UIFCONF=1,0,90,0,56090,56091
OK
AT+UIFCONF=1,0,90,0+UIFCONF: 56090,56091
OKInterface MAC address configuration
Read
AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_MAC_
98
address>OK

AT+UIFCONF=1,0,98+UIFCONF: "56:1F:5A:C9:90:E1"
OKInterface name configuration
Read
AT+UIFCONF=<iftype>,<ifnumber>, +UIFCONF: <interface_name>99
OK

AT+UIFCONF=1,0,99+UIFCONF: "eth0"OK38.4.3 Defined values
Parameter<iftype>Type
Number<ifnumber><cmd_tag>

NumberNumber<interface_status>

Number<interface_IP_
Stringaddress><interface_IP_
Stringnetmask><interface_DHCP_
Numberserver_status_conf><interface_DHCP_
Stringserver_range_begin_conf><interface_DHCP_
Stringserver_range_end_
conf><interface_apply_
Numberconf><terminal_id>
Number<tcp_control_port>

UBX-13002752 - R67

NumberDescription
Interface type identifier:• 0: NCM• 1: ETH
Interface number identifier
Command tag:
• 0: interface status• 1: IPv4 configuration• 3: IPv4 DHCP configuration• 90: AT interface over an IP connection• 98: interface MAC address• 99: interface nameInterface status. Allowed values:• 0: disabled• 1 (factory-programmed value): enabledInterface IPv4 address. The factory-programmed value depends on the module and of
the interface. For IP address format reference see the IP addressing.
Interface IPv4 network mask. The factory-programmed value depends on the moduleand of the interface. For IP address format reference see the IP addressing.
Interface IPv4 DHCP server status configuration. The allowed values are:
• 0: disabled• 1 (factory-programmed value): enabled
The first IPv4 address of the interface DHCP server range. The factory-programmed
value depends on the module and of the interface. For IP address format reference
see the IP addressing.
The last IPv4 address of the interface DHCP server range. The factory-programmed
value depends on the module and of the interface. For IP address format reference
see the IP addressing.
The value 100 is used to apply the configuration run-time without any power cycle.
Identifier of the AT terminal over the IP interface. The factory-programmed value
depends on the module and of the interface.
TCP control port number of the AT interface over an IP connection. The factoryprogrammed value depends on the module and of the interface.

38 Networking

Page 811 of 1001

u-blox cellular modules - AT commands manual

Parameter<tcp_data_port>

Type
Number<interface_MAC_
address><interface_name>

StringDescription
TCP data port number of the AT interface over an IP connection. The factoryprogrammed value depends on the module and of the interface.
Physical MAC address of the interface.

StringOperating system interface name.

38.4.4 Notes
TOBY-L4• For <iftype>=0 (NCM) and <iftype>=1 (ETH) only <ifnumber>=0 is supported.
• For <iftype>=0 the <interface_status>=0 and <cmd_tag>=0 are not applicable.
• For <cmd_tag>=90 only <terminal_id>=0 is supported.
• For <cmd_tag>=90 and <terminal_id>=0 <tcp_control_port> and <tcp_data_port> are applicable only for<iftype>=0 (ETH).
• <interface_apply_conf>=100 is not supported.
• Table 92 provides the factory-programmed setting for the supported TOBY-L4 interfaces:<interface_name><iftype><ifnumber><interface_status><interface_DHCP_server_status_conf><interface_IP_address><interface_IP_netmask><interface_DHCP_server_range_begin_conf><interface_DHCP_server_range_end_conf><tcp_control_port><tcp_data_port>

•

usb0
0
0
1
1
192.168.2.16
255.255.255.0
192.168.2.100
192.168.2.150
-

eth0
1
0
1
1
192.168.90.60
255.255.255.0
192.168.90.100
192.168.90.150
50950
50951

Table 92: TOBY-L4 factory-programmed setting
Here below is reported an example of how to configure the Ethernet interface. The <iftype> for the
Ethernet interface is equal to 1, while the <ifnumber> is equal to 0.
Command
Response
Get the current Ethernet configuration
AT+UIFCONF=1,0,0+UIFCONF: 1

Description
Get the status of the interface.

AT+UIFCONF=1,0,1,0

OK+UIFCONF: "192.168.90.60"

Get the IP address of the interface.

AT+UIFCONF=1,0,1,1

OK+UIFCONF: "255.255.255.0"

Get the netmask of the interface.

AT+UIFCONF=1,0,3,0

OK+UIFCONF: 1

AT+UIFCONF=1,0,3,1

OK+UIFCONF: "192.168.90.100"

AT+UIFCONF=1,0,3,2

OK+UIFCONF: "192.168.90.150"

AT+UIFCONF=1,0,90,0

OK+UIFCONF: 56090,56091
OK

Set the new Ethernet configuration
AT+UIFCONF=1,0,1,0,"192.168.100.1"

OK

AT+UIFCONF=1,0,1,1,"255.255.255.0"

OK

AT+UIFCONF=1,0,3,1,"192.168.100.2"

OK

UBX-13002752 - R67

Get the status of the DHCP serverof the interface.
Get the DHCP server range beginof the interface.
Get the DHCP server range end of
the interface.
Get the AT interface over an IP
connection configuration.
Set the new IP address of theinterface.
Set the new netmask of theinterface.
Set the new DHCP server range
begin of the interface.

38 Networking

Page 812 of 1001

u-blox cellular modules - AT commands manual

Command
Response
AT+UIFCONF=1,0,3,2,"192.168.100.100" OK
AT+UIFCONF=1,0,90,0,60000,60001

OK

Description
Set the new DHCP server range
end of the interface.
Set the AT interface over an IP
connection configuration.
Reboot the device to apply theconfiguration. After the reboot the
Ethernet interface is configured
with 192.168.100.1/24 IP address.
The DHCP server will provide
addresses in the range 192.168.10
0.2-192.168.100.100. The AT over
Ethernet console is available at theport 60000 of the IP 192.168.100.1.

38.5 Get the USB IP configuration +UIPADDR+UIPADDR
Modules
Attributes

TOBY-L4 TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

38.5.1 Description
Returns the current USB IP configuration for the requested active <cid> based on the current networking
mode (for more details, see the System networking modes section). If the <cid> parameter is omitted, theinformation text response will display all the active <cid>s.
The module does not create any virtual interface for an active IPv6 <cid> in bridge mode. The IPv6 configuration
session is performed between the DTE and the network. In this case the <cid> will not be reported asconfigured.
TOBY-L4
The bridge mode is not supported.

38.5.2 Syntax
Type
Set

SyntaxAT+UIPADDR=[<cid>]Response
Example+UIPADDR: <cid>,<if_name>,<ipv4_ See Examples
address>,<subnet_mask>,<ipv6_
global_address>,<ipv6_link_local_
address>
[...]

Test

AT+UIPADDR=?

OK+UIPADDR: (list of <cid>'s active
virtual device)+UIPADDR: 1,2
OKOK

38.5.3 Defined values
Parameter
<cid>

Type
Number<if_name><ipv4_address>

StringString<subnet_mask>

String<ipv6_global_
address>

StringUBX-13002752 - R67

Description
Active context. By default the active <cid> is reported. If the <cid> parameter isomitted, all the active <cid>s are reported.
Interface name. For more details on interface nomenclature, see Notes.
IPv4 address of the interface. The IPv4 address consists of 4 octets:"ddd.ddd.ddd.ddd". The default value is "192.168.1.1".
The subnet mask consists of 4 octets: "ddd.ddd.ddd.ddd". The default value is"255.255.255.0".
Global IPv6 address of the interface. It consists of 8 groups of four hexadecimal digits
representing 2 octets. The groups are separated by colons. Leading zero suppression
and zero compression maybe applied. The network prefix is written in CIDR notation,
by appending a slash and the needed decimal digits to the IPv6 address.

38 Networking

Page 813 of 1001

u-blox cellular modules - AT commands manual

Parameter<ipv6_link_local_
address>

Type
StringDescription
Link Local IPv6 address of the interface. It consists of 8 groups of four hexadecimal
digits representing 2 octets. The groups are separated by colons. Leading zero
suppression and zero compression maybe applied. The network prefix is written
in CIDR notation, by appending a slash and the needed decimal digits to the IPv6
address.

38.5.4 Notes•

If the requested <cid> is not active the command will reply with an error result code.

TOBY-L4006 / TOBY-L4106 / TOBY-L4206 / TOBY-L4906-01A / TOBY-L4906-51A• The <cid> parameter is mandatory.
• In the router mode the interface name (see the <if_name> parameter) is "inm(x)", where:o The "inm(x)" is the name of the Linux network interface mapped to an activated PDP context.
o The x parameter is in the range from 0 to 7.
o Example: "inm0" interface is mapped to the PDP context with CID 1.
TOBY-L4906-50A• The <cid> parameter is mandatory.
• In the router mode the interface name (see the <if_name> parameter) is "inm(x)", where:o The "inm(x)" is the name of the Linux network interface mapped to an activated PDP context.
o The x parameter is in the range from 0 to 3.
o Example: "inm0" interface is mapped to the PDP context with CID 1.
TOBY-L2 / MPCI-L2• In the router mode the interface name (see the <if_name> parameter) is "ccinetd", where d is a decimal
digit.
• In the bridge mode the interface name (see the <if_name> parameter) is "usb0:d", where d is a decimal
digit.

38.5.5 Examples
TOBY-L4
Description
CommandRouter mode (IPv4 context) AT+UIPADDR=1

Response+UIPADDR: 1,"inm0","5.168.120.13","255.255.255.0","",""

Wrong CID

OK
ERROR

AT+UIPADDR=4

TOBY-L2 / MPCI-L2
Description
CommandRouter mode (IPv4 context) AT+UIPADDR=1

Response+UIPADDR: 1,"ccinet0","5.168.120.13","255.255.255.0","",""

Router mode (IPv6 context) AT+UIPADDR=2

OK+UIPADDR: 2,"ccinet1","","","2001::2:200:FF:FE00:0/64","FE80::200:FF:FE00:0/64"

Router mode (IPv4v6
context)

AT+UIPADDR=3

Router mode (IPv4v6
context) (all contexts)

AT+UIPADDR=OK+UIPADDR: 3,"ccinet2","5.10.100.2","255.255.255.0","2001::1:200:FF:FE00:0/64","FE80::200:FF:FE00:0/64"
OK+UIPADDR: 1,"ccinet0","5.168.120.242","255.255.255.255","",""+UIPADDR: 2,"ccinet1","46.12.30.162","255.255.255.255","",""+UIPADDR: 4,"ccinet3","76.18.130.262","255.255.255.255","200
1::2:200:FF:FE00:0/64","FE80::200:FF:FE00:0/64""",""

Router mode (all contexts)

AT+UIPADDR=OK+UIPADDR: 1,"ccinet0","10.24.48.129","255.255.255.0","",""+UIPADDR: 2,"ccinet1","10.32.44.135","255.255.255.0","",""OK

UBX-13002752 - R67

38 Networking

Page 814 of 1001

u-blox cellular modules - AT commands manual

Description
Command
Bridge mode (IPv4 context) AT+UIPADDR=1
Bridge mode (IPv6 context) AT+UIPADDR=2
Bridge mode (IPv4v6
AT+UIPADDR=3
context)
Bridge mode (IPv4v6
context) (all contexts)

AT+UIPADDR=

Bridge mode (all contexts)

AT+UIPADDR=

Response+UIPADDR: 1,"usb0:0","5.168.120.242","255.0.0.0","",""OK
ERROR+UIPADDR: 3,"usb0:2","5.168.120.100","255.255.255.255","",""OK+UIPADDR: 1,"usb0:0","5.168.120.242","255.255.255.255","",""+UIPADDR: 4,"usb0:3","76.18.130.262","255.255.255.255","",""OK+UIPADDR: 1,"usb0:0","10.40.184.162","255.255.255.0","",""+UIPADDR: 2,"usb0:1","10.92.161.200","255.255.255.0","",""

Bridge mode (bridge
and router mode mixed
contexts)

AT+UIPADDR=

No virtual devices active
Wrong CID

AT+UIPADDR=AT+UIPADDR=4

OK+UIPADDR: 1,"ccinet0","10.98.126.158","255.255.255.0","",""+UIPADDR: 2,"usb0:1","10.26.129.73","255.255.255.0","",""
OK
OK
ERROR

38.6 IP routing configuration +UIPROUTE+UIPROUTE
Modules
Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A TOBY-L2
MPCI-L2
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

38.6.1 Description
Configures the module's IP routing, using the ROUTE syntax and implementing destination based routing. The
new configuration is added to the current one and it is instantly applied.
The configuration is not stored into NVM.
The configuration is allowed in the following cases:• The module is configured in router mode
• The module is configured in bridge mode but has at least one active PDN in router mode.
TOBY-L4
The bridge mode is not supported.
TOBY-L2 / MPCI-L2
See the +UDPDP AT command description for more details on the bridge mode.
The configuration can be reverted by manually deleting each route previously added or by a power cycle.
This AT command should be mainly used for setting static routing rules for specific networks/hosts.
The typical user case is the following:• The "internet" PDN is activated first and it is the current default gateway• The user activates another "alternate data" PDN (MMS for example)• The user wants to connect to a server through the "alternate data" PDN connection but the server's IP
address does not belong to the IP subnet of the "alternate data" PDN• Therefore the user must manually add a routing rule to reach the server through the "alternate data" PDN
The usage of default gateway rules is not recommended and can disrupt the module functionality.
TOBY-L200-00S / TOBY-L210-00S / TOBY-L210-60S
MPCI-L210-60S / MPCI-L210-63S
The command does not support IPv6 functionality.

UBX-13002752 - R67

38 Networking/

MPCI-L200-00S/

MPCI-L210-00S/

Page 815 of 1001

u-blox cellular modules - AT commands manual

38.6.2 Syntax
Type
Set

SyntaxResponse
ExampleAT+UIPROUTE=<route_raw_input> [+UIPROUTE: <route_raw_output>] AT+UIPROUTE="add -net
129.56.76.0 netmask 255.255.255.0
OK
dev ccinet2"

Read

AT+UIPROUTE?

+UIPROUTE:OK+UIPROUTE:[<route_raw_output>]

Kernel IP routing table

OK

Destination Gateway Genmask
Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U
0 0 0 usb0
Kernel IPv6 routing table
Destination Next Hop Flags Metric
Ref Use Iface
fe80::/64 :: U 256 0 0 usb0::1/128 :: U 0 0 1 lo
fe80::4483:18ff:feff:328/128 :: U 0 0
1 lo
ff00::/8 :: U 256 0 0 usb0

Test

AT+UIPROUTE=?

+UIPROUTE:OK+UIPROUTE:

OK

OK

38.6.3 Defined values
ParameterType<route_raw_input> String<route_raw_output> String

Description
String compliant to ROUTE syntax
Contains the ROUTE output related to the user's request

38.6.4 Notes
TOBY-L4006 / TOBY-L4106 / TOBY-L4206 / TOBY-L4906-51A• The nomenclature "inm(x)" is used instead of the "ccinet(x)".
o The "inm(x)" is the name of the Linux network interface mapped to an activated PDP context.
o The x parameter is in the range from 0 to 7.
o Example: "inm0" interface is mapped to the PDP context with CID 1.
• To provide "off the shelf" internet access (router mode only) an automatic default gateway route handlingmechanism has been introduced. This mechanism can be controlled (i.e. when custom default gateway
and routing handling is required) by means of the +UDCONF=64 AT command. The automatic default
gateway route handling mechanism is activated when an "internet" PDN is activated and follows thefollowing logic:
o When an "internet" PDN is activated a new "inm(x)" interface is added to the network interfaces list.
- A default gateway rule is searched in the internal routing rules table.
- If there is no default gateway rule, the newly added network interface "inm(x)" is added as
default gateway.
- If there is a default gateway rule already present no action is taken.
o When an "internet" PDN is deactivated the "inm(x)" is removed from the network interfaces list.
- A default gateway with "inm(x)" is searched in the internal routing table.
- If there is a default gateway with "inm(x)" present then it is removed.
- If there is no default gateway with "inm(x)" no action is taken.
• If the <route_raw_input> string is not compliant to the ROUTE syntax the <route_raw_output> parameter
will provide the ROUTE command error description. In this case the AT command will still respond with
the OK final result code.

UBX-13002752 - R67

38 Networking

Page 816 of 1001

u-blox cellular modules - AT commands manual

TOBY-L4906-50A• The nomenclature "inm(x)" is used instead of the "ccinet(x)".
o The "inm(x)" is the name of the Linux network interface mapped to an activated PDP context.
o The x parameter is in the range from 0 to 3.
o Example: "inm0" interface is mapped to the PDP context with CID 1.
• To provide "off the shelf" internet access (router mode only) an automatic default gateway route handlingmechanism has been introduced. This mechanism can be controlled (i.e. when custom default gateway
and routing handling is required) by means of the +UDCONF=64 AT command. The automatic default
gateway route handling mechanism is activated when an "internet" PDN is activated and follows thefollowing logic:
o When an "internet" PDN is activated a new "inm(x)" interface is added to the network interfaces list.
- A default gateway rule is searched in the internal routing rules table.
- If there is no default gateway rule, the newly added network interface "inm(x)" is added as
default gateway.
- If there is a default gateway rule already present no action is taken.
o When an "internet" PDN is deactivated the "inm(x)" is removed from the network interfaces list.
- A default gateway with "inm(x)" is searched in the internal routing table.
- If there is a default gateway with "inm(x)" present then it is removed.
- If there is no default gateway with "inm(x)" no action is taken.
• If the <route_raw_input> string is not compliant to the ROUTE syntax the <route_raw_output> parameter
will provide the ROUTE command error description. In this case the AT command will still respond with
the OK final result code.

38.7 IP firewall tables configuration +UIPTABLES+UIPTABLES
Modules
Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A TOBY-L2
MPCI-L2
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

38.7.1 Description
Changes the module's networking configuration, using the IPTABLES syntax. The new configuration is added
to the current one and it is applied and instantly saved into NVM.
The configuration is independent from the currently selected <networking_mode>.
The output of the configuration is reported as an IRC before the "OK" final result code.

38.7.2 Syntax
Type
Set

SyntaxAT+UIPTABLES=[<iptables_raw_
input>]

Response[+UIPTABLES: <iptables_raw_
output>]ExampleAT+UIPTABLES="-A INPUT -p ICMP
-icmp-type 8 -j DROP"OKOK
AT+UIPTABLES="<wrong_string>"+UIPTABLES: Bad argument<wrong_string>

Read

AT+UIPTABLES?

+UIPTABLES:OK+UIPTABLES:[<iptables_raw_output>]

Chain INPUT (policy DROP)

OK

target prot opt source destination
ACCEPT all -- anywhere anywherestate RELATED,ESTABLISHEDACCEPT tcp -- anywhere anywheretcp dpt:httpUBX-13002752 - R67

38 Networking

Page 817 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

ExampleACCEPT tcp -- anywhere anywheretcp dpt:https
ACCEPT tcp -- anywhere anywheretcp dpt:bootps
ACCEPT udp -- anywhere anywhere
udp dpt:bootps
ACCEPT udp -- anywhere anywhere
udp dpt:domain
ACCEPT tcp -- anywhere anywheretcp dpt:domain
ACCEPT udp -- anywhere anywhere
udp dpt:12345
ACCEPT tcp -- anywhere anywheretcp dpt:12345
ACCEPT udp -- anywhere anywhere
udp dpt:30001
ACCEPT icmp -- anywhere anywhereicmp echo-request limit: avg 10/sec
burst 5DROP icmp -- anywhere anywhereicmp echo-request
ACCEPT icmp -- anywhere anywhere
ACCEPT tcp -- anywhere anywheretcp dpt:49152
ACCEPT tcp -- anywhere anywheretcp dpt:49152
ACCEPT udp -- anywhere anywhere
udp dpt:1900
ACCEPT all -- 127.0.0.0/8 anywhere
ACCEPT tcp -- anywhere anywheretcp dpt:5555
ACCEPT tcp -- anywhere anywheretcp dpt:8080
Chain FORWARD (policy DROP)
target prot opt source destination
FWD_UPNP all -- anywhere
anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Test

AT+UIPTABLES=?

+UIPTABLES:OK+UIPTABLES:

OK

OK

38.7.3 Defined values
Parameter<iptables_raw_
input><iptables_raw_
output>UBX-13002752 - R67

TypeStringStringDescription
String compliant to IPTABLES syntax. The default value is an empty string, meaning
reset to the default configuration
String containing the IPTABLES output related to the user's request

38 Networking

Page 818 of 1001

u-blox cellular modules - AT commands manual

38.7.4 Notes
TOBY-L2 / MPCI-L2• The following TCP/UDP/ICMP connection timeouts are not affected by the command:
Timeout

Description

Default
value [s]600120generic_timeout
generic timeout value
tcp_timeout_syn_sent Timeout value related to the connection state SYN-SENT (defined in RFC 793[90])
tcp_timeout_syn_recv Timeout value related to the connection state SYN-RECEIVED (defined in RFC 60
793 [90])tcp_timeout_
Timeout value related to the connection state ESTABLISHED (defined in RFC
432000established
793 [90])tcp_timeout_fin_wait Timeout value related to the connection state FIN-WAIT-1 and FIN-WAIT-2
120(defined in RFC 793 [90])tcp_timeout_close_
Timeout value related to the connection state CLOSE-WAIT (defined in RFC 793 60
wait
[90])
tcp_timeout_last_ack Timeout value related to the connection state LAST-ACK (defined in RFC 793
30[90])
tcp_timeout_time_
Timeout after which the connection goes to the closed state120
wait
tcp_timeout_close
Timeout value related to the connection state CLOSE (defined in RFC 793 [90]) 10
udp_timeout
Timeout value for UDP packets
300
udp_timeout_stream Timeout value for UDP packets, when UDP stream is detected300
icmp_timeout
Timeout value for IPv4 ICMP packets
30

TOBY-L4• The command setting in not stored in the NVM.
• If the <iptables_raw_input> string is not compliant to the IPTABLES syntax the <iptables_raw_output>
will provide the IPTABLES command error description. In this case the AT command will still respond with
the OK final result code.
TOBY-L2• The configuration can be reverted to its default values with AT+UIPTABLES=.

38.8 IPv6 firewall tables configuration +UIP6TABLES+UIP6TABLES
Modules
Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A TOBY-L280-03S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

38.8.1 Description
Changes the module's networking configuration, using the IP6TABLES syntax. The new configuration is added
to the current one and it is applied and instantly saved into NVM.
The configuration is independent from the currently selected <networking_mode>.
The output of the configuration is reported as an IRC before the "OK" final result code.

38.8.2 Syntax
Type
Set

SyntaxResponse
AT+UIP6TABLES=[<ip6tables_raw_ [+UIP6TABLES: <ip6tables_raw_
input>]
output>]OK

ExampleAT+UIP6TABLES="-A INPUT -p
icmpv6 --icmpv6-type echo-request-j DROP"OK
AT+UIP6TABLES="wrong_string"+UIP6TABLES: Bad argument
wrong_string

UBX-13002752 - R67

38 Networking

Page 819 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse

Read

AT+UIP6TABLES?

+UIP6TABLES:

ExampleOK+UIP6TABLES:[<ip6tables_raw_output>]

Chain INPUT (policy ACCEPT)

OK

target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Test

AT+UIP6TABLES=?

+UIP6TABLES:OK+UIP6TABLES:

OK

OK

38.8.3 Defined values
Parameter<ip6tables_raw_
input><ip6tables_raw_
output>Type
StringStringDescription
String compliant to IP6TABLES syntax. The default value is an empty string, meaning
reset to the default configuration
String containing the IP6TABLES output related to the user's request

38.8.4 Notes••

The following TCP/UDP/ICMP connection timeouts are not affected by the command:
Timeout

Description

generic_timeout
icmpv6_timeout
frag6_timeout

generic timeout value
Timeout value for IPv6 ICMP packets
Timeout value after the last fragmented IPv6 packet

Default
value [s]
600
30
60

The configuration can be reverted to its default values with AT+UIP6TABLES=.

TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S• The command is not supported by TOBY-L200-03S-00, TOBY-L210-03A-00, TOBY-L210-03S-00,
TOBY-L280-03S-00.

38.9 Configure PDP/EPS bearer connection type over USB+UDPDP+UDPDP
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
partialNo

Settings saved Can be aborted
No
No

Response time-Error reference+CME Error

38.9.1 Description
Sets the connection type of a specific context.
TOBY-L2 MPCI-L2
The default configuration reflects the +UBMCONF settings. The command will work only in bridge mode
to give connectivity to the internal IP stack. In the information text response to the read command the
dedicated bearer information is provided by means of the <networking_mode>=3 value.

38.9.2 Syntax
Type
Set

SyntaxAT+UDPDP=<cid>[,<networking_mode>]

UBX-13002752 - R67

Response
OK

ExampleAT+UDPDP=1,1
OK

38 Networking

Page 820 of 1001

u-blox cellular modules - AT commands manual

Type
Read

SyntaxAT+UDPDP?

Response
For each cid:

Example+UDPDP: 1,1+ UDPDP: <cid>,<networking_mode>+UDPDP: 2,1[..]+UDPDP: 3,1+UDPDP: 4,1

OK+UDPDP: 5,1+UDPDP: 6,1+UDPDP: 7,1+UDPDP: 8,1

Test

OK
+UDPDP: (list of supported <cid>s), +UDPDP: (1-8),(1-2)(list of supported <networking_OKmode>s)AT+UDPDP=?

OK

38.9.3 Defined values
Parameter
Type
<cid>
Number
<networking_mode> Number

Description
See <cid>.
State configuration:• 0: no mapping• 1: router context• 2: bridge context• 3: reference to a dedicated bearer; this value cannot be set but it is provided only in
the information text response to the read command
Allowed values:• TOBY-L2 / MPCI-L2 - 1, 2, 3

38.9.4 Notes
TOBY-L2 / MPCI-L2• A <cid>'s configuration can be reverted to the current +UBMCONF <networking_mode> with AT+UDPDP=<cid>.

38.10 RNDIS driver optimization configuration +UDCONF=67+UDCONF=67
Modules
Attributes

TOBY-L2 MPCI-L2
SyntaxPIN required
fullNo

Settings saved Can be aborted
NVM
No

Response time-Error reference+CME Error

38.10.1 Description
The RNDIS driver optimization allows a data transfer over the RNDIS link to reach the maximum throughput(LTE CAT4). This optimization can cause a lower throughput on some linux based operating systems bothin router mode and in bridge mode. To fix this a DTE's kernel modification is needed (see Networking Modes
Application Note [96]); if this is not possible and using CDC-ECM is not an option then disabling this featuremight mitigate the effects in router mode only.
The new configuration is saved in NVM and will be effective at the next power on.

38.10.2 Syntax
Type
Set

SyntaxAT+UDCONF=67,<mode>

Response
OK

ExampleAT+UDCONF=67,1

Read

AT+UDCONF=67+UDCONF: 67,<mode>

OK+UDCONF: 67,1

UBX-13002752 - R67

38 Networking

Page 821 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

ExampleOK

38.10.3 Defined values
Parameter<mode>

Type
NumberDescription
Configures the RNDIS driver optimization. Allowed values:••

0: RNDIS driver optimization disabled
1 (factory-programmed value): RNDIS driver optimization enabled

38.11 Automatic default gateway route handling mechanism
control +UDCONF=64+UDCONF=64
Modules
Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-50A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

38.11.1 Description
To provide "off the shelf" internet access (router mode only) an automatic default gateway route handlingmechanism has been introduced. The mechanism is activated when an "internet" PDN is activated (for more
information, see the +UIPROUTE AT command description). This command enables/disables the describedmechanism in cases when custom the default gateway and routing handling is required.
The configuration value is saved in NVM and is effective at the next module power-on.

38.11.2 Syntax
Type
Set

SyntaxAT+UDCONF=64,<mode>

Response
OK

ExampleAT+UDCONF=64,1

Read

AT+UDCONF=64+UDCONF: 64,<mode>

OK+UDCONF: 64,1

OKOK

38.11.3 Defined values
Parameter<mode>

Type
NumberDescription
Configures the automatic default gateway route handling mechanism. Allowed
values:• 0: automatic default gateway route handling mechanism disabled.
• 1: (factory-programmed value): automatic default gateway route handlingmechanism enabled.

38.12 Throughput optimization via CDC-NCM or Ethernet+UDCONF=71+UDCONF=71
Modules
Attributes

TOBY-L4006-51A TOBY-L4106-51A TOBY-L4206-51A TOBY-L4906-51A
SyntaxPIN required
Settings saved Can be aborted Response time
full
No
NVM
No
-

Error reference+CME Error

38.12.1 Description
Configures the chosen network interface in order to maximize the possible throughput over any active context.
Reboot the module to apply the new parameter configuration.

UBX-13002752 - R67

38 Networking

Page 822 of 1001

u-blox cellular modules - AT commands manual

38.12.2 Syntax
Type
Set

SyntaxAT+UDCONF=71,<interface>

Response
OK

ExampleAT+UDCONF=71,1

Read

AT+UDCONF=71+UDCONF: 71,<interface>

OK+UDCONF: 71,0OKOK

38.12.3 Defined values
Parameter<interface>Type
NumberDescription
Indicates the module interface where the throughput is optimized. Allowed values:• 0 (factory-programmed value): USB interface• 1: Ethernet interface

38.13 Advanced DNS configuration +UDNSCONF+UDNSCONF
Modules
Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A TOBY-L280-03S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

38.13.1 Description
Configures additional settings of the Domain Name Server (DNS) resolver. The AT command allows:• to set a list of preferred DNS servers;• to set a list of IP address that will be ignored as the resolution of required URL.
The DNS servers in the preferred list will be used at first. The DNS requests are sent starting consequentiallyfrom the first entry to the last one, if available. Once the list of the preferred DNS servers is exhausted, thesystem DNS servers are used. The system DNS servers are obtained from the cellular network at PDP context/
EPS bearer activation. The system DNS servers list will contain also the DNS servers of the Wi-Fi STA interface
connected to the external hotspot.
Several mobile operator DNS servers can provide an IP address into "No such domain" replies. This IP address
can correspond to an advertising/unwanted web page in response to a query for a not found domain name,instead of the correct NXDOMAIN response. The responses containing the IP addresses of the list to be ignored
list are considered by the DNS resolver as a NXDOMAIN response (see "--bogus-nxdomain=<ipaddr>" option in
the dnsmasq man page).
The configuration value is not saved in NVM and it is applied real time.
The factory-programmed setting does not imply neither a preferred DNS server nor an IP addresses tobe ignored.

38.13.2 Syntax
Type
SyntaxGeneric syntax
Set
AT+UDNSCONF=<op_code>[,<IP
address>]

Response

ExampleOK

AT+UDNSCONF=1,"35.26.73.24"

Read[+UDNSCONF: <IP address>

OK
AT+UDNSCONF=10[...]]+UDNSCONF: "10.45.2.45"

OK

OK[+UDNSCONF: <IP address>

AT+UDNSCONF=0[...]]+UDNSCONF: "10.45.2.45"

OK+UDNSCONF: "183.32.63.13"

AT+UDNSCONF=<op_code>

List preferred DNS servers
Read
AT+UDNSCONF=0+UDNSCONF: "12.54.1.2"

UBX-13002752 - R67

38 Networking

Page 823 of 1001

u-blox cellular modules - AT commands manualType

SyntaxAppend a preferred DNS server to the list
Set
AT+UDNSCONF=1,<IP address>

Response

ExampleOK

OK

AT+UDNSCONF=1,"34.54.62.23"
OK

Delete a preferred DNS server from the list
Set
AT+UDNSCONF=2,<IP address>

OK

AT+UDNSCONF=2,"34.54.62.23"
OK

Delete the list of preferred DNS servers
Set
AT+UDNSCONF=9

OK

AT+UDNSCONF=9
OK

List the IP addresses to the ignored
Read
AT+UDNSCONF=10[+UDNSCONF: <IP address>

AT+UDNSCONF=10[...]]+UDNSCONF: "50.41.2.75"

OK+UDNSCONF: "83.38.63.23"+UDNSCONF: "52.54.41.32"
OK

Append to the list an IP address to the ignored
Set
AT+UDNSCONF=11,<IP address>
OK

AT+UDNSCONF=11,"45.22.57.51"
OK

Delete from the list an IP address to the ignored
Set
AT+UDNSCONF=12,<IP address>
OK

AT+UDNSCONF=12,"45.22.57.51"
OK

Delete the list of the IP addresses to the ignored
Set
AT+UDNSCONF=19
OK

AT+UDNSCONF=19
OK

Test

AT+UDNSCONF=?

+UDNSCONF:+UDNSCONF:

OK

OK

38.13.3 Defined values
Parameter<op_code>Type
Number<IP address>

StringDescription
Allowed values:• 0: list preferred DNS servers• 1: append a preferred DNS server to the list
• 2: delete a preferred DNS server from the list
• 9: delete the list of preferred DNS servers• 10: list the IP addresses to the ignored• 11: append to the list an IP address to the ignored• 12: delete from the list an IP address to the ignored• 19: delete the list of the IP addresses to the ignored
IP address of the preferred DNS server or of the host to be ignored as DNS resolutionof an URL. For IP address format reference, see the IPv4/IPv6 addressing.

38.13.4 Notes
TOBY-L200-03S / TOBY-L210-03A / TOBY-L210-03S / TOBY-L280-03S• The command is not supported by TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L210-03A-00,
TOBY-L280-03S-00.
• The list of the preferred DNS servers accepts IPv4 and IPv6 addresses.
• The list of the IP addresses to be ignored accepts IPv4 addresses.
• The preferred DNS server are applied to the internal contexts and internal clients (e.g. BIP, IMS).

UBX-13002752 - R67

38 Networking

Page 824 of 1001

u-blox cellular modules - AT commands manual

39 Wi-Fi
39.1 Introduction
TOBY-L2 series modules (see the Wi-Fi AT commands applicability for the complete list of product versions
supporting Wi-Fi functionalities) can be connected to ELLA-W1 Wi-Fi modules via the Secure Digital Input
Output (SDIO) interface to provide Wi-Fi functionalities. The subsystem composed of these u-blox modules isreferred to as Cellular / Wi-Fi subsystem.
An external processor can be connected to the Cellular / Wi-Fi subsystem by means of these interfaces:• Ethernet over USB (e.g. RNDIS or CDC-ECM): see +UUSBCONF for the USB interface configuration• UART
In the following description only the USB interface is displayed, since it is more suitable in terms of IP
connectivity.
The Cellular / Wi-Fi subsystem can be configured in the following ways:••

Router mode with Internet access via cellular network - the cellular module provides Internet connectivity
to Wi-Fi clients connected to the Wi-Fi access point. The clients communicate to the TOBY-L2 IP subsystemand the router functionality of the IP subsystem provides them Internet connection.

Figure 27: Router mode with Internet access via cellular network
Router mode with Internet access via external hotspot - the Wi-Fi module is acting concurrently in twomodes: wireless access point (AP) and wireless station (STA), respectively. The Wi-Fi clients are connected
through the wireless access point to the TOBY-L2 module IP subsystem. The IP subsystem is connected toan external hotspot through the Wi-Fi interface operating in station mode. The IP traffic of the Wi-Fi clientsand of the external hotspot is forwarded through the Wi-Fi interface (STA) of the Wi-Fi module. In this case
the Internet connectivity is provided to users by the external hotspot instead of the cellular network. The
AP is set on the same channel of the external hotspot, hence they should operate and share the resources
available on the channel. The AP channel configuration is ignored, since it operates on the same channel as
the STA. This behavior is also present in wireless repeaters (also known as wireless range extenders).

UBX-13002752 - R67

39 Wi-Fi

Page 825 of 1001

u-blox cellular modules - AT commands manual•

Figure 28: Router mode with Internet access via external hotspot
Router mode with Internet access either via cellular network or via external hotspot - the cellular module
IP subsystem can provide Internet connection either through the cellular module or through the wirelessstation interface dynamically switching between the two configurations described above.

Figure 29: Router mode with Internet access via cellular network or via external hotspot

UBX-13002752 - R67

39 Wi-Fi

Page 826 of 1001

u-blox cellular modules - AT commands manual•

Bridge mode with Internet access either via cellular network or via external hotspot - in bridge modethe cellular module provides Internet connectivity to the external processor by a bridge PDP contexts/
EPS bearers. A bridge PDP context/EPS bearer sets up a bridge between the cellular network and the
USB interface. Furthermore, when the module is in bridge mode, several PDP contexts/EPS bearers canbe configured as router contexts (see +UDPDP for PDP context/EPS bearer configuration). Router PDP
contexts/EPS bearers are connected to the module IP subsystem. The cellular module IP subsystem
can provide Internet connectivity either through the cellular module (router PDP context/EPS bearer) or
through the wireless station interface, switching dynamically between the two options described above.
The external processor may connect to the Internet either through the bridge PDP context/EPS bearer or
through the USB interface which is connected to the module IP subsystem where connectivity is granted
by a router PDP context/EPS bearer or by the wireless station interface.

Figure 30: Bridge mode with Internet access via cellular network or via external hotspot
The current scenario presents the most complete configuration between cellular and Wi-Fi modules.
The only difference respect with the previous scenario is the bridge context / ESP bearer and hence
the previous scenarios are a subset of this one.
The external processor can communicate directly with the wireless stations and access to Internet via cellular
network or via the external Wi-Fi interface accordingly to the permitted system configuration.
See Wi-Fi / Cellular Integration Application Note [167] for a complete description of Wi-Fi functionalities andthe configurations briefly described above.
The Wi-Fi functionalities can be properly configured by the following AT commands to cover all the previous
use-cases:• Wi-Fi module management:o Power mode configuration: +UWCFG
o Firmware reset: +UWFWRESETo Maximum allowed output power configuration: +UWMP
o Test mode configuration: +UWTEST• Access point management:

UBX-13002752 - R67

39 Wi-Fi

Page 827 of 1001

u-blox cellular modules - AT commands manual•o Physical layer configuration: +UWAPCFG
o Network layer configuration: +UWAPIPCFG
o MAC address: +UWAPMACADDR
o List of connected stations: +UWAPSTALIST
Wireless station management:o Physical layer configuration: +UWSTACFG
o Network layer configuration: +UWSTAIPCFG
o Wi-Fi station signal level indicator: +UWSTACSQo Network scan: +UWSCAN

39.2 Web User Interface (WebUI)
A graphical Web User Interface is provided for the Cellular/Wi-Fi subsystem configuration. In particular, the
WebUI is used to configure the cellular and Wi-Fi functionalities. The features configurable with the WebUI are
the following:• Cellular:o Cellular network profile (APN, initial EPS bearer APN for LTE networks, roaming, alternative DNS servers,
PIN entry, authentication parameters, ...)o Routing within the cellular network• Wi-Fi:o Access point physical layero Access point network layero Station physical layero Station network layero Routing within the external hotspot
o Web user interface customization• Further information:o The list of the wireless clients associated to the access pointo Uplink and downlink traffic counters
The configuration performed within the WebUI is applied after a reboot of the Cellular / Wi-Fi subsystem.
Access to the settings is password protected.
The WebUI interface can be properly enabled via the +UWWEBUI AT command.
The internal connection manager handles the cellular connectivity configured by means of the WebUI. The
connection manager can be enabled either by means of the WebUI or the +UWCFG AT command. See +UWCFGAT command for further information regarding the internal connection manager.
The connection manager ensures the cellular connectivity using the fourth (4-th) CID in the case of LTE
networks and the first (1-st) CID in the case of 2G/3G networks. When the connection manager is configured
by means of the WebUI, previous configurations of these two CIDs done through AT commands may beoverwritten.
The customization of the Web user interface can be performed through the FTP access to certain files of the
HTTP server. See +UWWEBUIFTP AT command details for further information regarding the customization
feature.
Manual refresh of the WebUI page is required if the setting is not accepted during the storing of theconfiguration due to an invalid setting.
See Wi-Fi / Cellular Integration Application Note [167] for a complete description of WebUI functionality andits configuration.

UBX-13002752 - R67

39 Wi-Fi

Page 828 of 1001

u-blox cellular modules - AT commands manual

39.3 Wi-Fi module power mode, connection manager andCellular / Wi-Fi conflict detection +UWCFG+UWCFG
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 20 s+CME Error

39.3.1 Description
Configures the Wi-Fi access point power mode, the connection manager, and the Cellular / Wi-Fi conflict
detection.
The command turns on/off and puts in flight mode the Wi-Fi AP interface. The fight mode is applied also to
the Wi-Fi STA interface, if it is enabled.
The complete power cycle of the AP Wi-Fi interface can be performed by consecutively turning off and turningon the AP interface (i.e. +UWCFG=0/1 cycle).
The connection manager (also referred to as connection configuration manager) allows the user to check andconfigure the cellular connectivity through the WebUI: since the AT commands interface is not available to
Wi-Fi clients, they shall use the WebUI to configure the basic cellular connectivity.
When the connection manager is enabled, the MT is set to full functionality (+CFUN: 1), while when theconnection manager is disabled the MT is put to minimum cellular functionality (+CFUN: 0). It is worth noticingthat the cellular module boots in full functionality (+CFUN: 1,0) state and generally in automatic network
selection mode (+COPS: 0,0), independently from the connection manager state. Hence, in LTE networks, theconnectivity may be granted after boot time even if the connection manager is disabled (LTE networks may
provide Internet connectivity on the initial EPS bearer).
The command can enable also URC reporting of possible conflicts between the cellular band and the Wi-Fi
channels currently in use, that can disrupt the communications of both radio technologies. Depending on
the value of the <conflict_ind_mode> parameter, the resolution of such conflict can be up to the user or
automatically performed by the connection manager:• <conflict_ind_mode>=0: no URC is shown and the user should handle connectivity issues if they appear• <conflict_ind_mode>=1: a URC indicates the possible situation of conflict and the user is still in charge ofhandling the possible performance degradation• <conflict_ind_mode>=2 (semi automatic algorithm): a simple algorithm adjusts the range of channels
adopted in the automatic Wi-Fi channel selection• <conflict_ind_mode>=3 (full automatic algorithm): adjusts the range of channels adopted in the automatic
Wi-Fi channel selection and performs an automatic channel re-selection
The URC +UUWCFG reports the detected conflict:• <conflict_ind>=1: the conflict affects LTE working in band 7 and Wi-Fi channels between 10 and 14• <conflict_ind>=2: the conflict affects GSM 850 band and the Wi-Fi channels in the range 11 to 14
If a parameter is omitted in the set command, the current value is kept.
The <conflict_ind_mode> setting is not saved in NVM.

39.3.2 Syntax
Type
Set

SyntaxResponse
AT+UWCFG=<wifi_mode>[,<mgr>[, OK<conflict_ind_mode>]]Read

AT+UWCFG?

Test

AT+UWCFG=?

UBX-13002752 - R67+UWCFG: <wifi_mode>,<mgr>,<conflict_ind_mode>

ExampleAT+UWCFG=2,0,1
OK+UWCFG: 1,1,0

OK
OK+UWCFG: (list of supported <wifi_+UWCFG: (0-2),(0,1),(0-3)
mode>s),(list of supported <mgr>s),OK

39 Wi-Fi

Page 829 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse(list of supported <conflict_ind_mode>s)OK+UUWCFG: <conflict_ind>

URC

Example+UUWCFG: 1

39.3.3 Defined values
Parameter<wifi_mode>

Type
NumberDescription
Configures the power modes. Allowed values:
•
•
•

<mgr>

Number<conflict_ind_mode> Number<conflict_ind>

Number0 (factory-programmed value): wireless off. The wireless access point is turned off
1: wireless on. The wireless access point is turned on
2: airplane mode. The wireless access point is turned off (the radio frequency
transmission is turned off). If enabled, the Wi-Fi module enters the airplane mode
(AP and STA are turned off).
Configures the connection manager. Allowed values:• 0 (factory-programmed value): connection manager disabled• 1: connection manager enabled
Specifies the configuration of the cellular Wi-Fi conflict reporting URC and whichalgorithm is adopted:• 0 (factory-programmed value): conflict reporting URC disabled• 1: URC enabled, manual user intervention is required to handle the conflict• 2: URC enabled, semi automatic algorithm• 3: URC enabled, full automatic algorithm
Specifies which cellular/Wi-Fi frequency conflict occurs:•••

0: no conflict
1: possible conflict among cellular module working in LTE band 7 and Wi-Fi working
in channel range 10-14
2: possible conflict among cellular module working in GSM 850 band and Wi-Fi
working in channel range 11-14

39.3.4 Notes••

When configuring both AP and STA mode at the same time via +UWCFG and +UWSTACFG AT
commands, the STA channel setting is set also on the AP channel setting.
When the module works as a Wi-Fi station (STA mode), <conflict_ind_mode>=0 and 1 are supported, while<conflict_ind_mode>=2 and 3 are equivalent to <conflict_ind_mode>=1.

39.4 Wi-Fi access point physical layer configuration+UWAPCFG+UWAPCFG
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 20 s+CME Error

39.4.1 Description
Configures the physical layer parameters of the Wi-Fi access point.
Since the regulatory domains block feature is supported, the current Wi-Fi access point physical layer
configuration may differ from the one selected by the user. In particular, the reported regulatory domain is thecurrently applied regulatory domain. In addition, the user is not allowed to set a configuration (e.g. regulatory
domain, channel and mode) in violation of the constraints of the currently applied regulatory domain. For
further information see the +UWREGBLOCK AT command description.
In the case the security passphare is volatile, it is not valid after the module reboot. Since the security
passphrase is not valid after the module reboot, the AP interface will not be activated. The default SSID/
passphrase are used enabling the AP interface when the SSID/passphrase are not set.

UBX-13002752 - R67

39 Wi-Fi

Page 830 of 1001

u-blox cellular modules - AT commands manual

Reboot the Cellular / Wi-Fi subsystem or perform a complete power cycle of the AP Wi-Fi interface to apply
the new configuration.

39.4.2 Syntax
Type
Set

SyntaxResponse
AT+UWAPCFG=<ssid>,<security>, OK<psk>,<region>,<channel>,<mode>

Read

AT+UWAPCFG?

Test

AT+UWAPCFG=?

ExampleAT+UWAPCFG="UBXWifi",2,"ubxwifi",1,0,3

OK+UWAPCFG: <ssid>,<security>,+UWAPCFG: "UBXWifi",2,"ubx-wifi",<psk>,<region>,<channel>,<mode> 1,0,3
OK+UWAPCFG: <ssid>,(list of
supported <security>s),<psk>,(list of supported <region>s),(listof supported <channel>s),(list of
supported <mode>s)

OK+UWAPCFG: "UBXWifi",(0-3),"password",(0-2),(0-14),(0-4)
OKOK

39.4.3 Defined values
Parameter<ssid>Type
String<security>

NumberDescription
ESSID of the access point. The maximum length is 32 characters. The factoryprogrammed value is "UBXWifi".
Wireless authentication method. Allowed values:<psk>

String<region>Number• 0: OPEN• 1: WPA• 2 (factory-programmed value): WPA2
• 3: WPA_WPA2_MIXED• 4: WPA (volatile passphrase)• 5: WPA2 (volatile passphrase)• 6: WPA_WPA2_MIXED (volatile passphrase)
Security passphrase. It can be long from 8 to 64 characters. The factory-programmed
value is "ubx-wifi". If <security>="OPEN" the <psk> value is not taken into accountand can be omitted
Country code. Supported values:

Number• 0: EU• 1: US• 2: JPDue to the regulatory domains block feature, this parameter has a limited
configurability.
Wireless channel number. Allowed values:

Number• 0 (factory-programmed value): automatic channel selection• 1-11: 2.4 GHz channel number• 12-13: Europe/Japan only
• 14: Japan 11b only
IEEE standard. Allowed values:<channel><mode>

•
•
•
•
•
•
•
•

0: 802.11b
1: 802.11g
2: 802.11b/g
3 (factory-programmed value): 802.11b/g/n
4: 802.11n
5: reserved
6: reserved
7: reserved

39.4.4 Notes•

If <mode>= 3 or 4 (802.11b/g/n or 802.11n), the <security> is automatically set to 2 (WPA2).

UBX-13002752 - R67

39 Wi-Fi

Page 831 of 1001

u-blox cellular modules - AT commands manual•

The <security> can be set to 1 (WPA), only if the <mode> is set to 0, 1, or 2 (802.11b, 802.11g, 802.11b/g).

TOBY-L200 / TOBY-L201• The factory-programmed value of <region> parameter is 1.
TOBY-L210 / TOBY-L280• The factory-programmed value of <region> parameter is 0.
TOBY-L220• The factory-programmed value of <region> parameter is 2.
TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S / TOBY-L220 / TOBY-L280-02S• <security>=4, 5, 6 are not supported.

39.5 Wi-Fi access point network layer configuration+UWAPIPCFG+UWAPIPCFG
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

39.5.1 Description
Configures the network layer parameters of the Wi-Fi access point.
Reboot the Cellular / Wi-Fi subsystem or perform a complete power cycle to apply the new configuration.
The subnetwork of the USB network function (e.g. RNDIS/CDC-ECM interface) should be different fromthe subnetwork of the wireless access point. Use the +UIPCONF AT command to set the subnetwork of
the USB network function. The connectivity between the two subnetworks is granted.

39.5.2 Syntax
Type
Set

SyntaxResponse
AT+UWAPIPCFG=<ip>,<netmask>, OK<dhcp_start>,<dhcp_end>

Read

AT+UWAPIPCFG?

+UWAPIPCFG: <ip>,<netmask>,<dhcp_start>,<dhcp_end>
OK

Test

AT+UWAPIPCFG=?

+UWAPIPCFG: <ip>,<netmask>,<dhcp_start>,<dhcp_end>
OK

ExampleAT+UWAPIPCFG="192.168.2.1","255.255.255.0","192.168.2.100","192.168.2.200"
OK+UWAPIPCFG: "192.168.2.1","255.255.255.0","192.168.2.100","192.168.2.200"
OK+UWAPIPCFG: "192.168.2.1","255.255.255.0","192.168.2.100","192.168.2.200"
OK

39.5.3 Defined values
Parameter
<ip>

Type
String<netmask>

String<dhcp_start>

StringDescription
IP address of the access point. The factory-programmed value is "192.168.2.1". The
address must not be a network or broadcast address (see Notes for more details).
The IP address shall not be in the range of DHCP server.
Netmask of the access point. The factory-programmed value is "255.255.255.0". The
netmask must be a valid address.
Start IP address of the DHCP range provided by the access point. The factoryprogrammed value is "192.168.2.100". The address must not be a network or
broadcast address (see Notes for more details).
The parameter value must be equal or lower than the <dhcp_stop> value.

UBX-13002752 - R67

39 Wi-Fi

Page 832 of 1001

u-blox cellular modules - AT commands manual

Parameter<dhcp_stop>

Type
StringDescription
Stop IP address of the DHCP range provided by the access point. The factoryprogrammed value is "192.168.2.200". The address must not be a network or
broadcast address (see Notes for more details).
The parameter value must be equal or greater than the <dhcp_start> value.

39.5.4 Notes••••

In the "network" address the last 32-(maskbit) bits are all set to 0.
In the "broadcast" address the last 32-(maskbit) bits are all set to 1.
The IP address should not be equal to an "network" or "broadcast" address
The maskbit is the prefix size of the subnet mask in CIDR (Classless Inter-Domain Routing) notation
expressed as a decimal number (see RFC 1518 [122] and RFC 1519 [123]).

39.6 Wi-Fi station physical layer configuration +UWSTACFG+UWSTACFG
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
< 20 s+CME Error

39.6.1 Description
Enables the STA interface and configures the physical layer parameters of the Wi-Fi station. The parameters
configured by means of this command are used to establish the connection between the station and theexternal hotspot:• If <enable>= 0, further parameters can be omitted.
• If <enable>= 1, the STA interface will be enabled and turned on.
The complete power cycle of the STA Wi-Fi interface can be performed by consecutively turning off and turningon the STA interface (i.e. +UWSTACFG=0/1 cycle).
Reboot the Cellular / Wi-Fi subsystem or perform a complete power cycle of the STA Wi-Fi interface toapply the new configuration.
In the case the security passphare is volatile, it is not valid after the reboot of the module. Since thesecurity passphrase is not valid after the module reboot, the STA interface will not be activated.

39.6.2 Syntax
Type
Set

SyntaxResponse
AT+UWSTACFG=<enable>[,<ssid>, OK<security>,<psk>]

Read

AT+UWSTACFG?

Test

AT+UWSTACFG=?

+UWSTACFG: <enable>[,<ssid>,<security>]

ExampleAT+UWSTACFG=1,"external_
hotspot_ssid",1,"external_hotspot_security_key"
OK+UWSTACFG: 1,"external_hotspot_ssid",1

OK
OK+UWSTACFG: (list of supported+UWSTACFG: (0,1),"external_<enable>s),<ssid>,(list of supported hotspot_ssid",(0-2,11-18,21-28,31-38,<security>s),<psk>
41-48),"external_hotspot_security_
key"
OK
OK

39.6.3 Defined values
Parameter<enable>Type
NumberDescription
Configures the station mode of the wireless interface. Allowed values:••

UBX-13002752 - R67

0 (factory-programmed value): disabled
1: enabled

39 Wi-Fi

Page 833 of 1001

u-blox cellular modules - AT commands manual

Parameter<ssid><security>

<psk>

Type
StringNumberStringDescription
ESSID of the access point. The maximum length is 32 characters.
Wireless authentication type. Allowed values:• 0 (default value): OPEN. The <psk> parameter is not mandatory• 1: WPA/WPA2• 2: WPA/WPA2 (volatile passphrase)• 11: WEP, key 1, hexadecimal passphrase, open system• 12: WEP, key 2, hexadecimal passphrase, open system• 13: WEP, key 3, hexadecimal passphrase, open system• 14: WEP, key 4, hexadecimal passphrase, open system• 15: WEP, key 1, ASCII passphrase, open system• 16: WEP, key 2, ASCII passphrase, open system• 17: WEP, key 3, ASCII passphrase, open system• 18: WEP, key 4, ASCII passphrase, open system• 21: WEP, key 1, hexadecimal passphrase, open system (volatile passphrase)• 22: WEP, key 2, hexadecimal passphrase, open system (volatile passphrase)• 23: WEP, key 3, hexadecimal passphrase, open system (volatile passphrase)• 24: WEP, key 4, hexadecimal passphrase, open system (volatile passphrase)• 25: WEP, key 1, ASCII passphrase, open system (volatile passphrase)• 26: WEP, key 2, ASCII passphrase, open system (volatile passphrase)• 27: WEP, key 3, ASCII passphrase, open system (volatile passphrase)• 28: WEP, key 4, ASCII passphrase, open system (volatile passphrase)• 31: WEP, key 1, hexadecimal passphrase, shared key• 32: WEP, key 2, hexadecimal passphrase, shared key• 33: WEP, key 3, hexadecimal passphrase, shared key• 34: WEP, key 4, hexadecimal passphrase, shared key• 35: WEP, key 1, ASCII passphrase, shared key• 36: WEP, key 2, ASCII passphrase, shared key• 37: WEP, key 3, ASCII passphrase, shared key• 38: WEP, key 4, ASCII passphrase, shared key• 41: WEP, key 1, hexadecimal passphrase, shared key (volatile passphrase)• 42: WEP, key 2, hexadecimal passphrase, shared key (volatile passphrase)• 43: WEP, key 3, hexadecimal passphrase, shared key (volatile passphrase)• 44: WEP, key 4, hexadecimal passphrase, shared key (volatile passphrase)• 45: WEP, key 1, ASCII passphrase, shared key (volatile passphrase)• 46: WEP, key 2, ASCII passphrase, shared key (volatile passphrase)• 47: WEP, key 3, ASCII passphrase, shared key (volatile passphrase)• 48: WEP, key 4, ASCII passphrase, shared key (volatile passphrase)
Security passphrase. The security passphrase length depends on <psk> parametervalue:•••

if <psk> = 1, 2 (WPA/WPA2) from 8 to 64 charactersif <psk> = 11-14, 21-24, 31-34, 41-44 (hexadecimal passphrase) 10 or 26 hexadecimal
digits (64-bit and 128-bit encryption)
if <psk> = 15-18, 25-28, 35-38, 45-48 (ASCII passphrase) 5 or 13 ASCII characters(64-bit and 128-bit encryption); allowed characters are printable ASCII characters,
expect for:o Apostrophe ('), code 0x27
o Quotation mark ("), code 0x22
o Grave accent (`), code 0x60

39.6.4 Notes•

It is not possible to change the external hotspot if the module is already connected with another external
hotspot; AT+UWSTACFG=0 command shall be issued before reconfiguring the hotspot settings.

TOBY-L200-02S / TOBY-L210-02S / TOBY-L280-02S• The range of <security> parameter is 0-1.
TOBY-L210-62S / TOBY-L210-65S / TOBY-L220• The range of <security> parameter is 0-2.

UBX-13002752 - R67

39 Wi-Fi

Page 834 of 1001

u-blox cellular modules - AT commands manual

39.7 Wi-Fi station network layer configuration +UWSTAIPCFG+UWSTAIPCFG
Modules
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
NVM
No
+CME Error

39.7.1 Description
Configures the network layer parameters of the Wi-Fi station. The network layer configuration can be obtained
from the DHCP server of the external hotspot. Otherwise, this command can specify a static IP address,
netmask, gateway IP address, and IP addresses of two DNS servers.
This command also allows switching between cellular and Wi-Fi connectivity.
If <dhcp>=1 further parameters can be omitted and are not taken into account when given.
Reboot the Cellular / Wi-Fi subsystem or perform a complete power cycle of the STA Wi-Fi interface toapply the new configuration.
The subnetwork of the station mode should be different from the subnetwork of the USB network function(e.g. RNDIS/CDC-ECM interface) and of the Wi-Fi access point. Use the +UIPCONF AT command to set
the subnetwork of the USB network function and the +UWAPIPCFG AT command to set the subnetworkof the Wi-Fi access point. The connectivity between the three subnetworks is granted.

39.7.2 Syntax
Type
Set

SyntaxAT+UWSTAIPCFG=<routing>,<dhcp>[,<ip>,<netmask>,<gateway>,[<dns1>],[<dns2>]]

Read

AT+UWSTAIPCFG?

Test

AT+UWSTAIPCFG=?

Response
OK

ExampleAT+UWSTAIPCFG=1,0,"10.254.0.100","255.255.0.0","10.254.0.1","8.8.8.8","208.67.222.222"

OK+UWSTAIPCFG: <routing>,<dhcp>[, +UWSTAIPCFG: 1,0,"192.168.254.10<ip>,<netmask>,<gateway>,<dns1>, 0","255.255.255.0","192.168.254.1",<dns2>]"192.168.254.1","192.168.254.1"
OK+UWSTAIPCFG: (list of supported<routing>s),(list of supported<dhcp>s),<ip>,<netmask>,<gateway>,<dns1>,<dns2>

OK+UWSTAIPCFG: (0,1),(0,1),"192.168.254.100","255.255.255.0","192.168.254.1","192.168.254.1","192.168.254.1"

OKOK

39.7.3 Defined values
Parameter<routing><dhcp><ip><netmask><gateway><dns1>

UBX-13002752 - R67

Type
NumberNumberDescription
Configures the connectivity type:• 0: the connectivity is provided by the cellular network• 1 (factory-programmed value): the connectivity is provided by an external hotspot
Configures the automatic DHCP IP address configuration of the wireless STA
interface (the DHCP client is enabled on the STA interface). Allowed values:

String• 0: disabled• 1 (factory-programmed value): enabled
IP address of the station.

StringString

The address must not be a network or broadcast address (see Notes for moredetails).
IP netmask of the station. The netmask must be a valid address.
IP address of the gateway.

String

The address must not be a network or broadcast address (see Notes for moredetails).
IP address of the first DNS server. The default value is an empty string.

39 Wi-Fi

Page 835 of 1001

u-blox cellular modules - AT commands manual

ParameterType<dns2>

StringDescription
If the parameter belongs to the IP/netmask network, it must not be a network or
broadcast address.
IP address of the second DNS server. The default value is an empty string.
If the parameter belongs to the IP/netmask network, it must not be a network or
broadcast address.

39.7.4 Notes
•

•

•
•
•
•
•

If <dhcp>=1 and the STA interface is associated to the external access point, the read command will
provide the IP configuration of the STA interface (IP address, netmask, gateway, IP address of the first
DNS server and IP address of the second DNS server).
The read command does not return the optional parameters if the module cannot connect in STA modeto the Wi-Fi network. When the connection of the STA interface is lost, a timeout of 10 s is required to
update the status.
In the "network" address the last 32-(maskbit) bits are all set to 0.
In the "broadcast" address the last 32-(maskbit) bits are all set to 1.
The IP address should not be equal to a "network" or "broadcast" address.
The maskbit is the prefix size of the subnet mask in CIDR (Classless Inter-Domain Routing) notation
expressed as a decimal number (see RFC 1518 [122] and RFC 1519 [123]).
The change of the <routing> value resets the ICMP timeout (for more details see the AT+UIPTABLES
command).

39.8 Wi-Fi station signal level indicator +UWSTACSQ+UWSTACSQ
Modules
Attributes

TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-03A TOBY-L210-03S TOBY-L280-03A
TOBY-L280-03S
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

39.8.1 Description
Shows the signal level of the received packets by the Wi-Fi station interface. To be noticed that:• An error result code will be provided if the Wi-Fi station is not enabled• The information text response will be empty if the Wi-Fi station is enabled but it is not still associated toa Wi-Fi access point

39.8.2 Syntax
Type
Read

SyntaxAT+UWSTACSQ?

Response
Example[+UWSTACSQ: <last_beacon_pkt>, +UWSTACSQ: -75,-72,-70,-72<average_beacon_pkt>,<last_data_OKpkt>,<average_data_pkt>]OK39.8.3 Defined values
ParameterType<last_beacon_pkt> Number<average_beacon_
Numberpkt><last_data_pkt>
Number<average_data_pkt> Number

UBX-13002752 - R67

Description
Signal level (dBm) of the last received beacon packet. The range goes from -25 to -94.
Average signal level (dBm) of received beacon packets. The range goes from -25 to 94.
Signal level (dBm) of the last received data packet. The range goes from -25 to -94.
Average signal level (dBm) of received data packets. The range goes from -25 to -94.

39 Wi-Fi

Page 836 of 1001

u-blox cellular modules - AT commands manual

39.9 Wi-Fi access point connected stations list
+UWAPSTALIST+UWAPSTALIST
Modules
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
No
No
+CME Error

39.9.1 Description
Lists all the stations connected to the Wi-Fi access point.

39.9.2 Syntax
Type
Read

SyntaxAT+UWAPSTALIST?

Response[+UWAPSTALIST: <mac>,<received_signal_level>

Example+UWAPSTALIST: "0
1:23:45:67:89:ab",-44[..]]+UWAPSTALIST: "0
1:23:45:67:89:cd",-53

OKOK

39.9.3 Defined values
Parameter<mac><received_signal_
level>Type
StringNumberDescription
MAC address of the station
Received signal level expressed in dBm. The range goes from -30 to -94

39.10 Wi-Fi access point MAC address +UWAPMACADDR+UWAPMACADDR
Modules
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
No
No
+CME Error

39.10.1 Description
Shows the Wi-Fi access point MAC (physical) address. The same MAC address is also valid for the stationmode.
An error result code is provided when the Wi-Fi module is disabled.

39.10.2 Syntax
Type
ActionSyntaxAT+UWAPMACADDRTestAT+UWAPMACADDR=?

Response
Example+UWAPMACADDR: <access_point_ +UWAPMACADDR: "00:0
MAC_address>
6:C6:38:1A:B2"
OK
OK

OK

39.10.3 Defined values
Parameter<access_point_
MAC_address>

UBX-13002752 - R67

TypeStringDescription
Access point MAC (physical) address.

39 Wi-Fi

Page 837 of 1001

u-blox cellular modules - AT commands manual

39.11 Web user interface configuration +UWWEBUI+UWWEBUI
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
NVM
No
+CME Error

39.11.1 Description
Configures the access to the Web user interface. See Web User Interface (WebUI) for a complete descriptionof Web user interface.

39.11.2 Syntax
Type
Set

SyntaxAT+UWWEBUI=<action>

Response
OK

ExampleAT+UWWEBUI=1

Read

AT+UWWEBUI?

+UWWEBUI: <action>OK+UWWEBUI: 1

Test

AT+UWWEBUI=?

OK+UWWEBUI: (list of supported<action>s)

OK+UWWEBUI: (0,1)
OKOK

39.11.3 Defined values
Parameter<action>Type
NumberDescription
Configures the access to the Web graphical access. Allowed values:••

0 (factory-programmed value): disabled. Access to the Web user interface is notallowed
1: enabled. Access to the Web user interface is allowed

39.12 Web user interface customization through FTP service+UWWEBUIFTP+UWWEBUIFTP
Modules
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
NVM
No
+CME Error

39.12.1 Description
Enables or disables the FTP access to certain files of the HTTP server running the Web user interface, inparticular HTML pages, CSS stylesheets/images, templates and some config files. The access to the web
pages of the HTTP server allows the customization of the user interface layout.
The accessible parts are put in the data partition of the module. The Web user interface can be customized
even if it is disabled. See Web User Interface (WebUI) for a complete description of the Web user interface.
The FTP access is configurable using this AT command and also on the web page itself. Once the FTP accessis enabled, an external FTP client should be used to access the Web user interface data/files.
This AT command and the Web user interface can also be used to revert the Web user interface to thefactory-programmed style.
Web page settings for the customization feature can be found on the Settings -> System page of the WebUI.
It provides the same options as the AT command, plus a control to clear the template cache. The latter forces
the template system to be visible immediately.

UBX-13002752 - R67

39 Wi-Fi

Page 838 of 1001

u-blox cellular modules - AT commands manual

39.12.2 Syntax
Type
Set

SyntaxAT+UWWEBUIFTP=<status>

Response
OK

ExampleAT+UWWEBUIFTP=1

Read

AT+UWWEBUIFTP?

+UWWEBUIFTP: <status>

OK+UWWEBUIFTP: 1

Test

AT+UWWEBUIFTP=?

OK+UWWEBUIFTP: (list of supported<status>s)

OK+UWWEBUIFTP: (0-2)
OKOK

39.12.3 Defined values
Parameter<status>Type
NumberDescription
Configures the access to the Web graphical access. Allowed values:•••

0 (factory-programmed value): disabled. Access to the Web user interface is notallowed
1: enabled. Access to the Web user interface through FTP service is allowed
2: revert the factory-programmed Web user interface; this value is not stored; theprevious <status> remains stored in NVM

39.13 Wi-Fi module firmware reset +UWFWRESET+UWFWRESET
Modules
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
No
No
+CME Error

39.13.1 Description
Resets all the configuration parameters listed in Table 93 to their factory-programmed settings andautomatically restarts the system.

39.13.2 Syntax
Type
Set

SyntaxAT+UWFWRESET=<reset>

Response
OK

ExampleAT+UWFWRESET=1

Test

AT+UWFWRESET=?

+UWFWRESET: (list of supported<reset>s)

OK+UWFWRESET: (1)OKOK

39.13.3 Defined values
Parameter<reset>Type
NumberDescription
Allowed value:•

1: reset user configuration

39.13.4 Notes
A graphical user interface (WebUI) allows the configuration of some parameters. The +UWFWRESET AT
command resets the parameters set both with WebUI and the AT command interface. The +UWFWRESET AT
command does not revert the layout of the WebUI to the factory-programmed one. The latter operation shouldbe performed with the +UWWEBUIFTP AT command; see the command description for further information
regarding the WebUI revert operation.
Parameter<ssid><security>

UBX-13002752 - R67

Configurable with
+UWAPCFG, +UWSTACFG, WebUI+UWAPCFG, +UWSTACFG, WebUI

39 Wi-Fi

Description
ESSID of the wireless network
Wireless authentication type

Page 839 of 1001

u-blox cellular modules - AT commands manual

Parameter<psk><region><channel><mode><enable><ip><netmask><dhcp_start><dhcp_stop><routing><dhcp><gateway><dns1><dns2><mac><received_signal_level><reset><wifi_mode><mgr><band><rate><power><test_mode><bw>
WebUI password
Network profile
Connection nameReset counter
Language
System reset
APN
Roaming
PIN
User
Password
Authentication

Configurable with
+UWAPCFG, +UWSTACFG, WebUI+UWAPCFG, WebUI+UWAPCFG, +UWTEST, WebUI+UWAPCFG, WebUI+UWSTACFG, WebUI+UWAPIPCFG, +UWSTAIPCFG, WebUI+UWAPIPCFG, +UWSTAIPCFG, WebUI+UWAPIPCFG+UWAPIPCFG+UWSTAIPCFG+UWSTAIPCFG, WebUI+UWSTAIPCFG, WebUI+UWSTAIPCFG, WebUI+UWSTAIPCFG, WebUI+UWAPSTALIST+UWAPSTALIST+UWFWRESET, WebUI+UWCFG+UWCFG, WebUI+UWTEST, WebUI+UWTEST, WebUI+UWTEST, WebUI+UWTEST, WebUI+UWTEST, WebUI
WebUI
WebUI
WebUI
WebUI
WebUI
WebUI
WebUI
WebUI
WebUI
WebUI
WebUI
WebUI

Description
Security passphrase
Country code
Wireless channel
IEEE standard protocol
Wireless station mode
IP address of the wireless interface
Netmask of the wireless interface
Start IP address of the DHCP server range
Stop IP address of the DHCP server range
Preferred routing configuration
DHCP client configuration
Gateway IP address
Primary DNS
Secondary DNS
Wireless station MAC
Received signal level from wireless clients
Enable factory-programmed reset
Wireless power mode configuration
Connection manager mode
Wireless band
Channel bit rate
Transmission power of the wireless interface
Test mode
Channel bandwidth
WebUI password
List of available network profiles for the SIM card
Name to identify specific cellular network configuration
Language setting of the WebUI
System reboot
Access Point Name
Roaming configuration
PIN entry
User name, if requested by the cellular provider
Password, if requested by the cellular provider
Authentication mode if a user name and password are
required

Table 93: List of parameters updated with +UWFWRESET

39.14 Wi-Fi network scan +UWSCAN+UWSCAN
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
< 15 s+CME Error

39.14.1 Description
Scans the surroundings for wireless networks and provide information on their configuration. The informationtext response returns one or more lines providing networks in the immediate surroundings.

UBX-13002752 - R67

39 Wi-Fi

Page 840 of 1001

u-blox cellular modules - AT commands manual

39.14.2 Syntax
Type
ActionSyntaxAT+UWSCAN

Response
Example+UWSCAN: <bssid>,<op_mode>,+UWSCAN: "45:94:FC:7D:88:21",1,<ssid>,<channel>,<received_"test1",1,-72,18,4,4
signal_level>,<authentication_+UWSCAN: "44:94:FC:7A:89:20",1,suites>[,<unicast_ciphers>,<group_"test2",11,-83,18,4,4
ciphers>]+UWSCAN: "44:04:FC:7D:88:20",1,[...]"test3",9,-48,0
OK+UWSCAN: "44:95:FC:7E:88:20",2,"test4",6,-83,0OK

39.14.3 Defined values
Parameter<bssid><op_mode><ssid><channel><received_signal_
level><authentication_
suites><unicast_ciphers><group_ciphers>

Type
StringNumberDescription
The MAC address of the external hotspot
Operation mode of the external hotspot

StringNumberNumber• 1: infrastructured• 2: ad-hoc
The SSID name of external wireless network
The channel the external wireless network
Signal strength value for the external wireless network in dBm

NumberNumberNumberAuthentication suite supported by the external wireless network. The number ispresented as a hexadecimal value; the meaning of each bit is as follows:• Bit 0: shared secret• Bit 1: PSK• Bit 2: EAP• Bit 3: WPA• Bit 4: WPA2
FF string is provided if an unsupported authentication suite is supported by theexternal wireless network (i.e. enterprise authentication level).
Unicast ciphers supported by the external wireless network. The number is presented
as a hexadecimal value; the meaning of each bit is as follows:• Bit 2: TKIP
• Bit 3: AES/CCMPGroup ciphers supported by the external wireless network. The number is presented
as a hexadecimal value; the meaning of each bit is as follows:••

Bit 2: TKIP
Bit 3: AES/CCMP

39.14.4 Notes•<authentication_suites>=FF is provided if an unsupported authentication suite is in use by the external
wireless network (i.e. enterprise authentication level).

39.15 Maximum allowed output power configuration +UWMP+UWMP
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
partial
No
No
No+CME Error

39.15.1 Description
Configures the maximum allowed output (transmission) power of the Wi-Fi module.

UBX-13002752 - R67

39 Wi-Fi

Page 841 of 1001

u-blox cellular modules - AT commands manual

The configuration is applied at run time, when the Wi-Fi interface is running in access point (AP) or station(STA) mode.

39.15.2 Syntax
Type
Set

SyntaxAT+UWMP=<max_output_power>

Response
OK

ExampleAT+UWMP=4Read

AT+UWMP?

+UWMP: <max_output_power>

OK+UWMP: 4

Test

AT+UWMP=?

OK+UWMP: (list of supported <max_
output_power>s)

OK+UWMP: (4-18)
OKOK

39.15.3 Defined values
Parameter<max_output_
power>

Type
NumberDescription
Output power in dBm. Allowed range is in:• TOBY-L200-02S / TOBY-L210-02S / TOBY-L210-62S / TOBY-L210-65S /TOBY-L220 / TOBY-L280-02S - [4,18]. The default value is 18.
• TOBY-L200-03A / TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A /TOBY-L210-03S / TOBY-L280-03A / TOBY-L280-03S - [4,17]. The default value is
17. On TOBY-L200-03S-00, TOBY-L201-02S-00, TOBY-L210-03S-00, TOBY-L28003S-00 the range goes from 4 to 18. The default value is 18.

39.16 Wi-Fi regulatory domains block configuration+UWREGBLOCK+UWREGBLOCK
Modules
TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
Attributes
full
No
NVM
No
+CME Error

39.16.1 Description
Configures the Wi-Fi regulatory domains block feature.
Since every country applies its own regulations regarding the use of Wi-Fi networks, the Wi-Fi regulatory
domains block feature avoids conflicts with the Wi-Fi limitations of the countries where the module will be used.
The Wi-Fi regulatory domains block feature is enabled when the Wi-Fi interface is active or when the WebUI
is enabled.
Three regulatory domains are defined:• "US" (United States): with the Wi-Fi regulatory domains block feature, this regulatory domain is
automatically applied when the module is registered to a North American cellular network;• "JP" (Japan): with the Wi-Fi regulatory domains block feature, this regulatory domain is automaticallyapplied when the module is registered to a Japanese cellular network;• "EU" (Europe / rest of the world): with the Wi-Fi regulatory domains block feature, this regulatory domain is
automatically applied when the module is not registered to a North American or a Japanese cellular network.
The limitations defined for every regulatory domain regard the list of available channels, the maximum
transmission power and the channel bit rate. In particular, if the previously selected channel falls outside
the allowed range of the currently applied domain, an automatic channel selection will be adopted. Further
information regarding the allowed settings for every regulatory domain can be found in the +UWAPCFG AT
command description.
The Wi-Fi regulatory domains block implies the following behavior:••

TOBY-L200 / TOBY-L201 - work in "US" regulatory domain and the domain cannot change;
TOBY-L210 / TOBY-L280 - start with "EU" regulatory domain as factory-programmed value;

UBX-13002752 - R67

39 Wi-Fi

Page 842 of 1001

u-blox cellular modules - AT commands manual••

TOBY-L220 - start with "JP" regulatory domain as factory-programmed value;
TOBY-L210 / TOBY-L220 / TOBY-L280 - when the module is out of coverage/not registered to any network(this implies that the current position of the module is unknown), the regulatory domain is automaticallyreverted to the "US" regulatory domain, which is the most restrictive in terms of channel usage, after aconfigurable <timeout>:
o the factory-programmed value of the timeout is 60 minutes;
o the timeout can be set from a minimum value of 10 minutes to a maximum of 60 minutes.
o during the period in which the module is out-of-coverage/not registered to any network (this implies
that the current position of the module is unknown) and the timeout is not elapsed, the physical Wi-Fi
setting can differ from the setting shown by the +UWAPCFG AT command. The user is able to change
the setting referred to the new valid regulatory domain, even if it is not applied. A complete Wi-Fi power
cycle will apply the new setting and the timeout will not be taken into account.
The last applied regulatory domain is stored in NVM and it is used for the next Wi-Fi activation; the current
regulatory domain can be derived from the <region> parameter returned by +UWAPCFG read command.

39.16.2 Syntax
Type
Set

SyntaxAT+UWREGBLOCK=[<timeout>]

Response
OK

ExampleAT+UWREGBLOCK=10Read

AT+UWREGBLOCK?

+UWREGBLOCK: <timeout>

OK+UWREGBLOCK: 10

Test

AT+UWREGBLOCK=?

OK+UWREGBLOCK: (list of supported<timeout>s)

OK+UWREGBLOCK: (10-60)
OKOK

39.16.3 Defined values
Parameter<timeout>Type
NumberDescription
Duration (in minutes) of the timer set when the module enters in out-of-coverage/
not registered state; at its expiration, the Wi-Fi regulatory domain is automaticallyreverted to "US". The range goes from 10 to 60; the factory-programmed and default
value is 60.

39.17 Wi-Fi test mode +UWTEST+UWTEST
Modules
Attributes

TOBY-L200-02S TOBY-L200-03A TOBY-L200-03S TOBY-L201-02S TOBY-L210-02S TOBY-L210-03A
TOBY-L210-03S TOBY-L210-62S TOBY-L210-65S TOBY-L220 TOBY-L280
SyntaxPIN required
Settings saved Can be aborted Response time Error reference
full
No
No
No
+CME Error

39.17.1 Description
Initiates the Wi-Fi module test mode. A reboot of the Wi-Fi / cellular subsystem is needed to exit the test mode.
Performs one of these procedures to exit from the test mode:• Reboot the Wi-Fi / cellular subsystem with the +CFUN command• Set the Wi-Fi power mode by the use of +UWCFG AT command
If the Wi-Fi / cellular subsystem is rebooted when it is in test mode, at the next boot the Wi-Fi module powermode is disabled; to turn it on issue the +UWCFG=1 command.

39.17.2 Syntax
Type
Set

SyntaxResponse
AT+UWTEST=<password>,<band>, OK<channel>,<rate>,<power>,<test_mode>,<bw>

Read

AT+UWTEST?

UBX-13002752 - R67+UWTEST: <version>

39 Wi-Fi

ExampleAT+UWTEST="password",0,1,1,13,3,
0
OK+UWTEST: "SD8787-14.44.35.p238M2614525-GPL-(FP44)"

Page 843 of 1001

u-blox cellular modules - AT commands manualType

SyntaxResponse
OK

ExampleOK

Test

AT+UWTEST=?

+UWTEST: "",(list of supported+UWTEST: "",(0),(1-14),(1-4,6-22),(6<band>s),(list of supported
18),(0-3),(0,1)<channel>s),(list of supported
OK<rate>s),(list of supported<power>s),(list of supported <test_mode>s),(list of supported <bw>s)OK

39.17.3 Defined values
Parameter<password><band>Type
StringNumber<channel><rate>

NumberNumber<power>Number<test_mode>

Number<bw>

Number<version>

NumberDescription
The command is password protected. The password is provided by u-blox.
Wi-Fi band. Allowed values:• 0: 2.4 GHz band
1-14: 2.4 GHz RF channel
Data rate. Allowed values:• 1-4: 1/2/5.5/11 Mb/s DSSS
• 6-14: 6/9/12/18/24/36/48/54/72 Mb/s OFDM
• 15-22: MCS0-7
Output power. Allowed values:• 6-18: Tx power in dBm
Test mode. Allowed values:• 0: reserved• 1: packet Tx• 2: continuous modulated Tx• 3: carrier mode (no modulation)
Channel bandwidth. Allowed values:• 0: 20 MHz bandwidth• 1: 40 MHz bandwidthFirmware version of Wi-Fi module39.17.4 Notes
TOBY-L200-00S / TOBY-L201-01S / TOBY-L210-00S / TOBY-L210-60S / TOBY-L210-62S /TOBY-L210-65S / TOBY-L220• The <password> parameter is not supported.

UBX-13002752 - R67

39 Wi-Fi

Page 844 of 1001

u-blox cellular modules - AT commands manual

A Appendix: Error result codes
A.1 Mobile termination error result codes +CME ERROR
Numeric error code
0
1
2
3
4
5
6
7
10
11
12
13
14
15
16
17
18
20
21
22
23
24
25
26
27
30
31
32
40
41
42
43
44
45
46
47
50
51
52
53
54
55
56
57
100
103
106
107
108

UBX-13002752 - R67

Description
Phone failure
No connection to phone
Phone-adaptor link reserved
Operation not allowed
Operation not supported
PH-SIM PIN required
PH-FSIM PIN required
PH-FSIM PUK required
SIM not inserted
SIM PIN required
SIM PUK required
SIM failure
SIM busy
SIM wrong
Incorrect password
SIM PIN2 required
SIM PUK2 required
Memory fullInvalid index
Network not foundMemory failure
Text string too long
Invalid characters in text string
Dial string too long
Invalid characters in dial string
No network service
Network timeout
Network not allowed - emergency calls only
Network personalisation PIN required
Network personalisation PUK required
Network subset personalisation PIN required
Network subset personalisation PUK required
Service provider personalisation PIN required
Service provider personalisation PUK required
Corporate personalisation PIN required
Corporate personalisation PUK required
Incorrect parameters
Command implemented but currently disabled
Command aborted by user
Not attached to network due to MT functionality restrictions
Modem not allowed - MT restricted to emergency calls only
Operation not allowed because of MT functionality restrictions
Fixed dial number only allowed - called number is not a fixed dial number
Temporarily out of service due to other MT usage
Unknown
Illegal MS
Illegal ME
GPRS services not allowed
GPRS and non GPRS services not allowed

A Appendix: Error result codes

Page 845 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
111
112
113
114
115
122
125
126
127
128
129
130
131
132
133
134
135
137
138
140
141
142
143
144
145
146
147
148
149
150
153
154
155
156
159
160
165
166
168
169
170
171
172
173
174
175
176
177
178
179
180
181
189
190
191

UBX-13002752 - R67

Description
PLMN not allowed
Location area not allowed
Roaming not allowed in this location area
GPRS services not allowed in this PLMNNo Suitable Cells In Location Area
Congestion
Not authorized for this CSG
Insufficient resources
Missing or unknown APN
Unknown PDP address or PDP type
User authentication failed
Request rejected by Serving GW or PDN GW
Request rejected, unspecified
Service option not supported
Requested service option not subscribed
Service option temporarily out of order
NS-api already used
EPS QoS not accepted
Network failure
Feature not supported
Semantic error in the TFT operation
Syntactical error in the TFT operation
Unknown PDP context
Semantic errors in packet filter(s)Syntactical errors in packet filter(s)PDP context without TFT already activated
PTI mismatch
Unspecified GPRS error
PDP authentication failure
Invalid mobile class
ESM information not received
PDN connection does not exist
Multiple PDN connections for a given APN not allowed
User Busy
Uplink Busy/ Flow Control
Bearer handling not supported
Maximum number of EPS bearers reached
Requested APN not supported in current RAT and PLMN combination
Network failure
IMSI unknown in VLR
Congestion
Last PDN disconnection not allowed
Semantically incorrect message
Mandatory information element error
Information element non-existent or not implemented
Conditional IE error
Protocol error, unspecified
Operator determined barring
Maximum number of PDP contexts reached
Requested APN not supported in current RAT and PLMN combination
Request rejected, bearer control mode violation
Invalid PTI value
Semantically incorrect message
Invalid mandatory IE
Message type non existent

A Appendix: Error result codes

Page 846 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
192
193
194
195
197
254
255
262
300
301
302
303
304
305
310
311
312
313
314
315
316
317
318
320
321
322
330
331
332
340
500
608
701
702
1001
1003
1006
1008
1016
1017
1018
1019
1021
1022
1026
1027
1028
1029
1030
1031
1034
1038
1041
1042
1043

UBX-13002752 - R67

Description
Message type not compatible
IE non existent
Conditional IE error
Message not compatible
Protocol error unspecified
Invalid error mapping
Internal error
SIM blocked
ME failure
SMS service of ME reserved
Operation not allowed
Operation not supported
Invalid PDU mode parameter
Invalid text mode parameter(U)SIM not inserted(U)SIM PIN required
PH-(U)SIM PIN required(U)SIM failure(U)SIM busy(U)SIM wrong(U)SIM PUK required(U)SIM PIN2 required(U)SIM PUK2 required
Memory failure
Invalid memory index
Memory full
SMSC address unknown
No network service
Network timeout
No +CNMA acknowledgement expected
Unknown error
Voice call active
Incorrect security code
Max attempts reached
Unassigned (unallocated) number
No route to destination
Channel unacceptable
Operator determined barring
Normal call clearing
User busy
No user responding
User alerting, no answer
Call rejected
Number changed
Non selected user clearing
Destination out of order
Invalid number format (incomplete number)
Facility rejected
Response to STATUS ENQUIRYNormal, unspecified
No circuit/channel available
Network out of order
Temporary failure
Switching equipment congestion
Access information discarded

A Appendix: Error result codes

Page 847 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
1044
1047
1049
1050
1055
1056
1057
1058
1059
1063
1065
1068
1069
1070
1079
1081
1087
1088
1091
1095
1096
1097
1098
1099
1100
1101
1102
1111
1112
1127
1142
1143
1149
1243
1244
1279
1283
1500
1501
1502
1503
1504
1505
1520
1521
1530
1531
1540
1542
1543
1544
1545
1546
1547
1548

UBX-13002752 - R67

Description
requested circuit/channel not available
Resources unavailable, unspecified
Quality of service unavailable
Requested facility not subscribed
Incoming calls barred within the CUG
Collision with network initiated request
Bearer capability not authorized
Bearer capability not presently available
Unsupported QCI value
Service or option not available, unspecified
Bearer service not implemented
ACM equal to or greater than ACMmax
Requested facility not implemented
Only restricted digital information bearer capability is available
Service or option not implemented, unspecified
Invalid transaction identifier value
User not member of CUG
Incompatible destination
Invalid transit network selection
Semantically incorrect message
Invalid mandatory information
Message type non-existent or not implemented
Message type not compatible with protocol state
Information element non-existent or not implemented
Conditional IE error
Message not compatible with protocol state
Recovery on timer expiry
Protocol error, unspecified
APN restriction value incompatible with active EPS bearer context
Interworking, unspecified
Network Error
Invalid EPS bearer identity
Last PDN disconnection not allowed
Emm Error Unspecified
Esm Error Unspecified
Number not allowed
CCBS possible
Wrong GPIO identifier
Set GPIO default error
Select GPIO mode error
Read GPIO error
Write GPIO error
GPIO busy
Wrong ADC identifier
Read ADC error
IPv4 only allowed
IPv6 only allowed
Wrong ringer identifier
LLC or SNDCP failure
Regular deactivation
Reactivation requested
Single address bearers only allowed
Invalid transaction identifier value
APN restriction val incompatible with PDP context
PDP activation rejected

A Appendix: Error result codes

Page 848 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1600
1560
1561
1612
1613
1614
1615
1616
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1660
1670
1671
1672
1673

UBX-13002752 - R67

Description
unknown PDP address or PDP type
GPRS generic operation error
GPRS invalid APN
GPRS authentication failure
GPRS QoS parameters inconsistent
GPRS network failure
GPRS context busy
CSD generic operation error
CSD undefined profile
CSD context busy
PLMN scan not allowed
FFS error
PDP type IPv4 only allowed
PDP type IPv6 only allowed
FILE NOT FOUND
Cannot open file
TAC value not allowed
OTP failure
Wrong Check Digit
Buffer fullFFS initializing
FFS already open file
FFS not open file
FFS file not foundFFS file already created
FFS illegal id
FFS illegal file handle
FFS illegal typeFFS illegal modeFFS file range
FFS operation not possible
FFS write error
FFS user id error
FFS internal fatal error
FFS memory resource error
FFS maximum number of files exceeded
FFS memory not available
FFS invalid filename
FFS streaming not enabled
FFS operation not allowed on static file
FFS memory table inconsistency
FFS not a factory default file
FFS requested memory temporary not available
FFS operation not allowed for a directory
FFS directory space not available
FFS too many streaming files open
FFS requested dynamic memory temporary not available
FFS user provided a NULL parameter instead of a suitable buffer
FFS timeout
Command line too longCall barred - Fixed dialing numbers only
USEC remote object wrong state
USEC ROT not personalized
USEC loss of connectivity
USEC service not authorized

A Appendix: Error result codes

Page 849 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
1674
1675
1676
1677
1678
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1800
1801
1802
1803
1804
1805
1806
1900
1901
1902
1903
1904
1910
1911
1912
1913
1914
1950
1951
1952
2000
3000
4000
4001
5000
5001
5002

Description
USEC FW package installation required
USEC FW package not valid
USEC resource not available
USEC data not available
USEC timeout
GPS GPIO not configured
GPS GPIO ownership error
Invalid operation with GPS ON
Invalid operation with GPS OFF
Invalid GPS aiding mode
Reserved GPS aiding mode
GPS aiding mode already set
Invalid GPS trace mode
Parameter valid only in case of GPS OTA
GPS trace invalid server
Invalid TimeZone
Invalid value
Invalid parameter
Invalid operation with LOC running / GPS Busy
No ongoing call
IBM busy / eCall already armed/active
IBM feature off / eCall feature off
Wrong IBM requested
Audio resource not available
ECALL restriction
eCall invalid dial number
No SAP Server Connection
SAP Protocol Error
SAP Connection failure
SAP Server Disconnection
SAP Other terminal using service
USECMNG import timeout expired (no input for > 20 s)
USECMNG import file size exceeds limit
USECMNG no memory available
USECMNG invalid certificate/key format
USECMNG database full
CDC-ECM is not available
CDC-ECM is busy
No DHCP Packets received from the DTE
Command timeout
Command aborted
APN configuration mismatch
IP type configuration mismatch
FOTA package download state or name mismatch
FOTA package data corrupted
FOTA memory is in use

A.2 Message service error result codes +CMS ERROR
Numeric error code
1
5
8
10
17

UBX-13002752 - R67

Description
Unassigned (unallocated) number
Delta firmware unavailable on FOTA server
Operator determined barring
Call barred
Network failure

A Appendix: Error result codes

Page 850 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
21
22
27
28
29
30
38
41
42
47
50
69
81
95
96
97
98
99
111
127
128
129
130
143
144
145
159
160
161
175
176
192
193
194
195
196
197
198
199
208
209
210
211
212
213
287
290
296
297
300
301
302
303
304
305

UBX-13002752 - R67

Description
Short message transfer rejected
Memory capacity exceeded
Destination out of service
Unidentified subscriber
Facility rejected
Unknown Subscriber
Network out of order
Temporary failure
Congestion
Resources unavailable, unspecified
Requested facility not subscribed
Requested facility not implemented
Invalid short message reference value
Invalid message, unspecified
invalid mandatory information
Message type non-existent or not implemented
Message not compatible with short message protocol state
Information element non-existent or not implemented
Protocol error, unspecified
Interworking, unspecified
Telematic interworking not supported
Short message type 0 not supported
Cannot replace short message
Unspecified TP-PID error
Data coding scheme (alphabet) not supported
Message class not supported
Unspecified TP-DCS error
Command cannot be actioned
Command unsupported
Unspecified TP-Command error
TPDU not supported
SC busy
No SC subscription
SC system failure
Invalid SME address
Destination SME barred
SM Rejected-Duplicate SM
TP-VPF not supported
TP-VP not supported
SIM SMS storage full
No SMS storage capability in SIM
Error in MS
Memory Capacity Exceeded
SIM Application Toolkit Busy
SIM data download error
Network failure unspecified
Network no resource
Radio Resources not Aailable due to DUAL SIM operation
Out of service due to DUAL SIM operation
ME failure
SMS service of ME reserved
Operation not allowed
operation not supported
Invalid PDU mode parameter
Invalid Text mode parameter

A Appendix: Error result codes

Page 851 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
310
311
312
313
314
315
320
321
322
330
331
332
340
350
351
352
353
354
355
356
357
358
359
364
365
368
369
370
371
372
373
360
361
362
363
366
367
500
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528

UBX-13002752 - R67

Description
SIM not inserted
SIM PIN required
PH-SIM PIN required
SIM failure
SIM busy
SIM wrongmemory failure
invalid memory index
memory full
SMSC address unknown
no network service
network timeout
no +CNMA acknowledgement expected
Unassigned (unallocated) number
Operator determined barring
Call barred
ME failure
Short message transfer rejected
Number changed
Destination out of order
Unidentified subscriber
Facility rejected
Unknown subscriber
Requested facility not subscribed
Requested facility not implemented
Invalid mandatory information
Message type non-existent or not implemented
Message not compatible with short message protocol state
Information element non-existent or not implemented
Protocol error, unspecified
Interworking, unspecified
Network out of order
Temporary failure
Congestion
Resources unavailable, unspecified
Invalid short message transfer reference value
Invalid message, unspecified
unknown error
Relay Protocol Acknowledgement
SMS timer expired
SMS forwarding availability failed
SMS forwarding availability aborted
MS invalid TP-Message-Type-Indicator
MS no TP-Status-Report in Phase 1
MS no TP-Reject-Duplicate in phase 1
MS no TP-Replay-Path in Phase 1
MS no TP-User-Data-Header in Phase 1
MS missing TP-Validity-Period
MS invalid TP-Service-Centre-Time-Stamp
MS missing TP-Destination-Address
MS invalid TP-Destination-Address
MS missing Service-Centre-Address
MS invalid Service-Centre-Address
MS invalid alphabet
MS invalid TP-User-Data-length

A Appendix: Error result codes

Page 852 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
543
544
545
546
547
548
548
549
555
556
557
558
560
561
562
563
564
565
566
567
568
569
571
572
576
577
579
580
581
583
584
585
586
587
590
591
595
601
604
605

UBX-13002752 - R67

Description
MS missing TP-User-Data
MS TP-User-Data to long
MS no Command-Request in Phase 1
MS Cmd-Req invalid TP-Destination-Address
MS Cmd-Req invalid TP-User-Data-Length
MS Cmd-Req invalid TP-User-Data
MS Cmd-Req invalid TP-Command-Type
MN MNR creation failed
MS CMM creation failed
MS network connection lost
MS pending MO SM transfer
RP-Error OK
RP-Error OK no icon display
SMS-PP Unspecified
SMS rejected By SMS CONTROLFDN check failed
Service Centre Address(SCA) FDN failed
Destination Address(DA) FDN failed
BDN check failed
Unspecified SMS PP error
Undefined Result
No Route To Destination
Channel Unacceptable
No Circuit/Channel Available
Access Information Discarded
Requested Circuit/Channel Not Available By Other Side
Quality Of Service Unavailable
Bearer Capability Not Authorized
Bearer Capability Not Presently Available
Service or Option Not Available, Unspecified
Bearer Service Not Implemented
ACM Equal to or Greater Than ACMmax
Only Restricted Digital Information Bearer Capability Is Available
Service or Option Not Implemented, Unspecified
User Not Member of CUG
Incompatible By Destination
Invalid Transit Network Selection
Message Not Compatible With Protocol State
Recovery On Timer Expiry
Data Call Active
Speech Call Active
MOC Setup Rejected Due to Missing ACM Info
Temporary Forbidden Call Attempt
Called Party is Blacklisted
Temporary Forbidden Call Attempt No Service
Temporary Forbidden Call Attempt Limited Service
Client Temporary Barred
Dual Service Call Active
Atc Fclass Not Speech
Client Not Registrated
Active Client Gone
Rejected By Call Control
Invalid ALS Line
MM No Service (out of coverage)
MM Access Class Barred (RR_REL_IND During RR Conn. Establishment)

A Appendix: Error result codes

Page 853 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
606
608
609
610
612
614
615
616
618
619
620
621
622
623
624
625
626
627
628
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
647
649
650
653
654
656
657
658
659
660
661
662
663
664
665
669
670
671
672

UBX-13002752 - R67

Description
ME Busy -CM Service Request Already Pending
Rejected Due To SUP Timer Expiry
Rejected Due To USSD Busy
Rejected Due To SS BusySIM Toolkit Request Is Rejected, Because Another SIM Toolkit Request
Is Pending
Rejected Because SIM Toolkit Request Is Not Yet Answered By The User
MN Setup SS Error
Call Controller Blocked (Other Call Command Pending)
Environment Parameter Not Set Correctly (Fclass/Cmod)
Other Blocking Call Present
Lower Layer Failure
The Authentication Proedure Failed
The Packet-Switched Registration Procedure Failed
CM Service Reject From The Network
The ABORT Message Was Received From The Network
Timer Expiry
IMSI Deatch Was Initiated
Normal RR Connection Release (2G)
Registration Failed
Failure Due To Handover
Link Establishment Failure
Random Access FailureRadio Link Aborted
Lower Layer Failure in Layer 1
Immediate Assignment Reject
Failure Due To Paging
Abnormal Release Unspecified
Abnormal Release Channel Unacceptable
Abnormal Release Timer Expired
Abnormal Release No Act On Radio Path
Preemptive Release
UTRAN Configuration Unknown
Handover Impossible
Channel Mode Unacceptable
Lower Layer Failure From NW
Conditional IE Error
No Cell Allocation Available
Re Establishment RejectDirected Sigconn Re Establishment
Release of RRC connection Witout Network Activity(3G) Lower Layer
Failure Downlink
Lower Layer Failure Uplink
Cell Barred Due To Authentication Failure
Signalling Connection Release
CS Connection Release Triggered By MM
RRC Connection Establishment Failure
RRC Connection Establsihment Reject With Redirection
Resource Conflict
Lower Layer Failure in Layer 2
L2 Cause T200 Expiry N200 Plus 1 Times
RR Connection Release Due to BAND Change (2G)
Release of the RRC Connection Due to Out of Service in Cell_Fach (3G)
Release of the RRC Connection Due to Not Matching PLMN in Shared
Networks(3G)
Error Happens While Call Is Already Disconnected / Late Error

A Appendix: Error result codes

Page 854 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
674
675
676
677
680

Description
SIM Toolkit Cannot Initiate A Call, Because MMI Is Not Registered
SIM Toolkit Call Setup Request Is Rejected Due User Did Not Accept
Proactive SIM Appl Terminated By User
SIM Toolkit Originated SIM Reset (Refresh Request)
Dial String/Number Incorrect

A.3 +CEER error result codes
A.3.1 TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 series
The following table lists the supported values for <cause> (number) and <error_description> (string) for +CEER
AT command if <type> assumes one of these values:• "CC setup error"• "CC modification error"• "CC release"• "SM attach error"• "SM detach"• "SM activation error"• "SM deactivation
In case the same <cause> values map to different <error_description> strings on the same product (see for
instance <cause> 129 on SARA-G3 series), they obviously refer to different <type> values, related to CS call
control or to PS session management failures.
<cause><error_description>

0
1
2
3
3
4
5
6
6
7
8
8

No cause information available
Unassigned (unallocated) numberx
SIM not provisioned
No route to destinationx
SIM not allowed
Call Failed
Call Failed
Channel unacceptablex
Phone not allowed
GPRS Service not allowed
Operator determined barringx
GPRS Service and Non GPRS service notallowedMS Identity cannot be Derived by
network
Implicitly Detached
SOS/Emergency calls only,PLMN not
allowedSOS/Emergency calls only,LA not
allowedSOS/Emergency calls only,roaming notallowed in LA
No Suitable cells in Location Area
Normal call clearingx
MSC Temporarily Not Reachable
User busyx
No user respondingx
User alerting, no answerx
MAC (Message Authentication Code)failure

9
10
11
12
13
15
16
16
17
18
19
20

UBX-13002752 - R67

LEON-G1

SARA-G3 LISA-U2

x

x
x

x

x

x

x

x

x

SARA-U2 TOBY-L2 / LARA-R2 /MPCI-L2 TOBY-R2
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x

x

x

x

x
x
x

x
x
x

x
x
x

x
x
x

A Appendix: Error result codes

x
x
x
x
x
x
x

Page 855 of 1001

u-blox cellular modules - AT commands manual<cause><error_description>

21
21
22
22
23
26
27
28

Call rejectedx
Synch failure
Number changedxError Congestion
SIM not allowed
Non selected user clearingx
Destination out of orderx
Invalid number format (incompletexnumber)Facility rejectedxResponse to STATUS ENQUIRYx
Normal, unspecified
x
Service Option Not supported
Requested Service option not subscribed
No circuit/channel availablex
Service temporarily out of order
Network out of orderxCall cannot be Identified
NO PDP Context Active
Temporary failurex
Switching equipment congestionx
Access information discardedxRequested circuit/channel not available x
Resources unavailable, unspecified
xRetry on New Cell beginning
Quality of service unavailable
x
Requested facility not subscribedxIncoming calls barred within the CUG
xBearer capability not authorizedxBearer capability not presently available x
Service or option not available,x
unspecified
Retry on New Cell End
Bearer service not implementedx
ACM equal to or greater than ACMmax x
Requested facility not implementedx
Only restr. digital information bearerxcapability
Service or option not implemented,x
unspecified
Invalid transaction identifier valuexUser not member of CUG
xIncompatible destinationx
Invalid transit network selectionx
Semantically incorrect message
x
Invalid mandatory informationx
Message type non-existent or notx
implemented
Message type not compatible withx
protocol state
Information element non-existent or not x
implemented
Conditional IE errorxMessage not compatible with protocolx
state
Recovery on timer expiry
x

29
30
31
32
33
34
34
38
38
40
41
42
43
44
47
48
49
50
55
57
58
63
63
65
68
69
70
79
81
87
88
91
95
96
97
98
99
100
101
102

UBX-13002752 - R67

LEON-G1

SARA-G3 LISA-U2
x

x

x

x

x
x
x

x
x
x

SARA-U2 TOBY-L2 / LARA-R2 /MPCI-L2 TOBY-R2
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x
x
x

x
x
x

x
x
x

x
x
x

x

x

x

x

x

x

x

x

x
x
x
x
x

x
x
x
x
x

x
x
x
x
x

x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x

x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x
x
x
x

x
x
x
x

x
x
x
x

x
x
x
x

x
x
x
x
x

x

x

x

x

x

x
x
x
x
x
x
x

x
x
x
x
x
x
x

x
x
x
x
x
x
x

x
x
x

x
x
x

x
x

x
x
x

x

x

x

x

x

x

x

x

x

x

x
x

x
x

x
x

x
x

x
x

x

x

x

x

x

A Appendix: Error result codes

Page 856 of 1001

u-blox cellular modules - AT commands manual<cause><error_description>

102
103
106
107
108

Unknown IMSIIllegal MS
Illegal ME
GPRS service not allowed
GPRS and non GPRS services notallowedOperator determined barring
Protocol error, unspecified
x
PLMN not allowed
Location area not allowedxRoaming not allowed in this location area x
LLC or SNDCP failure
Insufficient resources
Missing or unknown APN
Interworking, unspecifiedx
Unknown PDP address or PDP type
Outgoing calls barred within CUG
xUser authentication failed
No CUG selectedxActivation rejected by GGSN, Serving
GW or PDN GW
Unknown CUG indexx
Activation reject,unspecified
CUG index incompatible with requested x
basic service
Service not supported
CUG call failure, unspecifiedx
Requested service option not subscribed
Service not subscribed
CLIR not subscribedxService option temporarily out of order
CCBS possiblex
NSAPI already used
CCBS not possiblex
Regular PDP context deactivation
QoS not accepted
Network failure
Reactivation requested
Feature not supported
Semantic error in the TFT operation
Syntactical error in the TFT operation
Unknown PDP context
Semantic errors in packet filter(s)Syntactical errors in packet filter(s)PDP context without TFT alreadyactivated
Unspecified GPRS error
PDP authentication error
Single address bearers only allowed
ESM information not received
PDN connection does not exist
Multiple PDN connections for a given
APN not allowed
Collision with network initiated request
Unsupported QCI value

108
111
111
112
113
125
126
127
127
128
129
129
130
130
131
131
132
132
133
133
133
134
134
135
135
136
136
137
138
139
140
141
142
143
144
145
146
148
149
152
153
154
155
156
159

UBX-13002752 - R67

LEON-G1

SARA-G3 LISA-U2

SARA-U2 TOBY-L2 / LARA-R2 /MPCI-L2 TOBY-R2

x
x
x
x
x

x
x
x

x
x
x

x

x

x

x
x

x
x

x

x
x

x
x
x
x
x
x
x

x
x
x

x
x
x
x
x
x
x
x
x
x
x
x

x

x
x
x

x
x
x
x
x
x
x
x
x
x

x
x

x
x
x
x
x
x
x
x
x
x
x
x

x
x

x

x

x

x

x

x

x
x

x
x

x
x

x
x

A Appendix: Error result codes

x
x

x
x

x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 857 of 1001

u-blox cellular modules - AT commands manual<cause><error_description>

160
165

Bearer handling not supported
Maximum number of EPS bearers
reachedRequested APN not supported in current
RAT and PLMN combination
Invalid PTI value
APN restriction value incompatible withactive EPS bearer context
PTI already in use
EPS QoS not accepted
Invalid EPS bearer identity
PTI mismatch
Last PDN disconnection not allowed
PDN type IPv4 only allowed
PDN type IPv6 only allowed
APN resriction
Internal, unspecified
Out of memory
Invalid parameters
Data call active
Speech call active
Missing ACM information
Temporary forbidden
Called party is blacklisted
Blacklist is fullNo service
Limited service
Client conflict
Dual service call active
Unknown SIM error
Active Client is Gone
SIM status failure
Rejected by call control
FDN failed
BDN failed
CCBS possible
Invalid alternate service line
LND overflow
MM network failure unspecified
MM no service
MM access class barred
MM RR no resource
MM ME busy
MM unspecified
Dual sim radio conflict
No service due to dual sim radio conflict
MMI not registered
Rejected by user
Rejected due to time out
Disconnected due to SIM-Toolkit call
setup
Pending SIM-Toolkit call setup
SIM reset
MM sapi3 release
MM lower layer failure

166
181
182
183
184
185
186
187
188
189
212
256
257
258
259
260
262
263
264
265
266
267
268
269
271
274
277
278
279
280
283
284
285
287
288
289
290
291
292
296
297
301
303
304
306
307
310
340
341

UBX-13002752 - R67

LEON-G1

SARA-G3 LISA-U2

SARA-U2 TOBY-L2 / LARA-R2 /MPCI-L2 TOBY-R2
x
x
x
x
x

x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x
x
x
x
x
x
x

x
x
x
x
x
x
x

x
x
x
x

x
x
x
x

x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x
x
x
x

x
x
x
x

x
x
x
x

A Appendix: Error result codesxxx

Page 858 of 1001

u-blox cellular modules - AT commands manual<cause><error_description>

342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390

MM authentication failure
MM PS reject
MM service rejected
MM abort by network
MM timeout
MM detach
MM RR connection releaseMM not registered
MM re-establishment failure
Failure due to handover
Link establishment failure
Random access failureRadio link aborted
Lower layer failure in Layer 1
Immediate Assignment Reject
Failure due to paging
Abnormal release unspecified
Abnormal release channel unacceptable
Abnormal release timer expired
Abnormal release no act on radio path
Preemptive release
UTRAN configuration unknown
Handover impossible
Channel mode unacceptable
Frequency not implemented
Originator leaving call group area
Lower layer failure from network
Call already cleared
Semantically incorrect message
Invalid mandatory info
Message type non existing
Message type incompatible in state
Conditional information element error
No cell allocation available
Protocol error unspecified
Normal event
Unspecified
Preemptive release
Congestion
RE establishment rejectDirected sig conn establishment
User inactivity
Lower layer failure downlink
Lower layer failure uplink
Cell barred due to authentication failure
signalling connection release
CS connection release triggered by MM
RRC connection establishment failure
RRC connection establishment rejectwith redirection
resource conflict
Layer 2 sequence error
Layer 2 T200 exp N200 plus 1 times
Layer 2 unsolicited DM resp MFES

391
392
393
394

UBX-13002752 - R67

LEON-G1

SARA-G3 LISA-U2
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

SARA-U2 TOBY-L2 / LARA-R2 /MPCI-L2 TOBY-R2
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

x
x
x
x

x
x
x
x

A Appendix: Error result codes

x
x
x
x

Page 859 of 1001

u-blox cellular modules - AT commands manual<cause><error_description>

395
396
397

Layer 2 contention resolution
Layer 2 normal cause
RR connection release due to BAND
change (2G)
MM RR connection error while release
Local user disconnect/normal call
clearing
Remote user or NW disconnect\normal
call clearing,during any other call statethan "CALL PROCEEDING"
Remote user or NW disconnect\normal
call clearing,during the call state "CALL
PROCEEDING"
Request rejected, BCM violation

400
500
510

511

512

LEON-G1

SARA-G3 LISA-U2
xxx

SARA-U2 TOBY-L2 / LARA-R2 /MPCI-L2 TOBY-R2
x
x
x
x
x
x

x
x

x
x

x
x

x

x

x

x

x

x

x

TOBY-L200-03A / TOBY-L200-03S / TOBY-L201-02S / TOBY-L210-03A / TOBY-L210-03S /TOBY-L280-03A / TOBY-L280-03S / MPCI-L201-02S
The following table lists the supported values for <cause> (number) and <error_description> (string) for+CEER AT command if <type> assumes one of these values:• EMM cause
This is not valid for TOBY-L201-02S-00, TOBY-L200-03S-00, TOBY-L210-03S-00, TOBY-L210-03A-00,
TOBY-L280-03S-00, MPCI-L201-02S-00.
<cause>
0
2
3
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
35
39
40
42
95
96
97

<error_description>
No cause information available
IMSI unknown in HSS
Illegal UE
IMEI not accepted
Illegal ME
EPS services not allowed
EPS services and non-EPS services not allowed
UE identity cannot be derived by the network
Implicitly detached
PLMN not allowed
Tracking area not allowed
Roaming not allowed in this tracking area
EPS services not allowed in this PLMN
No suitable cells in tracking area
MSC temporarily not reachable
Network failure
CS domain not available
ESM failure
MAC (Message Authentication Code) failure
Synch failure
Congestion
UE security capabilities mismatch
Security mode rejected, unspecified
Not authorized for this CSG
Non-EPS authentication unacceptable
Requested service option not authorized in this PLMN
CS service temporarily not available
No EPS bearer context activated
Severe network failure
Semantically incorrect message
Invalid mandatory information
Message type non-existent or not implemented

UBX-13002752 - R67

A Appendix: Error result codes

TOBY-L2 / MPCI-L2
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 860 of 1001

u-blox cellular modules - AT commands manual<cause>
98
99
100
101
111

<error_description>
Message type not compatible with protocol state
Information element non-existent or not implemented
Conditional IE error
Message not compatible with protocol state
Protocol error, unspecified

TOBY-L2 / MPCI-L2
x
x
x
x
x

A.3.2 TOBY-L4 series
The following table lists the supported values for <cause> (number) and <error_description> (string) for +CEER
AT command if <type> assumes one of these values:• "CC setup error"• "CC modification error"• "CC release"• "SM activation error"• "SM deactivation<cause>
0
1
3
6
8
16
17
18
19
21
22
26
27
28
29
30
31
34
38
41
42
43
44
47
49
50
55
57
58
63
65
68
69
70
79
81
87
88
91

<error_description>
No cause information available
Unassigned (unallocated) number
No route to destination
Channel unacceptable
Operator determined barring
Normal call clearing
User busy
No user responding
User alerting, no answer
Call rejected
Number changed
Non selected user clearing
Destination out of order
Invalid number format (incomplete number)
Facility rejected
Response to STATUS ENQUIRYNormal, unspecified
No circuit/channel available
Network out of order
Temporary failure
Switching equipment congestion
Access information discarded
Requested circuit/channel not available
Resources unavailable, unspecified
Quality of service unavailable
Requested facility not subscribed
Incoming calls barred within the CUG
Bearer capability not authorized
Bearer capability not presently available
Service or option not available, unspecified
Bearer service not implemented
ACM equal to or greater than ACMmax
Requested facility not implemented
Only restr. digital information bearer capability
Service or option not implemented, unspecified
Invalid transaction identifier value
User not member of CUG
Incompatible destination
Invalid transit network selection

UBX-13002752 - R67

A Appendix: Error result codes

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 861 of 1001

u-blox cellular modules - AT commands manual<cause>
95
96
97
98
99
100
101
102
103
106
107
111
112
113
124
125
126
127
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
148
149
166
212
256
257
258
259
260
262
263
264
265
266
267
268
269

<error_description>
Semantically incorrect message
Invalid mandatory information
Message type non-existent or not implemented
Message type not compatible with protocol state
Information element non-existent or not implemented
Conditional IE error
Message not compatible with protocol state
Recovery on timer expiry
Illegal MS
Illegal ME
GPRS service not allowed
Protocol error, unspecified
Location area not allowed
Roaming not allowed in this location area
MBMS bearer capabilities insufficient for the service
LLC or SNDCP failure
Insufficient resources
Interworking, unspecified
Missing or unknown APN
Unknown PDP address or PDP type
User authentication failed
Activation rejected by GGSN
Activation reject,unspecified
Service not supported
Requested service option not subscribed
Service option temporarily out of order
NSAPI already used
Regular PDP context deactivation
QoS not accepted
Network failure
Reactivation requested
Feature not supported
Semantic error in the TFT operation
Syntactical error in the TFT operation
Unknown PDP context
Semantic errors in packet filter(s)Syntactical errors in packet filter(s)PDP context without TFT already activatedUnspecified GPRS error
PDP authentication error
Requested APN not supported in current RAT and PLMN combination
APN resriction
Internal, unspecified
Out of memory
Invalid parameters
Data call active
Speech call active
Missing ACM information
Temporary forbidden
Called party is blacklisted
Blacklist is fullNo service
Limited service
Client conflict
Dual service call active

UBX-13002752 - R67

A Appendix: Error result codes

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 862 of 1001

u-blox cellular modules - AT commands manual<cause>
271
274
277
278
279
280
283
284
285
287
288
289
290
291
292
296
297
301
303
304
306
307
310
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371

<error_description>
Unknown SIM error
Active Client is Gone
SIM status failure
Rejected by call control
FDN failed
BDN failed
CCBS possible
Invalid alternate service line
LND overflow
MM network failure unspecified
MM no service
MM access class barred
MM RR no resource
MM ME busy
MM unspecified
dual sim radio conflictno service due to dual sim radio conflict
MMI not registered
Rejected by user
Rejected due to time out
Disconnected due to SIM-Toolkit call setup
Pending SIM-Toolkit call setup
SIM reset
MM sapi3 release
MM lower layer failure
MM authentification failure
MM PS reject
MM service rejected
MM abort by network
MM timeout
MM detach
MM RR connection releaseMM not registered
MM reestablishment failure
Failure due to handover
Link establishment failure
Random access failureRadio link aborted
Lower layer failure in Layer 1
Immediate Assignment Reject
Failure due to paging
Abnormal release unspecified
Abnormal release channel unacceptable
Abnormal release timer expired
Abnormal release no act on radio path
Preemptive release
UTRAN configuration unknown
Handover impossible
Channel mode unacceptable
Frequency not implemented
Originator leaving call group area
Lower layer failure from network
Call already cleared
Semantically incorrect message
Invalid mandatory info

UBX-13002752 - R67

A Appendix: Error result codes

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 863 of 1001

u-blox cellular modules - AT commands manual<cause>
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
400
500
510
511
512
513

<error_description>
Message type non existing
Message type incompatible in state
Conditional information element error
No cell allocation available
Protocol error unspecified
Normal event
Unspecified
Preemptive release
Congestion
RE establishment rejectDirected sig conn establishment
User inactivity
Lower layer failure downlink
Lower layer failure uplink
Cell barred due to authentication failure
signalling connection release
CS connection release triggered by MM
RRC connection establishment failure
RRC connection establishment reject with redirection
resource conflict
Layer 2 sequence error
Layer 2 T200 exp N200 plus 1 times
Layer 2 unsolicited DM resp MFES
Layer 2 contention resolution
Layer 2 normal cause
RR connection release due to BAND change (2G)
MM RR connection error while releaselocal user disconnect/normal call clearing
Remote user or NW disconnect/normal call clearing,during any other call state than
"CALL PROCEEDING\
Remote user or NW disconnect/normal call clearing,during the call state "CALL
PROCEEDING"
Request rejected, BCM violation
No response timeout

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

The following table lists the supported values for <cause> (number) and <error_description> (string) for +CEER
AT command if <type> assumes one of these values:• "SM attach error"• "SM detach"<cause>
0
2
3
4
5
6
7
8
9
10
11
12
13
15
16

<error_description>
No cause information available
SIM not provisioned
SIM not allowed
Call Failed
Call Failed
Phone not allowed
GPRS Service not allowed
GPRS Service and Non GPRS service not allowed
MS Identity cannot be Derived by network
Implicitly Detached
SOS/Emergency calls only,PLMN not allowed
SOS/Emergency calls only,LA not allowed
SOS/Emergency calls only,roaming not allowed in LA
No Suitable cells in Location Area
MSC Temporarily Not Reachable

UBX-13002752 - R67

A Appendix: Error result codes

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 864 of 1001

u-blox cellular modules - AT commands manual<cause>
20
21
22
23
32
33
34
38
40
48
63
95
96
97
98
99
100
101
111

<error_description>
MAC (Message Authentication Code) FAILURESYNCH FAILURE
Error Congestion
SIM not allowed
Service Option Not supported
Requested Service option not subscribed
Service temporarily out of orderCall cannot be Identifed
NO PDP Context Active
Retry on New Cell beginning
Retry on New Cell End
Semantically Incorrect message
Invalid mandatory information
Message type non existent or Not implemented
Message type not compatible with protocols state
Information element non existent or Not implemented
Conditional IE Error
Message Not Compatible with Protocol state
Protocol error unSpecified

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

The following table lists the supported values for <cause> (number) and <error_description> (string) for +CEER
AT command if <type> assumes one of these values:• EMM cause<cause>
0
2
3
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
35
39
40
42
95
96

<error_description>
No cause information available
IMSI unknown in HSS
Illegal UE
IMEI not accepted
Illegal ME
EPS services not allowed
EPS services and non-EPS services not allowed
UE identity cannot be derived by the network
Implicitly detached
PLMN not allowed
Tracking area not allowed
Roaming not allowed in this tracking area
EPS services not allowed in this PLMN
No suitable cells in tracking area
MSC temporarily not reachable
Network failure
CS domain not available
ESM failure
MAC (Message Authentication Code) failure
Synch failure
Congestion
UE security capabilities mismatch
Security mode rejected, unspecified
Not authorized for this CSG
Non-EPS authentication unacceptable
Requested service option not authorized in this PLMN
CS service temporarily not available
No EPS bearer context activated
Severe network failure
Semantically incorrect message
Invalid mandatory information

UBX-13002752 - R67

A Appendix: Error result codes

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 865 of 1001

u-blox cellular modules - AT commands manual<cause>
97
98
99
100
101
111

<error_description>
Message type non-existent or not implemented
Message type not compatible with protocol state
Information element non-existent or not implemented
Conditional IE error
Message not compatible with protocol state
Protocol error, unspecified

TOBY-L4
x
x
x
x
x
x

The following table lists the supported values for <cause> (number) and <error_description> (string) for +CEER
AT command if <type> assumes one of these values:• ESM attach error• ESM detach<cause>
0
8
26
27
28
29
30
31
32
33
34
35
36
37
38
39
41
42
43
44
45
47
49
50
51
52
53
54
55
56
59
60
65
66
55
56
81
95
96
97
98
99
100

<error_description>
No cause information available
Operator Determined Barring
Insufficient resources
Missing or unknown APN
Unknown PDN type
User authentication failed
Request rejected by Serving GW or PDN GW
Request rejected, unspecified
Service option not supported
Requested service option not subscribed
Service option temporarily out of order
PTI already in use
Regular deactivation
EPS QoS not accepted
Network failure
Reactivation requested
Semantic error in the TFT operation
Syntactical error in the TFT operation
Invalid EPS bearer identity
Semantic errors in packet filter(s)Syntactical error in packet filter(s)PTI mismatch
Last PDN disconnection not allowed
PDN type IPv4 only allowed
PDN type IPv6 only allowed
single address bearers only allowed"
ESM information not received
PDN connection does not exist
Multiple PDN connections for a given APN not allowed
Collision with network initiated request
Unsupported QCI value
Bearer handling not supported
Maximum number of EPS bearers reached
Requested APN not supported in current RAT and PLMN combination
Multiple PDN connections for a given APN not allowed
Collision with network initiated request
Invalid PTI value
Semantically incorrect message
Invalid mandatory information
Message type non-existent or not implemented
Message type not compatible with protocol state
Information element non-existent or not implemented
Conditional IE error

UBX-13002752 - R67

A Appendix: Error result codes

TOBY-L4
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

Page 866 of 1001

u-blox cellular modules - AT commands manual<cause>
101
111
112

<error_description>
Message not compatible with protocol state
Protocol error, unspecified
APN restriction value incompatible with active EPS bearer context

TOBY-L4xxx

A.4 Firmware install final result codes
The +UFWINSTALL command issues a final result code providing the result of the FW install procedure. In case
the FW install procedure fails, the error result code provides some indication about the error cause (syntax
error or issue during the installation procedure).

A.4.1 TOBY-L2 / MPCI-L2 error result codes
This table lists the allowed error result codes applicable to TOBY-L2 / MPCI-L2 series modules:
Error result code
md5 not matching, update failed

Description
The md5 calculated from the stored file is not matching with the one
provided in the command. The module exits Firmware Install Mode andstarts the actual FW
md5 provided in the command has been detected shorter. The install
is not started. The module exits Firmware Install Mode and starts theactual FW
md5 provided in the command has been detected longer. The install
is not started. The module exits Firmware Install Mode and starts theactual FW
md5 in missing from the issued AT command. The install is not started.
The module exits Firmware Install Mode and starts the actual FW

ERROR3
short md5, update failed
ERROR1long md5, update failed
ERROR1
missing md5, update failed
ERROR1
md5 with no hex digits, update failed

md5 provided in the command has been detected with at least one nothex digits. Install is not started. The module exits Firmware Install Modeand starts the actual FW
Update file is not found in the specific folder. The install is not started.
The module exits Firmware Install Mode and starts the actual FW

ERROR1
update file not found
ERROR1

A.4.2 TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 final result codes
Syntax error resulting from the +UFWINSTALL command:
Numeric
code
4

1624

error Verbose description

Description+CME ERROR: not supported+CME ERROR: FFS file not
found

One of the following cases:• Wrong serial port number• Wrong baud rate
• Number of parameters not allowed• File name too long
The delta file is not stored in the module FS or the file name is wrong

A.4.2.1 TOBY-L4 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200-04B / LISA-U201-04B final result codes
Here below are listed the allowed final result codes that can be issued at the finalization of the install procedureby means of the +UFWINSTALL command:• 128: FW update successfully performed• In case a different error result code is provided please contact u-blox Technical Support offices for support
A.4.2.2 LISA-U200-83S / LISA-U201-83S final result codes
Here below are listed the allowed final result code that can be issued at the finalization of the install procedureby means of the +UFWINSTALL command:
Numeric error code
128
129
130

Description
General success Code
General failure CodeError in a run parameter

UBX-13002752 - R67

A Appendix: Error result codes

Page 867 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181

UBX-13002752 - R67

Description
Expected length error
Structural error
Signature error
Given RAM is not enough
Does not behave as RAM
Memory allocation failure
Flash writing failure
Flash erasing failure
Flash reading failure
One API function is not declared
Backup buffer(s) not sector aligned
Start address is not sector aligned
File does not exist
RO or no access rights
File does not exist
No access rights
Cannot resize fileCannot read specified size
Cannot close file handle
Failed creating symbolic link
Failed creating directory
Bad operation number for update
Unsupported compression
Can not apply reverse update for delta not generated as reverse delta
Number of backup buffers given to UPI does not match number in delta
file
Sector size mismatch between UPI and delta
UPI was not compiled to support reverse update
UPI was not compiled to support IFS on compressed images
UPI was not compiled to support IFS
Source mismatch in scout only operation
There is not enough RAM to run with operation=2 (Dry update)
Delta file too long - corrupted
Mismatch between deletes sig and delta deletes buffers signature
Number of fragments in section is not 1
Over all number of backup sects too big
Delta file is corrupt: signature mismatch between delta header
signature and calculated signature
File signature does not match signature
Signature for the target buffer does not match the one stored in thedelta file
Too many dirty buffers
UPI version mismatch between UPI and delta
Scout version mismatch between UPI and delta
Partition name is different in delta and in UPI data
There is not enough flash to update or install the files
There is not enough backup space on device
UPI does not support RW file system update
UPI does not support image update
Deployment Package header is invalid
Deployment Package signature is invalid
Deployment Package version is not supported
Requested ordinal does not exist in Deployment Package
Requested component was not found in Deployment Package

A Appendix: Error result codes

Page 868 of 1001

u-blox cellular modules - AT commands manual

A.5 Firmware install with signature verification final result
codes
The +UFWSINSTALL command issues a final result code providing the result of the FW installation procedure(with signature verification). In case the FW installation procedure fails, the error result code provides someindication about the error cause (syntax error or issue during the FW installation procedure).

A.5.1 TOBY-L2 / MPCI-L2 error result codes
This table lists the allowed error result codes applicable to TOBY-L2 / MPCI-L2 series modules:
Error result code
invalid parameter <usecmng_iname>, update
failedERROR1
invalid parameter <base64_signature>, update
failedERROR2
update file not foundDescription
The parameter <usecmng_iname> parameter is invalid. The FW
installation procedure fails and the module returns to AT commandmode.
The parameter <base64_signature> parameter is invalid. The FW
installation procedure fails and the module returns to AT commandmode.
Update file is not found in the specific folder. The FW installation
procedure fails and the module returns to AT command mode.

ERROR3signature verification error, update failed

The FW update file signature verification failed. The FW installation
procedure fails and the module returns to AT command mode.

ERROR4A.5.2 TOBY-L2 / MPCI-L2 final result codes
Syntax error resulting from the +UFWSINSTALL command:
Numericcode4

error Verbose description

Description+CME ERROR: not supported

One of the following cases:• Parameter <usecmng_iname> missing or too long
• Parameter <base64_signature> missing or too long
• Number of parameters not allowed

A.6 FOAT error result codes
See +UFWUPD command description.

A.6.1 TOBY-L2 / MPCI-L2 error result codes
This table lists the allowed error result codes applicable to TOBY-L2 / MPCI-L2 series:
Error result code
too many errors; giving up
ERROR1bad block ones compl
unexpected block no, #num, expecting #num1
crc error, expected num, got num1
checksum error, expected num, got num1
md5 not matching, update failed
ERROR3
short md5, update failed
ERROR1long md5, update failed
ERROR1UBX-13002752 - R67

Description
General error. The operation has been interrupted before starting towrite in flash, the actual FW is unchanged; the module exits Firmware
Update Mode and starts the actual FW
Block number error
Unexpected block number
crc error
checksum error
Download has been done correctly but the md5 calculated fromthe downloaded file is not matching with the one provided in thecommand.The module exits Firmware Update Mode and starts theactual FW
md5 provided in the command has been detected shorter. The download
is not started. The module exits Firmware Update Mode and starts theactual FW
md5 provided in the command has been detected longer. The download
is not started. The module exits Firmware Update Mode and starts theactual FW

A Appendix: Error result codes

Page 869 of 1001

u-blox cellular modules - AT commands manual

Error result code
md5 with no hex digits, update failed
ERROR1
missing md5, update failed
ERROR1

Description
md5 provided in the command has been detected with at least one nothex digits.Download is not started. The module exits Firmware Update
Mode and starts the actual FW
md5 in missing from provided AT command. The update is not started.
The module exits Firmware Update Mode and starts the actual FW

A.6.2 LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1 error result codes
Error result code
ERROR1ERROR2ERROR3
ERROR4
ERROR5ERROR6
FLS header decoding failed
Buffer Data Overrun
Timeout

Description
The operation has been interrupted and the actual FW is unchanged;
the module drops out from Firmware Update Mode
The operation has been interrupted during FW updating; the actual
firmware is corrupted and the module remains in Firmware Update
Mode
The signature check fails
The module has received unexpected EOT because not all excepted
bytes have been received
The boot does not support the selected baudrate
Invalid AT command sent during bootAn error occurs during decoding of file header
The buffers are not filled at least with a 1029 packet: data comes too
slowlyThe command must be re-sent: no data is coming

A.7 Dynamic DNS unsolicited indication codes
The following table lists the available values of <error_code> parameter of the last Dynamic DNS update
provided through +UUDYNDNS URC (for more details see the +UDYNDNS AT command description).
Numeric error code
0
1
2
3
4
5
6
7
8
9
10
40
41
42
43
44
45
46
47
48
49
50
51
52
53

UBX-13002752 - R67

Description
Success
Data connection lost while performing update
Cannot update dynamic DNS because a private IP address has been
assigned to the module
Connection to dynamic DNS server failed
Error occurred sending data to dynamic DNS server
Error occurred reading response from dynamic DNS server
Timeout while waiting response from dynamic DNS server
Dynamic DNS server closed connection unexpectedly
Unexpected response from dynamic DNS server
Dynamic DNS response seems to be incomplete
Update has been delayed in order to respect DNS update protocol timing
specification
Dynamic DNS protocol specific: good (TZO code 200)
Dynamic DNS protocol specific: nochg (TZO code 304)
Dynamic DNS protocol specific: notfqdn
Dynamic DNS protocol specific: nohost
Dynamic DNS protocol specific: numhost
Dynamic DNS protocol specific: badauth (TZO code 401)
Dynamic DNS protocol specific: badagent (TZO code 405)
Dynamic DNS protocol specific: !donator
Dynamic DNS protocol specific: abuse
Dynamic DNS protocol specific: dnserr
Dynamic DNS protocol specific: 911
Dynamic DNS protocol specific: badsys
Dynamic DNS protocol specific: !yours
Dynamic DNS protocol specific: TZO code 403

A Appendix: Error result codes

Page 870 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
54
55
56
57
100-108

Description
Dynamic DNS protocol specific: TZO code 407
Dynamic DNS protocol specific: TZO code 414
Dynamic DNS protocol specific: TZO code 415
Dynamic DNS protocol specific: TZO code 480
Internal errors

The meaning of dynamic DNS protocol specific codes depends on the provider used; see the provider
documentation.
Errors 45, 46, 53, 54 and 56 trigger a client self deactivation when the provider is TZO.com.
Errors 42, 43, 44, 46, 48, 51 and 52 trigger a client self deactivation when the selected provider is
DynDNS.org or DynDNS.it or No-IP.org or DynamicDNS.org.

A.8 Internal TCP/UDP/IP stack class error codes
The following table lists all allowed error classes that can be provided by the internal TCP/UDP/IP stack through+USOER and +USOCTL (with <param_id>=1) AT commands.
Numeric
error code0

Description

Resulting from the following commands

No error

1

EPERM - Operation not permitted (internal error)

2

ENOENT - No such resource (internal error)

4

EINTR - Interrupted system call (internal error)

5

EIO - I/O error (internal error)

9

EBADF - Bad file descriptor (internal error)

10

ECHILD - No child processes (internal error)

11
12

EWOULDBLOCK / EAGAIN - Current operation would block, try
again
ENOMEM - Out of memory (internal error)+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCO, +USOWR

14EFAULT - Bad address (internal error)

22

EINVAL - Invalid argument

32

EPIPE - Broken pipe (internal error)

38
64

ENOSYS - Function not implemented
ENONET - Machine is not on the internet

65
71

EEOF - End of file
EPROTO - Protocol error

UBX-13002752 - R67

A Appendix: Error result codes+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLI+USOSO, +USOGO+USOCR, +USOWR, +USOST, +USORD,+USORF, +USOLI+USOWR, +USOST, +USORD, +USORF+USOWR, +USOST, +USORD, +USORF

Page 871 of 1001

u-blox cellular modules - AT commands manual

Numeric
error code
77

78
89
91
92
93
94
95
96
97
98
99
100
101
102
103

104

105

106
107

108

110
111
112
113
115

160
161
162
163
164
165
166
167
168
169
170

Description

Resulting from the following commands

EBADFD - File descriptor in bad state (internal error)+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLIEREMCHG - Remote address changed+USOWR, +USOST, +USORD, +USORF,+USOCLEDESTADDRREQ - Destination address required+USOCO, +USOSTEPROTOTYPE - Wrong protocol type for socket+USOCRENOPROTOOPT - Protocol not available+USOCREPROTONOSUPPORT - Protocol not supported+USOCR
ESOCKTNNOSUPPORT - Socket type not supported+USOCR
EOPNOTSUPP - Operation not supported on transport endpoint +USOWR, +USOST, +USORD, +USORF,+USOCLEPFNOSUPPORT - Protocol family not supported+USOCR
EAFNOSUPPORT - Address family not supported by protocol+USOCREADDRINUSE - Address already in use+USOLIEADDRNOTAVAIL - Cannot assign requested address+USOCR, +USOLI, +USOCOENETDOWN - Network is down
+USOCR, +USOLI, +USOCO, +USOWR,+USOST, +USORD, +USORF, +USOCLENETUNREACH - Network is unreachable+USOCO, +USOST, +USORFENETRESET - Network dropped connection because of reset+USOCR, +USOLI, +USOCO, +USOWR,+USOST, +USORD, +USORF, +USOCLECONNABORTED - Software caused connection abort+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLIECONNRESET - Connection reset by peer
+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLIENOBUFS - No buffer space available+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLIEISCONN - Transport endpoint is already connected+USOCO
ENOTCONN - Transport endpoint is not connected+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLIESHUTDOWN - Cannot send after transport endpoint+USOCR, +USOSO, +USOGO, +USOCO,
shutdown+USOWR, +USOST, +USORD, +USORF,+USOLIETIMEDOUT - Connection timed out+USOCO, +USOST, +USORD, +USORFECONNREFUSED - Connection refused+USOCOEHOSTDOWN - Host is down
+USOCL, +USOCO, +USOWR, +USOST,+USORD, +USORFEHOSTUNREACH - No route to host
+USOCO, +USOWR, +USOST, +USORD,+USORF
EINPROGRESS - Operation now in progress+USOCR, +USOSO, +USOGO, +USOCO,+USOWR, +USOST, +USORD, +USORF,+USOLIENSRNODATA - DNS server returned answer with no data
+UDNSRNENSRFORMERR - DNS server claims query was misformatted +UDNSRNENSRSERVFAIL - DNS server returned general failure+UDNSRNENSRNOTFOUND - Domain name not found+UDNSRNENSRNOTIMP - DNS server does not implement requested+UDNSRN
operation
ENSRREFUSED - DNS server refused query+UDNSRNENSRBADQUERY - Misformatted DNS query+UDNSRNENSRBADNAME - Misformatted domain name+UDNSRNENSRBADFAMILY - Unsupported address family+UDNSRNENSRBADRESP - Misformatted DNS reply+UDNSRNENSRCONNREFUSED - Could not contact DNS servers+UDNSRNUBX-13002752 - R67

A Appendix: Error result codes

Page 872 of 1001

u-blox cellular modules - AT commands manual

Numeric
error code
171
172
173
174
175
176
177

Description

Resulting from the following commands

ENSRTIMEOUT - Timeout while contacting DNS servers
ENSROF - End of fileENSRFILE - Error reading file
ENSRNOMEM - Out of memory
ENSRDESTRUCTION - Application terminated lookup
ENSRQUERYDOMAINTOOLONG - Domain name is too long
ENSRCNAMELOOP - Domain name is too long

+UDNSRN+UDNSRN+UDNSRN+UDNSRN+UDNSRN+UDNSRN+UDNSRN

A.9 Internet suite error classes
The following table lists all allowed error classes that can be provided by the <error_class> parameter for these
AT error commands:• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 - +UFTPER, +UHTTPER
that provide the error of the last FTP, HTTP operation.
• SARA-G3 / LEON-G1 - +UFTPER, +UHTTPER, +USMTPER that provide the error of the last FTP, HTTP, SMTP
operation.
<error_class> Description
0
1
2
3
4
5
6
7
8
9
10
11
12

<error_codes>

Resultingfromfollowing commands
OK, no error occurred
All
FTP Protocol error classSee the Appendix A.9.1+UFTPC, +UFTP
SMTP Protocol error classSee the Appendix A.9.3+USMTP, +USMTPM,+USMTPC
HTTP Protocol error classSee the Appendix A.9.2+UHTTP, +UHTTPC
Flash File System error classSee the Appendix A.9.4+UFTPC, +UFTPER,+UHTTPCDNS error class+UFTPC, +UHTTPC,+USMTPC
Socket error class
BSD error codes standard All
Dynamic Memory error
0All
Wrong FTP API usage (e.g. missing/null parameters) See the Appendix A.9.1+UFTPC, +UFTP
Wrong SMTP API usage (e.g. missing/null
See the Appendix A.9.3+USMTP, +USMTPM,
parameters)+USMTPC
Wrong HTTP API usage (e.g. missing/null
See the Appendix A.9.2+UHTTP, +UHTTPC
parameters)
Syntax error in high layer Protocol (wrong/missing/+UFTPC, +UHTTPC,
corrupted data)+USMTPC
Unspecified error
0
All

the

A.9.1 FTP class error codes
The following table lists the available values of <error_code> parameter of the last FTP operation provided
through +UFTPER AT command if <error_class>=1 or 8 (for more details see the AT+UFTP, AT+UFTPC
commands description).
Numeric error code
0
1
2
3
4
5
6
7
8
9
10
11

Description
No error
User missing
Password missing
Account missing
Server missing
Directory name missing
File name missing
Null parameter
Unknown FTP command
Unknown file action
Wrong FTP state
Wrong parameter

UBX-13002752 - R67

A Appendix: Error result codes

Page 873 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26-30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70

UBX-13002752 - R67

Description
PSD or CSD connection not establishedNo memory available for allocation
Reserved internal code
Length of given web server (address or hostname) too long or too short
Hostname of given web server invalid
Address of given web server is invalid
Username too long or too shortPassword too long or too short
Account too long or too shortOperation not allowed because FTP client is busy
Not possible to connect to FTP server
Error occurred in FTP request
Reserved internal code
FFS filename pointer is null or its length is 0
Reserved internal code
Timeout elapsed while performing requested operation
Internal processing error
Not logged in
Login incorrect
File unavailable (not found or no access)File not readyFilename not allowed
Folder not foundFolder no access
Operation aborted by user
Permission denied
Cannot open FTP data channel
Socket invalid parameter
Invalid socket
No socket available
Cannot create socket
Cannot bind socket to network interface
Cannot resolve hostname
Cannot connect socket
Cannot get socket name
Cannot bind socket to port
Socket cannot listen
Socket cannot accept
Socket would block
Socket cannot write
Socket cannot read
Reserved internal code
No socket data to send
Socket cannot get available data
No socket data to read
Socket no response code found
Socket not connected
Cannot set secure socket
Socket cannot decode password
Socket cannot get size
FFS Invalid parameter
FFS invalid handle
FFS cannot open file
FFS cannot seek file
FFS cannot get file size

A Appendix: Error result codes

Page 874 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
71
72
73
74
75
76
77
78
79
226

Description
FFS cannot readFFS bad offset
FFS cannot write
Direct link internal error
Failed to open extended passive mode
Failed to parse extended passive mode server reply
Internal error
Client IP protocol not supported - try passive mode
Data transfer error. The transferred (received/sent) data is not complete
Closing data connection; requested file action successful (for example,
file transfer or file abort)
Requested file action okay, completed
Requested file action pending further information
Service not available, closing control connection.

250
350
421

User limit reached
Not authorized to make the connection
Maximum connections reached
Maximum connections exceeded
Cannot open data connection
Connection closed; transfer aborted. The command opens a data
connection to perform an action, but that action is cancelled, and thedata connection is closed
Requested file action not taken. File unavailable (e.g. file busy)
Requested action aborted: local error in processing
Requested action not taken. Insufficient storage space in system
Syntax error, command unrecognized, command line too long
Syntax error in parameters or arguments
Command not implemented
Bad sequence of commands
Command not implemented for that parameter
User not logged in
Need account for storing files
Requested action not taken. File unavailable, not found, not accessible
Requested file action aborted. Exceeded storage allocation
Requested action not taken. Filename not allowed

425
426

450
451
452
500
501
502
503
504
530
532
550
552
553

For all the errors not listed in the table see the RFC 959 [61] and RFC 2428 [62].

A.9.2 HTTP class error codes
The following table lists the available values of <error_code> parameter of the last HTTP operation provided
through +UHTTPER AT command if <error_class>=3 or 10 (for more details see the AT+UHTTP and AT+UHTTPC commands description).
Numeric error code
0
1
2
3
4
5
6
7
8
9
10

UBX-13002752 - R67

Description
No errorInvalid profile ID
Invalid input
Server hostname too long
Invalid server hostname
Invalid server IP address
Invalid authorization method
Server missing
Username length exceeded
Password length exceededInternal error

A Appendix: Error result codes

Page 875 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46 - 72
73

Description
Server connection error
Error occurred in HTTP request
Internal error
Internal error
Invalid POST data size
Empty FFS file name
Invalid FFS file length
Invalid content-type specified
Internal error
Internal error
Internal error
PSD or CSD connection not establishedServer or proxy hostname lookup failed
User authentication failed on server
User authentication failed on proxy
Connection timed out
Request prepare timeout expired
Response receive timeout expired
Request send timeout expired
HTTP operation in progress
Invalid HTTP parameter TCP port not in range (1-65535)
Invalid HTTP parameter secure
Invalid HTTP parameter authentication username
Invalid HTTP parameter authentication password
Invalid HTTP parameter output filename
Invalid HTTP parameter output filename length
Invalid HTTP parameter server path
Invalid HTTP parameter server path length
Invalid HTTP parameter content filename length
Invalid custom content type string
Output file open error
Output file close error
Output file write error
Connection lost
Operation not allowed in current state
Internal error
Secure socket connect error

A.9.3 SMTP class error codes
The following table lists the available values of <error_code> parameter of the last SMTP operation provided
through +USMTPER AT command if <error_class>=2 or 9 (for more details see the AT+USMTP, AT+USMTPM,
AT+USMTPC commands description).
Numeric error code
0
1
2
3
4
5
6
7
8
9
10

UBX-13002752 - R67

Description
No errorServer missing
Sender address missing
Receiver address missing
Maximum number of receivers exceeded
Maximum address length exceededInternal error
Maximum subject length exceeded
Maximum number of attachments exceeded
Wrong SMTP state
Wrong parameter

A Appendix: Error result codes

Page 876 of 1001

u-blox cellular modules - AT commands manual

Numeric error code
1112

Description
Internal error
PSD or CSD connection not establishedA.9.4 File system class error codes
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1
The following table lists the available values of <error_code> parameter of the last FTP, HTTP or SMTP
operation provided through +UFTPER, +UHTTPER and +USMTPER AT commands if the <error_class> is
4 "Flash File System error class".
Numeric error code
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

Description
Operation performed with success
Initialization in progress
File already opened
File not opened
File not foundFile already created
Illegal id
Illegal file handle
Illegal type
Illegal mode
File range error
The operation is not possible
Write error
User id error
Internal fatal error
Memory resource error
Maximum number of files exceeded
Memory not available
Invalid filename
Streaming not enabled
Operation not allowed on static file
Memory table inconsistency
Not a factory default file
Requested memory temporary not available
Operation not allowed for a directory
Space in the directory space not available
Too many streaming files opened
Requested dynamic memory temporary not available
The user provided a NULL parameter instead of a suitable buffer

A.10 IP change notification error result codes
The following table lists the available values of <error_code> parameter of the last IP Change Notification
provided through +UUIPCHGN URC (for more details see the AT+UIPCHGN command description).
Numeric error code
0
10
11
12
13
14
15
16
17
18

UBX-13002752 - R67

Description
The IP CN feature was enabled from a previous working session and isactiveInternal PSD data connection is not active
Invalid IP address assigned to module (e.g. empty string)
IMEI could not be retrieved
IMSI could not be retrieved
Error preparing HTTP GET request for IP CN
Error creating socket for HTTP connection
Error connecting to remote HTTP server
Error sending HTTP GET request to HTTP server
Error receiving or parsing HTTP GET response from HTTP server

A Appendix: Error result codes

Page 877 of 1001

u-blox cellular modules - AT commands manual

A.11 Ping error result codes
The following table lists the available values of <error_code> parameter of the last ping operation provided
through +UUPINGER URC (for more details see the AT+UPING command description).
Numeric error code
0
1-6
7
8
9
10
11
12
13
14
15
16
17
100 - 105
106
107
108
109
110
111-115

Description
Success (no error)
Internal error (ping level)
Empty remote host
Cannot resolve host
Unsupported IP version (RFU)
Invalid IPv4 address
Invalid IPv6 address (RFU)
Remote host too long
Invalid payload size
Invalid TTL value
Invalid timeout value
Invalid retries number
PSD or CSD connection not establishedInternal error (ICMP level)
Error creating socket for ICMP
Error settings socket options for ICMP
Cannot end ICMP packet
Read for ICMP packet failed
Received unexpected ICMP packet
Internal error (socket level)

A.12 Mobile termination error result codes
The command +CMOLRE (see subclause 9.1a of 3GPP TS 27.007 [2]) configures the <err> parameter in numericor verbose format.
Numeric error code
0
1
2
3
4
5
6
7
8
9
10
255

Description
Method not supported
Additional assistance data required
Not enough satellites
UE busy12
Network error
Failed to open internet connection, too many connections13
Failed to open internet connection, too many users13
Failure due to handoverInternet connection failure13
Memory error
Timeout
Unknown error

12

There is already one ongoing positioning session and the UE does not support multiple simultaneous
sessions
13
Only applicable to SUPL-based transactions. Currently SUPL is not supported

UBX-13002752 - R67

A Appendix: Error result codes

Page 878 of 1001

u-blox cellular modules - AT commands manual

B Appendix: AT Commands List

U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

+USAFE+UPLAYFILE

•
•

+URNG

+UPAR

•
•

+URECFILE

+UMSM

•
•

+UMSEL

•
•

+UMGC

•
•

+UMCLK••+UMAFE••+UMAAT••+UDTMFG••+UDTMFD••+UDCONF=33•+UDCONF=31

•

•

•

•

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S

UBX-13002752 - R67•••

U270-01S
U230-01S
U200-02S / U260-02S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+UI2S

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+UHFP

G350-01B
G340-02S / G350-02S+UDCONF=30

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UDBF+UAREC+UAPT+UAPLAY

AT command+UEXTDCONF

Audio interface and tuning

•

•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•

•
•

•
•

•
•
•
•
•
•
•
•
•

•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

Page 879 of 1001

u-blox cellular modules - AT commands manual

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

•
•
•
•
•
•
•
•
•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

+UMSEL

•

+UMGC

•

+UMCLK•+UMAFE•+UMAAT

•

•

+UI2S

•

+UHFP

•

+UDTMFG•+UDTMFD

•

+UDBF

•

+USAFE

•
•

•

+URNG

•

•

+URECFILE•+UPLAYFILE

•

+UPAR

•

+UEXTDCONF•+UAREC

•

+UMSM

•

+UDCONF=31

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UDCONF=30

L280-03S
L201-01S
L201-02S
L210-60S
L210-62S / L210-65S
L200-03A / L210-03A+UAPT+UAPLAY

AT command+UDCONF=33

Audio interface and tuning

•
•
•
•
•
•
•

•
•

•
•

•
•
•

B Appendix: AT Commands List

Page 880 of 1001

u-blox cellular modules - AT commands manualU201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

+UVGC

+UTGN

•
•

+UUBF

+USTOPFILE

•
•

+UTI

+USTN

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+USPM

G350-01B
G340-02S / G350-02S+USGC

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+USAR

AT command+USPEECHINFO

Audio interface and tuning

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•

•

•
•

•

•

•

•

•

•

•

•

•

•

B Appendix: AT Commands List

Page 881 of 1001

u-blox cellular modules - AT commands manual

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

+UVGC
•

+UUBF

•

+UTI

•

+USTN

•

+USPM

+UTGN

L210-62S / L210-65S
L200-03A / L210-03A

+USGC

•

+USAR

+USTOPFILE

AT command+USPEECHINFO

Audio interface and tuning

•
•
•
•
•
•
•

•
•

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 882 of 1001

u-blox cellular modules - AT commands manualU201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

A

D

D>

DL

L

M

P

•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•
•
•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

T

•
•
•
•
•

S0

+VTS

•
•
•
•
•

+UVTS

+VTD

+UPROGRESS

•
•
•
•
•

+UEMN

•
•
•
•
•

+UEMC

•
•
•
•
•

+CSVM

+CSTA

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CSNS

G350-01B
G340-02S / G350-02S+CMOD

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+CHUP

AT command+UCALLSTAT

Call control

•
•

•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•
•

•
•
•
•

B Appendix: AT Commands List

•

•
•
•

Page 883 of 1001

u-blox cellular modules - AT commands manualCall control

UBX-13002752 - R67

+VTD

+VTS

A

D

L

M

P

S0

T

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•

•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•
•
•
•
•
•

•

•
•

•

•

•

•

•

•

•
•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•

•

•
•
•

•

•

•
•
•

•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•
•
•

DL

+UVTS

•

D>

+UPROGRESS

•

+UEMN

•

+UEMC

+UCALLSTAT

•

+CSNS

+CSVM

L280-03S
L220-02S
L220-62S
L280-02S+CSTA

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CMOD

L210-62S / L210-65S
L200-03A / L210-03A+CHUP

AT command

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•

•

•

Page 884 of 1001

u-blox cellular modules - AT commands manualU270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+UCSNDU270-02S
U200-52S
U200-62S
U270-62S / U270-63S+UCSDA

U270-01S
U230-01S
U200-02S / U260-02S+UCSD

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S+FCLASS

U201-03X
U201-63B
U201-04A / U201-04B+CRLP

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CRC

G350-01B
G340-02S / G350-02S+CR

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+CBST

AT command+UDCONF=32

Circuit switched data services

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 885 of 1001

u-blox cellular modules - AT commands manual

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67+UCSND+UCSDA+UCSD+FCLASS

+CRLP

+CRC

+CR

+CBST

AT command+UDCONF=32

Circuit switched data services

•

•

•

•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•
•
•
•
•
•

•

•
•
•
•
•
•

•

•

•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 886 of 1001

u-blox cellular modules - AT commands manual

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S+UECALLVOICE

•

•

•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•

•

•

•

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S••

U270-01S
U230-01S
U200-02S / U260-02S

U270-68S
U200-03S / U201-03S+UECALLTYPE•+UECALLSTAT••+UECALLDATA

G350-01B
G340-02S / G350-02S+UDCONF=90

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+CECALL

AT command+UECALLCFG

eCall

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 887 of 1001

u-blox cellular modules - AT commands manual+UECALLVOICE+UECALLTYPE+UECALLSTAT+UECALLDATA+UECALLCFG+CECALL

AT command+UDCONF=90

eCall

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 888 of 1001

u-blox cellular modules - AT commands manual

FAX class 2

+FBS

+FBU

+FCC

+FCQ

+FCR

+FCS

+FCT

+FDR

+FDT

+FEA

+FFC

+FFD

+FHS

+FIE

+FIP

+FIS

+FIT

+FK

+FLI

+FLO

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+FBO

G350-01B
G340-02S / G350-02S+FAP

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+FAA

AT command

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 889 of 1001

u-blox cellular modules - AT commands manual

FAX class 2

+FLO

+FLI

+FK

+FIT

+FIS

+FIP

+FIE

+FHS

+FFD

+FFC

+FEA

+FDT

+FDR

+FCT

+FCS

+FCR

+FCQ

+FCC

+FBU

+FBS

+FBO

+FAP

+FAA

AT command

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 890 of 1001

u-blox cellular modules - AT commands manual

FAX class 2

+FMR

+FMS

+FND

+FNR

+FNS

+FPA

+FPI

+FPP

+FPS

+FPW

+FRQ

+FRY

+FSA

+FSP

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+FMM

G350-01B
G340-02S / G350-02S+FMI

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+FLP

AT command

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 891 of 1001

u-blox cellular modules - AT commands manual

FAX class 2

+FSP

+FSA

+FRY

+FRQ

+FPW

+FPS

+FPP

+FPI

+FPA

+FNS

+FNR

+FND

+FMS

+FMR

+FMM

+FMI

+FLP

AT command

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 892 of 1001

u-blox cellular modules - AT commands manual

File System

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+URDFILE

U201-03X
U201-63B
U201-04A / U201-04B+URDBLOCK

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+ULSTFILE

G350-01B
G340-02S / G350-02S+UDWNFILE

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UDELFILE

AT command

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

B Appendix: AT Commands List

Page 893 of 1001

u-blox cellular modules - AT commands manual

File System

UBX-13002752 - R67+URDBLOCK+URDFILE

L280-03S
L220-02S
L220-62S
L280-02S+ULSTFILE

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UDWNFILE

L210-62S / L210-65S
L200-03A / L210-03A+UDELFILE

AT command

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 894 of 1001

u-blox cellular modules - AT commands manual

General commands

UBX-13002752 - R67

+GMI

+GMM

+GMR

+GSN

A/

I

L280-03S
L201-01S
L201-02S
L210-60S+GCAP

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+CSCS

U270-68S
U200-03S / U201-03S+CLAC

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S+CIMI

U270-01S
U230-01S
U200-02S / U260-02S+CGSN

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S+CGMR

U201-03X
U201-63B
U201-04A / U201-04B+CGMM

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CGMI

G350-01B
G340-02S / G350-02S+CCID

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S&H

AT command

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 895 of 1001

u-blox cellular modules - AT commands manual

General commands

UBX-13002752 - R67

+CGMM

+CGMR

+CGSN

+CIMI

+CLAC

+CSCS

+GCAP

+GMI

+GMM

+GMR

+GSN

A/

I

L280-03S
L220-02S
L220-62S
L280-02S+CGMI

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CCID

L210-62S / L210-65S
L200-03A / L210-03A&H

AT command

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 896 of 1001

u-blox cellular modules - AT commands manual

GPIO interface

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+UGPIOW

G350-01B
G340-02S / G350-02S+UGPIORLEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UGPIOC

AT command

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•

•

•

•

•

•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

B Appendix: AT Commands List

Page 897 of 1001

u-blox cellular modules - AT commands manual

GPIO interface+UGPIOW

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UGPIOR

L210-62S / L210-65S
L200-03A / L210-03A+UGPIOC

AT command

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 898 of 1001

u-blox cellular modules - AT commands manual

I2C interface+UI2CC+UI2CO+UI2CR+UI2CREGR+UI2CW

AT command

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 899 of 1001

u-blox cellular modules - AT commands manual

I2C interface+UI2CR+UI2CREGR+UI2CW

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UI2CO

L210-62S / L210-65S
L200-03A / L210-03A+UI2CC

AT command

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 900 of 1001

u-blox cellular modules - AT commands manual

Internet suite

G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+UFTPER+UHTTP+UHTTPC+UHTTPER+UPING+USMTP+USMTPC+USMTPER+USMTPM

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

+UHTTPAC+UFTPC+UDYNDNS

•
•

+UFTP

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UDNSRN+UDCONF=4

AT command

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•
•
•

B Appendix: AT Commands List

Page 901 of 1001

u-blox cellular modules - AT commands manual

Internet suite

UBX-13002752 - R67+UHTTPAC+UHTTPC+UHTTPER+UPING

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

+USMTPM+UHTTP•+USMTPER+UFTPER•+USMTPC+UFTPC•+USMTP+UFTP

L280-03S
L220-02S
L220-62S
L280-02S+UDYNDNS

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UDNSRN

L210-62S / L210-65S
L200-03A / L210-03A+UDCONF=4

AT command

Page 902 of 1001

u-blox cellular modules - AT commands manualDevice and data security+USECPRF

•

•

•
•
•

•
•
•

•

•

•

•

•

•

•
•
•
•

•
•
•
•

•

•

•
•

•
•

•

•

•

•

•

•

•

•

+USECCFG+USECMNG

AT command

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 903 of 1001

u-blox cellular modules - AT commands manualDevice and data security

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67••+USECPRF

L210-62S / L210-65S
L200-03A / L210-03A+USECMNG+USECCFG

AT command

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 904 of 1001

u-blox cellular modules - AT commands manual

+UISS

•
•

+UISMS+UIMSRCONF••+UIMSREG+UIMSCONF+UIMSCFG+UICMGSMODE+UCMT3GPP2+CMMIVT+CIREP+CIREG+CEVDP+CASIMSAT command+UCMGS3GPP2

IP Multimedia Subsystem (IMS)

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•
•

•
•

B Appendix: AT Commands List

Page 905 of 1001

u-blox cellular modules - AT commands manual+UISS+UISMS+UIMSREG+UIMSRCONF

•
•
•
•
•
•

+UIMSCONF+CMMIVT

•
•
•
•
•
•

+UIMSCFG+CIREP

•
•
•
•
•
•
•
•

+UICMGSMODE+CIREG

•
•
•
•
•
•

+UCMT3GPP2+CEVDP+CASIMSAT command+UCMGS3GPP2

IP Multimedia Subsystem (IMS)

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S

•

•
•

•
•

•
•

•

•

•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•

•
•

•
•

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 906 of 1001

u-blox cellular modules - AT commands manualU201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S+UGIND+UGPRF+UGPS+UGRMC+UGTMR+UGUBX+UGVTG+UGZDA

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

+ULOC

+UGGSV+ULCSEVT+UGGSA••+UGSRV+UGGLL

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•

•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•

•
•
•
•

•
•
•
•

•
•
•
•

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S•••

U270-01S
U230-01S
U200-02S / U260-02S

U270-68S
U200-03S / U201-03S+UGGGA

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+UGAOS

G350-01B
G340-02S / G350-02S+UGAOPLEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UGAOF+CMTLRA+CMTLR+CMOLRE+CMOLR

AT command+UDCONF=70

Localization features

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 907 of 1001

u-blox cellular modules - AT commands manual+UGAOS+UGGGA+UGGLL+UGGSA+UGGSV+UGIND+UGPRF+UGPS+UGRMC+UGSRV+UGTMR+UGUBX+UGVTG+UGZDA

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

+ULOC

+UGAOP+ULCSEVT+UGAOF+CMTLRA+CMTLR+CMOLRE+CMOLR

AT command+UDCONF=70

Localization features

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 908 of 1001

u-blox cellular modules - AT commands manual

Localization features

•
•

•
•

G350-01B
G340-02S / G350-02S••

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B

•

•

•

•

•

•

•

•

•

•

•

U201-03X
U201-63B
U201-04A / U201-04B

•

•

•

•

•

•

•

•

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

•

•

•

•

•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•

•

•

•

•

•

•

•
•

•
•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+UTIME••LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+ULOCIND+ULOCGNSS••+ULOCAID+ULOCCELL

AT command••

L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 909 of 1001

u-blox cellular modules - AT commands manual

Localization features+ULOCCELL+ULOCGNSS+ULOCIND

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

+UTIME+ULOCAIDAT command

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 910 of 1001

u-blox cellular modules - AT commands manual

Mobile equipment control and status

UBX-13002752 - R67

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•
•
•

•
•
•

+CMER

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•

•

+CTZU

•

•
•

+CTZR

•
•
•
•
•

+CSGT

+CLCC

•

+CIND

•

+CFUN

•

•
•
•
•
•

+UCIND

•
•
•

•

•

•
•
•

•

•
•
•
•
•

•
•

+UCEER•+CISRVCC

•

•

•
•

•
•
•
•
•

•
•

+CRSL

L280-03S
L201-01S
L201-02S
L210-60S+CPWROFFU201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+CPAS

U270-68S
U200-03S / U201-03S

•

+CMEE

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

•

+CLVL

U270-01S
U230-01S
U200-02S / U260-02S

•

•

+CEER

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

•

•
•

+CCLK

U201-03X
U201-63B
U201-04A / U201-04B

•
•
•
•
•

•
•
•
•
•

+CALM

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B

•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

+CALD

G350-01B
G340-02S / G350-02S

•
•

•
•

•
•

+CALA
LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+CMUT

AT command

•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

B Appendix: AT Commands List

•

•
•
•

•
•

Page 911 of 1001

u-blox cellular modules - AT commands manual

Mobile equipment control and status

UBX-13002752 - R67

+CIND

+CLCC

+CLVL

+CMEE

+CMER

+CMUT

+CPAS

+CPWROFF

+CRSL

+CSGT

+CTZR

+CTZU

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•

•

•

•

•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•

+UCIND+CFUN•+UCEER+CEER•+CISRVCC+CCLK

L280-03S
L220-02S
L220-62S
L280-02S+CALM

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CALD

L210-62S / L210-65S
L200-03A / L210-03A+CALA

AT command

Page 912 of 1001

u-blox cellular modules - AT commands manual

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•
•

+UDCONF=20•+UDAMCFG

•

+UCSG

•

+UCSDETACH•+UCGOPS

•
•

+UCD

•

+UCGED+UCELLINFO+UBANDSEL

+CSQ

•
•
•
•
•

+UACT

+CREG

+PACSP+CPOL+CSSAC

+COPS

•
•
•
•
•

+CPLS

+COPN

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•

+CNEM

•
•
•
•
•

•
•

U201-03X
U201-63B
U201-04A / U201-04B

UBX-13002752 - R67

•
•
•
•
•

•
•

•
•

•
•
•
•
•

•
•
•
•

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B

L280-03S
L201-01S
L201-02S
L210-60S

•
•

•
•
•
•
•

G350-01B
G340-02S / G350-02S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+CNUM

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S

+CGED

+CESQ

AT command+UCELLLOCK

Network service

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•

•
•

•
•

•
•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List••

Page 913 of 1001

u-blox cellular modules - AT commands manual+UCGOPS+UCSDETACH

•

•

•

•

•

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

L280-03S
L220-02S
L220-62S
L280-02S

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

UBX-13002752 - R67

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•

•

+UDCONF=20+UCGED•+UDAMCFG+UCELLLOCK•+UCELLINFO

•

+UCD

+CSQ

•

+UBANDSEL

+CREG

•

+UACT

+CPOL

•

+PACSP+CPLS•+CSSAC

+COPS

•

+CNEM

+COPN

L210-62S / L210-65S
L200-03A / L210-03A

+CGED

•

+CESQ

+CNUM

AT command+UCSG

Network service

•
•
•
•
•

•

•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

Page 914 of 1001

u-blox cellular modules - AT commands manualU201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S••

U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•

•

•

+UNVMPLMN+UMNOPROF+UMNOPLMN

•

•

•

•

•

•

•

•

•

•

+URPM

•

+URAT

•

+UNVMMCC+UNFMCONF

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+UMNOCONF•+ULTECAT

•

+UJAD

+UNFM

G350-01B
G340-02S / G350-02S+UHSDUPA

•
•
•
•
•

+UHOMEZR+UEONS•••••LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UFDAC+UDOPN+UDCONF=83+UDCONF=81+UDCONF=61+UDCONF=59+UDCONF=57+UDCONF=56

AT command+UDCONF=55

Network service

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•
•
•
•

•
•
•
•

•
•
•
•

•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•
•
•

•

•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•
•
•

•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•

•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

•
•

•
•

•
•

Page 915 of 1001

u-blox cellular modules - AT commands manual

UBX-13002752 - R67

•

•

•

•

•

•

•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•
•
•

•

•
•

•
•
•
•
•
•

•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•

B Appendix: AT Commands List

•

•

+URAT

•

+UNVMMCC•+UNFMCONF

•

+UNFM

•

+UMNOPROF

•

•
•
•
•
•
•
•

•
•

•

•
•
•
•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•

+URPM

+UNVMPLMN+UMNOPLMN+UMNOCONF•+ULTECAT

•

+UJAD

•

+UHSDUPA+UFDAC•+UHOMEZR+UEONS+UDCONF=83+UDCONF=59+UDCONF=57+UDOPN

L280-03S
L220-02S
L220-62S
L280-02S+UDCONF=81

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UDCONF=61

L210-62S / L210-65S
L200-03A / L210-03A+UDCONF=56

AT command+UDCONF=55

Network service

•

•
•
•
•
•
•
•

•

Page 916 of 1001

u-blox cellular modules - AT commands manual

Network service+WS46+VZWRSRQ+VZWRSRP+VZWAPNE+URPMCONF

AT command

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B•

U201-03X
U201-63B
U201-04A / U201-04B••

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

•
•
•
•
•
•
•
•
•
•

U270-01S
U230-01S
U200-02S / U260-02S••

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S•••

U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•

•
•
•

•
•

•
•

•
•
•

B Appendix: AT Commands List

Page 917 of 1001

u-blox cellular modules - AT commands manual

Network service

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67+WS46+VZWRSRQ+VZWRSRP+VZWAPNE+URPMCONF

AT command

•
•

•

•
•
•
•
•
•
•

•

•

•
•

•
•

•
•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

Page 918 of 1001

u-blox cellular modules - AT commands manual+UIPROUTE+UIPTABLES
•

•

•

•

•

•
•
•
•

•
•
•
•

•

•

•

•
•
•

•
•
•

•
•
•

+UIPCONF•+UIPADDR+UIP6TABLES+UIFCONF+UDPDP+UDNSCONF+UDCONF=71+UDCONF=67+UBMCONF

AT command+UDCONF=64

Networking

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•

•

•

•

•

•

•

•

•

•
•

•

•

•
•

•
•

•

•

•
•
•

•
•
•

•
•
•

•
•
•
•

•

B Appendix: AT Commands List

Page 919 of 1001

u-blox cellular modules - AT commands manual

UBX-13002752 - R67+UIPROUTE+UIPTABLES+UIP6TABLES

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•
•
•

•
•
•

•
•
•
•
•

+UIFCONF••+UDPDP+UIPCONF

L280-03S
L220-02S
L220-62S
L280-02S+UDNSCONF+UIPADDR

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UDCONF=71•+UBMCONF
L210-62S / L210-65S
L200-03A / L210-03A+UDCONF=67

AT command+UDCONF=64

Networking

•
•

•

•

B Appendix: AT Commands List

Page 920 of 1001

u-blox cellular modules - AT commands manual+CGEQOSRDP

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

+CGEQREQ•+CGEQOS•+CGEQNEG•+CGEQMIN

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

U270-68S
U200-03S / U201-03S+CGDSCONT•+CGDEL•+CGCMOD•••••+CGCLASS

•
•
•
•
•

+CGAUTO•••••+CGATT•••••+CGANS

•
•
•
•
•

•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

+CGPERMSET

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

UBX-13002752 - R67

•
•
•
•
•

+CGPERMACTU270-01S
U230-01S
U200-02S / U260-02S

L280-03S
L201-01S
L201-02S
L210-60S

•
•
•
•
•

•

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+CGPADDR

U201-03X
U201-63B
U201-04A / U201-04B+CGEREP

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CGDCONT

G350-01B
G340-02S / G350-02S+CGDATALEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+CGACT+CEUS+CEREG+CEMODEAT command+CGCONTRDP

Packet switched data services••

Page 921 of 1001

u-blox cellular modules - AT commands manual

UBX-13002752 - R67+CGCMOD+CGCONTRDP+CGDATA+CGDCONT+CGDEL+CGDSCONT+CGEQMIN+CGEQNEG+CGEQOS+CGEQOSRDP+CGEQREQ+CGEREP+CGPADDR

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

+CGPERMSET+CGCLASS•+CGAUTO•+CGATT•+CGANS+CGACT

L280-03S
L220-02S
L220-62S
L280-02S+CEUS

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CEREG

L210-62S / L210-65S
L200-03A / L210-03A+CEMODEAT command+CGPERMACT

Packet switched data services

Page 922 of 1001

u-blox cellular modules - AT commands manual

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

U270-01S
U230-01S
U200-02S / U260-02S

•

•
•
•
•

•

•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•
•

+UPSD

•

+UPCO

+UGCNTSET

•

+UFGI

•

+UDNS

•

+UDCONF=9+UGCNTRD+UDCONF=66•

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

UBX-13002752 - R67+UDCONF=12•

U201-03X
U201-63B
U201-04A / U201-04B

L280-03S
L201-01S
L201-02S
L210-60S+UDCONF=11•+UCLASS•+UCGDFLT••

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+UCGCLASS

•
•
•
•
•

+UCGATT•••••

G350-01B
G340-02S / G350-02S

U270-68S
U200-03S / U201-03S+UAUTHREQ

•
•
•
•
•

+CGTFTRDP+CGREG•••••+CGTFT+CGQREQ•••••

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S+CGSCONTRDP+CGQMIN•••••+CGPIAF

AT command+CGPERMSTATE

Packet switched data services

•
•

•
•
•
•
•
•
•
•
•
•

•

•
•
•

Page 923 of 1001

u-blox cellular modules - AT commands manual

UBX-13002752 - R67+UCLASS+UDCONF=66+UDCONF=9

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•

•
•
•
•
•

•

•

•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

+UPSD

+UCGDFLT•+UPCO+UCGCLASS•+UGCNTSET+UCGATT•+UGCNTRD+UAUTHREQ

•

+UFGI

+CGTFTRDP

•

+UDNS

+CGTFT•+UDCONF=12+CGSCONTRDP•+UDCONF=11+CGREG

L280-03S
L220-02S
L220-62S
L280-02S+CGQREQ

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CGQMIN

L210-62S / L210-65S
L200-03A / L210-03A+CGPIAF

AT command+CGPERMSTATE

Packet switched data services

•
•
•
•

•
•
•
•

Page 924 of 1001

u-blox cellular modules - AT commands manual

Packet switched data services

U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+UTGSINK

•
•

+UREG

•
•

H

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B

•
•

D*

G350-01B
G340-02S / G350-02S+UPSND

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UPSDAAT command

•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•
•

•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

B Appendix: AT Commands List

Page 925 of 1001

u-blox cellular modules - AT commands manual

Packet switched data services

UBX-13002752 - R67+UTGSINK

D*

H

L280-03S
L220-02S
L220-62S
L280-02S+UREG

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UPSND

L210-62S / L210-65S
L200-03A / L210-03A+UPSDAAT command

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•

•

•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

B Appendix: AT Commands List

Page 926 of 1001

u-blox cellular modules - AT commands manual

Phonebook

U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

+UPBGR+CPBW

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CPBS

G350-01B
G340-02S / G350-02S+CPBR

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+CPBF

AT command•

B Appendix: AT Commands List

Page 927 of 1001

u-blox cellular modules - AT commands manual

Phonebook

UBX-13002752 - R67

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

+UPBGR+CPBW

L280-03S
L220-02S
L220-62S
L280-02S+CPBS

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CPBR

L210-62S / L210-65S
L200-03A / L210-03A+CPBF

AT command

B Appendix: AT Commands List

Page 928 of 1001

u-blox cellular modules - AT commands manualDevice lockU201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+USIMLCK

U201-03X
U201-63B
U201-04A / U201-04B+UPINCNT

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CPWD

G350-01B
G340-02S / G350-02S+CPIN

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+CLCK

AT command

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 929 of 1001

u-blox cellular modules - AT commands manualDevice lockUBX-13002752 - R67

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

+USIMLCK+UPINCNT

L280-03S
L220-02S
L220-62S
L280-02S+CPWD

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CPIN

L210-62S / L210-65S
L200-03A / L210-03A+CLCK

AT command

B Appendix: AT Commands List

Page 930 of 1001

u-blox cellular modules - AT commands manual

Serial interface

UBX-13002752 - R67

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•
•

S6

•
•
•
•
•

S5

•
•
•
•
•

S4

•
•
•
•
•

S3

•
•
•
•
•

S2

+IPR

•
•
•
•
•

S12

+IFC

•
•
•
•
•

S10

+ICF

•
•
•
•
•

Q

+CMUX

•
•
•
•
•

O

L280-03S
L201-01S
L201-02S
L210-60S

•
•
•
•
•

E

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S

•
•
•
•
•

+UTPB

U270-68S
U200-03S / U201-03S&Y

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S&W

U270-01S
U230-01S
U200-02S / U260-02S&V

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S&S

U201-03X
U201-63B
U201-04A / U201-04B&K

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B&F

G350-01B
G340-02S / G350-02S&D

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S&C

AT command

•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•
•
•

•
•
•

•
•

•

•
•

•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 931 of 1001

u-blox cellular modules - AT commands manual

Serial interface

UBX-13002752 - R67

&S

&V

&W

&Y

+CMUX

+ICF

+IFC

+IPR

E

O

Q

S10

S12

S2

S3

S4

S5

S6

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

+UTPB

&K

L280-03S
L220-02S
L220-62S
L280-02S&F

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S&D

L210-62S / L210-65S
L200-03A / L210-03A&C

AT command

•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

Page 932 of 1001

u-blox cellular modules - AT commands manual

Serial interface

U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67\Q

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

Z

U201-03X
U201-63B
U201-04A / U201-04B

X

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B

V

G350-01B
G340-02S / G350-02S

S8LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S

S7

AT command

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•
•
•
•
•

•

B Appendix: AT Commands List

Page 933 of 1001

u-blox cellular modules - AT commands manual

Serial interface

UBX-13002752 - R67

\Q

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

X

Z

L280-03S
L220-02S
L220-62S
L280-02S

V

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S

S8

L210-62S / L210-65S
L200-03A / L210-03A

S7

AT command

•
•
•
•
•
•
•
•
•
•

•
•
•
•

B Appendix: AT Commands List

Page 934 of 1001

u-blox cellular modules - AT commands manual

Short Messages Service

UBX-13002752 - R67

+CSAS

+CSCA

+CSCB

+CSDH

+CSMP

+CSMS

+UCMGL+UCMGR

+CRES

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

+CPNER

+CPMS

•
•
•
•
•

+CMMS

+CNMI

L280-03S
L201-01S
L201-02S
L210-60S+CNMA

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S+CMSS

U270-68S
U200-03S / U201-03S+CMGW

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S+CMGS

U270-01S
U230-01S
U200-02S / U260-02S+CMGR

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S+CMGL

U201-03X
U201-63B
U201-04A / U201-04B+CMGF

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CMGD

G350-01B
G340-02S / G350-02S+CGSMSLEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UCMGP

AT command

B Appendix: AT Commands List•

Page 935 of 1001

u-blox cellular modules - AT commands manual

Short Messages Service

UBX-13002752 - R67

+CMGR

+CMGS

+CMGW

+CMMS

+CMSS

+CNMA

+CNMI

+CPMS

+CPNER

+CRES

+CSAS

+CSCA

+CSCB

+CSDH

+CSMP

+CSMS

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

+UCMGR+CMGL•+UCMGL+CMGF

L280-03S
L220-02S
L220-62S
L280-02S+CMGD

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CGSMS
L210-62S / L210-65S
L200-03A / L210-03A+UCMGP

AT command•

Page 936 of 1001

u-blox cellular modules - AT commands manual

G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

•

•

•

•

•
•
•

•

•

•

•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

U270-68S
U200-03S / U201-03S

UBX-13002752 - R67••

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

L280-03S
L201-01S
L201-02S
L210-60S••

U270-01S
U230-01S
U200-02S / U260-02S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S

+UMWI

•

+UETWNTFYSTOP•+UETWNTFYSTART

•
•
•
•
•

+UETWCFG

•
•
•
•
•

+UDCONF=13+UCMGW

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UCMGS

AT command+UDCONF=82

Short Messages Service

•

•

•

•
•

•
•
•
•

•
•

B Appendix: AT Commands List

Page 937 of 1001

u-blox cellular modules - AT commands manual

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67+UMWI+UETWNTFYSTOP+UETWNTFYSTART+UETWCFG+UDCONF=13+UCMGW+UCMGS

AT command+UDCONF=82

Short Messages Service

•
•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•

B Appendix: AT Commands List

Page 938 of 1001

u-blox cellular modules - AT commands manual

UBX-13002752 - R67+UCATTR
•
•

•

•

•

•

•

•

•

•
•
•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

+SATR

•

+SATE

•
•
•
•
•

+SATD

•
•
•
•
•

+CUAD

•
•
•
•
•

+UBIPAPN

•
•

•
•
•
•
•

+UBIP

•
•

+STKTR••+STKPROF••+STKPRO+UCATPRON

L280-03S
L201-01S
L201-02S
L210-60S

•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•

•
•
•
•

•
•
•
•

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S

•
•
•
•
•

•

U270-01S
U230-01S
U200-02S / U260-02S

U270-68S
U200-03S / U201-03S+UCATPROI

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S+UCATPROF

U201-03X
U201-63B
U201-04A / U201-04B+UCATENV

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+STKENV

G350-01B
G340-02S / G350-02S+CSIM

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S

+CRSM

+CRLA

+CLAN

+CGLA

+CCHO

+CCHC

AT command+STKCTRLIND

SIM functionalities

•
•
•
•
•
•
•
•
•

•
•
•
•

•
•
•
•

•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•
•
•

Page 939 of 1001

u-blox cellular modules - AT commands manual

UBX-13002752 - R67+UCATENV+UCATPROF+UCATPROI+UCATPRON+UCATTR

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•

•

+UBIPAPN

•

+UBIP

•

+STKTR•+STKPROF•+STKPRO+CUAD•+STKENV

+CSIM

•

+SATR

+CRSM

•

+SATE

+CRLA

•

+SATD

+CLAN

L280-03S
L220-02S
L220-62S
L280-02S+CGLA

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+CCHO

L210-62S / L210-65S
L200-03A / L210-03A+CCHC

AT command+STKCTRLIND

SIM functionalities

•
•
•
•
•
•
•
•
•
•

Page 940 of 1001

u-blox cellular modules - AT commands manual+UDTMF+USAPIND+USAPMODE+USIMATR+USIMSTAT+UUICC

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•

•

•

•
•
•

•

+URCATR+UDCONF=54•+URCATE+UDCONF=50•+URCATCC+UCSP

AT command+XSIMSWITCH

SIM functionalities

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•

•

•
•
•
•

•

•

•
•

•
•

•
•

•

•

•

•

•
•
•

•
•
•

•
•
•

•

•
•
•
•
•
•
•
•
•

•

•

•
•

•
•
•
•
•
•
•
•
•
•
•
•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•

B Appendix: AT Commands List

Page 941 of 1001

u-blox cellular modules - AT commands manual

UBX-13002752 - R67

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•

•
•
•

•
•
•

•

•
•
•
•

•
•

•

•
•
•
•
•
•
•
•

•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•
•
•

•

•
•
•

•
•
•

•
•
•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

+XSIMSWITCH•+UUICC•+USIMSTAT•+USIMATR+URCATR•+USAPMODE+URCATE•+UDCONF=54+URCATCC

L280-03S
L220-02S
L220-62S
L280-02S+UDTMF

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UDCONF=50

L210-62S / L210-65S
L200-03A / L210-03A+UCSP

AT command+USAPIND

SIM functionalities

•

•

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

Page 942 of 1001

u-blox cellular modules - AT commands manual

Supplementary services

U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S

L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

+CCWA

+CCWE

+CHLD

+CLIP

+CLIR

+CNAP

+COLP

+COLR

+CPUC

+CSSN

+CTFR

+CUSD

+CUUS1

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•

+CPPS

+CCUG

+CAEMLPP

•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S

•
•
•
•
•

•

U270-01S
U230-01S
U200-02S / U260-02S

U270-68S
U200-03S / U201-03S+CCFC

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+CAOC

G350-01B
G340-02S / G350-02S+CAMM

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S

+CACM

+CAAP

AT command

•
•
•
•
•
•
•
•
•

•
•
•
•

•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 943 of 1001

u-blox cellular modules - AT commands manual

Supplementary services

UBX-13002752 - R67

+CLIP

+CLIR

+CNAP

+COLP

+COLR

+CPUC

+CSSN

+CTFR

+CUSD

+CUUS1

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•

•
•

•

•

•

•

•

•
•
•
•
•
•

•

•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•

•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•
•
•

•
•
•

•
•
•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

B Appendix: AT Commands List

+CPPS

+CHLD

•

•

•

+CCWA

•

+CAOC

+CAMM

+CAEMLPP+CCWE

L280-03S
L220-02S
L220-62S
L280-02S•+CCUG

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S

•

+CCFC

L210-62S / L210-65S
L200-03A / L210-03A

+CACM

+CAAP

AT command

•

•
•
•
•
•

Page 944 of 1001

u-blox cellular modules - AT commands manual+UDATACHANNEL

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•
•

•
•

•
•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S

•
•
•
•
•
•
•
•
•

•
•
•
•

•
•
•
•

•

•
•
•
•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•

•

•

•

•

•

•
•

•
•

•
•
•
•
•

•

•

•

•

•
•

•

•

•

•

•
•

•

•

•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•

•
•
•
•
•
•
•

•

•

•

•
•

•

•

•

•

•

•
•

•

•
•
•

B Appendix: AT Commands List

•

•

•

•
•
•

•

•
•
•
•
•
•
•
•
•

•

•
•
•
•
•
•
•

•

+UNVMW••+UNVMR••+UNVMF

•

•
•
•
•
•

+ULGASP•+UFWUPD•+UFWSINSTALL•+UFWINSTALL•+UFACTORY•+UDCONF=78•+UDCONF=60•+UDCONF=40•+UDCONF=110•+UDCONF=0

•

+UCTS

•

+UCEDATA

•

•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•

U270-01S
U230-01S
U200-02S / U260-02S

UBX-13002752 - R67+UOMADMREPU201-03X
U201-63B
U201-04A / U201-04B

L280-03S
L201-01S
L201-02S
L210-60S+UOMADMALERT

G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S•••

G350-01B
G340-02S / G350-02S

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S•+UANTR+UANT••+UOMADMLEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UADC

AT command*KTF*OPENING

System features

Page 945 of 1001

u-blox cellular modules - AT commands manual

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

B Appendix: AT Commands List

•

•

•
•
•
•

•
•
•
•

•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•

•

•
•
•
•
•

•
•

+UOMADMREP

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

+UOMADMALERT

•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

+UOMADM•••+UNVMW••+UNVMR

•
•
•
•
•
•
•
•
•
•
•
•
•

•

+UNVMF

•
•
•
•
•
•
•
•
•
•
•
•
•

•

+ULGASP••+UFWUPD••+UFWSINSTALL•+UFWINSTALL•+UFACTORY•+UDCONF=78+UDCONF=60•+UDCONF=0+UDCONF=40+UDCONF=110+UDATACHANNEL

•

+UCTS

•

+UCEDATA+UANTR

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+UANT

L210-62S / L210-65S
L200-03A / L210-03A+UADC

AT command*KTF*OPENING

System features•

Page 946 of 1001

u-blox cellular modules - AT commands manual

System features

•

•

•

•
•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•
•

•
•

•
•

•

•

•

•

•

•

•

•
•

•
•

•
•

•

•
•
•
•
•
•

•

•
•

•
•

•
•
•
•
•
•
•
•
•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•

•
•
•
•

•

•

•

•

•

•

•

•

KTUUMTSENV•+UUSBCONF+UTEST••U270-68S
U200-03S / U201-03S

UBX-13002752 - R67••

U270-02S
U200-52S
U200-62S
U270-62S / U270-63S

L280-03S
L201-01S
L201-02S
L210-60S••

U270-01S
U230-01S
U200-02S / U260-02S

U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S•

KTUCALLREJ

U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S•

KTUBXCONF

U201-03X
U201-63B
U201-04A / U201-04B

•
•

•
•
•
•
•

KTDEVSTAT

G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B+UTEMP••

KTCFUNLEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S

+USTS

+USIO

+URXDIV+URING+UOMASTAT

AT command

•

•

•

•

•

•
•

B Appendix: AT Commands List

Page 947 of 1001

u-blox cellular modules - AT commands manual

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

•
•
•
•
•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•
•

KTUUMTSENV•KTUBXCONF•KTDEVSTAT•KTCFUN•+UTEMP

•

+USTS

•

+USIO

+UUSBCONF•+UTEST

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S+URXDIV

L210-62S / L210-65S
L200-03A / L210-03A+URING+UOMASTAT

AT command

KTUCALLREJ

System features

•
•
•
•
•

B Appendix: AT Commands List

Page 948 of 1001

u-blox cellular modules - AT commands manual

Power management+UPSV

AT command

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•

B Appendix: AT Commands List

Page 949 of 1001

u-blox cellular modules - AT commands manual

Power management+UPSV

AT command

L210-62S / L210-65S
L200-03A / L210-03A
L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

B Appendix: AT Commands List

Page 950 of 1001

u-blox cellular modules - AT commands manual

G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+USODL+USOER+USOGO+USOLI+USORD+USORF

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

+USOSO+USOCTL+USOSEC+USOCR••+USOCO+USOAO+UIPCHGN+UFRW+UDCONF=8+UDCONF=7+UDCONF=6+UDCONF=5+UDCONF=3••+USOCL

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+UDCONF=2+UDCONF=1

AT command+UDCONF=10

Internet protocol transport layer

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•
•
•

•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•
•

B Appendix: AT Commands List

Page 951 of 1001

u-blox cellular modules - AT commands manual+USOCL+USOCO+USOCR+USOCTL+USODL+USOER+USOGO+USOLI+USORD+USORF+USOSEC+USOSO

•

•

•

•

•

•

•

•

•

•

•

•

•

•

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•
•

•

•
•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

L280-03S
L220-02S
L220-62S
L280-02S

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

UBX-13002752 - R67

•
•
•
•
•
•
•
•
•
•

+USOAO•+UIPCHGN+UDCONF=8

•

+UFRW

+UDCONF=7•+UDCONF=3+UDCONF=6

L210-62S / L210-65S
L200-03A / L210-03A+UDCONF=2•+UDCONF=1+UDCONF=5

AT command+UDCONF=10

Internet protocol transport layer

B Appendix: AT Commands List

Page 952 of 1001

u-blox cellular modules - AT commands manual

Internet protocol transport layer

G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67+USOWRLEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S+USOST

AT command

•
•

•
•

•
•

•
•

•

•

•

•

•
•
•

•
•
•

•

•

•

•

•

•

•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•

•

•

•

•

•

•

•
•

•
•

•

•

•

•

•
•

•
•

•

•

•

•

•
•

•
•

B Appendix: AT Commands List

Page 953 of 1001

u-blox cellular modules - AT commands manual

Internet protocol transport layer

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67+USOWR

L210-62S / L210-65S
L200-03A / L210-03A+USOST

AT command

•

•

•

•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•
•
•
•
•
•
•
•
•
•
•
•

•
•

•
•

•

•

•

•

•
•
•

•
•
•

B Appendix: AT Commands List

Page 954 of 1001

u-blox cellular modules - AT commands manual+UWFWRESET+UWMP+UWREGBLOCK+UWSCAN+UWSTACFG

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

+UWWEBUIFTP+UWCFG•+UWWEBUI+UWAPSTALIST•+UWTEST+UWAPMACADDR•+UWSTAIPCFG+UWAPIPCFG•

AT command

•

•

•

•

•

•

•

•

•

•

•

•

•

•

+UWSTACSQ+UWAPCFG

Wi-Fi interface

LEON G100-06S
G100-07S / G100-08S
SARA G300-00S / G310-00S
G340-00S / G350-00S
G350-00X
G340-01S / G350-01S
G350-01B
G340-02S / G350-02S
G350-02A
G340-02X / G350-02X
G450-00C
G450-01C
U201-03A / U201-03B
U201-03X
U201-63B
U201-04A / U201-04B
U201-04X
U260-00S / U280-00S
U270-00S / U270-00X
U260-03S / U280-03S
U270-03A / U270-03S
U270-53S
U270-73S
LISA U100 / U110
U120 / U130
U200-00S
U200-01S / U260-01S
U270-01S
U230-01S
U200-02S / U260-02S
U270-02S
U200-52S
U200-62S
U270-62S / U270-63S
U270-68S
U200-03S / U201-03S
U201-03A
U200-83S / U201-83S
U200-04B / U201-04B
TOBY L4006-01A
L4006-51A
L4106-01A
L4106-51A
L4206-01A
L4206-51A
L4906-01A
L4906-50A
L4906-51A
L200-00S / L210-00S
L200-02S / L210-02S
L200-03S / L210-03S
L280-03S
L201-01S
L201-02S
L210-60S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 955 of 1001

u-blox cellular modules - AT commands manual+UWFWRESET+UWMP+UWREGBLOCK+UWSCAN+UWSTACFG

•

•

•

•

•

•

•

L280-03A
L280-02S
L220-02S
L220-62S
R200-02B / R202-02B
R200-42B
R200-82B
LARA R202-02B
R202-82B
R203-02B
R204-02B
R211-02B
R220-62B
R280-02B
MPCI L200-00S / L210-00S
L201-01S
L201-02S
L210-60S / L210-63S
L200-02S / L210-02S
L200-03S / L210-03S

•

•

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•
•
•

•

+UWWEBUIFTP+UWCFG•+UWWEBUI+UWAPSTALIST•+UWTEST+UWAPMACADDR

L210-62S / L210-65S
L200-03A / L210-03A+UWSTAIPCFG+UWAPIPCFG•

AT command+UWSTACSQ+UWAPCFG

Wi-Fi interface

•

•

•

•

•

•

•

•

•
•
•

•
•
•

•
•
•

•
•
•

L280-03S
L220-02S
L220-62S
L280-02S

UBX-13002752 - R67

B Appendix: AT Commands List

Page 956 of 1001

u-blox cellular modules - AT commands manual

B.1 Parameters stored in profiles
The parameter settings of some commands can be stored in the profiles available in the memory module.
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1
To store, partially display, activate and deactivate these profiles, see the AT&W, AT&V, AT&Y commands
description. Not all the parameter setting are displayed through AT&V command.
TOBY-L4
To store, display, reset to default value the available profile, see the AT&W, AT&V, and ATZ commands
description.
Some AT commands have a unique configuration for all the AT interfaces while for other AT commands it
is possible to set a different configuration for each AT interface: the "AT interface configuration sharing"column in the next table provides this information.
Some AT command interfaces have a dynamic activation, which means they are not statically activatedat boot time (MUX AT channel is activated when the MUX protocol is established, USB AT channel isactivated if/when the USB cable is plugged-in, deactivated when it is removed). Since the activation
reloads the AT command profile from NVM for the activated interface, the shared "AT interface
configurations" could be overwritten. It is suggested to reconfigure them at the requested value if an AT
command interface is dynamically activated.
LARA-R211 / SARA-U201-04A / SARA-U201-04B / SARA-U201-04X
Due to AUX UART interface's limitations, at boot time, the parameter setting of AT+IFC command stored
in the profile might be not applicable. In this case, the factory-programmed value is applied.
The same behaviour is experienced in case the ATZ or AT&F commands are issued by the DTE on the AUXUART interface.
LARA-R211
The AUX UART interface is not supported by LARA-R211-02B-00, LARA-R211-02B-01 and
LARA-R211-02B-02.
SARA-G450-01C / SARA-G340-02S / SARA-G340-02X / SARA-G350-02A / SARA-G350-02S /SARA-G350-02X
Due to AUX UART interface's limitations, at boot time, the parameter setting of AT+IPR, AT+ICF and AT+IFC commands stored in the profile might be not applicable. In this case, the factory-programmed value
is applied.
The same behaviour is experienced in case the ATZ or AT&F commands are issued by the DTE on the AUXUART interface.
The following table lists the AT commands which setting can be stored in the profiles with their parameters
as well as the factory-programmed values.
AT command

Description

&C
&D
&K

DCD status
DTR status
Flow control status

AT interface
configuration
sharing
No
No
No

&S

DSR override

No

+CBST

Bearer service type

Yes

Factory-programmed value / Remarks

1 (DCD enabled)
1 (DTR enabled)•

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - 3 (RTS/CTS DTE flow control enabled)
1 (DSR line set to ON in data mode and to OFF in command
mode)
•

•
+CGREGGPRS network
registration status
reporting

Yes

+CMEE

Mobile termination
error reporting

Yes

•

•

UBX-13002752 - R67•

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 - 71
(Speed: 9600 b/s (V110 or X.31 flag stuffing)), 0 (data circuit
asynchronous), 1 (non-transparent)
SARA-G3 / LEON-G1 - 7 (Speed: 9600 b/s (V.32)), 0 (datacircuit asynchronous), 1 (non-transparent)
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The
command settings is not stored in the personal profile
SARA-G4 - 0 (network registration URC disabled)
TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The
command settings is not stored in the personal profile

B Appendix: AT Commands List

Page 957 of 1001

u-blox cellular modules - AT commands manual

AT command

Description

AT interface
configuration
sharing

Factory-programmed value / Remarks

•
+CMGF

Preferred message
formatYes

SARA-G4 - 0 (error result code formatting disabled and
ERROR used)
0 (format of messages in PDU mode)
TOBY-L201-02S / MPCI-L201-02S
On TOBY-L201-02S-00, TOBY-L201-02S-01, MPCI-L20102S-00, MPCI-L201-02S-01 the default value is 1 (textmode) if the module is configured in Verizon mode(+UMNOCONF: 3,<conf>).
TOBY-L201-01S / MPCI-L201-01S
The default value is 1 (text mode) if the module isconfigured in Verizon mode (+UMNOCONF: 3,<conf>).

+CNMI

New message
indication

Yes

•
•
•
•
•

+COPS

Operator selection

Yes

•
•
•

+CPMS

Preferred message
storage

No

•

+CR

Reporting control
NostatusCellular result code No
statusNetwork registration Yes
status reporting

+CRC
+CREG

Radio Link protocol
settings

Yes

0 (extended format disabled)
•

•

•

+CSCA
+CSCB

Service center
address
cell broadcast
message types

UBX-13002752 - R67

0 (autoregistration enabled)0 (operator expressed in long alphanumeric format)
FFFFF (undefined PLMN to register when +COPS: 1)

TOBY-L4 - The command setting is not stored in the
personal profile• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The commandsetting is stored in the NVM• SARA-G4 - <mem1>, <mem2> and <mem3> are set to "ME"0 (reporting disabled)

•
+CRLP

1 (discard indication and reject new received message URCs
when MT-DTE link is reserved)
0 (no SMS-DELIVER indications are routed to the TE)
0 (no CBM indications to the DTE)
0 (no SMS-STATUS-REPORTs are routed to the DTE)
0 (MT buffer of URCs defined within this command isflushed to the DTE when >mode< 1...3 is entered)

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The
command settings is not stored in the personal profile
SARA-G4 - 0 (network registration URC disabled)
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U200-03S /LISA-U200-04B / LISA-U200-83S / LISA-U201 /SARA-G340-01S / SARA-G340-02S / SARA-G340-02X /SARA-G350-01B / SARA-G350-01S / SARA-G350-02A /SARA-G350-02S / SARA-G350-02X / LEON-G100-07S /LEON-G100-08S
o 61 (IWF to MT window size)o 61 (MT to IWF window size)o 48 (acknowledgement timer)o 7 (retransmission attempts)
LISA-U200-00S / LISA-U200-01S / LISA-U200-02S /LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G300 /SARA-G310 / SARA-G340-00S / SARA-G350-00S /SARA-G350-00X / LEON-G100-06So 61 (IWF to MT window size)o 61 (MT to IWF window size)o 48 (acknowledgement timer)o 6 (retransmission attempts)

No
No

B Appendix: AT Commands List

Page 958 of 1001

u-blox cellular modules - AT commands manual

AT command

Description+CSMP

Select message
service
Select character set No
configuration+CSCS

AT interface
configuration
sharing
No

Factory-programmed value / Remarks

•

•
+CSMS

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The
command setting is not persistent
SARA-G4 - The command setting is stored in the NVM

Select message
service
Single numbering
schemeNoYes

0 (voice bearer service, during a mobile terminated single
numbering scheme call)• LISA-U200-00S / LISA-U200-01S / LISA-U200-02S /LISA-U200-52S / LISA-U200-62S / LISA-U230 /LISA-U260 / LISA-U270 / LISA-U1 / SARA-G300 /SARA-G310 / SARA-G340-00S / SARA-G340-01S /SARA-G350-00S / SARA-G350-00X / SARA-G350-01B /SARA-G350-01S / LEON-G1 - The command setting is notstored in the profile+ICF

DTE-DCE character
framing

No

•

+IFC

DTE-DCE local flow
control
Baud rate

No

Audio parameters
tuningDownlink biquaddigital filters

Yes

+CSNS

+IPR

+UAPT
+UDBF

No

Yes

TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 - 3, 1 (framing format: 8 data 1 stop, noparity)• SARA-G3 / LEON-G1 - 0, 0 (framing format autodetected)
2 (<DCE_by_DTE> on circuit 106 (CTS)), 2 (<DTE_by_DCE> on
circuit 105 (RTS))•

TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /SARA-G4 / SARA-G3 / LEON-G1 - 0 (autobauding enabled)• LISA-U200-00S / LISA-U1 - 115200 (115200 b/s)
See TOBY-L2 Audio Application Note [181] for the factoryprogrammed values stored in the profiles.
•

•

+UHFP

Hands-freeparameters

UBX-13002752 - R67

Yes•

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G3 - For all paths, all the filters are set to: 0 (a1), 0(b1), 0 (a2), 0 (b2), 32767 (a0)LEON-G1o Path 0:- Filter1: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)- Filter2: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)o Path 1:- Filter1: -29322 (a1), -29141 (b1), 29322 (a2), 26240(b2), 29322 (a0)- Filter2: 29322 (a1), 29141 (b1), 29322 (a2), 26240 (b2),29322 (a0)o Path 3:- Filter1: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)- Filter2: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)o Path 4:- Filter1: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)- Filter2: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)LARA-R2 / TOBY-R2
o Paths 0, 1, 2, 3: 0x0124 (HF_algorithm_init), NA(HF_Algorithm_Restart), NA (Step_Width), NA (LMS_
Length), NA (LMS_Offset), NA (Block_Length), NA(RXTX_Relation), 0 (Add_Atten), 0 (Min_Atten), 480(Max_Atten), 8192 (NR_sw_2), 7500 (NR_u_fak_0),
7500 (NR_u_fak), 2 (EC_block_length), 100 (EC_nr_
coeff_real), 100 (EC_nr_coeff_complex1), 100 (EC_nr_
coeff_complex2), 60 (EC_nr_coeff_complex3), 60 (EC_nr_coeff_complex4), 60 (EC_nr_coeff_complex5)o Path 4: 0x0524 (HF_algorithm_init), NA (HF_Algorithm_
Restart), NA (Step_Width), NA (LMS_Length), NA(LMS_Offset), NA (Block_Length), NA (RXTX_Relation),

B Appendix: AT Commands List

Page 959 of 1001

u-blox cellular modules - AT commands manual

AT command

Description

AT interface
configuration
sharing

Factory-programmed value / Remarks

•

•

•

•

UBX-13002752 - R67

15 (Add_Atten), 0 (Min_Atten), 191 (Max_Atten), 600
0 (NR_sw_2), 4500 (NR_u_fak_0), 5000 (NR_u_fak), 1(EC_block_length), 100 (EC_nr_coeff_real), 100 (EC_nr_
coeff_complex1), 100 (EC_nr_coeff_complex2), 100 (EC_nr_coeff_complex3), 100 (EC_nr_coeff_complex4), 100(EC_nr_coeff_complex5)
SARA-U2 / LISA-U2
o All the paths are set to: 0x0124 (HF_algorithm_init),
NA (HF_Algorithm_Restart), NA (Step_Width), NA(LMS_Length), NA (LMS_Offset), NA (Block_Length),
NA (RXTX_Relation), 0 (Add_Atten), 0 (Min_Atten),
500 (Max_Atten), 8192 (NR_sw_2), 7500 (NR_u_fak_0), 7500 (NR_u_fak), 2 (EC_block_length), 100 (EC_nr_
coeff_real), 100 (EC_nr_coeff_complex1), 100 (EC_nr_
coeff_complex2), 60 (EC_nr_coeff_complex3), 60 (EC_nr_coeff_complex4), 60 (EC_nr_coeff_complex5)
SARA-U201-04A / SARA-U201-04B / SARA-U201-04X /LISA-U200-04B / LISA-U201-04B
o Paths 0, 1, 2, 3: 0x0124 (HF_algorithm_init), NA(HF_Algorithm_Restart), NA (Step_Width), NA (LMS_
Length), NA (LMS_Offset), NA (Block_Length), NA(RXTX_Relation), 0 (Add_Atten), 0 (Min_Atten), 500(Max_Atten), 8192 (NR_sw_2), 7500 (NR_u_fak_0),
7500 (NR_u_fak), 2 (EC_block_length), 100 (EC_nr_
coeff_real), 100 (EC_nr_coeff_complex1), 100 (EC_nr_
coeff_complex2), 60 (EC_nr_coeff_complex3), 60 (EC_nr_coeff_complex4), 60 (EC_nr_coeff_complex5)o Paths 4: 0x0524 (HF_algorithm_init), NA (HF_
Algorithm_Restart), NA (Step_Width), NA (LMS_
Length), NA (LMS_Offset), NA (Block_Length), NA(RXTX_Relation), 15 (Add_Atten), 0 (Min_Atten), 191(Max_Atten), 6000 (NR_sw_2), 4500 (NR_u_fak_0), 50
00 (NR_u_fak), 1 (EC_block_length), 150 (EC_nr_coeff_real), 150 (EC_nr_coeff_complex1), 150 (EC_nr_coeff_
complex2), 136 (EC_nr_coeff_complex3), 136 (EC_nr_
coeff_complex4), 136 (EC_nr_coeff_complex5)
LISA-U120 / LISA-U130
o Paths 0, 1, 2: 0x01fd (HF_algorithm_init), NA (HF_
Algorithm_Restart), NA (Step_Width), NA (LMS_
Length), NA (LMS_Offset), NA (Block_Length), NA(RXTX_Relation), 0 (Add_Atten), 0 (Min_Atten), 500(Max_Atten), 8192 (NR_sw_2), 7500 (NR_u_fak_0),
7500 (NR_u_fak), 2 (EC_block_length), 100 (EC_nr_
coeff_real), 100 (EC_nr_coeff_complex1), 100 (EC_nr_
coeff_complex2), 60 (EC_nr_coeff_complex3), 60 (EC_nr_coeff_complex4), 60 (EC_nr_coeff_complex5)o Path 4: 0x01fd (HF_algorithm_init), NA (HF_Algorithm_
Restart), NA (Step_Width), NA (LMS_Length), NA(LMS_Offset), NA (Block_Length), NA (RXTX_Relation),50 (Add_Atten), 100 (Min_Atten), 500 (Max_Atten),
8192 (NR_sw_2), 7500 (NR_u_fak_0), 7500 (NR_u_fak),2 (EC_block_length), 220 (EC_nr_coeff_real), 220 (EC_nr_coeff_complex1), 220 (EC_nr_coeff_complex2), 60(EC_nr_coeff_complex3), 60 (EC_nr_coeff_complex4),
60 (EC_nr_coeff_complex5)
SARA-G340 / SARA-G350
o Path 0: 0x31fd (HF_algorithm_init), NA (HF_Algorithm_
Restart), NA (Step_Width), NA (LMS_Length), NA(LMS_Offset), NA (Block_Length), NA (RXTX_Relation),0 (Add_Atten), 0 (Min_Atten), 588 (Max_Atten), 8192
(NR_sw_2), 16384 (NR_u_fak_0), 16384 (NR_u_fak), 2(EC_block_length), 100 (EC_nr_coeff_real), 100 (EC_nr_
coeff_complex1), 100 (EC_nr_coeff_complex2), 0 (EC_B Appendix: AT Commands List

Page 960 of 1001

u-blox cellular modules - AT commands manual

AT command

Description

AT interface
configuration
sharing

Factory-programmed value / Remarks

•

+UMGC

Microphone gain
control

Yes

•
•

•

•

UBX-13002752 - R67

nr_coeff_complex3), 0 (EC_nr_coeff_complex4), 0 (EC_nr_coeff_complex5)o Path 1: 0x31fd (HF_algorithm_init), NA (HF_Algorithm_
Restart), NA (Step_Width), NA (LMS_Length), NA(LMS_Offset), NA (Block_Length), NA (RXTX_Relation),0 (Add_Atten), 0 (Min_Atten), 588 (Max_Atten), 8192
(NR_sw_2), 16384 (NR_u_fak_0), 16384 (NR_u_fak), 2(EC_block_length), 100 (EC_nr_coeff_real), 100 (EC_nr_
coeff_complex1), 100 (EC_nr_coeff_complex2),0 (EC_nr_coeff_complex3),0 (EC_nr_coeff_complex4),0 (EC_nr_coeff_complex5)o Path 2: 0x31fd (HF_algorithm_init), NA (HF_Algorithm_
Restart), NA (Step_Width), NA (LMS_Length), NA(LMS_Offset), NA (Block_Length), NA (RXTX_Relation),0 (Add_Atten), 0 (Min_Atten), 588 (Max_Atten), 8192
(NR_sw_2), 16384 (NR_u_fak_0), 16384 (NR_u_fak), 2(EC_block_length), 100 (EC_nr_coeff_real), 100 (EC_nr_
coeff_complex1), 100 (EC_nr_coeff_complex2), 0 (EC_nr_coeff_complex3),0 (EC_nr_coeff_complex4),0 (EC_nr_coeff_complex5)o Path 4: 0x31fd (HF_algorithm_init), NA (HF_Algorithm_
Restart), NA (Step_Width), NA (LMS_Length), NA(LMS_Offset), NA (Block_Length), NA (RXTX_Relation),0 (Add_Atten), 0 (Min_Atten), 588 (Max_Atten), 8192
(NR_sw_2), 16384 (NR_u_fak_0), 16384 (NR_u_fak), 2(EC_block_length), 100 (EC_nr_coeff_real), 100 (EC_nr_
coeff_complex1), 100 (EC_nr_coeff_complex2), 0 (EC_nr_coeff_complex3), 0 (EC_nr_coeff_complex4), 0 (EC_nr_coeff_complex5)
LEON-G1o Path 0: 0x01fd (HF_algorithm_init), 0x016e (HF_
Algorithm_Restart), 2200 (Step_Width), 250 (LMS_
Length), 3 (LMS_Offset), 5 (Block_Length), 150 (RXTX_
Relation), 0 (Add_Atten), 0 (Min_Atten), 500 (Max_
Atten), 4096 (NR_sw_2), 16384 (NR_u_fak_0), 16384(NR_u_fak)o Path 1: 0x01fd (HF_algorithm_init), 0x016e (HF_
Algorithm_Restart), 2200 (Step_Width), 250 (LMS_
Length), 3 (LMS_Offset), 5 (Block_Length), 150 (RXTX_
Relation), 0 (Add_Atten), 0 (Min_Atten), 500 (Max_
Atten), 4096 (NR_sw_2), 16384 (NR_u_fak_0), 16384(NR_u_fak)o Path 2: 0x01fd (HF_algorithm_init), 0x016e (HF_
Algorithm_Restart), 2200 (Step_Width), 250 (LMS_
Length), 8 (LMS_Offset), 5 (Block_Length), 150 (RXTX_
Relation), 0 (Add_Atten), 0 (Min_Atten), 500 (Max_
Atten), 4096 (NR_sw_2), 16384 (NR_u_fak_0), 16384(NR_u_fak)
TOBY-L4o The digital gain of scal_i2s_in is 88.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
o All the paths are set to: NA (analog gain), 8192 (digital
gain)
LISA-U120 / LISA-U130
o Path 0: 12 (analog gain), 8192 (digital gain)o Path 1: 12 (analog gain), 8192 (digital gain)o Path 2: 6 (analog gain), 8192 (digital gain)o Path 4: 13 (analog gain), 8192 (digital gain)
SARA-G340 / SARA-G350
o Path 0: 10 (analog gain),8192 (digital gain)o Path 1: 10 (analog gain),8192 (digital gain)

B Appendix: AT Commands List

Page 961 of 1001

u-blox cellular modules - AT commands manual

AT command

Description

AT interface
configuration
sharing

Factory-programmed value / Remarks

•

+UPSV

Power saving control Yes

•

•

+USGC

Speaker gain control Yes

•
•

•

•

•

+USIO

Serial interfaces
configuration

UBX-13002752 - R67

Yes•o Path 2: 6 (analog gain),8192 (digital gain)o Path 4: 10 (analog gain),8192 (digital gain)
LEON-G1o Path 0: 10 (analog gain), 9384 (digital gain)o Path 1: 12 (analog gain), 8192 (digital gain)o Path 2: 6 (analog gain), 8192 (digital gain)
TOBY-L4 - 1 (power saving enabled), 5000 (guard period toenter S3 state expressed in milliseconds), 30000 (guard
period to enter suspended state expressed in milliseconds)
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - 0(power saving disabled)
TOBY-L4o The digital gain of the scal_i2s_out is 88.
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
o For all the paths are set to: NA (Speaker gain), NA(Headset gain), 8192 (speech and Tone Generator gain),
16384 (Synthesizers gain), NA (Speech gain)
LISA-U120 / LISA-U130
o Path 0: NA (speaker gain), 0 (headset gain), 8192
(speech and tone Generator gain), 16384 (synthesizers
gain), NA (speech gain)o Path 1: NA (speaker gain), 1 (headset gain), 8192 (speech
and tone Generator gain), 16384 (synthesizers gain), NA(speech gain)o Path 3: NA (speaker gain), 0 (headset gain), 8192
(speech and tone Generator gain), 16384 (synthesizers
gain), NA (speech gain)o Path 4: NA (speaker gain), 3 (headset gain), 8192
(speech and tone Generator gain), 16384 (synthesizers
gain), NA (speech gain)
SARA-G340 / SARA-G350
o Path 0: 3 (speaker gain), 3 (headset gain), 8192 (speech
and tone Generator gain), 16384 (synthesizers gain),
8192 (speech gain)o Path 1: 3 (speaker gain), 3 (headset gain), 8192 (speech
and tone Generator gain), 16384 (synthesizers gain),
8192 (speech gain)o Path 3: 3 (speaker gain), 3 (headset gain), 8192 (speech
and tone Generator gain), 16384 (synthesizers gain),
8192 (speech gain)o Path 4: 5 (speaker gain), 0 (headset gain), 8192 (speech
and tone Generator gain), 16384 (synthesizers gain),
8192 (speech gain)
LEON-G1o Path 0: 6 (speaker gain), 1 (headset gain), 8192 (speech
and tone generator gain), 16384 (synthesizers gain),
8192 (speech gain)o Path 1: 6 (speaker gain), 0 (headset gain), 8192 (speech
and tone generator gain), 16384 (synthesizers gain), 10
240 (speech gain)o Path 3: 0 (speaker gain), 6 (headset gain), 8192 (speech
and tone generator gain), 16384 (synthesizers gain),
8191 (speech gain)o Path 4: 6 (speaker gain), 6 (headset gain), 8192 (speech
and tone generator gain), 16384 (synthesizers gain),
8191 (speech gain)
SARA-U2 / SARA-G3 - The command setting is stored in the
NVM

B Appendix: AT Commands List

Page 962 of 1001

u-blox cellular modules - AT commands manual

AT command+USTN

Description

Sidetone

AT interface
configuration
sharing

Yes

Factory-programmed value / Remarks•

SARA-G450-01C - 1 (AT command on UART and on AUX
UART, diagnostic log on FT UART)•

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2
o Gain on all paths for side tone: 512
LISA-U120 / LISA-U130 / SARA-G340 / SARA-G350
o Gain on path 0 for side tone: 512o Gain on path 1 for side tone: 512o Gain on path 3 for side tone: 0o Gain on path 4 for side tone: 0
LEON-G1o Gain on path 0 for side tone: 2249
o Gain on path 1 for side tone: 2249
o Gain on path 3 for side tone: 0o Gain on path 4 for side tone: 0

•

•

+USTS

Smart temperature
supervisor+UTI

Audio parameters
YestuningParity bit
Yestransmission over
the air
Uplink biquad digital Yes
filters

+UTPB

+UUBF

Yes

•

TOBY-L4 - 3 (smart temperature feature enabled with noindication)• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - 0(smart temperature feature disabled)
See product-specific Extended Audio Tuning Application Note
for the factory-programmed values stored in the profiles.
0 (transmission of the parity bit over the air is disabled)

•

•

+UVGC

Volume gain control Yes

E
Q

Echo status
No
Result codeNosuppression
Automatic answer
No
Escape characterNo
selection
Command line
No
termination
character
ResponseNo
formatting character
Command lineNo
editing character
Connection
No
completion timeout
DCE response
No
format

S0
S2
S3

S4
S5
S7
V

UBX-13002752 - R67

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G340 / SARA-G350 - For all the paths, all filters are
set to: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)LEON-G1o Path 0: Filter1: -13915 (a1), 2249 (b1), 4377 (a2), -325 (b2),23450 (a0) Filter2: 21682 (a1), -2312 (b1), 17984 (a2), 15517 (b2), 32767 (a0)o Path 1: Filter1: -29322 (a1), -29141 (b1), 29322 (a2), 26240(b2), 29322 (a0) Filter2: 29322 (a1), 29141 (b1), 29322(a2), 26240 (b2), 29322 (a0)o Path 2: Filter1: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)Filter2: 0 (a1), 0 (b1), 0 (a2), 0 (b2), 32767 (a0)• <componentID> 0 (External codec Maxim MAX9860)• <gainID> 0: -5 (DVA: -5 dB)• <gainID> 1: OFF (DVST: OFF)• <gainID> 2: 20 (PAM: 20 dB)• <gainID> 3: 4 (PGAM: 4 dB)
1 (echo enabled)
0 (DCE transmits result codes)
0 (automatic answering disabled)
43 (043 corresponds the '+' character)
13 (0x0d corresponds to the carriage return character)

10 (0x0a corresponds to the line feed character)
8 (008 corresponds to the backspace character)60
1 (Verbose response text)

B Appendix: AT Commands List

Page 963 of 1001

u-blox cellular modules - AT commands manual

AT command

X

Description

AT interface
configuration
sharing
Result code selection No
and call progress
monitoring control

Factory-programmed value / Remarks

4 (CONNECT <text> result code is given upon entering online
data state; dial tone and busy detection are both enabled)

B.2 Parameters stored in non volatile memory
The following table lists the AT commands which setting can be stored in the non volatile memory with theirparameters and the factory-programmed values.
AT command
E

Description
Echo status

Factory-programmed value / Comment

&Y
+CALA
+CALM

Designate a default reset
profileAlarm
Alert sound mode

+CCLK

Clock

•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - "04/01/01,00:00:00+00"+CEMODEUE modes of operation for
EPS•

TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S /TOBY-L210-02S / TOBY-L210-03A / TOBY-L210-03S /TOBY-L210-62S / TOBY-L210-65S / TOBY-L220-02S /TOBY-L280 / MPCI-L200-02S / MPCI-L200-03S /MPCI-L210-02S / MPCI-L210-03S / MPCI-L220-02S /MPCI-L280 / LARA-R202 / LARA-R211 / LARA-R280 /TOBY-R2 - 1 (CS/PS mode 1 of operation; "voice-centric")
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S /TOBY-L210-60S / TOBY-L220-62S / MPCI-L200-00S /MPCI-L201 / MPCI-L210-00S / MPCI-L210-60S /MPCI-L210-63S / MPCI-L220-62S / LARA-R203 /LARA-R204 / LARA-R220 - 2 (CS/PS mode 2 of operation;"data centric")•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - The command setting is stored in the personal
profile.
0 (profile 0 selected)
No alarms are stored•••+CEVDP+CGDCONT

UE's voice domain preference •E-UTRAN•PDP context definition•••

1 (CS service selected)

•

•

•

UBX-13002752 - R67

Select service for MO SMS
messages

TOBY-L2 / LARA-R202 / LARA-R211 / LARA-R280 / TOBY-R2- 3 (IMS PS voice preferred, CS voice as secondary)
LARA-R203 - 4 (IMS PS voice only)
TOBY-L4106 / TOBY-L4206 / TOBY-L4906 / TOBY-L2 /MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 - all contexts are undefined
TOBY-L4006 - for <cid>= 1: "IPV4V6" (PDP type),"nxtgenphone" (APN), "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0" (PDP address), 0 (PDP data compression off), 0 (PDP
header compression off)
LARA-R202/
LARA-R203/
TOBY-R200-02B/
TOBY-R200-82B / TOBY-R202 - for <cid>= 1: "IPV4V6" (PDP
type), "nxtgenphone" (APN), "0.0.0.0 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0" (PDP address), 0 (PDP data compression off), 0(PDP header compression off)
LARA-R211 / LARA-R220 / LARA-R280 / TOBY-R200-42B for <cid>= 1: "IPV4V6" (PDP type), "" (blank APN), "0.0.0.0
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0" (PDP address), 0 (PDP datacompression off), 0 (PDP header compression off)
SARA-G3 / LEON-G1 - the context's setting is not
permanently stored; the PDP contexts are permanently
stored when they are defined or deleted
SARA-G4 - the context's setting is not permanently stored•+CGSMSTOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G3 / LEON-G1 - 0 (mute disabled)
SARA-G4 - The command setting is not stored in NVM

B Appendix: AT Commands List

Page 964 of 1001

u-blox cellular modules - AT commands manual

AT command

Description

Factory-programmed value / Comment• TOBY-L4 / TOBY-L201 / MPCI-L201 - The command setting
is not stored in NVM+CISRVCCIMS single radio voice callcontinuity

•
•

+CLIR

Calling line identification
restriction

•
•

+CLVL

Loudspeaker volume level+CMMIVTUE's Mobility Management
IMS Voice Termination
Network emergency bearer
services support

+CNEM
+CPMS

Preferred message storage

LARA-R202-82B / TOBY-R200-42B / TOBY-R200-82B - 0(SRVCC not supported)
LARA-R202-02B / LARA-R211 / TOBY-R200-02B /TOBY-R202 - 1 (SRVCC supported)
0 (presentation indicator used according to the subscriptionof the CLIR service)
SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - The command setting is not persistent••

TOBY-L2 - 30 (loudspeaker volume level)
TOBY-L4 / LARA-R202 / LARA-R203 / LARA-R211 /LARA-R280 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G3 / LEON-G1 - 80 (loudspeaker volume level)• SARA-G4 - The command setting is not stored in NVM
2 (Mobility Management for IMS Voice Termination enabled)•

TOBY-L4 / LARA-R2 / TOBY-R2 - The setting is not stored in
NVM•

TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S /TOBY-L210-02S / TOBY-L210-03A / TOBY-L210-03S /TOBY-L210-60S / TOBY-L210-62S / TOBY-L210-65S /TOBY-L220/
TOBY-L280/
MPCI-L200-02S/
MPCI-L200-03S / MPCI-L210-02S / MPCI-L210-03S /MPCI-L220 / MPCI-L280 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G340 / SARA-G350 / LEON-G1 - <mem1>, <mem2>and <mem3> are set to "MT"="ME"+"SM" with "ME"preferred
TOBY-L200-00S / TOBY-L201 / TOBY-L210-00S /TOBY-L210-60S / MPCI-L200-00S / MPCI-L201 /MPCI-L210-00S / MPCI-L210-60S / MPCI-L210-63S /SARA-G300 / SARA-G310 - <mem1>, <mem2> and <mem3>
are set to "SM"LARA-R2 / TOBY-R2 - <mem1>, <mem2> and <mem3> areset to "ME"TOBY-L4 - <mem1>, <mem2> and <mem3> are set to "SM".
The command setting is not stored in NVM
SARA-G4 - The command setting is stored in the personal
profile

•

•
•
•
+CRSL

Ringer sound level+CSCA

Service center address
setting•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - The command setting is not stored in NVM+CSCB

Accepted cell broadcast•
message types configuration

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - The command setting is not stored in NVM+CSCS

Select character set
configuration

+CSGT
+CSMS

Set greeting text
Message service
configuration+CTZR

Time zone reporting••

UBX-13002752 - R67

TOBY-L4 / TOBY-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - 4 (ringer soundlevel)SARA-G4 - The command setting is not stored in NVM•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G3 / LEON-G1 - The
command setting is not stored in the NVM• SARA-G4 - "GSM" (GSM default alphabet)
Greeting text is empty•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - The command setting is not stored in NVM•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - The command setting is not stored in NVM

B Appendix: AT Commands List

Page 965 of 1001

u-blox cellular modules - AT commands manual

AT command
+CTZU

+IPR

+UBIP
+UBIPAPN+UBMCONF+UCD+UCGATT+UCGCLASS+UCGDFLT+UCLASS

+UCSD
+UCTS
+UDAMCFG+UDCONF=9+UDCONF=12+UDCONF=13

UBX-13002752 - R67

Description
Factory-programmed value / Comment
Automatic time zone update • TOBY-L4/
TOBY-L201-02S/
TOBY-L210-62S/
TOBY-L210-65S / MPCI-L201-02S / LARA-R2 / TOBY-R2 - 1(automatic time zone via NITZ enabled)• TOBY-L200 / TOBY-L201-01S / TOBY-L210-00S /TOBY-L210-02S / TOBY-L210-03A / TOBY-L210-03S /TOBY-L210-60S / TOBY-L220 / TOBY-L280 / MPCI-L200 /MPCI-L201-01S / MPCI-L210 / MPCI-L220 / MPCI-L280 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - 0 (automatic time zone via NITZ disabled)• TOBY-L201-02S / MPCI-L201-02S - In TOBY-L201-02S-00, MPCI-L201-02S-00 the factory-programmed value is 0
(automatic time zone via NITZ disabled)
Baud rate• TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - The
command setting is stored in the personal profile
Bearer Independent Protocol 0 (BIP status indication disabled)
status indication
Default BIP APN"" (Empty string as default APN for BIP service)configuration
Boot mode configuration
1 (router mode), 0 (bridge DHCP server disabled), 4 (CID used by
DHCP server)
Jamming detection• SARA-G340 / SARA-G350 - 0 (jamming detection disabled),
configuration
255 (number of 2G minimum disturbing carriers), 63 (power
level threshold for 2G carriers)• SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G340-00S /SARA-G340-01S / SARA-G350-00S / SARA-G350-00X /SARA-G350-01B / SARA-G350-01S / LEON-G1 - The
command setting is not stored in NVM
Auto attach to PS domain on 1 (enables the auto attach at the module power on)
power on configuration
Changing the startup MS"B" (MS class B)
class
Initial PDP context"IP" (<PDP_type>), "" (<APN>), 0 (<emg_ind>), 0 (<ipcp_req>),
configuration
0 (<pcscf_v6>), 0 (<icmn_sig>), 0 (<dns_v6>), 1 (<ip_via_nas>),0 (<ip_via_dhcp>), 0 (<pcscf_v4>), 1 (<dns_v4>), 0 (<auth_type>), NULL (<auth_user>), NULL (<auth_pass>), "" (<vendor_
specific>)
Device class setting• TOBY-L2 / MPCI-L2 / SARA-U2 / LISA-U2 / LISA-U1 - 12 (GPRS
class 12), 12 (EGPRS class 12), 11 (DTM GPRS class 11), 11 (DTM
EGPRS class 11)• LARA-R202 / LARA-R203 / LARA-R204 / LARA-R220 /LARA-R280 / TOBY-R200-02B / TOBY-R200-82B /TOBY-R202 - 33 (GPRS class 33), 33 (EGPRS class 33), 33(DTM GPRS class 33), 33 (DTM EGPRS class 33)• LARA-R211 / TOBY-R200-42B - 33 (GPRS class 33), 33(EGPRS class 33), 0, 0
• SARA-G3 / LEON-G1 - 10 (GPRS class 10)• SARA-G4 - 12 (GPRS class 12)
Circuit Switched Data
Empty profile
CTS line state in case of
0 (legacy behavior: CTS line is set to ON state if HW flow
disabled HW flow control
control is disabled)
Device Aggresion
1 (DAM enabled)Management configuration
Uplink user data plane
1 (uplink user data plane enabled)
configuration
ESM code 52 handling
1 (ESM code 52 handling enabled)(additional PDP context
activation)
Send message (+CMGS/
0 (final result code issued before the transaction with the+CMSS) set commands
network takes place, UUCMSRES URC disabled)
conclusion configuration

B Appendix: AT Commands List

Page 966 of 1001

u-blox cellular modules - AT commands manual

AT command+UDCONF=20

Description
Steering of Roaming
configuration

Factory-programmed value / Comment+UDCONF=30

Speech codec configuration+UDCONF=32

Connection type groups
enable/disable+UDCONF=33

Waiting call tone
configuration
User defined power reduction •••+UDCONF=40+UDCONF=50+UDCONF=54+UDCONF=55+UDCONF=56+UDCONF=59+UDCONF=60+UDCONF=61+UDCONF=64+UDCONF=66+UDCONF=67+UDCONF=70+UDCONF=71

UBX-13002752 - R67

LARA-R2 / TOBY-R2 / SARA-U201 / SARA-U260 /SARA-U270-00S / SARA-U270-00X / SARA-U270-03A /SARA-U270-03S / SARA-U270-73S / SARA-U280 / LISA-U2 1 (SoR is enabled)
SARA-U270-53S / SARA-G3 / LEON-G1 - 0 (SoR is disabled)• TOBY-L2 - 3647
• LARA-R211 - 63
• TOBY-R200 - 3647
• LARA-R202 / LARA-R203 / LARA-R280 / TOBY-R202 - 3584
• SARA-U2 / LISA-U2 - 3135
• SARA-U270-53S - 1567
• SARA-G3 / LEON-G1 - 31
127 (UDI multimedia, UDI data, RDI, audio 3.1 kHz, all synctransparent, all async transparent, all async non transparent
supported)
4 (waiting call supervisory tone volume)
LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - 2 (MSPR GPRS
and EDGE profile), 2 (MSPR GMSK and EDGE profile)• TOBY-L2 / MPCI-L2 - The command setting is not stored in
NVM
0 (disabled)
8 (ENVELOPE, SMS-PP download will delay a REFRESH
command)
0 (<timer1> and <timer2> disabled)

SIM hot insertion detection
Refresh delay events
management
PLMN search configurationin Out Of Coverage
conditions
Purging of temporary mobile 1 (<purge_identities_enabled> enabled)
identities after SIM refresh
Preferred RAT scope0 (<preferred_rat_conf> disabled)
F-DPCH/enhanced F-DPCH • TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /configuration
LISA-U200-02S / LISA-U200-03S / LISA-U200-04B /LISA-U200-52S / LISA-U200-62S / LISA-U200-83S /LISA-U201 / LISA-U260-02S / LISA-U270-02S - 2 (F-DPCH
and Enhanced F-DPCH enabled)• LISA-U200-01S/
LISA-U230/
LISA-U260-01S/
LISA-U270-01S - 0 (F-DPCH and Enhanced F-DPCH disabled)
Fast Dormancy configuration 2 (all the <FD_mode> values are allowed)
Automatic default gateway 1 (automatic default gateway route handling mechanism
route handling mechanism
enabled)control
IPv6 configuration• TOBY-L200-03A / TOBY-L200-03S / TOBY-L201-02S /TOBY-L210-00S / TOBY-L210-02S / TOBY-L210-03A /TOBY-L210-03S/
TOBY-L220/
TOBY-L280/
MPCI-L201-02S / MPCI-L210 / MPCI-L220 / MPCI-L280 - 1(enabled)• TOBY-L200-00S / TOBY-L200-02S / TOBY-L210-60S /TOBY-L210-62S / TOBY-L210-65S / MPCI-L200 /MPCI-L210-60S / MPCI-L210-63S / SARA-U2 / LISA-U2 - 0(disabled)• TOBY-L201-01S / MPCI-L201-01S - 0 (disabled) in AT&T, 1 in
VZW (enabled)• TOBY-L201-02S / MPCI-L201-02S - On TOBY-L201-02S-00,
MPCI-L201-02S-00, 0 (disabled) in AT&T, 1 in VZW (enabled)• TOBY-L200-03S - On TOBY-L200-03S-00, 0 (disabled)
Router mode configuration 1 (enabled)
LCS positioning capabilities 0 (standalone, MS-Based and MS-Assisted disabled)
configuration
Throughput optimization via 0 (USB interface)
CDC-NCM or Ethernet

B Appendix: AT Commands List

Page 967 of 1001

u-blox cellular modules - AT commands manual

AT command+UDCONF=81

Description
Integrity check on test
networks configuration

Factory-programmed value / Comment•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 - The command setting is not stored in
the NVM+UDCONF=110•

TOBY-L4 - 1 (RAM mode)+UDYNDNS

NVM RAM modemanagement
User setting for proactive
DTMF tone generation
Dynamic DNS+UECALLCFG

eCall configuration mode

+UEXTDCONF

Automatic configuration of
the Maxim MAX9860 audio
codec
Restore factory
configuration
Fast dormancy activation• TOBY-L4 - 0 (analog audio path), 0 (headset profile)0 (disabled),"00000000101E3F04000006330050000000
8A"(MAX9860 registers configuration)+UDTMF+UFACTORY+UFDAC

1 (proactive DTMF tone generation available)
0 (Client disabled), 0 (TZO.com as dynamic DNS service
provider), "" (Domain name empty), "" (Username empty),"" (Password empty)

0 (no FS factory restore), 0 (no NVM factory restore)•

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U200 / LISA-U201 / LISA-U260 / LISA-U270-02S - 3(automatic SCRI transmission request deactivated, 5 (FDDelay Timer=5 s), 5 (FD Inhibit Timer=5 s)• LISA-U270-62S / LISA-U270-63S / LISA-U270-68S - 2(automatic SCRI transmission request activated), 7 (FDDelay Timer=7 s), 120 (FD Inhibit Timer=120 s)"http://alp.u-blox.com/current_14d.alp" (AssistNow Offline
URL file),0, 1 (One minute of timeout after a fail download), 3 (3attempts in case of failed download)"eval1-les.services.u-blox.com" (Host name server), 46434(Server port), 1000 (Expected network latency: 1000 ms), 0(AssistNow Online data downloaded at GPS receiver power up)
0 (NMEA $GGA messages disabled)• SARA-G4 - The command setting is not stored in the NVM
0 (NMEA $GLL messages disabled)• SARA-G4 - The command setting is not stored in the NVM
0 (NMEA $GSA messages disabled)• SARA-G4 - The command setting is not stored in the NVM
0 (NMEA $GSV messages disabled)• SARA-G4 - The command setting is not stored in the NVM+UGAOF

AssistNow Offline
configuration+UGAOP

AssistNow Online
configuration+UGGGA

Get GPS fix data

+UGGLLGet geographic position+UGGSA

Get satellite information+UGGSVGet number of GNSS
satellites in view

+UGIND

Assisted GNSS unsolicitedindication•

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 /SARA-G4 / SARA-G3 / LEON-G1 - The command setting is notstored in the NVM+UGPIOCGPIO functionality setting•

TOBY-L4 - RI: 15, GPIO1: 255, GPIO2: 255, GPIO3: 255, GPIO4:
255, GPIO5: 7, GPIO6: 255, GPIO7: 255, GPIO8: 255
TOBY-L2 - DSR: 15, RI: 15, DCD: 15, DTR: 15, GPIO1: 16, GPIO2:
255, GPIO3: 255, GPIO4: 0, I2S_WA: 12, I2S_TXD: 12, I2S_CLK:
12, I2S_RXD: 12, GPIO5: 7, GPIO6: 14
TOBY-L201-02S - GPIO1: 16, GPIO2: 255, GPIO3: 255, GPIO4:
0, I2S_WA: 255, I2S_TXD: 255, I2S_CLK: 255, I2S_RXD: 255,
GPIO5: 7, GPIO6: 255
TOBY-R2 - GPIO1: 255, GPIO2: 3, GPIO3: 4, GPIO4: 0, I2S_WA:
12, I2S_TXD: 12, I2S_CLK: 12, I2S_RXD: 12, GPIO5: 7
LARA-R2 - GPIO1: 255, GPIO2: 3, GPIO3: 4, GPIO4: 0, I2S_WA:
12, I2S_TXD: 12, I2S_CLK: 12, I2S_RXD: 12, GPIO5: 7
SARA-U2 - GPIO1: 255, GPIO2: 3, GPIO3: 4, GPIO4: 5, SIM_
DET: 7, I2S_RXD: 12, I2S_TXD: 12, I2S_CLK: 12, I2S_WA: 12
LISA-U2 - GPIO1: 255, GPIO2: 3, GPIO3: 4, GPIO4: 5, GPIO5: 7,
I2S1_RXD / GPIO6: 12, I2S1_TXD / GPIO7: 12, I2S1_CLK / GPIO8:
12, I2S1_WA / GPIO9: 12, SPI_SCLK / GPIO10: 13, SPI_MOSI /GPIO11: 13, SPI_MISO / GPIO12: 13, SPI_SRDY / GPIO13: 13,
SPI_MRDY / GPIO14: 13

•

•

•
•
•
•

UBX-13002752 - R67

B Appendix: AT Commands List

Page 968 of 1001

u-blox cellular modules - AT commands manual

AT command+UGPRF+UGRMC+UGSRV+UGVTG+UGZDA+UHSDUPA+UI2S+UICMGSMODE+UIFCONF

UBX-13002752 - R67

Description

Factory-programmed value / Comment• LISA-U200-00S - GPIO1: 255, GPIO2: 255, GPIO3: 255, GPIO4:
255, GPIO5: 7, I2S1_RXD / GPIO6: 255, I2S1_TXD / GPIO7: 255,
I2S1_CLK / GPIO8: 255, I2S1_WA / GPIO9: 255• LISA-U1 - GPIO1: 255, GPIO2: 3, GPIO3: 4, GPIO4: 5, GPIO5: 7• SARA-G340 / SARA-G350 - GPIO1: 255, GPIO2: 3, GPIO3: 4,
GPIO4: 5• SARA-G450-01C - GPIO1: 255, GPIO2: 3, GPIO3: 255, GPIO4:255• SARA-G450-00C - GPIO1: 255, GPIO2: 255, GPIO3: 255,
GPIO4: 255• LEON-G1 - HS_DET: 8, GPIO1: 255, GPIO2: 3, GPIO3: 4, GPIO4:
5
GNSS profile configuration 0 (No data flow on multiplexer, file and IP address), 0 (IP port
not defined), "" (Server address string not defined)• SARA-G4 - The command setting is not stored in the NVM
Get recommended minimum 0 (NMEA $RMC messages disabled)
GNSS data• SARA-G4 - The command setting is not stored in the NVM
Aiding server configuration "cell-live1.services.u-blox.com" (primary MGA server), "celllive2.services.u-blox.com" (secondary MGA server), 14 (Numberof days for validation of Offline data), 4 (Number of weeks
for validation of Offline data), 1 (Resolution of offline data
for MGA), 65 (Desired GNSS for the (offline) aiding: GPS andGLONASS), 0 (AssistNow Online data are downloaded at GNSS
receiver power up), 15 (all the desired data types for the (online)
aiding are set)Get course over ground and 0 (NMEA $VTG messages disabled)
ground speed• SARA-G4 - The command setting is not stored in the NVM
Get GPS time and date0 (NMEA $ZDA messages disabled)• SARA-G4 - The command setting is not stored in the NVM
HSDPA/HSUPA mode
• LARA-R202 / LARA-R280 / TOBY-R2 / SARA-U2 / LISA-U2 /configuration
LISA-U1 - 1 (HSDPA on), 8 (category 8), 1 (HSUPA on), 6(category 6)• TOBY-L200 / TOBY-L201 / MPCI-L200 / MPCI-L201 - 1(HSDPA on), 14 (category 14), 1 (HSUPA on), 6 (category 6)• TOBY-L4 / TOBY-L210 / TOBY-L220 / TOBY-L280 /MPCI-L210 / MPCI-L220 / MPCI-L280 - 1 (HSDPA on), 24(category 24), 1 (HSUPA on), 6 (category 6)
I2S digital interface mode
• TOBY-L4 - 0 (PCM mode 0), 0 (I2S is connected to I2S_A
connection point), 0 (CLK and WA active in dynamic mode),
3 (sample rate: 16 kHz), 0 (master mode)• TOBY-L2 - 21 (PCM mode 21), 1 (I2S is connected to I2Sx
connection point), 0 (CLK and WA active in dynamic mode),
3 (sample rate: 16 kHz), 0 (master mode)• LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - 1 (PCM mode 1), 1(I2S is connected to I2Sx connection point), 0 (CLK and WA
active in dynamic mode), 3 (sample rate: 16 kHz), 0 (mastermode)• LISA-U2 I2S1 settings - 1 (PCM mode 1), 3 (I2S1 is connected
to I2Sx connection point), 0 (CLK and WA active in dynamicmode), 3 (sample rate: 16 kHz), 0 (master mode)• LISA-U120 / LISA-U130 - 0 (PCM mode 0), 1 (I2S is connected
to I2Sx connection point), 0 (CLK and WA active in dynamicmode), 0 (sample rate: 8 kHz), 0 (master mode)• SARA-G3 - 1 (PCM mode 1), 1 (I2S is connected to I2Sx
connection point), 0 (CLK and WA active in dynamic mode)• LEON-G1 - 4 (normal mode 4),2 (I2S is connected to I2Sy
connection point), 1 (CLK and WA active in continuous mode)
MO SMS mode configuration 2 (3GPP2 mode)
Interface configuration• TOBY-L4
o usb0: 0 (NCM interface type), 0 (interface number),
1 (interface enabled), 192.168.2.16 (interface IPv4
address), 255.255.255.0 (interface IPv4 network mask), 1

B Appendix: AT Commands List

Page 969 of 1001

u-blox cellular modules - AT commands manual

AT command

Description

Factory-programmed value / Comment(interface IPv4 DHCP server status enabled), 192.168.2.10
0 (first IPv4 address of the interface DHCP server range),
192.168.2.150 (last IPv4 address of the interface DHCP
server range), 50950 (TCP control port number), 50951(TCP data port number)o eth0: 1 (ETH interface type), 0 (interface number),
1 (interface enabled), 192.168.90.60 (interface IPv4
address), 255.255.255.0 (interface IPv4 network mask), 1(interface IPv4 DHCP server status enabled), 192.168.90.100 (first IPv4 address of the interface DHCP server
range), 192.168.90.150 (last IPv4 address of the interface
DHCP server range), 50960 (TCP control port number),
50961 (TCP data port number)+UIMSCFG

IMS client configuration

•
•

•

•
•

•
•

•
•
•
•
•
•

•

•
+UIMSCONFIMS configuration setting

•
•
•
•
•
•

UBX-13002752 - R67

9: 3GPP_CONFERENCE_URIo LARA-R211 - <data>= ""50: AUTOLOGIN_MODEo LARA-R202 / LARA-R203 / LARA-R204 / LARA-R211 /TOBY-R200-02B / TOBY-R202 - <data>= 1 (AUTOLOGIN_
ALWAYS)o LARA-R204 - <data>= 2 (AUTOLOGIN_HOME_
NETWORK) (on LARA-R204-02B-00 is <data>= 1(AUTOLOGIN_ALWAYS))o TOBY-R200-42B - <data>=3 (AUTOLOGIN_LTE_EPS_
ONLY)
51: APN_NAME
o LARA-R204 - "IMS". On LARA-R204-02B-00 / LARA-R20
4-02B-01 the factory-programmed value is "VZWIMS".
o LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2 - "ims".
53: PREFFERED_PDPTYPE (<data>= 2)
162: IMSI_in_Contact_headero LARA-R202 / LARA-R203 - 1 (IMSI present in SIP"contact" header)164: aSRVCC_configurationo LARA-R202 - 1 (aSRVCC call enabled)
200: XCAP_APN
o LARA-R204 - "NONE".
o LARA-R211 - "ims".
o LARA-R202 / LARA-R203 / TOBY-R2 - "nxtgenphone".
201: XCAP_ROOT_URI (<data>= empty string)
202: XCAP_AUTH_USER_NAME (<data>= empty string)203: XCAP_AUTH_PASSWORD (<data>= empty string)
204: XCAP_TRANSPORT_TYPE (<data>= 0 TRANSPORT_
HTTP)
205: XCAP_Bearer_Deactivation_Timer (<data>= 3)
253: SIP_URI_FORMATo LARA-R204 - 2.
o LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2 - 1.
264: VoPS_registrationo LARA-R204 - 0.
o LARA-R202 / LARA-R203 / LARA-R211 / TOBY-R2 - 1.
269: VoLTE_conference (<data>= 1)"KEY_IMS_PDP_APN": "IMS" (IMS Access Point Name)"KEY_IMS_PDP_CID": 0 (PDP context identifier)"KEY_IMS_PDP_TYPE": "IPV4V6" (IMS PDP type)"KEY_AUTH_TYPE_AKA": "true" (AKAv1 MD5 Digest
Authentication enabled)"KEY_AUTH_TYPE_AKAV2": "false" (AKAv2 MD5 Digest
Authentication disabled)"KEY_AUTH_TYPE_MD5":"false"(MD5
DigestAuthentication disabled)

B Appendix: AT Commands List

Page 970 of 1001

u-blox cellular modules - AT commands manual

AT command

UBX-13002752 - R67

Description

Factory-programmed value / Comment• "KEY_SEC_AGREE": "true" (Security Agreement and IPsec
enabled)• "KEY_XDM_URL": "" (XDM/XCAP Server Root URL empty)• "KEY_PASSWORD": "" (password for IMS MD5 Digest
Authentication and XCAP Authentication empty)• "KEY_HOME_NETWORK_DOMAIN": "" (Home Domain/Realm
empty string)• "KEY_PRIVATE_IDENTITY": "" (private User ID for IMS
Registration and XDM Authentication (IMPI) empty)• "KEY_PUBLIC_IDENTITY": "" (public User ID empty)• "KEY_CONFIG_SOFT_SIM": "false" (Software SIM featuredisabled)• "KEY_CONFIG_SOFT_SIM_K": "" (Software SIM secret K
empty)• "KEY_CONFIG_SOFT_SIM_OP": "" (Software SIM secret OP
empty string)• "KEY_PCSCF_SERVER_ADDRESS": "" (P-CSCF IP Address/
Domain empty)• "KEY_DNS_SERVER": "" (DNS IP address empty)• "KEY_SIP_TIMER_T1": Timer_T1 set to 2000 if the <MNO>
parameter of the +UMNOCONF command is set to 0
(regulatory MNO), 3000 if the <MNO> parameter is set to 3
(Verizon).
• "KEY_SIP_TIMER_T2": 16000 (Timer_T2)• "KEY_SIP_TIMER_T4": 17000 (Timer_T4)• "KEY_SIP_TIMER_TF": 64000 (Timer_TF)• "KEY_MTU_SIZE": 1500 (Maximum Transmission Unit
(MTU))• "KEY_IMS_CLIENT_PORT": 5060 (port 5060 used by theUE's SIP application)• "KEY_REG_EXPIRES": 600000 (IMS registration expiration
time set to 600000)• "KEY_MAX_REG_EXPIRES":
600000(maximumIMS
registration expiration time set to 600000)• "KEY_RETRY_BASE_TIME": 30 (Retry Base Time set to 30)• "KEY_RETRY_MAX_TIME": 1800 (Retry Max Time set to 180
0)• "KEY_REG_BARRED_USER_ID": "true" (Use Barred User ID in
Registration and Deregistration feature disabled)• "KEY_EXPLICIT_UNSUB_REG_EVENT":"false" (unsubscription of the Registration Event Package
during deregistration disabled)• "KEY_PCSCF_BACKOFF_PREFERENCE": "LIST" (Backoff on
P-CSCF change due to server failure set to "LIST")• "KEY_SMSC_NUMBER": "" (SMSC phone number empty)• "KEY_SMSC_URI": "" (SMSC URI empty)• "KEY_MO_SMS_FORMAT": "3gpp" (SMS format set to"3gpp")• "KEY_MO_SMS_ENCODING": "gsm7" (SMS encoding to be
used for Mobile Originated SMS set to "gsm7")• "KEY_QOS_PREFERENCE": "AUTO" (QoS precondition
during SIP call set-up set to "AUTO")• "KEY_PDP_BEARER_MODE": "AUTO" (QoS Allocation Modeset to "AUTO")• "KEY_DOMAIN_PREFERENCE":"PS_PREF"(DomainPreference for the IMS Service Continuity feature set to "PS_PREF")• "KEY_SMS_PREFERENCE": "IMS_PREF" (preferred service
used for MO SMS: "IMS_PREF")• "KEY_IMS_SUPPORT": "true" (IMS support and registration
enabled)B Appendix: AT Commands List

Page 971 of 1001

u-blox cellular modules - AT commands manual

AT command

Description+UIPCHGN+UIPCONF

IP change notification
Configure the Ethernet over •USB IP network+UIPTABLES

IP tables configuration+UIP6TABLES+UISS

IP tables configuration
SS domain configuration•

LARA-R211 - 1 (CSFB)+UJAD

Smart jamming detection•

TOBY-L4 - The setting is not stored in NVM+ULGASP

Last gasp configuration•+ULOCCELL

Configure cellular location
sensor (CellLocate®)
Configure GNSS sensor•+ULOCGNSS

Factory-programmed value / Comment• "KEY_IMS_MWI_SUPPORT": "true" (MWI Event Package
Support for IMS enabled)• "KEY_IMS_SIGCOMP_SUPPORT":"false"(SignalCompression Support for IMS Signaling feature disabled)• "KEY_IMS_RAT": "lteonly" (IMS will try to register on LTE RAT
only)• "KEY_IMS_SMS_SEND_OK_WRITE_UICC": "false" (SMSes
correctly sent not stored)• "KEY_IMS_SMS_SEND_NOK_WRITE_UICC": "false" (SMSes
not sent due to network errors not stored)
0 (IP change notification disabled)
TOBY-L4 - <ipv4_address>: "192.168.2.16", <subnet_mask>:"255.255.255.0", <dhcp_ipv4_start>: "192.168.2.100", <dhcp_
ipv4_end>: "192.168.2.150", <dhcp_status>: 1• TOBY-L2 / MPCI-L2 - <ipv4_address>: "192.168.1.1", <subnet_mask>: "255.255.255.0", <dhcp_ipv4_start>: "192.168.1.100",<dhcp_ipv4_end>: "192.168.1.100"
IPTABLES empty• TOBY-L4 - The command setting is not stored in the NVM
IP6TABLES empty

SARA-U2 / LISA-U2 / SARA-G4
o <GPIO_mode>: 0 (disabled)o <text>: "Last Gasp"o <msg_format>: 0 (text)o <tel_number>: "" (empty)o <profile_id>: 0o <IP_protocol>: 17 (UDP)o <IP_addr:PORT>: "" (empty)o <method>: 0 (send SMS)o <max_pow_red>: 0 (no power reduction)o <urc_enable>: 0 (no URC)
0 (normal mode enabled)•+ULOCIND+ULTECAT+UMAFE

Localization information
request status unsolicitedindication
LTE category configuration•

Microphone analog anddigital gains•

LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / SARA-G4 /SARA-G3 - The command setting is not stored in the NVM

0 (factory-programmed LTE category configuration applied), 4(LTE category)•UBX-13002752 - R67

15 (Local aiding, AssistNow online, AssistNow offline,
AssistNow autonomous enabled), 0 (power saving disabled),
3 (Minimum number of satellites for navigation), 7(Minimum satellite signal level for navigation), 0 (Disabledinitial Fix must be 3D flag), 0 (Static Hold Mode), 0(SBAS disabled), 0 (Jamming indicator disabled), 0(Antenna settings unknown), 0 (Broadband jamming
detection threshold: 0 dB), 0 (Continuous wave jamming
detection threshold: 0 dB), 1 (GPS), 0, 0
LISA-U200-01S / LISA-U200-02S / LISA-U200-03S /LISA-U200-52S / LISA-U200-62S / LISA-U200-83S /LISA-U201-03A / LISA-U201-03S / LISA-U201-83S /LISA-U230 / LISA-U260 / LISA-U270 / LISA-U1 / SARA-G300 /SARA-G310 / SARA-G340-00S / SARA-G350-00S /SARA-G350-00X / LEON-G1 - 0 (no GPS)TOBY-L4006/
TOBY-L4106/
TOBY-L4206/
TOBY-L4906-01A / TOBY-L4906-51A - <analog_gain>: 4(corresponds to 0 dB gain), <adc_gain>: 2 (corresponds to 0
dB gain)
TOBY-L4906-50A - <analog_gain>: 0 (corresponds to 0 dBgain), <adc_gain>: 2 (corresponds to 0 dB gain)

B Appendix: AT Commands List

Page 972 of 1001

u-blox cellular modules - AT commands manual

AT command+UMCLK

Description
Master clock control

Factory-programmed value / Comment••+UMNOCONF

MNO configuration

•
•
•
•
•

+UMNOPLMN

PLMN list extensions•

0 CODEC_CLK mode setting (<mclk_mode>): clock out pin
from LISA module (input for audio codec) is set as three statewith pull down resistor.
0 Setting of dynamic of the application mode (<enabling_mode>): <mclk_mode> setting is applied to CODEC_CLK pin
only when audio path is active. After audio path is disabled(i.e. a call is hang up) CODEC_CLK is disabled too
TOBY-L201 / MPCI-L201 - 2 (AT&T configuration), 7(automatic power cycle)
TOBY-L280 / MPCI-L280 - 4 (Telstra configuration), 1(automatic power cycle)
LARA-R202/
LARA-R203/
TOBY-R200-02B/
TOBY-R200-82B / TOBY-R202 - 2 (AT&T configuration)
TOBY-R200-42B - 9 (Global Data Only)
LARA-R204 - 3 (Verizon configuration), 7 (automatic power
cycle)••

2,"310.030,310.150,310.170,310.280,310.380,310.410,310.560" (for AT&T)
3,"310.590,310.890,311.480" (for Verizon)
4,"505.11,505.71,505.72,505.01,530.04" (for Telstra)
TOBY-L4 - 20 (NTT DoCoMo)+UMNOPROF

MNO profile configuration•+UMSEL

Microphone selection+UNFM

Network friendly mode
activation
Network friendly mode
configuration• <mic_id>: 1 (corresponds to AMIC1)
0 (Network friendly mode deactivated), 0 (+UUNFM URC
disabled)+UNFMCONF+UNVMMCC+UNVMPLMN+UOMADMREPMCC update table
PLMN info list
OMA-DM repository access+UPSVPower saving control

UBX-13002752 - R67•

Back-off timer configuration parameter set(+UNFMCONF=
0)o 60 (Back-off timer base: 60 s)
o 2 (Multiplier factor of the geometrical sequence)o 7680 (back-off timer's maximum duration: 7680 s)• Basic parameter set(+UNFMCONF=1)
o 10 (maximum number of CS registration attempts per
defined time interval)o 1 (time interval in hours associated to CS registration
attempts: 1 h)o 10 (maximum number of PS registration attempts per
defined time interval: 10)
o 1 (time interval in hours associated to PS registration
attempts: 1 h)o 10 (maximum number of PDP context activation
attempts per defined time interval: 10)
o 1 (time interval in hours associated to PDP context
activation attempts: 1 h)
Empty table
Empty table
The contents of the leaf (terminal) node of the DM tree for thefollowing ODIS nodes is as follows:• ./DevDetail/Ext/HostMan: "HMAN1"• ./DevDetail/Ext/HostMod: "HMOD1"• ./DevDetail/Ext/HostSwV: "HSW1"• ./DevDetail/Ext/HostID: "HUID1"• TOBY-R2 / SARA-U201-03A / SARA-U201-03B /SARA-U201-03X / SARA-U201-63B : the default value forthe above nodes is an empty string; furthermore, the"HostPlasmaID" node name is used in place of "HostID"•

TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 /SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - The command setting is stored in the personal
profileB Appendix: AT Commands List

Page 973 of 1001

u-blox cellular modules - AT commands manual

AT command+UPSD

Description
Packet switched data

Factory-programmed value / Comment+URAT

Selection of Radio AccessTechnology•+USAFE

Speaker analog and digital
gains+USIMSTAT(U)SIM initialization status
reporting
Serial interfaces
configuration• <earpiece_gain>: 4 (corresponds to 0 dB gain)• <dac_coarse_gain>: 4 (corresponds to 0 dB gain)• <dac_fine_gain>: 3 (corresponds to 0 dB gain)
0 (URC +UUSIMSTAT disabled)+URING+URNG+URPM+URPMCONF+URXDIV+USIO•

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 - The
command setting is not stored in the NVM

TOBY-L4 - 4 (GSM / UMTS / LTE RAT), 3 (LTE as preferred
RAT)• TOBY-L200 / TOBY-L210 / TOBY-L280 / MPCI-L200 /MPCI-L210 / MPCI-L280 - 4 (GSM / UMTS / LTE RAT), 3 (LTEas preferred RAT)• TOBY-L201 / TOBY-L220 / MPCI-L201 / MPCI-L220 - 6(UMTS / LTE RAT), 3 (LTE as preferred RAT)• TOBY-R200 - 4 (GSM / UMTS / LTE RAT), 3 (LTE as preferred
RAT), 2 (UTRAN as second preferred RAT)• LARA-R202 / LARA-R280 / TOBY-R202 - 6 (UMTS / LTERAT), 3 (LTE as preferred RAT)• LARA-R203 / LARA-R204 / LARA-R220 - 3 (LTE RAT)• LARA-R211 - 5 (GSM / LTE RAT), 3 (LTE as preferred RAT)• SARA-U2 / LISA-U2 / LISA-U1 - 1 (GSM/UMTS dual mode
RAT), 2 (UMTS as preferred RAT)• SARA-U270-53S / SARA-U270-73S / SARA-U280 - 2 (UMTS
RAT), 2 (UMTS as preferred RAT)RING line handling
0 (feature disabled (RING line is only asserted on incoming calland incoming SMS))
Ringing tone selection
0 (melody 0)
RPM activation
0 (Radio Policy Manager deactivated)
Radio Policy Manager (RPM) <PLMN> empty, i.e. no PLMNs available
configuration
RX diversity• 1 (3G Rx diversity disabled), 3 (DARP Phase 2 always on)

•

•

•

LARA-R211 / SARA-U201-04A / SARA-U201-04B /SARA-U201-04X - 0 (AT command on UART and USB,
diagnostic log on USB, no AUX UART)
SARA-G340-02S / SARA-G340-02X / SARA-G350-02A /SARA-G350-02S / SARA-G350-02X - 1 (AT command on
UART, diagnostic log on AUX UART, I2S can be used for DAI)SARA-G4 - The command setting is stored in the personal
profile+USOAO

Socket Always On

•
•
•
•
•
•
•

0,0 (Feature disable)
1,0 (PSD profile: 0)2,0 (Client Mode)
3,"" (Empty)
4,2000 (Default port: 2000)
5,6 (TCP socket)
20+i,"" (Empty)+USPM

Audio path mode setting••

TOBY-L4 - 0 (analog audio path), 0 (handset profile)
TOBY-L2 - 1 (speech audio output path: Downlink path 1 via
I2S), 1 (speech audio input path: Uplink path 1 via I2S), 0(alert sound on main downlink path (downlink path 1 via I2S)),
0 (Headset indication: not considered), 2 (VMIC is always
switched Off)LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 - 1 (speech audio
output path: Downlink path 1 via I2S), 1 (speech audio input
path: Uplink path 1 via I2S), 0 (alert sound on main downlink
path (Downlink path 1 via I2S)), 0 (headset indication: notconsidered), 2 (VMIC is always switched Off)LISA-U1 - 1 (speech audio output path: Headset microphone),
1 (speech audio input path: Mono headset earpiece), 0 (alert
sound on main downlink path (mono headset earpiece)),••

UBX-13002752 - R67

B Appendix: AT Commands List

Page 974 of 1001

u-blox cellular modules - AT commands manual

AT command

Description+UTEST+UUSBCONF

End user test
USB profiles configuration+UWAPCFG

Wireless access point
physical layer configuration+UWAPIPCFG

Wireless access point
network layer configuration+UWCFG

Wi-Fi module power mode

+UWREGBLOCK

Wi-Fi regulatory domains
block configuration
Wireless station physicallayer configuration
Wireless station network
layer configuration

Factory-programmed value / Comment
0 (Headset indication: not considered), 2 (VMIC is always
switched Off)
• SARA-G340 / SARA-G350 - 0 (speech audio output path:
Handset microphone), 0 (speech audio input path: Normal
earpiece), 0 (alert sound on main downlink path (monoheadset earpiece)), 0 (headset indication: not considered), 0(VMIC is switched On /Off)• LEON-G1 - 0 (speech audio output path: Handset
microphone), 0 (speech audio input path: Normal earpiece),1 (alert sound on Loudspeaker), 1 (headset indication:
considered), 0 (VMIC is switched On /Off)
Antenna dynamic tuner control: 0 (disabled)••+UWSTACFG+UWSTAIPCFG+UWWEBUI+UWWEBUIFTP+VZWAPNE+XSIMSWITCH

Web user interface
configuration
Web user interface
customization through FTP
service
Edit Verizon wireless APN
table

TOBY-L2 / MPCI-L2 - 3 (High throughput), "RNDIS" (USB
network function)
SARA-U2 / LISA-U2 - 0 (7 CDC-ACM)•

TOBY-L200-02S / TOBY-L200-03A / TOBY-L200-03S /TOBY-L201-02S"UBXWifi"(ESSID),2(WPA2
authentication type), "ubx-wifi" (security passphrase), 1 (UScountry code), 0 (automatic channel selection), 3 (802.11b/g/
n IEEE standard)• TOBY-L210-02S / TOBY-L210-03A / TOBY-L210-03S /TOBY-L210-62S / TOBY-L210-65S / TOBY-L280 "UBXWifi" (ESSID), 2 (WPA2 authentication type), "ubxwifi" (security passphrase), 0 (EU country code), 0(automatic channel selection), 3 (802.11b/g/n IEEE standard)• TOBY-L220 - "UBXWifi" (ESSID), 2 (WPA2 authenticationtype), "ubx-wifi" (security passphrase), 2 (JP country code), 0(automatic channel selection), 3 (802.11b/g/n IEEE standard)"192.168.2.1" (access point IP address), "255.255.255.0" (accesspoint netmask), "192.168.2.100" (start IP address of the DHCP
range), "192.168.2.200" (top IP address of the DHCP range)
0 (Wi-Fi module is turned off), 0 (connection manager
disabled), 0 (conflict reporting URC disabled)
60 (Timer duration when the module enters in not registeredstate: 60 minutes)
0 (station mode disabled)
1 (connectivity within an external access point enabled), 1(internal DHCP client to associate to the external access point
enabled)0 (web user interface disabled)
0 (access to the Web user interface through FTP service is notallowed)Verizon wireless APN table (APN list entry, APN class, Network
identifier, APN type, APN bearer, APN status, APN inactivity
timer)• 1,1,"IMS","ipv4v6","LTE","Enabled",0• 2,2,"VZWADMIN","ipv4v6","LTE","Enabled",0• 3,3,"VZWINTERNET","ipv4v6","LTE","Enabled",0• 4,4,"VZWAPP","ipv4v6","LTE","Enabled",0• 6,6,"ENTERPRISE","ipv4v6","LTE","Enabled",0• 7,7,"THINGSPACE","ipv4v6","LTE","Enabled",0Class 1 APN in table above may differ from the one here
specified. Refer to +VZWAPNE for details.

SIM slot for switch operation •TOBY-L4 - 0 (i.e. by default sim slot 1 is active)

B.3 Saving AT commands configuration
The following procedure can be used to store the AT commands configuration for the AT commands listed inAppendix B.1:

UBX-13002752 - R67

B Appendix: AT Commands List

Page 975 of 1001

u-blox cellular modules - AT commands manual••

TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1- Write the run-time configuration of the AT commands listed in Appendix B.1 to the RAM profile mirror bymeans of the AT&W command (e.g. AT&W0)
TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 / LEON-G1 Confirm that the boot loading is performed with the desired parameter profile (e.g. profile 0 if the parametersave was performed with AT&W0; use AT&Y0 to select this)The following procedure can be used to store the AT commands configuration for the AT commands listed inAppendix B.2:
• TOBY-L4 / TOBY-L2 / MPCI-L2 / LARA-R2 / TOBY-R2 / SARA-U2 / LISA-U2 / LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - Since the permanently saving of NVM content is achieved by a low priority process, the timedepends on all the other activities as network procedures, call management, and so on. To be sure tosave suddenly the run-time configuration of the commands listed in Appendix B.2, it is advisable to use+CPWROFF or +CFUN=15 or +CFUN=16. If the +CPWROFF has been issued the module, perform a rebootof the device

B.4 Estimated command response time
After having sent a command to a u-blox cellular module, the time to obtain a resulting result code depends
on the SIM and the network. It is possible to have an immediate response if the command does not interact
with either the network or the SIM.
The following table reports the maximum time to get the result code for the AT commands. The commands
are grouped by categories.
Category

Estimated maximum time to get Commands
response
Power off
< 40 s+CPWROFFSet module functionality Up to 3 min+CFUNCall control< 20 sA, H, +CHUP, +CSVM
Dial
Up to 3 min
D, D>, DL
DTMF and tone
Up to 7 min+VTS
generation
Supplementary services < 20 s
+CAEMLPP, +CHLD, +CHUP, +CNAP, +COLP, +COLR
Supplementary services Up to 3 min+CCFC, +CCWA, +CLIP, +CLIR, +CTFR, +CUSD
Data connection
Up to 3 min+CGATT, +CGDATA, +UCGOPS, +UCSDA, +UPSDA
commands
Network commands• TOBY-L4 / TOBY-L2 / MPCI-L2 / +COPS
LARA-R2 / TOBY-R2 / SARA-U2 /LISA-U2 / LISA-U1 / SARA-G4 /SARA-G3 / LEON-G1 - Up to 3 min
Network commands< 10 s+URAT
Operator nameUp to 1 s
+UDOPN
Cell information<5s+UCELLINFOEONS names< 40 s+UEONS
Security
Up to 3 min+CLCK, +CPWD
Phonebook commands < 35 s
+CPBF, +CPBR, +CPBS, +CPBWDelete all SMSes< 55 s+CMGD
SMS acknowledgement < 150 s
+CNMA
to MT
SMS
Up to 3 min (<1 s for prompt ">")+CPMS, +CMGL, +CMSS, +CMGS, +UCMGS,+UCMGS3GPP2, +UCMGLSIM management< 10 s+CACM, +CAMM, +CAOC, +CMGW, +UCMGW, +CMGR,+UCMGP, +UCMGR, +CNUM, +CPIN, +CPOL, +CPUC,+CR, +CRES, +CRSM, +CSCA, +CSCB, +CSMP
SIM switch< 3 min+XSIMSWITCH
SIM toolkit< 20 s+SATD, +SATE, +SATR, +STKENV, +STKTR,+UCATENV, +UCATTR, +URCATE, +URCATR
PDP context activation < 150 s+CGACTPDP context< 40 s+CGACT
deactivation

UBX-13002752 - R67

B Appendix: AT Commands List

Page 976 of 1001

u-blox cellular modules - AT commands manual

Category
USB disable/enable
selection and status
ECM data connection
Restore configuration
End user test (antenna
dynamic tuner control)
OMA-DM alert
Audio path testing
Audio recording
GPIO commands
Internet suite (socket
connect)
Internet suite (socket
connect with SSL)

Estimated
response< 200 smaximumtime

toget Commands+UDCONF=78

Up to 3 min<5s
Up to 1 s

+UCEDATA+UFACTORY+UTEST~400s (depending on network
connectivity)<2s
Up to 10 s
< 10 s< 120 s+UOMADMALERT+UMAAT+URECFILE+UGPIOC, +UGPIOR, +UGPIOW+USOCOTOBY-L2 / MPCI-L2 / LARA-R2 / +USOSECTOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - < 120 s
Internet suite (socket+USOWR• LEON-G1 - < 10 s
write)• TOBY-L2 / MPCI-L2 / LARA-R2 /TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - < 1 sInternet suite (UDP
+USOST• LEON-G1 - < 10 ssocket write)• TOBY-L2 / MPCI-L2 / LARA-R2 /TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - < 1 sInternet suite (socket+USOCL• LEON-G1 - < 10 s
closure)• TOBY-L2 / MPCI-L2 / LARA-R2 /TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - < 1 sInternet suite+USMTPC, +USMTPM, +USODL, +USOLI, +USORD,• LEON-G1 - < 10 s
• TOBY-L2 / MPCI-L2 / LARA-R2 / +USORF
TOBY-R2 / SARA-U2 / LISA-U2 /LISA-U1 / SARA-G4 / SARA-G3 /LEON-G1 - < 1 s
Resolve name/IP number < 120 s (except URC)
+UDNSRN
through DNSGNSS commands< 10 s (except +UGPS for which+UGAOS, +UGGGA, +UGGLL, +UGGSA, +UGGSV,
timeout is according to the performed +UGPS, +UGRMC, +UGTMR, +UGUBX, +UGVTG,
operation)+UGZDA, +ULOC
Time information< 10 s+UTIME
Wi-Fi network scan
< 15 s+UWSCAN
Wi-Fi configuration< 20 s+UWAPCFG, +UWCFG, +UWSTACFG
Last gasp configuration < 10 s
+ULGASPMNO configuration< 3 min+UMNOCONF
Firmware update+UFWUPD•

B.5 Multiple AT command interfaces
u-blox cellular modules support multiple AT command interfaces, that means a certain number of virtual or
physical channels that work as described in Definitions.
Each interface maintains an own run-time AT commands configuration (AT command profile); this means that
the AT command profile is different among the interfaces and therefore the AT commands configuration forthe commands belonging to the profile can be different among the interfaces.
At the module start-up, since there is only a set of the profiles (not one for each interface), all the interfaces are
configured in the same way (AT commands configuration for the commands in the profile is the same for all the

UBX-13002752 - R67

B Appendix: AT Commands List

Page 977 of 1001

u-blox cellular modules - AT commands manualinterfaces). Subsequently, each interface can change its run-time AT profile (stored in RAM). The commands
AT&W, AT&V manage this run-time AT commands configuration for the interface where they are issued.
The USB interface implements multiple AT command interfaces. Unlike what happens for the other physicalinterfaces (e.g. UART, SPI), the AT command interfaces that run on the USB interface only exists as long as the
USB interface connects the module with the DTE. As a result, if the USB connection between the module andthe DTE is interrupted (e.g. by USB cable removal), all the AT command interfaces running on it are destroyed.
This has two main consequences:••

Any data connection (both circuit switched and packet switched) established over an AT commandinterface associated to the USB interface is released.
Whenever the USB connection between the module and the DTE is re-established, the AT commandinterfaces running on it are created, and for each of these interfaces the AT command profile is reloaded
from NVM and applied.
The reload of the AT command profile from the NVM also results in the re-application of the +UPSV
setting, which is a shared "AT interface configuration". This must be kept in mind, since the change could
have impacts on the communication over the UART interface.

As mentioned in Definitions, generally there is not difference in the execution of an AT command among theinterfaces. But, there are some exceptions due to interface restrictions. In particular, the differences relate to
AT commands that configure the DCE-DTE interface.
Table 94 provides the major differences.
AT command&K

UART / AUX UART
(where available)
Effective\Q

Effective+ICF

Effective+IFC

Effective+IPR

Effective+UPSV

Effective

Multiplexer

USB (where available)

SPI (where available)

When it returns OK (the When it returns OK (the When it returns OK (theconfiguration is allowed), configuration is allowed), configuration is allowed),
it is effective
it is not effective (only
it is not effective (onlychange the value in thechange the value in the
AT command profile)
AT command profile)
When it returns OK (the When it returns OK (the When it returns OK (theconfiguration is allowed), configuration is allowed), configuration is allowed),
it is effective
it is not effective (only
it is not effective (onlychange the value in thechange the value in the
AT command profile)
AT command profile)
Returns OK, but it is not Returns OK, but it is not Returns OK, but it is noteffective (only change the effective (only change the effective (only change thevalue in the AT command value in the AT command value in the AT commandprofile)profile)profile)When it returns OK (the When it returns OK (the When it returns OK (theconfiguration is allowed), configuration is allowed), configuration is allowed),
it is effective
it is not effective (only
it is not effective (onlychange the value in thechange the value in the
AT command profile)
AT command profile)
Returns OK, but it is not Returns OK, but it is not Returns OK, but it is noteffective (only change the effective (only change the effective (only change thevalue in the AT command value in the AT command value in the AT commandprofile)profile)profile)Returns OK, but it
Returns OK, but it
Returns OK, but itchanges UART settingchanges UART settingchanges UART setting

Table 94: Interface comparison

UBX-13002752 - R67

B Appendix: AT Commands List

Page 978 of 1001

u-blox cellular modules - AT commands manual

C Appendix: UDP Direct Link workflow
C.1 Data from the IP network to the external port
When a UDP data packet is received from the network, its payload is forwarded through the external port assoon as possible (according to the HW flow control, if any).

Data from IP netw ork

Forw ard it to external port
(according with HW flow control, if any)

Figure 31: Workflow of data from the IP network to the external port

C.2 Data from the external port to the IP network
When some data comes from the external port, there are 2 parameters involved:
1.
2.

The UDP DL packet size (factory-programmed: 1024 bytes; valid range 100-1472)
The UDP DL sending timer delay (factory-programmed: 1000 ms; valid range 100-120000)

Both parameters are specific for each socket and could be modified by the user. These values are not saved
into the NVM and if not specified, the factory-programmed values are used.
There are 3 different cases that may occur while receiving data from the external port in UDP DL mode:
1.
2.

3.

The received data from the external port is equal to the UDP DL packet size: the received data isimmediately sent to the network
The received data from the external port is more than the UDP DL packet size: the amount of data till
UDP DL packet size is immediately sent to the network, the remaining data is saved into an intermediate
buffer.
The received data from the external port is less than UDP DL packet size: the received data is saved into
an intermediate buffer and sent to the network when the UDP DL sending timer expires. The timer isreset (it restarts the countdown) every time new data is received from the external port, this means thatthe data will be sent to the network after N ms (default 1000 ms) since the last received byte.
The data sent from the serial port is not echoed to the sender.
The configuration of UDP DL packet size and UDP DL sending timer are NOT saved in NVM.

The following diagram shows how the events of external data input and sending timer expire are handled.

UBX-13002752 - R67

C Appendix: UDP Direct Link workflow

Page 979 of 1001

u-blox cellular modules - AT commands manual

Event: newdata fromexternal port

Reset sending timer

New data + data
into intermediate
bufferis < thanmax_packet_size?

YES

Put data into
intermediate
buffer andw ait sending
timer expires
or new data

Finish,event
handledNO
Send max_packet_sizeof data to IP netw ork
YES
YES

Remainingdatais >= max
packet size?

Event:
sending
timer expiresNOIs thereanydata?

Is there any data
into the intermediate
buffer?

NO

YES

Send data to IP
netw orkNO
Finish,event
handledRescheduletimer

Figure 32: Workflow of data from the external port to the IP network

UBX-13002752 - R67

C Appendix: UDP Direct Link workflow

Page 980 of 1001

u-blox cellular modules - AT commands manual

D Appendix: Glossary
2G
3G
3GPP
ADC
AIeC
ADN
AMR
AP
APN
ASCII
AT
BL
BSD
CB
CBM
CLI
CLIP
CLIR
COLP
COLR
CM
CPHS
CR
CS
CSD
CSG
CTS
CUG
DA
DARP
DCD
DCE
DCM
DHCP
DNS
DSR
DTE, TE
DTMF
DTR
DUT
EARFCNeCall
EEP
EF
EFCGSTEFHNBNEFPLMNwAcT
eIM
EONS
EPD
ETSI
E-UTRAN/EUTRAN
FDN

2nd Generation
3rd Generation
3rd Generation Partnership Project
Analog to Digital Converter
Automatically Initiated eCall
Abbreviated Dialing Numbers
Adaptive Multi Rate
Access Point
Access Point Name
American Standard Code for Information Interchange
AT Command Interpreter Software Subsystem, or attention
Black List
Berkley Standard Distribution
Cell Broadcast
Cell Broadcast Message
Calling Line Identification
Calling Line Identification Presentation
Calling Line Identification Restriction
Connected Line Identification Presentation
Connected Line Identification Restriction
Connection Management
Common PCN Handset Specification
Carriage Return
Circuit Switch
Circuit-Switched Data
Closed Subscriber Group
Clear To Send
Closed User Group
Destination Address
Downlink Advanced Receiver Performance
Data Carrier Detect
Data Communication Equipment
Data Connection Management
Dynamic Host Configuration Protocol
Domain Name Server
DSC transponder response
Data Terminal Equipment
Dual Tone Multi Frequency
Data Terminal Ready
Device Under Test
E-UTRAN Absolute Radio Frequency Channel Number
Emergency Call
EEPROM Emulation Parameters
Elementary File
Elementary File "Closed Subscriber Group Type"Elementary File "Home Node B Number"
Elementary File "User controlled PLMN Selector with Access Technology"
eCall In-band Modem
Enhanced Operator Name from SIM-files EFOPL and EFPNN
Escape Prompt Delay
European Telecommunications Standards Institute
Evolved UTRAN
Fixed Dialling Number

UBX-13002752 - R67

D Appendix: Glossary

Page 981 of 1001

u-blox cellular modules - AT commands manual

FOAT
FOTA
FS
FTP
FW
FWINSTALL
GAS
GERAN
GPIO
GPRS
GPS
GSM
HDLC
HNB
HPLMN
HTTP
I
I2C
I2S
ICCID
ICMP
ICP
IMEI
IMSI
InBM
IP
IRA
IRC
ISDN
ISP
IVS
L3
LCP
LF
LNS
M2M
MCC
ME
MIeC
MMI
MN
MNC
MNO
MO
MS
MSC
MSD
MSIN
MSISDN
MSPR
MT
MWI
NAA
NAS
NITZ
NVM

UBX-13002752 - R67

Firmware Over AT
Firmware Over The Air
File System
File Transfer Protocol
FirmwareFirmware InstallGrouping information Alpha String
GSM/EDGE Radio Access Network
General Purpose Input Output
General Packet Radio Service
Global Positioning System
Global System for Mobile Communications
High Level Data Link Control
Home Node B
Home PLMN
HyperText Transfer Protocol
Information
Inter-Integrated Circuit
Inter IC Sound or Integrated Interchip Sound
Integrated Circuit Card ID
Internet Control Message Protocol
Inter Processor Communication
International Mobile Equipment Identity
International Mobile Station Identity
In-Band Modem (generic)Internet Protocol
International Reference Alphabet
Intermediate Result CodeIntegrated Services Digital Network
Internet Service Provider
In-Vehicle System (eCall related)
Layer 3
Link Control Protocol
Line Feed
Linux Network Subsystem
Machine-To-Machine
Mobile Country Code
Mobile Equipment
Manually Initiated eCall
Man Machine Interface
Mobile Network Software Subsystem
Mobile Network Code
Mobile Network Operator
Mobile OriginatedMobile Station
Modem Status Command
Minimum Set of Data (eCall related)
Mobile Subscriber Identification Number
Mobile Systems International Subscriber Identity Number
Multi-Slot Power Reduction
Mobile TerminatedMessage Waiting Indication
Network Access Application
Non Access Stratum
Network Identity and Time Zone
Non-Volatile Memory

D Appendix: Glossary

Page 982 of 1001

u-blox cellular modules - AT commands manual

ODIS
OLCM
PAD
P-CID
PCN
PDP
PDU
PIN
PLMN
PPP
PSAP
PSD
PUK
QoS
RAM
RDI
RFU
RNDIS
RI
RTC
RTP
RTS
Rx
SAP
SC
SI
SIP
SIM
SMS
SMSC
SMTP
SoR
SDIO
SES
STA
SSID
TA
TCP
TE
TFT
TP
Tx
TZ
UCS2
UDI
UDP
UI
UICC
UIH
URC
USIM
UTRAN
UUS1
WLAN

UBX-13002752 - R67

OMA-DM IMEI Sync
On Line Commands Mode
Packet Assembler/Disassembler
Physical Cell Id
Personal Communication Network
Packet Data Protocol
Protocol Data Unit
Personal Identification Number
Public Land Mobile Network
Point-to-Point Protocol
Public Safety Answering Point (eCall related)
Packet-Switched Data
Personal Unblocking Key
Quality of Service
Random Access Memory
Restricted Digital Information
Reserved for Future Use
Remote Network Driver Interface Specification
Ring Indicator
Real Time Clock
Real-time Transport Protocol
Request To Send
ReceiverSIM Access Profile
Service Centre
SIM Application Part Software Subsystem
Session Initiation Protocol
Subscriber Identity Module
Short Message Service
Short Message Service Center
Simple Mail Transfer Protocol
Steering of Roaming
Secure Digital Input Output
Speech Enhancement System
stationService Set Identifier
Terminal Adaptor
Transfer Control Protocol
Terminal Equipment
Traffic Flow TemplateTransfer layer Protocol
Transmitter
Time Zone
Universal Character Set
Unrestricted Digital Information
User Datagram Protocol
Unnumbered Information
Universal Integrated Circuit Card
Unnumbered Information with header Check
Unsolicited Result Code
UMTS Subscriber Identity Module
Universal Terrestrial Radio Access Network
User-to-User Signalling Supplementary Service 1
Wireless Local Area Network

D Appendix: Glossary

Page 983 of 1001

u-blox cellular modules - AT commands manual

Related documents
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.

38.
39.

Stevens. TCP/IP Illustrated Volume1 & 2 Addison-Wesley, 1994.
3GPP TS 27.007 - Technical Specification Group Core Network and Terminals; AT command set for User
Equipment (UE)
3GPP TS 22.004 - General on supplementary services
GSM 02.04 - Digital cellular telecommunication system (Phase 2+); Mobile Stations (MS) features
3GPP TS 22.030 - Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Man-Machine Interface (MMI) of the User Equipment (UE)
3GPP TS 22.090 - Unstructured Supplementary Service Data (USSD); Stage 1
3GPP TS 23.038 - Alphabets and language-specific information
3GPP TS 23.040 - Technical realization of Short Message Service (SMS)
3GPP TS 23.041 - Technical realization of Cell Broadcast Service (CBS)
3GPP TS 23.060 - Technical Specification Group Services and System Aspects; General Packet Radio
Service (GPRS); Service description
3GPP TS 24.007 - Mobile radio interface signalling layer 3; General aspects
3GPP TS 24.008 - Mobile radio interface layer 3 specification
3GPP TS 24.011 - Point-to-point (PP) Short Message Service (SMS) support on mobile radio interface
GSM 04.12 - Digital cellular telecommunications system (Phase 2+); Short Message Service Cell
Broadcast (SMSCB) Support on Mobile Radio Interface.
3GPP TS 27.005 - Technical Specification Group Terminals; Use of Data Terminal Equipment Data Circuit terminating Equipment (DTE-DCE) interface for Short Message Services (SMS) and Cell
Broadcast Service (CBS)
3GPP TS 27.060 - Technical Specification Group Core Network; Packet Domain; Mobile Station (MS)supporting Packet Switched Services
3GPP TS 51.011 - Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber
Identity Module - Mobile Equipment (SIM - ME) interface
3GPP TS 31.102 - Characteristics of the Universal Subscriber Identity Module (USIM) application
ITU-T Recommendation V250, 05-99.
ITU-T V.25ter - ITU-T V.25 ter Recommendation: Data Communications over the Telephone Network;
Serial asynchronous automatic Dialling and control.
ITU-T T.32 - ITU-T Recommendation T.32 Asynchronous Facsimile DCE Control - Service Class 2
ISO 639 (1988) Code for the representation of names of languages
ITU-T Recommendation V24, 02-2000. List of definitions for interchange circuits between Data
Terminal Equipment (DTE) and Data Connection Equipment (DCE).
RFC 791 - Internet Protocol - http://www.ietf.org/rfc/rfc791.txt
3GPP TS 05.08 - Radio subsystem link control
3GPP TS 22.087 - User-to-User Signalling (UUS)
3GPP TS 22.022 - Personalisation of Mobile Equipment (ME)
3GPP TS 22.082 - Call Forwarding (CF) supplementary services
3GPP TS 22.083 - Call Waiting (CW) and Call Holding (HOLD)
3GPP TS 22.081 - Line identification Supplementary Services- Stage 1
3GPP TS 23.081 - Line identification supplementary services- Stage 2
3GPP TS 22.086 - Advice of Charge (AoC) Supplementary Services
3GPP TS 22.024 - Description of Charge Advice Information (CAI)
3GPP TS 22.085 - Closed User Group (CUG) Supplementary Services
3GPP TS 22.096 - Name identification supplementary services
3GPP TS 04.18 - Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol
GSM 04.60 - Digital cellular telecommunications system (Phase 2+); General Packet Radio Service(GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium AccessControl (RLC/MAC) protocol
3GPP TS 05.02 - Multiplexing and Multiple Access on the Radio Path
3GPP TS 51.014 - Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile
Equipment (SIM - ME) interface

UBX-13002752 - R67

Related documents

Page 984 of 1001

u-blox cellular modules - AT commands manual

40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.

3GPP TS 27.010 V3.4.0 - Terminal Equipment to User Equipment (TE-UE) multiplexer protocol (Release
1999)
3GPP TS 22.060 - General Packet Radio Service (GPRS); Service description; Stage 1
ETSI TS 102 223 - Smart cards; Card Application Toolkit (CAT)
3GPP TS 25.306 - UE Radio Access capabilities
RFC3267 - Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive
Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs
RFC 792 Internet Control Message Protocol (http://tools.ietf.org/html/rfc0792)
3GPP TS 22.002 - Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)
3GPP TS 22.067 - enhanced Multi Level Precedence and Pre-emption service (eMLPP); Stage 1
AT&T: Device Requirements -- Requirements Document -- Document Number 13340 -- Revision 4.6 -Revision Date 9/2/11
3GPP TS 23.972 - Circuit switched multimedia telephony
3GPP TS 24.615 Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem;
Protocol Specification
3GPP TS 25.101 - User Equipment (UE) radio transmission and reception (FDD)
3GPP TS 45.005 - Radio transmission and reception
Common PCN Handset Specification v4.2
SIM Access Profile - Interoperability Specification - Bluetooth Specification V11r00
Maxim MAX9860 16-Bit Mono Audio Voice Codec datasheet, 19-4349; Rev 1; 9/09. Available from the
Maxim website (http://datasheets.maxim-ic.com/en/ds/MAX9860.pdf)
3GPP TS 23.122 - NAS Functions related to Mobile Station (MS) in idle modeETSI TS 122 101 V8.7.0 (2008-01) Service aspects; Service principles (3GPP TS 22.101 version 8.7.0
Release 8)
BS EN 16062:2015 Intelligent transport systems - ESafety - eCall high level application requirements(HLAP) using GSM/UMTS circuit switched networks, April 2015
3GPP TS 26.267 V12.0.0 (2012-12) eCall Data Transfer; In-band modem solution; General description(Release 12)
3GPP TS 51.010-1 Mobile Station (MS) conformance specification; Part 1: Conformance specification
RFC 959 File Transfer Protocol (http://tools.ietf.org/html/rfc959)
RFC 2428 FTP Extensions for IPv6 and NATs (https://tools.ietf.org/html/rfc2428)
3GPP TS 23.014 Support of Dual Tone Multi-Frequency (DTMF) signalling V11.0.0 (2012-09)
ETSI TS 127 007 V10.3.0 (2011-04) AT command set for User Equipment (UE) (3GPP TS 27.007 version
10.3.0 Release 10)
3GPP TS 51.010-2 Mobile Station (MS) conformance specification; Part 2: Protocol Implementation
Conformance Statement (PICS) proforma specification
3GPP TS 34.121-2 User Equipment (UE) conformance specification; Radio transmission and reception(FDD); Part 2: Implementation Conformance Statement (ICS)PCCA standard - Command set extensions for CDPD modems, Revision 2.0, March, 1998
3GPP TS 24.301 Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3
3GPP TS 44.060 General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS)interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol
3GPP TS 23.221 Architectural requirements
3GPP TS 23.203 Policy and charging control architecture
3GPP TS 31.101 UICC-terminal interface; Physical and logical characteristics
ETSI TS 102 221 V8.2.0 (2009-06) Smart Cards; UICC-Terminal interface; Physical and logicalcharacteristics (Release 8)
RFC 4291 - IP Version 6 Addressing Architecture (http://tools.ietf.org/html/rfc4291)
3GPP TS 25.305 User Equipment (UE) positioning in Universal Terrestrial Radio Access Network(UTRAN); Stage 2
3GPP TS 23.032: Universal Geographical Area Description (GAD)
3GPP TS 25.331 Radio Resource Control (RRC); Protocol specification
3GPP TS 36.101 Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radiotransmission and reception
3GPP TS 24.173 IMS Multimedia telephony communication service and supplementary services; Stage 3

UBX-13002752 - R67

Related documents

Page 985 of 1001

u-blox cellular modules - AT commands manual

80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
99.
100.
101.
102.
103.
104.
105.
106.
107.
108.
109.
110.
111.
112.
113.
114.
115.
116.
117.

3GPP TS 24.341 Support of SMS over IP networks; Stage 3
3GPP TS 24.229 IP multimedia call control protocol based on Session Initiation Protocol (SIP) andSession Description Protocol (SDP); Stage 3
3GPP TS 36.306 Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio accesscapabilities
3GPP TS 36.133 Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio
resource management
3GPP TS 25.133 Requirements for support of radio resource management (FDD)
3GPP TS 22.071 Location Services (LCS); Service description
IEC 61162 Digital interfaces for navigational equipment within a ship
3GPP TS 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC);
Protocol specification (Release 10)
3GPP TS 24.167 3GPP IMS Management Object (MO); Stage 3
ITU-T E.212 - Series E: Overall network operation, telephone service, service operation and human factors
RFC 793 - Transmission Control Protocol (TCP) Protocol Specification (https://www.rfc-editor.org/rfc/
rfc793.txt)
3GPP TS 26.201 Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB)
speech codec; Frame structure
3GPP TS 24.216 Communication Continuity Management Object (MO)3GPP TS 36.521-2 - Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment conformance
specification; Radio transmission and reception; Part 2: Implementation Conformance Statement (ICS)
3GPP TS 36.523-2 - Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC);
User Equipment conformance specification; Part 2: Implementation Conformance Statement (ICS)
3GPP TS 23.003 Numbering, addressing and identification
3GPP TS 31.111 Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)
RFC 3969 - The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter
Registry for the Session Initiation Protocol (SIP)
RFC 3261 - SIP: Session Initiation Protocol
RFC 5341 - The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI)
Parameter Registry
RFC 3966 - The tel URI for Telephone Numbers
RFC 2141 - URN Syntax
RFC 3406 - Uniform Resource Names (URN) Namespace Definition Mechanisms
RFC 5031 - A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
3GPP TS 22.084 MultiParty (MPTY) supplementary service; Stage 1
3GPP TS 24.607 Originating Identification Presentation (OIP) and Originating Identification Restriction(OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification
3GPP TS 24.608 Terminating Identification Presentation (TIP) and Terminating Identification
Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification
3GPP TS 36.213 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures
3GPP TS 36.212 Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding
RFC 4715 - The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI
OMA
DeviceManagement
V1.2.1(http://technical.openmobilealliance.org/Technical/
technical-information/release-program/current-releases/dm-v1-2-1)
RFC 5626 - Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
3GPP TS 24.166 - 3GPP IP Multimedia Subsystem (IMS) conferencing Management Object (MO)3GPP TS 29.061 - Interworking between the Public Land Mobile Network (PLMN) supporting packet
based services and Packet Data Networks (PDN)
3GPP TS 24.303 - Mobility management based on Dual-Stack Mobile IPv6; Stage 3
3GPP TS 24.327 - Mobility between 3GPP Wireless Local Area Network (WLAN) interworking (I-WLAN)
and 3GPP systems; General Packet Radio System (GPRS) and 3GPP I-WLAN aspects; Stage 3
3GPP TS 25.367 - Mobility procedures for Home Node B (HNB); Overall description; Stage 2
3GPP TS 25.304 - User Equipment (UE) procedures in idle mode and procedures for cell reselection inconnected mode

UBX-13002752 - R67

Related documents

Page 986 of 1001

u-blox cellular modules - AT commands manual

118.
119.
120.
121.
122.
123.
124.
125.
126.
127.
128.
129.
130.
131.
132.
133.
134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.
146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.
158.
159.
160.

3GPP TS 36.304 - Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures
in idle mode
RFC 4867 - RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and
Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs
RFC 4733 - RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
3GPP2 C.S0015-0 - Short Message Service
RFC 1518 - An Architecture for IP Address Allocation with CIDR (https://tools.ietf.org/html/rfc1518)
RFC 1519 - Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy(https://tools.ietf.org/html/rfc1519)
3GPP TS 45.008 - GSM/EDGE Radio Access Network; Radio subsystem link control
3GPP TS 25.401 - Universal Mobile Telecommunications System (UMTS); UTRAN Overall Description
3GPP TS 24.237 - Technical Specification Group Core Network and Terminals; IP Multimedia (IM) Core
Network (CN) subsystem IP Multimedia Subsystem (IMS) Service Continuity; Stage 3
3GPP TS 36.211 - Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels andmodulation
3GPP TS 23.682 - Architecture enhancements to facilitate communications with packet data networks
and applications
3GPP TS 23.401 - General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial
Radio Access Network (E-UTRAN) access
GSMA TS.34 - IoT Device Connection Efficiency Guidelines
RFC 7252 - Constrained Application Protocol (CoAP)
Open Mobile Alliance (OMA) SyncML Common Specification, Version 1.2.2 (http://
www.openmobilealliance.org/release/Common)
Open Mobile Alliance (OMA) - Lightweight Machine to Machine Technical Specification, Version 1.0
MQTT Version 3.1.1 - OASIS Standard
MQTT-SN Protocol Specification Version 1.2
3GPP TS 44.018 - Mobile radio interface layer 3 specification; GSM/EDGE Radio Resource Control (RRC)
protocol3GPP TS 43.064 - General Packet Radio Service (GPRS); Overall description of the GPRS radio interface;
Stage 2
3GPP TS 36.321 - Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC)
protocol specification
3GPP TS 22.011 - Service accessibility
Device terminal access protocol-EDP technical specification, version 1.6
TOBY-L4 series data sheet, UBX-16009856
TOBY-L4 series system integration manual, UBX-16024839
TOBY-L2 series data sheet, UBX-13004573
MPCI-L2 series data sheet, UBX-13004749
TOBY-L2 / MPCI-L2 series system integration manual, UBX-13004618
LARA-R2 series data sheet, UBX-16005783
LARA-R2 series system integration manual, UBX-16010573
TOBY-R2 series data sheet, UBX-16005785
TOBY-R2 series system integration manual, UBX-16010572
SARA-R5 series data sheet, UBX-19016638
SARA-R5 series system integration manual, UBX-19041356
SARA-R4 series data sheet, UBX-16024152
SARA-R4 series system integration manual, UBX-16029218
SARA-U2 series data sheet, UBX-13005287
LISA-U2 series data sheet, UBX-13001734
LISA-U1 series data sheet, UBX-13002048
LISA-U1 / LISA-U2 series system integration manual, UBX-13001118
SARA-G450 data sheet, UBX-18006165
SARA-G450 system integration manual, UBX-18046432
SARA-G3 series data sheet, UBX-13000993

UBX-13002752 - R67

Related documents

Page 987 of 1001

u-blox cellular modules - AT commands manual

161.
162.
163.
164.
165.
166.
167.
168.
169.
170.
171.
172.
173.
174.
175.
176.
177.
178.
179.
180.
181.
182.
183.
184.
185.
186.
187.
188.
189.
190.
191.

SARA-G3 / SARA-U2 series system integration manual, UBX-13000995
LEON-G1 series data sheet, UBX-13004887
LEON-G1 series system integration manual, UBX-13004888
SARA-N2 series data sheet, UBX-15025564
SARA-N3 series data sheet, UBX-18066692
SARA-N2 / SARA-N3 series system integration manual, UBX-17005143
Wi-Fi / cellular integration application note, UBX-14003264
u-blox multiplexer implementation application note, UBX-13001887
u-blox Firmware update application note, UBX-13001845
Firmware update with uFOTA, FOAT and EasyFlash application note, UBX-17049154
GNSS implementation application note, UBX-13001849
SARA-R5 series application development guide, UBX-20009652
SARA-R5 series positioning implementation application note, UBX-20012413
End user test application note, UBX-13001922
AT commands examples application note, UBX-13001820
SARA-R5 series application development guide, UBX-20009652
SARA-R4 series application development guide, UBX-18019856
LwM2M objects and commands application note, UBX-18068860
NB-IoT application development guide, UBX-16017368
TOBY-L4 series eCall implementation in u-blox cellular modules application note, UBX-18019819
TOBY-L2 series audio application note, UBX-15015834
TOBY-L2 series networking modes application note, UBX-14000479
LISA-U1 / LISA-U2 audio application note, UBX-13001835
SARA-U2 audio application note, UBX-14002981
SARA-U2 series audio extended tuning application note, UBX-17012797
SARA-G3 audio application note, UBX-13001793
LEON-G1 audio application note, UBX-13001890
TOBY-L4 series extended audio application note, UBX-17065359
TOBY-L4 uCPU series Audio CSD API application note, UBX-18067601
RFC 8323 - CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets - https://www.ietf.org/rfc/rfc8323.txt
RFC 5280 - Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL)
Profile - http://www.ietf.org/rfc/rfc5280.txt
For regular updates to u-blox documentation and to receive product change notifications, register on our
homepage.

UBX-13002752 - R67

Related documents

Page 988 of 1001

u-blox cellular modules - AT commands manual

Revision history
Revision
P1
1
2
3

Date
30-Apr-2011
06-May-2011
11-May-2011
26-May-2011
07-Jul-2011

Name
tgri
lpah
lpah
lpah
lpah

A

14-Oct-2011

lpah

Comments
Initial release
Changed the title, removed "2G and 3.75G"
New commands for LEON-06x supported
Improvement for GPS and GPIO AT commands
Changed status to Preliminary; Assistnow online and offline description in+ULOCGNSS corrected
Applicable to LISA-U1x0-01S and LISA-U200-00S

A1

05-Dec-2011

mtom / lpah

New commands for STK raw mode and +PACSP
Changed status to Advance Information
Improved the +UVTS command syntax and the primary and secondary
PDP contexts description+CGDCONT setting stored in non volatile memory
New settings for the FW update over AT commands

A2
B

03-Feb-2012
18-May-2012

mtom / lpah
mtom / lpah

Added number of allowed SIM locks
Changed status to Preliminary
Changed status to Objective Specification status
Extended audio AT commands for LISA-U200-01 and LISA-U230-01
New commands: +UCMGP, +UMCLK, +URXDIV, +UMWI I2C and SAP

B1

31-Jul-2012

mtom

B2

10-Oct-2012

lpah

B3

13-Dec-2012

lpah

C

26-Mar-2013

lpah

Extended applicability to LEON-G100-07
Changed status to Preliminary; added +UEXTDCONF commanddescription and one shot automatic baud rate detection description
Changed status to Advance Information; applicable to LISA-U260 and
LISA-U270
Changed status to Preliminary; applicable to LEON-G100-08S and LEONG100-71S
Changed status to Advance Information; applicable to SARA-G350-00Sand SARA-G350-71S

C1
C2

17-Apr-2013
06-Jun-2013

lpah
lpah

C3

04-Jul-2013

lpah

New AT commands: +UDYNDNS, +UAEC, +UAGC, +UIPCHGN, +USER,+USOAO, +UTPB
Changed status to Preliminary
Changed status to Objective Specification; applicability extended to
SARA-G300-01S, SARA-G310-01S and LISA-U2x0-02S
Changed status to Advance Information

D
D1

30-Jul-2013
13-Sep-2013

lpah
lpah

(Last revision with old doc number, WLS-SW-11000)
Changed status to Preliminary
Added LEON-G100-71S FW version for Initial Production
SIM detection not supported by SARA-G300 / SARA-G31310 modules

R19

29-Nov-2013

lpah

Removed +UAEC, +UAGC, +USER AT commands
Extended the document applicability to new products
New commands: +UFWINSTALL
Updated +UCELLLOCK applicability
Improved description on +UHFP for SARA-G350 and the eCall commanddescription

R20

23-Jan-2014

lpah

Added note on +COPS command description for LISA-U1 / LISA-U2 series
Document applicable to LEON only for LEON-G100-06S-02, LEON-G100-0
7S-01 and LEON-G100-08S-01
New commands: +CECALL, +CECALL

R21

10-Apr-2014

lpah

Modified commands: +CSQ, +COPS and +CGED
Document applicable to SARA-U260 / SARA-U270 / SARA-G340 products
New layout for the command description

UBX-13002752 - R67

Revision history

Page 989 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

Comments
Reviewed the contents of the sections. Introduced these new sections:
SIM management, Audio interface
Split the +UDCONF command description for each supported
functionality
New commands: +CECALL, +UDCONF=66, +UGSRV
Modified commands: +UGPRF, +UDCONF=30, +USPM, +USMTP,+UHSDUPA, +UHTTPC, +UDTMFD, +UGAOF, +UGAOP, +UGAOS,+UGGGA, +UGGLL, +UGGSA, +UGGSV, +UGPS, +UGRMC, +UGTMR,+UGUBX, +UGVTG, +UGZDA, +ULOC, +ULOCCELL, +ULOCGNSS, +CGED,+CRLP, +UDCONF=40, +UDCONF=20

R22

23-Jun-2014

lpah

Updated estimated response time information for these commands:+CAOC, +CGANS, +CGCLASS, +CGCMOD, +CMGL, +CMGR, +CMGW,+CPMS, +CR, +CSCA, +CSCB, +CSMP, +CSVM, +SATD, +SATE,+SATR, +STKPRO, +UCMGL, +UCMGR, +UCMGP, +UCMGS, +UCMGW,+UDNSRN, +UDYNDNS, +UFRW, +UFTPER, +UGAOP, +UGPRF,+UIPCHGN, +ULOCCELL, +ULOCGNSS, +UPSDA, +USMTP, +USMTPER,+USOAO, +USOCO, +USOCR, +USOCTL, +USOER, +USOGO, +USOSO,+VTS, D*, D>, DL, Z, +UCELLINFO, +UEONS
Modified commands: +UCELLLOCK, GPRS definition, +USPM, GPIO
Introduction, +UDWNFILE, +UFTPC, +UFTP, +UHTTPC, +UHTTP, +CPBS,+USOGO, +USOSO, +CSVM, +CGPERMSTATE, +UFWUPD, +UI2S,+CGDCONT, +UI2CO, +UPSDA, +UEXTDCONF, +UMCLK, +USOAO,+USOAO, +UGIND, +UGIND, +UGPS, +UGAOF, +UGAOF, +UGAOP,+UGAOP, +UGAOS, +UGAOS, Multiple AT command interfaces
Extended the command description: +CMUX, +UFTP, HTTP errors,+UPSD, +UDCONF=8, +D, +UPING, +UFTPC, +UCELLINFO, +USOST,+UDCONF=40, +UGPRF, I, +UGSRV, Multiple AT command interfaces,+CGDCONT, +UDCONF=30, +ICF, +IPR, +UTPB, +UPSV, +UGPIOC,+ULSTFILE, +CBST, +UUFTPCD, +UBANDSEL, +UHSDUPA, +STKTR,+CIND AT commands

R23

21-Jul-2014

lpah

Review the command applicability for these commands: +UDCONF=2,+UDCONF=3, +UDCONF=20, +UDCONF=40, +UDCONF=30,+UDCONF=81, +UGPS, +UGIND, +UGPRF, +UGAOP, +UGAOF, +UGSRV,+UGAOS, +UGUBX, +UGTMR, +UGZDA, +UGGGA, +UGGLL, +UGGSV,+UGRMC, +UGVTG, +UGGSA, +ULOC, +ULOCGNSS, +ULOCCELL, +COPS,+USOAO, +UDBF, +UHFP, +UMGC, +USGC, +USTN, +UUBF, +UI2S,+UPAR, +UPLAYFILE, +USAR, +USPM, +USTOPFILE, +UTGN, +UGPIOC,+UDCONF=30
Modified commands: CME error result codes, Multiple AT commandinterfaces, Audio, +UDCONF=30, +UPAR, +UTGN, H, +CHUP,+UDCONF=32, +UDCONF=31, +UDCONF=90, FTP, +CSCS, +CGCLASS,+CGREG, +UCGCLASS, +UPSD, +UGAOF, +UGAOP, +UGGSV, +UGIND,+UGPRF, +UGPS, +UGSRV, +UGTMR, +ULOCCELL, +ULOCGNSS, +CPOL,+UCD, +UCELLLOCK, +UDCONF=20, +UDCONF=61, +UDCONF=81,+WS46, PING, +UDCONF=4, +UPING, +STKPRO, +CSIM, +UDCONF=50,+CNMA, +UCMGP, +UANTR, +UDCONF=0, +UDCONF=40, +UDCONF=66,+UFWUPD, +CALM, +UDCONF=1, +UDCONF=2, +UDCONF=3,+UDCONF=5, +UDCONF=6, +UDCONF=7, +UDCONF=8, +USODL, Z
Extended the command description: GPIO, +URDBLOCK, +CRC, +CRLP,+FCLASS, PPP, +UDCONF=0, +UPSD, +CGTFT, GPRS, SMS, +STKTR,SMS error result codes, +UTEST, +CGED, +CGDSCONT, +CGQMIN,+CGQREQ AT commands
Updated estimated response time information for this command:+UDOPN

R24

18-Sep-2014

lpah

Review the command applicability for this command: +UDCONF=90
Extended the document applicability to TOBY-L2 / MPCI-L2 products
starting from UBX-14000245-R03
New commands: +CCHC, +CCHO, +CGLA, +CRLA, +CGPIAF, +CUAD,+CESQ, +UCSDETACH, +CPNER, +UCATPROF, +UCATPROI,+UCATPRON, +UCATTR, +UCATCNF, +UCATENV, +UCATCC, +URCATI,+URCATN, +URCATR, +URCATF, +URCATCC, +UCGATT, +CEMODE,

UBX-13002752 - R67

Revision history

Page 990 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

Comments+CEREG, +CGDEL, +CGTFTRDP, +UAUTHREQ, +UTGSINK, +CGEQOS,+CGEQOSRDP, +CGSCONTRDP, +CEUS, +CGCONTRDP, +UCGDFLT,+UDCONF=9, +UCGED, +UDCONF=60, +UUSBCONF, +UIPADDR,+UIPCONF, +UIPROUTE, +UIPTABLES, +UBMCONF, +UDPDP
Modified commands: +CFUN, +CALA, +CCLK, +COPS, +WS46, +CPWD,+CPBW, +CSCB, +CPMS, +CNMA, +FCLASS, +UCSP, +CUSD, +CGACT,
D*, +UPSD, +CGTFT, +CGTFTRDP, +UTEST, +UI2S, +UEXTDCONF,+UHTTPC, +UFTPC

R25

R26

17-Nov-2014

23-Jan-2015

lpah

lpah

Review the command applicability for these commands: +UCELLLOCK,+CGED, +UDATACHANNEL, +CGANS, +CGAUTO
New command: +UDCONF=67
Modified commands: D, DL, D>, +CFUN, +CALA, +CIND, +CMER, +CPOL,+URAT, +UCGOPS, +CSQ, +CREG, +COPS, +CESQ, +UHOMEZR,+UCELLLOCK, +CPLS, +UCGED, +CLCK, +CPBS, SMS introduction,+CPMS, +CMGR, +CMGW, +CMGS, +CMGL, +CSMP, +UCMGR, +CUSD,&C, &D, V, &V, +CGLA, +CRLA, +CCHO, +CUAD, +CCHC, +STKCNF,+CGDCONT, <APN>, +CEMODE, +UCGATT, D*, +UCGDFLT, +CGREG,+UREG, +UTEST, +UFWUPD, +UUSBCONF, +UPSV, GPIO Introduction
Extended the document applicability to TOBY-L200-50S / TOBY-L200-50
S products version
New command: +UWAPIPCFG, +UWAPCFG, +UWCFG, +UWTEST,+UWAPSTALIST, +UWSTAIPCFG, +UWSTACFG, +UWFWRESET,+UWAPMACADDR, +UWMP, +UWSCAN, +UWWEBUI

R27

27-Feb-2015

lpah

Modified commands: +CSQ, +UTEST, +CMUX, &K, +ICF, +IFC, \Q, +UPSV,+IPR, +UUSBCONF, O, S2, S12, &C, &D, +UDNSRNExtended the document applicability to SARA-U270-00X and SARA-U280-00S product versions
Modified commands: +CMUX, +CGSN, +CSNS, +UBANDSEL, +CGED,+URAT, +UHSDUPA, +CREG, +UCELLLOCK, +UCSDETACH, +COPS,+UDCONF=20, +UCGOPS, +CLCK, +CNMI, +CLCC, O, S2, S12, &C, &D,+IPR, +ICF, +IFC, &K, \Q, <PDP_Type>, +UPSD, +UPSDA, +UPSND,+UCGDFLT, +UAUTHREQ, +CRSM, +STKTR, +STKPRO, +STKCNF,+UFWINSTALL, +UFWUPD, +UPSV, +UTEST, +URXDIV, +UDYNDNS,+UDWNFILE, +ULSTFILE, +URDFILE, +URDBLOCK, +UDELFILE, +UI2S,+UWAPCFG, +UWCFG, +UWTEST, +UWSTAIPCFG, +UWAPMACADDR,+UWWEBUI

R28

08-Jun-2015

lpah

Review the command applicability for these commands: +CMUX,+UCALLSTAT, +UCSD, +UCSDA, +UCSND, +UPSV, &K, &S, \Q, +SATF,+SATI, +SATN, +UDELFILE, +UDWNFILE, +ULSTFILE, +URDBLOCK,+URDFILE
Extended the document applicability to TOBY-L201-01S and TOBY-L28000S product versions
New commands: +CASIMS, +CIREG, +UIMSCONF, +UIMSRCONF,+UMNOCONF, +UMNOPLMN, +ULTECAT, +UANT

R29

19-Jun-2015

lpah

Modified commands: +CALA, +CTZR, +CREG, +COPS, +UBANDSEL,+UCGED, +CMGR, +IPR, +CSIM, +STKPRO, +STKTR, +STKCNF,+STKENV, +SATE, +UCATTR, +UCATPROI, <PDP_addr>, +CGREG,+UAUTHREQ, +UPSDA, +UDELFILE, +UDWNFILE, +ULSTFILE,+URDBLOCK, +URDFILE, +USOST, HTTP introduction, +UFTP, +UFTPC,+UHTTP, +UHTTPC, +UHTTPER, +UGPS, +UGSRV, +ULOCGNSS,+UDCONF=31, Wi-Fi introduction
Extended the document applicability to LISA-U200-03S, LISA-U201-03S,
SARA-U260-03S, SARA-U270-03S, SARA-U280-03S product versions
New commands: +UEMC, +UEMN, +UDCONF=82, +CAEMLPP,+CPPS, +CAAP, +USIMSTAT, +UBIP, +UNFM, +UNFMCONF, +URPM,+UNVMPLMN, +UNVMMCC, +UFACTORY, +UCEDATA, +UCTS,+USOSEC, +UDCONF=10, +USECMNG, +USECPRF, +UHTTPAC,+ULOCIND, +ULOCAID, +UDCONF=70, +CMOLRE, +CMOLR, +ULCSEVT,+CMTLR, +CMTLRA

UBX-13002752 - R67

Revision history

Page 991 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

R30

22-Jul-2015

lpahComments
Modified commands: +CGSN, +CSGT, +COPS, +UCELLINFO,+CGED, +URAT, +CSQ, +CLCK +CPBW, +UCMGP, +CNMI, +CGSMS,+CCWA, +CUSD, +UDCONF=50, D*, +UNVMPLMN, +UCEDATA,+UUSBCONF, GPIO Introduction, +UGPIOC, File System Introduction,+UEXTDCONF, +UPLAYFILE, +USOWR, +UFTPC, +ULOC, +UECALLSTAT,+UECALLVOICE, +UECALLDATA, +UDCONF=67
Objective Specification status
Extended the document applicability to TOBY-L200-02S, TOBY-L210-0
2S, MPCI-L200-02S, MPCI-L210-02S product versions
New commands: +UVGC, +UAPT, +UWWEBUIFTP

R31

14-Aug-2015

lpah

Modified commands: +CMUX, H, +CSNS, +CIND, +COPS, +UBANDSEL,+UDCONF=81, +CGED, +UMNOCONF, +UCELLLOCK, +UIMSCONF,+CPMS, +CMGF, +CNMI, +ICF, +IPR, +UCATENV, +UCATTR, +URCATE,+URCATR, +STKPRO, <APN>, +UCGDFLT, +URING, +UDATACHANNEL,+USOSEC, GPIO Introduction, +UGPIOC, +URDFILE, +UPAR, +UGSRV,+ULOCIND, +ULOCGNSS, LCS, +ULCSEVT, +CMOLRE, +CMOLR,+CMTLR, +CMTLRA, +UDCONF=70, +UIPROUTE, Web User Interface(WebUI), Audio interface introduction, +UAPT, +USTN, +UVGC, +UI2S,+UMCLK, +USPM, +UTGNEarly Production Information status
Extended the document applicability to LISA-U200-83S, LISA-U270-68S,
SARA-U270-53S product versions
Extended the document applicability to TOBY-L210-60S and MPCI-L21060S product versions
Modified commands: +CMUX, +CGSN, +CFUN, +CIND, +CSNS, +COPS,+CREG, +CGED, +CPOL, +UCELLINFO, +UDCONF=20, +UFDAC,+UMNOCONF, +USIMLCK, +CPBW, +FCLASS, \Q, &K, +ICF, +IFC,+UDCONF=50, <cid>, <PDP_addr>, <type_of_service_(tos)_(ipv4)_and_mask-traffic_class_(ipv6)_and_mask>, <flow_label (ipv6)>, <PDP_Type>,+CEUS, +UCGDFLT, D*, +UCGCLASS, +UCLASS, +UPSD, +USTS, +UPSV,+UTEST, +UUSBCONF, +UFACTORY, File tags, File System limits,
GPIO Introduction, +UGPIOC, +UPAR, +USAR, +UTGN, +UDCONF=30,
Audio parameters tuning introduction, IPv4/IPv6 addressing, +USOSO,+USOCO, +USOCTL, +USOLI, +UFTP, +USORF, +USOST, +UHTTP,+UHTTPC, +ULOC, +ULOCIND, +UGUBX, +CMOLR, +ULCSEVT, Wi-Fi
Introduction, +UWAPCFG

R32

14-Sep-2015

lpah

Review the command applicability for these commands: +UNVMMCC,+USPM, +UIPCHGN, +UDCONF=4
Advance Information status
New commands: +UFGI, KTDEVSTAT, KTCFUN, KTUBXCONF,
KTUCALLREJ, *KTF*OPENING, KTUUMTSENV, +USIMATR
Modified commands: AT Commands Settings, +CGSN, +GSN, +CALA,+CALM, +UPROGRESS, +COPS, +URAT, +UCELLLOCK, +CEMODE,+UFWUPD, +UANT, +UTEST, +UDCONF=40, +UFACTORY, +UDCONF=30,+UVGC, IPv4/IPv6 addressing, +USOWR, +USOST, +UDCONF=7,+USOAO, +UFTP

R33

23-Sep-2015

lpah

Review the command applicability for these commands: +CSVM,+CCWE, +UPROGRESS, L, M, P, T, +UCELLLOCK, +CGED, +ULTECAT,+UMNOCONF, +UMNOPLMN, +CASIMS, +UIMSCONF, +UIMSRCONF,+CIREG, +UANT, +UI2CC, +UI2CO, +UI2CR, +UI2CW, +UI2CREGR
New commands: +UWREGBLOCK
Modified commands: +UPROGRESS, +UCELLLOCK, +FCLASS,+UCATPROI, +UCATPRON, +UCATTR, +CGDATA, +UANT, File Tags
Introduction, +UDCONF=30, +UFTPC, +UDCONF=31, +UWWEBUI,+UWAPCFG

R34

12-Oct-2015

UBX-13002752 - R67

lpah

Review the command applicability for these commands: +VTS, +UVTS,
D*, +UDATACHANNEL, +UDCONF=40, +UDTMFD,
Extended the document applicability to TOBY-L280-02S, MPCI-L280-02S

Revision history

Page 992 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

R35

30-Nov-2015

lpahComments
Modified commands: Information text responses and result codes,
Operational restrictions, +CMUX, +CIND, +CEER, +UCEER, D, +CSQ,+CESQ, +COPS, +UHSDUPA, +UMNOCONF, +UMNOPLMN, +URAT,+UBANDSEL, +CPLS, +CLCK, +CHLD, +ICF, +CSIM, +CRSM, +UUICC,+CCHO, +UCATPRON, +UDTMF, Introduction and common parameters
definition, <cid>, <PDP_Type>, +UCGDFLT, +UAUTHREQ, +CGDSCONT,+CGDATA, +CGACT, D*, +UDCONF=9, +UFWINSTALL, +UFWUPD,+UDCONF=40, +UUSBCONF, +UI2S, +UPAR, +UPLAYFILE, +UTGN, TCP/
IP UDP/IP Introduction, +USOLI, +USORF, +USODL, +USOCTL, +UHTTP,+UHTTPC, +UI2CO, +UIPROUTE, +UIPADDR, +UWCFG,
Review the command applicability for these commands: +UAUTHREQ, D*,
Early Production Information status
Modified commands: AT command settings, +CMUX, +CPAS, +CIND,+CTZU, +CSTA, S0, +COPS, +UCD, +UMNOCONF, +CGED, +UCGED,+UMNOPLMN, SMS Introduction, +CPMS, &D, +CCFC, &K, +ICF, +IFC,\Q, +IPR, O, +CGSMS, +CGCLASS, D*, +CGPIAF, +CGDATA, +UPSD,+UDCONF=40, +UDCONF=66, +UPSV, +UNFMCONF, GPIO Introduction,+UGPIOC, +UMCLK, +UPLAYFILE, +UHFP, +USODL, +UFTP, +UGPRF,+ULOC, +UGSRV, +UDTMFD, +UDCONF=31, +USAPIND, +USAPMODE,+UIPADDR, Web User Interface (WebUI), +UWCFG, +UWAPCFG,+UWREGBLOCK

R36

15-Dec-2015

lpah

Review the command applicability for these commands: +CASIMS,+UIMSCONF, +UIMSRCONF, +CIREG, +UDCONF=31
Extended the document applicability to SARA-G340-02S, SARA-G350-0
2S, SARA-G350-02X, SARA-G350-02A, LISA-U201-83S, MPCI-L201-01S
Modified commands: +CSCS, +CFUN, +CIND, +CSQ, +COPS, +URAT,+UBANDSEL, +CGED, +UCD, +UMNOCONF, +CPOL, +WS46,+UIMSCONF, +CLCK, +CPWD, +CPBS, +CPBW, +CPBR, +CPBF, +CGSMS,+CNMI, +CAOC, +CCFC, +CCUG, +CCWA, +CHLD, +CLIP, +CLIR, +CNAP,+COLP, +COLR, +CSSN, +CTFR, +CUSD, +CUUS1, &K, &S, \Q, +IFC,<PDP_Type>, +CGDCONT, D*, +UPSD, +CGEREP, +UFWUPD, +UPSV,+UFACTORY, GPIO Introduction, File System Introduction, +UDWNFILE,+UI2S, +USPM, +UVGC, +UFTPC, +ULOCAID, Web User Interface (WebUI)

R37

R38

29-Jan-2016

16-Feb-2016

lpah

lpah

Review the command applicability for these commands: +CGED,+CAEMLPP, +CPPS, +CAAP, \Q, &K, &S
Document status updated to Early Production Information
Modified commands: Command line, +CMUX, +CEER, S0, +UCELLLOCK,+UCGED, +CPBS, +CPBR, +CPBF, +CPBW, SMS Introduction, +CNMI,+CMGW, &D, &K, +IFC, \Q, +IPR, O, +UTPB, +UPSD, +UPSDA, +CGACT,+CGDATA, D*, +UPSV, +UPLAYFILE, +UHFP, +USODL, +USECPRF,+UFTPC, +UPING, +UI2CR, +UI2CREGR, +UI2CC, +UIPADDR, +UWAPCFG,+UWREGBLOCK, Internal TCP/UDP/IP stack class error codes
Document status reverted to Advance Information. Extended the
document applicability to TOBY-L210-62S
New commands: +CNEM, +CSSAC
Modified commands: &H, +VTS, S0, +COPS, +URAT, +UHSDUPA,+UBANDSEL, +WS46, +UMNOCONF, +UIMSCONF, +UIMSRCONF,&V, <APN>, PPP, D*, +CGACT, +UCGCLASS, +UCLASS, +CEMODE,+UCGDFLT, +URXDIV, +UFACTORY, +UDCONF=40, +UDCONF=60,+UDCONF=30, +UDTMFD, +UDCONF=70

R39

31-Mar-2016

lpah

Review the command applicability for this command: +VTD
Extended the document applicability to SARA-U260-00S-01, SARA-U270-00S-01 and TOBY-L220-02S. Removed the document applicability to
SARA-U260-00S-00
Modified commands: Summary table, +CSCS, +CMOD, +UVTS, +COPS,+CGED, +ULTECAT, +UMNOCONF, +CLCK, +CPBW, &V, <PDP_Type>,<IM_CN_Signalling_Flag_Ind>, PPP LCP handshake behaviour, D*,+CGDCONT, +CGDSCONT, +CGCONTRDP, +CGSCONTRDP, +UCGDFLT,+UCGCLASS, +CGEREP, +CGCMOD, +UFWINSTALL, +UFWUPD,+UDCONF=66, KTUUMTSENV, +UAPT, +UVGC, +UTGN, +UPAR,+USECPRF, +UHTTPC, +UIPADDR, +UDPDP, Wi-Fi introduction,

UBX-13002752 - R67

Revision history

Page 993 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

Comments+UWSTAIPCFG, +UWAPCFG, +UWAPIPCFG, +UWAPMACADDR,+UWAPSTALIST, +UWCFG, +UWFWRESET, +UWMP, +UWREGBLOCK,+UWSCAN, +UWSTACFG, +UWTEST, +UWWEBUI, +UWWEBUIFTP
Review the command applicability for this command: +UDTMF

R40

26-Apr-2016

lpah

Updated estimated response time information for these commands:+UWCFG, +UWAPCFG, +UWSTACFG
Extended the document applicability to TOBY-L210-60S-01, MPCI-L21060S-01
New commands: +CISRVCC, +COPS, +UMNOCONF, +CMMIVT

R41

18-May-2016

lpah

Modified commands: +CPOL, +CASIMS, +USIMSTAT, +UDCONF=50,+CGEREP, +UGAOP, +UGUBX
Document reverted to Objective Specification status
Extended the document applicability to SARA-G300-00S-01, SARA-G31000S-01, LISA-U201-03A, LISA-U270-63S
New commands: +UBIPAPN, +UDCONF=11, +UOMADM,+UOMADMALERT, +UOMADMREP

R42

24-Jun-2016

lpah

Modified commands: +URAT, +CGED, +UCGED, +CLCK, +CRLP,+UCATPROF, <PDP_addr>, +CGDCONT, +UCTS, Audio interface
introduction, +UMGC, +USGC, +USECMNG, +USECPRF, +UFTPC,+UDTMFD, eCall Introduction, +UECALLVOICE, +UECALLDATA,+CECALL, Networking introduction, +UDPDP, Mobile termination error
result codes +CME ERROR, Internal TCP/UDP/IP stack class error codes
Document updated to Advance Information status
Modified commands: Summary table, AT Commands Settings, General
Operations, +UBANDSEL, +CNEM, +UMNOCONF, +CEVDP, +UIMSCONF,+UIMSRCONF, +CASIMS, +CPBS, +CPMS, V, +USIMSTAT, +CGEREP,+UFGI, +CGAUTO, +USTS, File System limits, +ULSTFILE, +UDBF,+USOWR, +USOST, +USECMNG, +USECPRF, +UFTPC, +UHTTPC,+USMTPM, +UGAOP, +UWTEST

R43

05-Aug-2016

lpah

Review the command applicability for these commands: +UCALLSTAT,+CGED, +CCWA, +CAEMLPP, +CPPS, +CAAP, +UNVMPLMN,+UNVMMCC
Document status updated to Early Production Information
Extended document applicability to LISA-U200-62S-02 and SARA-G34002X
Modified commands: AT Commands Settings, +CMUX, +CGSN, +CMER,+CTZR, +CISRVCC, +CMOD, S0, +COPS, +CSQ, +UBANDSEL, +CGED,+UCGED, +UHSDUPA, +UMNOCONF, +UMNOPLMN, +URAT, IMSIntroduction, +UIMSCONF, +UIMSRCONF, SMS Introduction, Class
0 SMS, SMS limitations, +CMGR, +CMGD, +CNMI, O, &D, &K, +ICF,+IFC, +IPR, \Q, +CSIM, +CRSM, +UDCONF=50, +CGLA, +CRLA, <cid>,<d_comp>, <h_comp>, +CGDCONT, D*, +CEMODE, +CEUS, +CEREG,+UAUTHREQ, +UCGDFLT, +CGDATA, +CGPADDR, +CGDEL, +UCLASS,+UFWUPD, +UPSV, +UOMADM, +UOMADMALERT, +UOMADMREP,GPIO Introduction, +UGPIOC, File System Introduction, +UDWNFILE,+USODL, +USECPRF, +USTN, +UHFP, +USOCR, +UFTP, +UFTPC,+UHTTP, +UGPRF, +UGSRV, +UDTMFD, Wi-Fi Introduction, Web User
Interface (WebUI), +UWAPCFG, +UWAPIPCFG, +UWCFG, +UWSCAN,+UWSTACFG, +UWSTAIPCFG, Mobile termination error result codes+CME ERROR

R44

22-Sep-2016

lpah

Review the command applicability for these commands: +UDCONF=11,+UDCONF=9, +UCGATT
Document status reverted to Advance Information
Extended document applicability to MPCI-L201-02S, TOBY-L201-02S,TOBY-R202-02B
New commands: +UCSG, +UIMSCFG, +UIMSREG, +UPCO, +UDNS,+USPEECHINFOUBX-13002752 - R67

Revision history

Page 994 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

R45

21-Oct-2016

lpah

R46

18-Nov-2016

lpah

Comments
Modified commands: AT command line, AT Commands Settings Notes,+CSQ, +CALA, +CIND, +URAT, +IPR, +UDCONF=50, PPP LCP handshake
behaviour, +UCGDFLT, +CGEQOSRDP, +UDNS, +CEMODE, +UFWUPD,+UOMADM, +URING, +UDCONF=30, +USOCR, +USOWR, +USOST,+USECMNG, +UHTTPC, +USMTPM, +UI2CO, +UIPCONF, +UWSTACFG,+UWSTAIPCFG, +UWAPIPCFG
Extended the document applicability to TOBY-L280-72S, MPCI-L220-02S,
MPCI-L280-72S
Modified commands: +CALA, +CFUN, +CPOL, +URAT, +UMNOCONF,+UMNOPLMN, +CLCK, SMS Introduction, +CNMI, &K, +ICF, +IFC,\Q, +UCATPRON, +UCGDFLT, +CGEREP, +UPSV, GPIO Introduction,+USECPRF, +UFTPC
Extended the document applicability to LARA-R204-02B, TOBY-L200-00
S-01, MPCI-L200-00S-01
New commands: +VZWAPNE, +VZWRSRP, +VZWRSRQ
Modified commands: +CFUN, +CSGT, +CTZU, +COPS, +URAT, +CNEM,+UCELLINFO, +UDCONF=20, +WS46, +CLIP, +CLIR, +COLP, +COLR,<cid>, +CGDCONT, +CGQMIN, +CGACT, +CGPADDR, +UANT, +URXDIV,+UTEST, +UNVMPLMN, +UNVMMCC, +UOMADMALERT, +UFACTORY,GPIO Introduction, +USPM, +UEXTDCONF, +UMCLK, LARA-R2 / TOBYR2 Audio interface, SARA-U2 Audio interface, LISA-U2 Audio interface,+UDYNDNS, +UWCFG

R47

15-Dec-2016

lpah

Review the command applicability for these commands: +CSNS, +CGED,+VZWAPNE, +VZWRSRP, +VZWRSRQ, +CAEMLPP, +CPPS, +CAAP"Disclosure restriction" replaces "Document status" on page 2 anddocument footer
New commands: +UDCONF=12,
Modified commands: +CISRVCC, +VTS, +COPS, +UEONS, +UMNOCONF,+CPOL, +UIMSCFG, +UCMGS3GPP2, +CLCK, +CPBW, +UFGI,+UFACTORY, +UTEST, +UUSBCONF, +UOMADMREP, +UEXTDCONF

R48

10-Feb-2017

lpah

Review the command applicability for these commands: +CNEM,+CSSAC, +UMNOCONF, +CISRVCC, +CASIMS, +CIREG, +UIMSCONF,+UIMSRCONF, +CEVDP, +CACM, +URXDIV, +UOMADMREP
Extended the document applicability to SARA-U270-03A
Modified commands: URCs presentation deferring, I, +CFUN, +CMER,+CALA, +UDOPN, +UFDAC, +UDCONF=81, +CGED, +UCGED, +WS46,+UMNOCONF, +UIMSCFG, +UIMSREG, +UCMT3GPP2, +CNMI, +CMGR,+CMGL, +UCMGR, +UCMGL, +CCHO, +CGACT, +CGEREP, +CEREG,+CGCONTRDP, +UFWINSTALL, +UANT, +UTEST, +UNVMPLMN,+UGPIOC, +UPAR, +USAR, +UTGN, +UDCONF=30, +UHFP, +USOCR,+USOSO, +USOGO, +USOCL, +USOCO, +USOWR, +USOST, +USORD,+USORF, +USOLI, +USODL, +USOCTL, +USECMNG, +USAPIND,+UWREGBLOCK, +UWTEST

R49

24-Feb-2017

lpah

Review the command applicability for these commands: +CSSAC,+UFDAC, +UDCONF=61, +UDCONF=30
Extended the document applicability to LARA-R202-02B and LARA-R20302B
New commands: +CIREP
Modified commands: +VTS, +CFUN, +COPS, +URAT, +UCGOPS,+UHSDUPA, +UCGED, +WS46, +UIMSCFG, S7, <cid>, <h_comp>,+CGDCONT, +UPSDA, +CGACT, +UCLASS, +UANT, +UOMADMALERT,+UOMADMREP, +UDCONF=30, LARA-R2 / TOBY-R2 Audio interface

R50

19-Apr-2017

lpah

Review the command applicability for these commands: +UOMADM,+UOMADMALERT, +UOMADMREP, +UOMASTAT
Extended the document applicability to SARA-U270-53S-01, MPCI-L22062S, TOBY-L220-62S
Modified commands: Information text responses and result codes,+CMER, +CFUN, +CISRVCC, +UCALLSTAT, +UPROGRESS, +CSQ, +CREG,+UMNOCONF, +UIMSCFG, +CMMIVT, +CIREP, +CLCK, +UPINCNT,UBX-13002752 - R67

Revision history

Page 995 of 1001

u-blox cellular modules - AT commands manual

Revision

R51

Date

31-May-2017

Name

lpah

Comments+USIMSTAT, +UDCONF=54, +CCFC, +CCWA, +CGDCONT, +UCGATT,+CGACT, +UCLASS, +CGREG, +UCGDFLT, +UANT, GPIO mapping,
Network status indication, File System limits, +UDCONF=30, +UI2S,+UFTP, +UDTMFD, +USAPMODE
Review the command applicability for these commands: +CISRVCC,+CSTA, +UCALLSTAT, +UPROGRESS, +UEMC, +CASIMS, +CLCK,+CCFC, +CCWA, +CLIR, +CLIP, +CAOC, +CCWE, +CHLD, +CLCC, +CBST,+UDCONF=32, +FCLASS, +CR, +CRC, +CRLP, +UDCONF=54, +URXDIV,+UDCONF=40,
New commands: +UDAMCFG
Modified commands: AT command settings, General operation, I, +CIND,+CEER, D, +COPS, +URAT, +CGED, +UIMSCFG, +CEVDP, +CLCK, +CPBS,+CPBW, SIM toolkit introduction, +UBIP, D*, +CEMODE, +CGCONTRDP,+UDNS, +UGCNTRD, +UGCNTSET, +UFWINSTALL, +URXDIV, GPIO
Introduction, +USOCO, +UIPROUTE, +CEER error result codes

R52

30-Jun-2017

lpah

Review the command applicability for these commands: +UDCONF=20,+UBIP, +UOMASTAT
Extended document applicability to SARA-G350-02X, TOBY-L200-03S,TOBY-L210-03S, TOBY-L280-03S, MPCI-L200-03S, MPCI-L210-03S,MPCI-L280-03S
New commands: +UDCONF=33
Modified commands: +CMUX, I, +UPROGRESS, +CPAS, +CSGT, +CTZU,+CSQ, +COPS, +URAT, +UCGOPS, +CPOL, +UCGED, +UMNOCONF,+UMNOPLMN, +VZWAPNE, +CLCK, +CPBS, +CPBW, +CHLD, SMS
Introduction, +CNMI, &K, +ICF, +IFC, \Q, +CRSM, +CRLA, +UCATPRON,+CGDCONT, +UCGATT, +UCGDFLT, +UPCO, +UDNS, +CGANS,+UFWUPD, +UOMADMREP, +UPSV, GPIO Introduction, Network statusindication, +UI2S, Internet protocol transport layer, +USOCO, +USECPRF,+UFTPC, +UGPRF, +ULOCCELL, Error result codes
Updated estimated response time information for these commands:+UCMGR, +UCMGP,

R53

R54

14-Jul-2017

25-Sep-2017

lpah

lpah

Review the command applicability for these commands: +UFGI, +UGPS,+UGIND, +UGPRF, +UGAOP, +UGAOF, +UGSRV, +UGAOS, +UGUBX,+UGTMR, +UGZDA, +UGGGA, +UGGLL, +UGGSV, +UGRMC, +UGVTG,+UGGSA, +ULOC, +ULOCIND, +ULOCAID, +ULOCGNSS, +ULOCCELL
Extended document applicability to LARA-R220-62B
Modified commands: AT Command Settings, URCs presentation
deferring, +CMUX, +CGSN, +CFUN, +CEER, +CALA, D, A, +VTD,+VTS, +UVTS, +UPROGRESS, +COPS, +UNVMMCC, +UNVMPLMN,+UHSDUPA, +URAT, +WS46, +CPBS, +CPBR, +CNMI, +CMGL, +CLIP,+COLP, +COLR, &K, +IFC, Packet switched parameter definition, PPP,+CGDCONT, +UPCO, +UDNS, +CGQREQ, +CGQMIN, +CGATT, +CGACT,+CGANS, +UCLASS, +CGEREP, +CGEQREQ, +CGEQMIN, +CGEQNEG,+CGDSCONT, +CEMODE, +CGTFTRDP, +CGSCONTRDP, +CGCONTRDP,+CGEQOS, +CGEQOSRDP, +CGTFT, +UANT, GPIO introduction, +UGPIOC,+UDCONF=30, Audio parameters tuning introduction, FTP, HTTP,+UGUBX, +ULOCCELL, +UDTMFD, +USAPMODE, Error result codes,+CEER error result codes
Extended the document applicability to SARA-U201-63B, SARA-U201-0
4A, SARA-U201-04B, SARA-U201-04X, LARA-R280-02B, TOBY-R200-0
2B-01, TOBY-R202-02B-01
Modified commands: AT Commands Settings, Concatenation of AT
commands, S-parameters, +CMUX, +CFUN, +CTZR, +CLCC, +COPS,+UMNOCONF, +UCGED, +UEONS, +URPM, +UNFM, +UNFMCONF,+UIMSCFG, +CMGS, +CMGW, +CSMP, &D, &K, +IFC, \Q, O, +STKPROF,<cid>, +CGDATA, +UPSD, +CGATT, +CGDSCONT, +CGQMIN, +CGACT,+CEREG, +UCLASS, +CGTFT, +CGQREQ, +CGTFTRDP, +UREG,
Multiple PDP contexts, +UFWUPD, +UPSV, +USIO, GPIO introduction,+UPLAYFILE, +USTOPFILE, +UEXTDCONF, +UHFP, +UDNSRN, Internet
protocol transport layer, +USOCR, +USOCO, +USOST, +USODL,+USECPRF, USECMNG Notes, +UHTTP, Ping Introduction, +UGPS,UBX-13002752 - R67

Revision history

Page 996 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

Comments+UGIND, +UGPRF, +UGAOP, +UGAOF, +UGSRV, +UGAOS, +UGUBX,+UGTMR, +UGZDA, +UGGGA, +UGGLL, +UGGSV, +UGRMC, +UGVTG,+UGGSA, +ULOC, +ULOCIND, +ULOCAID, +ULOCGNSS, +ULOCCELL,+UI2CO, FTP class error codes
Updated estimated response time information for these commands:+CMGR, +CMSS, +UCMGP, +UCMGR, +USOSEC, +USOCL, +USOWR,+USOST, +USORD, +USORF, +USOLI, +USODL, +USMTPM, +USMTPC

R55

R56

15-Oct-201722-Nov-2017

lpah

lpah

Review the command applicability for these commands: +CISRVCC,+UMNOCONF, +CNEM, +CSSAC, +CIREG, +CIREP, +CASIMS, +CMMIVT,+CEVDP, +UISMS, +UDCONF=60, +UGPS, +UGIND, +UGPRF, +UGAOP,+UGAOF, +UGSRV, +UGAOS, +UGUBX, +UGTMR, +UGZDA, +UGGGA,+UGGLL, +UGGSV, +UGRMC, +UGVTG, +UGGSA, +ULOC, +ULOCIND,+ULOCAID, +ULOCGNSS, +ULOCCELL
Modified commands: Summary table, Information text responses
and result codes, Auto-registration, +CFUN, +CEER, +COPS, +CGED,+UCELLINFO, +CPMS, Supplementary services introduction,+UDCONF=32, +UDCONF=66, +UPSD, +CGEREP, +CEMODE,+UAUTHREQ, SARA-U2 audio interface, +ULGASP, +UHFP, +UTIME,+UIPTABLES, +UWSTAIPCFG,
Review the command applicability for these commands: +CSVM, +CNEM,+CSSAC, +CLCK, +USPM
Extended document applicability to TOBY-L4 series
New commands: +UJAD, +UACT, +UTI, +UMAFE, +USAFE, +UMSEL

R57

16-Mar-2018

lpah

Modified commands: +CFUN, +CREG, +FCLASS, +CRC, +CGDCONT,+UDNS, +CGACT, +CGREG, +UAUTHREQ, +UFWINSTALL, +UFWUPD,+URXDIV, +UTEST, +URING, +UFACTORY, File System Introduction,+UDWNFILE, +URDFILE, +USPM, +UI2S, +UI2S, Audio interface
introduction, +UTIME
Extended document applicability to TOBY-L210-03A and new LISA-U2 /SARA-U2 type numbers
New commands: +URPMCONF
Modified commands: Command line, Start-up and initialization, +CFUN,+CCLK, +CRSL, +CMEE, +CTZU, +CSQ, +CESQ, +CREG, +COPS,+URAT, +UHSDUPA, +UCSDETACH, +UMNOCONF, +CPOL, +CNEM,+UDCONF=20, +UCGED, +UCELLINFO, +UNFMCONF, +UIMSCFG,+CPWD, +CPBS, SMS Introduction, +CNMI, +CGSMS, +UETWCFG,+UETWNTFYSTART, +UETWNTFYSTOP, +UDCONF=50, V24 control andV25ter introduction, &K, +ICF, +IFC, \Q, <APN>, D*, +CGDCONT, +CGREG,+UCGATT, +CGACT, +UCGDFLT, +UGCNTSET, +UDCONF=9, +STKTR,+STKCNF, +UBIP, +UCATPRON, +UFWINSTALL, +UFWUPD, +UTEST,+UDCONF=40, File System Introduction, +UDWNFILE, +URDFILE,+USPM, +UI2S, Audio interface introduction, +UMGC, +USGC, +UMAFE,+UFTPC, +UGPRF, +USAPMODE, +UIPTABLES, +UWSTACSQ, +UWMP,+UWTEST, Saving AT commands configuration

R58

30-Apr-2018

lpah

Review the command applicability for these commands: DL,+UDCONF=20, +PACSP, +CGED, +UCELLINFO, +URPM, +UMGC, +USGC,
Extended document applicability to LARA-R202-02B-01, LARA-R20302B-01, LARA-R204-02B-01, LARA-R211-02B-01, LARA-R220-62B-01,
LARA-R280-02B-01, LARA-R280-02B-02, TOBY-R200-02B-02, TOBY-R20
2-02B-02.
New commands: +UDCONF=56, +UTEMP, +UDCONF=64.
Modified commands: AT command settings, General Operations, Start
up and initialization, +CGSN, +CFUN, +CIND, S0, +CSQ, +CESQ, +COPS,+URAT, +UDCONF=81, +UCGED, +UJAD, +UMNOCONF, +UIMSCFG, SMS
introduction, +CSCB, +CLIR, +CRC, PPP, PDP contexts and parameter
definition, <cid>, <PDP_addr>, +CGDCONT, +CGANS, +CGDATA, D*,+CGCMOD, +CGEQREQ, +CGEQMIN, +CGEQNEG, +CEREG, +UTEST,+USTS, +URING, GPIO Introduction, +UGPIOC, File System Introduction,+UDWNFILE, +URDFILE, +UDELFILE, +USPEECHINFO, DNS introduction,
Internet protocol transport layer, +USOCL, +UIPCHGN, +USECMNG,+USECPRF, HTTP introduction, +UHTTP, FTP introduction, PING,

UBX-13002752 - R67

Revision history

Page 997 of 1001

u-blox cellular modules - AT commands manual

Revision

R59

Date

30-Sep-2018

Name

lpah

Comments+UGPS, +UGIND, +UGPRF, +UGAOP, +UGAOF, +UGSRV, +UGAOS,+UGUBX, +UGTMR, +UGZDA, +UGGGA, +UGGLL, +UGGSV, +UGRMC,+UGVTG, +UGGSA, +ULOC, +ULOCIND, +ULOCAID, +ULOCGNSS,+ULOCCELL, eCall Introduction, +UECALLDATA, +UECALLVOICE,+UECALLSTAT, +UI2CR, +UBMCONF, +UIPCONF, +UIPROUTE, +UWMP,
Mobile termination error result codes +CME ERROR, Internal TCP/UDP/IP
stack class error codes, FTP class error codes.
Review the command applicability for these commands: +UCELLINFO,+UMNOCONF, +UDCONF=20, +UDCONF=57, +USTS, +USPEECHINFO,+UGPS, +UGIND, +UGPRF, +UGAOP, +UGAOF, +UGSRV, +UGAOS,+UGUBX, +UGTMR, +UGZDA, +UGGGA, +UGGLL, +UGGSV, +UGRMC,+UGVTG, +UGGSA, +ULOC, +ULOCIND, +ULOCAID, +ULOCGNSS,+ULOCCELL, +UDCONF=90.
Extended the document applicability to SARA-G450-00C, LISA-U200-0
1S-03, LISA-U200-03S-02, LISA-U200-52S-03, LISA-U200-62S-04, LISAU230-01S-03, LISA-U270-63S-02.
New commands: +USECCFG, +UECALLCFG, +UIFCONF.
Modified commands: +CGSN, D, +CESQ, +COPN, +CHLD, +CGEREP,+UFWUPD, +USIO, +UDWNFILE, +UDCONF=30, +USPM, Audio interface
introduction, +USECPRF, +UHTTPC, +UECALLDATA, +UECALLVOICE,+UECALLSTAT.

R60

15-Dec-2018

lpah

Review the command applicability for these commands: +URPM,+URPMCONF, &W, &V, +USTS, +UOMADM, +UOMADMALERT,+UOMADMREP, +UOMASTAT, +UTEMP, +USPM, +USPEECHINFO,+USECMNG, +USECPRF, +UI2CO, +UI2CW, +UI2CR, +UI2CREGR, +UI2CC.
Extended the document applicability to SARA-U270-04B.
New commands: +UFWSINSTALL.
Modified commands: AT command settings, Profiles, +CMUX, &H,+CPAS, +CIND, +CCLK, +CALD, +CALM, +CRSL, +CTZU, +CLCC, H,+CMOD, S0, +CSVM, +CSQ, +COPS, +UNVMMCC, +COPN, +UJAD,+UMNOCONF, +UIMSCFG, +UPINCNT, +CLCK, +CPWD, +CCWA,+CLIR, +CHLD, +CNAP, +CRC, &D, &K, +IFC, \Q, +IPR, O, S2, &W,&V, +XSIMSWITCH, SIM toolkit introduction, <cid>, <PDP_Type>,+CGDCONT, +UPSD, +CGQREQ, +CGANS, +CGDATA, D*, +CGCLASS,+CGEQREQ, +CGDSCONT, +UAUTHREQ, +CGEQOS, +CGTFT,+UFGI, +UFWINSTALL, +UFWUPD, +UPSV, +UTEST, +USTS, +USIO,+UFACTORY, GPIO Introduction, +UGPIOC, +UDWNFILE, +URDFILE,
File System limits, +UPLAYFILE, +URECFILE, +UAREC, +UEXTDCONF,+UMAAT, Audio parameters tuning Introduction, +UHFP, +UDNSRN,+USOSEC, +USODL, Data security introduction, +USECMNG, +USECPRF,+USECCFG, +UFTP, +UHTTP, +UGPS, +UGPRF, +UGSRV, +UDTMFD,+UI2CO, +UBMCONF, +UIFCONF, +UIPROUTE, +UIPTABLES, +CEER error
result codes, +UFWSINSTALL error result codes, Parameters stored in
profiles.
Updated estimated response time information for these commands:+XSIMSWITCH.

R61

15-Feb-2019

lpah

Review the command applicability for these commands: A/, +CLAC,&H, +CPAS, +CALM, +CLCC, +CSTA, D, T, P, A, H, +CMOD, +CHUP,+UCALLSTAT, +VTD, +VTS, +USIMLCK, +CCFC, +CCWA, +CLIR, +CLIP,+COLP, +COLR, +CAOC, +CACM, +CAMM, +CPUC, +CHLD, +CSSN,+CNAP, +CR, +CRC, +UTPB, +USPEECHINFO, +USOSEC, +USOAO.
Extended the document applicability to SARA-U201-63B-02, TOBY-L20
0-03S-01, TOBY-L201-02S-01, TOBY-L210-03S-01, TOBY-L280-03S-01,
MPCI-L201-02S-01.
New commands: +UISS.
Modified commands: +CFUN, +CMER, +CEER, D, +UCALLSTAT,+CSVM, +COPS, +UNVMMCC, +CREG, +PACSP, +CGED, +UMNOCONF,+VZWAPNE, +UIMSCFG, +UIMSCONF, +UICMGSMODE, +CPBS,+CPNER, Supplementary services introduction, &F, +UBIP,<PDP_Type>, +CGDCONT, +UDCONF=66, +CGATT, +CGDATA, +CGREG,+CGCONTRDP, +UFWSINSTALL, +UPSV, +UTEST, +USPM, +UAREC,UBX-13002752 - R67

Revision history

Page 998 of 1001

u-blox cellular modules - AT commands manual

Revision

Date

Name

Comments+UEXTDCONF, +UHFP, +UMGC, +USGC, +UAPT, +UMAFE, +USAFE,+UMSEL, +USOCO, +USECMNG, +USECPRF, +UFTPC, +UHTTPC,+UECALLDATA, +UECALLCFG, +UBMCONF, Mobile termination error
result codes +CME ERROR, Parameters stored in profiles.
Updated estimated response time information for these commands:+UDNSRN, +USOCO.

R62

20-Apr-2019

lpah

Review the command applicability for these commands: +CGDATA.
Extended the document applicability to TOBY-R200-02B-04, TOBY-R20202B-04, LARA-R202-02B-03, LARA-R203-02B-03.
New commands: +UMNOPROF, +UDCONF=110, +UNVMW, +UNVMR,+UNVMF, +UDNSCONF, +UDCONF=71, +UIP6TABLES.
Modified commands: u-blox Technical Documentation, Profiles,+UDCONF AT command, URCs presentation deferring, +CSCS, +CIND,+CMER, +CRSL, +CLVL, +URAT, +CREG, +UHSDUPA, +UBANDSEL,+UMNOCONF, +UDCONF=57, +UIMSCFG, +CEVDP, +CPIN, +CLCK,+CPMS, +CSAS, +CSCB, +UDCONF=50, +CGCLASS, +UDCONF=9,+UOMADMREP, +UGPIOC, +USPM, +UI2S, +UDCONF=30, +UMGC,+USGC, +UMAFE, +USAFE, +UMSEL, +USORF, +USECPRF, +UFTP,+UBMCONF, +UIPTABLES, +UWMP, Message service error result codes+CMS ERROR.
Updated estimated response time information for these commands:+URAT.

R63

29-Aug-2019

lpah

Review the command applicability for these commands: +CLAC, &H,+UMNOCONF.
Extended the document applicability to SARA-G450-00C-01, TOBY-R20042B, TOBY-R200-82B, LARA-R202-82B, LARA-R220-62B-03, LARA-R280-02B-04.
New commands: +UDCONF=59.
Modified commands: Auto-registration, &H, +CTZU, +CTZR, +CISRVCC,
H, S0, +COPS, +CREG, +URAT, +UHSDUPA, +UCELLLOCK, +UMNOCONF,+UMNOPROF, +URPM, +URPMCONF, +UIMSCFG, +UCMT3GPP2,+USIMLCK, +CPBS, +CNMI, +CMGD, +UCMGW, +CPPS, +CAAP, +IPR,&D, Z, +CRSM, +CGDCONT, +UCLASS, +CGREG, +CEREG, +UPSD,+UAUTHREQ, +UDCONF=9, +UFWINSTALL, +UADC, +UPSV, +UTEST,+URXDIV, +UTEMP, +UOMADMREP, +UNVMW, +UANT, +UNVMR,+ULGASP, GPIO introduction, +UGPIOC, File System Introduction,+UPLAYFILE, +UAPLAY, SARA-U2 Audio interface, LISA-U2 Audiointerface, +UMAFE, +UDCONF=10, Device and data security introduction,+USECMNG, +USECPRF, +UFTPC, +UHTTP, +UGPRF, +UDTMFD,+UECALLDATA, +UECALLSTAT, +UDCONF=90, +UIFCONF, Internet
suite error classes, Internal TCP/UDP/IP stack class error codes, Related
Documents.
Updated estimated response time information for these commands:

R64

31-Oct-2019

lpah

Review the command applicability for these commands: +URPM,+URPMCONF, +UDCONF=57, +UUICC, +ULGASP.
Updated the application version of TOBY-R200-82B. Extended document
applicability to TOBY-L210-65S, MPCI-L210-63S.
Modified commands: +CMUX, +CSQ, +CESQ, +COPS, +UDOPN,+UCGOPS, +UCGED, +UMNOCONF, &K, +CRSM, +CLAN, +UUICC,+CUAD, +XSIMSWITCH, +UPSDA, +CGDATA, D*, +UCLASS, +ULGASP,GPIO Introduction, +UGPIOC, File System Introduction, +URDFILE, File
System limits, +USOCR, +USOSEC, +USOCO, +USOST, +USOLI, +USODL,+UDCONF=2, +UDCONF=3, +UDCONF=5, +UDCONF=6, +UDCONF=7,+USOAO, Device and data security introduction, +USECMNG, +UFTP,+UFTPC, +UFTPER, +UHTTP, +UHTTPAC, +UHTTPC, +USMTPM, +ULOC,+UDTMFD, +UIFCONF, Mobile termination error result codes +CME
ERROR.
Review the command applicability for these commands: +UOMADM,+UOMADMALERT, +UOMADMREP, +UOMASTAT.

UBX-13002752 - R67

Revision history

Page 999 of 1001

u-blox cellular modules - AT commands manual

Revision
R65

Date
27-Jan-2020

Name
lpah

Comments
Extended document applicability to SARA-G450-01C, LARA-R203-02B-34
and TOBY-L210-03S-34.
New commands: +UDCONF=78.

R66

21-May-2020

lpah

Modified commands: AT commands settings, Information text
responses and result codes, +CMUX, +CSCS, +CPAS, +CPWROFF,+CALM, +CRSL, +CLVL, D, H, S0, Network services parameter
description, +COPS, +CGED, +UCGED, +UCELLINFO, +VZWRSRQ,+URAT, +CREG, +UBANDSEL, +UCD, +UMNOCONF, +VZWAPNE,+CPBW, +CNMI, &D, +ICF, +IFC, +IPR, O, Z, &F, +CLAN, +STKPROF,+UBIP, +UCATPROF, +CGDCONT, +CGDATA, D*, +CGREG, +CEREG,+UAUTHREQ, +UGCNTSET, +UDCONF=9, +UFWUPD, +UPSV, +USTS,+USIO, +UOMADM, +UOMADMALERT, +UOMADMREP, +UOMASTAT,+ULGASP, GPIO introduction, +USPM, +UPAR, +USAR, +UPLAYFILE,+USTOPFILE, +USODL, +USECMNG, +USECPRF, +UFTP, +UFTPC,+UHTTPAC, +UHTTPC, +UGPS, +UGPRF, +UGSRV, +UGUBX, +ULOC,+ULOCGNSS, +ULOCCELL, +UDTMFD, +UECALLCFG, +UDPDP.
Modified commands: Summary table, Switch from data mode toonline command mode, Information text responses and result codes,+CSCS, +CGSN, I, +CFUN, +CALA, +CALM, +CRSL, +CLVL, +CTZR,+CMEE, D, <RxLev>, <rscp_lev>, <ecn0_lev>, <RSRP>, <RSRQ>, <RAC>,<ul_frequency>, +COPS, +UDOPN, +CREG, +PACSP, +CGED, +UCD,+UMNOCONF, +VZWAPNE, +UMNOPROF, +CEVDP, +CPBW, +CPBR,+CPMS, +CNMI, +UDCONF=82, +CMGR, +CMGL, +CSMP, +CSCA,+CSCB, +UCMGR, +UCMGL, +CCHO, +UBIP, +CGLA, Multiple PDP
contexts, <cid>, PPP LCP handshake behaviour, +UDCONF=66, +UPSD,
D*, +CGEREP, +CGREG, +UDCONF=9, +UFWINSTALL, +UTEST, +USIO,GPIO introduction, Module status indication, Module operating modeindication, +UGPIOC, File Tags Introduction, +UDWNFILE, +URDFILE,+UDELFILE, +USPM, +UPAR, +UPLAYFILE, +USTOPFILE, SARA-G4
audio interface, +USORD, +USECMNG, +USECPRF, +UHTTP, +UHTTPC,+UGPRF, +UGTMR, +UGZDA, +UGGGA, +UGGLL, +UGGSV, +UGRMC,+UGVTG, +UGGSA, +UTIME, +UDTMFD, Networking introduction,+UBMCONF, +UIPCONF, +UIFCONF, +UIPADDR, +UIPROUTE,+UIPTABLES.
Updated estimated response time information for these commands:+USOSEC.

R67

07-Aug-2020

lpah

Review the command applicability for these commands: +USPM,+UBMCONF.
Extended document applicability to LARA-R211-02B-03. Updated
application versions for SARA-G450-00C, SARA-G450-01C, TOBY-L4 "01"and "51" product versions.
New commands: Cipher suite applicability, +UDTMFG.
Modified commands: +CMUX, +CFUN, D, H, S0, +CREG, +UCELLINFO,+URPM, +URPMCONF, +UMNOPROF, +CMGF, +CNMI, &C, &D, &S, &K,+IFC, +ICF, S3, S4, S5, X, \Q, O, +CGPIAF, +CGDCONT, +UPSD, +CGDATA,
D*, +CGREG, +UAUTHREQ, +UGCNTSET, +CEMODE, +UFWUPD,+USIO, +UPSV, +UGPIOR, +UGPIOW, File System Introduction,+UPLAYFILE, +URECFILE, +UAPLAY, +UAREC, +UEXTDCONF, TOBYL4 Audio interface, LARA-R2 / TOBY-R2 Audio interface, SARA-U2
Audio interface, +UTI, +USODL, +USECMNG, +USECPRF, +UFTP,+UGPS, +UGIND, +UGPRF, +ULOCIND, +UDTMFD, +UI2CO, +UI2CR,
Networking introduction, +UBMCONF, +UIPCONF, +UIFCONF, +UIPADDR,+UIPROUTE, +UIPTABLES.
Review the command applicability for these commands: +URPM,+URPMCONF, Z, +UFWINSTALL, +UANTR, +USTS, +URING, +USIO,+UTEMP, +UFACTORY, +UPSV, +UGPIOC, +UGPIOR, +UGPIOW,+UDWNFILE, +URDFILE, +UDELFILE, +URECFILE, +UAPLAY, +UAREC,+UTI, +UI2CO, +UI2CW, +UI2CR, +UI2CREGR, +UI2CC, +UBMCONF,+UIFCONF, +UIPROUTE, +UIPTABLES, +UDCONF=64, +UDCONF=71.

UBX-13002752 - R67

Revision history

Page 1000 of 1001

u-blox cellular modules - AT commands manual

Contact
For complete contact information, visit us at www.u-blox.com.
u-blox Offices
North, Central and South America

Headquarters

Asia, Australia, Pacific

Europe, Middle East, Africa
u-blox America, Inc.
Phone: +1 703 483 3180
E-mail: info_us@u-blox.com

u-blox AG
Phone: +41 44 722 74 44
E-mail: info@u-blox.com
Support: support@u-blox.com

u-blox Singapore Pte. Ltd.
Phone: +65 6734 3811
E-mail: info_ap@u-blox.com
Support: support_ap@u-blox.com

Regional Office West Coast:
Phone: +1 408 573 3640
E-mail: info_us@u-blox.com

Regional Office Australia:
Phone: +61 2 8448 2016
E-mail: info_anz@u-blox.com
Support: support_ap@u-blox.com

Technical Support:
Phone: +1 703 483 3185
E-mail: support_us@u-blox.com

Regional Office China (Beijing):
Phone: +86 10 68 133 545
E-mail: info_cn@u-blox.com
Support: support_cn@u-blox.com
Regional Office China (Chongqing):
Phone: +86 23 6815 1588
E-mail: info_cn@u-blox.com
Support: support_cn@u-blox.com
Regional Office China (Shanghai):Phone: +86 21 6090 4832
E-mail: info_cn@u-blox.com
Support: support_cn@u-blox.com
Regional Office China (Shenzhen):Phone: +86 755 8627 1083
E-mail: info_cn@u-blox.com
Support: support_cn@u-blox.com
Regional Office India:
Phone: +91 80 4050 9200
E-mail: info_in@u-blox.com
Support: support_in@u-blox.com
Regional Office Japan (Osaka):
Phone: +81 6 6941 3660
E-mail: info_jp@u-blox.com
Support: support_jp@u-blox.com
Regional Office Japan (Tokyo):Phone: +81 3 5775 3850
E-mail: info_jp@u-blox.com
Support: support_jp@u-blox.com
Regional Office Korea:
Phone: +82 2 542 0861
E-mail: info_kr@u-blox.com
Support: support_kr@u-blox.com
Regional Office Taiwan:
Phone: +886 2 2657 1090
E-mail: info_tw@u-blox.com
Support: support_tw@u-blox.com

UBX-13002752 - R67

Contact

Page 1001 of 1001