R1-031163
`
`R1-03xxxx
`
`3GPP TSG RAN WG1 Meeting #35
`Lisbon, Portugal, 17 – 21 November, 2003
`3GPP TSG RAN WG1 Meeting #34
`Seoul, Korea 6th – 10th October, 2003
`
`
`Agenda item
`
`2
`
`
`
`Title:
`
`
`Document for:
`
`
`
`
`
`
`[DRAFT r1] Report of 3GPP TSG RAN WG1 #33
`(New York, NY, USA, 25 – 29 August, 2003)
`
`Comments and approval
`
`Source:
`
`
`
`WG1 Secretary
`
`
`
`Notes:
`
`All timestamps in this document are in CET unless otherwise noted.
`
`The local time is EDT, or GMT-4H. To obtain the local time from the timestamps, subtract 6 hours.
`
`
`
`Fact Summary
`
`Meeting:
`
`3GPP TSG RAN WG1 #33
`
`Dates:
`
`Venue:
`
`Host:
`
`25th through 29th August 2003
`
`Marriott Marquis New York Hotel; New York, NY, USA
`
`North American Friends of 3GPP
`
`Attendees:
`
`100 delegates from 47 3GPP members (companies)
`
`Tdocs registered:
`
`320 (including some post-meeting artefacts)
`
`
` Alcatel, Ericsson, Lucent Technologies, Mitsubishi Electric, Nokia, Nortel Networks, Orange, Siemens, Sonera, TIM, T-Mobile, Vodafone
`
`NAC1057
`Page 1
`
`

`

`Table of contents
`
`
`
`1. Opening of the meeting ............................................................................................................................ 1
`1.1 Call for IPR .............................................................................................................................................................. 1
`
`2.
`
`3.
`
`4.
`
`Approval of the draft agenda and the minutes of the previous meeting ................................................... 1
`
`Report from TSG RAN#20 ...................................................................................................................... 2
`
`Identification of incoming LS and actions in the answering .................................................................... 2
`
`Change request handling .......................................................................................................................... 3
`5.
`5.1 R99 CRs + shadow CRs .......................................................................................................................................... 3
`3
`TS 25.214
`Node B behaviour during subsequent RL synchronisation ................................................................................................. 3
`4
`TS 25.224
`5.2 Rel4 CRs + shadow CRs.......................................................................................................................................... 4
`4
`TS 25.223
`4
`TS 25.224
`5.3 Rel5 CRs + shadow CRs.......................................................................................................................................... 4
`4
`TS 25.211
`4
`TS 25.212
`Turbo coding
`5
`TS 25.213
`6
`TS 25.214
`7
`TS 25.215
`7
`TS 25.222
`7
`TS 25.224
`7
`TS 25.225
`5.4
`Inputs for TS 34.108 + TR 25.993 ........................................................................................................................... 8
`5.5 Other inputs ............................................................................................................................................................. 8
`
`5
`
`Beamforming Enhancements ................................................................................................................... 9
`6.
`Text proposals for TR 25.887 .................................................................................................................................. 9
`6.1
`6.2 Other inputs ............................................................................................................................................................. 9
`
`7. MBMS ...................................................................................................................................................... 9
`7.1
`Text proposals for TR 25.803 .................................................................................................................................. 9
`7.2 Other inputs ........................................................................................................................................................... 10
`
`8.
`
`Improvement of Inter-frequency and intersystem measurements for 1.28 Mcps TDD .......................... 11
`
`9. MIMO .................................................................................................................................................... 11
`
`10. Enhanced Uplink DCH ........................................................................................................................... 12
`10.1
`Scheduling........................................................................................................................................................ 13
`10.2
`HARQ .............................................................................................................................................................. 14
`10.3
`Channel structure ............................................................................................................................................. 15
`PhCH structure .................................................................................................................................................................. 15
`Pilots/power control .......................................................................................................................................................... 15
`TrCH structure .................................................................................................................................................................. 16
`10.4
`Fast DCH setup ................................................................................................................................................ 16
`10.5
`Other inputs ...................................................................................................................................................... 17
`
`11. Uplink Enhancements for UTRA TDD .................................................................................................. 17
`
`12. Analysis of higher chip rates for UTRAN evolution (TDD) .................................................................. 17
`
`13. OFDM .................................................................................................................................................... 18
`13.1
`Simulation methodology and simulation results .............................................................................................. 18
`13.2
`Complexity aspects .......................................................................................................................................... 19
`13.3
`Other inputs ...................................................................................................................................................... 19
`
`NAC1057
`Page 2
`
`

