3GPP TSG RAN WG1 Meeting #47 R1-063613

Riga, Latvia, 06 –10 November, 2006

Agenda item 3
Title: Approved Report of 3GPP TSG RAN WG1 #46bis
(Seoul, Korea, 09 – 13 October, 2006)
Document for: Information
Source: MCC Support

Notes:

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

Fact Summary
Meeting: 3GPP TSG RAN WG1 #46bis
Dates: 09th through 13th October, 2006
Venue: JW Marriott Hotel Seoul, Korea
Host: Samsung
Attendees: 166 delegates
Documents: 573 (including some withdrawn and post-meeting artefacts)

Yoshikazu Ishii
ETSI Mobile Competence Center
yoshikazu.ishii@etsi.org
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Table of contents

Executive summary..........................................................................................................................................1
1. Opening of the meeting..........................................................................................................................2
1.1 Call for IPR..........................................................................................................................................................2
2 Approval of the agenda...........................................................................................................................2
3. Approval of the minutes from previous meeting....................................................................................3
4. Liaison statement handling.....................................................................................................................4
5. Maintenance of R99, Rel4, Rel5, Rel6, Rel-7.........................................................................................6
5.1 R99, Rel4, Rel5 or Rel6 CRs + shadow CRs......................................................................................................6
5.2 Rel7 CRs..............................................................................................................................................................6
5.3 Other....................................................................................................................................................................6
6. Evolved UTRA and UTRAN..................................................................................................................7
6.1 Physical Layer Specifications..............................................................................................................................9
6.2 Physical Layer Model........................................................................................................................................11
6.3 UL/DL Transmission Scheme...........................................................................................................................13
6.3.1 UL/DL Modulation Scheme.........................................................................................................................13
6.3.2 Need for distributed transmission in UL......................................................................................................14
6.3.3 Numerology for alternative TDD Frame Structure......................................................................................16
6.3.4 Remaining issues on FDD/TDD aligned numerology.................................................................................17
6.4 Basic Access Procedures...................................................................................................................................20
6.4.1 BCH.............................................................................................................................................................20
6.4.2 PCH..............................................................................................................................................................22
6.4.3 RACH Procedure Physical Layer Aspects...................................................................................................22
6.4.4 SCH and Cell Search....................................................................................................................................28
6.5 Reference signal structure..................................................................................................................................31
6.5.1 Downlink reference signals..........................................................................................................................31
6.5.2 Uplink reference signals...............................................................................................................................35
6.6 Downlink MIMO, Transmit Diversity and Beamforming.................................................................................36
6.6.1 Maximum number of code words for 4x4 MIMO.......................................................................................37
6.6.2 Layer permutation vs. no layer permutation................................................................................................38
6.6.3 MU-MIMO..................................................................................................................................................38
6.6.4 Transmit diversity........................................................................................................................................39
6.6.5 Precoding details..........................................................................................................................................40
6.6.6 UE feedback.................................................................................................................................................41
6.7 UL Timing Control............................................................................................................................................42
6.8 UL/DL Power Control.......................................................................................................................................42
6.9 DL PAPR Reduction..........................................................................................................................................43
6.10 Physical Layer specification aspects of Scheduling..........................................................................................43
6.11 Physical Layer specification aspects of Link Adaptation..................................................................................43
6.12 Specification of Control Signalling...................................................................................................................44
6.12.1 Downlink Control Signalling.......................................................................................................................44
6.12.2 Uplink Control Signalling............................................................................................................................45
6.13 Physical Layer Measurements...........................................................................................................................47
6.13.1 UE Measurements........................................................................................................................................47
6.13.2 eNode B Measurements...............................................................................................................................47
6.14 Physical Layer UE Capability Aspects..............................................................................................................47
7. HSPA Evolution...................................................................................................................................48
7.1 MIMO in UTRA (Rel-7 Work Item).................................................................................................................48
7.1.1 Downlink Signalling Structure.....................................................................................................................49
7.1.2 Uplink Signalling Structure.........................................................................................................................49
7.1.3 4x2 MIMO Configuration............................................................................................................................50
7.2 Continuous Connectivity for Packet Data Users...............................................................................................50
7.3 Scope of future FDD HSPA Evolution..............................................................................................................52

2
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
8. 1.28Mcps TDD Enhanced Uplink.........................................................................................................54
9. Closing of the meeting..........................................................................................................................56
Annex A: List of participants at RAN1 #46bis...........................................................................................57
Annex B: TSG RAN WG1 meetings in 2006 and 2007..............................................................................62
Annex C: List of CRs agreed at RAN1#46bis............................................................................................64
Annex D: List of Outgoing LSs..................................................................................................................65
Annex E: List of Tdocs at RAN1 #46bis....................................................................................................66
Annex F: List of actions.............................................................................................................................98

3
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Executive summary
WG RAN1 #46bis meeting took place in JW Marriott Hotel - Seoul, Korea. The meeting started at 9:00 on Monday 9 th
October and finished at 17:00 on Friday 13th 2006.

LTE topics were discussed Monday through Friday and the discussion could reach many agreements as followed:

1. The set of Evolved UTRA and UTRAN physical layer specification, 36.201, 36.211, 36.212, 36.213 and 36.214
was endorsed as v0.1.0
2. E-UTRA physical layer model was agreed and as for L1 MUX, for the UL, no L1 MUX for single layer
transmission. On the other hand, for the DL, two schemes proposed and proposal 1 was agreed, and leave
proposal 2 FFS after the DL MIMO signalling has been decided.
3. Regarding UL/DL transmission scheme, modulation scheme for UL/DL was agreed with some FFS points and it
was agreed that D-FDMA is not supported for UL data transmission. As for 1RB in a 1ms TTI, it was agreed that
it is not needed for the UL. For the DL if agreement can be reached over email reflector until the next meeting it
can be agreed at the next meeting. In addition, the discussion could reach to agreement on the numerology of
alternative E-UTRA TDD frame structure, UL sub-frame format and CP durations, the principle of specifying a
bandwidth agnostic L1.
4. With regards to basic access procedure, working assumption for BCH was agreed and also concerning SCH,
working assumption was agreed for evaluations of the proposal and the alternative proposals to be discussed. It
was agreed as working assumption that SFN combining of PCH from same eNodeB or different eNodeB not
supported. Furthermore, RACH preamble structure for 1.0msec case was agreed.
5. Working assumption for downlink reference signal was agreed. In case of multi antennas, the structure for 2-TX
antenna MIMO was agreed, and for 4-Tx antenna case, working assumption was agreed to be confirmed by
simulations.
6. The discussion on MIMO for E-UTRA also could reach to some agreements. 2 CWs was agreed as maximum
number of code words for 4x4 MIMO. Regarding Layer permutation or not, working assumption for taking a
decision at next meeting was agreed. Companies' view for Tx diversity were listed and it was agreed as way
forward to take email discussion on the control channel Tx Diversity until the next meeting.
7. Finally, regarding transmission scheme for non-data associated control signalling, it was agreed that working
assumption in absence of data is to use a reserved frequency, on the other hand, working assumption in presence
of data is to use the multiplexing of control and data prior to DFT.

The topics of HSPA evolution were discussed in whole of Wednesday and Thursday evening parallel to LTE sessions. As
for MIMO LTE, the discussion could reach to some agreements on CQI signalling, HSDPA MIMO UE categories, HS-
SCCH for MIMO, CQI reporting. The set of CRs will be prepared in next RAN1 meeting for agreement. As for
Continuous Connectivity for Packet Data users, the set of CRs was agreed on the e-mail reflector after the meeting.

The topic of 1.28Mcps TDD enhanced uplink was discussed on Friday early morning and some text proposals to
TR25.827 were agreed.

The number of contributions for this meeting was 553 (without including withdrawn documents), and those documents
were categorized as followed.

Input Discussed
Agenda Item
Document Document
Liaison statement handling 23 23
Maintenance of R99, Rel4, Rel5, Rel6 6 1
Evolved UTRA and UTRAN (Physical Layer) 443 134
HSPA Evolution 57 49
1.28 Mcps TDD Enhanced Uplink 13 13

1
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

1. Opening of the meeting

09/10/2006 09:15

Mr. RAN1 Chairman, Mr. Dirk Gerstenberger and welcomed the participants to RAN WG1 46bis meeting and opened the
meeting at 09.15.
Dr. Juho Lee welcomed the delegates on behalf of the host company, Samsung.

1.1 Call for IPR

09/10/2006 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-062455 Draft Agenda for RAN1#46bis (RAN1 Chairman)
R1-062540 Revised Draft Agenda for RAN1#46bis (RAN1 Chairman)
09/10/2006 09:20 Presented by Mr. Dirk Gerstenberger.
Discussion (Question / Comment): Mr. RAN1 Chairman explained the schedule for the week.
MBMS evolution topic will be discussed with the other WGs in RIGA.
Decision: This document was approved.

2
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

3. Approval of the minutes from previous meeting

R1-062456 Draft Report of RAN1#46 (MCC)
09/10/2006 09:25 Presented by Mr. Yoshikazu Ishii
Discussion (Question / Comment):
Decision: This document was approved in R1-063013.
R1-063013 Approved Report of RAN1#46 (MCC)

3
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

4. Liaison statement handling

R1-062457 LS on co-ordination of work on GERAN-LTE Interworking (To: RAN, SA,
CC: SA2, RAN1, RAN2) (TSG GERAN, T-Mobile)
09/10/2006 09:25 Presented by Mr. Georg Wannemacher
Discussion (Question / Comment):
Decision: This document was noted.
R1-062458 Reply LS on co-ordination of work on GERAN-LTE Interworking (To:
GERAN, SA, Cc: SA2, RAN1, RAN2, GERAN2) (TSG RAN, T-Mobile)
09/10/2006 09:30 Presented by Mr. Georg Wannemacher
Discussion (Question / Comment):
Decision: This document was noted.
R1-062467 LS from RAN #33 to SA#33 “Consideration of timelines between RAN and SA
with regard to LTE and SAE” (To:SA, Cc: RAN1, RAN2, RAN3, RAN4, RAN5)
(TSG RAN, NTT DoCoMo)
09/10/2006 09:35 Presented by Dr. Sadayuki Abeta
Discussion (Question / Comment):
Decision: This document was noted.
R1-062882 LS on 3GPP SAE&LTE Workplan (To: SA1, SA2, SA3, SA4, SA5, RAN1,
RAN2, RAN3, CT1, CT3, CT4, CT6, GERAN1, GERAN2, GERAN3, Cc: RAN,
CT, GERAN) (TSG SA, Ericsson)
This LS captured the updated version of attachment, SAE/LTE work plan in R1-062948.
R1-062948 LS on 3GPP SAE&LTE Workplan (To: SA1, SA2, SA3, SA4, SA5, RAN1,
RAN2, RAN3, CT1, CT3, CT4, CT6, GERAN1, GERAN2, GERAN3, Cc: RAN,
CT, GERAN) (TSG SA, Ericsson)
09/10/2006 09:40 Presented by Mr. Dirk Gerstenberger.
Discussion (Question / Comment):
Mr. RAN1 Chairman showed the RAN1 part in the attachment and pointed out the handover measurement was
added in RAN1 task.
Decision: This document was noted.
R1-062462 Physical Channel Definitions supporting PCH, MCH and BCH (To: RAN1)
(WG RAN2, Motorola)
12/10/2006 14:40 Presented by Mr. Robert Love
Discussion (Question / Comment):
Decision: This document was noted.
R1-062464 Reply-LS on "Bearer QoS Information Elements Signaled on S1" (To: SA2,
SA4, RAN2, Cc: RAN1) (WG RAN3, Siemens)
09/10/2006 09:45 Presented by Dr. Joern Krause
Discussion (Question / Comment):
Decision: This document was noted.
R1-062465 Reply-LS on Single Frequency Network synchronization for E-MBMS (To:
RAN1, RAN2, Cc: RAN4) (WG RAN3, Siemens)
09/10/2006 09:50 Presented by Dr. Przemek Czerepinski
Discussion (Question / Comment):
Decision: This document was noted.
R1-062920 E-MBMS LS Discussion (Siemens)
09/10/2006 10:00 Presented by Dr. Przemek Czerepinski
Discussion (Question / Comment):
Mr. Chairman commented that we are not expecting to finalize this topic in this meeting so that we continue the
discussion until the next meeting.
Decision: This document was noted.
R1-062466 LS on E-UTRA mobility support (To: RAN1, Cc: RAN2, RAN3)
(WG RAN4, Nokia)
09/10/2006 10:10 Presented by Mr. Asbjorn Grovlen

4
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Discussion (Question / Comment):

Decision: This document was noted.
R1-062459 LS on random access control for 1.28Mcps TDD Enhanced Uplink (To:RAN1)
(WG RAN2, TD-Tech)
09/10/2006 10:15 Presented by Mr. Nicholas Anderson
Discussion (Question / Comment):
Decision: This document was noted.
R1-062460 Reply LS to RAN1 LS on Uplink Control Signalling for 1.28Mcps TDD
Enhanced Uplink (To:RAN1) (WG RAN2, CATT)
09/10/2006 10:16 Presented by Mr. Ke Wang
Discussion (Question / Comment):
Decision: This document was noted.
R1-062461 Reply LS on feedback regarding the concepts for "Continuous connectivity for
packet data users" (To: RAN1, Cc: RAN3, RAN4) (WG RAN2, Nokia)
09/10/2006 10:20 Presented by Mr. Karri Ranta-aho
Discussion (Question / Comment):
Decision: This document was noted.
R1-062463 LS on VoIP RAB combination (To:RAN1) (WG RAN2, Orange)
09/10/2006 10:25 Presented by Dr. Thomas Salzer
Discussion (Question / Comment):
Decision: This document was noted. Collect comments and draft LS in R1-062955
R1-062955 Draft Reply LS on VoIP RAB combination (Orange)
13/10/2006 12:40 Presented by Dr. Thomas Salzer
Discussion (Question / Comment):
Decision: This draft LS was approved in R1-063010.

R1-062984 LS on minimum receiver bandwidth capability (To: RAN1, Cc: RAN4) (WG
RAN2, LG Electronics)
12/10/2006 12:25 Presented by Mr. Dragan Vujcic
Discussion (Question / Comment):
Stefan Parkvall (Ericsson) informed that R1-062983 is output from offline discussion during lunch break and it
would be reply to this RAN2 LS. (So, RA1-062983 was treated).
Decision: This document was noted.

Outgoing LS
R1-062976 Reply to RAN2 LS on Random-Access Related Issues
(To: RAN2) (WG RAN1)
R1-063006 Reply LS on minimum receiver bandwidth capability
(To: RAN2, Cc: RAN4) (WG RAN1)
R1-063009 LS on status of Rel-7 FDM MIMO
(To: RAN2, RAN3, RAN4, Cc: RAN) (WG RAN1)

R1-063010 Reply LS on VoIP RAB combination (To: RAN2) (WG RAN1)

R1-063011 LS on status of RAN1 CRs for "Continuous connectivity for packet data users"
(To: RAN2, RAN3, RAN4) (WG RAN1)
R1-063012 LS on E-UTRA physical-layer model (To: RAN2) (WG RAN1)
R1-063015 LS on non-Scheduled Traffic and Scheduled Traffic Transmissions
(To: RAN2) (WG RAN1)

5
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

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

5.1 R99, Rel4, Rel5 or Rel6 CRs + shadow CRs

The following five CRs were postponed to the next meeting, RAN1#47, to be discussed due to the late
submission after the submission deadline
R1-062590 25.214 CR0424 (R99, F) "Correction of DPDCH Gain factor in compressed
mode" (Huawei)
R1-062591 25.214 CR0425 (Rel-4, A) "Correction of DPDCH Gain factor in compressed
mode" (Huawei)
R1-062592 25.214 CR0426 (Rel-5, A) "Correction of DPDCH Gain factor in compressed
mode" (Huawei)
R1-062593 25.214 CR0427 (Rel-6, F) "Correction of DPDCH and E-DPDCH Gain factor
in compressed mode" (Huawei)
R1-062594 25.214 CR0428 (Rel-7, A) "Correction of DPDCH and E-DPDCH Gain factor
in compressed mode" (Huawei)

5.2 Rel7 CRs

No Contribution

5.3 Other
R1-062884 Analysis of HSDPA in CELL_FACH state (Nokia)
09/10/2006 10:25 Presented by Mr. Karri Ranta aho
Discussion (Question / Comment):
Evelyne Le Strat (Nortel) commented this topic is relate to RAN2 so that some coordination is need
Mr. Chairman suggested giving the comment and question directly to Karri and continuing the discussion on e-mail
in which RAN2 can monitor the RAN1 discussion.
Decision: This document was noted and it was decided to continue discussion over e-mail until next meeting. Karri
will indicate discussion.

6
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

6. Evolved UTRA and UTRAN

The overview of conclusions on this topic is as followed.

8. Physical Layer Specifications

a. Draft set of Evolved UTRA and UTRAN physical layer specification, TS36.201, 36.211,
36.212, 36.213 and 36.214 was endorsed as v0.1.0
9. Physical Layer model
a. E-UTRA physical-layer model was agreed in R1-062973
b. L1 MUX
i. For the UL, no L1 MUX for single layer transmission
ii. For the DL two schemes proposed and agreement on proposal 1, and leave proposal 2
FFS after the DL MIMO signalling has been decided.
Proposal 1
- Non L1 mux4
- For non-MIMO: 1 HARQ process
- For MIMO (including fallback to single CW transmission): # HARQ
processes to be decided separately (depending on MIMO scheme selection)
Proposal 2
- L1 mux4
- For MIMO (including fallback to single CW transmission): # HARQ
processes to be decided separately (depending on MIMO scheme selection)
- For non-MIMO: Up to 2TB based on TB size, but not based on QoS
o Reuse the same signalling structure for the non-MIMO case
o Allowing for one to two HARQ processes even for non-MIMO
dynamically, e.g. based on a threshold of the TB size. (TB
segmentation in L2)
10. UL/DL Transmission Scheme
a. Modulation scheme
i. For the DL: QPSK, 16QAM and 64QAM were agreed.
ii. For the UL: QPSK and 16QAM were agreed. Need for Pi/2 BPSK or QPSK &
spectrum shaping is FFS, and need for 8PSK is FSS
iii. Signal constellations for QAM modulation was agreed in R1-062813
iv. DL scrambling on bit level after the channel coding, scrambling of reference signals
(or having different reference signals) agreed, provided the scrambling is of low
complexity. One-to-one mapping between reference signal sequence and scrambling of
the BCH.
b. UL data transmission: It was agreed that D-FDMA not supported. As for L-FDMA with
support for inter-TTI FH and intra-TTI FH, if activated, hop at the sub-frame border between
two sub-frames within a TTI
c. TDD Numerology
i. Multiple switching points (up to 10) within 10ms radio frame with asymmetric
(including symmetric) UL/DL allocation. Similarities between FDD and TDD should
be aimed for (general requirement).
ii. The numerology of alternative E-UTRA TDD was agree in R1-062959
d. UL sub-frame format and CP durations were agreed in R1-062544 and R1-062820.
e. As for 1RB in a 1ms TTI it was agreed that it is not needed for the UL. For the DL if
agreement can be reached over email reflector until the next meeting it can be agreed at the
next meeting.
f. The Principle of specifying a bandwidth agnostic L1 was agreed. The details on lower end
spectrum allocation is to be decided further (e.g. resolution of 1RB at 1.25MHz allocation.)
11. Basic Access Procedure
a. BCH
i. R1-062983 is agreed as working assumption

7
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

ii. SCH, P-BCH transmitted only in the centre frequency , BW is 72sub carriers
iii. PCH and S-BCH (If a S-BCH will be defined) transmitted only in the centre
frequency, maximum BW is 600 sub carriers
b. PCH: It was agreed as working assumption that SFN combining of PCH from same eNodeB or
different eNodeB not supported.
c. RACH
i. 1.0msec preamble structure was agreed as followed;
RA slot = 1 ms

TCP TGP

CP Preamble

Parameters for 1msec TTI only:

CP: 0.1msec
Preamble: 0.8msec
GT: 0.1msec
ii. 0.5msec: Continue to discuss until next meeting (with effect of frequency error)
d. SCH: Approach 1 is taken as the working assumption, but will not yet be included in the draft
spec before evaluations of the proposal and the alternative proposals have been discussed.
Approach 1
 TDM of P-SCH and S-SCH, transmitted 2x per 10ms for FDD and LCR aligned
TDD frame structure (1-2x per 10ms for TDD)
 5ms timing: P-SCH
 radio frame timing, group id, and possibly #antennas for BCH): S-SCH
 cell id: DL RS
 read the BCH
12. Downlink Reference signal
a. R1-063008 was agreed as working assumption.
b. In case of multi antennas, the structure for 2-TX antenna MIMO is agreed as shown
Frequency domain

T1 D D T2 D D T1 D D T2 D D T1 D D T2 D D T1
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D
0.5 ms
D D D D D D D D D D D D D D D D D D D
T2 D D T1 D D T2 D D T1 D D T2 D D T1 D D T2
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D

T1 : Pilots for Tx Ant 1 T2 : Pilots for Tx Ant 2

R D : Data

For 4-Tx antenna case, R1-062993 is agreed as working assumption for 4Tx and to be confirmed
by simulations, e.g. against reference cases in R1-062998 or R1-063007. In addition, R1-062980
was agreed as working assumption for 4Tx alternative TDD frame structure.

8
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

13. MIMO for E-UTRA

a. Maximum number of code words for 4x4 MIMO: 2 CWs was agreed as working assumption
b. Layer permutation: Agreed way forward
i. On the layer permutation proposal, continue discussion including simulation
assumptions etc via email reflector until the next meeting.
1. Take into account the implication on the UL feedback overhead and also other
aspects of LTE MIMO solution.
ii. Take decision in the next meeting on whether to use or not.
iii. The layer permutation to be discussed as a part of UE feedback agenda item in the next
meeting.
c. Tx Diversity: Companies view was listed and it was Agreed as way forward to take email
discussion on the control channel TxD until the next meeting.
14. UL control channel: Non-data associated control signalling
a. Transmission in absence of data: Working assumption is to use a reserved frequency.
b. Transmission in presence of data: Working assumption is to use the multiplexing of control and
data prior to DFT

Not treated
R1-062511 LTE DL VoIP capacity (Samsung)

Withdrawn
R1-062918 System simulation scenario for large cells to aid LTE design (Vodafone)

6.1 Physical Layer Specifications

R1-062896 Draft specification skeleton, 36.201 (Ericsson)
09/10/2006 11:30 Presented by Mr. Dirk Gerstenberger
Discussion (Question / Comment):
Decision: This document was noted. It was confirmed that the specification number for LTE is 36 series. This
document was endorsed as v 0.1.0 in R1-063005
R1-063005 TS 36.201 v0.1.0 (Ericsson)

R1-062897 Draft specification skeleton, 36.211 v0.0.0

(Ericsson)
This document was revised before the presentation
R1-062947 Draft specification skeleton, 36.211 v0.0.0 (Ericsson)
09/10/2006 11:40 Presented by Dr. Stefan Parkvall

9
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Discussion (Question / Comment):

Tim Moulsley (Philips) commented that in the skeleton of 36.201 the antenna mapping is described as the feature of
36.211 but there is no description really for multi antenna in this document so that the corresponding section should
be added
Decision: This document was noted and revised as 0.0.1 in R1-062957 with addition of the section for multi
antenna.
R1-062957 Skeleton of 36.211 v0.0.1 (Ericsson)
13/10/2006 09:45 Presented by Dr. Stefan Parkvall
Discussion (Question / Comment):
Decision: This document was endorsed as v 0.1.0 in R1-063001
R1-063001 TS 36.211 v0.1.0 (Ericsson)

R1-062684 Skeleton of TS36.212 v0.0.0 (Qualcomm Europe)

09/10/2006 12:00 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
It was commented that coding control channel should be for both UL and DL although in the current structure is
just for DL
Amitava Ghosh (Motorola) asked if we shall specify the MIMO and beamforming case in this specification. Mr.
Chairman clarified that as same as the last specification, it's the just structure and skeleton level so that we can
modify in the future with waiting for the decision for selecting what kind of MIMO scheme.
Thomas Salzer (Orange) asked how the channel coding is for broadcast. Mr. Chairman clarified that for Layer 1 not
so much specification area for MBMS and we shall capture just synchronization feature in Layer 1 specification for
MBMS.
In addition, Mr. Chairman clarified about the procedure for updating the specification that until March in next year
we are focus on the technical discussion and editors should capture the decision on the specification so that we don't
focus on the detail of specification text, meaning that we don't need many text proposals and after March we focus
on the detains on the specification.
Decision: This document was noted and revised in R1-062956 as v0.0.1 with modification of coding of control
signalling for UL and DL.
R1-062956 Skeleton of TS36.212 v0.0.1 (Qualcomm Europe)
13/10/2006 09:45 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Decision: This document was endorsed as v 0.1.0 in R1-063002
R1-063002 TS 36.212 v0.1.0 (Ericsson)

R1-062596 Skeleton of 36.213 Physical Layer Procedure for E-UTRA, v0.0.0 (Motorola)
09/10/2006 09:xx Presented by Dr. Amitava Ghosh.
Sarah (Nortel) raise a wonder that the cell search procedure is not described in the section but should be in Annex
as TS25.214. Mr. Chairman we should be careful for description on the specification we can consider and decide
later.
Thanh Bui asked if (NEC) ask why the inter-cell synchronization is captured in it. Mr. RAN1 Chairman commented
that it may be in RNA3 specification, in basically it is out of RAN1 but we need some text in L1 specification such
what method we select.
Sharat Chander (Cingular) asked how status of synchronization topic and way forward is. Mr. Chairman clarified
that we will discuss a few methods and will send a LS according to our discussion to RAN3 and then may have a
joint session with RAN3.
Discussion (Question / Comment):
Decision: This document was noted This document was endorsed as v 0.1.0 in R1-063004
R1-063004 TS 36.213 v0.1.0 (Ericsson)

R1-062943 Draft specification skeleton, 36.214 v0.0.0 (Nokia)

09/10/2006 12:30 Presented by Mr. Asbjørn Grøvlen
Discussion (Question / Comment):
Christina G. Gerlach (Alcatel) asked about the measurement for each WG. Mr. Chairman clarified that RAN1
define the measurement and RAN4 define the requirement and RAN3 needs to specify the signalling between NB
for measurement. In addition, he informed about the discussion at the last RAN plenary that each WG specify the
corresponding area for measurement individually and harmonise among WGs after then.
The relation to the higher layer on the reporting, and CQI measurement topics were discussed.

10
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Mr. Chairman commented that CQI is the one of the measurement but anyway this proposed structure is fine so that
we can agree this draft.
Decision: This document was noted and revised R1-062967
R1-062967 Draft specification skeleton, 36.214 v0.0.1 (Nokia)
xx/10/2006 12:30 Presented by Mr. Asbjørn Grøvlen
Discussion (Question / Comment):
Decision: This document was endorsed as v 0.1.0 in R1-063003
R1-063003 TS 36.214 v0.1.0 (Nokia)

It was clarified about the procedure of drafting specification by RAN1 Chairman that until next
March, the inputs to draft specs should be provided by editors, based on the decisions taken in
the group. Endorse the specs at each WGs meeting (0.x.0)
Withdrawn
R1-062875 Text capturing RAN1 decision in 36.211 (Ericsson)

6.2 Physical Layer Model

R1-062577 L1 Multiplexing aspects of broadcast/unicast superposition (Samsung)
10/10/2006 09:20 Presented by Dr. Farooq Khan
Discussion (Question / Comment):
It was clarified by Samsung that there are two transport channels, DSCH and MTCH (MCH).
Mr Chairman clarified that if we agree this superposition, we need to agree the principle before the specification.
Decision: This document was noted.
R1-062685 Physical channel structure and multiplexing (Qualcomm Europe)
10/10/2006 09:35 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Erik Dahlman (Ericsson) commented that it's a good definition for physical channels, on the other hand inter
relation between L1 and L2 should be discussed.
Mr. Chairman commented that we need some discussion about some channel before agreement, however, now the
discussion is a little bit early in WI phase. Anyway the structure is OK.
Decision: This document was noted.
R1-062711 Views on Rate Matching in E-UTRA (NTT DoCoMo)
10/10/2006 09:45 Presented by Dr. Kenichi Higuchi
Discussion (Question / Comment):
It was clarified that channel bit size is the transport block size.
It was clarified by NTT DoCoMo that the necessity of this control is especially for DL and the necessity for UL is
less than for DL.
Decision: This document was noted.
R1-062814 Mapping of the Transport Channels to the Physical Channels (Nokia)
10/10/2006 09:50 Presented by Mr. Asbjørn Grøvlen
Discussion (Question / Comment):
Decision: This document was noted.
R1-062846 E-UTRA physical-layer model (Ericsson)
10/10/2006 09:55 Presented by Dr. Erik Dahlman
Discussion (Question / Comment):
This paper is submitted also in RAN2.
It was clarified that power allocation and FH for UL is a part of resource assignment on this figure.
Suzuki Hidetoshi (Panasonic) asked how the view for the single-cell operation of multicast is, DSCH or MTCH and
actually it's related to RAN2. It was clarified that MCH is intend to multi-cell including for single -cell.
Noriyuki Fukui (Mitsubishi) asked if PCH and multi-cast channel is control by the dynamic adaptive modulation It
was clarified by Ericsson that DSCH is dynamic, BCH is selected modulation scheme, dynamic is allowed to PCH
but current assumption is not dynamic, MCH is semi-static not dynamic so that it's slower adaptive modulation that
DSCH.
It was pointed out by Lucent that Figure 1 does not consider the different HARQ process among different antenna.
Ericsson commented that now we are a little bit wondering on multi antenna processing so we need more work.
Also they clarified that one hard processor is intended for multiple processing for one antenna

11
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Some companies asked and commented about more details on the figures and long discussion continued. As the
procedure for the specification on this area, Mr. Chairman commented that we need a high level figure for the next
step not need details and we surely will come back to this figure after the discussion more details in the future.
Decision: This document was noted.
Physical Layer model to be revised offline in R1-062961 and prepare the draft LS to RAN2.
R1-062961 E-UTRA physical-layer model (Ericsson)
11/10/2006 13:00 Presented by Dr. Erik Dahlman
Discussion (Question / Comment):
Decision: This document was noted and final version (endorsed version) is R1-062973
R1-062973 E-UTRA physical-layer model (Ericsson)
11/10/2006 13:20 Presented by Dr. Erik Dahlman
Discussion (Question / Comment):
Decision: This document was agreed and the agreed LS was sent to RAN2 in R1-063012.

R1-062597 Number of HARQ Channels (Motorola)

10/10/2006 09:30 Presented by Mr. Brian Classon
Discussion (Question / Comment):
It was clarified by Motorola that there are two processes, MIMO and non-MIMO
Decision: This document was noted.
R1-062847 L1 multiplexing (Ericsson, Samsung, Nokia)
10/10/2006 11:30 Presented by Dr. Stefan Parkvall
Discussion (Question / Comment):
It was clarified by Ericsson that the MAX 4 is not allowed for DSCH for one user. Sadayuki Abeta (NTT DoCoMo)
asked for confirmation if BCH and DL-SCH can be multiplexed in Layer 1 and UE can receive them
simultaneously. This question was confirmed that it can. It was pointed out by Motorola that this discussion is
tightly related to the number of HARQ processes so that we shall consider the number of process at first. It was
reconfirmed again about the general conclusion in January ad hoc meeting that no multiple modulation schemes can
be allowed in single code word and different RB
Decision: This document was noted.
R1-062921 Downlink Multiplexing (Lucent Technologies)
10/10/2006 11:45 Presented by Mr. Frank Favichia
Discussion (Question / Comment):
It was commented that it should be discussed in RAN2 at first and we are concentrated in MAX4 or not.
Decision: This document was noted.

