R1-10xxxx
`
`
`
`
`
`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`Agenda item
`3
`Title:
` Draft Report of 3GPP TSG RAN WG1 #60bis v0.1.0
`(Beijing, China, 12th – 16th April, 2010)
`
`
`Document for:
` Comment
`Source:
`
`MCC Support
`
`
`Please provide your feedback by the latest on 5th May2010
`
`
`
`
`
`
`
`
`
`Fact Summary
`Meeting:
`Dates:
`Venue:
`
`
`
`
`
`
`
`
`
`
`
`3GPP TSG RAN WG1 #60bis
`12th through 16th February, 2010
`China World Hotel, Beijing – People’s Republic of China
`
`1
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 1
`
`

`

`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`Table of contents
`
`
`
`R1-10xxxx
`
`
`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 ............................................................................................................... 5
`4.1
`New LS received in the course of the week ................................................................................................ 7
`5
`UTRA ....................................................................................................................................................... 7
`5.1
`Maintenance of UTRA Release 99 – Release 9 ......................................................................................... 8
`5.1.1
`FDD .............................................................................................................................................................. 8
`5.1.2
`TDD .............................................................................................................................................................. 8
`5.2
`4-carriers HSDPA ............................................................................................................................................ 8
`5.2.1
`HS-DPCCH design .................................................................................................................................... 9
`5.2.2
`Other .......................................................................................................................................................... 12
`5.3
`LCR TDD MC-HSUPA .................................................................................................................................. 15
`5.4
`MU-MIMO for LCR TDD ............................................................................................................................... 16
`5.5
`Study on UL TxD ............................................................................................................................................ 17
`5.6
`SI on Energy Saving for UMTS ................................................................................................................... 19
`5.7
`SI on Improvements for Distributed Antennas for LCR TDD................................................................... 21
`5.8
`Other ............................................................................................................................................................... 21
`6
`E-UTRA ................................................................................................................................................. 21
`6.1
`Maintenance of E-UTRA Releases 8 – 9 ................................................................................................... 21
`6.2
`Carrier Aggregation ....................................................................................................................................... 22
`6.2.1
`PCFICH ..................................................................................................................................................... 22
`6.2.2
`PHICH ....................................................................................................................................................... 24
`6.2.3
`PDCCH ...................................................................................................................................................... 24
`6.2.3.1
`Linkage between PDSCH/PUSCH and PDCCH ........................................................................... 24
`6.2.3.2
`Blind decoding and search spaces .................................................................................................. 26
`6.2.3.3
`Remaining details of CIF ................................................................................................................... 30
`6.2.4
`PUCCH ...................................................................................................................................................... 30
`6.2.4.1
`Method(s) for A/N multiplexing ......................................................................................................... 30
`6.2.4.2
`Transmit diversity ............................................................................................................................... 33
`6.2.4.3
`Other .................................................................................................................................................... 34
`6.2.5
`UL Power Control ..................................................................................................................................... 36
`6.2.5.1
`Pathloss derivation ............................................................................................................................. 36
`6.2.5.2
`Power headroom reporting ............................................................................................................... 36
`6.2.5.3
`Power scaling in case of power limitation ....................................................................................... 37
`6.2.5.4
`Details of cross carrier PC with DCI Format 3/3A ......................................................................... 38
`6.2.5.5
`Other .................................................................................................................................................... 39
`6.2.6
`PUSCH Resource allocation .................................................................................................................. 39
`6.2.7
`Other .......................................................................................................................................................... 40
`6.3
`Enhanced Downlink Multiple Antenna Transmission ............................................................................... 40
`6.3.1
`DM RS ....................................................................................................................................................... 40
`6.3.1.1
`DM RS pattern for extended CP ...................................................................................................... 42
`6.3.1.2
`Other .................................................................................................................................................... 43
`6.3.2
`CSI RS ....................................................................................................................................................... 43
`6.3.3
`DL Single-Cell MU-MIMO ....................................................................................................................... 45
`6.3.3.1
`Transparent vs. non-transparent MU-MIMO .................................................................................. 45
`6.3.3.2
`Use of DM RS ports / scrambling sequences for MU-MIMO ....................................................... 46
`6.3.3.3
`Other .................................................................................................................................................... 46
`6.3.4
`Feedback .................................................................................................................................................. 46
`6.3.4.1
`8 Tx Codebook design....................................................................................................................... 46
`6.3.4.2
`Extensions to Rel-8 CQI/PMI/RI feedback ..................................................................................... 47
`6.3.5
`Other .......................................................................................................................................................... 53
`
`2 2
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 2
`
`

