Last updated: December 2, 2008
This section is only applicable to the EGPRS lab application.
Support for incremental redundancy in the test set allows you to verify a mobile station's implementation of Type II hybrid ARQ (incremental redundancy), as well as stress the mobile station's memory and processor. The Wireless Protocol Advisor (WPA) software (see Protocol Logging ) also provides full tracing of the current modulation and coding scheme and the puncturing scheme.
By default, the test set sends 1/3 convolutionally encoded RLC data blocks using puncturing scheme 1 (PS1). When incremental redundancy is enabled, the test set begins transmitting RLC data blocks using PS1 and retransmits blocks using the next puncturing scheme based either on Negative Acknowledgments (NACKs) received from the mobile station for specific RLC block numbers or, if there is no new data to send, for RLC blocks that have not yet been acknowledged or not acknowledged. For additional retransmissions, the test set continues to cycle through the available puncturing schemes for the selected modulation and coding scheme (MCS) until the blocks are acknowledged.
The mobile station must be able to store the original received bits in memory for failed block transmissions, combine those bits with retransmissions of the same block using different puncturing schemes, and decode the combined bits until the decode is successful.
You can force the mobile station to NACK RLC blocks by defining some downlink blocks to be corrupted intentionally by the test set. See Downlink Corruption for more information.
When the mobile station no longer has enough memory to perform incremental redundancy, it indicates this by setting the MS_OUT_OF_MEMORY field in the EGPRS Packet Downlink Ack/Nack message. In response to this indication, the test set stops sending new blocks to the mobile station and only retransmits blocks that have already been NACKed by the mobile station. Only when the mobile station sends an indication that enough memory has been freed up for normal operation does the test set begin transmitting new blocks.
The test set does not allow you to change the state of incremental redundancy for uplink TBFs. This situation exists because the test set does not yet support link adaptation to MCS below MCS-5. This would require splitting RLC blocks in half for transmission and then resegmenting the split blocks by the receiver. By ordering the mobile station to not resegment retransmitted RLC data blocks in RLC MAC control messages, the test set is turning on incremental redundancy for uplink TBFs, as specified in 3GPP TS 04.60, Section 9.3.2.1.
You can observe the use of incremental redundancy on uplink TBFs by setting up the test set to intentionally NACK a percentage of correctly received uplink blocks. Incorrectly received blocks are always NACKed and do not affect the specified percentage of good blocks to be NACKed.
| NOTE |
The operating mode must be Active Cell and the serving cell must be EGPRS. However, the forced uplink retransmission parameter can be changed in other operating modes, but does not affect the test set's operation until the operating mode is changed to Active Cell.
The forced uplink retransmission parameter is applicable in all connection types.
This section is only applicable to the EGPRS lab application. The Window Size for GPRS operation is fixed to 64 bits. According to 3GPP TS 51.010, section 14.18.7, one of the conditions that Incremental Redundancy requires for the MS to achieve a long-term throughput of 20 kbps per time slot measured between the LLC an RLC/MAC layer is that the transmit window size be set to Maximum.
The window size parameters set the RLC window size on the downlink for EGPRS. The window size can be set to the maximum allowable value for the number of downlink slots or the minimum window size for all timeslots. The maximum and minimum allowed window sizes can be found in 3GPP TS 04.60, Table 9.1.9.2.1.
The test set allows you to set the window size for different Data Connection Types. The parameters available in the test set are:
Window Size (Current)
This parameter sets the window size for the current Data Connection Type.
The GPIB command to set this parameter is CALL:(PDTCH|PDTChannel):WINDow:SIZE:SELected .
Window Size (Auto)
This parameter sets the window size that the test set uses when the Data Connection Type is set to
Auto
.
The GPIB command to set this parameter is CALL:(PDTCH|PDTChannel):WINDow:SIZE:AUTO .
Window Size (Other)
This parameter sets the window size that the test set uses when the Data Connection Type is not set to
Auto
.
The GPIB command to set this parameter is CALL:(PDTCH|PDTChannel):WINDow:SIZE:OTHer .
The window size specified by these parameters will be used with the next TBF that is established, not with the current TBF if one is in progress.
These parameters are applied to both uplink and downlink TBFs.
| NOTE |
This procedure is only applicable to the EGPRS lab application. (The Window Size for GPRS operation is fixed to 64 blocks.) This procedure describes how you manually configure the RLC/MAC Window Size parameter for different Data Connection Types in the test set.
Protocol Control
(
F4
).
RLC/MAC
(
F2
).
Window Size
(
F3
). This displays the
Window Size Parameters
menu. To configure the Window Size via the GPIB interface, use the command appropriate for your Data Connection Type. See Window Size for more information.
The test set currently allows you to configure all the fields in the protocol stack according to the Method of Test for Incremental Redundancy Performance defined in 3GPP TS 51.010 Section 14.18.7. It is currently necessary to use a method external to the test set to evaluate the throughput between the LLC and RLC/MAC layers.
The operating mode must be Active Cell and the serving cell must be EGPRS. However, parameters associated with Incremental Redundancy can be changed in other operating modes, but do not effect the test set's operation until the operating mode is changed to Active Cell.
The Incremental Redundancy State parameter is only applicable when the connection type is set to Auto.
How do I test Incremental Redundancy?
Tips for analyzing protocol logs of Incremental Redundancy and Retransmission MCS Switching