GSM Radio Quality Metrics (Compact 7)
3/12/2014
This test is designed to test the basic BSP radio/RIL functionality, and can be used for BSP radio/RIL validation.
| Area | Case Name | Case ID | Description | Iteration | Expected Pass Rate |
|---|---|---|---|---|---|
Voice |
TSP_OutNormal |
101 |
Outgoing call to the dial-up server. |
10 |
100% |
_ |
TSP_InNormal |
105 |
Outgoing call to the dial-up server, sending DTMF, incoming call from the dial-up server. |
10 |
100% |
Data |
DAT_Download |
201 |
Download data. |
1 |
100% |
_ |
DAT_Upload |
202 |
Upload data. |
1 |
100% |
SMS |
SMS_SendRecv |
301 |
Send short messages to self. |
10 |
100% |
_ |
SMS_LongMessage |
302 |
Send long (>160) messages to self. |
2 |
100% |
Radio |
TSP_SetEquipmentState |
801 |
Turn radio off and on. |
1 |
100% |
Manual Test Engineer intervention is required for the setup and configuration of this test.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The test should be run with Windows Embedded image with Cellcore enabled.
Additional Hardware Requirement:
SIM Card
Phone Device:
To run this test, a connection to a phone network is required. Also a phone PIN and phone number must be programmed in to the phone.
This information will be stored on a SIM card that will be inserted into the phone. You also need to determine the carrier that you will be using.
You must then gather information needed about the specific services provided by the carrier that are configured on a specific SIM card. It is a good idea to locate the PIN Unlock Key (PUK) for the SIM in case the incorrect PIN is entered and the SIM is locked. Typically, if the wrong PIN is typed in more than three times the SIM card can become locked. The PUK code can be used to unlock the SIM to allow testing to continue.
Test Setup Options
Two options are supported to allow these tests to be run. One method uses two phones under control of the test software. These phones use SMS to control the execution of the client / server test setup. The other method is to set up a dial-up server using a PC and a special dial-up server card. This method uses dial DMTF tones to control the execution of the tests.
Two Phones
Refer to the Test Kit Help for more information on how to work with the Two Phone Setup.
Dial-up Server
To allow the tests to be conducted access to a dial-up server is required. This dial-up server will answer the call from the device under test and process and respond to DMTF tones. The dial-up server is essentially an Interactive Voice Response (IVR) system that emulates a "real" telephone. Server functionality typically includes:
• Answer an incoming call and end the call after a few seconds
• Call back a specified number
• Play "music on hold"
• Basic Circuit Switched Data (CSD) test functionality
• No answer line
• Always busy line
The voice functionality provided by the dial-up server is enabled by sending DTMF tones to the server. To initiate voice functions, call the voice line, wait for an answer and then send an appropriate command via DTMF.
| Function | DTMF Sequence |
|---|---|
Play greeting and end the call |
001* |
Stay connected until caller ends the call |
002[#L]* |
Call back |
003#XXXXXXX[#D][#L]* |
Call back every N seconds for M minutes |
004#Y#Z#XXXXXXX[#D][#L]* |
Microsoft provides a demonstration dial-up server that is located in the United States. It uses toll phone lines and can be in use or under maintenance and otherwise unavailable. Use of this dial-up server is intended only to assist with the development and testing of mobile devices.
The following table shows the phone numbers necessary to access the dial-up server functionality.
| Call type | Phone Number |
|---|---|
Voice call |
(425) 727-2470 |
Busy call |
(425) 727-2024 |
No answer |
(425) 727-2773 |
Data call |
(425) 727-2455 |
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
101 |
Outgoing call to the dial-up server. |
105 |
Outgoing call to the dial-up server, sending DTMF, incoming call from the dial-up server. |
201 |
Download data. |
202 |
Upload data. |
301 |
Send short messages to self. |
302 |
Send long (>160) messages to self. |
801 |
Turn radio off and on. |
Setting Up the Test
To run this test, a connection to a phone network is required and the phone PIN and phone number must be programmed in to the phone.
1. Locate the SIM PIN code and the phone number of the phone that will be used for testing. You may be able to locate the phone number of the device under test by calling a phone with the Caller ID service.
2. Locate the stinger.ini that corresponds to the type of build that you are using.
3. Using a plain text editor, such as Notepad, make changes to the stinger.ini file to reflect your TelCo carrier information.
a. To set a phone number of 14257272470, locate and change the following line in the stinger.ini, note preceding "+".
SIM_VOICE_NUMBER=+14257272470
b. To set a SIM PIN code of 1234, locate and change the following line in the stinger.ini:
RILT_SIM_PWD=1234
c. Set the GPRS access point to the carrier you will be using in the stinger.ini file. Check with the carrier for the access point address that should be used for a specific SIM card. Some example access points are shown:
* For AT&T / Cingular User: RILT_GPRS_APN= isp.cingular
* For T-Mobile User: RILT_GPRS_APN=internet3.voicestream.com
* For Orange User: RILT_GPRS_APN= orangeinternet
* For BT User: RILT_GPRS_APN= adf.btcellnet.net
4. Depending on the specifics of the network you are connecting to the following items may also need to be configured in the stinger.ini file. The settings are grouped below.
Dial Service Phone Numbers:
These numbers are used to dial into a live phone number that provides dedicated services for dial-up phone network testing.
| Parameter | Description |
|---|---|
DS_VOICE_NUMBER0 |
Telephone number for outgoing call test. |
DS_VOICE_NUMBER1 |
Telephone number 1 for conference call test. |
DS_VOICE_NUMBER2 |
Telephone number 2 for conference call test. |
DS_NUMBER_BUSY |
Busy line telephone number. |
DS_NUMBER_NoAnswr |
No answer line telephone number. |
SIM Card Carrier Settings
| Parameter | Description |
|---|---|
RILT_SIM_PWD |
SIM PIN code. |
MAX_GPRS_APN_COUNT |
Supported maximum simultaneous APN counts. |
SIM_VOICE_NUMBER |
Telephone number for the device under test. |
GPRS_APNn |
Access entry name of APN n, n could be 1, 2, …, 9. |
The GPRS_APNn will often have multiple entries, for example a stinger.ini file could contain:
// Max APN count for the target device and network, if MAPN is not supported then set it to 1
MAX_GPRS_APN_COUNT=3
// APN1
GPRS_APN1=wap.myTelCo.com
// APN2
GPRS_APN2=internet2.myTelCo.com
// APN3
GPRS_APN3=epc.myTelCo.com
// Set APN4, APN5, ...APN9 if the device/network support them
Additional Optional Test Settings
These settings can be modified to change the behavior of the test.
| Parameter | Description |
|---|---|
GPRS_MAPN_SIZE (optional) |
Download data size of MAPN test. By default, the size is 1 MB. |
BLOCKS_PER_SESSION (optional) |
Block counts of each GPRS session. By default, the block count is 40. |
BLOCK_SIZE (optional) |
Data size of each block. By default, the block size is 256 KB. |
DOWNLOAD_URL (optional) |
URL for GPRS test. By default, the URL is http://www.sfone.net/gprs.zip. |
GPRS_USERNAMEn (optional) |
User name of APN n. |
GPRS_PASSWORDn (optional) |
Password of APN n. |
GPRS_DOMAINn (optional) |
Domain name of APN n. |
SMS_TIMEOUT (optional) |
Max waiting time of SMS test. |
In addition to these settings a value for a linear SIM record is specified in the stinger.ini file:
SMT_LINEARRECORD=6F17
Set Own Number Utility - Scale Up of Testing
A "setownnumber" utility may be available to set the phone number on the SIM chip. This can be useful when attempting to manage groups of phones under test. The utility can be invoked via platform builder using the following syntax.
s setownnumber -add 4255551212
Running the Test
Running the Test - Dial-Up Server
Run the test and then view the log to see the test results.
Optional Command Line Information
tux -o -d cellulartest -c"-metrics all -dtmfds -own_number <dial number> -gprs_apn <apn> -gprs_username <user name> -gprs_pw <password>"
Verifying the Test
When the test completes running, verify that "PASS" appears in the test log.
Troubleshooting the Test
Determine the point of failure and record the exact error message. Check that the setup steps were followed and that all prerequisites were met. If the source code is available, examine the point of failure in code to see if any additional information can be gathered about the failure domain.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.