R1-071245 (Approved ReportWG1 #47bis)

3GPP TSG RAN WG1 Meeting #48 R1-071245
St Louis, US, 12 –16 February, 2007

Agenda item 3
Title: Approved Report of 3GPP TSG RAN WG1 #47bis v2.0.0
(Sorrento, Italy, 15 – 19 January, 2007)
Document for: Information
Source: MCC Support
Notes:
All timestamps in this document are in GMT+1H unless otherwise noted.
Fact Summary
Meeting: 3GPP TSG RAN WG1 #47bis
Dates: 15th through 19th January, 2007
Venue: Hilton Hotel, Sorrento, Italy
Host: European Friends of 3GPP
Attendees: 218 delegates
Documents: 637 (including some withdrawn and post-meeting artefacts)
Yoshikazu Ishii
ETSI Mobile Competence Center
yoshikazu.ishii@etsi.org
St Louis, US, 12 – 16 February, 2006
Table of contents
Executive summary..........................................................................................................................................1
1. Opening of the meeting..........................................................................................................................3
1.1 Call for IPR..........................................................................................................................................................3
2 Approval of the agenda...........................................................................................................................3
3. Approval of the minutes from previous meeting....................................................................................4
4. Liaison statement handling.....................................................................................................................5
5. Maintenance of R99, Rel4, Rel5, Rel6, Rel-7.......................................................................................10
6. Evolved UTRA and UTRAN................................................................................................................14
6.1 Updated Physical Layer Specifications.............................................................................................................17
6.2 Remaining issues on numerology......................................................................................................................18
6.3 Modulation.........................................................................................................................................................22
6.4 Channel coding..................................................................................................................................................24
6.5 Basic Access Procedures...................................................................................................................................29
6.5.1 RACH Procedure Physical Layer Aspects...................................................................................................29
6.5.2 SCH and Cell Search....................................................................................................................................31
6.6 Reference signal structure..................................................................................................................................34
6.6.1 Downlink reference signals..........................................................................................................................34
6.6.2 Uplink reference signals...............................................................................................................................36
6.7 Downlink MIMO, Transmit Diversity and Beamforming.................................................................................38
6.7.1 Mapping of codewords to layers..................................................................................................................39
6.7.2 Precoding details..........................................................................................................................................39
6.7.3 UE feedback.................................................................................................................................................41
6.7.4 MU-MIMO..................................................................................................................................................44
6.7.5 Transmit Diversity.......................................................................................................................................45
6.8 Uplink MIMO and Transmit Diversity..............................................................................................................45
6.8.1 SU-MIMO....................................................................................................................................................46
6.8.2 SDMA..........................................................................................................................................................46
6.8.3 Transmit Diversity.......................................................................................................................................47
6.9 Specification of Control Signalling...................................................................................................................47
6.9.1 Uplink Control Signalling............................................................................................................................49
6.9.2 Downlink Control Signalling.......................................................................................................................50
6.10 Physical Layer specification aspects of Link Adaptation..................................................................................53
6.11 UL Timing Control............................................................................................................................................53
6.12 UL/DL Power Control.......................................................................................................................................54
6.13 Physical Layer Measurements...........................................................................................................................56
7. HSPA Evolution...................................................................................................................................57
7.1 MIMO in UTRA (Rel-7 Work Item).................................................................................................................57
7.2 Continuous Connectivity for Packet Data Users...............................................................................................60
7.3 Higher Order Modulation..................................................................................................................................62
7.3.1 64QAM for HSDPA(FDD)..........................................................................................................................62
7.3.2 16QAM for HSUPA(FDD)..........................................................................................................................64
7.4 Enhancement FDD cell FACH..........................................................................................................................66
7.5 Review of MBMS Physical Layer Enhancement Work Item Sheet..................................................................67
2
8. 1.28Mcps TDD Enhanced Uplink.........................................................................................................68
9. Closing of the meeting..........................................................................................................................70
Annex A: List of participants at RAN1 #47bis...........................................................................................71
Annex B: TSG RAN WG1 meetings in 2007.............................................................................................78
Annex C: List of CRs agreed at RAN1#47bis............................................................................................79
Annex D: List of Outgoing LSs from RAN1#47bis....................................................................................81
Annex E: List of Tdocs at RAN1 #47bis....................................................................................................82
Annex F: List of actions...........................................................................................................................117
3
Executive summary
3GPP TSG WG RAN1 #47bis meeting took place in Hilton Hotel, Sorrento, Italy. The meeting started at 9:15 on Monday
15th January and finished at 17:10 on Friday 19th 2007.
On the first day, after incoming LSs were treated, Rel-5, Rel-6 and Rel-7 topics including CRs were discussed. The output
from this discussion, some CRs were agreed; Power control function of HS-SICH and HS-SCCH for LCR TDD, HS-SICH
reception quality of HS-SICH for LCR TDD, Closed Loop Uplink HS-SICH Power Control for 1.28 Mcps TDD,
Enhanced F-DPCH.
LTE session started from afternoon on Monday and there were parallel sessions for LTE by using two meeting rooms on
Wednesday and Thursday. The outcome from this meeting on LTE topics was followed.
- The endorsed latest version: TS36.211 v.0.3.0 (R1-070627), 36.212 v.0.3.0 (R1-070562), 36.213
v.0.2.0 (R1-070563)
- Numerology: The discussion could reach to agreement on DFT sizes, way forward for 7.5KHz CP
length, TDM multiplexing on MBSFN and non-MBSFN, way forward on half duplex operation, way
forward on UE minimum transmission bandwidth, idle period position for E-UTRA TDD.
- Modulation scheme: The discussion could reach to agreement on UE specific UL scrambling, and as for
Frequency Domain Spectrum Shaping (FDSS), LS to RAN4 on expected improvement with proposed
FDSS functions, and on general issue of Tx power boosting beyond 24dBm was sent in R1-070632.
- Channel coding: RAN1 selects QPP and will base the further work on this.
- Basic Access Procedures: The discussion could reach to the agreement on some points on RACH and
random access procedure, and SCH and cell search procedure
- References signal structure: As for Downlink RS, the way forward for DL RS frequency hopping was
agreed. As for Uplink RS, the agreement of Long RS was endorsed. In addition, there was agreement on
RS sequence length.
- Downlink MIMO, Tx. Diversity and Beamforming: The discussion could reach to agreement on
precoding for TDD, mapping codewords to layers, precoding codebook construction focusing on
optimizing SU-MIMO, UE feedback scheme and MU-MIMO (semi-static configuration of SU-MIMO or
MU-MIMO per a UE.
- Uplink MIMO and Tx. Diversity: It was agreed that SU-MIMO should be addressed in a future
release. As for Tx. Diversity, it was agreed not to specify the blind antenna switching/hopping in the
standard.
- Control Signalling: The structure of data-non-associated control signalling was endorsed in R1-070602.
- UL Timing Control: The current status of TA discussion in RAN1 was listed.
- UL/DL Power Control: The basic UL power control mechanism was agreed, such as slow power
control, controlled PSD.
The work for HSPA Evolution went well using the whole day of Tuesday. The outcome was as followed.
- MIMO in UTRAN: Working assumption for HS-SCCH part 1 structure for MIMO and 64QAM. In
addition, The principle for ACK/NACK power setting and the CR regarding CQI reporting was endorsed
- Continuous Connectivity for Packet Data Users: Regarding interaction of CPC and Compressed
Mode, it was agreed as way forward to continue work to include the principle outlined in R1-070352 in a
separate set of CRs for CPC.
- Higher Order Modulation for HSDPA and USUPA (FDD): The way forward of 64QAM for HSDPA
and 16QAM for HSUPA was agreed and the sets of RAN1 CRs were agreed as baseline for further
discussion.
- Enhanced FDD Cell FACH: It was agree as way forward to continue the work based on HSDPA in cell
FACH. FFS until next meeting whether HS-SCCH can be reduced.
- Review of MBMS Physical Layer Enhancement Work Item Sheet: Proposal for Work Item for
MBMS FDD Physical layer Enhancements and Proposal for Work Item for MBMS TDD Physical Layer
Improvements were agreed.
1
Finally, 1.28Mcps TDD enhanced uplink topics was discussed at early morning session on Wednesday and some text
proposals to TR25.827 were endorsed and the TR was updated to version 1.1.0.
The number of contribution documents for this meeting was 619, and those documents were categorized as followed.
Input Discussed
Agenda Item
Document Document
Liaison statement handling 42 42
Maintenance of R99, Rel4, Rel5, Rel6, Rel7 27 25
Evolved UTRA and UTRAN (Physical Layer) 434 154
HSPA Evolution 82 74
1.28 Mcps TDD Enhanced Uplink 17 17
2
1. Opening of the meeting

06/11/2007 09:15
The RAN1 Chairman, Mr. Dirk Gerstenberger and welcomed the participants to the 47bis RAN WG1 meeting and opened
the meeting at 09.15.
Mr. Enrico Buracchini from Telecom Italia welcomed the delegates on behalf of the European Friends of 3GPP.
1.1 Call for IPR

06/11/2007 09:20
The Chairman drew attention to Members' obligations under the 3GPP Partner Organizations'
IPR policies. Every Individual Member organization is obliged to declare to the Partner
Organization or Organizations of which it is a member any IPR owned by the Individual
Member or any other organization which is or is likely to become essential to the work of 3GPP.
The attention of the members of this Technical Specification Group is drawn to the fact that 3GPP
Individual Members have the obligation under the IPR Policies of their respective Organizational Partners
to inform their respective Organizational Partners of Essential IPRs they become aware of.
The members take note that they are hereby invited:
 to investigate in their company whether their company does own IPRs which are, or are likely to become
Essential in respect of the work of the Technical Specification Group.
 to notify the Director-General, or the Chairman of their respective Organizational Partners, of all
potential IPRs that their company may own, by means of the IPR Statement and the Licensing declaration
forms (e.g. see the ETSI IPR forms http://webapp.etsi.org/Ipr/).
2 Approval of the agenda

R1-070001 Draft Agenda for RAN1#47bis (RAN1 Chairman)
15/01/2007 09:20 Presented by Mr. Dirk Gerstenberger.
Discussion (Question / Comment):
Decision: This document was approved.
3
3. Approval of the minutes from previous meeting

R1-070002 Draft Report of RAN1#47 (MCC)
15/01/2007 09:25 Presented by Mr. Yoshikazu Ishii
Decision: This document was approved in R1-070633.
R1-070633 Approved Report of RAN1#47 (MCC)
4
4. Liaison statement handling

R1-070003 LS on Synchronization at handover (To: RAN1, Cc: RAN4)
(RAN WG2, LG Electronics)
15/01/2007 09:25 Presented by Mr. Dragan Vujcic
Decision: This document was noted.
R1-070305 Proposed Response to LS on Synchronization at Handover (Siemens, Nokia)
15/01/2007 09:30 Presented by Mr. Mieszko Chmiel from Siemens
Decision: It was decided to revisit this document on Thursday at the TA discussion, provided an LS answer on
Friday.
R1-070599 Draft reply LS to RAN2 on Synchronization at Handover (Siemens)
19/01/2007 09:30 Presented by Mr. Mieszko Chmiel from Siemens
Decision: This draft LS was approved in R1-070622 with addition of RAN3 as Cc.
R1-070004 Estimated peak hour loads in LTE (To: RAN3, Cc: RAN1)
(RAN WG2, Samsung)
15/01/2007 09:40 Presented by Mr. Juho Lee
R1-070005 LS on improved HARQ operation (To: RAN1)
(RAN WG2, ASUSTek)
15/01/2007 09:45 Presented by Mr. Elliot Jen
ASUSTek commented that they have a document related to this LS but it was for LTE AI.
Decision: This document was noted. It was decided to check again at the end of week if an answer can be provided
(related document for LTE in R1=070175). On Friday, the status was checked but there was no progress during the
week so that it was decided to try to provide an answer at the next meeting if the RAN1 discussion has progressed
sufficiently
R1-070006 LS on status of Rel-7 FDD MIMO (To: RAN1)
(RAN WG2, Vodafone)
15/01/2007 09:50 Presented by Mr. Prakash Bhat
Decision: This document was noted. The related Tdoc is R1-070512 under MIMO Rel-7 so that it was decided to
and discuss the answer LS on Tuesday.
R1-070007 LS on Primary BCH Transmission (To: RAN1)
(RAN WG2, NTT DoCoMo)
15/01/2007 09:53 Presented by Mr. Sadayuki Abeta
R1-070083 Proposed response to RAN2 LS in [R1-070007]
(NTT DoCoMo, Fujitsu, Mitsubishi Electric, NEC, Panasonic, Sharp)
15/01/2007 09:55 Presented by Mr. Yoshihisa Kishiyama
NTT DoCoMo commented that 300 bits is many number considering the complexity and so on for cell search
procedure, so that at first RAN1 would better ask RAN2 to reduce the number of bits on P-BCH.
Stefan Parkvall from Ericsson commented that increasing BW is much impact on cell search procedure compared
with Tx Div approach.
R1-070304 Proposed Response to LS on Primary BCH Transmission (Siemens)
15/01/2007 10:05 Presented by Mr. Mieszko Chmiel
Rupert Rheinschmitt from Alcatel-Lucent commented that regarding the simulation result for Tx. Diversity we have
not had a official decision on MIMO Tx Diversity for the control channel so that we should take a consideration of
5
the RAN1 official decision on Tx. Diversity before submitting the response for RAN2 even though the change are
expected to be much less depending on the Tx Diversity scheme. Mr. Chairman commented that we would make a
decision on Tx. Diversity scheme but RAN2 would not hope the delay for the response from RAN1.
R1-070369 Answer to RAN2 LS on Primary BCH Transmission (Nokia)
15/01/2007 10:15 Presented by Mr. Asbjörn Grovlen
Erik Dahlman from Ericsson supported fully to this proposal that RAN2 should reduce the number of bits for P-
BCH.
R1-070046 E-UTRA P-BCH Performance Evaluation (Motorola)
15/01/2007 10:20 Presented by Mr. Jean-Aicard Fabien
It was clarified that Motorola view for the response to RAN2 is we should consider to reduce the number of bits on
P-BCH.
It was decided to provide the draft answer LS in R1-070542, summarising the discussion in RAN1 (Nokia + NTT
DoCoMo contributions + others)
R1-070542 Draft Reply LS on Primary BCH Transmission (Nokia)
Decision: This draft LS was approved in R1-070606
R1-070008 LS on “Inter-Cell Interference Coordination and its signalling” (To: RAN1)

(RAN WG3, Nokia)
R1-070142 Proposed RAN1 Response to LS R3-062005=R1-070008 on "Inter-Cell
Interference Coordination and its signalling" (Siemens, Nokia)
15/01/2007 11:25 Presented by Dr. Joern Krause
Christian G. Gerlach from ALcatel-Lucent commented on the conclusion that we already decided on the ICIC that
we need to specify the UL signaling related to ICIC even though which scheme for ICIC should be specified so that
we had better capture that in the conclusion on this document. It was discussed that we need more discussion for
this topic at the moment for response to RAN3, but some companies proposed not to postpone this issue more and
should allocate the corresponding AI for much progress, on the other hand it was commented that we have much
other issues to solve for completion of stage 2 in March and also this topics is dropped in measurement topics.
Mr. Chairman proposed changing the small parts of this contribution for the current response to RAN3 without any
details and initiating the email ad hoc on this topic to make a progress on RAN1 view.
Decision: This document was revised in R1-070546 and it was decided to initiate email ad hoc on this to progress
the RAN1 view.
R1-070546 Draft Proposed RAN1 Response to LS R3-062005=R1-070008 on "Inter-Cell
Interference Coordination and its signalling" (Siemens, Nokia)
19/01/2007 14:10 Presented by Dr. Joern Krause
R1-070009 LS on SFN acronym disambiguation (To: RAN1, RAN2, RAN4)

(RAN WG3, Siemens)
15/01/2007 11:40 Presented by Dr. Przemek Czerepinski
It was commented that this acronym is used for LTE and also WCDMA. Mr. Chairman commented that we discuss
the SFN operation for MBMS on WCDMA as well so that we don't see any problem on this proposal from
technical point of view. In fact, some opposition to this proposal such like more suitable acronym or that it is more
related to RAN2 points.
Decision: This document was noted. It was decided to provide a short LS in R1-070547 confirming use of MBSFN.
6
R1-070547 DRAFT Reply LS on SFN acronym disambiguation R1-070009 (R3-062012)

(Siemens)
Decision: This draft LS was approved in R1-070607.
R1-070010 LS on LTE-MBMS Discussions in RAN3 (To: RAN1, RAN2, SA2)

(RAN WG3, Vodafone)
It was asked if Section 1.1 about what the definition of SFN is considering that if the single MBMS is included. The
answer was that it could provide the more dynamic SFN service such that it may have two services, one is that all
service is SFN services and the other is that SFN service on some cells and the other cell is not SFN but single cell
MBMS service.
Christian G. Gerlach asked about synchronization for the neighbouring cell (channel) in different bandwidth.
R1-070011 LS on Impact of Release 7 bit rate increase and MIMO on Specifications

(To: RAN1, RAN2, CT1, CT4, SA1, SA2) (RAN WG3, Nortel)
15/01/2007 12:05 Presented by Mr. Dirk Gerstenberger
Decision: This document was noted. It was decided to provide a reply LS in R1-070548 (Ericsson) indicating the
foreseen bitrate increases
R1-070548 Draft Reply LS on Impact of Release 7 bit rate increase and MIMO(Ericsson)
16/01/2007 22:00 Presented by Mr. Johan Bergman
Charlie Zhang from Motorola commented on that last point of this document that we have not approved any WI for
combination of MIMO and 64QAM so that the text should be modified appropriately.
Decision: This draft LS was approved in R1-070594 with modification.
R1-070012 Response to your November 28, 2006 request for information on IEEE 1588
(To: RAN3, Cc: RAN1, RAN2) (IEEE1588)
15/01/2007 12:10 Presented by Mr. Dirk Gerstenberger
This LS is related to the synchronization mechanism corresponding RAN3 LS at the October meeting 2006.
R1-070013 LS on introduction of radio bearers for MTCH in TS 34.108 (To:
RAN1, RAN2) (RAN WG5, Ericsson)
R1-070014 Reply LS to SA1, SA4 on Service Requirement for MBMS LTE (To: SA1, SA4,
Cc: RAN1, RAN2, RAN3) (TSG RAN, Nokia)
15/01/2007 12:15 Presented by Mr. Lars Lindh
R1-070051 Performance of MBMS Transmission Configurations (Motorola)

15/01/2007 12:20 Presented by Mr. Eoin Buckley
R1-070481 Spectral efficiency comparison of possible MBMS transmission schemes
(Ericsson)
This document was revised before the presentation.
R1-070536 Spectral efficiency comparison of possible MBMS transmission schemes
(Ericsson)
15/01/2007 12:30 Presented by Dr. Erik Dahlman
7

From Motorola, there are many comments and question to this contribution compared with their contributions
Mr. Chairman commented that we have two set of results and more discussion on the each other between the larger
difference and this is the first input so that we would check again the next meeting.
Decision: This document was noted. It was decided to provide feedback to RAN2 at the next meeting.
R1-070565 LS on CPC Long preamble (To: RAN1)

(RAN WG2, Nokia)
16/01/2007 15:20 Presented by Mr. Karri Ranta-aho
It was comment and clarification on the timing between starting the long preamble and ETFC selection (after or
before) and the problem on the DL timing and ignoring the DL commands was pointed out.
Decision: This document was noted. The related RAN1 document is R1-070184.
Proposed alternative to removing the long preamble is to delay the EDCH transmission and let the UE ignore the
DL commands received during the long preamble. So, it was decided to indicate this as an alternative to removing
the long preamble to RAN2, draft LS reply in R1-070579.
R1-070184 Preamble transmission simplification (Nokia)

This document is related to the LS from RAN2 in R1-070565
It was clarified that this issue is more tightly for 2ms but could be 10ms as well so that it's better to check RAN2
document.
R1-070579 [Draft] Reply LS on CPC Long preamble (Nokia)
Outgoing LS
R1-070578 Answer LS on status of Rel-7 FDD MIMO (To: RAN2, Cc; RAN4)
(RAN WG1)
R1-070594 Reply LS on Impact of Release 7 bit rate increase and MIMO
(To: RAN3, Cc; CT1, CT4, SA1, SA2, RAN2) (RAN WG1)
R1-070606 Reply LS on Primary BCH Transmission (To: RAN2) (RAN WG1)
R1-070607 Reply LS on SFN acronym disambiguation R1-070009 (R3-062012)
(To: RAN3) (RAN WG1)
R1-070621 Proposed RAN1 Response to LS R3-062005=R1-070008 on "Inter-Cell
Interference Coordination and its signalling" (To: RAN3) (RAN WG1)
R1-070622 LS Response to RAN2 LS on Synchronization at Handover
(To: RAN2, Cc; RAN3, RAN4) (RAN WG1)
R1-070623 Reply LS on CPC Long preamble (To: RAN2) (RAN WG1)
R1-070626 LS on F-DCH enhancement for Release-7
(To: RAN2, RAN3, RAN4) (RAN WG1)
R1-070628 LS on 7.5 kHz carrier spacing (To: RAN4) (RAN WG1)
R1-070629 LS on data-associated uplink control signalling (To: RAN2) (RAN WG1)
R1-070631 LS on Transport Block Size Signalling for 1.28Mcps TDD Enhanced Uplink
R1-070632 LS on Frequency Domain Spectrum Shaping and /2 BPSK
R1-070634 LS to RAN2 On Synchronization and Mobility with CPC
8
Withdrawn
R1-070370 LS on Synchronization at handover (Nokia)
R1-070371 Draft Reply LS on “Inter-Cell Interference Coordination and its signalling”
(Nokia)
9
5. Maintenance of R99, Rel4, Rel5, Rel6, Rel-7

R1-070070 25.224 CR0154 (Rel-6, F) "Modification on the power control function of HS-
SICH and HS-SCCH for LCR TDD" (CATT, ZTE, TD-Tech,
Spreadtrum Communication)
15/01/2007 14:35 Presented by Mrs. Xueyuan Gao from CATT
The corresponding CRs to the other WGs (RAN3 and RAN4) will submitted in February meeting.
Decision: This CR was agreed in principle and revised the cover sheet (to new version) in R1-070550.
R1-070550 25.224 CR0154r1 (Rel-6, F) "Modification on the power control function of HS-
Decision: This CR was agreed
R1-070071 25.224 CR0155 (Rel-7, A) "Modification on the power control function of HS-
R1-070551 25.224 CR0155r1 (Rel-7, A) "Modification on the power control function of
HS-SICH and HS-SCCH for LCR TDD" (CATT, ZTE, TD-Tech,
R1-070072 25.225 CR0084 (Rel-6, F) "Modification on the HS-SICH reception quality of
HS-SICH for LCR TDD" (CATT, ZTE, TD-Tech, Spreadtrum
Communication)
R1-070552 25.225 CR0084r1 (Rel-6, F) "Modification on the HS-SICH reception quality of
Communication)
R1-070073 25.225 CR0085 (Rel-7, A) "Modification on the HS-SICH reception quality of
Communication)
R1-070553 25.225 CR0085r1 (Rel-7, A) "Modification on the HS-SICH reception quality of
Communication)
19/01/2007 09:xx Presented by Mrs. Xueyuan Gao from CATT
R1-070074 25.224 CR0156 (Rel-5, F) "Clarification of Closed Loop Uplink HS-SICH
Power Control for 1.28 Mcps TDD" (ZTE)
15/01/2007 14:45 Presented by Mr. Zhifeng Ma
10

From Mr. Chairman it was asked what was the wrong ins the Rel-5 and commented that Informative is not the
mandatory specification for implementation and the informative is not to need too much. Nicholas Anderson
commented that they don't have any problem for Rel-6 and onward with more clarification on the cover sheet
Decision: This CR was not agreed.
R1-070075 25.224 CR0157 (Rel-6, A) "Clarification of Closed Loop Uplink HS-SICH
Decision: This CR was revised in R1-070554 (category F)
R1-070554 25.224 CR0157r1 (Rel-6, F) "Clarification of Closed Loop Uplink HS-SICH
Decision: This CR was revised in R1-070624 again to indicate on the cover sheet that the NodeB implementation is
not mandated and that the consequence if not approved is “none”. Email approval until Friday next week, 26th
January.
R1-070624 25.224 CR0157r2 (Rel-6, F) "Clarification of Closed Loop Uplink HS-SICH
Decision: This CR was agreed on the e-mail reflector after the meeting.
R1-070076 25.224 CR0158 (Rel-7, A) "Clarification of Closed Loop Uplink HS-SICH
Decision: This CR was revised in R1-070555 (category C)
R1-070555 25.224 CR0158r1 (Rel-7, A) "Clarification of Closed Loop Uplink HS-SICH
Decision: This CR was revised in R1-070625 again to indicate on the cover sheet that the nodeB implementation is
not mandated and that the consequence if not approved is “none”. Email approval until Friday next week, 26th
January.
R1-070625 25.224 CR0158r2 (Rel-7, A) "Clarification of Closed Loop Uplink HS-SICH
Decision: This CR was agreed on the e-mail reflector after the meeting.
R1-070177 Computation of E-DPDCH gain factors (Nokia)

Rainer Bachl (Alcatel-Lucent) commented that they agree in principle but still wonder on changing the
specification. They already investigated this point on the their submitted document in 2005 and it was pointed that
it was difficult to make a decision on one optimum gain factor because the gain factor is depending on the many
parameter and conditions. Some companies raised a concern on the changing the specification for Rel.6 even
though this point is very valuable for discussion on Rel-7 such as 16QAM for uplink.
Mr. Chairman commented that from the all comments we don's change in Rel-6 and focus on the discussion on Rel-
7 for 16 QAM.
Juho Lee (Samsung) proposed that we would have some time and more discussion to take a decision on way
forward for this issue because we don't have much time on it.
Decision: This document was noted and it was suggested that companies are invited to investigate this for Rel-7
until the next meeting.
R1-070178 System results for reduced E-DPCCH overhead (Nokia)
R1-070419 System analysis and further details of proposed new coding for E-DPCCH
(Qualcomm Europe)
11
R1-070545 System analysis and further details of proposed new coding for E-DPCCH
(Qualcomm Europe)
15/01/2007 15:20 Presented by Mr. Juan Montojo
Rainer commented that we had a quite similar result on the other optimization 2005 so that we would consider that.
Karri Ranta-aho (Nokia) commented that two main aspects on this is one is data rate, i.e. VoIP and data services
and the other is how many number of set we would support.
Ericsson and Motorola expressed a little anxiety on the simulation assumption and results from Nokia and
Qualcomm.
Mr. Chairman commented that at last meeting we already discussed this topic for RAN4 LS and had much time on
line but there are still some doubts on this. We don't want to have any more time so that we continue to discuss
offline during this week and then if no agreement on it this change would not be decided.
R1-070420 25.211CR0233 (Rel-7, C) "New coding for E-DPCCH" (Qualcomm Europe)
Decision: No agreement at this point and continue discussion offline and come back to Friday. Proposal was
withdrawn.
R1-070416 UL system analysis with proposed new F-DPCH (Qualcomm Europe)
There were comments and questions for timing for DL and UL
Karri Ranta-aho (Nokia) expressed a wondering on the assumption on the delay that all UE delay one slot or two
slot although we could consider the other assumption. It was commented by Qualcomm that in fact in this
contribution all user is one slot delayed or two slots delayed but we were showing the worst case at last and it
provided the good results
R1-070417 25.211CR0232 (Rel-7, C) "Enhanced F-DPCH" (Qualcomm Europe)
Decision: This CR was revised in R1-070558 with inclusion of the relation to the other WGs specification on the
cover sheet.
R1-070558 25.211CR0232r1 (Rel-7, C) "Enhacned F-DPCH"(Qualcomm Europe)
19/01/2007 14:25 Presented by Mr. Serge Willenegger
Matthew Baker from Philips proposed more time to check wording so that this CR was agreed in principle.
Decision: This CR was agreed in principle.
R1-070418 25.214CR0433 (Rel-7, C) "Enhanced F-DPCH" (Qualcomm Europe)
Karri Ranta-aho (Nokia) pointed out a few editorial errors
Joern Krause from Siemens asked if two F-DPCH is covered by UE capability and pointed out we should keep
consistency to Rel-6. It was answered that it's configurable by higher layer signalling and we already analyzed that
the proposal is Rle-6 compatible.
Sarah Boumendil commented on the way forward for these CRs that we need to consider the impact on various
RAN specifications, especially for RAN4 performance requirement we expect some impact so that we should check
these impact before agreement of RAN1 CRs. Juan Montojo (Qualcomm) commented that they already have
analyzed the impact and it could be minimized and RAN4 so that we cannot see any serious impact as we already
see system level performance.
Mr. Chairman asked if we can agree in principle or not. Sarah Boumendil strongly showed an objection considering
that We are missing on global impact on RAN. To this objection, Mr. Chairman showed his opinion that in fact
such kind of argument is not directly to this proposal and this is not RAN1 way but the other WGs way forwards.
Karri Ranta-aho raised a concern that we already have Rel-6 for F-DPCH and then now rework in the next Rel-7.
Johan Bergman commented that from system design there could be issue such situation such as Rel-6 and Rel-7 and
impact on RAN4.
Mr. Chairman RAN4 normally come later to CR and considering the RAN4 meeting schedule, if we send th eLS to
RAN4 the response from RAN4 will be October or December so that we need to wait but from our perspective we
revise CR so that it could be done.
12
Finally Mr. Chairman commented that I don't have any fundamental problem so that he proposed to revise the CR
(CR would be agreed in our side) and send LS to the other WGs.
Decision: This CR was revised in R1-070559 according to the discussion and it was decided to prepare LS to
RAN2, 3 and 4 to inform them that RAN1 would like to introduce this and ask them to do their part in R1-060560.
R1-070559 25.214CR0433r1 (Rel-7, C) "Enhaced F-DPCH" (Qualcomm Europe)
Matthew Baker from Philips proposed more time to check wording so that this CR was agreed in principle.
Decision: This CR was agreed in principle.
R1-070560 Draft LS on F-DCH enhancement for Release-7 (Qualcomm Europe)

Jean-Aicard Fabien from Motorola Karri Ranta-aho from Nokia raised a little concern on SH issue so that would
come back again. Mr. Chairman suggested coming back to February meeting.
Decision: This draft LS was agreed in R1-070626 with attachments.
R1-070540 Impact of F-DPCH timing restrictions due to SHO (Ericsson)

Decision: This document was noted without presentation.
13
6. Evolved UTRA and UTRAN

The overview of conclusions and agreements on this topic is as followed.
1. Updated Physical Layer Specifications

- The endorsed latest version: TS36.211 v.0.3.0 (R1-070627), 36.212 v.0.3.0 (R1-070562), 36.213 v.0.2.0
(R1-070563)
2. Numerology
- It was agreed that DFT sizes are multiples of 2, 3 and 5.
- It was agreed as way forward that current RAN1 focus regarding 7.5 kHz is carriers only carrying
MBMS (more exactly MCH with MBSFN). This does not rule out future extensions to other cases.
RAN1 should inform RAN4 about this decision (LS to RAN4 in R1-070628)
- It was agreed that Only TDM on subframe basis of data transmission (control channels need to be
discussed more) on MBSFN and non-MBSFN is supported. How this relates to different MBSFN areas
is FFS.
- As for half duplex FDD operation, the way forward was endorsed in R1-070533.
- As UE minimum transmission bandwidth, it was agree as way forward that Design of control channels
in absence of scheduling of user data can assume 20MHz. Decide at next meeting whether the minimum
UE Tx bandwidth is 20MHz.
- As for idle period position for E-UTRA TDD, it was agreed to reserve the idle symbol(s) for idle period
from the downlink subframe end before the DL-to-UL switch point. Idle symbols in the uplink are not
precluded
3. Modulation
- UE specific UL scrambling is supported by the specification and can be configured to be used or not to
be used.
- As for Frequency Domain Spectrum Shaping (FDSS), LS to RAN4 on expected improvement with
proposed FDSS functions, and on general issue of Tx power boosting beyond 24dBm was sent in R1-
070632.
4. Channel coding
- RAN1 selects QPP and will base the further work on this.
5. Basic Access Procedures
- RACH and random access procedure: The followings were agreed as working assumption.
o It was agreed as working assumption that for early L2 contention resolution, NACK- collision
(to indicate collision in the preamble) is not supported
o Non contention based scheduling request mechanism for synchronized users. Providing
contention based scheduling request (Non sync random access) is RAN2 decision
o Maintain 0.8 msec preamble with restricted set of cyclic shifts for cell supporting high mobility
UE
- SCH and cell search procedure: The followings were agreed as working assumption
o RAN1 confirms that Approach 1 is working assumption.
o Multiple P-SCH (number of P-SCH sequences is 3)
o Number of Hypotheses at stage 2: detect 1 out of 170 cell ID groups, frame timing detection in
stage 2. Number of Hypotheses at stage 3: detect 1 out of 3 cells from the cell ID groups
selected in stage 2
o Rest number of Hypotheses dependent upon P-BCH transmit scheme (TBD) whether it will be
detected in stage 1, 2 or stage 3
o Location of P-SCH and S-SCH as Figure 2 of R1-062990, located in last 2 OFDM symbols of
slot.
6. References signal structure
- Downlink RS
14
o Regarding RS Frequency Hopping for E-MBMS or BCH sub-frames, it was agreed that RS
from the multiple Node Bs always occupy the same sub-carriers during MBMS sub-frames.
o Agreed way forward for DL RS frequency hopping
- Shifting is a sub-set of hopping patterns
- Hop-pattern/shift tied to cell group ID
 Pattern known in step #2 , 170 hop ”patterns”
 Hopping period equal on one 10 ms frame (i.e. length of the hopping
sequence is 10ms)
- All subframes of cell/carrier are either hopping or not hopping
 [In practice implies carriers with MCH/MBSFN subframes do not hop]
- To find out if hopping or not hopping is used
 Indicated from S-SCH (step 2)
 or detected from step 3 (twice as many hypothesis)
 TBD at next meeting
- Uplink RS
o Agreement on Long RS was endorsed
0.5 ms slot structure:
 Adopt LB RS (RS in the 4th LB of the slot – Figure 1).
 Have as working assumption that no additional (UE speed adaptive) RS is inserted for
high speed UEs. This is based on current evidence that it does not adversely impact
the fulfillment of EUTRA requirements; however it can be re-assessed if evidence to
the contrary is demonstrated.
The 0.675 ms slot structure can be treated separately.
If SB RS is maintained for the 0.675 slot structure, it was noted that a possibility to increase
the number of ZC sequences is to set the minimum data allocation equal to 2 RBs.
o RS sequence length is equal to the number of sub-carriers in the resource blocks, either
truncation or cyclic extension of ZC sequences are used, depending on the RB allocation size.
Problems with the working assumption related to cross-correlation should be raised during the
e-mail discussion.
7. Downlink MIMO, Tx. Diversity and Beamforming
- Precoding on TDD
o Agreed on that codebook based precoding will be supported for TDD as well.
o Continue discussion on whether non-codebook based pre-coding shall be supported for TDD and
if so, how.
- Mapping codewords to layers
o DL signaling supports for Node B’s overriding the rank reported from the UE (working
assumption)
o Full flexibility for mapping between HARQ process ID and CW (working assumption)
o Fixed mapping between CWs to layers (working assumption)
 Rank1: CW1 to 1st layer (working assumption)
 Rank2: CW1 to 1st layer, CW2 to 2nd layer (working assumption)
 Rank3: CW1 to 1st layer, CW2 to 2nd and 3rd layers (working assumption)
 Rank4:
 Working assumption: CW1 to 1st and 2nd layers, CW2 to 3rd and 4th layers
 Working assumption may be revisited in R1#48 meeting regarding the issues
identified below
 FFS: CW1 to 1st layer, CW2 to 2nd, 3rd, 4th layers
o Issues identified (check the situation in the next meeting)
 Performance difference between 2+2 and 1+3
15
 Diversity aspect 2+2 vs 1+3 regarding CQI imperfection

under practical conditions
 Implication of Node B overriding the rank reported from the
UE on CQI mismatch.
 System operation scenario and UE implementation
complexity
- Precoding codebook construction (focusing on optimizing SU-MIMO)
o Working assumption: Rank non-specific precoding codebook
 For a given codebook, predefine (i.e. no dynamic update) a set of M precoding matrices
of 2x2 for 2tx antenna, where 2x2 identity matrix may be configured by the network to
be included in the set.
 For a given codebook, predefine (i.e. no dynamic update) a set of N precoding matrices
of 4x4 for 4tx antenna, where 4x4 identity matrix may be configured by the network to
be included in the set.
 Rank adaptation by selecting a non-square precoding matrix that is a part of a square
precoding matrix.
o FFS:
 Performance benefit of less restrictive approaches
 The working assumption may be revisited in R1#48 meeting if needed.
 Can UE assume that Node B should use the precoding matrix reported by the UE?
 Further limitation on the codebook (including the associated signalling scheme)
 UE capability
 Node B’s expectation on the usage of the codebook
- UE feedback
o Frequency granularity
 Precoding feedback information
 Working assumption: one per 2/5/10/whole RBs (configured by the network)
 FFS: single report over the selected best RBs
 Working assumption may be revisited in R1#48 meeting if needed.
 Rank feedback information
 Working assumption: single report over the whole bandwidth (pending the
results for the >5MHz system BW)
 FFS: same as the precoding (configured by the network) (there may be a
mechanism for reducing the overhead when combined with the precoding
feedback information)
 Working assumption may be revisited in R1#48 meeting if needed.
o Time granularity
 Working assumption: configured by the network (similar to CQI in HSDPA)
- MU-MIMO
o Semi-static configuration of SU-MIMO or MU-MIMO per a UE
o Only one layer (in another word, only transmission rank of one) is allocated to a UE configured to
be in MU-MIMO transmission
8. Uplink MIMO and Tx. Diversity
- SU-MIMO: SU-MIMO should be addressed in a future release.
o The first release should at least be such that it should not preclude introducing uplink SU-MIMO
at a later stage
o Signaling support to be defined later (legacy LTE UEs should not be affected)
o Discussion on the support of 64QAM to be continued until the next meeting.
- Tx Diversity
16
o Not specify the blind antenna switching/hopping in the standard. Note: Adaptive antenna
selection should be discussed as a part of scheduling of the spatial resource (if needed), and hence
the related contributions are recommended to be under UL MIMO AI.
9. Control Signalling
- Downlink signalling
o The bandwidth of the downlink control channel is equal to the system bandwidth (i.e., the
bandwidth over which the reference signals can be transmitted in a cell)
- Uplink signalling
o Data-non-associated UL control signalling
- Transmission of ACK/NAK and CQI spans 1ms
- To handle coverage-limited situations, it should be possible to use the full 1 ms
subframe for control signalling before starting to repeat control signalling in multiple
1ms subframes, if only one type of control signalling is to be transmitted in the
subframe. This applies to ACK/NAK and/or CQI
- Different UEs can be allocated on different frequency resources (FDM). Code-domain
multiple-access between UEs simultaneously transmitting control signaling (ACK/NAK
and/or CQI) on the same frequency resource.
 Each frequency resource is a multiple of 12 subcarriers (consisting of an upper
and/or a lower part with the slots of one subframe, upper and lower part are of
equal size if both upper and lower part are present). CDM would be used within
the upper and the lower part, respectively
- The structure Data-non-associated UL control signalling was endorsed in R1-070602
o No data-associated uplink control signaling is used.
- RAN1 assumption is that Node B is not required to perform blind transport format
detection.
- Send an LS to RAN2 (R1-070629) to inform about this, and ask how VoIP will operate
from their view.
10. UL Timing Control
- The current status of TA discussion in RAN1 was listed and it was suggested to continue discussion on the
e-mail reflector based on the listed status.
11. UL/DL Power Control
- It was agreed that
o Basic power control mechanism: Slow power control (not faster than 200Hz, with a-periodic PCD
updates (FFS whether a-periodic PSD updates will be agreed) the power control rate may
temporarily be higher than 200Hz)
o PSD is controlled
o Pure open loop UL power control only (i.e., without adjustments made by the network) is not
sufficient
- Further issues were listed for further discussion.
6.1 Updated Physical Layer Specifications

R1-070525 TS 36.211 v 0.2.2 (Editor; Ericsson, NTT DoCoMo)
15/01/2007 17:20 Presented by Dr. Stefan Parkvall
Motorola commented on the large cell size (E-MBMS) issue that we consider that considering the output from
RAN#34 we need clarify this point and they clarified that 7.5 KHz is for dedicated only case although someone
said it is also applicable for the mixed unicast and multicast case. Mr. Chairman clarified about MBMS issue that in
fact there was no decision from the last RAN and this updated version should capture only the decision and output
from the last RAN1 meeting but should not include the others
Regarding scrambling, Farooq Khan from Samsung asked if some specific scrambling is used in two box in Figure
3 and these are the same or different. Also he expressed a wonder on the UL scrambling that at the last meeting we
agreed that we specified scrambling if it's beneficial but not more ant analysis so far so that we should not capture it
in specification if we are not capturing the issue raised on UL modulation, i.e. spectrum shaping.
Stefan Parkvall from Ericsson commented that as for the question for Fig 3 the scrambling is not decided yet to be
the same or different for two box and it's depending on MIMO topics.
17
In addition, some concerns were raised on the texts for spectrum shaping and scrambling capturing or not.
To these concerns that, Mr. Chairman clarified that this version captured only decision on the last meeting and in
fact we need to make a sure the spectrum shaping and scrambling issue raised so far during this meeting and the
output would be captured for the next meeting. It should be updated step by step.
Farooq commented on the text for UL scrambling that "shall be" means that it is always used (mandatory) so that it
should be changed in line to RAN1 working assumption (not mandatory)
Decision: This version was revised in R1-070561.
Decision: This version was endorsed as version 0.3.0 in R1-070627
R1-070422 TS 36.212 v0.2.2 (Editor; Qualcomm Europe)

Mr. Chairman commented that FFS should be removed and we capture just whether agree or not. Juan Montojo
commented that it could be helpful for the future discussion.
Decision: This version was endorsed as version 0.3.0 in R1-070562.
R1-070562 TS 36.212 v0.3.0 (Editor; Qualcomm Europe)
R1-070194 TS 36.213 v0.1.1 (Editor; Motorola)

15/01/2007 18:15 Presented by Mr. Robert Love
Decision: This version was endorsed as version 0.2.0 in R1-070563.
R1-070563 TS 36.213 v0.2.0 (Editor; Motorola)
6.2 Remaining issues on numerology

Minimum DFT size
R1-070037 DFT Restrictions and impact on UL System Performance (Motorola)
18/01/2007 09:20 Presented by Mr. Ravi Nory
R1-070067 The effect of FFT size restrictions on the system performance of uplink SC-
FDMA (Freescale Semiconductor)
18/01/2007 09:25 Presented by Dr. Wes McCoy
It was asked how your view for 20MHz system BW is because the combination of RB is related to BW. It was
answered that it's the same view for 5MHz.
R1-070355 Capacity Impact of DFT size restriction (NEC Group, NTT DoCoMo)
18/01/2007 09:30 Presented by Mr. Yoshikazu Kakura
R1-070423 Subset of allowed DFT sizes for UL (Qualcomm Europe)
Przemek Czerepinski from Siemens commented that although the simulation results from the other companies are
based on full buffer, no-full buffer case should be taken into account as well.
R1-070461 DFT size for uplink transmissions (Ericsson)
18
Juan Montojo from Qualcomm clarified their position that they don't have any strong opinion but we should take
into account of 20MHz BW case. Considering Ericsson paper, they support to 2, 3, and 5.
Conclusion:
DFT sizes are multiples of 2, 3 and 5.
MBMS long CP for shared carrier

R1-070050 CP Length for Unicast-MBMS-mixed Mode (Motorola, Nokia)
18/01/2007 09:50 Presented by Mr. Eoin Buckley from Motorola
It was commented by Motorola on impact on the cell search, blind detection is much complicated. There are some
discussions related to the decision at Riga meeting. Przemek Czerepinski from Siemens commented that in their
understanding there was no limitation in that decision, however they support just dedicated service. Robert Love
from Motorola supported to this and commented that as shown in their contribution, there are many issue on shared
services so we proposed only dedicated service.
R1-070052 Deployment Scenarios for MBMS (Motorola)
18/01/2007 10:05 Presented by Mr. Eoin Buckley
It was discussed whether new scenario means no support for unicast in 5km cell size.
Mr. Chairman commented that we don't want such a restricted simulation scenario for long cell and it seems to be
strange approach, even though indeed we should support the unicast for 5, 10 and 20 km as shown in LTE
requirement. Erik Dahlman form Ericsson commented that if we want to take such a scenario, we also take more
scenario based on LTE requirement and it's quite much. Mr. Chairman also commented that such a scenario might
be taken in RAN4, however it causes the delay of discussion.
Brian Classon from Motorola commented that although the evaluation scenario already fixed, the additional
evaluation such shown in this document is useful for further discussion so that they propose not to stop such
evaluations on additional scenario. Mr. Chairman confirmed that.
R1-070204 Observation on MBMS extended physical Layer Parameter for Shared Carrier
Mode on 2Ghz Carrier Frequency (ZTE)
18/01/2007 10:20 Presented by Mr. Zhisong Zuo
Nortel, IPWireless and Motorola raised concerns on the deployment scenario of small cell radius and 43dbm
transmit power.
R1-070357 Issue of dynamic CP length change in a cell with mixed unicast and MBMS
transmission (NEC Group)
18/01/2007 11:20
R1-070456 Benefits of 7.5 kHz Numerology with 43dBm Transmit Power
(Nortel, Orange, CMCC)
18/01/2007 11:30 Presented by Mr. Julius Robson
R1-070424 Longer CP for MBMS (Qualcomm Europe)
Decision: This document was noted without presentation
R1-070609 Way forward on 7.5kHz (Ericsson)
Nortel supported. IPW supported but ?
Decision: This document was agreed. This decision is informed to RAN4 Draft LS in R1-070610.
Agreed way forward
19
Current RAN1 focus regarding 7.5 kHz is carriers only carrying MBMS (more exactly MCH with
MBSFN). This does not rule out future extensions to other cases. RAN1 should inform RAN4
about this decision.
R1-070610 [draft] LS on 7.5 kHz carrier spacing (Ericsson)

R1-070373 Need for Frequency Multiplexing of MBMS (Nokia, Motorola)

This document was revised before the presentation
R1-070603 Need for Frequency Multiplexing of MBMS (Nokia, Motorola)
18/01/2007 11:45 Presented by Mr. Lars Lindh
Farooq Kahn from Samsung object to "no motivation in RAN1" and commented that in 2005 they submitted
document on this issue and showed the motivation for FDM. Some discussion were the UE complexity and impact
by FDM and TDM for 20MHz UE
R1-070528 Performance of Frequency Multiplexing for Broadcast and Unicast
(Samsung)
15/01/2007 12:05 Presented by Dr. Farooq Khan
It was clarified that this analysis is more for large cell than small cell.
Motorola raised a concern from MCE point of view.
Asbjörn Grovlen from Nokia raised a concern on the power allocation on this proposal from reliability point view.
Farooq Kahn clarified that their view is not the dynamic power allocation for unicast and multicast but static power
allocation.
Erik Dahlman from Ericsson commented that he would like clarify that this discussion is multiplex of MCH and
DL-SCH and it was confirmed among the interested party.
Lars Lindh from Nokia pointed out that Samsung proposal does not consider any interference from MBMS to
unicast, however, Farooq raised a concern that they don't see any such a interference in their view.
Thomas Sälzer from Orange express a wonder on FDM approach from a viewpoint of dimensioning power,
coverrage and so on, and they supported TDM approach,
Farooq Khan commented that they agree to 20MHz UE capability view point, but also the other capability such as
data rate capability would be taken into account
Asbjörn Grovlen from Nokia raised a concern that from the viewpoint of MBMS data rate and unicat data rate
supported by UE they don't see any difference between TDM and FDM.
Erik Dahlman expressed their view that they don't allow to multiplex DL-SCH and MCH in the same subframe.
It was pointed out how we treat in case for the different MBSFN area.
Joon Kui Ahn from LGE asked if this conclusion is considered for control channel. It was confirmed that it is just
for data.
Discussion: Two alternatives

- Prohibit MBMS FDM (with respect to MCH transmitted via MBSFN)
o Multiple MCH can be multiplexed with a MBSFN subframe
- Allow MBMS TDM/FDM (with respect to MCH transmitted via MBSFN)
Conclusion:
Only TDM on subframe basis of data transmission (control channels need to be discussed more) on
MBSFN and non-MBSFN is supported. How this relates to different MBSFN areas is FFS
R1-070306 Uplink Extended Cyclic Prefix Use Cases (Siemens)

18/01/2007 12:40 Presented by Mr. Mieszko Chmiel
20

The last sentence in the third bullet in conclusion means such a measurement does not need to be specified.
The concern was raised that the rapid change such a using control channel would be challenging. Mieszko clarified
that they don't assume dynamic but such like semi-static changes and L3 signalling should be sufficient as well.
Some people pointed out some impact on scheduling related to RAN area.
It was proposed by Mr. Chairman as conclusion that "L3 signalling can control the CP for different UEs within
a cell, i.e. usage of different CP for different uses within a cell is not precluded. This is applicable to the UL
and to the DL CP.", some people still raised concerns. Joon Kui Ahn from LGE expressed his concern for the
complex issue even though semi-static. Juan Montojo from Qualcomm commented we don't take a UE based but
just subframe based. It was discussed whether we take a RAN1 decision now and send LS to RAN2 or discuss
again from scratch with RAN2, but no concreted way forward there was. So, finally, in conclusion, this document
and this proposal were just noted.
Not treated due to lack of time

R1-070569 E-MBMS performance in repeaters (Motorola)
Duplex operation
R1-070480 Duplex operation (Ericsson)
It was discussed on the relation of UE/frequency band for half-duplex and full-duplex. One question was that full
duplex service is in certain band and the half duplex service is in the other certain band.
Erik Dahlman explained their view that they can not say exclusive or not but NW don't need to know UE capability
but UE should know network capability (service) and by this operation we can expect the benefit of power
consumption and UE complexity issue.
Tim Frost from Vodafone pointed out the impact on RAN4 area such coverage so that we should consider what the
impact on RAN4 specification.
R1-070533 Half duplex FDD (Vodafone)
Erik Dahlman from Ericsson commented that they don't think a physical specific structure but more related to
higher layer on this topic. It was asked if there any time period between UL/DL such like switching point. Erik
answered that it may be needed like normal TDD.
Serge Willengger from Qualcomm commented that as the approach for investigating a half-duplex at first stage the
requirement is necessary to investigate at the next stage and make sure how and what we consider.
Decision: The proposed way forward was endorsed.
UE Tx bandwidth
R1-070336 On UE tx bandwidth (Samsung)
18/01/2007 15:10 Presented by Dr. Joonyoung Cho
Stefan Parkvall from Ericsson commented that as shown in their proposal, R1-070473 they support this proposal,
UE Tx minimum bandwidth is 20MHz.TI also expressed their supporting.
Juan Montojo from Qualcomm commented that they could not fully understand Samsung and Ericsson view.
The main point proposed in Samsung paper could be considered as implementation issue and we can do that by
analogue and digital tuner filter. Also it was pointed out the issue related to control channels.
R1-070604 UE minimum transmission bandwidth (Motorola, Nokia)
18/01/2007 09:xx Presented by Mr. Robert Love from Motorola
R1-070473 Uplink control signaling and 10 MHz UE transmission capability (Ericsson)
After the offline discussion, the following way forward was proposed and agreed.
21
Agreed way forward

Design of control channels in absence of scheduling of user data can assume 20MHz. Decide at
next meeting whether the minimum UE Tx bandwidth is 20MHz
R1-070372 Idle Period position for E-UTRA TDD with Generic frame structure
(Nokia)
18/01/2007 16:30 Presented by Mr. Xiangguang Che
Conclusion:
It is proposed to reserve the idle symbol(s) for idle period from the downlink subframe end
before the DL-to-UL switch point. Idle symbols in the uplink are not precluded.

R1-070444 E-MBMS inter-resource block combining (Alcatel-lucent)
R1-070203 Multiple Continuous RB Allocation Frequency Hopping in E-UTRAN Uplink
(ZTE)
R1-070224 Uplink Frequency Hopping (LG Electronics)
R1-070337 UL LFDMA with hopping (Samsung)
R1-070084 Comparison Between RB-level and Sub-carrier-level Distributed Transmission
for Shared Data Channel in E-UTRA Downlink (NTT DoCoMo,
Fujitsu, KDDI, Mitsubishi Electric, NEC, Nokia, Panasonic, Sharp, Toshiba
Corporation)
R1-070114 Description and numerology of the Physical Downlink Shared Channel
(Huawei)
R1-070338 Performance of DL distributed transmission (Samsung)
R1-070344 Resource-Block mapping of Distributed Transmissions in E-UTRA downlink
(Philips)
R1-070356 Downlink Distributed Resource Block Mapping
(NEC Group, NTT DoCoMo)
R1-070161 E-UTRA DL Distributed Multiplexing and Mapping Rules (Motorola)
R1-070310 DL Multiplexing of Localized and Distributed Resource Blocks (Siemens)
6.3 Modulation
UL scrambling
R1-070127 Performance of UE-specific scrambling for E-UTRA uplink (Samsung)
18/01/2007 16:40 Presented by Dr. Jiann-An Tsai
Stefan Parkvall from Ericsson raised a concern that Samsung scenario (scenario B) is a special case not a typical
case and they could not agree to Samsung proposal.
Farooq Khan from Samsung explained their view that yes it's not typical scenario but in a special case scrambling is
not beneficial so that we can not agree to specify scrambling if it is not beneficial in any cases.
R1-070249 On the consideration of the uplink UE-specific bit-level scrambling
(LG Electronics)
18/01/2007 16:50
Modulation level combining, theyagreed to considering the interfarecen onsidereing .
22
Farooq Khan from Samsung proposed to add the text "symbol level is not precluded". Stefan Parkvall commented
that it's related to HARQ and rate-matching and it's is premature so that that text is not captured in minutes at the
moment. Also Asbjörn Grovlen from Nokia supported his view. Mr. Chairman commented that of course the detail
scrambling should be considered but just scrambling is enough for the stage 2 level decision.
Conclusion:
UE specific UL scrambling is supported by the specification and can be configured to be used or not to
be used.
DFSS
R1-070047 UE Power De-rating Reduction Techniques in LTE (Motorola)
R1-070048 Frequency Domain Spectral Shaping for LTE (Motorola)
R1-070564 Frequency Domain Spectral Shaping for LTE (Motorola)
R1-070605 Way forward for spectrum shaping for LTE
(Motorola, Nokia, Freescale Semiconductor)
18/01/2007 17:25 Presented by Mr. Robert Love from Motorola
The understanding for Riga decision was discussed. Robert Love commented that different companies has different
view on that decision so that the final decision should be based on the document during this week, not based on
Riga decision.
Oskar Mauritz from Huawei commented that if not achieve 24dBm, the spectrum shaping way is very simple.
R1-070374 On the Feasibility of Higher UE Maximum Output Power (Nokia)
R1-070375 Coverage analysis of UL Spectrum Shaping (Nokia)
18/01/2007 17:xx Presented by Mr. Jari Lindholm
It was clarified by Nokia that 2 RB is assumed for all cases.
Noriyuki Fukui from Mitsubishi asked if the impact on power amplifier in case of R=0 is considered or evaluated.
The answer is that not consider and just CM point of view, but they think that we can power boosting.
R1-070208 Simulation results of Pout, ACLR, PAE and Power consumption vs. various
roll-off factor in LTE Uplink (Mitsubishi Electric)
18/01/2007 17:50 Presented by Mr. Noriyuki Fukui
Robert Love from Motorola commented that as for PA Rel-5 is larger than R99 so that why R99 is chosen for
comparison. The answer was that no reason just the data for R99 there was.
R1-070068 Frequency Domain Spectral Shaping and Power Amplifier Optimization

(Freescale Semiconductor)
18/01/2007 17:55 Presented by Dr. Wes McCoy
R1-070115 Spectrum-shaping function for E-UTRA uplink (Huawei)
18/01/2007 18:15 Presented by Dr. Oskar Mauritz
23
Robert Love (Motorola) commented that there are tow function on this proposal, each for each modulation and to if
only Kaiser is taken to be inline to the assumption in Riga, it could not fulfil the assumption in Riga.
Long discussion there was.
R1-070126 Spectrum shaping function for E-UTRA uplink (Samsung)