After the presentation and discussion on the documents related to L1 MUX, it was discussed whether one or
multiple HARQ processes (channels) should be supported.
Brian Classon (Motorola) commented that we have not seen the simulation results for non-MIMO case and we are
submitting such a results in the next time so that we should take a decision based on the simulation results.
Stefan Parkvall (Ericsson) pointed out that if we take multiple HARQ processes for non-MIMO case, control
signalling overhead increases and the cava rage issues of ACK/NACK will be raised. Brian clarified that the HARQ
processes is not always two and it has the freedom for one or two. The freedom is controlled by signalling
procedure as same as MIMO.
Tim Moulsley (Philips) supported Motorola view. On the other hand, Przemek Czerepinski (Siemens) supported
Ericsson View with wonder on the simulation results and concern on the signalling perspective.
Christian G. Gerlach (Alcatel) supported MAX 4 (Motorola view) with commented that if we support to MAX4,
the different modulation scheme can be supported to the different RB.

After some discussion, Mr. Chairman summarized the status as followed. Even after long discussion, it could not
agree to select one option so that the following way forward was agreed.
Summary (Chairman's note)
Uplink: no L1 max for single layer transmission
Downlink
Proposal 1 (Samsung, Nokia, Ericsson, Siemens, Lucent, Qualcomm)
- Non L1 mux4
- For non-MIMO: 1 HARQ process
- For MIMO (including fallback to single CW transmission): # HARQ processes to be decided
separately (depending on MIMO scheme selection)

12
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Proposal 2 (Motorola, Philips, Alcatel)

- L1 mux4
- For MIMO (including fallback to single CW transmission): # HARQ processes to be decided
separately (depending on MIMO scheme selection)
- For non-MIMO: Up to 2TB based on TB size, but not based on QoS
o Reuse the same signalling structure for the non-MIMO case
o Allowing for one to two HARQ processes even for non-MIMO dynamically e.g. based
on a threshold of the TB size. (TB segmentation in L2)

Agreed way forward:

- For the DL, agreement on proposal 1, and leave proposal 2 FFS after the DL MIMO signalling
has been decided.
- For the UL, no L1 MUX for single layer transmission.

The discussion on summarizing

Regarding the signalling overhead for multi HARFQ processes, it was commented that pretty much signalling is
need for UL and the additional bit for the indication of transmission format is need for DL. In addition, it was
pointed out that more complexity cane be expected when TB size, i.e. each processing is different on each HARQ
process.
Qualcomm expressed their support on option 1 for non MIMI case from control signalling perspective.
Juho Lee (Samsung) pointed out on the simulation results of Motorola that 10% gain on link level simulation is
under high SNR level so that we cannot expected much gain for system level simulation.
The long discussion continued and some comments pointed out that in order to reach to conclusion, we are lacking
of necessary analysis such as signalling aspects, enough simulation results for benefits provided by multi HARQ
processes, coverage issue for control signalling. Also from the signalling aspects, it was pointed out that RAN2 also
need additional signalling.
Finally, Tim Moulsley (Philips) proposed as way forward that now we agree option 1 and leave option 2 FFS, and
then signalling issue for option 2 would be considered in MIMO session because the signalling for MIMO case is
reused to option 2. One point was pointed out to this proposal by Motorola that we should consider the number of
HARQ process for MIMO case in MIMO session and then the proposal was agreed.

6.3 UL/DL Transmission Scheme

6.3.1 UL/DL Modulation Scheme
R1-062848 Downlink modulation schemes for E-UTRA (Ericsson)
09/10/2006 13:55 Presented by Mr. Johan Bergman
Discussion (Question / Comment):
Decision: This proposal was agreed.
R1-062849 Uplink modulation schemes for E-UTRA (Ericsson)
This document was revised before the presentation.
R1-062951 Uplink modulation schemes for E-UTRA (Ericsson)
09/10/2006 14:00 Presented by Dr. Stefan Parkvall
Discussion (Question / Comment):
Decision: This document was noted
R1-062512 Modulation Schemes for E-UTRA uplink (Samsung)
This document was revised before the presentation.
R1-062953 Modulation Schemes for E-UTRA uplink (Samsung)
09/10/2006 14:00 Presented by Mr. Jiann-An Tsai
Discussion (Question / Comment):
Samsung clarified that they propose QPSK and 16 QAM as basic modulation scheme and need more discuss pi/2
BPSK and 8PSK with spectrum shaping.
Ericsson and Nokia raised a concern that the spectrum shaping makes an additional complexity.
It was commented that in the case of short block the different between both schemes for link performance could not
change because fro both case the coding gain decrease although the coding gain reduce in the case of short block

13
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

As for 8 QPSK, it was commented that we need more evidence for new modulation scheme.
It was commented that the comparison should be under the same Eb/No because the link budge is related to it.
Samsung commented that their intention is that data rate is the same for both modulation schemes.
Wes McCoy (Freescale Semiconductor) asked how the Tx power class is for LTE. Asbjorn Grovlen (Nokia)
commented that in RAN4 discussion, tx power is based on the power class stay in the same as HSDPA and HSUPA
At final, Chairman summarised the current situation and commented that for the decision for FFS, we need to keep
offline and more contributions, but he is not sure to put the agenda for this in next meeting.)
Decision: This document was noted. The conclusion was followed.
16QAM, QPSK agreed.
- Need for Pi/2 BPSK or QPSK & spectrum shaping: FFS
- Need for 8PSK: FSS

R1-062813 Text proposal for mapping of QAM modulation to TS36.21x (NEC Group)
09/10/2006 14:50 Presented by Mr. Thanh Bui
Discussion (Question / Comment):
Decision: This proposal was agreed. (Signal constellations same as in Rel6, with addition of 64 QAM for LTE)
R1-062712 Scrambling Code in E-UTRA Downlink
(NTT DoCoMo, Fujitsu, Mitsubishi Electric, NEC, Panasonic, Sharp)
09/10/2006 14:50 Presented by Dr. Kenichi Higuchi
Discussion (Question / Comment):
NTT DoCoMo clarified that the first priority in this proposal is that the decision of the necessity for scrambling for
Downlink.
Asbjorn Grovlen (Nokia) commented that they agree to having scrambling but why the specific scrambling is
needed in this stage. Ericsson also commented to this point that the bit level scrambling after the channel coding is
OK for their side.
Christian G. Gerlach asked why two dimension scrambling is need. Kenichi Higuchi clarified that this scheme is
just that different scrambling is for time and frequency domain so that both of bit level and symbol level is fine.
Aris Papasakellariou (TI) raised a concern why we need scrambling in addition to the scrambling of reference
signal. Eric Dahlman commented that such scrambling is beneficial to decode the signal for the different cell by
randomization of the interference. NTT DoCoMo clarified that they also need scrambling for reference signal. To
these comments, Aris express a wonder on the complexity issue on double scrambling.
The symbol level or bit level scrambling was discussed and some companies expressed a wonder on the benefits
provided by bit level scrambling.
With regards to the relation to channel coding, Erik Dahlman (Ericsson) clarified that the scrambling is after the
channel coding not before.
Decision: This document was noted and the discussion was summarized as followed.
DL scrambling on bit level after the channel coding, scrambling of reference signals (or having different
reference signals) agreed, provided the scrambling is of low complexity. One-to-one mapping between
reference signal sequence and scrambling of the BCH.

Not treated due to lack of time

R1-062713 Investigations on Adaptive Control of Roll-off Factor for DFT-Spread OFDM
Based SC-FDMA in E-UTRA Uplink (NTT DoCoMo,
Fujitsu, LG Electronics, NEC, Panasonic, Sharp, Toshiba Corporation)
R1-062919 Adaptive Control of Roll-off Factor for SC-FDMA (Siemens)

6.3.2 Need for distributed transmission in UL

Related to UL reference signal discussion
R1-062513 Performance comparison between LFDMA and DFDMA transmission in UL
(Samsung)
09/10/2006 16:20 Presented by Miss Yunok Cho
Discussion (Question / Comment):
It was clarified by Samsung that real estimation is assumed in this contribution.

14
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Decision: This document was noted.

R1-062553 Localized and distributed transmission in uplink (LG Electronics)
09/10/2006 16:25 Presented by Mr. Jeonghoon Lee
Discussion (Question / Comment):
Decision: This document was noted.
R1-062598 UL distributed transmissions (Motorola)
09/10/2006 16:30 Presented by Dr. Amitava Ghosh
Discussion (Question / Comment):
Some discussions were on the bandwidth for reference signals.
Erik Dahlman (Ericsson) raised a concern why the reference BW needs 6 RB even though data BW is one RB
option 2 it's too much power for reference. He commented that if date BW is one the reference BW should be also
one. Amitava commented that option 2 doesn't use LB for sounding but use SB and for the frequency.
Decision: This document was noted.
R1-062661 E-UTRA Uplink System Design Options (Motorola)
09/10/2006 16:55 Presented by Dr. Amitava Ghosh
Discussion (Question / Comment):
Mr. Chairman commented that the proposal is really correct but in fact we have a fixed time to make a decision so
that can not consider the all things in the same time to make a decision.
Aris Papasakellariou (TI) commented that he agree to the this proposal, on the other hand we must specify until
next September as Mr. Chairman mentioned and asked what kind date the distributed transmission is needed for.
Amitava answered that it's need surely for VoIP case. Mr. Chairman commented that we already decision a half of
RB, 6RB for adapting to VoIP case so that he is not sure that more adaptation is needed for VoIP.
Christian G Gerlach (Alcatel) pointed out the interference coordination become complicated in case of distributed
transmission
Decision: This document was noted.
R1-062686 Localized vs. Distributed transmission for Uplink (Qualcomm Europe)
09/10/2006 17:20 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Decision: This document was noted.
R1-062761 Performance of D-FDMA and L-FDMA with Frequency Hopping for EUTRA
Uplink (NEC Group, NTT DoCoMo)
09/10/2006 17:25 Presented by Mr. Yassin Awad
Discussion (Question / Comment):
Decision: This document was noted.
R1-062816 Comparison between distributed sub-carrier allocation and sub-framae based
frequency hopping (Nokia)
09/10/2006 17:30 Presented by Mr. Jari Lindholm
Discussion (Question / Comment):
Decision: This document was noted.
R1-062850 On distributed transmission in E-UTRA uplink (Ericsson)
09/10/2006 17:33 Presented by Dr. Erik Dahlman
Discussion (Question / Comment):
Decision: This document was noted.
R1-062922 Localized vs. Distributed Subcarrier Allocation for the SC-FDMA UL
(Lucent Technologies)
09/10/2006 17:35 Presented by Dr. Rainer Bachl
Discussion (Question / Comment):
Juho Lee (Samsung) pointed out the data non-associated control signalling aspects.
Joon Kui Anh (LGE) commented that they also compared intra and inter TTI FH and the intra TTI FH can provide
the additional gain with inter TTI FH but it causes more complexity.
Decision: This document was noted.

After the discussion for the all document, the proposals by all documents were summarized as followed.
Proposals:
 L-FDMA (with or without hopping) and D-FDMA
or
 L-FDMA with inter-TTI FH and no intra-TTI FH
o Not proposed.

15
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

 L-FDMA with inter-TTI FH and intra-TTI FH

o hop between two sub-frames within a TTI
o closer to D-FDMA
 L-FDMA with inter-TTI FH and intra-TTI FH (allowing also multiple hops between 2 frequencies
within 1 sub-frame)
o closest to D-FDMA

Conclusion for UL data transmission

 D-FDMA not supported
 L-FDMA with support for inter-TTI FH and intra-TTI FH
o if activated, hop at the sub-frame border between two sub-frames within a TTI
UL control transmission dependent on decisions on control signalling
Reference signal transmission is to be discussed separately (channel sounding etc.)

Discussion on summarising
At first, Mr. Chairman clarified that considering the majority, L-FDMA with FH is beneficial and as the next step,
we must consider what kind of hopping is needed (hopping scheme is too early to be discussed), however, anyway
we must come back to Motorola concern. Motorola commented that D-FDMA is beneficial not only for VoIP but
also for gaming provided by TCP and D-FDMA has the interference diversity gains larger than L-FDMA. For
captured the motivation from Motorola, D-FDMA the forth proposals in the above list was added. But some
companies express their wonder what the difference is between D-FDMA and forth one and it seems to the same.
Aris Papasakellariou (TI) commented that we don't any issue on L-FDMA with FH from the viewpoint of
frequency diversity gain and according to the decision on the TTI length at the last meeting, just Inter TTI FH
should be considered. Eric Dahlman (Ericsson) raised a concern to this comment that we cannot expect the
interference diversity gain for inter TTI FH.
Sarah (Nortel) asked if we assume this for all case control transmission, HARQ, not just date.
Also Juna Montojo (Qualcomm) asked if we can also assume this for sounding reference. Mr. Chairman clarified
that sounding is separate issue and control transmission is depending on the decisions of control signalling.
NTT DoCoMo proposed that the possibility intra sub-frame FH shall be kept. However, Samsung raised a concern
on this proposal from the channel estimation point of view.
It was clarified by Mr. Chairman that the FH is not mandated in the NW.
After the long discussion, Mr, Chairman commented that we don't want to open this issue until the next meeting
and then proposed that we focus on the third option. Motorola agreed to the proposal considering the majority.

6.3.3 Numerology for alternative TDD Frame Structure

R1-062662 TDD Numerology and Alignment with FDD (Motorola)
09/10/2006 21:15 Presented by Mr. Robert Love
Discussion (Question / Comment):
It was clarified that Motorola's definition of the TTD frame is 1 UL and 1 DL and switching point and the
switching point could be changed because TDD UL and DL is asymmetric,
The discussion was on the requirement of latency for LTE. That understanding was not consensus during the
interesting people so that long discussion continued.
Nicholas Anderson (IPWireless) commented that we already have discussed this aspect at San Diego meeting so we
don't need to change, they are happy not to change anything. In addition, they commented that TTI is one milli-
second and more switching point is very interesting from the viewpoint of the latency.
Loic Brunel (Mitsubishi) commented that from the latency point of view they objected to this proposal. .
Tang Hai (CATT) commented that they prefer less SW point, that is one point in 5ms and this can keep in 10ms
even though the flame length is changed.
The long discussion continued one switching point (less point) and multiple switching points (up to 10) within
10ms.
Decision: This document was noted and the conclusion was followed.
Conclusion
Multiple switching points (up to 10) within 10ms radio frame with asymmetric (including symmetric)
UL/DL allocation. Similarities between FDD and TDD should be aimed for (general requirement).

16
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062784 TTI vs TTD (CATT, RITT, ZTE, Huawei, LG Electronics)

09/10/2006 22:00 Presented by Mr. Tang Hai from CATT
Discussion (Question / Comment):
It was clarified by CATT that the problem was the definition of TTI for TDD. Mr. Chairman commented that layer
2 doesn't care about TDD and FDD so that it's nonsense and also he commented that in fact we decided the TTI
length at the last meeting in R1-062441 however the definition of TTI was not described so that the definition will
be defined in LTE specification as same as UTRA, maybe in RAN2 part.
Tang commented that we should discuss with RAN2 although they have not submitted this issue to RAN2 so that
they proposed to send LS to RAN2 reporting the RAN1 current status. Mr. Chairman clarified that we don't discuss
the definition of TTI yet so that we should not send LS also we focus on numerology. Tang commented that TTI is
very important numerology so that the definition should be clear.
Finally, Mr. Chairman commented that now we cannot agree "TTD" and need more discussion so that he
suggesting continue discussion on e-mail reflector.
Decision: This document was noted. No agreement on the new definition yet so that it was decided to continue
discussion on email reflector. It was suggested to provide some input on LCR TDD frame structure compatible
numerology.
R1-062959 The numerology of alternative EUTRA TDD frame structure
(CATT, Huawei, ZTE, RITT)
13/10/2006 09:55 Presented by Mr. Tang Hai from CATT
Discussion (Question / Comment):
It was clarified that TI means timing interval.
Decision: This document was agreed.

6.3.4 Remaining issues on FDD/TDD aligned numerology

Hopping in Uplink
R1-062497 Link Performance of Frequency Hopping in LTE Uplink Localized
transmission (Huawei)
09/10/2006 17:45 Presented by Mr. Chengyu Wang
Discussion (Question / Comment):
Joon Kui Ahn (LGE) commented that the results is almost same as LGE but one point should be notified inter TTI
FH and mix of inter and intra FH has the gains is almost same and it's means that there is no gain by intra TTI FH.
Decision: This document was noted.
R1-062554 Uplink frequency hopping (LG Electronics)
09/10/2006 17:55 Presented by Dr. Joon Kui Ahn
Discussion (Question / Comment):
It was asked how the interference diversity aspect is. The answer was that it should be checked.
Asbjorn Grovlen (Nokia) asked how to maintain the single carrier property on the Inter TTI.
Rainer Bachl (Lucent) pointed out the complexity issue for control signalling although FH could provide the gain.
Decision: This document was noted.
R1-062687 Issues for FDD/TDD aligned Numerology (Qualcomm Europe)
09/10/2006 18:05 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
It was clarified that inter TTI FH should be supported if it is asked which intra and inter TTI FH should be
supported.
Joon Kui Ahn (LGE) asked if the number of RB hopping for each user is same and if not the hopping pattern is
very complicated. The answer was that it depends on the allocation of RB in TTI for each user.
Decision: This document was noted.
R1-062851 Frequency hopping for E-UTRA uplink (Ericsson)
09/10/2006 18:20 Presented by Dr. Erik Dahlman.
Discussion (Question / Comment):
The benefit of intra TTI FH was discussed.
Juho Lee (Samsung) commented that intra TTI FH is worst than Inter TTI due to the Channel estimation so that we
should assumed that inter TTI is the baseline and intra TTI should be consider an additional considering the channel
estimation. To this comment, Erik Dahlman (Ericsson) commented that he agree to the channel estimation issue
that we cannot see the frequency diversity gain however interference diversity and channel diversity gain can be

17
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

expected. Juho commented that we also consider the large RB case for intra FH and such a case could not provide
much interference diversity gain so that we cannot assume just one RB for analysis FH gain.
Decision: This document was noted.

New UL sub-frame structure

R1-062581 The New Sub-Frame Structure for EUTRA Uplink (ZTE)
09/10/2006 19:50 Presented by Ms. Guohong LI.
Discussion (Question / Comment):
Stefan Parkvall (Ericsson) pointed out that form viewpoint of the control signaling discussion, the changing
structure have problem.
Decision: Flame structure is not changed. Signalling concerns can be addressed as part of control signalling
discussion.

CP length
R1-062544 UL sub-frame format and CP durations (ZTE, China Mobile, CATT)
09/10/2006 20:00 Presented by Mr. Zhisong Zuo from ZTE
Discussion (Question / Comment):
Ericsson supported this proposal.
Decision: This proposal was agreed. Editor for 36.211 will capture this agreement on the next version.
R1-062820 UL sub-frame format for long CP (Nokia)
09/10/2006 20:05 Presented by Mr. Jari Lindhlom
Discussion (Question / Comment):
Ericsson, Siemens and Alcatel supported this proposal.
Decision: This proposal was agreed.

Addressing of 1RB in a 1ms TTI

R1-062599 Single RB Assignment (Motorola)
09/10/2006 10:20 Presented by Mr. Robert Love
Discussion (Question / Comment):
It was clarified that one and also more than one RB in frequency domain could be allocated. Nokia raised a wonder
to this proposal at the point of high granularity
Samsung raised a concern on the benefit of this proposal from the viewpoint of channel estimation
It was clarified by Motorola that two consecutive 0.5 sub-frames are allocated to the same user including the
mixture of uni-cast and multi-cast and also the different users.
Decision: This document was noted.
R1-062714 Further Investigations on Resource Block Size for E-UTRA
(NTT DoCoMo, NEC, Panasonic, Sharp)
09/10/2006 10:40 Presented by Dr. Kenichi Higuchi
Discussion (Question / Comment):
Farooq Kahn (Samsung) comment regarding the power control that it can be possible to allocate much power for
one RB and decrease the number of RBs allocated.
Erik Dahlman (Ericsson) commented that from the simplicity the up proposal is good and asked if the MAC
multiplexing is also applicable instead of physical layer multiplexing.
NTT DoCoMo answered that from the delay perspective, in some case MAC layer multiplexing is not allowed but
there is the possibility of MAC multiplexing.
Christian G. Gerlach (Alcatel) asked if the one RB allocation is just for persistent scheduling or also channel
dependent scheduling. The answer was it can be used for persistent scheduling.
Decision: This document was noted.
R1-062763 Single Resource Block Allocation (NEC Group)
09/10/2006 11:00 Presented by Mr. Yassin Awad
Discussion (Question / Comment):
Decision: This document was noted.
R1-062819 Considerations for minimum TTI size for downlink LTE (Nokia)
09/10/2006 11:10 Presented by Mr. Asbjørn Grøvlen
Discussion (Question / Comment):
It was clarified by Nokia that the simulation for VoIP is DL only.

18
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Decision: This document was noted.

After the presentation and discussion on each document, it was discussed whether we keep the possibility the
allocation individual RB
Conclusion
Agreement that it is not needed for the UL.
No agreement that it is needed for the DL. => If agreement can be reached over email reflector until the
next meeting it can be agreed at the next meeting.

The discussion on summarizing

Erik Dahlman (Ericsson) proposed that we should avoid the possibility for UL. Motorola commented that their
proposal is mainly for DL such as related to multicast so no possibility UL is fine. Nokia commented that we don't
need the possibility for DL/UL from view point of complexity issue. Juan Montojo (Qaulcomm) expressed their
view that the option of single allocation is not necessary for both from view point of complexity issue and raised a
concern on Motorola view's about multiplexing of uni-cast and multi-cast.
After the long discussion, taking account of the current situation, that is now we cannot reach to agreement, Mr.
RAN1 Chairman proposed to continue discussion on DL possibility on the e-mail reflector.

BW agnostic L1
R1-062815 On specifying the variable channel bandwidth property for E-UTRA (Nokia)
09/10/2006 12:35 Presented by Mr. Asbjørn Grøvlen
Discussion (Question / Comment):
Mr. Chairman commented that it's definitely very useful document and we are not touching to the RAN4 area such
as the different frequency allocation.
Almost companies agreed principally and pointed out the necessity or more discussion on lower end allocation,
1.25 MHz.
It was asked if FFT size and sampling rate is specified. It was clarified by Mr. Chairman that FFT size and
sampling rate are implementation issue so that we will not specify.
Decision: This document was noted.
Conclusion:Principle of specifying a bandwidth agnostic L1 agreed, details on lower end spectrum
allocation to be decided further (e.g. resolution of 1RB at 1.25MHz allocation. )

Not treated due to lack of time

Hopping in Downlink
R1-062479 Resource-Block mapping of Distributed Transmissions in E-UTRA downlink
(Philips, Intel)
R1-062480 Impacts on channel estimation of Resource-Block Mapping of Distributed
Transmissions in E-UTRA Downlink (Philips)
R1-062578 Performance of DL distributed transmission (Samsung)
R1-062589 Evaluation on mapping scheme from distributed VRB to PRB (Huawei)
R1-062762 Downlink Distributed Resource Block Mapping (NEC Group, NTT DoCoMo)

Spectrum size, number of RB

R1-062477 Spectral efficiency considerations for EUTRA at higher bandwidths
(Alcatel)
R1-062817 Simulation results for 5 MHz E-UTRA DL BLER performance with BS spectrum
shaping FIR filtering (Nokia)
R1-062818 Simulation results for 2.5 MHz E-UTRA DL BLER performance with BS
spectrum shaping FIR filtering (Nokia)

DTF size
R1-062852 DFT size for uplink transmissions (Ericsson)

ACK/NACK repetition

19
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062715 Repetition of ACK/NACK in E-UTRA Uplink

(NTT DoCoMo, Mitsubishi Electric, NEC, Panasonic, Sharp)

BW at cell edge
R1-062716 Minimum Transmission Bandwidth for Shared Data Channel in SC-Based E-
UTRA Uplink (NTT DoCoMo,
Fujitsu, Mitsubishi Electric, NEC, Panasonic, Sharp, Toshiba Corporation)

Withdrawn
R1-062600 UL E-UTRA VoIP Performance with Intra-TTI frequency hopping (Motorola)
R1-062579 Distributed transmission on downlink (Samsung)

6.4 Basic Access Procedures

6.4.1 BCH
R1-062717 BCH Structure considering 20-MHz Overall Transmission Bandwidth
(NTT DoCoMo)
12/10/2006 09:15 Presented by Dr. Kenichi Higuchi
Discussion (Question / Comment):
Asbjorn Grovelen (Nokia) agreed generally to this proposal and asked if what information UE need to read in P-
BCH. It was answered that the specific information in P-BCH should be decided in RAN2, however, if say their
thinking, the information may be needed for HO processes. Joon Kui Ahn asked how UE camping left or right had
side 10MHz BW can read P-BCH if it is located only in center 1.25 MHz BW how. The answer was that it can be
resolved by the extension of UE minimum reception capability.
Joonyoung Cho (Samsung) raised on BCH overhead in this proposal.
Decision: This document was noted.
R1-062765 New definition of minimum UE capability (NEC Group, NTT DoCoMo)
12/10/2006 09:x30Presented by Mr. Thanh Bui
Discussion (Question / Comment):
Joonyoung Cho (Samsung) raised a concern that if extend the UE minimum reception capability it could make a
serious consideration on UE implementation complexity. Thanh Bui commented that in fact we need to consider tat
issue but there are no contribution on RAN1 so far and we don' know exactly what complexity is. Now we can
manage 600 sub carriers and if we extend BW by X RAN4 should discuss this complexity, however, their
expectation is a small deal complexity. They assume that X is 32 and BW is 10.38MHz.
Decision: This document was noted.
R1-062764 BCH, PCH, Cell Search and scalable bandwidth (NEC Group)
12/10/2006 09:45 Presented by Mr. Thanh Bui
Discussion (Question / Comment):
Mieszko Chmiel (Siemens) asked if in option 3 of figure 4, UE capping in left hand side can not connected to the
right hand side. The answer was that in current situation what is the exact of S-BCH is not decided by RAN2 and in
their view active UE don't need to read S-BCH. Anyway option 3 is not their preference.
Mr. Chairman commented that in this proposal S-BCH P-BCH, S-BCH reception is a little bit challenging.
P-BCH, expected to small, S-BCH is large
Joonyoung Cho (Samsung) pointed out a concern on SCH and BCH overhead and commented about MBMS that in
this proposal system need to transmit MBMS carrier more, on the other hand, their proposal MBSM is transmitted
in one of 10 MHz side band.
Decision: This document was noted.
R1-062514 BCH design considering EUTRA spectrum allocations (Samsung)
12/10/2006 10:00 Presented by Dr. Joonyoung Cho
Discussion (Question / Comment):
It was clarified that in this document S-BCH is not consider but probably it is located in centre of system BW as
same as P BCH.
Mr. Chairman commented that there are 3 level of system information, BCH 1 and BCH 2 for primary BCH, and
non- primary BCH. Joonyoung commented that it is not necessary to send BCH 1 and BCH 2, however the wonder
was raised that how UE know BCH2 not be transmitted. The discussion is related to RAN2 discussion on the
previous day, but at that time there was still no information (LS) from RAN2.

20
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Decision: This document was noted.

R1-062688 Design and Performance of BCH for E-UTRA (Qualcomm Europe)
12/10/2006 10:15 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Thanh Bui (NEC) expressed a wonder that the splitting of P and B-BCH is not in line with RAN2 status.
Considering that P-BCH is quite frequently sent and overhead should be minimum, he can not be sure to this
proposal. Mieszko Chmiel (Siemens) commented that the this proposal is different from RAN2 current status,
Decision: This document was noted.
R1-062743 E-UTRA BCH Structure and Procedures, 20 MHz BW Mapping (Siemens)
12/10/2006 10:25 Presented by Mr. Mieszko Chmiel
Discussion (Question / Comment):
Decision: This document was noted.

R1-062983 Mininum UE reception capability (Ericsson, Qualcomm, Nokia, Motorola,

Freescale, IPWireless, Nortel, Siemens, NTT DoCoMo, TeliaSonera,
Vodafone, Sharp, Mitsubishi, Toshiba, Fujitsu, Panasonic, NEC, Lucent, T-
Mobile, TelecomItalia, Alcatel)
12/10/2006 12:30 Presented by Dr. Stefan Parkvall from Ericsson
Discussion (Question / Comment):
Farooq Khan (Samsung) expressed his wonder that when we talked about UE minimum BW capability, almost
people confirmed that 10 MHz BW is too complex and then this time, then 15 MH z. It's much more complex.
Stefan Parkvall (Ericsson) commented for clarification that at that time Tx and Rx BW capability and this time is
just RX so situation is different. We consider just DL not UL.
Joonyoung Cho (Samung) expressed his concern that they cannot agree right now because there are serious
problem on their SCH and BCH design if agreed so we need to more discussion on the SCH and BCH design. To
this comment, Mr. Chairman clarified that the complexity issue is not sure and if this is agreed RAN2 serious
problem can be resolved so that the decision is quite clear.
Finally, this proposal was agreed.
Decision: This proposal was agreed as working assumption
Conclusion
Working assumption
 R1-062983 is agreed.
 SCH, P-BCH transmitted only in the centre frequency , BW is 72sub carriers
 PCH and S-BCH (If a S-BCH will be defined) transmitted only in the centre frequency,
maximum BW is 600 subcarriers

Discussion and comment on summarizing

It was clarified that this working assumption would be agreed and discussion about 20MHz BW and MBMS is next
step. Sarah (Nortel) commented that P- and S-BCH is not clear now in RAN2 so that in working we should not
touch to something related to S-BCH. However, after the off line discussion, this concern could be removed.
Hiroshi Katsuragawa (Sharp) asked if PICH is transmitted in 10MHz at the centre BW or in whole band in DL
control CH. It was clarified by Mr. Chairman that in this working assumption PICH is not related, just PCH and
PICH will take in next step.

R1-062985 [DRAFT] Reply LS on minimum receiver bandwidth capability (Ericsson)

13/10/2006 10:00 Presented by Dr. Stefan Parkvall
Discussion (Question / Comment):
Mr. Jean-Aicard Fabien commented that terminology, primary and secondary has not decided in RAN2 so that we
had better use fixed and flexible in line with RAN2 LS.
Decision: This draft LS was approved with some modification in R1-063006

Not treated due to lack of time

R1-062550 BCH Location in E-UTRA Downlink (ZTE)
R1-062551 Some considerations on BCH of ETURA TDD (ZTE, CATT)

21
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062660 Need to Decode BCH from Adjacent Non–Serving Cells (Texas Instruments)
R1-062824 Broadcast Channel (BCH) structure and performance (Nokia)
R1-062913 LTE BCH - performance analysis (IPWireless)
R1-062960 Summary of BCH in 20MHz (NEC Group)

6.4.2 PCH
R1-062555 Soft-Combined synchronous PCH transmission (LG Electronics)
12/10/2006 11:35 Presented by Mr. Daewon Lee
Discussion (Question / Comment):
Nicholas Anderson (IPWireless) commented that it's a useful paper. The gains from soft-combining within the same
site do not appear to significantly improve the 5%’ile (cell edge) performance. To increase those gains soft-
combining between sites is required but then and we would need to consider the impact on higher layer.
Decision: This document was noted.
R1-062689 On the possibility of intra eNB SFN paging (Qualcomm Europe)
12/10/2006 11:40 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Decision: This document was noted.
R1-062718 Paging Channel Transmission Scheme in E-UTRA Downlink
(NTT DoCoMo, Fujitsu,
Mitsubishi Electric, NEC, Panasonic, Toshiba Corporation)
12/10/2006 11:45 Presented by Mr. Yoshihisa Kishiyama
Discussion (Question / Comment):
Asbjorn Grovlen (Nokia) commented that although PI is shared with control channel in Figure 1, it is different from
decision on Cannes meeting, that is, PI is transmitted in control channel.
Kenichi Higuchi clarified that they agreed PI is a part of L1/L2 control channel however the coding scheme (joint
or separate) was not agreed so that separate coding could be. If we agree joint coding, in that case only PCH can
use soft combining.
Decision: This document was noted.
After the presentation and discussion, the working assumption on PCH soft combining was discussed. The utilized
channel, DL-SCH or PCH was discussed. Nokia commented that even which channel mechanize is taken, the gain
is limited so that they don't care of this technology.

Conclusion
Working assumption: SFN combining of PCH from same eNodeB or different eNodeB not
supported.

