NR / 5G - some restrictions PDSCH scheduling


 

Protocol description can often see such a description "The UE is not extpected to ......", UE does not expect to receive ...... scheduling, is scheduling done some restrictions.

 

In 5.1 38.214, the scheduling of the PDSCH also made a series of restrictions.

 

 

For any HARQ process ID(s) in a given scheduled cell, the UE is not expected to receive a PDSCH that overlaps in time with another PDSCH.

Here is mainly required for the HARQ-ACK feedback PDSCH in Semi-static HARQ-ACK feedback manner Introduction ( TypeI - Semi-static determination HARQ-ACK bits ) in order to reduce the number of feedback bits will PDSCH Candidate temporal overlapping some merge processing.

 


The UE is not expected to receive another PDSCH for a given HARQ process until after the end of the expected transmission of HARQ-ACK for that HARQ process, where the timing is given by Subclause 9.2.3 of [6].

Before the downlink HARQ-ACK feedback process, can not continue the downlink scheduling process, scheduling a return to the need, in this case is not disposed a PDSCH-AggregationFactor , a scene with a process multiple transmissions.

 


 In a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i, with the corresponding HARQ-ACK assigned to be transmitted in slot j, and a second PDSCH starting later than the first PDSCH with its corresponding HARQ-ACK assigned to be transmitted in a slot before slot j.

 

不同下行进程之间,不能插队,先来先反馈。

 


For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH starting in symbol j by a PDCCH ending in symbol i, the UE is not expected to be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH that ends later than symbol i.

理解还是PDCCH先调度,则对应PDSCH先来的原则吧。

 


The UE is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI if another PDSCH in the same cell scheduled with RA-RNTI partially or fully overlap in time.

 

The UE is not expected to decode a PDSCH scheduled in a serving cell with C-RNTI or MCS-C-RNTI and another PDSCH scheduled in the same serving cell with CS-RNTI if the PDSCHs partially or fully overlap in time.

 

 

记得在LTE里面,如果需要检测RA-RNTI时候,LTE描述“When RA-RNTI andeither C-RNTI or SPS C-RNTI are assigned in the same subframe, UE is notrequired to decode a PDSCH indicated by a PDCCH with a CRC scrambled by C-RNTIor SPS C-RNTI”,在同一个子帧C-RNTI /SPS C-RNTI PDSCH是可以不进行译码的。

 

另外一个方面考虑问题,RA-RNTI与C-RNTI会同时接收的场景,在连接态下,SR Fail之后的RACH申请上行调度是一种场景?此时UE上下行链路有可能属于正常状态,无上行发送,基站还会一直给UE调度下行?

 

C-RNTI/MCS-C-RNTI PDSCH与CS-RNTI PDSCH不能时域重叠,个人理解在第一个图里面应该包含了。

The UE in RRC_IDLE and RRC_INACTIVE modes shall be able to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs.

在RRC_IDLE和RRC_INACTIVE下,PDSCH可以时域在符号上进行重叠的,在频域上是分开的。这里SI-RNTI/RA-RNTI/P-RNTI不需要进行HARQ-ACK反馈的,唯一的例外是TC-RNTI PDSCH,在竞争解决成功的时候,需要反馈1比特ACK。

 


On a frequency range 1 cell, the UE shall be able to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI that partially or fully overlap in time in non-overlapping PRBs, unless the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI requires Capability 2 processing time according to subclause 5.3 in which case the UE may skip decoding of the scheduled PDSCH with C-RNTI, MCS-C-RNTI, or CS-RNTI.

 

On a frequency range 2 cell, the UE is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI if in the same cell, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI partially or fully overlap in time.

这里描述的是P-RNTI指示的系统消息更新场景,FR1和FR2调度要求不一样,FR2下SI-RNTI PDSCH和业务数据PDSCH不能时域重叠。FR1则根据UE能力区分。

 


In a given scheduled cell, for any PDSCH corresponding to SI-RNTI, the UE is not expected to decode a re-transmission of an earlier PDSCH with a starting symbol less than N symbols after the last symbol of that PDSCH, where the value of N depends on the PDSCH subcarrier spacing configuration m, with N=13 for m=0, N=13 for m=1, N=20 for m=2, and N=24 for m=3.

 

这个调度限制的原因,还没领悟到……

 


                                                                                        帮忙同时关注公众号  谢谢!

发布了31 篇原创文章 · 获赞 13 · 访问量 1万+

Guess you like

Origin blog.csdn.net/kakamilan/article/details/104610506