R1-091069
`
`
`
`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`Agenda item
`3
`Title:
` Final Report of 3GPP TSG RAN WG1 #55bis v3.0.0
`
`
`(Ljubljana, Slovenia, 12 – 16 January, 2009)
`Document for:
` Approval
`Source:
`
`MCC Support
`
`
`
`
`
`
`
`
`
`Fact Summary
`Meeting:
`Dates:
`Venue:
`Host:
`Attendees:
`Documents:
`
`
`3GPP TSG RAN WG1 #55bis
`12th through 16th January, 2009
`Grand Hotel Union in Ljubljana, SLOVENIA
`European Friends of 3GPP
`159 delegates
`543 (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 2008 - Page 1
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`Table of contents
`
`R1-091069
`
`
`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 ............................................................................. 10
`6. Maintenance of Evolved UTRA Release 8 ...................................................................................... 13
`6.1
`Corrections for TS 36.211 ............................................................................................................................ 14
`6.2
`Corrections for TS 36.212 ............................................................................................................................ 18
`6.3
`Corrections for TS 36.213 ............................................................................................................................ 22
`6.4
`Corrections for TS 36.214 ............................................................................................................................ 32
`7.
`Continuous Connectivity for packet data users for 1.28Mcps TDD ............................................. 33
`8. MIMO for 1.28Mcps TDD .................................................................................................................... 34
`9.
`Discussion on UTRA Multi-Carrier Evolution ................................................................................... 35
`10. Positioning Support for LTE ............................................................................................................... 37
`11. Study Item on E-UTRAN Mobility Evaluation & Enhancement ..................................................... 38
`12. Study Item on LTE-Advanced ............................................................................................................ 39
`12.1
`UL transmission scheme .............................................................................................................................. 41
`12.2
`Bandwidth extension ..................................................................................................................................... 46
`12.3
`Coordinated Multipoint Transmission/Reception (COMP) ....................................................................... 50
`12.4
`UL MIMO extension up to 4x4 ..................................................................................................................... 52
`12.5
`DL MIMO extension up to 4x4 ..................................................................................................................... 53
`12.5.1
`DL MIMO extension up to 4x4 (ad-hoc) ................................................................................................ 55
`12.6
`Relaying .......................................................................................................................................................... 58
`13. Closing of the meeting ........................................................................................................................ 60
`Annex A: List of participants at RAN1 #55bis......................................................................................... 61
`Annex B: TSG RAN WG1 meetings in 2009 .......................................................................................... 62
`Annex C: List of CRs agreed at RAN1#55bis ......................................................................................... 63
`Annex D: List of Outgoing LSs from RAN1#55bis ................................................................................. 67
`Annex E: List of Tdocs at RAN1 #55bis .................................................................................................. 68
`Annex F: List of actions ............................................................................................................................. 69
`
`
`
`
`2 2
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 2
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`
`R1-091069
`
`Executive summary
`3GPP TSG WG RAN1 #55bis meeting took place in Grand Hotel Union, Ljubljana, SLOVENIA.
`
`The meeting started at 9:20 on Monday 12th January and finished at 17:00 on Friday 16th January 2009.
`
`
`
`The week was scheduled as follows:
`
`• Monday: Common session on Agenda items 1, 2, 3, 4, 6, 6.1 and 6.2.
`
`• Tuesday: Parallel sessions. On one hand, session dedicated to corrections to TS36.213 (AI 6.3) chaired by
`Sadayuki Abeta and on the other hand, session on Agenda items 5,7,8 and 9 chaired by Dirk Gerstenberger.
`
`• Wednesday morning: Parallel sessions on Agenda items 12 and 12.2 chaired by Dirk Gerstenberger and Agenda
`item 12.5 (DL MIMO in LTE-A) chaired by Juho Lee
`
`• Wednesday afternoon: Common session on Agenda item 12.1 chaired by Dirk Gerstenberger.
`
`• Thursday morning: Parallel sessions on Agenda items 12.3 and 12.6 chaired by Dirk Gerstenberger and Agenda
`items 12.4 and 12.5 chaired by Juho Lee
`
`• Friday morning: Common session on Agenda items 10 and 11.
`
`• 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 529, and those documents were categorized as followed.
`
`Agenda Item
`Liaison statement handling
`Maintenance of UTRA R99 – Rel-8
`Maintenance of Evolved UTRA Rel-8
`Continuous Connectivity for Packet Data users for
`1.28Mcps TDD
`MIMO for 1.28Mcps TDD
`UTRA Multi-Carrier Evolution
`Positioning support for LTE
`Study Item on E-UTRAN Mobility Evaluation &
`Enhancement
`Study Item on LTE-A
`Study Item on LTE-A: UL transmission scheme
`Study Item on LTE-A: Bandwidth extension
`Study Item on LTE-A: COMP
`Study Item on LTE-A: UL MIMO extension up to 4x4
`Study Item on LTE-A: DL MIMO extension up to 8x8
`Study Item on LTE-A: Relaying
`
`Input
`Document
`28
`33
`148
`7
`7
`22
`4
`5
`20
`35
`57
`44
`28
`46
`45
`
`Discussed
`Document
`25
`30
`
`7
`7
`21
`4
`3
`10
`19
`5
`5
`1
`20
`3
`
`
`
`Note: The amount of documents includes those discussed during the email discussion session post meeting.
`
`3 3
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 3
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`The following document are missing. The corresponding contributions have not been handed over by companies.
`
`R1-091069
`
`
`
`
`
`R1-090097
`
`UL A/N Multiplexing for Carrier aggregation
`
`Samsung
`
`R1-090212
`
`Codebook-based PMI Restriction for LTE-advanced system
`
`LG Electronics
`
`R1-090324
`
`Supporting Asymmetric Carrier Aggregation and Non Rel-8 Carriers in LTE-
`A (TBD)
`
`R1-090376
`
`Evaluation of UE specific RS for COMP schemes
`
`R1-090378
`
`Downlink SU-MIMO in LTE-A
`
`Motorola
`
`Ericsson
`
`Ericsson
`
`4 4
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 4
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`
`R1-091069
`
`Opening of the meeting
`1.
`Mr. Dirk Gerstenberger (RAN1 Chairman) welcomed the participants to the 55th RAN WG1 bis meeting and opened the
`meeting at 09:20. Highlight was put on the 10th year of existence of 3GPP starting with first meeting in Espoo, Finland in
`January 1999.
`
`Eric Hardouin from Orange welcomed the delegates on behalf of European Friends of 3GPP and informed them about
`logistic issues during the week.
`
`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#55bis meeting
`R1-090001
`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
`
`
`MCC Support
`Draft report of RAN1#55 meeting
`R1-090002
`The document was presented by Patrick Mérias and draws the minutes from last meeting with special attention to RAN1
`email approval issues not resolved prior to RAN1#55b meeting, namely:
`
`• LTE 55/10: on path loss definition
`
`• LTE 55/18: on CQI reporting for trnasmission mode 7
`
`• LTE-A 55/1 (resp. LTE-A 55/3) on TP for evaluation methodology (resp. for default antenna tilt)
`Discussion (Question / Comment): Mr Chairman confirmed that August 2009 meeting was of course co-located the same
`week as the other WGs (due to confusion in recent email on the reflector).
`
`5 5
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 5
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`Decision: The document was approved.
`
`
`
`Liaison statement handling
`4.
`Incoming LS
`
`R1-091069
`
`= R2-087402
`RAN2, Texas Instruments
`LS on preamble group selection based on radio link condition
`R1-090003
`The document was presented by Zukang Shen from TI and asks RAN1 to confirm the agreement on the method of
`preamble group selection and to provide more values for messagePowerOffsetGroupB.
`
`Discussion (Question / Comment): .
`Decision: Document is noted.
`
`R1-090274
`
`Radio-link criterion for preamble group selection
`
`Texas Instruments, LG
`Electronics, Nokia Siemens
`Networks, Nokia
`The document was presented by Zukang Shen from TI and addresses the RAN2 LS in R1-090003 by proposing a set of
`values for the parameter messagePowerOffsetGroupB used for computing the radio-link condition for preamble group
`selection.
`Discussion (Question / Comment): .
`Decision: Document is noted.
`
`
`
`R1-090275
`
`Texas Instruments, LG
`Draft response LS on preamble group selection based on radio link
`Electronics, Nokia Siemens
`condition
`Networks, Nokia
`The document was presented by Zukang Shen from TI and draws the response to the RAN2 LS in R1-090003.
`Discussion (Question / Comment): LS shall detail the equation to compute messagePowerOffsetGroupB.
`Decision: Document is noted. It shall be revised in R1-090426.
`
`
`
`Tuesday 13th evening
`
`R1-090426
`
`Draft response LS on preamble group selection based on radio link
`condition
`Decision: Document is noted and final LS is agreed in R1-090494.
`
`
`Texas Instruments, LG
`Electronics, Nokia Siemens
`Networks, Nokia
`
`(R1-090275)
`
`= R2-087406
`RAN2, Panasonic
`LS on SPS explicit release
`R1-090004
`The document was presented by Alexander Golitschek edler von elbwart from Panasonic and asks RAN1 to decide on the
`exact PDCCH codepoint(s) for indicating the explicit release of SPS resources and to capture the codepoints for downlink
`and uplink release in the appropriate RAN1 specification.
`Discussion (Question / Comment): .
`Decision: Document is noted.
`
`
`LG Electronics
`DCI formats and bit fields for SPS deactivation
`R1-090197
`The document was presented by (…) from LGE and proposes to only support SPS de-activation using DCI format 0 for
`uplink and DCI format 1A for downlink, and used following bit field states as listed in Table 3 to indicate SPS de-
`activation and to differentiate the DCI format from SPS activation.
`
`Discussion (Question / Comment): .
`Decision: Document is noted.
`
`R1-090247
`
`Explicit Release and its Acknowledgement for Semi-Persistent
`Scheduling
`
`Panasonic
`
`
`
`6 6
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 6
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`The document was presented by Alexander Golitschek edler von elbwart from Panasonic and proposes to agree on the
`following items:
`
`R1-091069
`
`• SPS explicit release is facilitated by additionally allowing the ‘11111’ entry in the MCS / MCS+RV field for
`PDCCH SPS validation.
`
`• A successfully detected explicit release for downlink triggers a HARQ-ACK message which is generated in the
`same way as a HARQ-ACK/NACK message for a downlink shared channel transmission.
`
`• For hopping of uplink SPS, the hopping information as conveyed is the most recently received SPS
`activation/reconfiguration message is used.
`
`A corresponding CR is submitted in R1-090251 and a draft LS reply to inform RAN2 of the decisions taken is submitted
`in R1-090248.
`
`Discussion (Question / Comment): .
`Decision: Document is noted. Mr Chairman noticed the existence of a number of compagny’s CR on this topic under AI
`6.3 and requested proponents try to converge on it. Discussion shall continue off line and topic shall be revisited when
`looking at AI 6.3.
`
`Draft reply to “LS on SPS explicit release”
`Draft CR for Correction of Semi-Persistent Scheduled data
`transmission de-activation
`
`Panasonic
`
`LG Electronics
`
`
`
`(R1-090198)
`
`R1-090248
`
`R1-090421
`…/…
`
`
`
`LS on Capturing the Agreements of Measurement Gap
`R1-090005
`The document was presented by Yu Ding from CATT.
`Discussion (Question / Comment): .
`Decision: Document is noted.
`
`
`
`Reply LS to R1-084063 = R2-086029 on BCH transport block size
`R1-090006
`The document was presented by Sadayuki Abeta from NTT DoCoMo.
`Discussion (Question / Comment): .
`Decision: Document is noted.
`
`
`
`RAN2, CATT
`
`= R2-087407
`
`RAN2, NTT DoCoMo
`
`= R2-087428
`
`RESPONSE LS on Maximum allowed transmission power on the
`RAN4, NTT DoCoMo
`R1-090007
`uplink
`The document was presented by Sadayuki Abeta from NTT DoCoMo and proposes:
`
`= R4-083041
`
`• RAN4 response 1: The Pmax value range should be “-30…33 dBm with a step size of 1 dB.”
`
`• RAN4 response 2: Pcompensation should be applicable in LTE.
`Discussion (Question / Comment): No action to RAN1.
`Decision: Document is noted.
`
`
`
`= R4-083317
`RAN4, Ericsson
`LS on new definitions of maximum UE output powers
`R1-090010
`The document was presented by Daniel Larsson from Ericsson and introduce three new definitions and notations related to
`maximum UE output power in TS 36.101 as follows:
`
`7 7
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 7
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`PCMAX is the configured UE transmitted power defined as follows;
`
`PCMAX = MIN {PEMAX, PUMAX}
`
`Where
`
`R1-091069
`
`• PEMAX is the maximum allowed power configured by higher layers and defined in [TS36.331]
`
`• PUMAX is the maximum UE power for the UE power class specified in section 6.2.2 modified by section 6.2.3 and
`section 6.2.4
`
`The UE shall not exceed PCMAX with the tolerances defined in sub-clause 6.2.1-1.
`
`Discussion (Question / Comment):
`Decision: Document is noted.
`
`R1-090430
`
`LG Electronics, Ericsson,
`36.213 CR0196R1 (Rel-8, F) Alignment of RAN1/RAN4 specification
`Panasonic, NTT DoCoMo,
`on UE maximum output power
`Nokia, NSN
`The document was presented by Dragan Vujcic from LGE and addresses the notations related to maximum UE output
`power for PUSCH and RACH in order to ensure consistency between RAN1 and RAN4 specification.
`
`(R1-090387)
`
`Discussion (Question / Comment):
`Decision: Document is noted and CR is agreed.
`
`
`
`= R4-083264
`RAN4, NTT DoCoMo
`RESPONSE LS on E-UTRA UL Power Control
`R1-090008
`The document was presented by Sadayuki Abeta from NTT DoCoMo and asks RAN1 to introduce the definition of
`pathloss estimate in specifications preferably where UL PC is specified.
`
`Discussion (Question / Comment): .
`Decision: Document is noted.
`
`
`
`= R4-083298
`RAN4, NTT DoCoMo
`RESPONSE LS on radio link monitoring
`R1-090009
`The document was presented by Sadayuki Abeta from NTT DoCoMo and shows the conclusions reached in RAN4 as:
`
`• The transmitter power shall be turned off within [40] ms after expiry of T310 timer as specified in section 5.3.11
`in TS 36.331.
`
`• According to RAN1 LS, out-of-sync would be indicated to higher layers when the radio link quality is worse than
`the threshold Qout, and in-sync would be indicated to higher layers when the radio link quality is better than the
`threshold Qin, i.e. there would be no indication when the radio link quality is in-between Qin and Qout.
`
`• Counter-based L3 filtering, which is used in UTRAN, could be applicable in E-UTRAN.
`
`• After L3 filtering, i.e. T310 starts, non-DRX L1 evaluation period and reporting interval would be applied in the
`radio link monitoring
`Discussion (Question / Comment): No compatibility with the related procedures set by RAN1 in the specifications. No
`further action required to RAN1
`Decision: Document is noted. LS in R1-090431 shall be prepared to keep RAN2 informed of the decision.
`
`Friday 16th
`
`R1-090431
`
`[DRAFT] RESPONSE LS on radio link monitoring
`
`NTT DOCOMO
`
`
`
`Decision: Document is noted and final LS is agreed as R1-090538.
`
`
`
`LS on idle interval of LCR TDD for E-UTRAN cell monitoring
`R1-090011
`The document was presented by Yu Ding from CATT.
`
`RAN4, CATT
`
`= R4-083323
`
`8 8
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 8
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`Discussion (Question / Comment): No action required to RAN1.
`Decision: Document is noted.
`
`
`Response to LS on scope and reference for parameter
`R1-090012
`“sameRefSignalsInNeighbour” (R1-083474) (R4-082534)
`The document was presented by Prakash Bhat from Vodafone.
`
`Discussion (Question / Comment): No action required to RAN1.
`Decision: Document is noted.
`
`
`
`R1-091069
`
`RAN4, Vodafone
`
`= R4-083331
`
`= R4-085515
`RAN5, NTT DoCoMo
`LS on Common Test Environment (TS 36.508)
`R1-090013
`The document was presented by Sadayuki Abeta from NTT DoCoMo and asks RAN1 to review and comment on TS
`36.508 v8.0.0 when available, especially on the following sections:
`
`• Section 4.4.3.2 to 4.4.3.4 Common contents of system information messages/blocks
`
`• Section 4.6 Default RRC message and information contents
`
`• Section 4.8 Reference radio bearer configurations
`Discussion (Question / Comment): Mr Chairman informed the group that response shall be available by the end of the
`week to let RAN5 progress in their work.
`Decision: Document is noted. Draft response LS is expected in R1-090432.
`Friday 16th
`
`[Draft] Reply LS on Common Test Environment (TS 36.508)
`R1-090432
`Decision: Document is noted and final LS is agreed in R1-090539.
`
`NTT DOCOMO
`
`
`
`
`
`LS on enhancing radio bearer parameters in 34.108 for Improved
`= R4-085542
`RAN5, Ericsson
`R1-090014
`Layer 2 UL (FDD)
`The document was presented by Daniel Larsson from Ericsson and asks RAN1 to check the physical layer parameters of
`the enhanced radio bearer parameters for combinations on HS-PDSCH and E-DPDCH in the attached CR to TS 34.108.
`
`Discussion (Question / Comment): .
`Decision: Document is noted. Draft response LS is expected in R1-090433.
`
`Friday 16th
`
`Draft Reply LS on enhancing radio bearer parameters in 34.108 for
`R1-090433
`Improved Layer 2 UL (FDD)
`Decision: Document is noted and final LS is agreed in R1-090540.
`
`Ericsson
`
`
`
`
`
`LS received in the course of the week
`
`R1-090477
`Refer to AI 6.3.
`
`LS on additional values of wideband CQI/PMI period
`
`RAN2, InterDigital
`
`= R2-090731
`
`9 9
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 9
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`
`R1-091069
`
`Maintenance of UTRA Release 99 – Release 8
`
`
`
`5.
`CPC
`
`
`CPC impact on UE internal measurement
`R1-090165
`Decision: Document is noted. No changes needed to RAN1 specification, text in RAN4 (25.133) is sufficient from RAN1
`perspective. RAN2 should decide whether they need more clarification in RAN2 specifications.
`
`Huawei
`
`R1-090293
`
`25.214 CR0530 (Rel-7, F) Editorial correction to UE transmit
`power control behaviour in case of DTX/DRX
`25.214 CR0531 (Rel-8, A) Editorial correction to UE transmit
`R1-090294
`power control behaviour in case of DTX/DRX
`Decision: Both documents are noted and CRs are agreed.
`
`Nokia, Nokia Siemens
`Networks
`Nokia, Nokia Siemens
`Networks
`
`Clarification of CQI preamble length when switching UE DTX cycle
`R1-090406
`Decision: Document is noted. Revisit after offline discussion on what clarification is needed.
`Friday 16th
`
`Ericsson
`
`
`
`
`
`
`
`R1-090520
`
`
`
`25.214 CR0533 (Rel-7, F) Clarification of CQI preamble length
`when switching UE DTX cycle
`25.214 CR0535 (Rel-8, A) Clarification of CQI preamble length
`
`R1-090525
`when switching UE DTX cycle
`Decision: Both documents are noted. Johan Bergman from Ericsson is expecting feedback from other companies and
`requested to approve them by email  22/01
`
`Ericsson
`
`Ericsson
`
`
`
`EUL CELL_FACH
`
`Individual Initial Serving Grant per Common E-DCH Resource
`R1-090304
`Decision: Document is noted.
`
`R1-090305
`
`Individual Initial Serving Grant per Common E-DCH Resource in
`25.214
`Decision: Document is noted. Revisit after discussion in RAN2.
`Friday 16th : RAN2 did not agree to the concept.
`
`NEC Group, Nokia
`Siemens Networks
`
`NEC Group, Nokia
`Siemens Networks
`
`
`
`DC-HSDPA
`
`Transient behavior due to HS-SCCH orders for DC-HSDPA
`R1-090407
`Decision: Document is noted. Revisit after offline discussion.
`
`Friday 16th
`
`25.214 CR0534 (Rel-8, F) Corrections of HS-SCCH orders for DC-
`R1-090521
`HSDPA
`Decision: Document is noted and CR is agreed
`
`
`Ericsson
`
`Ericsson
`
`MBSFN IMB
`
`
`
`
`
`
`
`
`
`10 10
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 10
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`
`TDM pilot sequences for MBSFN IMB
`R1-090452
`Decision: Document is noted.
`
`R1-091069
`
`IPWireless
`
`(R1-090422)
`
`T-CPICH sequences for MBSFN IMB
`R1-090442
`Decision: Document is noted. Revisit after offline discussion.
`Friday 16th : Qualcomm indicated that sequence designs shall be presented at next meeting, in line with the DOB
`compromise proposal. Orange commented that this should be considered as important topic to be concluded for Rel-8.
`
`
`
`Qualcomm Europe
`
`Scrambling codes and code groups for MBSFN IMB
`R1-090401
`Decision: Document is noted. Decide together with the pilot sequences.
`
`IPWireless
`
`
`
`25.213 CR0100 (Rel-7, F) Correction to DTX bit insertion for
`R1-090402
`MBSFN 16-QAM
`Decision: Document is noted.
`
`IPWireless
`
`
`
`
`
`25.213 CR0101 (Rel-8, A) Correction to DTX bit insertion for
`
`IPWireless
`R1-090403
`MBSFN 16-QAM
`Decision: Document is noted. Agreement on the need to specify DTX mapping, discuss offline how to set the dummy bits.
`Friday 16th : no feedback received at RAN1#55bis. Let’s decide at next meeting.
`
`
`
`
`IPWireless
`TFCI for 16-QAM in MBSFN IMB
`R1-090404
`Decision: Document is noted and is agreed in principle. Formal CRs for 25.221, 25.222, 25.223 shall be prepared
`respectively in R1-090500, R1-090501, R1-090502.
`
`Friday 16th
`
`R1-090501
`
`R1-090500
`
`25.221 CR0173 (CatF,Rel-8) "TFCI for Secondary CCPCH frame
`type 2 with 16QAM" (work item code MBSFN-DOB)
`25.222 CR0169 (CatF,Rel-8) "TFCI for Secondary CCPCH frame
`type 2 with 16QAM" (work item code MBSFN-DOB)
`25.223 CR0057 (CatF,Rel-8) "TFCI for Secondary CCPCH frame
`R1-090502
`type 2 with 16QAM" (work item code MBSFN-DOB)
`Decision: The three documents are noted and CRs are agreed.
`
`
`
`Potential Alterations for MICH in MBSFN IMB
`R1-090405
`Decision: Document is noted.
`
`25.222 CR0168 (Rel-8, F) Corrections to 25.222 for 3.84Mcps
`R1-090413
`MBSFN IMB
`Decision: Document is noted and CR is agreed.
`
`
`TDD
`
`25.221 CR0171 (Rel-7,F) Clarification of uplink multicode
`R1-090169
`transmission for 1.28Mcps TDD
`Decision: Document is noted and CR is agreed.
`
`25.221 CR0172 (Rel-8,A) Clarification of uplink multicode
`R1-090170
`transmission for 1.28Mcps TDD
`Decision: Document is noted and CR is agreed.
`
`11 11
`
`IPWireless, Ericsson
`
`IPWireless, Ericsson
`
`IPWireless, Ericsson
`
`IPWireless
`
`Ericsson, IPWireless,
`Qualcomm Europe
`
`CATT, TD-TECH, ZTE
`
`CATT, TD-TECH, ZTE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 11
`
`

`

`R1-091069
`
`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`
`Discussion on the absolute grant (power) value for LCRTDD
`R1-090429
`Decision: Document is noted.
`
`25.222 CR0164 (Rel-7,F) Correction of the absolute grant (power)
`R1-090171
`value mapping for 1.28Mcps TDD EUL
`Decision: Document is noted and CR is agreed.
`
`25.222 CR0165 (Rel-8,A) Correction of the absolute grant (power)
`R1-090172
`value mapping for 1.28Mcps TDD EUL
`Decision: Document is noted and CR is agreed.
`
`25.224 CR0204 (Rel-7,F) Clarificaion of the beta value for
`R1-090173
`smallest E-TFC of E-PUCH for 1.28Mcps TDD EUL
`Decision: Document is noted and CR is agreed.
`
`25.224 CR0205 (Rel-8,A) Clarificaion of the beta value for
`R1-090174
`smallest E-TFC of E-PUCH for 1.28Mcps TDD EUL
`Decision: Document is noted and CR is agreed.
`
`CATT
`
`CATT, TD-TECH, ZTE
`
`CATT, TD-TECH, ZTE
`
`CATT, TD-TECH, ZTE
`
`CATT, TD-TECH, ZTE
`
`25.225 CR0091 (Rel-8, F) RSRQ Measurement Definition
`R1-090184
`Decision: Document is noted. Prepare a similar CR for 25.215 (Ericsson).
`
`CATT
`
`Friday 16th
`
`25.215 CR0194 (Rel-8, F) E-UTRA RSRQ Measurement
`R1-090522
`Definition
`Decision: Document is noted and CR is agreed.
`
`
`Ericsson
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`12 12
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 12
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`
`R1-091069
`
`6.
`
`Maintenance of Evolved UTRA Release 8
`
`R1-090249
`Undefined LTE UE behaviour
`Panasonic
`
`The document was presented by Hidetoshi Suzuki from Panasonic and proposes the following to be captured:
`
`• UE behaviour is unspecified around RRC reconfiguration
`
`• When a UE’s uplink transmissions in subframe n and subframe n+1 are overlapped due to TA, the exact method
`of dropping is undefined.
`
`• UE behaviour of PUCCH around PRACH transmission is unspecified.
`Discussion (Question / Comment): Question was raised whether third bullet refers to the same subframe. Answer was yes
`and also for mixed subframes.
`Decision: Document is noted.
`Conclusions:
`
`• UE behaviour is unspecified around RRC reconfiguration
`
`• When a UE’s PUCCH/PUSCH/SRS transmissions in subframe n and subframe n+1 are overlapped due to TA, the
`exact method of dropping is undefined.
`
`• UE behaviour of PUCCH around PRACH transmission is unspecified  TDD part shall be revisited after
`discussions on TDD PRACH.
`
`• Prepare an LS to RAN2 in R1-090435.
`
`Friday 16th
`
`R1-090435
`
`LS on undefined LTE UE behaviour and transmission timing
`
`Decision: Document is noted and final LS is agreed in R1-090545.
`
`
`Panasonic, LGE, ZTE,
`Ericsson, Texas
`Instruments, CATT, Nokia,
`Nokia Siemens Network
`
`
`
`36.201 CR0003 (Rel-8, F) Removing inverse modulo operation
`R1-090373
`The document was presented by Daniel Larsson from Ericsson.
`
`Ericsson
`
`
`
`Discussion (Question / Comment): Cover sheet indicates wrong specification number (8.5.0 must be changed into 8.2.0 –
`MCC to correct it).
`Decision: Document is noted.
`
`36.211 CR0121R1 (Rel-8, F) Removing inverse modulo
`R1-090423
`operation
`The document was presented by Daniel Larsson from Ericsson.
`
`Ericsson
`
`(R1-090372)
`
`Discussion (Question / Comment): LGE requested more time to check it.
`Decision: Document is noted. Both CRs are conditionnally agreed unless problems are found. Later in the day, CRs are
`finally agreed with support from LGE.
`
`
`
`13 13
`
`IPR2018-01476
`Apple v. INVT
`INVT Exhibit 2008 - Page 13
`
`

