5.2 Data Rate Control Performance

5.2 Data Rate Control Performance

Last updated: July 23, 2008


When the test set is configured to operate in a Test Application session using either FTAP (for subtype 0 physical layer), FETAP (for subtype 2 physical layer), or FMCTAP (for subtype 3 physical layer) with the DRC Value Fixed Mode Attribute set to Off, the test set works in a variable rate state and transmits the Forward Traffic Channel to the AT in accordance with the DRC Channel received from the AT. The Data Rate Control Performance of the AT is determined by measuring the average data throughput and Forward Traffic Channel PER.

The figure of merit is FTC Throughput and PER.

Method of Measurement

  1. Connect the access network emulator and AWGN to the AT.
  2. Set the DRC Value Fixed Mode Attribute to Off.
  3. Set the Forward Early Termination State to On and Set DRCLength to 2 slots.
  4. Set the Control Channel data rate to 38.4 kbps (because the default power level for 38.4 kbps Control Channel is high enough to overcome the large AWGN power required for these tests).
  5. Set the AN forward packet activity to 100%. Set the AT Direct Packet to 100%.
  6. Set Î or to -55 dBm/1.23 MHz.
  7. Set up a Test Application session, open a connection (FTAP connection for Subtype 0 or 1 Physical Layer, or FETAP connection for Subtype 2 Physical Layer, or FMCTAP connection for Subtype 3 Physical Layer).
  8. Perform test 1 which evaluate the AT's performance in AWGN (no fading), Set I oc as specified for the test.
  9. Perform test 2-5 which evaluate the AT's performance with fading, Set I oc as specified for each test.
  10. Calculate FTC Throughput and PER for each test.

Minimum Standard

PER shall not exceed 2% with 95% confidence. The average throughput shall exceed the values in Table 5.2.3-1 in C.S0033

Related Topics

Manual Operation: Testing 5.2 Data Rate Control Performance

Programming a Packet Error Rate (PER) Measurement

Packet Error Rate (PER) Measurement Description

Packet Error Rate Measurement Troubleshooting