SMS Tab


In MME Nodal and MSC Nodal Testing, the Short Message Service (SMS) provides a means for sending messages of limited size to and from GSM/UMTS mobile units.  

In IMS Node and VoLTE Test cases (MME Nodal, SGW Nodal, PGW Nodal, IP Application Node and Wifi Offload Gateway Nodal) available when Enable SMS-over-IP is selected.

In AMF Nodal / AMF Node, the SMS Over 5G NAS feature provides support for sending and receiving SMS messages using 5G NAS signaling. The SMS messages are carried in 5G UL NAS Transport (UE to network) and DL NAS Transport (network to UE) messages with a payload container type of SMS. SMS is handled in the MM layer for 5G. SMS Over 5G is supported in 5G NAS version 15.2 and later.

General Settings

Payload Type

 

 

  
 
Message Service   Basic Service   
 

 

Related Measurements

Measurements collected for SMS related processing are reported on the SMS report tab.


General Settings

NOTEs:
  • Tcl Parameters from S1-MME/SMS Tab will begin with S1. Ex. Protocol Identifier Tcl parameter from S1-MME/SMS Tab = S1SmsProtolId.
  • Tcl Parameters from Gm/SMS Tab on IMS Node will begin with ImsNode. Ex. Protocol Identifier Tcl parameter from Gm/SMS Tab (IMS Node) = ImsNodeSmsProtolId.
  • Tcl Parameters from Gm/SMS Tab on VoLTE TCs (e.g. MME Nodal, SGW Nodal, etc) will begin with UeNode. E.g. Protocol Identifier Tcl parameter from Gm/SMS Tab (VoLTE TCs) = UeNodeSmsProtolId.
  • Tcl Parameters from NAS-5G/SMS Tab in AMF Nodal will begin with 5g. Ex. Protocol Identifier Tcl parameter from NAS-5G/SMS Tab = 5gSmsProtolId.

 

Payload Type

Select Payload type. Support for vnd.3gpp.sms, CPIM and vnd.3gpp2.sms.

SMS over VOLTE is supported in accordance to 3GPP TS 24.341 and 24.011 specifications. The SM-over-IP sender builds and populates RP-DATA message. This message payload format is according to vnd.3gpp.sms format.

CPIM Message format for SMS over SIP is based on RFC #3428 and RFC# 3862.

 The CPIM message format encapsulates arbitrary MIME message content, together with message and its content. A Message/CPIM object is a two-part entity, where the first part contains the message metadata and the second part is the message content.  The two parts are separated from the enclosing MIME header fields and also from each other by blank lines. 

When vnd.3gpp2.sms is selected, the Data Coding Scheme option is CDMA ANSI/ASCII 7-bit. (Only available on AMF Nodal, MME Nodal and IMS Node on the Gm | SMS Tab)

Options: vnd.3gpp.sms or CPIM , vnd.3gpp2.sms (CDMA formatted SMS over IP Message Body with ANSI / ASCII 7-bit)

Tcl Parameter: ImsNodeSmsPayloadType

Tcl Parameter: UeSmsPayloadType

Protocol Identifier

Indicates the protocol identifier (when applicable) of the content of a short message.  

Range: 0 - 255

Default: 0 (Content reserved)

Tcl Parameter: SmsProtocolId

Tcl Parameter: S1SmsProtocolId

Tcl Parameter: UeSmsProtocolId

Tcl Parameter: ImsNodeSmsProtocolId

Tcl Parameter: 5gSmsProtocolId

Teleservice Identifier

Indicates the teleservice identifier. Available on IMS Node's Gm|SMS tab, when "Payload Type" is "vnd.3gpp2.sms". 

The default setting represents the pre-existing configuration with one Coding Scheme for "CDMA ANSI/ASCII 7-bit" and Message Content using ASCII characters.