`

`14. Radio Link Performance Enhancements ................................................................................................ 20
`14.1
`HSDPA enhancements ..................................................................................................................................... 20
`14.2
`TX diversity with more than 2 antennas .......................................................................................................... 20
`14.3
`Power control enhancements for TDD ............................................................................................................. 20
`14.4
`Other inputs ...................................................................................................................................................... 20
`
`15. Enhancements to OTDOA positioning using advanced blanking methods ........................................... 21
`
`16. TEI6 ........................................................................................................................................................ 21
`
`17.
`
`Issues postponed from the meeting (late or revised CRs, TR approval etc.) ......................................... 21
`
`18. Approval of outgoing LS ........................................................................................................................ 21
`
`19. Other issues ............................................................................................................................................ 22
`
`20. Closing of the meeting: 5.00 PM............................................................................................................ 22
`
`Annex A:
`
`List of participants ................................................................................................................ 23
`
`Annex B: List of CRs treated at RAN1#33 and/or presented to TSG RAN #21 ................................... 28
`
`Annex C:
`
`TSG RAN WG1 meetings 2003 ............................................................................................ 32
`
`Annex D:
`
`Updated WG1 Email Ad-hocs Codes .................................................................................. 33
`
`Annex E: List of tdocs at RAN1#33 ........................................................................................................... 34
`
`NAC1057
`Page 3
`
`

`

`1.
`
`Opening of the meeting
`
`At 9:05AM on August 25, 2003 in local time, the chairman, Mr Dirk Gerstenberger (Ericsson) opened the meeting. Mr.
`Donald Zelmer (Cingular Wireless LLC, TSG RAN Vice chairman) welcomed the delegates on behalf of the host, The
`North American Friends of 3GPP, and briefly introduced the meeting facilities.
`
`1.1 Call for IPR
`
`The chairman made the following call for APRs, and asked ETSI members to check the latest version of ETSI’s policy
`available on the web server:
`
`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 draft agenda and the minutes of the
`previous meeting
`
`R1-030641 Draft Agenda for TSG RAN WG1 meeting No.33
`Source: TSG RAN WG1 Chairman
`Discussion: No comments/questions
`Decision: This agenda was approved without changes.
`
`R1-030803 Draft1 Minutes of the RAN1-RAN2 joint Meeting
`Source: Secretary
`Discussion: The secretary explained that this document was already updated and made available in RAN2 reflector but the
`changes were very small. The only change pertaining to RAN1 was a prefix of RAN1 tdoc was corrected from “R2” to
`“R1”.
`Decision: This document was approved without questions and comments.
`
`R1-030642 Draft Report of 3GPP TSG RAN WG1 #32 meeting
`Source: Secretary
`Discussion: No comments/questions
`Note: This document was uploaded to the meeting server and made available in the evening of Day3
`Decision: This report was approved in the morning on Day5.
`
`3.
`
`Report from TSG RAN#20
`
`R1-030850 Report from RP#20
`
`NAC1057
`Page 4
`
`

