All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aki Niemi <aki.niemi@nokia.com>
To: ofono@ofono.org
Subject: Re: Selecting multiple radio access technologies in oFono
Date: Tue, 01 Feb 2011 22:25:30 +0200	[thread overview]
Message-ID: <1296591930.2619.60.camel@tucson> (raw)
In-Reply-To: <4D46C032.60405@tieto.com>

[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]

Hi Paavo,

On Mon, 2011-01-31 at 15:59 +0200, ext Paavo Leinonen wrote:
> Could it be possible to extend current TechnologyPreference setting in
> radio-settings-api in a way which would enable user to limit usage of 
> certain
> radio accesses? For example user could choose to limit technology usage to
> technologies like GSM and UMTS even if the LTE coverage would be available.
> Following value could be introduced to current API to enable this kind of
> selection:
> 
> "gsm"      Only GSM used for radio access.
> "umts"     Only UMTS used for radio access.
> "gsm_umts" Only GSM or UMTS used for radio access.
> "lte"      Only LTE used for radio access.

The current API has 'gsm', 'umts', 'lte' and 'any'. I think you are
suggesting something like 'all-but-lte', right?

> Other approach could be that we would rephrase existing API so that 
> instead of
> using "only" LTE, we would use LTE whenever available and some older 
> technology
> when LTE coverage is lacking. So user would select "highest" allowed radio
> access without restrictions to use only one technology which has been 
> selected.

This is what 'any' essentially is for.

> This would save us from polluting value selection with options like 
> "gsm_umts",
> a decision we'd be grateful when we'll run oFono on 10G modems. ;)
> 
> Use case for this could be energy conservation. At least I have habit to set
> network preference to 'GSM' to conserve battery life when I know I'm 
> going to
> travel places where 3G coverage is not that good or I'm not going to 
> need it.

I think this will also get gradually better as networks and handsets are
upgraded to use better power saving features, such as CPC.

Cheers,
Aki

> Br,
> Paavo
> 
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> http://lists.ofono.org/listinfo/ofono




  parent reply	other threads:[~2011-02-01 20:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 13:59 Selecting multiple radio access technologies in oFono Paavo Leinonen
2011-01-31 14:08 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-02-01 20:25 ` Aki Niemi [this message]
2011-02-02  9:33   ` Paavo Leinonen
2011-02-02  9:42     ` Marcel Holtmann
2011-02-02 10:05       ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-02-02 10:31       ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2011-02-02 10:44         ` Marcel Holtmann
2011-02-02 12:00           ` Kjetil ASDAL
2011-02-02 12:46             ` Lucas De Marchi
2011-02-02 13:10               ` Kjetil ASDAL

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=1296591930.2619.60.camel@tucson \
    --to=aki.niemi@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.