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.

      TELECOMSPACE HOME PAGE         TELECOM DISCUSSION FORUM          CONTACT

+  SMS Forum Online Discussion
|-+  SMS Technologies
| |-+  ANSI-41 (CDMA & TDMA) Related (Moderator: SMS Forum Support)
| | |-+  SMPP DCS to IS-41 DCS MAPPING
« previous next »
Pages: [1] Go Down Print
Author Topic: SMPP DCS to IS-41 DCS MAPPING  (Read 2931 times)
Uniformsystems
Newbie
*
Offline Offline

Posts: 5



WWW
« on: February 21, 2003, 16:49:23 UTC »

hi:
Is anyone have the mapping table for SMPP DCS to IS-41 DCS?


thanks


Roger
Logged
vaizki
Newbie
*
Offline Offline

Posts: 3



« Reply #1 on: March 10, 2003, 19:24:41 UTC »

I might be totally wrong here but since there's no other replies (yet), I'll throw in what I've got..

To my knowledge there is no DCS in anything but GSM. In IS-41 the User Data encoding is defines as a parameter in the start of the UD.

Some SMSCs have a configurable translation table from the SMPP DCS-parameter to the IS-41 character-encoding value.. Some values I've encountered:

DCS -- > Encoding
-----------------------------------------
0,1,2,7 --> IRA (IA5) 7bit "usascii"
3 --> Latin1 (ISO-8859-1), Western European languages
8 --> Unicode (UCS-2 I think)
9 --> Latin8 (ISO-8859-8), Hebrew

But, like I said, this is usually configurable so check with the carrier..
Logged
Uniformsystems
Newbie
*
Offline Offline

Posts: 5



WWW
« Reply #2 on: March 10, 2003, 21:28:02 UTC »

thanks. But seems thereis a little different  from what you wrote down here ,
here are the smpp DCSs
SMPP data-coding   
0   SMSC Default Alphabet
1   IA5 (CCITT T.50)/ASCII (ANSI X3.4) b
2    Octet unspecified (8-bit binary) b
3   Latin 1 (ISO-8859-1) b
4   Octet unspecified (8-bit binary) a
5   JIS (X 0208-1990) b
6   Cyrllic (ISO-8859-5) b
7   Latin/Hebrew (ISO-8859-8) b
8   UCS2 (ISO/IEC-10646) a
9   Pictogram Encoding b
0xA   ISO-2022-JP (Music Codes) b
0xB   reserved
0xC   
0xD   Extended Kanji JIS(X 0212-1990) b
0xE   KS C 5601 b
0xF   reserved
:   
0xBF    reserved
0xC0--CF   GSM MWI control - see [GSM 03.38] d
0xD0-DF    GSM MWI control - see [GSM 03.38] d
0xE0-EF    reserved
0xF0-FF    GSM message class control - see [GSM 03.38] e

a. These coding schemes are common to GSM, TDMA and CDMA. The SMPP protocol allows ESME applications to use the same DCS value (i.e. the GSM 03.38 value) for all three technologies.
b, In cases where a Data Coding Scheme is defined for TDMA and/ or CDMA but not
defined for GSM, SMPP uses GSM 03.38 reserved values."



and for IS-41 the DCSs are defined as the follow:

IS-41   
0   Octet unspecified --8 Bits
1               Extended Protocol message (in my implementation is for IS-91 )
2   7-bit ASCII
3   IA5 -7 Bits
4   UNICODE--16 bits
7   Latin/Hebrwew -- 8bits
8   Latin  --8 bits


I want to know what is right mapping table between SMPP to IS-41 , such as SMPP 1 to IS-41 3 IA5 7-bit



Regards


Roger
Logged
milo
Full Member
***
Offline Offline

Posts: 12


« Reply #3 on: October 09, 2005, 07:05:52 UTC »

Hi,

I am an operator in CDMA network and I got problems with SMS interworking to GSM operator.

1. Short message with unicode characters from CDMA to GSM is normally display. But from GSM --> CDMA, its display is incorrect. While internal sms (CDMA) with unicode characters, they are display correct.

2. One more strange thing is unicode message is sent from CDMA handset (A) to GSM handset (B), it displays correct, and then I send it back from (B) to (A), its display is correct.