`

`Source; Chairman
`Discussion: Some points in this presentation were;
`1)
`Isolated impact analysis for all R99, Rel4 and Rel5 CRs is to be filled in by the WGs from now
`onWI/SI Rapporteurs to provide accurate information on the expected completion date and percentage
`completed for the work items
`There were no questions/comments to this report.
`Decision: The report was noted.
`
`4.
`
`Identification of incoming LS and actions in the
`answering
`
`(Cc/To T1) LS on Description of HS-DSCH Radio bearers (R2-031471)
`R1-030643
`Source: TSG RAN WG2
`Discussion: The technical discussion took place actually under Agenda Item 5.4 “Inputs for TS 34.108 + TR 25.993” in
`the day2 morning. Related discussion papers were R1-030648, R1-030728, and R1-030874
`Decision: The decision was postponed to the next meeting.
`
`(Cc/To S2) Liaison Statement on DRX parameter (R2-031473)
`R1-030644
`Source: TSG RAN WG2
`Discussion: No questions/comments
`Decision: The LS was noted.
`
`R1-030645
`
`(Cc/To S2) Response to LS on Minimum UE Capability Required for supporting
`MBMS (R2-031482)
`Source: TSG RAN WG2
`Discussion: No questions/comments
`Decision: The LS was noted.
`
`R1-030646
`
`(Cc/To S2) Reply to LS on Core Network Provision of separate flows for P2P and
`P2M radio Transmission (R2-031483)
`Source: TSG RAN WG2
`Discussion: No questions/comments
`Decision: The LS was noted.
`
`R1-030647
`
`(To) Reply to LS on Core Network Provision of separate flows for P2P and P2M
`radio Transmission (S4-030558)
`Source: TSG RAN WG4
`Discussion: No questions/comments
`Decision: The LS was noted.
`
`R1-030684
`
`(To) LS on the material to be submitted to ITU-R WP8F#11 for Revision 4 of
`Recommendation ITU-R M.1457
`Source: ITU-R Ad Hoc
`Discussion: No questions or immediate comments
`Decision: Comments on the proposed text should be provided to Mr. Alessandro Pace, TELECOM ITALIA
`S.p.A. and the response LS should be prepared and sent by the end of Friday, 29th August 2003.
`
`Note: The response was drafted in R1-030929 and approved to be sent as R1-030942. See AI 18.
`
`(To) LS on HSDPA Node-B HS-DPCCH signalling Detection Performance
`R1-030843
`Source: TSG RAN WG4
`Discussion: No questions/comments
`Decision: The referenced tdocs need to be provided and the answer LS will be prepared at the next meeting
`(RAN1#34) so that it will become available to RAN4 by their next meeting in November.
`
`Note: This LS from RAN4 and referenced tdocs will be provided in tdoc R1-031078 for RAN1#34.
`
`(To) LS on addition of 768kbps bearer to TS 34.108
`R1-030847
`Source: TSG T WG1
`
`NAC1057
`Page 5
`
`

`

`Discussion: A question was raised by Vodafone how this modification became necessary. Nokia clarified that there was
`no definition of 768kbps configuration in 34.108 whereas 25.306 and other specification provide that definition. Vodafone
`indicated concerns to recommend this change for R99.
`Decision (as of Day1 morning): Check the L1 parameters and come back on Friday (Day5)
`Note: This LS later turned out to be wrong tdoc and given to WG1 by mistake. This was replaced by R1-
`030869 on Day3 morning. But, RAN1 could not notice any difference between the old (wrong) and the new
`(correct) documents and therefore the discussion over R1-030847 (T1-031255) was considered still valid.
`
`(To) LS on addition of 768kbps bearer to TS 34.108 (T1-031252)
`R1-030869
`Source: TSG T WG1
`Discussion: In the morning of Day5 the discussion resumed with the new (correct) version of LS. Nokia reported any party
`provided no feedback.
`Decision: RAN1 agreed to recommend T1 to update TS34.108 for Rel-4 and onward. The answer LS would be
`prepared in R1-030930. See AI 18 in this report for further discussion on the response LS.
`
`5.
`
`Change request handling
`
`5.1
`
`R99 CRs + shadow CRs
`
`TS 25.214
`
`Node B behaviour during subsequent RL synchronisation
`
`QUALCOMM
`R1-030685 UL synchronization
`This is a discussion paper, which gives background consideration for the R99 & R4 CRs in R1-030759. This paper
`pointed out that there are two scenarios where UE may go to maximum or minimum transmit power level depending on
`the improper behaviour of Node-B, and proposes clarifications in the specifications for R99+ Rel-4 and Rel-5 respectively.
`
`Qualcomm
`R1-030759 CR25.214-332(R99): UL synchronization
`Not approved (28/08/2003 14:23). Later this was revised into R1-030894 and discussed along with R1-030814.
`
`R1-030814 CR25.214-327r1(Rel-5): Correction to TPC command generation on downlink
`during RL Failure procedure
`Nokia
`Not approved (28/08/2003 14:23). This CR was originally intended for Rel-5 only. But discussed under R99 subject since
`this is about the same subject with R1-030759
`
`WG1 Decision regarding the issue
`
`For R99/Rel4
`
`a) do nothing on the specifications, and
`
`b) document improper UTRAN behaviour in the LS (R1-030902) and the RAN1#33 meeting report
`
`For Rel5 (or later):
`
`a) introduce SHO indicator over Iub
`
`R1-030895
`
`[DRAFT] LS on Node B behaviour during subsequent RL synchronization
`
`Qualcomm
`This LS was prepared according to the WG decision mentioned above. Contents were agreed and the final version to be
`was in R1-030902. (See agenda 18)
`
`Qualcomm
`R1-030894 CR25.214-332r1(R99): UL synchronization
`WG Noted. It was suggested that this might be presented to RP#21 as a company proposal. At RP#21, the CR was
`revised twice and finally approved.
`
`NAC1057
`Page 6
`
`

