Quectel BC26 User manual

BC26
AT Commands Manual
NB-IoT Module Series
Rev. BC26_AT_Commands_Manual_V1.1
Date: 2018-01-25
Status: Preliminary
www.quectel.com

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 1 / 73
Our aim is to provide customers with timely and comprehensive service. For any
assistance, please contact our company headquarters:
Quectel Wireless Solutions Co., Ltd.
7th Floor, Hongye Building, No.1801 Hongmei Road, Xuhui District, Shanghai 200233, China
Tel: [phone]
Email: [email protected]om
Or our local office. For more information, please visit:
http://quectel.com/support/sales.htm
For technical support, or to report documentation errors, please visit:
http://quectel.com/support/technical.htm
Or email to: [e-mail]
GENERAL NOTES
QUECTEL OFFERS THE INFORMATION AS A SERVICE TO ITS CUSTOMERS. THE INFORMATION
PROVIDED IS BASED UPON CUSTOMERS’ REQUIREMENTS. QUECTEL MAKES EVERY EFFORT
TO ENSURE THE QUALITY OF THE INFORMATION IT MAKES AVAILABLE. QUECTEL DOES NOT
MAKE ANY WARRANTY AS TO THE INFORMATION CONTAINED HEREIN, AND DOES NOT ACCEPT
ANY LIABILITY FOR ANY INJURY, LOSS OR DAMAGE OF ANY KIND INCURRED BY USE OF OR
RELIANCE UPON THE INFORMATION. ALL INFORMATION SUPPLIED HEREIN IS SUBJECT TO
CHANGE WITHOUT PRIOR NOTICE.
COPYRIGHT
THE INFORMATION CONTAINED HERE IS PROPRIETARY TECHNICAL INFORMATION OF
QUECTEL WIRELESS SOLUTIONS CO., LTD. TRANSMITTING, REPRODUCTION, DISSEMINATION
AND EDITING OF THIS DOCUMENT AS WELL AS UTILIZATION OF THE CONTENT ARE
FORBIDDEN WITHOUT PERMISSION. OFFENDERS WILL BE HELD LIABLE FOR PAYMENT OF
DAMAGES. ALL RIGHTS ARE RESERVED IN THE EVENT OF A PATENT GRANT OR
REGISTRATION OF A UTILITY MODEL OR DESIGN.
Copyright © Quectel Wireless Solutions Co., Ltd. 2018. All rights reserved.

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 2 / 73
About the Document
History
Revision
Date
Author
Description
1.0
2018-01-05
Randy LI/
Lebron LIU
Initial
1.1
2018-01-25
Lebron LIU
Modified the Description of Some AT Commands

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 4 / 73
Contents
About the Document...................................................................................................................................2
Contents.......................................................................................................................................................4
Table Index...................................................................................................................................................6
1Introduction..........................................................................................................................................7
1.1. Scope of the Document.............................................................................................................7
1.2. AT Command Syntax.................................................................................................................7
1.3. Supported Character Sets.........................................................................................................8
23GPP Commands (27.007) ..................................................................................................................9
2.1. ATI Display Product Identification Information........................................................................9
2.2. ATE Set Command Echo Mode............................................................................................10
2.3. AT+CGMI Request Manufacturer Identification....................................................................11
2.4. AT+CGMM Request Manufacturer Model............................................................................11
2.5. AT+CGMR Request Manufacturer Revision.........................................................................12
2.6. AT+CESQ Extended Signal Quality......................................................................................13
2.7. AT+CGSN Request Product Serial Number Identification ...................................................15
2.8. AT+CEREG EPS Network Registration Status.....................................................................16
2.9. AT+CSCON Signalling Connection Status ...........................................................................19
2.10. AT+COPS Operator Selection..............................................................................................21
2.11. AT+CGATT GPRS/Packet Domain Attach/Detach ...............................................................24
2.12. AT+CGDCONT Define the PDP Context..............................................................................25
2.13. AT+CGACT PDP ContextActivation/Deactivation................................................................29
2.14. AT+CGPADDR Show PDPAddresses .................................................................................31
2.15. AT+CIMI Request International Mobile Subscriber Identity..................................................32
2.16. AT+CFUN Set Phone Functionality ......................................................................................33
2.17. AT+CMEE Report Mobile Termination Error.........................................................................34
2.18. AT+CPSMS Power Saving Mode Setting.............................................................................35
2.19. AT+CEDRXS eDRX Setting..................................................................................................37
2.20. AT+CEDRXRDP eDRX Read Dynamic Parameters............................................................40
2.21. AT+CEER Extended Error Report ........................................................................................42
3PDN Commands.................................................................................................................................44
3.1. AT+QGACT Activate/Deactivate a PDN Context .................................................................44
4Network Commands –PING.............................................................................................................47
4.1. AT+QPING Test IP Network Connectivity to a Remote Host ...............................................47
5Network Commands –Socket..........................................................................................................48
5.1. AT+QSOC Create a TCP/UDP Socket.................................................................................48
5.2. AT+QSOB Bind Local Address and Local Port.....................................................................49
5.3. AT+QSOCON Connect Socket to RemoteAddress and Port..............................................49
5.4. AT+QSOSEND Send Data to Remote via Socket..............................................................50
5.5. AT+QSODIS Disconnect Socket...........................................................................................51

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 5 / 73
5.6. AT+QSOCL Close Socket.....................................................................................................51
5.7. +QSONMI Socket Message Arrived Indicator......................................................................52
5.8. +QSOERR Socket Error Indicator........................................................................................52
5.9. Examples.................................................................................................................................53
5.9.1. Example of Creating a TCP Socket (Do Not Support Now)..........................................53
5.9.2. Example of Creating a UDP Socket Example...............................................................53
6General Commands...........................................................................................................................55
6.1. AT+QBAND Query Current Operating Band ........................................................................55
6.2. AT+QRESET Reset UE...........................................................................................................55
6.3. AT+QSPCHSC Set Scrambling Algorithm...............................................................................56
6.4. AT+QFRCLLCK Frequency & Cell Lock...............................................................................57
6.5. AT+QNBIOTRAI NB-IoT Release Assistance Indication......................................................58
6.6. AT+QATWAKEUP Enable Deep Sleep Wakeup Indication..................................................58
6.7. AT+QENGINFO Query Current Network Status...................................................................59
7OneNET Commands..........................................................................................................................63
7.1. AT+MIPLCREATE Create OneNET Instance.......................................................................63
7.2. AT+MIPLDELETE Delete OneNET Instance........................................................................64
7.3. AT+MIPLADDOBJ Add LWM2M Object...............................................................................64
7.4. AT+MIPLDELOBJ Delete LWM2M Object............................................................................65
7.5. AT+MIPLOPEN Send OneNET Login Request....................................................................65
7.6. AT+MIPLCLOSE Send OneNET Logout Request................................................................66
7.7. AT+MIPLREADRSP Respond the Read Request from Application Server/IoT Platform ....66
7.8. AT+MIPLWRITERSP Respond the Write Request from Application Server/IoT Platform ...67
7.9. AT+MIPLEXECUTERSP Respond the Execute Request from Application Server/IoT
Platform................................................................................................................................................68
7.10. AT+MIPLOBSERVERSP Respond the Observe Request from Application Server/IoT
Platform................................................................................................................................................68
7.11. AT+MIPLNOTIFY Notify the Data to Application Server or IoT Platform..............................69
7.12. AT+MIPLUPDATE Send Update Request............................................................................70
7.13. AT+MIPLVER Query the OneNET Version...........................................................................71
8Appendix A Reference.......................................................................................................................72

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 6 / 73
Table Index
TABLE 1: TYPES OF AT COMMANDS AND RESPONSES ............................................................................... 8
TABLE 2: TERMS AND ABBREVIATIONS........................................................................................................ 72

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 7 / 73
1Introduction
1.1. Scope of the Document
This document gives details of theAT Command Set supported by Quectel NB-IoT BC26 module.
1.2. AT Command Syntax
The “AT”or “at” prefix must be set at the beginning of each command line. To terminate a command line
enter <CR>. Commands are usually followed by a response that includes
“<CR><LF><response><CR><LF>”. Throughout this document, only the responses are presented,
“<CR><LF>” are omitted intentionally.
The AT Commands Set implemented by BC26 is a combination of 3GPP TS 27.005, 3GPP TS 27.007
and ITU-T recommendation V.250 as well as theAT Commands developed by Quectel.
All these AT commands can be split into three categories syntactically: “basic”, “S parameter”, and
“extended”. They are listed as follows:
Basic syntax
These AT commands have the format of “AT<x><n>”, or “AT&<x><n>”, where “<x>” is the command, and
“<n>” is/are the argument(s) for that command. An example of this is “ATE<n>”, which tells the DCE
whether received characters should be echoed back to the DTE according to the value of “<n>”. “<n>” is
optional and a default will be used if it is missing.
S parameter syntax
These AT commands have the format of “ATS<n>=<m>”, where “<n>” is the index of the S register to set,
and “<m>” is the value to assign to it. “<m>” is optional; if it is missing, then a default value is assigned.
Extended syntax
These commands can be operated in several modes, as following table:

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 8 / 73
Table 1: Types of AT Commands and Responses
Each time a single AT command is supported. When execution of the previous AT command is finished,
the nextAT command will be executed.
1.3. Supported Character Sets
The BC26 AT command interface defaults to the IRA character set. The BC26 supports the following
character sets:
GSM
UCS2
HEX
IRA
PCCP437
PCDN
8859-1
The character set can be configured and interrogated using the AT+CSCS command (3GPP TS 27.007).
The character set is defined in 3GPP specification 27.005.
Test Command
AT+<x>=?
This command returns the list of parameters and value ranges
set by the corresponding Write Command or internal
processes.
Read Command
AT+<x>?
This command returns the currently set value of the parameter
or parameters.
Write Command
AT+<x>=<…>
This command sets the user-definable parameter values.
Execution
Command
AT+<x>
This command reads non-variable parameters affected by
internal processes in the module.
NOTE

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 9 / 73
23GPP Commands (27.007)
2.1. ATI Display Product Identification Information
Parameter
Example
ATI
Quectel_Ltd
Quectel_BC26
Revision: BC26NAR01A01
OK
ATIDisplay Product Identification Information
Execution Command
ATI
Response
Quectel_Ltd
<Object Id>
Revision:<revision>
OK
If there is any error, response:
+CME ERROR:<err>
<Object Id> Identifier of device type
<revision> Revision of software release

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 10 / 73
2.2. ATE Set Command Echo Mode
Parameter
Example
ATE0
OK
ATI
Quectel_Ltd
Quectel_BC26
Revision: BC26NAR01A01
OK
ATE1
OK
ATI
ATI
Quectel _Ltd
Quectel_BC26
Revision: BC26NAR01A01
OK
ATE Set Command Echo Mode
Execution Command
ATE[<value>]
Response
OK
If there is any error, response:
+CME ERROR:<err>
<value> 0 Echo mode OFF
1Echo mode ON

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 11 / 73
2.3. AT+CGMI Request Manufacturer Identification
Parameter
Example
AT+CGMI
Quectel_Ltd
Quectel_BC26
Revision: MTK_2625
OK
2.4. AT+CGMM Request Manufacturer Model
AT+CGMI Request Manufacturer Identification
Execution Command
AT+CGMI
Response
Quectel_Ltd
<Object Id>
Revision: MTK_2625
OK
If there is any error, response:
+CME ERROR:<err>
Test Command
AT+CGMI=?
Response
OK
<Object Id> Identifier of device type
AT+CGMM Request Manufacturer Model
Execution Command
AT+CGMM
Response
<Object Id>
OK
If there is any error, response:
+CME ERROR:<err>

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 12 / 73
Parameter
Example
AT+CGMM
Quectel_BC26
OK
2.5. AT+CGMR Request Manufacturer Revision
Parameter
Example
AT+CGMR
Revision: BC26NAR01A01
OK
Test Command
AT+CGMM=?
Response
OK
<Object Id> Identifier of device type
AT+CGMR Request Manufacturer Revision
Execution Command
AT+CGMR
Response
Revision :<revision>
OK
If there is any error, response:
+CME ERROR:<err>
Test Command
AT+CGMR=?
Response
OK
<revision> Revision of software release

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 13 / 73
2.6. AT+CESQ Extended Signal Quality
The execution command returns received signal quality parameters. If the current serving cell is not a
GERAN cell, <rssi> and <ber> are set to value 99. If the current serving cell is not a UTRA FDD or UTRA
TDD cell, <rscp> is set to 255. If the current serving cell is not a UTRA FDD cell, <ecno> is set to 255. If
the current serving cell is not an E-UTRA cell, <rsrq> and <rsrp> are set to 255.
Parameter
AT+CESQ Extended Signal Quality
Execution Command
AT+CESQ
Response
+CESQ: <rxlev>,<ber>,<rscp>,<ecno>,<rsrq>,<rsrp>
OK
If there is any error, response:
+CME ERROR:<err>
Test Command
AT+CESQ=?
Response
+CESQ: (list of supported <rxlev>s), (list of supported
<ber>s), (list of supported <rscp>s), (list of supported
<ecno>s), (list of supported <rsrq>s), (list of supported
<rsrp>s)
OK
<rxlev> Integer type. Rx signal strength level
0 -110 dBm or less
1 -110 dBm ≤<rssi> < -109 dBm
2 -109 dBm ≤<rssi> < -108 dBm
….: ….
61 -50dBm ≤<rssi> < -49 dBm
62 -49dBm ≤<rssi> < -48 dBm
63 -48dBm ≤<rssi>
99 not known or not detectable
<ber> Integer type; channel bit error rate (in percent)
0…7 as RXQUAL values RXQUAL_0…RXQUAL_7 as defined in 45.008.
99 not known or not detectable
<rscp> Integer type, received signal code power (see 3GPP 25.133 and 3GPP 25.123)
0 -120 dBm or less
1 -120 dBm ≤<rscp> < -119 dBm
2 -119 dBm ≤<rscp> < -118 dBm
…: …

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 14 / 73
Example
AT+CESQ
+CESQ: 15,99,255,255,8,30
OK
94 -27 dBm ≤<rscp> < -26 dBm
95 -26 dBm ≤<rscp> < -25 dBm
96 -25 dBm ≤<rscp>
255 not known or not detectable
<ecno> Integer type, Ec/No (see 3GPP 25.133)
0 -24 dBm or less
1 -24dBm ≤<ecno> < -23.5 dBm
2 -23.5dBm ≤<ecno> < -23 dBm
…: …
47 -1dBm ≤<ecno> < -0.5 dBm
48 -0.5dBm ≤<ecno> < 0 dBm
49 0 dBm ≤<ecno>
255 not known or not detectable
<rsrq> Integer type, reference signal received quality (see 3GPP 36.133)
0 -19.5 dB or less
1 -19.5dB ≤<rsrq> < -19 dB
2 -19dB ≤<rsrq> < -18.5 dB
…: …
32 -4 dB ≤<rsrq>< -3.5 dB
33 -3.5 dB ≤<rsrq> < -3 dB
34 -3 dB ≤<rsrq>
255 not known or not detectable
<rsrp> Integer type, reference signal received power (see 3GPP 36.133)
0 -140 dBm or less
1 -140dBm ≤<rsrp> < -139 dBm
2 -139dBm ≤<rsrp> < -138 dBm
…: …
95 -46dBm ≤<rsrp> < -45 dBm
96 -45dBm ≤<rsrp> < -44 dBm
97 -44dBm ≤<rsrp>
255 not known or not detectable

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 15 / 73
2.7. AT+CGSN Request Product Serial Number Identification
Parameter
AT+CGSN Request Product Serial Number Identification
Execution/Write Command
AT+CGSN[=<snt>]
Response
When <snt>=0 (or omitted) and command is executed
successfully:
<sn>
When <snt>=1 and command is executed successfully:
+CGSN:<imei>
When <snt>=2 and command is executed successfully:
+CGSN:<imeisv>
When <snt>=3 and command is executed successfully:
+CGSN:<svn>
OK
If there is any error, response:
+CME ERROR:<err>
Test Command
AT+CGSN=?
Response
When TE supports <snt> and command is executed
successfully:
+CGSN:(list of supported <snt>s)
OK
<snt> Integer type indicating the serial number type that has been requested
0 Returns <sn>
1 Returns the IMEI number
2 Returns the IMEISV (International Mobile station Equipment Identity and Software
Version) number
3 Returns the SVN (Software Version Number)
<sn> The 128-bit UUID of the UE. The total number of characters, including line terminators. In
the information text shall not exceed 2048 characters, and shall not contain the sequence 0
<CR> or OK<CR>.
<imei> String type in decimal format indicating the IMEI number
<imeisv> String type in decimal format indicating the IMEISV
<svn> String type in decimal format indicating the current SVN which is a part of IMEISV

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 16 / 73
2.8. AT+CEREG EPS Network Registration Status
The set command controls the presentation of an unsolicited result code (URC) “+CEREG:<stat>” when
<n>=1 and there is a change in the MT's EPS network registration status in E-UTRAN, or unsolicited
result code “+CEREG:<stat>[,[<tac>],[<ci>],[<AcT>]]” when <n>=2 and there is a change of the network
cell in E-UTRAN. The parameters <AcT>, <tac> and <ci> are provided only if available. The value <n>=3
further extends the unsolicited result code with [,<cause_type>,<reject_cause>], when available, when
the value of <stat> changes.
If the UE requests PSM for reducing its power consumption, the set command controls the presentation of
an unsolicited result code: “+CEREG:<stat>[,[<tac>],[<ci>],[<AcT>][,[<cause_type>],[<reject_cause>][,
[<Active-Time>],[<Periodic-TAU>]]]]”.
When <n>=4, the unsolicited result code will provide the UE with additional information for the active time
value and the extended periodic TAU value if there is a change of the network cell in E-UTRAN. The value
<n>=5 further enhances the unsolicited result code with <cause_type> and <reject_cause> when the
value of <stat> changes. The parameters <AcT>, <tac>, <ci>, <cause_type>, <reject_cause>,
<Active-Time> and <Periodic-TAU> are provided only if available.
The read command returns the status of result code presentation and an integer <stat> which shows
whether the network has currently indicated the registration of the MT. Location information elements
<tac>, <ci> and <AcT>, if available, are returned only when <n>=2 and MT is registered on the network.
The parameters [,<cause_type>,<reject_cause>], if available, are returned when <n>=3.
The test command returns supported parameter values.
AT+CEREG EPS Network Registration Status
Write Command
AT+CEREG=[<n>]
Response
OK
If there is any error, response:
+CME ERROR:<err>
Read Command
AT+CEREG?
Response
When <n>=0, 1, 2 or 3 and command is executed
successfully:
+CEREG:<n>,<stat>[,[<tac>],[<ci>],[<AcT>[,<cause_type>
,<reject_ cause>]]]
When <n>=4 or 5 and command is executed successfully:
+CEREG:<n>,<stat>[,[<lac>],[<ci>],[<AcT>],[<rac>][,[<cau
se_type>],[<reject_cause>][,[<Active-Time>],[<Periodic-T
AU>]]]]

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 17 / 73
Parameter
If there is any error, response:
+CME ERROR:<err>
Test Command
AT+CEREG=?
Response
+CEREG:(list of supported <n>s)
OK
<n> Integer type
0 Disable network registration unsolicited result code
1 Enable network registration unsolicited result code: “+CEREG:<stat>”
2 Enable network registration and location information unsolicited result code:
“+CEREG:<stat>[,[<tac>],[<ci>],[<AcT>]]”
3 Enable network registration, location information and EMM cause value information
unsolicited result code:
“+CEREG:<stat>[,[<tac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]]”
4 For a UE that requests PSM, enable network registration and location information
unsolicited result code:
“+CEREG:<stat>[,[<tac>],[<ci>],[<AcT>][,,[,[<Active-Time>],[<Periodic-TAU>]]]]”
5 For a UE that requests PSM, enable network registration, location information and
EMM cause value information unsolicited result code:
+CEREG:<stat>[,[<lac>],[<ci>],[<AcT>],[<rac>][,[<cause_type>],[<reject_cause>][,[<A
c tive-Time>],[<Periodic-RAU>]]]]
<stat> Integer type, indicates the EPS registration status
0 Not registered, MT is not currently searching an operator to register to
1 Registered, home network
2 Not registered, but MT is currently trying to attach or searching an operator to register
to
3 Registration denied
4 Unknown
5 Registered, roaming
6 Registered for “SMS only”, home network (applicable only when
<Act> indicates NB-IoT)
7 Registered for “SMS only”, roaming (applicable only when
<Act> indicates NB-IoT
8 Attached for emergency bearer services only
9 Registered for “CSFB not preferred”, home network (not applicable)
10 Registered for “CSFB not preferred”, roaming (not applicable)
<tac> String type; two bytes tracking area code in hexadecimal format (e.g. “00C3” equals 195 in
decimal)
<ci> String type; four bytes E-UTRAN cell ID in hexadecimal format

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 18 / 73
<AcT> Integer type; access technology of the registered network
0 GSM (not applicable)
1 GSM Compact (not applicable)
2 UTRAN (not applicable)
3 GSM w/EGPRS (not applicable)
4 UTRAN w/HSDPA (not applicable)
5 UTRAN w/HSUPA (not applicable)
6 UTRAN w/HSDPA and HSUPA (not applicable)
7 E-UTRAN
8 EC-GSM-IoT (A/Gb mode) (see NOTES 5) (not applicable)
9 E-UTRAN (NB-S1 mode) (see NOTES 6)
<cause_type> Integer type; indicates the type of <reject_cause>
0 Indicates that <reject_cause> contains an EMM cause value
1 Indicates that <reject_cause> contains a manufacturer-specific cause value
<reject_cause> Integer type; contains the cause of the failed registration. The value is of type as
defined by <cause_type>.
<Active-Time> String type; one byte in an 8-bit format. Indicates the active time value (T3324)
allocated to the UE in E-UTRAN. The 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, please refer to the GPRS Timer 2 IE
in 3GPP TS 24.008 Table 10.5.163/3Gpp TS 24.008, 3GPP TS 23.682 and 3GPP TS
23.401.
Bits 5 to 1 represent the binary coded timer value.
Bits 6 to 8 defines the timer value unit for the GPRS timer as follows:
Bits
8 7 6
0 0 0 value is incremented in multiples of 2 seconds
0 0 1 value is incremented in multiples of 1 minute
0 1 0 value is incremented in multiples of decihours
1 1 1 value indicates that the timer is deactivated.
<Periodic-TAU> String type; one byte in an 8-bit format. Indicates the extended periodic TAU value
(T3412) allocated to the UE in E-UTRAN. The extended periodic TAU value is coded
as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format
(e.g. “01000111” equals 70 hours). For the coding and the value range, please refer to
the GPRS Timers 3 IE in 3GPP TS 24.008 Table 10.5.163a/3GPP TS 24.008, 3GPP
TS 23.682 and 3GPP TS 23.401.
Bits 5 to 1 represent the binary coded timer value
Bits 6 to 8 define the timer value unit as follows:
Bits
8 7 6
0 0 0 value is incremented in multiples of 10 minutes
0 0 1 value is incremented in multiples of 1 hour
0 1 0 value is incremented in multiples of 10 hours
0 1 1 value is incremented in multiples of 2 seconds

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 19 / 73
1. If the EPS MT in GERAN/UTRAN/E-UTRAN also supports circuit mode services and/or GPRS
services, the AT+CREG command and AT+CGREG command can be used to query the registration
status and location information for those services.
2. 3GPP TS 24.008 and 3GPP TS 24.301 specify the condition when the MS is considered as attached
for emergency bearer services.
3. 3GPP TS 44.060 specifies the system information messages which give the information about
whether the serving cell supports EGPRS.
4. 3GPP TS 25.331 specifies the system information blocks which give the information about whether
the serving cell supports HSDPAor HSUPA.
5. 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates
that the serving cell supports EC-GSM-IoT.
6. 3GPP TS 36.331 [86] specifies the system information blocks which give the information about
whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode).
Example
AT+CEREG=1 //Enable network registration URC.
OK
AT+CEREG?
+CEREG:1,1
OK
AT+CEREG=?
+CEREG:(0-5)
OK
2.9. AT+CSCON Signalling Connection Status
The command gives details of the terminal‟s perceived radio connection status (i.e. to the base station). It
returns an indication of the current state. Please note that this state is only updated when radio events,
such as sending and receiving, take place. This means that the current state may be out of date. The
terminal may think it is "Connected" yet cannot currently use a base station due to a change in the link
1 0 0 value is incremented in multiples of 30 seconds
1 0 1 value is incremented in multiples of 1 minute
1 1 0 value is incremented in multiples of 320 hours
1 1 1 value indicates that the timer is deactivated
NOTES