Not treated due to lack of time

R1-062782 Physical Allocation of PCH for 20MHz Operating Bandwidth (Sharp)

6.4.3 RACH Procedure Physical Layer Aspects

This section was discussed on Wednesday chairing by RAN1 Vice Chairman, Dr. Sadayuki Abeta (NTT
DoCoMo)

R1-062603 Random Access Channel Email discussion summary (Motorola)

11/10/2006 14:10 Presented by Dr. Amitava Ghosh
Discussion (Question / Comment):
Decision: This document was noted.

R1-062994 Summary of LTE RACH session (Ad Hoc Chairman)

13/10/2006 09:30 Presented by Dr. Sadayuki Abeta
Discussion (Question / Comment):

22
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Decision: This document was endorsed.

Reply LS to RAN2
Conclusion (Chairman's note)
Q1:
The number of preamble is 64.
The number of root sequence is configurable.
Q2:
The control channel design in RAN1 is not yet stable and it is therefore hard to provide
exact bit count.
RAN1 preference is to signal this message on the regular L1/L2 control channels for UL
grants and DL assignments provided the control L1/L2 control channel structure can
accommodate this signalling.
Q3:
There is no restriction from RAN1 prospective
Q4:
a) 24 bit (including CRC) (IOT level is ..)
b) 48 bit (1HARQ), 72 bit (2 HARQ)
c) HARQ can not resolve the contention with good success rate. However, since the
probability of contention should be less than 1%, HARQ should be supported.
Q5:
Asynchronous
Q6:
Mis-alignment of the timing of hybrid ARQ ACKs and NACKs due to contention, may
further have undesirable effects on the data transmissions of other UEs. Therefore, from a
simplicity perspective, it seems preferable not to use hybrid ARQ in DL in case of
possible contention.
Q7:
(a) Our analysis shows that H-ARQ can significantly increase the probability of capturing
one of the transmissions during contention. However, its overall success rate in resolving
contention is not good.
(b) The capture probability depends on the difference in received power between the
contending users. In general, the bigger the power difference, the larger the capture
probability. As a result, the use of power control will reduce the capture probability.
Having different power settings for message 1 and 3 should not affect the capture effect.

Discussion and comment

As for Q1, Dragan Vujcic (LGE) commented that we don't need to waste the resource and the number of
preamble would be limited to be used because it's depending on cell size and the small cell has the small
number of users. NB can inform the number to UE by BCH. However, some companies could not be
sure about the benefits of the limitation and pointed out the UE complexity issue due to changing the
used preamble.
As for Q2, Stefan Parkvall (Ericsson) commented that RAN2 want to multiplex multi user on L1 L2
control signaling, however, RAN1 has not decided the control channel topics, so after the control channel
is discussed, this issue would be discussed. On the other hand, Amitava Ghosh (Motorola) commented
that RAN2 would know this information as soon as possible so that RAN1 is expected to inform some
RAN1 preference.
As for Q3, Noriyuki Fukui (Mitsubishi) asked if there should be maximum time for asynchronous case
considering retransmission case. Stefan commented that time window could be covering such timing and
such a preferable time could be found. Regarding synchronous and asynchronous, the benefit for both
was clarified; sync: simplicity, power saving, non-sync: scheduling flexibility. However, it was
confirmed that these benefits does not need to be informed to RAN2

23
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

As for Q4, from the simulation results of contributions form Motorola, Samsung, Panasonic, possible bits
were listed as followed
a) 24-32 bit (IOT level is ...)
b) 48-64 bit (1 retransmission), 72-96 bit (2 retransmissions)
It was clarified that the difference is depending on cell loading but minimum number is selected as the
value in final LS because RAN2 asked the maximum number of bits. In addition, it was clarified that
these bits includes CRC. Regarding HARQ support or not, it was confirmed that HARQ is no meaning
under contention, however when the probability of contention is less than 1%, it can working very well.
As for Q6, it was asked if what the DL message in LS from RAN2 points, message 2 or message 4.
Stefan commented that if there is no message HARQ is possible, however if there are a risk of
contention, HARQ is not possible, Therefore message 2 in RACH procedure 2 does not use HARQ
because of the possibility of contention, on the other hand, message 4 can use HARQ.

The agreed conclusion was captured in draft reply LS to RAN2 in R1-062972

R1-062972 Draft Reply to RAN2 LS on Random-Access Related Issues (Motorola)
11/10/2006 14:10 Presented by Dr. Amitava Ghosh
Discussion (Question / Comment):
Dragan Vujcic (LGE) raised a concern that in the last sentence what is the benefit of cause. He agreed to the benefit
of CQI but cannot agree to cause. It's should be discussed by RAN2. Hidetoshi Suzuki (Panasonic) commented that
yes in the morning session we agreed to that point and the sentence could capture tat point. For more clarification
on this point, the last sentence was modified to "RAN1 sees the benefit to indicate CQI in the non-synchronized
random access implicit message content".
Tang Hai (CATT) commented that although it was agreed that 64 sequences is preamble for genetic FDD/TDD, in
LCR TDD compatible frame structure, 64 sequences could be reduced and also they submit the RACH procedure
for LCR TDD compatible frame structure. Therefore, they recommend sending the corresponding LS to RAN2. To
capture this comment, the following sentence was added. "It may be noted that these responses are with respect to
generic FDD/TDD frame structure. The recommendation on LCR TDD compatible frame structure will be sent
later to RAN2."
Decision: This draft LS was approved with modification in R1-062976.

The following documents was treated with related to Q4

R1-062602 E-UTRAN Non-Synchronized Random Access Procedure (Motorola)
11/10/2006 10:25 Presented by Dr. Rapeepat Ratasuk
Discussion (Question / Comment):
Decision: This document was noted.
R1-062664 Synchronized Random Access Channel & Scheduling Request (Motorola)
11/10/2006 10:25 Presented by Dr. Rapeepat Ratasuk
Discussion (Question / Comment):
Decision: This document was noted
R1-062576 Proposed response to RAN2 LS in [R1-062434] (Samsung,
NTT DoCoMo, NEC)
11/10/2006 10:30 Presented by Mr. Yongjun Kwak
Discussion (Question / Comment):
Decision: This document was noted
R1-062812 Target collision probability and HARQ adoption for the 1st UL message
(Panasonic, NTT DoCoMo)
11/10/2006 10:32 Presented by Mr. Daichi Imamura
Discussion (Question / Comment):
Decision: This document was noted

Not treated due to lack of time

R1-062595 Proposed LS response on Random Access Related Issues (Motorola)
R1-062853 Proposed answers to RAN2 LS on random access (Ericsson)
R1-062899 RAN2 questions on RACH operation (Siemens)
R1-062822 Procedure for non-synchronized random access (Nokia)

24
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Non-Synchronized RACH message

R1-062481 Asynchronous RACH preamble message design (Philips)
11/10/2006 11:55 Presented by Dr. Filippo Tosato
Discussion (Question / Comment):
Decision: This document was noted
R1-062601 Non-Synchronized Random Access Message Content (Motorola)
11/10/2006 12:00 Presented by Dr. Rapeepat Ratasuk
Discussion (Question / Comment):
The discussion was that what information RAN1 should inform to RAN2. In fact, some company provide the
contents and corresponding number of bits in preamble. It was commented that the content should be discussed in
RAN2.
Dragan Vujcic (LGE) commented that RAN1 should no consider the content which is RAN2 task but focus on the
number of bit, meaning "up 6 bits". In fact, RAN2 has not decided what kind of message should be sent in
preamble.
Panasonic commented that RAN1 work from RAN1/RAN2 joint session in June 2006 is RAN1 provide the
collision probability including additional bit (control information) in addition to random ID.
Mr. RAN1 Vice Chairman commented that RAN1 has task to evaluate the collision probability and also evaluate
the how many clause and CQI bit could be sent from RAN1 perspective for the information to RAN2 final decision.
Decision: This document was noted.
R1-062811 Sequence allocation and Collision probability analysis of RACH with control
information (Panasonic, NTT DoCoMo)
11/10/2006 12:20 Presented by Mr. Daichi Imamura
Discussion (Question / Comment):
Mr. RAN1 Vice Chairman clarified that according to Panasonic and Motorola contributions, 8 control information
can be sent in preamble. Suzuki Hidetoshi (Panasonic) commented that we are informing to RAN2 how many
control information can be sent, 8 control information, and RAN2 should be decided what kind of information can
be considered in 8 information.
Lucent raised a concern that in fact their evaluation results is that all bits should be allocated to random ids under
high collision probability and the results is depending on collision probability so their analysis also could be good
information to RAN2Also LGE supported to Lucent's view.
Mr. Vice chairman expressed his view that it's implementation (operator) matter to allocate how many random
sequences (ids).
Stefan Parkvall (Ericsson) commented that RAN1 can evaluate the benefit of CQI but we should not inform to
Decision: This document was noted.
Conclusion
RAN1 see the benefit of including CQI in cause field so that RAN1 request to RAN2 to kindly consider
to this aspects when designing the cause bits.
This conclusion will be captured in draft LS in R1-062972.

Non-Synchronized RACH Design

R1-062746 On the Length of ZC Sequence for Non-Synchronized RACH Preamble
(Fujitsu)
11/10/2006 14:55 Presented by Mr. Yoshinori Tanaka
Discussion (Question / Comment):
Decision: This document was noted.
R1-062821 Extension of Random Access Preamble: Effect of Frequency Error (Nokia)
11/10/2006 15:00 Presented by Mr. Jari Lindholm
Discussion (Question / Comment):
The concern was raised why the sequence should be optimized for speed.
Lucent and IPWireless commented that in fact in handover or cell edge area the current RACH length, 1msec has
problem on frequency error.
Mr. Vice- Chairman commented that in fact some analysis performed but those are not clear so we keep the length
of RACH and if problem and impact are cleared until the next meeting, we come back to here and he suggested
proponents providing the clarification of impact until the next meeting.
Decision: This document was noted. Keep the current structure. Company will clarify the impact until the next
meeting.

25
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062515 Asynchronous RACH Preamble Design (Samsung)

This document was revised before the presentation
R1-062958 Asynchronous RACH Preamble Design (Samsung)
11/10/2006 15:20 Presented by Mr. Yinong Ding
Discussion (Question / Comment):
Decision: This document was noted.
R1-062552 Non-synchronized random access procedure and preamble (ZTE)
11/10/2006 15:30 Presented by Mr. Zhisong Zuo
Discussion (Question / Comment):
Decision: This document was noted.
R1-062556 RACH Sequence Design Based on Repetition Method (LG Electronics)
11/10/2006 15:35 Presented by Mr. Dragan Vujcic
Discussion (Question / Comment):
Decision: This document was noted.
R1-062630 Non synchronized Random Access Structure for E-UTRA(Texas Instruments)
11/10/2006 15:45 Presented by Dr. Aris Papasakellariou
Discussion (Question / Comment):
Decision: This document was noted
R1-062854 Parameters for basic Random Access preamble (Ericsson)
11/10/2006 15:50 Presented by Dr. Stefan Parkvall
Discussion (Question / Comment):
It was clarified that the sampling rate BW are a little bit rate from TI document (1.07875 and 1.10875 MHz) but the
sequence is exactly same
Decision: This document was noted
R1-062914 Required RACH preamble length (IPWireless)
11/10/2006 14:05 Presented by Mr. Nicholas Anderson
Discussion (Question / Comment):
It was commented that as stating point any UE has the same guard size for every cell size. It was raised a concern
that case 3 has much overhead assumed for cell edge cell.
Decision: This document was noted
After the presentation and discussion, Mr. RAN1 Vice Chairman proposed a 1.0 msec preamble structure for
agreement and way forward for 0.5 msec preamble structure. Nicholas Anderson expressed a wonder that they
proposed 0.5 msec length and the corresponding structure and he also pointed out 1.0 msec has problem in cell edge
user. He pointed out that although the worst case should be considered for the system design, this should not come
always at the expense of commonly-occurring (normal) cases. Therefore, he objected to the only supporting a
1msec structure and commented that if an additional 0.5 ms structure was also possible then the overall design
would be applicable to all deployment scenarios and as such this approach should be agreed. To this comment,
some companies and Mr. Chairman raised a concern that at the last meeting we agreed to change TTI to 1.0 msec
and it decision is applicable to RACH so that at this time the proposed 1.0 preamble structure would be agreed and
0.5 msec case should be discussed with frequency error issue at the next meeting. Also they raised a concern that
changing to 0.5 msec on RACH length causes some problems on TTI length DL transmission, switching points of
TDD and so on. Finally, the proposal below was agreed. One thing was confirmed on this proposal that repetition
case should be excluded form this agreement but the repetition case is not excluded form the future scope.
Nicholas clarified again that 0.5 structure seems to be beneficial for many possible deployment scenarios and that at
the next meeting it should be discussed again.

Agreement
 1.0msec preamble structure:
RA slot = 1 ms

TCP TGP

CP Preamble

Parameters for 1msec TTI only:

CP: 0.1msec
Preamble: 0.8 msec

26
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

GT: 0.1msec
 0.5 msec:
Continue to discuss until next meeting (with effect of frequency error)

Not treated due to lack of time

R1-062629 Collision probability and randomness requirements for Random Access in E-
UTRA (Texas Instruments)
R1-062631 Configurable Cyclic Shift for Non Synchronized Random Access preamble
(Texas Instruments)
R1-062690 RACH sequences and planning (Qualcomm Europe)
R1-062766 RACH Preamble Length (NEC Group)
R1-062883 Filtering roll-off for non-synchronized transmission (Nokia)
R1-062557 RACH Design Issues of Large Cell Deployment (LG Electronics)
This document was revised before the presentation.
R1-062965 RACH Design Issues of Large Cell Deployment (LG Electronics)
R1-062758 On the signal structures of non-synchronized RACH (Nortel)

Alternative TDD structure

R1-062503 Random access preamble design for alternative EUTRA TDD (TD-Tech)
11/10/2006 17:25 Presented by Mr. Dongdong Shen
Discussion (Question / Comment):
Decision: This document was noted.
R1-062785 Consideration on the non-synchronized random access procedure for EUTRA
TDD (CATT, RITT, ZTE, Huawei)
11/10/2006 17:30 Presented by Mr. Tang Hai
Discussion (Question / Comment):
Stefan Parkvall (Ericsson) pointed out that RACH procedure in figure 2 (proposed procedure in this document) is a
little bit different from agreed generic FDD/TDD procedure and the both procedure should be the same with each
other and RAN2 should discuss such procedure (not RAN1). Also Nokia commented that both procedures should
keep to be the same procedure. So Mr. Chairman suggested continuing discussion on the e-mail reflector. In fact,
CATT proposed to make a draft RAN2 LS related LCR TDD version corresponding to R1-062976, but this
business postponed to the next meeting after the agreement on the RACH procedure for LCR TDD compatible
LTE.
Decision: This document was noted. It was decided to continue discussion on e-mail reflector until the next
meeting (Moderator: Mr, Tang Hai from CATT).

Not treated due to lack of time

L1 procedure
R1-062501 Layer 1 Procedure of Non-synchronized Random Access in E-UTRA (ITRI)
R1-062757 The open-loop power-control effect of RACH signals (Nortel)

Clarification on Sync RACH use case

R1-062719 Scheduling Request Transmission Method for E-UTRA Uplink (NTT DoCoMo,
Fujitsu, Mitsubishi Electric, NEC, Sharp, Toshiba Corporation)
Sync RACH design
R1-062516 Synchronized Random Access Design for E-UTRA (Samsung)
R1-062632 Synchronized Random Access Structure for E-UTRA (Texas Instruments)
R1-062633 Wideband Pilot in Synchronized Random Access Burst (Texas Instruments)
R1-062634 Synchronized Random Access: performance comparison of preamble-based
and UL sub-frame structures (Texas Instruments)

27
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062823 Multiplexing of Synchronous RACH (Nokia)

Others
R1-062517 Antenna switching transmission of RACH preamble (Samsung)
R1-062923 Capacity Analysis of E-UTRA Non-synchronized RACH
(Lucent Technologies)
HO aspect (RAN2 issue)
R1-062494 Elimination of the Asynchronous RACH Procedure Requirement during LTE
Handover (InterDigital)
R1-062893 Random access for less-contention-based handover (Fujitsu)

Withdrawn
R1-062629 Collision probability and randomness requirements for Random Access in E-
UTRA (Texas Instruments)

6.4.4 SCH and Cell Search

R1-062606 SYNC channel email discussion summary (Motorola)
This document was revised before the presentation.
R1-062946 SYNC channel email discussion summary (Motorola)
12/10/2006 14:50 Presented by Dr. Amitava Ghosh
Discussion (Question / Comment):
Decision: This document was noted.

The items which should be agreed are listed as followed.

a. Number of cell ids: 512
 Feasibility of creating 512 good reference signal sequences should be investigated
b. Multiplexing of P-SCH and S-SCH: TDM?
c. How many transmissions per 10ms frame
 For TDD: 2x as upper limit (1x better)
 IRAT measurements: more often better (requirements depending on originating RAT)
 Basic structure should allow multiple transmission per frame (allowing for IRAT and
TDD constraints)
 P-SCH and S-SCH 2x per 10ms
 P-SCH 2x per 10ms and S-SCH 1x per10ms
d. Information resulting transmission per 10ms frame
 Symbol/subframe timing, frame timing, cell id, #antennas
e. Initial cell search
1. Symbol timing: P-SCH
2. Radio frame timing, group id and possibly #antennas for BCH: S-SCH
3. Cell id: DL RS
Or
1. Symbol timing : P-SCH
2. Radio frame timing, Cell id : S-SCH
Or
1. Symbol timing, radio timing : P-SCH
2. Cell id : S-SCH
f. Reuses of P-SCH: 1 or 3?
g. Non-initial cell search steps
1. (P-SCH)
2. S-SCH
3. DL RS

28
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

The following 4 approach proposed, but long discussion could not reach agreement to one
approach.

Approach 1 (Ericsson, Motorola, NEC, TI, Nokia, NTT DoCoMo, Freescale,

Fujitsu, Mitsubishi, Panasonic, Interdigital, CATT):
 TDM of P-SCH and S-SCH, transmitted 2x per 10ms for FDD and LCR aligned TDD
frame structure (1-2x per 10ms for TDD)
 5ms timing: P-SCH
 radio frame timing, group id, and possibly #antennas for BCH): S-SCH
 cell id: DL RS
 read the BCH
Approach 1a (Huawei):
 TDM of P-SCH and S-SCH, transmitted 2x per 10ms
 5ms timing: P-SCH
 radio frame timing, cell id: S-SCH
 read the BCH
Approach 2 (Qualcomm):
 TDM of P-SCH and S-SCH, P-SCH transmitted 2x per 10ms with unequal distance
and S-SCH transmitted 1x per 10ms
 5ms timing, radio frame timing: P-SCH
 cell id: S-SCH
 read the BCH
Approach 2a (Samsung, Nortel):
 TDM of P-SCH and S-SCH, P-SCH transmitted 2x per 10ms and S-SCH transmitted
2x per 10ms
 5ms timing, radio frame timing: P-SCH
 cell id: S-SCH
 read the BCH

Discussion and comment

Different companies commented about pros and cons of each different proposal and the long discussion
continued. As on strong discussion point is whether RS is used fro cell search or not. NTT DoCoMo
commented that cell procedure accuracy can be improved by using RS which is beneficial for cell id
detection as shown in their contributions.
Qualcomm expressed a wonder that in this morning session we took care of BW for SCH, BCH and then
now if we take reference signal (RS) into cell search procedure we must consider again BW for RS.
As for "How many transmissions per 10ms frame" Ericsson clarified that multiple transmission per flame
should not be always assumed but should be allowed in basic structure.
Regarding a group id, Huawei expressed his wonder that now we have not decided what group id is and
the benefit of group id not sure and so this time we must consider only complete id and as next step we
consider whether group id is needed or not.

R1-062691 Link analysis of initial cell search (Qualcomm Europe)

12/10/2006 15:30 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
It was clarified by Qualcomm that this proposal is 2 step procedures.
Decision: This document was noted.
R1-062825 Cell Search Concept and Performance (Nokia)
12/10/2006 17:10 Presented by Mr. Asbjørn Grøvlen
Discussion (Question / Comment):
Decision: This document was noted

At the end of the session on Thursday, the following way forward was proposed by Mr.
Chairman.

29
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Way forward: Evaluate the 4 approaches below until next meeting. Drafting session today
18.00 to further consolidate the proposals if possible, outcome of the drafting should be
captured in R1-062990.

R1-062990 Outcome of cell search drafting session (Nokia, Ericsson, Siemens,

TI, NTT DoCoMo, Motorola, Freescale, Institute for Infocomm Research,
Panasonic, Mitsubishi Electronic, Toshiba, CATT, NEC, Nortel, Interdigital)
13/10/2006 13:25 Presented by Mr. Asbjorn Grovlen from Nokia
Discussion (Question / Comment):
LGE supported to approach 1 with redefinition by this document. Nicholas Anderson (IPWireless) mentioned that
placement of the PSC on the last symbol of a sub-frame could still be possible even for TDD by taking guard time
from the start of any subsequent UL sub-frame.
Decision: This document was agreed.
Approach 1 is redefined by this document, with added support from LG Electronics.
Approaches 1a, 2, 2a are still proposed.
Considering the current, Mr, Chairman proposed the following conclusion and it was agreed by
all proponents.
Approach 1 is taken as the working assumption, but will not yet be included in the draft spec
before evaluations of the proposal and the alternative proposals have been discussed.

Not treated due to lack of time

R1-062487 Hierarchical SCH signals suitable for both (FDD and TDD) modes of E-UTRA
(Huawei)
R1-062495 Cell Search Proposal for E-UTRA (InterDigital)
R1-062504 Cell search time performance for alternative EUTRA TDD (TD-Tech)
R1-062518 Cell search procedure and channel structure (Samsung)
R1-062519 SCH design for 20 MHz spectrum allocation (Samsung)
R1-062558 SCH/BCH transmission (LG Electronics)
R1-062559 Comparison of TDM and FDM for P-SCH/S-SCH (LG Electronics)
R1-062560 SCH Structure and Sequences for Cell Search (LG Electronics)
R1-062584 Non-initial cell search performance comparison of FDM based and TDM based
cell search schemes (ETRI)
R1-062604 Cell Search and Measurement with Heterogeneous Bandwidth (Motorola)
R1-062605 SCH Design for Initial Cell Search for E-UTRA DL (Motorola)
R1-062607 SCH Design for Non-initial Cell Search (Motorola)
R1-062635 Proposal for DL SYNC Channel (SCH) for E-UTRA Cell Search
(Texas Instruments)
This document was revised before the presentation
R1-062963 Proposal for DL SYNC Channel (SCH) for E-UTRA Cell Search
(Texas Instruments)

R1-062636 Cell Search Performance in Tightly Synchronized Network for E-UTRA

(Texas Instruments)
This document was revised before the presentation
R1-062964 Cell Search Performance in Tightly Synchronized Network for E-UTRA
(Texas Instruments)
R1-062637 Design of Primary Synchronization Code (PSC) for E-UTRA Cell Search
(Texas Instruments)
R1-062638 Comparison of different S-SCH structures for E-UTRA cell search
(Texas Instruments)
R1-062692 Neighbor cell search - structure and simulations (Qualcomm Europe)

30
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062720 SCH Sequence Configuration for E-UTRA Downlink (NTT DoCoMo,

Institute for Infocomm Research, Mitsubishi Electric, Panasonic, Toshiba
Corporation)
R1-062721 Multiplexing Method of SCH for E-UTRA Downlink (NTT DoCoMo, Fujitsu,
Institute for Infocomm Research, NEC, Panasonic, Toshiba Corporation)
R1-062722 Three-Step Cell Search Method for E-UTRA (NTT DoCoMo, Fujitsu,
Mitsubishi Electric, NEC, Panasonic, Toshiba Corporation)
R1-062723 Neighboring cell search without Using SCH for E-UTRA (NTT DoCoMo, Fujitsu,
Toshiba Corporation)
R1-062744 Reduction of Initial E-UTRA Cell Search Delay (Siemens)
R1-062753 Non-initial access procedure (Nortel)
R1-062754 The further discussion of SCH (Nortel)
R1-062781 Discussion on SCH contents (Sharp)
R1-062783 SCH Structure and Initial Cell Search Procedure for E-UTRA (Sharp)
R1-062786 SCH Structure and Cell Search Method for E-UTRA TDD system (CATT)
R1-062787 Comparing Hybrid and Cross-correlation method for Cell search (CATT)
R1-062826 Cell Search for E-UTRA TDD (Nokia)
R1-062844 SCH structure and 3-step cell search procedure (Nokia)
R1-062845 Initial cell search and long-CP sub-frame structure (Nokia)
R1-062880 Higher-order sectorization in E-UTRA (Ericsson)
R1-062911 LTE Frame Structure for Coherent and Non-Coherent Cell ID Detection
(Freescale Semiconductor)
R1-062912 An Interference Resistant Frame Structure for Cell ID Detection
(Freescale Semiconductor)

6.5 Reference signal structure

R1-062639 Summary of Reflector Discussions on EUTRA DL RS Design Issues
(Texas Instruments)
10/10/2006 14:50 Presented by Dr. Aris Papasakellariou
Discussion (Question / Comment):
It's was clarified that first point is related to SCH and also second but not so much.
Decision: This document was noted.
Not treated
R1-062640 Summary of Reflector Discussions on EUTRA UL RS Design Issues
(Texas Instruments)
6.5.1 Downlink reference signals
General principle of constructing the DL RS
- A DL RS is a combination of a scrambling code (SC) and a orthogonal or “pseudo”-orthogonal sequence (OS or
P-OS)
- FFS what is meant by OS or P-OS (try to agree on a proposal during this week)
- One of N cell ids identifies a combination of one out of X SC and one out of Y P-OS (X*Y=N)
- N, X, Y FFS
- RS structure for 1 TX antenna

31
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Frequency domain

D R1 D D D D D R1 D D D D D R1 D D D D D
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D
0.5 ms
D D D D D D D D D D D D D D D D D D D
D D D D R2 D D D D D R2 D D D D D R2 D D
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D

R1 : First reference symbol R2 : Second reference symbol D : Data

RS Structure for MIMO

- RS structure for 2-TX antenna MIMO is agreed as follows:

Frequency domain

T1 D D T2 D D T1 D D T2 D D T1 D D T2 D D T1
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D
0.5 ms
D D D D D D D D D D D D D D D D D D D
T2 D D T1 D D T2 D D T1 D D T2 D D T1 D D T2
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D

T1 : Pilots for Tx Ant 1 T2 : Pilots for Tx Ant 2

R D : Data

R1-062724 Reference Signal Structure in E-UTRA Downlink (NTT DoCoMo, Fujitsu,

KDDI, Mitsubishi Electric, NEC, Panasonic, Sharp, Toshiba Corporation)
09/10/2006 15:05 Presented by Mr. Yoshihisa Kishiyama
Discussion (Question / Comment):
It was clarified that at last time we agreed CDM in same Node B and this proposal is for more that 3 sector case, 6.
It was clarified that the scrambling need more different sequence in addition to CDM and scrambling code is type
of reference sequence. The cell ID is used for scrambling code.
Huawei commented that what the exact orthogonal pattern is and if 6 in that case orthogonal code and scrambling
uses the same cell ID. It mean the overlapping of cell ID so that not 6. NTT DoCoMo commented that they don't
propose the exact orthogonal sequence pattern but just reference signal is the combination for orthogonal code and
scrambling code. NEC also pointed out the overlap of cell ID for orthogonal and scrambling code. To this point,
Mr. Chairman clarified that we don't need basically to identify the cell ID with scrambling code and orthogonal.
NTT DoCoMo clarified that their preference is figure 2, meaning three orthogonal patterns with no overlapping.
It was raised a concern where number of 3 comes from. Aris (TI) clarified that it can provide the reasonable number
so we decided.
Erik Dahlman (Ericsson) clarified that in his understanding the reference signal is produced by combination of
orthogonal reference and scrambling as same as DoCoMo view.
Decision: This document was noted.
To try to reach to conclusion, the discussion summarized. The final summary is and as for the orthogonal of
sequence and number of necessary cell ID, the long discussion continued. The final summary for RS multiplexing
for cells of same Node B, is as followed.

- A DL RS is a combination of a scrambling code (SC) and a orthogonal or “pseudo”-orthogonal sequence (OS

or P-OS)
- FFS what is meant by OS or P-OS (try to agree on a proposal during this week)

32
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

- One of N cell ids identifies a combination of one out of X SC and one out of Y P-OS (X*Y=N)
- N, X, Y FFS

As the number of cell ID and combination of N, X, Y, following options was proposed but the discussion
could not reach to the agreement.
- With N = 512: 170 SC and 3 P-OS
- With N = 768: 128 SC and 6 P-OS or 256 SC and 3 P-OS
- With N = 512: 64 SC and 8 P-OS or 128SC and 4 P-OS
Also the following point was discussed but could not be concluded.
- Orthogonal sequence and RS scrambling code follow from the same ID.
- Orthogonal sequence can be re-used in non-overlapping synchronized cells.
- Allocation of different scrambling codes in synchronized cells is also possible. RS scrambling
code follows from cell id.
- Frequency hopping pattern can be derived from the SC.

Other comment and question on summarizing.

As the meaning of pseudo-orthogonal, Branislav Popovic (Huawei) commented that in the DoCoMo proposal, it's
orthogonal just between overlapping cells.
Mr. Chairman asked if we need a larger number of cell ID than WCDMA and not smaller. Nokia raised a concern
that from the channel estimation perspective the considerable ids are limited. The issue is just on channel estimation
and cell search procedure has not generic issue even if the sequence feature is satisfied.

On the last day, R1-062966 was proposed as general principle of DL reference signals.
R1-062966 Downlink Reference signals (Ericsson)
13/10/2006 10:10 Presented by Dr Erik Dahlman
Discussion (Question / Comment):
The some comments were raised mainly on the page 6. For instance, the pattern on the third bullet is related to
position and the exact pattern is TBD. The mutually orthogonal over a block depends on TF position. The
discussion on line could not reach to the agreement so that Mr. Chairman suggested offline discussion on the coffee
break.
Decision: After the off line discussion, this document was revised in R1-063008.
R1-063008 Downlink Reference signals (Ericsson)
13/10/2006120:10 Presented by Dr Erik Dahlman
Discussion (Question / Comment):
Decision: This document was agreed as working assumption.

2-Tx antenna case

From the summary in R1-062639, there is no concern on two antenna case for MIMO so that RS structure for
2-TX antenna MIMO is agreed as shown
Frequency domain

T1 D D T2 D D T1 D D T2 D D T1 D D T2 D D T1
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D
0.5 ms
D D D D D D D D D D D D D D D D D D D
T2 D D T1 D D T2 D D T1 D D T2 D D T1 D D T2
D D D D D D D D D D D D D D D D D D D
D D D D D D D D D D D D D D D D D D D

T1 : Pilots for Tx Ant 1 T2 : Pilots for Tx Ant 2

R D : Data

4-Tx antenna case

33
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062751 Consideration on MIMO DL Reference Signal Design for 4 Tx (Nortel)

10/10/2006 17:40 Presented by Mr. Dongsheng Yu
Discussion (Question / Comment):
It was asked if the proposal has the intention for that the option 1 and 2 could be selected depending on the
threshold of speed. It was clarified by Nortel that they don't intend reconfigurable option but select one option for
specification. The other question asked if compared with 2 tx antenna case, in option 1, there are any performance
degradation except for overhead increasing. Nortel commented that we would consider no degradation except for
overhead increasing i.e. channel estimation does not degrade because the proposal has the same TF spacing as 2-tx
MIMO case.
CATT expressed a wonder for option 1 in case of TDD. Motorola raised a concern on much overhead, 20 % in the
case of option 1.
Aris Papasakellariou pointed out the spacing in case of option 1 is 6 same as 1 an 2 -tx case and supported option 1.
Juan Montojo (Qualcomm) considering CQI and interference estimation for power control, supported option 1.
Also Juho Lee (Samsung) supported option 1 considering the compatibility to 1 and 2-tx case and interference
estimation.
It was discussed how to optimise, MIMO case and TX diversity.
Long discussion continued and then Mr. Chairman commented that option 1 is good to stick to SI working
assumption, however, there are concern on overhead. Also some companies pointed out we need more evaluation
and simulation results fro decision.