`

`TS 25.224
`
`R1-030918 CR25.224-123r1 (R99), -124r1(Rel-4) & -125r1(Rel-5): DTX and Special Bursts in
`case of no data on S-CCPCH and Beacon Channels
`InterDigital
`Approved. This was originally proposed as Rel-4 CR in tdoc 711 and R99 CR was found to be needed.
`
`5.2
`
`Rel4 CRs + shadow CRs
`
`TS 25.223
`
`R1-030750 CR25.223-035(Rel-4) & -036(Rel-5): Correction to Combination of physical
`channels in uplink
`Samsung
`
`Not approved
`
`TS 25.224
`
`R1-030711 CR25.224-xxx (Rel-4) & -yyy(Rel-5): DTX and Special Bursts in case of no data on
`S-CCPCH and Beacon Channels
`InterDigital
`This is a proposal of changes for Rel4 TS 25.224. Contents were greed and base CR # was given as 123 that should be
`issued for R99 with Rel-4/5 shadows. The CRs were issued in R1-030918 and agreed. (See 5.1)
`
`5.3
`
`Rel5 CRs + shadow CRs
`
`TS 25.211
`
`R1-030652 CR25.211-186 & CR25.214-326 (Rel-5): Removal of the combination of TxAA
`Mode 1 with HS-SCCH Nokia
`CR25.211-186 was revised in R1-030857 (see below) to indicate that 4 bullets in 5.3.1 are valid for DPCH only. Related
`LS is drafted in R1-030858 CR25.214-326 was approved.
`
`R1-030857 CR25.211-186r1(Rel-5): Removal of the combination of TxAA Mode 1 with HS-
`SCCH Nokia
`Nokia
`
`Approved.
`
`[DRAFT] LS on HS-SCCH transmit diversity options
`R1-030858
`This LS was to inform RAN2/3/4 that HS-SCCH uses only STTD.
`
`Qualcomm
`
`R1-030658 On SCH & P-CCPCH Tx diversity Nokia
`Noted as the basis of discussion on R1-030659
`
`R1-030659 CR25.211-187(Rel-5): On SCH & P-CCPCH Tx diversity
`Revised to include comments and proposed solution
`
`Nokia
`
`R1-030931 CR25.211-187r1(Rel-5): On SCH & P-CCPCH Tx diversity Nokia
`Continue discussion until next meeting. Revised into 982 for R1#34 Resubmitted as R1-030982
`
`TS 25.212
`
`R1-030752 CR25.212-179(Rel-5): Correction on table number in first interleave description
`
`Panasonic
`
`Agreed
`
`R1-030849 CR25.212-178r2(Rel-5): Clarification on Single Transport Format Detection
`
`Nokia
`Agreeable CR text was requested, which clarifies that Fixed positions and CRC have to be used for STFD The CR was
`revised into R1-030860
`
`NAC1057
`Page 7
`
`

