Receiving SMS Messages Sent from the Mobile Station
Last updated: January 3, 2008
This section is applicable to the lab application and to a test application with the required feature license.
The test set supports receiving short messages sent from the mobile station (MS) in three methods.
Configurations Required for Receiving Mobile-Originated SMS Message
summarizes the test set configurations required for each method. For details on front panel operation, see
Mobile-Originated SMS Procedure
.
Conf
igurations Required for Receiving Mobile-Originated SMS Message
|
Methods
|
Call Status
|
Service Option
|
Message Type
|
Channel
|
Description
|
|
Method 1
|
Idle
|
Any value other than SO6 and SO14 (for example, SO1, SO2, SO3, SO9, SO33, etc.)
|
Point to Point
|
R-ACH
|
-
An SMS message is sent from the MS to the test set on the R-ACH (reverse access channel) via Data Burst Message. No call is established in this process.
-
If the message is too long for the R-ACH, the MS will attempt an SO6 or SO14 call to send an SMS message on the R-Traffic (reverse traffic channel) or R-FCH (reverse fundamental channel). The call will fail during service negotiation because the test set requires the MS to use the test set's service option setting. An error message appears for the error conditions. Use Method 2 (see below) for the long message.
See
Method 1: Receiving an SMS message while in idle state (current service option is other than SO6/SO14).
for front panel operation.
|
|
Method 2
|
Idle
|
SO6 or SO14
|
Point to Point
|
R-ACH or
R-Traffic (for IS-95 system)/R-FCH (for IS-2000 system)
|
-
If the message length is shorter than what is allowed on R-ACH, the MS will send the message on R-ACH. No call is established in this process. Same as Method 1 (see above).
-
If the message is too long for the R-ACH, the MS will attempt an SO6 or SO14 call to send an SMS message on the R-Traffic (reverse traffic channel) or R-FCH (reverse fundamental channel). See
Test Set Behavior In Method 2
for details.
See
Method 2: Receiving an SMS message while in idle state (current service option is SO6 or SO14)
for front panel operation.
|
|
Method 3
|
Connected
|
Any value other than SO6 and SO14 (for example, SO1, SO2, SO3, SO9, SO33, etc.)
|
Point to Point
|
R-Traffic (for IS-95 system)/R-FCH (for IS-2000 system)
|
Establish a voice or data call (other than SO6/SO14 connection). An SMS message is sent from the MS to the test set on the R-Traffic (reverse traffic channel) or R-FCH (reverse fundamental channel) via Data Burst Message. The call remains connected when the MS has finished sending the SMS message unless you disconnect the call.
See
Method 3: Receiving an SMS message while in a voice or data call.
for front panel operation
|
Test Set Behavior In Method 2
Standards specify that the shorter messages are sent on the R-ACH (Reverse Access Channel) and the longer messages are sent on the R-Traffic (reverse traffic channel) or R-FCH (reverse fundamental channel).
If the MS supports automatically selecting channel to transmit the SMS message based on the message length, the test set supports receiving SMS messages either from the R-ACH or R-Traffic/R-FCH channel while the current service option is SO6 or SO14.
-
If the message length is shorter than what can be sent on R-ACH, the MS will send the message on R-ACH. No call is established in this process. Same as Method 1 (see
Configurations Required for Receiving Mobile-Originated SMS Message
).
-
In the case of an MS Originate (MS initiated connection) with a current service option of SO6 or SO14, a call is established for the purpose of transferring an SMS message that is too long for the R-ACH.
When the test set receives an MS Originate event when the current service option is SO6 or SO14 and the service option is accepted by the MS, the SMS Status will change to "Originating". The test set then expects the MS to transmit an SMS message. The call is expected to be terminated by the MS sending an Release Order when the MS has finished sending the SMS message. Errors may occur if the SMS messages or the Release Order from the MS is not received within the timeout periods (see
SMS Call Drop Timer Control
for details). The test set will ensure that the SMS Status changes to a terminal state (Idle, if call ended without SMS message being received, or Received, when SMS message received). See
SMS Status Description
for details.
|
top
of page