`

`R1-10xxxx
`
`
`
`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`6.4
`UL Multiple Antenna Transmission ............................................................................................................. 53
`6.4.1
`HARQ bundling ........................................................................................................................................ 53
`6.4.2
`Transmission modes and Signalling requirements ............................................................................. 54
`6.4.3
`PUCCH TxD transmission scheme ....................................................................................................... 54
`6.4.4
`Other .......................................................................................................................................................... 54
`6.5
`Uplink RS issues relevant to LTE-A Work Items ...................................................................................... 56
`6.5.1
`DM RS ....................................................................................................................................................... 56
`6.5.1.1
`OCC ..................................................................................................................................................... 56
`6.5.1.2
`Other .................................................................................................................................................... 57
`6.5.2
`SRS ............................................................................................................................................................ 57
`6.6
`Relaying .......................................................................................................................................................... 61
`6.6.1
`Backhaul design for Type1 relays ......................................................................................................... 61
`6.6.1.1
` Timing relation between eNB and RN ............................................................................................ 61
`6.6.1.2
` Backhaul control channel design .................................................................................................... 63
`6.6.1.3
` HARQ .................................................................................................................................................. 66
`6.6.2
`Other .......................................................................................................................................................... 67
`6.7
`Network Based Positioning Support for LTE ............................................................................................. 68
`6.8
`Enhanced ICIC for non-CA based deployments of heterogeneous networks for LTE ........................ 68
`6.9
`Other ............................................................................................................................................................... 71
`7
`Closing of the meeting ........................................................................................................................ 72
`Annex A: List of Tdocs at RAN1 #60bis .................................................................................................. 73
`Annex B: List of CRs agreed at RAN1#60bis ......................................................................................... 74
`Annex C - 1: List of Outgoing LSs from RAN1#60bis ............................................................................ 75
`Annex C - 2: List of Incoming LSs from RAN1#60bis ............................................................................ 76
`Annex D: List of Approved updated WIDs ............................................................................................... 77
`Annex E: List of draft TSs/TRs agreed at RAN1 #60bis ....................................................................... 78
`Annex F: List of actions ............................................................................................................................. 79
`Annex G: List of participants at RAN1 #60bis......................................................................................... 83
`Annex H: TSG RAN WG1 meetings in 2010 - 2011 .............................................................................. 84
`
`
`
`3 3
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 3
`
`

`

`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`
`
`
`Main facts summary
`
`R1-10xxxx
`
`3GPP TSG WG RAN1 #60bis meeting, hosted by Huawei Technologies took place at the China World Hotel in Beijing,
`P.R. of China.
`The meeting started at 9:08 on Monday 12th April and finished at 17:20 on Friday 16th April 2010.
`The number of attending delegates was xxx.
`
`The week was scheduled as follows:
`• Monday: Common session on Agenda items 1, 2, 3, 4, 6.1
`• 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 xxx.
`Agenda Item
`
`Input
`Document
`
`
`Discussed
`Document
`
`
`
`
`
`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
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 4
`
`

