You may need to upgrade the hardware in your test set to get the capability described here. If you install application firmware on a test set with incompatible hardware, the following may occur:
-
Your test set may lock up.
-
The application may not run.
-
Some features in the application may not be accessible, or may not perform to specifications.
Please review the hardware requirement information at
http://www.agilent.com/find/8960upgrades
to determine if a hardware upgrade is required for your testing needs.
This section details the test set's operation for the following:
By default, the test set does not make available multislot configurations or modulation coding schemes that it does not support for combinations of the following parameters: Operating Mode, Connection Type, Multislot Configuration, and Modulation Coding Scheme (MCS).
Unsupported data rate configurations can be enabled using the CALL:DATA:RATE:CONFig command (see
CALL:DATA:RATE:CONFig[:EGPRs]
) or from the test set's front panel (see
How Do I Gain Access to All the EGPRS Multislot Configurations?
). The value of this parameter can be set to either Supported or All.
Supported Configurations
The test set provides consistent support for the configurations indicated by an LA or LA/TA in the following table, where LA signifies that the test set provides consistent support for the specified multislot configuration in the Lab Application and LA/TA signifies that the test set provides consistent support for the specified multislot configuration in both the Lab Application and the Test Application. The multislot configurations in the table are indicated as Downlink x Uplink. ETSI Type A, BLER, Auto, ETSI Type B (Unack), ETSI Type B (Ack), and SRB Loopback are all connection type parameters. MCS-1 through MCS-4 use GMSK modulation, while MCS-5 through MCS-9 use 8PSK modulation.
Supported Multislot Configurations by Operating Mode and Connection Type
|
|
Active Cell Operating Mode
EGPRS Serving Cell |
EGPRS BCH+PDTCH
Operating Mode |
All Configurations Allowed
|
|
|
ETSI Type A |
BLER |
Auto
ETSI Type B (Unack)
ETSI Type B (Ack)
SRB Loopback |
|
|
MCS-1 to
MCS-4 |
MCS-5 to
MCS-9 |
MCS-1 to
MCS-4 |
MCS-5 to
MCS-9 |
MCS-1 to
MCS-6 |
MCS-7 to
MCS-9 |
MCS-1 to
MCS-4 |
MCS-5 to
MCS-9 |
MCS-1 to MCS-9 |
|
1x1 |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
1x2 |
LA/TA |
LA/TA |
|
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA* |
|
1x3
|
LA/TA |
LA/TA |
|
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA* |
|
1x4
|
LA/TA |
LA/TA |
|
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA* |
|
1x5
|
LA/TA |
LA/TA |
|
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA* |
|
2x1 |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
2x2 |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
2x3
|
LA/TA |
LA/TA |
|
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA* |
|
2x4
|
LA/TA |
LA/TA |
|
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA* |
|
3x1 |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
3x2 |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
3x3
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
4x1 |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
4x2
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
|
5x1
|
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
LA/TA |
*Not available for the BLER connection type
See
All Configurations
for more details.
Operating Considerations for Supported Configurations
Attempting to set the test set to an unsupported downlink multislot configuration or modulation coding scheme generates the following warning messages
GPRS/EGPRS functionality restriction; Requested multislot configuration not supported
.
GPRS/EGPRS functionality restriction; Requested modulation coding scheme not supported.
If you change the Connection Type to an option that makes the current multislot configuration and modulation coding scheme combination unsupported, the multislot configuration is reset to the default value of 2x1. For example, if the multislot configuration is 1x2 and the modulation coding scheme setting is MCS-5, changing the connection type from ETSI Type B to BLER causes the multislot configuration to return to the default value of 2x1.
All Configurations
To gain access to the multislot configurations and modulation coding schemes not indicated as supported in the table above, you must set the EGPRS Data Rate Configurations parameter value to All.
When you change the
EGPRS Data Rate Configurations
parameter value to
All
, the following warning message appears on the front panel screen:
Warning: Not all EGPRS data rate configurations are supported
.
Remember that although you now have access to all EGPRS data rate configurations, the performance of those not supported by the test set is not guaranteed.
The following multislot configurations are not available in the EGPRS Test Application, regardless of the EGPRS Data Rate Configuration parameter setting:
-
2 Down, 4 Up
-
3 Down, 3 Up
-
4 Down, 2 Up
-
5 Down, 1 Up
Multislot configurations that have more uplink timeslots than downlink timeslots are not available while the
Connection Type
is set to
BLER
, regardless of the EGPRS Data Rate Configuration parameter setting.
Why use Unsupported Data Rate Configurations?
While the test set may not currently guarantee support for all EGPRS data rate configurations, some unsupported configurations can still be used to verify your mobile station's capabilities if you need to perform a quick verification rather than intensive testing. When using unsupported configurations the following considerations apply:
-
In general, unsupported configurations may work if you minimize other activities such as receiver measurements (or protocol logging in the lab application).
-
If you want to use the data channel (lab application only) to verify your mobile station's ability to transmit 2 timeslots using 8PSK modulation use the following combination:
-
multislot configuration - 2x2
-
modulation coding scheme - MCS-5
-
connection type - Auto
-
data channel application - something with intermittent data like WAP transfers. (Avoid ftp transfers.)
Additionally, you should perform activities such as receiver measurements and protocol logging one at a time. For example, turn off logging while performing a receiver measurement and turn off receiver measurements while using protocol logging. Unidirectional transfers such as uplink FTP or downlink FTP are also a good way to minimize loading in the downlink or uplink, respectively.
top
of page