Decision: This document was noted. As conclusion from long discussion, it was proposed that we need more
evaluation on the condition that 4-Tx antenna RS structure is stick to SI working assumption, i.e. RS from 1-Tx
antenna and reasonable OH. The following way forward was agreed.
RS structure for 4-TX antenna MIMO
o RS from 1-TX antenna transmission are kept in the same positions also for the 4-TX antenna
RS structure
o RS overhead in the order of 15%
o Prepare a proposal during this week that will be taken as a working assumption and needs to be
confirmed by simulations until before the next meeting.

R1-062979 MIMO DL Reference Signal Design for 4 Tx (Nortel, Motorola)

R1-062993 MIMO DL Reference Signal Design for 4 Tx (Nortel, Motorola,
Samsung, Nokia, Siemens, Philips, LGE, Huawei, ZTE, NTT DoCoMo )
13/10/2006 12:15 Presented by Mr. Brian Classon
Discussion (Question / Comment):
Decision: This document was agreed as working assumption.
R1-062998 DL RS structures for evaluation with 4 Tx Antennas
(TI , NTT DoCoMo, Siemens, Philips)
13/10/2006 12:20 Presented by Dr. Aris Papasakellariou
Discussion (Question / Comment):
Decision: This document was noted.
R1-063007 MIMO DL Reference Signal Design fro 4Tx (Qualcomm Europe)
13/10/2006 12:30 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Decision: This document was noted.
Sarah Boumendil (Nortel) commented that we need more discussion to conclude this topic with a target of reducing
OH to around 15%. Mr. Chairman proposed as conclusion that R1-062993 is agreed as working assumption and we
Prepare a proposal during this week that will be taken as a working assumption and needs to be confirmed by
simulations until before the next meeting.

Conclusion
R1-062993 is agreed as working assumption for 4Tx and to be confirmed by simulations, e.g.
against reference cases in R1-062998 or R1-063007.

R1-062980 DL-RS-4Tx for EUTRA TDD (CATT, RITT, Huawei, ZTE)

13/10/2006 12:35 Presented by Mr. Tang Hai from CATT

34
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Discussion (Question / Comment): Nicholas Anderson (IPWireless) commented that this structure (for the LCR
TDD mode) seemed far more sensible than the one presented in R1-062993 for the generic frame structure
FDD/TDD modes.  He indicated that this was because the structure in R1-062993 would result in channel
estimation performance variation between antennas which he said would be undesirable and could have severe
consequences for UE terminal design and for the system performance of link adaptation.
Decision: This was agreed as working assumption for 4Tx alternative TDD frame structure..

Not treated due to lack of time

R1-062473 Pilot Boosting Consideration in E-UTRA Downlink (SHRCWC)
R1-062474 A Proposal for an Improved DL Reference Symbol Positioning in EUTRA
(Alcatel)
R1-062475 Considerations on the EUTRA DL reference signal structure and the DC sub-
carrier (Alcatel)
R1-062488 DL reference symbols with varying positions in frequency - system-level
evaluation (Huawei)
R1-062520 Downlink reference signal : time-frequency averaging/interpolation(Samsung)
R1-062521 DL reference signal structure: common vs dedicated (Samsung)
R1-062561 LGE’s views on the various aspects of downlink reference signal design
(LG Electronics)
R1-062608 Issues of non-overlapping DL reference signal with power boosting(Motorola)
R1-062609 Simulation Results for GCL based DL Reference Signals (Motorola)
R1-062693 Design of DL Reference Signals (Qualcomm Europe)
R1-062725 Reference Signal Structure for MIMO in E-UTRA Downlink (NTT DoCoMo,
Fujitsu, Mitsubishi Electric, Panasonic)
R1-062788 The downlink reference symbols design for EUTRA TDD (CATT, RITT, ZTE)
R1-062827 Reference signals for mixed carrier MBMS (Nokia)
R1-062855 DL reference symbols (Ericsson)
R1-062901 Proposal for dedicated pilots in downlink precoding for EUTRA MIMO
(Motorola)

6.5.2 Uplink reference signals

All documents of this section were not treated due to lack of time
R1-062498 Uplink Reference Signal for E-UTRA (Huawei)
R1-062548 Uplink Reference Design Considering Reference Power Boost, Channel
Measurement and Interference Mitigation (ZTE)
R1-062562 Uplink reference signal multiplexing method (LG Electronics)
R1-062563 Performance comparison between CDM and FDM Pilot for Uplink SC-FDMA
(LG Electronics)
R1-062610 UL Reference Signal Multiplexing Structures for E-UTRA (Motorola)
R1-062611 E-UTRA SC-FDMA UL Reference Signal Design (Motorola)
R1-062641 Multiplexing of Distributed (“Sounding”) Reference Signals for CQI
Measurement and Scheduling in EUTRA Uplink (Texas Instruments)
R1-062642 Uplink Reference Signal Design in EUTRA (Texas Instruments)
R1-062643 Overview of Distributed (“Sounding”) Reference Signal Multiplexing Methods
in EUTRA Uplink (Texas Instruments)
R1-062644 Reference Signal Multiplexing for 1 ms TTI in EUTRA Uplink
(Texas Instruments)
R1-062694 Design of UL Reference Signals (Qualcomm Europe)

35
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062726 Multiplexing Method for Orthogonal Reference Signals for E-UTRA Uplink
(NTT DoCoMo, Fujitsu, KDDI, LG Electronics, Mitsubishi
Electric, NEC, Panasonic, Sharp, Toshiba Corporation)
R1-062727 Orthogonal Reference Signal Structure for Uplink MIMO in E-UTRA (NTT
DoCoMo, Mitsubishi Electric, NEC, Panasonic, Sharp, Toshiba Corporation)
R1-062728 Reference Signal Sequence Allocation Method in E-UTRA Uplink (NTT
DoCoMo, Mitsubishi Electric, Panasonic, Sharp, Toshiba Corporation)
R1-062729 Group-wised Frequency Resource Allocation for Frequency Domain Channel-
dependent Scheduling in SC-Based E-UTRA Uplink (NTT DoCoMo, Fujitsu,
Mitsubishi Electric, NEC, Panasonic, Sharp, Toshiba Corporation)
R1-062752 Further discussion on UL reference signals (Nortel)
R1-062767 Reference signal multiplexing for EUTRA uplink (NEC Group)
R1-062768 Reference signal multiplexing for data-non-associated control signal in EUTRA
uplink (NEC Group)
R1-062789 Multiplexing Scheme of EUTRA SC-FDMA Uplink Reference Signals
(CATT, RITT, ZTE)
R1-062828 UL Reference Signal Structure for E-UTRA (Nokia)
R1-062856 UL reference symbols (Ericsson)
This document was revised before the presentation.
R1-062952 UL reference symbols (Ericsson)
R1-062924 On Reference Signals for SC-FDMA (Lucent Technologies)
R1-062941 Low cost training for transmit antenna selection on the uplink
(Mitsubishi Electric, NTT DoCoMo)
R1-062942 Performance comparison of training schemes for uplink transmit antenna
selection (Mitsubishi Electric, NTT DoCoMo)

Withdrawn
R1-062522 Uplink reference signal multiplexing (Samsung)

6.6 Downlink MIMO, Transmit Diversity and Beamforming

This section was discussed on Thursday chairing by RAN1 Vice Chairman, Dr. Juho Lee (Samsung)

R1-062580 LTE MIMO email discussion summary (Samsung)

Decision: This document was noted.
R1-062999 LTE MIMO session Chairman's note (Ad Hoc Chairman)
13/10/2006 09:35 Presented by Dr. Juho Lee
Discussion (Question / Comment):
Decision: This document was endorsed, and it was decided to schedule conference calls on selected topics to speed
up the progress until next meeting.

After the endorsement of this document, Nokia clarified about companies' view regarding Tx Diversity. They now
are in neutral position on the following points; (although the position is edited as "NO" in R1-062999)
 For 2TX antennas, only one TxD scheme for control channels other than SCH,
 For 4TX antennas, only one TxD scheme for control channels other than SCH.

Not treated due to lack of time

R1-062482 MIMO resource definition for E-UTRA (Philips, Ericsson)

36
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

6.6.1 Maximum number of code words for 4x4 MIMO

R1-062564 System level results for investigation; Maximum number of codewords for 4x4
MIMO (LG Electronics)
Decision: This document was noted.
R1-062645 Description of Per-Group Rate Control (PGRC) And System Level
Comparison With Per-Antenna Rate Control (PARC) (Texas Instruments)
Decision: This document was noted.
R1-062646 Signaling and Feedback Requirements For Different Number of Codewords
(Texas Instruments)
Decision: This document was noted.
R1-062647 Single-user MIMO performance with largest CQI feedback
(Texas Instruments)
Decision: This document was noted.
R1-062695 Max number of codewords for DL SU-MIMO (Qualcomm Europe)
Decision: This document was noted.
R1-062810 Discussion on maximum number of codewords for 4x4 MIMO (Panasonic)
Decision: This document was noted
R1-062829 Impact of the maximum number of codewords on the 4x4 LTE system
performance (Nokia)
Decision: This document was noted
R1-062859 Maximum number of codewords for MIMO in E-UTRA downlink (Ericsson)
Decision: This document was noted
R1-062902 Maximum number of codewords for E-UTRA MIMO (Motorola)
Decision: This document was noted
R1-062975 MSC levels for E-UTRA MIMO (Qualcomm Europe)
Decision: This document was noted

Discussion points
- Peak data rate
 CQI accuracy: more severe impact for high geometry case. Adaptability to such cases?
- MCS granularity
 Impact on the performance not agreed at least for SIC
 Concern on impact of CQI estimation error especially when having very good MCS granularity
- Signalling overhead
 DL: TF signalling
 UL:
 CQI
 Should be a single CQI reporting scheme regardless the UE receiver type
 ACK/NACK
- Latency due to different receiver implementation
- Should consider various receiver implementations
 LMMSE
 (near-)ML
 SIC
- Optimization of the overall design should be for 2x2. -> Common understanding.
 Better performance for 4x4 on top of the optimization for 2x2.
 Justification of the cost needed vs performance for 4x4.
- Is there any receiver structure that absolutely requires 4 CWs?

Proposals:
- 2 CWs (supported by 14 companies)
- 4 CWs (supported by 2 companies)

Agreed working assumption: 2 CWs.

37
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

(Chairman’s note: from the Node B perspective, the maximum number of codewords is 4)

Withdrawn
R1-062696 ACK structure for 4x4 DL SU-MIMO (Qualcomm Europe)
6.6.2 Layer permutation vs. no layer permutation
R1-062523 Link performance comparison of layer permutation vs. no layer permutation
(Samsung)
Decision: This document was noted
R1-062524 System performance comparison of layer permutation vs. no layer permutation
(Samsung)
Decision: This document was noted
R1-062565 Link performance of DL SU-MIMO according to the amount of feedback
overhead (LG Electronics)
Decision: This document was noted
R1-062566 Link Evaluation of DL SU-MIMO – Impact of Generalized CDD
(LG Electronics)
Decision: This document was noted
R1-062648 System Level Study Of Channel Quality Indicator (CQI) Quantization
(Texas Instruments)
Decision: This document was noted
R1-062649 Link level performance of layer permutation scheme (Texas Instruments)
Decision: This document was noted
R1-062697 Link analysis of layer permutation and no layer permutation
(Qualcomm Europe)
This document was revised before the presentation.
R1-062974 Link analysis of layer permutation and no layer permutation
(Qualcomm Europe)
Decision: This document was noted

R1-062830 Performance of layer permutation for LTE SU-MIMO (Nokia)

Decision: This document was noted
R1-062940 Effects on throughput when using Layered Permutation for LTE-Based
RXCVR Structures (Broadcom)
Decision: This document was noted

Layer permutation benefit

▪ Yes (1 company)
▪ No (5 companies)

Agreed way forward

- On the layer permutation proposal, continue discussion including simulation assumptions etc via email
reflector until the next meeting.
 Take into account the implication on the UL feedback overhead and also other aspects of LTE
MIMO solution.
- Take decision in the next meeting on whether to use or not.
- The layer permutation to be discussed as a part of UE feedback agenda item in the next meeting.

6.6.3 MU-MIMO
Precoding, unitary vs non-unitary

38
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062483 Comparison between MU-MIMO codebook-based channel reporting

techniques for LTE downlink (Philips)
Decision: This document was noted
R1-062489 Unitary precoding with non-unitary fallback mode (Huawei)
Decision: This document was noted
R1-062525 Dynamic Mode Switching between Single and Multi-User MIMO (Samsung)
Decision: This document was noted
R1-062526 Further Performance Comparison of Unitary vs. Non-Unitary Precoding
(Samsung)
Decision: This document was noted
R1-062545 Performance Comparison of Unitary vs. Non-Unitary Precoding for MU-
MIMO (ZTE)
Decision: This document was noted
R1-062698 System Comparison of SU-MIMO and SDMA operations
(Qualcomm Europe)
Decision: This document was noted
R1-062925 Link-level results for nonunitary precoding using zero-forcing in LOS channels
(Lucent Technologies)
Decision: This document was noted

Not treated to due to lack of time

MCS selection and power loading
R1-062472 Advanced MCS Selection and Power Loading for Multi-stream Downlink
MIMO with Reduced CQI Feedback (SHRCWC, RITT)
Resource allocation type with MU-MIMO
R1-062730 Downlink MIMO Scheme for Shared Data Channel in E-UTRA (NTT
DoCoMo, Fujitsu, Institute for Infocomm Research, Mitsubishi Electric, NEC)
Quantization
R1-062776 Effect of Quantization Errors on the Achievable Throughput of LTE MU-MIMO
Schemes (CHTTL)

6.6.4 Transmit diversity

Tx Diversity for SCH, Tx Diversity for the other channels
R1-062476 Comparison of transmit diversity schemes for E-UTRA in noise and
interference limited scenarios (Alcatel)
Decision: This document was noted.

Companies’ views are as follows:

For 2TX antennas, only one TxD scheme for control channels other than SCH
- Yes: Qualcomm, Sharp, Samsung, Siemens, LGE, Huawei, Motorola
- No: Nortel, ETRI
For 2TX antennas, only one TxD scheme for control channels other than SCH & BCH
- Yes: Qualcomm, Sharp, Samsung, Siemens, LGE, Huawei, Motorola, Nokia, Nortel, ETRI
For 4TX antennas, only one TxD scheme for control channels other than SCH
- Yes: Qualcomm, Sharp, Samsung, Siemens, LGE, Huawei, Motorola
- No: Nortel, ETRI
For 4TX antennas, only one TxD scheme for control channels other than SCH & BCH
- Yes: Qualcomm, Sharp, Samsung, Siemens, LGE, Huawei, Motorola, Nokia, Nortel, ETRI
For control channels,
1) non-SFBC-based: Motorola, Samsung, ETRI, Sharp, Qualcomm, LGE, Siemens, Nokia

39
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

A. CDD (or PSD) (for both 2 tx and 4 tx antennas) (not for SCH)
B. FSTD (for both 2 tx and 4 tx antennas)
C. PVS
2) SFBC-based (with allowing different TxD for SCH): Nortel, Nokia, Alcatel, Huawei, Philips,
Ericsson, Lucent
A. SFBC (only for 2 tx antennas)
B. SFBC + PSD (or CDD) (4 tx antennas)
C. SFBC + FSTD (4 tx antennas)

Agreed way forward:

Take email discussion on the control channel TxD until the next meeting.

Not treated to due to lack of time

R1-062490 System Level Simulations of Common Control Channel Transmit Diversity
(Huawei)
R1-062527 Transmit diversity performance for the common control channels (Samsung)
R1-062528 Transmit diversity performance for the shared data channel (Samsung)
R1-062583 Downlink Transmit Diversity Method for BCH Channel (ETRI)
This document was revised before the presentation.
R1-062977 Downlink Transmit Diversity Method for BCH Channel (ETRI)
R1-062584 System level evaluations of diversity schemes for SCH (ETRI)
R1-062699 Link analysis of DL control channel with transmit diversity
(Qualcomm Europe)
R1-062731 Transmit Diversity Scheme for E-UTRA Downlink (NTT DoCoMo, Fujitsu,
Institute for Infocomm Research, LG Electronics, Mitsubishi Electric, NEC,
Panasonic,)
R1-062732 CDD-Based Pre-coding Scheme for Rank = 1 and 2 (NTT DoCoMo)
R1-062747 Performance Evaluation of Downlink Open Loop Schemes for 2- and 4-Branch
LTE Control Channel (Nortel)
R1-062755 Further Results on SCH Search Performance with Transmit Diversity(Nortel)
R1-062756 BCH Detection Performance Evaluation (Nortel)
R1-062778 Further System-Level Simulation Results for Downlink Inter-Sector Macro
Diversity (CHTTL)
R1-062780 Comparing Transmit Diversity Schemes for common control channels in E-UTRA
Downlink (Sharp)
R1-062790 Transmit diversity schemes for E-UTRA SCH (CATT)
R1-062831 Open Loop DL Transmit Diversity for Common Control Channels (Nokia)
R1-062832 Open Loop DL Transmit Diversity for the Shared Data Channel (Nokia)
R1-062858 Further results on transmit diversity for common control and data channels
(Ericsson)
R1-062903 E-UTRA Open Loop Transmit Diversity (Motorola)

6.6.5 Precoding details

All documents of this section were not treated due to lack of time
R1-062493 Performance Benchmark for a New Unitary Precoding Scheme with Uniform
MCS Allocation (Intel Corporation)
R1-062507 Performance of codebook based precoded MIMO transmission schemes for
EUTRA (Freescale Semiconductor)
R1-062508 Cluster size for codebook based precoding in downlink MIMO for EUTRA
(Freescale Semiconductor)

40
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062509 Precoding methodologies with rank adaptation for EUTRA MIMO

(Freescale Semiconductor)
R1-062510 Efficient method for feedback reduction and feedback mechanism for precoded
MIMO in EUTRA (Freescale Semiconductor)
R1-062529 Precoding for MIMO spatial multiplexing and transmit diversity (Samsung)
R1-062546 Performance Evaluation of Codebook-based Precoding (ZTE)
R1-062567 Codebook design and verification for 4x1 MIMO (LG Electronics)
R1-062568 System level evaluation of 2x2 downlink SU-MIMO with rank adaptation
(LG Electronics)
R1-062650 Codebook Design for E-UTRA MIMO Pre-coding (Texas Instruments)
R1-062700 Precoding structure for DL MIMO (Qualcomm Europe)
R1-062769 On the codebook and precoding block sizes for downlink MIMO precoding
(NEC Group)
R1-062770 Way forward on precoding scheme (NEC Group, NTT DoCoMo)
R1-062775 A Non-codebook-based Precoding Scheme for TDD E-UTRA (CHTTL)
R1-062791 Further consideration on the downlink reference symbols of beam-forming for
EUTRA TDD (CATT)
R1-062792 Non-codebook based pre-coding for E-UTRA TDD Downlink (CATT)
R1-062793 Downlink reference signal aspects for non-codebook based pre-coding in TDD
mode (CATT)
R1-062794 Link level simulation results for non-codebook based pre-coding in EUTRA TDD
(SVD) (CATT)
R1-062795 Link level simulation results for non-codebook based pre-coding in EUTRA TDD
(GBF) (CATT)
R1-062833 Linear Precoding for single stream transmission from 2TX antennas (Nokia)
R1-062857 Beamforming in E-UTRA (Ericsson)
R1-062904 Frequency Domain Adaptive Precoding for E-UTRA MIMO (Motorola)
R1-062905 Additional results on frequency-domain adaptive precoding for EUTRA
MIMO (Motorola)

6.6.6 UE feedback
All documents of this section were not treated due to lack of time
R1-062491 Overhead reduction of UL CQI signalling for E-UTRA DL (Huawei)
R1-062492 Baseline uplink E-CQI message – content and size (Huawei)
R1-062665 Differential Feedback for MIMO Precoding (Intel Corporation)
R1-062701 Analysis of support channel overhead for DL MIMO (Qualcomm Europe)
R1-062749 Further results on the impact of speed, feedback period, and sub-channel
bandwidth on the performance of downlink closed loop schemes for 4-branch
LTE (Nortel)
R1-062750 Further Performance Evaluation for DL Adaptive MIMO (Nortel)
R1-062796 Uplink transmit diversity scheme to provide full CSI to support downlink MIMO
transmission for TDD operation (CATT)
R1-062873 E-UTRA Incremental CQI Reporting Using DCT Coding (Ericsson)
R1-062906 Uplink sounding for obtaining channel state information at Node B in EUTRA
(Motorola)
R1-062907 Direct channel feedback for obtaining channel state information at Node B in
EUTRA (Motorola)
R1-062908 Mobile Assisted Sounding feedback for Multi Antenna System for EUTRA
(Motorola)

41
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

6.7 UL Timing Control

All documents of this section were not treated due to lack of time
R1-062541 Physical Channel for Timing Synchronization
(Mitsubishi Electric, NTT DoCoMo)
R1-062702 Timing control for UL transmissions (Qualcomm Europe)
This document was revised before the presentation.
R1-062949 Timing control for UL transmissions (Qualcomm Europe)
R1-062834 UL timing control accuracy and update rate (Nokia)
R1-062860 Timing advance for E-UTRA uplink (Ericsson)
R1-062926 Considerations for Frequency Control in E-UTRA Uplink
(Lucent Technologies)

6.8 UL/DL Power Control

All documents of this section were not treated due to lack of time
R1-062496 Combined Open Loop/CQI Based Uplink Power Control for E-UTRA
(InterDigital)
R1-062586 Power Control for Interference Coordination including Pilot and Control
Channels (Alcatel)
R1-062612 UL Power Control for E-UTRA (Motorola)
R1-062613 Acceptable UL IoT Level vs. Resource Allocation Attributes (Motorola)
R1-062614 DL Power Control for E-UTRA (Motorola)
R1-062615 DL Power Allocation for Dynamic Interference Avoidance in E-UTRA
(Motorola)
R1-062651 Uplink Power Control for EUTRA: Optimizing the Trade-off between Cell-
Edge and Cell-Average Throughputs (Texas Instruments)
R1-062703 UL RACH Power Ramping (Qualcomm Europe)
R1-062704 Intra-cell power control for UL (Qualcomm Europe)
R1-062705 Analysis of Inter-cell Power Control for Interference Management in E-UTRA
UL (Qualcomm Europe)
R1-062706 DL power control (Qualcomm Europe)
R1-062733 Transmission Power Control in E-UTRA Downlink (NTT DoCoMo, Fujitsu,
Mitsubishi Electric, NEC, Sharp)
R1-062734 Transmission Power Control in E-UTRA Uplink (NTT DoCoMo)
R1-062745 Considerations on E-UTRA Uplink Time Synchronization (Siemens)
R1-062777 Investigations on Fast Sector Selection with Intra-Cell Interference coordination
in E-UTRA Downlink (CHTTL)
R1-062835 UL power control (Nokia)
R1-062861 Uplink Power Control for E-UTRA (Ericsson)
R1-062862 Downlink Power Control for E-UTRA– Impact on Standards (Ericsson)
R1-062915 UL power control for predictable interference (IPWireless)
R1-062932 Uplink Scheduling With Inter-Cell Power Control, with Extensions to
Interference Coordination (Lucent Technologies)
R1-062933 Intra-Cell Power Control for the E-UTRA Uplink (Lucent Technologies)

Withdrawn
R1-062616 UL System performance impact from EVM and Adjacent channel emissions
with UL PC (Motorola)

42
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

6.9 DL PAPR Reduction

All documents of this section were not treated due to lack of time
R1-062471 A Gradient Based Peak-to-Average Power Ratio Reduction Method
(Agere Systems)
R1-062549 One Efficient PAPR Reduction Method in Downlink (ZTE, CATT, RITT)
R1-062617 DL PAR Reduction (Motorola)
R1-062836 Initial results for BS PAPR impact of EVM requirements (Nokia)
R1-062928 On definition and target range for DL PAPR (Lucent Technologies)
R1-062929 Comparison of DL PAPR reduction methods (Lucent Technologies)

6.10 Physical Layer specification aspects of Scheduling

All documents of this section were not treated due to lack of time
R1-062530 DL resource allocation strategy (Samsung)
R1-062531 Uplink cell throughput performance with different allocation unit
(Samsung)
R1-062569 Restriction on the number of scheduled UEs in downlink (LG Electronics)
R1-062570 Downlink HARQ (LG Electronics)
R1-062571 Uplink resource request for uplink scheduling (LG Electronics)
R1-062572 Group Scheduling for Downlink and Uplink (LG Electronics)
R1-062573 Alternative Uplink Synchronous HARQ schemes (LG Electronics)
R1-062619 E-UTRA DL Distributed Multiplexing and Mapping Rules (Motorola)
R1-062707 Multiplexing Localized and Distributed Users in DL and UL of E-UTRA
(Qualcomm Europe)
R1-062735 Comparison between RB-level and Sub-carrier-level Distributed Transmission for
Shared Data Channel in E-UTRA Downlink (NTT DoCoMo, Ericsson, Fujitsu,
KDDI, Mitsubishi Electric, NEC, Nokia, Panasonic, Sharp, Toshiba Corporation)
R1-062736 RB-level Distributed Transmission Method for Shared Data Channel in E-UTRA
Downlink (NTT DoCoMo, Fujitsu, KDDI, Mitsubishi Electric, NEC,
Panasonic, Sharp, Toshiba Corporation)
R1-062863 Semi-persistent scheduling (Ericsson)
R1-062895 Some issues of VoIP transmission (Fujitsu)
R1-062900 Scheduling for VoIP (Siemens)
R1-062916 Baseline performance of reuse partitioning (IPWireless)

Withdrawn
R1-062894 UL radio resource use in mixed cells (Fujitsu)

6.11 Physical Layer specification aspects of Link Adaptation

All documents of this section were not treated due to lack of time
R1-062620 Benefits of sending two MCS to a user within a TTI (Motorola)
R1-062865 Physical Layer Aspects of Link Adaptation (Ericsson)

43
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

6.12 Specification of Control Signalling

6.12.1 Downlink Control Signalling
All documents of this section were not treated due to lack of time
R1-062499 E-UTRA Downlink L1/L2 Control Signalling design (Huawei)
R1-062500 Evaluation of E-UTRA Downlink L1/L2 Control Channel Multiplexing (FDM
vs TDM) (Huawei)
R1-062502 Partition Rule for Distributed Multiplexing in E-UTRA Downlink (ITRI)
R1-062532 Downlink Link Adaptation and Related Control Signaling (Samsung)
R1-062533 Downlink Hybrid ARQ Signaling (Samsung)
R1-062534 DL control channel structure: overview (Samsung)
R1-062535 Performance of DL L1/L2 control channel (Samsung)
R1-062536 Joint vs. Separate Coding for DL Control Signalling (Samsung)
R1-062542 Signaling Way of Resource Assignment (Mitsubishi Electric)
R1-062547 Downlink shared control signalling (ZTE)
R1-062574 Downlink control signaling (LG Electronics)
R1-062585 Signaling for downlink scheduling: separate vs. joint coding (ETRI)
R1-062618 Persistent Scheduling for E-UTRA VoIP and Control Channel considerations
(Motorola)
This document was revised before the presentation
R1-062981 Persistent Scheduling for E-UTRA VoIP and Control Channel considerations
(Motorola)
R1-062621 E-UTRA DL L1/L2 Control Channel Information fields & bit requirements
(Motorola)
R1-062622 E-UTRA DL L1/L2 Control Channel Non-Persistent Performance (Motorola)
This document was revised before the presentation.

R1-062982 E-UTRA DL L1/L2 Control Channel Non-Persistent Performance (Motorola)

R1-062623 E-UTRA DL L1/L2 Control Channel TDM vs. FDM (Motorola)
R1-062625 Downlink Acknowledgement and Group Transmit Indicator Channels
(Motorola)
R1-062652 Control Channel Structure and Coding in E-UTRA Downlink
(Texas Instruments)
R1-062653 Control Channel Coding for Uplink Scheduling in E-UTRA Downlink
(Texas Instruments)
R1-062654 Category 0 for the Control Channel in E-UTRA Downlink(Texas Instruments)
R1-062655 Link Level Control Channel Performance in E-UTRA Downlink
(Texas Instruments)
R1-062656 System Level Control Channel Performance in E-UTRA Downlink
(Texas Instruments)
R1-062657 Control Channel Multiplexing in E-UTRA Downlink (Texas Instruments)
R1-062663 Max #UEs/TTI for optimum E-UTRA DL performance (Motorola)
R1-062708 Structure and link analysis of DL control signalling (Qualcomm Europe)
R1-062737 Coding Scheme of L1/L2 Control Channel for E-UTRA Downlink (NTT
DoCoMo, Fujitsu, Mitsubishi Electric, NEC, Toshiba Corporation)
R1-062738 Multiplexing Method of Downlink L1/L2 Control Channel (NTT DoCoMo,
KDDI, Mitsubishi Electric, Sharp)
R1-062739 Persistent Scheduling in E-UTRA (NTT DoCoMo, NEC)
R1-062748 TDM vs FDM for Multiplexing of Downlink L1/L2 Control Signaling
(Nortel)

44
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062759 Detection Performance of TDM vs. FDM downlink control channels (Nortel)
R1-062760 Further discussion on adaptive fractional frequency reuse (Nortel)
R1-062771 Downlink ACK/NACK Mapping for E-UTRA (NEC Group)
R1-062779 Shorter UE ID for Downlink Scheduling Information (Sharp)
R1-062804 Phase Adjustment Methods of Rotational CDM for L1/L2 Control channel
(KDDI, NTT DoCoMo)
R1-062805 L1/L2 Control Channel Structure with CDM Based Multiplexing in E-UTRA
Downlink (KDDI, NTT DoCoMo)
R1-062806 Coding for Downlink L1/L2 Control Signaling (Panasonic)
R1-062807 Multiplexing of Downlink L1/L2 Control Channel with Data Channel
(Panasonic)
R1-062837 DL L1/L2 control signaling channel encoding structures (Nokia)
R1-062838 Short UE ID for DL L1/L2 control signaling (Nokia)
R1-062839 TDM vs. FDM Downlink Control Signaling (Nokia)
R1-062843 DL L1/L2 control signaling channel performance: Evaluation of grouped coding
(Nokia)
R1-062864 Scheduling Request in E-UTRAN (Ericsson)
R1-062866 Downlink control signalling (Ericsson)
R1-062898 L1 Control signalling (Siemens)
R1-062944 L1/L2 Control Channel Structure with CDM Based Multiplexing in E-UTRA
Downlink (KDDI, NTT DoCoMo)
R1-062945 Scrambling Code for L1/L2 Control Channel with CDM Based Multiplexing in E-
UTRA Downlink (KDDI)

Withdrawn
R1-062478 Impact of PRB size on Control Signalling (Alcatel)
R1-062624 DL L1/L2 Control Signaling for 15 and 20MHz carriers (Motorola)
R1-062802 L1/L2 Control Channel Structure with CDM Based Multiplexing in E-UTRA
Downlink (KDDI)
R1-062803 Scrambling Code for L1/L2 Control Channel with CDM Based Multiplexing in
E-UTRA Downlink (KDDI)
6.12.2 Uplink Control Signalling
R1-062874 Summary of email discussion on control signaling (Ericsson)
13/10/2006 15:05 Presented by Dr. Stefan Parkvall
Discussion (Question / Comment):
Farooq Khan (Samsung) commented that Samsung comments about non data associated control signaling were not
captured. It was clarified that it was due to late comments over deadline.
Decision: This document was noted.
At first stating discussion, the decision point was listed;
Non-data associated control signalling
- Transmission in absence of data
- Transmission in presence of data

Regarding the transmission in absence of data, as show in the document, R1-062874, this point already has consensus so
that it was agreed that working assumption is to use a reserved frequency.
On the other hand, regarding the transmission in presence of data, this point has not reached to consensus among
proponents so that the discussion for the agreement was continued.

R1-062538 Uplink ACK/NACK signaling in support of downlink Hybrid ARQ