`

`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`
`
`
`R1-10xxxx
`
`Opening of the meeting
`1.
`Mr. Matthew Baker (RAN1 Chairman) welcomed the participants to the 60th RAN WG1 bis meeting and opened the
`meeting at 09:08.
`Mr. Brian Classon from Huawei Technologies welcomed the delegates and detailed the domestic arrangements (coffee
`breaks, restaurants) for the week.
`1.1
`Call for IPR
`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:
`
`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/).
`
`
`
`Approval of Agenda
`
`
`
` 2
`
`
`
`
`RAN1 Chairman
`Draft Agenda for RAN1#60bis meeting
`R1-101710
`Matthew Baker (Chairman) proposed the agenda for the meeting and the plan (tentative schedule) of the week. In addition,
`Mr Chairman provided the group with the main highlights relevant to RAN1 [R1-102468] from last plenary in Vienna
`(RAN#47).
`Discussion (Question / Comment):
`Decision: The agenda is approved.
`
`Approval of Minutes from previous meeting
`
` 3
`
`
`
`
`MCC Support
`Final report of RAN1#60 meeting
`R1-101711
`The document was presented by Patrick Mérias (ETSI Mobile Competence Center) and provides the outcomes of last
`meeting.
`Discussion (Question / Comment): Huawei asked for a clarification on PDCCH (AI 7.1.3 – page 28) w.r.t CRC size.
`There is no will to change the decision that CRC size does not need to be increased in Rel-10.
`Decision: The document is approved.
`
`Incoming Liaison Statements
`
` 4
`
`
`
`Metro Ethernet Forum,
`Liaison Statement from MEF Mobile Backhaul Project to 3GPP TSG
`= L00101-000
`R1-101717
`Verizon
`RAN WG 1, WG 3, WG 4
`The document was presented by Matthew Baker. Not direct impact to RAN1 work. The LS from Metro Ethernet Forum
`concerns the introduction of synchronization requirements in support of mobile backhaul services and shall be further
`proceeded by RAN3/RAN4.
`Decision: The document is noted.
`
`5 5
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 5
`
`

`

`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`
`
`
`
`R1-10xxxx
`
`= R4-101042
`RAN4, Ericsson
`Band Combination Scenarios for Four Carrier HSDPA
`R1-101713
`The document was presented by Johan Bergman from Ericsson and requests RAN to take into account the agreed list of
`band combination scenarios for ‘Four Carrier HSDPA’ WI.
`Discussion (Question / Comment): No action specific to RAN1, to be considered under AI 5.2.
`Decision: The document is noted.
`
`
`= R4-101043
`RAN4, Ericsson
`Feasibility of Non-adjacent Carrier Operation due to Deactivation
`R1-101714
`The document was presented by Johan Bergman from Ericsson and informs RAN on RAN4 recommendation that the non-
`adjacent carrier operation due to the deactivation of the configured carriers within a single band is feasible from the
`perspectives of UE and BS implementation.
`Discussion (Question / Comment): No action specific to RAN1.
`Decision: The document is noted.
`
`
`LS on signalling support for inter-frequency OTDOA RSTD
`R1-101716
`= R4-101070
`RAN4, Ericsson
`measurements
`The document was presented by Daniel Larsson from Ericsson and asks RAN2 to make sure that the following
`information is available to the UE in the OTDOA assistance data for each neighbor cell on an inter-frequency carrier to be
`measured by the UE:
`• Number of subframes between the first PRS subframe in the serving cell on the serving carrier frequency layer and the first
`PRS subframe in the closest subsequent PRS burst of the other cell on the other carrier frequency layer. With the maximum
`PRS periodicity of 1280 ms, this is in the range [0, 1279] sub-frames with resolution of 1 sub-frame.
`Discussion (Question / Comment): No action specific to RAN1.
`Decision: The document is noted.
`
`
`= R4-100977
`RAN4, NTT DoCoMo
`Reply LS on additional carrier types for LTE-A
`R1-101712
`The document was presented by Nobuhiko Miki from NTT DoCoMo and provides RAN4 conclusions that only normal
`component carrier (R8 backward compatible carrier) should be utilized to achieve efficient spectrum usage in Release 10
`time frame. That is, neither extension carrier nor carrier segment should be introduced in Release 10 but could be
`considered for introduction in Release 11.
`Decision: The document is noted.
`Discussion on "Reply LS on additional carrier types for LTE-A" from
`CHTTL, HTC
`R1-102286
`RAN4
`The document was presented by Robinson Chiu from CHTTL and proposes that RAN1 should:
`• Develop carrier aggregation for Release 10 using Release 8 compatible carriers without introducing new types
`else.
`• 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.
`Decision: The document is noted.
`
`
`
`
`= C4-100801
`CT4, TruePosition
`Response LS to RAN1 and RAN3 on UTDOA
`R1-101718
`The document was presented by Simon Isskav from TruePosition and highlights CT4’s view that MME processing time for
`transport of LPPa messages should be minimal— approximately 1 millisecond. The link latency between the MME and
`eSMLC should be similar to the eNB to MME link latency.
`Discussion (Question / Comment): .
`Decision: The document is noted.
`
`
`= R2-101893
`RAN2, Huawei
`Sharing a PUCCH-SR resource among UEs
`R1-101719
`The document was presented by Ms Meng Zhao from Huawei and concerns a proposal to share a PUCCH-SR among more
`than one UE as discussed in RAN2. Questions raised are:
`• Can the eNB detect reliably between [no UE indicates scheduling request] and [one or more UE indicates
`scheduling request]?
`• Can RAN1 study the feasibility and detection performance?
`In case two UEs perform a transmission on the same resource, what would the probability of successful decoding
`•
`of one PUSCH transmission after one single transmission (no HARQ) be?
`Decision: The document is noted.
`R1-101932
`Feasibility and performance discussion on SR sharing
`
`Huawei
`
`
`
`6 6
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 6
`
`

`

