【正文】 高的 CQI和使基站傳輸更大的傳輸塊，相當(dāng)于更高的數(shù)據(jù)傳輸速率，具有晶片均衡起的移動(dòng)終端可以接收不同信道狀態(tài)下的高速率的數(shù)據(jù)。 前置移動(dòng)接收的單元容量和數(shù)據(jù)傳輸速率的增強(qiáng) HSDPA 第五版的介紹包含了對(duì)使用單天線接收機(jī)性能的要求。 在大量單元的 64 位 QAM 的模擬結(jié)果如圖 所示。版本 6 支持下行鏈路的正交相移編碼（ QPSK）和 16 階正交幅度調(diào)制（ QAM），上行鏈路的二進(jìn)制相移編碼。一旦網(wǎng)頁被下載，連接進(jìn)入間斷傳輸和接收。 3GPP 的挑戰(zhàn)來自當(dāng)移動(dòng)終端正在使用 HSDPA/HSUPA 時(shí)從版本 99 到版本 6 仍然是連續(xù)接收和傳輸， 3GPP 版本7 介紹了一些改進(jìn)的 HSDPA/HSUPA，這對(duì)數(shù)據(jù)包服務(wù)，如瀏覽器和 IP 電話（ VoIP），有助于降低功耗。商業(yè)部署和設(shè)備預(yù)計(jì)到 2021 年完成?？傊?，對(duì)語音 IP （ VoIP ）服務(wù)，版本 7 的單元容量與版本 6 相比，提高了將近一倍。Overall Description,‖ 3GPP , , June 2021. [9] H. Holma et al., ―VoIP over HSPA with 3GPP Release 7,‖ PIMRC ’06, Sept. 2021. [10] 3GPP, ―HSDPA VoIP Capacity,‖ 3GPP R1062251, Aug. 2021. 外文 資料 譯文 3GPP 版本 7 中高速分組接入的演進(jìn) 概 述 高速分組接入（ HSPA ）被列入第三代合作項(xiàng)目計(jì)劃（ 3GPP ）的第 5 版和第 6版的下行和上行鏈路中。 3GPP 版本 7 提供了一些 HSPA 的增強(qiáng)，對(duì)終端用戶的性能和網(wǎng)絡(luò)速率提供了重大改進(jìn)。 3GPP 版本 7 使簡(jiǎn)化了網(wǎng)絡(luò)架構(gòu)。 前 言 隨著 2021 年高速下行分組接入（ HSPA）的推出，第三代合作伙伴計(jì)劃項(xiàng)目（ 3GPP ）規(guī)范包括下行數(shù)據(jù)傳輸速率和第五版容量的重大改進(jìn)。 3GPP 版本 6 移動(dòng)終端保持發(fā)射物理控制信道，甚至無數(shù)據(jù)的信道發(fā)射。 最大數(shù)據(jù)傳輸速率因多輸入多輸出和高次調(diào)制而提高 HSDPA 的第六版中下行鏈路的最大數(shù)據(jù)傳輸速率是 ， 3/4 的編碼和 的傳輸率，不含任何信道編碼。雙信道的 BPSK 調(diào)制和 QPSK 相似。 64位 QAM 調(diào)制比時(shí)間表 (RR = round robin, PR = proportional fair)將用戶數(shù)據(jù)傳輸速率提高了 15－ 25%。第六版引入了兩種增強(qiáng)型的接收機(jī)：第一種是，對(duì)應(yīng)的雙天線接收機(jī)，第二種對(duì)應(yīng)的是單天線的晶片均衡器。 這種前置接收機(jī)和報(bào)告的 CGI 值的優(yōu)點(diǎn)在于，任何修改都不再受限于移動(dòng)終端中前置接收機(jī)的基站算法。 帶有晶片均衡起的前置接收機(jī)可以提高對(duì)移動(dòng)終端不同信道狀態(tài)下的容量的補(bǔ)償，這使得前置移動(dòng)終端返回比沒有任何均衡器的移動(dòng)終端更高的 CQI 值。 HSUPA 分類 7和 16 位 QAM 容量一起被加入到了第七版中，使上行最大數(shù)據(jù)傳輸速 率達(dá)到了。因此，下行鏈路 64 位 QAM 和上行鏈路 16 位 QAM 只有在信道狀態(tài)非常好的時(shí)候才可以運(yùn)用。 高次調(diào)制在不增加傳輸帶寬的情況下就可以提高最大數(shù)據(jù)傳輸速率。網(wǎng)頁瀏覽的連續(xù)傳輸?shù)母拍钫f明圖如圖 1。此外，快速和準(zhǔn)確的功率控制寬帶碼分多址（ WCDMA）有利于減少傳輸?shù)墓β仕健? 3GPP 版本 7 完成于 2021 年 6 月，還存在一些剩余的性能的要求。 在新型終端的需求下對(duì)于雙天線與 MIMO 的均衡，下行單元的容量將得到加強(qiáng)。 only a reference receiver is used to set the performance requirements that a mobile terminal must meet to declare it as enhanced Type 1, 2, or 3pliant. The advanced receivers in mobile terminals improve the single user data rates and cell capacities due to increased average CQI reporting as discussed previously. The capacity improvements are shown in Fig. 4, assuming finite transmission buffers. The simulation results are shown with different number of codes in the work and with round robin and a proportional fairpacket scheduler. More details about the HSDPA packet schedulers can be found in [2]. The gain of the twoantenna equalizer receiver is 100–150 percent pared to the oneantenna Rake and 50–80 percent pared to the oneantenna equalizer. The achievable macro cell capacity is 4 Mbps with a twoantenna equalizer with a dedicated HSDPA carrier and proportional fair scheduler. That capacity corresponds to the spectral efficiency of nearly 1 bps/Hz/cell. The downlink MIMO transmission further improves the cell throughput. The more detailed capacity evaluations can be found in[5]. Additional downlink capacity enhancements can be achieved with intercell interference cancellation in the receiver of the mobile terminal. Such enhanced receivers also are being studied in 3GPP to improve the capacity and especially the celledge data rates. Those receivers are called enhanced Type 3i. LAYER 2 OPTIMIZATION WITH FLEXIBLE RLC AND MAC SEGMENTATION The WCDMA release 99 specification was based on the packet retransmissions running from the radio work controller (RNC) to the mobile terminal on the layer 2. The layer 2 radio link control (RLC) packets were required to be relatively small to avoid the retransmission of very large packets in case of transmission errors. Another reason for the relatively small RLC packet size was the requirement to provide sufficiently small step sizes for adjusting the data rates for the release 99 channels. The RLC packet size in release 99 is not only small, but it is also fixed for acknowledged mode data, and there are only a limited number of block sizes in unacknowledged mode data. This limitation is due to transport channel limitations. The RLC payload size is fixed to 40 bytes in release 99 for acknowledged mode data. The same RLC solution is applied to HSDPA release 5 and HSUPA release 6, as well: the 40byte packets are transmitted from RNC to the base station in the case of HSDPA. An additional configuration option to use an 80byte RLC packet size already was introduced in release 5 to avoid extensive RLC protocol overhead, layer 2 processing, and RLC transmission window stalling. With the 2ms transmission time interval(TTI) used with HSDPA, this leads to possible data rates being multiples of 160 kbps and 320kbps, respectively. As the data rates are further increased in release 7, increasing the RLC packet size even more would have a significant impact on the granularity of the data rates available for HSDPA scheduling and the possible minimum data rates. 3GPP HSDPA and HSUPA allow the optimization of the layer 2 operation because layer 1retransmissions are used, and the probability of layer 2 retransmissions is very low. Also, the release 99 transport channel limitation does not apply to HSDPA/HSUPA because the layer 2block sizes are independent of the transport formats. Therefore, it is possible to use flexible and considerably larger RLC sizes and introduce segmentation to the Medium Access protocol(MAC) layer in the base station. This optimization is included in the release 7 downlink operation and is called the flexible RLC and MAC segmentation solution. The RLC block size in a flexible RLC solution can be as large as an Inter Protocol (IP) packet, which is typically 1500 bytes for download. There is no requirement for packet segmentation in RNC. By introducing the segmentation to the MAC, the MAC can perform the segmentation of the large RLC packet data unit (PDU), based on physical layer requirements when required. The flexible RLC and MAC segmentation offers a number of benefits in terms of layer 2 efficiency and in terms of peak bit rates. ? The relative layer 2 overhead is reduced. With the RLC header of 2 bytes, the RLC