R1-08xxxx
`
`
`
`
`
`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`Agenda item
`3
`Title:
` Final Report of 3GPP TSG RAN WG1 #53 v1.0.0
`
`
`(Kansas City, USA, 5 – 9 May, 2008)
`Document for:
` Approval
`Source:
`
`MCC Support
`
`
`
`
`
`
`
`Fact Summary
`Meeting:
`Dates:
`Venue:
`Host:
`Attendees:
`Documents:
`
`
`3GPP TSG RAN WG1 #53
`5th through 9th May, 2008
`Kansas City Marriott Downtown, Missouri - USA
`North American Friends of 3GPP
`174 delegates
`561 (including some withdrawn and post-meeting artefacts)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Patrick Mérias
`ETSI Mobile Competence Center
`F-06921 Sophia Antipolis Cedex
`Tel: +33 4 92 94 42 06
`
`Patrick.merias@etsi.org
`
`1
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 1
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`Table of contents
`
`
`
`R1-08xxxx
`
`
`Executive summary ......................................................................................................................................... 3
`1. Opening of the meeting ........................................................................................................................ 5
`1.1
`Call for IPR ....................................................................................................................................................... 5
`2.
`Approval of the agenda ......................................................................................................................... 5
`3.
`Approval of the minutes from previous meeting ............................................................................... 5
`4.
`Liaison statement handling .................................................................................................................. 6
`5. Maintenance of UTRA Release 99 – Release 8 ............................................................................. 11
`6.
`Study Item on LTE-Advanced ............................................................................................................ 14
`6.1
`Review of LTE-Advanced Requirements ................................................................................................... 14
`6.2
`Discussion on Physical Layer Aspects LTE-Advanced Proposals ......................................................... 17
`7. Maintenance of Evolved UTRA and UTRAN ................................................................................... 23
`7.1
`Corrections for TS 36.211 ............................................................................................................................ 23
`7.1.1
`Downlink Control Signaling .................................................................................................................... 23
`7.1.2
`Uplink Control Signalling ......................................................................................................................... 29
`7.1.3
`Other remaining issues for TS 36.211 .................................................................................................. 33
`7.1.4
`Possible vote on removal of small delay CDD and eNodeB antenna selection ............................. 43
`7.2
`Corrections for TS 36.212 ............................................................................................................................ 44
`7.3
`Corrections for TS 36.213 ............................................................................................................................ 47
`7.3.1
`Timing synchronization ........................................................................................................................... 47
`7.3.2
`Inter-cell Interference Coordination ....................................................................................................... 47
`7.3.3
`UE Procedures for downlink shared channel ...................................................................................... 49
`7.3.4
`Other remaining issues for TS 36.213 .................................................................................................. 51
`7.4
`Corrections for TS 36.214 ............................................................................................................................ 53
`7.5
`Corrections for TS 36.306 ............................................................................................................................ 54
`8
`Enhanced Uplink for CELL_FACH State in FDD ............................................................................ 56
`9
`HS-PDSCH serving cell change enhancements ............................................................................. 60
`10 Study Item on Dual-Cell HSDPA Operation ..................................................................................... 61
`11. 64QAM for 1.28 Mcps TDD HSDPA ................................................................................................. 64
`12 Enhanced CELL_FACH state in 1.28 Mcps TDD (UL/DL) ............................................................ 64
`13 Continuous Connectivity for packet data users for 1.28Mcps TDD ............................................. 64
`14 Study Item on Scope of future HSPA Evolution for 1.28Mcps TDD ............................................. 64
`15 Closing of the meeting ........................................................................................................................ 65
`Annex A: List of participants at RAN1#53 ............................................................................................... 66
`Annex B: TSG RAN WG1 meetings in 2008 .......................................................................................... 67
`Annex C: List of CRs agreed at RAN1#53 .............................................................................................. 68
`Annex D: List of Outgoing LSs from RAN1#53 ...................................................................................... 72
`Annex E: List of Tdocs at RAN1 #53 ....................................................................................................... 74
`Annex F: List of actions ............................................................................................................................. 75
`
`
`
`2 2
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 2
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`
`
`
`R1-08xxxx
`
`Executive summary
`3GPP TSG WG RAN1 #53 meeting took place at Marriott Downtown hotel in Kansas City, USA.
`
`The meeting started at 9:10 on Monday 5th May and finished at 17:10 on Friday 9th May 2008.
`
`
`
`The week was scheduled as follows:
`
`• Monday: Common session on Agenda items 1, 2, 3, 6.1 and 6.2.
`
`• Tuesday morning: Early session chaired by Juho Lee on AI 7.1.1. Common session on AI 4. Discussion on LTE-
`Advanced Requirements chaired by Takehiro Nakamura in parallel with AI 5 chaired by Dirk Gerstenberger.
`
`• Tuesday afternoon: Agenda items 4, 7.1.1, 7.1.2 and 7.1.4.
`
`• Wednesday: HSPA FDD (AI 8, 9 and 10) + HSPA TDD (AI 13 and 14) chaired by Dirk Gerstenberger. Channel
`coding (AI 7.2), UE categories (AI 7.5) chaired by Sadayuki Abeta. CQI (AI 7.3.3) chaired by Juho Lee.
`
`• Thursday: parallel sessions in the morning on AI 7.1.3 followed by AI 7.1.2 and 7.3.4
`
`• Friday morning: Agenda items 7.3.1, 7.4 and 7.3.2.
`
`• 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 540, and those documents were categorized as followed.
`
`Agenda Item
`Liaison statement handling
`Maintenance of UTRA R99 – Rel8
`Maintenance of Evolved UTRA and UTRAN
`Study item on LTE-Advanced
`Enhanced Uplink for CELL_FACH State in FDD
`HS-PDSCH serving cell change enhancements
`Study item on Dual-Cell HSDPA Operation
`64QAM for 1.28Mcps TDD HSDPA
`Enhanced CELL_FACH in 1.28Mcps TDD (UL/DL)
`Continuous Connectivity for Packet Data users for
`1.28Mcps TDD
`Study Item on Scope of future HSPA Evolution for
`1.28Mcps TDD
`
`Input
`Document
`32
`21
`394
`43
`20
`5
`19
`0
`0
`1
`
`Discussed
`Document
`25
`21
`145
`40
`20
`5
`19
`
`
`1
`
`5
`
`5
`
`
`
`
`
`3 3
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 3
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`The following set of documents is missing. The corresponding contributions have not been handed over by companies.
`
`
`
`R1-08xxxx
`
`
`
`
`
`R1-081772
`
`Modification of Cyclic Shift Hopping for CQI
`
`R1-082038
`
`Search space design for PDCCH blind decoding
`
`R1-082040
`
`Distributed Resource Allocation Signalling on PDCCH
`
`ZTE
`
`Philips, NXP
`
`Philips, NXP
`
`R1-082132
`
`DTX Detection Performance of ACK/NACK on PUSCH
`
`Ericsson
`
`4 4
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 4
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`
`
`
`R1-08xxxx
`
`Opening of the meeting
`1.
`Mr. Dirk Gerstenberger (RAN1 Chairman) welcomed the participants to the 53 RAN WG1 meeting and opened the
`meeting at 09:10.
`
`Mr. Sharat Chander from AT&T welcomed the delegates on behalf of the North American Friends of 3GPP.
`
`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:
`
`•
`
`•
`
`
`
`2.
`
`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 the agenda
`
`
`RAN1 Chairman
`Draft Agenda for RAN1#53 meeting
`R1-081710
`Dirk Gerstenberger (Chairman) proposed the agenda for the meeting. Focus of first day is to discuss the LTE Advanced
`topic and Mr. Chairman asked kindly company to concentrate on fixed time for presentation and questions (10 – 15
`minutes).
`
`Discussion (Question / Comment):
`Decision: The agenda was approved.
`
`
`
`3.
`
`Approval of the minutes from previous meeting
`
`Final report of RAN1#52bis meeting
`R1-081711
`The document was presented by Patrick Mérias.
`
`Discussion (Question / Comment):
`Decision: The document is noted and approved.
`
`MCC Support
`
`
`
`5 5
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 5
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`
`
`
`4.
`
`Liaison statement handling
`
`R1-08xxxx
`
`= SP-080218
`TSG SA, Ericsson
`LS on Release 8 non-essential SAE features
`R1-081715
`The document was presented by Erik Dahlman from Ericsson and discusses the SAE features classified as non-essential
`and agreed on Release 8.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`= S2-083168
`SA2, NTT DoCoMo
`LS on Earthquake and Tsunami Warning System
`R1-081719
`The document was presented by Sadayuki Abeta from NTT DoCoMo and informs RAN1 that SA2 has selected a CBS
`based solution with enhancements for Rel-8 ETWS.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`= S4-080256
`SA4, Qualcomm
`LS Request for Evaluation Framework Link Level Data
`R1-081720
`The document was presented by Juan Montojo from Qualcomm and shows SA4 work progress in specifying a dynamic
`video rate adaptation feature for MTSI video (MTSI_DRASIS) and SA4 request in developing a framework for evaluating
`the performance of rate adaptation protocols.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Qualcomm Europe
`LTE Link Level Throughput Data for SA4 Evaluation Framework
`R1-081955
`The document was presented by Juan Montojo from Qualcomm and proposes data (link-level MAC PDU payload data) to
`be sent to SA4 for their evaluation framework.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Draft LS response to Request for Evaluation Framework Link
`R1-081954
`Level Data
`The document was presented by Juan Montojo from Qualcomm
`
`Qualcomm Europe
`
`
`
`Discussion (Question / Comment):
`Decision: Document is noted and shall be revisited in R1-082084 later this week.
`
`Friday 9th
`
`LS response to Request for Evaluation Framework Link Level Data
`R1-082084
`Decision: Document is agreed.
`
`RAN1, Qualcomm
`
`(R1-081954)
`
`
`
`LS on Decision of MBMS and LCS in SAE Rel8 Scope
`R1-081716
`Discussions
`The document was presented by Sadayuki Abeta from NTT DoCoMo.
`
`TSG SA, NTT DoCoMo
`
`= SP-080223
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`R1-081718
`
`LS on PDCCH for DL data arrival and random access response
`format
`
`RAN2, Qualcomm
`
`= R2-082040
`
`6 6
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 6
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`The document was presented by Juan Montojo from Qualcomm and asks RAN1 to provide answers to the following
`questions:
`
`
`
`R1-08xxxx
`
`• which PDCCH format to use for DL data arrival
`
`•
`
`how to indicate that the PDCCH is used for DL data arrival (versus regular grant)
`
`• which PDCCH fields should be used to indicate the 6-bit preamble and the FFS fields
`
`• RAN2 would like RAN1 to indicate the maximum number of PRACH in a TDD subframe.
`
`• what is the UE turn around time to issue PRACH in response to PDCCH for DL data arrival
`
`• Provide the list of fields and size for the grant in the random access response
`
`• what is the UE turn around time between the reception of random access response and UL-SCH transmission
`
`•
`
`confirm that RAN1 plans to capture the timing relationship for DL data arrival and PUSCH transmission in
`response to the random access response in the RAN1 specifications
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Qualcomm Europe
`Details on UL grant portion of RACH MSG2
`R1-081977
`The document was presented by Juan Montojo from Qualcomm and suggests a reduced set of fields to indicate an UL
`grant that fits into the RAR format and proposed to agree on the timing of the uplink grant relative to the reception of
`RAR.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Nokia, Nokia Siemens
`(R1-081840)
`UL grant for random access message 3
`R1-082078
`Networks
`The document was presented by Jari Lindholm from NSN and proposes content of the UL grant in preamble response as
`shown in Table 1 of R1-082078. All the necessary information in 21 bits would optimize the size for the MAC message.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`Panasonic
`Reply of RAN2 LS of RACH
`R1-081802
`The document was presented by Hidetoshi Suzuki from Panasonic and proposes some of the reply on R1-081718 LS.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Qualcomm Europe
`Details on PDCCH for DL data arrival
`R1-081978
`The document was presented by Juan Montojo from Qualcomm and provides the following 3 proposals:
`
`• Proposal 1: use the smallest PDCCH format (format 1C) to indicate DL data arrival
`
`• Proposal 2: use the UEID for masking the CRC to indicate the use of PDCCH for DL data arrival for the specific
`UE
`
`• Proposal 3 When PDCCH is used to allocate a dedicated preamble in subframe N, UE must transmit on PRACH
`in the first PRACH occasion with subframe number equal to or greater than N+4+Time Location (only for TDD).
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`7 7
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 7
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`
`
`
`R1-08xxxx
`
`Nokia, Nokia Siemens
`
`PDCCH format for allocation of dedicated preambles
`R1-081839
`Networks
`The document was presented by Jari Lindholm from NSN and proposes answers to the questions of R1-081718 concerning
`allocation of dedicated preambles:
`
`• which PDCCH format to use for DL data arrival
`o Format 0/1A.
`• how to indicate that the PDCCH is used for DL data arrival (versus regular grant)
`o All “1” RB assignment field indicates that the grant is for dedicated preambles.
`• which PDCCH fields should be used to indicate the 6-bit preamble and the FFS fields
`o Physical layer extracts the RB bits and forwards the rest of the bits to MAC. RAN2 can freely design
`their use.
`
`• RAN2 would like RAN1 to indicate the maximum number of PRACH in a TDD subframe.
`o The maximum number is six so that three bits are needed for indicating the frequency allocation in case
`of TDD.
`
`• what is the UE turn around time to issue PRACH in response to PDCCH for DL data arrival
`o UE should be able to start the preamble transmission when 4 ms has passed from the end of the subframe
`containing the PDCCH entry.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`Based on the above set of contributions, discussion should continue offline between interested parties, and revisit later for
`a joint proposal (Qualcomm) 2194
`
`Friday 9th
`
`[Draft] LS reply on PDCCH for DL data arrival and random access
`
`Qualcomm Europe
`R1-082194
`response format
`Decision: Document is noted without been presented during the session. LS is for email approval until May 16th
`
`
`
`
`
`Ericsson
`Draft LS on power headroom reporting
`R1-082021
`The document was presented by Ylva Jading from Ericsson and outlines RAN1 decisions on Power Headroom reporting.
`
`Discussion (Question / Comment):
`Decision: Document is noted and final LS is agreed in R1-082096.
`
`
`
`= R2-082048
`RAN2, Ericsson
`LS on RAN2 assumptions on L1
`R1-082029
`The document was presented by Erik Dahlman from Ericsson and informs RAN1 about a number of assumptions made
`about L1 and L1 specifications. RAN2 requests confirmation that the listed aspects are captured in L1 specifications.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Preamble sequence selection
`R1-081944
`The document was presented by Dragan Vujcic from LGE
`
`LG Electronics
`
`
`
`8 8
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 8
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`Discussion (Question / Comment): Panasonic indicates that RAN1 has already informed RAN2 that preamble selection
`should be in the RAN2 specs in R1-071838. Ericsson proposes to say yes to all 6 points and Panasonic agrees this.
`Decision: Document is noted. LS shall be prepared in R1-082098.
`
`R1-08xxxx
`
`
`
`Friday 9th
`
`Draft LS response on RAN2 assumptions on L1
`R1-082098
`Decision: Document is noted and final LS is agreed in R1-082195
`
`
`
`
`Ericsson
`
`
`
`= R2-082039
`RAN2, Ericsson
`LS on Transmission of physical layer parameters
`R1-081717
`The document was presented by Erik Dahlman from Ericsson and aims to further clarify when certain parameters are
`needed by the UE in order to place them the correct messages or possibly specify default configurations in the
`specification.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`R1-082022
`
`Response on RAN2 LS on transmission of Physical Layer
`parameters
`The document was presented by Erik Dahlman from Ericsson.
`
`Ericsson
`
`Discussion (Question / Comment):
`Decision: Document is noted. Response shall be revised in R1-082099.
`
`Friday 9th
`
`Draft Response to LS on Transmission of physical layer parameters
`R1-082099
`Decision: Document is noted and final LS is agreed in R1-082196
`
`Ericsson
`
`
`
`
`
`R1-082054
`
`Physical-layer parameters to be configured by RRC
`
`Ericsson
`
`
`
`
`
`
`
`
`Physical-layer parameters to be configured by RRC, explanations Ericsson
`R1-082055
`R1-082054 was presented by Erik Dahlman from Ericsson and summarizes the current assumption regarding Layer-1-
`related parameters to be configured by higher layers.
`
`R1-082055 is attached as explanation of the set of parameter tables.
`
`Discussion (Question / Comment):
`Decision: Documents are noted. R1-082054 shall be revised in R1-082101 and LS to RAN2 shall be prepared in R1-
`082102.
`
`Friday 9th
`
`Ericsson
`Physical-layer parameters to be configured by RRC
`R1-082148
`The document was presented by Erik Dahlman from Ericsson. Tdoc number R1-082101 is avoided.
`
`(R1-082054)
`
`Discussion (Question / Comment):
`Decision: Document is noted and agreed in R1-082199 without Dynamic-cyclic-shift entry under UL RS. The final LS to
`RAN2 is agreed in R1-082200.
`
`
`
`
`
`9 9
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 9
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`
`
`
`Draft response to LS on change rate of Physical Layer
`R1-082082
`parameters
`The document was presented by Erik Dahlman from Ericsson.
`
`R1-08xxxx
`
`Ericsson
`
`
`
`Discussion (Question / Comment):
`Decision: Document is noted and shall be further discussed off line to refine the content of the LS.
`
`Friday 9th
`
`Draft response to LS on change rate of Physical Layer
`R1-082147
`parameters
`Decision: Document is noted and final LS is agreed in R1-082201.
`
`Ericsson
`
`(R1-082082)
`
`
`
`
`
`10 10
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 10
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`
`
`
`R1-08xxxx
`
`5.
`
`Maintenance of UTRA Release 99 – Release 8
`
`
`
`R1-081878
`
`25.212 CR0262r1 (Rel-8, B) HS-SCCH orders for HS-SCCH-less
`operation
`25.214 CR0483r3 (Rel-8, B) HS-SCCH orders for HS-SCCH-less
`(R1-081879)
`Ericsson
`R1-082085
`operation
`Both documents were presented by Johan Bergman from Ericsson. These CRs introduce HS-SCCH orders for activation
`and deactivation of HS-SCCH-less operation.
`
`Ericsson
`
`
`
`Discussion (Question / Comment):
`Decision: Documents are noted and both CRs are agreed.
`
`
`
`25.211 CR0253 (Rel-6, F) Correction to E-DCH control channel
`R1-081886
`timing
`The document was presented by Aziz Gholmieh from Qualcomm
`
`Qualcomm Europe
`
`
`
`Discussion (Question / Comment): WI code should be revisited. Discussion to which Release this CR should apply.
`Decision: Document is noted. Decision to create Release 7 CR and Release 8 shadow CR in R1-082089.
`
`Friday 9th
`
`25.211 CR0253 & CR0255 (Rel-7, F; Rel-8, A) Correction to E-DCH
`R1-082089
`control channel timing
`The document was presented by Sharad Sambhwani from Qualcomm.
`
`Qualcomm Europe
`
`(R1-081886)
`
`Discussion (Question / Comment): Is there 25.214 CR available? Asked by NSN
`Decision: Document is noted and CR is agreed, conditional that the corresponding CR to 25.214 is agreed via email
`reflector by May 16th
`
`
`
`
`
`25.214 CR0484 & CR0485 (Rel-7, F; Rel-8, A), Correction to E-
`R1-081894
`DPCCH gain factor calculation
`The document was presented by Antti Hiltunen from Nokia.
`
`Nokia, Nokia Siemens
`Networks
`
`
`
`Discussion (Question / Comment):
`Decision: Document is noted and CRs are agreed. MCC shall make sure CR cover sheet is properly filled with CR
`numbers prior submitting to plenary.
`
`
`
`R1-082049
`
`25.214 CR0486 (Rel-7, F) Clarification of burst transmission
`during DTX transitions
`25.214 CR0487 (Rel-8, A) Clarification of burst transmission
`R1-082050
`during DTX transitions
`Both documents were presented by Aziz Gholmieh from Qualcomm
`
`Qualcomm Europe
`
`Qualcomm Europe
`
`Discussion (Question / Comment):
`Decision: Documents are both withdrawn.
`
`
`
`R1-082051
`
`25.214 CR0488 (Rel-7, F) Correction to attachment method for
`HS-DSCH in the URA_PCH or CELL_PCH state
`25.214 CR0489 (Rel-8, A) Correction to attachment method for
`R1-082052
`HS-DSCH in the URA_PCH or CELL_PCH state
`Both documents were presented by Aziz Gholmieh from Qualcomm
`
`Qualcomm Europe
`
`Qualcomm Europe
`
`
`
`
`
`
`
`
`
`Discussion (Question / Comment): Motivation for correction to Release 7 doesn’t seem to reach consensus.
`
`11 11
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 11
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`Decision: Documents are noted. Discussion should continue to confirm the need of such CR into Release 8.
`
`
`
`R1-08xxxx
`
`
`
`25.215 CR0188 (Rel-8, B), E-UTRA measurements for UTRA –
`R1-081895
`E-UTRA interworking
`The document was presented by Karri Ranta-aho from NSN
`
`Nokia, Nokia Siemens
`Networks
`
`
`
`Discussion (Question / Comment): Ericsson indicated that the RSRQ measurements in CELL_PCH/URA_PCH could be
`included in this version of the CR.
`Decision: Document is noted. Check the applicable states for RSRQ during the week and revisit.
`
`Friday 9th
`Decision: Ericsson commented that they agree with the CR. CR is agreed.
`
`
`
`
`
`
`Ericsson
`EUL coverage enhancements
`R1-081880
`The document was presented by Johan Bergman from Ericsson and provides input on potential enhancements –
`“Autonomous retransmissions” and “Improved power control at UE power limitation” – taking into account the feedback
`received from other companies during RAN1#52bis.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Qualcomm Europe
`Power Scaling and EUL Coverage
`R1-082053
`The document was presented by (…) from Qualcomm and shows that equal scaling of uplink channels provides better
`EUL cell coverage for AMR 12.2 VoIP compared to the current scaling. The paper concludes with 2 proposals:
`
`• Proposal 1: βed,k,min to be configurable by the network which can set it to higher values (> 8/15) in order to
`increase EUL coverage
`
`• Proposal 2: Further studies to be performed to determine EUL coverage for different TTIs, power gains and
`βed,k,min settings and compare it to Release 99
`Discussion (Question / Comment): Philips commented that the effects on HS-DPPCH were missing.
`Decision: Document is noted.
`Based on the above contributions, Mr. Chairman suggests letting the discussion continue until next meeting and look at
`further simulation results for decision. The question remains: does RAN1 want to introduce equal scaling and/or TTI
`bundling into Rel-8?
`
`
`
`NextWave Wireless
`25.221 CR0156 (Rel-7,cat-F) "Applicability of sync case 2"
`R1-081906
`NextWave Wireless
`25.221 CR0157 (Rel-8,cat-A) "Applicability of sync case 2"
`R1-081907
`Both documents were presented by Nick Anderson from NextWave Wireless.
`
`
`
`
`Discussion (Question / Comment): Ericsson asked for the gain having only sync case 1 for dedicated carriers and
`removing case 2. Answer is “UE simplification”.
`Decision: Documents are noted and CRs are agreed. Check progress both in RAN4 and RAN5 to see whether it’s
`necessary to inform them on the decision taken.
`
`
`
`25.223 CR0053 (Rel-7, F) Correction of uplink multicode
`
`CATT
`R1-081774
`capability for 1.28Mcps TDD EUL
`The document was presented by Ke Wang from CATT and brings consistency between 25.221 and 25.223.
`
`Discussion (Question / Comment):
`
`12 12
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 12
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`Decision: Document is noted and CR is agreed. CATT shall prepare the relevant shadow CR to Release 8 (R1-082093)
`
`R1-08xxxx
`
`
`
`Friday 9th
`
`25.223 CR0054 (Rel-8, A) Correction of uplink multicode capability for
`R1-082093
`1.28Mcps TDD EUL
`Decision: Document is noted and CR is agreed.
`
`CATT
`
`
`
`
`
`
`
`Introduction of 25.321CR(Rel-7) on 1.28Mcps TDD EUL TBS
`R1-081936
`table change
`The document was presented by Chen Ying from TD-Tech.
`
`RITT, TD Tech, CATT,
`ZTE, Spreadtrum
`
`
`
`Discussion (Question / Comment):
`Decision: Document is noted. The content is endorsed from RAN1 perspective (this can be communicated to RAN2
`delegates).
`
`13 13
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 13
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`
`
`
`Study Item on LTE-Advanced
`6.
`The main conclusions from the workshop are:
`
`
`
`R1-08xxxx
`
`• LTE Advanced shall be an evolution of LTE.
`o LTE terminal shall be supported in LTE-advanced networks.
`o An LTE-Advanced terminal can work in an LTE part of the network.
`o Primary focus of LTE-Advanced is low mobility users.
`• All requirements/targets in TR25.913 apply to LTE-Advanced.
`LTE-Advanced requirements shall fulfil IMT-Advanced requirements within the ITU-R time plan.
`• For LTE-Advanced:
`o Same inter-RAT interworking capability with at least same performance as in LTE Release 8
`Intra-RAT handover performance shall be same or better than LTE Release 8
`o
`• As a way forward for LTE-Advanced it was agreed:
`o TSG RAN email reflector specific to LTE-Advanced is now up and running
`o TR 36.913 "Requirements for LTE-Advanced" does exist and will be further updated by RAN WG
`meetings in May 2008.
`
`
`
`Review of LTE-Advanced Requirements
`6.1
`Based on the outcomes of the 3GPP RAN IMT-Advanced Workshop organized in Shenzhen (7-8 April 2008), focus on
`reviewing the requirements from a RAN1 perspective.
`
`Summary of the outcome from the WS:
`
`http://www.3gpp.org/ftp/workshop/2008-04-07_RAN_IMT_Advanced/Docs/REV-080058.zip
`
`LTE-Advanced rapporteur
`Skeleton of TR36.913"Requirements for LTE-Advanced"
`R1-081946
`
`(NTT DoCoMo)
`The document was presented by Takehiro Nakamura from NTT DoCoMo and shows the first attempt for drafting TR
`36.913.
`
`Discussion (Question / Comment):Yukitsuna Furuya (KDDI) highlighted the important requirement that LTE-Advanced
`goal is to decrease the cost of infrastructure. Response is that section 13 covers this.
`Decision: Document is noted and shall be revised in R1-082072.
`
`Friday 9th
`R1-082072 is endorsed from RAN1 perspective.
`
`
`
`
`
`R1-082070
`
`Operator Views on requirements for LTE-Advanced
`
`NTT DoCoMo, AT&T,
`CMCC, Orange, Telecom
`Italia, Telefonica, T-
`Mobile, Vodafone
`The document was presented by Takehiro Nakamura from NTT DoCoMo and shows high-level views of co-source
`operators on the LTE-Advanced requirements. Some text proposals on the requirements are also included in the
`contribution. Main goal is:
`
`
`
`•
`
`to exchange high-level views on the requirements with RAN delegates before making text proposal so that TR
`36.913 can efficiently be developed.
`
`14 14
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2004 - Page 14
`
`