When "Teleservice Identifier" is set to "Wireless Application Protocol (4100)", the Coding Scheme is changed to one selection for "Octet/unspecified" (ImsNodeSmsDataCoding Tcl value = 2) and the Message Content becomes Hex format. This is similar to Message Content for Payload Type = "vnd.3gpp.sms" and Coding Scheme = "GSM 8-bit Data" except for having a different max hex bytes. For Hex format, Message Content must begin with "0x". For Coding Scheme "Octet/unspecified", a maximum of 256 Hex bytes is allowed (or 514 text characters in the Message Content field that includes the leading "0x").

Options: "Cellular Messaging Teleservice (4098)" Tcl value 4098 (default), "Wireless Application Protocol (4100)" Tcl value 4100

Tcl Parameter: ImsNodeSmsTeleServiceId

Data Coding Scheme

Indicates a coding scheme used for coding the message content.  Select the required scheme from the dropdown list.

When Payload Type vnd.3gpp2.sms is selected, the Data Coding Scheme option is CDMA ANSI/ASCII 7-bit.

Default: GSM 7-bit coding scheme, CDMA ANSI/ASCII 7-bit , GSM 8-bit Data

When GSM 8-bit Data is selected, the Message Content is a Hex stream that begins with 0x with a maximum length of 320 bytes.

Tcl Parameter: SmsDataCoding

Tcl Parameter: S1SmsDataCoding

Tcl Parameter: UeSmsDataCoding

Tcl Parameter: ImsNodeSmsDataCoding

Tcl Parameter: 5gSmsDataCoding

Relative Validity Period

Indicates the time period for which a short message is valid.  The input value is interpreted as follows:

  • 0 to 143 (TP VP + 1) x 5 minutes (i.e. 5 minutes intervals up to 12 hours)
  • 144 to 167  12 hours + ((TP VP -143) x 30 minutes)
  • 168 to 196  (TP VP - 166) x 1 day
  • 197 to 255  (TP VP - 192) x 1 week

Range: 0 - 255

Default: 0

Tcl Parameter: SmsValidPeriod

Tcl Parameter: S1SmsValidPeriod

Tcl Parameter: UeSmsValidPeriod

Tcl Parameter: ImsNodeSmsValidPeriod

Tcl Parameter: 5gSmsValidPeriod

Wait Time for RP Ack (TR1)

Specify the time (in seconds) in which the relay-layer is expected to wait for an acknowledgement from a remote short message entity (SME).  

Range: 35 - 45

Default: 40

Tcl Parameter: SmsRpAckWaitTime

Tcl Parameter: S1SmsRpAckWaitTime

Tcl Parameter: UeSmsRpAckWaitTime

Tcl Parameter: ImsNodeSmsRpAckWaitTime

Tcl Parameter: 5gSmsRpAckWaitTime

Wait Time for TP Report (TR2)

Specify the time (in seconds) in which the relay-layer is expected to wait for its application to acknowledge it has received short message.  

Range: 12 - 20

Default: 16

Tcl Parameter: SmsTpReportWaitTime

Tcl Parameter: S1SmsTpReportWaitTime

Tcl Parameter: UeSmsTpReportWaitTime

Tcl Parameter: ImsNodeSmsTpReportWaitTime

Tcl Parameter: 5gSmsTpReportWaitTime

Wait Time for CP Ack (TC1)

Specify the time (in seconds) in which the connection-layer is expected to wait for an acknowledgement from a remote short message entity (SME). If this timer expires before the connection-layer receives an acknowledgement, the connection-layer can retransmit the message up to the maximum number specified in the CP-Retries parameter.

NOTE: The default value is set to 10 seconds, which is just enough to allow this layer to be able to send up to a maximum of 3 messages in case of the upper layer TR1 set to minimum of 35 seconds.

Range: 1 - 35

Default: 10

Tcl Parameter: SmsCpAckWaitTime

Tcl Parameter: S1SmsCpAckWaitTime

Tcl Parameter: UeSmsCpAckWaitTime

