| Author |
Message |
joyce
New member
Username: Cheerie
Post Number: 3
Registered: 04-2007
| | Posted on Wednesday, July 18, 2007 - 08:15 am: | |
May I know what is the number of chars count per SMS for English & Chinese Wap Push SMS? |
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 7394
Registered: 10-2002
| | Posted on Wednesday, July 18, 2007 - 09:56 pm: | |
A WAP Push message is sent as a binary SMS. A binary SMS is limited to 140 8-bit bytes of data.
I can't give you a formula for how much text can be included, because it depends on other options that are included in your push ... and how much overhead they add.
If you're talking about a service indication message, then there is also the question of the length of the URL that is included in the push.
I can give you an example of this overhead if you are sending a WAP Push Service Indication message using the web interface of NowSMS.
NowSMS will use 26 bytes of overhead for the basic structure of the WAP Push Service Indication message. Each byte of the URL (not including the "http://" or "https://" prefix) will consume another byte. Then one byte per character of text if you're working in English.
If the message text needs to be sent out using Unicode, then the overhead increases to 29 bytes ... and the text is encoded using UTF-8 (which I think requires 3 bytes per typical Chinese character if I recall correctly).
If the message size exceeds 140 bytes, then you end up with a multipart message.
5 additional bytes of overhead are required for segmentation headers in the first message part. (Increasing the total non-URL/non-text overhead in the first part to 31 or 34 bytes for NowSMS.)
12 bytes of overhead are required for headers in all parts beyond the first part.
Not a real clear answer, but maybe this helps you.
-bn |
joyce
New member
Username: Cheerie
Post Number: 4
Registered: 04-2007
| | Posted on Thursday, July 19, 2007 - 04:01 am: | |
it is clear enough for me. thks for the reply. :-) |
|
Search
Last