`

`3GPP TSG RAN WG1 Meeting #53
`Kansas City, USA, 5 – 9 May, 2008
`
`Discussion (Question / Comment): Motorola requested clarification of the figure for VoIP capacity (up to 300 concurrent
`VoIP). There were also discussion w.r.t latency and spectrum efficiency requirements.
`Decision: Document is noted.
`
`R1-08xxxx
`
`
`
`
`
`
`Vodafone Group
`Review of LTE advanced requirements
`R1-081998
`The document was presented by Prakash Bhat from Vodafone and provides further considerations on the requirements and
`evaluation of LTE-Advanced, specifically:
`
`• Proposals regarding peak data rate and bandwidths
`• Addition of potential scenarios
`• Key points for a review of the evaluation methodology
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`Views on Requirements for LTE-Advanced
`R1-081947
`The document was presented by Motohiro Tanno from NTT DoCoMo.
`
`NTT DoCoMo
`
`
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`
`CEWiT
`IMT Advanced RAN1 Requirements - An India Perspective
`R1-081714
`The document was presented by Vinosh James from CEWiT and focuses on some essential features of the air-interface and
`discusses the basic framework for the development of the technologies capable of satisfying the requirements from an
`Indian perspective.
`
`Discussion (Question / Comment): Mr. Chairman asked the motivation behind the sentence “…that large numbers of UE
`remain in the cell-edges…” The answer is to focus on small area…
`Decision: Document is noted.
`
`
`R1-081721
`Requirement for LTE-Advanced
`Samsung
`
`The document was presented by Juho Lee from Samsung. Same paper as the one presented during the workshop.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`
`LG Electronics
`On the requirements for LTE-advanced
`R1-081808
`The document was presented by Young woo Yun from LGE and discusses aspects that need to be clarified before final
`resolution on the requirements for LTE-advanced such as the meaning of system performance requirements (bandwidth,
`cell sp