Last updated: December 2, 2008
The AUTO connection type emulates a typical real world scenario where a GPRS or EGPRS capable mobile can initiate either a voice call or a data connection (not simultaneously). Alternatively the test set can initiate a voice call to simulate the mobile being called. Voice calls have priority over data connections. If a voice call is in progress, data transfer requests will be ignored. Originating a mobile terminated voice call while a data transfer is in progress will cause the data connection to be terminated.
Also see Operating Considerations .
This connection type is not applicable to GSM.
The BLER connection type ensures that an Agilent proprietary data connection type is used which allows the test set to obtain BLock Error Rate (BLER) measurement reports from the mobile station (see Block Error Rate (BLER) Reports Description ). In addition, the BLER connection type allows you to perform other GPRS measurements at the same time (except BER and ORFS due to Modulation).
Also see Operating Considerations .
This connection type is not applicable to GSM.
The ETSI Type A connection type ensures that packet data traffic channel (PDTCH) bursts are only transmitted on the uplink, not on the downlink. The number of downlink bursts is determined by the setting of the command CALL:(PDTCH|PDTChannel):MSLot:CONFig .
The Protocol Data Unit (PDU) count value can be set to one of two values: 0 or 4095. When the PDU is set to zero, the test set commands the mobile station to continually transmit PDUs as long as there is a connection between the mobile station and the test set. The default PDU count is 4095. When the PDU count is set to 4095 the test set commands the mobile station to send 4095 PDUs on the uplink TBF before the mobile station terminates the connection between the mobile station and the test set.
| NOTE |
The PDU count can be set in any operating mode, however the PDU count cannot be set during data transfer if the connection type is ETSI Type A, ETSI Type B (Unacknowledged) , or ETSI Type B Acknowledged . If an attempt is made to change the PDU count while in an invalid connection type the change will not occur and the front panel will display a message that states "Call operation rejected; Protocol request ignored".
The PDU count is only accessible via the GPIB command CALL:FUNCtion:DATA:ETSIA:PDUNit|PDU:COUNt .
Also see Operating Considerations .
This connection type is not applicable to GSM.
The ETSI Type B connection type ensures that one or more downlink (PDTCH) bursts are present, which can be used to loopback data through the uplink. ETSI Type B is required if you want to perform BER measurements in active cell mode.
Also see Operating Considerations .
This connection type is not applicable to GSM.
The ETSI Type B Acknowledged connection type is almost identical to the ETSI Type B (Unacknowledged) connection type, except that it features an acknowledged downlink. The acknowledged downlink ensures maximum compatibility with different mobile station types.
Also see Operating Considerations .
This connection type is only applicable to EGPRS.
The Switched Radio Block (SRB) Loopback connection type allows an EGPRS mobile to perform a layer one loopback while in a signaling mode. This ETSI defined standard test mode within the mobile is sometimes known as ETSI test mode C.
Also see Operating Considerations .
The operating mode must be Active Cell for any connection types to be used. For more information about Active Cell operating mode, see Active Cell Operating Mode .
These settings are not coupled to the serving cell which must be set to GPRS or EGPRS to allow the GPRS or EGPRS mobile to accept or originate data connections. See Serving Cell for more information.