R1-104271
`
`
`
`
`
`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`Agenda item
`3
`Title:
` Final Report of 3GPP TSG RAN WG1 #61bis v1.0.0
`(Dresden, Germany, 28th June – 2nd July, 2010)
`
`
`Document for:
` Approval
`Source:
`
`MCC Support
`
`
`
`
`
`
`
`
`3GPP TSG RAN WG1 #61bis
`28th June through 2nd July, 2010
`Maritim Hotel Dresden – Germany
`
`
`
`
`
`Fact Summary
`Meeting:
`Dates:
`Venue:
`
`
`
`
`
`
`
`
`
`
`
`1
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`Table of contents
`
`
`
`R1-104271
`
`
`Main facts summary ........................................................................................................................................ 4
`1. Opening of the meeting ........................................................................................................................ 5
`1.1
`Call for IPR ........................................................................................................................................................... 5
`2
`Approval of Agenda ............................................................................................................................... 5
`3
`Approval of Minutes from previous meeting ...................................................................................... 5
`4
`Incoming Liaison Statements ............................................................................................................... 6
`5
`UTRA ....................................................................................................................................................... 7
`5.1
`Maintenance of UTRA Release 99 – Release 9 ........................................................................................... 7
`5.1.1
`FDD ................................................................................................................................................................. 7
`5.1.2
`TDD ................................................................................................................................................................. 9
`5.2
`4-carriers HSDPA ............................................................................................................................................... 9
`5.2.1
`Remaining details ......................................................................................................................................... 9
`5.2.2
`Draft CRs ...................................................................................................................................................... 13
`5.3
`LCR TDD MC-HSUPA ..................................................................................................................................... 14
`5.4
`MU-MIMO for LCR TDD .................................................................................................................................. 15
`5.5
`SI on Improvements for Distributed Antennas for LCR TDD .................................................................... 16
`5.6
`Other ................................................................................................................................................................... 16
`6
`E-UTRA ................................................................................................................................................. 16
`6.1
`Maintenance of E-UTRA Releases 8 – 9 ..................................................................................................... 16
`6.2
`Carrier Aggregation .......................................................................................................................................... 18
`6.2.1
`PCFICH ......................................................................................................................................................... 18
`6.2.2
`PHICH ........................................................................................................................................................... 19
`6.2.3
`PDCCH ......................................................................................................................................................... 20
`6.2.4
`PUCCH ......................................................................................................................................................... 27
`6.2.5
`UL Power Control ........................................................................................................................................ 36
`6.2.6
`PUSCH Resource allocation ..................................................................................................................... 37
`6.2.7
`UCI on PUSCH ............................................................................................................................................ 39
`6.2.8
`Other .............................................................................................................................................................. 42
`6.3
`Enhanced Downlink Multiple Antenna Transmission ................................................................................. 42
`6.3.1
`DM RS ........................................................................................................................................................... 43
`6.3.2
`CSI RS .......................................................................................................................................................... 45
`6.3.3
`DL Single-Cell MU-MIMO .......................................................................................................................... 49
`6.3.4
`Feedback design & Codebook ................................................................................................................. 51
`6.3.5
`Other .............................................................................................................................................................. 62
`6.4
`UL Multiple Antenna Transmission ................................................................................................................ 62
`6.4.1
`Transmission modes and Signalling requirements ............................................................................... 63
`6.4.2
`UCI multiplexing on PUSCH in case of SU-MIMO ............................................................................... 63
`6.4.3
`PHICH mapping for UL SU-MIMO ........................................................................................................... 65
`6.4.4
`PUCCH TxD transmission scheme ......................................................................................................... 66
`6.4.5
`Other .............................................................................................................................................................. 66
`6.5
`Uplink RS issues relevant to LTE-A Work Items ........................................................................................ 67
`6.5.1
`DM RS ........................................................................................................................................................... 67
`6.5.2
`SRS ............................................................................................................................................................... 68
`6.6
`Relaying .............................................................................................................................................................. 69
`6.6.1
`Backhaul design for Type1 relays ............................................................................................................ 69
`6.6.2
`Other .............................................................................................................................................................. 75
`6.7
`Network Based Positioning Support for LTE ............................................................................................... 75
`6.8
`Enhanced ICIC for non-CA based deployments of heterogeneous networks for LTE ......................... 76
`6.8.1
`Control Channel solutions ......................................................................................................................... 77
`6.8.2
`Data Channels ............................................................................................................................................. 79
`6.8.3
`Cell Association ........................................................................................................................................... 80
`6.8.4
`Uplink ............................................................................................................................................................ 80
`6.8.5
`Other .............................................................................................................................................................. 80
`6.9
`Other ................................................................................................................................................................... 81
`
`2 2
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`R1-104271
`
`
`
`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`7
`Closing of the meeting ........................................................................................................................ 82
`Annex A: List of Tdocs at RAN1 #61bis .................................................................................................. 83
`Annex B: List of CRs agreed at RAN1#61bis ......................................................................................... 84
`Annex C - 1: List of Outgoing LSs from RAN1#61bis ............................................................................ 86
`Annex C - 2: List of Incoming LSs from RAN1#61bis ............................................................................ 87
`Annex D: List of Approved updated WIDs ............................................................................................... 88
`Annex E: List of draft TSs/TRs agreed at RAN1 #61bis ....................................................................... 89
`Annex F: List of actions ............................................................................................................................. 90
`Annex G: List of participants at RAN1 #61bis......................................................................................... 91
`Annex H: TSG RAN WG1 meetings in 2010 - 2011 .............................................................................. 92
`
`
`
`3 3
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`
`
`
`Main facts summary
`
`R1-104271
`
`3GPP TSG WG RAN1 #61 bis meeting, hosted by the European Friends of 3GPP took place at the Maritim Hotel
`Congress Center in Dresden, Germany.
`The meeting started at 9:05 on Monday 28th June and finished at 17:14 on Friday 2nd July 2010.
`The number of attending delegates was 234.
`
`The week was scheduled as follows:
` Monday: Common session on Agenda items 1, 2, 3, 4, 6.1 (LTE CRs), 6.9 (UE cat) in the morning session.
`Common session on Agenda item 6.2.4 (PUCCH) and 6.2.3 (PDCCH) for the rest of the day.
` Tuesday: Main session on Agenda item 6.3.4 (Feedback), 6.2.4 (PUCCH), 6.2.3 (PDCCH), 6.2.7 (UCI on
`PUSCH) and 6.2.2 (PHICH) chaired by Matthew Baker. HSPA parallel session on Agenda items 5.1.1, 5.1.2
`(CRs), 5.3 (LCRTDD MC-HSUPA), 5.4 (LCRTDD MU-MIMO) and 5.5 (SI on Improvements for distributed
`antennas for LCRTDD) chaired by Johan Bergman.
` Wednesday: Parallel sessions dedicated to Downlink RS (AIs 6.3.1 and 6.3.2) chaired by Tetsushi Abe on one
`hand, remaining HSPA issues on 4-carrier HSDPA (AI 5.2) chaired by Matthew Baker on the other hand.
` Wednesday following afternoon: Continued discussion on DL RS on one hand and session dedicated on AI 6.7
`(Net.Pos) and 6.3.4 (Feedback) chaired by Matthew Baker. Drafting session on CRs related to 4C HSDPA chaired
`by Johan Bergman.
` Thursday morning: Parallel sessions on AI 6.8 (eICIC) chaired by Tetsushi Abe and on AI 6.3.3 (MU-MIMO) and
`remaining CA topics chaired by Matthew Baker.
` Thursday afternoon: Parallel sessions on remaining CA topics and Relay (AI 6.6) chaired by Matthew Baker and
`Agenda items 6.4.1 to 6.5.2 (UL RS and UL MIMO) chaired by Charlie Zhang.
` Friday morning: Early parallel sessions to complete 4C HSDPA on one hand and eICIC on the other hand,
`followed by common session on Agenda item 6.3.4 (Feedback) and CA continuation.
` Friday afternoon: Revisions
`
`
`
`The list of action points that required RAN1 close follow-up is listed in Annex F (end of document).
`
`The number of contribution documents for this meeting was 816.
`Agenda Item
`
`Input
`Document
`811
`
`Discussed
`Document
`373
`
`From AI 4 to 6.9
`
`
`Note: The amount of documents includes those discussed during the email discussion session post meeting.
`
`
`The following documents are missing. The corresponding contributions have not been handed over by companies.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`4 4
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`
`
`
`R1-104271
`
`Opening of the meeting
`1.
`Mr. Matthew Baker (RAN1 Chairman) welcomed the participants to the 61st RAN WG1 bis meeting and opened the
`meeting at 09:05.
`Mr Georg Wannemacher from Deutsche Telekom AG welcomed the delegates on behalf of the European Friends of 3GPP
`and detailed the domestic arrangements (meeting rooms, coffee breaks, restaurants and lunch suggestions) for the week. It
`was also noticed that a QUALITY MEETING SURVEY to fill-in after the meeting will be greatly appreciated by the
`organizer.
`Furthermore, the group was also informed of a kind of social event that Vodafone would like to host together with
`Technical University of Dresden. TU- Dresden is active is many European projects and has requested an opportunity to
`demo their ongoing work on COMP to 3GPP community.
`The demonstration is proposed to be done using live test bed with Vodafone and T-mobile providing the site, from the
`entrance of the congress center.
`Meeting time is requested for presentation of a brief contribution on simulation results and demo setup details (R1-
`104122).
`R1-104122
`
`Cooperative Multipoint Performance Evaluation Based on Simulation and
`Trial Measurements in Easy-C Project
`
`Vodafone
`
`
`
`
`Call for IPR
`1.1
`The Chairman drew attention to Members’ obligations under the 3GPP Partner Organizations’ IPR policies. Every
`Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a
`member any IPR owned by the Individual Member or any other organization which is or is likely to become
`essential to the work of 3GPP.
`
`
`The attention of the members of this Technical Specification Group is drawn to the fact that 3GPP
`Individual Members have the obligation under the IPR Policies of their respective Organizational Partners
`to inform their respective Organizational Partners of Essential IPRs they become aware of.
`The members take note that they are hereby invited:
`(cid:31)
`to investigate in their company whether their company does own IPRs which are, or are likely to become
`Essential in respect of the work of the Technical Specification Group.
`to notify the Director-General, or the Chairman of their respective Organizational Partners, of all
`potential IPRs that their company may own, by means of the IPR Statement and the Licensing declaration
`forms (e.g. see the ETSI IPR forms http://webapp.etsi.org/Ipr/).
`
`(cid:31)
`
`Approval of Agenda
`
`
`
` 2
`
`
`
`
`RAN1 Chairman
`Draft Agenda for RAN1#61bis meeting
`R1-103430
`Matthew Baker (Chairman) proposed the agenda for the meeting and the plan (tentative schedule) of the week.
`Decision: The agenda is approved.
`
` 3
`
`
`
`Approval of Minutes from previous meeting
`
` (R1-103431)
`MCC Support
`Final report of RAN1#61 meeting
`R1-104138
`The document was presented by Patrick Mérias (ETSI Mobile Competence Center) and provides the outcomes of last
`meeting. The revised document includes correct conclusion on the WF on HS-DPCCH for 4C-HSDPA that was agreed at
`last meeting. It was brought to the attention of delegates that discrepency exists between the number of
`registered/attending/signing participants. Signature of the participants list is mandatoty for all participants to a 3GPP
`meeting and will impact the calculation of voting rights for future election.
`Discussion (Question / Comment): Late comment was raised that the sentence in brackets “(with DMRS or non-
`interleaving of CRS)”w.r.t Relaying UL grant agreement shall be removed on page 60.
`
`5 5
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`Decision: The document is updated in R1-104183 and approved.
`
`
`
`
`R1-104271
`
` (R1-103431)
`RAN1 Chairman
`Selected highlights from RAN#48
`R1-104182
`The document was presented by Matthew Baker and provides an overview of the outcomes of last plenary meeting.
`Discussion (Question / Comment): Ericsson commented the CoMP simulation assumptions bullet observing that it had
`two folds, meeting time issue and how companies set resources on the topic. Ericsson plans to run simulations and see
`what can be concluded already by September timeframe.
`Decision: The document is approved.
`
`Note: SI on Energy Saving for UMTS on hold until RAN#49.
`
`Incoming Liaison Statements
`
` 4
`
`
`
`Reply LS on UE transmitter structure and power in MC-HSUPA for
`R1-103525
`RAN4, CATT
`= R4-101779
`1.28Mcps TDD
`The document was presented by Ms Yanping Xing from CATT and confirms that RAN1 working assumptions are
`consistent with the most likely implementation for multi-carrier HSUPA which utilize contiguous carriers. The reply also
`confirms that no new UE power classes is currently foreseen by RAN4 with the introduction of MC-HSUPA, since
`introducing higher maximum power will bring difficult problems for PA (higher unwanted emission and power
`consumption, EMC requirements difficulties).
`Discussion (Question / Comment): To be taken into account under AI 5.3.
`Decision: The document is noted.
`
`
`= R4-102337
`RAN4, ST-Ericsson
`Reply to LS on DB-DC-HSDPA secondary carrier activation
`R1-103528
`The document was presented by Johan Bergman from ST-Ericsson and informs RAN1 that for the case of DB-DC-
`HSDPA, RAN4 concluded that it could be beneficial to allow for an interruption in the order of 200 µs, for the scenario
`mentioned in the question, in order to optimize the power consumption of the digital interface between RF and baseband.
`The interruption is expected to affect both reception as well as transmission.
`In addition, RAN4 concluded that it may be beneficial to allow for an interruption of the transmission and reception of the
`carrier(s), in the band that is kept in active state, whenever the other band is deactivated. In analogy with the conclusion
`from question 1, the interruption time can be in the order of 200 µs.
`Discussion (Question / Comment): To be taken into account.
`Decision: The document is noted.
`
`LTE related LSs
`
`
`R1-103524
`LS on DL timing difference and DL timing reference in Carrier Aggregation
`RAN2, Qualcomm
`= R2-103449
`The document was presented by Wanshi Chen from Qualcomm and provides RAN2 understandings w.r.t the timing of
`uplink grants and downlink assignments and reference DL timing used by the UE.
`Discussion (Question / Comment): RAN1 to take the information into account, and inform RAN2 if any concerns are
`seen. NSN commented that there may be some impact to layer 1  misadjustment between DL CC’s needs to be
`minimized to avoid reducing processing time.
`Decision: The document is noted.
`
`
`= R4-102260
`RAN4, NTT DoCoMo
`Reply LS on pathloss measurements in CA scenarios
`R1-103526
`The document was presented by Tetsushi Abe from NTT DoCoMo and confirms that path loss estimate should be done
`from DL CC which has the DL-UL linkage signalled by network on SIB2, regardless whether the CCis de-activated or not.
`No measurement configuration would be needed for the path loss measurement.
`Discussion (Question / Comment): Chairman’s understanding is that info from RAN4 still needed. Qualcomm
`commented that no RLF defined for SCC  Pathloss measurement may be unreliable. Philips commented that signalling
`issues shall be assessed.
`Decision: The document is noted.
`
`
`= R4-102268
`RAN4, CMCC
`LS on in-device coexistence interference
`R1-103527
`The document was presented by Xiaodong Xu from CMCC and shows RAN4 views on the coexistence issues between
`ISM technologies and LTE deployed in the adjacent bands. As a conclusion, the coexistence issue can cause interference to
`
`6 6
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`
`
`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`the LTE receiver at the UE or make the LTE Tx cause interference to the ISM radio and methods for new signalling
`procedures or resource sharing/re-allocation may need to be considered.
`Discussion (Question / Comment): Not really relevant to RAN1.
`Decision: The document is noted.
`
`LSs received during the week
`
`Friday 2nd
`
`
`R1-104271
`
`= R2-104181
`RAN2, NTT DoCoMo
`LS on SCell activation/deactivation
`R1-104168
`The document was presented by Tetsushi Abe from NTT DoCoMo and informs of RAN2 decision to keep the SCell
`activation/deactivation mechanism for Carrier Aggregation in Rel-10, as majority of the companies showed interest in the
`possible UE battery consumption saving benefits. The LS is to RAN4 for answering questions related to glitches in
`PDCCH/PDSCH reception if the UE is allowed to retune the RF bandwidth of a RF component at SCell
`activation/deactivation transitions and during RRM measurements on a deactivated Scell.
`Decision: The document is noted.
`
`
`RAN2, Qualcomm
`LS on CIF values
`R1-104264
`The document was presented by Perter Gaal from Qualcomm. RAN2 asks RAN1:
`to indicate if the value of the CIF is unique for each cell configured for a particular UE.
`
`
`to indicate if the CIF is expected to change during the lifetime of an SCell.
`Decision: The document is noted. RAN1 should think about it until next meeting.
`
`
` = R2-104209
`
` = R2-104205
`RAN2, MediaTek
`Per UE PHR related questions
`R1-104265
`The document was presented by Matthew Baker on behalf of MediaTek. RAN2 asks RAN1’s advice as to the need for
`additional power headroom information to be provided to the eNB, in addition to the per-CC PHR.
`Decision: The document is noted. RAN1 should think about it until next meeting.
`
`
` = R2-104201
`RAN2, Alcatel-Lucent
`LS on status of RAN2 decisions on CA
`R1-104266
`The document was presented by Mrs Jungah Lee from Alcatel-Lucent and informs RAN1 of the relevant CA decisions (not
`covered by other LSes) taken in RAN2#70bis.
`Decision: The document is noted.
`
`UTRA
`
` 5
`
`
`
`R1-104141
`Minutes from RAN1#61bis HSPA sessions
`The document was presented by Johan Bergman from Ericsson.
`Decision: The document is endorsed and reported as follows in sections 5.1, 5.3, 5.4, 5.5 and 5.6.
`5.1
`Maintenance of UTRA Release 99 – Release 9
`
`Ad Hoc chairman (Ericsson)
`
`
`
`5.1.1
`
`FDD
`
`Ericsson. ST-Ericsson
`
`R1-103460
`Support for different HS-SCCHs in contiguous TTIs in CELL_FACH
`Decision: The document is noted.
`
`Agreement:
` From RAN1 point of view, there is nothing preventing the Rel-8 feature ‘Support for different HS-SCCHs in
`contiguous TTIs’ from being valid also in CELL_FACH (i.e. not only in CELL_DCH).
` Provide a draft LS to RAN2 and RAN3 in R1-104145 (Ericsson).
`Friday 2nd
`Draft LS to RAN2 and RAN3 on Support for different HS-SCCHs in
`R1-104145
`Ericsson
`
`contiguous TTIs in CELL_FACH
`The document was presented by Johan Bergman from Ericsson. MCC shall check WI code. Motorola questioned whether
`the attachment was actually needed  just for background information.
`
`
`
`7 7
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`Decision: The document and final LS is agreed in R1-104243. (WI code: RANimp-UplinkEnhState)
`
`
`
`
`
`R1-104271
`
`R1-103868
`
`R1-103869
`
`Infineon Technologies.
`25.214 CR0605R3 (Rel-7. F) Clarification of HS-DSCH and HS-SCCH
`Qualcomm Incorporated
`reception in CELL_FACH. CELL_PCH and URA_PCH states
`Infineon Technologies.
`25.214 CR0606R2 (Rel-8. A) Clarification of HS-DSCH and HS-SCCH
`Qualcomm Incorporated
`reception in CELL_FACH. CELL_PCH and URA_PCH states
`Infineon Technologies.
`25.214 CR0607R2 (Rel-9. A) Clarification of HS-DSCH and HS-SCCH
`R1-103870
`
`Qualcomm Incorporated
`reception in CELL_FACH. CELL_PCH and URA_PCH states
`Decision: The documents are noted and agreed in principle. Companies are encouraged to check the details until Friday. If
`needed, revisions can be provided in R1-104146 to R1-104148 (Infineon).
`Friday 2nd
`Qualcomm informed that consensus was reached and asked to minute that the following UE behavior is implied by the
`CRs in R1-103868/3869/3870: “In CELL_FACH and CELL_PCH state, when UE receives two H-RNTIs on two HS-
`SCCHs in the same TTI, the UE behavior is not defined."
`Infineon informed that no more comments were received. R1-104146 to R1-104148 are not needed and original versions in
`R1-103868 to R1-103870 are agreed.
`
`
`
`
`
`
`Impact of Unequal P/S-CPICH power setting on CQI reporting procedure
`R1-103847
`when the UE is configured in MIMO mode
`Decision: The document is noted.
`
`R1-104003
`
`25.214 CR0602R2 (Rel-7, F) Clarification of the CQI definition when the UE
`is configured in MIMO mode
`
`R1-104004
`
`25.214 CR0603R2 (Rel-8, A) Clarification of the CQI definition when the
`UE is configured in MIMO mode
`
`Qualcomm Incorporated
`
`Huawei, Qualcomm
`Incorporated, InterDigital
`Communication LLC
`
`Huawei, Qualcomm
`Incorporated, InterDigital
`Communication LLC
`
`
`
`
`
`
`
`R1-104005
`
`Huawei, Qualcomm
`25.214 CR0604R2 (Rel-9, A) Clarification of the CQI definition when the
`Incorporated, InterDigital
`UE is configured in MIMO mode
`Communication LLC
`Decision: The documents are noted. It is agreed that the desired UE behaviour is to compensate for the S-CPICH power
`offset in the MIMO CQI calculation. Continue discussion offline until Friday. If needed, revisions can be provided in R1-
`104149 to R1-104151 (Huawei).
`Friday 2nd
`Huawei briefly presented the revisions in R1-104149 to R1-104151.
`Motorola provided following text on the reflector “In addition, while estimating the CQI, the UE should take into account
`the relative transmit power of the S-CPICH compared to the primary CPICH transmit power as specified in section
`5.2.16.” Text was not agreed by Qualcomm. NSN do not strongly see the necessity of such CRs.
`The need for a clarification is agreed in principle. The details of the CRs shall be agreed by RAN1#62.
`
`
`
`
`Activation state of the secondary uplink frequency
`R1-104006
`Decision: The document is noted.
`
`
`25.212 CR0287 (Rel-9, F) Clarification of uplink frequencies
`R1-104038
`Decision: The document is noted. Provide revision 1 in R1-104152 (ZTE).
`Friday 2nd : R1-104152 is agreed
`
`
`25.213 CR0107 (Rel-9, F) Clarification of uplink frequencies
`R1-104039
`Decision: The document is noted. Provide revision R1 in R1-104153 (ZTE).
`Friday 2nd : R1-104153 is agreed
`
`
`Huawei
`
`ZTE
`
`ZTE
`
`
`
`
`
`
`
`
`ZTE
`RF impact of multi-carrier HSDPA
`R1-104037
`Decision: The document is noted. Companies are encouraged to check further and if needed contribute to the appropriate
`WG(s) at the next meeting(s).
`
`
`Clarification of E-AGCH/E-RGCH monitoring in a CM gap when
`R1-104180
`Qualcomm Incorporated
`
`DL_DRX_Active is TRUE
`Decision: The document is noted. Provide a Rel-7 CR and shadow CRs for Rel-8 and Rel-9 in R1-104154 to R1-104156
`(Qualcomm).
`Friday 2nd :
`
`8 8
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`
`
`
`R1-104271
`
`25.214 CR0612 (Rel-7, F) Clarification of E-AGCH/E-RGCH monitoring in
`a CM gap when DL_DRX_Active is TRUE
`25.214 CR0613 (Rel-8, A) Clarification of E-AGCH/E-RGCH monitoring in
`a CM gap when DL_DRX_Active is TRUE
`25.214 CR0614 (Rel-9, A) Clarification of E-AGCH/E-RGCH monitoring in
`R1-104156
`Qualcomm Incorporated
`
`a CM gap when DL_DRX_Active is TRUE
`Decision: The documents are noted and CRs are agreed according MCC shall check for the correct spec version, CR
`category and CR release version into the cover sheets.
`
`5.1.2
`
`Qualcomm Incorporated
`
`Qualcomm Incorporated
`
`
`
`
`
`R1-104154
`
`R1-104155
`
`TDD
`
`
`
`
`
`
`
`TD Tech
`
`TD Tech
`
`TD Tech
`
`25224 CR0253 (Rel-8, F) Clarification on HS-DSCH transmission in
`R1-103993
`CELL_PCH or URA_PCH state for 1.28Mcps TDD
`Decision: The document is noted.
`25224 CR0254 (Rel-9, A) Clarification on HS-DSCH transmission in
`R1-103994
`CELL_PCH or URA_PCH state for 1.28Mcps TDD
`Decision: The document is noted.
`Updated simulation assumptions can be provided in R1-104143 (TD Tech).
`
`Friday 2nd
`Simulation assumptions HS-DSCH transmission in CELL_PCH or
`R1-104143
`URA_PCH state for 1.28Mcps TDD
`The document was presented by Ms Rong Li from TD Tech.
`Discussion (Question / Comment): CATT believes payload size is not sufficient and the value 176 should be added.
`Decision: The document is noted and shall be revised with the add-on “select one or both of {176, 240}. Final version in
`R1-104257 is agreed for HS-DSCH performance investigation in Enhanced CELL_PCH or URA_PCH states.
`
`4-carriers HSDPA
`5.2
`WID in RP-091438
`5.2.1
`Remaining details
`3C without MIMO
`
`
`R1-103461
`
`Proposed way forward on HS-DPCCH design for 3C-HSDPA w/o MIMO
`
`Ericsson, ST-Ericsson, Nokia
`Siemens Networks, Nokia,
`Alcatel-Lucent, Alcatel-
`Lucent Shanghai Bell
`
`
`
`The document was presented by Johan Hultell from Ericsson and proposes the following as a basis for further detailed
`design:
` Proposal 1: Adopt SF128 for HS-DPCCH also for the cases when 3 carriers without MIMO are configured.
` Proposal 2: A DTX codeword is included in the ACK/NACK codebook also for the case when 3 carriers are
`configured without MIMO.
` Proposal 3: Changing transmission power in the middle of an uplink slot due to half slot ACK/NACK
`transmission should be avoided also for the case where 3 carriers without MIMO are configured.
` Proposal 4: When 3 carriers are configured the information of the fourth CQI field is always DTXed.
`Discussion (Question / Comment): Number of contributions seems to show other proposals, said Mr Chairman. Huawei
`has different view on DTX codeword and believes better performance can be achieved.
`Decision: The document is noted.
`
`
`R1-104213
`HS-DPCCH Configuration for 3C without MIMO
`Qualcomm Incorporated
`The document was presented by Arjun Bharadwaj from Qualcomm and proposes:
` When the UE is configured with 4 carriers or 3 carriers with MIMO on at least one carrier,
`o Spreading factor 128 is used for the HS-DPCCH channel regardless of the number of activated carriers.
`o Rel-9 DC-MIMO codebook is used regardless of whether MIMO is configured or not.+
`
` (R1-103851)
`
`9 9
`
`Ericsson Exhibit 1020
`ERICSSON v. ETRI
`
`

`

`3GPP TSG RAN WG1 Meeting #62
`Madrid, Spain, 23 – 27 August, 2010
`
`
`
`
`R1-104271
`
` Adopt a single code book Rel-10 TC-HSDPA solution for the case when the UE is configured with 3 carriers
`without MIMO that is transmitted using 1xSF256.
`Discussion (Question / Comment): Issues on robustnees raised by Huawei. Ericsson agreed with proposal 1 in first bullet.
`Decision: The document is noted.
`
`
`
`
`Ericsson. ST-Ericsson
`
`R1-103463
`ACK/NACK for 3C-HSDPA without MIMO
`The document was presented by Johan Hultell from Ericsson and proposes to:
` Adopt a 1xSF128 HS-DPCCH solution also for the case of 3C-HSDPA and where none of the carriers are
`configured with MIMO.
` Reuse the Rel-9 HARQ-ACK codebook also for the case of 3C-HSDPA and where none of the carriers are
`configured with MIMO.
` Discuss whether a new DTX codeword for the 3C-HSDPA without MIMO as a possible optimization.
` Agree that the HARQ-ACK information of the fourth carrier always is DTXed (i.e. the codeword A/D would be
`used when sending an ACK for carrier 3) when a UE is configured with 3 carriers without MIMO.
`Discussion (Question / Comment): Evaluating detection performance was debated, when Node