I know that the problem may be from encoding scheme but that's all and I am unable to find detail.

Do anyone has experience with this issue and any help is highly appreciated.

Thanks in advance
Logged
SMS Forum Support
SMS Forum Support
Administrator
Sr. Member
*****
Offline Offline

Posts: 1754


WWW
« Reply #4 on: October 09, 2005, 22:32:28 UTC »

ANSI technologies have two character set encodings.. language and encoding..

There's no set in stone method of converting these to/from GSM.. but if using SMPP as an interop interface, the logical way (and certainly one that I personally used in a previous job) is to map pairs of CDMA/TDMA language/encoding values to/from GSM equivalent DCS values.

So Chinese/UCS2 -> GSM UCS2 (using SMPP data_coding field values).. and so on.

Now obviously.. when going the other way  (GSM -> ANSI).. you don't know the language (from GSM you know its unicode but not that its Korean, Chinese, Arabic etc).. and I'm wondering if whats happening is that some defalt (or no value at all ) is being set for language and causing the phone to fail to decode.

Recommend trying against another manufacture/model of CDMA/TDMA phone if possible.. may help test if the translation etc is totally broken or just broken for some models... other than that, hopefully its a configuration that can be tweaked to default language of just properly define the mappings.
Logged

Regards,
   Cormac Long
   Webmaster & Technical Enquiry Moderator,
   SMS Forum

milo
Full Member
***
Offline Offline

Posts: 12


« Reply #5 on: October 11, 2005, 09:13:46 UTC »

Hi admin,

Many thanks for your soon reply.

Language of message from GSM is vietnamese. And this case was tested with so many models of some manufacturers and I got same results.

But, it I sent back vietnamese message, which was sent from CDMA handset, from GSM to CDMA handset its display is normal ^^ while new one is broken Sad.

Hope these information help you find out the problem.

Thank you, once again.
Logged
SMS Forum Support
SMS Forum Support
Administrator
Sr. Member
*****
Offline Offline

Posts: 1754


WWW
« Reply #6 on: October 11, 2005, 12:50:07 UTC »

my earlier reply still stands.. its more than likely a language mapping.. the GSM ->CDMA mapping can only identify that the message is unicode... it can't say which exact language it is.. but CDMA will probably accept some kind of default.. my guessis that the reverse mapping is not setting language at all, not even to some default and that this is the cause
Logged

Regards,
   Cormac Long
   Webmaster & Technical Enquiry Moderator,
   SMS Forum

milo
Full Member
***
Offline Offline

Posts: 12


« Reply #7 on: October 12, 2005, 02:52:04 UTC »

DCS of message from GSM is UCS2 and CDMA's SMSC change it to UTF8 then make bearer data by UFT8 encoding scheme (I am not totally sure this flow is correct 100%, but it should be like that).

Another case is CDMA handset of Nokia doesn't support Vietnamese message in my network. If Vietnamese message send to nokia model, it is not displayed even though sending message is successful. I think nokia handset discard message, but I don't know which case message will be discard by handset???

Best,
Logged
milo
Full Member
***
Offline Offline

Posts: 12


« Reply #8 on: October 20, 2005, 04:45:38 UTC »

I checked Nokia handset issue with sms, and got answer from Nokia Com like that:

"On the network side, there is no language indicator being used by SMSC,
other handsets is using a work around solution by setting language indicator
= 17 (for Vietnamese). However, according to standard TIA - EIA - 637B and
TSB - 58E, language indicator = 17 is a reserved value.

* Due to the lack of universal language indicator from standard, the
long-term solution would be sending a request to the SMS Standard group to
formally define an encoding for Vietnamese SMS's".

Does anyone know about this situation help me check that is correct or not...

Thank you,

milo


Logged
SMS Forum Support
SMS Forum Support
Administrator
Sr. Member
*****
Offline Offline

Posts: 1754


WWW
« Reply #9 on: October 21, 2005, 00:31:05 UTC »

OK.. it looks then like you are stuck.

I can't think of a solution to this
Logged

Regards,
   Cormac Long
   Webmaster & Technical Enquiry Moderator,
   SMS Forum

Pages: [1] Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length