R1-070556 Spectrum shaping function for E-UTRA uplink (Samsung)
18/01/2007 18:30 Presented by Dr. Jiann-An Tsai
The long discussion continued among different parties who have different view.
After the presentation and discussion, Mr. Chairman summarised the proposed alternatives and also questions for
further discussion as followed.
Questions:
- Does the E-Node B need to know the UE transmitted power?
- How else identify a power limited MCS?
- Does the E-Node B need to know the shaping function used?
- Is power boosting above 24dBm needed to make windowing efficient?
-
It was decided to send an LS to RAN4 on expected improvement with proposed FDSS functions, and on
general issue of Tx power boosting beyond 24dBm in R1-070614. (Nokia)
Discussion on summarizing
Farooq Khan (Samsung) commented with concern that rectangular function should not included as one of the
candidates because the assumption agreed at Riga means that we select one candidates expect for rectangular (the
rectangular already agreed to be considered.
Branislav Popovic (Huawei) express a wonder that the first alternative is not exact their proposal and we should not
discuss the understanding of the agreed assumption in Riga, but discuss the spectrum function which provides the
benefit the most. In fact, almost companies agreed that both of two functions (Kaiser and RRC) provide
improvement so that they could not understand why we choose one function.
Wes McCoy from Freescale commented that it is according to narrow view, just CM, but from the view point of
overview including practical view, there is no benefit as shown in Motorola paper.
Mr. Chairman commented with wonder from personal impression that how we know what is true and what is not
true. Some way forward were discussed, such as considering RAN4 view, RAN level decision but he commented
that it's better way forward to leave a decision and send an LS to RAN4. Regarding the content of LS, Huawei and
Samsung proposed to include details but Mr. Chairman and the other companies thought with consensus that
keeping simple is better
R1-070614 LS on Frequency Domain Spectrum Shaping and /2 BPSK (Nokia)

Decision: This draft LS was approved in R1-070632.
6.4 Channel coding

R1-070411 Summary of the E-mail discussion on existing interleaver (NTT DoCoMo)
15/01/2007 18:20 Presented by Dr. Sadayuki Abeta
R1-070412 Summary of the E-mail discussion on channel coding (NTT DoCoMo)
24
It was clarified that all proponents except for QC (France telecomm) provided the simulation results. Thomas
Sälzer clarified that the proposal from France telecom, QC would be withdrawn to be a candidate for new CF
interleaver.
For starting the discussion on each contribution, way forward for discussion in this meeting was addressed.
Mr. Chairman suggested focusing on looking at the performance for the different proposals based on the working
assumption agreed at the last meeting.
Juho Lee commented that we should take also complexity issue for LTE and also HSPA (HSPA+) implementation
perspective as discussed on e-mail reflector. To this proposal, Mr. Chairman clarified again that we have already
agreed that we need the CF interleaver so that concentrate on discussing the performance technically of the several
CF interleaver.
Juho agreed to Chairman's clarification that we should focus on the performance for CF but also the complexity
issue could be included in such a discussion. In addition, he commented that HSPA+ issue including MIMO and
64QAM we can support the higher data rate so that we need the implementation of the extension of Rel6 TC
interleaver. Nortel also support to such a view and raised a concern on the summary from the e-mail discussion and
they proposed to agree the summary or not.
Samsung and Nortel commented that the existing TC interleaver could be considered as one of new CF interleaver
as some companies showed in their contributions so far.
Again for clarification, Mr. Chairman commented that as shown in summary from the email discussion we could
not reach any agreement on the CF property for the existing TC interleaver until this meeting, meaning the existing
TC interleaver could not be considered as one of the new CF interleaver according to the working assumption
agreed at the last meeting. Also in order to clarify more, Mr. Chairman asked the delegates in the meeting to agree
that the existing interleaver has CF property. Motorola, Ericsson, Nokia and Qualcomm expressed their objection to
this.
Samsung requested to ask which companies support inclusion of Rel6 TC interleaver as one of candidates for LTE
interleaver for further discussion and minutes the list of those companies, which was however not accepted by the
Chairman as he thinks it seems clear that there is no consensus on the Rel6 interleaver.
So finally, Mr. Chairman proposed that we are not going back to last a half year and would start the technical
discussion on the performance of several new CF interleavers.
LTE Turbo coding interleaver

R1-070060 QPP Interleaver Design for LTE (Motorola)
15/01/2007 19:20 Presented by Mr. Brian Classon
It was clarified that the discussion of parallerization is R1-070054.
Brian Classon from Motorola strongly clarified that QPP is CF even though Samsung raised a concern that it's the
contention free implementation.
Samsung pointed out on R1-070463
R1-070463 Contention-Free Interleavers vs Contention-Avoidance Decoding solutions
(Ericsson)
15/01/2007 19:40 Presented by Dr. Thomas Cheng
Samsung asked if there are any contention limitations taking account of the second sentence in the section 4.1.1
second sentence, is the contention limitation. It was commented by Ericsson that there are contention avoidance for
resolving this point and they proposed the best solution in this document.
R1-070425 Link analysis of QPP based turbo interleaver (Qualcomm Europe)
15/01/2007 19:30 Presented by Miss Xiaoxia Zhang
R1-070462 QPP Interleaver Designs for LTE Turbo Coding (Ericsson)
R1-070484 QPP interleaver parameters (Ericsson, Motorola)
15/01/2007 19:50 Presented by Dr. Thomas Cheng from Ericsson
25

Juho Lee (Samsung) raised a concern that it's a new parameter after the deadline and it's not aligned to the
agreement for way forward on the last meeting. It was commented by Ericsson and Motorola that this is the further
detail proposal fro harmonize the different QPP proposal to conclude the decision on the interleaver during this
meeting.
Giovanni Vannucci (Mitsubishi) commented there is a appropriate number of parallerisation order for the
complexity even though Ericsson clarified that any order can be supported with the almost same complexity.
R1-070483 LTE Turbo Coding Interleaver (Ericsson, Nokia, Motorola, Qualcomm)
15/01/2007 20:05 Presented by Dr. Thomas Cheng from Ericsson
R1-070061 ARP Interleaver Design for LTE (Motorola)

15/01/2007 20:05 Presented by Dr. Ajit Nimbalker
It was clarified by Motorola that they had investigation on ARP and QPP and they think the both scheme can be
applicable for LTE but taking account of the other companies view, they proposal QPP as the appropriate scheme.
R1-070171 An ARP base 4 hardware saving, flexible granularity an flexible parallelism
ARP interleaver suitablew for all possible block sizes in 3GPP LTE Turbo Codes
(Broadcom)
15/01/2007 20:10 Presented by Mr. Shen
Ericsson raised a concern on the performance the difference from the last contribution on the last meeting.
Motorola raised a concern on the new parameters that we don't want more delay by taking more cross check for the
new parameters.
Broadcom proposed the ARP for LTE taking consideration that ARP is less complexity and much flexibility from
their analysis
R1-070172 Formulaic Collision-free Memory Accessing Mapping for Parallel Turbo
Decoding with ARP interleaver (Broadcom)
15/01/2007 20:xx Presented by Mr. Shen
R1-070112 IBP interleaver for turbo coding and shortening position assigning algorithm
(ITRI)
15/01/2007 20:40 Presented by Mr. Chi-Fang Li
It was clarified that in the cross check in Figure 8, the updated parameters are applied for all scheme.
R1-070111 Turbo decoder parallelism degree for IBP-like interleaver (ITRI)
15/01/2007 20:50 Presented by Mr. Chi-Fang Li
R1-070342 Turbo coding performance with Rel'6 PIL and IBPI (Samsung)
15/01/2007 20:55
R1-070209 A PIL-Based New Contention-Free Interleaver for Turbo Codes

(Mitsubishi Electric)
15/01/2007 21:00 Presented by Mr. Giovanni Vannucci
26
Brian Classon (Motorola) commented that they don't agree to CF for LRI as shown intheR1-070549 and raised a
concern on the change of the parameters from the first version (what is reason). It was clarified by Mitsubishi that
the performance is stable and just for the simple implementation.
R1-070549 Issues with LRI Interleaver (Motorola)
15/01/2007 21:30 Presented by Mr. Adjit Nimbalker
Giovanni Vannucci from Mitsubishi commented that contention free is depending on the definition although they
explore and explore on this point, but anyway LRI has CF property, much flexibility and less complexity such that
LRI is very close to PIL for implementation point.
Summarising the discussion by Chairman

At first, Mr. Chairman listed the candidates of new CF interleaver and commented that we have a lot of concerns on
the cross check for the performance even though it was satisfied to the requirement that the performance cannot be
worse that Rel-6 interleaver. In addition, it is not sure for the comparison on the complexity and memory property.
The best way forward is that we could select one solution and discuss more details in the next meeting for being
stable until March (Stage 2).
Juho Lee from Samsung commented that although they proposed the PIL all companies did not supported to CF
property of PIL, so if they take one solution from the left solutions they prefer to the Mitsubishi proposal. Julius
Robson from Nortel commented that they are support to Mitsubishi considering the minimizing the complexity for
both HSPA (HSPA+) and LTE. LGE also support to LRI
Stefan Parkvall from Ericsson commented that as already shown in Motorola paper, LRI has issue on CF property
for the higher data rate.
ITRI raised a concern that the evaluation from Mitsubishi on LRI is just a couple set of block length and for
example in the case of K=902 LRI is worse than the other CF interleaver
In addition, Thomas Chang from Ericsson pointed out the performance behaviour on LRI that LRI has error floor
behaviour as shown in R1-070464 (K = 902) and the error floor starts from Block error rate 10-3.
Brian Classon from Motorola commented that at first we should choose the CF interleaver and at next consider the
complexity and also we should take a scheme for long term.
Juho commented about the complexity comparison that there are no sure criteria so the comparison has been
depending on the each company definition so far.
Mark Kent (Broadcom) about the complexity and flexibility is much different between ARP and QPP in their
analysis and we need to discuss the metric for complexity discussion.
Mr. Chairman commented from his personal impression that LRI is just one analysis, on the other hand QPP is
more solid because almost company done. More comparison between QPP and LRI is the difficult but it is not
ready to give up this topic during this meeting. So finally Mr. Chairman recommended trying to make a comparison
between LRI and QPP among the interested people and it can be done in this week and check later on.
Discussion and support for the different proposals:

- QC: Proposal withdrawn
- QPP: Ericsson, Motorola, Nokia, Qualcomm
- ARP: Broadcom
- IBP: ITRI
- LRI: Mitsubishi, Samsung, Nortel, LGE
Two proposals to be further considered: QPP and LRI, focus on complexity improvements and
potential performance issues (with LRI), discuss this offline during this week and check again
on Friday.
R1-070617 LRI (Mitsubishi Electric, LGE, Samsung, Nortel)

19/01/2007 12:11 Presented by Dr. Giovanni Vannucci
Vincent Belaiche from Renesas Technologies supported LRI from a viewpoint of the benefit shown in this
contribution.
27
R1-070619 On the Turbo Interleaver selection

(Motorola, Ericsson, Nokia, Broadcom, Freescale, Qualcomm, CATT, ITRI)
19/01/2007 12:15 Presented by Mr. Brian Classon from Motorola
Siemens and France Telecom support to this contribution and QPP as the TC Interleaver for the further work.
Mr. Chairman commented considering the physical layer time schedule we have still the other work in this area
such as rate matching and channel interleaving so that we would like to down selection from these two proposals
soon.
Julius Robson from Nortel commented that considering the contributions for two proposals and their comparison,
there is nothing separated as for complexity, performance and so on so that they propose to go back to Rel-6
interleaver considering the commonality to R99.
Mr. Chairman commented that the commonality is very important and we have the same structure WCDMA and
HADPA even though performance such as data rate was improved. We don't see just the commonality in near
future (area) but also see the scalability to the future improvement.
After that, there were still some discussion as for complexity and performance between Mitsubishi and Ericsson as
same as Monday session.
As for QPP, TI, T-Mobil, Cingular Wireless and ZTE supported it as the further work considering the benefit
compared with LRI and also LTE time schedule.
So finally supporting companies for LRI v.s QPP is 5 v.s. 14 as followed.
LRI supported by Mitsubishi, LGE, Nortel, Samsung, Renesas

QPP supported by Motorola, Ericsson, Qualcomm, Nokia, Broadcom, Freescale, CATT, ITRI, France
Telecom, Siemens, Texas Instruments. T-Mobile, Cingular, ZTE
Mr. Chairman commented that if we take a voting, the supporter to QPP would reach to more than 71 %, so that he
proposed as following conclusion and all proponents of QPP and also LRI agreed this conclusion with no objection.
Conclusion:
RAN1 selects QPP and will base the further work on this.

R1-070054 Contention-free Interleaver designs for LTE Turbo Codes (Motorola)
R1-070055 Performance of Contention-free Interleavers for LTE Turbo Codes
(Motorola)
R1-070056 Performance of Contention Free Interleaver Designs for LTE
(Motorola)
R1-070057 Summary of Rel 6 Turbo Code Interleaver Issues for LTE (Motorola)
R1-070059 Code Block Segmentation for Contention-free Turbo Interleavers (Motorola)
R1-070225 On the consideration of parallel TC decoder for LTE (LG Electronics)
R1-070254 Parallel Turbo Decoder Options (Texas Instruments)
R1-070341 Views on Turbo interleaver candidates: complexity and other aspects
(Samsung)
R1-070453 Turbo Interleaver Performance Comparison (Nortel)
R1-070454 Discussion on LTE Turbo Interleaver selection (Nortel)
R1-070464 Performance Comparison of LTE Turbo Internal Interleaver Proposals
(Ericsson)
R1-070618 Flexible and Formulaic Collision-free Memory Accessing for Parallel Turbo
decoding with QPP Interleave (Broadcom)

Tail-biting
28
R1-070058 Eliminating tail bits in LTE channel coding (Motorola)

R1-070173 Tail-Biting Encoding for 3GPP LTE Turbo Codes of Arbitrary Number of
Information Bits and performance comparison (Broadcom)
R1-070544 Tail-Biting Encoding for 3GPP LTE Turbo Codes of Arbitrary Number of
Information Bits and performance comparison (Broadcom)
R1-070253 Turbo Code Tail Methods (Texas Instruments)
R1-070376 Performance of tail-biting turbo codes (Nokia)
Mr. Chairman remind to keep in mind the following other issues although we could not treat at the moment.
Other LTE coding
R1-070113 Shortening and prunning for turbo coding (ITRI)
R1-070219 System-Level Evaluation using the low rate extension of UTRA turbo code
(Fujitsu)
R1-070312 LTE Channel Coding Aspects (Siemens)
Mr. Chairman listed up the following technical points as other issues.

Other issues: segmentation size, code rates lower than 1/3
Withdrawn
R1-070110 Network for turbo coding (ITRI)
6.5 Basic Access Procedures

This agenda point was discussed in Tuesday with RAN1 Vice Chairman, Dr. Sadayuki Abeta chairing.
The following decision was captured from R1-070612
R1-070612 Summary of SCH and RACH session (Ad Hoc Chairman, NTT DoCoMo)
Decision: The decision from this ad hoc session was agreed.
6.5.1 RACH Procedure Physical Layer Aspects
R1-070065 Summary of RACH e-mail reflector discussion (Motorola)

Working assumption:
For early L2 contention resolution, NACK- collision (to indicate collision in the preamble) is not
supported
Scheduling request
R1-070041 Dynamic contention free Scheduling Request (Motorola)
R1-070085 Uplink Physical Channel for Scheduling Request Transmission
(NTT DoCoMo, Fujitsu, NEC, Panasonic, Sharp)
R1-070259 Contention-Free Preamble-Based Synchronized Random Access
(Texas Instruments)
29

R1-070378 UL Resource Request for LTE System (Nokia)
R1-070379 Multiplexing for Dedicated Resource Request (Nokia)
R1-070426 UL requests (Qualcomm Europe)

R1-070260 Contention-Free Preamble-Based Synchronized RACH: Comparison with
other solutions (Texas Instruments)
Working assumption:
Non contention based scheduling request mechanism for synchronized users
Providing contention based scheduling request (Non sync random access) is RAN2 decision
UE eNB
1 Scheduling Request Indicator

asynchronous
Uplink Scheduling Grant 2
3 Scheduling Request + Data
Actual content of 3rd message will be decided by RAN2
Actual scheduling request schemes will be decided later

- Specific dedicated channel (including CQI CH etc.):
- Preamble based:
The detail procedures are related to UL L1/L2 control channel. Thus, the procedures should be discussed
together with L1/L2 control channel
Support high mobility

R1-070188 Non-synchronized RACH preamble structure for high mobility UE
(Panasonic, NTT DoCoMo)
R1-070377 Restricted sets of RACH preamble signatures for environments with high
Doppler shifts (Nokia)
Proposals:
Maintain 0.8 msec preamble with restricted set of cyclic shifts for cell supporting high mobility UE:
Ericsson, Huawei, Nokia, TI, Qualcomm, LGE, Vodafone, Motorola, InterDigital,
Support 2 structures: 0.8msec and repeat 3 0.27 msec structure: Panasonic, DoCoMo, Alcatel-Lucent,
Working assumption:
Maintain 0.8 msec preamble with restricted set of cyclic shifts for cell supporting high mobility UE

R1-070129 Non-Synchronized RACH Preamble structure to support high mobility
(Samsung)
30
R1-070226 Non-Synchronized Random Access Design under Frequency Offset

(LG Electronics)
R1-070227 Ways to Mitigate Frequency Offset with CAZAC Cyclic Shift
(LG Electronics)
R1-070257 Non Synchronized Random Access Performance in High Doppler Conditions
(Texas Instruments)
R1-070316 Non-synchronized RACH in support of high-speed UEs: detailed parameters
(Alcatel-Lucent)
R1-070427 Impact of high Doppler to random access preamble detection
(Qualcomm Europe)

Filtering/Guard band
R1-070128 Filtering for Non-Synchronized RACH preamble (Samsung)
R1-070255 Improved Non-Synchronized Random Access structure for E-UTRA
(Texas Instruments)
R1-070256 Interference between Data and RACH in EUTRA (Texas Instruments)
R1-070380 Filtering Roll-off for Non-synchronized Transmissions (Nokia)
R1-070405 Non-synchronized RACH Sampling Rate in LTE (ZTE)

Alternative frame structure in TDD
R1-070286 Preamble design of non-synchronized RACH for E-UTRA TDD
(CATT, RITT)
R1-070287 Implicit message transmitted for non-synchronized RACH
(CATT, RITT)
Others
R1-070340 Discussion on the cell planning with non-synchronized RACH (Samsung)
Decision: This document was noted

R1-070042 Non-synchronized random access (Motorola)
R1-070163 Minimizing the Non-synchronized RACH Procedure Requirement During LTE
Handover (InterDigital)
R1-070189 Zadoff-Chu sequence allocation on RACH for complexity reduction
R1-070228 Multi-TTI RACH Allocation Methods (LG Electronics)
R1-070258 Non Synchronized Random Access Collision Rate and Performance Impact
(Texas Instruments)
R1-070315 Capacity analysis of E-UTRA non-synchronized RACH with additional control
information (Alcatel-Lucent)
R1-070317 Load control for E-UTRA non-synchronized RACH (Alcatel-Lucent)
R1-070413 Content of the preamble (LG Electronics)
R1-070527 Non-Synchronized Random Access Procedure (ETRI)
6.5.2 SCH and Cell Search

R1-070064 Summary of S-SCH e-mail reflector discussion (Motorola)
31
Cell search time evaluation

R1-070382 Cell Search Performance for Approach 1 and Approach 2 (Nokia)
R1-070428 Further analysis of initial cell search for Approach 1 and 2 - single cell scenario
(Qualcomm Europe)
R1-070429 Further analysis of initial cell search for Approach 1 and 2 - multi cell scenario
(Qualcomm Europe)
Agreement
RAN1 confirm that Approach 1 is working assumption.

R1-070143 Initial Cell Search Design (Motorola)
P-SCH (Multiple P-SCH or Single P-SCH)

R1-070018 The number of P-SCHs and coherent vs. non-coherent second step (ETRI)
R1-070086 Investigations on Primary-SCH sequences for E-UTRA Downlink
(NTT DoCoMo, Mitsubishi Electric, Panasonic)
R1-070145 P-SCH Sequence Design (Motorola)
R1-070262 Performance of 3-Stage Cell Search (Texas Instruments)
R1-070381 Cell Search Performance for Different Number of PSC in Synchronized
Network (Nokia)
R1-070118 Encoding cell-specific information by generalized 2-D orthogonal DL RS
sequences (Huawei)
Decision: This document was noted as supporting information in the discussion about the possible allowed number
of hypothesis in the 3rd stage of cell search
Multiple P-SCH
- cell planning is real issue? : Yes or No
- Performance improvement: 20% - 100%
Multiple P-SCH: Sharp, TI, ETRI, DoCoMo, InterDigital, LGE, Panasonic, Freescale, Mitsubishi, ZTE,
Single P-SCH: Nokia, Ericsson, Motorola, Qualcomm, Huawei, Samsung, Siemens,
Working assumption:
Multiple P-SCH (number of P-SCH sequences is 3)
Number of Hypotheses
- Number of antenna: at least 1 bit (stage 2 or 3)
- Cell ID: 9 bits (stage 2)
- Frame timing: 1 or 0 bit (stage 2 or 3)
- blind CP detection?:
32
Total : 2040?
Working assumption:
Number of Hypotheses at stage 2: detect 1 out of 170 cell ID groups, frame timing
detection in stage 2
Number of Hypotheses at stage 3: detect 1 out of 3 cells from the cell ID groups selected
in stage 2
Rest number of Hypotheses dependent upon P-BCH transmit scheme (TBD) whether it
will be detected in stage 1, 2 or stage 3
Location of P-SCH and S-SCH as Figure 2 of R1-062990, located in last 2 OFDM

symbols of slot.

R1-070229 Comparison of single PSC and multiple PSCs (LG Electronics)
R1-070216 Further Results on Multiple P-SCH Complexity for E-UTRA Cell Search
(Sharp)
R1-070261 Further Details of SCH Based on Approach 1 Option 2 (Texas Instruments)
R1-070451 Timing Synchronization Performance Evaluation (Nortel)

P-SCH sequence designs
R1-070019 Minimization of the number of P-SCH sequences using subframe offset
between node Bs in synchronized network (ETRI)
R1-070164 Cell Search SCH Proposal for E-UTRA (InterDigital)
R1-070196 A New Method on P-SCH Design and Detection (ZTE)
R1-070230 P-SCH sequence design for single and multiple PSCs (LG Electronics)
R1-070358 Primary Synchronization Codes (PSC) for E-UTRA (NEC Group)
R1-070447 Frame Timing Acquisition based on P-SCH (Nortel)
S-SCH (Coherent or Non-Coherent)

R1-070116 Performance of coherent and non-coherent S-SCH demodulation (Huawei)
R1-070289 Performance of S-SCH detection using channel estimation by P-SCH
(CATT)
R1-070445 Cell Search Performance in Synchronized Networks (Nortel)
S-SCH design
R1-070020 S-SCH structure for EUTRA cell search (ETRI)
R1-070146 S-SCH Sequence Design (Motorola)
R1-070231 S-SCH sequence design (LG Electronics)
R1-070264 Comparison of Different S-SCH Structures for E-UTRA Cell Search
(Texas Instruments)
Others
R1-070017 Soft-combining for P-BCH (Toshiba)
R1-070021 Location of SCH and P-BCH (ETRI)

R1-070053 Cell Search and MBMS (Motorola)
R1-070081 Interworking between LTE and GSM - Monitoring LTE from GSM
(Siemens)
33
R1-070144 Non-initial Cell Search and Neighbor list impact (Motorola)

R1-070195 One improvement on SCH Location for E-UTRA TDD (ZTE, CATT)
R1-070575 One improvement on SCH Location for E-UTRA TDD (ZTE, CATT)
R1-070263 Performance of Coherent and Non-Coherent Stage 2 Detection
(Texas Instruments)
R1-070288 Comparing Hybrid and cross-correlation method for cell search
(CATT)
R1-070307 Reduction of Initial E-UTRA Cell Search Delay (Siemens)
R1-070430 Neighbor cell search: analysis and simulations (Qualcomm Europe)
R1-070452 Extended SCH for non-initial cell search (Nortel)
Withdrawn
R1-070087 S-SCH Sequence for E-UTRA Downlink (NTT DoCoMo)
6.6 Reference signal structure

6.6.1 Downlink reference signals
R1-070265 Summary of Reflector Discussions on EUTRA DL RS (Texas Instruments)
19/01/2007 09:15 Presented by Dr. Aris Papasakellariou
Aris commented the main issue to be decided is RS frequency hopping so that FH impact mainly was discussed. At
Firstly, the following point was agreed
Conclusion from the email discussion:

- Is RS FH enabled for E-MBMS or BCH sub-frames? It was agreed that RS from the multiple Node
Bs always occupy the same sub-carriers during MBMS sub-frames.
R1-070149 Hopping of Downlink Reference Signals (Motorola)

The FH mode, 0 offset, constant, variable was discussed. Some companies commented that 0 offset and constant
mode is considered as the same mode (same benefit) so reduce the option. Some companies also pointed out that to
discuss on FH pattern should take into account of the decision on cell search in this week.
Juan Montojo asked with wonder how P-BCH could be decoded and also he commented that three options can be
reduced to two considering zero shift as constant shifting. Erik Dahlman from Ericsson commented that three
modes (options) could be valuable and 1 bits is allocated for P-BCH for indicating hop/shit or no and not 2 bits.
Asbjörn Grovlen from Nokia raised a concern why we need to support three options taking into account of
complexity issue.
Mr. Chairman suggested offline discussion during coffee break and making a clear text.
After the coffee break, Erik Dahlman from Ericsson proposed the following text.
• Pre-requisite: Hopping(1), shifting,(2) zero-shift/no-hop (3)
• Shifting is a sub-set of hopping patterns
– Implies that, if an operator wants to exclusively use ”hops” or ”shifts” there is less than 510
sequences available
– General case: Shift: N*6 sequences, Hop: 170-N*6 sequences
– Note! In case of zero-shift, there would be 170 sequnces!!!
• Hop-pattern/shift tied to cell group ID
– Pattern known in step #2 , 170 hop ”patterns”
• Known format (hop/shift or no hop/shift?) for sub-frame#0 and #5, i.e. sub-frames carrying P-BCH/SCH
34
• 1 bit on P-BCH indicates if hop/shift or not hop/shift in remaining sub-frames

– No hop/shifts in sub-frames used for MCH using MBSFN
Asbjörn Grovlen from Nokia still expressed a concern on the number of modes (options) for this text. In addition,
he raised a concern on the P-BCH indication from viewpoint of P-BCH measurement
Juan Montojo from Qualcomm commented that regarding the text "Hop-pattern/shift tied to cell group ID ... ", the
hopping pattern is OK, but the sift pattern is much large on meaning of this sentence. Also he pointed out the
signaling of sift pattern taking into account of TDM multiplexing of unicast and SFN-MBMS which endorsed in
this week.
So, the offline discussion took place among the interested parties.
R1-070630 Way forward on DL RS (Ericsson, Nokia, Huawei, NTT DoCoMo,

Motorola, Qualcomm, Samsung, TI, Alcatel-Lucent, LGE, Nortel Networks)
It was clarified that "Hopping period equal on one 10 ms frame" means length of the hopping sequence is 10ms
Decision: This document was noted and the following text was agreed.
Agreed way forward for DL RS FH

• Shifting is a sub-set of hopping patterns
• Hop-pattern/shift tied to cell group ID
– Pattern known in step #2 , 170 hop ”patterns”
– Hopping period equal on one 10 ms frame (i.e. length of the hopping sequence is
10ms)
• All subframes of cell/carrier are either hopping or not hopping
– [In practice implies carriers with MCH/MBSFN subframes do not hop]
• To find out if hopping or not hopping is used
– Indicated from S-SCH (step 2)
– or detected from step 3 (twice as many hypothesis)
– TBD at next meeting
Dl dedicated RS
R1-070290 Downlink dedicated reference signal aspects in EUTRA TDD
(CATT, RITT, ZTE)
19/01/2007 10:10 Presented by Mr. Ke wang
It was clarified that the first sentence in conclusion means that common RS is not need in every subframe and
dedicated RS is sent in each time slot. Also this contribution recommended power boosting but there has not the
simulation results, may be needed later.
Additionally, it was clarified that this contribution is considered for LCR compatible structure so that normal TDD
structure is not.
R1-070089 Dedicated Reference Signal for Beam-forming in E-UTRA Downlink
(NTT DoCoMo, Fujitsu, Mitsubishi Electric, NEC, Panasonic)
19/01/2007 10:20 Presented by Dr. Kenichi Higuchi from NTT DoCoMo
It was clarified by NTT DoCoMo that the structure of RS is just example and not exact one and also they assume
UE specific BF and not assume the high level sectorization.
Mark Harrison from Motorola commented that they support BF is useful and then they pointed out the structure for
BF is close to precoding so that the structure for BF would support precoding. Kenichi Higuchi from NTT
DoCoMo commented that they understand such possibility and only precoding case is not necessary.
Juho Lee from Samsung commented that we don't have clear conclusion on control signalling for pre-coding and
also he expressed a wonder that the motivation of BF is dedicated for the coverage but how much gain can be
achieved by BF. Klaus Hugl from Nokia also expressed a wonder on the gain by BF from point of coverage and
also data rate. Kenichi commented that MIMO and BF is different configuration and if data rate are prioritized it is
configured for MIMO precoding and in such case the coverage is smaller than BF case.
35
It was asked if the coverage gain by BF is just for shared data channel. It was answered that it is for shared data
channel but also if the coverage of data channel is improved by BF and then it is possible to allocate the more RB
(power) to control signalling such BCH so that the gain for control channel can be expected as well.
Hai Tang from CATT commented that they share with NTT DoCoMO view and BF is specialised for the coverage
and MIMO precoding is for data rate in the small cell data rate and both can be complementary with each other,
Juho commented that this discusison is very related to MU-MIMO discussion and also he is not sure how clear the
scenario for the dedicate RS is so that at first we should consider and define the scenario for dedicated RS and
evaluate the performance gain by that. Also Klause still expressed his wonder for the BF gain considering the cost
an addition to MIMO precoding.

R1-070147 Four Transmit Antenna Downlink RS Formats for EUTRA (Motorola)
R1-070148 Downlink RS Placement within a Slot (Motorola)
R1-070232 Performance evaluation of DL reference signal on control channel
(LG Electronics)
R1-070151 Proposal for dedicated pilots in downlink precoding for EUTRA MIMO
(Motorola)
R1-070117 Cell-specific integer sequences for frequency positioning of DL RS on subframe
basis (Huawei)
R1-070532 Cell-specific integer sequences for frequency positioning of DL RS on subframe
basis (Huawei)
R1-070088 Power Boosting of Reference Signal in E-UTRA Downlink (NTT DoCoMo,
Fujitsu, Mitsubishi Electric, NEC, Panasonic, Sharp)
R1-070122 TDD/FDD E UTRA commonality aspects of the reduced-latency DL reference
signal for FDD E-UTRA (Alcatel-Lucent)
R1-070123 Considerations on the EUTRA DL reference signal structure and the DC sub-
carrier (Alcatel-Lucent)
R1-070150 Simulation results for GCL based DL reference signals (Motorola)
R1-070291 Downlink reference signal aspects for non-codebook based pre-coding in TDD
mode (CATT, RITT)
R1-070383 Reference Signals for Mixed Carrier MBMS (Nokia)
R1-070431 DL RS for Multiplexed Unicast and MBMS Configurations
(Qualcomm Europe)
Withdrawn
R1-070077 Reference Signal Structure for Multi-antenna E-MBMS Transmission
(Alcatel-Lucent)
R1-070526 Reference Signal Structure for Multi-antenna E-MBMS Transmission
(Alcatel-Lucent)
6.6.2 Uplink reference signals

R1-070266 Summary of Reflector Discussions on EUTRA UL RS (Texas Instruments)
Decision: This document was noted. Agreement on Long RS was endorsed
0.5 ms slot structure:

 Adopt LB RS (RS in the 4th LB of the slot – Figure 1).
36
 Have as working assumption that no additional (UE speed adaptive) RS is inserted for high speed UEs. This is
based on current evidence that it does not adversely impact the fulfillment of EUTRA requirements; however it
can be re-assessed if evidence to the contrary is demonstrated.
RS
Data
Slot
RS
Sub-Frame
Figure 1: UL Sub-Frame Comprising of 2 Slots. Each slot has 7 LBs - DM RS is in the middle LB.
The 0.675 ms slot structure can be treated separately.

If SB RS is maintained for the 0.675 slot structure, it was noted that a possibility to increase the number of ZC sequences
is to set the minimum data allocation equal to 2 RBs.
R1-070152 Uplink RS generation methods (Motorola)

R1-070384 UL Reference Signals (Nokia)
19/01/2007 15:15 Presented by Mr. Jari Lindholm
Daichi Imamura from Panasonic asked if 3 RB case have been considered so far although this document considered
just one RB considering cross correlation point view. The answer was that have not but it's important point so that it
should be done before the decision.
R1-070365 Structure of uplink reference signal (Fujitsu)
19/01/2007 15:25 Presented by Mr. Yoshihiro Kawasaki
Brian Classon from Motorola commented out that 3RB case is very important point as for CM viewpoint . The
cross-correlation-properties were not yet examined for other sequence indexes than 1and 2. It was commented that
truncation might be better than cyclic-extension for 3-RB allocation in terms of cubic metric of p/2-BPSK.
R1-070190 Uplink reference signal structure and allocation for E-UTRA
19/01/2007 15:35 Presented by Mr. Daichi Imamura
R1-070433 UL RS Planning and Structure with Long Blocks (Qualcomm Europe)
19/01/2007 15: 40 Presented by Mr. Juan Montojo
Brian Classon from Motorola recommended RS sequence length is the same as the number of resource blocks, i.e.,
the number of subcarriers, either truncation or cyclic extension. Erik Dahlman from Ericsson supported Motorola
view. Pierre Bertrand from TI raised a concern on two options were available from view point of simple and Node
B processing and he proposed to select just one option. Jari Lindholm from Nokia also raised a concern that we
need more study on cross correlation property before the decision and they took the contribution from Toshiba as
the interesting contributions relate to this point. Finally, taking into account of the view from interested parties, Mr.
Chairman proposed the working assumption and the assumption was agreed.
Working Assumption:
RS sequence length is equal to the number of sub-carriers in the resource blocks, either
truncation or cyclic extension of ZC sequences are used, depending on the RB allocation size.
37
Problems with the working assumption related to cross-correlation should be raised during the
e-mail discussion.
R1-070432 UL RS structure issues with frequency domain CDM (Qualcomm Europe)

19/01/2007 15:45 Presented by Miss. Xiaoxia Zhang

R1-070090 Necessity of Multiple Bandwidth for Sounding Reference Signals
R1-070091 Assignment Scheme of Sounding Reference Signals in E-UTRA Uplink
(NTT DoCoMo)
R1-070092 Throughput Comparisons between SB and LB Reference Signals in E-UTRA
Uplink (NTT DoCoMo)
R1-070153 Uplink Reference Signal Planning Aspects (Motorola)
R1-070213 Cyclic shift-hopping for uplink sounding reference signal (ETRI)
R1-070217 Staggered Uplink Reference Signal Allocation (Sharp)
R1-070233 Performance evaluation of uplink LB DM reference signal (LG Electronics)
R1-070234 Several Types of Uplink Reference Signal Sequence (LG Electronics)
R1-070267 Sounding Reference Signal Assignments in E-UTRA Uplink
(Texas Instruments)
R1-070268 Sequence Hopping for the Uplink Reference Signal (Texas Instruments)
R1-070292 Uplink LB vs. SB Structure for EUTRA TDD (CATT)
R1-070359 Definition of Cyclic Shift in Code Division Multiplexing (NEC Group)
R1-070367 Sequence Allocation Method for E-UTRA Uplink Reference Signal
(Huawei)
R1-070465 LTE uplink reference-signal structure (Ericsson)
R1-070492 On UL Reference Signal Structure (Toshiba)
6.7 Downlink MIMO, Transmit Diversity and Beamforming

This agenda point was discussed in Tuesday with RAN1 Vice Chairman, Dr. Juho Lee chairing. The
following decision was captured from R1-070616
R1-070616 Summary of LTE MIMO session (Ad Hoc Chairman)

19/01/2007 16:30 Presented by Dr. Juho Lee from Samsung
Decision: This document was endorsed.
MIMO Ad Hoc Chairman, Juho Lee from Samsung clarified that we will no take SU-MIMO as agenda item in the
next meeting and he pointed out that we should take the decision for SU-MIMO in UL into account in discussion
on DL and UL signalling.
Regarding the discussion on the support of 64QAM to be continued in the main session, Mr. Chairman commented
that we don't have enough time to discuss here so that continue the e-mail discussion and we would hopefully
decide in next meeting.
R1-070343 LTE MIMO email discussion summary (Samsung)

Conclusion:
- Agreed on that codebook based precoding will be supported for TDD as well.
- Continue discussion on whether non-codebook based pre-coding shall be supported for TDD and
if so, how.
38
Withdrawn
R1-070345 Text Proposal for MIMO resource definition for E-UTRA (Philips)
6.7.1 Mapping of codewords to layers

R1-070130 Considerations on codewords to layers mapping for downlink MIMO
(Samsung)
R1-070235 Codeword to layer mapping for SU-MIMO (LG Electronics)
R1-070269 Multi-Codeword Principles for E-UTRA MIMO (Texas Instruments)
R1-070385 Layer to Codeword mapping for DL SU-MIMO (Nokia)
Conclusion:
- DL signaling supports for Node B’s overriding the rank reported from the UE (working
assumption)
- Full flexibility for mapping between HARQ process ID and CW (working assumption)
- Fixed mapping between CWs to layers (working assumption)
 Rank1: CW1 to 1st layer (working assumption)
 Rank2: CW1 to 1st layer, CW2 to 2nd layer (working assumption)
 Rank3: CW1 to 1st layer, CW2 to 2nd and 3rd layers (working assumption)
 Rank4:
 Working assumption: CW1 to 1st and 2nd layers, CW2 to 3rd and 4th layers
 Working assumption may be revisited in R1#48 meeting regarding the issues
identified below
 FFS: CW1 to 1st layer, CW2 to 2nd, 3rd, 4th layers
 Issues identified (check the situation in the next meeting)
- Performance difference between 2+2 and 1+3
- Diversity aspect 2+2 vs 1+3 regarding CQI imperfection under practical
conditions
- Implication of Node B overriding the rank reported from the UE on CQI
mismatch.
- System operation scenario and UE implementation complexity
6.7.2 Precoding details

Codebook based vs non-codebook based precoding for TDD
R1-070201 Non-codebook based precoding in E-UTRA TDD (ZTE)
R1-070293 Single user throughput simulation results for non-codebook based pre-coding
in EUTRA TDD (CATT)
R1-070294 Link level simulation results for non-codebook based pre-coding in EUTRA
TDD (GBF) (CATT)
R1-070295 Link level simulation results for non-codebook based pre-coding in EUTRA
TDD (SVD) (CATT)
39
R1-070482 On MIMO operation in TDD (Ericsson)

R1-070490 Consideration on non-codebook based pre-coding for TDD (IPWireless)
R1-070576 Consideration on non-codebook based pre-coding for TDD (IPWireless)
Way forward: Try to make the final decision in R1#48 meeting.

R1-070062 Mobile Assisted Non-codebook based precoding for TDD (Motorola)
Precoding codebook proposals

R1-070093 Investigations on Codebook Size for MIMO Precoding in E-UTRA Downlink
(NTT DoCoMo)
R1-070236 Precoding for E-UTRA downlink MIMO
(LG Electronics, Samsung, NTT-DoCoMo)
Precoding codebook construction (focusing on optimizing SU-MIMO)

Conclusion:
- Working assumption: Rank non-specific precoding codebook
 For a given codebook, predefine (i.e. no dynamic update) a set of M precoding matrices of 2x2
for 2tx antenna, where 2x2 identity matrix may be configured by the network to be included in
the set.
 For a given codebook, predefine (i.e. no dynamic update) a set of N precoding matrices of 4x4 for
4tx antenna, where 4x4 identity matrix may be configured by the network to be included in the
set.
 Rank adaptation by selecting a non-square precoding matrix that is a part of a square precoding
matrix.
- FFS:
 Performance benefit of less restrictive approaches
The working assumption may be revisited in R1#48 meeting if needed.
 Can UE assume that Node B should use the precoding matrix reported by the UE?
 Further limitation on the codebook (including the associated signalling scheme)
UE capability
Node B’s expectation on the usage of the codebook

R1-070094 Multi-Codebook Pre-coding Scheme for MIMO in E-UTRA Downlink
(NTT DoCoMo)
R1-070119 Inter-cell interference rejection performance for CDD-type transmission
(Huawei)
R1-070131 MIMO precoding for E-UTRA Downlink (Samsung)
R1-070237 System Level Evaluation of the CDD-based Precoding (LG Electronics)
R1-070238 Codebook evaluation for E-UTRA MIMO precoding - 2Tx and 4Tx rank 1
(LG Electronics)
R1-070360 Codebook based precoding for MIMO EUTRA (NEC Group)
R1-070434 Precoding details for DL MIMO (Qualcomm Europe)
R1-070168 Beamforming Compact Codebook Method and Results in E-UTRA
(Broadcom)
40
R1-070202 Codebook Design for E-UTRA MIMO (ZTE)
Withdrawn
R1-070239 Codebook design and evaluation for E-UTRA MIMO precoding - 4Tx rank 1~2
scheme (LG Electronics)
R1-070491 Comparison between codebook and non-codebook based pre-coding for TDD
(IPWireless)
6.7.3 UE feedback
UE feedback granularity
R1-070125 Effects of frequency selective feedback on precoding in E-UTRA downlink
(Alcatel-Lucent)
R1-070154 Further results on Frequency Domain Adaptive Precoding for E-UTRA MIMO
(Motorola)
R1-070155 Frequency-Domain Adaptive Precoding Granularity for EUTRA (Motorola)
R1-070191 Frequency selective/non-selective precoding for SU-MIMO (Panasonic)
R1-070220 Overview and Way forward on MIMO Precoding in DL EUTRA
R1-070120 On the precoding feedback granularity for DL MIMO (Huawei)
R1-070133 MIMO System Performance with variable frequency granularity of UE
feedback (Samsung)
This document was revised in R1-070577 before the presentation.
R1-070577 MIMO System Performance with variable frequency granularity of UE
feedback (Samsung)
R1-070134 MIMO Link Performance with variable frequency granularity of UE feedback
(Samsung)
R1-070274 Rank Feedback For MIMO E-UTRA (Texas Instruments)
R1-070386 Performance of frequency dependent precoding for 2x2 LTE DL SU-MIMO
(Nokia)
R1-070387 On UL Feedback of DL SU-MIMO Rank and DL SU-MIMO Rank Adaptation
(Nokia)
R1-070460 Further results on the impact of speed, feedback period, and sub-channel
bandwidth on the performance of downlink closed loop schemes for 4-Tx LTE
(Nortel)
R1-070169 Beamforming Frequency and Time Update Requirements in E-UTRA
(Broadcom)
R1-070240 Link Performance Evaluation of Precoding Scheme According to the Cluster
Size (LG Electronics)
41
Conclusion:
Frequency granularity for UE feedback
- Precoding feedback information
 Working assumption: one per 2/5/10/whole RBs (configured by the network)
 Motorola, Samsung, Nortel, TI, Alcatel-Lucent, IDC, LGE, DoCoMo, Panasonic, ZTE,
NEC, Broadcom, Ericsson, Huawei (single report over the selected best RBs in case of
whole RBs), Freescale, Qualcomm
 FFS: single report over the selected best RBs
 Huawei, Nokia
 Working assumption may be revisited in R1#48 meeting if needed.
- Rank feedback information
 Working assumption: single report over the whole bandwidth (pending the results for the
>5MHz system BW)
 TI, Broadcom, Qualcomm, Nokia, Huawei, IDC, DoCoMo, Nortel, Ericsson,
Panasonic, Siemens, NEC, Freescale
 FFS: same as the precoding (configured by the network) (there may be a mechanism for
reducing the overhead when combined with the precoding feedback information)
 Samsung, Alcatel-Lucent
 Working assumption may be revisited in R1#48 meeting if needed.
- CQI feedback: ?
Time granularity
- Working assumption: configured by the network (similar to CQI in HSDPA)
Number of bits for precoding-related UE feedback

R1-070270 Further Details on Codebook-Based Pre-coding for E-UTRA
(Texas Instruments)
Initial estimate of upper bound on number of precoding possibilities per a selected rank
(Note: the initial estimate should not imply any limitation on the selection of the precoding scheme)
Upper bound for SU-MIMO with 2 tx antennas at Node B: 2 - 12
- TI: 8
- Huawei: 8
- Samsung: 12
- Motorola: 8
- Ericsson: 8 (>= 2)
- IDC: 8
- DoCoMo: 8
- NEC: 8
- Nokia: 8 (>= 4)
- Freescale 8
- LGE: 8
- Panasonic: 8
- Qualcomm: 12
Upper bound for SU-MIMO with 4 tx antennas at Node B: 16 - 32
- TI: 16
- Huawei: 16
- Samsung: 24
- Motorola: (roughly) 16
- Ericsson: 16
- IDC: (roughly) 16
- DoCoMo: 16
- NEC: 32
42
- Nokia: 32
- Freescale 32
- LGE: 16
- Panasonic: 16
- Nortel: 32
- Qualcomm: 24
Upper bound for MU-MIMO with 2 tx antennas at Node B: ? - ?
- TI: ?
- Huawei: ?
- Samsung: ?
- Motorola: ?
- Ericsson: 4
- IDC: ?
- DoCoMo: ?
- NEC: ?
- Nokia: ?
- Freescale: 32
- LGE: ?
- Panasonic: 4
- Nortel: ?
- Qualcomm: ?
Upper bound for MU-MIMO with 4 tx antennas at Node B: ? - ?
- TI: ?
- Huawei: ?
- Samsung: ?
- Motorola: ?
- Ericsson: 4
- IDC: ?
- DoCoMo: ?
- NEC: ?
- Nokia: ?
- Freescale: 32
- LGE: ?
- Panasonic: 4
- Nortel: ?
- Qualcomm: ?

R1-070193 MIMO codebook size discussion for both MU- and SU-MIMO (Panasonic)
R1-070132 Performance of Precoded Single User MIMO with LMMSE receiver
(Samsung)
R1-070271 Precoding Codebook Design For 2 Node-B Antennas (Texas Instruments)
R1-070272 Precoding Codebook Design For 4 Node-B Antennas (Texas Instruments)
R1-070466 Precoding Considerations in LTE MIMO Downlink (Ericsson)
This document was revised in R1-070573before the presentation
R1-070573 Precoding Considerations in LTE MIMO Downlink (Ericsson)
R1-070457 On Codebook Index Feedback and Beamforming Matrix Verification
(Nortel)
R1-070467 CQI delay impact on downlink multi-antenna systems for E-UTRA(Ericsson)
R1-070574 CQI delay impact on downlink multi-antenna systems for E-UTRA(Ericsson)
43
Feedback information
R1-070156 Direct channel feedback for obtaining channel state information at Node B in
EUTRA (Motorola)
R1-070157 Uplink sounding for obtaining channel state information at Node B in EUTRA
(Motorola)
R1-070296 Uplink transmit diversity scheme to provide full CSI to support downlink
MIMO transmission for TDD operation (CATT)
R1-070192 UE feedback information for MIMO support (Panasonic)
R1-070200 UE Feedback Aspects for Downlink MIMO in E-UTRA (ZTE)
R1-070170 UE Feedback Classification and CQI Characterization in E-UTRAN
(Broadcom)
R1-070543 UE Feedback Classification and CQI Characterization in E-UTRAN
(Broadcom)
Feedback Scheme
R1-070221 Efficient method for feedback reduction and feedback mechanism for precoded
MIMO in EUTRA (Freescale Semiconductor)
R1-070273 Views on MIMO-Related UE Feedback (Texas Instruments)
R1-070309 Dual tracking mode feedback for unitary precoding (Siemens)
R1-070388 Reduced CQI design for DL SU-MIMO (Nokia)
R1-070435 UE feedback for DL MIMO (Qualcomm Europe)
R1-070158 Precoding Feedback Overhead (Motorola)
R1-070458 Differential Codebook for LTE Downlink Closed-Loop MIMO
(Nortel)
Withdrawn
R1-070207 Assistant Feedback Channel for E-UTRA TDD to Report Downlink
Transmission CQI and ACK/NACK (ZTE)
6.7.4 MU-MIMO
R1-070222 Aspects of SU/MU Switching and MU-MIMO in DL EUTRA
Working assumption for support of SU- and MU-MIMO:
- Semi-static configuration of SU-MIMO or MU-MIMO per a UE
- Only one layer (in another word, only transmission rank of one) is allocated to a UE configured
to be in MU-MIMO transmission
R1-070223 Scheme for MU-MIMO in DL EUTRA (Freescale Semiconductor)

R1-070608 Scheme for MU-MIMO in DL EUTRA (Freescale Semiconductor)
R1-070318 Link-level results for multiuser eigenmode transmission with limited feedback
(Alcatel-Lucent)
R1-070346 Comparison of MU-MIMO feedback schemes with multiple UE receive
antennas (Philips)
R1-070347 Receiver Phase Reference for Support of MU-MIMO (Philips)
44
Topics for further discussion:

- Performance gain taking into account the required overhead
- What should be specified in the standard?
 Signalling to be specified should be able to be tested resulting in a set of performance
requirements defined in the standard.
6.7.5 Transmit Diversity

E-mail discussion to be held (Moderator by Dr. Juho Lee)

R1-070015 Open Loop Transmit Diversity for Downlink Channels with 4 Transmit
Antennas in E-UTRA (Agere Systems)
R1-070022 Intra- and/or Inter-Sector Diversity Scheme for P-BCH using S-SCH (ETRI)
R1-070023 Comparison of SCH diversity schemes in initial cell search (ETRI)
R1-070095 Transmit Diversity Scheme for Common/Shared Control Channel in E-UTRA
Downlink
R1-070096 Transmit Diversity Scheme for MBMS in E-UTRA Downlink
(NTT DoCoMo, Fujitsu, Institute for Infocomm Research, Mitsubishi Electric,
NEC, Panasonic, Sharp)
R1-070124 Comparison of SFBC and CDD for E-UTRA in noise and interference limited
cases (Alcatel-Lucent)
R1-070135 Transmit diversity performance for the control channels (Samsung)
R1-070136 Transmit diversity performance for the shared data channels (Samsung)
R1-070137 A Way Forward on Transmit Diversity for E-UTRA Downlink (Samsung)
R1-070159 E-UTRA Open Loop Transmit Diversity Performance in Correlated Channels
(Motorola)
R1-070160 E-UTRA Open Loop Transmit Diversity (Motorola)
R1-070214 System Level Simulations of Transmit Diversity for CCPCH (Huawei)
R1-070215 Link Level Simulations of Transmit Diversity for CCPCH with IRC Receiver
(Huawei)
R1-070218 Performance Comparison between the Conventional CDD and a Sub-carrier
Grouping CDD scheme for the common control channel in the E-UTRA Downlink
(Sharp)
R1-070241 Evaluation of SFBC and CDD for control channel with real channel estimation
(LG Electronics)
R1-070598 Evaluation of SFBC and CDD for control channel with real channel estimation
(LG Electronics)
R1-070389 Open Loop DL Transmit Diversity for the Shared Data Channel (Nokia)
R1-070390 Open Loop DL Transmit Diversity for Common Control Channels(Nokia)

R1-070446 Transmit Diversity for Synchronization and Cell Search in a Synchronized
System (Nortel)
R1-070455 Further Performance Evaluation of Downlink Transmit Diversity Schemes for
2- and 4-Branch L1/L2 Control (Nortel)
R1-070468 Two- and four-antenna transmit diversity performance for the SCCH
(Ericsson)
45
Withdrawn
R1-070252 E-MBMS inter resource block combining (Alcatel-Lucent)
6.8 Uplink MIMO and Transmit Diversity

This agenda point was discussed in Tuesday with RAN1 Vice Chairman, Dr. Juho Lee chairing. The
following decision was captured from R1-070616
6.8.1 SU-MIMO
R1-070138 Performance of MIMO for E-UTRA uplink (Samsung)
R1-070165 System Performance Evaluation of Uplink Single User MIMO for E-UTRA
(InterDigital)
R1-070391 Single-user MIMO support in E-UTRA uplink (Nokia)
R1-070436 Aspects of UL MIMO (Qualcomm Europe)
R1-070449 System Level Performance Comparison for UL MIMO (Nortel)
R1-070469 SU-MIMO and 64-QAM in E-UTRA Uplink (Ericsson)
Discussion on the support of SU-MIMO as an UE capability

○ Following alternatives were identified
 Alt1: SU-MIMO to be a feature of the E-UTRA uplink from the start, conditioned on that it
does not delay the time table
 Alt2: Continue work on SU-MIMO without spending considerable time. If SU-MIMO
turns out to not be supported initially in the standard (set an appropriate timeline for
checking the situation), the first release should at least be such that it facilitates introducing
uplink SU-MIMO at a later stage. (IDC, Alcatel-Lucent)
 If the SU-MIMO will be turned out not to be included in the first release, the SU-
MIMO signaling support will be defined later so that legacy LTE UEs should not be
affected.
 Alt3: SU-MIMO should be addressed in a future release (Nokia, Motorola, Nortel, T-
Mobile, Vodafone, Samsung, Ericsson, Siemens, Mitsubishi, TI, DoCoMo, Freescale,
Panasonic, ETRI, Sharp)
 The first release should at least be such that it should not preclude introducing uplink
SU-MIMO at a later stage
 Signaling support to be defined later (legacy LTE UEs should not be affected)
Conclusion:
SU-MIMO should be addressed in a future release.
○ The first release should at least be such that it should not preclude introducing uplink SU-
MIMO at a later stage
○ Signaling support to be defined later (legacy LTE UEs should not be affected)
Discussion on the support of 64QAM to be continued in the main session
○ Yes/No
○ If yes, mandatory or optional
46
6.8.2 SDMA
R1-070139 Hybrid ARQ for multi-user MIMO in E-UTRA uplink (Samsung)
R1-070199 UE Paring for E-UTRA Uplink Multiuser MIMO (ZTE)
6.8.3 Transmit Diversity

R1-070097 Performance Evaluation of Closed Loop-Based Antenna Switching Transmit
Diversity in E-UTRA Uplink (NTT DoCoMo)
R1-070392 Benchmarking of antenna switching and frequency hopping for LTE FDD UL
(Nokia)
R1-070448 Open-loop Adaptive Antenna Switching for UL MIMO (Nortel)
R1-070470 Antenna hopping for LTE uplink (Ericsson)
R1-070523 Comparison of closed-loop antenna selection with open-loop transmit diversity
(antenna switching within a TTI) (Mitsubishi Electric)
R1-070524 Comparison of closed-loop antenna selection with open-loop transmit diversity
(antenna switching between TTIs) (Mitsubishi Electric)
Conclusion:
Not specify the blind antenna switching/hopping in the standard.
Note: Adaptive antenna selection should be discussed as a part of scheduling of the spatial
resource (if needed), and hence the related contributions are recommended to be under UL MIMO
AI.
R1-070174 Performance Evaluation of SC-FDMA with STBC in E-UTRA Uplink

(Alcatel-Lucent)
Noted without presentation as the SU-MIMO discussion conclusion implies that only one PA will be available for
the UEs of the first LTE release.
6.9 Specification of Control Signalling

R1-070472 Uplink Control Signaling – Summary of e-mail discussions (Ericsson)
The output (way forward) from e-mail discussion was discussed and summarised as followed.
Downlink signalling
- The bandwidth of the downlink control channel is equal to the system bandwidth (i.e., the
bandwidth over which the reference signals can be transmitted in a cell)
Uplink signalling
- Transmission of ACK/NAK and CQI spans 1ms
- To handle coverage-limited situations, it should be possible to use the full 1 ms subframe for
control signalling before starting to repeat control signalling in multiple 1ms subframes, if
47
only one type of control signalling is to be transmitted in the subframe. This applies to
ACK/NAK and/or CQI
- Different UEs can be allocated on different frequency resources (FDM). Code-domain
multiple-access between UEs simultaneously transmitting control signaling (ACK/NAK
and/or CQI) on the same frequency resource.
o Each frequency resource is a multiple of 12 subcarriers (consisting of an upper
and/or a lower part with the slots of one subframe, upper and lower part are of equal
size if both upper and lower part are present). CDM would be used within the upper
and the lower part, respectively
- No data-associated uplink control signaling is used.
o RAN1 assumption is that Node B is not required to perform blind transport format
detection.
o Send an LS to RAN2 (R1-070601) to inform about this, and ask how VoIP will
operate from their view.
Discussion
As for downlink signalling, the discussion could reach to agreement with consensus, on the other hand, as for
uplink signalling, some concerns were raised on the three bullets proposed as way forward by R1-070472.
Non-data associated
As for the first billet (original), Brian Classon from Motorola commented that "simultaneously" is not clear so that
it should be made a clear. Stefan clarified it means that multiple uses the same T/F resources simultaneously and
then CDM code is allocated for at least one resources whatever it's located in lower and higher band. In addition,
the granularity for resources was discussed. Stefan Parkvall proposed "the frequency resources is [6] sub-carriers
considering the discussion so far, TI proposal, however Robert Love form Motorola raised a concern that should be
removed considering this could allow to allocate the control channel in the middle of resources block so that should
be replace "at least one resources. What TDM means was discussed with related to prior or after FFT. Aris
Papasakellariou commented we already multiplex data associated and non-associated control channel TDM manner
so that for multiplex ACK/NAK and CQI could be assumed after FFT. Stefan raised a objection that we don't have
any details at the moment on this point so that should not be captured
As for the second bullet (original), Sarah Boumendil commented that it described the case that ACK/NAK and CQI
are transmitted at the same time, but also we should addressed the case for only ACK.NACK.
As for the third bullet (original), the resource size allocated for control signalling was mainly discussed. For
capturing the proposal TI, "The frequency resources is 6 subcarriers" was proposed, however, Robert Love from
Motorola raised a concern that it could allowed to allocate the control channel in the middle of RB, not upper or
lower in RB so that he proposed it should be "The frequency resources is at least one resource block. Juan Montojo
from Qualcomm Europe commented on this issue that the discussion on this point is premature so that anything
should not be captured. Finally, some texts were added to resolve the concerns from Motorola.
In conclusion, it was decided to make more clear description with figure for make sure the output from the
discussion, in R1-070600.
R1-070600 Data-non-associated control signaling (Ericsson, Motorola, Qualcomm)

With related to frequency hopping, depending on frequency hopping scheme, it could not allowed to align to this
proposal but it's depend on the FH discussion so that it was clarified that this proposal does not preclude the
frequency hopping at the moment.
It was raised a concern that puncturing proposal seems to be a little bit drastic (complexity) and we can consider the
option where more RBs are allocated to control signalling. Stefan Parkvall clarified that the problem happens
mainly in case of narrow band so that there are enough RB on that case. It was clarified that how UE knows "K" is
that UE and Node B should know the same K with each other so that it would signal to UE via higher layer
signalling, i.e., RRC.
Decision: This document was endorsed in principle with modification in R1-070602
R1-070602 Data-non-associated control signaling (Ericsson, Motorola, Qualcomm)
Data-associated (No data-associated uplink control signaling is used?)
48
Joon Kui Ahn from LGE clarified their position with regards to NDI that if no NDI, there is no solution for
persistent scheduling so that such a scheduling would be removed although it very beneficial for VoIP.
Joonyoung Cho from Samsung commented that NDI is very useful, but if almost company think this decision is
good they would agree to the decision, but they would like to point out that persistent scheduling is very important.
Noriyuki Fukui from Mitsubishi commented that there is not solution for persistent scheduling without NDI at the
moment so that they would consider further this issue.
Sarah Boumendil from Alcatel-Lucent commented that they are not comfortable and they have an anxiety for Node
B complexity with regards to scheduling so that they proposed to consider more detail regarding uplink scheduling
with RAN2 impact before agreement.
Mieszko Chmiel from Siemens asked if "there is no data associated control signalling" means Node B must do
blind transport format detection. For making clear, the text was added.
Sadayuki Abeta from NTT DoCoMo commented that the scheduling scheme for VoIP is very important so that we
should ask RAN2 view for this RAN1 decision from point of VoIP operation.
Finally, it was clarified that the texts mean that NDI is not attached with data as well.
R1-070601 [DRAFT] LS on data-associated uplink control signalling (Ericsson)

Juho Lee, blind detection is not needed is premature, because no enough discussion. => This is reflected to
discussion. Sarah Boumendil also this information is very important so that this is the the next discussion for RAN1
and RAN2.
Decision: This draft LS was approved with revision in R1-070629
6.9.1 Uplink Control Signalling

General transmission structure
R1-070275 ACK/NAK Transmission without Reference Signal Overhead in E-UTRA
Uplink (Texas Instruments)
It was clarified by TI that this non-coherent scheme is just for ACK/NAK detection not also CQI.
Motorola and Joonyoung Cho from Samsung asked with concerns on the RB allocation and signalling OH
regarding the resource allocation to ACK/NAK between coherent and non-coherent method. Aris clarified that in
non-coherent case, 6 and 6 subcarriers for ACK/NAK and at the next 6 and 6 ACK./NAK as well so that no any
OH increasing.
It was commented with a concern on the CAZAC sequence assignment of this scheme.
R1-070437 Proposed structure for UL ACK and CQI (Qualcomm Europe)
There were some discussions on the two proposals with comparison. Aris Papasakellariou from TI commented
about their intention of their proposal that if one ACK/NACK slot passes away, it must be waiting through one
subframe and it causes to waste the resources. However, this point, Stefan and Kenichi Higuchi from NTT
DoCoMo commented that considering the other UEs, they don't think such a waste if assuming the same UE
multiplexed in one subframe.
In addition, the joint coding of ACK/NAK and CQI proposed by Qualcomm was discussed.
Regarding cat 0 proposed by TI, Juan Montojo from Qualcomm commented that category 0 would be cost so that
we would not have it. To this comment, Aris clarified that as shown in their contributions, it is for saving the
resources and it provides just benefit and not drawback.

R1-070031 E-UTRA Multiplexing of UL Control Signaling with Data (Motorola)
R1-070078 Non-coherent ACK/NACK signaling using code sequences as indicators in E-
UTRA uplink (ETRI)
49
R1-070100 CDM-based Multiplexing Method of Multiple ACK/NACK and CQI for E-

UTRA Uplink (NTT DoCoMo,
Fujitsu, KDDI, Mitsubishi Electric, Sharp, Toshiba Corporation)
R1-070101 Repetition of ACK/NACK in E-UTRA Uplink (NTT DoCoMo,
KDDI, Mitsubishi Electric, NEC, Panasonic, Sharp)
R1-070102 Performance Enhancement Techniques for ACK/NACK in E-UTRA Uplink
(NTT DoCoMo, KDDI, Mitsubishi Electric, Sharp)
R1-070205 Uplink non-data-associated control signaling (ZTE)
R1-070319 Multiplexing method for uplink non-data-associated control signals

(Alcatel-Lucent)
R1-070330 Uplink control channel multiplexing (Samsung)
R1-070361 Multiplexing for data-non-associated control signal in EUTRA uplink
(NEC Group)
R1-070393 ACK/NACK coverage in the absence of UL data (Nokia)
R1-070394 Multiplexing of L1/L2 Control Signals between UEs in the abcense of UL data
(Nokia)
R1-070395 CDM based Control Signal multiplexing w/ and w/o additional RS (Nokia)
R1-070521 CDMA based Multiplexing of ACK/NACK and CQI Control Information in E-
UTRA Uplink (KDDI, NTT DoCoMo)
R1-070162 E-UTRA UL L1/L2 Control Channel Mapping (Motorola)

Scheduling
R1-070098 Persistent Scheduling in E-UTRA(NTT DoCoMo, Mitsubishi Electric, NEC)
R1-070099 Frequency Domain Channel-Dependent Scheduling Considering Interference
to Neighbouring Cell for E-UTRA Uplink (NTT DoCoMo)
CQI
R1-070121 Description of UL L1/L2 control message (Huawei)
R1-070187 DCT partitioning for CQI reporting (Panasonic)
R1-070210 Further Evaluation of CQI feedback schemes (Mitsubishi Electric)
R1-070242 System level performance analysis between best-M and DCT based CQI
reporting schemes (LG Electronics)
R1-070331 CQI reporting for E-UTRA (Samsung)
R1-070362 Compressed CQI Reporting Scheme (NEC Group)
R1-070368 System level comparison of best-M and DCT-based CQI compression schemes
(Huawei)
R1-070396 Evaluation Method for Benchmarking CQI Schemes for LTE (Nokia)
R1-070397 CQI Design and its Impact to DL Performance (Nokia)
R1-070049 CQI feedback for E-UTRA (Motorola)
R1-070348 Control of CQI feedback signalling in E-UTRA (Philips)
MBMS
R1-070063 MBMS with feedback (Motorola)
R1-070471 Scheduling Request in E-UTRAN (Ericsson)
WIthdrawn
R1-070029 E-UTRA UL L1/L2 Control Channel Design (Motorola)
50
6.9.2 Downlink Control Signalling

General transmission structure
R1-070030 E-UTRA DL L1/L2 Control Channel Design (Motorola)
There was long discussion and clarification, and some companies raised concerns on this proposal regarding
scheduling problem, dependency on the system bandwidth (less flexibility), how to find ACK.NAK, granularity,
etc.

R1-070066 E-UTRA DL Coding Performance for Control Channel (Motorola)
R1-070079 Downlink L1/L2 control signaling (ETRI)
R1-070103 Downlink L1/L2 Control Channel Structure in E-UTRA - Bits and Coding
(NTT DoCoMo, Fujitsu, KDDI, Mitsubishi Electric, NEC)
R1-070186 Downlink L1/L2 control signalling: multiplexing, configuraiton and logical
receiver model (Panasonic)
R1-070278 Multiplexing of L1/L2 Control Channels in E-UTRA Downlink
(Texas Instruments)
R1-070314 Basic Multiplexing Schemes of Multiple L1/L2 Control Information in E-
UTRA Downlink (NTT DoCoMo)
R1-070332 Control Channel Structure for EUTRA Downlink (Samsung)
R1-070398 Structure and transport of the Downlink Control Channel (Nokia)
R1-070438 Proposed structure for DL ACK and PDCCH (Qualcomm Europe)
R1-070516 L1/L2 Control Channel Structure with CDM Based Multiplexing in E-UTRA
Downlink (KDDI, NTT DoCoMo)
Cat0
R1-070104 Downlink L1/L2 Control Channel Structure in E-UTRA - Mapping
(NTT DoCoMo, Fujitsu, KDDI, NEC, Sharp)
15/01/2007 15:20 Presented by Dr. Kenichi Higuchi from NTT DoCoMo
It was clarified by NTT DoCoMo that RB is logical RB in slide 12.
It was asked why the DL and UL control channels are allocated separately upper and lower band in the scheme in
the slide 12 and if UE monitor the both UE need to know UL or DL signalling in advance. It was answered by
NTT DoCoMo that the main purpose is to reduce the number of blind detection and if UE monitor both signalling,
the approach in slide 12 does not work.
It was commented on the number of bits for category 0 by TI that the more the number of bits for cat0, more easily
the blind detection is. NTT DoCoMo agreed to this view and commented that there is trade off between the
overhead of cat0 and overall signalling, at the moment they thinks 2 or 3 bits is enough but the further study could
be needed.
R1-070276 L1/L2 Control Channel Size and Cat0 in E-UTRA Downlink
(Texas Instruments)
Mr. Chairman suggested interested people discussing during this week about the open issue on control channel.

R1-070247 Downlink Cat0 signaling for scheduling assignments (LG Electronics)
R1-070034 Downlink Acknowledgement and Group Transmit Indicator Channels
(Motorola)
51
R1-070105 ACK/NACK Signal Structure in E-UTRA Downlink

(NTT DoCoMo, Fujitsu, NEC, Toshiba Corporation)
R1-070246 Downlink ACK/NACK transmission (LG Electronics)
R1-070277 ACK/NAK Channel Transmission in E-UTRA Downlink
(Texas Instruments)
R1-070517 Category 0 Information for TDM Based Multiplexing of L1/L2 Control
Signaling in E-UTRA Downlink (KDDI, NTT DoCoMo)

HARQ-related papers
R1-070141 Downlink Hybrid ARQ Signaling (Samsung)
R1-070244 Modification of Downlink asynchronous HARQ scheme (LG Electronics)
R1-070245 Modification of Uplink synchronous HARQ scheme (LG Electronics)
R1-070175 Reducing Transmission Control Signalling with Bit Correction (BC)
(ASUSTek)
Rotational OFDM
R1-070518 Scrambling Code for L1/L2 Control Channel with CDM Based Multiplexing in
E-UTRA Downlink (KDDI)
R1-070519 An Evaluation of the Rotational CDM for L1/L2 Control Channel
(KDDI, NTT DoCoMo)
R1-070520 System-Level Evaluation of the Rotational CDM for L1/L2 Control Channel
(KDDI)
TDD-aspects on control signaling
R1-070297 E-UTRA Downlink control signaling for TDD system (CATT, Huawei)
Other
R1-070035 Max #UEs/TTI for optimum E-UTRA DL performance (Motorola)
R1-070248 Consideration on the number of scheduled UEs in downlink (LG Electronics)
R1-070279 Maximum Number of Scheduled UEs per Sub-Frame in E-UTRA Downlink
(Texas Instruments)
R1-070032 Support of Precoding for E-UTRA DL L1/L2 Control Channel (Motorola)
R1-070140 Downlink Link Adaptation and Related Control Signaling (Samsung)
Encoding of resource assingment

R1-070036 E-UTRA DL L1/L2 Control Channel Information & RA map reduction
(Motorola)
R1-070211 Signaling Way of Resource Assignment (Mitsubishi Electric)
R1-070243 Downlink control signaling overheads (LG Electronics)
R1-070363 Signalling discontinuous localised allocations in E-UTRA downlink
(NEC Group)
R1-070364 Uplink Resource Allocation for E-UTRA (NEC Group, NTT DoCoMo)
R1-070410 Signaling Resource Allocations in DL Control Channel (Alcatel-Lucent)
R1-070450 Signaling Channel Designing for DL Adaptive MIMO (Nortel)
R1-070197 An Efficient UL resource allocation control signaling (ZTE)
Signaling-related issues
R1-070333 VoIP support in LTE (Samsung)
R1-070334 Discussion on control signalling for persistent scheduling of VoIP (Samsung)
R1-070399 Considerations on the False Positive Probability for the DL Shared Control
Channel (Nokia)
52
Withdrawn
R1-070033 E-UTRA DL L1/L2 Control Channel Design - Persistent Scheduling
(Motorola)
6.10 Physical Layer specification aspects of Link Adaptation

R1-070311 Aspects of DL HARQ in Frequency Selective Channels (Siemens)
R1-070439 Principles of Unicast Scheduling for Downlink and Uplink
(Qualcomm Europe)
R1-070511 Timing advance based resource allocation in half-duplex FDD
(Mitsubishi Electric)
6.11 UL Timing Control

R1-070045 E-UTRA UL Timing Control (Motorola)
18/01/2007 21:15 Presented by Dr. Rapeepat Ratasuk
It was commented and discussed what the benefit is by specifying to obtain the timing measurement. Also the
number of bits was discussed. Motorola commented that it depends on the update time and there is a trade off to
OH, they consider 3 or 4 bits.
R1-070106 Uplink Timing Control for E-UTRA
(NTT DoCoMo, Fujitsu, NEC, Panasonic, Sharp, Toshiba Corporation)
18/01/2007 21:30 Presented by Dr. Kenichi Higuchi
It was clarified by DoCoMo that 10 msec is just example and exactly it should be less that 1 sec.
Mieszko Chmiel from Siemens asked if the regular command are binary or multi-step and how many bits are. It
was answered by DoCoMo that they don't have any exact number but think multiple is beneficial considering the
flexible control.
R1-070281 Uplink Timing Control for E-UTRA (Texas Instruments)
Discusson on the number of bits. Qualcomm raised a strong concern.
R1-070531 Preferences for UL Timing Control (IPWireless)
18/01/2007 21:55 Presented by Mr. Nicholas Anderson
Mr. Chairman summarised a current status as followed and suggest e-mail discussion on the reflector before the
next meeting.
Current status of TA discussion in RAN1
When UE has previously established time alignment:

 TA update rate: on a per-need basis, at most 2 Hz
 Granularity of TA signalling: 0.52us
 1 step correction
 TA step size: X bits, relative to current UL timing
 What to base the TA command on:
53
o When the UE has data to transmit, implementation issue in NodeB (e.g. based
on sounding RS, CQI)
o If the UE has no data to transmit, FFS whether e.g. periodic signals such as
sounding RS may be ordered
o RACH?
 How to transmit TA in the DL: TBD whether L1L2, in-band (MAC or RRC)
When no TA is established or UE is out of sync

 TA update rate: on a per-need basis
 Granularity of TA signalling: 0.52us
 1 step correction
 TA step size: Y bits, relative to RACH preamble TX timing (Y may be larger than X and
depend on the cell size)
 What to base the TA command on:
o RACH
o Initial TA will have to cover the full range
 How to transmit TA in the DL: Confirm whether this is part of RACH procedure [in-band
(MAC)]

R1-070212 Physical Channel for Timing Synchronization (Mitsubishi Electric)
R1-070280 Uplink Synchronization management in LTE_ACTIVE
(Texas Instruments)
R1-070282 Timing Advance Accuracy from Non Synchronized Random Access in E-
UTRA (Texas Instruments)
R1-070308 Considerations on E-UTRA Uplink Time Synchronization (Siemens)
R1-070320 E-UTRA UL Timing Control (Alcatel-Lucent)
R1-070321 Considerations for frequency control in E-UTRA uplink (Alcatel-Lucent)
R1-070335 Uplink timing control (Samsung)
R1-070400 UL Timing Accuracy and Update Rate (Nokia)
R1-070440 Timing control (Qualcomm Europe)
R1-070474 Timing advance for E-UTRA uplink (Ericsson)
6.12 UL/DL Power Control

R1-070402 Power Control Email Discussion Summary (Nokia)
18/01/2007 22:45 Presented by Mr. Jari Lindholm
Regarding slow ro fast power control, it was discussed how faster the slow and fast power control. It was consensus
among the interested parties that slow power control" is understood as in order of 100Hz, "faster power control" is
understood as in the order of 1000Hz. In order to make clear for the slow power control, it was defined as not faster
than 200Hz. NTT DoCoMo accepted it even though they proposed more than 500Hz in their contribution
As the points for agreed conclusion, Christian G. Gerlach from Lucent Alcatel proposed their view that a small
dynamic power offset being part of the scheduling grant can adjust the PSD in addition to the "slow power control
". Also Youn Heo from Samsung proposed by a small power offset by a higher layer signaling. However, they
proposals could not be in consensus so that they were listed as further issues. Finally, three points was agreed as
followed and the other issues were left for the further discussion on the email reflector.
Conclusion on power control
54
- Basic power control mechanism: Slow power control (not faster than 200Hz, with
a-periodic PCD updates (FFS whether a-periodic PSD updates will be agreed)
the power control rate may temporarily be higher than 200Hz)
- PSD is controlled
- Pure open loop UL power control only (i.e., without adjustments made by the
network) is not sufficient
Further issues to discuss

- FFS Whether additional mechanism(s) will be defined to update the PSD
- For TDD fast PC should not be precluded (if it comes "for free")
- If the bandwidth allocation of the UE is changed, is the power or PSD kept constant?
- PC scheme: TBD closed loop or open loop (with adjustable parameters)
- In the proposed scheme what should be standardized (signaling, algorithm…)?
- Should the PC scheme for data and control be same or different?
- UL PC dynamic range, granularity, update frequency

R1-070038 UL Power Control for E-UTRA (Motorola)
R1-070039 DL Power Control for E-UTRA (Motorola)
R1-070040 DL Power Allocation for Dynamic Interference Avoidance in E-UTRA
(Motorola)
R1-070043 Performance comparison of UL Power control methods (Motorola)
R1-070069 Power Control in uplink LTE (Freescale Semiconductor)
R1-070107 Transmission Power Control in E-UTRA Downlink (NTT DoCoMo,
Fujitsu, Mitsubishi Electric, NEC, Sharp, Toshiba Corporation)
R1-070108 Transmission Power Control in E-UTRA Uplink (NTT DoCoMo,
NEC, Panasonic, Sharp, Toshiba Corporation)
R1-070109 Investigations on Inter-cell Transmission Power Control based on Overload
Indicator in E-UTRA Uplink
(NTT DoCoMo, NEC, Panasonic, Sharp, Toshiba Corporation)
R1-070166 Combined Open Loop/Closed Loop Uplink Power Control with Interference
Mitigation for E-UTRA (InterDigital)
R1-070167 System Performance Evaluation of Combined Open Loop/ Closed Loop Uplink
Power Control for E-UTRA (InterDigital)
R1-070250 Downlink Transmit Power Boosting (LG Electronics)
R1-070251 Power control of uplink shared data channel (LG Electronics)
R1-070283 Downlink Power Control for E-UTRA (Texas Instruments)
R1-070284 Fractional Time Re-Use Interference Co-Ordination in E-UTRA Downlink
(Texas Instruments)
R1-070285 Uplink Power Control for EUTRA: Optimizing the Trade-off between Cell-
Edge and Cell-Average Throughputs (Texas Instruments)
R1-070322 Fractional Power Control using Pilot Power Ratio Measurements for the E-
UTRA Uplink (Alcatel-Lucent)
R1-070339 Discussion on uplink power control (Samsung)
R1-070366 UL Power Control (Siemens)
R1-070401 UL Power Control (Nokia)
R1-070409 Power Setting for Interference Coordination including Pilot and Control
Channels (Alcatel-Lucent)
55
R1-070611 Power Setting for Interference Coordination including Pilot and Control
Channels (Alcatel-Lucent)
R1-070441 Overview of Uplink Intra and Inter Cell Power Control
(Qualcomm Europe, NTT DoCoMo)
R1-070442 Inter-cell interference control (Qualcomm Europe)
R1-070443 Uplink Power Control Simulations – Mobility in Urban Canyons
(Qualcomm Europe)
R1-070459 Further Discussion on Adaptive Fractional Frequency Reuse (Nortel)
R1-070475 Intra-cell Uplink Power Control for E-UTRA – Proposed Mechanism
(Ericsson)
R1-070476 Intra-cell Uplink Power Control for E-UTRA – Control Channel Performance
Evaluation (Ericsson)
R1-070477 Intra-cell Uplink Power Control for E-UTRA – Traffic Channel Performance
Evaluation (Ericsson)
R1-070478 Inter-cell Uplink Power Control for E-UTRA (Ericsson)
R1-070530 Uplink Power and IoT Control Method: Description and Simulation Results
(IPWireless)
Withdrawn
R1-070206 Assistant Feedback Channel for E-UTRA TDD Uplink Transmission Power
Control and AMC (ZTE)
6.13 Physical Layer Measurements

R1-070044 E-UTRA Measurements Related to Mobility (Motorola)
R1-070403 UTRA Measurement Quantity Selection (Nokia)
R1-070404 Initial simulation results comparing different E-UTRA UE DL measurement
quantities (Nokia)
R1-070479 Physical Layer Measurements in E-UTRAN (Ericsson)
E-mail discussion on measurement to be held (moderator: Mr. Dirk Gerstenberger)
Withdrawn
R1-070082 Interworking between LTE and GSM - Monitoring GSM from LTE
(Siemens)
56
7. HSPA Evolution
The overview of discussions and conclusions on this topic is as followed.
1. MIMO in UTRA
- Working assumption for HS-SCCH part 1 structure for MIMO and 64QAM was agreed in R1-070570
- The principle for ACK/NACK power setting from R1-070180 was agreed.
- The CR regarding CQI reporting was endorsed in R1-070571
- As for CQI/PCI coding scheme, it was agreed as way forward that Continue work on selecting CQI/PCI
coding scheme based on 10 base vectors, focusing on a (20.10) code and a (20, 7) sub-set code. Agree on
codes to be evaluated during the week after the meeting and present simulation results until one week
later.
2. Continuous Connectivity for Packet Data Users
- Regarding interaction of CPC and Compressed Mode, it was agreed as way forward to continue work to
include the principle outlined in R1-070352 in a separate set of CRs for CPC. Concerns on operation
with relevant compressed mode patterns from 25.133 should be raised until 2 weeks after this meeting.
The summary was captured in R1-070615.
3. Higher Order Modulation for HSDPA and USUPA (FDD)
- It was agreed as way forward of 64QAM for HSDPA that
o Update the set of RAN1 CRs according to the discussion on R1-070572 as the baseline, CoRe
and RV table review at next meeting whether CoRe should be applicable to Chase/IR, and
whether 16QAM RV table is used for 64QAM.
o HS-SCCH: Solve with the discussion on MIMO and MIMO+64QAM during this week
o HS-DPCCH: New CQI tables for the new UE categories (same number of CQI values as for
16QAM)
 proposals 1) from R1-070497 uses equal sized steps of 1.5dB, 2) 1dB + offset, 3) two
