Network name behaviour change between Legato 18.10.3 and 19.11.6

Hello,

Our apps were scanning surrounding networks using the Modem Radio Control functions, previously on Legato 18.10.3. Now we are compiling using Legato 19.11.6 and have noticed a difference in the behaviour of le_mrc_GetCellularNetworkName(), which doesn’t return the name of the connected network but the sim card provider (in our case, for one of them, Twilio) for each of the networks.

I’ve run a network scan using AT commands just to make sure of what was returned by the modem, and the networks names are coming across as expected.

at+cops=?
+cops: (1,“Orange F”,“Orange”,“20801”,7),(1,“Orange F”,“Orange”,“20801”,2),(1,“Orange F”,“Orange”,“20801”,0),(1,“Free”,“Free”,“20816”,7),(1,“F SFR”,“SFR”,“20810”,7),(1,“F SFR”,“SFR”,“20810”,2),(1,“F SFR”,“SFR”,“20810”,0),(1,“F-Bouygues Telecom”,“BYTEL”,“20820”,2),(1,“F-Bouygues Telecom”,“BYTEL”,“20820”,7),(1,“Free”,“Free”,“20815”,2),(2,“Free”,“Free”,“20815”,7),(1,“F-Bouygues Telecom”,“BYTEL”,“20820”,0),(0,1,2,3,4),(0,1,2)

Each of those are returned as being named Twilio when coming through with the Legato API.

When running cm radio, the same occurs: the network is named Twilio instead of the expected network (probably Orange in my case).

Is there a way to retrieve the names of the network the way it worked in Legato 18.10.3?

Thanks in advance,
Best regards

EDIT: Module used is WP76

What module are you using?
Wp76? Wp77?

My testing:

root@fx30:~# cm radio
Power:                         ON
Current Network Operator:      1O1O
Current RAT:                   GSM network (LE_MRC_RAT_GSM)
Status:                        Registered, home network (LE_MRC_REG_HOME)
Signal:                        Strong signal strength (4)
PS:                            Packet Switched Registered, home network (LE_MRC_REG_HOME)

root@fx30:~# microcom /dev/ttyAT

+WDSI: 4
at+cops=?
+cops: (1,"1O1O","1O1O","45400",0),(3,"China Mobile HK","CMHK","45412",0),,(0,1,2,3,4),(0,1,2)

OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7702
Revision: SWI9X06Y_02.36.08.02 c3f5ef jenkins 2021/09/07 08:00:51
IMEI: 352653090012345
IMEI SV:  6
FSN: VU735370312345
+GCAP: +CGSM,+DS

OK
ati8
Legato Ver: 21.05.0.0d38bc34_40288ac0b0ffed9ebe2ffce8ae730a91
Yocto Ver:  SWI9X06Y_03.00.03.00 2021-11-26_12:02:26
OS Ver: Linux version 4.14.253 (oe-user@oe-host) ( gcc version 9.3.0 (GCC), GNU ld (GNU Binutils) 2.34.0.20200220) #1 PREEMPT Fri Nov 26 09:52:28 UTC 2021
LK Ver: 1.3.0_1aea4d8ec8
RootFS Ver: SWI9X06Y_03.00.03.00 2021-11-26_12:02:26
UserFS Ver: unknown
MCU Ver: 002.015

OK

Hello,

I’m using the WP76

No problem is found for WP76 with FW R16.1.




root@swi-mdm9x28-wp:~# cm radio
Power:                         ON
Current Network Operator:      1O1O
Current RAT:                   LTE network (LE_MRC_RAT_LTE)
Status:                        Registered, home network (LE_MRC_REG_HOME)
Signal:                        Very strong signal strength (5)
PS:                            Packet Switched Registered, home network (LE_MRC_REG_HOME)



at!gstatus?
!GSTATUS:
Current Time:  275              Temperature: 38
Modem Mitigate Level: 0         ModemProc Mitigate Level: 0
Reset Counter: 2                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
IMS reg state: NOT REGISTERED   IMS mode:    Normal
IMS Srv State: NO SMS,NO VoIP
LTE band:      B3               LTE bw:      20 MHz
LTE Rx chan:   1400             LTE Tx chan: 19400
LTE CA state:  INACTIVE
EMM state:     Registered       Normal Service
RRC state:     RRC Connected

