E1968A GSM/GPRS GPIB COMMAND CHANGES

E1968A GSM/GPRS GPIB COMMAND CHANGES

Last updated: December 3, 2008

This section describes the GPIB command changes that occurred in the GSM commands and GPRS commands as the E1960A GSM Mobile Test Application functionality and the E1964A GPRS Mobile Test Application functionality moved to the E1968A GSM/GPRS Mobile Test Application.

Operating Mode Commands

The operating mode was determined by three separate GPIB commands in the E1960A GSM Mobile Test Application (TA):

CALL[:CELL]:OPERating:MODE  CALL | CELL | TEST

CALL[:CELL]:FUNCtion:DOWNlink  CW | BCH | BCHTCH

CALL[:CELL]:ACTivated  1 | ON | 0 | OFF

The operating mode command selected between active cell mode and test mode. When in active cell mode, the cell activated command determined the cell state. When in test mode, the downlink function command determined which test mode was used.

The above three commands have been replaced with a single combined operating mode command in the E1968A GSM/GPRS Mobile Test Application:

CALL[:CELL]:OPERating:MODE

     with the following parameters:

     CALL* | CELL | GBTest | GBTTest | PBTest | PBPTest | OFF | CW

*CALL and CELL are equivalent, CALL is always returned by the query form of the command.

All existing E1960A test code should be checked wherever the above three commands occur. In most cases, the new form of the operating mode command will be required. See CALL:OPERating:MODE .

CALL[:CELL]:FUNCtion:DOWNlink has been deleted and should be replaced by CALL[:CELL]:OPERating:MODE

CALL[:CELL]:ACTivated has been retained as an alias of CALL[:CELL]:OPERating:MODE

CALL[:CELL]:ACTivated 1 | ON  is replaced by  CALL[:CELL]:OPERating:MODE CALL

CALL[:CELL]:ACTivated 0 | OFF  is replaced by  CALL[:CELL]:OPERating:MODE OFF

Connection Type Commands

A new E1968A GSM/GPRS command CALL:FUNCtion:CONNection:TYPE has been added to control what type of connection can be made. This command replaces the E1964A GPRS Mobile Test Application command CALL:FUNCtion:DATA:TYPE which is also retained for backwards compatibility with existing E1964A test code. The new command accepts the following parameters:

A | B | ACKB | BLER | AUTO

The A, B, ACKB, BLER parameters are only applicable when licensed for GPRS. The AUTO parameter is only applicable when licensed for either GSM TA or the E6701C GSM/GPRS Lab Application (LA). When set to AUTO, either mobile originated or mobile terminated GSM voice calls can be made, or alternatively IP Data data connections can be made. Effectively, AUTO is equivalent to the GPRS LA IPData connection type for GPRS data connections, but adds capability for GSM voice calls.

When licensed for GSM (E1960A or E6701C license present), the default setting for connection type is AUTO meaning that existing GSM code will not need to be modified to take account of this new setting. If the GPRS TA only is licensed, this setting defaults to BLER.

The old GPRS TA/LA command CALL:FUNCtion:DATA:TYPE is maintained for backwards compatibility and is identical to the newer CALL:FUNCtion:CONNection:TYPE command except that IPData is used instead of AUTO.

GSM RF Generator Commands

The E1960A GSM Mobile Test Application CW test mode was specific to the E1960A Mobile TA only, it was accessed by the following commands:

CALL:OPERating:MODE TEST

CALL:FUNCtion:DOWNlink CW

The E1964A GPRS Mobile Test Application and the E6701B GPRS Lab Application Rev B did not have any form of CW mode. E1968A GSM/GPRS based applications use a CW operating mode which is common to all other TAs e.g. IS136 and WCDMA. The new CW operating mode is accessed as follows:

CALL:OPERating:MODE CW

Since the common CW operating mode is used for all formats, it does not support setting the CW frequency by specifying GSM band and ARFCN as these have no meaning in formats such as IS136. To maintain backwards compatibility with the E1960A GSM Mobile Test Application, the old CALL:RFG commands are supported but with some differences, these are explained below.

