LTE_MAC_协议解读.ppt

Random Access Procedure Downlink Data Transfer Uplink Data Transfer Scheduling Requests Terminal make a scheduling request (SR) if it wants to transmit One bit SR is transmitted on a dedicated PUCCH schedule request resource Initially, buffer situation at terminal unknown: Possibly, scheduler give small resource and then ask for buffer status (etc ) transmitted via a specific MAC control header (etc.) Terminal without SR resource has to rely on random access mechanism DRX Semi-persistent scheduling Semi-persistent scheduling Possible to schedule recourses to be used until further notice (on every N subframe) Help reduce control signaling Used for e.g. VoIP * 5.1 Random Access procedure 5.2 Maintenance of Uplink Time Alignment 5.3 DL-SCH data transfer 5.3.1 DL Assignment reception 5.3.2 HARQ operation 5.3.3 Disassembly and demultiplexing 5.4 UL-SCH data transfer 5.4.1 UL Grant reception 5.4.2 HARQ operation 5.4.3 Multiplexing and assembly 5.4.4 Scheduling Request 5.4.5 Buffer Status Reporting 5.4.6 Power Headroom Reporting 5.5 PCH reception 5.6 BCH reception 5.7 Discontinuous Reception (DRX) 5.8 MAC reconfiguration 5.9 MAC Reset 5.10 Semi-Persistent Scheduling 5.10.1 Downlink 5.10.2 Uplink 5.11 Error Handling 5.12 MCH reception 5.13 Activation/Deactivation of SCells MAC procedures Spec 36.321 5.xx Random Access Procedure 下行HARQ ?? 自适应异步HARQ ?? UL ACK/NAK 在PUCCH/PUSCH发送 ?? PDCCH 携带HARQ 进程号 ?? 重传通过总是PDCCH调度，这是因为它采用异步自适应HARQ Maybe N =2 异步HARQ 上行HARQ ?? 同步HARQ，相对于第一次传输，会在固定的地方重传 ?? 最大传输次数是针对UE的而不是RB ?? 在PHICH 发送DL ACK/NAK 此图是异步UL HARQ Just for reference PDCCH n=0 n=4 Ue Rx (detection) Ue Tx PDCCH Format 0 PN, RV, RBs, NDI,… PUSCH eNB Tx eNB Rx NACK PHICH n=8 PUSCH RV++ n=12 TTI PN: process number RV: redundancy version NDI: new data indication 此图是同步UL HARQ 此图是异步DL HARQ On duration Timer ?? 指定在开始一个DRC周期的连续个数的PDCCH-subframe Inactivity Timer ?? 指定成功解码一个指示初始UL/DL用户数据传输的PDCCH以后连续个数的PDCCH subframe， ?? UE在醒着时每次成功解码HARQ初始发送的PDCCH后保持active的时间 Ac