`

`R1-030860 CR25.212-178r3(Rel-5): Clarification on Single Transport Format Detection
`
`Nokia
`Technically agreed. Revise to correct sub clause numbering into R1-030932
`
`R1-030932 CR25.212-178r4(Rel-5): Clarification on Single Transport Format Detection
`
`Nokia
`
`Approved
`
`Turbo coding
`
`R1-030726 Some simulations evaluating solutions for the HS-DSCH rate matching problem
`
`Siemens, InterDigital
`R1-030725 Proposed modified HS-DSCH rate matching algorithm
`InterDigital
` Bit interleaving to resolve Turbo coder irregularities in HSDPA
`
`Samsung
`Above three tdocs were noted as technical input for Turbo Coding.
`
`R1-030808
`
`Siemens,
`
`R1-030831 CR25.212-177r1(Rel-5): HS-DSCH Rate Matching Algorithm Siemens,
`InterDigital
`
`Not agreed.
`
`Way forward discussion
`
`Among listed three options, WG favoured toward Option a)
`
`a) do nothing (scheduler may avoid critical code rates), study if there is impact on CQI reporting
`
`b) Correction of RM
`
`c) Bit interleaver
`
`TS 25.213
`
`R1-030689 CR25.213-062(Rel-5): Clarification of 16QAM modulation description
`
`Ericsson
`
`Agreed
`
`R1-030686 Scrambling code & phase reference combinations for DL HS-x channels
`
`QUALCOMM
`Noted as discussion paper to provide background for the CR in R1-030758
`
`R1-030758 CR25.213-063(Rel-5): Scrambling code & phase reference combinations for DL
`HS-x channels
`Qualcomm
`Agreed in principle revised into R1-030862
`
`R1-030862 CR25.213-063r1(Rel-5): Scrambling code & phase reference combinations for DL
`HS-x channels
`Qualcomm
`CR is technically endorsed and presented with linked RAN WG2 CR in RP-030502 by WG2 at RAN#21. There was an
`intensive discussion over the issue and the CRs were rejected. Refer to the RAN #21 meeting report for the details.
`
`TS 25.214
`
`R1-030652 CR25.211-186 & CR25.214-326 (Rel-5): Removal of the combination of TxAA
`Mode 1 with HS-SCCH Nokia
`CR25.214-326 was approved. CR25.211-186 was revised in R1-030857 (see below) to indicate that 4 bullets in 5.3.1 are
`valid for DPCH only. Related LS is drafted in R1-030858
`
`R1-030649 CR25.214-325(Rel-5): Correction of CQI definition table
`
`Fujitsu
`
`NAC1057
`Page 8
`
`

`

`Agreed
`
`R1-030741 CR25.214-328(Rel-5): Clarification of power scaling with HS-DPCCH
`Panasonic
`No agreement reached. Revised to include solution after off-line discussion. Revised into R1-030863
`
`Philips,
`
`R1-030863 CR25.214-328r1(Rel-5): Clarification of power scaling with HS-DPCCH Philips,
`Panasonic, Nokia
`Technically agreed. Revise to clarify the statement. Revised into R1-030934.
`
`R1-030934 CR25.214-328r2(Rel-5): Clarification of power scaling with HS-DPCCH Philips,
`Panasonic, Nokia
`
`Approved.
`
`R1-030844 CR25.214-329r2(Rel-5): CQI reporting in downlink compressed mode Philips
`
`Philips
`Revise into R1-030864
`
`R1-030864 CR25.214-329r3(Rel-5): CQI reporting in downlink compressed mode Philips
`
`Philips
`
`Approved
`
`Philips
`R1-030744 TPC command combining with Algorithm 1 in SHO
`This discussion tdoc was noted. After discussions it was recognized to send an LS to RAN2 regarding signalling change
`so that UEs can become aware of current TPC off-set value for better estimation. The LS was drafted in tdoc R1-030920.
`sent as R1-030954.
`
`R1-030920 Draft LS on Signalling of DL TPC-bit power offset to UE (To: R2 Cc:_) Philips,
`Nokia, Panasonic, Motorola
`Went through e-mail discussion and revised into the final in R1-030954, which was sent to RAN2 and RAN4 on
`September 15. See Agenda 19
`
`R1-030753 CR25.214-333(Rel-5): Clarification on CQI repetition behaviour
`
`Panasonic
`Revised to take comments and to simplify the descriptions into R1-030865..
`
`R1-030865 CR25.214-333r1(Rel-5): Clarification on CQI repetition behaviour
`
`Panasonic
`Approved. Further clarification may be necessary for the case of k=0.
`
`R1-030754 CR25.214-330(Rel-5): Clarification of HS-SCCH reception
`Revise to take comments into R1-030866.
`
`Panasonic
`
`R1-030866 CR25.214-330r1(Rel-5): Clarification of HS-SCCH reception Panasonic
`Approved
`
`R1-030755 CR25.214-331(Rel-5): Clarification on reconfiguration of HSDPA
`
`Panasonic
`Revised into R1-030868
`
`R1-030868 CR25.214-331r1(Rel-5): Clarification on reconfiguration of HSDPA
`
`Panasonic
`Revised into R1-030919.
`
`R1-030919 CR25.214-331r2(Rel-5): Clarification on reconfiguration of HSDPA
`
`Panasonic
`Revised into R1-030935 for better wording.
`
`R1-030935 CR25.214-331r3(Rel-5): Clarification on reconfiguration of HSDPA
`
`Panasonic
`
`NAC1057
`Page 9
`
`

`