step size values for low and high SNR respectively
- It was agreed as way forward of 16QAM for HSUPA that from the discussion on the three proposal
pilot power enhancements, the concern on E-DPCCH boosting was with respect to delay and processing
in the Node B (this should be checked within the concerned companies). Discussion whether to use one
of the three proposed solutions and if so, which, should take place on the e-mail reflector within two
weeks after this meeting. Consider outcome of this discussion for the beta factor specification
- The set of CRs for 64QAM/HSDPA and 16QAM/HSUPA were agreed as baseline for further
discussion.
4. Enhanced FDD Cell FACH
- It was agree as way forward to continue the work based on HSDPA in cell FACH. FFS until next
meeting whether HS-SCCH can be reduced.
5. Review of MBMS Physical Layer Enhancement Work Item Sheet
- Proposal for Work Item for MBMS FDD Physical layer Enhancements is agreed in R2-070395.
Concerns were stated by some companies on the feasibility of the finalization dates.
- Proposal for Work Item for MBMS TDD Physical Layer Improvements is agreed in R2-070394.
Concerns were stated by some companies on the feasibility of the finalization dates.
7.1 MIMO in UTRA (Rel-7 Work Item)

HS-SCCH
R1-070179 HS-SCCH structure for MIMO and 64QAM (Nokia)
Bo Göransson commented that more than 60 combinations (exactly 65) has much cost.
Mr. related to
57
R1-070535 HS-SCCH structure for MIMO and 64QAM (Ericsson)

16/01/2007 09:20 Presented by Dr. Bo Göransson
Josef Blanz (Qualcomm) commented that this approach that restrict combination is very straightforward way and
very clear but combination of 64QAM and QPSA would be one beneficial for some case, e.g., considering the
linear receiver so that it might cause some penalty for the some constructing case. Bo commented that yes they
agree to this issue and we could see the limitation on the some case so that we intend to see the penalty by
simulation. Karri Ranta-aho from Nokia commented that it's good way as it's the modification of Nokia proposal
and erasing the combination of QPSA and 64 QAM can providing the save the cost.
It was clarified by Ericsson that number of bits for HS-SCCH Part 1 is 11 bits in case of MIMO and full 64 QAM
R1-070350 HS-SCCH for MIMO and 64QAM (Philips)
R1-070537 HS-SCCH for MIMO and 64QAM (Philips)
16/01/2007 09:35 Presented by Mr. Matthew Baker
Vincent Belaiche form Renesas Technology pointed out .the reliability of the reception of HS-SCCH considering
that the current restriction to receive one single HS-SCCH after the first schedule makes the HS-SCCH detection
more reliable. It was commented back that this restriction was actually not made for reliability reasons, but in order
to alleviate the UE workload during HS-PDSCH reception
Rainer Bachl from Alcatel-Lucent asked if there are any impacts on the number of HS-SCCH monitor. The answer
was that there is no impact and no any different number from Rel-6.
Sarah Boumendil from Alcatel-Nortel asked if, the proposal has code sharing for the HS-SCCH with Rel-5, 6 or
setting up the separate the channelisation. It was commented by Philips that nothing prevent from the old type and
new type formant, setting.
Mr. Chairman asked if there are any impacts on the CPC type the power saving considering the continuous
monitoring the HS-SCCH. It was clarified by Philips that it doesn't have to monitor longer and no impact on DRX
such as CPC type.
Summarising from above documents
- 11bits for part 1 (with MIMO)
R1-070351 HARQ process handling for Rel-7 FDD MIMO (Philips)