Tcl Parameter: ImsNodeSmsCpAckWaitTime

Tcl Parameter: 5gSmsCpAckWaitTime

CP-Retries

Specify the maximum times the connection-layer can retransmit a message.   

Range: 1 - 3

Default: 2

Tcl Parameter: SmsCpRetries

Tcl Parameter: S1SmsCpRetries

Tcl Parameter: UeSmsCpRetries

Tcl Parameter: ImsNodeSmsCpRetries

Tcl Parameter: 5gSmsCpRetries

 

 

^ Back to Top


Message Service

Basic Service
  • Send Messages: Select to enable Message Service fields to capture SMS messages and sending toward a service-centre device. Available when Payload Type = CPIM.

Tcl Parameter: SmsSendMsgEn

Tcl Parameter: S1SmsSendMsgEn

Tcl Parameter: UeSmsSendMsgEn

Tcl Parameter: ImsNodeSmsSendMsgEn

Tcl Parameter: 5gSmsSendMsgEn

  • Mobile Terminated Short Message: Indicates that a mobile device is responsible for generating SMS messages and sending toward a service-centre device.

Tcl Parameter: SmsMobTermMsgEn

Tcl Parameter: S1SmsMobTermMsgEn

Tcl Parameter: UeSmsMobTermMsgEn

Tcl Parameter: ImsNodeSmsMobTermMsgEn

Tcl Parameter: 5gSmsMobTermMsgEn

  • Mobile Originated Short Message: Indicates that a service-centre device is responsible for delivering SMS messages to a mobile device.

Tcl Parameter: SmsMobOrigMsgEn

Tcl Parameter: S1SmsMobOrigMsgEn

Tcl Parameter: UeSmsMobOrigMsgEn

Tcl Parameter: ImsNodeSmsMobOrigMsgEn

Tcl Parameter: 5gSmsMobOrigMsgEn

  • Include Priority: Indicates a message is a priority short message.

Tcl Parameter: SmsIcPrirityEn

Tcl Parameter: S1SmsIcPrirityEn

Tcl Parameter: UeSmsIcPrirityEn

Tcl Parameter: ImsNodeSmsIcPrirityEn

Tcl Parameter: 5gSmsIcPrirityEn

  • Include Status Report Request: Select the checkbox to include a status-report-request indicator in the outgoing messages to indicate that the sender requests the recipient to send a report back (to the sender).

Tcl Parameter: SmsIncStatusReqEn

Tcl Parameter: S1SmsIncStatusReqEn

Tcl Parameter: UeSmsIncStatusReqEn

Tcl Parameter: ImsNodeSmsIncStatusReqEn

Tcl Parameter: 5gSmsIncStatusReqEn

  • Message Start Delay (ms): Enter a value (in milliseconds) to specify the delay between the start generating SMS messages and the time when the device is ready for generating messages (i.e., the delay between the time a mobile successfully attaches to a network and the time the mobile device starts generating its first message). Available when Payload Type = CPIM.

Range: 0 - 4294967295

Tcl Parameter: SmsMsgStartDelay

Tcl Parameter: S1SmsMsgStartDelay

Tcl Parameter: UeSmsMsgStartDelay

Tcl Parameter: ImsNodeSmsMsgStartDelay

Tcl Parameter: 5gSmsMsgStartDelay

  • Message Interval (ms): Specify the delay (in milliseconds) between two consecutive generated messages. Available when Payload Type = CPIM.

Range: 0 - 4294967295

Tcl Parameter: SmsMsgInterval

Tcl Parameter: S1SmsMsgInterval

Tcl Parameter: UeSmsMsgInterval

Tcl Parameter: ImsNodeSmsMsgInterval

Tcl Parameter: 5gSmsMsgInterval

  • Message Cycle: Select the radio button to indicate continuous generation of SMS or a fixed number of SMS. Available when Payload Type = CPIM.
  • Continuous Message: When selected generates SMS messages till the stop-button is pressed
  • Fixed Number: When selected generates a fixed number of messages according to the value entered.