`Comments were to be provided and the proponent was free to present this CR to RAN as a company proposal. However
`the proponent seems to have chosen to continue trying for WG agreement. It was further revised into R1-031068 for
`RAN1#34.
`
`R1-030757 CR25.214-324r1(Rel-5): clarification of power preamble and compressed mode
`
`Panasonic
`
`Not agreed
`
`TS 25.215
`
`R1-030810 CR25.215-144r1(Rel-5): Beamforming Enhancement support in Rel'5
`Agreed
`
`Nokia
`
`TS 25.222
`
`R1-030832 CR25.222-115r1(Rel-5): HS-DSCH rate-matching algorithm InterDigital,
`Siemens
`Not agreed (Mirror of R1-030831)
`
`TS 25.224
`
`R1-030751 CR25.224-122(Rel-5): Correction to HS-DSCH Procedure
`Not agreed
`
`Samsung
`
`R1-030815 CR25.224-121r2(Rel-5): Clarification on PDSCH Downlink Power Control
`Procedures IPWireless, Siemens
`CR text was agreed. Revised to include isolated impact analysis into R1-030872.
`
`R1-030872 CR25.224-121r3(Rel-5): Clarification on PDSCH Downlink Power Control
`Procedures IPWireless, Siemens
`
`Agreed
`
`TS 25.225
`
`R1-030818 CR25.225-071r2(Rel-5) "Definition of Transmitted Code Power, RSCP, ISCP and
`SIR measurements in the case of antenna diversity for TDD" Siemens,
`IPWireless
`Agreed in principle. Revised to provide the isolated impact analysis into R1-030873.
`
`R1-030873 CR25.225-071r3(Rel-5) "Definition of Transmitted Code Power, RSCP, ISCP and
`SIR measurements in the case of antenna diversity for TDD" Siemens,
`IPWireless
`Despite that this was instructed to make this available 5/9/03, this was never become available. Renumbered as R1-
`031081 for RAN1#34.
`
`
`
`
`
`
`
`
`
`
`
`NAC1057
`Page 10
`
`

