转自金辉的博客:http://blog.sina.com.cn/s/blog_927cff010101c01c.html
接下来,我们来看看上行是如何进行同步的。
FDD有8个HARQ process。
对应下行:
a) it can use the 8 HARQ processes in any order (Asynchronous Process).
b) UE does not know anything about HARQ process information for DL data before it gets it. So Network send these information (Process ID, RV) in PDCCH DCI
对于上行
a)it have to use the specific process in a specific subframe (Synchronous Process). UE has to use the same HARQ process number every 8 subframes.在特定的子帧里必须用特定的进程,且每8个子帧UE必须使用相同的进程
b) Since UE have to use specific HARQ process ID at specific subframe, the reciever (eNode B) knows exactly which HARQ process comes when. And eNodeB can also knows about RV because UL Grant (DCI 0) from eNodeB can specify RV using MCS field.
c)it has two mode of operation : Adaptive and Non-Adaptive HA
或PHICH(只收到NACK,对应非自适应重传),则UE会在n+ 4子帧发送对应的PUSCH。(见36.213的8.0节)
图3:FDD中的上行传输,ULgrant、PUSCH、ACK/NACK之间的timing关系
Table8-2 k for TDD configurations 0-6
TDDUL/DL | subframenumber n | |||||||||
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | |
0 | 4 | 6 | | | | 4 | 6 | | | |
1 | | 6 | | | 4 | | 6 | | | 4 |
2 | | | | 4 | | | | | 4 | |
3 | 4 | | | | | | | | 4 | 4 |
4 | | | | | | | | | 4 | 4 |
5 | | | | | | | | | 4 | |
6 | 7 | 7 | | | | 7 | 7 | | | 5 |
图4:TDD1/2中,ULgrant/PHICH与对应的PUSCH传输之间的timing关系
(对应36.213的Table8-2)
Table8.3-1 k for TDD configurations 0-6
TDDUL/DL | subframenumber i | |||||||||
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | |
0 | 7 | 4 | | | | 7 | 4 | | | |
1 | | 4 | | | 6 | | 4 | | | 6 |
2 | | | | 6 | | | | | 6 | |
3 | 6 | | | | | | | | 6 | 6 |
4 | | | | | | | | | 6 | 6 |
5 | | | | | | | | | 6 | |
6 | 6 | 4 | | | | 7 | 4 | | | 6 |
图5:TDD1/2中,PUSCH传输与对应的PHICH(ACK/NACK)之间的timing关系
(对应36.213的Table8.3-1)
图6:举例