In the E1960A GSM Mobile Test Application there were no separate RFG settings, all RFG commands except frequency were actually aliases to other CELL commands, as shown below:

CALL[:CELL]:RFGenerator:BAND     -->    CALL[:CELL]:BAND

CALL[:CELL]:RFGenerator:CHANnel:[SELected]     -->    CALL[:CELL]:BCH:ARFCn:[SELected]

CALL[:CELL]:RFGenerator:CHANnel:EGSM     -->    CALL[:CELL]:BCH:ARFCn:EGSM

CALL[:CELL]:RFGenerator:CHANnel:RGSM     -->    CALL[:CELL]:BCH:ARFCn:RGSM

CALL[:CELL]:RFGenerator:CHANnel:DCS     -->    CALL[:CELL]:BCH:ARFCn:DCS

CALL[:CELL]:RFGenerator:CHANnel:PCS     -->    CALL[:CELL]:BCH:ARFCn:PCS

CALL[:CELL]:RFGenerator:CHANnel:GSM450     -->    CALL[:CELL]:BCH:ARFCn:GSM450

CALL[:CELL]:RFGenerator:CHANnel:GSM480     -->    CALL[:CELL]:BCH:ARFCn:GSM480

CALL[:CELL]:RFGenerator:CHANnel:GSM750     -->    CALL[:CELL]:BCH:ARFCn:GSM750

CALL[:CELL]:RFGenerator:CHANnel:GSM850     -->    CALL[:CELL]:BCH:ARFCn:GSM850

CALL[:CELL]:RFGenerator:POWer[:SAMPlitude]     -->    CALL[:CELL]:POWer:[SAMPlitude]

CALL[:CELL]:RFGenerator:POWer:AMPLitude     -->    CALL[:CELL]:POWer:AMPLitude

CALL[:CELL]:RFGenerator:POWer:STATe     -->    CALL[:CELL]:POWer:STATe

This meant that if you modified any RFG setting, it would reflect on its equivalant setting BCH setting. For example, if you modified CALL:RFG:BAND while in CW test mode, it would also change CALL:BAND, meaning that when you returned to Active Cell mode, the BCH BAND would have been changed.

In the E1968A GSM/GPRS Mobile Test Application there is no linkage between the CW mode parameters and BCH ARFCN, band and power parameters. CW mode maintains its own separate frequency, power and state parameters.

In the E1968A GSM/GPRS Mobile Test Application, the legacy GSM RFG commands are mapped onto common CW operating mode commands as shown below:

CALL[:CELL]:RFGenerator:POWer[:SAMPlitude]     -->    CALL[:CELL]:POWer:[SAMPlitude]:CW

CALL[:CELL]:RFGenerator:POWer:AMPLitude     -->    CALL[:CELL]:POWer:AMPLitude:CW

CALL[:CELL]:RFGenerator:POWer:STATe     -->    CALL[:CELL]:POWer:STATe:CW

The CALL[:CELL]:RFGenerator:FREQuency command exists unchanged from from the E1960A GSM Test Application.

The other GSM RFG band and channel commands do not have direct equivalent common CW operating mode commands. These commands have been implemented in the yuc code layer only, to provide a degree of backwards compatibility with E1960A code. This means that a *RST (or MUI full preset) will not reset these commands to their power on default values - their values do not change during a reset.

CALL[:CELL]:RFGenerator:BAND

CALL[:CELL]:RFGenerator:CHANnel:[SELected]

CALL[:CELL]:RFGenerator:CHANnel:PGSM

CALL[:CELL]:RFGenerator:CHANnel:EGSM

CALL[:CELL]:RFGenerator:CHANnel:RGSM

CALL[:CELL]:RFGenerator:CHANnel:DCS

CALL[:CELL]:RFGenerator:CHANnel:PCS

