Re: SAT support in oFono

[Philippe Nunes <philippe.nunes@linux.intel.com>]

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

On 01/24/2011 11:49 AM, Marcel Holtmann wrote:
> Hi Lasse,
>
>>>> I am checking what is the level of SAT/STK support in ofono and have a couple of questions. The current implementation contains support for basic STK commands, like menus, inputs, calls, sms and so on. In TODO, there is only REFRESH command on the list.
>>>>
>>>> Is there plans or ideas to extend the support in oFono Core with more complex STK features like (3GPP TS 31.111):
>>>> - Call control by USIM
>>>> - MO SMS Control by USIM
>>> Let us set aside the the merits of the use cases for these features for
>>> the moment ;)  Implementing Call control by USIM is fairly
>>> straightforward to do in the core.  However, no modem manufacturer
>>> currently allows us to have full control over this feature.  It is
>>> implemented in the firmware and every vendor does this differently.  So
>>> for now support of this feature is in the realm of the modem driver.
>>>
>> okay, so assuming this is how it is going stay. Even modem handles
>> these, ofono should deliver possible AlphaId SIM may give in a response
>> to call control envelope. I did not see if this is implemented. Or is it
>> dropped since it is not tested in GCF..
> show us modem hardware where this is needed. At some point we just had
> to be realistic here in what can be tested with real hardware. And thus
> is really required to be supported and what makes sense in a smartphone
> environment.
>
>>>> - BIP (Bearer independent protocol), including commands like OPEN CHANNEL, CLOSE CHANNEL, SEND/RECEIVE DATA
>> BIP is on many operators' wish list of supported SAT features. Even it
>> is optional in 3GPP, some market areas will probably require BIP. I
>> don't have an example to give right now.
> I think the important phrase is "wish list". So far nobody could really
> showed me the exact use case for BIP. I am actually really interested in
> understanding what the operators wanna use it for. I prefer to have hard
> facts here and not just "wish list" and "probably". If this is not a
> requirement for certification and the operator is not actually using
> such a feature at all, then why bother. Feel free to convince me
> otherwise here.
>
> While we can certainly look into supporting BIP at some point, but from
> where I am standing it is pretty clear; first get all mandatory STK
> features sorted out, before trying to work on optional ones.
>
>>>> - Extend support in PROVIDE LOCAL INFO
>>> What support are you looking for?  Most of the information that is asked
>>> by provide local info is implemented in the modem firmware.  We have
>>> only included support for items which are not covered by the firmware.
>>>
>> If aiming GCF approval support should contain: IMEI, location info,
>> network measurements&BCCH channel list, timing advance, access
>> technology, IMEISV, Inter-frequency UTRAN measurements. As you said
>> these are often handled by modem, but isn't possible that modem can be
>> configured in a way it leaves the full control of SAT to the host?
>> Although certain AT command based modems would require proprietary
>> commands to fetch all the needed information. So in that sense it is
>> more logical for modem to handle these commands what requires low level
>> interfaces.
> What we have seen so far is that all of these are handled by the modem.
> If the modem has all information available, then why bother waking up
> the host CPU for this. It does make a lot of sense to keep the host CPU
> asleep if possible. I am pretty pragmatic here; if we have to support a
> modem that does not handle these, then we have to do it.
>
> So if you have more information about other modem types, please let us
> know. And patches are always welcome.
>
>>>> - EVENT DOWNLOAD / SET UP EVENT LIST
>>>>
>>> Again, which ones are you looking for?  oFono explicitly ignores the
>>> following two events as these make no sense in the smartphone context:
>>>
>>> - Idle Screen Available
>>> - User Activity
>>>
>> It looks like  Idle Screen Available and User Activity&  User Activity
>> are mandatory features in 3GPP TS 31.124, chapter 3.4 Applicability
>> table. Rest of the sub-features are listed there.
> Don't they depend on the STK profile that you are using?
>

Apparently, the answer (shall we support or not those UI events ?) seems 
to be also linked to which release we are claiming to comply with the 
product.

Indeed, according the conformance specification 31.124, the tests 
related to the events are described as follows:
*
Table B.1: Applicability of tests*
----------------------------------------------------------------------------------------------------------------------------------------------------- 

|           Item description                        |  Whatever is the 
release  |                            
Profile                                        |
-----------------------------------------------------------------------------------------------------------------------------------------------------
| 27.22.7.5: user activity event                | C178                   
          | E.1/38 AND E.1/33 AND E.1/111                          |
-----------------------------------------------------------------------------------------------------------------------------------------------------
| 27.22.7.6: idle screen available event    | C177 AND C178            | 
E.1/39 AND E.1/33 AND E.1/110 AND E.1/111      |
------------------------------------------------------------------------------------------------------------------------------------------------------
C177 = IF A.1/84 THEN M ELSE N/A
C178 = IF A.1/85 THEN M ELSE N/A*

Table A.1: Options*
------------------------------------------------------------------------------------------- 

|  Item       |    Option                                          |     
status      |
------------------------------------------------------------------------------------------- 

|     A1.84  | Terminal supports display capability  | C002       |
-------------------------------------------------------------------------------------------
|     A1.85  | Terminal supports keypad                 | C002      |
-------------------------------------------------------------------------------------------

C002 = If feature is implemented according to Rel-8 or later then O, else M

In other words, the events are optional if we are following at least the 
release 8 for the display and keypad capabilities.
So far, I don't see what is the specificity of the release 8 regarding 
those capabilities.

But for previous release, I'm afraid, those events are mandatory as 
stated by Lasse.

Regards,

Philippe.

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 11887 bytes --]