From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: CDMA SMS Handling
Date: Wed, 06 Oct 2010 19:10:04 -0500 [thread overview]
Message-ID: <4CAD0FDC.7030103@gmail.com> (raw)
In-Reply-To: <C681C76E0D5F1E4BB01DE79E0A80EEC702AC9A8D@usrdes03.ebgroup.elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Hi Rajesh,
> As from the above decoding example we can see there is substantial
> differences between the GSM and CDMA SMS specifications and so the SMS
> atom needs many additions and needs to be heavily modified to support
> also CDMA SMS handling. Currently the oFono sms file unit handles the
> common and the GSM technology aspects of the SMS stack along with the
> smsutils. The SMS atom has the GSM specific members, segmentation and
> queuing logic. The smsutils mainly takes care of encoding/decoding of
> the PDUs, which is GSM specific. As the segmentation and queuing logic
> and the interface is common for both GSM and CDMA, we could reuse this
> common code and add the CDMA handling into it and create a new
> cdmasmsutils unit to support the CDMA SMS specifics, much like the
> smsutils does already for GSM.
This gets my vote, I like to start bottom up. E.g. build the
infrastructure first, with unit tests, etc and then hook up the
controlling logic. So starting cdma smsutils seems like a good idea to me.
Do note however that there's more to smsutils than basic parsing. We
also have sms fragmentation / de-fragmentation logic, sms assembly
serialization, status reports, character encoding / decoding, etc. We
will have to figure out which parts can be re-used for both CDMA and GSM
as we go along...
Regards,
-Denis
next prev parent reply other threads:[~2010-10-07 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 6:48 CDMA SMS Handling Rajesh.Nagaiah
2010-10-06 9:01 ` Marcel Holtmann
2010-10-07 0:10 ` Denis Kenzior [this message]
2010-10-09 1:19 ` Rajesh.Nagaiah
2010-10-13 21:21 ` Denis Kenzior
2010-10-14 18:26 ` Rajesh.Nagaiah
2010-10-18 22:31 ` Denis Kenzior
2012-06-15 15:13 ` asraf
2012-06-15 13:46 ` asraf
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=4CAD0FDC.7030103@gmail.com \
--to=denkenz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.