CALL[:CELL]:RFGenerator:CHANnel:GSM450

CALL[:CELL]:RFGenerator:CHANnel:GSM480

CALL[:CELL]:RFGenerator:CHANnel:GSM750

CALL[:CELL]:RFGenerator:CHANnel:GSM850

GSM RFAN Commands

The GSM RFAN commands are now obsolete and the GPRS RFAN commands should be used instead. To maintain backwards compatibility, the old GSM RFAN commands have been mapped onto the newer GPRS RFAN commands where possible. Where a direct mapping isn't possible, the setting has been created in the yuc code layer only to provide a degree of backwards compatibility. It is strongly recommended that previous code be changed over to the newer GPRS RFAN commands where ever possible.

One fundamental difference between GSM and GPRS RFAN commands is in GSM where there was only a single receiver expected power, therefore, when the receiver was under base station emulator control, changing MS TX Level would alter the single receiver expected power setting. This meant that if you switched from base station emulator (auto) control to RFAN (manual) control, the receiver expected power setting would remain the same as it was under base station emulator control until changed. There was a coupling between the base station emulator control MS TX Level and the manual expected power setting.

The E1968A GSM/GPRS Mobile Test Application does not retain this coupling between base station emulator (auto) and RFAN (manual) settings. The E1968A GSM/GPRS Mobile Test Application maintains separate settings for automatic and manual control, therefore, when you change to manual control in the E1968A, the receiver expected power and frequency settings will not necessarily remain the same, in fact it is likely that they will change. This means that receiver expected frequency and/or power must be explicitly set rather than assuming that it will be correct.

Another difference between the E1960A GSM and E1968A GSM/GPRS Mobile Test Application is in the expected power control and measurement and uplink (demod) receivers. E1960A GSM Mobile Test Application used a single auto/manual control that governed the expected power control and measurement and uplink (demod) receivers. The E1968A GSM/GPRS Mobile Test Application individually sets these settings.

The following shows how the GSM RFAN commands map onto the newer GPRS RFAN commands.

RFANalyzer:CONTrol:AUTO     -->     RFANalyzer:CONTrol:POWer:AUTO

                                                   -->     RFANalyzer:CONTrol:MEASurement:FREQuency:AUTO

The single GSM auto/manual control command maps onto the GPRS expected power control and measurement control commands. Note however that the uplink (demod) frequency control is not altered.

RFANalyzer:EXPected:POWer[:SELected]     -->     RFANalyzer:MANual:POWer:BURS1

RFANalyzer:MANual:FREQuency     -->     RFANalyzer:MANual:MEASurement:FREQuency

The GPRS RFAN commands do not support banded settings for either power or frequency, and do not support setting frequency in terms of ARFCN, so the following GSM RFAN commands have had legacy settings added into the yuc code to ensure a degree of backwards compatibility:

RFANalyzer:MANual:BAND

RFANalyzer:EXPected:POWer:PGSM

RFANalyzer:EXPected:POWer:EGSM

RFANalyzer:EXPected:POWer:RGSM

RFANalyzer:EXPected:POWer:DCS

RFANalyzer:EXPected:POWer:PCS

RFANalyzer:EXPected:POWer:GSM450

RFANalyzer:EXPected:POWer:GSM480

RFANalyzer:EXPected:POWer:GSM750

RFANalyzer:EXPected:POWer:GSM850

RFANalyzer:MANual:CHANnel[:SELected]

RFANalyzer:MANual:CHANnel:PGSM

RFANalyzer:MANual:CHANnel:EGSM

RFANalyzer:MANual:CHANnel:RGSM

RFANalyzer:MANual:CHANnel:DCS

RFANalyzer:MANual:CHANnel:PCS

RFANalyzer:MANual:CHANnel:GSM450

RFANalyzer:MANual:CHANnel:GSM480

RFANalyzer:MANual:CHANnel:GSM750

RFANalyzer:MANual:CHANnel:GSM850