(Samsung)
13/10/2006 15:20 Presented by Dr. Farooq Khan
Discussion (Question / Comment):

45
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Stefan Parkvall (Ericsson) commented that in the assumption in case of FDM structure ACK is allocated over TTI,
on the other hand, in case of the structure of TDM is one type. For the fair comparison between TDM and FDM
ACK can be allocated in other manner in the structure of TDM
It was long discussion on the different between FDM and TDM regarding CM and link budget, however the
understanding could not be consensus with each other parts.
It was commented that in case of FDM the modulation scheme is not single carrier scheme which was agreed for
UL in SI phase.
Decision: This document was noted.
R1-062740 Single-Carrier Based Multiplexing of Uplink L1/L2 Control Channel
(NTT DoCoMo, Ericsson, Fujitsu, Mitsubishi Electric, NEC,
Panasonic, Sharp, Toshiba Corporation)
13/10/2006 09:50 Presented by Dr. Kenichi Higuchi
Discussion (Question / Comment):
Samsung commented that in FDM case, frequency diversity effect seems to be low and asked if there are any
simulation results for coverage. The answer was that DoCoMo doesn't have any results but their view was that
assuming the same condition single carrier would be much coverage.
It was pointed out about the high impact on CM and the impact on scheduling and implementation rate matching of
FDM structure and the long discussion continued on the comparison of multi-carrier base and single-carrier based,
but the view and opinion of each part were crossing.
Decision: This document was noted.
After long discussion, Mr. Chairman commented that we need to decide the assumption and move to
next step for keep the time schedule, however there are different view on some pints between both
proponents. In fact at last December meeting, single-carrier scheme was agreed for UL so we should
choose single-carrier in UL at this time. Some companies commented that single carrier is a good reason
for the decision. On the other hand, Juho Lee (Samsung) raised a concern that they don't propose multi-
carrier but single carrier and issue is just how to convey control channel. In fact, we have not seen the
coverage issue and the corresponding data for TDD.
Finally, Mr. Chairman proposed the single structure scheme as working assumption from the view point
of transmission scheme and majority, and the proposal was agreed with the support and the consent by
Samsung. Juho Lee proposed that the other companies kindly provide the simulation results concerning
coverage for their convince although the scheme was decided and his proposal was accepted.
Conclusion
Non-data associated control signalling
- Transmission in absence of data
Working assumption is to use a reserved frequency.
- Transmission in presence of data
Two proposals:
- FDM of control data with SC-FDMA signal  multi-carrier FDMA signal (not in line
with the decision on UL transmission scheme)
- Multiplexing of control and data prior to DFT  single carrier FDMA signal
Working assumption is to use the multiplexing of control and data prior to DFT

Not treated due to lack of time

R1-062626 E-UTRA UL L1/L2 Control Channel Mapping (Motorola)
R1-062484 Control of CQI feedback signalling in E-UTRA (Philips, Intel)
R1-062537 Uplink data-associated control signalling (Samsung)
R1-062543 Comparison of CQI feedback schemes (Mitsubishi Electric)
R1-062575 Analysis on DCT based CQI reporting scheme (LG Electronics)
This document was revised before the presentation.
R1-062954 Analysis on DCT based CQI reporting scheme (LG Electronics)
R1-062627 UL L1/L2 Control Signaling for 15 and 20MHz carriers (Motorola)
R1-062658 ACK/NACK Transmission without a Reference Signal (Texas Instruments)
R1-062659 Reduced L1 identity for UL synchronized UE’s (Texas Instruments)
R1-062709 Structure and link analysis of UL control signalling (Qualcomm Europe)

46
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062741 Data-non-associated L1/L2 Control Channel Structure for E-UTRA Uplink

(NTT DoCoMo, Ericsson, Mitsubishi Electric, NEC,
Panasonic, Sharp, Toshiba Corporation)
R1-062742 CDM-based Multiplexing Method of Multiple ACK/NACK and CQI for E-UTRA
Uplink (NTT DoCoMo, Ericsson, Fujitsu, Mitsubishi
Electric, Sharp, Toshiba Corporation)
R1-062772 Compressed CQI Reporting Scheme (NEC Group)
R1-062773 Uplink Resource Allocation for E-UTRA (NEC Group, NTT DoCoMo)
R1-062808 Evaluation and Error Statistics for CQI Reporting Schemes (Panasonic)
R1-062809 E-UTRA Downlink System Level Performance with Compressed CQI Feedback
(Panasonic)
R1-062840 TDM based Multiplexing Schemes between L1/L2 Control and UL Data (Nokia)
R1-062841 Multiplexing of L1/L2 Control Signalling when UE has no data to transmit(Nokia)
R1-062842 CQI design and its impact of DL performance (Nokia)
R1-062867 Uplink non-data-associated control signaling (Ericsson)
R1-062868 Uplink non-data-associated control signaling – additional details (Ericsson)
R1-062869 Uplink data-associated control signaling (Ericsson)
R1-062917 Overhead for periodic and triggered CQI reporting (IPWireless)
This document was revised before the presentation.
R1-062962 Overhead for periodic and triggered CQI reporting (IPWireless)

Withdrawn
R1-062628 E-UTRA DL ACK/NACK and CQI Link performance and coverage
(Motorola)

6.13 Physical Layer Measurements

All Documents under this section were not treated due to lack of time

6.13.1 UE Measurements
R1-062870 Physical Layer Measurements - UE (Ericsson)
R1-062931 LTE UE measurements provided by the physical layer
(Lucent Technologies)

6.13.2 eNode B Measurements

R1-062871 Physical Layer Measurements - Node B (Ericsson)
R1-062930 eNodeB measurements provided by the physical layer
(Lucent Technologies)

6.14 Physical Layer UE Capability Aspects

All Documents under this section were not treated due to lack of time
R1-062539 Physical layer UE capability aspects of broadcast/unicast superposition
(Samsung)
R1-062710 UE Physical layer capability aspects for E-UTRA (Qualcomm Europe)
R1-062872 UE capabilities (Ericsson)

47
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

7. HSPA Evolution
The overview of conclusions on this topic is as followed.

1. MIMO in UTRA
a. Agreement on the following points as baseline for specifying the CQI signalling:
i. UE’s CQI report conveying information for dual stream CQI should be seen only to
apply in the case when both streams are allocated to UE. This would allow flexibility
in the development of advanced MIMO RX schemes.
ii. The SDMA operation is not prohibited from NodeB schedulers, but no specific
operation in terms of UE receiver capability or CQI reporting is assumed.
iii. No specific signalling for limited UE advanced RX schemes is introduced as it is not
seen necessary.
b. HSDPA MIMO UE categories was agreed in R1-062885
c. HS-SCCH for MIMO: Approach 1 was agreed and, performance to be verified together with
the decision on the exact signaling content and coding scheme.
i. Approach 1: Single HS-SCCH with part1/part2, two formats for part 2 selected
dynamically (based on information in part1), SF128
d. CQI reporting: R1-062996 was agreed as working assumption.
e. Way forward on up- and downlink signalling in support of Rel-7 FDD MIMO was agreed as
working assumption in R1-062997.
f. LS to the other RAN WGs to informed the RAN1 status was agreed in R1-063009.
2. Continuous Connectivity for Packet Data users
a. Set of CRs
i. CR to TS25 211 was agreed in R1-062986
ii. CR to TS25.212 was agreed in R1-063014
iii. CR to TS25.214 was agreed in principle in R1-063017 as a RAN1 baseline for further
corrections (if any) and clarifications.
iv. LS to the other RAN WGs to inform the RAN1 status was agreed in R1-063011

7.1 MIMO in UTRA (Rel-7 Work Item)

MIMO in UTRA was discussed on Wednesday.
R1-062675 Summary of Teleconference and email reflector activity on MIMO for Rel-7
(Qualcomm Europe)
Decision: This document was noted
R1-062677 Use of transmit diversity on F-DPCH when the UE is operating in MIMO mode
(Qualcomm Europe, Ericsson, Philips, Nokia)
Decision: This document was agreed.
R1-062679 Support of DPCH when operating in MIMO mode
(Qualcomm Europe, Ericsson, Philips)
Decision: This document was agreed.
R1-062678 Handling of preferred primary beam forming vector (Qualcomm Europe)
Decision: Points 1,2,4,5 agreed in principle. It is noted that UE feedback does not assume feedback error cases or
other deviations in the actual NodeB transmission from the assumptions under which the UE estimates the CQI.
R1-062888 Discussion on some CQI related issues (Nokia)
Decision: This document was noted.
Agreement on the following points as baseline for specifying the CQI signalling:
o UE’s CQI report conveying information for dual stream CQI should be seen only to apply in
the case when both streams are allocated to UE. This would allow flexibility in the
development of advanced MIMO RX schemes.
o The SDMA operation is not prohibited from NodeB schedulers, but no specific operation in
terms of UE receiver capability or CQI reporting is assumed.

48
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

o No specific signalling for limited UE advanced RX schemes is introduced as it is not seen

necessary.
R1-062885 HSDPA MIMO UE categories (Nokia, Ericsson, Qaulcomm)
Decision: This document was agreed. The indicated Rel5 category is one of the Rel5 15 codes categories.

Withdrawn
R1-062681 HSDPA MIMO UE categories (Qualcomm Europe)

7.1.1 Downlink Signalling Structure

R1-062485 Details of HS-SCCH signalling for Rel-7 MIMO (Philips)
Decision: This document was noted
R1-062876 HS-SCCH for Rel-7 MIMO (Ericsson, Philips, Qualcomm Europe)
Decision: This document was noted
R1-062877 New MIMO DL signaling (Ericsson)
Decision: This document was noted. Can be discussed further and if agreeable within the Rel7 timeframe, can be
considered in the Rel7 MIMO package.
R1-062886 HS-SCCH for MIMO in UTRA (Nokia)
Decision: This document was noted
R1-062909 WCDMA MIMO Downlink Signaling (Motorola)
Decision: This document was noted.

Two approaches for the HS-SCCH for MIMO:

1. Single HS-SCCH with part1/part2, two formats for part 2 selected dynamically (based on information
in part1), SF128
(Philips, Ericsson, Qualcomm, Nortel, Samsung)
2. Two HS-SCCH with part1/part2 and same coding chain as in Rel6 (+ awi, hap), second HS-SCCH
transmitted only when two streams are transmitted
(Nokia, Motorola)
Agreed way forward: Agreement on approach 1, performance to be verified together with the decision on
the exact signaling content and coding scheme.

Withdrawn
R1-062682 HS-SCCH signalling for MIMO (Qualcomm Europe)

7.1.2 Uplink Signalling Structure

R1-062676 L1 uplink control information in support of MIMO (Qualcomm Europe)
Decision: This document was noted.
R1-062680 CQI reporting for Rel-7 FDD MIMO
(Philips, Qualcomm Europe, Nokia, Ericsson)
Decision: This document was noted. Revise the proposal offline and present it again, once agreement is reached.
R1-062996 CQI reporting for Rel-7 FDD MIMO (Qualcomm
Europe, Nokia, Philips, Ericsson, Cingular Wireless, T-Mobile, Nortel)
13/10/2006 11:50 Presented by Dr. Josef Blanz
Discussion (Question / Comment):
Decision: This was agreed as working assumption.

R1-062878 Feedback of antenna weight information for D-TxAA (Ericsson)

Decision: This document was noted.
R1-062879 Coding for ACK/NACK in MIMO operation (Ericsson)
Decision: This document was noted.

49
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062887 Performance of Different Feedback Weight Optimization Strategies and

Impact on the FBI Signalling (Nokia)
Decision: This document was noted.
R1-062910 WCDMA MIMO Uplink Signaling (Motorola)
Decision: This document was noted.

Antenna weights:
Approach 1: antenna weight indication on HS-DPCCH, i.e. all MIMO information contained in one
feedback channel
Ericsson, Qualcomm, Nortel, Philips
Approach 2: antenna weight indication on DPCCH (using FBI reporting mechanism of Rel99-Rel6)
Nokia, Motorola
Continue discussion offline, and let the chair know if agreement is reached.

Draft LS should be prepared to other WGs to inform them about the conclusions taken on MIMO so far
(Qualcomm).
Prepare set of draft CRs for L1 specifications for November meeting.
R1-062995 Draft LS on status of Rel-7 FDM MIMO
(Qualcomm Europe, Philips, Nokia, Ericsson)
13/10/2006 09:55 Presented by Dr. Josef Blanz
Discussion (Question / Comment):
Hidetoshi Suzuki commented regarding the text "Non-MIMO category of MIMO UEs will be signalled
independently using the existing signalling mechanism" the existing signalling mechanism could be used to Rel-6
RRC so that it had better to be removed.
Decision: This draft LS was approved with modification in R1-063009
R1-062997 Proposed way forward on up- and downlink signalling in support of Rel-7 FDD
MIMO (Qualcomm Europe, Nokia, Philips, Ericsson, Cingular
Wireless, T-Mobile, Nortel)
13/10/2006 11:50 Presented by Dr. Josef Blanz
Discussion (Question / Comment):
Decision: This was agreed as working assumption.

Withdrawn
R1-062683 ACK/NACK encoding for MIMO (Qualcomm Europe)

7.1.3 4x2 MIMO Configuration

No input

7.2 Continuous Connectivity for Packet Data Users

Continuous Connectivity for Packet Data users was discussed on Wednesday.

R1-062486 25.211 CR0230 (Rel-7, B) "UL DPCCH slot format"

(Philips, Qualcomm Europe, Siemens, Ericsson, Nokia)
Decision: CR agreed in principle, revision should be made to take effect of gating on transmitted slots into account.
R1-062986 25.211 CR0230r1 (Rel-7, B) "UL DPCCH slot format"
(Philips, Qualcomm Europe, Siemens, Ericsson, Nokia)
13/10/2006 12:40 Presented by Mr. .Juan Montjo
Discussion (Question / Comment):
As the procedure of CR agreement, Evelyne Le Strat commented that CRs should be agreed as the set of CRs so the
agreement of this CR should be postpone to the next meeting considering the other CRs for TS25.212 and 25.214
might block the agreement of 25.211 CR.
Decision: This CR was agreed conditionally that the other two CRs are agreed as well.

50
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

R1-062505 25.212 CR0238r1 (Rel-7, B) "Support of CPC feature"

(Qualcomm, Nokia, Ericsson, Siemens)
R1-062978 25.212 CR0238r2 (Rel-7, B) "Support of CPC feature"
(Qualcomm, Nokia, Ericsson, Siemens)
Decision: CR agreed in principle, revision should be made to reflect the comments made (QPSK, editorial, …)
R1-062987 25.212 CR0238r3 (Rel-7, B) "Support of CPC feature"
(Qualcomm, Nokia, Ericsson, Siemens)
13/10/2006 12:55 Presented by Mr. .Juan Montojo
Discussion (Question / Comment):
Decision: This CR was agreed in principle pending comments to be reflected on a revision for email approval until
20 October. After the e-mail discussion, this was revised in R1-063014.
R1-063014 25.212 CR0238r4 (Rel-7, B) "Support of CPC feature"
(Qualcomm, Nokia, Ericsson, Siemens, Philips)
Decision: This version was agreed.

R1-062506 25.214 CR0421r1 (Rel-7, B) "Support of CPC feature"

(Qualcomm, Nokia, Ericsson, Siemens)
R1-062968 25.214 CR0421r2 (Rel-7, B) "Support of CPC feature"
(Qualcomm, Nokia, Ericsson, Siemens)
Decision: Reason for HS-SCCH orders (agreed for drx in Tallinn meeting): for robustness to disable drx in fully
loaded situations, to quickly disable the CPC feature in handover situations. CR agreed in principle, revision should
be made to reflect the editorial comments
R1-062988 25.214 CR0421r3 (Rel-7, B) "Support of CPC feature"
(Qualcomm, Nokia, Ericsson, Siemens, LG Electronics, Nortel, Huawei)
13/10/2006 13:00 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Decision: This CR was agreed in principle pending comments to be reflected in a revision for email approval until
27 October. After the e-mail discussion, this was revised in R1-063016.
R1-063016 25.214 CR0421r4 (Rel-7, B) "Support of CPC feature"
(Qualcomm, Nokia, Ericsson, Siemens, Philips)
Decision: This version was agreed as a RAN1 baseline for further corrections (if any) and clarifications. After the
agreement, it was clear that Nortel was not listed on co-sign companies on the CR cover page even though they
indicated on the e-mail reflector that they are willing to co-sign this CR. Therefore this version was revised with
addition of Nortel in co-sign companies in R1-063017.
R1-063017 25.214 CR0421r5 (Rel-7, B) "Support of CPC feature"
(Qualcomm, Nokia, Ericsson, Siemens, Philips, Nokia)
Decision: This version was considered as the final agreed version.

Way forward: Revised set of CRs to be agreed by RAN1 this week, then send and LS to other WGs
informing about the state of conclusions.
R1-062989 DRAFT LS on status of RAN1 CRs for "Continuous connectivity for packet
data users" (Siemens)
13/10/2006 13:05 Presented by Dr. Joern Krause
Discussion (Question / Comment):
Decision: This draft LS was approved with modification in R1-063011.

Not covered by the CRs

R1-062892 Compressed mode with CPC (Nokia)
Decision: This document was noted. Problem is recognised, and impact on RAN4 specs shall be avoided, discuss
and agree a solution over email reflector until 20 October.

R1-062934 Length of the Periodic UL DPCCH Burst (Ericsson)

51
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Decision: This document was noted. Proposal is to start the DPCCH burst at known times. Discuss and agree a
solution over email reflector until 20 October.

Not treated due to lack of time

R1-062889 Link results for UL DPCCH gating with different PC step sizes during DPCCH
only transmissions (Nokia)
R1-062927 Lower Layer Signalling for Continuous Packet Connectivity
(Lucent Technologies)
R1-062668 Complexity and buffering requirements for reduced complexity HS-SCCH-less
Operation (Qualcomm Europe)
R1-062774 Further clarification for HS-SCCH less feature (NEC Group)
R1-062667 Further DL VoIP capacity analysis (Qualcomm Europe)
Covered by the CRs
R1-062881 Proposed modification to align UL DPCCH gating patterns for 2ms and 10 ms
TTI (Nortel)
R1-062890 Link results for UL DPCCH transmission burst length in case of 10ms TTI
(Nokia)
R1-062891 Downlink synchronisation primitives and uplink power control out-of-
synchronisation handling in case of discontinuous uplink transmission
(Nokia)

7.3 Scope of future FDD HSPA Evolution

FDD HSPA + was discussed on Thursday evening.

R1-062674 Link analysis of 16QAM for E-DPDCH (Qualcomm Europe)

12/10/2006 18:40 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
It was notified that between 8PSK and 16QAM there are trade between CM and data rate. It was asked if there are
Decision: This document was noted.
R1-062936 16QAM for HSUPA - Cubic Metric (Ericsson)
This document was revised before the presentation.
R1-062950 16QAM for HSUPA - Cubic Metric (Ericsson)
12/10/2006 18:45 Presented by Dr. Lars Lindbom
Discussion (Question / Comment):
It was asked how RAN1take a decision the parameter such as CM and power back off with relation to RAN4. In
fact some point should be by RAN1 and the other point should be by RAN4. Regarding CM, we already discussed
with RAN4, but if some extend is need in study in HAPA +, RAN1 will take.
It was pointed out that 16QAM impact on RAN4 specification, power accuracy.
Decision: This document was noted.
R1-062939 16QAM for HSUPA - Impact of Power Back-Off (Ericsson)
12/10/2006 19:00 Presented by Dr. Lars Lindbom
Discussion (Question / Comment):
It was clarified that perfect channel estimation, type 3 receiver was assumed in simulation evaluation.
Decision: This document was noted.
R1-062469 Implementation Aspects of 16-QAM for HSPA Uplink (Motorola)
12/10/2006 19:15 Presented by Dr. Qiang Guo
Discussion (Question / Comment):
Decision: This document was noted.
R1-062470 Further Observations on 64-QAM for HSPA Downlink (Motorola)
12/10/2006 09:30 Presented by Dr. Raja Bachu
Discussion (Question / Comment):
It was informed that the additional assumption of simulation such as channel estimation can be found in the
document at last meeting.

52
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

It was asked if we have not agreed the interference reduction scheme is not agreed so that how it is implemented in
simulation.
Decision: This document was noted.
R1-062937 64QAM for HSDPA - Impact of Cell Isolation (Ericsson)
12/10/2006 19:50 Presented by Mr. Johan Bergman
Discussion (Question / Comment):
It was asked if there are the results for any other tilt. Johan answered that there aren't any results for that, however,
considered tilt in this contribution could be more realistic.
It was asked if the 64 QAM can be also expected to micro cell. It was clarified that in close to BS 64 QAM but
large cell case, order will be less than 64QAM, may be 16QAM.
Decision: This document was noted.
R1-062938 64QAM for HSDPA - Impact of Power Back-Off (Ericsson)
12/10/2006 20:10 Presented by Mr. Johan Bergman
Discussion (Question / Comment):
It was clarified by Ericsson that in simulation, the perfect channel knowledge, ideal type 3 receiver are assumed.
Motorola raised a wonder how the achievable data rate is configurable.
Decision: This document was noted.
R1-062935 Higher Order Modulation for HSPA – Impact on RAN1 specifications
(Ericsson)
12/10/2006 20:25 Presented by Mr. Johan Bergman
Discussion (Question / Comment):
Evelyne Le Strat commented that high bit rate has impact also in Iu interface, RANAP.
Decision: This document was noted.
Regarding higher order modulation scheme for HSPA +Further contributions invited with results,
conclude at next meeting (end of SI)

R1-062669 Improvements on E-DPCCH for HSPA (Qualcomm Europe)

Decision: This document was noted without presentation
R1-062670 Improved E-DPCCH coding (Qualcomm Europe)
12/10/2006 20:30 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Decision: This document was noted.
R1-062671 Improved E-DPCCH power setting as a function of the Handoff state
(Qualcomm Europe)
12/10/2006 20:40 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Decision: This document was noted.
R1-062672 F-DPCH time alignment (Qualcomm Europe)
12/10/2006 21:00 Presented by Mr. Juan Montojo
Discussion (Question / Comment):
Motorola, Nokia and Nortel commented that this proposal is very good. It was commented that combining aspects
may be also changed in 25.214.
Decision: This document was noted.
R1-062673 Monitoring of HSUPA grant channels (Qualcomm Europe)
12/10/2006 21:15 Presented by Mr. Serge Willeneger
Discussion (Question / Comment):
Nokia commented that we don't need to worry about additional signaling and it's a good approach and 2005
Evelyne Le Strat commented that this topic should be discussed in RAN2 and this is resubmission of CPC
document at the last meeting and asked more discussion on the e-mail. Serge clarified that this submission is for
acknowledgement in RAN1 and in fact it is under MAC and RRC aspects.
Decision: This document was noted.
Discuss this on the email reflector as part of the CPC discussion (to be concluded 20 Oct).

R1-062666 Further Results on VoIP Enhancements for HSPA Evolution(InterDigital)

12/10/2006 21:40 Presented by Mr. Eldad Zeira
Discussion (Question / Comment):
Karri Ranta-aho commented that as same as Tallinn meeting, what was done in simulation and what the BS do. It
was suggested that the proponent shall provide what kind of change is needed in specification. It was clarified that
this scheme has impact on DL capacity or signalling.

53
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Decision: This document was noted.

Withdrawn
R1-062468 Observations on MBMS Enhancement via Synchronization (Motorola)

54
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

8. 1.28Mcps TDD Enhanced Uplink

The overview of conclusions on this topic is as followed.

1. TR25.827 was endorsed as v0.2.0 in R1-062991

2. Three text proposals to TR25.827 were agreed.

R1-062797 TR25.827v0.1.1 (Editor, CATT)

13/10/2006 08:10 Presented by Mr. Ke Wang
Discussion (Question / Comment):
Decision: This document was endorsed as v0.2.0 in R1-062991.
R1-062991 TR25.827v0.2.0 (Editor, CATT)

R1-062587 Non-Scheduled Traffic and Scheduled Traffic Transmissions (ZTE)

This document was revised before the presentation
R1-062969 Non-Scheduled Traffic and Scheduled Traffic Transmissions (ZTE)
13/10/2006 08:15 Presented by Ms. Chen Hui
Discussion (Question / Comment):
Conclusion some problem on second part of text proposal from TD -Tech.
Decision: The text proposal was agreed with revision of wording in R1-062992
R1-062992 TP on Non-Scheduled Traffic and Scheduled Traffic Transmissions (ZTE)

R1-062588 20ms TTI Co-existence with 5ms TTI for E-DCH of LCR TDD: System Level
Simulation Results (ZTE)
This document was revised before the presentation
R1-062970 20ms TTI Co-existence with 5ms TTI for E-DCH of LCR TDD: System Level
Simulation Results (ZTE)
13/10/2006 08:25 Presented by Ms. Chen Hui
Discussion (Question / Comment):
The concern was raised on the simulation results by CATT.
Decision: This document was noted and it was decided to reconfirm results with other simulations until next
meeting.
R1-062798 Performance of E-UCCH for 1.28Mcps E-DCH (CATT)
13/10/2006 08:30 Presented by Ms. Xueyuan Gao
Discussion (Question / Comment):

Decision: This document was noted and it was decided to continue discussion on the e-mail reflector and reach
agreement before the next meeting.
R1-062799 LCR TDD: Physical channel structure for E-PUCH (CATT)
R1-062971 LCR TDD: Physical channel structure for E-PUCH (CATT)
13/10/2006 08:40 Presented by Ms. Xueyuan Gao
Discussion (Question / Comment):
TD-Tech commented that text proposal should be revisited after the agreement of E-UCCH and suggesting
including 20ms TTI.
Decision: This document was noted and it was decided to revisit the proposal after the E-UCCH is agreed and
include 20ms TTI if it is agreed.
R1-062800 HARQ timing aspects for 1.28Mcps TDD Enhanced Uplink (CATT)
13/10/2006 08:50 Presented by Mr. Ke Wang.
Discussion (Question / Comment):
It was raised a concern on UE definition considering 20ms TTI from TD-Tech.
Decision: The text proposal was agreed wrt 5ms baseline and if 20ms is agreed, this text should be revised in the
TR.
R1-062801 Power control for 1.28Mcps TDD Enhanced Uplink (CATT)
13/10/2006 08:55 Presented by Mr. Ke Wang.
Discussion (Question / Comment):
It was concerned by TD-Tech on the power control part (E-RUCCH part is fine).

55
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Decision: The text proposal was agreed conditionally if simulation results indicate the need for further
modifications, theses can be decided in November meeting.
R1-063000, Draft LS to RAN2 to inform about conclusion in R1-062992 to be agreed over email until October 20
R1-063000 Draft LS on non-Scheduled Traffic and Scheduled Traffic Transmissions
(ZTE)
Decision: This draft LS was approved with modification in R1-063015 on the RAN1 reflector after the meeting.

56
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

9. Closing of the meeting

13/10/2006 17: 00. RAN1 Chairman, Mr. Dirk Gerstenberger expressed his appreciation to the delegates and the host,
Samsung for their supports. Towards the next meeting, he suggested e-mail discussion for reaching to consensus in the
next meeting and confirmed again about conference call for MIMO LTE. As new topic on e-mail discussion, Nokia was
designated as the moderator for e-mail discussion on power control. In addition, as for agenda item for the next meeting,
Mr. Chairman commented that we are in line with Workplan and it would be more similar agenda as this meeting and one
new is we would start discussion about rate matching and interleaving topics. And then the meeting was closed.

57
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Annex A: List of participants at RAN1 #46bis

Ctr
Name Representing Status-Partner y Ph Email
Dr. Abeta, Sadayuki NTT DoCoMo Inc. 3GPPMEMBER (ARIB) JP +81-468-40-3470 abeta@mlab.yrp.nttdocomo.co.jp
Dr. Ahn, Joon-Kui LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-4131 jkan@lge.com
Mr. Akita, Hidenori MOTOROLA Ltd 3GPPMEMBER (ETSI) GB +81 3 5424 3031 hidenori.akita@motorola.com
Mr. Anderson, Nicholas IPWireless Inc. 3GPPMEMBER (ETSI) GB +44 1249 800020 nanderson@ipwireless.com
Mr. Asanuma, Yutaka Toshiba Corporation 3GPPMEMBER (ARIB) JP +81-428-34-4273 ytk.asanuma@toshiba.co.jp
Mr. Awad, Yassin Telecom Modus Ltd. 3GPPMEMBER (ETSI) GB +44 (0) 1372381849 yassin.awad@t-modus.nec.co.uk
Dr. Bachl, Rainer Lucent Technologies N. S. UK 3GPPMEMBER (ETSI) DE +49 911 526 2656 rbachl@lucent.com
Mr. Barreto, Luis NOKIA UK Ltd 3GPPMEMBER (ETSI) GB +44 1252867618 luis.barreto@nokia.com
Dr. Berggren Fredrik HUAWEI TECHNOLOGIES Co. Ltd. 3GPPMEMBER (ETSI) CN +46 8 4770808 fredrik.b@huawei.com
Mr. Bergman, Johan Nanjing Ericsson Panda Com Ltd 3GPPMEMBER (CCSA) SE +46 8 594 36 849 johan.bergman@ericsson.com
Mr. Bertrand, Pierre TEXAS Instruments 3GPPMEMBER (ETSI) FR +33 (0)4 93 22 23 92 p-bertrand@ti.com
Dr. Blanz, Josef Qualcomm Korea 3GPPMEMBER (TTA) DE +49 6322 954572 jblanz@qualcomm.com
Ms. Boumendil, Sarah NORTEL NETWORKS (EUROPE) 3GPPMEMBER (ETSI) FR +33 1 39 44 58 16 boumendi@nortel.com
Dr. Brunel, Loïc Mitsubishi Elec Info Tech Eur 3GPPMEMBER (ETSI) JP +33 2 23 45 58 58 brunel@tcl.ite.mee.com
Mr. Bui, Thanh NEC Corporation 3GPPMEMBER (ARIB) AU +61 3 9271 4027 thanhb@icpdd.neca.nec.com.au
Mr. Buracchini, Enrico TELECOM ITALIA S.p.A. 3GPPMEMBER (ETSI) IT +39 011 2287118 Enrico.Buracchini@telecomitalia.it
Mr. Callard, Aaron Nortel Networks 3GPPMEMBER (ATIS) US +1 613 763 8694 aaronca@nortel.com
Mr. Chai, Kangsuk LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-2-3777-5090 kschai@lge.com
Mr. Chander, Sharat Cingular Wireless LLC 3GPPMEMBER (ATIS) US +1 425 580 6596 sharat.chander@cingular.com
Mr. Che, Xiangguang NOKIA Corporation 3GPPMEMBER (ETSI) FI +8613910218830 xiangguang.che@nokia.com
Miss Chen, Hui ZTE Corporation 3GPPMEMBER (CCSA) CN +86-21-68895889 chen.hui2@zte.com.cn
Dr. Cheng, Tai-yuan ITRI 3GPPMEMBER (ETSI) TW +886-3-5914704 tycheng@itri.org.tw
Mr. Chiu, Robinson c.-s. CHTTL 3GPPMEMBER (ETSI) TW +886-3-4244436 robinson@cht.com.tw
Mr. Chmiel, Mieszko SIEMENS S.p.A 3GPPMEMBER (ETSI) DE +48(71)7992847 mieszko.chmiel@siemens.com
Dr. Cho, Joonyoung Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) KR +82 31 279 5881 joonyoung.cho@samsung.com
Mr. Choi, Hyung-Nam INFINEON TECHNOLOGIES 3GPPMEMBER (ETSI) DE +49-5341-9061812 Hyung-Nam.Choi@infineon.com
Mr. Classon, Brian MOTOROLA Ltd 3GPPMEMBER (ETSI) US +18475765675 Brian.Classon@motorola.com
Dr. Czerepinski, Przemyslaw Siemens nv/sa 3GPPMEMBER (ETSI) BE + przemek.czerepinski@roke.co.uk
Dr. Dahlman, Erik ERICSSON LM 3GPPMEMBER (ETSI) SE +46 8 764 13 77 erik.dahlman@ericsson.com
Mr. Ding, Yinong Samsung Telecommunications 3GPPMEMBER (ATIS) KR +19727617975 y.ding@samsung.com
Mr. Fabien, Jean-Aicard MOTOROLA S.A.S 3GPPMEMBER (ETSI) US +1 847 523 7610 jean-aicard.fabien@motorola.com

