lte-advanced overview

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

윤영우

[email protected] 전자

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

Contents

Generals on LTE-Advanced Overview of LTE-Advanced Technologies More details on LTE-Advanced Component

Technologies

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

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

3GPP specification releases

1999 2000 2001 2002 2003 2004 2005

Release 99

Release 4

Release 5

Release 6

1.28Mcps TDD

HSDPA, IMS

W-CDMA

HSUPA, MBMS, IMS+

2006 2007 2008 2009

Release 7 HSPA+ (MIMO, HOM etc.)

Release 8

2010 2011

LTE, SAEITU-R M.1457

IMT-2000 Recommendations

Release 9

LTE-AdvancedRelease 10

GSM/GPRS/EDGE enhancements

Small LTE/SAE enhancements

Cited from 3GPP, RP-091005, Proposal for Candidate Radio Interface Technologies for IMT-Advanced Based on LTE Release 10 and Beyond

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

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

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

LTE-Advanced SI Approved

3GPP LTE-Advanced

Early Submission to

ITU-R

Steps 1 & 2Circular Letter & Development of Candidate RITs

3/08 to 10/09

IMT-AdvancedEvaluation Group(s) Formed

(notify ITU-R)

3GPP

Initiate 3GPP LTE-Advanced

Self-Evaluation

3GPP LTE-Advanced Final Submission to

ITU-R including Updated Technical

Submission & Required Self-

Evaluation

LTE-Advanced Specifications

3GPP LTE-Advanced Complete Technical

Submission to ITU-R

Step 3Submission3/09 to 10/09

Step 4Evaluations1/09 to 6/10

3/08 6/08

10/09

10/09

6/103/09

ITU-R

Detailed Timelines for ITU-R Steps 1- 4

3/09

LTE-Advanced Specifications

to ITU-R~ Jan 2011

Evaluation of ITU-R

Submissions

EvalReports

ITU-R Circular Letter 5/LCCE/2

Process & Timelines

ITU-R Circular Letter Addendum

5/LCCE/2 + Requirements& Submission

Templates Cutoff for Evaluation Reports

to ITU-RJune 2010

INDUSTRY

RAN #41 RAN #42 RAN #43RAN #39 RAN #44RAN #40 RAN #45

WP 5D #1 WP 5D #2

WP 5D #4

WP 5D #8

WP 5D #6

WP 5D #4 WP 5D #6

RAN #47RAN #46

