This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

UCI on PUSCH support of BCP

Hi all,

In BCP user guide it is obvious that UCI bits coming over PUSCH with data is not demodulated&descrambled in BCP. ACK/NACK and RI bits have to be extracted from the buffer during deinterleaving operation before BCP work. But I wonder if these control bits can be given into BCP (SSL) as separate buffers for demodulation&descrambling operations only. Is this possible? or do we have to do all soft demodulation, descrambling and decoding work of A/N and RI on DSP core?

Thanks&Regards,

Cem

  • Hi,

    Please provide DSP part number used?

    Thank you.

  • Hi Rajasekaran,

    I am working on EVM 6670.

    Thanks.

  • Hi Cem,

    You can use BCP SSL in WiMAX mode for demodulation only of ACK/NACK and RI symbols. As mentioned in section 4.7, the descrambler (along with the de-interleaver and uplink control information handler) is bypassed in this mode so software will have to perform descrambling along-with the rest of the ACK/NACK and RI processing. We don't recommend this approach of sending a seperate BCP packet just for demodulating the UCI symbols as it will be in-efficient to construct a BCP input packet for this simple operation on such a short payload, especially when the DSP needs to extract these symbols in software anyway before sending them to the BCP for demodulation. Additionally, this may also impact PUSCH packet processing throughput as SSL (and other BCP resources) will be shared between PUSCH and UCI demodulation packets.

    TI's LTE Lib software offering provides very efficient and easy to use functions to handle ACK/NACK and RI processing in software.

    Regards
    -Nitin

  • Nitin,

    Thanks for the information.

    Regards,

    Cem