From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] TODO: Add task for NITZ name support in netreg
Date: Thu, 09 Dec 2010 01:47:57 -0600 [thread overview]
Message-ID: <4D0089AD.2010409@gmail.com> (raw)
In-Reply-To: <AANLkTimpfM88KdOg-kGL6ZTnGur7x6ULU5u0pgbSxYx2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Hi Aki,
On 12/09/2010 12:52 AM, Aki Niemi wrote:
> Hi Denis,
>
> 2010/12/3 Denis Kenzior <denkenz@gmail.com>:
>> Out of curiosity, how do you plan to support this on AT modems? I have
>> yet to see any AT modem report the NITZ network name via a proprietary
>> command.
>
> Are you sure? In my experience, the NITZ name may be received moments
> after registration, so it would make sense to have an unsolicited
> notification of it.
The NITZ notification does indeed arrive unsolicited. However, no AT
modem that I know of reports the received NITZ name. This is only
reported via COPS. The best you can do is call COPS again after the
driver reports ofono_netreg_time_notify.
>
>> Besides, all AT modems report the NITZ name via COPS. So in effect
>> oFono already fulfills this task...
>
> Well, not with ISI modems it doesn't. Also, if we move PLMN name
> handling over to oFono, how can you determine if the name reported by
> COPS is indeed the NITZ name and as such should take precedence over
> the core's PLMN name?
Hence the reason for my pointed questions. I'm a big proponent of
moving the PLMN database to the core, however this needs to work for
both ISI and AT modems.
Regards,
-Denis
next prev parent reply other threads:[~2010-12-09 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 14:02 [PATCH] TODO: Add task for NITZ name support in netreg Aki Niemi
2010-12-03 18:43 ` Denis Kenzior
2010-12-09 6:52 ` Aki Niemi
2010-12-09 7:47 ` Denis Kenzior [this message]
2010-12-10 5:50 ` Aki Niemi
2010-12-10 8:36 ` Denis Kenzior
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=4D0089AD.2010409@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