These legacy settings will retain their existing values through a *RST or full preset operation, they will not be reset to their power on default values.

RFANalyzer:MSLot:MEASurement:BURSt     -->     CALL:PDTCh:MSLot:MEASurement:BURSt

Note that none of the legacy GSM RFAN commands have any coupling to the new command CALL:PDTCh:MSLot:MEASurement:BURSt command which selects which burst is measured. This setting must be set to 1 for GSM TCH measurements. See CALL:(PDTCH|PDTChannel):MSLot:MEASurement:BURSt . This command replaces RFAN:MSLot:MEASurement:BURSt.

Overlapped Commands

The E1960A GSM Mobile Test Application supported overlapped command functionality for the following commands:

CALL[:CELL]:BCHannel[:ARFCn][:SELected]

CALL[:CELL]:BCHannel[:ARFCn]:PGSM

CALL[:CELL]:BCHannel[:ARFCn]:EGSM

CALL[:CELL]:BCHannel[:ARFCn]:DCS

CALL[:CELL]:BCHannel[:ARFCn]:PCS

CALL[:CELL]:BCHannel[:ARFCn]:RGSM

CALL[:CELL]:BCHannel[:ARFCn]:GSM450

CALL[:CELL]:BCHannel[:ARFCn]:GSM480

CALL[:CELL]:BCHannel[:ARFCn]:GSM850

CALL[:CELL]:BCHannel[:ARFCn]:GSM750

CALL:END

CALL:MS:TADVance[:SELected]

CALL:MS:TADVance:PGSM

CALL:MS:TADVance:EGSM

CALL:MS:TADVance:DCS

CALL:MS:TADVance:PCS

CALL:MS:TADVance:RGSM

CALL:MS:TADVance:GSM450

CALL:MS:TADVance:GSM480

CALL:MS:TADVance:GSM850

CALL:MS:TADVance:GSM750

CALL:MS:TXLevel[:SELected]

CALL:MS:TXLevel:PGSM

CALL:MS:TXLevel:EGSM

CALL:MS:TXLevel:DCS

CALL:MS:TXLevel:PCS

CALL:MS:TXLevel:RGSM

CALL:MS:TXLevel:GSM450

CALL:MS:TXLevel:GSM480

CALL:MS:TXLevel:GSM850

CALL:MS:TXLevel:GSM750

CALL:TCHannel[:ARFCn][:SELected]

CALL:TCHannel[:ARFCn]:PGSM

CALL:TCHannel[:ARFCn]:EGSM

CALL:TCHannel[:ARFCn]:DCS

CALL:TCHannel[:ARFCn]:PCS

CALL:TCHannel[:ARFCn]:RGSM

CALL:TCHannel[:ARFCn]:GSM450

CALL:TCHannel[:ARFCn]:GSM480

CALL:TCHannel[:ARFCn]:GSM850

CALL:TCHannel[:ARFCn]:GSM750

CALL:TCHannel:CMODe[:VALue]

CALL:TCHannel:CMODe:HRSPeech:SCHannel

CALL:TCHannel:TSLot

In the E1968A GSM/GPRS Mobile Test Application, this functionality has been removed. All other commands with overlapped functionality, such as CALL:ORIGinate, still have overlapped functionality as before. This means that sending one of the above commands in the E1968A Mobile TA is equivalent to appending :SEQ in the E1960A Mobile TA. All of the above commands execute sequentially in the E1968A GSM/GPRS Mobile Test Application.

:SEQ

All of the above commands operate sequentially by default, therefore appending :SEQ is uneccessary, but is still supported.

:WAIT

In the E1960A GSM Mobile Test Application, the :WAIT GPIB extension could be used to convert a previously issued overlapped command into a sequential command. In the E1968A GSM/GPRS Mobile Test Application, overlapped functionality is not available for the above commands, therefore, this GPIB extension has no purpose. To maximise backwards compatibility, the :WAIT GPIB extension will be accepted without error for the above commands, but will be ignored. Ideally, :WAIT GPIB extensions should be removed from test code.

