TSGR1-02-0791
`
`-
`
`Secretary
`
`Revised minutes of TSG RAN WG1 #25 meeting
`
`TSG-RAN Working Group 1 meeting No. 25
`April 9-12, Paris, France
`
`
`Agenda Item:
`
`Source:
`
`Title:
`
`Document for: Approval
`
`_________________________________________________________________________
`
`Revised Minutes for 3GPP TSG-RAN WG1 25th Meeting
`
`/*** Revised Point ***/
`
`- Presenter's name of R1-02-0584 (No.34-36) was corrected.
`
`
`Meeting start: April 9th, 2002, in Paris, France
`
`1. Opening of the meeting
`
`The chairman, Mr. Antti Toskala (Nokia), opened the meeting.
` Ms. Evelyne Le Strat (Nortel) welcomed the delegates to the meeting on behalf of hosting company (Nortel).
`
`
`2. Approval of agenda
` R1-02-0521 Draft Agenda for TSG RAN WG1 meeting No.25
` Chairman made a brief introduction of the agenda on the screen.
`
`The detailed agenda on HSDPA topic was to be organised after checking the documents prepared for it.
` Agenda was approved with no specific comments.
`
`
`3. Identification of the incoming liaison statements and actions in the answering
`
`
`Notes
`
`Title
` Draft response to LS on "Procedure for specifying
` UMTS QoS Parameters per Application"
` LIAISON FOR INFORMATION:
` Reduction of the number of AMR-WB modes for speech
` telephony service. ( Reply to GP-(02)0505 = S4-(02)0035 )
` LS on WCDMA reference bearers for
` streaming
` LS to RAN1 and RAN2 in response to
` T1-020025, LS on 34.108 Updates
` Reply to LS on downlink power control
` (DPC_Mode=1)
` LS on Introduction of radio bearer configuration “Conversational /
` speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS
` RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB +
` UL:3.4 DL:3.4 kbps SRBs for DCCH” into TS 34.108
` LS on TFRI formula
`(*1) Mr. Jean-François Labal (NEC) presented this LS.
`
` This was the answer from SA WG4 to the LS sent from CN WG3 which we had also received and treated in
` RAN WG1#24 in R1-02-0227 (N3-020119). This LS was informing the current status of mapping rules for streaming
`
`
` and conversational applications.
`
` This LS was noted. The rules mentioned in this LS are to be taken into account for the inputs for TS 34.108.
`
`Source To/Cc Tdoc No. Contact point
`SA
`WG4 CC R1-02-0522
`SA
`WG4 CC R1-02-0523
`Siemens
`(S4-020225)
`SA
`WG4 TO R1-02-0524
`(S4-020227) Ericsson
`T
`WG1 TO R1-02-0525
`(T1-020185) Anritsu
`RAN
`WG3 CC R1-02-0587
`Lucent
`(R3-020851)
`RAN
`WG2 TO R1-02-0652
`(R2-020782) Vodafone Noted (*5)
`RAN
`WG2 TO R1-02-0668
`(R2-020786) Ericsson
` Noted (*6)
`
`NEC
`
` Noted (*1)
`
` Noted (*2)
`
` Noted (*3)
`
` Noted
`
` Noted (*4)
`
`(S4-020198)
`
` No.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`
`
`
`
`
`
`- 1 -
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 1 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`(*2) Mr. Marcus Purat (Siemens) presented this LS.
`
` This LS was noted with the same attention as the previous LS in R1-02-0522.
`(*3) Mr. Dirk Gerstenberger (Ericsson) presented this LS.
`
` This LS was noted with the same attention as the previous 2 LSs.
`(*4) Mr. Man Hung Ng(Lucent) presented this LS.
`
` This was the RAN WG3 answer for the LS from RAN WG4which we had also received and treated in RAN WG1#24 in
` R1-02-0228 (R4-020474) in which RAN WG4 had asked RAN WG3 to inform RAN WG4 in which Release of the
`
`
` RAN WG3 technical specifications the signalling protocols on Downlink Power Control Mode DPC_MODE = 1 would
`
` be specified. RAN WG3 answered that the signalling for DPC_Mode=1 is supported in Release 4 of the RAN WG3
`
` specifications as an optional feature.
`(*5) Mr. Yannick Le Pezennec (Vodafone group) presented this LS.
` This LS was received on Day1 afternoon. It was reviewed in connection with R1-02-0533 and R1-02-0534.
`
`
` (See No.40-42)
`
` R1-02-0533 was proposing to include a new radio bearer configuration in TS 34.108 which had been omitted from the
`
` previous discussions of a new set of reference radio bearers in the joint RAN WG1-WG2 Ad Hoc in Sophia Antipolis
`
` in February. R1-02-0354 contained CRs of this inclusion for R99 and Rel-4.
`
` Now in this current LS RAN WG2 was informing that it had also reviewed the same CRs and it approved them from
`
` RAN WG2 point of view with a minor editorial correction. The modified CRs were attached to this LS.
`
` There was no specific comment made for this LS. Having this reviewed, it was concluded that we should send a LS with
`
` those attached CRs to T WG1 to inform them to include this change in TS 34.108.
` R1-02-0660 was allocated for the LS. It was reviewed and approved in R1-02-0669 on Day2 (See No. 120) and sent to
`
`
` T1-SIG/T1/RAN WG2 on Day2 evening so that T1-SIG could receive it during its meeting held in parallel in Helsinki.
`(*7) Mr. Stefan Parkvall (Ericsson) presented this LS. This LS was received on Day2 evening from RAN WG2 and reviewed
`
` on Day4 morning.
`
` During the RAN WG2#28, it agreed to include in the 3GPP specifications, formulas which provide a mapping between
`
` the TFRI and the TB size. The intention was instead of providing every UE with a UE-specific TFRI mapping by RRC
`
` signalling, the UE (and Node-B) can use the standardised formulas. Although RAN WG2 had agreed on this approach,
`
` no agreement was reached yet on the exact formulas to be included in the specifications. Two examples of such
`
` formulas were indicated in the attached papers (R2-020765[Ericsson], and R2-020767[Samsung]). In relation to these
`
` formulas, RAN WG2 listed several questions for RAN WG1 guidance.
`
` There took place a quite long discussion and finally the conclusion was made so that formula should be based on the
` Ericsson's proposal. The answer LS was drafted in R1-02-0382 and approved in R1-02-0384. (See No.122)
`
`
` The relevant discussion took place following the reviewal of this LS. (See No. 97, 98)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(R1-02-0640)
`4. Report from TSG RAN #15
` Chairman made a briefly introduction of the report from TSG RAN #15 in Jeju, Korea held during 3-6 May
`
`
`- TSG RAN WG1 CRs approved, the measurement validity CRs were slightly revised for RAN WG2 alignment.
`
`
`- Release 5 CRs were all approved as they were.
`
`
`- The following work items are still active for Release 5 (WG1 related)
`
`
`
`• SSDT in UTRAN (On hold waiting for WG4 work, WG1 has to only update the CRs)
`
`
`
`• HSDPA performance aspects (HSDPA was noted still needing some correction. RAN WG1 WI was closed)
`- The R’99 clean-up meeting output resulted for the no-coding option to be removed, others were retained.
`
`
`
`
`- The measurement applicability and SSDT (R’99/Rel-4) CRs were slightly modified (in TSG RAN).
`
`
`- All WG1 specs were raised to 5.0.0 versions
`
` There was one question raised regarding the treatment of TRs (especially HSDPA TR) from now on.
`
` Chairman answered that we should now really focus on the actual CRs. If there are some essential things missing in the
`
` TR, of course then TR should be revised. He said that maybe one single CR can be made for the TR for the bigger issues,
`
` but we should not focus on minor things.
`
` Report was approved with no other comments.
`
`- 2 -
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 2 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`5. Rel’99/4 CR identification /** The actual approval for the RAN submission will take place in RAN WG1#26. **/
`
`
`Cat Source Conclusion Notes
`- Ericsson
`Panasonic
`
`No. R CR rev TS
`
`Tdoc
`
`Title
`
`8
`
`-
`
`-
`
`-
`
`-
`
`R1-02-0381 Downlink bit mapping
`
`9 99 015
`
`- 25.201 R1-02-0595 Downlink bit mapping
`
`10 4 016
`
`- 25.201 R1-02-0595 Downlink bit mapping
`
`11 5 017
`
`- 25.201 R1-02-0595 Downlink bit mapping
`
`12 99 151
`
`- 25.211 R1-02-0596 Downlink bit mapping
`
`13 4 152
`
`- 25.211 R1-02-0596 Downlink bit mapping
`
`14 5 153
`
`- 25.211 R1-02-0596 Downlink bit mapping
`
`15 99 134
`
`- 25.212 R1-02-0597 Downlink bit mapping
`
`16 4 135
`
`- 25.212 R1-02-0597 Downlink bit mapping
`
`17 5 136
`
`- 25.212 R1-02-0597 Downlink bit mapping
`
`18 99 051
`
`- 25.213 R1-02-0598 Downlink bit mapping
`
`Ericsson
`
`Ericsson
`
`Ericsson
`
`F
`
`A
`
`A
`
`F
`
`A
`
`A
`
`F
`
`A
`
`A
`
`F
`
`To be checked
`until R1#26.
`
`Comments
` are to be
`provided
`on R1
`reflector
`prior to R1#26
`
`(*1)
`
`Agreed in
`principle.
`Wording
`needs to be
`adjusted
`until R1#26
`
`(*2)
`
`LS to be sent
`to RAN
`WG2
`
`(*3)
`
`19 4 052
`
`- 25.213 R1-02-0598 Downlink bit mapping
`
`A
`
`Ericsson
`
`20 5 053
`
`21 99 143
`
`22 4 144
`
`23 5 149
`
`24 99 241
`
`- 25.213 R1-02-0598 Downlink bit mapping
`- 25.211 R1-02-0312 SCCPCH structure with STTD
` encoding
`- 25.211 R1-02-0312 SCCPCH structure with STTD
` encoding
`- 25.211 R1-02-0312 SCCPCH structure with STTD
` encoding
`- 25.214 R1-02-0311 Physical channel reconfiguration F
`
`A
`
`F
`
`A
`
`A
`
`Nokia
`
`25 4 242
`
`- 25.214 R1-02-0311 Physical channel reconfiguration A
`
`Nokia
`
`26 5 254
`
`27 99 077
`
`28 4 078
`
`29 4 079
`
`33 5 077
`
`- 25.214 R1-02-0311 Physical channel reconfiguration A
`- 25.221 R1-02-0398 Clarification of shared channel
` functionality for TDD
`- 25.221 R1-02-0398 Clarification of shared channel
` functionality for TDD
`- 25.221 R1-02-0398 Clarification of shared channel
` functionality for TDD
`- 25.221 R1-02-0398 Clarification of shared channel
`30 5 080
` functionality for TDD
`31 99 070 1 25.222 R1-02-0445 Second stage interleaving and
` physical channel mapping
`32 4 071 1 25.222 R1-02-0445 Second stage interleaving and
` physical channel mapping
`- 25.222 R1-02-0445 Second stage interleaving and
` physical channel mapping
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`A
`
`Siemens Agreed in
`principle
`
`(*4)
`
`IPWireless
` Siemens
`
`Agreed in
`principle
`
`(*5)
`
`- 3 -
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 3 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`No. R CR rev TS
`
`Tdoc
`
`Title
`
`Cat Source Conclusion Notes
`
`F
`
`A
`
`A
`
`F
`
`A
`
`A
`
`-
`
`F
`
`Panasonic Agreed in
`principle
`
`(*6)
`
`Siemens
`
`To be
`checked
`until
`R1#26
`
`(*7)
`
`Vodafone
`Group
`
`Approved
`
`(*8)
`
`A
`F Ericsson Approved
`LS to be sent
`
`Siemens Agreed in
`principle
`
`(*9)
`
`(*10)
`
`Siemens Agreed in
`principle
`
`(*11)
`
`NTT
`DoCoMo Approved
`
`(*12)
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`34 99 074
`
`- 25.222 R1-02-0584 Zero padding for TFCI
`
`35 4 075
`
`- 25.222 R1-02-0584 Zero padding for TFCI
`
`36 5 076
`
`37 99 046
`
`38 4 047
`
`39 5 050
`
`40
`
`
`
`-
`
`41 99 XXX
`
`42 4 XXX
`
`43 99 XXX
`
`44 4 072
`
`45 5 073
`
`46 4 087
`
`- 34.108 R1-02-0534
`
`-
`
`-
`
`- 25.222 R1-02-0584 Zero padding for TFCI
`- 25.225 R1-02-0375 Clarification of UE
` measurements applicability
`- 25.225 R1-02-0375 Clarification of UE
` measurements applicability
`- 25.225 R1-02-0375 Clarification of UE
` measurements applicability
`R1-02-0533 Introduction of radio bearer configuration
` "Conversational / speech / UL:(12.2 7.95
` 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps /
` CS RAB + Conversational / unknown /
` UL:64 DL:64 kbps / CS RAB + UL:3.4
` DL:3.4 kbps SRBs for DCCH" into
`- 34.108 R1-02-0534
` 34.108
`- 34.108 R1-02-0589 Correction of Puncturing Limit
` for several RAB configurations
`- 25.222 R1-02-0396 Correction to addition of padding
` zeros to PICH in 1.28 Mcps TDD
`- 25.222 R1-02-0396 Correction to addition of padding
` zeros to PICH in 1.28 Mcps TDD
`- 25.224 R1-02-0397 Clarification on power control and
` TxDiversity procedure for 1.28 Mcps TDD
`
`47 5 088
`
`- 25.224 R1-02-0397 Clarification on power control and TxDiversity
` procedure for 1.28 Mcps TDD
`
`48 99 XXX
`
`- 34.108 R1-02-0679 Change of the range of rate matching attribute
` for DL:3.4 kbps SRBs for DCCH
`
`49 4 XXX
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`- 4 -
`
`- 34/108 R1-02-0679 Change of the range of rate matching attribute
` for DL:3.4 kbps SRBs for DCCH
`(*1) Mr. Dirk Gerstenberger (Ericsson) presented these papers.
` R1-02-0381 contained a summary of the CRs proposed in R1-02-0595, R1-02-0596, R1-02-0597 and R1-02-0598
`
`
` which proposed to clarify the downlink bit mapping. The current specification of bit mapping in downlink is not
`
` consistent between the different Layer 1 specifications. In particular, the mapping of logical "0" and logical "1" is not
`
` described. A number of different signal formats is used, e.g. the CPICH is defined as a sequence of complex symbols
`
` (TS 25.211) that is serial-to-parallel converted and then mapped to I/Q before spreading (TS 25.213).
`
` There were some concerns raised saying that we needed to check these CRs in details before we can agree on them.
`
` Having those comments, chairman concluded that we postpone the decision until RAN WG1#26 meeting and he invited
`
` people to have careful check on these CRs meantime. He also suggested that comments ,if any, should be made
`
` available on the RAN WG1 e-mail reflector prior to the next meeting.
`(*2) Mr. Markku Tarkiainen (Nokia) presented this set of CRs.
`
` These CRs proposed that TFCI is to be included in STTD encoding with SCCPCH.
`
` There was one comment from Panasonic suggesting rewording. There were no other comments. Chairman concluded
`
` these CRs were OK in principle. He suggested having offline discussion between Nokia and Panasonic for rewording by
`
` the next meeting.
`(*3) Mr. Markku Tarkiainen (Nokia) presented this set of CRs.
`
` TS 25.214 specifies that radio link synchronisation procedure A (full synchronisation) shall be performed when "the UE
`
` has its entire previous radio links removed and replaced by other radio links i.e. intra-frequency hard-handover". It has
`
` not been the intention to trigger the full synchronisation procedure each time when details of a physical channel or
`
` transport channel are reconfigured, e.g. slot format or spreading factor. This CR proposed to clarify that
`
` synchronization procedure is not necessarily needed when reconfiguration occurs.
`
` There were concerns raised and it turned out that the meaning of hard handover is not necessarily clear to everybody.
`
` Based on the comments chairman suggested sending a LS to RAN WG2 asking how RAN WG2 understand the
`
` different hard handover (the definition of hard handover) and whether we need to modify our specifications or not.
` The LS was drafted in R1-02-0645 by Mr. Markku Tarkiainen. It was reviewed on Day4 and approved in R1-02-0683.
`
`
` (See No.123)
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 4 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`Deleted: Hidetoshi Suzuki
`
`(*4) Mr. Marcus Purat (Siemens) presented this set of CRs.
`
`
` There were no comments raised. All these CRs were agreed in principle. The actual approval will take place in
`
`
` RAN W#26.
`
`(*5) Mr. Martin Beale (IPWireless) presented this set of CRs.
`
` This was the revision R1-02-0339 which had already been provided in RAN WG1#24 meeting. Since some concerns
`
`
`
` were raised in RAN WG1#24, this paper had been postponed to this meeting. In this revision, the shadow CR for Rel-5
`
`
` was newly added. This CR proposed to clarify 2 inconsistencies with respect to TS 25.222.
`
`
` No comments were raised. This set of CRs was agreed in principle.
`
`(*6) Mr. Akihiko Nishio (Panasonic) presented this set of CRs.
`
`
` This CR proposed to insert following sentence. That was because the coding method for TFCI in case where TFCI bit
`
`
` number is less than 10bits or 5bits had not been clearly specified so far.
`
`
`
`
`"If the TFCI consists of less than 10[5] bits, it is padded with zeros to 10[5] bits, by setting the most significant bits to zero"
`
` This set of CRs was agreed in principle with no comments.
`
`(*7) Mr. Marcus Purat (Siemens) presented this set of CRs.
`
`
` This CR proposed to clarify for each UE measurement in which RRC state it can be requested from the mobile and on
`
`
` which type of cell (intra/inter frequency). This level of detail was agreed to be included in the RAN WG1 specifications
`
` at the joint RAN WG1/WG2 meeting February 5th-6th in Sophia-Antipolis. The same clarification CRs had already been
`
`
`
` proposed for FDD mode and approved in RAN WG1#24. This set of CRs corresponded to those CRs and was for TDD
`
`
` mode.
`
`
` It was concluded that these CRs need to be checked in detail until RAN WG1#26.
`
`(*8) Mr. Yannick Le Pezennec (Vodafone group) presented these papers. R1-02-0553 was discussion paper and R1-02-0534
`
`
` contained actual CRs for TS 34.108.
`
`
` These papers were proposing to include a new radio bearer configuration in TS 34.108 which had been omitted from the
`
`
` previous discussions of a new set of reference radio bearers in the joint RAN WG1-WG2 Ad Hoc in Sophia Antipolis
`
` in February. RAN WG2 was also reviewing these papers in parallel in its 28th meeting in Japan and we were expecting
`
`
`
` to receive LS from them. Chairman proposed to postpone the decision until we receive that LS from RAN WG2.
`
` Eventually we received that LS on Day1 afternoon from RAN WG2 in R1-02-0652 and we reviewed it on
`
`
`
` Day2. (See No. 6) Since RAN WG2 had agreed on this proposal from RAN WG2 point of view, it only depended on
`
`
` RAN WG1's decision. There was no specific concerns raised and thus these CRs were agreed. It was also agreed to send
`
` these CRs to TSG T WG1 in the LS. The draft LS was made in R1-02-0660 and approved in R1-02-0669. (See No. 120)
`
`
`(*9) Mr. Gerke Spaling (Ericsson) presented this CR.
`
`
` For a number of RAB configurations which were newly introduced in TS 34.108 in the last TSG-T meeting, the value of
`
`
` the Puncturing Limit prevents the use of the full range of the RM attributes whereas so far the Puncturing Limit of the
`
`
` RAB combinations in TS 34.108 had been specified in such a way that the full flexibility in the setting of RM attributes
`
`
` was allowed. This CR proposed to correct the Punctual Limits for these RAB combinations to allow for maximum
`
`
` flexibility in the setting of the RM attributes.
`
`
` There was one comment from Nortel saying that we needed to have time to check in detail.
`
`
` Eventually this CR was approved. It was also agreed to send a LS to T to inform this change request. The LS was
`
` drafted by Mr. Gerke Spaling in R1-02-0651 and approved in R1-02-0670 on Day2. The LS was sent by the secretary
`
`
`
` on Day2 evening so that T1-SIG could treat it in their meeting held in parallel in Helsinki. (See No. 121)
`
` (*10) Mr. Marcus Purat (Siemens) presented this pair of CRs (Rel-4/Rel-5).
`
`
` When the number of bits available to a PICH in a radio frame is greater than the number of actual PICH bits used for
`
`
` paging indicators, then padding zeros are added. However the function for the addition of the padding zeros is
`
`
` incorrectly specified for 1.28 Mcps TDD. This CR proposed to correct this error. The corresponding CR for 3.84Mcps
` TDD had already been approved in RAN WG1#24 in R1-02-0338 (IPWireless).
`
`
`
`
` No comments were raised and this pair of CRs was agreed in principle.
` (*11) Mr. Marcus Purat (Siemens) presented this pair of CRs(Rel-4/Rel-5).
`
`
` This CR proposed some clarification on power control and TxDiversity procedure for 1.28 Mcps TDD in order to align
`
`
` the other RAN WG1 specifications and to avoid redundant information in different WGs.
`
`
` No comments were raised and this pair of CRs was agreed in principle.
` (*12) Mr. Masafumi Usuda (NTT DoCoMo) presented this pair of CRs.
`
`
` Ericsson supported this change. (Nortel raised concern.)
`
`
` After some clarification discussion this pair of CRs was agreed to be sent to T1 with no modification. An LS was
` drafted by NTT DoCoMo in R1-02-0672 and approved in R1-02-0686. (See No. 128)
`
`
`
`- 5 -
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 5 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`6. High Speed Downlink Packet Access (Ad Hoc 24)
`
`
`No. Category
`
`50
`
`51
`
`52
`
`53
`
`54
`
`55
`
`56
`
`57
`
`58
`
`59
`
`60
`
`61
`
`62
`
`63
`
`64
`
`65
`
`66
`
`67
`
`68
`
`69
`
`70
`
`71
`
`72
`
`73
`
`74
`
`Tx-div
`related
`issues
`
`CRC
`
`Title
`T-doc
`R1-02-0622 HSDPA and rel99 features, both from
` WG1 and WG4 point of view
`R1-02-0624 Performance and system scenarios for
` 16QAM in HSDPA and tx diversity
`R1-02-0611 System performance with/without STTD
` for different schedulers
`R1-02-0612 HSDPA performance w/wo STTD when the HS-
` SCCH and Associated DCH are explicitly modelled
`R1-02-0290 System-level performance of transmit
` diversity (STTD and TxAA) for HSDPA
`R1-02-0599 System-level performance of STTD for
` HSDPA with a fixed outage criterion
`R1-02-0646 Transmit diversity for HSDPA
`
`R1-02-0607 Transmit diversity for HSDPA channels
`R1-02-0600 Link level performance of mode 1 and 2
` TxAA for HSDPA
` HSDPA performance w/wo closed-loop transmit
`R1-02-0614
` diversity when the HS-SCCH and Associated DCH
` are explicitly modelled
`R1-02-0555 Pre-coding of UE ID before modulo 2
` addition with CRC
`R1-02-0493 Improved UE specific CRC generation
`
`R1-02-0610 Performance of the HS-SCCH
`R1-02-0535 HS-SCCH: Performance results and
` improved structure
`R1-02-0637 HS-SCCH: Performance results and
` improved structure
`R1-02-0649 Performance of the HS-SCCH
`
`R1-02-0553 Way forward on HS-SCCH coding
`
`HS-SCCH
`Coding
`
`R1-02-0604 Coding and rate matching for HS-SCCH
`R1-02-0542 On user-specific scrambling code for the
` part 1 of HS-SCCH
`R1-02-0615 Optimal DL signalling for HARQ in
` HSDPA
`R1-02-0400 UE specific bit scrambling for TDD HS-
` SCCH
`R1-02-0559 Considerations on HS-SCCH power
` control
`R1-02-0633 Options for power control of HS-SCCH
` for TDD Release 5
`mapping R1-02-0601 Proposal on I/Q mapping of the HS- IQ DPCCH for multi-code case
`
`R1-02-0561 Considerations on the amplitude gain
`
` factor for HS-DPCCH
`
`
`
`- 6 -
`
`Source
`
`Conclusion Notes
`
`Nokia
`
`Noted
`LS to be sent
`to R4
`
`(*1)
`
`Motorola
`
`Noted
`
`(*2)
`
`Noted
`
`(*3)
`
`Texas
`Instruments
`
`Lucent
`
`Siemens
`Texas
`Instruments
`Motorola
`
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Lucent
`
`Siemens
`
`To be checked
`with R2, R3
`in May
`meeting
`
`Motorola
`
`Noted
`
`Texas
`Instruments
`
`Noted
`
`Lucent
`
`Lucent
`
`Siemens
`
`LGE
`
`NEC
`
`Noted
`
`Noted
`CR to be
`produced
`Noted
`
`Noted
`
`(*4)
`
`(*5)
`
`(*6)
`
`(*7)
`
`(*8)
`
`(*9)
`
`(*10)
`
`(*11)
`
`Siemens
`
`Postponed
`
`(*12)
`
`LGE
`
` LS to R3
`
`(*13)
`
`IPWireless
`
`Postponed
`
`(*14)
`
`Mitsubishi
`
`LGE
`
`Postponed. CR
`to be produced.
`detailed
`proposal needed
`
`(*15)
`
`(*16)
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 6 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`No. Category
`
`T-doc
`
`Title
`
`75
`
`76
`
`CQI
`
`R1-02-0458 Revised HSDPA CQI proposal
`
`R1-02-0459 HSDPA CQI proposal
`
`R1-02-0577 HS-DPCCH and compressed mode
`
`77 HSDPA
`&
`78
`Compre-
`ssed
`mode
`
`79
`
`R1-02-0564 HSDPA operation in compressed mode
`R1-02-0279 Interaction of compressed mode with
` HSDPA
`FCS R1-02-0528 Node-B controlled fast cell selection in
` HSDPA
`R1-02-0499 Proposal on UE category of HSDPA
` (CR 25.306-XXX)
`R1-02-0644 HSDPA UE Capabilities for 3.84 Mcps
` TDD
`R1-02-0657 UE Capability for 3.84Mcps TDD
` HSDPA
`R1-02-0579 Comparison of HSDPA schedulers
`R1-02-0580 ACK/NACK repetition: Effect of
` downlink transmission gap
`R1-02-0616 Power control for uplink HS-DPCCH in
` soft handover
`R1-02-0537 Discussion on ACK/NACK signalling
`R1-02-0636 HS-DPCCH power control using the
` special pilot bits in HS-DPCCH
`R1-02-0554 HS-DPCCH Power requirements with
` HS-Pilot and Repetition
`R1-02-0538 Power and repetition control for uplink
` HS-DPCCH
`R1-02-0592 Channel estimation for HS-DPCCH in
` Soft Handover
`R1-02-0671 Comments about R1-02-0538 and
` R1-02-0592
`R1-02-0582 Effect of channel estimation errors on
`93
` ACK/NACK signalling
`94 HARQ R1-02-0619 Optimisation of the redundancy versions
` for HARQ functionality
`
`coding R1-02-0653 Consideration on Basis Sequences for CQI CQI Coding
`
`TDD R1-02-0602 Improved HS-SICH coding structure for
` TDD HSDPA
`R1-02-0594 Transport block sizes for HS-DSCH
`R1-02-0569 Transport Block Size (TBS) signalling
` for HS-DSCH
`R1-02-0648 Signalling for closed loop transmit
` diversity in HSDPA
`R1-02-0568 System performance of 2x2 CLTD for
` HSDPA
`
`80
`
`81
`
`82
`
`83
`
`84
`
`85
`
`86
`
`87
`
`88
`
`89
`
`90
`
`91
`
`92
`
`95
`
`96
`
`97
`
`98
`
`99
`
`100
`
`UE
`Capability
`
`uplink
` HS-
`DPCCH
`
`TrBlock
`size
`
`Tx-
`diversity
`
`Source
`Motorola
`Nokia
`Motorola
`
`Philips
`
`Samsung
`
`Siemens
`
`Lucent
`
`Panasonic
`
`Nokia
`
`IPWireless
`
`Philips
`
`Philips
`
`Huawei
`
`NEC
`Samsung
`Motorola
`Lucent
`
`Nokia
`
`Ericsson
`Samsung
`Lucent
`Philips
`Texas
`Instruments
`LGE
`Philips
`Samsung
`
`Ericsson
`
`Samsung
`
`Lucent
`
`Lucent
`
`Conclusion Notes
`
`To be
`revised
`
`CR agreed
`in principle
`Noted
`
`Agreed in
`principleCR
`
`Noted
`To be revised
`LS to be sent
`
` Offline
`discussion
`
`Noted as
`background
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Noted
`
`Agreed
`
`Noted
`
`LS to be sent
`for R2
` based on
` R1-02-0594
`Noted
`
`Noted
`
`(*17)
`
`(*18)
`
`(*19)
`
`(*20)
`
`(*21)
`
`(*22)
`
`(*23)
`
`(*24)
`
`(*25)
`
`(*26)
`
`(*27)
`
`(*28)
`
`(*29)
`
`(*30)
`
`- 7 -
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 7 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`No. Category
`
`T-doc
`
`Title
`
`101 CQI R1-02-0675 Revised CQI proposal
`
`Source
`Motorola
`Ericsson
`
`Conclusion Notes
`
`Agreed
`
`(*31)
`
`(*1) Ms. Anu Virtanen (Nokia) presented these 2 papers.
` R1-02-0622 raised some potential issues which will arise when both HSDPA and Tx diversity co-exist in the same
`
`
` cell especially when advanced receiver is being assumed. A similar paper had already been brought up and discussed in
`
` RAN WG4 in a week before in RAN WG4#22 but there had not been any consensus obtained. This paper proposed that
`
` RAN WG1 should further discuss on this issue and send a LS to RAN WG4, clarifying RAN WG1 opinion on these
`
` issues. It stated that following issue should be clarified by RAN WG1.
`
`
`- The usage of R'99 features (Tx div, beamforming) in HS-DSCH
`
`
`- The usage of R'99 features (Tx div, beamforming) in the same cell with HS-DSCH
`
`
`- The usage of R'99 features (Tx div, beamforming) for the associated DPCH and HS-SCCH , when used
`
`
` together with HS-DSCH
` R1-02-0624 presented some simulation results on the same issue of the use of R'99 features (Tx div, beamforming) in
`
`
` HSDPA and proposed some alternative approaches how to proceed with RAN WG1 and RAN WG4 work with
`
` Tx diversity and HSDPA performance requirements.
`
` There took place a long discussion and a number of concerns were raised. Main concerns seemed that even though
`
` Tx-diversity is in RAN WG1 responsibility, the issue of test cases and performance requirements is out of RAN WG1
`
` scope. It should be done in RAN WG4. There was also a comment that the objective of these papers was not clear.
`
` There was also a discussion on the choice of Tx-diversity schemes and combination of those schemes with HS-channels.
`
` Chairman said that R'99 open loop Tx diversity may be used on HS-DSCH as well and it may be also used on DPCH
`
` and HS-DSCH. He said that we need to discuss what kind of additional combinations are possible or not.
`
` In the end chairman suggested to have joint session with RAN WG4 on this issue in the next co-located meeting in
`
` Korea. He said that we need to have a whole picture together with RAN WG4. He also suggested sending a LS to
`
` RAN WG4 prior to that meeting. RAN WG4 should be informed of RAN WG1 view and some guidance because the
`
` simulation would take long time.
`
` In conclusion, there no agreement was obtained on what was proposed in these papers but it was agreed to send a LS
`
` to RAN WG4 informing current RAN WG1 situation. (there were a couple strong objections against sending LS itself
`
` saying that RAN WG4 had decided not to send a LS to RAN WG1 although it had been requested by Nokia in
`
` RAN WG4.)
`(*2) Mr. Robert Love (Motorola) presented these 2 papers. These papers were related to the previous discussion.
` In R1-02-0611, HSDPA system performance with and without open loop Tx diversity was investigated for different
`
`
` schedulers and multi-path channel models. A rake receiver was assumed. It was shown that open loop Tx diversity
`
` improves system performance for higher speeds with little multi-path or when the poor performing round robin
`
` scheduler is used. However, at slow speeds and/or when there is significant multi-path there is some throughput
`
` degradation caused by open loop Tx diversity.
` R1-02-0612 investigated system impact of open loop Tx diversity when the HSDPA control channels are explicitly
`
`
` modeled (Associated DCH, HS-SCCH). A single power scale factor was assumed for part 1 and part 2 of the HS-SCCH.
`
` It was shown that when the proposed control channel structure is explicitly modelled, STTD still causes system
`
` degradation at slow speeds but mainly improves system performance at higher speeds for the Ped-A channel model.
`
` With some questions for clarifications on the simulation assumptions these papers were noted.
`(*3) Mr. Tim Schmidl (Texas Instruments) presented these 2 papers.
` R1-02-0290 presented some system level simulation results, which demonstrate the advantage of Tx diversity over the
`
`
` no-Tx-diversity scheme in both single-path and multi-path channels. The system level performance of TxAA for
`
` HSDPA was evaluated for the first time and it was found that Mode 1 TxAA performs the best for low to moderate
`
` UE speeds (approximately below 50-kmph). For higher UE speeds, STTD starts to take over. Based on these results it
` was recommended that Tx diversity (STTD and TxAA) be supported for HSDPA as in R'99 without any conceptual
`
`
` changes.
`
` There were some questions on the simulation assumptions. Chase combining was assumed in the simulation. The gain
`
` with IR is FFS. Chairman commented that we should not go into too much in detail at this point. The key issue is to
`
` know what the impact would be if we took Tx-diversity away or to consider the impact of co-operation of HSDPA and
`
` existing features. This paper was noted.
` R1-02-0599 demonstrated that STTD provides significant average service throughput gain over single antenna systems
`
`
` when a fixed outage criterion is used for comparison. This gain is seen with both round robin and max C/I schedulers.
`
` Based on the simulation results it was recommend that STTD be applied for HSDPA whenever applicable. It said that
`
` the application of STTD in HSDPA should be considered jointly with other existing Tx diversity solutions such as
`
` TxAA. Motorola mentioned that they had similar results with flat fading channel.
`
` This paper was noted.
`(*4) Mr. Farooq Khan (Lucent) presented this paper. In this paper a comparison of the system-level performance of different
`
` Tx diversity schemes for HSDPA, as also the performance of a system with no transmit diversity, were presented. It was
`
` shown that TxAA is likely to be less robust to channel estimation errors and feedback errors than STD or STTD because
`
` it attempts to coherently combine the received signals from the two antennas. It was summarised that if the weight
`
` feedback error rate is low, or with other techniques – such as, antenna verification or explicit signalling of the weight
`
` information on the HS-SCCH – gains for TxAA will not be impacted. Otherwise, the performance of TxAA can be
`
` impacted severely.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`- 8 -
`
`IPR2021-00908 Honeywell Exh. 1008 - Page 8 of 23
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` A discussion took place on the choice of Tx-diversity schemes for HSDPA. Chairman said R99 open loop may be
`
` used on HS-SCCH, DPCH and HS-SCCH as well. He said we needed to consider what kind of combinations are
`
` possible. No clear conclusion was made on this discussion. The issue of choice and combination of Tx diversity
`
` schemes with HS channels will continue further in the next meeting.
`
`(*5) Mr. Ralf Wiedmann (Siemens) presented this paper.
`
` This paper proposed to include STTD as Tx diversity technique for HSDPA. Following ta