Disclaimer: These archives are mirrored from smsforum.net in 2007 before the forum got closed. Please only part of the forum is available here.
For any clarifications regarding these archives you can contact us at http://www.telecomspace.com/contact.


+  SMS Forum Online Discussion
|-+  SMS Technologies
| |-+  ANSI-41 (CDMA & TDMA) Related (Moderator: SMS Forum Support)
| | |-+  Encoding/Decoding of Picture msgs,ringtones in CDMA
« previous next »
Pages: [1] Go Down Print
Author Topic: Encoding/Decoding of Picture msgs,ringtones in CDMA  (Read 720 times)
Jr. Member
Offline Offline

Posts: 5

« on: October 16, 2006, 07:02:16 UTC »

whats the difference in Encoding/Decoding of picturemsgs / ringtones when compared to ordinary text messages incase of SMSC supporting CDMA
Sr. Member
Online Online

Posts: 54

« Reply #1 on: October 16, 2006, 17:19:38 UTC »

Hi Satya

Good question! I wish I knew the answer  Smiley

One way is to use the GSM EMS encoding, called WEMT in CDMA. Below is a sample of a short message sent including a sound. The Teleservice ID (not shown) is set to WEMT (4101). The HEADER_IND field is set to 1, indicating the presence of the GSM User Data Header (as defined in 3GPP TS 23.040 section Although the trace program says "Bytes" for the User Data, they are actually 7-bit fields.

                  PARAMETER_ID  Bearer Data 
                   PARAMETER_LEN  27 
                   Bearer Data
                     SUBPARAMETER_ID  Message Identifier 
                     SUBPARAM_LEN  3 
                     Message Identifier
                       MESSAGE_TYPE  Submit 
                       MESSAGE_ID  162 
                       HEADER_IND  1
                     SUBPARAMETER_ID  User Data 
                     SUBPARAM_LEN  14 
                     User Data
                       MSG_ENCODING  9 
                       NUM_FIELDS  13 
                       Byte  4 
                       Byte  64 
                       Byte  0 
                       Byte  48 
                       Byte  16 
                       Byte  4 
                       Byte  2 
                       Byte  11 
                       Byte  1 
                       Byte  0 
                       Byte  32 
                       Byte  24 
                       Byte  0 
                     SUBPARAMETER_ID  Priority Indicator 
                     SUBPARAM_LEN  1 
                     Priority Indicator
                       PRIORITY  Normal 
                     SUBPARAMETER_ID  Reply Option 
                     SUBPARAM_LEN  1 
                     Reply Option
                       USER_ACK_REQ  0 
                       DAK_REQ  1 
                       READ_ACK_REQ  0 

The User Data header is encoded in octets as follows:
09 Length of User Data Header
00 Information Element Identifier: "Concatenated short messages, 8-bit reference number"
03 Length of Information Element
02 Concatenated short message reference number
01 Maximum number of short messages in the concatenated short message
01 Sequence number of the current short message
0B Information Element Identifier: "Predefined Sound"
02 Length of Information Element
01 Play sound after 1st character
01 Sound #1 = "Chimes low"

The remaining 11 bits of the User Data should be made up of 4 bits padding to align the (octet-encoded) User Data Header with a septet boundary, followed by 7-bits for the 1-character text in the message. Unfortunately I can't decode the actual text itself - it doesn't seem to be using the GSM default aphabet, and repeating the same character in the message doesn't repeat the same sequence of bits... Sad. Anyone who can help please let me know...

Jr. Member
Offline Offline

Posts: 5

« Reply #2 on: October 20, 2006, 09:35:13 UTC »

thanks for the info shad
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Login with username, password and session length