58
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
Mr. Favichia, Frank Lucent Technologies 3GPPMEMBER (ATIS) US +1 973 3867 326 f2@lucent.com
Mr. Feuillette, Remi LG Electronics Mobilecomm 3GPPMEMBER (ETSI) FR +33 1 41 59 93 04 rfeuillette@lge.com
Mr. Frost, Tim VODAFONE Group Plc 3GPPMEMBER (ETSI) GB +44 774893885 tim.frost@vodafone.com
Mr. Fukui, Noriyuki Mitsubishi Electric Co. 3GPPMEMBER (ARIB) JP +81 467 41 2885 fukui.noriyuki@df.mitsubishielectric.co.jp
3GPPMARK_REP
Mrs. Gao, Xueyuan TD-SCDMA Forum (OTHER) CN +861058832151 gaoxueyuan@datangmobile.cn
Dr. Gerlach, Christian G. ALCATEL S.A. 3GPPMEMBER (ETSI) DE +49.711.821-32200 christian.gerlach@alcatel.de
Dr. Gerlach, Heino ROHDE & SCHWARZ 3GPPMEMBER (ETSI) DE +49 89 4129 12517 heino.gerlach@rsd.rohde-schwarz.com
Mr. Gerstenberger, Dirk ERICSSON LM 3GPPMEMBER (ETSI) SE +46 8 585 33901 dirk.gerstenberger@ERICSSON.COM
Dr. Ghosh, Amitabha MOTOROLA GmbH 3GPPMEMBER (ETSI) DE +18476324121 qa0047@email.mot.com
Mr. Golitschek edler von elbwart,
Alexander PANASONIC R&D Center Germany 3GPPMEMBER (ETSI) DE +49 6103 766 163 alexander.golitschek@eu.panasonic.com
Dr. Göransson, Bo Ericsson Inc. 3GPPMEMBER (ATIS) SE +46 8 7570703 bo.goransson@ericsson.com
Mr. Grieco, Donald INTERDIGITAL COMMUNICATIONS 3GPPMEMBER (ETSI) US +1 631 622 4102 donald.grieco@interdigital.com
Mr. Grøvlen, Asbjørn NOKIA UK Ltd 3GPPMEMBER (ETSI) FI +358 405642489 asbjorn.grovlen@nokia.com
Dr. Guo, Qiang MOTOROLA Ltd 3GPPMEMBER (ETSI) US +1 847 523 3217 qiangguo@motorola.com
Mr. Han, Seung hee LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-1852 dondai@lge.com
Mr. Harrison, Mark Motorola Broadband Com. Sector 3GPPMEMBER (ETSI) US 18 475 233 217 mark.harrison@motorola.com
Ms. Heo, Youn SAMSUNG Electronics Co. 3GPPMEMBER (ARIB) JP +82-279-5362 hushhuk@korea.com
Dr. Higuchi, Kenichi NTT DoCoMo Inc. 3GPPMEMBER (ARIB) JP +81-46-840-3470 higuchi@mlab.yrp.nttdocomo.co.jp
Mr. Hiramatsu, Katsuhiko Matsushita Electric Industrial 3GPPMEMBER (ARIB) JP +81 46 840 5422 hiramatsu.katsuhiko@jp.panasonic.com
Mr. Holt, Keith INTEL CORPORATION SAS 3GPPMEMBER (ETSI) FR +1 916 356-5279 keith.holt@intel.com
Mr. Hoshino, Masayuki Matsushita Electric Industrial 3GPPMEMBER (ARIB) JP +81 46 840 5435 hoshino.masayuki@jp.panasonic.com
Mr. Iizuka, Yosuke NTT DoCoMo Inc. 3GPPMEMBER (TTC) JP +81 468 40 3100 iizuka@cet.yrp.nttdocomo.co.jp
Mr. Imamura, Daichi Matsushita Electric Industrial 3GPPMEMBER (ARIB) JP +81.46.840.5631 imamura.daichi@jp.panasonic.com
Mr. Imamura, Kimihiko SHARP Corporation 3GPPMEMBER (ARIB) JP +81-43-299-8562 imamura.kimihiko@sharp.co.jp
Mr. Ishii, Yoshikazu ETSI Secretariat 3GPPORG_REP (ETSI) FR +33 4 92 94 42 06 yoshikazu.Ishii@etsi.org
Miss Jeong, Joon ho LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-2-3777-5777 jhjeong@lge.com
Mr. Jonsson, Elias Nippon Ericsson K.K. 3GPPMEMBER (ARIB) SE +46 46 23 15 75 elias.jonsson@ericsson.com
Mr. Jung, Injae LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-7897 goldeninjae@lge.com
Mr. Jung, Jea Hoon LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-9903  
Mr. Kakura, Yoshikazu NEC Corporation 3GPPMEMBER (ARIB) JP +81 44 396 2592 y-kakura@cb.jp.nec.com
Dr. Kalluri, Sudhakar INTEL CORPORATION SAS 3GPPMEMBER (ETSI) FR +1-916-356-6321 sudhakar.kalluri@intel.com
Mr. Katsuragawa, Hiroshi SHARP Corporation 3GPPMEMBER (ARIB) JP +81-43-299-8265 katsuragawa.hiroshi@sharp.co.jp
Mr. Kawasaki, Yoshihiro Fujitsu Limited 3GPPMEMBER (ARIB) JP + yosihiro@labs.fujitsu.com
Mr. Kent Mark BROADCOM CORPORATION 3GPPMEMBER (ETSI) US 18 585 215 853 mkent@broadcom.com
Dr. Khan, Farooq Samsung Telecommunications 3GPPMEMBER (ATIS) US +1 972 762 7929 fkhan@sta.samsung.com
Dr. Kim, Byoung-hoon Flarion Technologies 3GPPMEMBER (ETSI) US +1 858 658 2127 byoungk@qualcomm.com
Mr. KIM, Youngbum SAMSUNG ELECTRONICS CO. LTD 3GPPMEMBER (ARIB) KR 82 31 279 5092 youngbum.kim@samsung.com

59
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
Mr. Kim, Donghan Pantech&Curitel Communications 3GPPMEMBER (TTA) KR +82-2-2030-1614 kim.donghan@pantech.com
Ms. Kim, Eun sun LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-7858 esunkim@lge.com
Mr. Kim, Hak-Seong LG Electronics Inc. 3GPPMEMBER (TTA) KR +82 31 450 4127 bryankim@lge.com
Dr. Kim, Joel INTEL CORPORATION SAS 3GPPMEMBER (ETSI) FR +1-408-653-9599 joel.kim@intel.com
Dr. Kim, Ki jun LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-7316 kjun@lge.com
Mr. Kishiyama, Yoshihisa NTT DoCoMo Inc. 3GPPMEMBER (ARIB) JP +81-46-840-3470 kishi@mlab.yrp.nttdocomo.co.jp
Dr. Kotecha, Jayesh Freescale Semiconductors 3GPPMEMBER (ETSI) US +1-512-996-7454 jayeshkotecha@freescale.com
Dr. Krause, Joern Siemens Networks GmbH & Co. KG 3GPPMEMBER (ETSI) DE +49-30-386-23417 joern.krause@siemens.com
Mr. Kurose, Kengo Toshiba Corporation 3GPPMEMBER (ARIB) JP +81428344354 kengo.kurose@toshiba.co.jp
Mr. Kwak, Yongjun SAMSUNG Electronics 3GPPMEMBER (ETSI) KR +82 31 279 5112 evatt@samsung.com
Dr. Kwon, Hyuck-chan Nortel Networks 3GPPMEMBER (ATIS) US +82-31-450-7324 durer@lg-nortel.com
Ms. Le Strat, Evelyne Nortel Networks 3GPPMEMBER (ATIS) FR +33139445339 elestrat@nortel.com
Mr. Lee, Daewon LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-7858 cents@lge.com
Dr. Lee, Juho Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) KR +82-31-279-5115 juho95.lee@samsung.com
Ms. Lee, Jung a. Lucent Technologies N. S. UK 3GPPMEMBER (ETSI) US +1 973 386 3280 jalee@lucent.com
Mr. Lee, Jung Hoon LG Electronics Inc. 3GPPMEMBER (TTA) KR +82.31.450.2931 jh_lee@lge.com
Mr. Lee, Jungseung Nortel Networks 3GPPMEMBER (ATIS) US +82314507324 jeslee@lg-nortel.com
Mr. Lee, Moonil LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-7903 emoon1@lge.com
Mr. Li, Jun Nortel Networks 3GPPMEMBER (ATIS) US + 972 684 3775 junli@nortel.com
Dr. Li, Richard c.-f. ITRI 3GPPMEMBER (ETSI) TW +886-3-591-7596 richard929@itri.org.tw
Dr. Lindbom, Lars ERICSSON LM 3GPPMEMBER (ETSI) SE +46 8 757 16 63 lars.lindbom@ericsson.com
Mr. Lindh, Lars NOKIA Corporation 3GPPMEMBER (ETSI) FI +358 9 43761 lars.e.lindh@nokia.com
Mr. Lindholm, Jari Nokia Japan Co, Ltd 3GPPMEMBER (ARIB) FI +358 7180 66762 jari.o.lindholm@nokia.com
Mr. Liu, Jianghua HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) CN +8682882650 jianghua811@huawei.com
Mr. Love, Robert MOTOROLA GmbH 3GPPMEMBER (ETSI) DE +18475233702 qa2178@email.mot.com
Dr. Lozano, Angel Lucent Technologies 3GPPMEMBER (ATIS) US +1 732 8887160 aloz@lucent.com
Dr. Lu, Feng ARIB 3GPPORG_REP (ARIB) JP +81468476350 lu@kddilabs.jp
Mr. Lunttila, Timo NOKIA Corporation 3GPPMEMBER (ETSI) FI +358504821552 timo.lunttila@nokia.com
Dr. Luo, Ping Matsushita Electric Industrial 3GPPMEMBER (ARIB) JP +65-65505320 ping.luo@sg.panasonic.com
Miss Ma, Jianglei Nortel Networks 3GPPMEMBER (ATIS) US +1-613-7651853 jianglei@nortel.com
Mr. Mai Huiheng IPWireless Inc. 3GPPMEMBER (ETSI) UK +44 1249 800069 hmai@ipwireless.com
Dr. Mccoy, Wes Freescale Semiconductors 3GPPMEMBER (ETSI) US +1 512 996 7627 wes.mccoy@freescale.com
Dr. Mehta, Neelesh Mitsubishi Electric Co. 3GPPMEMBER (ARIB) JP +16176217597 mehta@merl.com
Miss Mo, Ronghong Matsushita Electric Industrial 3GPPMEMBER (ARIB) JP +65 65505328 RongHong.Mo@sg.panasonic.com
Mr. Montojo, Juan Qualcomm Japan Inc 3GPPMEMBER (ARIB) JP +1 858-651-2426 juanm@qualcomm.com
Dr. Moon, Hichan Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) KR +82-31-279-5351 hchan.moon@samsung.com
Dr. Moulsley, Tim Philips International B.V. 3GPPMEMBER (ETSI) GB +44 1293 815 717 tim.moulsley@philips.com
Mr. Murphy, Mark TTP Communications plc 3GPPMEMBER (ETSI) GB +44 1763 266266 mark.murphy@ttpcom.com

60
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
Mr. Murias, Ron INTERDIGITAL COMMUNICATIONS 3GPPMEMBER (ETSI) US +1 403 889 1200 ron@murias.ca
Dr. Ng, Man Hung Lucent Technologies N. S. UK 3GPPMEMBER (ETSI) GB +44 1793 897312 ngm@lucent.com
Dr. Nicolas, Julien TEXAS Instruments 3GPPMEMBER (ETSI) FR +1-858-404-6429 jnicolas@ti.com
Dr. Nie, Junhong TEXAS Instruments 3GPPMEMBER (ETSI) JP +1-858-693-4450 jnie@ti.com
Mr. Nishio, Akihiko Panasonic (PMCDE) 3GPPMEMBER (ETSI) JP +81 46 840 5694 nishio.akihiko@jp.panasonic.com
Mr. Ogana, Shinsuke NTT DoCoMo Inc. 3GPPMEMBER (TTC) JP +81 468 40 3530  
Mr. Ojala, Jussi NOKIA Corporation 3GPPMEMBER (ETSI) FI +358504836248 Jussi.Ojala@nokia.com
Mr. Onggosanusi, Eko TEXAS Instruments 3GPPMEMBER (ETSI) FR +1 214 480 1809 eko@ti.com
Dr. Papasakellariou, Aris Texas Instruments Deutschland 3GPPMEMBER (ETSI) US +1 214 480 4572 aris@ti.com
Dr. Paranchych, David Nortel Networks 3GPPMEMBER (ATIS) US +1 (972) 685-1828 paranchy@nortel.com
Dr. Parkvall, Stefan Ericsson Inc. 3GPPMEMBER (ATIS) SE +46 719 00 00 stefan.parkvall@ericsson.com
Mr. Pham, Duong NEC Corporation 3GPPMEMBER (TTC) AT +61392643902 duongp@3g.nec.com.au
Mrs. Phan huy, Dinh thuy France Telecom 3GPPMEMBER (ETSI) FR +33 1 45 29 65 82 dinhthuy.phanhuy@orange-ft.com
Mr. Pollard, Adam VODAFONE LTD 3GPPMEMBER (ETSI) GB +44 1635 672479 adam.pollard@vodafone.com
Dr. Prasad, Narayan NEC Corporation 3GPPMEMBER (ARIB) JP +1-609-951-2985 prasad@nec-labs.com
Mr. Ranta-aho, Karri Nokia Telecommunications Inc. 3GPPMEMBER (ATIS) FI +358 50 521 0651 Karri.Ranta-aho@nokia.com
Dr. Ratasuk, Rapeepat MOTOROLA Ltd 3GPPMEMBER (ETSI) GB +1 847 632 6881 ratasuk@motorola.com
Mr. Rheinschmitt, Rupert ALCATEL S.A. 3GPPMEMBER (ETSI) DE +49 711 821 34172 Rupert.Rheinschmitt@alcatel.de
Mr. Ruprich, Thomas INFINEON TECHNOLOGIES 3GPPMEMBER (ETSI) DE +49 89 234 86253 thomas.ruprich@infineon.com
Dr. Sälzer, Thomas ORANGE SA 3GPPMEMBER (ETSI) FR +33 1 45 29 64 80 thomas.salzer@orange-ft.com
Mr. Seo, Dongyoun LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-2931 dseo@lge.com
Mr. Seyama, Takashi Fujitsu Limited 3GPPMEMBER (ARIB) JP +81-46-839-5374 seyama.takashi@jp.fujitsu.com
Mr. Shen, Jia RITT 3GPPMEMBER (CCSA) CN +86-10-62302438 shenjia@mail.ritt.com.cn
Dr. Stamatis, Georgoulis Aeroflex 3GPPMEMBER (ETSI) GB +441763267859 Stamatis.Georgoulis@Aeroflex.com
Dr. Suh, Hyung sik LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-2-3777-5694 suh1@lge.com
Dr. Sun, Shaohui CATT 3GPPMEMBER (CCSA) CN +86 10 58832133 sunshaohui@datangmobile.cn
Miss Sunju, Park Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) KR +82-31-279-5861 sunju0124.park@samsung.com
+86-10-82029090-
Mr. Suo, Shiqiang CATT 3GPPMEMBER (CCSA) CN 6546 suoshiqiang@datangmobile.cn
Mr. Suzuki, Hidetoshi Panasonic Mobile Communication 3GPPMEMBER (TTC) JP +81 468 40 5451 Suzuki.Hidetoshi@jp.panasonic.com
Dr. Suzuki, Toshinori ARIB 3GPPORG_REP (ARIB) JP +81-46-847-6350 tn-suzuki@kddi.com
Mr. Tanaka, Yoshinori Fujitsu Limited 3GPPMEMBER (ARIB) JP    
Mr. Tang, Hai CATT 3GPPMEMBER (CCSA) CN +86 10 58832228 tanghai@datangmobile.cn
Mr. Taoka, Hidekazu NTT DoCoMo Inc. 3GPPMEMBER (TTC) JP +81 468 40 3470  
Dr. Tosato, Filippo Philips International B.V. 3GPPMEMBER (ETSI) GB +44 1293 815 475 filippo.tosato@philips.com
Dr. Tsai, Jiannan Samsung Telecommunications 3GPPMEMBER (ATIS) US +1-972-761-7424 jtsai@sta.samsung.com
Mr. Tuomaala, Esa NOKIA Corporation 3GPPMEMBER (ETSI) FI +8613910195882 esa.tuomaala@nokia.com
Dr. Van de beek, Jaap HUAWEI TECHNOLOGIES Co. Ltd. 3GPPMEMBER (ETSI) CN +468 4770808 jaap.vandebeek@huawei.com
Mr. Van rensburg, Cornelius Samsung Telecommunications 3GPPMEMBER (ATIS) US +1 972 761 7970 c.rensburg@samsung.com

61
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
Mr. Vujcic, Dragan LG Electronics Mobilecomm 3GPPMEMBER (ETSI) FR +33 1 41 59 93 78 dvujcic@lge.com
Mr. Wan, Tak Wing Rogers Wireless Inc. 3GPPMEMBER (ATIS) CA +1 416 935 6029 takwing.wan@rci.rogers.com
Mr. Wang, Chengyu HuaWei Technologies Co., Ltd 3GPPMEMBER (CCSA) CN +86-10-82882719 wangchengyu@huawei.com
Mr. Wang, Ke CATT 3GPPMEMBER (CCSA) CN +86 10 82029090 wangke@datangmobile.cn
Mr. Wannemacher, Georg T-Mobile International AG 3GPPMEMBER (ETSI) DE +49229/936-18433 georg.wannemacher@t-mobile.de
Mr. Willenegger, Serge QUALCOMM EUROPE S.A.R.L. 3GPPMEMBER (ETSI) CH +41 24 436 3540 sergew@qualcomm.com
Ms. Wimmer, Malgorzata Siemens nv/sa 3GPPMEMBER (ETSI) PL +48(0)717992624 Malgorzata.Wimmer@siemens.com
Mr. Zirwas, Wolfgang SIEMENS AG 3GPPMEMBER (ETSI) DE +49 89 722 34369 wolfgang.zirwas@siemens.com
Miss Wong, Eliza ALCATEL S.A. 3GPPMEMBER (ETSI) FR +33130775698 eliza.wong@alcatel.Fr
Mr. Wong, Sai ho Institute for Infocomm Researc 3GPPMEMBER (ETSI) SG +65 6874 5682 shwong@i2r.a-star.edu.sg
Mr. Wu, Jianming ATIS 3GPPORG_REP (ATIS) US +1 613 765 5671 jianmwu@nortel.com
Mr. Xu, Hua Nortel Networks 3GPPMEMBER (ATIS) US +0016137652564 huaxu@nortel.com
Dr. Yamamoto, Toshiaki ARIB 3GPPORG_REP (ARIB) JP +81-46-847-6350 tos-yama@kddilabs.jp
Mr. Yu, Dongsheng Nortel Networks 3GPPMEMBER (ATIS) US +613-765-9665 dongshengyu@nortel.com
Ms. Yu, Qian Matsushita Electric Industrial 3GPPMEMBER (ARIB) JP +65 65505348 Qian.Yu@sg.panasonic.com
Dr. Yuen, Chau Institute for Infocomm Researc 3GPPMEMBER (ETSI) SG +65-68745679 cyuen@i2r.a-star.edu.sg
Dr. Yun, Young woo LG Electronics Inc. 3GPPMEMBER (TTA) KR +82-31-450-7316 youngwooy@lge.com
Mr. Zeira, Eldad INTERDIGITAL COMMUNICATIONS 3GPPMEMBER (ETSI) US +1 631 622 4134 eldad.zeira@interdigital.com
Miss Zhang, Xiaoxia QUALCOMM EUROPE S.A.R.L. 3GPPMEMBER (ETSI) US +001 858-6585035 xiaoxiaz@qualcomm.com
Mr. Zhang, Yincheng ZTE Corporation 3GPPMEMBER (CCSA) CN +86 21 68895821 zhang.yincheng@zte.com.cn
Mr. Zhang, Yujian Samsung Electronics Co., Ltd 3GPPMEMBER (TTA) CN +86 13511008996 yujian.zhang@samsung.com
Mr. Zuo, Zhisong ZTE Corporation 3GPPMEMBER (CCSA) CN +86 755 26770894 zuo.zhisong@zte.com.cn

62
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Annex B: TSG RAN WG1 meetings in 2006 and 2007

TITLE TYPE DATES LOCATION CTRY
3GPPRAN1 LTE Ad Hoc AH 23 - 25 Jan 2006 Helsinki FIN
3GPPRAN1#44 WG 13 - 17 Feb 2006 Denver USA
3GPPRAN1#44bis WG 27 - 31 March 2006 Athens GR
3GPPRAN1 #45 WG 09-13 May 2006 Shanghai China
3GPPRAN1 LTE Ad Hoc AH 27-30 June 2006 Cannes FR
3GPPRAN1#46 WG 28 Aug-01 Sept 2006 Tallinn Estonia
3GPPRAN1#46bis WG 09-13 Oct 2006 Seoul Korea
3GPPRAN1#47 WG 06 - 10 Nov 2007 Riga Latvia

TITLE TYPE DATES LOCATION CTRY

3GPPRAN1#47bis WG 15 - 19 Jan 2007 Sorrento IT
3GPPRAN1#48 WG 12 - 16 Feb 2007 TBD US
3GPPRAN1#48bis WG 26 - 30 2007 TBD TBD
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

63
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
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

64
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Annex C: List of CRs agreed at RAN1#46bis

Spec CR R Cat Rel R1 Tdoc Title Work Item
25.211 0230 1 B Rel-7 R1-062986 UL DPCCH slot format RANimp-CPC
25.212 0238 4 B Rel-7 R1-063014 Support of CPC feature RANimp-CPC
25.214 0421 5 B Rel-7 R1-063017 Support of CPC feature RANimp-CPC
Note: CR 0421R4 to 25.214 was agreed as a RAN1 baseline for further corrections and clarifications so that this CR might be updated in next meeting if necessary.

65
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Annex D: List of Outgoing LSs

NUMBER TITLE Release WI To Cc
R1-062976 Reply to RAN2 LS on Random-Access Related Issues Rel-7 LTE RAN2 -
R1-063006 Reply LS on minimum receiver bandwidth capability Rel-7 LTE RAN2 RAN4
R1-063009 LS on status of Rel-7 FDM MIMO Rel-7 MIMO RA2, RAN3, RAN
RAN4
R1-063010 Reply LS on VoIP RAB combination Rel-6 RAB Support RAN2 -
Enhancement
R1-063011 LS on status of RAN1 CRs for "Continuous connectivity for packet Rel-7 RANimp-CPC RAN2, RAN3, -
data users" RAN4
R1-063012 LS on E-UTRA physical-layer model Rel-7 LTE RAN2 -
R1-063015 LS on non-Scheduled Traffic and Scheduled Traffic Transmissions Rel-7 1.28 Mcps TDD RAN2 -
Enhanced Uplink

66
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006

Annex E: List of Tdocs at RAN1 #46bis

AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
R1-062455 Draft Agenda for RAN1 #46bis RAN1 Chairman 2 R1-062540 Approved
R1-062456 Draft Report of RAN1#46 MCC 3   Approved in R1-063013
LS on co-ordination of work on GERAN- = GP-061878 Noted
TSG GERAN, T-
R1-062457 LTE Interworking (To: RAN, SA, CC: SA2, 4
Mobile
RAN1, RAN2)
Reply LS on co-ordination of work on = RP-060638 Noted
R1-062458 GERAN-LTE Interworking (To: GERAN, TSG RAN, T-Mobile 4
SA, Cc: SA2, RAN1, RAN2, GERAN2)
LS on random access control for = R2-062669 Noted
R1-062459 1.28Mcps TDD Enhanced Uplink WG RAN2, TD-Tech 4
(To:RAN1)
Reply LS to RAN1 LS on Uplink Control = R2-062715 Noted
R1-062460 Signalling for 1.28Mcps TDD Enhanced WG RAN2, CATT 4
Uplink (To:RAN1)
Reply LS on feedback regarding the = R2-062716 Noted
concepts for "Continuous connectivity for
R1-062461 WG RAN2, Nokia 4
packet data users" (To: RAN1, Cc: RAN3,
RAN4)
Physical Channel Definitions supporting = R2-062720 Noted
R1-062462 WG RAN2, Motorola 4
PCH, MCH and BCH (To: RAN1)
R1-062463 LS on VoIP RAB combination (To:RAN1) WG RAN2, Orange 4 = R2-062721 Noted.
Reply-LS on "Bearer QoS Information = R3-061372 Noted
R1-062464 Elements Signaled on S1" (To: SA2, SA4, WG RAN3, Siemens 4
RAN2, Cc: RAN1)
Reply-LS on Single Frequency Network = R3-061424 Noted
R1-062465 synchronization for E-MBMS (To: RAN1, WG RAN3, Siemens 4
RAN2, Cc: RAN4)
LS on E-UTRA mobility support (To: = R3-061081 Noted
R1-062466 WG RAN4, Nokia 4
RAN1, Cc: RAN2, RAN3)
LS from RAN #33 to SA#33 = RP-060637 Noted
“Consideration of timelines between RAN
TSG RAN, NTT
R1-062467 and SA with regard to LTE and SAE” 4
DoCoMo
(To:SA, Cc: RAN1, RAN2, RAN3, RAN4,
RAN5)
67
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Observations on MBMS Enhancement via   Withdrawn
R1-062468 Motorola 7.3
Synchronization
Implementation Aspects of 16-QAM for   Noted
R1-062469 Motorola 7.3
HSPA Uplink
Further Observations on 64-QAM for   Noted
R1-062470 Motorola 7.3
HSPA Downlink
A Gradient Based Peak-to-Average Power   Not treated
R1-062471 Agere Systems 6.9
Ratio Reduction Method
Advanced MCS Selection and Power   Not treated
R1-062472 Loading for Multi-stream Downlink MIMO SHRCWC, RITT 6.6.3
with Reduced CQI Feedback
Pilot Boosting Consideration in E-UTRA   Not treated
R1-062473 SHRCWC, ZTE 6.5.1
Downlink
A Proposal for an Improved DL Reference   Not treated
R1-062474 Alcatel 6.5.1
Symbol Positioning in EUTRA
Considerations on the EUTRA DL   Not treated
R1-062475 reference signal structure and the DC sub- Alcatel 6.5.1
carrier
Comparison of transmit diversity schemes   Noted
R1-062476 for E-UTRA in noise and interference Alcatel 6.6.4
limited scenarios
Spectral efficiency considerations for   Not treated
R1-062477 Alcatel 6.3.4
EUTRA at higher bandwidths
R1-062478 Impact of PRB size on Control Signalling Alcatel 6.12.1   Withdrawn
Resource-Block mapping of Distributed   Not treated
R1-062479 Philips, Intel 6.3.4
Transmissions in E-UTRA downlink
Impacts on channel estimation of   Not treated
R1-062480 Resource-Block Mapping of Distributed Philips 6.3.4
Transmissions in E-UTRA Downlink
Asynchronous RACH preamble message   Noted
R1-062481 Philips 6.4.3
design
R1-062482 MIMO resource definition for E-UTRA Philips, Ericsson 6.6   Not treated
Comparison between MU-MIMO   Noted
R1-062483 codebook-based channel reporting Philips 6.6.3
techniques for LTE downlink
Control of CQI feedback signalling in E-   Not treated
R1-062484 Philips, Intel 6.12.2
UTRA

68
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Details of HS-SCCH signalling for Rel-7   Noted
R1-062485 Philips 7.1.1
MIMO
Philips, Qualcomm, R1-062986 Revised in R1-062986
25.211 CR0230 (Rel-7, B) "UL DPCCH
R1-062486 Siemens, Ericsson, 7.2
slot format"
Nokia
Hierarchical SCH signals suitable for both   Not treated
R1-062487 Huawei 6.4.4
(FDD and TDD) modes of E-UTRA
DL reference symbols with varying   Not treated
R1-062488 positions in frequency - system-level Huawei 6.5.1
evaluation
Unitary precoding with non-unitary fallback   Noted
R1-062489 Huawei 6.6.3
mode
System Level Simulations of Common   Not treated
R1-062490 Huawei 6.6.4
Control Channel Transmit Diversity
Overhead reduction of UL CQI signalling   Not treated
R1-062491 Huawei 6.6.6
for E-UTRA DL
Baseline uplink E-CQI message – content   Not treated
R1-062492 Huawei 6.6.6
and size
Performance Benchmark for a New   Not treated
R1-062493 Unitary Precoding Scheme with Uniform Intel Corporation 6.6.5
MCS Allocation
Elimination of the Asynchronous RACH   Not treated
R1-062494 Procedure InterDigital 6.4.3
Requirement during LTE Handover
R1-062495 Cell Search Proposal for E-UTRA InterDigital 6.4.4   Not treated
Combined Open Loop/CQI Based Uplink   Not treated
R1-062496 Power InterDigital 6.8
Control for E-UTRA
Link Performance of Frequency Hopping   Noted
R1-062497 Huawei 6.3.4
in LTE Uplink Localized transmission
R1-062498 Uplink Reference Signal for E-UTRA Huawei 6.5.2   Not treated
E-UTRA Downlink L1/L2 Control   Not treated
R1-062499 Huawei 6.12.1
Signalling design
Evaluation of E-UTRA Downlink L1/L2   Not treated
R1-062500 Control Channel Multiplexing(FDM vs Huawei 6.12.1
TDM)
Layer 1 Procedure of Non-synchronized   Not treated
R1-062501 ITRI 6.4.3
Random Access in E-UTRA
69
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Partition Rule for Distributed Multiplexing   Not treated
R1-062502 ITRI 6.12.1
in E-UTRA Downlink
Random access preamble design for   Noted
R1-062503 TD Tech 6.4.3
alternative EUTRA TDD
R1-062504 Cell search time performance TD Tech 6.4.4   Not treated
25.212 CR0238r1 (Rel-7, B) "Support of Qualcomm, Nokia, R1-062978 Revised in R1-062978
R1-062505 7.2
CPC feature" Ericsson, Siemens
25.214 CR0421r1 (Rel-7, B) "Support of Qualcomm, Nokia, R1-062968 Revised in R1-062968
R1-062506 7.2
CPC feature" Ericsson, Siemens
Link performance of codebook based   Not treated
Freescale
R1-062507 precoded MIMO transmission schemes for 6.6.5
Semiconductor
EUTRA
Cluster size for codebook based Freescale   Not treated
R1-062508 6.6.5
precoding in downlink MIMO for EUTRA Semiconductor
Precoding methodologies with rank Freescale   Not treated
R1-062509 6.6.5
adaptation for EUTRA MIMO Semiconductor
Efficient method for feedback reduction   Not treated
Freescale
R1-062510 and feedback mechanism for precoded 6.6.5
Semiconductor
MIMO in EUTRA
R1-062511 LTE DL VoIP capacity Samsung 6   Not treated
R1-062512 Modulation Schemes for E-UTRA uplink Samsung 6.3.1 R1-062953 Revised in R1-062953
Performance comparison between LFDMA   Noted
R1-062513 Samsung 6.3.2
and DFDMA transmission in UL
BCH design considering EUTRA spectrum   Noted
R1-062514 Samsung 6.4.1
allocations
R1-062515 Asynchronous RACH Preamble Design Samsung 6.4.3 R1-062958 Revised in R1-062958
Synchronized Random Access Design for   Not treated
R1-062516 Samsung 6.4.3
E-UTRA
Antenna swiching transmission of RACH   Not treated
R1-062517 Samsung 6.4.3
preamble
Cell search procedure and channel   Not treated
R1-062518 Samsung 6.4.4
structure
SCH design for 20 MHz spectrum   Withdrawn
R1-062519 Samsung 6.4.4
allocation
Downlink reference signal : time-frequency   Not treated
R1-062520 Samsung 6.5.1
averaging/interpolation
DL reference signal structure: common vs   Not treated
R1-062521 Samsung 6.5.1
dedicated
70
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
R1-062522 Uplink reference signal multiplexing Samsung 6.5.2   Withdrawn
Link performance comparison of layer   Noted
R1-062523 Samsung 6.6.2
permutation vs. no layer permutation
System performance comparison of layer   Noted
R1-062524 Samsung 6.6.2
permutation vs. no layer permutation
Dynamic Mode Switching between Single   Noted
R1-062525 Samsung 6.6.3
and Multi-User MIMO
Further Performance Comparison of   Noted
R1-062526 Samsung 6.6.3
Unitary vs. Non-Unitary Precoding
Transmit diversity performance for the   Not treated
R1-062527 Samsung 6.6.4
common control channels
Transmit diversity performance for the   Not treated
R1-062528 Samsung 6.6.4
shared data channels
Precoding for MIMO spatial multiplexing   Not treated
R1-062529 Samsung 6.6.5
and transmit diversity
R1-062530 DL resource allocation strategy Samsung 6.10   Not treated
Uplink cell throughput performance with   Not treated
R1-062531 Samsung 6.10
different allocation unit
Downlink Link Adaptation and Related   Not treated
R1-062532 Samsung 6.12.1
Control Signaling
R1-062533 Downlink Hybrid ARQ Signaling Samsung 6.12.1   Not treated
R1-062534 DL control channel structure: overview Samsung 6.12.1   Not treated
R1-062535 Performance of DL L1/L2 control channel Samsung 6.12.1   Not treated
Joint vs. Separate Coding for DL Control   Not treated
R1-062536 Samsung 6.12.1
Signalling
R1-062537 Uplink data-associated control signalling Samsung 6.12.2   Not treated
Uplink ACK/NACK signaling in support of   Noted
R1-062538 Samsung 6.12.2
downlink Hybrid ARQ
Physical layer UE capability aspects of   Not treated
R1-062539 Samsung 6.14
broadcast/unicast superposition
R1-062540 Revised draft Agenda for RAN1 #46bis RAN1 Chairman 2 (R1-062455) Not treated
Physical Channel for Timing Mitsubishi Electric 6.7   Not treated
R1-062541
Synchronization, NTT DoCoMo
R1-062542 Signaling Way of Resource Assignment Mitsubishi Electric 6.12.1   Not treated
R1-062543 Comparison of CQI feedback schemes Mitsubishi Electric 6.12.2   Not treated
ZTE, China Mobile, 6.3.4   Agreed
R1-062544 UL sub-frame format and CP durations
CATT

