Format of AT%XOPNAME operator name notification

[Chraebs]

Hi

I checked how AT%XOPNAME could be used to receive notifications about operator name updates. However I'm wondering about the notification syntax.

According to the specification, the notification might look sth like

"88D6B23CAD7FBB41D7B4BCCC2ECFE7","8B56FD15","556776"

which could be decoded according to 3GPP TS 24.008 Ch. 10.5.3.5a Network Name.

However, when running the at_client example on my devkit (v0.9.0) with modem version v1.2.0 I get:

AT+CFUN?
+CFUN: 0
OK
AT%XOPNAME=1
OK
AT+CFUN=1
OK
%XOPNAME: "80","80","22801"

So I have two questions:

• Will the <full_name> and <short_name> ever be something different than "80"?
• Is <oper> always a 5 or 6 character string with MCC and MNC? I'm asking because I couldn't match the example string "556776" to any MCC/MNC tuple.

Thanks for clarifying this.

[Chraebs]

Hi

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?

[Chraebs]

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!