[~Release 10 ][~RAN #50 12/10]

6/09WP 5D #5

10/08WP 5D #3

5 Source: RP-080651

ITU-REvaluation

Criteria

3GPP work on ITU-R Step 2Technology Development

3GPP work on ITU-R Step 3Technology Submission

3GPP Q&A with evaluation

groups (as required)


IMT-Advanced Process

Steps in radio interface development process:

Step1 and 2

No.1 No.2 No.3 No.4 No.5 No.6 No.7 No.8 No.9

Step 3(0)

(1)

(20 months)

Step 4(8 months)

(16 months) (2)Steps 5,6 and 7

(3)Steps 8

(4)(12 months)

(20 months)

WP 5D meetings

Step 1: Issuance of the circular letterStep 2: Development of candidate RITs and SRITsStep 3: Submission/Reception of the RIT and SRIT proposals

and acknowledgement of receiptStep 4: Evaluation of candidate RITs and SRITs

by evaluation groups

Step 5: Review and coordination of outside evaluation activitiesStep 6: Review to assess compliance with minimum requirementsStep 7: Consideration of evaluation results, consensus building

and decision Step 8: Development of radio interface Recommendation(s)

Critical milestones in radio interface development process:(0): Issue an invitation to propose RITs March 2008(1): ITU proposed cut off for submission October 2009

of candidate RIT and SRIT proposals

(2): Cut off for evaluation report to ITU June 2010(3): WP 5D decides framework and key October 2010

characteristics of IMT-Advanced RITs and SRITs(4): WP 5D completes development of radio February 2011

interface specification Recommendations

2008 2009 2010No.10

2011

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

ITU-R WP5DProposals

EvaluationConsensus

Specification

LTE Rel.9 LTE Rel.10 [LTE Rel.11]LTE-A SI

2009 2010 2011Complete Tech

Final Submission

Standard Roadmap

3GPPLTE-A LTE-A Functional Work Items

[LTE Rel.12]

2012

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 Functional

freezeIn RAN1

RAN1 has to complete their specification by Sept. 10 (only 9 month)

RAN2/3/4 have to complete their specification by Dec. 10 (only 12 month) reflectingRAN1 agreements

Core specFunctional

freeze

ASN.1freeze


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

Contents1. Scope2. References3. Definitions, symbols and abbreviations4. Introduction5. Support of wider bandwidth6. Uplink transmission scheme7. Downlink transmission scheme8. CoMP9. Relaying10. Improvement for latency11. Radio transmission and reception12. Mobility enhancements13. TS 36.133 requirements enhancements14. MBMS enhancements15. SON enhancements16. 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 planExtended LTE-Advanced targets are adopted

Syst

em

Perf

orm

ance IMT-Advanced

requirements and time plan

Rel. 8 LTE

LTE-Advancedtargets

Time

Cited from 3GPP, RP-091005, Proposal for Candidate Radio Interface Technologies for IMT-Advanced Based on LTE Release 10 and Beyond


Requirements for LTE-Advanced [2] Comparison between IMT-Advanced and LTE-Advanced

LTE-Advanced should at least fulfill or exceed IMT-Advanced requirements

ITU Requirement 3GPP Requirement

Peak data rates1Gbps in DL

500Mbps in UL

Bandwidth 40MHz (scalable BW) Up to 100MHz

User plane latency 10ms Improved compared to LTE

Control plane latency 100msActive Active dormant(<10ms)

Camped Active (<50ms)

Peak spectrum efficiency15bps/Hz in DL

6.75bps/Hz in UL

30bps/Hz in DL

15bps/Hz in UL

Average spectrum efficiency Set for four scenarios and several antenna configurations

See next slide for case 1 requirementCell edge spectrum effciency

VoIP capacity Up to200 UEs per 5MHz Improved compared to LTE


Requirements for LTE-Advanced [3]

System performance requirements for IMT-Advanced

ITU system performance requirement

Enviromnet Indoor Micro-cellBase

coverage Urban

Rural/

High speed

Spectrum

Efficiency

DL(4x2 MIMO)

3 2.6 2.2 1.1

UL(2x4 MIMO)

2.25 1.8 1.4 0.7

Cell Edge

Spectrum

Efficiency

DL(4x2 MIMO)

0.1 0.075 0.06 0.04

UL(2x4 MIMO)

0.07 0.05 0.03 0.015


Requirements for LTE-Advanced [4] 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?

Case-1

Ant. Config

LTE

Cell Avg. SE[bps/Hz/cell]

(3GPP R1-072580)

LTE-ADV

Cell Avg. SE[bps/Hz/cell]

(3GPP TR36.913)

LTE

Cell Edge SE[bps/Hz/user]

(3GPP R1-072580)

LTE-ADV

Cell Edge SE[bps/Hz/user]

(3GPP TR36.913)

UL1x2 0.735 1.2 0.024 0.04

2x4 - 2.0 - 0.07

DL

2x2 1.69 2.4 0.05 0.07

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

3300 3400 3500 3600 3700 3800 3900 4000 4100 4200 4300 4400 4500 4600 4700 4800 4900 5000

1300 1400 1500 1600 1700 1800 1900 2000 2100 2200 2300 2400 2500 2600 2700 2800 2900

2025 21102170 26901710

100 500 600 700 800 900 1000200 300 400

5150 470 890915925960

806450 790698

New for IMT in some countries of

Regions 1 & 3

NewRegion 2

NewGlobal

ExistingIMT

identified

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

UL peak spectrum efficiency

SchemeFDD spectral efficiency

(bps/Hz)TDD spectral efficiency

(bps/Hz)

ITU requirement 15 15

Rel-8 4 layer spatial multiplexing 16.3 16.0

8 layer spatial multiplexing 30.6 30.0

SchemeFDD spectral efficiency

(bps/Hz)TDD spectral efficiency

(bps/Hz)

ITU requirement 6.75 6.75




Self-Evaluation Results [2] Indoor Hotspot / downlink / FDD

LTE Rel-8 meets the requirement

Indoor Hotspot / downlink / TDD LTE Rel-8 meets the requirement

Scheme and antenna conf.

ITUrequirement(Ave./Edge)

Numberof

samples

Cell average Cell edge

L=1 L=2 L=3 L=1 L=2 L=3

Rel-8 SU-MIMO4X2 (A) 3 / 0.1 15 4.8 4.5 4.1 0.23 0.21 0.19

MU-MIMO4X2 (C) 3 / 0.1 3 6.6 6.1 5.5 0.26 0.24 0.22



Numberof

samples


L=1 L=2 L=3 L=1 L=2 L=3

Rel-8 SU-MIMO4X2 (A) 3 / 0.1 10 4.7 4.4 4.1 0.22 0.20 0.19

MU-MIMO4X2 (C) 3 / 0.1 4 6.5 6.1 5.7 0.23 0.22 0.20


Self-Evaluation Results [3] Indoor Hotspot / uplink / FDD

LTE Rel-8 meets the requirement

Indoor Hotspot / uplink / TDD LTE Rel-8 meets the requirement

Scheme and antenna conf.ITU requirement

(Ave./Edge)Number of

samplesCell average Cell edge

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




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


Self-Evaluation Results [4] Urban Micro/downlink/FDD:Single cell MU-MIMO meets the requirement

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



Numberof

samples


L=1 L=2 L=3 L=1 L=2 L=3

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



Numberof

samples


L=1 L=2 L=3 L=1 L=2 L=3

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


Self-Evaluation Results [5]

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

Urban Micro / uplink / TDD: LTE Rel-8 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




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


Self-Evaluation Results [6] Urban Macro / downlink / FDD: Single cell MU-MIMO (4x2) meets the requirement

Urban Macro / downlink / TDD: Single cell MU-MIMO (4x2) meets the requirement



Numberof

samples


L=1 L=2 L=3 L=1 L=2 L=3

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

Scheme and antenna conf.ITU

requirement(Ave./Edge)

Numberof

samples


L=1 L=2 L=3 L=1 L=2 L=3

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 LTE Rel-8 meets the requirement

Urban Macro / uplink / TDD LTE Rel-8 meets the requirement




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




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


Self-Evaluation Results [8] Rural Macro / downlink / FDD: LTE Rel-8 meets the requirement

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



Numberof

samples


L=1 L=2 L=3 L=1 L=2 L=3

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



Numberof

samples


L=1 L=2 L=3 L=1 L=2 L=3

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

Rural Macro / uplink / 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




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

Antenna conf.

ScenariosITU

requirement

FDD TDD

Number ofsamples

Capacity(user/MHz/cell)

Number ofsamples

Capacity(user/MHz/cell)

(A)

Indoor Hotspot 50 3 140 2 137

Urban Micro 40 3 80 2 74

Urban Macro 40 3 68 2 65

Rural Macro 30 3 91 2 86

(C)

Indoor Hotspot 50 3 131 3 130

Urban Micro 40 3 75 3 74

Urban Macro 40 3 69 3 67

Rural Macro 30 3 94 3 92


Self-Evaluation Results [11] Mobility Traffic Channel Link Data Rates

Rel-8 LTE can meet all the requirements

LOS/NLOS

ScenariosITU

requirement

MedianSINR(dB)

FDD TDD

Number ofsamples

UL spectrumefficiency (bps/Hz)

Number ofsamples

UL spectrumefficiency (bps/Hz)

Antenna conf.1X4, NLOS

Indoor Hotspot 1.0 13.89 7 2.56 4 2.63

Urban Micro 0.75 4.54 7 1.21 4 1.14

Urban Macro 0.55 4.30 7 1.08 4 0.95

Rural Macro 0.25 5.42 7 1.22 4 1.03

Antenna conf.1X4, LOS

Indoor Hotspot 1.0 13.89 4 3.15 2 3.11

Urban Micro 0.75 4.54 4 1.42 2 1.48

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-AdvancedSpectrum Aggregation Advanced MIMO

High-order MIMO

Enhanced DL/UL MU-MIMO

UL SU-MIMO

FFR & Power Control

A

A

A

Frequency

Power Spectral Density

B

B

C

C

D

D

D

Reuse 1 Reuse 1/3

B C

Sector 1

Sector 2

Sector 3

UL Hybrid Multiple Access

Cluster

IFFTP/S

Modulationsymbols

Time DomainsignalS/P

DFT

: mapping to a RB


Emerging Technologies for LTE-AdvacedMultihop Transmission (Relay) Multi-cell Cooperation (Collaborative MIMO)

Self Organizing Network (SON) Heterogeneous Cell Overlay

Pico eNB

Femto eNB

Relay eNB

Macro eNB

X2

Internet

Mobile Core

Network

Femto-cell Controller


LTE-Advanced Improvements

A schematic view on LTE-Advanced improvements

LTE-Advanced

LTE

Higher OrderMIMO

SpectrumAggregation

CoMP

CoMP

Coverage ExtensionHeNB/Relay

eNodeB

Data rate

SON

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

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

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

Case 1: Contiguous BW aggregation Aggregated allocation of contiguous

carrier BWs Need of further clarification for

feasibility of contiguous BW allocation up to 100MHz

Case 2: Non-contiguous BW aggregation Aggregated allocation of separated carrier

BWs Need of further clarification for spectrum

range of BW aggregation


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 Restricted flexibility due to “single-

carrier property” in scheduling and control channel design

However, low PAPR/CM of SC-FDMA at power-limited situation is still very important

Uplink Hybrid Multiple Access of Clustered SC-FDMA and SC-FDMA Clustered SC-FDMA transmission

for more flexible scheduling Non-contiguous resource allocation

should also be supported for PUSCH transmission from UE with 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

IFFTP/S

Time-domainsignal

: mapping to a RB

IFFTP/S

IFFTP/S

S/PRE

mapping

S/PRE

mapping

Time-domainsignal

Time-domainsignal

ModulationSymbols

for TrBlk B

ModulationSymbols

for TrBlk C

DFT

S/PRE

mappingDFT

DFT

ModulationSymbols

for TrBlk AClustered-

DFTsOFDM

Clustered-DFTsOFDM

Clustered-DFTsOFDM


Relay [1] Several types of data transmission between eNB and

UEUE Relaying

• Direct inter-UE connectivity• Autonomous ad-hoc network configuration and management• Support of emergency call status

Relay Node Tx/Rx

• Remote relay node Tx/Rx• Coverage extension and throughput enhancement

Conventional UE-eNB Tx/Rx

• Conventional single-hop Tx/Rx between UE and eNB as a basic connection scheme

Wireless link connectioneNB

Relay Node

Relay Node

Out of focus in LTE-Advanced study

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 TypesMAC-PHY interface Uplink Multiple Access Uplink Control Channel Downlink Control Channel UL Power control

LTE-Advanced 주요표준동향및요소기술LTE/MIMO 표준기술 46

Overview [1]

Carrier aggregationSupport wider bandwidth Two or more component carriersUp to 100MHz and for spectrum aggregationEach component carrier limited to a maximum of 110 RBsUsing Rel’8 numerology

Carrier aggregation typeContiguousNon-contiguous


Overview [2] Concept of carrier aggregation

Contiguous component carrier

Non-contiguous component carrier

Frequency

LTE bandwidth

Frequency

Aggregated bandwidth


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

E-UTRA CA

Band

E-UTRA operating

Band

Uplink (UL) band Downlink (DL) bandDuple

xmode

UE transmit / BS receiveChannel BW MHz

UE receive / BS transmitChannel BW MHzFUL_low (MHz) – FUL_high (MHz)

FDL_low (MHz) – FDL_high(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

TBD bandwidth will be finally decided after having RAN4 discussion

E-UTRA CA

Band

E-UTRA operating

Band

Uplink (UL) band Downlink (DL) bandDuple

xmode

UE transmit / BS receiveChannel BW MHz

UE receive / BS transmitChannel BW MHzFUL_low (MHz) – FUL_high (MHz)

FDL_low (MHz) – FDL_high(MHz)

CA_1-51 1920 – 1980 [TBD] 2110 – 2170 [TBD]

FDD5 824 – 849 [TBD] 869 – 894 [TBD]


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)

Frequency

System bandwidth, e.g., 100 MHz

CC, e.g., 20 MHz

UE capabilities• 100-MHz case

• 40-MHz case

• 20-MHz case (Rel. 8 LTE)


Carrier Types

Backward compatible carrierA carrier accessible to UEs of all existing LTE releasesCan 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 carrierA carrier not accessible to UEs of earlier LTE releasesCan be operated as a single carrier (stand-alone) from the duplex

distanceOtherwise, 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.

Channel coding

Modulation

RB mapping

Component carrier 1 Component carrier 2

20MHz 20MHz

transport block

Channel coding

Modulation

RB mapping

transport block

One UE


Uplink Multiple Access SC-FDMA for PUSCH

One DFT per component carrierSupported for spatial multiplexing

Resource allocation Frequency-contiguous Frequency-non-contiguous

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

IFFTP/S

Time-domainsignal

: mapping to a RB

IFFTP/S

IFFTP/S

S/PRE

mapping

S/PRE

mapping

Time-domainsignal

Time-domainsignal

ModulationSymbols

for TrBlk B

ModulationSymbols

for TrBlk C

DFT

S/PRE

mappingDFT

DFT

ModulationSymbols

for TrBlk AClustered-

DFTsOFDM

Clustered-DFTsOFDM

Clustered-DFTsOFDM


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


Uplink Control ChannelOne SR per UE transmitted on PUCCH

Semi-statically mapped onto one UE specific UL CCPeriodic 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


Uplink Control Channel 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

PDSCH

PDSCH

PDSCH

PUCCH

PUCCH

PUCCH

PUCCH

PUCCH

PUCCHA/N A/N A/N

PDSCH

PDSCH

PDSCH

PUCCH

PUCCH

A/N A/N A/N

Bundling

PDSCH

PDSCH

PDSCH

PUCCH

PUCCHA/N A/N A/N Joint coding

Multiple resources transmission Bundling Joint coding


Uplink Control Channel CQI (Channel Quality Indication)

Multiple CQIs on single component carrier Multiple resources transmission Joint coding TDM

PUCCH

PUCCH

PUCCH

PUCCH

PUCCH

PUCCHCQI CQI CQI

DL CC #0 DL CC #1 DL CC #2DL CC #0 DL CC #1 DL CC #2

PUCCH

PUCCH

CQI CQI CQI

Joint coding

Multiple resources transmissionJoint codingPU

CCH

PUCCH

PUCCH

PUCCH

PUCCH

PUCCH

CQI CQI CQI

DL CC #0 DL CC #1 DL CC #2subfram

e #nsubfram

e #n+1subfram

e #n+2

Time

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

Receive PDSCH Not receive PDSCH Receive PDSCH

PDSCH error due to CFI error, also leads to

HARQ buffer corruption.

PDCCH correctCFI correct

PDCCH DTXCFI error

PDCCH correct

CFI correct CFI errorPDCCH correct

Linked Carrier Scheduling Cross Carrier Scheduling

CC#1 CC#2 CC#1 CC#2


Downlink Control Channel 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


Downlink Control Channel 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?


Downlink Control Channel

PCFICH Independent control region size per CCOn 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 ControlPHR

Per CC FFS whether or not PHR is per channel (i.e. PUSCH / PUCCH) within

each per-CC PHRMax 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 nodeAt least part of the RRM is controlled by the eNB to which the

donor cell belongs It can transmit PDSCHAt 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

No TX

UL RX

Relay UL TX

Relay UL RX

UL TXR-UE UL TX

subframe

UL TX

No RX

e.g. blocked subframe

UL RXeNB UL RX


Access-Backhaul Partitioning

Illustration

eNB

RN

UE2

DL (F1)

DL (F1)UL (F2)

UE1

DL (F1)UL (F2)

F1F2

UL (F2)

F1: DL frequency (FDD)F2: UL frequency (FDD)

One link active at a timeOne link active at a time


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

DataCtrl transmission gap(“MBSFN subframe”)Ctrl

One subframe

No relay-to-UE transmission

eNB-to-relay 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 mand 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.


Backhaul Link Timing: DL [2]

Case 1: DL (-) timing offsetA 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 timingRN should 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

Further discussion point 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 offsetNot 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]

CharacteristicsUE 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 layersRSs on different layers are mutually orthogonalRS 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 layersDM-RS pattern agreed for Rel-9 dual layer beamforming

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

Normal subframe DwPTS (symbols >= 11) DwPTS (symbols<11)


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 OFDM symbols



DL-RS: DM-RS [4] DM-RS pattern for rank5~8

Hybrid CDM+FDM DMRS patterns are adopted for rank 5-8 transmissionwith 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

Multiple RB optimization Followings are FFS

DM-RS pattern optimization according to the number of RBs allocated Precoding granularity indication

Normal subframe DwPTS with 11,12 OFDM symbols



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-10CSI 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


DL-MIMO in LTE-Advanced 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 SchemeRel-8 TxD 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


DL-MIMO in LTE-Advanced 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 Implementation flexibility: various algorithmsOne 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


UL-MIMO: Multi-Antenna Support [2] 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


UL-MIMO: Multi-Antenna Support [3] 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)

Modulation symbol

Spreading with n_r0

Spreading with n_rM-1

n_r=(n_cs, n_oc, n_PRB) for PUCCH format 1

n_r=(n_cs, n_PRB) for PUCCH format 2Ant#0

Ant#M-1d_0 (n)

d_0 (n)

d_0 (n)

.

.

.


UL-MIMO: Multi-Antenna Support [4] 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 4TxSeparate design of each rankNo nested propertyAlphabet in codebook element: from {1, -1, j, -j}Antenna selection codebook elements in rank 1Cubic metric preserving (CMP) codebook in rank 2 and rank 3 Identity precoding matrix in rank 4



4Tx rank-1 codebookSize-24: 16 constant modulus + 8 antenna pair turn-off vectors



4Tx rank-2 codebookSize-16: CM-preserving matricesQPSK alphabet


UL-MIMO: Multi-Antenna Support [9] 4Tx rank-3 codebook

Size-12 CMP codebook BPSK alphabet

4Tx rank-4 codebook Single identity matrix

Index 0 to 3

Index 4 to 7

Index 8 to 11

100010001001

21

−

100010001001

21

100001010001

21

−100001010001

21

001100010001

21

− 001100010001

21

100001001010

21

−100001001010

21

001100001010

21

− 001100001010

21

001001100010

21

− 001001100010

21


UL-MIMO: Multi-Antenna Support [10] 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 Further discussion point

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 TypesMAC-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) Data is only available at serving cell

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


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 mechanismsExplicit 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/RIChannel 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 matrixCovariance 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 !!