How Does the Test Set Build the Mobile-Terminated Message?

How Does the Test Set Build the Mobile-Terminated Message?

Last updated: January 3, 2008

This section is applicable to the lab application and to a test application with the required feature license.

The message contents you entered may be different from the message that is actually sent to the mobile station due to many factors. The following explains how the test set processes the messages to be sent to the mobile station.

Example of How the Settings Affect the Actual SMS Message

Assumed Settings:

Interim Results

Actual Results

Message Encoding = UNICODE

Message Source = Hex

User Input Message Contents = "12345" (5 hex characters)

Message Repeat = 200

Assumed maximum allowed encoded characters is 19 UNICODE characters due to current protocol configuration.

User input message would be padded with "000" to make 2 UNICODE encoded characters.

Desired message would be "1234500012345000...1234500012345000" (8 hex characters, repeated 200 times)

Message Length (the length of desired message in encoded characters, see Mobile-Terminated SMS Info ) would be 400 (8 hex characters are represented by 2 UNICODE encoded characters)

The actual message sent to the mobile station would be "1234500012345000123450001234500012345000123450001234500012345000123450001234", truncated to result in 19 UNICODE encoded characters due to the current protocol configuration allowed.

Two error messages would result, "SMS message padded with trailing zeros to define whole characters" and "SMS send message truncated due to protocol to <n> characters where <n> would be 19)"

Related Topics


Creating/Editing the Mobile-Terminated Message Contents

Setting Mobile-Terminated SMS Parameters

Short Message Service Information