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
|-+  Protocols
| |-+  MMAP-Related (Moderator: SMS Forum Support)
| | |-+  Request for Enhanced GSM/UMTS Support
« previous next »
Pages: [1] Go Down Print
Author Topic: Request for Enhanced GSM/UMTS Support  (Read 949 times)
Full Member
Offline Offline

Posts: 22

« on: February 07, 2003, 09:11:32 UTC »

In sections & 4. You have special options to support 1 or 2 operators in Korea, you have special options for TDMA which is a minority interest, and special options for CDMA, but you fail to adequately support correctly handle GSM/PCS & 3GPP which between them represent most of the total world short messaging market and a big slice of the future ! Is this a good strategy ? Personally I would have used the effort expended here to put in the necessary parameters to handle ALL of the features that can be
requested through GSM TP-DCS (see an up to date copy of 123.038). You currently appear to be missing:

*   Any way of specifying what the encoding to be used over the air
interface is required to be - 7 bit, 8 bit or 16 bit.

*   Message marked for Automatic Deletion.

*   Text Compression as described in 23.042

*   Discard Message after using for MWI manipulation.

Support for ALL of these facilities should be added to GSMOptions. You could handle DCS in a similar way to PID. You can either enter the options above or a hex value for DCS. In fact thinking about it if all the GSM stuff can be lumped together into GSMOptions why can't the same be done with the TDMA, CDMA and Korean stuff ? Shouldn't all of these delivery network specific attributes be moved to a NetworkSpecificOptions element.
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Login with username, password and session length