URLLC (Ultra reliable low latency communication):
Services for latency sensitive devices for applications like factory automation, autonomous driving, and remote surgery.
URLLC,超高可靠低时延通信,是NR的三大应用场景之一,上面所述的自动驾驶、远程手术等,可靠性和时延要求,不言自明。
今天主要学习一下在具体实现URLLC的一些技术,主要是上行部分,下行部分待继续学习。
为了减小时延,上行调度使用Configured Grant方式调度,在NR - 上行调度部分学习总结中有介绍到过,等同于LTE中的SPS调度,只是在NR中增加了RRC直接配置上行调度的方式,即Configured Grant Type1的方式。
Configured Grant Type1的方式优点是接收到配置后立即生效,但是如果需要改变PUSCH的时频位置,只能使用信令的方式,进行重配置。如果需要释放该配置,同样需要进行重配置指示。
类似于LTE中的SPS使用DCI进行激活的方式是Configured Grant Type 2,只有在DCI满足激活条件之后,如果需要改变调度配置,只要使用DCI进行重新激活即可。如果需要释放配置,同样适用DCI进行去激活即可。
为了提高可靠性,类似于LTE中TTI Bundling,使用repetition,即同一个上行进程,使用不同的冗余版本发送多次。LTE的TTI Bundling分别使用冗余版本0、1、2、3传输4次,NR下repetition则通过repK配置传输的次数,repK-RV配置传输的冗余版本样式。
这一部分的描述主要在38.214的6.1.2.3.1节“Transport Block repetition for uplink transmission with a configured grant”。
在R1-1901562中的描述,在讨论的时候有两种重复发送方式,一种是Mini-slot-based-repetition,在一个Slot内可以进行多次传输;另外一种是在Slot内只传输一次,在连续的Slot上进行重复发送。
To support extremely low-latency transmission for Rel.16 URLLC, the following two options have been proposed for both dynamic grant and configured grant PUSCH transmissions:
Ÿ Mini-slot-based repetition: two or more repetitions of a TB can be transmitted within one slot, or across slot boundary in consecutive available slots.
Ÿ Multi-segment transmission: two or more repetitions of a TB can be transmitted in consecutive available slots with only one repetition in each slot and with possibly different starting symbols and/or durations. Different repetitions in different slots can be with different starting symbols and/or durations.
38.214的6.1.2.3.1节的描述来看,Mini-slot-based-repetition方式没有被采用,基本采用Muti-segment transmission,但是其中的在不同Slot内可以在不同起始符号上重复发送这一点也没有被采纳。
For both Type 1 and Type 2 PUSCH transmissions with a configured grant, when the UE is configured with repK > 1, the UE shall repeat the TB across the repK consecutive slots applying the same symbol allocation in each slot. A Type 1 or Type 2 PUSCH transmission with a configured grant in a slot is omitted according to the conditions in Subclause 11.1 of [6, TS38.213].
重复传输的时机选择,取决于repK-RV的配置和UL数据到达的时间点。
- any of the transmission occasions of the K repetitions that are associated with RV=0 if the configured RV sequence is {0,3,0,3},
- any of the transmission occasions of the K repetitions if the configured RV sequence is {0,0,0,0}, except the last transmission occasion when K=8.
对于重复传输,也有几种提前终止传输的情况。
情况一 接收到相同进程的DCI调度,该DCI指示为新数据,此时隐式地指示该上行进程的HARQ-ACK反馈为ACK,那么后续的重复传输不需要再进行了
情况二 在Configured Grant的周期边界未到达最大重复传输次数,由于下一个周期开始是固定调度进程新数据
为了提高可靠性,URLLC传输时候使用计算TB Size的表格,对比前面两个表格,同一个MCS,码率都要远低于Table 5.1.3.1-1和Table 5.1.3.1-2。