`

`5.4
`
`Inputs for TS 34.108 + TR 25.993
`
`R1-030643
`
`(Cc/To T1) LS on Description of HS-DSCH Radio bearers (R2-031471)
`
`Source: TSG RAN WG2
`Vodafone
`R1-030648 Combinations of radio bearers for use with HSDPA
`R1-030728 CR34.108-xxx: Combinations of radio bearers on DPCH and HS-PDSCH
`
`Vodafone
`The LS from RAN2 was not by itself requesting anything to RAN1. But, it brought up the issue of test cases into light.
`Tdocs R1-030648 and R1-030728 were an effort to provide some solution. But RAN1 could not come to a single
`conclusion during the meeting period and agreed to continue the discussion until the next meeting #34. LS to RAN2
`would be drafted to express RAN1 views.
`
` (During RAN1#34, the LS to RAN2 (cc to T1) was finalized as R1-031132 and submitted)
`
`R1-030874 CR25.212-180r1(Rel-5): Broadening the conditions that require UEs to perform
`BTFD for the case of HS-DSCH reception
`NTT DoCoMo
`Requested to update bullets 2-11 to consider additional case of HS-DSCH type CCTrCH (restrictions apply only to the
`dedicated type CCTrCH)as well as wording to e.g. “common type CCTrCH used for HS-DSCH” or similar. Category “C”.
`Revision is in R1-030875.
`
`R1-030875 CR25.212-180r2(Rel-5): Broadening the conditions that require UEs to perform
`BTFD for the case of HS-DSCH reception
`NTT DoCoMo
`Revised further into R1-030936 to correct cover sheet and to add isolated impact Some technical terms also needed
`corrections.
`
`R1-030936 CR25.212-180r3(Rel-5): Broadening the conditions that require UEs to perform
`BTFD for the case of HS-DSCH reception
`NTT DoCoMo
`
`Agreed
`
`5.5
`
`Other inputs
`
`R1-030756 Discussion on 25.321CR173r1 UE procedure for TB size signalling
`
`Panasonic
`It was mentioned that it is not feasible to store received data in the described case. RAN2 to decide on UE behaviour in
`this case, e.g. whether UE transmits DTX (transmitting NACK is not seen as appropriate by RAN1). An LS was drafted in
`R1-030876.
`
`[DRAFT] LS on UE procedure for TB size signalling
`R1-030876
`Agreed to send the final version in R1-030904, which was submitted on 28/08/03.
`
`Panasonic
`
`Mitsubishi
`R1-030792 Priority between UPLINK DPCH and HS-DPCCH
`No agreement was reached for TFCI extension method. RAN1 was informed that RAN4 already discussed “Actual TX
`based method” (for 25.133). An LS to RAN4 to confirm that this is also RAN1’s understanding was drafted in R1-
`030879
`
`[DRAFT] LS on UE procedure for TFC selection Panasonic
`R1-030879
`revised to R1-030905 (include attachment).
`
`R1-030905 LS on UE procedure for TFC selection (To:R4, R2 Cc:_)
`Agreed to send the final LS (with minor modification) in R1-030937. Sent on 29/08/2003
`
`Panasonic
`
`Beamforming Enhancements
`
`6.
`
`
`
`NAC1057
`Page 11
`
`

`

`6.1
`
`Text proposals for TR 25.887
`
`No inputs.
`
`6.2
`
`Other inputs
`
`Nokia
`R1-030851 CR25.215-145(Rel-6): Beamforming Enhancement support in Rel'5
`Principle of the proposed changes was agreed. There is a need to check RAN3 reporting for measurements except SIR
`(report for all or for some beams). At first, a revision was planned in R1-030880, but actually RAN1 CRs covering both
`alternatives in CR 25.214-145r1 (option 1) in R1-030921 and CR 25.214-146 (option 2) in R1-030922.
`
`R1-030880 CR25.215-145r1(Rel-6): Beamforming Enhancement support in Rel'5
`Planned but replaced by R1-030921 and R1-030922.
`
`Nokia
`
`R1-030921 CR25.215-145r1(Rel-6): Beamforming Enhancement support in Rel'5 Option1
`
`Nokia
`R1-030922 CR25.215-146(Rel-6): Beamforming Enhancement support in Rel'5 Option2
`
`Nokia
`RAN3 had discussion on considerations taking place in RAN1 but no conclusion was reached. The latest observation of
`RAN3 progress is that they will not get any conclusion within this week. Therefore, as agreed earlier this week, two
`alternatives are prepared in two CRs.
`
`921 is the successor of previous 851 and reports transmitted carrier power, received total wide band power and other
`measurements are made for all of cell portions.
`
`922 is a more flexible.
`
`R1-030938 CR25.215-145r2(Rel-6): Beamforming Enhancement support in Rel'5 Option1
`
`Nokia
`Technically endorsed (with adding “type1” for SIR)
`
`R1-030939 CR25.215-146r1(Rel-6): Beamforming Enhancement support in Rel'5 Option2
`
`Nokia
`Technically endorsed
`
`Alcatel
`R1-030739 Fast Beam Selection
`New proposal for Rel6 WI on beamforming would change the completion time of the WI, e.g. because all RAN WGs are
`involved in the work. Report to RAN that there is a new proposal and ask for guidance whether to study this under the
`beamforming WI or e.g. the radio link performance enhancement SI.
`
`
`
`7.
`
`MBMS
`
`7.1
`
`Text proposals for TR 25.803
`
`R1-030675 Proposed structure for internal TR 25.803
`TR structure agreed, replace LCR/HCR TDD with 1.28/3.84Mcps TDD.
`
`QUALCOMM
`
`R1-030676 Text proposal for TR 25.803
`The simulation results shown were commonly agreed.
`
`QUALCOMM
`
`R1-030653 MBMS simulation results
`Noted as the results In line with 0676
`
`Nokia
`
`R1-030819 Link performance analysis of MBMS
`Noted as in agreement with results in 0676
`
`Samsung
`
`NAC1057
`Page 12
`
`

`

`R1-030781 Link Level Simulation Results for FDD MBMS Siemens
`Agreed to include results for PA3 and PB3. Text proposal in R1-030883
`
`R1-030883 Text Proposal for MBMS TR25.803 Section 4
`Agreed to put into TR
`
`Siemens
`
`R1-030882 Text proposal for TR25.803 describing S-CCPCH in Veh-A results
`
`Motorola
`Agreed text proposal for VA30 (“-“ to be added in the table).
`
`NTT DoCoMo
`R1-030884 Text Proposal for TR 25.803
`A text proposal for VA3 is to be made based on the agreed contents of R1-030884. (with set of curves and information
`about channel estimation) on the reflector in R1-030944.
`
`R1-030944 Text proposal for TR 25.803
`Agreed to include in the TR
`
`NTT DoCoMo
`
`R1-030723 Further Simulation Results for 1.28Mcps TDD MBMS
`Text proposal for 32&64kbps results in 881.
`
`Siemens
`
`R1-030881 Text proposal for TR 25.803: 1.28 Mcps TDD
`Agreed to include in the TR.
`
`Siemens
`
`R1-030839 Text proposal for TR25.803 describing functional characteristics and performance
`of two repetition schemes for S-CCPCH
`Motorola
`Not agreed. Described functionality is not supported by current L1 and L2 specifications.
`
`7.2
`
`Other inputs
`
`R1-030770 Layer 1 feasibility of MBMS
`Noted
`
`TeliaSonera
`
`R1-030853 Outer coding for MBMS
`Noted
`
`QUALCOMM
`
`R1-030854 Complexity aspects of outer coding for MBMS QUALCOMM
`Noted
`
`R1-030812 Outer Code Performance for MBMSMotorola
`Noted
`
`Interleaving gains with outer coding QUALCOMM
`R1-030856
`Noted Some more time needed to evaluate impact on complexity aspects. Some more simulation results needed to
`demonstrate the benefits of outer coding (using same baseline TTI and interleaver length).
`
`R1-030789 Power allocation and user assignment for MBMS Motorola
`Postponed to RAN1#34.
`
`R1-030840 Text proposal for TR25.803 describing “Power allocation and user assignment for
`MBMS” Motorola
`Postponed to RAN1#34.
`
`R1-030820 PCE scheme for MBMS Samsung
`Noted
`
`R1-030822 Enabling/disabling of power control with FACH for MBMS Samsung
`Noted
`
`R1-030821 Text proposal on PCE scheme for MBMS
`Noted
`
`Samsung
`
`NAC1057
`Page 13
`
`

`

`R1-030842 Consideration on UE reception of MBMS simulcast transmission
`DoCoMo
`
`NTT
`
`Noted
`
`
`
`Updated TR with agreed text proposals included was to be in Tdoc R1-030950. But, R1-031105