Tcl Parameter: SmsNumMsg

Tcl Parameter: SmsMsgCycleType

Tcl Parameter: S1SmsNumMsg

Tcl Parameter: S1SmsMsgCycleType

Tcl Parameter: UeSmsNumMsg

Tcl Parameter: UeSmsMsgCycleType

Tcl Parameter: ImsNodeSmsNumMsg

Tcl Parameter: ImsNodeSmsMsgCycleType

Tcl Parameter: 5gSmsNumMsg

Tcl Parameter: 5gSmsMsgCycleType

  • Message Content: Indicates the text message to be sent to the end-users on their devices or intended for other devices.  Available when Payload Type = CPIM. When GSM 8-bit Data Data Coding Scheme is selected, the Message Content is a Hex stream that begins with 0x with a maximum length of 320 bytes. When "Teleservice Identifier" is "CDMA Wireless Application Protocol (WAP) (4100) - 4100",  "Message Content" changes to "Hex Stream" which can input a maximom of 512 characters (256 bytes). Most of time CDMA MMS notification transfered with two fragmented SMS.

Option: Maximum of 160 characters

Tcl Parameter: SmsMsgContent

          Tcl Parameter: S1SmsMsgContent

Tcl Parameter: UeSmsMsgContent

          Tcl Parameter: ImsNodeSmsMsgContent

Tcl Parameter: 5gSmsMsgContent

 

^ Back to Top


 

Service Addresses

The SMS service requires the following addresses which are responsible for relaying the message between the local and remote parties:

  • Starting Originator Address (Select checkbox to to enable the capture of Starting Originator Address. Available when Send Messages is enabled)
  • Starting Recipient Address
  • Switching Center Address
  • Starting Originator MSISDN
  • Number or Originators

The SMS entity address consists the following parameters:

  • Type: Identifies the type of a number such as international number, national number, subscribes number, etc. (3-bit value).
  • Plan: The numbering plan identification provides extra information for categorizing a number such as ISDN/Telephone numbering plan, Data numbering plan, etc. (4-bit value).
  • Number: Indicates a valid MS address (enter 1 to 15 digits).

Tcl Parameters:

SmsOrigAddrType SmsOrigAddrPlan SmsOrigAddrNum
SmsRecipAddrType SmsRecipAddrPlan SmsRecipAddrNum
SmsScAddrType SmsScAddrPlan SmsScAddrNum
SmsOrigMsisdn SmsNumOrig  
S1SmsOrigAddrType S1SmsOrigAddrPlan S1SmsOrigAddrNum
S1SmsRecipAddrType S1SmsRecipAddrPlan S1SmsRecipAddrNum
S1SmsScAddrType S1SmsScAddrPlan S1SmsScAddrNum
S1SmsOrigAddrEn    
UeSmsOrigAddrType UeSmsOrigAddrPlan UeSmsOrigAddrNum
UeSmsRecipAddrType UeSmsRecipAddrPlan UeSmsRecipAddrNum
UeSmsScAddrType UeSmsScAddrPlan UeSmsScAddrNum
ImsNodeSmsOrigAddrType ImsNodeSmsOrigAddrPlan ImsNodeSmsOrigAddrNum
ImsNodeSmsRecipAddrType ImsNodeSmsRecipAddrPlan ImsNodeSmsRecipAddrNum
ImsNodeSmsScAddrType ImsNodeSmsScAddrPlan ImsNodeSmsScAddrNum
5gSmsOrigAddrType 5gSmsOrigAddrPlan 5gSmsOrigAddrNum
5gSmsRecipAddrType 5gSmsRecipAddrPlan 5gSmsRecipAddrNum
5gSmsScAddrType 5gSmsScAddrPlan 5gSmsScAddrNum
5gSmsOrigAddrEn    

 

 

 

^ Back to Top