`
`
`R1-10xxxx
`
`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`The document was presented by Ms Meng Zhao from Huawei and provides Huawei’s view based on their simulation
`results as a reply to the LS in R1-101719.
`Discussion (Question / Comment): Panasonic requested clarification on the transmission of scheduling resource.
`Ericsson commented that format 1B has not been evaluated. Q: Are the cyclic shifts different? Answer is no.
`Decision: The document is noted.
`
`MediaTek
`R1-101984
`Simulation results for CB-PUSCH (response to R1-101719)
`The document was presented by … from MediaTek and identifies that the following two requirements shall be met so that
`the data from two contending UEs are decodable.
`• The reference signals of the two contending UEs shall not be the same.
`• The eNB shall be equipped more than 1 receive antenna.
`It is suggested that RAN1 should discuss the simulation parameters for CB-PUSCH before further performance evaluation.
`Discussion (Question / Comment): .
`Decision: The document is noted.
`Draft LS Response to RAN2 on sharing a PUCCH-SR resource
`
`Huawei
`R1-101933
`among UEs
`The document wasn’t formally presented by Huawei as it’s roughly identical to the conclusion of R1-101932.
`Decision: The document is noted. Offline discussion is required to see whether there is consensus on a reply or whether
`more time is needed till RAN1#61.
`Friday 16th
`
`R1-102506
`
`[Draft] LS Response to RAN2 on sharing a PUCCH-SR resource
`among UEs
`Decision: The document is noted and final LS is agreed in R1-102575.
`
`
`Huawei, Ericsson, Alcatel-
`Lucent, MediaTek, ZTE,
`Panasonic
`
`(R1-101933)
`
`= R4-101082
`RAN4, ST-Ericsson
`LS on simultaneous PUSCH and PUCCH and clustered SC-FDMA
`R1-101720
`The document was presented by Daniel Larsson from Ericsson and raised question from RAN4 with regard to clustered
`PUSCH and decoupled control-data.
`Decision: The document is noted. LS shall be taken into account after discussion under AI 6.2.4.
`
`
`= R4-101083
`RAN4, Qualcomm
`LS reply on uplink power control in LTE-A
`R1-101721
`The document was presented by Peter Gaal from Qualcomm and provides RAN4 answers to R1-100831 for further
`consideration on carrier aggregation work.
`Discussion (Question / Comment): Maximum powers should be independant of the number of carriers.
`Decision: The document is noted.
`
`New LS received in the course of the week
`4.1
`= R3-101349
`LS response on MEF Mobile Backhaul Project
`RAN3, Ericsson
`R1-102505
`LS reply from RAN3 that the final reply LS to MEF should also refer to 25.402, 25.411 and 36.401 as example of 3GPP
`specifications addressing network synchronisation requirements.
`Decision: The document is noted. No action for RAN1.
`
`
`= R4-101260
`RAN4, Huawei
`LS on configurable transmission modes for Category 1 UE
`R1-102512
`The document was presented by … from Huawei. RAN4 requests RAN1 to confirm that all the UE categories should
`support all transmission modes.
`Decision: The document is noted. No need to reply at this meeting; the reply is expected at RAN1#61 (Huawei).
`
`UTRA
`
` 5
`
`
`
`Minutes from RAN1#60bis HSPA sessions
`R1-102473
`The document was presented by Johan Bergman from Ericsson.
`Decision: The document is endorsed and reported as follows in sections 5.1, 5.2, 5.4 and 5.5.
`
`Ad-hoc chairman
`(Ericsson)
`
`
`
`7 7
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 7
`
`