:DONE? And OPC?

These GPIB extensions no longer have any meaning for the above commands and will always return 1. It is recommended the above commands with :OPC? or :DONE? extensions be removed from test code.

Deferred Commands

To compensate for the loss of overlapped functionality in the above E1960A GSM commands, deferred commands have been added for the following settings:

CALL:SETup:TCHannel:MS:TXLevel[:SELected]

CALL:SETup:TCHannel:MS:TXLevel:PGSM

CALL:SETup:TCHannel:MS:TXLevel:EGSM

CALL:SETup:TCHannel:MS:TXLevel:DCS

CALL:SETup:TCHannel:MS:TXLevel:PCS

CALL:SETup:TCHannel:MS:TXLevel:RGSM

CALL:SETup:TCHannel:MS:TXLevel:GSM450

CALL:SETup:TCHannel:MS:TXLevel:GSM480

CALL:SETup:TCHannel:MS:TXLevel:GSM850

CALL:SETup:TCHannel:MS:TXLevel:GSM750

CALL:SETup:TCHannel[:ARFCn][:SELected]

CALL:SETup:TCHannel[:ARFCn]:PGSM

CALL:SETup:TCHannel[:ARFCn]:EGSM

CALL:SETup:TCHannel[:ARFCn]:DCS

CALL:SETup:TCHannel[:ARFCn]:PCS

CALL:SETup:TCHannel[:ARFCn]:RGSM

CALL:SETup:TCHannel[:ARFCn]:GSM450

CALL:SETup:TCHannel[:ARFCn]:GSM480

CALL:SETup:TCHannel[:ARFCn]:GSM850

CALL:SETup:TCHannel[:ARFCn]:GSM750

CALL:SETup:TCHannel:BAND

CALL:SETup:TCHannel:CMODe[:VALue]

CALL:SETup:TCHannel:CMODe:HRSPeech:SCHannel

CALL:SETup:TCHannel:TSLot

As with the E1964A GPRS TA, a handover is initiated with the CALL:HAND GPIB command.

Since the above deferred commands are new commands, there is no direct impact on previous test code. However, it is recommended previous test code be optimised to take advantage of the faster handovers possible using the new deferred commands.

Other Commands and Changes

CALL:COUNt:TDMA:FRAMes

In the E1960A GSM Mobile Test Application, this command specified the timeout period (in frames) within which a mobile must respond to a TCH assignment command such as a TCH ARFCN change. If this time was exceeded, an error was logged.

In the E1968A GSM/GPRS Mobile Test Application architecture, this command is redundant. It is supported for backwards compatibility reasons, but the setting doesn't do anything. It is recommended that this command be removed from previously written test code.

CALL:TCHannel:TSLot

This command now accepts values in the range 1 to 7 whereas previously, it was limited to 3 to 5. There is no impact on previously written test code.

CALL:BURSt:TYPE

This command now accepts the parameter RACH for GPRS as well as GSM. No impact on previously written test code.

CALL:STATus:TCHannel[:ARFCn]?

This command is now redundant, it is now an alias for CALL:TCHannel:ARFCn? which should be used instead.

CALL:STATus:TCHannel:BAND?

This command is now redundant, it is now an alias for CALL:TCHannel:BAND? which should be used instead.

CALL:STATus:TCHannel:TSLot?

This command is now redundant, it is now an alias for CALL:TCHannel:TSLot? which should be used instead.

SYSTem:APPLication:FORMat[:NAME]

In the E1985A Fast Switching Test Application, this command would fast switch between formats. In the E1968A GSM/GPRS Mobile Test Application, there is no fast switch between GSM and GPRS because the GSM and GPRS formats are integrated. To switch from another format e.g. WCDMA to GSM/GPRS, you can use any of the following parameters:

"GSM/GPRS" (preferred) or "GSM" or "GPRS"

The query will always return "GSM/GPRS".

