Lte A

LTE-Advanced 주요 표준 동향 및 기술
윤영우
yw.yun@lge.com
LG 전자
Contents
 Generals on LTE-Advanced
 Overview of LTE-Advanced Technologies
 More details on LTE-Advanced Component
Technologies
LTE-Advanced 주요 표준 동향 및 요소 기술 2
LTE-Advanced : Generals
 Definition of LTE-Advanced
 Major milestones for LTE-Advanced
 Requirements and targets for LTE-Advanced
 Current status of LTE-Advanced
 Self Evaluation Results
 Bands identified for IMT-Advanced
3GPP specification releases
Cited from 3GPP, RP-091005, Proposal for Candidate Radio Interface Technologies for IMT-Advanced Based on LTE Release 10 and Beyond
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011
GSM/GPRS/EDGE enhancements
Release 99 W-CDMA
Release 4 1.28Mcps TDD
Release 5 HSDPA, IMS
Release 6 HSUPA, MBMS, IMS+
Release 7 HSPA+ (MIMO, HOM etc.)

ITU-R M.1457
IMT-2000 Recommendations Release 8 LTE, SAE
Release 9 Small LTE/SAE

enhancements
LTE-Advanced 주요 표준 동향 및 요소 기술 Release 10 LTE-Advanced

Definitions
 What is IMT-Advanced?
 A family of radio access technologies fulfilling IMT-Advanced
requirements
 Relates to 4G as IMT-2000 relates to 3G
 IMT spectrum will be available to both IMT-2000 and IMT-Advanced
 What is LTE-Advanced?
 System now under study in 3GPP aiming toward IMT-Advanced within
WP5D time line
 Formal name: Advanced E-UTRA /Advanced E-UTRAN
 Evolution from 3GPP LTE specifications, not a revolution
 Comparable potential of 3GPP LTE with target requirements of IMT-advanced
 Fast and efficient correspondence against the timeline of WP5D’s specification
and commercialization for IMT-advanced
 Cost-efficient support for backward and forward compatibility between LTE and
LTE-A
 Natural evolution of LTE (LTE release 10 & beyond)
Detailed Timeline for ITU-R
Detailed Timelines for ITU-R Steps 1- 4
RAN #39 RAN #40 RAN #41 RAN #42 RAN #43 RAN #44 RAN #45 RAN #46 RAN #47
3/08 6/08 9/08 12/08 3/09 5/09 9/09 12/09 3/10

