TSGR1-02-0628
`
`-
`
`Secretary
`
`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 24th Meeting
`
`Revised minutes of TSG RAN WG1 #24 meeting
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` (19:05 - 09:06)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` (09:06 - 09:25)
`
`
`/***
` Revised Points:
`
`1) p.26 : note for R1-02-0502 (*12)
`
`2) p.31 : note for R1-02-0439 (*3)
`
`3) p.7 : note for R1-02-0201 (*8)
` The participants list was slightly updated.
`***/
`
`Meeting start: February 18th, 2002, in Orlando, Florida, U.S.A.
`
`Day 1, started at 09.05
`
`1. Opening of the meeting
`
`
`
`
`
`
`
`
`The chairman, Mr. Antti Toskala (Nokia), opened the meeting.
`
` Mr. Jean-Aicard Fabien (Motorola) welcomed the delegates to the meeting on behalf of hosting company. (Motorola)
`
`
`
`
`
`
`
`
`
`
`
`
`2. Approval of agenda
` R1-02-0200 Draft Agenda for TSG RAN WG1 meeting No.24
` Chairman made a brief introduction of the agenda on the screen.
`
`
`- Social event was scheduled on Day3 and meeting will be closed by 5PM.
`
`
`- Some comments were made on HSDPA agenda item.
`
`
`
`• The issue on HI should be added to the agenda item.(prior to the joint session)
`  accepted and it was added into agenda item 6.x.
`
`
`
`• The issue on HSDPA Open Issues for RAN WG3 (R1-02-0438) should also be discussed prior to the joint session.
`
`
`
`  Chairman answered that it would be discussed in the beginning of HSDPA discussion.
`
`
`
`
`
`
`• To what extent can we have open issues remaining in the CRs we are going to submit to RAN #15 ?
`  Chairman answered.
`
`
`
`
`
`
`
`
`Somewhat similar to the R99 case. Having too many FFS in the spec would not be nice though the details e.g.
`
`
`
`
`
`tables on beamforming or Tx-diversity applicability could be covered in the later stage. We should like to put
`
`
`
`
`
`something like "minor issues need to be still checked on what needs to be reflected in the spec" in the
`
`
`
`
` meeting minutes rather than putting "FFS" or "Editor's Note" in the specification. We can have square
`
`
`
`
`
`brackets for the values.
`
`
`
`• General downlink signalling issues should be added to the agenda.
`  They will be discussed under 6.11 other issues on HSDPA.
`
`
`
`
`
`
`• When will the open issues on power control be discussed ?
`  We will rearrange the agenda items after checking what kind of papers are to be presented. (Chairman)
`
`
`
`
`
`Eventually agenda was approved with one amendment on HI issue.
`
`
`3. Report from joint TSG RAN WG1/WG2 meeting
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(09:26 - 09:37)
`
`- 1 -
`
`IPR2021-00908 Honeywell Exh. 1007 - Page 1 of 45
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

` Chairman made brief presentation on the report from joint TSG RAN WG1/WG2 meeting which had been held in Sophia
` Antipolis, France during 5-6, February 2002.
`
`
`- One of the key topics was to provide further input to TSG-T WG1 on the RAB parameter combinations to be used
`
`
` in R99 testing. Most of the meeting time was spent on this issue. Finally the LS was drafted and sent out to
` TSG T WG1 in T-doc 12A020031 LS on 34.108 updates.
`
`
`
`
`- The other issue was the discussion on R99 stuffs to be removed or deferred. There was an input provided by several
` operators which lists the functional priorities on various features. (12A020009 Functional priorities of operators ).
`
`
`
`
` The discussion was made based on this priority list and several features shown below were identified as candidates
`
`
` for removal/deferral. For those features, companies had been assigned to provide CRs for the next RAN.
`
`
`
`The list of candidates (RAN WG1 concerned features.)
`
`
`
`
`• Closed loop Tx diversity mode 2
`-- Nokia to provide CRs
`
`
`
`
`• Power control Algorithm 2
`
`
`-- Qualcomm to provide CRs
`
`
`
`
`• No coding
`
`
`
`
`
`
`-- Siemens to provide CRs
`
`
`
`
`• DPC mode1
`
`
`
`
`
`
`-- Panasonic to provide CRs
`
`
`
`
`• SSDT
`
`
`
`
`
`
`
`-- Nortel to provide CRs
`
`
` (Among above, the removal of "No Coding" (except 1.28Mcps TDD) was agreed by consensus.)
`
`
` These CRs are to be checked by RAN WG1 during this meeting whether their technical contents are correct or not.
`
`
` TSG RAN #15 will be asked to make the final decision on these CRs except "No Coding".
`
`
` /*** As for the "Power control Algorithm 2", RAN WG1 received a liaison statement from TSG T WG1 on Day 2
`
`
`
` afternoon saying that TSG T WG1 would like to keep this function. (R1-02-0446, T1R020060r1). Having
`
`
`
` received this LS, RAN WG1 and RAN WG2 concluded not to remove this function. (See Annex A)
`
`
`
` The answer LS for this was drafted by Qualcomm and sent to TSG T WG1 in R1-02-0485. (See No. 201) ***/
`
`The report of this meeting can be found in R1-02-0436 (12A020033).
`
`
`
`
`4. Identification of the incoming liaison statements and actions in the answering
`
`
` No.
`
`Title
`
`Source To/Cc Tdoc No. Contact point
`
`Notes
`
`1
`
` LS on HSDPA Control channel error rate
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
` LS on support of flexible signalling approach
` for Node B synchronisation for 1.28 Mcps TDD
`
` LS on TFCI power control in hard split
` mode
`
` Liaison statement on impacts of
` subscriber and equipment trace
`
` Liaison statement on "Procedure for specifying
` UMTS QoS Parameters per Application"
`
` Liaison Statement on downlink power
` control (DPC_Mode = 1)
`
` LS on physical layer measurement aspects
` and new concept of UP
`
`8
`
` Liaison Statement on HSDPA open issues
`
`9
`
` Response liaison on "Performance of Dedicated
` Pilot Demodulation" (answer to LS R4-020085)
`
`10
`
`11
`
` LS on Speech Codecs references in
` GERAN specifications
`
` Liaison Statement on deletion of power
` control algorithm 2 from R99
`
`RAN
`WG2
`RAN
`WG3
`RAN
`WG3
`SA
`WG5
`CN
`WG3
`RAN
`WG4
`RAN
`WG4
`RAN
`WG4
`RAN
`WG4
`GE-
`RAN
`T1-
`RF
`
`TO R1-02-0209
`(R2-020148)
`TO R1-02-0210
`(R3-020271)
`TO R1-02-0211
`(R3-020285)
`TO R1-02-0212
`(S5-020013)
`TO R1-02-0227
`(N3-020119)
`CC R1-02-0228
`(R4-020474)
`CC R1-02-0229
`(R4-020488)
`TO R1-02-0230
`(R4-020519)
`TO R1-02-0231
`(R4-020521)
`CC R1-02-0249
`(GP-020505)
`TO R1-02-0446
`(T1R020060r1)
`
`Qualcomm (*1)
`
`Day 1 13:42-13:49
`
`InterDigital (*2) See No. 196
`
`LGE
`
` (*3) See No. 178
`
`Nokia
`T-mobil
`
` Noted (*4)
`
`Day 1 09:40-09:45
`
`Ericsson
`
` Noted (*5)
`
`Day 1 09:46-09:49
`
`Lucent
`
` Noted (*6)
`
`Nokia
`
`Day 1 09:49-09:55
`
`  Joint session
` with R2 (*7)
`
`Day 1 09:55-10:02
`
`Vodafone See No. 117
`
`
`
`Ericsson
`
` Noted (*8)
`
`Day 1 10:03-10:08
`
`Nortel
`
` Noted (*9)
`
`Day 1 10:08-10:014
`
`Agilent
`
` (*10)  Joint
` session with R2
`
`
`
`
`
`
`
`
`
`
`(*1) Mr. Serge Willenegger (Qualcomm) proposed that this should be reviewed in the HSDPA agenda item.
`
` This proposal was agreed but eventually this LS was not reviewed during this meeting.
`(*2) Chairman suggested that this should be reviewed in connection with the discussion of Node B synchronisation for 1.28
`
` Mcps TDD. Eventually this LS was revisited on Day 2 midnight. (See No. 196)
`(*3) Chairman suggested that this should be reviewed in the relevant agenda item 7.1. Eventually this LS was revisited on
`
` Day 2 midnight. (See No. 178)
`(*4) This LS was sent to all TSG WGs.
`
` SA WG5 is currently specifying Subscriber and Equipment Trace for Release 5. The Work Item Description (WID) for
`
`- 2 -
`
`IPR2021-00908 Honeywell Exh. 1007 - Page 2 of 45
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

