From: Jukka Saunamaki <jukka.saunamaki@nokia.com>
To: ofono@ofono.org
Subject: Re: [RFC PATCH 4/4] Dummy example GPRS context provisioning driver
Date: Fri, 14 Jan 2011 08:53:03 +0200 [thread overview]
Message-ID: <1294987983.29263.24.camel@jsaunama-desktop> (raw)
In-Reply-To: <4D2F2106.5010807@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Hello Denis,
On Thu, 2011-01-13 at 09:57 -0600, Denis Kenzior wrote:
> > Some virtual operators are using the same MCC/MNC as their host, or some
> > operators have several different trade names, and these can have
> > different access settings (at least different UI visible name).
> > SPN in SIM typically tells these cases apart. This is why I included
> > reading SPN to that example provisioning.
>
> Do you have specific examples? To my knowledge the MVNOs should be
> provisioning the SIM with a different MNC from the host but the network
> used (and thus the network's MCC/MNC) are their host's.
I was not sure if all MVNOs have their own MNC, but in any case some
operators use different trade names. Off the top of my hat I know our
local Finnish operators Elisa and Sonera use trade names like Kolumbus
and TeleFinland, and their name shown in UI needs to be correct.
> > All provisioning plugins might not care about SPN (e.g. the previously
> > discussed one using mobile-broadband-provider-info?), so I would suggest
> > not creating specific SIM API yet. Of cause it can be added later, if so
> > wished.
>
> You might be able to get away with reading of EFspn just because it is
> cached nicely on disk. But you will have to carefully consider your
> plugin design if you wish to do so to avoid any race conditions and be
> able to properly clean up.
You mean that if plugin gets removed/unregistered before SPN-reading
callback comes in?
That is a good point, and I also have to check how to handle this in
GPRS atom, since calling provisioning is asynchronous, and GPRS might
get removed while provisioning is running... I might need some help
figuring out solution to that.
Alternative is of cause to make provisioning synchronous, but that would
limit what plugin can do (like asking SPN with ofono_sim_read())
--Jukka
next prev parent reply other threads:[~2011-01-14 6:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 13:11 [RFC PATCHv3 0/4] Plugin API for provisioning of GPRS context settings Jukka Saunamaki
2011-01-10 13:11 ` [RFC PATCH 1/4] Added GPRS context provisioning driver API sources Jukka Saunamaki
2011-01-12 6:43 ` Marcel Holtmann
2011-01-12 16:43 ` Denis Kenzior
2011-01-10 13:11 ` [RFC PATCH 2/4] gprs: add automatic context settings provisioning Jukka Saunamaki
2011-01-12 6:51 ` Marcel Holtmann
2011-01-12 7:26 ` Jukka Saunamaki
2011-01-12 16:37 ` Marcel Holtmann
2011-01-10 13:11 ` [RFC PATCH 3/4] sim: add ofono_sim_get_mnc_length Jukka Saunamaki
2011-01-11 0:40 ` Marcel Holtmann
2011-01-11 15:03 ` Denis Kenzior
2011-01-10 13:11 ` [RFC PATCH 4/4] Dummy example GPRS context provisioning driver Jukka Saunamaki
2011-01-12 6:48 ` Marcel Holtmann
2011-01-12 7:41 ` Jukka Saunamaki
2011-01-12 16:46 ` Denis Kenzior
2011-01-13 6:36 ` Jukka Saunamaki
2011-01-13 15:57 ` Denis Kenzior
2011-01-14 6:53 ` Jukka Saunamaki [this message]
2011-01-14 7:47 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-14 10:37 ` Marcel Holtmann
2011-01-14 10:46 ` Jukka Saunamaki
2011-01-14 13:44 ` Marcel Holtmann
2011-01-14 13:58 ` Jukka Saunamaki
2011-01-14 14:10 ` Marcel Holtmann
2011-01-14 14:42 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-15 1:30 ` Marcel Holtmann
2011-01-17 6:20 ` Jukka Saunamaki
2011-01-14 15:07 ` 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=1294987983.29263.24.camel@jsaunama-desktop \
--to=jukka.saunamaki@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.