PCC RxM RSSI:  -63              RSRP (dBm):  -93
PCC RxD RSSI:  -94              RSRP (dBm):  -135
Tx Power:      12               TAC:         0652 (1618)
RSRQ (dB):     -11              Cell ID:     01E5110C (31789324)
SINR (dB):      2.8

OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7608
Revision: SWI9X07Y_02.37.03.05 52ddef jenkins 2021/12/22 04:24:24
IMEI: 352913090512345
IMEI SV: 16
FSN: XG207430712345
+GCAP: +CGSM

OK
ati8
Legato Ver: 19.11.6_225ac9b7882467c5c7f9e0bf4cdb5523
Yocto Ver:  SWI9X07Y_02.37.10.02 2022-02-11_09:57:45
OS Ver: Linux version 3.18.140 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Fri Feb 11 09:40:40 UTC 2022
LK Ver: SWI9X07Y_02.37.10.02
RootFS Ver: SWI9X07Y_02.37.10.02 2022-02-11_09:57:45
UserFS Ver: unknown
MCU Ver: 002.015

OK
at+cops=?
+cops: (2,"1O1O","1O1O","45400",7),(1,"CSL","CSL","45400",2),(1,"CSL","CSL","45400",0),(1,"SmarTone HK","SMC HK","45406",7),(1,"3","3","45403",2),(1,"454 21","454 21","45421",7),(3,"China Mobile HK","CMHK","45412",7),(3,"China Mobile HK","CMHK","45413",2),(1,"SmarTone HK","SMC HK","45406",2),(3,"China Mobile HK","CMHK","45412",0),(3,"CSL","CSL","45419",2),(1,"3","3","45403",7),,(0,1,2,3,4),(0,1,2)

OK

Hello,

Unfortunately in my case it is different. The actual network used is Free, but it is returned as Twilio.

root@hhv2-000000:~# cm radio
Power:                         ON
Current Network Operator:      Twilio
Current RAT:                   LTE network (LE_MRC_RAT_LTE)
Status:                        Registered to a roaming network (LE_MRC_REG_ROAMING)
Signal:                        Strong signal strength (4)
PS:                            Packet Switched Registered to a roaming network (LE_MRC_REG_ROAMING)

root@hhv2-000000:~# microcom /dev/ttyAT
at!gstatus?
!GSTATUS:
Current Time:  2567             Temperature: 32
Modem Mitigate Level: 0         ModemProc Mitigate Level: 0
Reset Counter: 13               Mode:        ONLINE
System mode:   LTE              PS state:    Attached
IMS reg state: NOT REGISTERED   IMS mode:    Normal
IMS Srv State: NO SMS,NO VoIP
LTE band:      B7               LTE bw:      20 MHz
LTE Rx chan:   3350             LTE Tx chan: 19675
LTE CA state:  INACTIVE
EMM state:     Registered       Normal Service
RRC state:     RRC Idle

PCC RxM RSSI:  -76              RSRP (dBm):  -107
PCC RxD RSSI:  -85              RSRP (dBm):  -115
Tx Power:      --               TAC:         1908 (6408)
RSRQ (dB):     -10              Cell ID:     066E223D (107881021)
SINR (dB):     12.4

OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7607-1
Revision: SWI9X07Y_02.37.03.05 52ddef jenkins 2021/12/22 04:24:24
IMEI: 359780080104460
IMEI SV: 16
FSN: VP804370060110
+GCAP: +CGSM

OK
ati8
Legato Ver: 19.11.6_fad3770365ae470cc5d640535ed56f84
Yocto Ver:  SWI9X07Y_02.37.10.02 2022-11-22_14:28:09
OS Ver: Linux version 3.18.140 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Tue Nov 22 14:24:23 UTC 2022
LK Ver: SWI9X07Y_02.25.02.01
RootFS Ver: SWI9X07Y_02.37.10.02 2022-11-22_14:28:09
UserFS Ver: unknown
MCU Ver: 002.015

OK
at+cops=?
+cops: (1,"Orange F","Orange","20801",7),(1,"Orange F","Orange","20801",2),(1,"Orange F","Orange","20801",0),(1,"F-Bouygues Telecom","BYTEL","20820",7),(1,"Free","Free","20816",7),(1,"F-Bouygues Telecom","BYTEL","20820",0),(2,"Free","Free","20815",7),(1,"F-Bouygues Telecom","BYTEL","20820",2),(1,"F SFR","SFR","20810",2),(1,"F SFR","SFR","20810",7),(1,"F SFR","SFR","20810",0),(1,"Free","Free","20815",2),,(0,1,2,3,4),(0,1,2)

