User's Manual

Chapter 4 - Operation and Administration ASN-GW Menu
BreezeMAX Extreme 109 System Manual
4.6.2.3.3 Service Profile Type
The type of a service using the Service Profile. The options available in the current
release are Data, VoIP and Management.
4.6.2.3.4 HARQ Repetitions
HARQ (Hybrid-ARQ) is an ARQ (Automatic Repeat reQuest) mechanism that is
implemented at the physical layer together with FEC, providing improved link
performance over traditional ARQ at the cost of increased implementation
complexity. HARQ uses a combination of FEC and ARQ, where blocks of data,
along with a CRC code, are encoded using a FEC coder before transmission;
retransmission is requested if the decoder is unable to correctly decode the
received block. When a retransmitted coded block is received, it is combined with
the previously detected coded block and fed to the input of the FEC decoder.
Combining the two or more received versions of the code block improves the
chances of correctly decoding.
The WiMAX standard supports this by combining an N-channel stop and wait
ARQ along with a variety of supported FEC codes. Doing multiple parallel
channels of HARQ at a time can improve the throughput, since when one HARQ
process is waiting for an acknowledgment, another process can use the channel to
send some more data. WiMAX supports signaling mechanisms to allow
asynchronous operation of HARQ and supports a dedicated acknowledgment
channel in the uplink for ACK/NACK signaling. Asynchronous operations allow
variable delay between retransmissions, which provides greater flexibility for the
scheduler.
In the current release HARQ is not configurable: It is enabled by default for Data
and Management Services Profiles (4 repetitions) and disabled (1 repetitions) for
VoIP Service Profiles.
4.6.2.4 QoS Profiles
The QoS Profile submenu option for a selected Service Profile enables managing
the QoS Profiles assigned to the Service Profile. At least one QoS Profile must be
assigned to each Service Profile, up to a maximum of four QoS Profiles per Service
Profile.
Each QoS Profile includes the following components:
NOTE
In the current release only BE and NRT QoS Types are supported. For BE QoS Profiles only a a
value of 0 is supported for the CP parameters. For NRT QoS Profiles only values of 1 or 2 are
supported for the CP parameter.