Mobile Terminated SMS (MT SMS)- Sending a Message to the Mobile Station

SMS Message State Synchronization

When sending SMS messages programmatically, you should use the SMS Message State query (see Mobile Terminated SMS Delivery Status for more information) to delay the sending of each message until the previous message sent has been acknowledged by the phone. If the command to send the message is received before the sending of a previous message has been acknowledged/rejected or timed out, the current message may not be sent.

Transportation

You can choose to send Point-to-Point SMS messages in the CS (Circuit Switched), or PS (Packet Switched) domain, or via SGs (SMS over SGs is an interim solution to realize the transmission of native SMS from CS infrastructure over the LTE radio network. SG is a new interface between the MME and the MSC). The domain to be used is configurable by specifying the Transportation mechanism (see CALL:SMService:PTPoint[:MTERminated]:TRANsport ).

When you send an SMS message to the mobile when the test set is in the idle call state, the SMS layer uses the services of the GMM or MM layer to establish an RRC Connection between the test set and UE. Once the connection is established, the SMS messages are carried in RRC Direct Transfer messages over RB 3.

The test set supports SMS point-to-point mobile-terminated messaging while in the Idle call state or over an active circuit-switched or active packet-switched connection, or over SGs when the UE is attached to an LTE network. You may send an SMS point-to-point mobile-terminated message to the UE while on a circuit switched connection (AMR Voice, RB Test Mode, or UE-to-UE Video) if Transportation is set to CS Domain. You may send an SMS point-to-point mobile-terminated message to the UE while on a packet-switched connection (UMTS/GPRS Packet Data) if Transportation is set to PS Domain. When the test set is connected with an EPC and sends a point-to-point SMS to the UE that is present on the E-UTRA access stratum, the data will be routed to the EPC and passed down the LTE stack , and the SMS will be transferred over the SGs. The test set supports sending SMS point-to-point mobile-terminated messages over existing or non-existing circuit-switched or packet-switched connections, or over SGs. It is therefore possible to send the UE an SMS point-to-point mobile-terminated message under the following conditions:

• while on a circuit-switched call (for example, an AMR Voice, an RB Test Mode or a UE-to-UE Video call) using the existing circuit-switched connection if Transportation is set to CS Domain.
• while on a packet-switched call using the existing packet-switched connection if Transportation is set to PS Domain.
• using a temporary circuit-switched connection while on a packet-switched call if Transportation is set to CS Domain and the UE is IMSI Attached.
• using a temporary packet-switched connection while on a circuit-switched call if Transportation is set to PS Domain and the UE is GMM Attached.
• while on a Simultaneous Services circuit-switched/packet-switched call using the existing circuit-switched connection if Transportation is set to CS Domain.
• while on a Simultaneous Services circuit-switched/packet-switched call using the existing packet-switched connection if Transportation is set to PS Domain
• using SMS over SGs when the test set is connected with an EPC and sends SMS to the UE that is camped on the LTE network.

Message Type

You can define the Message Type used for the SMS message sent from the test set to the mobile station. The Message types are defined as PDU types in 3GPP TS 23.040 Section 9.2.2. The Message types defined for MT SMS messages are:

• Deliver - sending a short message from the network to the mobile station
• Submit Report (not available when using the HTTP interface)- sends information as part of an acknowledgment to a Submit mobile originated (MO) SMS message. The header parameters in this Message Type are different depending on RP Type, which can be either RP-ERROR or RP-ACK. You can configure the value for this parameter in the test set (See CALL:SMService:PTPoint[:MTERminated][:MESSage]:TYPE:SUBReport:RPTYpe for GPIB command information.). When the RP Type is RP-ERROR a failure cause is included with other header information. The structure of Submit Report PDUs is defined in 3GPP TS 23.040 Section 9.2.2.2. Refer to Header Parameters for all the user configurable Submit Report elements.

  See Submit Report Mode for additional information about configuring Submit Reports.

• Status Report (not available when using the HTTP interface)- sent in response to a previous SMS-SUBMIT message from the mobile station which requested a status report. Refer to Header Parameters for all the user configurable Status Report elements. Refer to Message Parameters Managed by the Test Set for the elements automatically configured by the test set.

  See Status Report Mode for additional information about configuring Status Reports.

Sending a Text Message

The default values for the message header parameters are appropriate for sending a text message. However, when sending a text message, you may want to configure whether the message is delivered in the CS domain, or PS domain, or via SGs (EPC/E-UTRA) (see Transportation ). You may also want to specify the text message sent to the mobile station. One of two predefined messages can be sent or you can define a text message yourself. See Short Message Service (SMS) Messages for more information on selecting and defining the content for text messages.

See Procedure A: Sending a Text Message to the Mobile Station for an example of how to send an ASCII Text Message to the mobile station using the front panel.

See The test set as the server: for a simple example of how to send an ASCII Text Message to the mobile station using the HTTP interface.

Sending SMS messages for binary applications

When sending messages using binary data, such as WAP Push, smart messaging, ringtones, or MMS notifications, you may want to configure some of the header values. All the parameters configurable using the test set are listed in Header Parameters .

You must configure the following parameters to successfully send a binary SMS message:

