throbber
3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`Agenda item
` 3
`Title:
` Approved Report of 3GPP TSG RAN WG1 #44 meeting
`Document for:
`Information
`Source:
`
`RAN1 Secretary
`
`
`
`R1-061099
`
`Notes: All timestamps in this document are in GMT-7H unless otherwise noted.
`
`Fact Summary
`Meeting:
`Dates:
`Venue:
`Host:
`Attendees:
`Documents:
`
`3GPP TSG RAN WG1 #44 Meeting
`13th through 17th February, 2006
`Hyatt Regency Denver, Colorado, USA
`North American Friends of 3GPP
`183 delegates
`494 (including some withdrawn and post-meeting artefacts)
`
`Yoshikazu Ishii
`ETSI Mobile Competence Center
`yoshikazu.ishii@etsi.org
`
`APPLE 1018
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`Table of contents
`
`R1-061099
`
`Executive summary ......................................................................................................................................... 1
`Opening of the meeting ........................................................................................................................ 2
`1.
`1.1
`Call for IPR ....................................................................................................................................................... 2
`2
`Approval of the agenda ......................................................................................................................... 2
`Approval of the minutes from the previous meetings ....................................................................... 2
`3.
`Report from TSG RAN#30 and RAN1 LTE Ad Hoc .......................................................................... 4
`4.
`Liaison statement handling ............................................................................................................... 5
`5.
`Maintenance of R99, Rel4, Rel5, Rel6 ............................................................................................... 8
`6.
`6.1
`R99 CRs + shadow CRs ................................................................................................................................ 8
`6.2
`Rel4 CRs + shadow CRs ............................................................................................................................... 8
`6.3
`Rel5 CRs + shadow CRs ............................................................................................................................... 8
`6.4
`Rel6 CRs .......................................................................................................................................................... 8
`6.5
`Other ................................................................................................................................................................. 9
`3.84 Mcps TDD Enhanced Uplink ..................................................................................................... 12
`7.
`7.68 Mcps TDD Option ....................................................................................................................... 13
`8.
`MIMO in UTRA (Rel'7 Work Item) ..................................................................................................... 15
`9.
`10. Continuous Connectivity for Packet Data Users ............................................................................. 18
`Improved support of gaming over HSPA .......................................................................................... 22
`11.
`Improvements of MBMS ..................................................................................................................... 23
`12.
`13. Evolved UTRA and UTRAN (Physical Layer) .................................................................................. 24
`13.1
`Description of OFDMA Downlink used in the concept evaluation .......................................................... 25
`13.1.1
`Contributions reflecting results from email reflector discussions ...................................................... 26
`13.1.2
`Downlink MIMO Scheme used in the concept evaluation ................................................................. 26
`13.1.3
`Remaining downlink issues from the January Ad Hoc on LTE that need to be resolved .............. 29
`13.2
`Description of SC-FDMA Uplink used in the concept evaluation ........................................................... 38
`13.2.1
`Contributions reflecting results from email reflector discussions ...................................................... 38
`13.2.2
`Basic Transmission Scheme .................................................................................................................. 38
`13.2.3
`Physical Layer Procedures ..................................................................................................................... 44
`13.2.4
`Physical Layer Measurements ............................................................................................................... 50
`13.2.5
`Downlink related UE Capability ............................................................................................................. 50
`14. RAN1/RAN3 Joint session on RRM for LTE .................................................................................... 52
`15. Other business ..................................................................................................................................... 54
`16. Closing of the meeting ........................................................................................................................ 55
`Annex A: List of participants at RAN1 #44 ............................................................................................. 56
`Annex B: TSG RAN WG1 meetings in 2006 .......................................................................................... 62
`Annex C: List of CRs agreed at RAN1#44 .............................................................................................. 63
`Annex D: List of Outgoing LSs .................................................................................................................. 64
`Annex E: List of Tdocs at RAN1 #44 ....................................................................................................... 65
`Annex F: List of actions (E-mail Approval) ............................................................................................. 96
`
` 2
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`Executive summary
`RAN WG1#44 meeting took place in Hyatt Regency Hotel in Denver, USA. The meeting started at 9:05 on Monday 13th
`February and finished at 17:05 on Friday 17th February.
`On the first day, after treating incoming LS and some Rel-5 and Rel-6 CRs, the documents for Rel-7 TDD topics such as
`3.84 Mcps TDD Enhanced Uplink and 7.68Mcps TDD Option were treated and the set of CRs to RAN1 core specs on 7.68
`Mcps option were agreed.
`Further proposals, comparisons and details of concepts for the WI Continuous Connectivity for Packet Data Users were
`discussed on Monday and Friday, and as a results 14 text proposal (1 after email approval) for TR 25.903 were agreed. As
`for MIMO for UTRA (Rel-7 WI), two different proposed schemes were discussed for the selection of evaluation scheme
`and as a conclusion RAN1 chairman decided to report the RAN1 situation on the selection of the evaluation scheme to the
`RAN plenary and recommend to select PARC for the further evaluation.
`LTE session started from the morning on the second day, 14th February. In this meeting there were more than 330
`contributions for LTE topics so that a lot of contributions were not treated due to lack of time. Some topics not treated in
`this meeting would be discussed on the RAN1 reflector until the next meeting. MIMO for LTE was discussed at MIMO
`Ad hoc session parallel to the main session on Tuesday and Wednesday. As the results of LTE discussion, 30 text
`proposals including the texts for email approval after the meeting were agreed to be included in TR25.814. As for LTE
`topics, in addition to RAN1 discussion, RAN1/RAN3 joint session on RRM for LTE was held on Wednesday evening and
`the short report is shown in section 14 on this minutes.
`The number of contributions for this meeting was 471 (without withdrawn contributions), and those documents were
`categorized as followed.
`
`
`
`Input
`Document
`33
`21
`3
`14
`13
`36
`0
`0
`8
`187
`156
`
`Discussed
`Document
`32
`21
`3
`14
`12
`36
`0
`0
`8
`85
`89
`
`Agenda Item
`
`Liaison Statement
`Maintenance of R99, Rel4, Rel5, Rel6 and other
`3.84 Mcps TDD Enhanced Uplink
`7.68 Mcps TDD Option
`MIMO in UTRA
`Continuous Connectivity for Packet Data Users
`Improved support of gaming over HSPA
`Improvements of MBMS
`Evolved UTRA and UTRAN (Physical Layer)
`Evolved UTRA and UTRAN (Physical Layer): Downlink
`Evolved UTRA and UTRAN (Physical Layer): Uplink
`
`
`
` 1
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`1. Opening of the meeting
`13/02/2006 09:05
`RAN1 Chairman, Mr. Dirk Gerstenberger and welcomed the participants to the RAN WG1 LTE Ad Hoc meeting and
`opened the meeting at 09.05.
`Mr. Sharat Chander from Cingular Wireless welcomed the delegates on behalf of the North American Friends of 3GPP.
`
`
`Call for IPR
`1.1
`13/02/2006 09:05
`The Chairman drew attention to Members' obligations under the 3GPP Partner Organizations' IPR policies. Every
`Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a
`member any IPR owned by the Individual Member or any other organization which is or is likely to become
`essential to the work of 3GPP.
`The attention of the members of this Technical Specification Group is drawn to the fact
`that 3GPP Individual Members have the obligation under the IPR Policies of their
`respective Organizational Partners to inform their respective Organizational Partners of
`Essential IPRs they become aware of.
`The members take note that they are hereby invited:
`•
`to investigate in their company whether their company does own IPRs which are, or are
`likely to become Essential in respect of the work of the Technical Specification Group.
`to notify the Director-General, or the Chairman of their respective Organizational
`Partners, of all potential IPRs that their company may own, by means of the IPR
`Statement and the Licensing declaration forms (e.g. see the ETSI IPR forms
`http://webapp.etsi.org/Ipr/).
`
`•
`
`Approval of the agenda
`
`R1-060270 Draft Agenda
`
`
`
`
`13/02/2006 09:10 Presented by Mr. Dirk Gerstenberger.
`Discussion (Question / Comment):
`Mr. RAN1 Chairman explained the scheduling during this meeting. Non-LTE will be discussed in Monday and
`LTE will start from Tuesday. We start the interference mitigation topic and then UP link topics. For downlink
`topics, we will treat the topics and documents useful for the other WGs such as interference mitigation, UE
`capability, cell search, measurement. MIMO Rel-7 will be treated in the evening of Tuesday.
`On Thursday evening, joint session with RAN3 will be held, the topics is the signalling and so on.
`Decision: This draft agenda was approved without any comments.
`
`
`
`
`
`
`
`
`
`(RAN1 Chairman)
`
` 2
`
`Approval of the minutes from the previous meetings
`3.
`R1-060272 Draft Report from RAN1#43 Meeting
`
`
`
`
`(RAN1 Secretary)
`13/02/2006 09:15 Presented by Mr. Yoshikazu Ishii.
`Discussion (Question / Comment):
`Decision: This draft report was approved in R1-050755.
`R1-060755 Approved Report from RAN1#43 Meeting
`
`R1-060273 Draft Report from RAN1 LTE Ad Hoc Meeting
`13/02/2006 09:15 Presented by Mr. Yoshikazu Ishii.
`Discussion (Question / Comment):
`
`
`
`
`
`
`
`
`
`(RAN1 Secretary)
`
`(RAN1 Secretary)
`
`
`
` 2
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`Decision: This draft report was approved in R1-050756
`R1-060756 Approved Report from RAN1 LTE Ad Hoc Meeting
`
`
`
`
`(RAN1 Secretary)
`
` 3
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`Report from TSG RAN#30 and RAN1 LTE Ad Hoc
`4.
` Report from TSG RAN#30 and RAN1 LTE Ad Hoc
`
`(RAN1 Chairman)
`R1-060271
`13/02/2006 09:20 Presented by Mr. Dirk Gerstenberger.
`Discussion (Question / Comment):
`Decision: This document was noted.
`
`
`
`
`
`
`
` 4
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`(RAN WG2, LG Electronics)
`
`5. Liaison statement handling
`
`
`R1-060274
` LS on Reference RAB Configurations for MBMS (To: RAN1)
`
`
`
`
`
`
`
`
`
`
`(RAN WG2, Qualcomm)
`13/02/2006 09:25 Presented by Mr. Serge Willenegger from Qualcomm Europe
`Discussion (Question / Comment):
`Decision: This document was noted. It was decided to prepare the draft LS in R1-060675 (Qualcomm)
`R1-060675
` Reply to LS on Reference RAB Configurations for MBMS (R2-053142)
`
`
`
`
`
`
`
`
`
`
`
`(Qualcomm Europe)
`14/02/2006 09:15 Presented by Mr. Serge Willenegger from Qualcomm Europe
`Discussion (Question / Comment):
`Decision: This LS was approved as final version.
`R1-060275
`Value range for Qoffmbms (To: RAN1, RAN4)
`13/02/2006 09:28 Presented by Mr. Dragan Vujcic from LG electronics
`Discussion (Question / Comment):
`Decision: This document was noted. It was decided to prepare the draft LS in R1-060676 (LGE)
`R1-060676
` Reply to LS on Value range for Qoffmbms (R2-053171) (LG Electronics)
`14/02/2006 09:15 Presented by Mr. Dragan Vujcic from LG electronics
`Discussion (Question / Comment):
`Decision: This LS was approved as final version.
`R1-060276
`Improved Support of IMS Realtime Services using HSDPA/HSUPA
`
`(To: RAN2, RAN1, Cc: RAN3)
`
`
`
`
`
`(RAN WG4, Nokia)
`13/02/2006 09:30 Presented by Mr. Markku Tarkiainen from Nokia.
`Discussion (Question / Comment):
`Decision: This document was noted.
`R1-060277
` LS on Puncturing limit for Conversational / speech 12.2 kbps + Interactive 0
`kbps (To: RAN1)
`
`
`
`
`
`
`
`(RAN WG5, Ericsson)
`13/02/2006 09:32 Presented by Mr. Johan Bergman from Ericsson
`Discussion (Question / Comment):
`Decision: This document was noted.
`
`R1-060278
` LS on Higher data rates in MBMS user service (To: SA1, Cc: RAN1)
`
`
`
`
`
`
`
`
`
`
`(SA WG4, Ericsson, Nokia)
`13/02/2006 09:35 Presented by Mr. Johan Bergman from Ericsson
`Discussion (Question / Comment):
`Decision: This document was noted.
`R1-060279
` Liaison Statement from RAN2 on RAB and the error-delay-profile for the
`performance characterization of VoIMS over HSDPA/EUL (To: RAN2, Cc:
`RAN1, RAN4, RAN5, SA1)
`
`
`
`
`(SA WG4, BenQ mobile)
`13/02/2006 09:36 Presented by Dr. Heino Gerlach from BenQ mobile
`Discussion (Question / Comment):
`Decision: This document was noted.
`R1-060612
` Draft Reply LS on RAB and the error-delay-profile for the performance
`characterization of VoIMS over HSDPA/EUL
`
`(Lucent Technologies)
`13/02/2006 09:40 Presented by Dr. Rainer Bachl
`Discussion (Question / Comment):
`There were some discussion on the simulation results and simulation assumption.
`Mr. RAN1 chairman commented that we can discuss and agree on the parameter of RAN1 (layer 1), but voice
`codec is beyond RAN1 area so that at least we should clear the Layer 1.
`Decision: It was decided to continue the offline discussion during the week and prepare the draft LS by Friday in
`R1-060677
`R1-060677
` Draft Reply LS on RAB and the error-delay-profile for the performance
`characterization of VoIMS over HSDPA/EUL
`
`(Lucent Technologies)
`17/02/2006 09:10 Presented by Dr. Rainer Bachl
`Discussion (Question / Comment):
`Decision: This document was noted.
`
` 5
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`(Qualcomm Europe)
`(Qualcomm Europe)
`
`Draft LS reply to SA4 on Delay Profiles for VoIP
`R1-060445
`Draft LS reply to SA4 on Delay Profiles for VoIP
`R1-060739
`17/02/2006 09:15 Presented by Mr. Juan Montojo
`Discussion (Question / Comment):
`Rainer Bachl from Lucent comment on the set of parameter important thing is that we confirm the simulation
`results and informa the set of parameter to SA4, however, it's very difficult to confirm because the parameter is
`provided by one company and it's not sure. Malgorzata Wimmer from Siemens supported to Lucent.
`Serger Willenegger commented that they sent the document during the week so that there are enough time for other
`companies to confirm.
`Karri Ranta-aho commented that he doesn't agree to send the parameter and different companies provide some
`proposal and we should send the golden proposal to SA4. And he suggested sending this situation on RAN1 by LS.
`RAN1 Chairman commented that we never seen such a RAB definition provided by proposal so that we should
`confirm to RAN2
`Finally, RAN1 chairman suggested the way forward.
`Decision: it was decided to merge R1-060739 and R1-060677 into an LS to RAN2 (R1-060740) for their work on a
`RAB indicating the error delay profiles obtained under the given assumptions and revisit the topic in March
`meeting.
`R1-060740
`
`
`
`(Telecom Italia)
`
` Draft LS on RAB and the error-delay-profile for the performance
`
`
`characterization of VoIMS over HSDPA/EUL
`
`
`
`
`
`
`
`
`
`(Qualcomm Europe, Lucent Technology)
`17/02/2006 17:05 Presented by Dr. Rainer Bachl
`Discussion (Question / Comment):
`Decision: This document was approved as the final version in R1-060753.
`R1-060674
`Response to ITU-R WP8F on PDNR ITU-R M.[IP CHAR] (To: RAN1, RAN2,
`RAN3, RAN4, RAN5, CT1, CT3, CT4, CT5, CT6, SA1, SA2, SA3, SA4, SA5)
`
`
`
`
`
`
`
`
`
`
`
`(ITU-R Ad Hoc, Telecom Italia)
`13/02/2006 09: 50 Presented by Mr. Enrico Buracchini from Telecom Italia.
`Discussion (Question / Comment):
`Decision: This document was noted. It was decided to provide comments directly to Enrico by Thursday and
`prepare the draft LS in R1-060678
`
`
`R1-060678
` Draft Response LS to ITU-R Ad Hoc
`17/02/2006 09: 50 Presented by Mr. Enrico Buracchini from Telecom Italia.
`Discussion (Question / Comment):
`Decision: The draft LS was approved in R1-060741
`
`
` LS on RAN1 discussion about the introduction of 1.6MHz
`R1-060491
`13/02/2006 09:55
`Discussion (Question / Comment): Without the presentation
`Decision: This LS was approved as the final version.
`
`(RAN WG1)
`
`
`R1-060407
`
`R1-060709
`
`
` Draft LS answer to RAN3 R3-060085 (=R1-060004) on RRM for LTE
`
`
`
`
`
`
`
`
`
`
`
`
`(Siemens)
` Draft LS Reply for Inter-Cell RRM
`
`
`
`(Qualcomm Europe)
`R1-060490
` Proposal for RAN1 Answer on LS on "RRM for LTE" from RAN3 (Alcatel)
`R1-060663
`Decision: R1-600407, R1-060490 and R1-060663 were treated at the drafting session on RRM on Tuesday
`evening.
`LS to RAN1 on additional WB-AMR RAB combination,
`
`VT bearer configuration and Uplink streaming 128 kbps combinations
`
`
`
`
`
`
`
`
`
`
` (RAN WG2, Vodafone)
`16/02/2006 09:15 Presented by Mr. Yannick Le Pezennec.
`Discussion (Question / Comment):
`Decision: It was decided to confirm L1 parameters via email until 22 Feb, if no concerns raised, send an LS to
`RAN2 indicating OK from RAN1 in R1-060729. After the meeting, there was no concerns on the reflector so that
`the reply LS in R1-060729 was sent to RAN2.
`
`R1-060727
` LS on Real Time Gaming Requirements (To: SA1, Cc: RAN1, 2 ,3)
`
`
`
`
`
`
`
`
`
`
` (RAN WG2, Cingular)
`16/02/2006 14:20 Presented by Mr. Dirk Gerstenberger on behalf of Cingular Wireless.
`
` 6
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`Discussion (Question / Comment):
`Decision: This document was noted.
`
`
`
`R1-060728
` LS on input to TS25.202 (To: RAN1, Cc: RAN2, RAN4)
`
`
`
`
`
`
`
`
`
`
`(RAN WG3, IPWireless)
`16/02/2006 14:25 Presented by Dr. Martin Beale
`Discussion (Question / Comment):
`Decision: This document was noted. The text is included in TS25.202
`R1-060736
` LS on input to TS25.202 (To: RAN1)
`
`
`
`
`
`
`
`
`
`
`
`
`16/02/2006 17:45 Presented by Dr. Martin Beale
`Discussion (Question / Comment):
`Decision: This document was noted. The text is included in TS25.202
`R1-060744
` Response to LS on TS25.202 (To: RAN1)
`17/02/2006 10:50 Presented by Dr. Martin Beale
`Discussion (Question / Comment):
`Decision: This document was noted. The text is included in TS25.202
`The updated version 25.202 v.1.1.1 is provided in R1-060745 for email approval until 24th February.
`
`
`
`
`
`
`(RAN WG4, IPWireless)
`
`
`
`(RAN WG2, IPWireless)
`
`
`
`
`
`
`R1-060747 LS on LTE Channel Models and simulations (To: RAN1)
`
`
`
`
`
`
`
`
`
`
`(RAN WG4, Ericsson)
`17/02/2006 15:45 Presented by Bo Göransson
`Discussion (Question / Comment):
`Rainer Bachl from Lucent asked on the link simulation model. The answer was that it's based on ITU-R model
`Joern Krause from Siemens asked whether the channel model will be updated in the future as it was mentioned that
`RAN4 will continue working on the channel model. The answer was that it's on of the topics on e-mail ad-hoc.
`Decision: This document was noted. RAN1 to adopt the proposal in R4-060334.
`
`
`Outgoing LS
`R1-060491
`
`
` LS on RAN1 discussion about the introduction of 1.6MHz
`(RAN WG1)
`(To: RAN)
`
`
`
`
`
`
`
` Reply to LS on Reference RAB Configurations for MBMS (R2-053142)
`
`
`(To: RAN2)
`
`
`
`
`
`
`
`(RAN WG1)
` Reply to LS on Value range for Qoffmbms (R2-053171)
`
`R1-060676
` (To: RAN2)
`
`
`
`
`
`
`
`(RAN WG1)
`R1-060687
`LS for input to TS 25.202
`(To: RAN2, RAN3, RAN4)
`(RAN WG1)
`R1-060697
`LS on support for different E-DCH and HS-DSCH serving cells
`
`
`
`
`
`
`(To: RAN2, Cc: RAN3, RAN4)
`
`
`
`
`(RAN WG1)
`R1-060719
`LS answer to RAN3 R3-060085 (=R1-060004) on RRM for LTE
`
`(To: RAN3, Cc: RAN2, RAN4)
`
`
`
`
`
`(RAN WG1)
`
`R1-060729
` Response LS on additional WB-AMR RAB combination, VT bearer
`configuration, and Uplink streaming 128 kbps combinations
`
` (To: RAN2)
`
`
`
`
`
`
`
`
`(RAN WG1)
`R1-060741
`Response LS to ITU-R Ad Hoc (To: ITU-R Ad Hoc)
`
`(RAN WG1)
`R1-060743
` Reply to LS on Synchronisation of Reconfiguration with activation time “now”
`
`
`(To: RAN2, Cc: RAN3, RAN4)
`
`
`
`
`(RAN WG1)
`
`R1-060675
`
`
`R1-060753
`
`
`Not Treated
`R1-060481
`
`
` LS on RAB and the error-delay-profile for the performance characterization of
`VoIMS over HSDPA/EUL (To: RAN2, Cc: SA4)
`
`(RAN WG1)
`
` Draft LS Reply for RACH Related Questions
`
`
`
`(Qualcomm Europe)
`
` 7
`
`

`

`Spec
`
`Release
`
`25.804
`
`Rel-6
`
`R1-060682
`
`25.213
`
`Rel-6
`
`R1-060554
`
`25.214
`
`Rel-6
`
`R1-060619
`
`25.221
`
`Rel-7
`
`R1-060620
`
`25.222
`
`Rel-7
`
`R1-060621
`
`25.224
`
`Rel-7
`
`Title
`
`Simulation results of LCR TDD enhanced uplink
`Correction to number of configured DPDCHs when E-
`DPDCH is configured
`Correction to number of configured DPDCHs in
`relation to E-DPDCH power scaling
`Introduction of the Physical Layer Common Control
`Channel (PLCCH)
`Introduction of the Physical Layer Common Control
`Channel (PLCCH)
`Introduction of the Physical Layer Common Control
`Channel (PLCCH)
`
`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`6. Maintenance of R99, Rel4, Rel5, Rel6
`The overview of discussion and conclusion on this section is as followed:
`
`
`1. Code hopping for LCR TDD enhancement was seen as an issue that can be considered by Work Item so that the
`proponent will submit the proposal WID in next RAN Plenary.
`2. Regarding reconfiguration of EUDCH, it was decided to whether to specify behavior or not, which should be
`based on consequent analysis, would be provided by next RAN1 meeting.
`3. Regarding reconfiguration with activation time "now", there were two proposals from LG electrics and Siemens.
`And the conclusion that LG proposal seems feasible and shoes not require newly defined UE and new
`specification at all so that based on the LG proposal the LS was sent to RAN2 in R1-060743.
`4. Agreed CR
`Tdoc
`Number
`R1-060679
`
`
`R99 CRs + shadow CRs
`6.1
`No document
`6.2
`Rel4 CRs + shadow CRs
`No document
`6.3
`Rel5 CRs + shadow CRs
`R1-060330
` 25.214 CR0414 (Rel-5, F) "Clarification of Power Control for HS-PDSCH"
`
`
`
`
`
`
`
`
`
`
`
`
`(Agere Systems)
`13/02/2006 10:00 Presented by Mr. Matthew Cooke
`Discussion (Question / Comment):
`Ericsson, Nokia, Nortel and Siemens showed the objection to this CR because Node B behaviour is not intend to be
`specified and also there are no benefits for UE side by this CR.
`Decision: This CR was rejected because NodeB behaviour is not intended to be specified in detail.
`R1-060331
` 25.214 CR0415 (Rel-6, A) "Clarification of Power Control for HS-PDSCH"
`
`
`
`
`
`
`
`
`
`
`
`
`(Agere Systems)
`13/02/2006 10:00 Presented by Mr. Matthew Cooke
`Discussion (Question / Comment):
`Decision: This CR was rejected because NodeB behaviour is not intended to be specified in detail.
`
`
`Rel6 CRs
`6.4
`R1-060523
` TR25.804CR0002(Rel-6, B) "Analysis of intra-frame Scrambling Code hopping
`for LCR TDD Enhanced Uplink"
`
`
`
`
`
`
`(CATT)
`
` 8
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`13/02/2006 10:05 Presented by Mr. Wang Ke.
`Discussion (Question / Comment):
`Nicholas Anderson from IPWireless raised a concern on the UL synchronization on the simulation. Wang Ka from
`CATT answered the they assumed the UL synchronization on their simulation. Also Nicholas Anderson pointed out
`on the impact of the code hopping on the LCR-TDD.
`Mr. Chairman commented that this topics is not for SI phase, it means that we don't treat this on the TR25.804
`Decision: Offline discussion and come back Friday. The code hopping was seen as an issue that can be considered
`by work item so that this CR was not agreed.
`R1-060524
` TR25.804CR0001r2(Rel-6, B) "Simulation results of LCR TDD enhanced
`uplink"
`
`
`
`
`
`
`
`
`
`
`(CATT)
`13/02/2006 10:18 Presented by Mr. Wang Ke.
`Discussion (Question / Comment): .
`Decision: This CR was agreed in principle (pending the part on intra-frame code hopping which is for further
`discussion until Friday). It was decided to prepare revision of the CR in R1-060679.
`R1-060679
` TR25.804CR0001r3 (Rel-6, B) "Simulation results of LCR TDD enhanced
`uplink"
`
`
`
`
`
`
`
`
`
`
`(CATT)
`17/02/2006 09:55 Presented by Mr. Wang Ke.
`Discussion (Question / Comment):
`Decision: This CR was agreed. (WI code on the cover sheet was added by secretary)
`R1-060553
` 25.213 CR0084(Rel-6, F) "Correction to number of configured DPDCHs when
`E-DPDCH is configured"
`
`
`
`
`
`
`
`(Philips)
`13/02/2006 11:15 Presented by Mr. Matthew Baker
`Discussion (Question / Comment):
`Nokia, Ericsson, LGE and Panasonic showed their support to this CR except for the wording.
`Decision: This CR was agreed in principle with exact wording to be discussed further and it was revised in R1-
`060682
`R1-060682
`
`
`
`
`
`
`
`
`
`
`
`
`
`(Panasonic)
`
` 25.213 CR0084r1(Rel-6, F) "Correction to number of configured DPDCHs
`when E-DPDCH is configured"
`
`
`
`
`
`
`(Philips,
`Ericsson, LGE, Nokia, Panasonic, Qualcomm)
`17/02/2006 09:55 Presented by Mr. Matthew Baker
`Discussion (Question / Comment):
`Decision: This CR was agreed.
`R1-060554
` 25.214 CR0416(Rel-6, F) "Correction to number of configured DPDCHs in
`relation to E-DPDCH power scaling"
`
`
`
`
`(Philips)
`13/02/2006 11:25 Presented by Mr. Matthew Baker
`Discussion (Question / Comment):
`Decision: This CR was agreed.
`R1-060589
` Reconfiguration of EUDCH
`13/02/2006 11:28 Presented by Mr. Hidetoshi Suzuki
`Discussion (Question / Comment):
`Johan B from Ericsson commented that before making a decision we need the consequent analysis. Karri Ranta-aho
`from Nokia commented that he agree to this document generally so that the base line is no specify reconfiguration
`but we may do work for some special case.
`Sarah Boumendil from Nortel commented that she does not want to specify but we may do have some analysis on
`the potential case so that try to continue discussion until next meeting.
`Decision: This document was noted. It was decided that to decide whether to specify behaviour or not, which
`should be based on consequent analysis, should be provided by RAN1#44bis.
`
`
`Other
`6.5
`R1-060619
` 25.221CR0135 (Rel-7, B)"Introduction of the Physical Layer Common Control
`Channel (PLCCH)"
`
`
`
`
`
`
`
`
`(IPWireless)
`13/02/2006 11:45 Presented by Mr. Nicholas Anderson
`Discussion (Question / Comment):
`No comment for objection and comments
`Decision: This CR was considered to be agreed.
`
` 9
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`R1-060620
`
`
`
` 25.222CR0126 (Rel-7, B)"Introduction of the Physical Layer Common Control
`Channel (PLCCH)"
`
`
`
`
`
`
`
`(IPWireless)
`13/02/2006 11:48 Presented by Mr. Nicholas Anderson
`Discussion (Question / Comment):
`Decision: This CR was considered to be agreed.
`R1-060621
` 25.224CR0149 (Rel-7, B)"Introduction of the Physical Layer Common Control
`Channel (PLCCH)"
`
`
`
`
`
`
`
`(IPWireless)
`13/02/2006 11:50 Presented by Mr. Nicholas Anderson
`Discussion (Question / Comment):
`Nicholas Anderson from IPWireless clarified that RAN2 and RAN3 CRs are also available at this meeting.
`Decision: This CR was considered to be agreed.
`
`
`Fixed position and flexible position in TR25.993 (Panasonic)
`R1-060590
`13/02/2006 11:50 Presented by Mr. Hidetoshi Suzuki
`Discussion (Question / Comment):
`Johan Bergman from Ericsson commented that he doesn't want to specify the both.
`Evelyne Le Strat.from Nortel asked if we did not have any objection for the special case on the last plenary so what
`is the conclusion on the last plenary meeting. Hidetoshi Suzuki from Panasonic clarified that RAN conclusion was
`for only VoIP case and this document discusses the wider case.
`Decision: It was decided that Specification of both alternatives should be avoided whenever possible.
`R1-060530
` Synchronization with activation time “now”
`
`
`(LG Electronics)
`13/02/2006 12:00 Presented by Mr. Dragan Vujcic
`Discussion (Question / Comment):
`Malgorzata Wimmer from Siemens asked why the simulation assumption on ULSIRDPCCH target is 5 dB because
`conclusion mentioned ULSIRDPCCH targets is below 5dB. Dragan Vujcic from LGE answered that 5dB is "zero"
`target and the target is the implementation matter.
`Karri Ranta-aho from Nokia raised a concern on the SHO case.
`Decision: This document was noted
`
`
`R1-060605
`
` Call Setup Delay: Radio link reconfiguration with activation time now"
`
`
`
`
`
`
`
`
`
`
`
`
`(Siemens)
`13/02/2006 12:15 Presented by Ms. Malgorzata Wimmer.
`Discussion (Question / Comment): This document was moved from section 5.
`Yannick Le Pezennec from Vodafone commented that this proposal is the same issue as the LGE but this is UE side.
`The discussion on the detection and change of scrambling code continued
`Dragan Vujcic from LGE clarified that their proposal does not require on the RAN1 spec but change the RAN2 and
`RAN3 spec.
`Decision: This document was noted.
`Conclusion from the discussion on R1-060530 and R1-060605
`Draft an LS (R1-060683) reply indicating that LG proposal seems feasible (concerns expressed on NodeB
`complexity and lack of power control (and even data) during the detection period, SHO situation w.r.t. sync loss)
`and does not require newly defined UE behaviour, note that there are issues with too low DPCCH SIR target that
`could be overcome, e.g. through temporary SIR target increase (no new functionality needed in the UE). Mention
`that no new specification might be needed at all for the LG proposal. Alternative proposals discussed (L1 signalling
`TFCI, FBI), which require new UE behaviour.
`
`R1-060683
`
`[DRAFT] Reply to LS on Synchronisation of Reconfiguration with activation
`
`time “now”
`
`
`
`
`
`(LG Electronics, Ericsson, Vodafone)
`17/02/2006 12:15 Presented by Mr.. Dragan Vujcic
`Discussion (Question / Comment):
`Decision: This draft LS was approved in R1-060743with addition of RAN3 in Cc.
`R1-060735
`Synchronization with activation time “now” ; Impacts on R,99, Rel-4, and Rel.5
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(Siemens)
`17/02/2006 10:05 Presented by Dr. Joern Krause
`Discussion (Question / Comment): This document was treated with related to R1-060683.
`Decision: This document was noted. From the discussion on this contribution, it was clarified that Reconfiguration
`of UL scrambling code for a UE is not considered to make the radio link appear to be “new”.
`
`
` 10
`
`

`

`3GPP TSG RAN WG1 Meeting #44bis
`Athens, Greece, 27 – 31 March, 2006
`
`R1-061099
`
`F-DPCH support in early Rel-6 UE
`R1-060453
`13/02/2006 12:45 Presented by Mr. Serge Willenegger
`Discussion (Question / Comment):
`Yannick Le Pezennec from Vodafone commented that

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket