From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/3] Mobile broadband provider info plugin
Date: Tue, 19 Jul 2011 08:36:46 -0500 [thread overview]
Message-ID: <4E25886E.8000700@gmail.com> (raw)
In-Reply-To: <4E25847B.1070401@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]
Hi Oleg,
On 07/19/2011 08:19 AM, Oleg Zhurakivskyy wrote:
>
> Hello Denis,
>
> On 07/18/2011 03:46 PM, Denis Kenzior wrote:
>> Are you sure? Briefly looking through serviceproviders.xml I only
>> noticed different plans within the same provider. You might be right of
>> course, but even if you are, we have no way of distinguishing between a
>> different plan and a different APN type.
>
> Hmm, now I am not sure. In a plugin the settings is the access point
> settings? If so, yes, there are multiple access points within the same
> provider in serviceproviders.xml. Or what kind of setting is meant?
>
So oFono supports 3 context types:
- internet
- mms
- wap
Some (most?) providers use different APNs for these. However, the
providers also have different service plans (e.g. pre-paid, gprs-only,
wap-only, etc)
So your database ends up needing to have settings for each provider,
each service plan for that provider and different context type settings
for each service plan.
To my understanding, with mobile-broadband-provider-info the best we can
do is provision the internet context only.
>> Option 2 sounds like the most likely candidate right now. Option 3 is
>> the direction where we need mobile-broadband-provider-info to go in. In
>> particular adding the internet/mms/wap tags and SPN entries to its
>> database.
>
> OK, let's do option 2 for now and extend the
> mobile-broadband-provider-info. Could you please explain regarding the
> SPN entries, I am not sure if I understand this correct.
>
This is there to handle MVNOs. Basically you might have a provider (A)
that owns the network and a provider (B) that buys access to A's
network. Both can administer different service plans (and have
different settings for APNs, etc). In theory the MNC of provider B
should be different from that of A, however some countries / networks
are weird and have re-used provider's A MCC/MNC for subscribers of
provider B.
This is where the SPN comes in, since the MVNO is interested in
displaying their name to the customer, the SPN is nearly always provided
on the SIM. In the case of the same MCC/MNC, the SPN can thus be used
to distinguish between provider A's settings and provider B's settings.
Regards,
-Denis
next prev parent reply other threads:[~2011-07-19 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 15:12 [PATCH 0/3] Mobile broadband provider info plugin Oleg Zhurakivskyy
2011-07-15 15:12 ` [PATCH 1/3] " Oleg Zhurakivskyy
2011-07-15 18:18 ` Denis Kenzior
2011-07-18 13:32 ` Oleg Zhurakivskyy
2011-07-18 12:46 ` Denis Kenzior
2011-07-18 15:17 ` Marcel Holtmann
2011-07-19 13:20 ` Oleg Zhurakivskyy
2011-07-19 13:19 ` Oleg Zhurakivskyy
2011-07-19 13:36 ` Denis Kenzior [this message]
2011-07-19 14:05 ` Oleg Zhurakivskyy
2011-07-15 15:12 ` [PATCH 2/3] Mobile broadband provider info plugin autoconf support Oleg Zhurakivskyy
2011-07-15 15:12 ` [PATCH 3/3] Mobile broadband provider info plugin makefile changes Oleg Zhurakivskyy
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=4E25886E.8000700@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 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.