From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Read EF-SPDI and use it for SPN display.
Date: Mon, 22 Jun 2009 13:23:07 -0500 [thread overview]
Message-ID: <200906221323.07667.denkenz@gmail.com> (raw)
In-Reply-To: <1245548448-6757-1-git-send-email-andrew.zaborowski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
Hi,
>When the operator is one of those listed in EF-SPDI then we need to
>treat it like a HPLMN in deciding whether the SPN or PLMN name should
>be displayed.
Patch has been applied. I fixed a couple minor style issues. Thanks.
>---
>I was also going to try implementing the semantics described in EF-PNN /
>EF-OPL but I have not found evidence that it's not already handled by the
>modem in the responses to +COPN (i.e. it may already be taking care to
>substitute the network names? is this specified somewhere or would this
>be very unlikely?)
Unfortunately +COPN is based on the operator list stored in the modem itself.
This generally means this list is pretty much garbage after a few years.
Check 22.101 Appending A, Section A.3. Basically the +COPS=? lists the
operator names stored in the ME, +COPS? is likely to report the NITZ name once
it arrives. The SIM EFpnn and EFopl is not queried unless you use vendor
extensions.
For us the strategy should probably be:
- If EFpnn / EFopl exists on the SIM, read and cache
- If EFpnn / EFopl exists on the SIM and cache already exists, delay updating
cache until later
- If EFpnn / EFopl cache name exists, use that name
- Otherwise use COPS name.
There's also the possibility of including our own database of mcc/mnc
identifiers along with operator name and operator country. This would probably
have higher precedence over the COPS name.
Regards,
-Denis
next prev parent reply other threads:[~2009-06-22 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 1:40 [PATCH] Read EF-SPDI and use it for SPN display Andrzej Zaborowski
2009-06-22 18:23 ` Denis Kenzior [this message]
2009-06-22 18:30 ` Aki Niemi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906221323.07667.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox