Search the manual:

Overview Quick start Download Manual How to buy FAQ Contact Us
OZEKI NG SMS Gateway - Product Guide

Binary XML Contents | SearchPID

Home > Product Manual > Appendix > C - Message types > Binary XML > DCS

SMS Gateway SMS Gateway Home

  Product Manual
  Introduction
  SMS technology
  Installation Guide
  User Guide
  Developers Guide
  Examples and Solutions
  Appendix
  A - Terms and definitions
  B - References
  C - Message types
  Introduction
  OTA bitmap
  Operator logo I.
  Operator logo II.
  Ringtone
  Wappush
  Binary XML
  DCS
  PID
  VCard
  VCalendar
  Special SMS Message Indication
  Bookmark
  MMS:XML
  WAP Browser Settings
  SyncML settings
  OMA OTA Settings
  USSD
  WAP Push SL
  Picture message
  D - Database connection strings
  E - SMS alphabet
  F - GSM error codes
  G - SMSC settings
  H - MMSC settings
  I - GSM operators
  J - SMPP providers
  K - GSM modems, phones
  L - Error codes
  M - Country codes
  O - SMPP Error codes
  W - Wireshark Capture
  FAQ
  Feature list
  Commercial Information
  Search
 



Contact Us!
If you wish to get further information, do not hesitate to contact us!

E-mail: info@ozekisms.com

If you have a technical question, please submit a support request on-line.


Callcenter developers
If you are working on telephone solutions, please check out the Ozeki VoIP SIP SDK.
It can be used to create:

Webphone solutions:
- Adobe Flash video phone
- Silverlight video phone
- Web to web calls
- Web to VoIP calls

Custom SIP clients:
- Silverlight SIP VoIP client
- Flash SIP VoIP client
- C# .net SIP VoIP client
- ASP .net SIP VoIP client
- Web based SIP VoIP client

Custom VoIP solutions:
- VoIP SIP softphones
- VoIP call center clients
- VoIP IVR systems
- VoIP predictive dialer systems
- VoIP auto dialer systems
- VoIP call assistant
- VoIP call recording systems
- VoIP intercom solutions

Data Coding Scheme (TP-DCS)


The TP-Data-Coding-Scheme field, defined in GSM 03.40, indicates the data coding scheme of the TP-UD field, and may indicate a message class. Any reserved codings will be assumed to be the GSM default alphabet (the same as codepoint 00000000) by a receiving entity. The octet is used according to a coding group which is indicated in bits 7..4. The octet is then coded as follows:

Coding Group Bits 7..4Use of bits 3..0
00xxGeneral Data Coding indication
Bits 5..0 indicate the following:
Bit 5
0Text is uncompressed
1Text is compressed

Bit 4
0Bits 1 and 0 are reserved and have no message class meaning
1Bits 1 and 0 have a message class meaning

Bit 3Bit 2Alphabet being used
00Default alphabet
018 bit data
10UCS2 (16bit)
11Reserved

Bit 1Bit 0Message classDescription
00Class 0Immediate display (alert)
01Class 1ME specific
10Class 2SIM specific
11Class 3TE specific

NOTE: The special case of bits 7..0 being 0000 0000 indicates the Default Alphabet as in Phase 2

0100..1011Reserved coding groups
1100Message Waiting Indication Group: Discard Message

Bits 3..0 are coded in exactly the same way as Group 1101, however, with bits 7..4 set to 1100 the mobile may discard the contents of the message, and only present the indication to the user.

1101Message Waiting Indication Group: Store Message

This Group allows an indication to be provided for the user about the status of types of message waiting on systems connected to the GSM PLMN. The mobile may present this indication as an icon on the screen, or another MMI indication. The mobile may take note of the Origination Address for the message in this group and group 1100. For each indication supported, the mobile may provide storage for the Origination Address which is to control the mobile indication.
Text included in the user data is coded in the Default Alphabet.
Where a message is received with bits 7..4 set to 1101, the mobile will store the text of the SMS message in addition to setting the indication.
Bit 3Description
0Set Indication Inactive
1Set Indication Active

Bit 2 is reserved, and set to 0
Bit 1Bit 0Indication Type
00Voicemail Message Waiting
01Fax Message Waiting
10Electronic Mail Message Waiting
11Other Message Waiting*

* Mobile manufacturers may implement the "Other Message Waiting" indication as an additional indication without specifying the meaning. The meaning of this indication is intended to be standardized in the future, so Operators should not make use of this indication until the standard for this indication is finalized.

1110Message Waiting Indication Group: Store Message

The coding of bits 3..0 and functionality of this feature are the same as for the Message Waiting Indication Group above, (bits 7..4 set to 1101) with the exception that the text included in the user data is coded in the uncompressed UCS2 alphabet.

1111Data coding/message class

Bit 3 is reserved, set to 0.
Bit 2Message coding
0Default alphabet
18-bit data

Bit 1Bit 0Message ClassDescription
00Class 0Immediate display (alert)
01Class 1ME specific
10Class 2SIM specific
11Class 3TE specific





Next page: PID
Copyright © 2000 - 2013 Ozeki Informatics Ltd.
All rights reserved

Software PBX for Windows | VoIP SDK   |   Legal information   |   Privacy policy   |   Terms of use
Please, address your inquiries to info@ozekisms.com