From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 1/3] Mobile broadband provider info plugin
Date: Mon, 18 Jul 2011 17:17:22 +0200 [thread overview]
Message-ID: <1311002244.21109.161.camel@aeonflux> (raw)
In-Reply-To: <4E242B30.201@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
Hi Denis,
> > On 07/15/2011 09:18 PM, Denis Kenzior wrote:
> >> Does mobile-broadband-provider actually have multiple settings yet? If
> >> not, then this might need to be set to 1 until it does.
> >
> > Actually, it does.
> >
>
> 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.
I think you are right. It currently has multiple entries, but it misses
any kind of type declaration.
> >> I'm a little unclear on how we handle multiple matches of the same
> >> mcc/mnc. To my understanding these are different plans within the same
> >> provider and some user intervention is required to select the right
> >> plan. Or it could be that the operator is actually an MVNO, which is
> >> why the SPN provided by oFono in order to to distinguish between them.
> >>
> >> So it sounds like that if we encounter entries where multiple matches
> >> are possible, we should not actually provision the context.
> >
> > To my understanding, multiple matches of the same mcc/mnc might be
> > because of:
> >
> > - Different kind of settings (internet/mms/wap).
> > - Different plans for the same kind of setting (prepaid/postpaid).
> > - MVNO.
> >
> > A few possible solutions in order to avoid the ambiguity would be:
> >
> > 1. One could try guess the type of settings out of the access point
> > name. This should work with a few exceptions, which could be handled
> > case by case.
> >
> > 2. Same as item 1, except when the kind of settings can't be guessed,
> > just not to provision the context and let the user possibility to choose.
> >
> > 3. To introduce additional tags (internet, mms, wap, prepaid, postpaid).
>
> 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.
Oleg, please work with the NetworkManager/ModemManager guys to get the
XML extended and get these tags and additional information merged into
to the upstream database.
Regards
Marcel
next prev parent reply other threads:[~2011-07-18 15:17 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 [this message]
2011-07-19 13:20 ` Oleg Zhurakivskyy
2011-07-19 13:19 ` Oleg Zhurakivskyy
2011-07-19 13:36 ` Denis Kenzior
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=1311002244.21109.161.camel@aeonflux \
--to=marcel@holtmann.org \
--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