Antti Toskala and Karri Ranta-aho
This chapter presents the outlook of HSPA evolution to Release 12 and beyond. First the topics discussed in 3GPP regarding the HSPA-LTE interworking and regarding the 3GPP radio level interworking with WLAN are covered. Then, on-going studies for dealing with bandwidths smaller than 5 MHz are presented, followed by work on improving the Release 99 based dedicated channel operation. This chapter is concluded with a presentation of the work being done on uplink enhancements as well as addressing briefly the heterogeneous network aspects also being progressed in another ongoing Release 12 study item. It's worth noting that several items in this chapter represent work in progress and many of the issues mentioned may not be necessarily finalized on time, or included in the actual work items targeting finalization by the end of 2014. Thus, some of the items may end up being postponed for Release 13, with finalization scheduled to take place in March 2016. Typically 18 to 21 months is needed for a Release based on experience with recent 3GPP Releases.
The basic support for interworking between HSPA and LTE was introduced together with the first LTE Release, Release 8. This included the support for PS handover as well as necessary reselection for idle mode operation. Support for Single Radio Voice Call Continuity (SRVCC) was also included, which enabled Voice over LTE (VoLTE) [1] with ongoing PS voice calls to be moved to WCDMA/HSPA (or also to GSM if needed). Various optimization proposals were added later to reduce the additional delay introduced by the use of the CS fallback solution. Later in Release 11, support for reverse SRVCC (rSRVCC) was added too, which enables moving from a CS call in WCDMA/HSPA back to a VoLTE call in LTE.
As part of the Release 12 studies, proposals addressing the following areas have been made, as covered in [1]:
Besides interworking with HSPA, 3GPP has also been addressing the interworking between 3GPP radio and WLAN networks. In 3GPP radio specifications, there has been no work done so far with the radio level interworking between 3GPP radios (LTE and WCDMA) and Wireless LAN (WLAN) networks. The key issue to address is how to ensure quality of service is retained when moving from a 3GPP network to WLAN network. Currently, if a UE moves from a 3GPP network to WLAN, the resulting quality may be much worse than that provided by a HSPA or LTE network due, for example, to limitations in the backhaul with WLAN or for general load reasons. While at the moment there are no defined measures in RAN for how to fix the situation, such methods are not being specified in 3GPP.
The three different approaches originally considered were, as given in [2]:
3GPP has already decided that there will not be, for example, an interface specified between WLAN AP and HSPA NodeB or RNC. Especially for an RNC it would not be desirable to interface with a large number of access points, when considering a large HSPA network with hundreds of macro cells belonging to a single RNC area.
As part of the Release 12 studies, addressing smaller bandwidths than 5 MHz was investigated. As discussed in [4] already, somewhat smaller bandwidths have been enabled in the field with the GSM refarming case particularly, where tighter filtering was used to go down to the 3.8 to 4.2 MHz range when deploying WCDMA in the middle of the GSM carriers of the same operator, as addressed also in Chapter 11. Now the desire is to go down to half of the nominal bandwidth, to 2.5 MHz or even lower in some cases.
During the study, as reported in [5], two alternatives for Scalable Bandwidth UMTS (S-UMTS) emerged, as illustrated in Figure 16.2, for how to address bandwidths clearly below 5 MHz:
Smaller chip rate, also called Time-Dilated UMTS, where a divider N would be used so that with N = 2 or N = 4 the resulting chip rates would be 1.92 Mcps or even down to 0.96 Mcps.
The use of S-UMTS results naturally in smaller data rates than regular 5 MHz UMTS. Also, if the solution is to implement the S-UMTS with a Time-Dilated UMTS approach with longer chip duration and respectively longer TTI, this would result in longer latency both for the user plane and control plane data. Using a 2.5 MHz filter on an unmodified 3.84 Mcps signal with filtered UMTS was shown to have some spectral efficiency degradation on low-to-moderate data rates, and a significant reduction in spectral efficiency for higher data rates. Another approach developed during the study to address the resulting performance issues with filtered UMTS (especially for downlink with high geometries) was using chip-zeroing to reduce the impact of filtering, as shown in Figure 16.3.
From the performance point of view, the use of smaller bandwidth causes some performance loss as, for example, some of the multipath diversity benefits with 3.84 Mcps are lost, resulting in more sensitivity to frequency selective fading. Figure 16.4 shows the example performance with scalable bandwidth UMTS, with the smaller bandwidth created by a filtering or a filtering and chip-zeroing approach, showing that the use of chip-zeroing reduces the performance degradation compared to the pure filtering solution. As shown in Figure 16.4, the performance with smaller data rates is retained rather well while more degradation can be seen with higher data rates. The results in Figure 16.4 are based on approaches which retain, for example, the TTI length unchanged and do not create additional delay to the data or control signaling. If the approach is based on the time-dilated solution, the extra delay will cause further system-level issues, for example the mobility events are slower due to the longer round trip-time for signaling as well as impacts on the time needed to obtain and transmit the necessary measurements.
3GPP concluded the scalable bandwidth UMTS study at the end of 2013 and agreed to perform further studies on such an option that downlink is based on filtered UMTS with chip-zeroing, with every second chip being then zeroed. In the uplink, sufficient performance for widest use could be reached with a pure filtering based approach as well. Using the chip-zeroing in the downlink is important as otherwise with high geometry values (i.e., close to the base station) there would be greater degradation, especially with data rates in the order of 500 kbps or more. 3GPP ended up not agreeing to include scalable bandwidth UMTS in Release 12.
Regardless of the fact that HSPA-based radio supports efficient delivery of both packet- and circuit-switched voice, voice traffic is still typically operated using a circuit-switched core network and a Dedicated Channel (DCH) on the UMTS radio network. DCH channels were designed as circuit-switched radio connections capable of simultaneous voice and data services in the very first release of the UMTS radio, Release 99, and were never further optimized when future development became focused on the more efficient packet-access radio. Because of this, there was interest in looking at optimizing the DCH radio specifically for voice delivery and exploiting similar techniques defined for HSPA radio, including DTX/DRX operation, in order to reduce UE power consumption and save on control channel overhead – as well as a variant of HARQ exploiting the varying link quality. With HSDPA, the use of CPC, as introduced in Chapter 4, allows for any service basically to implement DTX/DRX operation saving power and improving system capacity.
The DCH enhancements that were considered in 3GPP included the following: [6]
A typical Release 99 operating point for voice service is 1% FER, meaning that 99% of the voice frames need to decode correctly after all the bits in the 20-ms TTI have been delivered. Statistically this means that many packets would be correctly decodable even before all the bits in the 20 ms were transmitted, and the remainder of the bits are transmitted for nothing.
An example of the enhancement in the uplink operation compared to Release 99 is shown in Figure 16.5. The NodeB receiver tries to decode the packet before the frame (or the 20-ms interleaving period) has ended. The receiver may try decoding at different instances to get correct decoding (with a CRC check giving the correct result) and then sending ACK message as early as possible to allow the UE transmitter to stop transmitting the rest of the frame (or interleaving period in general). The earlier the NodeB manages to inform the UE of the successful uplink frame decoding, the bigger the benefit and the more DTX can be applied. In comparison, if one would use HSUPA with a 2-ms frame size to carry the voice data, then 2-ms transmission time would be sufficient if the first transmission was successful.
In order to drive for a higher probability of the voice frame being decodable earlier, all the bits could be encoded to a 10-ms radio frame, and repeated in the second 10-ms radio frame up to the point when the decoding is successful. Further, the outer loop power control could target a more aggressive operating point, for example, 10–20% FER after 10 ms rather than 1% FER after 20 ms. This would give the OLPC more frame erasures for faster adaptation to link quality changes and allow for on average much earlier frame early termination.
The market interest in further enhancing DCH voice capability remains to be seen. While voice currently continues to be provided as CS voice with the WCDMA/HSPA network over the Release 99 based DCH, the additional deployments of VoIP (with Voice over LTE, VoLTE) are pushing the introduction of VoIP for HSPA as well, once the IMS investment for VoLTE is already made due to LTE. When all IP services are run over HSPA, it is foreseen that VoIP will also run on HSPA. In that case all the elements are there to operate CS voice on HSPA too (CSoHSPA) (see Chapter 7). If the introduction speed of VoIP remains slow enough in the marketplace, there may be interest to still optimize the CS voice service separately based on Release 12 to reduce especially the UE power consumption.
If the key drivers to DCH enhancements are considered to be:
then these are both already achieved with HSPA using earlier 3GPP Releases with CSoHSPA (when no further investment to the core network is made) or Voice Over HSPA (VoHSPA) when IMS is available for PS voice support.
In the domain of code resource utilization, the use of DCH enhancement – based on the new physical layer structure planned for Release 12 at the end of 2014 – does not free any additional code resources. Some of the downlink power could be used for HSDPA instead, if the transmission is stopped early enough, but services mapped on HSDPA are of course sharing the code and power resource in a more dynamic and coordinated way as resources are only booked for 2 ms at a time with a fixed booking period.
Study on further Enhanced Uplink (EUL) enhancements aims to improve the uplink performance after many rounds of improvements have focused on the downlink improvements. The uplink changes prior to Release 12 are
The following solutions have been considered in the study [7]:
3GPP is foreseen to start in early 2014 the specification work for the method selected based on the study conclusions in [6].
The use of HSPA with heterogeneous networks was studied already in Chapter 7. Release 12 work has looked at further potential enhancements for different scenarios, including both co-channel and dedicated frequency cases, as illustrated in Figure 16.7. Clearly, the existing HSPA deployments have shown that there are no fundamental problems preventing the use of heterogeneous networks with HSPA, but some further optimization could be considered. The study conducted in 3GPP [8] in the area of HSPA heterogeneous networks includes several smaller items, including the following:
For Release 12, there are also some additional issues that have been raised, such as whether the Broadcast Channel (BCH) structure is sufficient and whether the new features (in Release 12 and beyond) would be needed due to BCH capacity limitations. The proposed approach would rely on the new information elements in the System Information Blocks (SIBs) being transmitted on a parallel BCH to the legacy one, possibly using HSDPA instead of the existing BCH. Alternatively a second Release 99 style BCH could be added. This allows higher capacity than the current BCH, but is only usable with Release 12 and newer devices, thus the amount of information that could be transmitted via such BCH is limited. The use of HSPA for BCH delivery is similar to the LTE broadcast principle, where only the Master Information Block is on a separate broadcast channel but the SIBs are on the data channel (equivalent to HSDPA), as covered in [9]. Further details of the enhanced broadcast of system information are covered in [10]. Other smaller areas include investigation for possible further enhancements for home BTS (femto BTS) related mobility, though the practical interest seems limited for solutions not valid for legacy UEs in Release 11 or earlier Releases.
In this chapter we have looked at the evolution of HSPA for Release 12 and beyond. Release 12, expected to be finalized by the end of 2014, is foreseen to contain several enhancements for HSPA, some of them like radio level interworking with WLAN being common with LTE. Most of the solutions to improve interworking or HSPA-specific improvements to HSUPA operation can be introduced in a backwards compatible way supporting both legacy and newer devices, while some of the solutions being discussed relate to the heterogeneous networks or new bandwidth with scalable UMTS. The latter requires new UEs in the market before the solution can be used, as legacy UEs cannot access such a carrier. It remains to be seen if there is enough market interest to roll out solutions which would not allow the 1.5 billion UEs already in the field to use the carrier. However, if some specific spectrum allocation does not have room for two (or any) full carriers, then scalable bandwidth UMTS is an alternative to be considered if one does not want to consider the smaller bandwidth options enabled by LTE, as presented in [9]. Work on UE receiver improvements is expected to continue following the studies on NAIC, which would enable better UE receiver performance regardless of whether all UEs support such a feature or not.
Release 13 work is to be initiated at the end of 2014, with the target milestone set by 3GPP to be March 2016. However, one may assume finalization around mid 2016 based on the roughly 18 months Release duration, as with earlier 3GPP Releases.
3GPP is addressing further areas where performance could be improved with HSPA evolution work, but clearly increasing the peak data rate is no longer the focus in HSPA work. Rather it is addressing easy to deploy improvements for capacity issues, enabling HSPA technology to be the workhorse for providing mobile broadband connectivity for roughly 3 billion (estimated) users globally by 2016.
3.145.7.208