R1-070494 HARQ process signaling for UTRA MIMO (Ericsson)
Josef Blanz (Qualcomm) commented on the performance impact that the restriction on HARQ scheduling is quite
difficult because nobody investigate it form performance perspective and we could not know the performance
impact on this point and he showed Qualcomm view that we would not touch on HARQ process.
Summarising from the discussion on above documents
- No restriction in HARQ scheduling to the different streams (4 bits per stream)
- NDI+RV: 4bits (2 streams), 2bits (1 stream)
- 4 bits for HARQ process ID for single stream MIMO
R1-070024 64QAM in HSDPA - Modulation Format Indication (Motorola)

R1-070568 64QAM in HSDPA - Modulation Format Indication (Motorola)
16/01/2007 10:25 Presented by Dr. Charlie Zhang
Juho Lee from Samsung raised a concern on the switching point of modulation,16 and 64 QAM considering the
performance impact. It was answered by Carlie Zhang that yes we don't intend to switch randomly and we need to
investigate the optimum points and they will show that in further contribution.
It was commented that in the change for the table in the specification, which is formative and informative, then just
formative should be modified.
58

It was discussed about the modulation information. Nokia commented that as Nokia position they think the
complete information for modulation is needed. Qualcomm commented that it's could be possible that information
is moved to part 2 and be joint cording of part 1 and 2 but we need to consider the some complexity so that at the
moment we should be stick to split part 1 and 2.
Mr. Chairman commented that more discussion offline and come back to Friday with related part to RAN2.
Resolve the remaining issues offline until Friday, R1-070570 for a proposal.
R1-070570 Way forward for HS-SCCH part 1 structure for MIMO and 64QAM
(Philips, Nokia, Ericsson, Qualcomm, Motorola)
19/01/2007 16:40 Presented by Mr. Matthew Baker from Philips
Decision: This working assumption was agreed. It was confirmed that HS-SCCH orders as defined in the CPC CRs
are independent from this proposal.
HS-DPCCH
R1-070180 ACK/NACK transmission in MIMO Mode (Nokia)
It was commented on the handover case behaviour of the dual ACK.NACK sending, but anyway it's a small detail
and all interested companies agreed this power setting in principle.
Decision: The principle of ACK/NACK power setting in this contribution is agreed.
R1-070181 CQI Report for WCDMA MIMO, Revised Proposal (Nokia)
Josef Blanz from Qualcomm commented that this scheme has too much restriction especially for two streams case
as described more details in their document.
R1-070495 On CQI for UTRA MIMO (Ericsson)
R1-070513 CQI reporting for FDD MIMO (Qualcomm Europe)
16/01/2007 12:15 Presented by Dr. Josef Blanz
Bo Göransson from Ericsson commented as for the power updating that actual power allocation seems to be
roughly. Josef clarified that that is the fundamental problem for MIMO and not special for this case. It was
discussed how large dynamic range for data rate should be supported and Josef commented that lower end rate is
also important.
Resolve the remaining issues offline until Friday, Tdoc R1-070571 for a proposal.
R1-070571 CQI reporting for FDD MIMO (Qualcomm Europe, Ericsson)
Decision: The CR in this document was endorsed, final details to be agreed in next meeting.
R1-070349 Block codes for CQI reporting for Rel-7 MIMO (Philips)
R1-070557 Proposed for block code for CQI/PCI reporting for Rel-7 MIMO including
25.212CR0242r6 (Philips)
It was commented that considering the selecting the modulation and coding scheme the proposed generator matrix
is not in general good for the overall system case
Matthew Baker clarified that they don't say this code is the necessary code at the moment and we need more
investigations for come to conclusion. Mr. Chairman also mentioned it's our way forward so that the CR is just
noted at the moment.
59
Decision: This document and CR were noted.

R1-070493 FEC Coding of type-B CQI / PCI Information (InterDigital)
R1-070567 FEC Coding of type-B CQI / PCI Information (InterDigital)
16/01/2007 14:30 Presented by Mr. Eldad Zeira
It was clarified by InterDigital that they propose either UPE or EEP.
The selection of coding scheme was discussed based on the proposed document, R1-070567 and R1-070349.
Matthew Baker from Philips commented that if we constrain the coding scheme 20.7 could be selected, but if not,
both 20.10 and 20.7 would be allowed.
Josef Blanz from Qualcomm commented that from the procedure point of view we need keep in mind the small
number of options so that we need to evaluate the selecting coding scheme.
Way forward
Continue work on selecting CQI/PCI coding scheme based on 10 base vectors, focusing on a (20.10)
code and a (20, 7) sub-set code. Agree on codes to be evaluated during the week after the meeting and
present simulation results until one week later.
R1-070512 Draft answer LS on status of Rel-7 FDD MIMO (Qualcomm Europe)

16/01/2007 15:10 Presented by Dr. Josef Blanz
From the operator view point, the following sentence was added.
"RAN1 would like to add that MIMO is expected to operate in regions with higher SNR, hence the increased power
requirement is not seen as critical with respect to HS-SCCH coverage or HS-PDSCH capacity."
Tim Frost (Vodafone) suggested that RAN4 should be copied regarding to TF format
Decision: This draft LS was approved with revision in R1-070578
Not treated
R1-070514 25.214 CR0430r4 (Rel-7, B) "Definition of MIMO operation on HS-PDSCH,
preferred precoding and CQI reporting procedures, modified CQI tables"
(Qualcomm Europe)
R1-070529 25.212 CR0242r4 (Rel-7, B) "Coding of HS-DPCCH to support operation of
FDD MIMO" (Qualcomm Europe)
Decision: This topic on two CRs is still working so that CRs was not treated at this moment.
Withdrawn
R1-070323 PCI_CQI Definition for Rel-7 MIMO (Huawei)
R1-070515 25.212 CR0242r4 (Rel-7, B) "Coding of HS-DPCCH to support operation of
FDD MIMO" (Qualcomm Europe)
R1-070538 Proposed for block code for CQI/PCI reporting for Rel-7 MIMO including
25.212CR0242r5 (Philips)
7.2 Continuous Connectivity for Packet Data Users
Compressed mode
R1-070183 Compressed Mode with CPC (Nokia)
It was clarified by Nokia that we don't need any update on the endorsed set of physical layer CRs and the
modification on this proposal could be taken in MAC and RRC. No measurement gap change and same as R99.
This proposal is for both TTI, 2 and 10 ms.
60

R1-070352 Continuous Packet Connectivity in conjunction with Compressed Mode
(Philips)
Sarah Boumendil from Alcatel-Lucent commented that in case of 10ms case it is not possible to transmit the
signalling related to mobility during the overlap period but as the mobility still continue it is important that a kind
of mobility information would be transmitted. Philip agreed to this point and it is important to transmit the mobility
information quickly.
It was clarified that the proposal is exactly same as Rel-6 from MAC perspective. Sarah asked what the behaviour
is in 10ms. It was answered by Philips that it would be exactly CPC mode and the only change here is additional
restriction on the CPC pattern.
R1-070421 Proposed operation of CM equivalent behaviour using CPC
(Qualcomm Europe)
Sarah Boumendil from Alcatel-Lucent commented that Philips proposal would be direct proposal but she has still a
little wonder on the operation on CPC and CM overlapping from UE perspective so that they need a couple of time
for the further confirmation. In addition, she pointed out that we have 25.133 (RAN4) performance req. for CM in
25.133(RAN4) and if keeping the current CM parameters it could impose the restriction on CPC activity. Matthew
Baker from Philips expressed his wonder to her comments that we can see the nice joint optimization in Qualcomm
proposal and in that case, no change for CM mode parameters.
Sarah commented again that she could understand no impact on the CM operation but not be sure what the
modification for the CPC operation is and channel estimation performance might be degraded so that we would
have some time to check the details. So she proposed to keep the current text at the moment, that is, CPC mode
switched off on CM mode and she clarified her company position that they are not opposite to Philips proposal but
just need checking for more confirmation.
Vincent Belaiche expressed the same wonder as Sarah and would like to clarify whether it keep the minimum duty
cycle as same as normal CPC. Matthew Baker commented that NW has ability to choose the parameter depending
on the mode, CPC only and CPC and CM.
Taking this situation Joern Krause from Siemens proposed the e-mail discussion CRs based on the Philips proposed
and he pointed out the impact on the other WSG, RAN2 RAN3 signalling should be checked as well
Way forward:
Continue work to include the principle outlined in R1-070352 in a separate set of CRs for CPC.
Concerns on operation with relevant compressed mode patterns from 25.133 should be raised until 2
weeks after this meeting.
R1-070615 Summary of conclusions on interaction of CPC and CM (Philips)

Decision: This document was noted on the e-mail reflector after the meeting.
R1-070016 Improved HS-SCCH order signalling for CPC (Renesas Technology)

16/01/2007 18:00 Presented by Mr. Vincent Belaiche
It was commented that this is not compatible to the current agreement on part 1, 11bits in the morning on that day.
Mr. Chairman clarified that we have still some time to complete all Rel-7 CR (until March 2007)
Decision: This document was noted and it was confirmed that it may be considered at the next meeting once the
HS-SCCH solutions for 64QAM and for MIMO are agreed.
R1-070182 UL DPCCH transmission with HS-DPCCH during DPCCH gating (Nokia)
It was clarified by Nokia to assume the perfect estimation for both cases in the simulation. Serge Willenegger from
Qualcomm proposed to have a time for more confirmation before including in CR.
Decision: It was decided to be included in the CRs for CPC unless concern is raised by Friday. On the offline
discussion among interested parties during the week, Qualcomm raised a concern that they would prefer not include
the proposal in R1-060182 in the CPC CR.
61
R1-070353 Text proposal for Continuous Packet Connectivity Clarifications (Philips)

Some editorials were pointed out and also the detail monitoring operation on the point 7 in section 6C.7.
Decision: It was decided to revisit the text according to comments from the discussions in R1-070580
R1-070580 25.214 CR0421r9 (Rel-7, B) "Support of CPC feature"
(Philips, Siemens, Ericsson, Nokia, Qualcomm)
Decision: E-mail approval until Friday in next week, 26th January. After the meeting, Nokia proposed a
modification of R1-070580, however, the discussion on the e-mail reflector could not reach to agreement. So the
agreement of this CR needs to come back again during the next meeting in St. Louis.
R1-070324 Synchronization criteria during discontinuous transmission (Huawei)
16/01/2007 18:30 Presented by Mr. Zongjie Wang
It was clarified by Huawei that all alternatives could be configurable but the first one is better.
It was commented that there might be the reliability issue on this proposal and also need the observation on the
endorsed existing CRs.
Decision: It was decided to discuss until next meeting whether anything should be changed relative to the existing
set of CRs for the synchronization criteria.
R1-070496 On Synchronization and Mobility with CPC (Ericsson)
It was suggested to check RAN2 impact.
Decision: It was decided to continue discussion offline during the week and if appropriate, draft an LS proposal to
RAN2 in R1-070581
R1-070581 Draft LS to RAN2 On Synchronization and Mobility with CPC (Ericsson)
Decision: E-mail approval until Friday in next week, 26th January. This draft LS was approved in R1-070634 on the
e-mail reflector.
7.3 Higher Order Modulation

7.3.1 64QAM for HSDPA(FDD)
R1-070025 64QAM in HSDPA - Necessary Changes to Specifications (Motorola)

R1-070572 64QAM in HSDPA - Necessary Changes to Specifications (Motorola)
Siemens commented that it's a good proposal, especially in, constellation re-arrangement
R1-070497 Introduction of 64QAM for HSDPA (Ericsson, Qualcomm Europe)
Johan clarified that the differences form Motorola proposal are constellation arrangement, RV coding, UE
categories and HS-SCCH points, but they are not much controversial to this proposal.
R1-070313 Proposal for Constellation Rearrangement for 64-QAM (Siemens)
R1-070541 Proposal for Constellation Rearrangement for 64-QAM (Siemens)
Siemens supported to Motorola proposal, meaning not proposing the arrangement on this document.
R1-070522 On the HARQ Options for 64QAM for HSDPA (Ericsson)
62
Siemens commented that the constellation rearrangement is beneficial in case of higher coding rate in IR version.
Motorola expressed a wonder and concern on adding the more IR version.
R1-070325 HSDPA UE categories (Huawei)

R1-070326 Coding for HS-DSCH to support 64QAM (Huawei)
R1-070198 Some considerations about 64QAM for HSDPA (ZTE)
16/01/2007 19:40
It was commented that modulation scheme mapping should be discussed on the HS-SCCH offline discussion for
MIMO and 64QAM. Motorola showed a wonder that transmission format on 1 and 2 transmission when 1st
transmission wrong
R1-070498 25.201 CR0026 (Rel-7, B) "Introduction of 64QAM for HSDPA"

(Ericsson, Qualcomm)
This CR was revised before the presentation according to the discussion on the corresponding documents.
R1-070582 25.201 CR0026r1 (Rel-7, B) "Introduction of 64QAM for HSDPA"
(Ericsson, Qualcomm, Motorola, Philips)
Decision: E-mail approval until Friday in next week, 26th January. This CR was agreed as baseline on the e-mail
reflector after the meeting.
Decision: E-mail approval until Friday in next week, 26th January. This CR was revised in R1-070635 on the e-mail
reflector.
Decision: This CR was agreed as baseline on the e-mail reflector after the meeting.
63
R1-070587 Open issues for Higher Order Modulation for HSPA (Ericsson)
Decision: This document is information
Way forward:
- Update the set of RAN1 CRs according to the discussion on R1-070572 as the baseline, CoRe and
RV table review at next meeting whether CoRe should be applicable to Chase/IR, and whether
16QAM RV table is used for 64QAM.
- HS-SCCH: Solve with the discussion on MIMO and MIMO+64QAM during this week
- HS-DPCCH: New CQI tables for the new UE categories (same number of CQI values as for
16QAM)
o proposals 1) from R1-070497 uses equal sized steps of 1.5dB, 2) 1dB + offset, 3) two step size
values for low and high SNR respectively
7.3.2 16QAM for HSUPA(FDD)

R1-070026 Further Link Simulation Results of Higher Order Modulations in HSPA
Uplink (Motorola)
R1-070027 HSUPA 16QAM Inclusion - Modulation Selection (Motorola)
It was clarified by Motorola that two modulation format is implicitly informed.
R1-070185 16QAM link results (Nokia)
R1-070534 Further Cubic Metric Results for 16QAM for HSUPA (Ericsson)
Regarding Reference phase part, it was clarified that offset is 9.5 dB based on just calculation.
Summarising the above proposals
Use SF 2xSF2+2xSF4 only
R1-070503 Introduction of 16QAM for HSUPA (Ericsson, Qualcomm)

