R1-082771
`
`
`
`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`Agenda item
`Title:
`
`Document for:
`Source:
`
`
`
`
`3
` Final Report of 3GPP TSG RAN WG1 #53bis v1.0.0
`
`(Warsaw, Poland, 30 June – 4 July, 2008)
` Approval
`MCC Support
`
`
`
`
`
`
`Fact Summary
`Meeting:
`Dates:
`Venue:
`Host:
`Attendees:
`Documents:
`
`
`3GPP TSG RAN WG1 #53bis
`30th June through 4th July, 2008
`Hilton Warsaw Hotel & Convention Center, POLAND
`European Friends of 3GPP
`170 delegates
`495 (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 2005 - Page 1
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`Table of contents
`
`R1-082771
`
`
`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 ............................................................................. 15
`6
`Maintenance of Evolved UTRA and UTRAN ................................................................................... 17
`6.1
`Finalization of TS 36.211 .............................................................................................................................. 17
`6.2
`Finalization of TS 36.212 .............................................................................................................................. 27
`6.3
`Finalization of TS 36.213 .............................................................................................................................. 34
`6.4
`Finalization of TS 36.214 .............................................................................................................................. 41
`6.5
`Finalization of TS 36.306 .............................................................................................................................. 42
`7
`HS-PDSCH Serving Cell Change Enhancements .......................................................................... 43
`8
`Dual-Cell HSDPA Operation on Adjacent Carriers ......................................................................... 44
`9
`Enhanced CELL_FACH state in 1.28 Mcps TDD (UL/DL) ............................................................ 47
`10 Continuous Connectivity for packet data users for 1.28Mcps TDD ............................................. 48
`11 MIMO for 1.28Mcps TDD .................................................................................................................... 49
`12 Study Item on LTE-Advanced ............................................................................................................ 50
`13 Closing of the meeting ........................................................................................................................ 57
`Annex A: List of participants at RAN1 #53bis......................................................................................... 58
`Annex B: TSG RAN WG1 meetings in 2008/2009 ................................................................................ 59
`Annex C: List of CRs agreed at RAN1#53bis ......................................................................................... 60
`Annex C1:
` List of CRs agreed in principle at RAN1#53bis ............................................................. 61
`Annex D: List of Outgoing LSs from RAN1#53bis ................................................................................. 62
`Annex E: List of Tdocs at RAN1 #53bis .................................................................................................. 63
`Annex F: List of actions ............................................................................................................................. 64
`
`
`
`2 2
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 2
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`
`R1-082771
`
`Executive summary
`3GPP TSG WG RAN1 #53bis meeting took place at Hilton Warsaw Hotel & Convention Center Intercontinental Warsaw,
`POLAND.
`
`The meeting started at 9:10 on Monday 30th June and finished at 17:30 on Friday 4th July 2008.
`
`
`
`The week was scheduled as follows:
`
`• Monday: Common session on Agenda items 1, 2, 3, 4 and 6.4.
`
`• Tuesday: Common session focuses on TS 36.211 issues (Agenda item 6.1) and TS 36.306 (Agenda item 6.5).
`
`• Wednesday: Parallel sessions on Agenda items 5, 7, 8, 10 and 11 chaired by Dirk Gerstenberger and on TS 36.212
`(Agenda item 6.2) chaired by Sadayuki Abeta-san.
`
`• Thursday: Common session on Agenda item 12 on the technical areas and related proposals for LTE-Advanced.
`
`• Friday morning: Common session focuses on TS 36.213 issues (Agenda item 6.3).
`
`• 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 479, and those documents were categorized as followed.
`
`Agenda Item
`Liaison statement handling
`Maintenance of UTRA R99 – Rel8
`Maintenance of Evolved UTRA and UTRAN
`HS-PDSCH serving cell change enhancements
`Dual-Cell HSDPA Operation on Adjacent Carriers
`Enhanced CELL_FACH State in 1.28Mcps TDD
`(UL/DL)
`Continuous Connectivity for Packet Data users for
`1.28Mcps TDD
`MIMO for 1.28Mcps TDD
`Study Item on LTE-Advanced
`
`Input
`Document
`55
`17
`321
`6
`18
`0
`
`Discussed
`Document
`51
`17
`142
`4
`15
`0
`
`5
`5
`52
`
`5
`5
`30
`
`
`
`
`
`3 3
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 3
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`The following set of documents is missing. The corresponding contributions have not been handed over by companies.
`
`R1-082771
`
`
`
`
`
`R1-082321
`
`36.213 CR0042 (Rel-8, F) Clarification on resource allocation type 1
`
`Samsung
`
`R1-082332
`
`Further Results on DC Subcarrier on UL
`
`R1-082406
`
`CQI/PMI/RI configuration parameters
`
`R1-082457
`
`ACK/NAK mapping for extended cyclic prefix on PUCCH
`
`Motorola
`
`Panasonic
`
`Ericsson
`
`R1-082552
`
`UL ACK/NAK assignment procedure
`
`Qualcomm Europe
`
`R1-082750
`
`Discussion on RSN for BCCH message
`
`R1-082758
`
`SI-X tables
`
`Huawei
`
`Motorola
`
`4 4
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 4
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`
`R1-082771
`
`Opening of the meeting
`1.
`Mr. Dirk Gerstenberger (RAN1 Chairman) welcomed the participants to the 53bis RAN WG1 meeting and opened the
`meeting at 09:10.
`
`Mr. Christian Gerlach from Alcatel-Lucent welcomed the delegates on behalf of the European 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
`
`Draft Agenda for RAN1#53bis meeting
`R1-082271
`Dirk Gerstenberger (Chairman) proposed the agenda for the meeting.
`
`RAN1 Chairman
`
`
`
`Discussion (Question / Comment):
`Decision: The agenda was approved.
`
`
`3.
`
`Approval of the minutes from previous meeting
`
`Final report of RAN1#53 meeting
`R1-082272
`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 2005 - Page 5
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`
`Liaison statement handling
`4.
`NON LTE liaison statement
`
`Reply LS on E-AICH Power Offset and Error Targets for AICH/E-
`R1-082274
`AICH
`The document was presented by Sharad Sambhwani from Qualcomm.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`R1-082771
`
`RAN2, Qualcomm
`
`= R2-082804
`
`LS on allowing DTX on E-DPCCH
`R1-082288
`The document was presented by Sharad Sambhwani from Qualcomm.
`
`RAN5, Qualcomm
`
`= R5-081450
`
`Discussion (Question / Comment):
`Decision: Document is noted. R1-082640 is reserved for reply LS to RAN5/cc RAN2 after off line discussion with RAN2.
`Reply LS shall be reviewed by Wednesday.
`
`Wednesday 2nd
`
`Draft Reply LS on allowing DTX on E-DPCCH
`R1-082681
`The document was presented by Sharad Sambhwani from Qualcomm.
`
`Qualcomm Europe
`
`(R1-082640)
`
`Discussion (Question / Comment): NSN will provide inputs to elaborate more detailed response. Option 1 is agreed.
`Decision: Document is noted. Revision in R1-082687 shall be prepared by the end of the week.
`
`Friday 4th
`
`Reply LS on allowing DTX on E-DPCCH
`R1-082687
`Decision: Document is noted and final LS is agreed in R1-082759.
`
`Qualcomm Europe
`
`
`
`
`
`Reply LS on 1.28 Mcps TDD HS-DSCH physical layer categories
`R1-082275
`and related transport block sizes for 64-QAM modulation
`The document was presented by (…) from TDD Tech
`
`RAN2, TD Tech
`
`= R2-082805
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`LTE liaison statement
`
`• Earthquake and Tsunami Warning System
`
`= R2-082883
`RAN2, NTT DoCoMo
`Reply LS on Earthquake and Tsunami Warning System
`R1-082277
`The document was presented by Sadayuki Abeta from NTT DoCoMo and shows current RAN2 status w.r.t the study
`performed for the delivery mechanisms of ETWS notifications over the E-UTRAN air interface.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`SA2, NTT DoCoMo
`LS on Earthquake and Tsunami Warning System
`R1-082290
`The document was presented by Sadayuki Abeta from NTT DoCoMo for information.
`
`= S2-084460
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`6 6
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 6
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`
`R1-082771
`
`SA2, NTT DoCoMo
`Reply LS on Earthquake and Tsunami Warning System
`R1-082638
`The document was presented by Sadayuki Abeta from NTT DoCoMo for information.
`
`= S2-085267
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`• New PDCCH Format 1C
`
`= R2-082885
`RAN2, Qualcomm
`Reply LS on information about new PDCCH Format 1C
`R1-082278
`The document was presented by Juan Montojo from Qualcomm and provides information about the size and multiplicity
`of Random Access Response, BCCH and PCCH messages from RAN2.
`
`Discussion (Question / Comment):
`Decision: Document is noted. Related contributions under AI 6.2 shall be discussed before preparing the reply LS. See
`here below:
`
`R1-082622
`
`Proposed response to LS on PDCCH Format 1C (to R1-082278) Huawei
`
`(R1-082356)
`
`
`
`• Transport Block Sizes
`
`= R2-082889
`RAN2, Samsung
`Reply LS on Transport Block Sizes
`R1-082279
`The document was presented by (…) from Samsung and raises a number of concerns from RAN2 although the transport
`block sizes defined are largely satisfactory to RAN2.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`• Semi-Persistent Scheduling
`
`RAN2, Qualcomm
`Semi-Persistent Scheduling Activation with single PDCCH
`R1-082280
`The document was presented by Juan Montojo from Qualcomm and asks RAN1:
`
`= R2-082892
`
`• Q1: To evaluate if there is a serious problem with false activation of SPS due to PDCCH CRC false positives
`
`• Q2: If a problem is found, to indicate how many additional bits of ‘virtual’ CRC are required (if any) and which
`PDCCH fields can be used for uplink and downlink.
`
`• Q3: For UL SPS Ack/Nak resource allocation, to evaluate the need for more flexibility than provided by RRC
`signalling alone and, if need is found, to indicate which PDCCH fields (of the DL activation grant) can be used.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`R1-082639
`Required reliability of SPS uplink grant
`Samsung
` (R1-082297)
`The document was presented by (…) from Samsung and analyzes the false positive grant in terms of number of RBs
`wasted. Only the uplink is analyzed because the impact of the uplink false positive grant is more severe than that of the
`false positive downlink grant (in many cases cause the uplink collision between the false positive transmission and the
`correct transmission).
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Draft LS reply on Semi-Persistent Scheduling Activation with
`
`Qualcomm Europe
`R1-082541
`single PDCCH
`The document was presented by Wanshi Chen from Qualcomm and provides an attempt replying the questions raised by
`RAN2. The details are discussed under R1-082542.
`
`7 7
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 7
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`R1-082771
`
`
`Qualcomm Europe
`Details on SPS Activation with single PDCCH
`R1-082542
`The document was presented by Wanshi Chen from Qualcomm and identifies the potential severe impacts of false
`activation of SPS due to UL and DL PDCCH CRC false positives. The paper specifies the PDCCH fields in DCI formats 0
`and 1A that can be used to virtually expand the 16-bit CRC for more robust uplink and downlink SPS activations. Besides
`RRC signalling, it is proposed to reserve 2 bits in PDCCH DCI format 1A for additional flexibility in UL ACK/NAK
`resource allocation for DL SPS.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Semi Persistent Scheduling Activation and False Positive Grants Nokia, Nokia Siemens
`R1-082586
`
`Networks
`The document was presented by Timo Roman (?) from Nokia and concludes that false positive grants are shown to be
`serious problem, especially in UL. The solution selected by RAN2 has several drawbacks and requires new PDCCH
`formats for SPS. The paper proposes double PDCCH solution to be selected for SPS activation for UL. For DL, the false
`positive problem is less serious and single PDCCH solution is adequate.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Samsung
`Limiting TB size for SPS
`R1-082298
`The document was presented by (…) from Samsung and addresses a mechanism that enhances the false positive
`probability by limiting the TB sizes (in order to reduce the false positive SPS resource assignment).
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`Conclusion from the discussion:
`
`• Reply to Q1: RAN1 agrees that there is a serious problem with false activation of SPS due to PDCCH CRC false
`positives
`
`• Reply to Q2: Continue off line discussion on:
`o how many bits are required to solve the problem
`o which explicit bit fields of PDCCH should and can be reserved for it
`o Check whether additional protection is needed
`• Reply to Q3: Discussion shall continue based on proposal from R1-082280
`o Two (2) bits in DCI format 1 and 1A are reserved for that purpose
`o TPC (2bits): to indicate the selected UL SPS ACK/NACK resource configured by RRC signalling
`
`Friday 4th
`
`R1-082706
`
`Draft LS reply on Semi-Persistent Scheduling Activation with single
`PDCCH
`
`The document was presented by Wanshi Chen from Qualcomm.
`
`Qualcomm Europe,
`Samsung, Panasonic,
`Philips, NXP, Alcatel-
`Lucent, InterDigital,
`Motorola
`
`(R1-082541)
`
`Discussion (Question / Comment):
`Decision: Document is noted and is further revised in R1-082760. Final LS is agreed in R1-082766.
`
`
`
`
`
`8 8
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 8
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`
`• TTI Bundling
`
`R1-082771
`
`RAN2, Nokia Siemens
`= R2-082871
`LS on TTI Bundling
`R1-082276
`Networks
`The document was presented by Mieszko Chmiel from NSN and asks RAN1 to clarify if bundling is required for TDD and
`if required, for which UL/DL configurations.
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Motorola
`UL TTI Bundling Performance and Consideration
`R1-082476
`The document was presented by Rapeepat Ratasuk from Motorola and provides system simulation results showing that
`option 2 (as proposed in the LS R1-082276) improves the uplink VoIP coverage significantly.
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`R1-082334
`
`UL Bundling for TDD
`
`Motorola
`
`
`
`The document was presented by Robert Love from Motorola and discusses the impact introduced by subframe bundling
`based on agreed UL HARQ number and timing. Conclusion is:
`
`• Bundle size of 2 consecutive UL subframes in first transmission can be supported by TDD configurations 0, 1, 3,
`4, 6. Retransmission may occur with non-consecutive subframes.
`• Bundle size of 3 consecutive UL subframes in first transmission can be supported by TDD configurations 0, 3, 6.
`Retransmission may occur with non-consecutive subframes.
`• Bundle size of 4 is possible to be supported by TDD configurations 0, 1, 6. However, the UL subframe allocation,
`even for initial transmission, is non-consecutive.
`• Bundling is not recommended for configuration 2 and 5.
`
`
`
`Based on the UL HARQ timing budget, Alternative 1 (R1-081103) can be supported without extra retransmission delay
`with TDD configurations 3, 4 but modification to the PHICH timing for bundled UEs is needed.
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`(R1-082449)
`Ericsson
`On TTI bundling for LTE TDD
`R1-082626
`The document was presented by Lars Lindbom from Ericsson and provides simulation results showing that bundling with
`size of 4 TTI’s outperforms segmentation when there is a possibility to re-transmit 16 TTI’s. The paper concludes that a
`reply to RAN2 should indicate that TTI bundling is required as it has a substantial advantage over segmentation on the
`uplink coverage also for LTE TDD, and that it should be introduced for the UL-DL configurations 0, 1 and 6.
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Nokia, Nokia Siemens
`
`Consideration on TTI Bundling for LTE TDD
`R1-082585
`Networks
`The document was presented by Xiangguang Che from Nokia and first concludes that TTI bundling may have gain for
`configurations 0, 1 and 6. Secondly, running system simulations taking multi-users and multi-packets into consideration
`have shown that alternative1 with agreed delay budget (50ms) has no capacity gain compared to no bundling. Additionally
`there is no clear benchmarking coverage from legacy system, thus it is not obvious motivation for TTI bundling in LTE
`TDD.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`CATT, CMCC, RITT,
`
`Reply LS on the TTI bundling for TDD
`R1-082561
`ZTE, Huawei
`The document was presented by Yu Ding from CATT and concludes that TTI bundling for TDD should be as the decision
`made before by RAN1 in [R2-081326 & R1-081103].
`
`9 9
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 9
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`“During RAN1#52, RAN1 discussed the LTE uplink coverage using PUSCH and concluded that a solution improving
`coverage without the overhead associated with L2 segmentation and the issues with ACK/NAK errors pointed out by RAN2
`is needed.
`
`R1-082771
`
`RAN1 proposes to base this solution on so-called TTI bundling. The solution is characterized by:
`
`•
`
` A single transport block is coded and transmitted in a set of consecutive subframes.
`o The same hybrid ARQ process number is used in each of the bundled subframes
`
`• Bundling can be applied to FDD as well as TDD
` o For TDD, the bundling size needs to take the allocations of subframes to UL and DL into account.”
`
`In addition, configurations 0, 1, 3 and 6 should be used.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`From the above set of contributions and discussion, it is concluded:
`
`• Need for TTI bundling is agreed for TDD as for FDD
`
`• Do not request RAN2 to reconsider their decision on alternative 1 (delay can be traded versus coverage)
`o Provide RAN2 with some background on the technical aspects
`• UL/DL configurations 0, 1 and 6 should be applicable for TDD TTI bundling
`o Fixed TTI bundle size 4
`o Additional UL/DL configuration 3 is FFS until next meeting
`Indicate to RAN2 that ACK/NACK repetition as discussed for FDD is applicable for TDD as well
`
`•
`
`• LS to RAN2 shall be prepared in R1-082642 (Ericsson)
`
`Friday 4th
`
`Reply LS on TTI bundling
`R1-082642
`The document was presented by Lars Lindbom from Ericsson.
`
`RAN1, Ericsson
`
`Discussion (Question / Comment):
`Decision: Document is noted and LS is agreed.
`
`
`• System information scheduling
`
`= R2-082893
`RAN2, NTT DoCoMo
`LS on System information scheduling
`R1-082281
`The document was presented by Sadayuki Abeta from NTT DoCoMo and asks RAN1 to provide any feedback on the
`maximum size of SIB1 that can be transmitted under RAN2 assumptions, if any different from the values indicated in the
`LS received from RAN1 in R2-080473/R1-075102.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`LG Electronics
`Considerations on SI transmission/reception
`R1-082419
`The document was presented by Joon-Kui Ahn from LGE and shows evaluation results on the payload size for SI-1. It also
`proposes the possible approaches for the SI-1 payload size setting and discusses the current RAN2 assumption on the
`HARQ process for BCCH reception.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`R1-082420
`
`Proposed reply to RAN2 LS on system information scheduling
`(R2-082738)
`
`LG Electronics
`
`
`
`10 10
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 10
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`The document was presented by Joon-Kui Ahn from LGE and proposes 2 approaches:
`
`R1-082771
`
`• Approach 1: Maximum size of SIB1 is set different up to around 1200 bits depending on the system bandwidth.
`
`• Approach 2: Maximum size of SIB1 is set to one same value (around 300 bits) for all the system bandwidths
`based on 1.4 MHz bandwidth.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Nokia Siemens Networks,
`Proposed Response to LS on System Information Scheduling
`R1-082583
`
`Nokia
`(R2-082893)
`The document was presented by Mieszko Chmiel from NSN and addresses the questions raised in the RAN2 LS on system
`information scheduling. The results presented in this document indicated that:
`• SIB1 capacity amounts to a maximum of 310 bits assuming a total of 4 transmissions in sub-frame #5 of each
`even radio-frame considering the worst case scenario of 1.4 MHz system bandwidth.
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Motorola
`BCCH Coverage Issues and Maximum SI-x TBS
`R1-082558
`The document was presented by Robert Love from Motorola and suggests that the maximum SI-x TBS for Release-8 to be
`restricted to less than 600 bits for smaller BW modes like 1.4MHz (all 6RBs are used) and 1200 bits for the larger BW
`modes like 3MHz (12 RBs are used at a minimum). Segmentation of the SIBs to reduce the TBS used for a given SI-x is
`one possibility to meet these TBS restrictions.
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Discussion with RAN2 shall occurred during the week for drafting the response (to be revisited)
`
`Friday 4th
`
`LS response to LS on Information about new PDCCH Format 1C & LS
`R1-082751
`on SI scheduling
`The document was presented by Robert Love from Motorola.
`
`Huawei, Motorola,
`Qualcomm
`
`Discussion (Question / Comment):
`Decision: Document is noted and discussion concerning new PDCCH Format 1C will proceed until next meeting.
`
`
`
`• Synchronization of L1 parameters
`
`LS on synchronization of L1 parameter from system information
`R1-082282
`The document was presented by Hidetoshi Suzuki from Panasonic.
`
`RAN2, Panasonic
`
`= R2-082898
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Synchronization of L1 parameter from system information (Reply
`
`Panasonic
`R1-082415
`to: R2-082898)
`The document was presented by Hidetoshi Suzuki from Panasonic and shows that key factor to decide the need of the
`synchronization of L1 parameter from system information is the usage of frequency selective CQI on PUCCH.
`
`Discussion (Question / Comment):
`Decision: Document is noted. LS shall be prepared in R1-082648 (Panasonic) following off line discussion with RAN2.
`
`Friday 4th
`
`R1-082648
`
`Draft LS response to LS on synchronization of L1 parameter from
`system information
`
`Panasonic
`
`11 11
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 11
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`The document was presented by Hidetoshi Suzuki from Panasonic.
`
`Discussion (Question / Comment):
`Decision: Document is noted and final LS is agreed in R1-082765.
`
`
`
`• CSG cell identification
`
`R1-082771
`
`Reply LS on CSG related mobility (stage 2 text)
`R1-082289
`For information
`
`SA1, Nokia Siemens
`Networks
`
`= S1-080769
`
`RAN2, Qualcomm
`LS on CSG cell identification
`R1-082283
`The document was presented by Juan Montojo from Qualcomm and asks RAN1:
`
`= R2-082899
`
`• To provide feedback on the feasibility of introducing without impact to the Rel-8 timeline, a set of new Physical
`Cell Identities (PCIs) to be used for CSG cells only and identify how many additional PCIs can be defined in this
`case.
`
`•
`
`If not feasible, to comment on the possibility to reserve a number of existing PCIs (e.g. 50) for use only by CSG
`cells with the remaining PCIs being used for macrocells only.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`Samsung
`Differentiation between LTE home and macro eNBs
`R1-082296
`The document was presented by Juho Lee from Samsung and addresses the alternative based upon a reservation of a
`number of existing Physical Cell Identities for use only by CSG cells.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Draft LS reply on CSG cell identification
`R1-082539
`The document was not reviewed during the session.
`
`Qualcomm Europe
`
`
`
`
`Qualcomm Europe
`Extending the PCI space
`R1-082540
`The document was presented by Juan Montojo from Qualcomm and proposes two solutions to increase Physical layer cell
`Identity (PCI) for E-UTRA.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`Proposed response to LS on CSG cell identification (R2-082899) Nokia Siemens Networks,
`
`R1-082584
`Nokia
`The document was presented by Mieszko Chmiel from NSN and addresses the questions raised in the RAN2 LS on CSG
`identification. Proposal is as follows:
`
`• Signal via the BCCH of the macro network a set of cell IDs allocated to CSG (including none CSG) to take into
`account different deployment types including the case when there are no HeNBs on this frequency layer.
`
`Also, the CSG flag in the BCCH (SIB1) should be retained or replaced with CSG-specific DL RS scrambling for
`verification purposes of the SCH-based CSG detection.
`
`Discussion (Question / Comment):
`Decision: Document is noted. Discussion shall continue and topic shall be revisited later on.
`
`Friday 4th
`
`Qualcomm Europe
`LS reply on CSG cell identification
`R1-082748
`Decision: Document is noted and agreed in R1-082762 assuming the first action to RAN2 is removed from the list and
`sentence: “…several companies having concerns…” is replaced by “… many companies having concerns…”
`
`12 12
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 12
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`
`
`• RSRP (Related contributions under AI6.4)
`
`R1-082771
`
`= R4-081208
`RAN4, Ericsson
`RSRP Reporting Range
`R1-082284
`The document was presented by Ylva Jading from Ericsson and informs RAN1 on RAN4 agreement w.r.t the reporting
`range of RSRP measurement quantity.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`= R4-081215
`RAN4, Nokia
`LS on RSRP definition
`R1-082285
`The document was presented by Asbjørn Grøvlen from Nokia and provides a revision of RSRP definition to be taken
`account by RAN1.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`• RSRQ
`
`= R4-081699
`RAN4, Ericsson
`RSRQ Definition Update
`R1-082633
`The document was presented by Ylva Jading from Ericsson and requests RAN1 to remove E-UTRA carrier RSSI from TS
`36.214 as a separate measurement quantity and accordingly update RSRQ definition as suggested in this LS.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`= R4-081700
`RAN4, Ericsson
`RSRQ Reporting Range
`R1-082634
`The document was presented by Ylva Jading from Ericsson and shows RAN4 agreement on the reporting range of RSRQ
`measurement quantity.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`(R1-082646)
`Ericsson
`Draft CR to 36.214 on Modification of RSRQ and removal of RSSI
`R1-082647
`The document was presented by Ylva Jading from Ericsson and drafts the implementation of above decisions.
`
`Discussion (Question / Comment): Nokia commented that same should apply to TS 25.215
`Decision: Document is noted and final CR shall be provided in R1-082650 (CR0007 of TS36.214) and in R1-082651
`(CR0190 of TS25.215)
`
`Friday 4th
`
`CR
`6.4
`36.214 CR0007 (Rel-8, F) Modification of RSRQ and removal of RSSI Ericsson
`R1-082650
`Decision: Document is noted and CR to 36.214 is agreed. CR to 25.215 was already approved in R1-082651 under AI 5.
`
`
`
`
`
`= R4-081228
`RAN4, Nokia
`RESPONSE LS on downlink power settings
`R1-082286
`The document was presented by Asbjørn Grøvlen from Nokia and provides RAN4 response on DL power settings.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`
`
`= R4-081249
`RAN4, Ericsson
`LS Response on Transmission of Physical Layer Parameters
`R1-082287
`The document was presented by Erik Dahlman from Ericsson and informs RAN1 on RAN4 answers to questions 4, 5 and
`6 as requested by RAN2 in their LS.
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`13 13
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2005 - Page 13
`
`

`

`
`3GPP TSG RAN WG1 Meeting #54
`Jeju, South Korea, 18 – 22 August, 2008
`
`
`
`R1-082771
`
`Draft LS on the signalling of the number of antenna ports during
`R1-082507
`handover
`The document was presented by Anna Tee from Nortel.
`Discussion (Question / Comment):
`Decision: Document is noted. Before sending the LS, Mr. Chairman asked first to check with RAN2 colleagues whether
`this is already agreed in RAN2. If not, it shall be revisited later in the week.
`
`Nortel
`
`
`
`Friday 4th
`RAN2 seems to have already an assumption on the support of the signalling of the number of antenna ports in the destined
`cell site during handover.
`
`
`
`= R4-081658
`RAN4, Ericsson
`LS on CQI definition
`R1-082632
`The document was presented by Georg Jöngren from Ericsson and suggests the following rephrased definition of CQI:
`
`Based