From: Jukka Saunamaki <jukka.saunamaki@nokia.com>
To: ofono@ofono.org
Subject: Re: SAT support in oFono
Date: Mon, 24 Jan 2011 13:17:17 +0200 [thread overview]
Message-ID: <1295867837.2182.54.camel@jsaunama-desktop> (raw)
In-Reply-To: <1295866144.2676.15.camel@aeonflux>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Hello
> > > > - 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.
Sorry, still quite anecdotal, but I heard about a case related to RFC
payment system, where operator wants to use BIP for loading payment
application into SIM (I guess SMS-PP-data-download was not good enough
for that). Also, at least some NFC plans use Smart Card Web Server
(SCWS), that needs at least part of BIP.
--Jukka
next prev parent reply other threads:[~2011-01-24 11:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 8:44 SAT support in oFono Lasse.Kunnasluoto
2011-01-21 9:12 ` Jeevaka.Badrappan
2011-01-21 15:36 ` Andrzej Zaborowski
2011-01-21 16:13 ` Denis Kenzior
2011-01-24 7:15 ` Lasse Kunnasluoto
2011-01-24 10:14 ` Aki Niemi
2011-01-24 10:53 ` Marcel Holtmann
2011-01-24 10:49 ` Marcel Holtmann
2011-01-24 11:17 ` Jukka Saunamaki [this message]
2011-01-24 14:43 ` Lasse Kunnasluoto
2011-01-24 15:10 ` Marcel Holtmann
2011-01-27 15:46 ` Philippe Nunes
2011-01-27 16:11 ` Denis Kenzior
2011-01-24 14:58 ` Philippe Nunes
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=1295867837.2182.54.camel@jsaunama-desktop \
--to=jukka.saunamaki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox