3GPP TSG RAN WG1 #60bis

3GPP TSG RAN WG1 #60bis 99 04 11 99 04 17 99 04 20

3GPP RAN1 Meeting #60bis Huawei 2010 4 12 4 16 5 RAN1 RAN2#69bis 2 RAN1#60bis LTE/LTE-A R1-102286 ( HTC ) 1. RAN1 Release 10 Release 8 compatible carriers 2. RAN1 later release(s) (e.g. Release 11) extension carrier carrier segment LTE Release 8/9 Stage 3 RAN1 (PHY Layer) essential corrections LTE Release 8/9 LTE Release 8/9 CR (Change Request CR) 3 LTE-A (Study Item SI) 3 LTE-A (Work Item WI) 3GPP 2010 Q2 (i.e. Release 10) LTE-A Release 10 LTE-A Carrier DL/UL MIMO Relay (WI) Enhanced ICIC for non-ca based deployments of heterogeneous networks for LTE ICI (inter-cell interference) LTE 2

... 2... 4... 4... 4... 4 ( )... 4 3

3GPP TSG RAN1 #60bis Meeting LTE-A CoMP MIMO Bandwidth aggregation Dual Layer Beamforming 3GPP LTE/LTE-A 3GPP LTE/LTE-A ( (CHTTL)) (RAN1 RAN2) April 12, 2010 ~ April 16, 2010 China World Hotel, Beijing, China ( ) RAN1 4

5

RAN1 Meeting Huawei RAN1#60bis RAN2#69bis 3GPP RAN1 #60bis 350 70~80 / 15 / 7 UTRA (WCDMA/HSPA) 4 Agenda Item 5.2: 4-carrier HSDPA Agenda Item 5.3: LCR TDD MC-HSUPA Agenda Item 5.4: MU-MIMO FOR 1.28MCPS TDD Agenda Item 5.5: Study on UL Transmit Diversity Agenda Item 5.6: Study on Energy Saving for UMTS Agenda Item 5.7: Study on Improvements for Distributed Antennas for 1.28Mcps TDD E-UTRA (LTE/LTE-A) 7 Agenda Item 6.2: Carrier Agenda Item 6.3: Enhanced Downlink Multiple Antenna Transmission Agenda Item 6.4: UL Multiple Antenna Transmission Agenda Item 6.5: UL RS Issues Relevant to LTE-A Work Items Agenda Item 6.6: Relaying Agenda Item 6.7: Network-Based Positioning Support for LTE Agenda Item 6.8: Enhanced ICIC for Non-CA Based Deployments of Heterogeneous Network for LTE LTE-A SI (Study Item) 3 LTE-A WI (Work Item) 3GPP 2010 Q2 (i.e. Release 10) LTE-A WI Enhanced ICIC for Non-CA Based Deployments of Heterogeneous Network for LTE RAN Plenary#47 (2010/03) RAN1 Leading Group 3GPP RAN Plenary #49 (2010/09) WI PHY & MIMO 6

PHY MIMO PCFICH E-mail discussion Email R1-101878 Summary of email discussion on PCFICH Nokia, CC PCFICH : Alt 1: - In case of cross-carrier scheduling, the UE shall always follow the newly-standardized solution for ascertaining the PDSCH starting position on the CC carrying the PDSCH. Alt 2: - In case of cross-carrier scheduling, the UE shall follow the newly-standardized solution if it is used for ascertaining the PDSCH starting position on the CC carrying the PDSCH; if the newly-standardized solution is not used, the UE shall read the PCFICH on the CC carrying the PDSCH. : - CC PDSCH PDSCH CFI - PDSCH CC RRC Rel-8 CFI, PDSCH CC PDCCH CC CFI. Linkage between PDSCH/PUSCH and PDCCH E-mail discussion Email R1-101726 Summary from email discussion on the linkage between PDSCH/PUSCH and PDCCH linkage Option 1: PDCCH CC PDSCH CC PDCCH CC PDSCH CC CC1 CC1 CC2 CC2 CC3 CC3 (a) Independent search spaces (b) Shared search spaces Option 2: 7

PDCCH CC PDSCH CC PDCCH CC PDSCH CC CC1 CC1 CC2 CC2 CC3 CC3 (a) Independent search spaces (invalid) (b) Shared search spaces Working Assumption Option 1. Modified Option 1 and Option 2 Modified Option 1 PDCCH CC PDSCH CC PDCCH CC PDSCH CC CC1 CC1 CC2 CC2 CC3 CC3 (a) Independent search spaces (b) Shared search spaces Blind decoding and search spaces R1-102016 level 8 level 4 level 2 level 1 CCE Derived from hashing function UE-specific SS for PDSCH CC1 (same as Rel8) UE-specific SS for PDSCH CC2 UE-specific SS for PDSCH CC3 Figure 1: separate UE-SS for different PDSCH CCs (approach 1) 8

Derived from hashing function independently CCE level 8 level 4 level 2 level 1 UE-specific SS for PDSCH CC1 (same as Rel8) UE-specific SS for PDSCH CC2 UE-specific SS for PDSCH CC3 Figure 2: separate UE-SS for different PDSCH CCs (approach 2) common and UE-specific search spaces DCI formats 0/1A and DCI formats with CIF ( DCI common SS DCI UE-specific SS DCI format ) Blind decodings 20MHz Blind decodings CC BW RAN1#61 e-mail search space cross-carrier : - search space Rel-8 - CC DCI o DCI o SS PUCCH: Method(s) for A/N multiplexing e-mail R1-102019 Email discussion summary [60-04-LTE-A]: A/N transmission on PUCCH : - PUCCH A/N UL CC - UE-specific UL CC PUCCH A/N semi-statically - DL CC PDCCH. - 9

- SF 1 - PRBs PUCCH A/N ross-carrier A/N bundling : FDD 10 bits A/N DTX 12bits Simultaneous PUCCH+PUSCH 55bis UL Multiple Antenna Transmission/ HARQ bundling 2 NDIs (one NDI per CW) in the DCI format associated with UL SU-MIMO. 2 HARQ A/N Limit PHICH design to one to one mapping between an A/N and an existing PHICH resource Incoming Liaison Metro Ethernet Forum R1-101717 Liaison Statement from MEF Mobile Backhaul Project to 3GPP TSG LTE FDD 3GPP LTE Application Frequency Phase Time CDMA2000 ±50 ppb ±10µs (±3µs Preferred) (1) GSM ±50 ppb UMTS-FDD/WCDMA (FDD) ±50 ppb UMTS-TDD/WCDMA (TDD) ±50 ppb ±2.5µs (2) TD-SCDMA ±50 ppb ±3µs (3) 10

LTE (FDD) ±50 ppb Not yet specified for MBMS LTE (TDD) ±50 ppb ±3µs (2) Mobile WiMAX ±50 ppb ±1µs (2) Note: (1) Time alignment error with respect to UTC,(2) Phase alignment of neighboring base stations Table 1: Mobile Technology Synchronization Requirements RAN4 R1-101712 Reply LS on additional carrier types for LTE-A extension carrier extended segment Rel-10 Rel-11 R1-102286 Discussion on "Reply LS on additional carrier types for LTE-A" from RAN4 RAN4 RAN2 R2-102110 Removal of non-backward-compatible component carrier from Stage-2 36.300 CR ICIC: : NSN CATT Huawei Ericsson Samsung ICIC Picocell Femtocell RN (Relay Node) data channel control channel cell selection performance control channel Femtocell Macrocell CATT Samsung (1) (2) Range Extension (3) Way Forward 4 radio frames 4 radio frames MeNB 0 1 2 3 (40ms) MeNB 0 1 2 3 (40ms) HeNB 0 1 2 3 (40ms) HeNB 11 0 1 2 3 (40ms) 2-a only HeNB mutes its PBCH 2-b HeNB and MeNB staggered mute their PBCH

Femtocell Muting example Simultaneous PUSCH and PUCCH and clustered SC-FDMA Release 8/9 LTE (uplink) single carrier PUCCH PUSCH PUSCH resource block Release 10 LTE-A (scheduling flexibility) RAN1 Release 10 LTE-A (a) control-data decoupling (simultaneous PUCCH and PUSCH transmission) ( PUCCH+PUSCH ) (b) non-contiguous data transmission with single DFT per component carrier ( clustered PUSCH ) Release 10 LTE-A Carrier (CA) PUCCH+PUSCH component carriers (CCs) 2 UCI Uplink Control Information RAN4 RAN1 LS (Liaison Statements) R1-101720 PUCCH+PUSCH clustered PUSCH PUCCH+PUSCH clustered PUSCH UE inter-modulation products Release 8 (spectrum mask spurious emission) power back-off RAN1 RAN1#55bis (i.e. Release 10 LTE-A PUCCH+PUSCH clustered PUSCH) DTX or not scheduled With UCI UE-specific CC (a) UCI data CC f DTX or not scheduled UE-specific CC PUCCH/PUSCH simultaneous transmission f (b) UCI CC ( data CC) 12

PUCCH+PUSCH CCs Additional Carrier Types for LTE-A Release 10 LTE-A CA Release 8 backward compatible CC extension carrier carrier segment RAN1 RAN1 RAN4 2 LS R1-102286 ( HTC ) (a) RAN1 should develop carrier aggregation for Release 10 using Release 8 compatible carriers without introducing new types else. (b) RAN1 should further study on extension carrier and carrier segment for later release(s) of LTE-Advanced after the development of carrier aggregation in Release 10 becomes stable and/or the enhanced interference control in HetNet in Release 10 is fully studied. RAN4 RAN1 LS R1-101712 (a) Release 10 LTE-A normal component carrier (R8 backward compatible carrier) (b) Release 11 extension carrier carrier segment RAN1 RAN4 Extensions to Rel-8 CQI/PMI/RI feedback RAN1#60 Release 10 LTE-A (downlink, DL) basic feedback framework (a) Implicit feedback (PMI/RI/CQI) is used also for Rel-10 (b) A precoder for a subband is composed of two matrices Each of the two matrices belong to a separate codebook One of the two matrices (WL) targets wideband and/or long-term channel properties The other matrix (WS) targets frequency-selective and/or short-term channel properties LTE-A feedback ( 25 ) (a) Feedback enhancement scheme WL WS codebooks UE PMI (b) Codebook design Codebook Matrix dimensions Codebook 13

(c) Feedback channel: PUSCH/PUCCH enhanced PMI/CQI/RI enhanced PMI/CQI/RI feedback (a) For PUCCH, the feedback corresponding to WL and WS can be sent in different or the same subframe Periodic and aperiodic reports are independent For PUSCH: FFS FFS whether feedback corresponding to W1 and/or W2 may be switched off Enhanced ICIC for non-ca based deployments of heterogeneous networks for LTE 46 WI Enhanced ICIC non-ca Based Heterogeneous Networks 3GPP TR36.814 Heterogeneous Networks Macro+(Pico, Femto, relay, RRH) (a) Indoor HeNB clusters (b) Outdoor Hotzone scenario (c) Indoor Hotzone scenario CMCC ( RAN Plenary#47) WI rapporteur CMCC R1-102161 ( Considerations on evaluation and objective identification of eicic ) R1-102161 (a) Step 1 till RAN#48 (June 2010) Evaluation of the reliability of L1/L2 control channel detection and necessity of L1/L2 control channel coordination Identify candidate schemes for following standardization of L1/L2 control channel coordination (b) Step 2 till RAN#49 (Sep. 2010) Evaluation the gain of new mechanism for cell selection, ICIC, general management over R8/9 ICIC and its feasibility Strive for initial convergence among candidate schemes for following standardization of cell selection and general management Interference Coordination Femto / CSG Downlink Data channel ICIC Downlink Control Channel ICIC 8 4 Interference Coordination 14

UE Categories for Rel.10 (R1-102308) Release 10 UE Categories NTT DoCoMo Release 8/9 UE Categories NTT DoCoMo R1-102308 UE Categories (a) Basic idea for Rel. 10 In general, the number of UE categories should be limited as much as possible Limited number of UE categories in Rel. 10 Support for highest performance UE to identify the potential performance of LTE-Advanced (b) UE categories in downlink New UE categories with higher maximum data rate, i.e., Maximum number of DL-SCH transport block bits received within a TTI. Downlink carrier aggregation can be treated as a UE capability, i.e., no need to add any UE categories. (c) UE categories in uplink Maximum data rate is defined as a UE category, which is the same as in the downlink. Uplink layer is defined as a UE category, which is the same as in the downlink. Necessity for uplink CCs should be discussed in RAN4, since it highly depends on the RF transmitter structure. 15