It is strongly recommended that all instances of the SYS:APPL:FORM:NAMe command be removed where there is a fast switch between GSM and GPRS or vice-versa to optimise test plan execution. In the E1968A.GSM/GPRS Mobile Test Application this command does not perform any function and will waste time because the E1968A now integrates these two technologies. It is also recommended, though not essential, that the new format name "GSM/GPRS" be used when switching from other formats to the E1968A. Any code using the query form of this command must be modified to expect "GSM/GPRS" as the response.

SYSTem:APPLication:SELect[:NAME]

The name used for the E1968A is "GSM/GPRS Mobile Test Application".

New Commands

The following commands are new to the E1968A GSM/GPRS Mobile Test Application, consequently there will be no impact on existing test code.

CALL:TCHannel:PREDuction:LEVel[1|2]

Assigns a value in dB to power reduction level 1 or 2 - accepts values in the range 0 to 25 dB. This command works in the same manner as the existing E1964A GPRS command CALL:PDTChannel:PREDuction:LEVel[1|2].

CALL:TCHannel:PREDuction:BURSt

Specifies a power reduction level to use for the downlink TCH burst power - accepts either PRL1 or PRL2 as a parameter. This command works in the same manner as the existing E1964A GPRS command CALL:PDTChannel:PREDuction:BURSt[1|2|3|4].

CALL:TCHannel:PREDuction:UBURst

Specifies a power reduction level to use for the downlink TCH unused burst power - accepts either PRL1 or PRL2 as a parameter. This command works in the same manner as the existing E1964A GPRS command CALL:PDTChannel:PREDuction:UBURst.

CALL:TCHannel:POWer[:AMPLitude]?

Query only. Returns the downlink TCH used burst power in dB.

CALL:TCHannel:POWer[:AMPLitude]:UBURst?

Query only. Returns the downlink TCH unused burst power in dB.

CALL:MS:TXLevel:CCHannel[:SELected]

CALL:MS:TXLevel:CCHannel:PGSM

CALL:MS:TXLevel:CCHannel:EGSM

CALL:MS:TXLevel:CCHannel:RGSM

CALL:MS:TXLevel:CCHannel:DCS

CALL:MS:TXLevel:CCHannel:PCS

CALL:MS:TXLevel:CCHannel:GSM450

CALL:MS:TXLevel:CCHannel:GSM480

CALL:MS:TXLevel:CCHannel:GSM750

CALL:MS:TXLevel:CCHannel:GSM850

These commands specify the maximum burst power a mobile may uses for access bursts. At present this is an LA only feature. The range of values accepted is dependant on the band.

DCS band 0 to 28

PCS band 0 to 15 and 30 to 31

Other bands 0 to 31

These settings can only be changed when the operating mode is OFF.

CALL[:CELL]:MS:CCHannel:POWer:OFFSet:DCS

This command specifies an additional offset for use with the Max CCH value in the DCS band only. It accepts values in the range 0 to 3. This command is an LA only command, and can only be changed when the operating mode is OFF.

CALL:TRIGger[:OUTPut]:FRAMe:NIDLe:STATe

This command which was previously only available in the LA, is now available in the GSM and GPRS TAs.

CALL[:CELL]:BCHannel:SCELl

This command sets the serving cell, that is it determines the capabilities of the cell BCH generated by the base station emulator.

Parameters are license dependent and can include GSM | GPRS | EGPRS.

The EGPRS parameter is only applicable when licensed for EDGE. The GPRS parameter is only applicable when licensed for GPRS. If the only application licensed is GSM, you will be unable to change this setting. If you are licensed for GPRS, setting this parameter to GSM will mean that GPRS BCH information (sysinfo 13 etc) is not broadcast, therefore GPRS mobiles won't attempt to attach.

CALL:MS:REPorted:PCLass:EPSK:DCS

CALL:MS:REPorted:PCLass:EPSK:EGSM

CALL:MS:REPorted:PCLass:EPSK:GSM450

