From: Philippe Nunes <philippe.nunes@linux.intel.com>
To: ofono@ofono.org
Subject: [PATCH] TODO: Add STK class 'e' tasks
Date: Wed, 16 Feb 2011 18:24:29 +0100 [thread overview]
Message-ID: <1297877069-9085-1-git-send-email-philippe.nunes@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
---
TODO | 30 ++++++++++++++++++++++++++++++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/TODO b/TODO
index 9bd21d6..80b68fb 100644
--- a/TODO
+++ b/TODO
@@ -337,6 +337,36 @@ Sim Toolkit
Priority: High
Complexity: C8
+- Support of the BIP (Bearer Independent Protocol) proactive commands.
+ The specification defines several bearer types. For now, only the packet data
+ service bearer is considered.
+
+ - OPEN CHANNEL: requests the terminal to open a data channel with
+ parameters indicated in the command. A user confirmation may be
+ requested by the SimToolkitAgent.
+ - CLOSE CHANNEL:requests the terminal to close the specified data
+ channel.
+ - RECEIVE DATA:requests the terminal to return to the UICC data
+ received on the specified channel.
+ - SEND DATA:requests the terminal to send on the specified channel data
+ provided by the UICC.
+ - GET CHANNEL STATUS: requests the terminal to return the current
+ status of all available data channels.
+
+ Priority: Medium
+ Complexity: C4
+ Owner: Philippe Nunes <philippe.nunes@linux.intel.com>
+
+- Support Setup Event List proactive command.
+ To fully support the class 'e', the following events
+ -Data Available event
+ -Channel status event
+ shall be monitored by oFono if part of the current event list.
+ This list is supplied by the last SETUP EVENT LIST command.
+
+ Priority: Medium
+ Complexity: C2
+ Owner: Philippe Nunes <philippe.nunes@linux.intel.com>
Emergency Calls
===============
--
1.7.1
next reply other threads:[~2011-02-16 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 17:24 Philippe Nunes [this message]
2011-02-16 18:01 ` [PATCH] TODO: Add STK class 'e' tasks Denis Kenzior
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=1297877069-9085-1-git-send-email-philippe.nunes@linux.intel.com \
--to=philippe.nunes@linux.intel.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