`

`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`5.1
`
`Maintenance of UTRA Release 99 – Release 9
`
`
`
`R1-10xxxx
`
`25.224 CR0249 (Rel-8, F) Clarification of establishment of uplink
`synchronization in CELL-PCH state
`25.224 CR0250 (Rel-9, A) Clarification of establishment of uplink
`CATT
`R1-102061
`synchronization in CELL-PCH state
`Decision: Both documents are noted. Revisions (R1) can be provided in R1-102477/2478 (CATT).
`Friday 16th
`R1-102477
`
`FDD
`
`5.1.1
`No inputs.
`
`5.1.2
`
`TDD
`25.221 CR0203 (Rel-8, F) Clarification of HS-SCCH/HS-DSCH/HS-
`R1-102058
`SICH association for HS-SCCH order
`Decision: The document is noted and CR is agreed.
`25.221 CR0204 (Rel-9, A) Clarification of HS-SCCH/HS-DSCH/HS-
`R1-102059
`SICH association for HS-SCCH order
`Decision: The document is noted and CR is agreed.
`
`
`R1-102060
`
`25.224 CR0249R1 (Rel-8, F) Clarification of establishment of uplink
`synchronization in CELL-PCH state
`25.224 CR0250R1 (Rel-9, A) Clarification of establishment of uplink
`R1-102478
`synchronization in CELL-PCH state
`CRs are withdrawn.
`
`
`25.225 CR0096 (Rel-7, F) Correction to the reference table number
`R1-102064
`for nominal maximum output power for 1.28Mcps TDD
`Decision: The document is noted and CR is agreed.
`25.225 CR0097 (Rel-8, A) Correction to the reference table number
`R1-102065
`for nominal maximum output power for 1.28Mcps TDD
`Decision: The document is noted and CR is agreed.
`25.225 CR0098 (Rel-9, A) Correction to the reference table number
`R1-102066
`for nominal maximum output power for 1.28Mcps TDD
`Decision: The document is noted and CR is agreed.
`
`
`
`25.221 CR0205R1 (Rel-8,F) Resource sharing between scheduled
`R1-102514
`and non-scheduled E-HICHs for LCR TDD
`Decision: The document is noted and CR is agreed.
`25.221 CR0206R1 (Rel-9,A) Resource sharing between scheduled
`R1-102515
`and non-scheduled E-HICHs for LCR TDD
`Decision: The document is noted and CR is agreed.
`
`
`
`25.222 CR0204 (Rel-8, F) Corrections to the Physical channel
`R1-102441
`mapping of 64QAM for HS-DSCH for 1.28Mcps TDD
`Decision: The document is noted and CR is agreed.
`25.222 CR0205 (Rel-9, A) Corrections to the Physical channel
`R1-102442
`mapping of 64QAM for HS-DSCH for 1.28Mcps TDD
`Decision: The document is noted and CR is agreed.
`
`4-carriers HSDPA
`5.2
`WID in RP-091438
`
`8 8
`
`CATT
`
`CATT
`
`CATT
`
`CATT
`
`CATT
`
`CATT
`
`CATT
`
`CATT
`
`
`
`
`
`
`
`
`
`(R1-102060)
`
`(R1-102061)
`
`
`
`
`
`
`
`New Postcom
`
`(R1-102233)
`
`New Postcom
`
`(R1-102234)
`
`ZTE
`
`ZTE
`
`
`
`
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 8
`
`