CALL:MS:REPorted:PCLass:EPSK:GSM480

CALL:MS:REPorted:PCLass:EPSK:GSM750

CALL:MS:REPorted:PCLass:EPSK:GSM850

CALL:MS:REPorted:PCLass:EPSK:PCS

CALL:MS:REPorted:PCLass:EPSK:PGSM

CALL:MS:REPorted:PCLass:EPSK:RGSM

CALL:MS:REPorted:PCLass:EPSK[:SELected]

CALL:MS:REPorted:PCLass:GMSK:DCS

CALL:MS:REPorted:PCLass:GMSK:EGSM

CALL:MS:REPorted:PCLass:GMSK:GSM450

CALL:MS:REPorted:PCLass:GMSK:GSM480

CALL:MS:REPorted:PCLass:GMSK:GSM750

CALL:MS:REPorted:PCLass:GMSK:GSM850

CALL:MS:REPorted:PCLass:GMSK:PCS

CALL:MS:REPorted:PCLass:GMSK:PGSM

CALL:MS:REPorted:PCLass:GMSK:RGSM

CALL:MS:REPorted:PCLass:GMSK[:SELected]

The above commands return the power class for each band in either the GSMK or EPSK (8PSK - EDGE) modulation scheme. This information is only made available during the attach procedure and therefore, is not available to the GSM TA.

CALL:MS:REPorted:MCLass:EGPRS:DCS

CALL:MS:REPorted:MCLass:EGPRS:EGSM

CALL:MS:REPorted:MCLass:EGPRS:GSM450

CALL:MS:REPorted:MCLass:EGPRS:GSM480

CALL:MS:REPorted:MCLass:EGPRS:GSM750

CALL:MS:REPorted:MCLass:EGPRS:GSM850

CALL:MS:REPorted:MCLass:EGPRS:PCS

CALL:MS:REPorted:MCLass:EGPRS:PGSM

CALL:MS:REPorted:MCLass:EGPRS:RGSM

CALL:MS:REPorted:MCLass:EGPRS[:SELected]

CALL:MS:REPorted:MCLass:GPRS:DCS

CALL:MS:REPorted:MCLass:GPRS:EGSM

CALL:MS:REPorted:MCLass:GPRS:GSM450

CALL:MS:REPorted:MCLass:GPRS:GSM480

CALL:MS:REPorted:MCLass:GPRS:GSM750

CALL:MS:REPorted:MCLass:GPRS:GSM850

CALL:MS:REPorted:MCLass:GPRS:PCS

CALL:MS:REPorted:MCLass:GPRS:PGSM

CALL:MS:REPorted:MCLass:GPRS:RGSM

CALL:MS:REPorted:MCLass:GPRS[:SELected]

The above commands return the power class for each band in either the GSMK or EPSK (8PSK - EDGE) modulation scheme as reported by the mobile during its attach procedure. This information is only made available during the attach procedure and therefore, is not available to the GSM TA.

CALL:MS:REPorted:SBANd[:GMSK]?

Returns a comma-separated list of all supported bands.

RFANalyzer:CONTrol:MEASurement:BURSt:AUTO <0 | 1 | OFF | ON>

This command determines how the receiver decides which uplink burst to measure. If set to the default "ON" state, the measurement burst will be determined automatically. When set to the "OFF" or manual state, the measurement is made on either burst 1 or 2 set by the following new command

RFANalyzer:MANual:MEASurement:BURSt <1 | 2>

This manual measurement burst command is active only when the control measurement burst auto is off. In the manual mode, if you attempt to measure burst 2 while on a GSM call, the TXP measurement will report an integrity error of `Parameter Error'.

CALL:PCTCh:MSLot:MEASurement:BURSt <1 | 2>

This new command sets which uplink burst will be measured for single slot measurements on dual uplink PDTCH's when the receiver measurement burst control is AUTO. This command setting has no effect on GSM calls where the measurement burst will always be 1.