`

`
`3GPP TSG RAN WG1 Meeting #56
`Athens, Greece, 09 – 13 February, 2009
`
`
`Corrections for TS 36.211
`
`6.1
`Timing
`
`R1-091069
`
`
`IPWireless
`Correction related to sample timings for TDD timing advance
`R1-090397
`The document was presented by Paul Piggin from IPWireless and ensures correct symbol timings are defined at a sample
`rate of 1.92MHz. Companion CR to these CRs is in R1-090398 and provides correction to sample timings related to TDD
`random access.
`
`36.211 CR0122 (Rel-8, F) Correction related to sample timings
`R1-090398
`for TDD timing advance
`Discussion (Question / Comment):
`Decision: Documents are noted and topic shall be clarified after off line discussion.
`Friday 16th : Two proposals in R1-090536 and R1-090534.
`
`IPWireless
`
`R1-090536
`
`36.211 CR0126 (Rel-8, F) Correction of preamble format 4 timing
`
`The document was presented by Lars Lindbom from Ericsson and proposes:
`
`Ericsson, ZTE, CATT,
`Nokia, Nokia Siemens
`Network, LGE, Texas
`Instruments, Panasonic
`
`
`
`
`
`• To remove the brackets of the preamble format 4 start position, add 288Ts GT to the current timing and remove
`the implictly included N_TA_offset in [5158Ts] into the UpPTS uplink frame timing given by section 8.1.
`
`• To replace the tentative value [614] for the N_TA_offset defined in section 8.1 with 624 which corresponds to the
`20usec (614Ts) uplink-downlink switch time defined in TS36.101, rounded upwards to be a multiple of 16.
`
`Discussion (Question / Comment):.
`Decision: Document is noted and CR is agreed.
`
`36.211 Draft CR on Correction to UpPTS frame timing
`R1-090534
`The document was presented by Paul Piggin from IPWireless.
`
`IPWireless
`
`
`
`Discussion (Question / Comment): Similar CR with main difference due to different view on frame timing applied to
`UpPTS. IPWireless highlighted their concern on a collision issues as current specification indicates that the PRACH
`format 4 is transmitted in the UpPTS, however the PRACH has a longer duration than the UpPTS and begins transmission
`prior to the start of the UpPTS. Therefore IPWireless requested to go for a combined CR.
`Decision: Document is noted.
`
`Discussion of working assumption on maximum range for
`R1-090535
`PRACH preamble format 4
`Decision: Document is noted.
`
`IPWireless
`
`
`
`Conclusion: IPWireless agreed to technically endorse the CR in R1-090536 and requested adding in the minutes that one
`company (IPWireless) was objecting.
`
`
`
`PRACH
`
`36.211 CR0123R1 (Rel-8, F) Clarification on the use of
`(R1-090412)
`Ericsson, ZTE
`R1-090419
`preamble format 4
`The document was presented by Lars Lindbom from Ericsson and proposes to add that preamble format 4 is applicable to
`frame structure type 2 with UpPTS lengths of two SC-FDMA symbols only.
`Discussion (Question / Comment): Although not against t