It was clarified by Ericsson regarding the difference from Motorola proposal that the coding is not updated but the
table for E-DPCCH should be updated.
R1-070509 Bit Mapping for 16QAM for HSUPA (Ericsson)
Charlie from Motorola commented that they support to alternative1 but should be more evaluated so that this would
be baseline and the interested parties would provide the simulation for the upcoming meeting. Nokia supported
alternative 1.
Decision: This document was noted. It was confirmed that baseline is no CoRe and the proposed RV mapping
(better proposal on RV can of course be accepted if provided)
R1-070354 Pilot power setting for 16QAM in uplink (Philips)
Johan Bergman from Ericson mostly agreed to this document, however he expressed his concern on one point and
pointed out that EDPCCH decoding error is not major error so that the final proposal DPCCH boosting) could not
be approved .
64
Charlie Zhang from Motorola raised a concern on E-DPCCH approach that it could cause the delay and some
problem processing in the Node B.
R1-070414 Analysis of E-DPDCH with 16QAM (Qualcomm Europe)
Motorola commented that boosting could provide the performance improvement but it's not mandatory function but
can do without.
R1-070415 Enhanced Phase Reference for 16-QAM (Qualcomm Europe, Ericsson)
Mr. Chairman summarised the discussion on the pilot power enhancements that now three different approaches were listed
for boosting more pilot power as a good stating point so that we continue discussion to agreement. Charlie Zhang from
Motorola commented that the pilot boosting is beneficial for performance improvement but not necessity and we can do
without. Juan Montojo from Qualcomm commented that as shown their contributions, E-DPCCH approach has less
concerns than the other approach so that it would be a reasonable proposal for enhanced phase reference approach. To this,
Matthew Baker from Philips commented that they could accept to this choice although they proposed the other way as the
best approach.
To narrow down approach, it was proposed that at the moment we can agreed the boosting is needed even though the
selection of best approach is on the next phase, however, Rainer Bachl from Alcatel-Lucent raised a concern on the
agreement that we have not had any evidence that if not boosting any loss could be. So finally, Mr. Chairman summarized
the current situation and proposed the following way forward. In addition, he clarified on this WI (16QAM for HSUPA)
that WID described that the corresponding CRs from RAN1 should be available on RAN#35, it means that we should
endorsed the RAN1 set of CRS technically until March.
Summarizing on discussion (Chairman's note)

From the discussion on the three proposal pilot power enhancements, the concern on E-DPCCH boosting
was with respect to delay and processing in the Node B (this should be checked within the concerned
companies). Discussion whether to use one of the three proposed solutions and if so, which, should take
place on the e-mail reflector within two weeks after this meeting. Consider outcome of this discussion for
the beta factor specification
The following set of CRs are updated according to the discussion as a baseline for further work.
R1-070504 25.201 CR0027 (Rel-7, B) "Introduction of 16QAM for HSUPA"
This CR was revised before the presentation according to the discussion on the corresponding documents
R1-070588 25.201 CR0027r1 (Rel-7, B) "Introduction of 16QAM for HSUPA"
65

R1-070593 Further Cubic Metric Results for 16QAM for HSUPA (Ericsson)
R1-070620 Eb/N+ gain with E-DPCCH boosting (Qualcomm Erurope)
Withdrawn
R1-070510 E-DPCCH Aided Channel Estimation for 16QAM for HSUPA
(Ericsson)
7.4 Enhancement FDD cell FACH

R1-070028 Further Analysis of Enhanced CELL_FACH (Motorola)
R1-070080 Comparison of the proposals for enhancing CELL_FACH state
(Siemens)
R1-070327 Transmission Control in Enhanced CELL_FACH State (Huawei)
17/01/2007 09:20 Presented by Mr. Zongjie Wang
Charlie Zhang from Motorola commented that this proposal seems to be interesting but if do that, UE has to know
the follow up message and the loss of scheduling flexibility could be loss. Karri Ranta-aho from Nokia expressed a
wonder on the proposal as well.
Way forward:
Continue the work based on HSDPA in cell FACH. FFS until next meeting whether HS-SCCH can be
reduced.
7.5 Review of MBMS Physical Layer Enhancement Work Item Sheet

This agenda was discussed with RAN2 on Wednesday evening. Regarding the details on
discussion, please see the minutes of RAN2#56bis meeting, subclause 10.1. The following
decision was captured from RAN1 Chairman's note.
WIDs from RAN#34:

RP-060857 Proposal for Work Item for MBMS FDD Physical layer Enhancements
66
(Document 780 was approved in principle, in RP-060857. Working groups were tasked to review the completion
dates and the scope. Completion dates will be set in brackets in the sheet with tbd added afterwards.)
Original WID in 857 was updated during the discussion and the revised version is agreed in R2-070395. Concerns
were stated by some companies on the feasibility of the finalization dates.
RP-060858 Proposal for Work Item for MBMS TDD Physical layer Enhancements
(Document 781 was approved in principle, in RP-060858. Working groups were tasked to review the completion
dates and the scope. Completion dates will be set in brackets in the sheet with tbd added afterwards)
R1-070485 TDD MBMS Physical Layer Enhancements: Overview and Impact to RAN1
Specifications (IPWireless)
R2-070040 MBMS TDD Physical Layer Improvements IPWireless
Original WID in 858 was updated during the discussion and the revised version is agreed in R2-070394. Concerns
were stated by some companies on the feasibility of the finalization dates.
RP-060779 Proposal for Work Item for MBMS Protocol Enhancements

(The WI proposal was postponed. This will be rediscussed in RAN WG2)
R2-070201 Update of MBMS Protocol Enhancements WI LG Electronics Inc.
No impact on RAN1 is foreseen.

R1-070328 Enhanced multi-cell transmission for Mixed carrier MBMS (Huawei)
R1-070329 Enhanced Multi-Cell Transmission for Mixed carrier MBMS - Link level
simulation (Huawei)
R1-070486 Support for MBSFN operation: draft CR 25.221 (IPWireless)
67
8. 1.28Mcps TDD Enhanced Uplink

The overview of discussions and conclusions on this topic is as followed.
- It was agreed that there is benefit with longer TTI, but it is not proposed to include 20ms TI in this WI
and capture this also in the TR with a text proposal in R1-070595
- The text proposal as for Coding of E-DCH and UE capability was endorsed to be captured in TR25.827.
- The latest TR25.827 v.1.1.0 in R1-070636.
R1-070176 20ms TTI Co-existence with 5ms TTI for E-DCH of LCR TDD：Further
Revised System Level Simulation Results (ZTE)
R1-070303 Simulation Results of 20ms TTI and 5ms TTI for LCR TDD E-DCH
(CATT)
Decision: This document was noted without presentation. On the offline discussion, it was agreed that there is
benefit with longer TTI, but it is not proposed to include 20ms TI in this WI and capture this also in the TR with a
text proposal in R1-070595
R1-070595 Text proposal for 20ms TTI conclusion for LCR TDD EUL (ZTE, CATT)
Decision: E-mail approval until Friday in next week, 26th January. This TP was agreed to be included to TR after
the meeting.
R1-070299 Transport Block Size Signalling for 1.28Mcps TDD EUL (CATT)
Decision: This document is related to ongoing RAN2 discussion, and it was decided to discuss this via e-mail
reflector after RAN2 has discussed the topics. During the week, RAN2 had progress so that the following LS was
prepared.
R1-070613 LS on Transport Block Size Signalling for 1.28Mcps TDD Enhanced Uplink
(CATT)
19/01/2007 17:00 Presented by Mrs. Xueyuan Gao
R1-070298 LCR TDD: Structure and Coding for E-HICH (CATT)

17/01/2007 08:10 Presented by Mr. Ke Wang
R1-070406 Text Proposal for E-HICH/E-AGCH structure and coding for 1.28Mcps TDD
EUL (TD-Tech)
17/01/2007 08:15 Presented by Mr. Yonghong Chang
The comparison between two proposals was discussed.
Mr. Chairman and Nicholas Anderson from IPWireless commented the proposal from R1-070298 is more similar to
high chip rate TDD, on the other hand, the proposal on the 406 is a new structure so IPWireless supported R1-
070298 for harmonizing with high chip rate.
ZTE raised a concern on SS command.
CATT commented that considering time schedule, they propose the proposal from R1-070298 as the baseline,
however, TD-Tech raised a concern that we also consider a technical issue for conclusion in addition to time
schedule so they propose the further evaluation based on two proposals with sight of combining of two proposals
before finalizing this issue.
Nick pointed out that the main issue seems to be how to convey SS and TPC commands for non-scheduled users
(i.e. those without an E-AGCH grant channel). He reminded that the PLCCH already exists to carry TPC/SS in
Rel-7 so there should be no problem.
Decision: This document was noted. It was decided to continue discussion based on two proposals via e-mail; and
decide latest at next meeting.
R1-070300 Text Proposal for TR 25.827 (CATT)
17/01/2007 08:40 Presented by Mr. Ke Wang
68

ZTE and TD-Tech raised a concern on the compatibility to PLC RRC regarding Random access procedure so that
they proposed the further evaluation. CATT commented that they have no strong opinion on RACH procedure so
they proposed to approve the text proposal with removal of section 11.3
Decision: This text proposal was agreed to be included in TR with removal of section 11.3.
R1-070301 Coding of E-DCH for 1.28Mcps TDD Enhanced Uplink (CATT)
Decision: This text proposal was agreed to be included in TR.
R1-070302 Text Proposal on Power control and Synchronization control for 1.28Mcps
EUL (CATT)
ZTE raised a concern on SS command in section 11.2.1 so that proposed to leave it FFS.
R1-070407 Text proposal for power control for 1.28Mcps TDD Enhanced Uplink
(TD-Tech)
17/01/2007 09:55 Presented by Mr. Yonghong Chang
TD-Tech proposed further discussion with the first point, E-HICH/E-AGCH structure
CATT proposed to agree the text proposal not related to this issue.
It was decided to continue discussion based on two proposals from 302 and 407 via e-mail; and decide latest at next
meeting.
It was decided to revise TP in R1-070302 focussing on 11.1.1.1 in R1-070596
R1-070596 Text Proposal on Power control and Synchronization control for 1.28Mcps
EUL (CATT)
Decision: E-mail approval until Friday in next week, 26th January. This TP was agreed to be included to TR after
the meeting.
R1-070408 UE capability aspect for 1.28Mcps TDD EUL (TD-Tech)
R1-070566 UE capability aspect for 1.28Mcps TDD EUL (TD-Tech)
17/01/2007 09:xx Presented by Mr. Yonghong Chang
It is noted that in the formula on the first page 32 should be replaced with 16. The editorial was pointed out to
replace “received” with “transmitted” in table 13.2.
Decision: This text proposal was agreed to be included in TR.
The agreed text proposals were captured in updated TR, R1-070597.

R1-070597 TR 25.827 v1.0.1 (CATT)
Decision: E-mail approval until Friday in next week, 26th January. This version was endorsed as v1.1.0 in R1-
060636 on the RAN1 reflector
R1-070636 TR 25.827 v1.1.0 (CATT)
69
9. Closing of the meeting

19/01/2007 17: 10. RAN1 Chairman, Mr. Dirk Gerstenberger expressed his appreciation to the delegates and the host, the
European Friends of 3GPP for their supports, especially, Ms. Emmanuelle Wurffel. As the information of the meeting
schedule in 2007, one bis meeting will be held at the end of June or at the beginning of July.
The meeting was closed.
70
Annex A: List of participants at RAN1 #47bis

Name Representing Status-Partner Ph Email
Mr. Abe, Tetsushi DoCoMo Communications Lab. 3GPPMEMBER (ETSI) +49-89-56824-214 abe@docomolab-euro.com
Dr. Abeta, Sadayuki NTT DoCoMo Inc. 3GPPMEMBER (ARIB) +81-468-40-3470 abeta@mlab.yrp.nttdocomo.co.jp
Dr. Ahn, Joon-Kui LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-4014 jkan@lge.com
Mr. Akita, Hidenori MOTOROLA Ltd 3GPPMEMBER (ETSI) +81 3 5424 3031 hidenori.akita@motorola.com
Mr. Anderson, Nicholas IPWireless Inc. 3GPPMEMBER (ETSI) +44 1249 800020 nanderson@ipwireless.com
Mr. Asanuma, Yutaka Toshiba Corporation 3GPPMEMBER (ARIB) +81-428-34-4273 ytk.asanuma@toshiba.co.jp
Dr. Astely, David Nanjing Ericsson Panda Com Ltd 3GPPMEMBER (CCSA) +46 730 31 1906 david.astely@ericsson.com
Mr. Awad, Yassin Telecom Modus Ltd. 3GPPMEMBER (ETSI) +44 (0) 1372381849 yassin.awad@t-modus.nec.co.uk
Dr. Bachl, Rainer Alcatel-Lucent 3GPPMEMBER (ATIS) +49 911 526 2656 rbachl@alcatel-lucent.com
Mr. Baker, Matthew Philips International B.V. 3GPPMEMBER (ETSI) +44 1293 815287 bakermp2@prl.research.philips.com
Dr. Baligh, Mohammadhadi Nortel Networks 3GPPMEMBER (ATIS) +1-613-763-6343 hbaligh@nortel.com
Mr. Belaïche, Vincent Renesas Technology Europe 3GPPMEMBER (ETSI) +33 2 23 21 28 00 vincent.belaiche@rdf.renesas.com
Mr. Bergman, Johan Nanjing Ericsson Panda Com Ltd 3GPPMEMBER (CCSA) +46 8 594 36 849 johan.bergman@ericsson.com
Mr. Bertrand, Pierre TEXAS Instruments 3GPPMEMBER (ETSI) +33 (0)4 93 22 23 92 p-bertrand@ti.com
Mr. Bhat, Prakash Vodafone D2 GmbH 3GPPMEMBER (ETSI) +44(0)7825073804 prakash.bhat@vodafone.com
Dr. Blanz, Josef Qualcomm Korea 3GPPMEMBER (TTA) +49 6322 954572 jblanz@qualcomm.com
Mr. Boudreau, Gary Nortel Networks 3GPPMEMBER (ATIS)
Ms. Boumendil, Sarah Alcatel-Lucent 3GPPMEMBER (ETSI) +33 1 69 55 12 53 Sarah.Boumendil@alcatel-lucent.fr
Mr. Braun, Volker Alcatel-Lucent 3GPPMEMBER (ETSI) +49 711 821 40985 Volker.Braun@alcatel.de
Dr. Brunel, Loïc Mitsubishi Elec Info Tech Eur 3GPPMEMBER (ETSI) +33 2 23 45 58 58 brunel@tcl.ite.mee.com
Mr. Buckley, Eoin MOTOROLA GmbH 3GPPMEMBER (ETSI) +1-847-52300642 E.Buckley@motorola.com
Mr. Buracchini, Enrico TELECOM ITALIA S.p.A. 3GPPMEMBER (ETSI) +39 011 2287118 Enrico.Buracchini@telecomitalia.it
Ing. Cai, Qipeng mimoOn GmbH 3GPPMEMBER (ETSI) +492033064500 cai.qipeng@mimoOn.de
Mr. Callard, Aaron Nortel Networks 3GPPMEMBER (ATIS) +1 613 763 8694 aaronca@nortel.com
Mr. Chander, Sharat Cingular Wireless, LLC 3GPPMEMBER (ETSI) +1 425 580 6596 sharat.chander@cingular.com
Mr. Chang, Jaewon LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-1903 cygnus6@lge.com
Mr. Chang, Kapseok ETRI 3GPPMEMBER (TTA) +82 42 860 1237 kschang@etri.re.kr
Mr. Chang, Yonghong TD Tech Ltd 3GPPMEMBER (CCSA) +86-10-58223590 yonghong.chang@td-tech.com
Mr. Che, Xiangguang NOKIA Corporation 3GPPMEMBER (ETSI) +8613910218830 xiangguang.che@nokia.com
Dr. Cheng, J.-f. thomas Ericsson Inc. 3GPPMEMBER (ATIS) +1-919-472-1631 thomas.cheng@ericsson.com
Mr. Chmiel, Mieszko SIEMENS Networks S.p.A 3GPPMEMBER (ETSI) +48(71)7992847 mieszko.chmiel@siemens.com
Dr. Cho, Joonyoung Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82 31 279 5881 joonyoung.cho@samsung.com
Mr. Choi, Hyung-Nam INFINEON TECHNOLOGIES 3GPPMEMBER (ETSI) +49-5341-9061812 Hyung-Nam.Choi@infineon.com
Dr. Chung, Jae hoon LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-1934 jhchung329@lge.com
71
Mr. Classon, Brian MOTOROLA Ltd 3GPPMEMBER (ETSI) +18475765675 Brian.Classon@motorola.com
Dr. Clerckx, Bruno Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82312809503 bruno.clerckx@samsung.com
Dr. Czerepinski, Przemyslaw SIEMENS Networks S.p.A 3GPPMEMBER (ETSI) + przemek.czerepinski@roke.co.uk
Dr. Dahlman, Erik Nanjing Ericsson Panda Com Ltd 3GPPMEMBER (CCSA) +46 8 764 13 77 erik.dahlman@ericsson.com
Mr. Ding, Yinong Samsung Telecommunications 3GPPMEMBER (ATIS) +19727617975 y.ding@samsung.com
Mr. Dwarakanath, Pradeep Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +919880650041 pradeepd@samsung.com
Mr. Fabien, Jean-Aicard MOTOROLA S.A.S 3GPPMEMBER (ETSI) +1 847 523 7610 jean-aicard.fabien@motorola.com
Dr. Florén, Fredrik TeliaSonera AB 3GPPMEMBER (ETSI) +46406618148 fredrik.floren@teliasonera.com
Mr. Frost, Tim VODAFONE Group Plc 3GPPMEMBER (ETSI) +44 1635674334 tim.frost@vodafone.com
Mr. Fukui, Noriyuki Mitsubishi Electric Co. 3GPPMEMBER (ARIB) +81 467 41 2885 fukui.noriyuki@df.mitsubishielectric.co.jp
Mrs. Gao, Xueyuan CATT 3GPPMEMBER (CCSA) +861058832151 gaoxueyuan@datangmobile.cn
Dr. Gerlach, Christian G. Alcatel-Lucent 3GPPMEMBER (ETSI) +49.711.821-32200 christian.gerlach@alcatel-lucent.de
Dr. Gerlach, Heino ROHDE & SCHWARZ 3GPPMEMBER (ETSI) +49 89 4129 12517 heino.gerlach@rohde-schwarz.com
Mr. Gerstenberger, Dirk Telefon AB LM Ericsson 3GPPMEMBER (ETSI) +46 8 585 33901 dirk.gerstenberger@ERICSSON.COM
Dr. Ghosh, Amitabha MOTOROLA GmbH 3GPPMEMBER (ETSI) +18476324121 qa0047@email.mot.com
Mr. Golitschek edler von
elbwart, Alexander PANASONIC R&D Center Germany 3GPPMEMBER (ETSI) +49 6103 766 163 alexander.golitschek@eu.panasonic.com
Mr. Gomez, Gerardo AT4 wireless 3GPPMEMBER (ETSI) +34952134168 ggomez@ic.uma.es
Dr. Göransson, Bo Nanjing Ericsson Panda Com Ltd 3GPPMEMBER (CCSA) +46 8 7570703 bo.goransson@ericsson.com
Mr. Grieco, Donald INTERDIGITAL COMMUNICATIONS 3GPPMEMBER (ETSI) +1 631 622 4102 donald.grieco@interdigital.com
Mr. Grøvlen, Asbjørn NOKIA UK Ltd 3GPPMEMBER (ETSI) +358 405642489 asbjorn.grovlen@nokia.com
Dr. Guo, Qiang MOTOROLA Ltd 3GPPMEMBER (ETSI) +1 847 523 3217 qiangguo@motorola.com
Miss Han, Cuihong ZTE Corporation 3GPPMEMBER (CCSA) +86-755-26776612 han.cuihong@zte.com.cn
Ing. Han, Jin-Kyu Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82-31-279-5842 claude9.han@samsung.com
Mr. Han, Seung hee LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-1852 dondai@lge.com
Ing. Häring, Lars mimoOn GmbH 3GPPMEMBER (ETSI) +492033064500 haering@nts.uni-due.de
Mr. Harrison, Mark MOTOROLA A/S 3GPPMEMBER (ETSI) +18 475 233 217 mark.harrison@motorola.com
Ms. Heo, Youn SAMSUNG Electronics Co. 3GPPMEMBER (ARIB) +82-279-5362 hushhuk@korea.com
Miss Hernández, María José TELEFONICA S.A. 3GPPMEMBER (ETSI) +34 680012574 mariajose.hernandezlujan@telefonica.es
Dr. Higuchi, Kenichi NTT DoCoMo Inc. 3GPPMEMBER (ARIB) +81-46-840-3470 higuchi@mlab.yrp.nttdocomo.co.jp
Mr. Hiramatsu, Katsuhiko Panasonic Mobile Comm. 3GPPMEMBER (ARIB) +81 468 40 5422 hiramatsu.katsuhiko@jp.panasonic.com
Dr. Hong, Seung-Chul Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82-31-279-4906 seungchul.hong@samsung.com
Mr. Hoshino, Masayuki Panasonic Mobile Communication 3GPPMEMBER (TTC) +81 46 840 5435 hoshino.masayuki@jp.panasonic.com
Mr. Hosoda, Kenichiro MOTOROLA Ltd 3GPPMEMBER (ETSI) +81 354243155 r58080@motorola.com
Dr. Huang, Howard Alcatel-Lucent 3GPPMEMBER (ETSI) +1-732-888-7187 hchuang@alcatel-lucent.com
Dr. Huang, Yuan-hao ITRI 3GPPMEMBER (ETSI) +886-3-5162213 yhhuang@ee.nthu.edu.tw
Mr. Hugl, Klaus NOKIA Corporation 3GPPMEMBER (ETSI) +358 50 4860460 klaus.hugl@nokia.com
Dr. Humblet, Pierre Airvana, Inc. 3GPPMEMBER (ETSI) +1 978 250 3158 Pierre.Humblet@airvananet.com
Mr. Iizuka, Yosuke NTT DoCoMo Inc. 3GPPMEMBER (TTC) +81 468 40 3100 iizuka@cet.yrp.nttdocomo.co.jp
72
Mr. Imamura, Daichi Matsushita Electric Industrial 3GPPMEMBER (ARIB) +81.46.840.5631 imamura.daichi@jp.panasonic.com
Mr. Ishii, Yoshikazu ETSI Secretariat 3GPPORG_REP (ETSI) +33 4 92 94 42 06 yoshikazu.Ishii@etsi.org
Mr. Jang, Jaesung Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82 342 779 6818 sukjin.jang@samsung.com
+886 2
Mr. Jen, Elliot ASUSTeK Computer Inc. 3GPPMEMBER (ETSI) 28943447x4262 Elliot_Jen@asus.com.tw
Dr. Jöngren, George Telefon AB LM Ericsson 3GPPMEMBER (ETSI) +46768314820 george.jongren@ericsson.com
Prof. Kaiser, Thomas mimoOn GmbH 3GPPMEMBER (ETSI) +49(0)2033064500 thomas.kaiser@mimoOn.de
Mr. Kakura, Yoshikazu NEC Corporation 3GPPMEMBER (ARIB) +81 44 396 2592 y-kakura@cb.jp.nec.com
Mr. Kang, Seunghyun LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-1932 sh_kang@lge.com
Mr. Katsuragawa, Hiroshi SHARP Corporation 3GPPMEMBER (ARIB) +81-43-299-8265 katsuragawa.hiroshi@sharp.co.jp
Mr. Kawasaki, Yoshihiro Fujitsu Limited 3GPPMEMBER (ARIB) + yosihiro@labs.fujitsu.com
Dr. Kent, Mark BROADCOM CORPORATION 3GPPMEMBER (ETSI) +858-521-5853 mkent@broadcom.com
Dr. Khan, Farooq Samsung Telecommunications 3GPPMEMBER (ATIS) +1 972 761 7929 fkhan@sta.samsung.com
Mr. Kim, Bong Hoe LG Electronics Inc. 3GPPMEMBER (TTA) +82 343 450 4131 ofdm88@lge.com
Mr. Kim, Byungsik Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +8231299-5289 byungsik.kim@samsung.com
Mr. Kim, Hojin ArrayComm, Inc 3GPPMEMBER (ATIS) +1-408-428-9080 hkim@arraycomm.com
Dr. Kim, Joel Marvell Semiconductor 3GPPMEMBER (ATIS) +14082222859 joel.kim@marvell.com
Dr. Kim, Ki jun LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-7316 kjun@lge.com
Mr. Kim, Youngbum SAMSUNG Electronics Co. 3GPPMEMBER (ARIB) +82 31 279 5092 youngbum.kim@samsung.com
Mr. Kishiyama, Yoshihisa NTT DoCoMo Inc. 3GPPMEMBER (TTC) +81-46-840-3470 kishi@mlab.yrp.nttdocomo.co.jp
Mr. Kistowski, Dirk T-Mobile International AG 3GPPMEMBER (ETSI) +49 228 936 1 8419 dirk.kistowski@t-mobile.de
Dr. Ko, Young-jo ETRI 3GPPMEMBER (TTA) +82-42-860-4810 koyj@etri.re.kr
Dr. Kotecha, Jayesh Freescale Semiconductors 3GPPMEMBER (ETSI) +1-512-996-7454 jayeshkotecha@freescale.com
Dr. Koulakiotis, Dimitris ZTE Corporation 3GPPMEMBER (CCSA) dimitris.koulakiotis@ztewistron.com
Dr. Kowalski, John SHARP Corporation 3GPPMEMBER (ARIB) +1 (360) 817 7520 kowalskj@sharplabs.com
Dr. Krause, Joern Siemens Networks GmbH & Co. KG 3GPPMEMBER (ETSI) +49-30-386-23417 joern.krause@siemens.com
Mr. Kwak, Yongjun SAMSUNG Electronics 3GPPMEMBER (ETSI) +82 31 279 5112 evatt@samsung.com
Mr. Kwon, Eddy Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82 31 279 5089 eddykwon@samsung.com
Mr. Kwon, Jaekyun TTA 3GPPORG_REP (TTA) +82 42 860 6759 jack@etri.re.kr
Dr. Lee, Juho Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82-31-279-5115 juho95.lee@samsung.com
Mr. Lee, Jun Hwan ETRI 3GPPMEMBER (TTA) +82 42 860 5325 junhwanlee@etri.re.kr
Ms. Lee, Jung a. Alcatel-Lucent 3GPPMEMBER (ETSI) +1 973 386 3280 jalee@alcatel-lucent.com
Mr. Lee, Jung Hoon LG Electronics Inc. 3GPPMEMBER (TTA) +82.31.450.2931 jh_lee@lge.com
Mr. Lee, Moonil LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-7903 emoon1@lge.com
Dr. Li, Bin HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) +86-755-28762689 binli@huawei.com
Mr. Li, Jun Nortel Networks 3GPPMEMBER (ATIS) + 972 684 3775 junli@nortel.com
Dr. Li, Richard c.-f. ITRI 3GPPMEMBER (ETSI) +886-3-591-7596 richard929@itri.org.tw
TOSHIBA RESEARCH EUROPE
Dr. Lillie, Andy LTD 3GPPMEMBER (ETSI) +44 1179069840 andy.lillie@toshiba-trel.com
73
Dr. Lindbom, Lars Nippon Ericsson K.K. 3GPPMEMBER (ARIB) +46 8 757 16 63 lars.lindbom@ericsson.com
Mr. Lindh, Lars NOKIA Corporation 3GPPMEMBER (ETSI) +358 9 43761 lars.e.lindh@nokia.com
Mr. Lindholm, Jari Nokia Japan Co, Ltd 3GPPMEMBER (ARIB) +358 7180 66762 jari.o.lindholm@nokia.com
Mr. Liu, Jianghua HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) +8682882650 jianghua811@huawei.com
+86 21 58541240-
Miss Liu, Jin Alcatel Shanghai Bell Co. 3GPPMEMBER (CCSA) 3136 jin.a.liu@alcatel-sbell.com.cn
Mr. Liu, Jingxiu NTT DoCoMo Inc. 3GPPMEMBER (ARIB) +861082861501 liujx@docomolabs-beijing.com.cn
Mr. Logli, Nicola Aeroflex 3GPPMEMBER (ETSI) +441763264903 nicola.logli@aeroflex.com
Mr. Love, Robert MOTOROLA GmbH 3GPPMEMBER (ETSI) +18475233702 qa2178@email.mot.com
Dr. Lu, Feng KDDI Corporation 3GPPMEMBER (ARIB) +81468476359 lu@kddilabs.jp
Mr. Lunttila, Timo NOKIA Corporation 3GPPMEMBER (ETSI) +358504821552 timo.lunttila@nokia.com
Miss Ma, Jianglei Nortel Networks 3GPPMEMBER (ATIS) +1-613-7651853 jianglei@nortel.com
Dr. Ma, Zhifeng ZTE Corporation 3GPPMEMBER (CCSA) +86-21-68895889 zfmail@zte.com.cn
Mr. Ma, Zijiang ZTE Corporation 3GPPMEMBER (CCSA) +086-25-52870494 ma.zijiang@zte.com.cn
Dr. Mai, Huiheng IPWireless Inc. 3GPPMEMBER (ETSI) +441249 800069 hmai@ipwireless.com
Dr. Malkamaki, Esa NOKIA Corporation 3GPPMEMBER (ETSI) +358 7180 36562 esa.malkamaki@nokia.com
Dr. Mauritz, Oskar HUAWEI TECHNOLOGIES Co. Ltd. 3GPPMEMBER (ETSI) +46 8 477 0804 oskar.mauritz@huawei.com
Dr. Mccoy, Wes Freescale Semiconductors 3GPPMEMBER (ETSI) +1 512 996 7627 wes.mccoy@freescale.com
Dr. Mehta, Neelesh Mitsubishi Electric Co. 3GPPMEMBER (ARIB) +16176217597 mehta@merl.com
Mr. Miki, Nobuhiko TTC 3GPPORG_REP (TTC) +81-468-40-3470 nmiki@mlab.yrp.nttdocomo.co.jp
Dr. Min, Seunghyun Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82-31-279-3387 seunghyun.min@samsung.com
Mr. Montojo, Juan Qualcomm Japan Inc 3GPPMEMBER (ARIB) +1 858-651-2426 juanm@qualcomm.com
Dr. Moon, Hichan Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82-31-279-5351 hchan.moon@samsung.com
Mr. Motozuka, Hiroyuki Matsushita Electric Industrial 3GPPMEMBER (ARIB) +81-46-840-5456 motozuka.hiroyuki@jp.panasonic.com
Dr. Mottier, David Mitsubishi Elec Info Tech Eur 3GPPMEMBER (ETSI) +33 2 23 45 58 58 mottier@tcl.ite.mee.com
Dr. Mujtaba, Syed aon Agere Systems Deutschland GmbH 3GPPMEMBER (ETSI) +1 610 712 6616 mujtaba@agere.com
Mr. Nakashima, Daiichiro SHARP Corporation 3GPPMEMBER (ARIB) +81-43-299-8562 nakashima.daiichiroh@sharp.co.jp
Dr. Nam, Haewoon MOTOROLA Ltd 3GPPMEMBER (ETSI) +1 512-427-7310 haewoon.nam@motorola.com
Dr. Nicolas, Julien TEXAS Instruments 3GPPMEMBER (ETSI) +1-858-345-7516 jnicolas@ti.com
Dr. Nimbalker, Ajit MOTOROLA Ltd 3GPPMEMBER (ETSI) +18475765122 A.Nimbalker@motorola.com
Mr. Nishio, Akihiko Panasonic (PMCDE) 3GPPMEMBER (ETSI) +81 46 840 5694 nishio.akihiko@jp.panasonic.com
Mr. Noh, Taegyun ETRI 3GPPMEMBER (TTA) +82 42 860 5897 taegyun@etri.re.kr
Mr. Nory, Ravikiran MOTOROLA Ltd 3GPPMEMBER (ETSI) +18475234611 ravi.nory@motorola.com
Mr. Ojala, Jussi NOKIA Corporation 3GPPMEMBER (ETSI) +358504836248 Jussi.Ojala@nokia.com
Mr. Onggosanusi, Eko TEXAS Instruments 3GPPMEMBER (ETSI) +1 214 480 1809 eko@ti.com
Mr. Ozluturk, Fatih INTERDIGITAL COMMUNICATIONS 3GPPMEMBER (ETSI) +1 516 622 4321 fatih.ozluturk@interdigital.com
Dr. Papasakellariou, Aris Texas Instruments Deutschland 3GPPMEMBER (ETSI) +1 214 480 4572 aris@ti.com
Dr. Paranchych, David Nortel Networks 3GPPMEMBER (ATIS) +1 (972) 685-1828 paranchy@nortel.com
Mr. Park, HyeongGeun ETRI 3GPPMEMBER (TTA) +82 42 860 1635 hgpark@etri-re.kr
74
Dr. Parkvall, Stefan Ericsson Inc. 3GPPMEMBER (ATIS) +46 719 00 00 stefan.parkvall@ericsson.com
Dr. Pesavento, Marius mimoOn GmbH 3GPPMEMBER (ETSI) +492033064500 marius.pesavento@mimoOn.de
Mr. Pham, Duong NEC Corporation 3GPPMEMBER (TTC) +61392643902 duongp@3g.nec.com.au
Mrs. Phan huy, Dinh thuy France Telecom 3GPPMEMBER (ETSI) +33 1 45 29 65 82 dinhthuy.phanhuy@orange-ftgroup.com
Dr. Popovic, Branislav HUAWEI TECHNOLOGIES Co. Ltd. 3GPPMEMBER (ETSI) +46 8 4700808 branislav.popovic@huawei.com
Dr. Prasad, Narayan NEC Corporation 3GPPMEMBER (ARIB) +1-609-951-2985 prasad@nec-labs.com
Mr. Provvedi, Leonardo Siemens nv/sa 3GPPMEMBER (ETSI) +44 1794 833951 leonardo.provvedi@roke.co.uk
Mr. Ranta-aho, Karri Nokia Telecommunications Inc. 3GPPMEMBER (ATIS) +358 50 521 0651 Karri.Ranta-aho@nokia.com
Dr. Rao, Anil Alcatel-Lucent 3GPPMEMBER (ETSI) +1 973 884 3817 amrao@lucent.com
Dr. Ratasuk, Rapeepat MOTOROLA Ltd 3GPPMEMBER (ETSI) +1 847 632 6881 ratasuk@motorola.com
Dr. Rhee, Jonghun Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +82-31-279-5834 jh.rhee@samsung.com
Mr. Rheinschmitt, Rupert Alcatel-Lucent 3GPPMEMBER (ETSI) +49 711 821 34172 Rupert.Rheinschmitt@alcatel.de
Mr. Robson, Julius NORTEL NETWORKS (EUROPE) 3GPPMEMBER (ETSI) juliusr@nortel.com
Mr. Rong, Zhigang HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) +1-858-882-0328 zrong@huawei.com
Mr. Ruprich, Thomas INFINEON TECHNOLOGIES 3GPPMEMBER (ETSI) +49 89 234 86253 thomas.ruprich@infineon.com
Dr. Sälzer, Thomas ORANGE SA 3GPPMEMBER (ETSI) +33 1 45 29 64 80 thomas.salzer@orange-ftgroup.com
Mr. Scheim, Jacob IAESI 3GPPMEMBER (ETSI) +972-9-9717850 kobi.scheim@comsysmobile.com
Dr. Schroeder, Werner mimoOn GmbH 3GPPMEMBER (ETSI) +492033064500 werner.schroeder@mimoOn.de
Mr. Seyama, Takashi Fujitsu Limited 3GPPMEMBER (ARIB) +81-46-839-5374 seyama.takashi@jp.fujitsu.com
Mr. She, Xiaoming NTT DoCoMo Inc. 3GPPMEMBER (ARIB) +861082861501 +861082861501
Dr. Shen, Bazhong BROADCOM CORPORATION 3GPPMEMBER (ETSI) +19499266019 bzshen@broadcom.com
Mr. Shen, Jia RITT 3GPPMEMBER (CCSA) +86-10-62302438 shenjia@mail.ritt.com.cn
Mr. Shitara, Shoichi SHARP Corporation 3GPPMEMBER (ARIB) +81-43-299-8561 shitara.shoichi@sharp.co.jp
Mr. Sood, Prem SHARP Corporation 3GPPMEMBER (ARIB) +1 360 834 8708 pls@sharplabs.com
Dr. Soong, Anthony HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) +1-469-229-5379 asoong@huawei.com
Dr. Sun, Shaohui CATT 3GPPMEMBER (CCSA) +86 10 58832133 sunshaohui@datangmobile.cn
+86-10-82029090-
Mr. Suo, Shiqiang CATT 3GPPMEMBER (CCSA) 6546 suoshiqiang@datangmobile.cn
Mr. Tanaka, Yoshinori Fujitsu Limited 3GPPMEMBER (ARIB) yoshi.tanaka@jp.fujitsu.com
Mr. Tang, Hai CATT 3GPPMEMBER (CCSA) +86 10 58832228 tanghai@datangmobile.cn
Mr. Taoka, Hidekazu NTT DoCoMo Inc. 3GPPMEMBER (ARIB) +81 468 40 3470
Dr. Tatesh, Said Lucent Technologies N. S. UK 3GPPMEMBER (ETSI) +44 1793 883 293 statesh@alcatel-lucent.com
Mr. Wolf, Tod Texas Instruments A/S 3GPPMEMBER (ETSI) +1 214-480-4450 tod2w@ti.com
Dr. Tosato, Filippo Philips International B.V. 3GPPMEMBER (ETSI) +441293815475 filippo.tosato@philips.com
Dr. Tsai, Jiannan Samsung Telecommunications 3GPPMEMBER (ATIS) +1-972-761-7424 jtsai@sta.samsung.com
+886 2
Mr. Tseng, Richie ASUSTeK Computer Inc. 3GPPMEMBER (ETSI) 28943447x4255 Richie_Zen@asus.com.tw
Mr. Van rensburg, Cornelius Samsung Telecommunications 3GPPMEMBER (ATIS) +1 972 761 7970 c.rensburg@samsung.com
Dr. Vannucci, Giovanni Mitsubishi Electric Co. 3GPPMEMBER (ARIB) +1-617-621-7500 gv@merl.com
75
Dr. Varadarajan, Badri TEXAS Instruments Japan Ltd 3GPPMEMBER (ARIB) +214-480-4554 badriv@ti.com
Mr. Vujcic, Dragan LG Electronics Mobilecomm 3GPPMEMBER (ETSI) +33 1 41 59 93 78 dvujcic@lge.com
Mr. Wang, Chengyu HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) +86-10-82882719 wangchengyu@huawei.com
Mr. Wang, Irving ZTE Corporation 3GPPMEMBER (CCSA) +18139947381 iwang@ztesandiego.com
Mr. Wang, Ke CATT 3GPPMEMBER (CCSA) +86 10 82029090 wangke@datangmobile.cn
Dr. Wang, Sherwin Magnolia Broadband Inc. 3GPPMEMBER (ATIS) +1.908.234.0885 x227 swang@magnoliabroadband.com
Dr. Wang, Yonggang Alcatel-Lucent 3GPPMEMBER (ETSI) +862150554550-7440 yonggang.wang@alcatel-sbell.com.cn
Mr. Wang, Zongjie HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) +86-021-68644808 zongjie.wang@huawei.com
Mr. Wannemacher, Georg T-Mobile International AG 3GPPMEMBER (ETSI) +49229/936-18433 georg.wannemacher@t-mobile.de
Dr. Wennström, Mattias HUAWEI TECHNOLOGIES Co. Ltd. 3GPPMEMBER (ETSI) +46-8-4770803 mattias.wennstrom@huawei.com
Mr. Willenegger, Serge QUALCOMM EUROPE S.A.R.L. 3GPPMEMBER (ETSI) +41 24 436 3540 sergew@qualcomm.com
Ms. Wimmer, Malgorzata Siemens nv/sa 3GPPMEMBER (ETSI) +48(0)717992624 Malgorzata.Wimmer@siemens.com
Dr. Womack, James Research in Motion UK Limited 3GPPMEMBER (ETSI) +1 972 791 2393 jwomack@rim.com
Miss Wong, Eliza Alcatel-Lucent 3GPPMEMBER (ETSI) +33130775698 eliza.wong@alcatel-lucent.fr
Mr. Wong, Sai ho Institute for Infocomm Researc 3GPPMEMBER (ETSI) +65 6874 5682 shwong@i2r.a-star.edu.sg
Mr. Wu, Jianming Nortel Networks 3GPPMEMBER (ATIS) +1 613 765 5671 jianmwu@nortel.com
Ms. Wurffel, Emmanuelle ETSI Secretariat 3GPPORG_REP (ETSI) +33 4 92 94 42 66 emmanuelle.wurffel@etsi.org
Dr. Xiao, Weimin MOTOROLA Ltd 3GPPMEMBER (ETSI) +1 847 632 2367 wxiao1@motorola.com
Mr. Xu, Hua Nortel Networks 3GPPMEMBER (ATIS) +0016137652564 huaxu@nortel.com
Mr. Yang, Yoon-oh LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-4161 uknow@lge.com
Mr. Yano, Yasuhiro Mitsubishi Electric Co. 3GPPMEMBER (ARIB) +81 467 41 2850 yano.yasuhiro@ap.MitsubishiElectric.co.jp
Dr. Yi, Hyo-seok ETRI 3GPPMEMBER (TTA) +82-42-860-5160 yhs64204@etri.kr
Mr. Yoon, Sukhyon LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-4382 ysukhyon@lge.com
Mr. Yu, Bin ZTE Corporation 3GPPMEMBER (CCSA) +86(0)2168895729 yu.bin4@zte.com.cn
Miss Yu, Hui ZTE Corporation 3GPPMEMBER (CCSA) +86-755-26776612 yu.hui@zte.com.cn
Dr. Yun, Young woo LG Electronics Inc. 3GPPMEMBER (TTA) +82-31-450-7316 youngwooy@lge.com
Mr. Zeira, Eldad INTERDIGITAL COMMUNICATIONS 3GPPMEMBER (ETSI) +1 631 622 4134 eldad.zeira@interdigital.com
Dr. Zhang, Charlie (jianzhong) MOTOROLA S.A.S 3GPPMEMBER (ETSI) +1-817-245-6559 charlie.zhang@motorola.com
Mr. Zhang, Junfeng ZTE Corporation 3GPPMEMBER (CCSA) +8675526771477 zhang.junfeng@zte.com.cn
Miss Zhang, Xiaoxia QUALCOMM EUROPE S.A.R.L. 3GPPMEMBER (ETSI) +001 858-6585035 xiaoxiaz@qualcomm.com
Mr. Zhang, Yujian Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +86 13511008996 yujian.zhang@samsung.com
Mr. Zhou, Yongxing Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) +86-10-68481901 yongxing.zhou@samsung.com
Dr. Zimmermann, Manfred INFINEON TECHNOLOGIES 3GPPMEMBER (ETSI) +49 89 234 81636 Manfred.Zimmermann@infineon.com
76
Annex B: TSG RAN WG1 meetings in 2007
TITLE TYPE DATES LOCATION CTRY

3GPPRAN1#47bis WG 15 - 19 Jan 2007 Sorrento IT
3GPPRAN1#48 WG 12 - 16 Feb 2007 St Louis US
3GPPRAN1#48bis WG 26 - 30 March 2007 St Julian Malta
3GPPRAN1#49 WG 07-11 May 2007 Kobe JP
3GPPRAN1#49bis WG June 2007 TBD TBD
3GPPRAN1#50 WG 20-24 Aug 2007 TBD EU
3GPPRAN1#50bis WG Oct 2007 TBD TBD
3GPPRAN1#51 WG 05 - 09 Nov 2007 TBD KR
MEETING TYPES
AH = Ad Hoc CM = Chairmen's meeting
JM = Joint OR = Ordinary
PM = Preparatory
Meeting RG = Rapporteurs Group
RM = Resolution Meeting SG = Steering Group
ST = Startup Meeting TG = Task Group
WG = Working Group XO = Extraordinary
77
Annex C: List of CRs agreed at RAN1#47bis

Spec CR R Cat Rel R1 Tdoc Title Work Item
Modification on the power control function of HS-SICH and HS-SCCH for LCR HSDPA-Phys
25.224 0154 1 F Rel-6 R1-070550
TDD"
Modification on the power control function of HS-SICH and HS-SCCH for LCR HSDPA-Phys
25.224 0155 1 A Rel-7 R1-070551
TDD"
25.225 0084 1 F Rel-6 R1-070552 Modification on the HS-SICH reception quality of HS-SICH for LCR TDD HSDPA-Phys
25.225 0085 1 A Rel-7 R1-070553 Modification on the HS-SICH reception quality of HS-SICH for LCR TDD HSDPA-Phys
25.211 0232 1 C Rel-7 R1-070558 Enhanced F-DPCH TEI7
25.214 0433 1 C Rel-7 R1-070559 Enhanced F-DPCH TEI7
25.224 0157 2 F Rel-6 R1-070624 Clarification of Closed Loop Uplink HS-SICH Power Control for 1.28 Mcps TDD HSDPA-Phys
25.224 0158 2 A Rel-7 R1-070625 Clarification of Closed Loop Uplink HS-SICH Power Control for 1.28 Mcps TDD HSDPA-Phys
RANimp-
25.201 0026 1 B Rel-7 R1-070582 Introduction of 64QAM for HSDPA
64QamDownlink
RANimp-
64QamDownlink
RANimp-
64QamDownlink
RANimp-
64QamDownlink
RANimp-
64QamDownlink
RANimp-
25.201 0027 1 B Rel-7 R1-070588 Introduction of 16QAM for HSUPA
16QamUplink
RANimp-
16QamUplink
RANimp-
16QamUplink
RANimp-
16QamUplink
RANimp-
16QamUplink
Note 1): CR 0232r1 for 25.211 and CR 0433r1 for 25.214 were agreed in principle
78
Annex D: List of Outgoing LSs from RAN1#47bis

NUMBER TITLE Rel To Cc
R1-070578 Answer LS on status of Rel-7 FDD MIMO Rel-7 RAN2 RAN4
R1-070594 Reply LS on Impact of Release 7 bit rate increase and MIMO Rel-7 RAN3 CT1, CT4,
SA1, SA2,
RAN2
R1-070606 Reply LS on Primary BCH Transmission Rel-8 RAN2 -
R1-070607 Reply LS on SFN acronym disambiguation R1-070009 (R3-062012) Rel-8 RAN3 -
R1-070621 Response to LS R3-062005=R1-070008 on "Inter-Cell Interference Rel-8 RAN3 -
Coordination and its signalling"
R1-070622 LS Response to RAN2 LS on Synchronization at Handover Rel-8 RAN2 RAN3, RAN4
R1-070623 Reply LS on CPC Long preamble Rel-7 RAN2 -
R1-070626 LS on F-DCH enhancement for Release-7 Rel-7 RAN2, RAN3, -
RAN4
R1-070628 LS on 7.5 kHz carrier spacing Rel-8 RAN4 -
R1-070629 LS on data-associated uplink control signalling Rel-8 RAN2 -
R1-070631 LS on Transport Block Size Signalling for 1.28Mcps TDD Enhanced Rel-7 RAN2 -
Uplink
R1-070632 LS on Frequency Domain Spectrum Shaping and /2 BPSK Rel-8 RAN4 -
R1-070634 LS to RAN2 on Synchronization and Mobility with CPC Rel-7 RAN2 -
79
Annex E: List of Tdocs at RAN1 #47bis

AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
R1-070001 Draft Agenda for RAN1#47bis meeting RAN1 Chairman 2 Approved
R1-070002 Draft Report of RAN1#47 MCC 3 Approved in R1-070633
LS on Synchronization at handover (To: RAN WG2, LG = R2-063628 Noted
R1-070003 4
RAN1, Cc: RAN4) Electronics
Estimated peak hour loads in LTE (To: = R2-063631 Noted
R1-070004 RAN WG2, Samsung 4
RAN3, Cc: RAN1)
LS on improved HARQ operation (To: RAN WG2, = R2-063633 Noted
R1-070005 4
RAN1) ASUSTek
LS on status of Rel-7 FDD MIMO (To: RAN WG2, = R2-063645 Noted
R1-070006 4
RAN1) Vodafone
LS on Primary BCH Transmission (To: RAN WG2, NTT = R2-063657 Noted
R1-070007 4
RAN1) DoCoMo
LS on “Inter-Cell Interference Coordination = R3-062005 Noted
R1-070008 RAN WG3, Nokia 4
and its signalling” (To: RAN1)
LS on SFN acronym disambiguation (To: = R3-062012 Noted
R1-070009 RAN WG3, Siemens 4
RAN1, RAN2, RAN4)
LS on LTE-MBMS Discussions in RAN3 RAN WG3, = R3-062015 Noted
R1-070010 4
(To: RAN1, RAN2, SA2) Vodafone
LS on Impact of Release 7 bit rate = R3-062033 Noted
R1-070011 increase and MIMO on Specifications (To: RAN WG3, Nortel 4
RAN1, RAN2, CT1, CT4, SA1, SA2)
Response to your November 28, 2006 Noted
R1-070012 request for information on IEEE 1588 (To: IEEE1588 4
RAN3, Cc: RAN1, RAN2)
LS on introduction of radio bearers for = R5-063566 Noted
R1-070013 RAN WG5, Ericsson 4
MTCH in TS 34.108 (To: RAN1, RAN2)
Reply LS to SA1, SA4 on Service = RP-060864 Noted
R1-070014 Requirement for MBMS LTE (To: SA1, TSG RAN, Nokia 4
SA4, Cc: RAN1, RAN2, RAN3)
Open Loop Transmit Diversity for Not treated
R1-070015 Downlink Channels with 4 Transmit Agere Systems 6.7.5
Antennas in E-UTRA
Improved HS-SCCH order signalling for Noted
R1-070016 Renesas Technology 7.2
CPC
80
AGENDA REVISED BY
ITEM (From)
R1-070017 Soft-combining for P-BCH Toshiba 6.5.2 Not treated
The number of P-SCHs and coherent vs. Noted
R1-070018 ETRI 6.5.2
non-coherent second step
Minimization of the number of P-SCH Not treated
R1-070019 sequences using subframe offset between ETRI 6.5.2
node Bs in synchronized network
R1-070020 S-SCH structure for EUTRA cell search ETRI 6.5.2 Not treated
R1-070021 Location of SCH and P-BCH ETRI 6.5.2 Not treated
Intra- and/or Inter-Sector Diversity Not treated
R1-070022 ETRI 6.7.5
Scheme for P-BCH using S-SCH
Comparison of SCH diversity schemes in Not treated
R1-070023 ETRI 6.7.5
initial cell search
64QAM in HSDPA - Modulation Format R1-070568 Revised in R1-070568
R1-070024 Motorola 7.3.1
Indication
64QAM in HSDPA - Necessary Changes R1-070572 Revised in R1-070572
R1-070025 Motorola 7.3.1
to the Specifications
Further Link Simulation Results of Higher Noted
R1-070026 Motorola 7.3.2
Order Modulations in HSPA Uplink
HSUPA 16QAM Inclusion - Modulation Noted
R1-070027 Motorola 7.3.2
Selection
Further Analysis of Enhanced Noted
R1-070028 Motorola 7.4
CELL_FACH
E-UTRA UL L1/L2 Control Channel Withdrawn
R1-070029 Motorola 6.9.1
Design
E-UTRA DL L1/L2 Non-Persistent Control Noted
R1-070030 Motorola 6.9.2
Channel Design
Multiplexing of UL Control Signaling with Not treated
R1-070031 Motorola 6.9.1
Data
Support of Precoding for E-UTRA DL Not treated
R1-070032 Motorola 6.9.2
L1/L2 Control Channel
E-UTRA DL L1/L2 Control Channel Withdrawn
R1-070033 Motorola 6.9.2
Design - Persistent Scheduling
Downlink Acknowledgement and Group Not treated
R1-070034 Motorola 6.9.2
Transmit Indicator Channels
Max #UEs/TTI for optimum E-UTRA DL Not treated
R1-070035 Motorola 6.9.2
performance
E-UTRA DL L1/L2 Control Channel Not treated
R1-070036 Motorola 6.9.2
Information & RA map reduction
81
AGENDA REVISED BY
ITEM (From)
DFT Restrictions and impact on UL Noted
System Performance
R1-070038 UL Power Control for E-UTRA Motorola 6.12 Not treated
R1-070039 DL Power Control for E-UTRA Motorola 6.12 Not treated
DL Power Allocation for Dynamic Not treated
R1-070040 Motorola 6.12
Interference Avoidance in E-UTRA
Dynamic contention free Scheduling Noted
R1-070041 Motorola 6.5.1
Request
R1-070042 Non-synchronized random access Motorola 6.5.1 Not treated
Performance comparison of UL Power Not treated
R1-070043 Motorola 6.12
control methods
E-UTRA Measurements Related to Not treated
R1-070044 Motorola 6.13
Mobility
R1-070045 Uplink Timing Control Motorola 6.11 Noted
R1-070046 Performance Evaluation of P-BCH Motorola 6.5.2 Noted
UE Power De-rating Reduction Noted
Techniques in LTE
Frequency Domain Spectral Shaping for R1-070564 Revised in R1-070564
LTE
R1-070049 CQI feedback for E-UTRA Motorola 6.9.1 Not treated
R1-070050 CP Length for Unicast-MBMS-mixed ModeMotorola, Nokia 6.2 Noted
Performance of MBMS Transmission Noted
R1-070051 Motorola 4
Configurations
R1-070052 Deployment Scenarios for MBMS Motorola 6.2 Noted
R1-070053 Cell Search and MBMS Motorola 6.5.2 Not treated
Contention-free Interleaver designs for Not treated
LTE Turbo Codes
Performance of Contention-free Not treated
Interleavers for LTE Turbo Codes
Performance of Contention Free Not treated
Interleaver Designs for LTE
Summary of Rel 6 Turbo Code Interleaver Not treated
Issues for LTE
R1-070058 Eliminating tail bits in LTE channel coding Motorola 6.4 Not treated
Code Block Segmentation for Contention- Not treated
free Turbo Interleavers
R1-070060 QPP Interleaver Design for LTE Motorola 6.4 Noted
R1-070061 ARP Interleaver Design for LTE Motorola 6.4 Noted
82
AGENDA REVISED BY
ITEM (From)
Mobile Assisted Non-codebook based Not treated
precoding for TDD
R1-070063 MBMS with feedback Motorola 6.9.1 Not treated
Summary of S-SCH e-mail reflector Noted
R1-070064 Motorola 6.5.2
discussion
Summary of RACH e-mail reflector Noted
R1-070065 Motorola 6.5.1
discussion
E-UTRA DL Coding Performance for Not treated
R1-070066 Motorola 6.9.2
Control Channel
The effect of FFT size restrictions on the Freescale Noted
R1-070067 6.2
system performance of uplink SC-FDMA Semiconductor
Frequency Domain Spectral Shaping and Freescale Noted
R1-070068 6.3
Power Amplifier Optimization Semiconductor
Freescale Not treated
R1-070069 Power Control in uplink LTE 6.12
Semiconductor
25.224 CR0154 (Rel-6, F) "Modification on CATT, ZTE, TD- R1-070550 Revised in R1-070550
R1-070070 the power control function of HS-SICH and Tech, Spreadtrum 5
HS-SCCH for LCR TDD" Communication
25.224 CR0155 (Rel-7, A) "Modification onCATT, ZTE, TD- R1-070551 Revised in R1-070551
R1-070071 the power control function of HS-SICH and Tech, Spreadtrum 5
HS-SCCH for LCR TDD" Communication
25.225 CR0084 (Rel-6, F) "Modification on CATT, ZTE, TD- R1-070552 Revised in R1-070552
R1-070072 the HS-SICH reception quality of HS-SICH Tech, Spreadtrum 5
for LCR TDD" Communication
25.225 CR0085 (Rel-7, A) "Modification onCATT, ZTE, TD- R1-070553 Revised in R1-070553
R1-070073 the HS-SICH reception quality of HS-SICH Tech, Spreadtrum 5
for LCR TDD" Communication
25.224 CR0156 (Rel-5, F) "Clarification of Rejected
R1-070074 Closed Loop Uplink HS-SICH Power ZTE 5
Control for 1.28 Mcps TDD"
25.224 CR0157 (Rel-6, A) "Clarification of R1-070554 Revised in R1-070554
25.224 CR0158 (Rel-7, A) "Clarification of R1-070555 Revised in R1-070555
Reference Signal Structure for Multi- Withdrawn
R1-070077 Alcatel-Lucent 6.6.1
antenna E-MBMS Transmission
83
AGENDA REVISED BY
ITEM (From)
Non-coherent ACK/NACK signaling using Not treated
R1-070078 code sequences as indicators in E-UTRA ETRI 6.9.1
uplink
R1-070079 Downlink L1/L2 control signaling ETRI 6.9.2 Not treated
Comparison of the proposals for Noted
R1-070080 Siemens 7.4
enhancing CELL_FACH state
Interworking between LTE and GSM - 6.5.2 Not treated
R1-070081 Siemens
Monitoring LTE from GSM
Interworking between LTE and GSM - 6.13 Withdrawn
R1-070082 Siemens
Monitoring GSM from LTE
NTT DoCoMo, 4 Noted
Proposed response to RAN2 LS in [R1- Fujitsu, Mitsubishi
R1-070083
070007] Electric, NEC,
Panasonic, Sharp
NTT DoCoMo, 6.2 Not treated
Comparison Between RB-level and Sub- Fujitsu, KDDI,
carrier-level Distributed Transmission for Mitsubishi Electric,
R1-070084
Shared Data Channel in E-UTRA NEC, Nokia,
Downlink Panasonic, Sharp,
Toshiba Corporation
NTT DoCoMo, 6.5.1 Noted
Uplink Physical Channel for Scheduling
R1-070085 Fujitsu, NEC,
Request Transmission
Panasonic, Sharp
Investigations on Primary-SCH sequences
R1-070086 Mitsubishi Electric,
for E-UTRA Downlink
Panasonic
R1-070087 S-SCH Sequence for E-UTRA Downlink NTT DoCoMo 6.5.2 Withdrawn
NTT DoCoMo, 6.6.1 Not treated
Power Boosting of Reference Signal in E- Fujitsu, Mitsubishi
R1-070088
UTRA Downlink Electric, NEC,
Panasonic, Sharp
Dedicated Reference Signal for Beam- Fujitsu, Mitsubishi
R1-070089
forming in E-UTRA Downlink Electric, NEC,
Panasonic
84
AGENDA REVISED BY
ITEM (From)
Necessity of Multiple Bandwidth for Fujitsu, Mitsubishi
R1-070090
Sounding Reference Signals Electric, NEC,
Panasonic, Sharp
Assignment Scheme of Sounding 6.6.2 Not treated
R1-070091 NTT DoCoMo
Reference Signals in E-UTRA Uplink
Throughput Comparisons between SB and 6.6.2 Not treated
LB Reference Signals in E-UTRA Uplink
Investigations on Codebook Size for 6.7.2 Noted
MIMO Precoding in E-UTRA Downlink
Multi-Codebook Pre-coding Scheme for 6.7.2 Not treated
MIMO in E-UTRA Downlink
Transmit Diversity Scheme for
Fujitsu, Mitsubishi
R1-070095 Common/Shared Control Channel in E-
Electric, NEC,
UTRA Downlink
Panasonic, Sharp
Fujitsu, Institute for
Infocomm Research,
Transmit Diversity Scheme for MBMS in
R1-070096
E-UTRA Downlink
Mitsubishi Electric,
NEC, Panasonic,
Sharp
Performance Evaluation of Closed Loop- 6.8.3 Noted
R1-070097 Based Antenna Switching Transmit NTT DoCoMo
Diversity in E-UTRA Uplink
R1-070098 Persistent Scheduling in E-UTRA Mitsubishi Electric,
NEC
Frequency Domain Channel-Dependent 6.9.1 Not treated
R1-070099 Scheduling Considering Interference to NTT DoCoMo
Neighbouring Cell for E-UTRA Uplink
CDM-based Multiplexing Method of NTT DoCoMo, 6.9.1 Not treated
Multiple ACK/NACK and CQI for E-UTRA Fujitsu, KDDI,
R1-070100 Uplink Mitsubishi Electric,
Sharp,
Toshiba Corporation
85
AGENDA REVISED BY
ITEM (From)
NTT DoCoMo, KDDI, 6.9.1 Not treated
Repetition of ACK/NACK in E-UTRA Mitsubishi Electric,
R1-070101
Uplink NEC, Panasonic,
Sharp
NTT DoCoMo, KDDI, 6.9.1 Not treated
Performance Enhancement Techniques
R1-070102 Mitsubishi Electric,
for ACK/NACK in E-UTRA Uplink
Sharp
Downlink L1/L2 Control Channel Structure Fujitsu, KDDI,
R1-070103
in E-UTRA - Bits and Coding Mitsubishi Electric,
NEC
Downlink L1/L2 Control Channel Structure
R1-070104 Fujitsu, KDDI, NEC,
in E-UTRA - Mapping
Sharp
NTT DoCoMo, 6.9.2 (R1-063326) Not treated
ACK/NACK Signal Structure in E-UTRA
R1-070105 Fujitsu, NEC,
Downlink
Toshiba Corporation
NTT DoCoMo, Noted
Fujitsu, NEC,
R1-070106 Uplink Timing Control for E-UTRA 6.11
Panasonic, Sharp,
Toshiba Corporation
NTT DoCoMo, (R1-061668) Not treated
Fujitsu, Mitsubishi
Transmission Power Control in E-UTRA
R1-070107 Electric, NEC, Sharp, 6.12
Downlink
Toshiba Corporation
NTT DoCoMo, NEC, Not treated
Transmission Power Control in E-UTRA
R1-070108 Panasonic, Sharp, 6.12
Uplink
Toshiba Corporation
Investigations on Inter-cell TransmissionNTT DoCoMo, NEC, Not treated
R1-070109 Power Control based on Overload Panasonic, Sharp, 6.12
Indicator in E-UTRA Uplink Toshiba Corporation
R1-070110 Network for turbo coding ITRI 6.4 Withdrawn
Turbo decoder parallelism degree for IBP- Noted
R1-070111 ITRI 6.4
like interleaver
IBP interleaver for turbo coding and Noted
R1-070112 ITRI 6.4
shortening position assigning algorithm
R1-070113 Shortening and prunning for turbo coding ITRI 6.4 Not treated
86
AGENDA REVISED BY
ITEM (From)
Description and numerology of the Not treated
R1-070114 Huawei 6.2
Physical Downlink Shared Channel
Spectrum-shaping function for E-UTRA Noted
R1-070115 Huawei 6.3
uplink
Performance of coherent and non- Not treated
R1-070116 Huawei 6.5.2
coherent S-SCH demodulation
Cell-specific integer sequences for R1-070532 Revised in R1-070532
R1-070117 frequency positioning of DL RS on Huawei 6.6.1
subframe basis
Encoding cell-specific information by Not treated
R1-070118 generalized 2-D orthogonal DL RS Huawei 6.6.1
sequences
Inter-cell interference rejection Not treated
R1-070119 Huawei 6.7.2
performance for CDD-type transmission
On the precoding feedback granularity for Noted
R1-070120 Huawei 6.7.3
DL MIMO
R1-070121 Description of UL L1/L2 control message Huawei 6.9.1 Not treated
TDD/FDD E UTRA commonality aspects Not treated
R1-070122 of the reduced-latency DL reference signal Alcatel-Lucent 6.6.1
for FDD E-UTRA
Considerations on the EUTRA DL Not treated
R1-070123 reference signal structure and the DC sub- Alcatel-Lucent 6.6.1
carrier
Comparison of SFBC and CDD for E- Not treated
R1-070124 UTRA in noise and interference limited Alcatel-Lucent 6.7.5
cases
Effects of frequency selective feedback on Noted
precoding in E-UTRA downlink
Spectrum shaping function for E-UTRA R1-070556 Revised in R1-070556
R1-070126 Samsung 6.3
uplink
Performance of UE-specific scrambling for Noted
R1-070127 Samsung 6.3
E-UTRA uplink
Filtering for Non-Synchronized RACH Not treated
R1-070128 Samsung 6.5.1
preamble
Non-Synchronized RACH Preamble Not treated
R1-070129 Samsung 6.5.1
structure to support high mobility
Considerations on codewords to layers Noted
R1-070130 Samsung 6.7.1
mapping for downlink MIMO
87
AGENDA REVISED BY
ITEM (From)
R1-070131 MIMO precoding for E-UTRA Downlink Samsung 6.7.2 Not treated
Performance of Precoded Single User Not treated
R1-070132 Samsung 6.7.2
MIMO with LMMSE receiver
MIMO System Performance with variable R1-070577 Revised in R1-070577
R1-070133 Samsung 6.7.3
frequency granularity of UE feedback
MIMO Link Performance with variable Noted
R1-070134 Samsung 6.7.3
Transmit diversity performance for the Not treated
R1-070135 Samsung 6.7.5
control channels
Transmit diversity performance for the Not treated
R1-070136 Samsung 6.7.5
shared data channels
A Way Forward on Transmit Diversity for Not treated
R1-070137 Samsung 6.7.5
E-UTRA Downlink
R1-070138 Performance of MIMO for E-UTRA uplink Samsung 6.8.1 Noted
Hybrid ARQ for multi-user MIMO in E- Noted
R1-070139 Samsung 6.8.2
UTRA uplink
Downlink Link Adaptation and Related Not treated
R1-070140 Samsung 6.9.2
Control Signaling
R1-070141 Downlink Hybrid ARQ Signaling Samsung 6.9.2 Not treated
DRAFT LS /Proposed RAN WG1 R1-070546 Revised in R1-070546
Response to LS R3-062005=R1-070008
R1-070142 on Siemens, Nokia 4
"Inter-Cell Interference Coordination and
its signalling"
R1-070143 Initial Cell Search Design Motorola 6.5.2 Not treated
Non-initial Cell Search and Neighbor list Not treated
R1-070144 Motorola 6.5.2
impact
R1-070145 P-SCH Sequence Design Motorola 6.5.2 Noted
R1-070146 S-SCH Sequence Design Motorola 6.5.2 Not treated
Four Transmit Antenna Downlink RS Not treated
R1-070147 Motorola 6.6.1
Formats for EUTRA
R1-070148 Downlink RS Placement within a Slot Motorola 6.6.1 Not treated
R1-070149 Hopping of Downlink Reference Signals Motorola 6.6.1 Noted
Simulation results for GCL based DL Not treated
R1-070150 Motorola 6.6.1
reference signals
Proposal for dedicated pilots in downlink Not treated
R1-070151 Motorola 6.6.1
precoding for EUTRA MIMO
R1-070152 Uplink RS generation methods Motorola 6.6.2 Noted
88
AGENDA REVISED BY
ITEM (From)
R1-070153 Uplink Reference Signal Planning Aspects Motorola 6.6.2 Not treated
Further results on Frequency Domain Noted
R1-070154 Motorola 6.7.2
Adaptive Precoding for E-UTRA MIMO
Frequency-Domain Adaptive Precoding Noted
R1-070155 Motorola 6.7.2
Granularity for EUTRA
Direct channel feedback for obtaining Not treated
R1-070156 channel state information at Node B in Motorola 6.7.3
EUTRA
Uplink sounding for obtaining channel Not treated
R1-070157 Motorola 6.7.3
state information at Node B in EUTRA
R1-070158 Precoding Feedback Overhead Motorola 6.7.2 Not treated
E-UTRA Open Loop Transmit Diversity Not treated
R1-070159 Motorola 6.7.5
Performance in Correlated Channels
R1-070160 E-UTRA Open Loop Transmit Diversity Motorola 6.7.5 Not treated
E-UTRA DL Distributed Multiplexing and Not treated
R1-070161 Motorola 6.10
Mapping Rules
E-UTRA UL L1/L2 Control Channel Not treated
R1-070162 Motorola 6.9.1
Mapping
Minimizing the Non-synchronized RACH Not treated
R1-070163 Procedure Requirement During LTE InterDigital 6.5.1
Handover
R1-070164 Cell Search SCH Proposal for E-UTRA InterDigital 6.5.2 Not treated
System Performance Evaluation of Uplink Noted
R1-070165 InterDigital 6.8.1
Single User MIMO for E-UTRA
Combined Open Loop/Closed Loop Uplink Not treated
R1-070166 Power Control with Interference Mitigation InterDigital 6.12
for E-UTRA
System Performance Evaluation of Not treated
R1-070167 Combined Open Loop/ Closed Loop InterDigital 6.12
Uplink Power Control for E-UTRA
Beamforming Compact Codebook Method Not treated
R1-070168 Broadcom 6.7.2
and Results in E-UTRA
Beamforming Frequency and Time Update Noted
R1-070169 Broadcom 6.7.2
Requirements in E-UTRA
UE Feedback Classification and CQI R1-070543 Revised in R1-070543
R1-070170 Broadcom 6.7.3
Characterization in E-UTRAN
89
AGENDA REVISED BY
ITEM (From)
An ARP base 4 hardware saving, flexible Noted
granularity an flexible parallelism ARP
R1-070171 Broadcom 6.4
interleaver suitablew for all possible block
sizes in 3GPP LTE Turbo Codes
Formulaic Collision-free Memory Noted
R1-070172 Accessing Mapping for Parallel Turbo Broadcom 6.4
Decoding with ARP interleaver
Tail-Biting Encoding for 3GPP LTE Turbo R1-070544 Revised in R1-070544
R1-070173 Codes of Arbitrary Number of Information Broadcom 6.4
Bits and performance comparison
Performance Evaluation of SC-FDMA with Noted
STBC in E-UTRA Uplink
Reducing Transmission Control Signalling Not treated
R1-070175 ASUSTeK 6.9
with Bit Correction (BC)
20ms TTI Co-existence with 5ms TTI for Noted
E-DCH of
R1-070176 ZTE 8
LCR TDD：Further Revised System Level
Simulation Results
R1-070177 Computation of E-DPDCH gain factors Nokia 5 Noted
System results for reduced E-DPCCH Noted
R1-070178 Nokia 5
overhead
R1-070179 HS-SCCH structure for MIMO and 64QAM Nokia 7.1 Noted
R1-070180 ACK/NACK transmission in MIMO Mode Nokia 7.1 Noted
CQI Report for WCDMA MIMO, Revised Noted
R1-070181 Nokia 7.1
Proposal
UL DPCCH transmission with HS-DPCCH Noted
R1-070182 Nokia 7.2
during DPCCH gating
R1-070183 Compressed Mode with CPC Nokia 7.2 Noted
R1-070184 Preamble transmission simplification Nokia 7.2 Noted
R1-070185 16QAM link results Nokia 7.3.2 Noted
Downlink L1/L2 control signalling: Not treated
R1-070186 multiplexing, configuraiton and logical Panasonic 6.9.2
receiver model
R1-070187 DCT partitioning for CQI reporting Panasonic 6.9.1 Not treated
Non-synchronized RACH preamble Panasonic, NTT Noted
R1-070188 6.5.1
structure for high mobility UE DoCoMo
Zadoff-Chu sequence allocation on RACH Panasonic, NTT Not treated
R1-070189 6.5.1
for complexity reduction DoCoMo
90
AGENDA REVISED BY
ITEM (From)
Uplink reference signal structure and Panasonic, NTT 6.6.2 Noted
R1-070190
allocation for E-UTRA DoCoMo
Frequency selective/non-selective Noted
R1-070191 Panasonic 6.7.2
precoding for SU-MIMO
UE feedback information for MIMO Not treated
support
MIMO codebook size discussion for both Not treated
MU- and SU-MIMO
R1-070194 TS 36.213 v0.1.1 Editor, Motorola 6.1 Endorsed as v0.2.0 in R1-070563
One improvement on SCH Location for E- R1-070575 Revised in R1-070575
R1-070195 ZTE, CATT 6.5.2
UTRA TDD
A New Method on P-SCH Design and Not treated
R1-070196 ZTE 6.5.2
Detection
An Efficient UL resource allocation control Not treated
R1-070197 ZTE 6.9.2
signaling
Some considerations about 64QAM for Noted
R1-070198 ZTE 7.3.1
HSDPA
UE Paring for E-UTRA Uplink Multiuser Noted
R1-070199 ZTE 6.8.2
MIMO
UE Feedback Aspects for Downlink MIMO Not treated
R1-070200 ZTE 6.7.3
in E-UTRA
Non-codebook based precoding in E- Noted
R1-070201 ZTE, CATT 6.7.2
UTRA TDD
R1-070202 Codebook Design for E-UTRA MIMO ZTE 6.7.2 Not treated
Multiple Continuous RB Allocation Not treated
R1-070203 ZTE 6.2
Frequency Hopping in E-UTRAN Uplink
Observation on MBMS extended physical Noted
R1-070204 Layer Parameter for Shared Carrier Mode ZTE 6.2
on 2Ghz Carrier Frequency
Uplink non-data-associated control Not treated
R1-070205 ZTE 6.9.1
signaling
Assistant Feedback Channel for E-UTRA Withdarwn
R1-070206 TDD Uplink Transmission Power Control ZTE 6.12
and AMC
Assistant Feedback Channel for E-UTRA Withdarwn
R1-070207 TDD to Report Downlink Transmission ZTE 6.7.3
CQI and ACK/NACK
91
AGENDA REVISED BY
ITEM (From)
Simulation results of Pout, ACLR, PAE Noted
R1-070208 and Power consumption vs. various roll-off Mitsubishi Electric 6.3
factor in LTE Uplink
A PIL-Based New Contention-Free Noted
R1-070209 Mitsubishi Electric 6.4
Interleaver for Turbo Codes
Further Evaluation of CQI feedback Not treated
R1-070210 Mitsubishi Electric 6.9.1
schemes
R1-070211 Signaling Way of Resource Assignment Mitsubishi Electric 6.9.2 Not treated
Physical Channel for Timing Not treated
Synchronization
Cyclic shift-hopping for uplink sounding Not treated
R1-070213 ETRI 6.6.2
reference signal
System Level Simulations of Transmit Not treated
R1-070214 Huawei 6.7.5
Diversity for CCPCH
Link Level Simulations of Transmit Not treated
R1-070215 Huawei 6.7.5
Diversity for CCPCH with IRC Receiver
Further Results on Multiple P-SCH Not treated
R1-070216 Sharp 6.5.2
Complexity for E-UTRA Cell Search
Staggered Uplink Reference Signal Not treated
R1-070217 Sharp 6.6.2
Allocation
Performance Comparison between the Not treated
Conventional CDD and a Sub-carrier
R1-070218 Sharp 6.7.5
Grouping CDD scheme for the common
control channel in the E-UTRA Downlink
System-Level Evaluation using the low Not treated
R1-070219 Fujitsu 6.4
rate extension of UTRA turbo code
Overview and Way forward on MIMO Freescale Noted
R1-070220 6.7.2
Precoding in DL EUTRA Semiconductor
Efficient method for feedback reduction Freescale Not treated
R1-070221 and feedback mechanism for precoded Semiconductor 6.7.3
MIMO in EUTRA
Aspects of SU/MU Switching and MU- Freescale Noted
R1-070222 6.7.4
MIMO in DL EUTRA Semiconductor
Freescale R1-070608 Revised in R1-070608
R1-070223 Scheme for MU-MIMO in DL EUTRA 6.7.4
Semiconductor
R1-070224 Uplink Frequency Hopping LG Electronics 6.2 Not treated
On the consideration of parallel TC LG Electronics Not treated
R1-070225 6.4
decoder for LTE
92
AGENDA REVISED BY
ITEM (From)
Non-Synchronized Random Access LG Electronics Not treated
R1-070226 6.5.1
Design under Frequency Offset
Ways to Mitigate Frequency Offset with LG Electronics Not treated
R1-070227 6.5.1
CAZAC Cyclic Shift
R1-070228 Multi-TTI RACH Allocation Methods LG Electronics 6.5.1 Not treated
Comparison of single PSC and multiple LG Electronics Not treated
R1-070229 6.5.2
PSCs
P-SCH sequence design for single and LG Electronics Not treated
R1-070230 6.5.2
multiple PSCs
R1-070231 S-SCH sequence design LG Electronics 6.5.2 Not treated
Performance evaluation of DL reference LG Electronics Not treated
R1-070232 6.6.1
signal on control channel
Performance evaluation of uplink LB DM LG Electronics Not treated
R1-070233 6.6.2
reference signal
Several Types of Uplink Reference Signal LG Electronics Not treated
R1-070234 6.6.2
Sequence
R1-070235 Codeword to layer mapping for SU-MIMO LG Electronics 6.7.1 Noted
LG Electronics, Noted
R1-070236 Precoding for E-UTRA downlink MIMO Samsung, NTT- 6.7.2
DoCoMo
System Level Evaluation of the CDD- LG Electronics Not treated
R1-070237 6.7.2
based Precoding
Codebook evaluation for E-UTRA MIMO LG Electronics Not treated
R1-070238 6.7.2
precoding - 2Tx and 4Tx rank 1
Codebook design and evaluation for E- LG Electronics Withdrawn
R1-070239 UTRA MIMO precoding - 4Tx rank 1~2 6.7.2
scheme
Link Performance Evaluation of Precoding LG Electronics Noted
R1-070240 6.7.2
Scheme According to the Cluster Size
Evaluation of SFBC and CDD for control LG Electronics R1-070598 Revised in R1-070598
R1-070241 6.7.5
channel with real channel estimation
System level performance analysis LG Electronics Not treated
R1-070242 between best-M and DCT based CQI 6.9.1
reporting schemes
R1-070243 Downlink control signaling overheads LG Electronics 6.9.2 Not treated
Modification of Downlink asynchronous LG Electronics (R1-063175) Not treated
R1-070244 6.9.2
HARQ scheme
93
AGENDA REVISED BY
ITEM (From)
Modification of Uplink synchronous HARQ LG Electronics Not treated
R1-070245 6.9.2
scheme
R1-070246 Downlink ACK/NACK transmission LG Electronics 6.9.2 Not treated
Downlink Cat0 signaling for scheduling LG Electronics Not treated
R1-070247 6.9.2
assignments
Consideration on the number of scheduled LG Electronics Not treated
R1-070248 6.9.2
UEs in downlink
On the consideration of the uplink UE- LG Electronics Noted
R1-070249 6.10
specific bit-level scrambling
R1-070250 Downlink Transmit Power Boosting LG Electronics 6.12 Not treated
Power control of uplink shared data LG Electronics Not treated
R1-070251 6.12
channel
R1-070252 E-MBMS inter resource block combining Alcatel-Lucent 6.7.5 Withdrawn
R1-070253 Turbo Code Tail Methods Texas Instruments 6.4 Not treated
R1-070254 Parallel Turbo Decoder Options Texas Instruments 6.4 Not treated
Improved Non-Synchronized Random Not treated
R1-070255 Texas Instruments 6.5.1
Access structure for E-UTRA
Interference between Data and RACH in Not treated
EUTRA
Non Synchronized Random Access Not treated
Performance in High Doppler Conditions
Non Synchronized Random Access Not treated
Collision Rate and Performance Impact
Contention-Free Preamble-Based Noted
Synchronized Random Access
Contention-Free Preamble-Based Not treated
R1-070260 Synchronized RACH: Comparison with Texas Instruments 6.5.1
other solutions
Further Details of SCH Based on Not treated
Approach 1 Option 2
R1-070262 Performance of 3-Stage Cell Search Texas Instruments 6.5.2 Noted
Performance of Coherent and Non- Not treated
Coherent Stage 2 Detection
Comparison of Different S-SCH Structures Not treated
for E-UTRA Cell Search
Summary of Reflector Discussions on Noted
EUTRA DL RS
94
AGENDA REVISED BY
ITEM (From)
Summary of Reflector Discussions on Noted
EUTRA UL RS
Sounding Reference Signal Assignments Not treated
in E-UTRA Uplink
Sequence Hopping for the Uplink Not treated
Reference Signal
Multi-Codeword Principles for E-UTRA Noted
MIMO
Further Details on Codebook-Based Pre- Noted
coding for E-UTRA
Precoding Codebook Design For 2 Node- Not treated
B Antennas
Precoding Codebook Design For 4 Node- Not treated
B Antennas
R1-070273 Views on MIMO-Related UE Feedback Texas Instruments 6.7.3 Not treated
R1-070274 Rank Feedback For MIMO E-UTRA Texas Instruments 6.7.3 Noted
ACK/NAK Transmission without Noted
R1-070275 Reference Signal Overhead in E-UTRA Texas Instruments 6.9.1
Uplink
L1/L2 Control Channel Size and Cat0 in E- Noted
UTRA Downlink
ACK/NAK Channel Transmission in E- Not treated
UTRA Downlink
Multiplexing of L1/L2 Control Channels in Not treated
E-UTRA Downlink
Maximum Number of Scheduled UEs per Not treated
Sub-Frame in E-UTRA Downlink
Uplink Synchronization management in Not treated
R1-070280 Texas Instruments 6.11
LTE_ACTIVE
R1-070281 Uplink Timing Control for E-UTRA Texas Instruments 6.11 Noted
Timing Advance Accuracy from Non Not treated
R1-070282 Texas Instruments 6.11
Synchronized Random Access in E-UTRA
R1-070283 Downlink Power Control for E-UTRA Texas Instruments 6.12 Not treated
Fractional Time Re-Use Interference Co- 6.12 Not treated
R1-070284 Texas Instruments
Ordination in E-UTRA Downlink
Uplink Power Control for EUTRA: 6.12 Not treated
R1-070285 Optimizing the Trade-off between Cell- Texas Instruments
Edge and Cell-Average Throughputs
95
AGENDA REVISED BY
ITEM (From)
Preamble design of non-synchronized Not treated
R1-070286 CATT，RITT 6.5.1
RACH for E-UTRA TDD
Implicit message transmitted for non- Not treated
R1-070287 CATT 6.5.1
synchronized RACH
Comparing Hybrid and cross-correlation Not treated
R1-070288 CATT 6.5.2
method for cell search
Performance of S-SCH detection using Not treated
R1-070289 CATT 6.5.2
channel estimation by P-SCH
Downlink dedicated reference signal Noted
R1-070290 CATT，RITT，ZTE 6.6.1
aspects in EUTRA TDD
Downlink reference signal aspects for non- Not treated
R1-070291 CATT，RITT 6.6.1
codebook based pre-coding in TDD mode
Uplink LB vs. SB Structure for EUTRA Not treated
R1-070292 CATT 6.6.2
TDD
Single user throughput simulation results Noted
R1-070293 for non-codebook based pre-coding inCATT 6.7.2
EUTRA TDD
Link level simulation results for non- Noted
R1-070294 codebook based pre-coding in EUTRACATT 6.7.2
TDD (GBF)
Link level simulation results for non- Noted
R1-070295 codebook based pre-coding in EUTRACATT 6.7.2
TDD (SVD)
Uplink transmit diversity scheme to Not treated
R1-070296 provide full CSI to support downlink MIMO CATT 6.7.3
transmission for TDD operation
E-UTRA Downlink control signaling for Not treated
R1-070297 CATT ,Huawei 6.9.2
TDD system
LCR TDD: Structure and Coding for E- Noted
R1-070298 CATT 8
HICH
Transport Block Size Signalling for Noted
R1-070299 CATT 8
1.28Mcps TDD EUL
Text Proposal for TR 25.827 This text proposal was agreed to be included
R1-070300 CATT 8
in TR with removal of section 11.3
Coding of E-DCH for 1.28Mcps TDD This text proposal was agreed to be included
R1-070301 CATT 8
Enhanced Uplink in TR
Text Proposal on Power control and Noted
R1-070302 CATT 8
Synchronization control for 1.28Mcps EUL
96
AGENDA REVISED BY
ITEM (From)
Simulation Results of 20ms TTI and 5ms Noted
R1-070303 CATT 8
TTI for LCR TDD E-DCH
Proposed Response to LS on Primary Noted
R1-070304 Siemens 4
BCH Transmission
Proposed Response to LS on Noted
R1-070305 Siemens, Nokia 4
Synchronization at Handover
R1-070306 Uplink Extended Cyclic Prefix Use Cases Siemens 6.2 Noted
Reduction of Initial E-UTRA Cell Search Not treated
R1-070307 Siemens 6.5.2
Delay
Considerations on E-UTRA Uplink Time Not treated
R1-070308 Siemens 6.11
Synchronization
Dual tracking mode feedback for unitary Not treated
R1-070309 Siemens 6.7.3
precoding
DL Multiplexing of Localized and Not treated
R1-070310 Siemens 6.10
Distributed Resource Blocks
Aspects of DL HARQ in Frequency Not treated
R1-070311 Siemens 6.10
Selective Channels
R1-070312 LTE Channel Coding Aspects Siemens 6.10 Not treated
Proposal for Constellation Rearrangement R1-070541 Revised in R1-070541
R1-070313 Siemens 7.3.1
for 64-QAM
Basic Multiplexing Schemes of Multiple NTT DoCoMo Not treated
R1-070314 L1/L2 Control Information in E-UTRA 6.9.2
Downlink
Capacity analysis of E-UTRA non- Not treated
R1-070315 synchronized RACH with additional control Alcatel-Lucent 6.5.1
information
Non-synchronized RACH in support of Not treated
high-speed UEs: detailed parameters
Load control for E-UTRA non- Not treated
synchronized RACH
Link-level results for multiuser eigenmode Noted
transmission with limited feedback
Multiplexing method for uplink non-data- Not treated
associated control signals
R1-070320 E-UTRA UL Timing Control Alcatel-Lucent 6.11 Not treated
Considerations for frequency control in E- Not treated
R1-070321 Alcatel-Lucent 6.11
UTRA uplink
97
AGENDA REVISED BY
ITEM (From)
Fractional Power Control using Pilot Not treated
R1-070322 Power Ratio Measurements for the E- Alcatel-Lucent 6.12
UTRA Uplink
R1-070323 PCI_CQI Definition for Rel-7 MIMO Huawei 7.1 Withdarwn
Synchronization criteria during Noted
R1-070324 Huawei 7.2
discontinuous transmission
R1-070325 HSDPA UE categories Huawei 7.3.1 Noted
R1-070326 Coding for HS-DSCH to support 64QAM Huawei 7.3.1 Noted
Transmission Control in Enhanced Noted
R1-070327 Huawei 7.4
CELL_FACH State
Enhanced multi-cell transmission for Not treated
R1-070328 Huawei 7.5
Mixed carrier MBMS
Enhanced Multi-Cell Transmission for Not treated
R1-070329 Huawei 7.5
Mixed carrier MBMS - Link level simulation
R1-070330 Uplink control channel multiplexing Samsung 6.9.1 Not treated
R1-070331 CQI reporting for E-UTRA Samsung 6.9.1 Not treated
Control Channel Structure for EUTRA Not treated
R1-070332 Samsung 6.9.2
Downlink
R1-070333 VoIP support in LTE Samsung 6.9.2 Not treated
Discussion on control signalling for Not treated
R1-070334 Samsung 6.9.2
persistent scheduling of VoIP
R1-070335 Uplink timing control Samsung 6.11 Not treated
R1-070336 On UE tx bandwidth Samsung 6.2 Noted
R1-070337 UL LFDMA with hopping Samsung 6.2 Not treated
Performance of DL distributed Not treated
R1-070338 Samsung 6.2
transmission
R1-070339 Discussion on uplink power control Samsung 6.12 Not treated
Discussion on the cell planning with non- Noted
R1-070340 Samsung 6.5.1
synchronized RACH
Views on Turbo interleaver candidates: Not treated
R1-070341 Samsung 6.4
complexity and other aspects
Turbo coding performance with Rel'6 PIL Noted
R1-070342 Samsung 6.4
and IBPI
R1-070343 LTE MIMO email discussion summary Samsung 6.7 Noted
Resource-Block mapping of Distributed Not treated
R1-070344 Philips 6.2
Transmissions in E-UTRA downlink
Text Proposal for MIMO resource Withdrawn
R1-070345 Philips 6.7
definition for E-UTRA
98
AGENDA REVISED BY
ITEM (From)
Comparison of MU-MIMO feedback Noted
R1-070346 schemes with multiple UE receive Philips 6.7
antennas
Receiver Phase Reference for Support of Noted
R1-070347 Philips 6.7
MU-MIMO
Control of CQI feedback signalling in E- 6.9.1 Not treated
R1-070348 Philips
UTRA
Block codes for CQI reporting for Rel-7 Noted
R1-070349 Philips 7.1
MIMO
R1-070350 HS-SCCH for MIMO and 64QAM Philips 7.1 R1-070537 Revised in R1-070537
HARQ process handling for Rel-7 FDD 7.1 Noted
R1-070351 Philips
MIMO
Continuous Packet Connectivity in Noted
R1-070352 Philips 7.2
conjunction with Compressed Mode
Text proposal for Continuous Packet Revised in R1-070580
R1-070353 Philips 7.2
Connectivity Clarifications
R1-070354 Pilot power setting for 16QAM in uplink Philips 7.3.2 Noted
NEC Group, NTT Noted
R1-070355 Capacity Impact of DFT size restriction 6.2
DoCoMo
Downlink Distributed Resource Block NEC Group, NTT Not treated
R1-070356 6.2
Mapping DoCoMo
Issue of dynamic CP length change in a Noted
R1-070357 cell with mixed NEC Group 6.2
unicast and MBMS transmission
Primary Synchronization Codes (PSC) for 6.5.2 Not treated
R1-070358 NEC Group
E-UTRA
Definition of Cyclic Shift in Code Division 6.6.2 Not treated
R1-070359 NEC Group
Multiplexing
Codebook based precoding for MIMO Not treated
R1-070360 NEC Group 6.7.2
EUTRA
Multiplexing for data-non-associated Not treated
R1-070361 NEC Group 6.9.1
control signal in EUTRA uplink
R1-070362 Compressed CQI Reporting Scheme NEC Group 6.9.1 Not treated
Signalling discontinuous localised Not treated
R1-070363 allocations in E-UTRA NEC Group 6.9.2
downlink
NEC Group, NTT Not treated
R1-070364 Uplink Resource Allocation for E-UTRA 6.9.2
DoCoMo
99
AGENDA REVISED BY
ITEM (From)
R1-070365 Structure of uplink reference signal Fujitsu 6.6.2 Noted
R1-070366 UL Power Control Siemens 6.12 Not treated
Sequence Allocation Method for E-UTRA Not treated
R1-070367 Huawei 6.6.2
Uplink Reference Signal
System level comparison of best-M and Not treated
R1-070368 Huawei 6.9.1
DCT-based CQI compression schemes
Answer to RAN2 LS on Primary BCH Noted
R1-070369 Nokia 4
Transmission
R1-070370 LS on Synchronization at handover Nokia 4 Withdrawn
Draft Reply LS on “Inter-Cell Interference Withdrawn
R1-070371 Nokia 4
Coordination and its signalling”,
Idle Period position for E-UTRA TDD with Noted
R1-070372 Nokia 6.2
Generic frame structure
R1-070373 Need for Frequency Multiplexing of MBMS Nokia, Motorola 6.2 R1-070603 Revised in R1-070603
On the Feasibility of Higher UE Maximum Noted
R1-070374 Nokia 6.3
Output Power
Coverage analysis of UL Spectrum Noted
R1-070375 Nokia 6.3
Shaping
R1-070376 Performance of tail-biting turbo codes Nokia 6.4 Not treated
Restricted sets of RACH preamble Noted
R1-070377 signatures for environments with high Nokia 6.5.1
Doppler shifts
R1-070378 UL Resource Request for LTE System Nokia 6.5.1 Noted
Multiplexing for Dedicated Resource Noted
R1-070379 Nokia 6.5.1
Request
Filtering Roll-off for Non-synchronized (R1-063364) Not treated
R1-070380 Nokia 6.5.1
Transmissions
Cell Search Performance for Different Noted
R1-070381 Nokia 6.5.2
Number of PSC in Synchronized Network
Cell Search Performance for Approach 1 Noted
R1-070382 Nokia 6.5.2
and Approach 2
Reference Signals for Mixed Carrier 6.6.1 (R1-063367) Not treated
R1-070383 Nokia
MBMS
R1-070384 UL Reference Signals Nokia 6.6.2 Noted
Layer to Codeword mapping for DL SU- Noted
R1-070385 Nokia 6.7.1
MIMO
Performance of frequency dependent Noted
R1-070386 Nokia 6.7.3
precoding for 2x2 LTE DL SU-MIMO
100
AGENDA REVISED BY
ITEM (From)
On UL Feedback of DL SU-MIMO Rank Noted
R1-070387 Nokia 6.7.3
and DL SU-MIMO Rank Adaptation
R1-070388 Reduced CQI design for DL SU-MIMO Nokia 6.7.3 Not treated
Open Loop DL Transmit Diversity for the (R1-063375) Not treated
R1-070389 Nokia 6.7.5
Shared Data Channel
Open Loop DL Transmit Diversity for (R1-063376) Not treated
R1-070390 Nokia 6.7.5
Common Control Channels
Single-user MIMO support in E-UTRA Noted
R1-070391 Nokia 6.8.1
uplink
Benchmarking of antenna switching and Noted
R1-070392 Nokia 6.8.3
frequency hopping for LTE FDD UL
ACK/NACK coverage in the absence of (R1-063382) Not treated
R1-070393 Nokia 6.9.1
UL data
Multiplexing of L1/L2 Control Signals Not treated
R1-070394 Nokia 6.9.1
between UEs in the abcense of UL data
CDM based Control Signal multiplexing w/ Not treated
R1-070395 Nokia 6.9.1
and w/o additional RS
Evaluation Method for Benchmarking CQI (R1-063383) Not treated
R1-070396 Nokia 6.9.1
Schemes for LTE
CQI Design and its Impact to DL (R1-063384) Not treated
R1-070397 Nokia 6.9.1
Performance
Structure and transport of the Downlink Not treated
R1-070398 Nokia 6.9.2
Control Channel
Considerations on the False Positive (R1-063389) Not treated
R1-070399 Probability for the DL Shared Control Nokia 6.9.2
Channel
R1-070400 UL Timing Accuracy and Update Rate Nokia 6.11 (R1-063377) Not treated
R1-070401 UL Power Control Nokia 6.12 (R1-063378) Not treated
R1-070402 Power Control Email Discussion Summary Nokia 6.12 Noted
R1-070403 UTRA Measurement Quantity Selection Nokia 6.13 Not treated
Initial simulation results comparing Not treated
R1-070404 different E-UTRA UE DL measurement Nokia 6.13
quantities
Non-synchronized RACH Sampling Rate Not treated
R1-070405 ZTE 6.5.1
in LTE
Text Proposal for E-HICH/E-AGCH Noted
R1-070406 structure and coding for 1.28Mcps TDD TD-Tech 8
EUL
101
AGENDA REVISED BY
ITEM (From)
Text proposal for power control for Noted
R1-070407 TD-Tech 8
1.28Mcps TDD Enhanced Uplink
UE capability aspect for 1.28Mcps TDD R1-070566 Revised in R1-070566
R1-070408 TD-Tech 8
EUL
Power Setting for Interference Alcatel-Lucent 6.12 R1-070611 Revised in R1-070611
R1-070409 Coordination including Pilot and Control
Channels
Signaling Resource Allocations in DL Alcatel-Lucent 6.9.2 Not treated
R1-070410
Control Channel
Summary of the E-mail discussion on NTT DoCoMo 6.4 Noted
R1-070411
existing interleaver
Summary of the E-mail discussion on NTT DoCoMo 6.4 Noted
R1-070412
channel coding
R1-070413 Content of the preamble LG Electronics 6.5.1 Not treated
R1-070414 Analysis of E-DPDCH with 16QAM Qualcomm Europe 7.3.2 Noted
Qualcomm Europe, Noted
R1-070415 Enhanced Phase Reference for 16-QAM 7.3.2
Ericsson
UL system analysis with proposed new F- Noted
R1-070416 Qualcomm Europe 5
DPCH
25.211CR0232 (Rel-7, C) "Redesigned F- R1-070558 Revised in R1-070558
DPCH"
25.214CR0433 (Rel-7, C) "Redesigned F- R1-070559 Revised in R1-070559
DPCH"
System analysis and further details of R1-070545 Noted
proposed new coding for E-DPCCH
25.211CR0233 (Rel-7, C) "New coding for Withdrawn
E-DPCCH"
Proposed operation of CM equivalent Noted
R1-070421 Qualcomm Europe 7.2
behaviour using CPC
Editor, Qualcomm Endorsed as v0.3.0 in R1-070562
R1-070422 TS 36.212 v0.2.2 6.1
Europe
R1-070423 Subset of allowed DFT sizes for UL Qualcomm Europe 6.2 Noted
R1-070424 Longer CP for MBMS Qualcomm Europe 6.2 Noted
R1-070425 Link analysis of QPP based interleaver Qualcomm Europe 6.4 Noted
R1-070426 UL requests Qualcomm Europe 6.5.1 Noted
Impact of high Doppler to random access Not treated
R1-070427 Qualcomm Europe 6.5.1
preamble detection
102
AGENDA REVISED BY
ITEM (From)
Further analysis of initial cell search for Noted
Approach 1 and 2 - single cell scenario
Further analysis of initial cell search for Noted
Approach 1 and 2 - multi cell scenario
Neighbor cell search: analysis and Not treated
simulations
DL RS for Multiplexed Unicast and MBMS Not treated
Configurations
UL RS structure issues with frequency Noted
domain CDM
UL RS Planning and Structure with Long Noted
Blocks
R1-070434 Precoding details for DL MIMO Qualcomm Europe 6.7.2 Not treated
R1-070435 UE feedback for DL MIMO Qualcomm Europe 6.7.3 Not treated
R1-070436 Aspects of UL MIMO Qualcomm Europe 6.8.1 Noted
R1-070437 Proposed structure for UL ACK and CQI Qualcomm Europe 6.9.1 Noted
Proposed structure for DL ACK and Not treated
PDCCH
Principles of Unicast Scheduling for Not treated
Downlink and Uplink
R1-070440 Timing control Qualcomm Europe 6.11 Not treated
Overview of Uplink Intra and Inter Cell Qualcomm Europe, Not treated
R1-070441 6.12
Power Control NTT DoCoMo
R1-070442 Inter-cell interference control Qualcomm Europe 6.12 Not treated
Uplink Power Control Simulations – Not treated
Mobility in Urban Canyons
R1-070444 E-MBMS inter-resource block combining Alcatel-Lucent 6.2 Not treated
Cell Search Performance in Synchronized Not treated
R1-070445 Nortel 6.5.2
Networks
Transmit Diversity for Synchronization and Not treated
R1-070446 Nortel 6.7.5
Cell Search in a Synchronized System
Frame Timing Acquisition based on P- Not treated
R1-070447 Nortel 6.5.2
SCH
Open-loop Adaptive Antenna Switching for Noted
R1-070448 Nortel 6.8.3
UL MIMO
System Level Performance Comparison Noted
R1-070449 Nortel 6.8.1
for UL MIMO
103
AGENDA REVISED BY
ITEM (From)
Signaling Channel Designing for DL Not treated
R1-070450 Nortel 6.9.2
Adaptive MIMO
Timing Synchronization Performance Not treated
R1-070451 Nortel 6.5.2
Evaluation
R1-070452 Extended SCH for non-initial cell search Nortel 6.5.2 Not treated
Turbo Interleaver Performance Not treated
R1-070453 Nortel 6.4
Comparison
Discussion on LTE Turbo Interleaver Not treated
R1-070454 Nortel 6.4
selection
Further Performance Evaluation of Not treated
R1-070455 Downlink Transmit Diversity Schemes for Nortel 6.7.5
2- and 4-Branch L1/L2 Control
Benefits of 7.5 kHz Numerology with Nortel, Orange, Noted
R1-070456 6.2
43dBm Transmit Power CMCC
On Codebook Index Feedback and Not treated
R1-070457 Nortel 6.7.3
Beamforming Matrix Verification
Differential Codebook for LTE Downlink Not treated
R1-070458 Nortel 6.7.4
Closed-Loop MIMO
Further Discussion on Adaptive Fractional Not treated
R1-070459 Nortel 6.12
Frequency Reuse
Further results on the impact of speed, Noted
feedback period, and sub-channel
R1-070460 Nortel 6.7.3
bandwidth on the performance of downlink
closed loop schemes for 4-Tx LTE
R1-070461 DFT size for uplink transmissions Ericsson 6.2 Noted
QPP Interleaver Designs for LTE Turbo Noted
R1-070462 Ericsson 6.4
Coding
Contention-Free Interleavers vs Noted
Contention-Avoidance Decoding solutions
Performance Comparison of LTE Turbo Not treated
Internal Interleaver Proposals
R1-070465 LTE uplink reference-signal structure Ericsson 6.6.2 Not treated
Precoding Considerations in LTE MIMO R1-070573 Revised in R1-070573
R1-070466 Ericsson 6.7.2
Downlink
CQI delay impact on downlink multi- R1-070574 Revised in R1-070574
R1-070467 Ericsson 6.7.3
antenna systems for E-UTRA
Two- and four-antenna transmit diversity Not treated
R1-070468 Ericsson 6.7.5
performance for the SCCH
104
AGENDA REVISED BY
ITEM (From)
R1-070469 SU-MIMO and 64-QAM in E-UTRA Uplink Ericsson 6.8.1 Noted
R1-070470 Antenna hopping for LTE uplink Ericsson 6.8.3 Noted
R1-070471 Scheduling Request in E-UTRAN Ericsson 6.9.1 Not treated
Uplink Control Signaling – Summary of e- Noted
R1-070472 Ericsson 6.9.1
mail discussions
Uplink control signaling and 10 MHz UE Noted
R1-070473 Ericsson 6.9.1
transmission capability
R1-070474 Timing advance for E-UTRA uplink Ericsson 6.11 Not treated
Intra-cell Uplink Power Control for E- Not treated
R1-070475 Ericsson 6.12
UTRA – Proposed Mechanism
R1-070476 UTRA – Control Channel Performance Ericsson 6.12
Evaluation
R1-070477 UTRA – Traffic Channel Performance Ericsson 6.12
Evaluation
Inter-cell Uplink Power Control for E- Not treated
R1-070478 Ericsson 6.12
UTRA
Physical Layer Measurements in E- Not treated
R1-070479 Ericsson 6.13
UTRAN
R1-070480 Duplex operation Ericsson 6.2 Noted
Spectral efficiency comparison of possible Noted
R1-070481 Ericsson 4
MBMS transmission schemes
R1-070482 On MIMO operation in TDD Ericsson 6.7.2 Noted
Ericsson, Nokia, Noted
R1-070483 LTE Turbo Coding Interleaver 6.4
Motorola, Qualcomm
R1-070484 QPP interleaver parameters Ericsson, Motorola 6.4 Noted
TDD MBMS Physical Layer Noted
R1-070485 Enhancements: Overview and Impact to IPWireless 7.5
RAN1 Specifications
Support for MBSFN operation: draft CR Not treated
R1-070486 IPWireless 7.5
25.221
25.222
25.223
25.224
105
AGENDA REVISED BY
ITEM (From)
Consideration on non-codebook based 6.7.2 R1-070576 Revised in R1-070576
R1-070490 IPWireless
pre-coding for TDD
Comparison between codebook and non- 6.7.2 Withdrawn
codebook based pre-coding for TDD
R1-070492 On UL Reference Signal Structure Toshiba 6.6.2 Not treated
FEC Coding of type-B CQI / PCI R1-070567 Revised in R1-070567
R1-070493 InterDigital 7.1
Information
R1-070494 HARQ process signaling for UTRA MIMO Ericsson 7.1 Noted
R1-070495 On CQI for UTRA MIMO Ericsson 7.1 Noted
R1-070496 On Synchronization and Mobility with CPC Ericsson 7.2 Noted
Ericsson, Qualcomm Noted
R1-070497 Introduction of 64QAM for HSDPA 7.3.1
Europe
25.201 CR0026 (Rel-7, B) "Introduction of Ericsson, Qualcomm R1-070582 Revised in R1-070582
R1-070498 7.3.1
64QAM for HSDPA" Europe
R1-070499 7.3.1
R1-070500 7.3.1
R1-070501 7.3.1
R1-070502 7.3.1
Ericsson, Qualcomm Noted
R1-070503 Introduction of 16QAM for HSUPA 7.3.2
Europe
R1-070504 7.3.2
16QAM for HSUPA" Europe
R1-070505 7.3.2
R1-070506 7.3.2
R1-070507 7.3.2
R1-070508 7.3.2
R1-070509 Bit Mapping for 16QAM for HSUPA Ericsson 7.3.2 Noted
E-DPCCH Aided Channel Estimation for Withdrawn
R1-070510 Ericsson 7.3.2
16QAM for HSUPA
106
AGENDA REVISED BY
ITEM (From)
Timing advance based resource allocation Not treated
in half-duplex FDD
Draft answer LS on status of Rel-7 FDD Approved in R1-070578
MIMO
R1-070513 CQI reporting for FDD MIMO Qualcomm Europe 7.1 Noted
25.214 CR0430r4 (Rel-7, B) "Definition of Not treated
MIMO operation on HS-PDSCH, preferred
precoding and CQI reporting procedures,
modified CQI tables"
25.212 CR0242r4 (Rel-7, B) "Coding of Withdrawn
R1-070515 HS-DPCCH to support operation of FDD Qualcomm Europe 7.1
MIMO"
L1/L2 Control Channel Structure with Not treated
R1-070516 CDM Based Multiplexing in E-UTRA KDDI, NTT DoCoMo 6.9.2
Downlink
Category 0 Information for TDM Based Not treated
Multiplexing of
R1-070517 KDDI, NTT DoCoMo 6.9.2
L1/L2 Control Signaling in E-UTRA
Downlink
Scrambling Code for L1/L2 Control (R1-063350) Not treated
R1-070518 Channel with CDM Based Multiplexing in KDDI 6.9.2
E-UTRA Downlink
An Evaluation of the Rotational CDM for Not treated
R1-070519 KDDI, NTT DoCoMo 6.9.2
L1/L2 Control Channel
System-Level Evaluation of the Rotational Not treated
R1-070520 KDDI 6.9.2
CDM for L1/L2 Control Channel
CDMA based Multiplexing of ACK/NACK (R1-063579) Not treated
R1-070521 and CQI Control Information in E-UTRA KDDI, NTT DoCoMo 6.9.1
Uplink
On the HARQ Options for 64QAM for Noted
R1-070522 Ericsson 7.3.1
HSDPA
Comparison of closed-loop antenna Noted
R1-070523 selection with open-loop transmit diversity Mitsubishi Electric 6.8.3
(antenna switching within a TTI)
Comparison of closed-loop antenna Noted
R1-070524 selection with open-loop transmit diversity Mitsubishi Electric 6.8.3
(antenna switching between TTIs)
107
AGENDA REVISED BY
ITEM (From)
Editor; Ericsson, Revised in R1-070561
R1-070525 TS 36.211 v 0.2.2 6.1
NTT DoCoMo
Reference Signal Structure for Multi- Withdrawn
antenna E-MBMS Transmission
Non-Synchronized Random Access Not treated
R1-070527 ETRI 6.5.1
Procedure
Performance of Frequency Multiplexing for Noted
R1-070528 Samsung 6.2
Broadcast and Unicast
25.212 CR0242r4 (Rel-7, B) "Coding of Not treated
R1-070529 HS-DPCCH to support operation of FDD Qualcomm Europe 7.1
MIMO"
Uplink Power and IoT Control Method: Not treated
Description and Simulation Results
R1-070531 Preferences for UL Timing Control IPWireless 6.11 Noted
Cell-specific integer sequences for (R1-070117) Not treated
R1-070532 frequency positioning of DL RS on Huawei 6.6.1
subframe basis
R1-070533 Support of half duplex FDD Vodafone 6.2 Noted
Further Cubic Metric Results for 16QAM Noted
R1-070534 Ericsson 7.3.2
for HSUPA
R1-070535 HS-SCCH structure for MIMO and 64QAM Ericsson 7.1 Noted
Spectral efficiency comparison of possible (R1-070481) Noted
MBMS transmission schemes
R1-070537 HS-SCCH for MIMO and 64QAM Philips 7.1 (R1-070350) Noted
Proposed for block code for CQI/PCI Withdrawn
R1-070538 reporting for Rel-7 MIMO including Philips 7.1
25.212CR0242r5
R1-070539 On UL Reference Signal Structure Toshiba 6.6.2 (R1-070492)
Impact of F-DPCH timing restrictions due Noted
to SHO
Proposal for Constellation Rearrangement (R1-070313) Noted
R1-070541 Siemens 7.3.1
for 64-QAM
Draft Reply LS on Primary BCH Approved in R1-070606
R1-070542 Nokia 4
Transmission
UE Feedback Classification and CQI (R1-070170) Not treated
R1-070543 Broadcom 6.7.3
Characterization in E-UTRAN
108
AGENDA REVISED BY
ITEM (From)
Tail-Biting Encoding for 3GPP LTE Turbo (R1-070173) Not treated
R1-070544 Codes of Arbitrary Number of Information Broadcom 6.4
Bits and performance comparison
System analysis and further details of (R1-070419) Noted
proposed new coding for E-DPCCH
DRAFT LS /Proposed RAN WG1 (R1-070142) Approved in R1-070621
Response to LS R3-062005=R1-070008
R1-070546 on Siemens, Nokia 4
its signalling"
DRAFT Reply LS on SFN acronym Approved in R1-070607
R1-070547 Siemens 4
disambiguation R1-070009 (R3-062012)
Draft Reply LS on Impact of Release 7 bit Approved in R1-070594
rate increase and MIMO
R1-070549 Issues with LRI Interleaver Motorola 6.4 Noted
25.224 CR0154r1 (Rel-6, F) "Modification CATT, ZTE, TD- (R1-070070) Agreed
R1-070550 on the power control function of HS-SICH Tech, Spreadtrum 5
and HS-SCCH for LCR TDD" Communication
25.224 CR0155r1 (Rel-7, A) "Modification CATT, ZTE, TD- (R1-070071) Agreed
R1-070551 on the power control function of HS-SICH Tech, Spreadtrum 5
and HS-SCCH for LCR TDD" Communication
25.225 CR0084r1 (Rel-6, F) "Modification CATT, ZTE, TD- (R1-070072) Agreed
R1-070552 on the HS-SICH reception quality of HS- Tech, Spreadtrum 5
SICH for LCR TDD" Communication
25.225 CR0085r1 (Rel-7, A) "Modification CATT, ZTE, TD- (R1-070073) Agreed
R1-070553 on the HS-SICH reception quality of HS- Tech, Spreadtrum 5
SICH for LCR TDD" Communication
25.224 CR0157r1 (Rel-6, F) "Clarification (R1-070075) Revised in R1-070624
R1-070554 of Closed Loop Uplink HS-SICH Power ZTE 5
25.224 CR0158r1 (Rel-7, A) "Clarification (R1-070076) Revised in R1-070625
Spectrum shaping function for E-UTRA (R1-070126) Noted
R1-070556 Samsung 6.3
uplink
Proposed for block code for CQI/PCI Noted
R1-070557 reporting for Rel-7 MIMO including Philips 7.1
25.212CR0242r6
109
AGENDA REVISED BY
ITEM (From)
25.211CR0232r1 (Rel-7, C) "Redesigned (R1-070417) Agreed in principle
F-DPCH"
25.214CR0433r1 (Rel-7, C) "Redesigned (R1-070418) Agreed in principle
F-DPCH"
Draft LS on F-DCH enhancement for Approved in R1-070626
Release-7
Editor; Ericsson, Endorsed as v0.3.0 in R1-070627
R1-070561 TS 36.211 v 0.2.3 6.1
NTT DoCoMo
Editor, Qualcomm Endorsed version
R1-070562 TS 36.212 v0.3.0 6.1
Europe
R1-070563 TS 36.213 v0.2.0 Editor, Motorola 6.1 Endorsed version
Frequency Domain Spectral Shaping for (R1-070048) Noted
LTE
R1-070565 LS on CPC Long preamble RAN WG2, Nokia 4 = R2-070359 Noted
UE capability aspect for 1.28Mcps TDD (R1-070408) This text proposal was agreed to be included
R1-070566 TD-Tech 8
EUL in TR
FEC Coding of type-B CQI / PCI (R1-070493) Noted
R1-070567 InterDigital 7.1
Information
64QAM in HSDPA - Modulation Format (R1-070024) Noted
R1-070568 Motorola 7.3.1
Indication
R1-070569 E-MBMS performance with repeaters Motorola 6.2 Not treated
Philips, Ericsson, Agreed in principle
Way forward for HS-SCCH part 1 structure
R1-070570 Nokia, Qualcomm, 7.1
for MIMO and 64QAM
Motorola
Qualcomm Europe, Endorsed
R1-070571 CQI reporting for FDD MIMO 7.1
Ericsson
64QAM in HSDPA - Necessary Changes (R1-070025) Noted
R1-070572 Motorola 7.3.1
to the Specifications
Precoding Considerations in LTE MIMO (R1-070466) Not treated
R1-070573 Ericsson 6.7.2
Downlink
CQI delay impact on downlink multi- (R1-070467) Not treated
R1-070574 Ericsson 6.7.3
antenna systems for E-UTRA
One improvement on SCH Location for E- (R1-070195) Not treated
R1-070575 ZTE, CATT 6.5.2
UTRA TDD
Consideration on non-codebook based 6.7.2 (R1-070490) Noted
pre-coding for TDD
MIMO System Performance with variable (R1-070133) Noted
R1-070577 Samsung 6.7.3
110
AGENDA REVISED BY
ITEM (From)
Answer LS on status of Rel-7 FDD MIMO Approved version
R1-070578 RAN WG1 4
(To: RAN2, Cc; RAN4)
R1-070579 [Draft] Reply LS on CPC Long preamble Nokia 4 Approved in R1-070623
Philips, Siemens, (R1-070353) Not concluded to be agreed so that come
25.214 CR0421r9 (Rel-7, B) "Support of
R1-070580 Ericsson, Nokia, 7.2 back again in next meeting
CPC feature"
Qualcomm
Draft LS to RAN2 On Synchronization and Approved in R1-070634
Mobility with CPC
Ericsson, Qualcomm (R1-070498) Agreed
25.201 CR0026r1 (Rel-7, B) "Introduction
R1-070582 Europe, Motorola, 7.3.1
of 64QAM for HSDPA"
Philips
of 64QAM for HSDPA"
Philips
Ericsson, Qualcomm (R1-070500) Revised in R1-070635
of 64QAM for HSDPA"
Philips
of 64QAM for HSDPA"
Philips
of 64QAM for HSDPA"
Philips
Open issues for Higher Order Modulation Noted
for HSPA
of 16QAM for HSUPA"
Philips
of 16QAM for HSUPA"
Philips
of 16QAM for HSUPA"
Philips
of 16QAM for HSUPA"
Philips
111
AGENDA REVISED BY
ITEM (From)
of 16QAM for HSUPA"
Philips
Further Cubic Metric Results for 16QAM Noted
R1-070593 Ericsson 7.3.2
for HSUPA
Reply LS on Impact of Release 7 bit rate Approved version
R1-070594 increase and MIMO (To: RAN3, Cc; CT1, RAN WG1 4
CT4, SA1, SA2, RAN2)
Text proposal for 20ms TTI conclusion for Agreed
R1-070595 ZTE, CATT 8
LCR TDD EUL
Text Proposal on Power control procedure (R1-070302) Agreed
R1-070596 CATT 8
for 1.28Mcps EUL
R1-070597 TR 25.827 v1.0.1 CATT 8 Endorsed as v1.1.0 in R1-070636
Evaluation of SFBC and CDD for control LG Electronics (R1-070241) Not treated
R1-070598 6.7.5
channel with real channel estimation
DRAFT LS Response to RAN2 LS on Approved in R1-070622
R1-070599 Siemens 4
Ericsson, Motorola, R1-070602 Agreed in principle and revised in R1-070602
R1-070600 Data-non-associated control signaling 6.9.1
Qualcomm Europe as final version
[DRAFT] LS on data-associated uplink Approved in R1-070629
R1-070601 Ericsson 6.9.1
control signalling
Ericsson, Motorola, (R1-070600) Agreed
R1-070602 Data-non-associated control signaling 6.9.1
Qualcomm Europe
R1-070603 Need for Frequency Multiplexing of MBMS Nokia, Motorola 6.2 (R1-070373) Noted
R1-070604 UE minimum transmission bandwidth Motorola, Nokia 6.2 Noted
Motorola, Nokia, Noted
R1-070605 Way forward for spectrum shaping for LTE Freescale 6.3
Semiconuctor
Reply LS on Primary BCH Transmission Approved version
R1-070606 RAN WG1 4
(To: RAN WG2)
Reply LS on SFN acronym disambiguation Approved version
R1-070607 RAN WG1 4
R1-070009 (R3-062012) (To: RAN WG3)
Freescale (R1-070223) Noted
R1-070608 Scheme for MU-MIMO in DL EUTRA 6.7.4
Semiconductor
R1-070609 Way forward on 7.5 KHz Ericsson 6.2 Noted
R1-070610 [draft] LS on 7.5 kHz carrier spacing Ericsson 6.2 Approved in R1-070628
112
AGENDA REVISED BY
ITEM (From)
Power Setting for Interference Alcatel-Lucent 6.12 (R1-070409) Not treated
R1-070611 Coordination including Pilot and Control
Channels
R1-070612 Summary of SCH and RACH session Ad-Hoc Chairman 6.5 Agreed
LS on Transport Block Size Signalling for Approved in R1-070631
R1-070613 CATT 8
R1-070614 Draft LS on spectrum shaping Nokia 6.3 Approved in R1-070632
Summary of conclusions on interraction of Philips, Ericsson, Noted
R1-070615 7.2
CPC and CM Nokia
R1-070616 Summary of LTE MIMO session Ad-Hoc Chairman 6.7 Endorsed
LGE, Mitsubishi Noted
R1-070617 LRI Electric, Nortel, 6.4
Samsung
Flexible and Formulaic Collision-free Not treated
R1-070618 Memory Accessing for Parallel Turbo Broadcom 6.4
decoding with QPP Interleave
Motorola, Ericsson, Noted
Nokia, Broadcom,
R1-070619 On the Turbo Interleaver selection Freescale, 6.4
Qualcomm, CATT,
ITRI
R1-070620 Eb/N+ gain with E-DPCCH boosting Qaulcomm Europe 7.3.2 Noted
LS /Proposed RAN WG1 Response to LS Approved version
R3-062005=R1-070008 on
R1-070621 RAN WG1 4
its signalling"
LS Response to RAN2 LS on Approved version
R1-070622 RAN WG1 4
R1-070623 Reply LS on CPC Long preamble RAN WG1 4 Approved version
25.224 CR0157r2 (Rel-6, F) "Clarification (R1-070554) Agreed
25.224 CR0158r2 (Rel-7, A) "Clarification (R1-070555) Agreed
R1-070626 LS on F-DCH enhancement for Release-7 RAN WG1 4 Approved version
Editor; Ericsson, Endorsed version
R1-070627 TS 36.211 v 0.3.0 6.1
NTT DoCoMo
113
AGENDA REVISED BY
ITEM (From)
R1-070628 LS on 7.5 kHz carrier spacing RAN WG1 4 Approved version
LS on data-associated uplink control Approved version
R1-070629 RAN WG1 4
signalling
Ericsson, Nokia, Noted
Huawei, NTT
DoCoMo, Motorola,
R1-070630 Way forward on DL RS Qualcomm, 6.6.1
Samsung, TI,
Alcatel-Lucent, LGE,
Nortel Networks
LS on Transport Block Size Signalling for Approved version
R1-070631 RAN WG1 4
R1-070632 LS on spectrum shaping RAN WG1 4 Approved version
R1-070633 Approved Report of RAN1#47 MCC 3 Approved version
LS to RAN2 On Synchronization and Approved version
R1-070634 RAN WG1 4
Mobility with CPC
Ericsson, Qualcomm Agreed
of 64QAM for HSDPA"
Philips
R1-070636 TR 25.827 v1.1.0 CATT 8 Endorsed version
114
3GPP TSG RAN WG1 Meeting #48
Annex F: List of actions

