Format of AT%XOPNAME operator name notification

RE: Format of AT%XOPNAME operator name notification

Hakon — Mon, 28 Jun 2021 13:54:39 GMT

The ticket in question is private, and this quote is not taken from the ticket directly. It's from an internal discussion.

RE: Format of AT%XOPNAME operator name notification

Chraebs — Wed, 23 Jun 2021 04:35:02 GMT

Thanks Hakon for the hint about the dependency on EMM information PDUs. Good to know this limitation. Could you link the originating ticket (I couldn't find it).

RE: Format of AT%XOPNAME operator name notification

Hakon — Tue, 22 Jun 2021 15:40:55 GMT

Hello,

I came across this from an old ticket, you can see if it is relevant for your case.

"It seems that the customer is relying on "%XOPNAME:" notifications for current PLMN. This shall not be done. "%XOPNAME:" notification is sent after network registration (attach), if network sends EMM INFORMATION PDU. There is no guarantee that this notification is ever sent. This is described in AT reference guide.

Unfortunately, there is no unsolicited notification for PLMN change. The standard "+CEREG:" notification does not contain PLMN.

There is one option the customer could implement. After receiving "+CEREG:" notification they should request the corresponding PLMN with "AT+COPS?" or "AT%XMONITOR". After that they have updated MCC, MNC and cell-id for database request."

RE: Format of AT%XOPNAME operator name notification

Chraebs — Fri, 18 Jun 2021 09:42:09 GMT

Ah playing around with COPS=1,2,"xxxx" and CFUN=0 and CFUN=1 showed me that the modem (or the SIM?) stores the last used PLMN when shutting down and there will be no notification if a transition occurs to that specific PLMN.

It's ok for me that there is no notification on startup when the same PLMN is chosen, but I think this is a bug that there is no notification, if the PLMN transitions back to the "default" PLMN when it was a different one before. See this example:

2021-06-18T09:39:10.522Z DEBUG modem << *** Booting Zephyr OS build v2.4.99-ncs1 ***
2021-06-18T09:39:10.534Z DEBUG modem << The AT host sample started
2021-06-18T09:39:14.622Z DEBUG modem >> AT+CFUN?
2021-06-18T09:39:14.634Z DEBUG modem << +CFUN: 0
2021-06-18T09:39:14.639Z DEBUG modem << OK
2021-06-18T09:39:16.012Z DEBUG modem >> AT%XOPNAME=1
2021-06-18T09:39:16.022Z DEBUG modem << OK
2021-06-18T09:39:17.613Z DEBUG modem >> AT+CEREG=5
2021-06-18T09:39:17.623Z DEBUG modem << OK
2021-06-18T09:39:21.180Z DEBUG modem >> AT+CFUN=1
2021-06-18T09:39:21.220Z DEBUG modem << OK
2021-06-18T09:39:21.292Z DEBUG modem << +CEREG: 0,"02C3","01007906",7,0,0,"11100000","11100000"
2021-06-18T09:39:22.687Z DEBUG modem << +CEREG: 2,"02C3","01007906",7,0,0,"11100000","11100000"
2021-06-18T09:39:24.183Z DEBUG modem << +CEREG: 5,"02C3","01007906",7,,,"11100000","11100000"
2021-06-18T09:39:24.201Z DEBUG modem << %XOPNAME: "80","80","22801"
2021-06-18T09:39:45.099Z DEBUG modem >> AT+CFUN=0
2021-06-18T09:39:45.248Z DEBUG modem << +CEREG: 0,"02C3","01007906",7,0,0,"11100000","11100000"
2021-06-18T09:39:48.160Z DEBUG modem << OK
2021-06-18T09:39:50.585Z DEBUG modem >> AT%XOPNAME=1
2021-06-18T09:39:50.600Z DEBUG modem << OK
2021-06-18T09:39:51.280Z DEBUG modem >> AT+CEREG=5
2021-06-18T09:39:51.290Z DEBUG modem << OK
2021-06-18T09:39:52.440Z DEBUG modem >> AT+CFUN=1
2021-06-18T09:39:52.482Z DEBUG modem << OK
2021-06-18T09:39:52.572Z DEBUG modem << +CEREG: 0,"02C3","01007906",7,0,0,"11100000","11100000"
2021-06-18T09:39:53.968Z DEBUG modem << +CEREG: 2,"02C3","01007906",7,0,0,"11100000","11100000"
2021-06-18T09:39:54.830Z DEBUG modem << +CEREG: 5,"02C3","01007906",7,,,"11100000","11100000"
2021-06-18T09:39:54.838Z DEBUG modem << %XOPNAME: "80","80","22801"
2021-06-18T09:40:16.375Z DEBUG modem >> AT+COPS=1,2,"22802"
2021-06-18T09:40:16.492Z DEBUG modem << +CEREG: 5,"9E98","0076E204",7,,,"11100000","11100000"
2021-06-18T09:40:18.738Z DEBUG modem << +CEREG: 2,"9E98","0076E204",7,0,10,"11100000","11100000"
2021-06-18T09:40:25.870Z DEBUG modem << +CEREG: 5,"9E98","0076E204",7,,,"11100000","11100000"
2021-06-18T09:40:25.888Z DEBUG modem << OK
2021-06-18T09:40:32.118Z DEBUG modem >> AT+CFUN=0
2021-06-18T09:40:32.272Z DEBUG modem << +CEREG: 0,"9E98","0076E204",7,0,0,"11100000","11100000"
2021-06-18T09:40:33.877Z DEBUG modem << OK
2021-06-18T09:40:35.200Z DEBUG modem >> AT%XOPNAME=1
2021-06-18T09:40:35.216Z DEBUG modem << OK
2021-06-18T09:40:36.303Z DEBUG modem >> AT+CEREG=5
2021-06-18T09:40:36.322Z DEBUG modem << OK
2021-06-18T09:40:37.480Z DEBUG modem >> AT+CFUN=1
2021-06-18T09:40:37.521Z DEBUG modem << OK
2021-06-18T09:40:37.610Z DEBUG modem << +CEREG: 0,"9E98","0076E204",7,0,0,"11100000","11100000"
2021-06-18T09:40:39.007Z DEBUG modem << +CEREG: 2,"9E98","0076E204",7,0,0,"11100000","11100000"
2021-06-18T09:40:40.032Z DEBUG modem << +CEREG: 5,"9E98","0076E204",7,,,"11100000","11100000"
2021-06-18T09:40:54.421Z DEBUG modem >> AT+COPS?
2021-06-18T09:40:54.436Z DEBUG modem << +COPS: 1,2,"22802",7
2021-06-18T09:40:54.441Z DEBUG modem << OK
2021-06-18T09:41:03.762Z DEBUG modem >> AT+COPS=1,2,"22801"
2021-06-18T09:41:03.853Z DEBUG modem << +CEREG: 5,"02C3","01007906",7,,,"11100000","11100000"
2021-06-18T09:41:03.971Z DEBUG modem << +CEREG: 2,"02C3","01007906",7,0,9,"11100000","11100000"
2021-06-18T09:41:07.463Z DEBUG modem << +CEREG: 5,"02C3","01007906",7,,,"11100000","11100000"
2021-06-18T09:41:07.470Z DEBUG modem << OK
2021-06-18T09:41:07.488Z DEBUG modem << %XOPNAME: "80","80","22801"
2021-06-18T09:41:16.108Z DEBUG modem >> AT+COPS=1,2,"22802"
2021-06-18T09:41:16.250Z DEBUG modem << +CEREG: 5,"9E98","0076E204",7,,,"11100000","11100000"
2021-06-18T09:41:16.443Z DEBUG modem << +CEREG: 2,"9E98","0076E204",7,0,10,"11100000","11100000"
2021-06-18T09:41:20.192Z DEBUG modem << +CEREG: 5,"9E98","0076E204",7,,,"11100000","11100000"
2021-06-18T09:41:20.198Z DEBUG modem << OK
2021-06-18T09:41:21.644Z DEBUG modem >> AT+COPS?
2021-06-18T09:41:21.655Z DEBUG modem << +COPS: 1,2,"22802",7
2021-06-18T09:41:21.670Z DEBUG modem << OK

RE: Format of AT%XOPNAME operator name notification

Chraebs — Fri, 18 Jun 2021 09:00:05 GMT

I could collect some more data, but the behavior does not make sense to me.

If I force to use a specific PLMN, then AT%XOPNAME does produce notifications, but only for one of the operators!!

In my example, I get only notifications if mccmnc changes to 22801, but not when it changes to 22802.

2021-06-18T08:55:02.203Z DEBUG modem << *** Booting Zephyr OS build v2.4.99-ncs1  ***
2021-06-18T08:55:02.223Z DEBUG modem << The AT host sample started
2021-06-18T08:55:06.072Z DEBUG modem >> AT%XOPNAME=1
2021-06-18T08:55:06.088Z DEBUG modem << OK
2021-06-18T08:55:07.175Z DEBUG modem >> AT+CFUN=1
2021-06-18T08:55:07.215Z DEBUG modem << OK
2021-06-18T08:55:10.453Z DEBUG modem << %XOPNAME: "80","80","22801"
2021-06-18T08:55:18.012Z DEBUG modem >> AT+CFUN=0
2021-06-18T08:55:19.020Z ERROR Error: 'AT+CFUN=0
' timed out
2021-06-18T08:55:19.747Z DEBUG modem << OK
2021-06-18T08:55:27.303Z DEBUG modem >> AT%XOPNAME=1
2021-06-18T08:55:27.314Z DEBUG modem << OK
2021-06-18T08:55:28.597Z DEBUG modem >> AT+CFUN=1
2021-06-18T08:55:28.638Z DEBUG modem << OK
2021-06-18T08:55:31.095Z DEBUG modem << %XOPNAME: "80","80","22801"
2021-06-18T08:55:43.320Z DEBUG modem >> AT+COPS=1,2,"22802"
2021-06-18T08:55:44.321Z ERROR Error: 'AT+COPS=1,2,"22802"
' timed out
2021-06-18T08:55:50.445Z DEBUG modem << OK
2021-06-18T08:55:59.442Z DEBUG modem >> AT+COPS?
2021-06-18T08:55:59.456Z DEBUG modem << +COPS: 1,2,"22802",7
2021-06-18T08:55:59.461Z DEBUG modem << OK

It seems that this feature is not reliable - I won't use it!

RE: Format of AT%XOPNAME operator name notification

Chraebs — Fri, 18 Jun 2021 08:50:19 GMT

Not fully related to the initial question, but I'm wondering why my nrf9160 devkit does not report any AT%XOPNAME notifications anymore (although it did 10 days ago - see initial question).

This is the log from at_client example on my devkit with modem version v1.2.0:

2021-06-18T08:29:38.494Z DEBUG modem << *** Booting Zephyr OS build v2.4.99-ncs1  ***
2021-06-18T08:29:38.502Z DEBUG modem << The AT host sample started
2021-06-18T08:29:43.071Z DEBUG modem >> AT+CFUN?
2021-06-18T08:29:43.082Z DEBUG modem << +CFUN: 0
2021-06-18T08:29:43.098Z DEBUG modem << OK
2021-06-18T08:29:48.933Z DEBUG modem >> AT%XOPNAME=1
2021-06-18T08:29:48.945Z DEBUG modem << OK
2021-06-18T08:29:55.805Z DEBUG modem >> AT+CEREG=5
2021-06-18T08:29:55.815Z DEBUG modem << OK
2021-06-18T08:29:59.494Z DEBUG modem >> AT+CFUN=1
2021-06-18T08:29:59.536Z DEBUG modem << OK
2021-06-18T08:30:01.075Z DEBUG modem << +CEREG: 2,"9E98","0076E204",7,0,0,"11100000","11100000"
2021-06-18T08:30:02.775Z DEBUG modem << +CEREG: 5,"9E98","0076E204",7,,,"11100000","11100000"
2021-06-18T08:32:32.449Z DEBUG modem << +CEREG: 5,"9E98","0076E305",7,,,"11100000","11100000"

I would expect a AT%XOPNAME notification when the device gets registered.

I repeated this after updating the modem to version v1.2.3 but got the same result.

Can it be that the operator name is stored on the SIM and if it is re-used, no notification is sent?