• Data Coding Scheme (DCS)
• User Data Header Indicator
• Custom User Data - The Custom Data parameter is a hexadecimal string. This string, including the appropriate header information, or the UDH (User Data Header), may be generated using an SMS gateway, or you can create the string yourself. See Short Message Service (SMS) Messages for more information on selecting and defining this parameter.

Header Parameters

Unless otherwise noted, all the following parameters can be configured when you are using the HTTP interface as well as the GPIB and front panel interfaces.

• Data Coding Scheme (DCS)
  • Used to identify the coding scheme used by the SMS message contents.
       

    NOTE

    There is no coupling between the Data Coding Scheme value and the content type selected to be included in mobile terminated SMS messages. See Short Message Service (SMS) Messages for more information on content type.

  • ---

       
    It is important for you to configure the Data Coding Scheme parameter in order for the mobile station to know what type of message it is receiving. Some examples of parameter values that you are likely to use are:

    0	ASCII Text Messages (concatenated or non-concatenated)
    4	General binary messages (ringtones, vcards, bitmap picture messages, etc.)
    8	UCS2 (Unicode) messages (Chinese, Japanese, Hebrew, etc.)
    245	WAP Push and MMS notification messages
    247

    The Message Class for mobile terminated SMS messages is determined by two bits in the middle of the 8-bit DCS field. Therefore, the Message Class is determined by the value you specify for the DCS parameter.

  • Applicable to the following message types: Deliver, Submit Report, and Status Report. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:DCSCheme
• Failure Cause
  • Used to identify the reason for the failure of a previous mobile originated short message.
  • not available in HTTP interface because Submit Report message type is not supported
  • Applicable to the Submit Report message type only. RP type must be set to RP-ERR. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:FCAuse
• Message Reference
  • Used to identify the previously submitted mobile originated short message.
  • not available in HTTP interface because Status Report message type is not supported
  • if you are sending status reports via GPIB or the front panel, the Message Reference setting must be configured to match the value of the Message Reference of the mobile originated message to which you are responding.
  • Applicable to only the Status Report message type. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:MREFerence
• More Messages to Send
  • This element is used to indicate to the mobile station if there are more messages waiting to be sent from the test set after the current message.
  • Applicable to the following message types: Deliver, Submit Report, and Status Report. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:MMTSend
• Originating Address
  • Used to identify the sender of the message.
  • Applicable to only the Deliver message type. See Message Type for more information.
  • GPIB commands
    • CALL:SMService:PTPoint[:MTERminated][:MESSage]:OADDress
    • CALL:SMService:PTPoint[:MTERminated][:MESSage]:OADDress:PLAN
    • CALL:SMService:PTPoint[:MTERminated][:MESSage]:OADDress:TYPE
• Parameter Indicator
  • Used to identify the presence of optional elements within SMS-SUBMIT-REPORT and SMS-STATUS-REPORT messages. The value you specify for this parameter determines the inclusion of the Data Coding Scheme, User Data Length, and Protocol Identifier elements for all SMS-SUBMIT-REPORT messages sent from the test set.
  • Applicable to the following message types: Submit Report and Status Report. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:PINDicator
• Protocol Identifier
  • Used to identify the higher layer protocol being used, or to indicate interworking with a particular type of telematic device.
  • Applicable to the following message types: Deliver, Submit Report, and Status Report. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:PIDentifier
• Recipient Address
  • Used to identify the recipient of the previously submitted SMS message.
  • Not available in HTTP interface because Status Report message type is not supported
  • Applicable to only the Status Report message type. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:RADDress
• Reply Path
  • Used to indicate if a Reply Path exists.
  • Applicable to only the Deliver message type. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:RPATh
• Status
  • Used to describe the status of the previously sent mobile originated short message.
  • not available in HTTP interface because Status Report message type is not supported
  • Applicable to only the Status Report message type. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:STATus
• Status Report Indication
  • Used to indicate if a status report has been requested from the entity sending the SMS message to the mobile station.
  • Applicable to only the Deliver message type. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:SREPort
• User Data Header Indicator
  • This header field indicates to the mobile station that the message content contains further header information. This should be set to 1 for any type of binary message, including concatenated text messages, as they also contain additional header information.
  • Applicable to the following message types: Deliver, Submit Report, and Status Report. See Message Type for more information.
  • CALL:SMService:PTPoint[:MTERminated][:MESSage]:UDHind
• SMSC Address
  • The SMSC Address (RP-Originating Address) is used to identify the originating SMS Service Center address for MT transfers.
  • Applicable to the following message types: Deliver, Submit Report, and Status Report. See Message Type for more information.
  • GPIB commands
    • CALL:SMService:PTPoint[:MTERminated][:MESSage]:SADDress
    • CALL:SMService:PTPoint[:MTERminated][:MESSage]:SADDress:PLAN
    • CALL:SMService:PTPoint[:MTERminated][:MESSage]:SADDress:TYPE

Message Parameters Managed by the Test Set

Some header parameters are automatically calculated by the test set and included in all SMS messages sent from the test set. These header elements are:

Related Topics

Mobile Originated SMS (MO SMS)- Receiving Messages Transmitted by the Mobile Station

Short Message Service (SMS) Messages

Mobile Terminated SMS Delivery Status

Logging SMS Messages

How to use the Short Message Service Features