1. Rel-5,6,7 Maintenace
- CR 0157r2 and 0158r2 for 25.224 (R1-070624, R1-070625): E-mail approval until 26th
January, (ZTE)
2. LTE
- E-mail discussion: UL RS, DL Tx Diversity, UL Timing control, UL/DL Power control,
Measuremeent, etc.
3. MIMO Rel-7
- Continue work on selecting CQI/PCI coding scheme based on 10 base vectors, focusing on
a (20.10) code and a (20,7) sub-set code. Agree on codes to be evaluated during the week
after the meeting and present simulation results until one week later.
4. CPC
- Continue work to include the principle outlined in R1-070352 in a separate set of CRs for
CPC. Concerns on operation with relevant compressed mode patterns from 25.133 should
be raised until 2 weeks after this meeting.
- Discuss until next meeting whether anything should be changed relative to the existing set
of CRs for the synchronization criteria.
- E-mail approval until 26th January: R1-070615 (Phiplis), R1-070580 (Philips), R1-070581
(Ericsson)
5. HOM for HSDPA/HSUPA
- CRs for Introduction of 64QAM for HSDPA: R1-070582, 583, 584, 585, 586, E-mail
approval until 26th January, (Ericsson).
- CRs for Introduction of 16QAM for HSUPA: R1-070588, 589, 590, 591, 592, E-mail
approval until 26th January, (Ericsson).
6. 1.28 Mcps TDD Enhanced Uplink
- E-mail approval until 26th January: R1-070595, 596. 597, (CATT)
- E-mail discussion until the next meeting based on R1-070406, R1-070302/407, (CATT)
115

R1-071245 (Approved ReportWG1 #47bis)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R1-071245 (Approved ReportWG1 #47bis)

Uploaded by

Copyright:

Available Formats

3GPP TSG RAN WG1 Meeting #48 R1-071245

St Louis, US, 12 –16 February, 2007

All timestamps in this document are in GMT+1H unless otherwise noted.

1. Opening of the meeting

1.1 Call for IPR

The members take note that they are hereby invited:

2 Approval of the agenda

3. Approval of the minutes from previous meeting

4. Liaison statement handling

R1-070008 LS on “Inter-Cell Interference Coordination and its signalling” (To: RAN1)

R1-070009 LS on SFN acronym disambiguation (To: RAN1, RAN2, RAN4)

R1-070547 DRAFT Reply LS on SFN acronym disambiguation R1-070009 (R3-062012)

R1-070010 LS on LTE-MBMS Discussions in RAN3 (To: RAN1, RAN2, SA2)

R1-070011 LS on Impact of Release 7 bit rate increase and MIMO on Specifications

R1-070051 Performance of MBMS Transmission Configurations (Motorola)

Discussion (Question / Comment):

R1-070565 LS on CPC Long preamble (To: RAN1)

R1-070184 Preamble transmission simplification (Nokia)

5. Maintenance of R99, Rel4, Rel5, Rel6, Rel-7

Discussion (Question / Comment):

R1-070177 Computation of E-DPDCH gain factors (Nokia)

R1-070560 Draft LS on F-DCH enhancement for Release-7 (Qualcomm Europe)

R1-070540 Impact of F-DPCH timing restrictions due to SHO (Ericsson)

6. Evolved UTRA and UTRAN

1. Updated Physical Layer Specifications

 Diversity aspect 2+2 vs 1+3 regarding CQI imperfection

6.1 Updated Physical Layer Specifications

R1-070422 TS 36.212 v0.2.2 (Editor; Qualcomm Europe)

R1-070194 TS 36.213 v0.1.1 (Editor; Motorola)

6.2 Remaining issues on numerology

MBMS long CP for shared carrier

R1-070610 [draft] LS on 7.5 kHz carrier spacing (Ericsson)

R1-070373 Need for Frequency Multiplexing of MBMS (Nokia, Motorola)

Discussion: Two alternatives

R1-070306 Uplink Extended Cyclic Prefix Use Cases (Siemens)

Discussion (Question / Comment):

Not treated due to lack of time

Agreed way forward

Not treated due to lack of time

R1-070068 Frequency Domain Spectral Shaping and Power Amplifier Optimization

R1-070126 Spectrum shaping function for E-UTRA uplink (Samsung)

R1-070614 LS on Frequency Domain Spectrum Shaping and /2 BPSK (Nokia)

6.4 Channel coding

LTE Turbo coding interleaver

Discussion (Question / Comment):

R1-070061 ARP Interleaver Design for LTE (Motorola)

R1-070209 A PIL-Based New Contention-Free Interleaver for Turbo Codes

Summarising the discussion by Chairman

Discussion and support for the different proposals:

R1-070617 LRI (Mitsubishi Electric, LGE, Samsung, Nortel)

R1-070619 On the Turbo Interleaver selection

LRI supported by Mitsubishi, LGE, Nortel, Samsung, Renesas

Not treated due to lack of time

Not treated due to lack of time

R1-070058 Eliminating tail bits in LTE channel coding (Motorola)

Mr. Chairman listed up the following technical points as other issues.

6.5 Basic Access Procedures

6.5.1 RACH Procedure Physical Layer Aspects

R1-070065 Summary of RACH e-mail reflector discussion (Motorola)

Decision: This document was noted.

Not treated due to lack of time

1 Scheduling Request Indicator

3 Scheduling Request + Data