` Trace on a feature level was approved in TSG-SA #14 in December 2001. The approved WID was attached to this LS.
`
`
` (SP-010758). In this LS SA WG5 was asking all WGs to identify their own WIs, which would be affected by this
`
`
` Subscriber and Equipment Trace, and to provide SA WG5 with their names and unique identifiers in the 3GPP work
`
`
` plan. The list which shows the issues that SA WG5 has so far identified as being related to Trace was provided in the
`
`
` attachment.
`
`
` Chairman made a question to the floor whether people had identified any impacts from physical layer point of view.
`
`
` There was no response raised. Chairman concluded that this LS was noted. Mr. Dirk Gerstenberger (Ericsson) remarked
`
`
` that since SA WG5 was asking us to identify work items that would receive impact, we had better write an answer LS
`
`
` even if there was no such work items identified in this group. Chairman agreed to this remark and asked the floor to
`
`
` draft a brief answer. R1-02-0422 was allocated for this answer but no one was specifically assigned for drafting.
`
`
` Eventually R1-02-0422 was not provided during this meeting.
`
`
`(*5) Mr. Dirk Gerstenberger (Ericsson) presented this LS.
`
`
` CN WG3 has identified the need for guidance when setting the UMTS BS Attributes in the UE. CN WG3 has special
`
`
` concerns for how the information from the SDP parameters can be used for setting the UMTS QoS parameters. Also the
`
`
` UE must have guidelines for setting the UMTS BS Attributes for applications not using SDP. CN WG 3 has agreed to
`
`
`
` implement a procedure for specifying UMTS BS Attributes per Application that very much relies on cooperation from
`
` other WGs within 3GPP. In this LS they were asking us following.
`
`
`
`- To provide input to Radio Bearers corresponding to the UMTS BS Attributes specified by SA WG4 and SA WG1.
`
`
`
`- To investigate the possibility of making the Radio Bearers above "reference RBs" (as specified in TS 34.108).
`
`
` Mr. Dirk Gerstenberger remarked that there was nothing to do for us until we see the inputs from SA WG1or SA WG4.
`
`
` Chairman agreed with this comment and concluded that this LS as noted. R1-02-0423 was allocated for the brief answer.
`
`
` R1-02-0423 was drafted by Mr. Dirk Gerstenberger and approved on Day5. (See No. 202)
`
`(*6) Lucent presented this paper.
`
`
` In this LS RAN WG4 was asking 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 will be specified.
`
`
` Chairman stated that this DPC_MODE=1 is the one of the candidates of removal/deferral that were discussed in the
`
`
` joint session with RAN WG2 in Sophia Antipolis. He said that this issue would be discussed in the upcoming RAN
`
`
` meeting. He concluded that this LS was noted. We will see the response from RAN WG3 on this issue.
`
`(*7) Mr. Ville Steudle (Nokia) presented this LS.
`
`
` This was the answer LS to R2-012773. RAN WG2 had decided to extend the applicability of UE positioning
`
`
` measurements to all connected mode states for R99 and it had been asking RAN WG4 to align their specification based
`
`
` on the agreed changes in RAN WG2. (The CR RAN WG2 had agreed can be found in R2-012755. This was modified in
`
`
` RAN #14 into RP-010941 and approved.) In this answer LS, however RAN WG4 stated with several reasons that it
`
`
` would be unrealistic to assume those changes to be completed to R99 nor Rel-4 because it is too late and has too big
`
`
` impact.
`
`
` This LS was sent to RAN WG1 as CC but since RAN WG1 was going to approve some related CRs on TS 25.215,
`
`
` Chairman stated that this issue would be revisited when we discuss those related CRs. (from Nortel)
`
`
` Ms. Sarah Boumendil (Nortel) remarked that RAN WG2 would also discuss this issue in this meeting and we need to
`
`
` have good coordination with RAN WG2. Mr. Dirk Gerstenberger (Ericsson) suggested that this issue had better be
`
`
` discussed in the joint session with RAN WG2 this week since it would be difficult to make our own decision without
`
`
` RAN WG2. Chairman agreed with this suggestion. (See Annex A, No.14,15 18-21)
`
`(*8) Mr. Dirk Gerstenberger (Ericsson) presented this LS.
`
`
` This was the answer LS to R1-02-0191 which RAN WG1 had sent out from RAN WG1 #23 meeting in Espoo as an
`
`
` answer LS to R1-01-1282 (R4-011615). In the original LS RAN WG4 had stated that the performance requirements for
`
`
` demodulation of dedicated pilots within the Rel-5 WI Beamforming may depend on the number of dedicated pilot bits
`
`
` in the slot format. There had been some concerns in RAN WG4 that the performance with 2 or 4 pilot bits will not be
`
`
` sufficient for satisfactory operation of UTRA FDD. In this current LS RAN WG4 was informing us further clarification
`
`
` on this issue in answering the question RAN WG1 raised in R1-02-0191.
`
`
` Chairman concluded this LS as "Noted".
`
`(*9) Ms. Evelyne Le Strat (Nortel) presented this LS.
`
`
` This was sent to us as CC and no action was expected to RAN WG1.
`
`
` This LS was noted.
`
` (*10) This LS was received from TSG T1-RF on Day2 afternoon.
`
`
` Eventually this LS was reviewed in the joint session with RAN WG2 held on Day 2 evening. (See Annex A)
`
`
` The answer LS was drafted by Mr. Serge Willenegger (Qualcomm) in R1-02-0485 and approved on Day 4.
`
`
` (See No.201)
`
`
`/** Leftovers from RAN WG1#23 ***/
`Setting of S-field length as 0 bit in SSDT
`: Source : NEC, Vodafone
`R1-02-0022
`This was postponed in RAN WG1#23. There had been a discussion that the proposed change in this CR should be reflected in
`RAN WG3 specifications rather than RAN WG1 specification. Ms. Nahoko Takano (NEC) now clarified that they reached
`conclusion to withdraw this CR after having had RAN WG3 opinion on this issue offline.
`
`
`
`(Day1 10:16)
`
`
`
`- 3 -
`
`IPR2021-00908 Honeywell Exh. 1007 - Page 3 of 45
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`5. Change Requests for WG1 Release –99 & Release-4 specifications
`
`
`No. R CR rev TS
`
`Tdoc
`
`Title
`
`Cat Source Conclusion Notes
`
`12 99 113
`
`- 25.215 R1-02-0330
`
`13 4 114
`
`- 25.215 R1-02-0330
`
`14 99 100 3 25.215 R1-02-0331
`
`15 4 101 3 25.215 R1-02-0331
`
`16 99 XXX
`
`- 25.306 R1-02-0170
`
` Clarification of UE
` measurements applicability
` Clarification of UE
` measurements applicability
` Correction to the definitions of UE and
` UTRAN GPS timing of cell frames for
` UE positioning
` Correction to the definitions of UE and
` UTRAN GPS timing of cell frames for
` UE positioning
` Clarification of Maximum
` number of TFC in the TFCS
`
`F
`
`A
`
`F
`
`A
`
`Nortel
`
`Nortel
`
`F Panasonic
`
`Reversion to be
`provided for
`joint session
`with R2
`
`To be discussed
`in the joint
`session.
`Coversheet to
`be modified.
`
` e-mail
`discussion
`
`(*1)
`
`Day 1 10:49-12:26
`
`(*2)
`
`Day 1 12:27-12:39
`
` (*3)
`
`Day1 12:40-12:59
`
` (*4)
`
`Day1 13:00-13:08
`
`17
`
`-
`
`-
`
`-
`
`-
`
`R1-02-0252
`
`18 99 115
`
`- 25.215 R1-02-0448
`
`19 4 116
`
`- 25.215 R1-02-0448
`
`20 99 117
`
`- 25.215 R1-02-0454
`
` Simultaneous reception of DPCH
` and SCCPCH
` Correction to the definition of UTRAN
` GPS timing of cell frames for UE
` positioning
` Correction to the definitions of UTRAN
` GPS timing of cell frames for UE
` positioning
`
` Correction to the definition of UE GPS
` timing of cell frames for UE positioning
`
`-
`
`F
`
`A
`
`F
`
`21 4 118
`
`- 25.215 R1-02-0454
`
` Correction to the definition of UE GPS
` timing of cell frames for UE positioning A
`
`22 99 113 1 25.215 R1-02-0455
`
`23 4 114 1 25.215 R1-02-0455
`
`24 99 124
`
`- 25.212 R1-02-0201
`
`25 4 125
`
`- 25.212 R1-02-0201
`
` Clarification of UE
` measurements applicability
`
` Clarification of UE
` measurements applicability
` Introduction of a new frame
` type in uplink compressed mode
`
`F
`
`A
`
`C
`
`A
`
`Intel
`
` Joint Session
`with R2 (Day2)
`
`Nortel
`
`Approved
`
`(*5)
`
`Day 4 14:14
`
`Nortel
`
`Approved
`
`(*6)
`
`Day 4 14:16
`
`Nortel
`Nokia
`
`Approved
`
`(*7)
`
`Day 4 14:30
`
`Huawei
`
`Not
`approved
`
`(*8)
`
`26 99 230
`
`- 25.214 R1-02-0023
`
`27 4 231
`
`- 25.214 R1-02-0023
`
`28 99 239
`
`- 25.214 R1-02-0310
`
`29 4 240
`
`- 25.214 R1-02-0310
`
`30 99 235
`
`- 25.214 R1-02-0207
`
`31 4 236
`
`- 25.214 R1-02-0207
`
`32
`
`-
`
`-
`
`-
`
`-
`
`R1-02-0392
`
`33 99 226
`
`- 25.214 R1-02-0305
`
`34 4 227
`
`- 25.214 R1-02-0305
`
`35 99 138 1 25.211 R1-02-0424
`
`36 4 139 1 25.211 R1-02-0424
`
` Introduction of a new frame
` type in uplink compressed mode
` Setting of Qth threshold
` parameter in SSDT
`
` Setting of Qth threshold
` parameter in SSDT
` TPC procedure in UE when
` SSDT is activated
`
` TPC procedure in UE when
` SSDT is activated
`
` Clarification of closed loop transmit
` diversity during soft handover
`
` Clarification of closed loop transmit
` diversity during soft handover
`
` Closed Loop Transmit Diversity
` for DSCH during SHO
`
` Clarification on DPCCH dedicated
` pilot bits with closed loop mode 1
`
` Clarification on DPCCH dedicated
` pilot bits with closed loop mode 1
`
` Clarification of different diversity
` modes used in the same active set
`
` Clarification of different diversity
` modes used in the same active set
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`NEC
`Fujitsu
`
`To be
`revised
`
`Nokia
`
`To be
`revised
`
`Motorola
`
`To be
`revised
`
`- Motorola
`
`Noted
`
`F
`
`A
`
`F
`
`A
`
`NEC
`
`Panasonic
`
`Approved
`coversheet
`to be
`corrected
`
`Approved
`coversheet
` to be
`corrected
`
`37
`
`-
`
`-
`
`-
`
`-
`
`R1-02-0251 Physical channel reconfiguration
`
`-
`
`Intel
`
`Noted
`
`Day 4 14:39
`
`(*9)
`
`Day 4 14:47
`
`(*10)
`
`Day 4 15:02
`
`(*11)
`
`Day 4 15:24
`
` (*11)
`
`Day 4 15:13-24
`
`(*12)
`
`Day 4 15:28
`
`(*13)
`
`Day 4 15:48
`
` (*14)
`
`Day 4 16:54-17:01
`
`- 4 -
`
`IPR2021-00908 Honeywell Exh. 1007 - Page 4 of 45
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`No. R CR rev TS
`
`Tdoc
`
`Title
`
`Cat Source Conclusion Notes
`
`38 99 009
`
`- 25.201 R1-02-0253
`
` Removal of channel coding option "no
` coding" for FDD and 3.84 Mcps TDD
`
`39 4 010
`
`- 25.201 R1-02-0253
`
` Removal of channel coding option "no
` coding" for FDD and 3.84 Mcps TDD
`
`40 99 127 1 25.212 R1-02-0308
`
`41 4 128 1 25.212 R1-02-0308
`
`42 99 110
`
`- 25.215 R1-02-0306
`
`43 4 111
`
`- 25.215 R1-02-0306
`
`44 99 067 1 25.222 R1-02-0309
`
`45 4 068 1 25.222 R1-02-0309
`
`46 99 044
`
`- 25.225 R1-02-0307
`
`47 4 045
`
`- 25.225 R1-02-0307
`
`48 99 142
`
`- 25.211 R1-02-0304
`
`49 99 238
`
`- 25.214 R1-02-0303
`
` Removal of channel coding
` option "no coding" for FDD
`
` Removal of channel coding
` option "no coding" for FDD
` Removal of channel coding
` option "no coding" for FDD
`
` Removal of channel coding
` option "no coding" for FDD
`
` Removal of channel coding option
` "no coding" for 3.84 Mcps TDD
`
` Removal of channel coding option
` "no coding" for 3.84 Mcps TDD
`
` Removal of channel coding option
` "no coding" 3.84 Mcps TDD
`
` Removal of channel coding option
` "no coding" for 3.84 Mcps TDD
`
` Deferring of mandatory UE
` support of SSDT to Rel-4
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`F
`
`Siemens
`
`To be
`revised
`
`Siemens
`
`Approved
`(coversheet
`to be
`corrected)
`
`(*15)
`
`Day 4 17:09
`
`(*15)
`
`Day 4 17:15
`
`Siemens Approved
`
`(*15)
`
`Day 4 17:17
`
`Siemens Approved
`
`(*15)
`
`Day 4 17:19
`
`Siemens Approved
`
`(*15)
`
`Nortel
`
`Technical
`contents
`were
`checked.
`
`Day 4 17:20
`
` (*16)
`
`Day 4 17:42
`
` (*16)
`
`50 99 249
`
`- 25.214 R1-02-0160
`
`51 99 074 3 25.221 R1-02-0442
`
`52 4 075 3 25.221 R1-02-0442
`
`53 99 070 2 25.221 R1-02-0337
`
`54 4 071 2 25.221 R1-02-0337
`
`55 99 072 1 25.221 R1-02-0336
`
`56 4 073 1 25.221 R1-02-0336
`
`57 99 064 3 25.222 R1-02-0282
`
`58 4 065 3 25.222 R1-02-0282
`
`59 99 062 1 25.222 R1-02-0338
`
`60 4 063 1 25.222 R1-02-0338
`
`61 99 070
`
`- 25.222 R1-02-0339
`
`62 4 071
`
`- 25.222 R1-02-0339
`
`63 99 024 1 25.223 R1-02-0340
`
` Deferring of mandatory UE
` support of SSDT to Rel-4
` Deferral of DPC_MODE=1 of
` downlink power control
` Correction to a transmission of
` paging indicators bits
`
` Correction to a transmission of
` paging indicators bits
` Clarification of spreading for UL
` physical channels
`
` Clarification of spreading for UL
` physical channels
` Common midamble Allocation
` for beacon time slot
`
` Common midamble Allocation
` for beacon time slot
` Clarification of the requirement for the
` determination of the rate matching parameters
` and editorial corrections to 25.222
` Clarification of the requirement for the
` determination of the rate matching parameters
` and editorial corrections to 25.222
` Correction to addition of padding
` zeros to PICH in TDD
`
` Correction to addition of padding
` zeros to PICH in TDD
` Second stage interleaving and
` physical channel mapping
`
` Second stage interleaving and
` physical channel Mapping
`
` Removal of quantisation of j gain factor
` when calculated from a reference TFC
`
`64 4 025 1 25.223 R1-02-0340 Removal of quantisation of j gain factor
` when calculated from a reference TFC
`
`F Panasonic
`
`To be
`revised
`
`Day 4 17:44
`
` (*17)
`
`Day 4 17:53
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`InterDigital Approved
`
`(*18)
`
`Day 4 18:01
`
`IPWireless Approved
`
`(*19)
`
`Day 4 18:03
`
`IPWireless
`Siemens
`
`Approved
`
`(*20)
`
`Day 4 18:04
`
`InterDigital Approved
`
`(*21)
`
`Day 4 18:05
`
`IPWireless Approved
`
`(*22)
`
`Day 4 18:05
`
`IPWireless Postponed
`
`(*23)
`
`Day 4 18:10
`
`IPWireless Approved
`
`(*24)
`
`Day 4 18:12
`
`- 5 -
`
`IPR2021-00908 Honeywell Exh. 1007 - Page 5 of 45
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

`No. R CR rev TS
`
`Tdoc
`
`Title
`
`Cat Source Conclusion Notes
`
`65 99 027
`
`- 25.223 R1-02-0341
`
` Channelisation code-specific multiplier
` operation under autonomous SF change
`
`F
`
`66 4 028
`
`- 25.223 R1-02-0341
`
` Channelisation code-specific multiplier
` operation under autonomous SF change A
`
`67 99 029
`
`- 25.223 R1-02-0342
`
`68 4 030
`
`- 25.223 R1-02-0342
`
` Alignment of gamma(i) gains of 25.223
` with SIR target of WG2 25.331
`
` Alignment of gamma(i) gains of 25.223
` with SIR target of WG2 25.331
`
`69 99 078 1 25.224 R1-02-0343
`
` Removal of quantisation of j gain factor
` when calculated from a reference TFC
`
`70 4 079 1 25.224 R1-02-0343 Removal of quantisation of j gain factor
` when calculated from a reference TFC
`
`71 99 085
`
`- 25.224 R1-02-0344 Transmit diversity on PICH
`
`72 4 086
`
`- 25.224 R1-02-0344 Transmit diversity on PICH
`
`73 99 083
`
`- 25.224 R1-02-0284
`
`74 4 084
`
`- 25.224 R1-02-0284
`
` TDD MAC layer subchannel
` assignment
`
` TDD MAC layer subchannel
` assignment
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`F
`
`A
`
`IPWireless Approved
`
`(*25)
`
`Day 4 18:14
`
`IPWireless
`Siemens
`
`Approved
`
`(*26)
`
`Day 4 18:16
`
`IPWireless Approved
`
`(*27)
`
`Day 4 18:18
`
`IPWireless
`Siemens
`
`Approved
`
`(*28)
`
`InterDigital
`
`Approved
`but revised
`
`Day 4 18:22
`
`(*29)
`
`Day 4 18:22
`
`75
`
`-
`
`-
`
`-
`
`-
`
`R1-02-0410
`
`- IPWireless
`
`Noted
`
` (*30)
`
` Response to WG3 - setting of appropriate
` synchronisation channel powers for TDD
`
`76 99 009 1 25.201 R1-02-0495
`
` Removal of channel coding option "no
` coding” for FDD and 3.84 Mcps TDD
`
`77 4 010
`
`- 25.201 R1-02-0495
`
`78 99 145
`
`- 25.211 R1-02-0496
`
`79 99 243
`
`- 25.214 R1-02-0497
`
`80 99 249
`
`- 25.214 R1-02-0498
`
` Removal of channel coding option “no
` coding” for FDD and 3.84 Mcps TDD
`
` Deferring of closed loop mode 2
` transmit diversity from R99
`
` Deferring of closed loop mode 2
` transmit diversity from R99
` Deferral of DPC_MODE=1 of
` downlink power contrl
`
`Day 4 17:53
`
`F
`
`A
`
`F
`
`F
`
`Siemens Approved
`
`(*31)
`
`Nokia
`
`Technical
`contents
`were
`checked.
`
`Day 5 10:41
`
` (*32)
`
`Day5 10:43
`
` (*32)
`
`Day5 10:45
`
`F Panasonic Reviewed
`
` (*33)
`
`Day5 10:47
`
`81 4 236 1 25.214 R1-02-0489
`
` Clarification of closed loop transmit
` diversity during soft handover
`
`A
`
`Motorola
`Samsung
`
`Approved
`
` (*34)
`
`Day5 10:49
`
`82 99 230 1 25.214 R1-02-0487 Qth threshold parameter in SSDT F
`
`83 4 231 1 25.214 R1-02-0487 Qth threshold parameter in SSDT A
`
`84 99 239 1 25.214 R1-02-0488
`
`85 4 240 1 25.214 R1-02-0488
`
`86 99 083 1 25.224 R1-02-0501
`
`87 4 084 1 25.224 R1-02-0501
`
` TPC procedure in UE when
` SSDT is activated
`
` TPC procedure in UE when
` SSDT is activated
` TDD MAC layer subchannel
` assignment
`
` TDD MAC layer subchannel
` assignment
`
`F
`
`A
`
`F
`
`A
`
`NEC
`Fujitsu
`
`Approved
`
`(*35)
`
`Day 5 10:41
`Day 5 14:42
`
`Nokia
`
`Approved
`
`(*36)
`
`Day 5 14:45
`
`InterDigital Approved
`
`(*37)
`
`Day 5 14:48
`
`
`
`
`
`
`
`
`
`
`
`(*1) Ms. Sarah Boumendil (Nortel) presented this pair of CRs.
`
` In RAN WG1#23 there had been a CR proposed by Nokia on the clarification of RAN WG1 understanding of
`
` applicability of the measurement with respect to "idle/active" mode to clarify the relation between those modes and
`
` RRC states (R1-02-0174). The current CR presented Nortel's approach for this problem in terms of UE. Since
`
` Mr. Ville Steudle (Nokia) announced that Nokia had withdrawn their CR in R1-02-0174, the current paper became an
`
` unique proposal for the solution. There was a relevant LS from RAN WG4 in R1-02-0229. (See No. 7)
` Mr. Ville Steudle commented that the summary of change in the coversheet should be modified because the current
`
`
` description might give an impression that TS 25.215 specifies the reporting requirements or performance requirements
`
` which are in the area of RAN WG4. The comment was agreed by the proponent. It was clarified that the intention was
`
`- 6 -
`
`IPR2021-00908 Honeywell Exh. 1007 - Page 6 of 45
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

` to clarify when or in which RRC state UE is required to perform certain measurement (one-to-one mapping).
`
`
`/*** Day1 Coffee break 11:01-11:44 ***/
`
`
` After coffee break, detailed reviewal was done on section-by-section basis. The intention was to clarify first the
`
`
` RAN WG1 understanding of the measurements. Discussion would continue with RAN WG2 in the joint session to see
`
`
` if there are some mismatches with RAN WG2 in the understanding of measurements. Ms. Sarah Boumendil stated that
`
`
` Nortel had already presented paper in the joint meeting with RAN WG1/RAN WG2 in Sophia Antipolis in which they
`
`
` listed all the measurements regarding what they can be used for and the RRC state applicability in 12A020010.
`
`
` Several points were noted for the joint session with RAN WG2 scheduled on Day 2. Chairman asked proponents
`
`
` together with other interested party to provide new version for the discussion with RAN WG2 reflecting the
`
`
` comments received. The revision can be found in R1-02-0431.
`
`(*2) Ms. Sarah Boumendil (Nortel) presented this pair of CRs. This was the revision of R1-02-0108. UE part modifications
`
`
` had been unchanged from R1-02-0108. It proposed "reference cell" instead of current "cell within the active set".
`
`
` UTRAN part had been slightly modified from the previous revision.
`
`
` Chairman stated that making "reference cell" instead of "cell within the active set" would definitely have impacts on the
`
`
` layer 1 implementation and it is not just the change of the terminology. He said that we need to discuss with
`
`
` RAN WG2 about the motivation of this change for R99. Why is this needed ?
`
`
` Mr. Ville Steudle (Nokia) remarked that this change would require much work in RAN WG4 as well and it would not
`
`
` be feasible at this stage. (It is too late for R99 and Rel-4. It might be possible for Rel-5.)
` Chairman commented that the Consequences if not approved in the coversheet needs to be clarified because with the
`
`
`
`
` current description, it is not clear exactly what requirements are conflicting and incorrect. He asked the proponent to
`
`
` revise this to clarify the conflicting items.
`
`
` Chairman concluded this issue to be revisited in the joint session with RAN WG2.
`
`(*3) Mr. Hidetoshi Suzuki (Panasonic) presented this pair of CRs.
`
`
` Mr. Markku Tarkiainen (Nokia) and Mr. Dirk Gerstenberger (Ericsson) remarked that they did not see that much
`
`
` additional gain by having this proposed text. Ms. Evelyne Le Strat (Nortel) remarked that she either did not see the real
` need of having this CR in terms of point 1 in the reason for change in the coversheet however she added that there is a
`
`
` certain ambiguity in DSCH case (point 3 in the reason for change) although the current proposed text needs to be
`
`
` modified. ("the difference of channelisation code"  "the difference of the number of channelisation code")
`
`
`
`
` After some discussion, chairman suggested that the issue on point 3 could be discussed in the joint session with
`
`
` RAN WG2.
`
`
` On Day5 Mr. Hidetoshi Suzuki announced that agreement had not been obtained by the offline discussion. He proposed
`
`
` to have e-mail discussion on this issue prior to the RAN#15. If we can make agreement on the e-mail discussion
`
`
` Mr. Hidetoshi Suzuki will provide the CR directly to RAN#15 with source name as Panasonic.
`(Day5 14:47)
`
`(*4) Mr. Alex Margulis (Intel) presented this discussion paper.
`
`
` Simultaneous reception of DPCH and SCCPCH is an optional UE capability and may be used for:
`
`
`
`- Reception of Cell Broadcast Service (CBS) mapped to FACH when dedicated channel is allocated to the UE.
`
`
`
`- DRAC control of an uplink DCH
`
`
` But according to the current description in TS 25.331 this capability of simultaneous reception is tied to the DRAC
`
`
` procedure since there is a following restriction;
`
`
`
` A UE that supports the simultaneous reception of one SCCPCH and one DPCH shall support the DRAC procedure
`
`
` This paper suggested removal of this restriction from TS 25.331.
`
`
` A couple of comments raised saying that this is maybe inconsistency between 2 RAN WG2 specifications and
`
`
` therefore it should be discussed in RAN WG2 internally.
`
`
` Chairman agreed with these comments and suggested the proponent to present this paper in RAN WG2. Intel
`
`
` questioned if it is possible to discuss this issue in the joint session because currently there is no Intel delegate attending
`
`
` in RAN WG2. Chairman accepted this request. (See Annex A)
`/*** Day1 lunch break 13:09 - 14:19 ***/
`
`(*5) Ms. Sarah Boumendil (Nortel) presented this pair of CRs. This CR was the revision of R1-02-0331 which had been
`
`
` reviewed on Day1. (See No.14, 15) Nortel divided the original CR into 2 separate CRs. This paper contains the
`
`
` UTRAN part. This CR was approved without any comments.
`
`(*6) Ms. Sarah Boumendil (Nortel) presented this pair of CRs. This paper was the revision of R1-02-0331 which had been
`
`
` reviewed on Day1. (See No.14, 15) Nortel divided the original CR into 2 separate CRs. This paper contains the UE part.
`
`
` "cell within the active set" was now proposed to be changed as "chosen by the UE".
`
`
` This CR was approved with no comments.
`
`(*7) Ms. Sarah Boumendil (Nortel) presented this pair of CRs. This paper was the revision of R1-01-0330 which was
`
`
` reviewed on Day1. (See No.12, 13)
`
`
` There short clarification discussion took place but finally this CR was approved.
`
`
` TDD version would be presented in RAN WG1#25 in R1-02-0375 and R1-02-0376. (measurement applicability and
`
`
` UTRAN GPS timing.)
`
`(*8) Judging from the CR coversheet this paper seemed to be proposing some kind of potential optimisation but there was
`
`
` no supporting simulation data. Chairman commented that we could not approve this kind of optimisation for R99.
`
`
` He said that even if there would be some performance improvement in certain cases it would not justify introducing
`
`
` new slot or frame structure for R99 at this stage. In conclusion this CR was not approved.
`
`(*9) Ms. Nahoko Takano (NEC) presented this pair of CRs. This CR had been postponed from RAN WG1#23.
`
`
` Ms. Evelyne Le Strat (Nortel) commented that in RAN #14 we had agreed a work item for the introduction of SSDT in
`
`
` the UTRAN side for Rel-5 and it means in effect that we agreed that SSDT in the UTRAN is not part of the R99 and
`
`
` Rel-4 specifications anymore. She said therefore we should rather state clearly that the behaviour for SSDT in the
`
`
` UTRAN is not specified for R99 and Rel-4.
`
`- 7 -
`
`Deleted: Although a delegate from Huawei was attending
`the meeting no presentation was done on this paper.¶
`
`
`IPR2021-00908 Honeywell Exh. 1007 - Page 7 of 45
`(Honeywell International, Inc., et al. v. 3G Licensing S.A.)
`
`

`

` Mr. Dirk Gerstenberger (Ericsson) shared the view with Ms. Evelyne Le Strat.
`
`
` Lucent commented that whole sentence (see below) should be removed.
`
`
`
`"The received uplink signal quality satisfies a quality threshold, Qth a parameter defined by the network."
`
`
` Chairman suggested the proponent to revise the CR taking into account the comments receive