OK
at+cops?
+cops: 1,0,"Free Twilio",7

OK

Could it be due to the fact that it’s not the home network? Do you see something different if you connect to a roaming network?

I’ve just tested with an Hologram sim card and get the same behaviour.

Note that this used to work properly on Legato 18.10.3

It is registering on below operator:
2,"Free","Free","20815",7

I believe this is “Twilio”

What do you see in legato 18?

Twilio is the sim card provider, which allows to roam on many networks. We use Twilio sim cards in our product in many countries.

Free is one of the networks available for me just now, just like China Mobile HK for you.

I believe that if you used a Twilio sim card you may see the same issue, despite being connected to 1O1O or China Mobile HK.

In legato 18, the network name returned was Free, Orange, or other value as returned by AT+COPS=? (depending on the network my board connected to).

i don’t have roaming sim card…
Can you take a SIM card that register to home network and see if it shows correctly?

Same sequence using Legato 18.10.3

Note that the network name is correctly returned by cm radio, using the same sim card but with the previous legato framework. This would be a regression in 19.11 unfortunately.

root@hhv2-000000:~# cm radio
Power:                         ON
Current Network Operator:      Free
Current RAT:                   LTE network (LE_MRC_RAT_LTE)
Status:                        Registered to a roaming network (LE_MRC_REG_ROAMING)
Signal:                        Strong signal strength (4)
PS:                            Packet Switched Registered to a roaming network (LE_MRC_REG_ROAMING)

root@hhv2-000000:~# microcom /dev/ttyAT
at!gstatus?
!GSTATUS:
Current Time:  2750             Temperature: 34
Modem Mitigate Level: 0         ModemProc Mitigate Level: 0
Reset Counter: 1                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
IMS reg state: NOT REGISTERED   IMS mode:    Normal
IMS Srv State: NO SMS,NO VoIP
LTE band:      B7               LTE bw:      20 MHz
LTE Rx chan:   3350             LTE Tx chan: 19675
LTE CA state:  INACTIVE
EMM state:     Registered       Normal Service
RRC state:     RRC Idle

PCC RxM RSSI:  -74              RSRP (dBm):  -104
PCC RxD RSSI:  -83              RSRP (dBm):  -116
Tx Power:      --               TAC:         1908 (6408)
RSRQ (dB):     -10              Cell ID:     066E223D (107881021)
SINR (dB):     13.2

OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7607-1
Revision: SWI9X07Y_02.37.03.05 52ddef jenkins 2021/12/22 04:24:24
IMEI: 359780080104460
IMEI SV: 16
FSN: VP804370060110
+GCAP: +CGSM

OK
[ 2758.509978] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090

Legato Ver: 18.10.3_bc1bbbb25a579ea3218b3407be6e3503
Yocto Ver:  SWI9X07Y_02.25.04.01 2022-09-21_09:45:09
OS Ver: Linux version 3.18.122-HomeHub_Custom_2.1.1 (ubuntu@ip-10-11-8-182) (gcc version 6.2.0 (GCC) ) #2 PREEMPT Wed Sep 21 09:45:47 UTC 2022
LK Ver: SWI9X07Y_02.25.02.01
RootFS Ver: SWI9X07Y_02.25.04.01 2022-09-21_09:45:09
UserFS Ver: unknown
MCU Ver: 002.011

OK
at+cops=?
+cops: (1,"Orange F","Orange","20801",7),(1,"Orange F","Orange","20801",2),(1,"Orange F","Orange","20801",0),(2,"Free","Free","20815",7),(1,"F SFR","SFR","20810",7),(1,"F-Bouygues Telecom","BYTEL","20820",2),(1,"Free","Free","20815",2),(1,"F SFR","SFR","20810",2),(1,"F SFR","SFR","20810",0),(1,"F-Bouygues Telecom","BYTEL","20820",7),(1,"F-Bouygues Telecom","BYTEL","20820",0),(3,"Free","Free","20816",7),,(0,1,2,3,4),(0,1,2)

OK
at+cops?
+cops: 1,0,"Free Twilio",7

OK


Another example using an O2 sim card in UK, with Legato 19.11.6. The difference here is the sim card used (an O2 sim card instead of a Twilio sim).

