How many saw can be done in TDD Harq process and what is max retransmission on MAC PDU?

How many saw can be done in TDD Harq process and what is max retransmission on MAC PDU?
As in FDD it is 8 saw continous and mex retex is 4.
As polling bit zero does not send any ack nack message, as this does not need RLC status, PDU in AM, so here can be the problem for MAC?.

For TDD it’s change per config basis i.e. for config 0 it’s different, for config 1 it’s different.
There is concept of K value which indicates after how many subframe ue will indicate Harq acknowledgment.

Ok, so that will be a lengthy topic to understand for each config.:slight_smile:

Yes don’t need to memorize value, just focus on concept.

In 5G there are 16 harq processes and max retrans is 32.

Yes, but I am trying in protocol as no jobs seen in RF inspite working for so long.
I am not worked in 5G so it kind of bouncher learning.

You can work in 5G by learning first.
You can replay 5G logs and understand what is hapenning.

1 Like

I’m seeing value as 5 currently, but range I’m seeing up to 8 only for 5G.

This is vendor dependent.
For Huawei in 5G there are 16 harq processes.

Max retx parameter is defined in 5G for RLC layer, current value is 16.

SAW and MAC PDU can be changed by vendor.
If high BLER is there may be it can be reduced, but in low BLER it should be max to get good throughput in retransmission state, apart from blertarget and other parameters.

As ultimately low BLER also gives low throughput, so if KPI is fine, increase BLER values just checking drop rate and restablishment counters.

Increase target BLER give gain in throughput, but at cost of call drop. :frowning:

Yes, but maxthreshold is t32 can help in rlc am.
Normally it’s t32 and mac time alignment of set high can reduce drops.