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.

[Hakon]

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."

[Chraebs]

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).

[Hakon]

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