root@hhv2-pavel-02:~# cm radio
Power:                         ON
Current Network Operator:      O2 - UK
Current RAT:                   LTE network (LE_MRC_RAT_LTE)
Status:                        Registered to a roaming network (LE_MRC_REG_ROAMING)
Signal:                        Very strong signal strength (5)
PS:                            Packet Switched Registered, home network (LE_MRC_REG_HOME)

root@hhv2-pavel-02:~# microcom /dev/ttyAT
at!gstatus?
!GSTATUS:
Current Time:  966              Temperature: 31
Modem Mitigate Level: 0         ModemProc Mitigate Level: 0
Reset Counter: 6                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
IMS reg state: NOT REGISTERED   IMS mode:    Normal
IMS Srv State: NO SMS,NO VoIP
LTE band:      B1               LTE bw:      10 MHz
LTE Rx chan:   199              LTE Tx chan: 18199
LTE CA state:  INACTIVE
EMM state:     Registered       Normal Service
RRC state:     RRC Idle

PCC RxM RSSI:  -50              RSRP (dBm):  -80
PCC RxD RSSI:  -52              RSRP (dBm):  -81
Tx Power:      --               TAC:         C270 (49776)
RSRQ (dB):     -10              Cell ID:     00109E90 (1089168)
SINR (dB):      2.2

OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7607-1
Revision: SWI9X07Y_02.37.03.05 52ddef jenkins 2021/12/22 04:24:24
IMEI: 359780080926094
IMEI SV: 16
FSN: V2015287241310
+GCAP: +CGSM

OK
ati8
Legato Ver: 19.11.6_fad3770365ae470cc5d640535ed56f84
Yocto Ver:  SWI9X07Y_02.37.10.02 2022-11-22_14:28:09
OS Ver: Linux version 3.18.140 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Tue Nov 22 14:24:23 UTC 2022
LK Ver: SWI9X07Y_02.37.10.02
RootFS Ver: SWI9X07Y_02.37.10.02 2022-11-22_14:28:09
UserFS Ver: unknown
MCU Ver: 002.015

OK
at+cops=?
+cops: (2,"O2 - UK","O2 - UK","23410",7),(1,"O2 - UK","O2 - UK","23410",2),(1,"O2 - UK","O2 - UK","23410",0),(3,"EE","EE","23430",7),(3,"vodafone UK","voda UK","23415",0),(3,"234 32","234 32","23432",7),(3,"vodafone UK","voda UK","23415",2),(3,"EE","EE","23430",0),(3,"3 UK","3 UK","23420",2),(3,"3 UK","3 UK","23420",7),(3,"vodafone UK","voda UK","23415",7),(3,"EE","EE","23430",2),,(0,1,2,3,4),(0,1,2)

OK
at+cops?
+cops: 1,0,"O2 - UK",7

OK

Can you take a SIM card that register to home network and see if it shows correctly?
I wonder if this API is for home network only according to the API guide.

Did you try to use le_mrc_GetCurrentNetworkMccMnc() and le_mrc_GetCellularNetworkName() to get the name?

Can you take a SIM card that register to home network and see if it shows correctly?

I don’t have a sim card for that unfortunately, we don’t use those with our product.

I wonder if this API is for home network only according to the API guide.

Would that be a new feature / limit from 19.11? Again, this was not the case in Legato 18.10.

Did you try to use le_mrc_GetCurrentNetworkMccMnc() and le_mrc_GetCellularNetworkName() to get the name?

Yes.
le_mrc_GetCurrentNetworkMccMnc() works correctly in both 18.10 and 19.11.
le_mrc_GetCellularNetworkName() works correctly in 18.10 but not in 19.11 (same as what is displayed with cm radio)

Are you using the code here for network scan?

Yes I am. Is there another way to retrieve the name of the network available within 19.11?

will you consider getting the response of AT+COPS? within legato application? (send through /dev/ttyAT)

Here is an example of sending AT!BSGPIO command to read the status in legato application:

Accordin to this page, using AT commands directly may conflict with legato APIs.

Warning
Some AT commands may conflict with Legato APIs; using both may cause problems that can be difficult to diagnose. AT commands should be avoided whenever possible, and should only be used with great care.

Is this safe to do?

I think it is ok as this is just query AT command

Is there more information on which AT commands are safe to use and which ones are not?