My Oracle Support Banner

SMS DCS Changes When Converting Between Protocols (Doc ID 2416390.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.


In all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), Messaging Manager (MM) may change the encoding of certain Short Message Service (SMS) fields if it is also perform a protocol change between an incoming and outgoing SMS.

For example, if a Short Message Peer-to-Peer (SMPP) arrives at MM which performs a conversion to Mobile Application Part (MAP), the Data Coding Scheme(DCS) encoding may change from 0xF6 to 0x15.  For example:

Incoming SMPP DCS

Data coding: 0xf6
    SMPP Data Coding Scheme: Unknown (0xf6)
    GSM SMS Data Coding
    1111 .... = DCS Coding Group for SMS: SMS DCS: Data coding / message class (0x0f)
    .... 01.. = DCS Character set: 8-bit data (0x01)
    .... ..10 = DCS Message class: Class 2 - (U)SIM specific (0x02)

Outgoing MAP DCS

TP-DCS: 21
    00.. .... = Coding Group Bits: General Data Coding indication (0)
    ..0. .... = Text: Not compressed
    ...1 .... = Message Class: Defined below
    .... 01.. = Character Set: 8 bit data (0x1)
    .... ..01 = Message Class: Class 1 Default meaning: ME-specific (0x1)

The outgoing DCS encoding may also not be valid for the version of MAP the outgoing message is encoded in.

In the above example, the incoming and outgoing DCS' are equivalent.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.