|
|
F-Traffic Format
Last updated: July 23, 2008
This section is only applicable to the lab application and to a test application with the required feature license.
F-Traffic Format
determines the specific DRC value and the transmission format (packets, slots, preamble) used to transmit the forward traffic test packets when the following conditions are met:
In the Active Cell operating mode, the test set uses the DRC value requested by the access terminal to set its forward transmission format, in the Active Cell operating mode:
-
When the
DRC Value Fixed Mode Attribute
is set to on and the Physical Layer Subtype is set to subtype 2, the test set sends the DRCValueFixedMode attribute in the FETAP Parameter Assignment message (see
Enhanced Test Application Protocol
), then sets the DRC Value for this attribute according to the
F-Traffic Format
setting. This means that the test set tells the access terminal to always request the DRC value that corresponds to the specified
F-Traffic Format
setting. The test set uses the specified transmission format associated with that DRC value to transmit the forward traffic packet.
-
When the
DRC Value Fixed Mode Attribute
is set to on and the Physical Layer Subtype is set to subtype 3, the test set sends the DRCValueFixedModeMC attribute in the FMCTAP Parameter Assignment message (see
Multi-carrier Test Application Protocol
), then sets the DRC Value for this attribute according to the
F-Traffic Format
setting. This means that the test set tells the access terminal to always request the DRC value that corresponds to the specified
F-Traffic Format
setting. The test set uses the specified transmission format associated with that DRC value to transmit the forward traffic packet.
-
When the
DRC Value Fixed Mode Attribute
is set to off, the AT requests the DRC value based on the current link conditions as in real system operation. Because the subtype 2 or subtype 3 physical layer supports multiple transmission formats in response to a DRC value requested by the AT, the
F-Traffic Config
determines which transmission format is used for each requested DRC value.
In the Test operation mode, You must select a
F-Traffic Format
as listed in the table below to match your AT's configuration because there's no signaling exchanged between the AN an the AT. What you set (including forward traffic DRC, transmission format (packets, slots, preamble), as well as the corresponding modulation type) is then displayed on the Call Setup screen in the Configuration Information window.
The table below shows the configuration of the forward traffic packet for each DRC value.
-
The characters in italic font for each DRC Value is called the
canonical
transmission format. The canonical transmission format is defined as the transmission format with the largest packet size for a given DRC Value. Additional transmission formats for the DRC Value are called
short packet
(or
non-canonical
) transmission formats.
-
The DRC Value is defined by the Rate Metric and the Nominal Duration (slots).
-
The Rate Metric for a DRC Value is defined as the Nominal Data Rate of the canonical transmission format of the DRC Value.
DRC Value and Forward Transmission Formats
|
F-Traffic Format |
DRC Value |
Single-User Transmission Format
(physical layer packet size in bits, number of slots, preamble length in chips) |
Modulation Format |
Nominal Duration (slots)
|
Rate Metric
(kbps) |
Nominal Data Rate
(kbps) |
|
1 (128, 16, 1024) |
0x1 |
(128, 16, 1024) |
QPSK |
16 |
38.4 |
4.8 |
|
1 (256, 16, 1024) |
(256, 16, 1024) |
9.6 |
|
1 (512, 16, 1024) |
(512, 16, 1024) |
19.2 |
|
1 (1024, 16, 1024)
|
(1024, 16, 1024)
|
38.4
|
|
2 (128, 8, 512) |
0x2 |
(128, 8, 512) |
QPSK |
8 |
76.8 |
9.6 |
|
2 (256, 8, 512) |
(256, 8, 512) |
19.2 |
|
2 (512, 8, 512) |
(512, 8, 512) |
38.4 |
|
2 (1024, 8, 512)
|
(1024, 8, 512)
|
76.8
|
|
3 (128, 4, 256) |
0x3 |
(128, 4, 256) |
QPSK |
4 |
153.6 |
19.2 |
|
3 (256, 4, 256) |
(256, 4, 256) |
38.4 |
|
3 (512, 4, 256) |
(512, 4, 256) |
76.8 |
|
3 (1024, 4, 256)
|
(1024, 4, 256)
|
153.6
|
|
4 (128, 2, 128) |
0x4 |
(128, 2, 128) |
QPSK |
2 |
307.2 |
38.4 |
|
4 (256, 2, 128) |
(256, 2, 128) |
76.8 |
|
4 (512, 2, 128) |
(512, 2, 128) |
153.6 |
|
4 (1024, 2, 128)
|
(1024, 2, 128)
|
307.2
|
|
5 (512, 4, 128) |
0x5 |
(512, 4, 128) |
QPSK |
4 |
307.2 |
76.8 |
|
5 (1024, 4, 128) |
(1024, 4, 128) |
153.6 |
|
5 (2048, 4, 128)
|
(2048, 4, 128)
|
307.2
|
|
6 (128, 1, 64) |
0x6 |
(128, 1, 64) |
QPSK |
1 |
614.4 |
76.8 |
|
6 (256, 1, 64) |
(256, 1, 64) |
153.6 |
|
6 (512, 1, 64) |
(512, 1, 64) |
307.2 |
|
6 (1024, 1, 64)
|
(1024, 1, 64)
|
614.4
|
|
7 (512, 2, 64) |
0x7 |
(512, 2, 64) |
QPSK |
2 |
614.4 |
153.6 |
|
7 (1024, 2, 64) |
(1024, 2, 64) |
307.2 |
|
7 (2048, 2, 64)
|
(2048, 2, 64)
|
614.4
|
|
8 (1024, 2, 64) |
0x8 |
(1024, 2, 64) |
QPSK |
2 |
921.6 |
307.2 |
|
8 (3072, 2, 64)
|
(3072, 2, 64)
|
8-PSK |
921.6
|
|
9 (512, 1, 64) |
0x9 |
(512, 1, 64) |
QPSK |
1 |
1228.8 |
307.2 |
|
9 (1024, 1, 64) |
(1024, 1, 64) |
614.4 |
|
9 (2048, 1, 64)
|
(2048, 1, 64)
|
1228.8
|
|
A (4096, 2, 64)
|
0xA |
(4096, 2, 64)
|
16-QAM |
2
|
1228.8
|
1228.8
|
|
B (1024, 1, 64) |
0xB |
(1024, 1, 64) |
QPSK |
1 |
1843.2 |
614.4 |
|
B (3072, 1, 64)
|
(3072, 1, 64)
|
8-PSK |
1843.2
|
|
C (4096, 1, 64)
|
0xC |
(4096, 1, 64) |
16-QAM |
1 |
2457.6 |
2457.6
|
|
D (5120, 2, 64)
|
0xD |
(5120, 2, 64)
|
16-QAM |
2 |
1536.0 |
1536.0
|
|
E (5120, 1, 64)
|
0xE |
(5120, 1, 64)
|
16-QAM |
1 |
3072.0 |
3072.0
|
Operating Considerations
-
You should set the
F-Traffic Format
to the canonical transmission format of a DRC value if your AT does not support short packet transmission formats.
-
In some cases, changing the
F-Traffic Format
may result in an error message posted (see
Short Packet Enabled Threshold
for details).
-
The actual number of slots transmitted for each transmission format may be less depending upon the
Max Forward Packet Duration
.
-
Signaling messages are always sent in the canonical format. This is to avoid the Signaling Link Protocol (SLP) from having to make very small fragments for the signaling messages that would be required with some non-canonical formats and forced single encapsulation (required for Test Applications).
|
|
top
of page