Hi Ti folks,
My question is regarding Multiple LTE PDCCH.
As i understand from User guide flow diagram CRC has to be done on software.
How are the headers prepared for other modules ?
Is there any example project from TI regarding this ?
BR
Rahul
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.
Hi Ti folks,
My question is regarding Multiple LTE PDCCH.
As i understand from User guide flow diagram CRC has to be done on software.
How are the headers prepared for other modules ?
Is there any example project from TI regarding this ?
BR
Rahul
Hi Rahul,
I think there is no example project available for this. Please refer the below link.
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/283672.aspx
Could you please provide the part number of your device & EVM or Custom board?
Thanks.
Hi Rajasekaran
Thanks for reverting back.
I am working on EVM C6670 and am wondering about the use case scenario of multiple PDCCH.
Lets take an example of Encoder header. Is it like one common header containing all DCI information in this case ?
Is it still a normal BCP packet type ?
Can you please put more some more light on its usage as I could not find much in UG.
Thanks in advance
BR
Rahul
Hi Rahul,
The usage of BCP for PDCCH transmit chain processing is shown in section 2.3.2 of the BCP user guide. As shown in Figure 2-3, BCP can be used to perform CRC (single PDCCH case only), Encoding and Rate matching. We don't have a PDCCH example available, but the following may be helpful pointers towards configuring the BCP for PDCCH handling.
1. CRC sub-module: The CRC sub module can perform block concatenation after attaching CRC to each block, but only one METHOD2_ID can be specified which is used to mask all the attached CRCs. The METHOD2_ID of a PDCCH depends on the corresponding RNTI so each PDCCH requests a different METHOD2_ID, therefore the CRC sub module cannot be used to perform CRC attachment for multiple PDCCHs with a single input packet. For this reason, BCP CRC can be used to handle only single PDCCH case and CRC attachment for multiple PDCCHs should be performed by the CPU (as shown in figure 2-3).
2. ENC: ENC is a block based sub module. It supports encoding at most three different blocks in one packet. The PDCCHs transmitted in one TTI may have more than three payload blocks. For example, in the case of an FDD 20MHz cell with 4 antenna ports, as per section 5.3.3.1 of 3GPP TS-36.212 we can figure out that there are at most six types of DCI payload size - 15 (format 1C), 28 (format 0/1A/3/3A), 33 (format 1B/1D), 39 (format 1), 50 (format 2A), 54 (format 2). So the BCP ENC needs 2 input packets to perform encoding for 6 PDCCHs in one TTI.
3. RM: RM is also a block-based sub module. It supports Rate matching of two code blocks in one input packet. RM needs both the payload block size (block size before rate matching, denoted by K) and channel block size (block size after rate matching, denoted by E) as it’s input parameters. There are four PDCCH formats and each format corresponds to one E value. In the above example scenario (FDD 20MHz cell and 4 antenna ports), there are at most 6x4=24 different [K, E] pairs so we need 12 BCP input packets to perform rate matching in one TTI with each packet processing the PDCCHs with two [K, E] pairs.
With the above considerations, to keep simplicity of the framework we recommend using one input packet to process the CRC attachment, convolutional coding and rate matching of a single PDCCH. The BCP input packet will contain the following headers: TM, CRC, ENC and RM, and PKT_TYPE will be Normal packet.
Regards
-Nitin
Hi Nitin
This information is really helpful.
I was actually wondering about RM module configuration which is now clear from your explanation.
you guys can probably update this information in User guide also.
Thanks
Kind Regards
Rahul Sharma