oFono SMS Validity Period and Message Class support

oFono SMS Validity Period and Message Class support

[Su, Yong]

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

Hi, all:
 
We are using ofono to send sms with validity period and message class in our project.
but by checking source code, it seems ofono doesn't support these requirements.   

Current implemntation is the dbus interface "SendMessage" contains "To" and "Text" only.
 
Does oFono plan to support these extra fields when sending sms? 
 
Thanks.
 
 

RE: oFono SMS Validity Period and Message Class support

[Rajesh.Nagaiah]

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

Hi,

> Hi, all:
>  
> We are using ofono to send sms with validity period and 
> message class in our project.
> but by checking source code, it seems ofono doesn't support 
> these requirements.   
> 
> Current implemntation is the dbus interface "SendMessage" 
> contains "To" and "Text" only.
>  
> Does oFono plan to support these extra fields when sending sms? 
>  

Right now oFono uses hardcoded Relative validity period of value
167 (24hrs: 12hrs +(167-143)x30mins)for SUBMIT message. 

If later supported then the Validity period should be part of the
SMS app settings and the setting changes will trigger the property
change in the org.ofono.MessageManager interface. But currently 
Validity Period property is missing in org.ofono.MessageManager
interface. So it doesnt need to be part of the SendMessage dbus
interface ?

Regarding the message class, none of the UE usually gives the a
user setting for message class for outgoing SMS. So oFono uses
unspecified message class and it sets only the encoding type
(GSM 7bit or UCS2) in the DCS byte for the SUBMIT message. For
the SMS DELIVER it decodes the Message class and handles it 
accordingly (Note: Class 2 messages are not supported in oFono)

BR,
Rajesh

Re: oFono SMS Validity Period and Message Class support

[Denis Kenzior]

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

Hi,

On 10/29/2010 03:43 AM, Su, Yong wrote:
> Hi, all:
>  
> We are using ofono to send sms with validity period and message class in our project.
> but by checking source code, it seems ofono doesn't support these requirements.   

oFono does not allow you to set the validity period and simply
hard-codes it (I believe 48 hours).  Unless you have a really good
reason why you want to set the validity period, this isn't likely to change.

Sending SMS messages other than class unspecified makes no sense and
will not be supported.  If you have some extremely specific use case in
mind where this does make sense, please write your own oFono plugin.

> 
> Current implemntation is the dbus interface "SendMessage" contains "To" and "Text" only.
>  
> Does oFono plan to support these extra fields when sending sms?

Right now the answer is no.

Regards,
-Denis

RE: oFono SMS Validity Period and Message Class support

[Su, Yong]

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


 Hi,

> -----Original Message-----
> From: Rajesh.Nagaiah(a)elektrobit.com 
> [mailto:Rajesh.Nagaiah(a)elektrobit.com] 
> Sent: 2010?10?29? 18:09
> To: ofono(a)ofono.org
> Subject: RE: oFono SMS Validity Period and Message Class support
> 
> Hi,
> 
> > Hi, all:
> >  
> > We are using ofono to send sms with validity period and 
> message class 
> > in our project.
> > but by checking source code, it seems ofono doesn't support 
> > these requirements.   
> > 
> > Current implemntation is the dbus interface "SendMessage" 
> > contains "To" and "Text" only.
> >  
> > Does oFono plan to support these extra fields when sending sms? 
> >  
> 
> Right now oFono uses hardcoded Relative validity period of value
> 167 (24hrs: 12hrs +(167-143)x30mins)for SUBMIT message. 
> 
> If later supported then the Validity period should be part of 
> the SMS app settings and the setting changes will trigger the 
> property change in the org.ofono.MessageManager interface. 
> But currently Validity Period property is missing in 
> org.ofono.MessageManager interface. So it doesnt need to be 
> part of the SendMessage dbus interface ?
> 
> Regarding the message class, none of the UE usually gives the 
> a user setting for message class for outgoing SMS. So oFono 
> uses unspecified message class and it sets only the encoding 
> type (GSM 7bit or UCS2) in the DCS byte for the SUBMIT 
> message. For the SMS DELIVER it decodes the Message class and 
> handles it accordingly (Note: Class 2 messages are not 
> supported in oFono)
> 
> BR,
> Rajesh
> 
> 

Thanks for your feedback. I know you are the CDMS SMS owner from the TODO list. 

We are developing one GSM&CDMA dual mode phone.  But current ofono is not support CDMA SMS decode&encode as ISA637 PDU format. 

Can I ask you another question about CDMA SMS? 

I want to know the CDMA SMS delepment schedule if possible. 

Thank you very much

RE: oFono SMS Validity Period and Message Class support

[Su, Yong]

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



Hi,
 

> -----Original Message-----
> From: Denis Kenzior [mailto:denkenz(a)gmail.com] 
> Sent: 2010?10?30? 1:20
> To: ofono(a)ofono.org
> Cc: Su, Yong
> Subject: Re: oFono SMS Validity Period and Message Class support
> 
> Hi,
> 
> On 10/29/2010 03:43 AM, Su, Yong wrote:
> > Hi, all:
> >  
> > We are using ofono to send sms with validity period and 
> message class in our project.
> > but by checking source code, it seems ofono doesn't support 
> these requirements.   
> 
> oFono does not allow you to set the validity period and 
> simply hard-codes it (I believe 48 hours).  Unless you have a 
> really good reason why you want to set the validity period, 
> this isn't likely to change.
> 
> Sending SMS messages other than class unspecified makes no 
> sense and will not be supported.  If you have some extremely 
> specific use case in mind where this does make sense, please 
> write your own oFono plugin.
> 
> > 
> > Current implemntation is the dbus interface "SendMessage" 
> contains "To" and "Text" only.
> >  
> > Does oFono plan to support these extra fields when sending sms?
> 
> Right now the answer is no.
> 
> Regards,
> -Denis
> 
> 

Thanks. I know these fields are less used.

But our customer require our phone must support to set SMS validity period and Message Class.

So, we will write oFono plugin to reslove it.