71
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Performance Comparison of Unitary vs. ZTE 6.6.3   Noted
R1-062545
Non-Unitary Precoding for MU-MIMO
Performance Evaluation of Codebook- ZTE 6.6.5   Not treated
R1-062546
based Precoding
R1-062547 Downlink shared control signalling ZTE 6.12.1   Not treated
Uplink Reference Design Considering ZTE, SHRCWC 6.5.2 (R1-062211) Not treated
R1-062548 Reference Power Boost, Channel
Measurement and Interference Mitigation
One Efficient PAPR Reduction Method in ZTE, CATT, RITT 6.9   Not treated
R1-062549
Downlink
R1-062550 BCH Location in E-UTRA Downlink ZTE 6.4.1   Not treated
Some considerations on BCH of ETURA ZTE, CATT 6.4.1   Not treated
R1-062551
TDD
Non-synchronized random access ZTE 6.4.3   Noted
R1-062552
procedure and preamble
Localized and distributed SC-FDMA LG Electronics 6.3.2   Noted
R1-062553
transmission in uplink
R1-062554 Uplink frequency hopping LG Electronics 6.3.4   Noted
Soft-Combined synchronous PCH LG Electronics 6.4.2   Noted
R1-062555
transmission
RACH Sequence Design Based on LG Electronics 6.4.3   Noted
R1-062556
Repetition Method
RACH Design Issues of Large Cell LG Electronics 6.4.3   Not treated
R1-062557
Deployment
R1-062558 SCH/BCH transmission LG Electronics 6.4.4   Not treated
Comparison of TDM and FDM for P- LG Electronics 6.4.4   Not treated
R1-062559
SCH/S-SCH
SCH Structure and Sequences for Cell LG Electronics 6.4.4   Not treated
R1-062560
Search
LGE’s views on the various aspects of LG Electronics 6.5.1   Not treated
R1-062561
downlink reference signal design
Uplink reference signal multiplexing LG Electronics 6.5.2   Not treated
R1-062562
method
Performance comparison between CDM LG Electronics 6.5.2   Not treated
R1-062563
and FDM Pilot for Uplink SC-FDMA
System level results for investigation; LG Electronics 6.6.1   Noted
R1-062564 Maximum number of codewords for 4x4
MIMO
72
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Link performance of DL SU-MIMO LG Electronics 6.6.2   Noted
R1-062565 according to the amount of feedback
overhead
Link Evaluation of DL SU-MIMO – Impact LG Electronics 6.6.2   Noted
R1-062566
of Generalized CDD
Codebook design and verification for 4x1 LG Electronics 6.6.5   Not treated
R1-062567
MIMO
System level evaluation of 2x2 downlink LG Electronics 6.6.5   Not treated
R1-062568
SU-MIMO with rank adaptation
Restriction on the number of scheduled LG Electronics 6.10   Not treated
R1-062569
UEs in downlink
R1-062570 Downlink HARQ LG Electronics 6.10   Not treated
Uplink resource request for uplink LG Electronics 6.10   Not treated
R1-062571
scheduling
R1-062572 Group Scheduling for Downlink and Uplink LG Electronics 6.10   Not treated
Alternative Uplink Synchronous HARQ LG Electronics 6.10   Not treated
R1-062573
schemes
R1-062574 Downlink control signaling LG Electronics 6.12.1   Not treated
Further Analysis on DCT based CQI LG Electronics R1-062954 Not treated
R1-062575 6.12.2
reporting Scheme
Proposed response to RAN2 LS in [R1- Samsung, NTT   Noted
R1-062576 6.4.3
062434] DoCoMo, NEC
L1 Multiplexing aspects of   Noted
R1-062577 Samsung 6.2
broadcast/unicast superposition
Performance of DL distributed   Not treated
R1-062578 Samsung 6.3.4
transmission
R1-062579 Distributed transmission on downlink Samsung 6.3.4   Not treated
R1-062580 LTE MIMO email discussion summary Samsung 6.6   Noted
The New Sub-Frame Structure for EUTRA   Not agreed
R1-062581 ZTE 6.3.4
Uplink
Non-initial cell search performance   Not treated
R1-062582 comparison of FDM based and TDM ETRI 6.4.4
based cell search schemes
Downlink Transmit Diversity Method for   Not treated
R1-062583 ETRI 6.6.4
BCH Channel
System level evaluations of diversity   Not treated
R1-062584 ETRI 6.6.4
schemes for SCH

73
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Signaling for downlink scheduling:   Not treated
R1-062585 ETRI 6.12.1
separate vs. joint coding
Power Control for Interference   Not treated
R1-062586 Coordination including Pilot and Control Alcatel 6.8
Channels
LCR TDD; Non-Scheduled Traffic and R1-062969 Agreed with revision of wording in R1-062992
R1-062587 ZTE 8
Scheduled Traffic Transmissions
20ms TTI Co-existence with 5ms TTI for R1-062970 Revised in R1-062970
R1-062588 E-DCH of LCR TDD: System Level ZTE 8
Simulation Results
Evaluation on mapping scheme from   Not treated
R1-062589 Huawei 6.3.4
distributed VRB to PRB
25.214 CR0424 (R99, F) "Correction of   Not treated
R1-062590 Huawei 5.1
DPDCH Gain factor in compressed mode"
25.214 CR0425 (Rel-4, A) "Correction of   Not treated
R1-062591 Huawei 5.1
DPDCH Gain factor in compressed mode"
25.214 CR0426 (Rel-5, A) "Correction of   Not treated
R1-062592 Huawei 5.1
DPDCH Gain factor in compressed mode"
25.214 CR0427 (Rel-6, F) "Correction of   Not treated
R1-062593 DPDCH and E-DPDCH Gain factor in Huawei 5.1
compressed mode"
25.214 CR0428 (Rel-7, A) "Correction of   Not treated
R1-062594 DPDCH and E-DPDCH Gain factor in Huawei 5.1
compressed mode"
Proposed LS response on Random   Not treated
R1-062595 Motorola 4
Access Related Issues
Skeleton of 36.213 Physical Layer   Endorsed as v0.1.0in R1-063004
R1-062596 Motorola 6.1
Procedure for E-UTRA
R1-062597 Number of HARQ Channels Motorola 6.2   Noted
R1-062598 UL distributed transmissions Motorola 6.3.2   Noted
R1-062599 Single RB Assignment Motorola 6.3.4   Noted
UL E-UTRA VoIP Performance with Intra-   Withdrawn
R1-062600 Motorola 6.3.4
TTI frequency hopping
Non-Synchronized Random Access   Noted
R1-062601 Motorola 6.4.3
Message Content
E-UTRAN Non-Synchronized Random   Noted
R1-062602 Motorola 6.4.3
Access Procedure

74
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Random Access Channel Email   Noted
R1-062603 Motorola 6.4.3
discussion summary
Cell Search and Measurement with   Not treated
R1-062604 Motorola 6.4.4
Heterogeneous Bandwidth
SCH Design for Initial Cell Search for E-   Not treated
R1-062605 Motorola 6.4.4
UTRA DL
R1-062606 SYNC channel email discussion summary Motorola 6.4.4 R1-062946 Revised in R1-062946
R1-062607 SCH Design for Non-initial Cell Search Motorola 6.4.4   Not treated
Issues of non-overlapping DL reference   Not treated
R1-062608 Motorola 6.5.1
signal with power boosting
Simulation Results for GCL based DL   Not treated
R1-062609 Motorola 6.5.1
Reference Signals
UL Reference Signal Multiplexing   Not treated
R1-062610 Motorola 6.5.2
Structures for E-UTRA
E-UTRA SC-FDMA UL Pilot/Reference   Not treated
R1-062611 Motorola 6.5.2
Signal Design
R1-062612 UL Power Control for E-UTRA Motorola 6.8   Not treated
Acceptable UL IoT Level vs. Resource   Not treated
R1-062613 Motorola 6.8
Allocation Attributes
R1-062614 DL Power Control for E-UTRA Motorola 6.8   Not treated
DL Power Allocation for Dynamic   Not treated
R1-062615 Motorola 6.8
Interference Avoidance in E-UTRA
UL System performance impact from EVM   Withdrawn
R1-062616 and Adjacent channel emissions with UL Motorola 6.8
PC
R1-062617 LTE Downlink PAPR Reduction Motorola 6.9   Not treated
Persistent Scheduling for E-UTRA VoIP R1-062981 Not treated
R1-062618 Motorola 6.12.1
and Control Channel considerations
E-UTRA DL Distributed Multiplexing and   Not treated
R1-062619 Motorola 6.10
Mapping Rules
Benefits of sending two MCS to a user   Not treated
R1-062620 Motorola 6.11
within a TTI
E-UTRA DL L1/L2 Control Channel   Not treated
R1-062621 Motorola 6.12.1
Information fields & bit requirements
E-UTRA DL L1/L2 Control Channel Non- R1-062982 Not treated
R1-062622 Motorola 6.12.1
Persistent Performance
E-UTRA DL L1/L2 Control Channel TDM   Not treated
R1-062623 Motorola 6.12.1
vs. FDM
75
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
DL L1/L2 Control Signaling for 15 and   Withdrawn
R1-062624 Motorola 6.12.1
20MHz carriers
Downlink Acknowledgement and Group   Not treated
R1-062625 Motorola 6.12.1
Transmit Indicator Channels
E-UTRA UL L1/L2 Control Channel   Not treated
R1-062626 Motorola 6.12.2
Mapping
UL L1/L2 Control Signaling for 15 and   Not treated
R1-062627 Motorola 6.12.2
20MHz carriers
E-UTRA DL ACK/NACK and CQI Link   Withdrawn
R1-062628 Motorola 6.12.2
performance and coverage
Collision probability and randomness   Withdrawn
R1-062629 requirements for Random Access in E- Texas Instruments 6.4.3
UTRA
Non synchronized Random Access   Noted
R1-062630 Texas Instruments 6.4.3
Structure for E-UTRA
Configurable Cyclic Shift for Non   Not treated
R1-062631 Texas Instruments 6.4.3
Synchronized Random Access preamble
Synchronized Random Access Structure   Not treated
R1-062632 Texas Instruments 6.4.3
for E-UTRA
Wideband Pilot in Synchronized Random   Not treated
R1-062633 Texas Instruments 6.4.3
Access Burst
Synchronized Random Access:   Not treated
R1-062634 performance comparison of preamble- Texas Instruments 6.4.3
based and UL sub-frame structures
Proposal for DL SYNC Channel (SCH) for R1-062963 Not treated
R1-062635 Texas Instruments 6.4.4
E-UTRA Cell Search
Cell Search Performance in Tightly R1-062964 Not treated
R1-062636 Texas Instruments 6.4.4
Synchronized Network for E-UTRA
Design of Primary Synchronization Code   Not treated
R1-062637 Texas Instruments 6.4.4
(PSC) for E-UTRA Cell Search
Comparison of different S-SCH structures   Not treated
R1-062638 Texas Instruments 6.4.4
for E-UTRA cell search
Summary of Reflector Discussions on   Noted
R1-062639 Texas Instruments 6.5
EUTRA DL RS Design Issues
Summary of Reflector Discussions on   Noted
R1-062640 Texas Instruments 6.5
EUTRA UL RS Design Issues

76
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Multiplexing of Distributed (“Sounding”)   Not treated
R1-062641 Reference Signals for CQI Measurement Texas Instruments 6.5.2
and Scheduling in EUTRA Uplink
R1-062642 Uplink Reference Signal Design in EUTRA Texas Instruments 6.5.2   Not treated
Overview of Distributed (“Sounding”)   Not treated
R1-062643 Reference Signal Multiplexing Methods in Texas Instruments 6.5.2
EUTRA Uplink
Reference Signal Multiplexing for 1 ms TTI   Not treated
R1-062644 Texas Instruments 6.5.2
in EUTRA Uplink
Description of Per-Group Rate Control   Noted
R1-062645 (PGRC) And System Level Comparison Texas Instruments 6.6.1
With Per-Antenna Rate Control (PARC)
Signaling and Feedback Requirements   Noted
R1-062646 Texas Instruments 6.6.1
For Different Number of Codewords
Single-user MIMO performance with   Noted
R1-062647 Texas Instruments 6.6.1
largest CQI feedback
System Level Study Of Channel Quality   Noted
R1-062648 Texas Instruments 6.6.2
Indicator (CQI) Quantization
Link level performance of layer   Noted
R1-062649 Texas Instruments 6.6.2
permutation scheme
Codebook Design for E-UTRA MIMO Pre-   Not treated
R1-062650 Texas Instruments 6.6.5
coding
Uplink Power Control for EUTRA:   Not treated
R1-062651 Optimizing the Trade-off between Cell- Texas Instruments 6.8
Edge and Cell-Average Throughputs
Control Channel Structure and Coding in   Not treated
R1-062652 Texas Instruments 6.12.1
E-UTRA Downlink
Control Channel Coding for Uplink   Not treated
R1-062653 Texas Instruments 6.12.1
Scheduling in E-UTRA Downlink
Category 0 for the Control Channel in E-   Not treated
R1-062654 Texas Instruments 6.12.1
UTRA Downlink
Link Level Control Channel Performance   Not treated
R1-062655 Texas Instruments 6.12.1
in E-UTRA Downlink
System Level Control Channel   Not treated
R1-062656 Texas Instruments 6.12.1
Performance in E-UTRA Downlink
Control Channel Multiplexing in E-UTRA   Not treated
R1-062657 Texas Instruments 6.12.1
Downlink

77
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
ACK/NACK Transmission without a   Not treated
R1-062658 Texas Instruments 6.12.2
Reference Signal in E-UTRA Uplink
Reduced L1 identity for UL synchronized   Not treated
R1-062659 Texas Instruments 6.12.2
UE’s in E-UTRA
Need to Decode BCH from Adjacent Non–   Not treated
R1-062660 Texas Instruments 6.4.1
Serving Cells
R1-062661 E-UTRA Uplink System Design Options Motorola 6.3.2   Noted
R1-062662 TDD Numerology and Alignment with FDD Motorola 6.3.3   Noted
Max #UEs/TTI for optimum E-UTRA DL   Not treated
R1-062663 Motorola 6.12.1
performance
Synchronized Random Access Channel &   Noted
R1-062664 Motorola 6.4.3
Scheduling Request
R1-062665 Differential Feedback for MIMO Precoding Intel Corporation 6.6.6   Withdrawn
Further Results on VoIP Enhancements   Noted
R1-062666 InterDigital 7.3
for HSPA Evolution
R1-062667 Further DL VoIP capacity analysis Qualcomm Europe 7.2   Not treated
Complexity and buffering requirements for Qualcomm Europe   Not treated
R1-062668 reduced complexity HS-SCCH-less 7.2
Operation
R1-062669 Improvements on E-DPCCH for HSPA Qualcomm Europe 7.3   Noted
R1-062670 Improved E-DPCCH coding Qualcomm Europe 7.3   Noted
Improved E-DPCCH power setting as a Qualcomm Europe   Noted
R1-062671 7.3
function of the Handoff state
R1-062672 F-DPCH time alignment Qualcomm Europe 7.3   Noted
Qualcomm Europe   Noted. Discuss this on the email reflector as
R1-062673 Monitoring of HSUPA grant channels 7.3 part of the CPC discussion (to be concluded
20 Oct).
R1-062674 Link analysis of 16QAM for E-DPDCH Qualcomm Europe 7.3   Noted
Summary of Teleconference and email Qualcomm Europe   Noted
R1-062675 7.1
reflector activity on MIMO for Rel-7
L1 uplink control information in support of Qualcomm Europe   Noted
R1-062676 7.1.2
MIMO
Qualcomm Europe,   Noted
Use of transmit diversity on F-DPCH when
R1-062677 Ericsson, Philips, 7.1
the UE is operating in MIMO mode
Nokia
Handling of preferred primary beam Qualcomm Europe   Noted
R1-062678 7.1
forming vector

78
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Support of DPCH when operating in MIMO Qualcomm Europe,   Noted
R1-062679 7.1
mode Ericsson, Philips
Philips, Qualcomm,   Noted
R1-062680 CQI reporting for Rel-7 FDD MIMO 7.1.2
Nokia, Ericsson
R1-062681 HSDPA MIMO UE categories Qualcomm Europe 7.1   Withdrawn
R1-062682 HS-SCCH signalling for MIMO Qualcomm Europe 7.1.1   Withdrawn
R1-062683 ACK/NACK encoding for MIMO Qualcomm Europe 7.1.2   Withdrawn
R1-062684 Skeleton of TS36.212 Qualcomm Europe 6.1 R1-062956 Revised in R1-062956
Physical channel structure and Qualcomm Europe   Noted
R1-062685 6.2
multiplexing
Localized vs. Distributed transmission for Qualcomm Europe   Noted
R1-062686 6.3.2
Uplink
R1-062687 Issues for FDD/TDD aligned Numerology Qualcomm Europe 6.3.4   Noted
Design and Performance of BCH for E- Qualcomm Europe   Noted
R1-062688 6.4.1
UTRA
R1-062689 On the possibility of intra eNB SFN paging Qualcomm Europe 6.4.2   Noted
R1-062690 RACH sequences and planning Qualcomm Europe 6.4.3   Not treated
R1-062691 Link analysis of initial cell search Qualcomm Europe 6.4.4   Noted
Neighbor cell search - structure and Qualcomm Europe   Not treated
R1-062692 6.4.4
simulations
R1-062693 Design of DL Reference Signals Qualcomm Europe 6.5.1   Not treated
R1-062694 Design of UL Reference Signals Qualcomm Europe 6.5.2   Not treated
Max number of codewords for DL SU- Qualcomm Europe   Noted
R1-062695 6.6.1
MIMO
R1-062696 ACK structure for 4x4 DL SU-MIMO Qualcomm Europe 6.6.1   Withdrawn
Link analysis of layer permutation and no Qualcomm Europe   Revised in R1-062974
R1-062697 6.6.2
layer permutation
System Comparison of SU-MIMO and Qualcomm Europe   Noted
R1-062698 6.6.3
SDMA operations
Link analysis of DL control channel with Qualcomm Europe   Not treated
R1-062699 6.6.4
transmit diversity
R1-062700 Precoding structure for DL MIMO Qualcomm Europe 6.6.5   Not treated
Analysis of support channel overhead for Qualcomm Europe   Not treated
R1-062701 6.6.6
DL MIMO
R1-062702 Timing control for UL transmissions Qualcomm Europe 6.7 R1-062949 Not treated
R1-062703 UL RACH Power Ramping Qualcomm Europe 6.8   Not treated
R1-062704 Intra-cell power control for UL Qualcomm Europe 6.8   Not treated

79
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Analysis of Inter-cell Power Control for Qualcomm Europe   Not treated
R1-062705 6.8
Interference Management in E-UTRA UL
R1-062706 DL power control Qualcomm Europe 6.8   Not treated
Multiplexing Localized and Distributed Qualcomm Europe   Not treated
R1-062707 6.10
Users in DL and UL of E-UTRA
Structure and link analysis of DL control Qualcomm Europe   Not treated
R1-062708 6.12.1
signalling
Structure and link analysis of UL control Qualcomm Europe   Not treated
R1-062709 6.12.2
signalling
UE Physical layer capability aspects for E- Qualcomm Europe   Not treated
R1-062710 6.14
UTRA
R1-062711 Views on Rate Matching in E-UTRA NTT DoCoMo 6.2   Noted
Scrambling Code in E-UTRA Downlink NTT DoCoMo, 6.3.1   Noted
Fujitsu, Mitsubishi
R1-062712
Electric, NEC,
Panasonic, Sharp
Investigations on Adaptive Control of Roll- NTT DoCoMo, 6.3.1   Not treated
off Factor for DFT-Spread OFDM Based Fujitsu, LG
R1-062713 SC-FDMA in E-UTRA Uplink Electronics, NEC,
Panasonic, Sharp,
Toshiba Corporation
Further Investigations on Resource Block NTT DoCoMo, NEC, 6.3.4   Noted
R1-062714
Size for E-UTRA Panasonic, Sharp
Repetition of ACK/NACK in E-UTRA NTT DoCoMo, 6.3.4   Not treated
Uplink Mitsubishi Electric,
R1-062715
NEC, Panasonic,
Sharp
Minimum Transmission Bandwidth for NTT DoCoMo,   Not treated
Shared Data Channel in SC-Based E- Fujitsu, Mitsubishi
UTRA Uplink Electric, NEC,
R1-062716 6.3.4
Panasonic,
Sharp, Toshiba
Corporation
BCH Structure considering 20-MHz NTT DoCoMo   Noted
R1-062717 6.4.1
Overall Transmission Bandwidth

80
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Paging Channel Transmission Scheme in NTT DoCoMo,   Noted
E-UTRA Downlink Fujitsu, Mitsubishi
Electric, NEC,
R1-062718 6.4.2
Panasonic,
Toshiba
Corporation
Scheduling Request Transmission Method NTT DoCoMo,   Not treated
for E-UTRA Uplink Fujitsu, Mitsubishi
Electric, NEC, Sharp,
R1-062719 6.4.3
Toshiba
Corporation
NTT DoCoMo,   Not treated
Institute for
SCH Sequence Configuration for E-UTRA Infocomm Research,
R1-062720 6.4.4
Downlink Mitsubishi Electric,
Panasonic, Toshiba
Corporation
NTT DoCoMo,   Not treated
Fujitsu, Institute for
Multiplexing Method of SCH for E-UTRA
R1-062721 Infocomm Research, 6.4.4
Downlink
NEC, Panasonic,
Toshiba Corporation
NTT DoCoMo,   Not treated
Fujitsu, Mitsubishi
Three-Step Cell Search Method for E- Electric, NEC,
R1-062722 6.4.4
UTRA Panasonic,
Toshiba
Corporation
NTT DoCoMo,   Not treated
Neighboring cell search without Using
R1-062723 Fujitsu, Toshiba 6.4.4
SCH for E-UTRA
Corporation
NTT DoCoMo,   Noted
Fujitsu, KDDI,
Reference Signal Structure in E-UTRA Mitsubishi Electric,
R1-062724 6.5.1
Downlink NEC, Panasonic,
Sharp, Toshiba
Corporation

81
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
NTT DoCoMo,   Not treated
Reference Signal Structure for MIMO in E-
R1-062725 Fujitsu, Mitsubishi 6.5.1
UTRA Downlink
Electric, Panasonic
NTT DoCoMo,   Not treated
Fujitsu, KDDI, LG
Electronics,
Multiplexing Method for Orthogonal
R1-062726 Mitsubishi Electric, 6.5.2
Reference Signals for E-UTRA Uplink
NEC, Panasonic,
Sharp, Toshiba
Corporation
NTT DoCoMo,   Not treated
Mitsubishi Electric,
Orthogonal Reference Signal Structure for NEC, Panasonic,
R1-062727 6.5.2
Uplink MIMO in E-UTRA Sharp,
Toshiba
Corporation
NTT DoCoMo,   Not treated
Reference Signal Sequence Allocation Mitsubishi Electric,
R1-062728 6.5.2
Method in E-UTRA Uplink Panasonic, Sharp,
Toshiba Corporation
NTT DoCoMo,   Not treated
Group-wised Frequency Resource
Fujitsu, Mitsubishi
Allocation for Frequency Domain Channel-
R1-062729 Electric, NEC, 6.5.2
dependent Scheduling in SC-Based E-
Panasonic, Sharp,
UTRA Uplink
Toshiba Corporation
NTT DoCoMo,   Not treated
Fujitsu, Institute for
Downlink MIMO Scheme for Shared Data
R1-062730 Infocomm Research, 6.6.3
Channel in E-UTRA
Mitsubishi Electric,
NEC
NTT DoCoMo,   Not treated
Fujitsu, Institute for
Infocomm Research,
Transmit Diversity Scheme for E-UTRA
R1-062731 6.6.4
Downlink LG Electronics,
Mitsubishi Electric,
NEC, Panasonic,
Sharp

82
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
CDD-Based Pre-coding Scheme for Rank NTT DoCoMo   Not treated
R1-062732 6.6.4
= 1 and 2
NTT DoCoMo,   Not treated
Transmission Power Control in E-UTRA
R1-062733 Fujitsu, Mitsubishi 6.8
Downlink
Electric, NEC, Sharp
Transmission Power Control in E-UTRA NTT DoCoMo   Not treated
R1-062734 6.8
Uplink
NTT DoCoMo,   Not treated
Ericsson, Fujitsu,
Comparison between RB-level and Sub-
KDDI, Mitsubishi
carrier-level Distributed Transmission for
R1-062735 Electric, NEC, 6.10
Shared Data Channel in E-UTRA
Nokia,Panasonic,
Downlink
Sharp, Toshiba
Corporation
NTT DoCoMo,   Not treated
Fujistu, KDDI,
RB-level Distributed Transmission Method
Mitsubishi Electric,
R1-062736 for Shared Data Channel in E-UTRA 6.10
NEC, Panasonic,
Downlink
Sharp, Toshiba
Corporation
NTT DoCoMo,   Not treated
Fujitsu, Mitsubishi
Coding Scheme of L1/L2 Control Channel
R1-062737 Electric, NEC, 6.12.1
for E-UTRA Downlink
Toshiba
Corporation
NTT DoCoMo, KDDI,   Not treated
Multiplexing Method of Downlink L1/L2
R1-062738 Mitsubishi Electric, 6.12.1
Control Channel
Sharp
R1-062739 Persistent Scheduling in E-UTRA NTT DoCoMo, NEC 6.12.1   Not treated
NTT DoCoMo,   Noted
Ericsson, Fujitsu,
Single-Carrier Based Multiplexing of Mitsubishi Electric,
R1-062740 6.12.2
Uplink L1/L2 Control Channel NEC, Panasonic,
Sharp, Toshiba
Corporation

83
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
NTT DoCoMo,   Not treated
Ericsson, Mitsubishi
Data-non-associated L1/L2 Control
R1-062741 Electric, NEC, 6.12.2
Channel Structure for E-UTRA Uplink
Panasonic, Sharp,
Toshiba Corporation
NTT DoCoMo,   Not treated
CDM-based Multiplexing Method of Ericsson, Fujitsu,
R1-062742 Multiple ACK/NACK and CQI for E-UTRA Mitsubishi Electric, 6.12.2
Uplink Sharp,
Toshiba Corporation
E-UTRA BCH Structure and Procedures,   Noted
R1-062743 Siemens 6.4.1
20 MHz BW Mapping
Reduction of Initial E-UTRA Cell Search   Not treated
R1-062744 Siemens 6.4.4
Delay
Considerations on E-UTRA Uplink Time   Not treated
R1-062745 Siemens 6.7
Synchronization
On the Length of ZC Sequence for Non-   Noted
R1-062746 Fujitsu 6.4.3
Synchronized RACH Preamble
Performance Evaluation of Downlink Open   Not treated
R1-062747 Loop Schemes for 2- and 4-Branch LTE Nortel 6.6.4
Control Channel
TDM vs FDM for Multiplexing of Downlink   Not treated
R1-062748 Nortel 6.12.1
L1/L2 Control Signaling
Further results on the impact of speed,   Not treated
feedback period, and sub-channel
R1-062749 Nortel 6.6.6
bandwidth on the performance of downlink
closed loop schemes for 4-branch LTE
Further Performance Evaluation for DL   Not treated
R1-062750 Nortel 6.6.6
Adaptive MIMO
Consideration on MIMO DL Reference   Noted
R1-062751 Nortel 6.5.1
Signal Design for 4 Tx
Further discussion on UL reference   Not treated
R1-062752 Nortel 6.5.2
signals
R1-062753 Non-initial access procedure Nortel 6.4.4   Not treated
R1-062754 The further discussion of SCH Nortel 6.4.4   Not treated
Further Results on SCH Search   Not treated
R1-062755 Nortel 6.6.4
Performance with Transmit Diversity
R1-062756 BCH Detection Performance Evaluation Nortel 6.6.4   Not treated
84
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
The open-loop power-control effect of   Not treated
R1-062757 Nortel 6.4.3
RACH signals
On the signal structures of non-   Not treated
R1-062758 Nortel 6.4.3
synchronized RACH
Detection Performance of TDM vs. FDM   Not treated
R1-062759 Nortel 6.12.1
downlink control channels
Further discussion on adaptive fractional   Not treated
R1-062760 Nortel 6.12.1
frequency reuse
Performance of D-FDMA and L-FDMA   Noted
NEC Group, NTT
R1-062761 with Frequency 6.3.2
DoCoMo
Hopping for EUTRA Uplink
Downlink Distributed Resource Block NEC Group, NTT   Not treated
R1-062762 6.3.4
Mapping DoCoMo
R1-062763 Single Resource Block Allocation NEC Group 6.3.4   Noted
BCH, PCH, Cell Search and scalable   Noted
R1-062764 NEC Group 6.4.1
bandwidth
New definition of minimum UE capability NEC Group, NTT 6.4.1   Noted
R1-062765
DoCoMo
R1-062766 RACH Preamble Length NEC Group 6.4.3   Not treated
Reference signal multiplexing for EUTRA 6.5.2   Not treated
R1-062767 NEC Group
uplink
Reference signal multiplexing for data- 6.5.2   Not treated
R1-062768 non-associated NEC Group
control signal in EUTRA uplink
On the codebook and precoding block 6.6.5   Not treated
R1-062769 sizes for downlink NEC Group
MIMO precoding
NEC Group, NTT 6.6.5   Not treated
R1-062770 Way forward on precoding scheme
DoCoMo
Downlink ACK/NACK Mapping for E- 6.12.1   Not treated
R1-062771 NEC Group
UTRA
R1-062772 Compressed CQI Reporting Scheme NEC Group 6.12.2   Not treated
Uplink Resource Allocation for E-UTRA NEC Group, NTT 6.12.2   Not treated
R1-062773
DoCoMo
Further clarification for HS-SCCH less 7.2   Not treated
R1-062774 NEC Group
feature
A Non-codebook-based Precoding   Not treated
R1-062775 CHTTL 6.6.5
Scheme for TDD E-UTRA
85
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Effect of Quantization Errors on the   Not treated
R1-062776 Achievable Throughput of LTE MU-MIMO CHTTL 6.6.3
Schemes
Investigations on Fast Sector Selection   Not treated
R1-062777 with Intra-Cell Interference coordination in CHTTL 6.8
E-UTRA Downlink
Further System-Level Simulation Results   Not treated
R1-062778 CHTTL 6.6.4
for Downlink Inter-Sector Macro Diversity
Shorter UE ID for Downlink Scheduling   Not treated
R1-062779 Sharp 6.12.1
Information
Comparing Transmit Diversity Schemes   Not treated
R1-062780 for common control channels in E-UTRA Sharp 6.6.4
Downlink
R1-062781 Discussion on SCH contents Sharp 6.4.4   Not treated
Physical Allocation of PCH for 20MHz   Not treated
R1-062782 Sharp 6.4.2
Operating Bandwidth
SCH Structure and Initial Cell Search   Not treated
R1-062783 Sharp 6.4.4
Procedure for E-UTRA
CATT,RITT,ZTE,   Noted
R1-062784 TTI vs TTD Huawei, LG 6.3.3
Electronics
Consideration on the non-synchronized   Noted
CATT, Huawei, ZTE,
R1-062785 random access procedure for EUTRA 6.4.3
RITT
TDD
SCH Structure and Cell Search Method for   Not treated
R1-062786 CATT 6.4.4
E-UTRA TDD system
Comparing Hybrid and Cross-correlation   Not treated
R1-062787 CATT 6.4.4
method for Cell search
The downlink reference symbols design   Not treated
R1-062788 CATT,RITT,ZTE 6.5.1
for EUTRA TDD
Multiplexing Scheme of EUTRA SC-FDMA   Not treated
R1-062789 CATT 6.5.2
Uplink Reference Signals
Transmit diversity schemes for E-UTRA   Not treated
R1-062790 CATT 6.6.4
SCH
Further consideration on the downlink   Not treated
R1-062791 reference symbols of beam-forming for CATT 6.6.5
EUTRA TDD