3GPP
3GPP work on ITU-R Step 2
LTE-Advanced Technology Development LTE-Advanced
SI Approved Specifications
3GPP LTE-
3GPP LTE-
Advanced 3GPP LTE- LTE-Advanced
Advanced Specifications
Complete Advanced Final
Early to ITU-R
Technical Submission to
Submission to ~ Jan 2011
Submission to ITU-R including
ITU-R 3GPP work on ITU-R Step 3 [~Release 10 ]
ITU-R Updated
Technology Submission [~RAN #50 12/10]
Technical
Initiate Submission &
3GPP LTE- Required Self-
Advanced Evaluation 3GPP Q&A with
Self-Evaluation evaluation
groups
(as required)
IMT-Advanced
Evaluation Evaluation of
INDUSTRY Group(s) ITU-R
Submissions
Formed
(notify ITU-R)
Steps 1 & 2
WP 5D #1 WP 5D #2 WP 5D #3 Circular Letter & Development of Candidate RITs WP 5D #6
ITU-R 3/08 6/08 10/08 3/08 to 10/09 10/09

ITU-R Circular Step 3
ITU-R Circular
Letter 5/LCCE/2 Letter Addendum Submission
ITU-R Eval
Process & 5/LCCE/2 + 3/09 to 10/09
Evaluation Reports
Timelines Requirements
Criteria WP 5D #4 WP 5D #5 WP 5D #6
& Submission
Templates 3/09 6/09 10/09 Cutoff for
Evaluation Reports
WP 5D #4
Step 4 to ITU-R
Evaluations June 2010
3/09 1/09 to 6/10 6/10
5 Source: RP-080651
WP 5D #8
LTE-Advanced 주요 표준 동향 및 요소 기술
IMT-Advanced Process
WP 5D
2008 2009 2010 2011
No.1 No.2 No.3 No.4 No.5 No.6 No.7 No.8 No.9 No.10
meetings
Step1 and 2
(0) (20 months)
Step 3
(8 months) (1)
Step 4
(16 months) (2)
Steps 5,6 and 7
(20 months) (3)
Steps 8
(12 months) (4)
Steps in radio interface development process:
Step 1: Issuance of the circular letter Step 5: Review and coordination of outside evaluation activities
Step 2: Development of candidate RITs and SRITs Step 6: Review to assess compliance with minimum requirements
Step 3: Submission/Reception of the RIT and SRIT proposals Step 7: Consideration of evaluation results, consensus building
and acknowledgement of receipt and decision
Step 4: Evaluation of candidate RITs and SRITs Step 8: Development of radio interface Recommendation(s)
by evaluation groups
Critical milestones in radio interface development process:
(0): Issue an invitation to propose RITs March 2008 (2): Cut off for evaluation report to ITU June 2010
(1): ITU proposed cut off for submission October 2009 (3): WP 5D decides framework and key October 2010
of candidate RIT and SRIT proposals characteristics of IMT-Advanced RITs and SRITs
(4): WP 5D completes development of radio February 2011
interface specification Recommendations
IMT-Advanced A2-01
Major Milestones for LTE-Advanced
 Major milestones for LTE-Advanced in 3GPP
 1st workshop in November 2007 – Cancun
 Approval of LTE-Advanced study item: Rapporteur: NTT DoCoMo
 2nd workshop in April 2008 – Shenzhen
 3rd workshop in May 2008 – Prague
 Approval of LTE-A requirement TR: TR 36.913 v8.0.0 approved in RAN#40 in May
 Early proposal to ITU-R WP5D in October 2008
 Complete submission to ITU-R in June 2009 (WP5D #5)
 Approval for RAN TR (TR 36.912) for ITU-R submission in September, 2009
 Final proposal update to ITU-R in October 2009 (WP5D #6)
 Study item completion in March 2010
 LTE-Advanced function block work items started in December, 2009, irrespective of completion for LTE-Advanced study item
 Initial approval of LTE-A (Rel-10 specification) will be done in December, 2010
 Functional freezing will be done at the same time in December next year
 ASN.1 freezing is expected to be done in March or June 2011
Standard Roadmap 2009 2010 2011 2012

Complete Tech
Final Submission
Proposals
ITU-R WP5D Evaluation
Consensus
Specification
3GPP LTE Rel.9 LTE Rel.10 [LTE Rel.11] [LTE Rel.12]
LTE-A LTE-A SI LTE-A Functional Work Items Beyond LTE-A SI
Agreed upon Time Plan for Rel-10
12.09 3.10 6.10 9.10 12.10 3.11 6.11
#46 #47 #48 #49 #50 #51 #52
Expected
RAN1 has to complete their Functional
specification by Sept. 10 freeze
(only 9 month) In RAN1
Core spec ASN.1

RAN2/3/4 have to completeFunctional freeze
freeze
their specification by Dec.
10 (only 12 month) reflecting
RAN1 agreements
Documents Related to LTE-Advanced
 TR (Technical Report)
 TR 36.806
 Technical report for relay architecture
 TR 36.814 (RAN1 technical report)
 Evolved Universal Terrestrial Radio Access (E-UTRA); Further
advancements for E-UTRA Physical layer aspects
 TR 36.815
 LTE-Advanced feasibility studies in RAN WG4
 TR 36.912 (RAN technical report)
 Feasibility study for Further Advancements for E-UTRA (LTE-
Advanced)
 TR 36.913
 Requirements for further advancements for Evolved Universal
Terrestrial Radio Access (E-UTRA)
RAN TR for LTE-Advanced
 TR 36.912: RAN plenary TR for LTE-Advanced study item
 RP-090743: TR36.912 v9.0.0
 Approved in RAN #45
 Will be submitted to ITU-R after PCG approval
 Contents
1. Scope
2. References
3. Definitions, symbols and abbreviations
4. Introduction
5. Support of wider bandwidth
6. Uplink transmission scheme
7. Downlink transmission scheme
8. CoMP
9. Relaying
10. Improvement for latency
11. Radio transmission and reception
12. Mobility enhancements
13. TS 36.133 requirements enhancements
14. MBMS enhancements
15. SON enhancements
16. Self-evaluation report on “LTE Rel.10 & beyond (LTE-Advanced)”
Annexs
Requirements for LTE-Advanced [1]
 General requirement
 LTE-Advanced is an evolution of LTE
 LTE-Advanced shall meet or exceed IMT-Advanced
requirements within the ITU-R time plan
 Extended LTE-Advanced targets are adopted
LTE-Advanced
targets
Performance
IMT-Advanced
System
requirements and time plan
Rel. 8 LTE
Time
Cited from 3GPP, RP-091005, Proposal for Candidate Radio Interface Technologies for IMT-Advanced Based on LTE Release 10 and Beyond
 Comparison between IMT-Advanced and LTE-Advanced
 LTE-Advanced should at least fulfill or exceed IMT-Advanced requirements
ITU Requirement 3GPP Requirement
1Gbps in DL
Peak data rates
500Mbps in UL
Bandwidth 40MHz (scalable BW) Up to 100MHz
User plane latency 10ms Improved compared to LTE
Active  Active dormant(<10ms)

Control plane latency 100ms
Camped  Active (<50ms)
15bps/Hz in DL 30bps/Hz in DL
Peak spectrum efficiency
6.75bps/Hz in UL 15bps/Hz in UL
Average spectrum efficiency Set for four scenarios and several antenna configurations
See next slide for case 1 requirement
Cell edge spectrum effciency
VoIP capacity Up to200 UEs per 5MHz Improved compared to LTE
 System performance requirements for IMT-Advanced
ITU system performance requirement

Base Rural/
Enviromnet Indoor Micro-cell coverage
Urban High speed
DL
3 2.6 2.2 1.1
Spectrum (4x2 MIMO)
Efficiency UL
2.25 1.8 1.4 0.7
(2x4 MIMO)
DL
Cell Edge 0.1 0.075 0.06 0.04
(4x2 MIMO)
Spectrum
UL
Efficiency 0.07 0.05 0.03 0.015
(2x4 MIMO)
 System Performance Requirements from TR 36.913
 Peak Spectral Efficiency:
 DL 30bits/Hz (8x8 MIMO), UL 15bps/Hz (4x4 MIMO)
 Seem to be easily achievable by means of extended utilization of # of antennas
 Average Spectral Efficiency (SE) and Edge Spectral Efficiency for LTE Case-1
 System performances of LTE Rel-8 are about 30% ~ 70% lower than 3GPP target
 What would be key enabling technologies to fill up the gap between two?
LTE LTE-ADV LTE LTE-ADV

Case-1 Cell Avg. SE Cell Avg. SE Cell Edge SE Cell Edge SE
[bps/Hz/cell] [bps/Hz/cell] [bps/Hz/user] [bps/Hz/user]
Ant. Config (3GPP R1-072580) (3GPP TR36.913) (3GPP R1-072580) (3GPP TR36.913)
1x2 0.735 1.2 0.024 0.04
UL
2x4 - 2.0 - 0.07
2x2 1.69 2.4 0.05 0.07
DL 4x2 1.87 2.6 0.06 0.09
4x4 2.67 3.7 0.08 0.12
Frequency Bands Identified for LTE-A
 WRC 07 identified some new IMT spectrum that is now under band planning
 There should be either a clear FDD band plan or TDD band plan
Existing
IMT
identified
New
Global
5150 450 790 806 890915
470 698 925960
New 100 200 300 400 500 600 700 800 900 1000
Region 2
New for IMT in some

countries of
Regions 1 & 3
1710 2025 2110 2690

2170
1300 1400 1500 1600 1700 1800 1900 2000 2100 2200 2300 2400 2500 2600 2700 2800 2900
3300 3400 3500 3600 3700 3800 3900 4000 4100 4200 4300 4400 4500 4600 4700 4800 4900 5000
IMT bands can be used by all IMT-2000 and IMT-Advanced technologies
Current Status of LTE-Advanced
 Status related to IMT-Advanced submission
 Early proposal in October 2008
 Main purpose was to inform ITU-R of 3GPP’s resolution for IMT-Advanced and provide
updated status of LTE-Advanced to ITU-R
 Complete technology submission in June 2009
 Initial proposal submission from 3GPP
 Compliant with the formal form of submissition requested by ITU-R
 Separate RIT for FDD and TDD
 Performance results were not included in the submission
 Final submission in October 2009
 Final proposal update to ITU-R
 Self evaluation results for LTE-Advanced were included
 Status of LTE-Advanced in 3GPP
 Study item has been formally completed in last RAN plenary meeting in March
 Several new work items with respect to LTE-Advanced were created, targetting
Rel’10 time frame
 Carrier aggregation work item: created in December 2009
 Enhanced DL MIMO work item: created in December 2009
 UL MIMO work item: created in December 2009
 Relay work item: created in December 2009
 Enhanced ICIC for non-ca based HetNet: created in March 2010
Self-Evaluation Activities in 3GPP
 RAN1 activities with respect to self evaluations for LTE-Advanced
 List of companies who submitted self evaluation results:
 Alcatel-Lucent, CATT, CMCC, Ericsson, Fujitsu, Hitachi, Huawei, LGE,
Motorola, NEC, Nokia, NTT DOCOMO, Panasonic, Qualcomm, RITT,
Samsung, Texas Instruments, ZTE
 How to capture self evaluation results from a lot of companies
 Since different companies have somewhat different assumptions on the
overhead, the group had to make decision on the common assumption for the
overhead so that the results from different companies can be comparable with
each other
 What kinds of features should be prioritized?
 LTE-Advanced is based on LTE Rel.8 and it is the long term evolution of LTE, thus
 It is good to inform that LTE Rel.8 can fulfill the most of requirements without any
enhanced techniques.
 It is also good to inform that only small updates from Rel.8 can fulfill the requirements
even in the very tough conditions (UMi and Uma).
 Thus, Rel-8 performance is captured if it fulfills the requirements.
 If Rel-8 cannot meet the req. , we should prioritize ones with small extension
from Rel-8, i.e.,
 DL: Rel-8 > MUMIMO > CS/BF-CoMP and JP-CoMP
 UL: Rel-8 > MUMIMO, SUMIMO and CoMP
Summary of Self-Evaluation Results
 From the self evaluation activities, it was found that
 For LTE Release 10,
 FDD RIT Component meets the minimum requirements of all 4 required test
environments
 TDD RIT Component meets the minimum requirements of all 4 required test
environments
 The complete SRIT meets the minimum requirements of all 4 required test
environments.
 Baseline configuration exceeding ITU-R requirements with minimum extension
 LTE release 8 fulfills the requirements in most cases (no extensions needed)
 Extensions to Multi-user MIMO from Release 8 fulfills the requirements in some scenarios
(Urban Macro/Micro DL)
 More advanced configurations, e.g. CoMP, with further enhanced performance
 Many (18) companies perticipated in the simulations, ensuring high reliability

 Self evaluation reports are captured in section 16 of Technical Report TR 36.912
Self-Evaluation Results [1]
 Peak spectrum efficiency
 DL peak spectrum efficiency
FDD spectral efficiency TDD spectral efficiency
Scheme
(bps/Hz) (bps/Hz)
ITU requirement 15 15
Rel-8 4 layer spatial multiplexing 16.3 16.0
8 layer spatial multiplexing 30.6 30.0
 UL peak spectrum efficiency

FDD spectral efficiency TDD spectral efficiency
Scheme
(bps/Hz) (bps/Hz)
ITU requirement 6.75 6.75
 Indoor Hotspot / downlink / FDD
 LTE Rel-8 meets the requirement
ITU Number Cell average Cell edge

Scheme and antenna
requirement of
conf.
(Ave./Edge) samples L=1 L=2 L=3 L=1 L=2 L=3
Rel-8 SU-MIMO
3 / 0.1 15 4.8 4.5 4.1 0.23 0.21 0.19
4X2 (A)
MU-MIMO
3 / 0.1 3 6.6 6.1 5.5 0.26 0.24 0.22
4X2 (C)
 Indoor Hotspot / downlink / TDD

Scheme and antenna
requirement of
conf.
Rel-8 SU-MIMO
3 / 0.1 10 4.7 4.4 4.1 0.22 0.20 0.19
4X2 (A)
MU-MIMO
3 / 0.1 4 6.5 6.1 5.7 0.23 0.22 0.20
4X2 (C)
 Indoor Hotspot / uplink / FDD
ITU requirement Number of
Scheme and antenna conf. Cell average Cell edge
(Ave./Edge) samples
Rel-8 SIMO 1X4 (A) 2.5 / 0.07 13 3.3 0.23
Rel-8 SIMO 1X4 (C) 2.5 / 0.07 10 3.3 0.24
Rel-8 MU-MIMO 1X4 (A) 2.5 / 0.07 2 5.8 0.42
SU-MIMO 2X4 (A) 2.5 / 0.07 5 4.3 0.25
 Indoor Hotspot / uplink / TDD

(Ave./Edge) samples
Rel-8 SIMO 1X4 (A) 2.5 / 0.07 9 3.1 0.22
Rel-8 SIMO 1X4 (C) 2.5 / 0.07 7 3.1 0.23
Rel-8 MU-MIMO 1X4 (A) 2.5 / 0.07 2 5.5 0.39
SU-MIMO 2X4 (A) 2.5 / 0.07 2 3.9 0.25
 Urban Micro/downlink/FDD:Single cell MU-MIMO meets the requirement
Scheme and antenna
requirement of
conf. L=1 L=2 L=3 L=1 L=2 L=3
(Ave./Edge) samples
MU-MIMO 4X2 (C) 2.6 / 0.075 8 3.5 3.2 2.9 0.11 0.096 0.087
MU-MIMO 4X2 (A) 2.6 / 0.075 3 3.4 3.1 2.8 0.12 0.11 0.099
CS/BF-CoMP 4X2 (C) 2.6 / 0.075 5 3.6 3.3 3.0 0.11 0.10 0.089
JP-CoMP 4X2 (C) 2.6 / 0.075 1 4.5 4.1 3.7 0.14 0.13 0.12
MU-MIMO 8X2 (C/E) 2.6 / 0.075 4 4.2 3.8 3.5 0.15 0.14 0.13
 Urban Micro/downlink/TDD: single cell MU-MIMO (4x2) meets the requirement

Scheme and antenna
requirement of
conf. L=1 L=2 L=3 L=1 L=2 L=3
(Ave./Edge) samples
MU-MIMO 4X2 (C) 2.6 / 0.075 8 3.4 3.2 3.0 0.10 0.096 0.089
MU-MIMO 4X2 (A) 2.6 / 0.075 1 3.1 2.9 2.7 0.11 0.10 0.095
CS/BF-CoMP 4X2 (C) 2.6 / 0.075 3 3.5 3.3 3.1 0.099 0.092 0.086
JP-CoMP 4X2 (C) 2.6 / 0.075 1 4.5 4.2 3.9 0.098 0.092 0.085
MU-MIMO 8X2 (C/E) 2.6 / 0.075 4 4.1 3.9 3.6 0.11 0.11 0.10
 Urban Micro / uplink / FDD: LTE Rel-8 meets the requirement
(Ave./Edge) samples
Rel-8 SIMO 1X4 (C) 1.8 / 0.05 13 1.9 0.072
Rel-8 MU-MIMO 1X4 (A) 1.8 / 0.05 2 2.5 0.077
MU-MIMO 2X4 (A) 1.8 / 0.05 1 2.5 0.086
 Urban Micro / uplink / TDD: LTE Rel-8 meets the requirement

(Ave./Edge) samples
Rel-8 SIMO 1X4 (C) 1.8 / 0.05 9 1.9 0.070
Rel-8 MU-MIMO 1X4 (A) 1.8 / 0.05 2 2.3 0.071
MU-MIMO 2X4 (A) 1.8 / 0.05 1 2.8 0.068
MU-MIMO 1X8 (E) 1.8 / 0.05 1 3.0 0.079
 Urban Macro / downlink / FDD: Single cell MU-MIMO (4x2) meets the requirement

Scheme and antenna
requirement of
conf. L=1 L=2 L=3 L=1 L=2 L=3
(Ave./Edge) samples
MU-MIMO 4X2 (C) 2.2 / 0.06 7 2.8 2.6 2.4 0.079 0.073 0.066
CS/BF-CoMP 4X2 (C) 2.2 / 0.06 6 2.9 2.6 2.4 0.081 0.074 0.067
JP-CoMP 4X2 (A) 2.2 / 0.06 1 3.0 2.7 2.5 0.080 0.073 0.066
CS/BF-CoMP 8X2 (C) 2.2 / 0.06 3 3.8 3.5 3.2 0.10 0.093 0.085
 Urban Macro / downlink / TDD: Single cell MU-MIMO (4x2) meets the requirement

Scheme and antenna conf. requirement of
MU-MIMO 4X2 (C) 2.2 / 0.06 7 2.8 2.6 2.4 0.076 0.071 0.067
CS/BF-CoMP 4X2 (C) 2.2 / 0.06 4 2.8 2.6 2.4 0.082 0.076 0.071
JP-CoMP 4X2 (C) 2.2 / 0.06 1 3.5 3.3 3.1 0.087 0.082 0.076
CS/BF-CoMP 8X2 (C/E) 2.2 / 0.06 3 3.5 3.3 3.1 0.10 0.093 0.087
 Urban Macro / uplink / FDD
(Ave./Edge) samples
Rel-8 SIMO 1X4 (C) 1.4 / 0.03 12 1.5 0.062
CoMP 1X4 (A) 1.4 / 0.03 2 1.7 0.086
CoMP 2X4 (C) 1.4 / 0.03 1 2.1 0.099
 Urban Macro / uplink / TDD

(Ave./Edge) samples
Rel-8 SIMO 1X4 (C) 1.4 / 0.03 9 1.5 0.062
CoMP 1X4 (C) 1.4 / 0.03 1 1.9 0.090
CoMP 2X4 (C) 1.4 / 0.03 1 2.0 0.097
MU-MIMO 1X8 (E) 1.4 / 0.03 1 2.7 0.076
 Rural Macro / downlink / FDD: LTE Rel-8 meets the requirement
Rel-8 SU-MIMO 4X2 (C) 1.1 / 0.04 15 2.3 2.1 1.9 0.081 0.076 0.069
Rel-8 SU-MIMO 4X2 (A) 1.1 / 0.04 14 2.1 2.0 1.8 0.067 0.063 0.057
MU-MIMO 4X2 (C) 1.1 / 0.04 3 3.9 3.5 3.2 0.11 0.099 0.090
MU-MIMO 8X2 (C) 1.1 / 0.04 1 4.1 3.7 3.4 0.13 0.12 0.11
 Rural Macro / downlink / TDD: LTE Rel-8 meets the requirement

Rel-8 SU-MIMO 4X2 (C) 1.1 / 0.04 8 2.0 1.9 1.8 0.072 0.067 0.063
Rel-8 SU-MIMO 4X2 (A) 1.1 / 0.04 7 1.9 1.7 1.6 0.057 0.053 0.049
MU-MIMO 4X2 (C) 1.1 / 0.04 4 3.4 3.2 3.0 0.095 0.089 0.083
MU-MIMO 8X2 (C/E) 1.1 / 0.04 2 3.9 3.6 3.4 0.11 0.11 0.10
Rel-8 single-layer BF 8X2 (E) 1.1 / 0.04 4 2.4 2.3 2.1 0.11 0.10 0.093
 Rural Macro / uplink / FDD: LTE Rel-8 meets the requirement
(Ave./Edge) samples
Rel-8 SIMO 1X4 (C) 0.7 / 0.015 11 1.8 0.082
Rel-8 MU-MIMO 1X4 (A) 0.7 / 0.015 2 2.2 0.097
CoMP 2X4 (A) 0.7 / 0.015 2 2.3 0.13
 Rural Macro / uplink / TDD: LTE Rel-8 meets the requirement

(Ave./Edge) samples
Rel-8 SIMO 1X4 (C) 0.7 / 0.015 8 1.8 0.080
Rel-8 MU-MIMO 1X4 (A) 0.7 / 0.015 2 2.1 0.093
CoMP 2X4 (A) 0.7 / 0.015 1 2.5 0.15
MU-MIMO 1X8 (E) 0.7 / 0.015 1 2.6 0.10
 VoIP capacity: Rel-8 LTE meets all the requirements
FDD TDD
Antenna ITU
Scenarios
conf. requirement Number of Capacity Number of Capacity
samples (user/MHz/cell) samples (user/MHz/cell)
Indoor Hotspot 50 3 140 2 137
Urban Micro 40 3 80 2 74
(A)
Urban Macro 40 3 68 2 65
Rural Macro 30 3 91 2 86
Indoor Hotspot 50 3 131 3 130
Urban Micro 40 3 75 3 74
(C)
Urban Macro 40 3 69 3 67
Rural Macro 30 3 94 3 92
 Mobility Traffic Channel Link Data Rates
 Rel-8 LTE can meet all the requirements
FDD TDD
Median
LOS/ ITU
Scenarios SINR UL spectrum UL spectrum
NLOS requirement Number of Number of
(dB) efficiency efficiency
samples samples
(bps/Hz) (bps/Hz)
Indoor Hotspot 1.0 13.89 7 2.56 4 2.63
Urban Micro 0.75 4.54 7 1.21 4 1.14

Antenna conf.
1X4, NLOS
Urban Macro 0.55 4.30 7 1.08 4 0.95
Rural Macro 0.25 5.42 7 1.22 4 1.03
Indoor Hotspot 1.0 13.89 4 3.15 2 3.11
Urban Micro 0.75 4.54 4 1.42 2 1.48

Antenna conf.
1X4, LOS
Urban Macro 0.55 4.30 4 1.36 2 1.36
Rural Macro 0.25 5.42 4 1.45 2 1.38
Overview of LTE-Advanced Technologies
 Outlining of candidate technologies for LTE-Advanced

 LTE enhancement areas for LTE-Advanced
 Emerging technology areas for LTE-Advanced
Outline of Candidate Technologies for LTE-A
 Emerging technologies for LTE-Advanced
 Multi-hop transmission (relay)
 Multi-cell cooperation (CoMP: Cooperative Multipoint Tx/Rx)
 Heterogeneous cell overlay
 Self-organizing network
 Enhancements from LTE Rel-8/9

 Bandwidth/spectrum aggregation
 Contiguous and non-contiguous
 Control channel design for UL/DL
 MIMO enhancement
 Extended utilization of antennas (increasing the number of layers)
 UL SU-MIMO
 Enhanced UL/DL MU-MIMO
 Hybrid multiple access scheme for UL
 Clustered SC-FDMA in addition to SC-FDMA
 DL/UL Inter-cell Interference Management
LTE Enhancement Areas for LTE-Advanced
Spectrum Aggregation Advanced MIMO
High-order MIMO
UL SU-MIMO
Enhanced
DL/UL MU-MIMO
FFR & Power Control UL Hybrid Multiple Access

Power Spectral Density
:
mapping to a RB
Sector 1 A B Cluster
C D
Frequency
Sector 2 A C Modulation Time Domain

B D symbols S/P IFFT signal
DFT P/S
Sector 3 A D
B C
Reuse 1 Reuse 1/3
Emerging Technologies for LTE-Advaced
Multihop Transmission (Relay) Multi-cell Cooperation (Collaborative MIMO)
Self Organizing Network (SON) Heterogeneous Cell Overlay

Mobile
Core
Network
Macro eNB
Femto-cell
Controller
X2
Pico eNB Relay eNB
Femto eNB
Interne
t
LTE-Advanced Improvements
 A schematic view on LTE-Advanced improvements
LTE-Advanced
Data rate
Spectrum
Higher Order Aggregation
MIMO
LTE
CoMP
Coverage Extension
HeNB/Relay CoMP
SON
eNodeB
Spectrum and Carrier Aggregation
 Motivation
 Higher data rate support in wider bandwidth
 LTE-Advanced should extend up to 100MHz
 Backward compatible co-existence with LTE and LTE-A in IMT carrier bands
 Aggregation of muliple component carriers into overall wider bandwidth
 Each component carrier can appear as LTE carrier to LTE UE
 Two types of aggregation
 Case 1: Contiguous BW aggregation  Case 2: Non-contiguous BW aggregation

 Aggregated allocation of contiguous  Aggregated allocation of separated carrier
carrier BWs BWs
 Need of further clarification for  Need of further clarification for spectrum
feasibility of contiguous BW allocation range of BW aggregation
up to 100MHz
 Contiguos carrier aggregaion in a same frequency band

 Maybe difficult to find out frequency bands where maximum of 200MHz (FDD) can be allocated in
contiguos manner
 Non-contiguous carrier aggregation in different frequency band
 Possibility for wider total bandwidth without correspondingly wider contiguous spectum
 Feasibility, complexity and cost analysis should be done in RAN4 WG
MIMO Enhancement for LTE-Advanced
 DL MIMO enhancements
 Design issues
 8 Tx antennas
 RS structure to support 8 Tx antennas
 DM RS
 CSI RS
 # of codewords
 Codebook design
 Tx diversity in case of 8 Tx antennas
 MU-MIMO enhancement scheme
 UL MIMO enhancements
 Design issues
 UL SU-MIMO transmission
 Up to 4Tx antenna
 Reference signal design
 Number of codewords
 Tx diversity
 UL MU-MIMO enhancement
Uplink Multiple Access
 Motivation
 Problems of SC-FDMA
 PAPR/CM gain is not so crucial for
UE without power limitation problem : mapping to a RB
 Restricted flexibility due to “single-
carrier property” in scheduling and
Modulation
control channel design Symbols DFT
S/P
RE
IFFT
P/S
Time-domain
signal
 However, low PAPR/CM of SC- for TrBlk A
Clustered-
mapping
FDMA at power-limited situation is DFTsOFDM
still very important

 Uplink Hybrid Multiple Access of Modulation S/P
IFFT
Clustered SC-FDMA and SC- Symbols
for TrBlk B
DFT RE
mapping
P/S
Time-domain
signal
FDMA Clustered-
DFTsOFDM
 Clustered SC-FDMA transmission

for more flexible scheduling
 Non-contiguous resource allocation Modulation S/P
IFFT
Symbols DFT RE Time-domain
should also be supported for for TrBlk C mapping P/S signal
PUSCH transmission from UE with Clustered-
DFTsOFDM
sufficient amount of power
headroom both in absence and
presence of spatial multiplexing
 SC-FDMA transmission for
power-limited UEs
 Support of low PAPR/CM property
Relay [1]
 Several types of data transmission between eNB and
UE Out of focus in LTE-Advanced study
UE Relaying
Conventional UE-eNB Tx/Rx
• Direct inter-UE connectivity
• Conventional single-hop Tx/Rx between UE • Autonomous ad-hoc network configuration
and eNB as a basic connection scheme and management
• Support of emergency call status
Wireless link
eNB connection
Relay
Node
Relay
Node Relay Node Tx/Rx
• Remote relay node Tx/Rx

• Coverage extension and throughput
enhancement
Main focus in LTE-Advanced study
Relay [2]
 Exemplary use case for relay
CoMP [1]
 CoMP stands for
coordinated multipoint
transmission
 CoMP in Rel-10 time
frame
 Agreed not to pursue
standardized CoMP
solution at least during
Rel-10 time frame
 However, new study item
for CoMP was created
during last RAN plenary
meeting in March
CoMP [2]
 CoMP categories under
consideration
 Joint Processing
 Data is available at each point in
CoMP cooperating set
 Joint Transmission
 Dynamic Cell Selection
 Coordinated
Scheduling/Beamforming (CS/CB)
 Data is only available at serving cell
CoMP [3]
 Joint Transmission
 Data to a single UE is available at multiple transmission points
 PDSCH transmission from multiple points (part of or entire CoMP
cooperating set) at a time
 Coherently or non-coherently
 To improve the received signal quality and/or cancel actively interference
for other UEs
 Dynamic Cell Selection
 CoMP transmission point from a single point
 Can change dynamically within the CoMP cooperating set.
 Cooperative Scheduling/ Beamforming (CS/CB)
 Data is only available at serving cell
 User scheduling/beamforming decisions are made with coordination
among the CoMP cooperating set.
 CoMP transmission point : serving cell
More Details on LTE-Advanced
Component Technologies
 Spectrum and carrier aggregation

 Relay
 Enhanced DL MIMO
 UL MIMO
 CoMP
Spectrum and carrier aggregation
 Overview
 Carrier Types
 MAC-PHY interface
 Uplink Multiple Access
 Uplink Control Channel
 Downlink Control Channel
 UL Power control
Overview [1]
 Carrier aggregation
 Support wider bandwidth
 Two or more component carriers
 Up to 100MHz and for spectrum aggregation
 Each component carrier limited to a maximum of 110 RBs
 Using Rel’8 numerology
 Carrier aggregation type

 Contiguous
 Non-contiguous
LTE/MIMO 표준기술
Overview [2]
 Concept of carrier aggregation
Contiguous component carrier

LTE
bandwidth
Frequency
Non-contiguous component carrier
Aggregated bandwidth
Frequency
Overview [3]
 Deployment scenarios in RAN4
 Intraband contiguous CA
 Originally, intraband contiguous CA scenario was proposed only for
TDD, but it was agreed also for FDD afterwards for the sole reason of
satisfying ITU-R requirement
Uplink (UL) band Downlink (DL) band

E-UTRA E-UTRA Duple
UE transmit / BS receive UE receive / BS transmit
CA operating Channel Channel x
Band Band BW MHz FDL_low (MHz) – FDL_high BW MHz mode
FUL_low (MHz) – FUL_high (MHz)
(MHz)
CA_40 40 2300 – 2400 [TBD] 2300 – 2400 [TBD] TDD
CA_1 1 1920 – 1980 [TBD] 2110 – 2170 [TBD] FDD
Overview [4]
 Interband non-contiguous CA
Uplink (UL) band Downlink (DL) band
E-UTRA E-UTRA Duple
UE transmit / BS receive UE receive / BS transmit
CA operating Channel Channel x
Band Band BW MHz FDL_low (MHz) – FDL_high BW MHz mode
FUL_low (MHz) – FUL_high (MHz)
(MHz)
1 1920 – 1980 [TBD] 2110 – 2170 [TBD]
CA_1-5 FDD
5 824 – 849 [TBD] 869 – 894 [TBD]
 TBD bandwidth will be finally decided after having RAN4

discussion
Overview [5]
 UE capability regarding carrier aggregation
 LTE-A UE
 Simultaneous transmission/reception on multiple component carrier
 Depends on the transmission/reception capability
 Rel’8 UE
 Transmission on a single component carrier only
 Characteristics of component carrier
 It shall be possible to configure all component carriers LTE Release 8 compatible at least
when the aggregated numbers of component carriers in the UL and the DL are same
 Consideration of non-backward-compatible configurations of LTE-A component carriers is not
precluded (CC only for LTE-A)
System bandwidth, CC, e.g., 20 MHz

e.g., 100 MHz
Frequency
UE capabilities
• 100-MHz case
• 40-MHz case
• 20-MHz case
(Rel. 8 LTE)
Carrier Types
 Backward compatible carrier
A carrier accessible to UEs of all existing LTE releases
 Can be operated as a single carrier (stand-alone) or as a part of
carrier aggregation
 For FDD, backwards compatible carriers always occur in pairs, i.e.
DL and UL
 Non-backward compatible carrier
A carrier not accessible to UEs of earlier LTE releases
 Can be operated as a single carrier (stand-alone) from the duplex
distance
 Otherwise, as a part of carrier aggregation
MAC-PHY Interface
 From a UE perspective
 There is one transport block (in absence of spatial multiplexing)
 One hybrid-ARQ entity per scheduled component carrier.
 Each transport block is mapped to a single component carrier
 A UE may be scheduled over multiple component carriers
simultaneously.
transport block transport block
Channel Channel
coding coding
Modulation Modulation
RB mapping RB mapping
Component carrier 1 Component carrier 2
20MHz 20MHz
One UE
Uplink Multiple Access
 SC-FDMA for PUSCH
 One DFT per component carrier
: mapping to a RB
 Supported for spatial multiplexing

Modulation S/P IFFT Time-domain
 Resource allocation Symbols

for TrBlk A
DFT
Clustered-
DFTsOFDM
RE
mapping
P/S signal
 Frequency-contiguous
 Frequency-non-contiguous Modulation
Symbols DFT
S/P
RE
IFFT
P/S
Time-domain
signal
for TrBlk B mapping
Clustered-
DFTsOFDM
Modulation S/P
Symbols DFT RE IFFT Time-domain
for TrBlk C mapping P/S signal
Clustered-
DFTsOFDM
 Uplink multiplexing of L1/L2 control signalling and data

 Control signalling is transmitted on PUCCH simultaneously with data
on PUSCH
 Control signalling is multiplexed with data on PUSCH according to the
same principle as in Rel-8
Uplink Control Channel
 PUCCH design
 Rel’10 design supports up to 5 DL CC
 Consider extendability to larger number of DL CC in the future
 All ACK/NACK for a UE can be transmitted on PUCCH in absence of
PUSCH transmission
 Simultaneous A/N on PUCCH transmission from 1 UE on multiple UL CCs
is not supported
 A single UE-specific UL CC is configured semi-statically for carrying PUCCH
A/N
 Method for assigning PUCCH resource(s) for a UE on the above single UL
carrier in case of carrier aggregation
 Implicit / Explicit / Hybrid: FFS
 Note that for a CA-capable UE that is configured for single UL/DL carrier-pair operation
, single-antenna PUCCH resource assignment shall be done as per Rel-8.
 A single UE-specific UL CC is configured semi-statically for carrying
PUCCH A/N, SR, and periodic CSI from a UE
 Concept of primary carrier
 One SR per UE transmitted on PUCCH
 Semi-statically mapped onto one UE specific UL CC
 Periodic CSI reporting for up to 5 DL CC supported
 Semi-statically mapped onto one UE specific UL CC
 Following Rel8 principles for CQI/PMI/RI
 Consider ways to reduce reporting overhead, e.g. DL CC cycling
 Consider ways to support extending CSI payload
 Further discussion points for ACK/NACK transmission
 Method(s) for A/N multiplexing
 How many simultaneous PUCCH signals?
 PUCCH format 1b with SF reduction to 2 or 1
 Channel selection with appropriate modification
 PUCCH format 2
 New PUCCH signal/format (e.g. DFT-S-OFDM based)
 A/N bundling within / across CCs
 Also consider TDD
H H H H H H H H H
C C C C C C C C C
S S S S S S S S S
D D D D D D D D D
P P P P P P P P P
A/N A/N A/N
H A/N H H H H
A/N H A/N H H A/N H A/N H A/N Joint coding
C C C C C C C C
Bundling C C
C C C C C C C C C C
U U U U U U U U U U
P P P P P P P P P P
Multiple resources transmission Bundling Joint coding
 CQI (Channel Quality Indication)
 Multiple CQIs on single component carrier
 Multiple resources transmission
 Joint coding
 TDM
DL CC #0 DL CC #1 DL CC #2
DL CC #0 DL CC #1 DL CC #2
H CQI H H H H
CQI H CQI
CQI CQI CQI
C C C C C C H H
C C C C C C C C Joint coding
U U U U U U C C
P P P P P P U U
DL CC #0 DL CC #1 DL CC #2 P P
H H
Multiple resources transmission CQI C
C
CQI C
C
CQI
U
P
U
P Joint coding
subframe #n
Time
H H
C C
C C
U U
P P
subframe #n+1
H H
C C
C C
U U
P P
subframe #n+2
TDM
Downlink Control Channel
 PDCCH structure
 PDCCH is transmitted within one component carrier
 Mapping of PDCCH information
 Separate coding of DL/UL scheduling for each component carrier
 Based on DCI format(s) for single carrier
 Linked carrier scheduling w/o CIF (carrier indicator field)
 Rel’8 PDCCH structure and DCI formats
 Cross carrier scheduling with CIF
 Rel’8 DCI formats extended with 3 bit carrier indicator field
 Reusing Rel’8 PDCCH structure
 Solutions to PCFICH detection errors on the CC carrying PDSCH to be standardized
 PDCCH blind decoding reduction is desirable
CC#1 CC#2 CC#1 CC#2
CFI correct CFI error CFI correct CFI error
PDCCH correct PDCCH DTX PDCCH PDCCH
correct correct
PDSCH error due to
CFI error, also leads to
Receive PDSCH Not receive PDSCH Receive PDSCH HARQ buffer
corruption.
Linked Carrier Scheduling Cross Carrier Scheduling
 Linkage
between PDSCH/PUSCH
and PDCCH
 Further discussion required on
whether at least the following is
supported:
 A UE only monitors PDCCH on
one DL CC for each
PDSCH/PUSCH CC
 For any DL carrier with CIF where the
UE monitors PDCCH, PDCCH on the
DL carrier shall be able to schedule
PDSCH at least on the same carrier
and/or PUSCH on a linked UL carrier
 Further discussion required on
whether this can be extended to
support modified Option 1
 PHICH transmission
 Re-use PHICH physical transmission aspects from Rel’8
 Orthogonal code design, modulation, scrambling sequence, mapping to REs
 PHICH transmitted only on the ‘DL CC used to transmit the UL grant’
 PHICH resource mapping rules:
 For 1-to-1 or many-to-1 mapping between DL and UL without CIF
 Reuse Rel’8 mapping
 For many-to-1 UL:DL mapping or many-to-1 mapping between DL and UL
with CIF
 Single set of PHICH resources shared by all UEs (Rel-8 to Rel-10)
 DM RS cyclic shift mechanism remains available and can be used to reduce collision
probability
 Working assumption to be confirmed at RAN1#60bis if no fundamental problem
identified:
 Further discussion point
 Additional standardised mechanism for handling PHICH collisions needed?
 PCFICH
 Independent control region size per CC
 On any carrier with a control region, re-use Rel’8 design
 Modulation
 Coding
 RE mapping
 PCFICH for cross-CC scheduling

 In case of cross carrier scheduling, a standardized solution will be
supported to provide CFI to the UE for the carriers on which
PDSCH is assigned
Uplink Power Control
 Assume similar operation of Rel’8:
 Mainly compensate for slow-varying channel conditions while reducing the
interference generated towards neighboring cells
 Fractional PC or full path-loss compensation is used on PUSCH and full path-
loss compensation on PUCCH
 Supports component carrier specific UL PC for both contiguous and
non-contiguous CC aggregation
 Which PC parameters are CC-specific?
 P0_PUSCH, P0_PUCCH, α, δpusch, ∆TF are CC-specific
 There is a max power for the total UE transmit power (provided by RAN4)
 There is a CC-specific max power
 Pathloss derivation
 The DL CC used for pathloss derivation for power control of each UL CC is configured by
the network (any restrictions on correspondence between DL and UL CCs for this purpose
are up to RAN4)
 Whether a pathloss offset per CC needs to be signalled to the UE is FFS
 The number of DL CCs measured is up to RAN4
 TPC command transmission
 TPC in UL grant is applied to UL CC for which the grant applies
 TPC in DL grant is applied to UL CC on which the ACK/NACK is transmitted
Uplink Power Control
 PHR
 Per CC
 FFS whether or not PHR is per channel (i.e. PUSCH / PUCCH) within
each per-CC PHR
 Max power scaling
 Starting point:
 PUCCH power is prioritised; remaining power may be used by PUSCH (i.e.
PUSCH power is scaled down first, maybe to zero)
 scaling is per channel
 Detailed formula is FFS
 Power control for multiple antennas: FFS
Relay
 Overview
 Type 1 Relay
 Type 2 Relay
 Resource Partioning for Relay-eNB link
 Access-Backhaul Partitioning
 Backward compatible backhaul partitioning
 Backhaul Resource Assignment
 R-Channel design
Overview
 Relaying
 as a tool to improve e.g. the coverage of high data rates, group mobility, temporary
network deployment, the cell-edge throughput and/or to provide coverage in new areas.
 Relay functionalities
 Wirelessly connected to radio-access network via a donor cell.
 Connection type
 Inband,
 Outband
 Duplexing
 Half duplex relay  resource partioning required
 Full duplex relay
 Outband relay
 Inband relay with enough spatial separtion or enhanced interference cancellation
 no need to consider resource partioning
 Relay classification w.r.t the knowledge in the UE
 Transparent
 Non-transparent
 Depending on the relaying strategy, a relay may
 Control cells of its own (similar to eNB : type 1 relay)
 Be part of the donor cell (L2 relay, Type 2 relay)
 Relay in Rel’10 LTE-Advanced
 Inband half duplex relay and outband relay will be included in the initial version of LTE-
Advanced
Type 1 Relay
 Control Cells of its own
 It control cells, each of which appears to a UE as a separate cell distinct
from the donor cell
 Has unique physical-layer cell identity (defined in Rel-8)
 Shall transmit its own synchronization, reference symbols, ..
 The same RRM mechanisms as normal eNB
 No difference in accessing cells controlled by a relay and cells controlled

by a “normal” eNB from a UE perspective
 Shall appear as a Rel-8 eNB to Rel.8 UE
 To LTE-A UEs, it should be possible for a type 1 relay node to appear

differently than Rel.8 eNB to allow for further performance enhancement
 UE shall receive scheduling information and HARQ feedback directly from
the relay node and send its control channels (SR/CQI/ACK) to the relay
node
 Self-backhauling, in-band relay
Type 2 Relay
 Part of the donor cell
 It does not have a separate Physical Cell ID
 Would not create any new cells
 It is transparent to Rel-8 UEs;
 A Rel-8 UE should not be aware of the presence of a type 2 relay node
 At least part of the RRM is controlled by the eNB to which the
donor cell belongs
 It can transmit PDSCH
 At least, it does not transmit CRS and PDCCH
 L2 relay, smart repeaters, decode-and-forward relays
Resource Partioning for Relay-eNB Link
 Link definition
 Backhaul link
 DL backhaul : eNB-> RN
 UL backhaul : RN -> eNB
 Access link
 DL access : RN -> UE
 UL access : UE -> RN
 Inband Backhauling of Relay
 eNB-to-relay link operates in the same frequency spectrum as the
relay-to-UE link
 In this case, half duplex relay operation is more feasible
 Simultaneous eNB-to-relay and relay-to-UE transmissions on the same
frequency resource may not be feasible
 Due to relay transmitter causing interference to its own receiver
 Unless sufficient isolation of the outgoing and incoming signals is provided
 Similarly,
relay may not be possible to receive UE transmissions
simultaneously with the relay transmitting to the eNB
 Therefore, resource partioning scheme should be taken into
account in case of inband half duplex relay
 Relay functionalities
 In-band backhauling of the relay traffic
 General principle for resource partitioning at the relay:
 eNB → RN and RN → UE links are time division multiplexed in a single
frequency band (only one is active at any time)
 RN → eNB and UE → RN links are time division multiplexed in a single
frequency band (only one is active at any time)
 Multiplexing of backhaul links in FDD:
 eNB → RN transmissions are done in the DL frequency band
 RN → eNB transmissions are done in the UL frequency band
 Multiplexing of backhaul links in TDD:
 eNB → RN transmissions are done in the DL subframes of the eNB and RN
 RN → eNB transmissions are done in the UL subframes of the eNB and RN
Access-Backhaul Partitioning
 Example of UL resource TDM partitioning
eNB UL RX UL RX
subframe
Relay UL TX UL TX No TX
Relay UL RX No RX UL RX
R-UE UL TX e.g. blocked subframe UL TX
Access-Backhaul Partitioning
 Illustration
F2 F1
UE1
UL (F2) DL (F1)
eNB F1: DL frequency (FDD)

F2: UL frequency (FDD)
UL (F2) DL (F1)
RN
One link active at a time One link active at a time
UL (F2) DL (F1)
UE2
Backward Compatible Backhaul Partitioning
 Backward compatibility of Relay node
 In certain subframes, a relay node receives DL transmissions
 In certain other subframes, a relay node transmits on DL
 In the subframes where a relay node receives DL transmissions, Rel. 8 UE does
not expect any relay transmission in PDSCH by configuring MBSFN subframe
 Relay backhauling subframe
 Create transmission gap in the relay-to-UE transmission
 Relay is not transmitting any signal to UE when it is supposed to receive data from the
donor eNB
 Configuring MBSFN subframes
 During “gaps”, UEs(including Rel-8 UEs) are not supposed to expect any relay transmission
 Relay-to-eNB transmissions can be facilitated by not allowing any terminal-to-relay
transmission in some subframes
 Relay should transmit PDCCH and CRSs in PDCCH region
eNB-to-relay transmission
One subframe
transmission gap
Ctrl Data Ctrl
(“MBSFN subframe”)
No relay-to-UE transmission
Backhaul Resource Assignment
 Backhaul Subframe allocation
 At the RN, the access link DL subframe boundary is aligned with the backhaul link
DL subframe boundary, except for possible adjustment to allow for RN
transmit/receive switching
 The set of DL backhaul subframes
 During which DL backhaul transmission may occur
 Semi-statically assigned
 The set of UL backhaul subframes
 During which UL backhaul transmission may occur,
 Can be semi-statically assigned,
 Or implicitly derived from the DL backhaul subframes using the HARQ timing
relationship
 R-PDCCH (Relay Physical Downlink Control CHannel)
 R-PDCCH is used to assign resources for the DL backhaul data
 Dynamically or semi-persistently assign resources
 May assign DL resources in the same and/or in one or more later subframes.
 R-PDCCH is used to assign resources for the UL backhaul data
 Dynamically or semi-persistently assign resources
 May assign UL resources in one or more later subframes.
R-Channel Design (TR 36.814)
 R-PDCCH resources
 PRBs for R-PDCCH transmission is semi-statically assigned
 Resources for R-PDCCH transmission within semi-statically assigned may
vary dynamically between subframes
 Resources that are not used for R-PDCCH within the semi-statically
assigned PRBs may be used to carry R-PDSCH or PDSCH
 R-PDCCH decoding
 R-PDCCH transmitter processing (channel coding, interleaving,
multiplexing, etc.) should reuse Rel-8 functionality to the extent possible
 Search space approach of R8 is used for the backhaul link
 Use of common search space, which can be semi-statically configured (and
potentially includes entire system bandwidth
 If RN-specific search space is configured, it could be implicitly or explicitly
known by RN.
 The R-PDCCH is transmitted starting from an OFDM symbol within
the subframe that is late enough so that the relay can receive it.
 “R-PDSCH” and “R-PDCCH” can be transmitted within the same
PRBs or within separated PRBs.
R-Channel Design
 Backhaul link reference signal
 For R-PDCCH,
 For a given RN, R-PDCCH demodulation RS type (CRS or DM-RS) shall not
change dynamically nor depend on subframe type.
 Demodulate with
 In normal subframes:
 Rel-10 DM-RS when DM-RS are configured by eNB
 Otherwise Rel-8 CRS
 In MBSFN subframes, Rel-10 DM-RS
 Baseline may be modified (in relation to which OFDM symbols contain DM RS)
depending on RAN4 response on the timing.
 For downlink shared data transmission on Un
 Same possibilities as for R-PDCCH
 Further discussion point

 R-PDCCH multiplexing
 Backhaul link HARQ timing
 Detailed R-PDCCH design
Backhaul Link Timing: DL [1]
 Backhaul downlink timing
 The RN can receive Un DL transmissions starting with OFDM symbol numbered m
and it can stop receiving with the OFDM symbol numbered n.
 Here OFDM symbol numbering within the subframe starts at 0
 k is equal to the number of OFDM symbols used for the L1/L2 control region at the RN
access
 The following cases are deemed for further consideration:
 Case 1: RN can receive the DL backhaul subframe starting from OFDM symbol m=k+1 until
the end of the subframe (n=13 in case of normal CP)
 This corresponds to the case when RN switching time is longer (> cyclic prefix) and RN DL access
transmit time is slightly offset with respect to DL backhaul reception time at the RN
 Case 2: RN can receive the DL backhaul subframe starting from OFDM symbol m=k until
the end of the subframe (n=13 in case of normal CP)
 This corresponds to the case when RN switching time is sufficiently shorter than the cyclic prefix and
RN DL access transmit time is aligned to the DL backhaul reception time at the RN
 Case 3: RN can receive the DL backhaul subframe starting from OFDM symbol m ≥k until
OFDM symbol n<13 (depending on the propagation delay and the switching time)
 This corresponds to the case when RN DL Uu transmissions is synchronized with the eNB DL
transmissions
 Case 4: RN can receive the DL backhaul subframe starting from OFDM symbol 0 until
OFDM symbol n=13-(k+1)
 This corresponds to the case when RN can receive the normal PDCCH.
 Case 1: DL (-) timing offset
A fixed delay in addition to propagation delay
 Case 2 (DL): No offset, Switching time < CP
 Case 3 (DL): Global Tx timing sync
 Cas3 3a: [(Tp<L)&(Tp<G1)&(Tp+G2<L), symbol_length = L]
 Case 3 (DL): Global Tx timing sync
 Case 3b: [(G1<Tp<L)&(Tp+G2<L), symbol_length = L]
Backhaul Link Timing: UL [1]
 Backhaul link UL timing
 RNshould transmit SC-FDMA symbols m=0 until the end of the UL
backhaul subframe (n=13 in case of normal CP)
 This corresponds to the case when the access link and backhaul link
UL subframe boundary is staggered by a fixed gap and RN switching
time is considered by configuring the UE not to transmit the last SC-
FDMA symbol of the Uu link
 There are concerns about the impact of Case 2b on the usage of SRS
and/or CQI on the access link
 Companies are encouraged to analyze the impact and evaluate the pe
rformance, especially for TDD, for the next meeting
 If impact is not acceptable, consider other RN UL timing cases
Backhaul Link Timing: UL [2]
 UL timing: (-) time offset
 Not listening to the symbol#13 (or SRS) in Uu link
Enhanced DL MIMO Transmission
 DL RS: Overview
 DL-RS: DM-RS
 DL-RS: CSI-RS
 DL MIMO: Overview
 DL-MIMO: DL-MIMO in LTE-Advanced
DL-RS: Overview [1]
 RS types in LTE-Advanced
 Two types of new RS are introduced in LTE-Advanced in addition to CRS
(Common Reference Signal) defined in Rel-8
 DMRS (Demodulation RS)
 CSI-RS (Channel State Information RS)
 UE-specific DM-RS, which is precoded, makes it possible to apply non-
codebook-based precoding
 UE-specific DM-RS will enable application of enhanced multi-user
beamforming such as zero forcing (ZF) for, e.g., 4-by-2 MIMO
DL-RS: Overview [2]
 DM-RS based system in LTE-Advanced
 Support of Rel-8 Common RS
 LTE-Advanced eNB should always support LTE UE as well
 Rel-8 CRS is also used for LTE-Advanced UEs to detect PCFICH, PHICH, PDCCH, PBCH
and PDSCH (TxD only)
 RS overhead optimization  main motivation for DM-RS based approach
 Employing DM-RS for demodulation of PDSCH only (except TxD)
 Transmitted only in an RB allocated for a UE in every subframe
 12RE up to rank-2
 24RE up to rank-8
 Employing CSI-RS for measurment
 Transmitted by pucturing PDSCH RE in a duty cycle
 Idea is that CSI-RS overhead can be made very small (e.g. less than 1% for 8Tx antenna support)
 Define LTE-Advanced only subframe by MBSFN type signalling
 LTE-Advanced PDSCH only in these subframe
 Rel-8 CRS is not transmitted in PDSCH region
 Independent antenna configuration
 Although LTE-Advanced antenna port is larger than 4Tx, Rel-8 antenna port can be defined less than
4Tx
DL-RS: Overview [3]
 Allow transmissions of PDSCH to Rel-10 UEs in MBSFN (LTE-
advanced) subframes
 Possible to configure CSI RS for transmission in LTE-Advanced subframes
 Possible to use LTE-Advanced features without any LTE-
advanced subframes
 Cell specific CSI-RS possible to transmit in normal Rel-8 subframes
 Consideration on CSI-RS impact on PDSCH transmissions to Rel-8
UEs for various RS densities needed
 There should be no impact from CSI RS transmission on transmission of
PBCH/PSS/SSS
 Strive for same CSI RS and DM-RS patterns regardless of
subframe type (DL Rel-8 or DL LTE-A subframes)
 DM-RS in support of up-to 8 transmission layers should be
defined
DL-RS: DM-RS [1]
 Characteristics
 UE specific
 Transmitted only in scheduled RBs and the corresponding layers:
 Design principle is an extension of the concept of Rel-8 UE-

specific RS (used for beamforming) to multiple layers
 RSs on different layers are mutually orthogonal
 RS and data are subject to the same precoding operation

 No need to transmit precoding information
 Per-PRB based channel estimation
 Precoding granularity indication is FFS
 Complementary use of Rel-8 CRS by the UE is not precluded
DL-RS: DM-RS [2]
 DM-RS pattern for rank-1 and rank-2
 Forward compatible DM-RS pattern design from LTE Rel-9 dual
layer beamforming
 CDM between two layers
 DM-RS pattern agreed for Rel-9 dual layer beamforming
Normal subframe DwPTS (symbols >= 11) DwPTS (symbols<11)
 Extended CP was not agreed and thus is not supported in conjunction

with transmission mode 8 in Rel-9.
 Note that this does not preclude a solution being introduced in a later
release
DL-RS: DM-RS [3]
 DM-RS pattern for rank-3 and rank-4
 Baseline is alternative 1 in the figure below
 CDM+FDM, OCC length=2
 24RE in an RB
DwPTS with 11,12 DwPTS with 9,10

OFDM symbols OFDM symbols
DL-RS: DM-RS [4]
 DM-RS pattern for rank5~8
 Hybrid CDM+FDM DMRS patterns are adopted for rank 5-8 transmission
with normal CP (normal subframe, DwPTS)
 Same location with same density (24RE per PRB) as the rank3-4
 The length of OCC in time domain is 4 for both CDM groups
 2 CDM group, OCC length=4
Normal subframe DwPTS with 11,12 DwPTS with 9,10

OFDM symbols OFDM symbols
 Multiple RB optimization
 Followings are FFS
 DM-RS pattern optimization according to the number of RBs allocated
 Precoding granularity indication
DL-RS: CSI-RS [1]
 Baseline assumption for CSI-RS
 CSI-RS is transmitted by puncturing data RE on both LTE Rel-8/9 and
LTE-Advanced PDSCH
 Some performance impacts on the legacy Ues are inevitable
 Loss of information due to puncturing
 Interference from CSI-RS
 Uniform frequency spacing and periodic time domain transmission
 Agreed to transmit all the CSI-RS for every antenna port within the same
subframe
 Overhead assumption
 CSI-RS density in frequency domain  1 RE per PRB for 2, 4 and 8 antenna
port
 CSI-RS density in time domain
 Multiple of 5 msec is baseline for further evaluations.
 10ms periodicity is prioritized
 Assuming 10ms periodicity, CSI-RS overhead can be calculated as 0.06%
(1/1680) (8 antenna port = 0.48 %)
 Time density: 1 symbol every 10ms per antenna port  1/140
 Frequency density: 1 RE per PRB  1/12
DL-RS: CSI-RS [2]
 Relationship between CSI-RS and Rel-8 CRS
 No mixed use of Rel-8 CRS and Rel-10 CSI RS for a configured Rel-10
CSI measurement of a given cell at Rel-10 UE (for all possible number of
antenna ports in the cell)
 For the configured CSI measurement the UE measures either on Rel-8 CRS or
on Rel-10 CSI RS for the given cell
 8 Rel-10 CSI RS can be configured for Rel-10 CSI measurements in a
given cell
 For this case of Rel-10 CSI measurements, only the 8 Rel-10 CSI RS are used
for the CSI measurements corresponding to the given cell
 CSI RS are punctured into the data region of normal/MBSFN subframes
 However, independent antennea configuration is possible
DL-RS: CSI-RS [3]
 Further agreement in RAN1 with respect to CSI-RS
 Full-power utilization is the design target.
 Send an LS to RAN4 asking about the feasibility of 9 dB boosting.
 Same data RE power between a data RE in the OFDM symbol containing CSI-RS
and a data RE in the OFDM symbol without CSI-RS/Rel-8 CRS is assumed within a
subframe
 Resource elements (REs) of CSI-RS are configured and/or tied to system
parameters for inter-cell orthogonality, i.e, no collision between CSI-RS
 Partial collision of CSI-RS for inter-cell randomization is not precluded.
 CSI-RS pattern for {2,4,8} CSI-RS ports
 Port 0 is fully configured (subframe, OFDM symbol, frequency location) by L3 signaling and
/or tied to system parameters
 The other ports follow port0 (implicit)
 FFS if all ports have the same shift or different shift in time and frequency
 For intra-cell CSI-RS, FDM/TDM/CDM/CSM needs further study.
 Study RE muting, i.e., no collision between CSI-RS and data, for multi-cell CSI
measurement
 Consider the impact of muting on UE interference measurement
 Consider the impact on Rel-8 UE
 Power reallocation of muted REs is FFS
DL-MIMO: Overview
 Gains from MIMO
DL-MIMO: Overview
DL-MIMO in LTE-Advanced
 The number of transmit antennas in DL: up to 8
 Design issue
 Number of codewords
 Reference signal (RS)
 Transmit diversity
 Precoding
 Multi-user MIMO (MU-MIMO)
 Maximum number of codewords: 2

 2 transport blocks in a subframe
 Number of MCS fields: 2

 Separate link adapation of two codewords
 CW-to-Layer mapping in support of 8-Tx antenna
 Up to 4 layers, same mapping rule as in Rel-8
 For higher number layers, it was agreed to simply extend the Rel-8 mapping so that two
codewords are as much evenly distributed over each layer as possible
DL MIMO in LTE-Advanced
 Transmit Diversity Scheme
 Rel-8TxD will be reused with CRS in normal subframe
 TBD: TxD definition in LTE-Advanced only subframe
 Alt 1: rank-2 DRS supports SFBC
 Alt 2: channel interpolation with the CRS in the next subrame PDCCH
region
 Alt 3: no definition of TxD in LTE-Advanced only subframe
DL MIMO in LTE-Advanced
 MU-MIMO
 In Rel-9, DM-RS based MU-MIMO scheme was decided
 Dynamic indication of DM-RS port is supported in case of rank 1 transmission
 To enable scheduling of two UEs with rank-1 transmission using different orthogonal DMRS ports on
the same PDSCH resources
 SU/MU assumption
 no explicit signaling of the presence of co-scheduled UE in case of rank 1 transmissions
 in case of rank-1 transmission, the UE cannot assume that the other DM RS antenna port is not
associated with PDSCH assigned to another UE
 Dynamic SU/MU switching in LTE-Advanced
 Switching between SU- and MU-MIMO transmission is possible without RRC
reconfiguration
 Transparent vs. Non-transparent MU-MIMO
 “Transparent” here means that no downlink signalling is provided to indicate to a UE
whether a downlink transmission to another UE is taking place in the same RB.
 No clear preference for transparent or non-transparent MU-MIMO at this stage.
 If MU-MIMO were to be non-transparent, strongest possibilities to consider for downlink
signalling include:
 whether / which DM-RS ports are used for other UEs
 Power offset
 Target design criteria for 8Tx Codebook
 8Tx codebook is now under discussion for feedback purpose only
 Design criteria
 For rank > 2, optimize for SU-MIMO only
 For rank <= 2, optimize for both SU- and MU-MIMO
 For MUMIMO, target UE separation in correlation domain
 Suitable for various antenna configurations
 Feedback of precoding codebook
 Implicit feedback (PMI/RI/CQI) is used also for Rel-10
 UE spatial feedback for a subband represents a precoder (as constructed below)
 CQI computed based on the assumption that eNodeB uses a specific precoder (or precoders), as given by
the feedback, on each subband within the CQI reference resource
 Note that a subband can correspond to the whole system bandwidth
 A precoder for a subband is composed of two matrices
 The precoder structure is applied to all Tx antenna array configurations
 Each of the two matrices belong to a separate codebook
 The codebooks are for further study
 The codebooks are known (or synchronized) at both the eNodeB and UE
 Codebooks may or may not change/vary over time and/or different subbands
 That is, two codebook indices together determine the precoder
 One of the two matrices targets wideband and/or long-term channel properties
 The other matrix targets frequency-selective and/or short-term channel properties
 Note that a matrix codebook in this context should be interpreted as a finite enumerated set of matrices
that for each RB is known to both UE and eNodeB.
 Note that Rel-8 precoder feedback can be deemed as a special case of this structure
UL MIMO
 UL MIMO: Overview
 UL MIMO: Multiple Access Scheme
 UL MIMO: Receiver for UL MIMO
 UL MIMO: Multi-Antenna Support
 UL MIMO: Reference Signal
UL-MIMO: Overview [1]
 UL-MIMO in Rel’8
 UL MIMO was not supported for complexity reason
 64QAM was introduced instead during Rel’8 time frame
 Only antenna switching Tx diversity is defined in Rel-8 LTE
 MU-MIMO was supported in an implicit manner (specification transparent way)
 LTE-Advanced
 Agreed to employ SU-MIMO in LTE-Advanced
 Crucial in satisfying 3GPP’s own peak spectrum efficiency requirement
 The number of transmit antennas in UL
 Up to 4 transmit antenna will be supported
 4 layer transmission
 Design issue
 Multiple access scheme
 Number of codewords
 Precoder design
 Transmit diversity
UL-MIMO: Overview [2]
 Necessity of Preserving CM
 OFDM vs. SC-FDMA discussion in early LTE-Advanced SI phase
 SC-FDMA is agreed as an uplink multiplexing scheme
 MIMO transmission should be implemented with SC-FDMA
 SC-FDMA based MIMO transmission
 CM can be one of design criteria for uplink MIMO scheme
 Single antenna mode support

 In this mode, the UE behavior is same as the UE behaviour with single
antenna from eNB’s perspective
 Exact UE implementation is left to UE vendors (e.g., PA archiecture)
 PUCCH and/or PUSCH and/or SRS transmission can be independently
configured for single uplink antenna port transmission
 Detail scenario and operation is FFS
 UL single antenna port mode is the default operation mode before
eNB is aware of the UE transmit antenna configuration
UL-MIMO: Multiple Access Scheme
 SC-FDMA vs. OFDMA
 Complexity
 SC-FDMA: turbo SIC
 OFDMA: maximum likelihood detector (MLD)
 MLD is more complex in 16/64 QAM, especially for 4x4 configuration
 Latency
 Depends on computational complexity
 SC-FDMA and OFDMA may not give significant difference
 Performance
 OFDMA shows gain over SC-FDMA in high SNR range for 2x2 configuration
 Similar performance for 2x4 configuration
 OFDMA shows system level gain over SC-FDMA in 2x2 and 4x4 configuration
 SC-FDMA was adopted for multiple access scheme as UL MIMO
transmission
UL-MIMO: Receiver for UL MIMO
 Soft interference canceller (SIC): turbo SIC
 Implementationflexibility: various algorithms
 One implementation [1]: R1-083732
UL-MIMO: Multi-Antenna Support [1]
 Number of codewords: 2
2 transport blocks in a subframe
 Same codeword-to-layer mapping as in LTE downlink
codeword to layer mapping for 2 Tx and 4 Tx
 Candidates forTx diversity for PRACH
 PVS, CDD, TSTD
 Candidates for Tx Diversity for PUSCH

 No consensus on the necessity of TxD in Rel-10
 Identify target use cases where 2 TxD bring additional benefit, compared to single antenna
mode and SM mode
 Following candidates are on the table
 2 transmit antennas
 FSTD
 STBC: special care of unpaired symbol due to SRS
 Modified SFBC
 Closed loop rank 1 precoding
 4 transmit antennas
 STBC + FSTD
 STBC + PSD
 CDD + FSTD
 Modified SFBC + FSTD
 Closed loop rank 1 precoding
 PUCCH TxD
 2 Tx PUCCH transmit diveristy scheme
 Rel-8 PUCCH format 1/1a/1b: Spatial Orthogonal Tramsit Diveristy (SORTD) is applied
 The same modulation symbol d(0) is transmitted on different orthogonal resources for different
antennas
 Exact resource allocation: FFS
 PUCCH format 2 TxD
 Three major camps for PUCCH format 2 :
 No TxD, SORTD, STBC without slot hopping
 4 Tx PUCCH transmit diversity: 2Tx TxD is applied (UE implementation issue)
n_r=(n_cs, n_oc, n_PRB) for PUCCH format 1
n_r=(n_cs, n_PRB) for PUCCH format 2

Ant#0
d_0 (n)
Spreading with n_r0
.
d_0 (n)
Modulation symbol .
. Ant#M-1
d_0 (n)
Spreading with n_rM-1
 SU-MIMO
 Codebook based precoding
 Independent codebook design for different ranks
 Single wideband TPMI per UL component carrier
 Frequency non-selective precoding in a component carrier
 Codebook size
 2 Tx: 1-layer+2-layer ≤ 8 (3-bit codebook)
 4 Tx: 1-layer+2-layer+3-layer+4-layer ≤ 64 (6-bit codebook
 Dynamic rank adaptation
 Alphabet size: QPSK alphabet: {1, -1, j, -j}
 Further consideration point
 UL frequency selective precoding
 Impact on antenna gain imbalance (AGI) due to hand-gripping problem
 Antenna power amp (PA) configuration
 2 Tx antenna
 20dBm + 20dBm
 23dBm + 23dBm
 23dBm + x, where x ≤ 23dBm
 4 Tx antenna
 17dBm + 17dBm + 17dBm + 17dBm
 23dBm + 23dBm + 23dBm + 23dBm and
 23dBm + x + x + x where x ≤ 23dBm
 Precoder design for 2 Tx
 Precoder design for 4Tx
 Separate design of each rank
 No nested property
 Alphabet in codebook element: from {1, -1, j, -j}
 Antenna selection codebook elements in rank 1
 Cubic metric preserving (CMP) codebook in rank 2 and rank 3
 Identity precoding matrix in rank 4
 4Tx rank-1 codebook
 Size-24: 16 constant modulus + 8 antenna pair turn-off vectors
 Size-16:
CM-preserving matrices
 QPSK alphabet
 Size-12 CMP codebook
 BPSK alphabet
1 0 0 1 0 0 1 0 0 1 0 0
  0

1 1 0 0

1 − 1 0 0 1 0 1 0 10 1
Index 0 to 3
2 0 1 0 2 0 1 0 2 1 0 0 2 − 1 0 0
       
0 0 1 0 0 1 0 0 1 0 0 1
1 0 0 1 0 0 0 1 0 0 1 0
 0 

1 0 1 0 10 1 1 1 0 0 
11 0 0
Index 4 to 7
2 0 0 1 2 0 0 1 2 1 0 0 2 − 1 0 0
       
1 0 0 − 1 0 0 0 0 1 0 0 1
0 1 0 0 1 0 0 1 0 0 1 0
  1  1

1 1 0 0 11 0 0 1 0 0 10 0
Index 8 to 11
2 0 0 1 2 0 0 1 2 1 0 0 21 0 0
       
1 0 0 − 1 0 0 1 0 0 − 1 0 0

 Single identity matrix
 Number of MCS fields: 2
 Separate link adapation of two codewords
 Discussion on layer shifting
 Among the followings, alternative 2 was agreed
 Alt1: No HARQ-ACK Spatial Bundling and no layer shifting.
 Alt2: No layer shifting, and continue discussion on HARQ bundling.
 Alt 3: Layer shifting with HARQ bundling
UL-MIMO: Reference Signal [1]
 UL DM-RS in support of UL-MIMO
 Precoded UL DM-RS
 2Tx
 rank 1-rank 2: precoded RS
 4Tx
 rank 1-rank2, rank 4: precoded RS
 rank 3 : FFS, but potential agreement of precoded DM-RS in case of rank-3
 Same precoding for DM RS and PUSCH
 UL DM-RS multiplexing
 Cyclic shift (CS) separation for DM-RS multiplexing
 TBD: Orthogonal cover code (OCC) separation between slots for interference
suppression
 DM-RS sequence design for non-contiguous resource allocations
 Working assumption: Base sequence according to the whole allocation size and
split into clusters.
UL-MIMO: Reference Signal [2]
 UL sounding reference signal
 Re-use of Rel-8 principles (CS separation, IFDM separation) with some
possible modifications
 SRS configuration per CC in case of carrier aggregation
 Dynamic aperiodic SRS is supported
 Continue discussion on PDCCH signaling aspects,
 how to provide aperiodic SRS resources (including for multiple antennas), how
to share these resources with ones for periodic SRS, and for the duration of the
dynamic SRS transmission (e.g. one-shot, with a timer, semi-persistent until
disabled, etc.)
 Precoded SRS is not supported in Rel-10
 need for sounding via DMRS
 need for increased SRS multiplexing possibilities (if so, which methods)
 need for multi-cell coordination / randomisation (which methods if any)
 need for SRS coverage enhancement
 need for non-contiguous SRS transmission
CoMP
 Overview
 Carrier Types
 MAC-PHY interface
 Uplink Multiple Access
 Uplink Control Channel
 Downlink Control Channel
 UL Power control
Terminology and Definition – CoMP Set
 CoMP Cooperating Set
 Set of (geographically separated) points directly or indirectly participating
in PDSCH transmission to UE.
 COMP transmission point(s)
 Point or set of points actively transmitting PDSCH to UE
 CoMP transmission point(s) is a subset of the CoMP cooperating set
 For Joint transmission, the points in the CoMP cooperating set
 For Dynamic cell selection, a single point is the transmission point at every
subframe. This transmission point can change dynamically within the CoMP
cooperating set.
 For Coordinated scheduling/beamforming, the “serving cell”
 Transparent/non-transparent to UE
 CoMP measurement set
 Set of cells about which channel state/statistical information related to their
link to the UE is reported
 May be the same as the CoMP cooperating set
 The actual UE reports may down-select cells for which actual feedback
information is transmitted (reported cells)
CoMP Category
 Joint Processing
 Data is available at each point in CoMP cooperating set
 Joint Transmission
 Dynamic Cell Selection
 Coordinated Scheduling/Beamforming (CS/CB)
 Joint Transmission
 Data to a single UE is available at multiple transmission points
 PDSCH transmission from multiple points (part of or entire CoMP cooperating set) at a time
 Coherently or non-coherently
 To improve the received signal quality and/or cancel actively interference for other UEs
 Dynamic Cell Selection
 CoMP transmission point from a single point
 Can change dynamically within the CoMP cooperating set.
 Cooperative Scheduling/ Beamforming (CS/CB)
 User scheduling/beamforming decisions are made with coordination among the CoMP
cooperating set.
 CoMP transmission point : serving cell
CoMP Operation- Joint Transmission
CoMP Operation– CS/CB
참고) R1-092232, “Summary of email discussion for CoMP” Qualcomm
Joint Processing:
Transparent vs. Non-transparent
 Transparent to UE
 DL joint transmission is based on the dedicated reference signals (DRS)
for demodulation
 UEs need not know which eNBs participate in transmission
 Easy to implement and minimal spec change
 May cause performance degradation due to CRS and PDSCH collision
 RE collision may be resolved by alignment among CoMP transmission

points
 Non-transparent to UE
 CRS and PDSCH RE mapping collision among transmission points
 Enable resource mapping optimization
 Increase overhead for DL control channels
 Transmission Points : semi-statically (or dynamically) configured
Joint processing:
Coherent vs. Non-coherent
 In terms of manner of the combination of signal from multiple
cells at UE
 Coherent transmission
 Non-coherent transmission
 Coherent transmission
 UE could combine transmitted signal coherently
 Network obtains channel state information of all the cooperating cell sites
 Phase correction + precoding
 Phase factor obtained from feedback or calculated at network side
 The transmitted signal from each cell is multiplied by a distinct phase

factor
 Global precoding
 Non-coherent transmission
 Signal arriving at UE is unable to combine coherently
Precoding Codebook for CoMP
 Global precoding (joint design)
 A single super-cell codebook is designed considering multiple points.
 A codebook needs to be designed for each combinations
 Number of cooperating points
 Number of transmit antennas
 Number of layers
 The performance is upper bound of all precoding schemes for CoMP
 High Complexity
 Large global codebook to quantize
 Codebook varies with the size of CoMP cells
 Local precoding (disjoint design)
 A single super-cell codebook is composed by the N(number of cooperating
points) single-cell codebook
 Local precoding design is simpler
 The performance is worse than that of global precoding
Cell Clustering for CoMP
 UE-specific Clustering
 Cluster of coordinated cells chosen based on the preference of the UE
 Largest throughput gain
 Scheduling among all eNBs in the system needed
 Excessive Backhaul overhead
 Fixed Clustering
 Simple in terms of implementation
 Throughput gain obtained is limited
 Hybrid UE-specific clustering – UE specific with Network

assistance
 Cluster of eNB serving a particular UE is a subset of a larger fixed cluster
 Throughput gain
 Reduce scheduling complexity and backhaul demand
 Semi-statically (or dynamically) configured
Feedback in Support of DL CoMP
 CoMP Feedback mechanisms
 Explicit channel state/statistical information feedback
 Channel as observed by the receiver, without assuming any
transmission or receiver processing
 Implicit channel state/statistical information feedback
 Use hypotheses of different transmission and/or reception processing,
e.g., CQI/PMI/RI
 Channel reciprocity
 UE transmission of SRS can be used for CSI estimation at eNB
 UE CoMP feedback reports target the serving cell

 on UL resources from serving cell
Explicit Feedback
 Channel part
 For each cell in the UE’s measurement set that is reported in a
given subframe, one or several channel properties are reported
 Channel properties include (but are not limited to) the following
 Channel matrix – short term (instantaneous)
 Transmit channel covariance
 Inter-cell channel properties may also be reported
 Noise-and interference part

 Interference outside the
 Cells reported by the UE
 CoMP transmission points
 Total
receive power (Io) or total received signal covariance matrix
 Covariance matrix of the noise-and-interference
Implicit Feedback
 Hypotheses at the UE and the feedback
 based on one or a combination of two or more of the following, e.g.:
 Single user vs. Multi user MIMO
 Single cell vs. Coordinated transmission
 Within coordinated transmission : Single point (CB/CS) vs. multi-point (JP)
transmission
 Within Joint processing CoMP
 Subsets of transmission points or subsets of reported cells (Joint Transmission)
 CoMP transmission point(s) (Dynamic Cell Selection)
 Transmit precoder (i.e. tx weights)
 JP : multiple single-cell or multi-cell PMI capturing
 CB/CS : single-cell or multiple single-cell PMIs
 Other types of feedbacks, e.g. main Multi-cell eigen-component, instead of
PMIs are being considered
 Receive processing (i.e. rx weights)
 Interference based on particular tx/rx processing
Reference [1]
[1] ITU-R, Revision 1 to Document IMT-ADV/2-E, “Submission and
evaluation process and consensus building”
[2] 3GPP, RP-08099, “Proposed schedule for the submission of LTE-
Advanced to ITU-R as a candidate for IMT-Advanced”, AT&T et. Al
[3] ITU-R, Addendum 2 to circular letter 5/LCCE/2
[4] ITU-R, Report ITU-R M.2133 “Requirements, evaluation criteria, and
submission templates for the development of IMT-Advanced”
[5] ITU-R, Report ITU-R M.2134 “Requirements related to technical
system performance for IMT-Advanced Radio interface(s)”
[6] ITU-R, Report ITU-R M.2135 “Guidelines for evaluation of radio
interface technologies for IMT-Advanced”
[7] 3GPP, RP-091000, Release 10 time plan
[8] ITU-R WP5D/291, Initial 3GPP submission of a candidate IMT-
Advanced technology
[9] ITU-R WP5D/496, AN INITIAL TECHNOLOGY SUBMISSION OF
3GPP LTE RELEASE 10
Reference [2]
[10] 3GPP, RP-090743, TR TR36.912 v9.0.0, Feasibility study for Further
Advancements for E-UTRA, September 2009
[11] 3GPP, RP-090745, Annex C1: Characteristics template
[12] 3GPP, RP-090746, Annex C2: Link budget template
[13] 3GPP, RP-090747, Annex C3: Compliance template
[14] 3GPP, RP-090744, Annex A3: Self-evaluation results
[15] ITU-R, WP5D/564-E, COMPLETE SUBMISSION OF 3GPP LTE
RELEASE 10 & BEYOND (LTE-ADVANCED) UNDER STEP 3 OF
THE IMT-ADVANCED PROCESS
[16] 3GPP, TR 36.913, “Requirements for further advancements for E-
UTRA (LTE-Advanced)”, V8.0.0, June 2008
[17] 3GPP, RP-091005, Proposal for Candidate Radio Interface
Technologies for IMT-Advanced Based on LTE Release 10 and
Beyond
[18] 3GPP, RP-100357, TR36.814, “Further Advancements for E-UTRA
Physical Layer Aspects (Release 9)”, V2.0.1, March 2010
Thanks !!

Lte A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lte A

Uploaded by

Copyright:

Available Formats

LTE-Advanced 주요 표준 동향 및 기술

Release 4 1.28Mcps TDD

Release 5 HSDPA, IMS

Release 6 HSUPA, MBMS, IMS+

Release 7 HSPA+ (MIMO, HOM etc.)

Release 9 Small LTE/SAE

LTE-Advanced 주요 표준 동향 및 요소 기술 Release 10 LTE-Advanced

3/08 6/08 9/08 12/08 3/09 5/09 9/09 12/09 3/10

ITU-R 3/08 6/08 10/08 3/08 to 10/09 10/09

Standard Roadmap 2009 2010 2011 2012

#46 #47 #48 #49 #50 #51 #52

Core spec ASN.1

requirements and time plan

Bandwidth 40MHz (scalable BW) Up to 100MHz

User plane latency 10ms Improved compared to LTE

Active  Active dormant(<10ms)

ITU system performance requirement

LTE LTE-ADV LTE LTE-ADV

New for IMT in some

1710 2025 2110 2690

IMT bands can be used by all IMT-2000 and IMT-Advanced technologies

 Many (18) companies perticipated in the simulations, ensuring high reliability

Rel-8 4 layer spatial multiplexing 16.3 16.0

8 layer spatial multiplexing 30.6 30.0

 UL peak spectrum efficiency

ITU requirement 6.75 6.75

2 layer spatial multiplexing 8.4 8.1

4 layer spatial multiplexing 16.8 16.1

ITU Number Cell average Cell edge

 Indoor Hotspot / downlink / TDD

 Indoor Hotspot / uplink / TDD

 Urban Micro/downlink/TDD: single cell MU-MIMO (4x2) meets the requirement

Rel-8 SIMO 1X4 (C) 1.8 / 0.05 13 1.9 0.072

Rel-8 MU-MIMO 1X4 (A) 1.8 / 0.05 2 2.5 0.077

MU-MIMO 2X4 (A) 1.8 / 0.05 1 2.5 0.086

 Urban Micro / uplink / TDD: LTE Rel-8 meets the requirement

ITU requirement Number of

Rel-8 SIMO 1X4 (C) 1.8 / 0.05 9 1.9 0.070

Rel-8 MU-MIMO 1X4 (A) 1.8 / 0.05 2 2.3 0.071

MU-MIMO 2X4 (A) 1.8 / 0.05 1 2.8 0.068

MU-MIMO 1X8 (E) 1.8 / 0.05 1 3.0 0.079

ITU Number Cell average Cell edge

ITU Number Cell average Cell edge

Rel-8 SIMO 1X4 (C) 1.4 / 0.03 12 1.5 0.062

CoMP 1X4 (A) 1.4 / 0.03 2 1.7 0.086

CoMP 2X4 (C) 1.4 / 0.03 1 2.1 0.099

 Urban Macro / uplink / TDD

 Rural Macro / downlink / TDD: LTE Rel-8 meets the requirement

Rel-8 SIMO 1X4 (C) 0.7 / 0.015 11 1.8 0.082

Rel-8 MU-MIMO 1X4 (A) 0.7 / 0.015 2 2.2 0.097

CoMP 2X4 (A) 0.7 / 0.015 2 2.3 0.13

 Rural Macro / uplink / TDD: LTE Rel-8 meets the requirement

Rel-8 SIMO 1X4 (C) 0.7 / 0.015 8 1.8 0.080

Rel-8 MU-MIMO 1X4 (A) 0.7 / 0.015 2 2.1 0.093

CoMP 2X4 (A) 0.7 / 0.015 1 2.5 0.15

MU-MIMO 1X8 (E) 0.7 / 0.015 1 2.6 0.10

Indoor Hotspot 50 3 140 2 137

Indoor Hotspot 50 3 131 3 130

Indoor Hotspot 1.0 13.89 7 2.56 4 2.63

Urban Micro 0.75 4.54 7 1.21 4 1.14

Rural Macro 0.25 5.42 7 1.22 4 1.03

Indoor Hotspot 1.0 13.89 4 3.15 2 3.11

Urban Micro 0.75 4.54 4 1.42 2 1.48