Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 25.202  Word version:  16.0.0

Top   Top   None   None   Next
1…   6…

 

1  ScopeWord‑p. 6

The present document is the overall technical specification for the support of the 7.68Mcps TDD option in UTRA.

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 25.895: (V6.0.0) "Analysis of higher chip rates for UTRA TDD evolution".
[2]
TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".
[3]
TS 25.222: "Multiplexing and channel coding (TDD)".
[4]
TS 25.223: "Spreading and modulation (TDD)".
[5]
TS 25.224: "Physical layer procedures (TDD)".
[6]
TS 25.225: "Physical layer; Measurements (TDD)".
[7]
TS 25.301: "Radio Interface Protocol Architecture".
[8]
TS 25.306: "UE Radio Access capabilities".
[9]
TS 25.321: "Medium Access Control (MAC) protocol specification".
[10]
TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)".
[11]
TS 25.105: "UTRAN (BS) TDD; Radio transmission and reception".
[12]
TR 21.905: "Vocabulary for 3GPP Specifications".
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.
(void)

3.2  SymbolsWord‑p. 7

For the purposes of the present document, the following symbols apply:
(void)

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.
BCH
Broadcast Channel
CCPCH
Common Control Physical Channel
DCH
Dedicated Channel
DPCH
Dedicated Physical Channel
DSCH
Downlink Shared Channel
E-AGCH
E-DCH Absolute Grant Channel
E-DCH
Enhanced Dedicated Channel
E-HICH
E-DCH Hybrid ARQ Indicator Channel
E-PUCH
E-DCH Physical Uplink Channel
E-RUCCH
E-DCH Random Access Uplink Control Channel
FACH
Forward Access Channel
HS-DSCH
High Speed Downlink Shared Channel
HS-PDSCH
High Speed Physical Downlink Shared Channel
HS-SCCH
Shared Control Channel for HS-DSCH
HS-SICH
Shared Information Channel for HS-DSCH
P-CCPCH
Primary CCPCH
PCH
Paging Channel
PDSCH
Physical Downlink Shared Channel
PI
Paging Indicator (value calculated by higher layers)
PICH
Page Indicator Channel
PRACH
Physical Random Access Channel
PUSCH
Physical Uplink Shared Channel
RACH
Random Access Channel
S-CCPCH
Secondary CCPCH
SCH
Synchronisation Channel
TrCH
Transport Channel
USCH
Uplink Shared Channel
Up

4  Background and introduction

The 7.68Mcps TDD option is an evolution of the 3.84Mcps TDD option to a higher chip rate. There exists a great degree of commonality between the 3.84Mcps TDD option and the 7.68Mcps TDD option. Nevertheless, there are many aspects of the 7.68Mcps TDD option that require separate specification to the 3.84Mcps TDD option. The following aspects are specified at a high level in this document:
  • Physical layer structure;
  • Physical layer procedures;
  • UE capabilities;
  • Layer 2/3 protocol aspects;
  • Iub / Iur aspects;
  • Radio aspects;
Up

5  RequirementsWord‑p. 8

  • The 7.68Mcps TDD option shall provide significant enhancements in terms of user experience (throughput and delay) and/or capacity (at least to the extent shown in [1]).
  • Full mobility shall be supported, i.e., mobility should be supported for high-speed UE cases also, but optimisation should be for low-speed to medium-speed scenarios.
  • It is highly desirable for the 7.68Mcps TDD option to maintain commonality with the 3.84Mcps TDD option. New features shall therefore provide significant incremental gain for an acceptable complexity.
  • The UE and network complexity shall be minimised for a given level of system performance.
  • The impact on current releases in terms of both protocol and hardware perspectives shall be taken into account.
Up

Up   Top   ToC