86
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Non-codebook based pre-coding for E-   Not treated
R1-062792 CATT 6.6.5
UTRA TDD Downlink
Downlink reference signal aspects for non-   Not treated
R1-062793 CATT 6.6.5
codebook based pre-coding in TDD mode
Link level simulation results for non-   Not treated
R1-062794 codebook based pre-coding in EUTRA CATT 6.6.5
TDD (SVD)
Link level simulation results for non-   Not treated
R1-062795 codebook based pre-coding in EUTRA CATT 6.6.5
TDD (GBF)
Uplink transmit diversity scheme to   Not treated
R1-062796 provide full CSI to support downlink MIMO CATT 6.6.6
transmission for TDD operation
R1-062797 TR25.827v0.1.1 Editor, CATT 8   Endorsed as v0.2.0 in R1-062991
Performance of E-UCCH for 1.28Mcps E-   Noted
R1-062798 CATT 8
DCH
LCR TDD: Physical channel structure for   Noted
R1-062799 CATT 8
E-PUCH
HARQ timing aspects for 1.28Mcps TDD   Agreed wrt 5ms baseline
R1-062800 CATT 8
Enhanced Uplink
Power control for 1.28Mcps TDD   Agreed conditionally
R1-062801 CATT 8
Enhanced Uplink
L1/L2 Control Channel Structure with   Withdrawn
R1-062802 CDM Based Multiplexing in E-UTRA KDDI 6.12.1
Downlink
Scrambling Code for L1/L2 Control   Withdrawn
R1-062803 Channel with CDM Based Multiplexing in KDDI 6.12.1
E-UTRA Downlink
Phase Adjustment Methods of Rotational   Not treated
R1-062804 KDDI, NTT DoCoMo 6.12.1
CDM for L1/L2 Control channel
L1/L2 Control Channel Structure with   Not treated
R1-062805 CDM Based Multiplexing in E-UTRA KDDI, NTT DoCoMo 6.12.1
Downlink
Coding for Downlink L1/L2 Control   Not treated
R1-062806 Panasonic 6.12.1
Signaling
Multiplexing of Downlink L1/L2 Control   Not treated
R1-062807 Panasonic 6.12.1
Channel with Data Channel

87
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Evaluation and Error Statistics for CQI   Not treated
R1-062808 Panasonic 6.12.2
Reporting Schemes
E-UTRA Downlink System Level   Not treated
R1-062809 Performance with Compressed CQI Panasonic 6.12.2
Feedback
Discussion on maximum number of   Noted
R1-062810 Panasonic 6.6.1
codewords for 4x4 MIMO
Sequence allocation and Collision   Noted
Panasonic, NTT
R1-062811 probability analysis of RACH with control 6.4.3
DoCoMo
information
Target collision probability and HARQ Panasonic, NTT   Noted
R1-062812 6.4.3
adoption for the 1st UL message DoCoMo
Text proposal for mapping of QAM   Agreed
R1-062813 NEC Group 6.3.1
modulation to TS36.21x
Mapping of the Transport Channels to the   Noted
R1-062814 Nokia 6.2
Physical Channels
On specifying the variable channel   Noted
R1-062815 Nokia 6.3.4
bandwidth property for E-UTRA
Comparison between distributed sub-   Noted
R1-062816 carrier allocation and sub-frame based Nokia 6.3.2
frequency hopping
Simulation results for 5 MHz E-UTRA DL   Not treated
R1-062817 BLER performance with BS spectrum Nokia 6.3.4
shaping FIR filtering
Simulation results for 2.5 MHz E-UTRA DL   Not treated
R1-062818 BLER performance with BS spectrum Nokia 6.3.4
shaping FIR filtering
Considerations for minimum TTI size for   Noted
R1-062819 Nokia 6.3.4
downlink LTE
R1-062820 UL sub-frame format for long CP Nokia 6.3.4   Agreed
Extension of Random Access Preamble:   Noted
R1-062821 Nokia 6.4.3
Effect of Frequency Error
Procedure for non-synchronized random   Not treated
R1-062822 Nokia 6.4.3
access
R1-062823 Multiplexing of Synchronous RACH Nokia 6.4.3   Not treated
Broadcast Channel (BCH) structure and   Not treated
R1-062824 Nokia 6.4.1
performance
R1-062825 Cell Search Concept and Performance Nokia 6.4.4   Noted
88
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
R1-062826 Cell Search for E-UTRA TDD Nokia 6.4.4   Not treated
R1-062827 Reference signals for mixed carrier MBMS Nokia 6.5.1   Not treated
UL Reference Signal Structure for E-   Not treated
R1-062828 Nokia 6.5.2
UTRA
Impact of the maximum number of   Noted
R1-062829 codewords on the 4x4 LTE system Nokia 6.6.1
performance
Performance of layer permutation for LTE   Noted
R1-062830 Nokia 6.6.2
SU-MIMO
Open Loop DL Transmit Diversity for   Not treated
R1-062831 Nokia 6.6.4
Common Control Channels
Open Loop DL Transmit Diversity for the   Not treated
R1-062832 Nokia 6.6.4
Shared Data Channel
Linear Precoding for single stream   Not treated
R1-062833 Nokia 6.6.5
transmission from 2TX antennas
UL timing control accuracy and update   Not treated
R1-062834 Nokia 6.7
rate
R1-062835 UL power control Nokia 6.8   Not treated
Initial results for BS PAPR impact of EVM   Not treated
R1-062836 Nokia 6.9
requirements
DL L1/L2 control signaling channel   Not treated
R1-062837 Nokia 6.12.1
encoding structures
R1-062838 Short UE ID for DL L1/L2 control signaling Nokia 6.12.1   Not treated
R1-062839 TDM vs. FDM Downlink Control Signaling Nokia 6.12.1   Not treated
TDM based Multiplexing Schemes   Not treated
R1-062840 Nokia 6.12.2
between L1/L2 Control and UL Data
Multiplexing of L1/L2 Control Signalling   Not treated
R1-062841 Nokia 6.12.2
when UE has no data to transmit
CQI design and its impact of DL 6.12.2   Not treated
R1-062842 Nokia
performance
DL L1/L2 control signaling channel 6.12.1   Not treated
R1-062843 performance: Evaluation of grouped Nokia
coding
SCH structure and 3-step cell search Fujitsu 6.4.4   Not treated
R1-062844
procedure
Initial cell search and long-CP sub-frame Fujitsu 6.4.4   Not treated
R1-062845
structure
R1-062846 E-UTRA physical-layer model Ericsson 6,2   Noted
89
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Ericsson, Samsung,   Noted
R1-062847 L1 multiplexing 6,2
Nokia
Downlink modulation schemes for E-   Agreed
R1-062848 Ericsson 6.3.1
UTRA
R1-062849 Uplink modulation schemes for E-UTRA Ericsson 6.3.1 R1-062951 Revised in R1-062951
On distributed transmission in E-UTRA   Noted
R1-062850 Ericsson 6.3.2
uplink
R1-062851 Frequency hopping for E-UTRA uplink Ericsson 6.3.4   Noted
R1-062852 DFT size for uplink transmissions Ericsson 6.3.4   Not treated
Proposed answers to RAN2 LS on random   Not treated
R1-062853 Ericsson 6.4.3
access
Parameters for basic Random Access   Noted
R1-062854 Ericsson 6.4.3
preamble
R1-062855 DL reference symbols Ericsson 6.5.1   Not treated
R1-062856 UL reference symbols Ericsson 6.5.2 R1-062952 Not treated
R1-062857 Beamforming in E-UTRA Ericsson 6.6.5   Not treated
Further results on transmit diversity for   Not treated
R1-062858 Ericsson 6.6.4
common control and data channels
Maximum number of codewords for MIMO   Noted
R1-062859 Ericsson 6.6.1
in E-UTRA downlink
R1-062860 Timing advance for E-UTRA uplink Ericsson 6.7   Not treated
R1-062861 Uplink Power Control for E-UTRA Ericsson 6.8   Not treated
Downlink Power Control for E-UTRA–   Not treated
R1-062862 Ericsson 6.8
Impact on Standards
R1-062863 Semi-persistent scheduling Ericsson 6.10   Not treated
R1-062864 Scheduling Request in E-UTRAN Ericsson 6.12.1   Not treated
R1-062865 Physical Layer Aspects of Link Adaptation Ericsson 6.11   Not treated
R1-062866 Downlink control signalling Ericsson 6.12.1   Not treated
Uplink non-data-associated control   Not treated
R1-062867 Ericsson 6.12.2
signaling
Uplink non-data-associated control   Not treated
R1-062868 Ericsson 6.12.2
signaling – additional details
R1-062869 Uplink data-associated control signaling Ericsson 6.12.2   Not treated
R1-062870 Physical Layer Measurements - UE Ericsson 6.13.1   Not treated
R1-062871 Physical Layer Measurements - Node B Ericsson 6.13.2   Not treated
R1-062872 UE capabilities Ericsson 6.14   Not treated
E-UTRA Incremental CQI Reporting Using   Not treated
R1-062873 Ericsson 6.6.6
DCT Coding
90
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Summary of email discussion on control   Noted
R1-062874 Ericsson 6,12
signaling
R1-062875 Text capturing RAN1 decision in 36.211 Ericsson 6,1   Withdrawn
Ericsson, Philips,   Noted
R1-062876 HS-SCCH for Rel-7 MIMO 7.1.1
Qualcomm Europe
R1-062877 New MIMO DL signaling Ericsson 7.1.1   Noted
Feedback of antenna weight information   Noted
R1-062878 Ericsson 7.1.2
for D-TxAA
R1-062879 Coding for ACK/NACK in MIMO operation Ericsson 7.1.2   Noted
R1-062880 Higher-order sectorization in E-UTRA Ericsson 6.4.4   Not treated
Proposed modification to align UL DPCCH   Not treated
R1-062881 Nortel 7.2
gating patterns for 2ms and 10 ms TTI
LS on 3GPP SAE&LTE Workplan (To: R1-062948 Not treated
SA1, SA2, SA3, SA4, SA5, RAN1, RAN2,
R1-062882 RAN3, CT1, CT3, CT4, CT6, GERAN1, TSG SA, Ericsson 4
GERAN2, GERAN3, Cc: RAN, CT,
GERAN)
Filtering roll-off for non-synchronized   Not treated
R1-062883 Nokia 6.4.3
transmission
R1-062884 Analysis of HSDPA in CELL_FACH state Nokia 5.3   Noted
Nokia, Ericsson,   Noted
R1-062885 HSDPA MIMO UE categories 7.1
Qualcomm
R1-062886 HS-SCCH for MIMO in UTRA Nokia 7.1.1   Noted
Performance of Different Feedback   Noted
R1-062887 Weight Optimization Strategies and Nokia 7.1.2
Impact on the FBI Signalling
R1-062888 Discussion on some CQI related issues Nokia 7.1.2   Noted
Link results for UL DPCCH gating with   Not treated
R1-062889 different PC step sizes during DPCCH Nokia 7.2
only transmissions
Link results for UL DPCCH transmission   Not treated
R1-062890 Nokia 7.2
burst length in case of 10ms TTI
Downlink synchronisation primitives and   Not treated
uplink power control out-of-
R1-062891 Nokia 7.2
synchronisation handling in case of
discontinuous uplink transmission
  Noted. Discuss and agree a solution over
R1-062892 Compressed mode with CPC Nokia 7.2
email reflector until 20 October
91
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Random access for less-contention-based   Not treated
R1-062893 Fujitsu 6.4.3
handover
R1-062894 UL radio resource use in mixed cells Fujitsu 6.10   Withdrawn
R1-062895 Some issues of VoIP transmission Fujitsu 6.10   Not treated
R1-062896 Draft specification skeleton, 36.201 Ericsson 6.1   Endorsed as 0.1.0 in R1-063005
R1-062897 Draft specification skeleton, 36.211 Ericsson 6.1 R1-062947 Revised in R1-062947
R1-062898 L1 Control signalling Siemens 6.12.1   Not treated
R1-062899 RAN2 questions on RACH operation Siemens 6.4.3   Not treated
R1-062900 Scheduling for VoIP Siemens 6.10   Not treated
Proposal for dedicated pilots in downlink   Not treated
R1-062901 Motorola 6.5.1
precoding for EUTRA MIMO
Maximum number of codewords for E- 6.6.1   Noted
R1-062902 Motorola
UTRA MIMO
R1-062903 E-UTRA Open Loop Transmit Diversity Motorola 6.6.4   Not treated
Frequency Domain Adaptive Precoding for   Not treated
R1-062904 Motorola 6.6.5
E-UTRA MIMO
Additional results on frequency-domain 6.6.5   Not treated
R1-062905 Motorola
adaptive precoding for EUTRA MIMO
Uplink sounding for obtaining channel 6.6.6   Not treated
R1-062906 Motorola
state information at Node B in EUTRA
Direct channel feedback for obtaining   Not treated
R1-062907 channel state information at Node B in Motorola 6.6.6
EUTRA
Mobile Assisted Sounding feedback for   Not treated
R1-062908 Motorola 6.6.6
Multi Antenna System for EUTRA
R1-062909 WCDMA MIMO Downlink Signaling Motorola 7.1.1   Noted
R1-062910 WCDMA MIMO Uplink Signaling Motorola 7.1.2   Noted
LTE Frame Structure for Coherent and Freescale 6.4.4   Not treated
R1-062911
Non-Coherent Cell ID Detection Semiconductor
An Interference Resistant Frame Structure Freescale 6.4.4   Not treated
R1-062912
for Cell ID Detection Semiconductor
R1-062913 LTE BCH - performance analysis IPWireless 6.4.1   Not treated
R1-062914 Required RACH preamble length IPWireless 6.4.3   Noted
UL power control for predictable   Not treated
R1-062915 IPWireless 6.8
interference
R1-062916 Baseline performance of reuse partitioning IPWireless 6.10   Not treated
Overhead for periodic and triggered CQI   Not treated
R1-062917 IPWireless 6.12.2
reporting
92
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
System simulation scenario for large cells   Withdrawn
R1-062918 Vodafone 6
to aid LTE design
Adaptive Control of Roll-off Factor for SC-   Not treated
R1-062919 Siemens 6.3.1
FDMA
R1-062920 E-MBMS LS Discussion Siemens 4   Not treated
R1-062921 Downlink Multiplexing Lucent Technologies 6.2   Noted
Localized vs. Distributed Subcarrier   Noted
R1-062922 Lucent Technologies 6.3.2
Allocation for the SC-FDMA UL
Capacity Analysis of E-UTRA Non- 6.4.3   Not treated
R1-062923 Lucent Technologies
synchronized RACH
R1-062924 On Reference Signals for SC-FDMA Lucent Technologies 6.5.2   Not treated
Link-level results for nonunitary precoding   Noted
R1-062925 Lucent Technologies 6.6.3
using zero-forcing in LOS channels
Considerations for Frequency Control in   Not treated
R1-062926 Lucent Technologies 6.7
E-UTRA Uplink
Lower Layer Signalling for Continuous   Not treated
R1-062927 Lucent Technologies 7.2
Packet Connectivity
On definition and target range for DL   Not treated
R1-062928 Lucent Technologies 6.9
PAPR
Comparison of DL PAPR reduction   Not treated
R1-062929 Lucent Technologies 6.9
methods
eNodeB measurements provided by the   Not treated
R1-062930 Lucent Technologies 6.13.2
physical layer
LTE UE measurements provided by the   Not treated
R1-062931 Lucent Technologies 6.13.1
physical layer
Uplink Scheduling With Inter-Cell Power   Not treated
R1-062932 Control, with Extensions to Interference Lucent Technologies 6.8
Coordination
Intra-Cell Power Control for the E-UTRA   Not treated
R1-062933 Lucent Technologies 6.8
Uplink
  Noted. Discuss and agree a solution over
R1-062934 Length of the Periodic UL DPCCH Burst Ericsson 7.2
email reflector until 20 October
Higher Order Modulation for HSPA –   Noted
R1-062935 Ericsson 7.3
Impact on RAN1 specifications
R1-062936 16QAM for HSUPA - Cubic Metric Ericsson 7.3 R1-062936 Revised in R1-062936
64QAM for HSDPA - Impact of Cell   Noted
R1-062937 Ericsson 7.3
Isolation

93
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
64QAM for HSDPA - Impact of Power   Noted
R1-062938 Ericsson 7.3
Back-Off
16QAM for HSUPA - Impact of Power   Noted
R1-062939 Ericsson 7.3
Back-Off
Effects on throughput when using Layered   Noted
R1-062940 Permutation for LTE-Based RXCVR Broadcom 6.6.2
Structures
Low cost training for transmit antenna Mitsubishi Electric,   Not treated
R1-062941 6.5.2
selection on the uplink NTT DoCoMo
Performance comparison of training   Not treated
Mitsubishi Electric,
R1-062942 schemes for uplink transmit antenna 6.5.2
NTT DoCoMo
selection
R1-062943 Draft specification skeleton, 36.214 Nokia 6.1 R1-062967 Revised in R1-062967
L1/L2 Control Channel Structure with   Not treated
R1-062944 CDM Based Multiplexing in E-UTRA KDDI, NTT DoCoMo 6.12.1
Downlink
Scrambling Code for L1/L2 Control   Not treated
R1-062945 Channel with CDM Based Multiplexing in KDDI 6.12.1
E-UTRA Downlink
R1-062946 SYNC channel email discussion summary Motorola 6.4.4 (R1-062606) Noted
R1-062947 Draft specification skeleton, 36.211 Ericsson 6.1 (R1-062897) Revised in R1-062957
LS on 3GPP SAE&LTE Workplan (To: (R1-062882) Noted
SA1, SA2, SA3, SA4, SA5, RAN1, RAN2,
R1-062948 RAN3, CT1, CT3, CT4, CT6, GERAN1, TSG SA, Ericsson 4
GERAN2, GERAN3, Cc: RAN, CT,
GERAN)
R1-062949 Timing control for UL transmissions Qualcomm Europe 6.7 (R1-062702) Not treated
R1-062950 16QAM for HSUPA - Cubic Metric Ericsson 7.3   Noted
R1-062951 Uplink modulation schemes for E-UTRA Ericsson 6.3.1 (R1-062849) Noted
R1-062952 UL reference symbols Ericsson 6.5.2 (R1-062856) Not treated
R1-062953 Modulation Schemes for E-UTRA uplink Samsung 6.3.1 (R1-062512) Noted
Further Analysis on DCT based CQI LG Electronics Not treated
R1-062954 6.12.2 (R1-062575)
reporting Scheme
R1-062955 Draft Reply LS on VoIP RAB combination Orange 4   Approved in R1-063010
R1-062956 Skeleton of TS36.212 v0.0.1 Qualcomm Europe 6.1 (R1-062684) Endorsed as v0.1.0 in R1-063002
R1-062957 Draft specification skeleton, 36.211 v0.0.1 Ericsson 6.1 (R1-062947) Endorsed as v0.1.0 in R1-063001
R1-062958 Asynchronous RACH Preamble Design Samsung 6.4.3 (R1-062515) Noted

94
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
The numerology of alternative EUTRA CATT, Huawei, ZTE,   Agreed
R1-062959 6.3.3
TDD frame structure RITT
R1-062960 Summary of BCH in 20MHz NEC Group 6.4.1   Not treated
R1-062961 Revised Physical layer model Ericsson 6.2 R1-062973 Revised in R1-062973
Overhead for periodic and triggered CQI (R1-062917) Not treated
R1-062962 IPWireless 6.12.2
reporting
Proposal for DL SYNC Channel (SCH) for (R1-062635) Not treated
R1-062963 Texas Instruments 6.4.4
E-UTRA Cell Search
Cell Search Performance in Tightly (R1-062636) Not treated
R1-062964 Texas Instruments 6.4.4
Synchronized Network for E-UTRA
RACH Design Issues of Large Cell LG Electronics 6.4.3 (R1-062557) Not treated
R1-062965
Deployment
R1-062966 Downlink reference signals Ericsson 6.5.1 R1-063008 Revised in R1-063008
R1-062967 Draft specification skeleton, 36.214 v0.0.1 Nokia 6.1 (R1-062943) Endorsed as v0.1.0 in R1-063003
Qualcomm, Nokia, R1-062988 Revised in R1-062988
25.214 CR0421r2 (Rel-7, B) "Support of Ericsson, Siemens,
R1-062968 7.2
CPC feature" LG Electoronic,
Nortel, Huawei
LCR TDD; Non-Scheduled Traffic and (R1-062587) agreed conditionally
R1-062969 ZTE 8
Scheduled Traffic Transmissions
20ms TTI Co-existence with 5ms TTI for (R1-062588) Noted
R1-062970 E-DCH of LCR TDD: System Level ZTE 8
Simulation Results
LCR TDD: Physical channel structure for (R1-062799) Noted
R1-062971 CATT 8
E-PUCH
[DRAFT] Reply to RAN2 LS on Random-   Approved with modification in R1-062976
R1-062972 Motorola 6.4.3
Access Related Issues
R1-062973 Revised Ericsson Physical layer mode. Ericsson 6.2 (R1-062961) Agreed
Link analysis of layer permutation and no Qualcomm Europe (R1-062697) Noted
R1-062974 6.6.2
layer permutation
R1-062975 MSC levels for E-UTRA MIMO Qualcomm Europe 6.6   Noted
Reply to RAN2 LS on Random-Access   Approved version
R1-062976 RAN WG1 4
Related Issues
Downlink Transmit Diversity Method for (R1-062583) Not treated
R1-062977 ETRI 6.6.4
BCH Channel
25.212 CR0238r2 (Rel-7, B) "Support of Qualcomm, Nokia, R1-062978 Revised in R1-062987
R1-062978 7.2
CPC feature" Ericsson, Siemens

95
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
MIMO DL Reference Signal Design for 4 R1-062993 Revised in R1-062993
R1-062979 Nortel, Motorola 6.5.1
Tx
CATT, RITT,   Agreed
R1-062980 DL-RS-4Tx for EUTRA TDD 6.5.1
Huawei, ZTE
Persistent Scheduling for E-UTRA VoIP (R1-062618) Not treated
R1-062981 Motorola 6.12.1
and Control Channel considerations
E-UTRA DL L1/L2 Control Channel Non- (R1-062622) Not treated
R1-062982 Motorola 6.12.1
Persistent Performance
Ericsson,   Agreed
Qualcomm, Nokia,
Motorola, Freescale,
IPWireless, Nortel,
Siemens, NTT
DoCoMo,
TeliaSonera,
R1-062983 Minimum UE reception capability 6.4.1
Vodafone, Sharp,
Mitsubishi, Toshiba,
Fujitsu, Panasonic,
NEC, Lucent, T-
Mobile,
TelecomItalia,
Alcatel
LS on minimum receiver bandwidth   Noted
R1-062984 RAN WG2 4
capability (To: RAN1, Cc: RAN4)
[DRAFT] Reply LS on minimum receiver   Approved with modification in R1-063006
R1-062985 Ericsson 6.5.1
bandwidth capability
  Agreed conditionally. As CRs to 25.212 and
Philips, Qualcomm,
25.211 CR0230r1 (Rel-7, B) "UL DPCCH 25.214 were agreed in R1-063014 and R1-
R1-062986 Siemens, Ericsson, 7.2
slot format" 063016 on the e-mail refelector afther the
Nokia
meeting, this CR was agreed.
(R1-062978) Agreed in principle pending comments to be
25.212 CR0238r3 (Rel-7, B) "Support of Qualcomm, Nokia,
R1-062987 7.2 reflected on a revision for email approval until
CPC feature" Ericsson, Siemens
20 October +> agreed in R1-063014
Qualcomm, Nokia, (R1-062968) Agreed in principle pending comments to be
25.214 CR0421r3 (Rel-7, B) "Support of Ericsson, Siemens, reflected on a revision for email approval until
R1-062988 7.2
CPC feature" LG Electoronic, 27 October+> agreed in R1-063016
Nortel, Huawei

96
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
Draft LS on status of RAN1 CRs for   Approved in R1-062989
R1-062989 "Continuous Connectivity for Packet Data Siemens 7,2
Users"
Nokia, Ericsson,   Agreed
Siemens, TI, NTT
DoCoMo, Motorola,
Freescale, Institute
for Infocomm
R1-062990 Outcome of cell search drafting session Research, 6.4.4
Panasonic,
Mitsubishi Electronic,
Toshiba, CATT,
NEC, Nortel,
Interdigital
R1-062991 TR25.827v0.2.0 Editor, CATT 8   Endorsed version
LCR TDD; Non-Scheduled Traffic and (R1-062969) Agreed version
R1-062992 ZTE 8
Scheduled Traffic Transmissions
Nortel, Motorola, (R1-062979) Agreed
Samsung, Nokia,
MIMO DL Reference Signal Design for 4
R1-062993 Siemens, Philips, 6.5.1
Tx
LGE, Huawei, ZTE,
NTT DoCoMo
R1-062994 Summary of LTE RACH session NTT DoCoMo 6.4.3   Endorsed
Qualcomm Europe,   Approved in R1-063009
R1-062995 Draft LS on status of Rel-7 FD MIMO Philips, Nokia, 7.1
Ericsson
Qualcomm Europe, (R1-062680) Agreed
Nokia, Philips,
R1-062996 CQI reporting for Rel-7 FDD MIMO Ericsson, Cingular 7.1
Wireless, T Mobile,
Nortel
Qualcomm Europe,   Agreed
Proposed way forward on up- and Nokia, Philips,
R1-062997 downlink signalling in support of Rel-7 Ericsson, Cingular 7.1
FDD MIMO Wireless, T Mobile,
Nortel
TI , NTT DoCoMo,   Noted
R1-062998 DL RS structures for evaluation with 4 Tx 6.5.1
Siemens, Philips

97
3GPP TSG RAN WG1 Meeting #47 R1-063613
Riga, Latvia, 06 – 10 November, 2006
AGENDA REVISED BY
NUMBER TITLE SOURCE Conclusion/decision
ITEM (From)
R1-062999 LTE MIMO session chairman's note Samsung 6.6   Noted
  Approved in R1-063015 with modification on
R1-063000 Draft LS on LCR TDD Enhanced Uplink ZTE 8
the RAN1 reflector.
R1-063001 TS 36.211 v0.1.0 Editor, Ericsson 6.1   Endorsed version
R1-063002 TS 36.212 v0.1.0 Editor, Qualcomm 6.1   Endorsed version
R1-063003 TS 36.214 v0.1.0 Editor, Nokia 6.1   Endorsed version
R1-063004 TS 36.213 v0.1.0 Editor, Motorola 6.1   Endorsed version
R1-063005 TS 36.201 v0.1.0 Editor, Ericsson 6.1   Endorsed version
Reply LS on minimum receiver bandwidth   Approved version
R1-063006 RAN WG1 4
capability
MIMO DL Reference Signal Design for 4   Noted
R1-063007 Qualcomm Europe 6.5.1
Tx Antennas
R1-063008 Downlink reference-signals Ericsson   (R1-062966) Agreed
R1-063009 LS on status of Rel-7 FD MIMO RAN WG1 4   Approved version
R1-063010 Reply LS on VoIP RAB combination RAN WG1 4   Approved version
LS on status of RAN1 CRs for   Approved version
R1-063011 "Continuous Connectivity for Packet Data RAN WG1 4
Users"
R1-063012 LS on E-UTRA physical-layer model RAN WG1 4   Approved version
R1-063013 Approved Report of RAN1#46 MCC  3   Approved version
Qualcomm, Nokia, (R1-062987) Agreed version
25.212 CR0238r4 (Rel-7, B) "Support of
R1-063014 Ericsson, Siemens, 7.2
CPC feature"
Philips
LS on non-Scheduled Traffic and  Approved version
R1-063015 RAN WG1 4
Scheduled Traffic Transmissions
Qualcomm, Nokia, (R1-062988) Revised in R1-063017
25.214 CR0421r4 (Rel-7, B) "Support of
R1-063016 Ericsson, Siemens, 7.2
CPC feature"
Philips

Qualcomm, Nokia, (R1-063016) Agreed version

25.214 CR0421r5 (Rel-7, B) "Support of
R1-063017 Ericsson, Siemens, 7.2
CPC feature"
Philips, Nortel

98
3GPP TSG RAN WG1 Meeting #47
Riga, Latvia, 06 – 10 November, 2006

Annex F: List of actions

1. Evolved UTRA and UTRAN
a. With related to R1-062784, e-mail discussion about the new definition of TTD
b. The need for 1RB in a 1ms TTI, e-mail discussion and if the agreement can be reach
until the next meeting it can be agreed at the next meeting.
c. Regarding RACH procedure, to be continue discussion about 0.5msec case with effect
of frequency error.
d. With related to R1-062785, e-mail discussion about RACH procedure for E-UTRA
TDD.
e. Conference call on LTE MIMO. The schedule will be informed by moderator.
2. Continuous Connectivity for Packet Data Users
a. R1-062987: 25.212 CR0238r3 (Rel-7, B) "Support of CPC feature" E-mail approval
until 20 October.
b. R1-062988: 25.214 CR0238r3 (Rel-7, B) "Support of CPC feature" E-mail approval
until 27 October.
c. R1-062892: Discuss and agree a solution over email reflector until 20 October.
d. R1-062934: Discuss and agree a solution over email reflector until 20 October.
3. HSPA Evolution Scope
a. R1-062673: Discuss on the email reflector as part of the CPC discussion (to be
concluded 20 Oct).
4. 1.28Mcps TTD Enhanced Uplink
a. R1-062970: Reconfirm results with other simulations until next meeting.
b. R1-062898: Continue discussion on the e-mail reflector and reach agreement before
the next meeting.
c. R1-063000: E-mail approval until October 20, Draft LS to inform about conclusion in
R1-062992.
5. The other
a. R1-062884: Continue discussion over e-mail until next meeting.

99