NB-IoT Module Series
BC26 AT Commands Manual
BC26_AT_Commands_Manual 20 / 73
quality.
The set command controls the presentation of an unsolicited result code. If <n>=1, “+CSCON:<mode>” is
sent from the MT when the connection mode of the MT is changed. When the MT is in UTRAN or
E-UTRAN, the mode of the MT refers to idle when no PS signaling connection and to connected mode
when a PS signalling connection between UE and network is setup.
When the UE is in GERAN, the mode refers to idle when the MT is in either the idle state or the standby
state and to connected mode when the MT is in ready state.
The read command returns the status of result code presentation and an integer <mode> which shows
whether the MT is currently in idle mode or connected mode.
The test command returns supported values as a compound value.
Parameter
Example
AT+CSCON Signalling Connection Status
Write command
AT+CSCON=[<n>]
Response
OK
If there is any error, response:
+CME ERROR:<err>
Read Command
AT+CSCON?
Response
+CSCON:<n>,<mode>[,<state>]
OK
If there is any error, response:
+CME ERROR:<err>
Test Command
AT+CSCON=?
Response
+CSCON:(list of supported <n>s)
OK
<n> Integer type
0 Disable unsolicited result code
1 Enable unsolicited result code: “+CSCON:<mode>”
<mode> Integer type; indicates the signalling connection status
0 Idle
1 Connected