Debugging connectivity for Telus network

IoT Modules LTE-A Module
1

Hi,

I am trying to debug a connectivity behavior difference between two modules:

A)
model: EM06-A
| firmware revision: EM06ALAR04A01M4G
| carrier config: Telus-Commercial
| carrier config revision: 0680FE01
| h/w revision: EM06-A

B)
model: EM06-A
| firmware revision: EM06ALAR03A05M4G
| carrier config: ROW_Generic_3GPP
| carrier config revision: 06010821
| h/w revision: EM06-A

During our test on the field with a drivetest IOT module B had overall better performance staying connected than module A , I would like to know/ understand Firmware differences between both and the cofig difference between ROW_Generic_3GPP and Telus-Commercial .

2

Hi,

Thank you for providing the module information.

The two modules are currently running under different software conditions:

  • Module A: EM06ALAR04A01M4G with Telus-Commercial

  • Module B: EM06ALAR03A05M4G with ROW_Generic_3GPP

EM06ALAR04A01M4G is a later firmware branch than EM06ALAR03A05M4G. However, the firmware version alone cannot explain the field-test result because the active carrier configuration is also different.

Regarding the carrier configurations:

  • Telus-Commercial is an operator-specific MBN profile containing configuration items intended for the TELUS network.

  • ROW_Generic_3GPP is the generic 3GPP profile normally used as a fallback when no matching operator-specific profile is selected.

The MBN profile can apply different operator-related NV and EFS configurations. Therefore, it may affect network registration, IMS services and other modem behaviour. However, the detailed internal parameter differences between these two MBN files are not publicly documented.

Please also note that EM06ALAR03A05M4G already contains both of the following profiles:

  • ROW_Generic_3GPP, version 0x06010821

  • Telus-Commercial, version 0x0680FE01

Therefore, please provide the following results from both modules:

ATI
AT+QMBNCFG="AutoSel"
AT+QMBNCFG="List"
AT+QCFG="band"
AT+QCFG="nwscanmode"
AT+QCFG="nwscanseq"
AT+COPS?
AT+CEREG?
AT+CGREG?
AT+QNWINFO
AT+QENG="servingcell"
AT+QCAINFO
AT+CGDCONT?

Please also clarify what “staying connected” means in this test:

  1. The module loses LTE registration.

  2. LTE remains registered, but the PDP/data connection is lost.

  3. The module remains connected, but ping or application traffic stops.

  4. The module takes longer to recover after entering a weak-signal area.

For a valid comparison, both modules should be tested with the same firmware, active MBN, SIM card, APN, band configuration, antenna setup and test route. Preferably, the same SIM should be moved between the modules for sequential testing.

If the issue can still be reproduced under identical conditions, please capture log from before the disconnection until the module reconnects. This will allow us to determine whether the difference is caused by cell reselection, registration rejection, radio-link failure or data-session recovery.

Regards,
Fazrul Redzuan