diff options
-rw-r--r-- | TODO | 14 | ||||
-rw-r--r-- | doc/features.txt | 12 |
2 files changed, 12 insertions, 14 deletions
@@ -31,20 +31,6 @@ SMS Priority: Low Complexity: C8 -- Source / Destination port addressing scheme from 3GPP 23.040. A special - header is used to indicate the source / destination port of the application - this SMS message belongs to. Such messages which are encoded in 8-bit should - be decoded by oFono automatically. The handler associated with this source / - destination port is called with the decoded stream. - - Proposed solution involves a registration / callback framework in the SMS - atom for plugins to register handlers. Default (wildcard) handler is also - desired. - - Priority: High - Complexity: C2 - Owner: Aki Niemi <aki.niemi@nokia.com> - - Smart Messaging Service. This is a separate standard from Nokia and uses the 3GPP 23.040 source / destination addressing scheme. The main aim of this task is to support vCards and vCalendar objects over SMS. diff --git a/doc/features.txt b/doc/features.txt index 2101b9c1..b3c067eb 100644 --- a/doc/features.txt +++ b/doc/features.txt @@ -151,6 +151,18 @@ Short Messaging Service status reports are received, the UI is notified either via DBus or history plugin API. +- Source / Destination port addressing scheme from 3GPP 23.040. A special + header is used to indicate the source / destination port of the application + this SMS message belongs to. oFono provides a handler registration + framework where plugins can handle the reception of such messages. The + handler can be registered to receive messages which contain a specific + source and destination port, or a wildcard. When such messages are received, + they are matched against the registered handlers and dispatched appropriately. + + oFono takes care of de-fragmentation of such SMS messages, so the handler + is informed only once the entire message has been received, and the data + payload has been extracted. + GPRS ==== |