Re: [PATCH 05/10] Update documentation for GPRS technology

2011-01-13 Thread Rémi Denis-Courmont
On Wednesday 12 January 2011 18:32:22 ext Marcel Holtmann, you wrote:
 Hi Remi,
 
+   string Technology [readonly, optional]
+
+   Contains the data technology as reported by the
+   GPRS service registration (if known).
+
+   Possible values are the same as for the 
Technology
+   property the NetworkRegistration object.
+
   
   we used to have this value and then we removed it since it ended up
   being not useful. So why do you wanna bring it back?
  
  The network registration only ever tells 2G/3G/4G. We need something to
  tell about EDGE or HS*PA. We cannot rely (only) on the CPSB bearer as it
  is only defined when there is an active context. Technology is set
  whenever we are registered to the GPRS service.
 
 as I said, we took the Technology field from the Connection Manager
 since it was just duplication.
 
 So why are we not feeding the CPSB bearer information into the Network
 Registration and have it just update from GSM - EDGE and UMTS - HSPA
 accordingly.
 
 I think that the UI should only require to monitor one location for this
 information to display them. And if it jumps from 3.5G to 3G and back
 depending if a GPRS context is active or not. That is fine with me.

Unfortunately, it is a bit more complicated. Different people have different 
understandings of what the UI should show... At the root of the issue, we have 
the fact that the network access technology (found in the network registration 
atom at the moment) and the current bearer technology (not currently exposed 
by oFono) have no total order.

It is of course perfectly normal for the access technology to be more 
powerful than the current bearer - for instance if the device is not 
transmitting much if any data. But on some network, we can also have the 
opposite situation because some network cells do not expose their support of 
HS*PA during registration, but only when data transfer occurs.

One view is that the UI should expose the highest of both values. Another 
view si that the UI should expose the current bearer if any, otherwise the 
network registration technology. And then I have seen some more advanced use 
cases where we need both infos separated.


So my take is that oFono should expose both values. If we want to make it 
easy for the user interface, then we should have a third pre-digested value, 
and even then we might need to make the algorithm configurable.

-- 
Rémi Denis-Courmont
Nokia Devices RD, Maemo Software, Helsinki
___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/listinfo/ofono


Re: [PATCH 05/10] Update documentation for GPRS technology

2011-01-12 Thread Marcel Holtmann
Hi Remi,

   + string Technology [readonly, optional]
   +
   + Contains the data technology as reported by the
   + GPRS service registration (if known).
   +
   + Possible values are the same as for the Technology
   + property the NetworkRegistration object.
   +
  
  we used to have this value and then we removed it since it ended up
  being not useful. So why do you wanna bring it back?
 
 The network registration only ever tells 2G/3G/4G. We need something to tell 
 about EDGE or HS*PA. We cannot rely (only) on the CPSB bearer as it is only 
 defined when there is an active context. Technology is set whenever we are 
 registered to the GPRS service.

as I said, we took the Technology field from the Connection Manager
since it was just duplication.

So why are we not feeding the CPSB bearer information into the Network
Registration and have it just update from GSM - EDGE and UMTS - HSPA
accordingly.

I think that the UI should only require to monitor one location for this
information to display them. And if it jumps from 3.5G to 3G and back
depending if a GPRS context is active or not. That is fine with me.

Regards

Marcel


___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/listinfo/ofono


Re: [PATCH 05/10] Update documentation for GPRS technology

2011-01-11 Thread Rémi Denis-Courmont
On Tuesday 11 January 2011 02:31:00 ext Marcel Holtmann, you wrote:
 Hi Remi,
 
   doc/connman-api.txt |8 
   1 files changed, 8 insertions(+), 0 deletions(-)
  
  diff --git a/doc/connman-api.txt b/doc/connman-api.txt
  index 22e02e5..b13efd1 100644
  --- a/doc/connman-api.txt
  +++ b/doc/connman-api.txt
  @@ -77,6 +77,14 @@ Properties   boolean Attached [readonly]
  
  be available, e.g. receiving SMS over packet radio
  or network initiated PDP activation.
  
  +   string Technology [readonly, optional]
  +
  +   Contains the data technology as reported by the
  +   GPRS service registration (if known).
  +
  +   Possible values are the same as for the Technology
  +   property the NetworkRegistration object.
  +
 
 we used to have this value and then we removed it since it ended up
 being not useful. So why do you wanna bring it back?

The network registration only ever tells 2G/3G/4G. We need something to tell 
about EDGE or HS*PA. We cannot rely (only) on the CPSB bearer as it is only 
defined when there is an active context. Technology is set whenever we are 
registered to the GPRS service.

-- 
Rémi Denis-Courmont
Nokia Devices RD, Maemo Software, Helsinki
___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/listinfo/ofono


[PATCH 05/10] Update documentation for GPRS technology

2011-01-10 Thread Rémi Denis-Courmont
---
 doc/connman-api.txt |8 
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/doc/connman-api.txt b/doc/connman-api.txt
index 22e02e5..b13efd1 100644
--- a/doc/connman-api.txt
+++ b/doc/connman-api.txt
@@ -77,6 +77,14 @@ Properties   boolean Attached [readonly]
be available, e.g. receiving SMS over packet radio
or network initiated PDP activation.
 
+   string Technology [readonly, optional]
+
+   Contains the data technology as reported by the
+   GPRS service registration (if known).
+
+   Possible values are the same as for the Technology
+   property the NetworkRegistration object.
+
boolean Suspended [readonly, optional]
 
Contains whether the GPRS service is suspended.
-- 
1.7.1

___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/listinfo/ofono