Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 25.707  Word version:  14.0.0

Top   Top   None   None   Next
0…   5…

 

0  IntroductionWord‑p. 5

Data scheduling on multi-carrier has been deployed to achieve higher data rates and load balancing. With the introduction of intra/inter-band features like DB-DC-HSPA/DC-HSPA, downlink and uplink data can be scheduled across two carriers for 2ms TTI. However the uplink coverage of cells deployed in different carriers may be different and in some areas, especially at the cell edge, the 2ms TTI cannot be configured.
In order to deploy multi-carrier features in these scenarios, 10ms TTI can be configured for multi-carrier deployments. In this way 10ms TTI can be configured on one carrier or two carriers when DB-DC-HSUPA/DC-HSUPA is configured to obtain higher data rates.
This Technical Report (TR) contains the investigations performed by the TSG RAN Working Groups involved in the study of multi-carrier enhancements for UMTS.
Up

1  ScopeWord‑p. 6

The study on multi-carrier enhancements is to investigate the potential gains obtained by enabling 10ms TTI configuration in one of the carriers or both of the carriers in the DB-DC-HSUPA and DC-HSUPA scenarios. It is also targeted to investigate the potential solutions for multi-carrier enhancements in both DB-DC-HSUPA and DC-HSUPA [2].

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
RP-152290, New SID: Study on Multi-Carrier Enhancements for UMTS
[3]
R1-160340, Considerations on UL coverage with 2/10ms EUL TTI, Qualcomm Inc.
[4]
R1-165084, Further evaluation results for 2+10ms TTI in DB-DC-HSUPA, Huawei, HiSilicon
[5]
R1-165085, Further evaluation results for 10+10ms TTI in DB-DC-HSUPA and DC-HSUPA, Huawei, HiSilicon
[6]
R1-160953, Evaluation methodology and results for Multi-Carrier enhancements, Huawei, HiSilicon
[7]
R1-163193, Evaluation of Multicarrier Enhancements for DB-DC HSUPA, Ericsson
[8]
R1-165325, Further Evaluation of Multicarrier Enhancements for DC HSUPA, Ericsson
[9]
R1-165326, Further Evaluation of Multicarrier Enhancements for DB-DC HSUPA, Ericsson
Up

3  Definitions, symbols and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.2  SymbolsWord‑p. 7

For the purposes of the present document, the following symbols apply:

3.3  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
HSUPA
High Speed Uplink Packet Access
DB
Dual Band
DC
Dual Carrier
SC
Single Carrier
UPH
UE transmission power headroom

4  Objective of multi-carrier enhancements for UMTS

The objective of the study item is the following:
  • Identify the scenarios for DB-DC-HSUPA/DC-HSUPA features and investigate mechanisms to improve coverage/capacity.
  • Study the potential deployment scenarios, e.g. scheduling 2ms+10ms TTI or 10ms+10ms TTI for uplink transmission with dual carrier.(RAN1, RAN2)
  • Investigate the performance for the enhanced scenarios and the impact on current mechanism, e.g. E-TFC selection, 2ms and 10ms switch, RRC measurement and handover.(RAN1, RAN2)
The study shall include considerations to minimize the impact on legacy terminals.
Up

Up   Top   ToC