`

`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`5.2.1
`
`HS-DPCCH design
`
`
`
`R1-10xxxx
`
`
`Ericsson, ST-Ericsson
`Information mapping to physical control channels for 4C-HSDPA
`R1-101796
`The document was presented by Johan Bergman from Ericsson and discusses information mapping principles for further
`consideration.
`Decision: The document is noted.
`
`
`
`Ericsson, ST-Ericsson
`HS-DPCCH for 4C-HSDPA
`R1-101794
`The document was presented by Johan Hultell from Ericsson and proposes a 1xSF128 design for the HS-DPCCH in 4C-
`HSDPA. The performance is evaluated and compared to a solution in which two I/Q multiplexed HS-DPCCHs are used :
`• A ‘DTX codeword’ is added to the Rel-9 DC-HSDPA MIMO codebook.
`• When 4C-HSDPA is configured the Rel-9 DC-HSDPA-MIMO ACK/NACK codebook (with an added ‘DTX
`codeword’) shall be used.
`• Carriers not configured in MIMO mode use Rel-5 encoding of the CQI information. Carriers configured in
`MIMO mode use Rel-7 encoding for the CQI information.
`• A carrier specific CQI feedback cycle is supported for 4C-HSDPA.
`• A common CQI repetition factor is used for 4C-HSDPA.
`• The CQI information associated with carrier k is transmitted in consecutive manner if CQI repetition is used.
`1xSF128 HS-DPCCH scheme is used whenever 4C-HSDPA is configured.
`•
`• When carrier 3 and carrier 4 are deactivated the HARQ-ACK and the CQI messages are repeated.
`Discussion (Question / Comment): .
`Decision: The document is noted.
`
`
`
`Ericsson, ST-Ericsson
`On the benefit of HS-DPCCH optimizations for 3C-HSDPA
`R1-101795
`The document was presented by Johan Hultell from Ericsson and proposes an HS-DPCCH solution for 3C-HSDPA when
`MIMO is not configured on any carrier. It is concluded that there is no technical reasons to adopt a special HS-DPCCH
`solution for the 3C-HSDPA solution only:
`• The Rel-9 codebook is re-used for the HARQ-ACK transmissions with an additional DTX codeword.
`• ACK and NACK for carrier 3 use the code words ‘ACK/DTX’ and ‘NACK/DTX’ of the Rel-9 codebook.
`• Carrier-specific CQI cycles are supported.
`• The CQI repetition factor should be common for all carriers (as in previous releases).
`If carrier 3 is deactivated the HARQ-ACK and CQI messages of the activated carriers repeated.
`•
`• When CQI repetition is employed the CQI information associated with ‘carrier k’ is transmitted in a consecutive
`manner.
`• The minimum supported CQI feedback cycle when 3C-HSDPA is configured is 4ms.
`Discussion (Question / Comment): .
`Decision: The document is noted.
`
`
`
`Qualcomm Incorporated
`Link Analysis of HS-DPCCH for 4C-HSDPA
`R1-101988
`The document was presented by Arjun Bharadwaj from Qualcomm and provides link level simulation results for different
`HS-DPCCH design options. A design proposal is detailed in companion R1-101990.
`Discussion (Question / Comment): .
`Decision: The document is noted.
`
`
`Qualcomm Incorporated
`Further Cubic Metric Analysis of HS-DPCCH for 4C-HSDPA
`R1-101989
`The document was presented by Sharad Sambhwani from Qualcomm and concludes:
`• For the case when all 4 carriers are scheduled, 1xSF128 is superior in CM to 2xSF256
`• For the case when 2 carriers are scheduled ({C1,C2} or {C3,C4})
`o 1xSF128(ON/OFF) is inferior to 1xSF128(ON/POST)
`o 2xSF256(ON/OFF) is inferior to 1xSF128(ON/POST)
`o 2xSF256(OFF/ON) is inferior to 2xSF256(ON/OFF)
`o 2xSF256(OFF/ON) is inferior to 2xSF256(POST/ON)
`Based on this analysis alone, it is recommended to select 1xSF128 with the POST code word option as the HS-DPCCH
`scheme for 4C-HSDPA.
`Decision: The document is noted.
`
`
`
`
`9 9
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2009 - Page 9
`
`

`

`3GPP TSG RAN WG1 Meeting #61
`Montreal, Canada, 10 – 14 May, 2010
`
`
`
`
`R1-10xxxx
`
`
`
`•
`
`Qualcomm Incorporated
`HS-DPCCH design for 4C-HSDPA
`R1-101990
`The document was presented by Sharad Sambhwani from Qualcomm and proposes:
`• A Rel-10 3C/4C-HSDPA UE, when configured with single or dual cells with or without MIMO should use the
`legacy HS-DPCCH physical layer design (channel coding, spreading factor, modulation, CQI reporting) as
`specified in previous releases (Rel-5 through Rel-9).
`If upon receiving an HS-SCCH order from a NodeB corresponding to activation/de-activation of secondary HS-
`DSCH serving cells and secondary uplink frequency, if there are one or two active HS-DSCH serving cells
`remaining, a a Rel-10 3C/4C-HSDPA UE, should use the legacy HS-DPCCH physical layer design (channel
`coding, spreading factor, modulation, CQI reporting) as specified in previous releases (Rel-5 through Rel-9).
`• As a working assumption, RAN WG1 assumes that the 1st, 2nd and 3rd secondary HS-DSCH secondary serving
`cells will be indicated to the physical layer by higher layers. If two uplink frequencies are configured, the 1st HS-
`