Beruflich Dokumente
Kultur Dokumente
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
3
4
5
6
7
8
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write
protected; it may be altered only by authorized persons. While copies may be printed, it is not recommended.
Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded
as uncontrolled copies.
9
10
11
12
13
14
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of AlcatelLucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information
contained herein confidential, shall disclose the information only to its employees with a need to know, and shall
protect the information from disclosure and dissemination to third parties. Except as expressly authorized in
writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have
received this document in error, please notify the sender and destroy it immediately.
15
16
PUBLICATION HISTORY
09/08/2010
17
18
19
20
21
22
19/02/2010
23
24
25
26
20/11/2009
27
28
29
06/11/2009
30
31
32
33
Takes into account contributions for MIMO aspects only. S-CPICH and VAM not
included.
34
List of contributors:
35
36
37
06/08/2009
38
39
40
41
42
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Page 2/171
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
43
CONTENTS
44
INTRODUCTION............................................................................................................................9
45
1.1
OBJECT ....................................................................................................................................9
46
1.2
FRS ........................................................................................................................................9
47
1.3
48
1.4
49
1.5
50
1.6
51
52
2.1
53
2.2
54
55
3.1
56
3.2
57
3.3
COMPLIANCE MATRIX..............................................................................................................18
58
3.4
59
3.5
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
NBAP....................................................................................................................................22
4.1.1
NBAP new or modified parameters...............................................................................23
4.1.1.1
MIMO Capability (9.2.1.118)..................................................................................... 23
4.1.1.2
MIMO Power Offset For S-CPICH Capability (9.2.2.118) ........................................ 23
4.1.1.3
SixtyfourQAM DL and MIMO Combined Capability (9.2.1.121) ............................... 23
4.1.1.4
MIMO Activation Indicator (9.2.1.119)...................................................................... 24
4.1.1.5
MIMO Mode Indicator (9.2.1.120) ............................................................................ 24
4.1.1.6
MIMO N/M Ratio (9.2.2.96) ...................................................................................... 24
4.1.1.7
HARQ Memory Partitioning (9.2.1.102).................................................................... 24
4.1.1.8
MIMO Pilot Configuration (9.2.2.73) ......................................................................... 25
4.1.1.9
MIMO Pilot Configuration Extension (9.2.2.120) ...................................................... 26
4.1.1.10 Power Offset For Secondary CPICH for MIMO (9.2.2.119) ..................................... 26
4.1.1.11 Precoding Weight Set Restriction (9.2.2.124) .......................................................... 26
4.1.1.12 Tx Diversity on DL Control Channel by MIMO UE capability (9.2.2.121)................. 27
Impacts on NBAP procedures.......................................................................................27
4.1.2
4.1.2.1
Audit Response ........................................................................................................ 27
4.1.2.2
Resource Status Indication....................................................................................... 27
4.1.2.3
Cell Setup ................................................................................................................. 28
4.1.2.4
Cell Reconfiguration ................................................................................................. 28
4.1.2.5
Radio Link Setup ...................................................................................................... 28
4.1.2.6
Radio Link Reconfiguration Prepare ........................................................................ 29
4.1.2.7
Radio Link Addition................................................................................................... 30
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Page 3/171
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
83
84
85
4.1.2.8
S-CPICH Power Management ................................................................................. 30
4.1.2.9
Impacts on MIMO calls when cell MIMO capability is lost........................................ 31
4.2
DELAYS IN MIMO PATHS .........................................................................................................32
86
87
88
4.2.1
Delay adjustment principle ............................................................................................32
4.2.2
Delay adjustment mechanism .......................................................................................32
4.3
SUPPORTED CONFIGURATIONS................................................................................................33
89
90
91
92
93
94
95
96
97
4.3.1
MIMO solution with distributed BTS sector with Paired RRH (Not a commercial
configuration)................................................................................................................................35
4.3.2
MIMO solution with distributed BTS sector with Twin RRH (preliminary) .....................37
4.3.3
MIMO on TRDU.............................................................................................................39
st
4.3.4
STRS2-M on iBTS with adjacent frequencies (Not requested for the 1 commercial
delivery) 40
4.3.5
STRS2-M on iBTS with non adjacent frequencies (not supported) ..............................41
4.3.6
STRS3-M on iBTS (not supported) ...............................................................................42
4.4
ASUMPTIONS AND RESTRICTIONS ............................................................................................42
98
4.5
USES CASES...........................................................................................................................43
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
4.5.1
MIMO Cell Activation/De-activation...............................................................................44
4.5.2
MIMO Cell Setup ...........................................................................................................45
4.5.3
R99/HSPA Cell Setup ...................................................................................................46
4.5.4
MIMO Cell Reconfiguration (S-CPICH Power Offset)...................................................47
4.5.5
MIMO parameters online modification ..........................................................................48
4.5.6
MIMO Cell Delete ..........................................................................................................49
4.5.7
Full RL Setup with MIMO HSDPA (RL-Setup Success case)......................................50
4.5.8
MIMO HSDPA Setup (RL-Setup CCM CallP Failure case) ..........................................51
4.5.9
R99 to MIMO HSDPA Setup (RL-Reconf-Prepare Success case)...............................52
4.5.10 R99 to MIMO HSDPA Setup (RL-Reconf-Commit / Cancel Success cases) ...............53
4.5.11 R99 to MIMO HSDPA Setup (RL-Reconf-Prepare CCM CallP Failure case)...............54
4.5.12 Serving HS-DSCH Modification from MIMO to non MIMO ...........................................55
4.5.13 Serving HS-DSCH Modification from non MIMO to MIMO ...........................................56
4.5.14 MIMO HSDPA Removal (RL Delete case)....................................................................57
4.5.15 MIMO HSDPA Removal (MAC-d Flow Delete case) ....................................................58
4.5.16 PA Failure (MIMO cell) ..................................................................................................59
4.5.17 PA Recovery (MIMO Cell).............................................................................................60
4.5.18 PA Failure (R99 cell) .....................................................................................................61
4.5.19 PA Recovery (R99 Cell) ................................................................................................62
4.5.20 Internal S-CPICH Power offset Reconfiguration (successful case) ..............................63
4.5.21 Internal S-CPICH power offset Reconfiguration (failure case) .....................................64
4.5.22 Internal S-CPICH power offset Reconfiguration (lost of MIMO capability) ...................65
4.5.23 MIMO Cell Setup (Failure case)...................................................................................66
4.6
FUNCTION DISTRIBUTION .........................................................................................................67
123
124
125
126
127
128
129
130
131
132
133
134
135
136
4.6.1
CCM OAM .....................................................................................................................67
4.6.1.1
Parameter Check...................................................................................................... 67
HW Configuration Validation .................................................................................... 68
4.6.1.2
4.6.1.3
NBAP interface and procedure impacts ................................................................... 68
4.6.1.4
SBBLINK routing map .............................................................................................. 70
4.6.1.5
TRM / PA defense .................................................................................................... 73
4.6.1.6
RRH/ TRDU defense ................................................................................................ 74
4.6.1.7
Capacity Licensing ................................................................................................... 75
4.6.1.7.1 additionalRadioPerSector ..................................................................................... 75
4.6.1.7.2 PA Power/ RRH Power......................................................................................... 75
4.6.1.8
get DD: getRadioPowerInfo...................................................................................... 76
4.6.1.9
CCM Call Processing CCM OAM Interaction ........................................................ 76
4.6.1.10 eCEM SLOAM CCM OAM Interaction................................................................... 76
4.6.1.11 Timing alignment ...................................................................................................... 76
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Page 4/171
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
Preliminary
09/08/2010
Page 5/171
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
193
194
195
196
197
198
199
200
201
4.7.4
UA07 FRS 81204 (Dual Cell HSDPA) ........................................................................118
4.7.5
UA08 FRS 104832 (Dual Cell HSDPA Capacity Increase) ........................................118
4.7.6
UA07 FRS 24186 (Common Channel Defense) .........................................................118
4.7.7
UA06 FRS 29808 (PA Power Pooling) .......................................................................118
4.7.8
UA08 FRS 89411 (eCEM HSPA aggregate throughput increase) .............................118
4.7.9
UA07 FRS 34396, 34194 (Automatic Carrier Switch Off)...........................................118
4.7.10 UA07 FRS 81122 (eCEM HSPA aggregate throughput increase) .............................119
4.7.11 FN 74682 BTS Serving RRH2x40W 2100 ..................................................................119
4.8
PERFORMANCE OBJECTIVES AND IMPACTS ............................................................................120
202
203
204
205
206
4.8.1
System performances .................................................................................................120
4.8.2
Dimensioning...............................................................................................................120
4.8.3
Capacity ......................................................................................................................120
4.8.4
Dependability...............................................................................................................120
4.9
SECURITY.............................................................................................................................120
207
INTERFACES ............................................................................................................................121
208
5.1
209
5.2
210
211
212
213
214
215
216
217
218
219
OAM ...........................................................................................................................................128
220
6.1
221
222
223
224
225
226
227
228
229
230
6.1.1
dualPaUsage...............................................................................................................129
6.1.2
vamParameters ...........................................................................................................129
6.1.2.1
vamAmplitudeCoeff ................................................................................................ 130
6.1.2.2
vamPhaseCoeff ...................................................................................................... 131
6.1.3
IsPrecodingWeightSetRestrictionPreferred ................................................................132
6.1.4
nCqiTypeAMCqiRatio..................................................................................................132
6.1.5
hsScchType3SingleStreamSnr ...................................................................................133
6.1.6
hsScchType3DualStreamSnr......................................................................................133
6.1.7
DualCellHsdpaMimoMaxNumberUserEcem...............................................................133
6.2
FAULT MANAGEMENT ............................................................................................................135
231
232
233
6.2.1
Alarms .........................................................................................................................135
6.2.2
Errors Message List ....................................................................................................136
6.3
PERFORMANCE MANAGEMENT ..............................................................................................137
234
235
236
237
238
6.3.1
Counters......................................................................................................................137
Counters for the measurement of the Tx powers ................................................... 137
6.3.1.1
6.3.1.2
Introduction of new UE categories: ........................................................................ 138
6.3.1.3
Counters that shall take into account dual streams for MIMO UEs....................... 138
6.3.1.4
Information concerning Single stream/Dual Stream statistics................................ 139
239
240
O&M PROCEDURES.................................................................................................................141
7
7.1
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Page 6/171
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
241
7.2
242
7.3
243
7.4
244
245
8.1
246
8.2
MS INTERWORKING...............................................................................................................141
247
TOOLS IMPACTS......................................................................................................................142
248
9.1
249
9.2
250
251
9.2.1
9.2.2
252
10
253
11
254
12
ANNEX .......................................................................................................................................147
255
12.1
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
UMT/BTS/DD/028488
02.01 / EN
....................................................................................147
Preliminary
09/08/2010
Page 7/171
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
TABLE OF FIGURES
Figure 1: MIMO operation for HS-PDSCH transmission
Figure 2: VAM Schematic diagram for MIMO cell
Figure 3: MIMO sector using Paired RRH (star or daisy chain)
Figure 4: d2U configuration using Paired RRH STSR2-M in star
Figure 5: d2U configuration using Paired RRH STSR2-M in full daisy chaining
Figure 6: MIMO sector using one Twin RRH (star or daisy chaining)
Figure 7: d2U MIMO configuration using Twin RRH STSR2-M in star
Figure 8: d2U MIMO configuration using Twin RRH STSR2-M in daisy chain
Figure 9: STSR2-M with TRDU
Figure 10: Macro iBTS STSR2-M (adjacent frequencies)
Figure 11: Macro iBTS STSR2-M (non adjacent frequencies)
Figure 12: MIMO solution for iBTS Macro STRS3-M
Figure 13: Generation of S-CPICH in OneChip
Figure 14: Ack/Nack User Info Format (proposal)
Figure 15: PCI/CQI User Info Format (Proposal)
Figure 16: VAM Function
Figure 17: Architectural view of VAM
Figure 18: Block diagram of the VAM Implementation
Figure 19:RE in star. TX diversity
Figure 20 UL Realignment Scenario
Figure 21 Rx Path Sequence modification triggered by UL delay alignment
Figure 22: Delay alignment in modem
Figure 23: MIMO solution for iBTS Macro STRS3-M (not supported)
Figure 24: MIMO solution for iBTS Macro STSR1+1 TX2, RX4 (not supported)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
15
17
35
35
36
37
37
38
39
40
41
42
104
106
110
113
114
115
153
156
161
165
170
171
Page 8/171
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
313
INTRODUCTION
314
1.1 OBJECT
315
316
This document is the functional specification describing the impacts in the iBTS due to the introduction
of the feature: FRS 83984 - MIMO for W-CDMA.
317
1.2 FRS
318
319
320
This document covers iBTS impacts due to introduction of MIMO feature in UA08.0 release.
321
322
Out of scope: OneBTS, MSNB, HSSL RRH since not required with MIMO.
323
324
The document will describe also the constraints linked to the introduction of future feature DC-MIMO DL
(84 Mbps) in longer term deliverables in 2012.
325
326
327
328
This document is intended for iBTS development and integration teams as well as system and RNC
architecture, system integration, engineering and PLM teams.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 9/171
329
330
331
332
333
The targeted Node B configuration for live validation is separated in 2 priorities P1 & P2:
P1: Most expected Configuration: Support with Twin RRH product (2100 MHz).
Twin PA RRH
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
RRH
2x40
F1&2&3
RRH
2x40
F1&2&3
RRH
2x40
F1&2&3
9326 d2U
The current working view is that Twin RRH 2x40 2100MHz will be part of May 2011 deliverables
but not including MIMO functionalities.
At this point, there is no official specifications of the Twin RRH RRH2x40 2100MHz
(See [R15]).
Section 4.3.2 MIMO solution with distributed BTS sector with Twin RRH (preliminary) is
a preliminary description.
The present MIMO FN document does not specify the impact of MIMO configuration with
Twin RRH, but with a pair of RRH equipments (Called Paired RRH) as illustrated in
hereafter figure.
The introduction of Twin RRH in MIMO configuration shall be covered by FN 74682 - BTS
Serving RRH2x40W 2100.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 10/171
355
356
357
358
359
360
361
eCEM
GPSAM
eCEM
TRDU60
TRDU60
eCEM
TRDU60
eCEM
TRDU60
eCEM
TRDU60
eCEM
TRDU60
Network
Interface
362
363
364
365
If xCOB is not available, the configuration is based on a distributed BTS using D2U.
366
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 11/171
367
368
369
370
371
372
373
374
375
376
377
378
379
380
Here are the intermediate integration phases that can be defined in order to de-risk the introduction of
VAM cells, VAMandMIMO cells on RRH/TRDU and Twin RRH configurations.
Integration phases:
Phase_1. De-risk the VAM performances
Phase_2. Control Plane for VAMandMIMO cells on RRH/TRDU
Phase_3. User Plane for VAMandMIMO cells on RRH/TRDU
Phase_4. De-risk Twin RRH User plane with VAM Cells
Phase_5. VAMandMIMO cells on Twin RRH
The table below summarizes the requested partial deliveries and the chosen configurations during the
phases.
Phase
Radio
Board
RRH or
TRDU-60W
(Note 1)
TRDU
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
CPRI
REproxy
RRH2x not
introduced
MODEM
RRH2x not
introduced
Only VAM
added in FPGA
Combiner
All L1
implemented
TRDU
RRH2x not
introduced
All L1
implemented
Twin RRH
Step 1.2
(Note 2)
Twin RRH
Step 2
(Note 2)
RRH2x
introduced
All L1
implemented
RRH2x
introduced
All L1
implemented
SBBLINK
Standard
Paired RRH
configuration
Standard
Paired RRH
configuration
Standard
Paired RRH
configuration
Standard
Paired RRH
configuration
All supported
configurations
Control
Plane
Modified
User
Plane
No change
Cell Type
Modified
No change
VAM
VAMandMIMO
Modified
Modified
VAM
VAMandMIMO
Modified
Modified
VAM
Modified
Modified
VAM
VAMandMIMO
VAM
Note 1: Radio board able to accept long optic fibers in order to test the Tx delay compensation.
Note 2:
Twin RRH Step1:
Official UA8.0 delivery not including MIMO functionalities.
Twin RRH Step1.2:
Modified Step1 version where the 2 AxC downlink containers are connected to the 2 Tx paths
according to the standard paired RRH configuration given in 4.6.1.4 SBBLINK routing map (not
configurable). The alarms, PM counters and power measurements are unchanged compared to
Step1.
Twin RRH Step2:
Official UA8.1 delivery including MIMO functionalities.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 12/171
401
RELATED DOCUMENTS
402
403
404
[A1]
405
406
[A2]
407
408
[A3]
409
410
[A4]
411
412
[A5]
413
414
[A6]
415
416
[A7]
417
418
[A8]
419
420
[A9]
421
422
[A10]
RRC Protocol
3GPP TS 25.331 (V8.10.0)
423
01.08/EN Standard
424
425
[R1]
426
427
428
429
[R2]
Multi-paths Diversity for MIMO (MPD) Advanced Studies team Hassan El Nahas
(2003)
https://wcdma-ll.app.alcatellucent.com/livelink/livelink.exe?func=ll&objId=45065344&objAction=browse&sort=name
430
[R3]
431
432
[R4]
433
434
[R5]
435
436
[R6]
UMTS Channel Element OneChip Plus Message Catalogue for phase 8/UA08
UMT/CE/DD/025272
437
438
[R7]
439
440
Plus
TIER0
Architecture
document
https://wcdma-ll.app.alcatellucent.com/livelink/livelink.exe?func=ll&objId=45574224&objAction=browse
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 13/171
441
442
[R8]
443
[R9]
TN MAC-hs
444
445
[R10]
446
447
[R11]
448
449
[R12]
UMTS Channel Element OneChip Plus Algorithms Specification for Downlink Baseband
transmitter for HSDPA
450
451
452
UMT/CE/DD/026892
[R13]
453
454
457
UMTS Channel Element OneChip Plus and OC-CR Plus Host Software Interface
Manual (HSIM)
UMT/CE/DD/026804 Issue 12.0
[R14]
455
456
[R15]
458
459
460
461
462
463
464
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 14/171
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
FUNCTION OVERVIEW
The general transmitter structure to support MIMO operation for HS-PDSCH transmission is shown in
Figure 1:
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 15/171
497
498
499
500
501
502
BTS and Mobile software are combining these techniques to maximise the quality of transmission in all
radio conditions. In particular, it avoids the BER degradation due to fading.
503
W 2pref are allowed (instead of 4) when only one transport block is preferred by the UE as reported in the
504
505
506
507
508
509
510
511
512
513
514
515
composite PCI/CQI. This mode has been introduced in the standard in order to balance the power onto
the 2 Tx branches in single stream.
OAM BTS Cell Parameter IsPrecodingWeightSetRestrictionPreferred indicates to the RNC whether this
mode is preferred or not by the NodeB.
The NodeB is not able to know whether the MIMO user is finally configured in this mode or not (i.e. no
NBAP IE specified).
The CE shall always decode PCI out of the 4 possible values and reports it to the scheduler.
When IsPrecodingWeightSetRestrictionPreferred=True, the scheduler forces any invalid PCI coming
from the CE to a valid value based on the latest valid PCI received.
See section PCI/CQI reporting of FTS document [A1] for details.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 16/171
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
When deploying MIMO with two transmit antennas, supporting legacy devices by means of transmit
diversity seems to be a natural approach. However, lately there has been some focus on the
performance of open loop transmit diversity, STTD, deployments in real networks. There have been
concerns with the performance in STTD mode for non-MIMO UEs.
An alternative way to deploy MIMO is to utilize the option of having an S-CPICH as a phase reference
for the second antenna. In this case, legacy channels would be transmitted from the first antenna alone.
One drawback with such a solution is that, if separate power amplifiers (PA) are used for the two
transmit antennas; the total power resource is not utilized to its full extent. Non-MIMO traffic will only
utilize half of the available power, while MIMO traffic will utilize the total installed power resource. One
way to overcome this problem would be to use a power balancing network (a.k.a. Virtual Antenna
Mapping). In this way both power amplifiers will be fully utilized even for signals transmitted from the first
antenna.
DPCH
/F-DPCH
MIMO
Stream 1
HS-PDSCH
(Non-MIMO)
P-CPICH
VAM
w1
v11
p1
v1
Common
CCH
w2
PA-1
v12
Virtual
antenna
ports
w3
v21
Physical
antenna
ports
MIMO
Stream 2
v2
w4
p2
PA-2
v22
S-CPICH
557
558
559
P-CPICH and S-CPICH are transmitted from both the antennas simultaneously. It is expected that the
channel impulse response to be the same for both pilots. It helps mitigate the problem for legacy Type-2
or 3 receivers using MMSE equalizer to orthogonalize both channels with same equalization.
560
561
Polarization domain (using co-located X-pol antenna) is relied upon for avoiding peak-null interference
patterns.
562
563
564
j1
a1e
v11 v12
VAM Matrix
=
v21 v22
UMT/BTS/DD/028488
j3
a3e
j2
a2e
j4
a4e
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 17/171
565
566
567
R1
General Requirements
For R7 and MIMO UE : support the 2 way data multiplexing
(DTxAA <> TxAA). Expected max throughput in an optimized
MIMO channel is 2 time cat 10 max performances.
First delivery of the solution could also support cat 19/20 being
treated by the system as cat 17/18.
Rel 8 UE may also support MIMO + 64 QAM capabilities (cat
19/20 full performances)
R&D compliance
statement
Compliant
Compliant
R2
Compliant
R3
Compliant
R4
R5
R6
Compliant
Tx-Div not requested
NA
(RNC feature)
Compliant
UMT/BTS/DD/028488
02.01 / EN
Preliminary
Compliant
Configuration supported:
STSR1-M, STSR2-M
(adjacent frequencies)
STSR3-M
Configuration not
supported:
STSR2-M (non adjacent
frequencies)
STSR3-M Macro IBTS
with MCPA is not
supported
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 18/171
STSR x+y
Compliant
R8
R9
Compliant
R11
Compliant
Compliant
R12
R13
Compliant
R&D compliance
statement
Compliant
Note that the sum of MIMO and DC users per board is 15.
In case a call is setup by a new MIMO capable UE and the
board limit (15) is reached then single transmission mode shall
be configured..
R14
N/A
569
Requirement #
R16
R&D compliance
statement
Compliant
R17
UMT/BTS/DD/028488
02.01 / EN
Preliminary
Compliant
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 19/171
R18
570
Requirement #
Counter Requirements
Estimation of number of stream / TTI usage : may help to
identify the (2*2 scheme) MIMO contribution on cell edge
improvement;
R19
R&D compliance
statement
Compliant
571
Requirement #
R20
R&D compliance
statement
Compliant
572
RequireConfiguration Management and Parameter Requirements
ment #
R21
Activation of the feature at NodeB (per cell) and RNC.
WIPS tool modified to check the consistency between MIMO
R22
activation and HW available + configuration on MIMO channels.
R&D compliance
statement
Compliant
NA
(WIPS feature)
Requirement #
R&D compliance
statement
Compliant
573
Billing Requirements
MIMO shall be handled by feature licensing
Capacity licensing shall consider 2 HSDPA connections used
per MIMO UE
R23
574
Requirement #
Serviceability Requirements
R&D compliance
statement
R&D compliance
statement
None
575
Requirement #
R23
None
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
This hypothesis is not restricting or constraining since the RNC can configure the second or third carrier
in MIMO.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 20/171
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 21/171
614
FUNCTIONAL DESCRIPTION
615
616
617
618
619
620
MIMO shall be supported in iBTS on eCEM boards. Support on xCEM is not feasible due to lack of
FPGA resources.
Maximum throughput achievable with MIMO is feasible only with IP transport solution and then requires
xCCM or eCCM.
MIMO feature is compliant with 3GPP Release-8 September, 2009 specifications and thus, will support
corresponding ASN.1 format. Feature can be activated/de-activated per local cell in iBTS.
621
622
623
624
625
626
627
628
629
7. Handling of modified HS-DPCCH format, handling of HS-SCCH type 3 and MIMO Transmission
in Layer 1 & 2
630
8. Counter Management
631
632
633
634
OAM modules in controller and modem boards are impacted to take care of activation/de-activation of
the feature, control and reporting of MIMO capability to RNC, validation of different configurations and
parameters as per requirements/constraints of MIMO and finally delay adjustments in modem boards
and radio modules for controlling timing alignment.
635
636
Call processing modules in controller and modem boards are impacted to support NBAP evolutions for
MIMO, evolution of load balancing algorithm and counters management for MIMO.
637
638
Radio modules (xTRM, TRDU and CPRI RRH) are impacted to take care of timing alignments (delay
adjustments).
639
640
641
Layer 1 & 2 in modem boards is impacted to support MIMO MAC-ehs scheduler evolutions, handling of
new HS-DPCCH format, handling of HS-SCCH type 3 and transmission of one or two transport blocks
per TTI to a UE and counters management for MIMO.
642
4.1 NBAP
643
644
645
646
647
648
649
650
651
652
653
654
655
For this feature the following new NBAP parameters are introduced:
(9.2.1.118) MIMO Capability
(9.2.2.118) MIMO Power Offset For S-CPICH Capability
(9.2.1.121) SixtyfourQAM DL and MIMO Combined Capability
(9.2.1.119) MIMO Activation Indicator
(9.2.1.120) MIMO Mode Indicator
(9.2.2.96) MIMO N/M Ratio
(9.2.1.102) HARQ Memory Partitioning
(9.2.2.73) MIMO Pilot Configuration
(9.2.2.120) MIMO Pilot Configuration Extension
(9.2.2.119) Power Offset For Secondary CPICH for MIMO
(9.2.2.124) Precoding Weight Set Restriction
They are described more in details in the following sections.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 22/171
656
657
4.1.1.1
658
659
This parameter defined the capability of the Local Cell to support MIMO
IE/Group Name
Presence
Range
MIMO Capability
660
661
662
663
664
665
4.1.1.2
IE Type and
Reference
ENUMERATED
(MIMO Capable,
MIMO Non-Capable)
Semantics Description
666
IE/Group Name
Presence
Range
IE Type and
Reference
Semantics Description
ENUMERATED
(S-CPICH Power
Offset Capable,
S-CPICH Power
Offset Not
Capable)
667
668
669
670
671
672
4.1.1.3
673
674
This parameter defines the SixtyfourQAM downlink and MIMO combined capability for a Local Cell.
IE/Group Name
Presence
Range
675
676
677
678
679
IE Type and
Reference
ENUMERATED
(SixtyfourQAM DL
and MIMO
Combined
Capable,
SixtyfourQAM DL
and MIMO
Combined NonCapable)
Semantics Description
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 23/171
680
4.1.1.4
681
682
683
684
685
686
687
688
689
690
691
692
Presence
Range
IE Type and
Reference
NULL
693
4.1.1.5
694
695
IE/Group Name
Presence
Range
696
697
698
699
700
701
702
Semantics Description
IE Type and
Reference
ENUMERATED
(Activate,
Deactivate)
Semantics Description
703
4.1.1.6
704
705
This parameter indicates which UE reporting configuration (N/M ratio) NodeB has decided to use.
IE/Group Name
MIMO N/M Ratio
706
707
708
709
710
711
712
713
Presence
Range
IE Type and
Reference
ENUMERATED (1/2,
2/3, 3/4, 4/5, 5/6,
6/7, 7/8, 8/9, 9/10,
1/1,)
Semantics Description
4.1.1.7
IE/Group Name
UMT/BTS/DD/028488
Presence
Range
02.01 / EN
IE Type and
Reference
Preliminary
Semantics
Description
Criticality
Assigned
Criticality
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 24/171
>Explicit
>>HARQ Memory Partitioning
Information
714
715
716
717
718
719
720
721
INTEGER
(1..8,...12,14,16)
1..<maxno
ofHARQpr
ocesses>
9.2.1.49D
0, 4, 6 or 8
9.2.1.49D
For HARQ
process IDs going
from 0 to
"Number of
Processes" 1
the Total number
of soft channel
bits [33] is
partitioned
equally between
all HARQ
processes
according to the
rules in [18].
GLOBAL
Ignore
722
4.1.1.8
723
724
This parameter indicates which Pilot Configuration shall be used when MIMO is configured in the cell.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 25/171
IE/Group Name
CHOICE Pilot Configuration
>Primary and Secondary
CPICH
>>Associated Secondary
CPICH
>Normal and Diversity
Primary CPICH
Presence
Range
IE Type and
Reference
Semantics Description
Common Physical
Channel ID 9.2.1.13
NULL
725
726
727
728
729
4.1.1.9
730
IE/Group Name
CHOICE Pilot Configuration
>Primary and Secondary
CPICH
>> Power Offset For
Secondary CPICH for
MIMO
>Normal and Diversity
Primary CPICH
Presence
Range
IE Type and
Reference
Semantics Description
9.2.2.119
NULL
731
732
733
734
735
736
4.1.1.10
737
738
739
740
The Power Offset For S-CPICH for MIMO IE indicates the relative transmit power of the S-CPICH
compared to the primary CPICH transmit power, when S-CPICH is used as a phase reference for a
second transmit antenna in MIMO mode.
IE/Group Name
Presence
Range
IE Type and
Reference
INTEGER(-6 .. 0)
Semantics Description
Offset in dB
741
742
743
744
745
746
4.1.1.11
747
748
This parameter defines the preferred Precoding Weight Set Restriction configuration.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 26/171
IE/Group Name
Presence
Range
749
750
751
752
753
754
755
756
IE Type and
Reference
ENUMERATED
(Preferred, Not
Preferred)
Semantics Description
757
4.1.1.12
758
759
760
The following optional IE shall not be used because TxD functionality is not supported this MIMO
release on iBTS.
IE/Group Name
Pres
ence
Range
TX Diversity on DL Control
Channels by MIMO UE
Capability
Semantics
Description
ENUMERATED (
761
762
763
764
765
766
767
4.1.2.1
768
769
770
771
772
773
774
775
776
777
4.1.2.2
778
779
780
781
782
If a Local Cell is MIMO-capable when it becomes existing, then the Node B shall include:
the MIMO Capability IE set to "MIMO Capable"
SixtyfourQAM DL and MIMO Combined Capability IE set to "SixtyfourQAM DL and MIMO
Combined Capable" (64QAM is always supported on eCEM) and
MIMO Power Offset For S-CPICH Capability IE set to "S-CPICH Power Offset Capable
Audit Response
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 27/171
783
784
785
786
787
788
789
790
Precoding Weight Set Restriction set to Preferred (resp. Not_Preferred) if OMC parameter
IsprecodingWeightSetRestriction is True (resp. False).
791
4.1.2.3
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
The RNC sends a CELL SET UP REQUEST message with MIMO to iBTS only on FDD cells that the
iBTS has declared as MIMO capable.
Err_Mess 4.1.2.3-2
If the Secondary CPICH Information IE is included in the CELL SETUP REQUEST message and the
Local Cell associated is not MIMO Capable, then the NodeB shall reject by sending a CELL SETUP
FAILURE with cause MIMO not available
812
4.1.2.4
813
814
815
816
817
818
819
820
821
822
823
824
825
If the MIMO Pilot Configuration IE is included in the CELL RECONFIGURATION REQUEST message
and the Local Cell associated is MIMO Capable, then the parameters defining the pilot configuration for
MIMO shall be stored in the Node B and applied when MIMO mode is used.
Err_Mess 4.1.2.4-1
If the MIMO Pilot Configuration IE or the MIMO Pilot Configuration Extension IE is included in the CELL
RECONFIGURATION REQUEST message and the Local Cell associated is not MIMO Capable, then
the NodeB shall reject by sending a CELL RECONFIGURATION FAILURE with cause MIMO not
available
826
4.1.2.5
827
828
829
830
831
If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B
shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE
reporting configuration (N/M ratio) for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD
Information Response IE in the RADIO LINK SETUP RESPONSE message.
Cell Setup
If the MIMO Pilot Configuration IE is included in the CELL SETUP REQUEST message and the Local
Cell associated is MIMO Capable, then the parameters defining the pilot configuration for MIMO shall be
stored in the Node B and applied when MIMO mode is used.
If the MIMO Pilot Configuration Extension IE is included in the CELL SETUP REQUEST message and
the Local Cell associated is MIMO Capable, then the parameters defining the pilot configuration for
MIMO shall be stored in the Node B and applied when MIMO mode is used
Err_Mess 4.1.2.3-1
If the MIMO Pilot Configuration IE or the MIMO Pilot Configuration Extension IE is included in the CELL
SETUP REQUEST message and the Local Cell associated is not MIMO Capable, then the NodeB shall
reject by sending a CELL SETUP FAILURE with cause MIMO not available
Cell Reconfiguration
If the MIMO Pilot Configuration Extension IE is included in the CELL RECONFIGURATION REQUEST
message and the Local Cell associated is MIMO Capable, then the parameters defining the pilot
configuration for MIMO shall be stored in the Node B and applied when MIMO mode is used
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 28/171
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
If the HS-DSCH Information IE is present in the RADIO LINK SETUP REQUEST message, the Node B
shall include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information Response IE in the
RADIO LINK SETUP RESPONSE message. The HARQ Memory Partitioning IE shall contain the
Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE is included in
the HS-DSCH Information IE.
848
4.1.2.6
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
HS-DSCH Setup:
If the HS-DSCH Information IE is present in the RADIO LINK RECONFIGURATION PREPARE
message, then the Node B shall include the HARQ Memory Partitioning IE in the HS-DSCH FDD
Information Response IE in the RADIO LINK RECONFIGURATION READY message. The HARQ
Memory Partitioning IE shall contain the Number of Processes IE set to a value higher than "8", if the
MIMO Activation Indicator IE is included in the HS-DSCH Information IE.
Err_Mess 4.1.2.5-1
If the RADIO LINK SETUP REQUEST message contains the MIMO Activation Indicator IE and/or
Sixtyfour QAM Usage Allowed Indicator IE set to "Allowed", but does not contain the HS-DSCH MAC-d
PDU Size Format IE set to "Flexible MAC-d PDU Size", then the Node B shall reject the procedure
using the RADIO LINK SETUP FAILURE message with Protocol Cause set to Semantic error
Err_Mess 4.1.2.5-2
If the RADIO LINK SETUP REQUEST message contains the MIMO Activation Indicator IE and an
additional HS cell Information RL Setup IE, then the NodeB shal reject the procedure using the RADIO
LINK SETUP FAILURE message with cause MIMO not available.
If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B
shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE
reporting configuration (N/M ratio) for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD
Information Response IE in the RADIO LINK RECONFIGURATION READY message.
Intra-Node B Serving HS-DSCH Radio Link Change:
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-PDSCH RL ID IE, this
indicates the new Serving HS-DSCH Radio Link:
In the new configuration the Node B shall de-allocate the HS-PDSCH resources of the old
Serving HS-PDSCH Radio Link and allocate the HS-PDSCH resources for the new Serving
HS-PDSCH Radio Link.
The Node B may include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information
Response IE in the RADIO LINK RECONFIGURATION READY message. The HARQ
Memory Partitioning IE may contain the Number of Processes IE set to a value higher than
"8".
HS-DSCH Modification:
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Information To
Modify IE, then:
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Physical
Layer Category IE in the HS-DSCH Information To Modify IE, the Node B shall use this
information in the new configuration and may include the HARQ Memory Partitioning IE in the
RADIO LINK RECONFIGURATION READY message. The HARQ Memory Partitioning IE may
contain the Number of Processes IE set to a value higher than "8".
If the MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then the
Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance
with the MIMO Mode Indicator IE.
If the MIMO Mode Indicator IE is set to "Activate", then the Node B shall decide the UE
reporting configuration (N/M ratio) for MIMO and include the MIMO N/M Ratio IE in the HS-
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 29/171
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
4.1.2.7
902
903
904
905
Err_Mess 4.1.2.7-1
The HS-DSCH FDD information IE in the RL Addition Request is not supported by the Node B. If
present in Radio Link Addition Request message the Node B shall answer with a Radio Link Addition
Failure with cause Requested configuration not supported (existing behavior already implemented).
906
4.1.2.8
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
3GPP CR R1-092912 discusses the impact of MIMO activation on non-MIMO UEs where it is shown
that the non-MIMO UEs experience a performance degradation due the presence of two downlink
transmit antennas.
In order to reduce the MIMO impact on legacy UEs and to co-exist with MIMO UEs that use the PCPICH and S-CPICH, 3GPP proposed using different power offset for the S-CPICH configured for
MIMO
NodeB shall be capable of applying different power offsets (w.r.t. P-CPICH) to S-CPICH in MIMO mode
and in non-MIMO mode. This means the configured S-CPICH will be transmitted with different power
depending upon whether there is any UE in MIMO mode in the cell.
RNC communicates in NBAP CellSetupRequest/CellReconfigurationRequest messages the power
offsets (w.r.t. P-CPICH) to be used for S-CPICH depending on presence of any UE in MIMO mode:
IE Secondary CPICH Information with IE Secondary CPICH Power. This power offset is to be
applied when there is no UE in the cell in MIMO mode.
IE MIMO Pilot Configuration extension with IE Power Offset For Secondary CPICH for MIMO.
This power offset is to be applied when there is at least one UE in the cell in MIMO mode.
CCM CallP shall save the two S-CPICH power offset Secondary CPICH Power and Power Offset For
Secondary CPICH for MIMO received in Cell Setup Request or Cell Reconfiguration request messages
from RNC.
eCEM does not manage the IE MIMO Pilot Configuration Extension. It is up to CCM CallP to provide
the IE Secondary CPICH Power filled with the right S-CPICH power depending upon whether there is
any UE in MIMO mode in the cell by using the S-CPICH power offset reconfiguration procedure (see
section 4.6.2.3).
In case of lost of MIMO capability in a cell this is indicated by CCM OAM to RNC using RSI-SI message
and to CCM CallP using OMIU_MODIFY_LOCAL_CELL_REQ message with MIMO activation = false.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 30/171
937
938
CCM CallP shall keep untouched the S-CPICH configuration but reconfigured the S-CPICH power to
the minimum value using the S-CPICH power offset reconfiguration procedure (see section 4.6.2.3).
939
4.1.2.9
940
941
942
943
944
945
946
947
948
949
950
951
In case of lost of MIMO capability (PA failure for example) the impact on MIMO calls is expected only
due to available power reduction. This can be minimal depending upon cell load.
Since MIMO UEs are still enabling HSDPA in MIMO mode, the NodeB shall continue scheduling the
MIMO UEs using HSDPA/MIMO control signalling (HS-SCCH Type 3 and HS-DPCCH/MIMO) according
to their channel conditions even if MIMO capability in the cell was lost.
No impact also on calls in progress (RL Setup request, RL Reconfiguration Request) which will be
setup, reconfigured as MIMO calls.
It is up to the RNC to reconfigure or not the call to non MIMO (RNC behaviour is out of the scope of this
document).
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 31/171
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
The delay will be compensated in modems and in the RRH for the dBTS + RRH or dBTS + TRDU
solutions. The integer part of delay is compensated in modem, and the fractional part is compensated in
RRH.
The delay of each MIMO path in DL will be compensated in modems and TRM for the TRM+MCPA
+DDM solution. There is no compensation needed in UL as the two Rx path used the same DDM.
More details in delay adjustment mechanism can be found in section 12.1
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 32/171
981
MIMO
Not supported
Number of
sectors
6 sectors
Priority
TX diversity
(MCPA,
Twin_RRH, RRH,
TRDU)
2 TX paths
RX diversity
(DDM,
Twin_RRH, RRH,
TRDU)
2 RX paths
MCPA
Cajun MCPA
MCPA mixity
Mixity of TRDU +
MCPA is not,
supported
Transceivers
(TRM) in iBTS
st
Not for 1
Commercial
delivery
TRM, iTRM
xTRM, xTRM2.
xTRM, xTRM2 mixity is supported
Not for 1
Commercial
delivery
Modems
eCEM, eCEM-U,
Controllers
RRH 2020
Not required,
Not supported
st
P1
CPRI RRH
Not a
commercial
requirement.
See Note.
P2: TRDU60-21
CPRI RRH
(single PA)
4RX on 4 antennas
TRDU
Repeaters
RRH in repeater
mode
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 33/171
MIMO
Not supported
iBTS macro
cabinets
STSR3-M Macro
IBTS with MCPA
is not supported
Distributed BTS
configurations
MSNB
(dBTS + C-MSR )
is not supported
(not required)
982
983
984
MIMO
Supported
Priority
P2
if xCOB is
available
P2 if xCOB is
not available
Note: Only one type and model of RRH is selected for the temporary Paired RRH configuration. The
type and model the closest to the Twin RRH will to be chosen.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 34/171
985
986
987
988
989
990
991
992
993
994
995
996
4.3.1 MIMO solution with distributed BTS sector with Paired RRH (Not a
commercial configuration)
The following MIMO configuration will be developed as an intermediate configuration while Twin RRH is
not available. See section 4.3 Supported Configurations.
Only one type of RRH shall be used, the closest to Twin RRH.
Only configuration in star shall be used as described on below, this configuration being similar to the
Twin RRH configuration.
One MIMO sector is built with one pair of RRHs, since the CPRI RRH has one PA and 2 RX paths
(Main and Div).
Antenna #2
Antenna #1
One sector
Main
Div
Main
RRH n
Duplexor Duplexor
TX
path=
TX
Main
f1, f2
TX
path=
TX Div
2nd RX
path
unused
BB Processing
(i/d)BTS
997
998
1st RX
path
=
RX Div
f1, f2
f1, f2
BB Processing
E
RRH n+1
Duplexor Duplexor
1st RX
2nd RX
path
path
=
RX Main
unused
f1, f2
Div
Daisy chaining
Short connection
RRH 11
RRH 12
Fiber 1
d2U
Fiber 2
RRH 21
RRH 22
Fiber 3
RRH 31
999
1000
1001
1002
RRH 32
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 35/171
1003
1004
1005
1006
The two Main antennas of RRH are associated in the UTRAN system through the
antennaAccessId parameter, as in the x+y feature.
Example: Paired RRH11 / RRH12 is associated to sector1 (, ).
Not required
RRH 12
Fiber 1
RRH 11
Fiber 1
d2U
RRH 14
RRH 13
Fiber 1
1007
1008
1009
1010
1011
1012
1013
1014
RRH 15
RRH 16
Figure 5: d2U configuration using Paired RRH STSR2-M in full daisy chaining
This architecture is derived from the STSR x+y feature in daisy chaining.
The 2 RRH serving a MIMO sector are consecutive in the daisy chain.
Example: paired RRH (RRH13, 14) is associated to sector2 (, ).
This dBTS+RRH architecture supports STRS2-M and STRS3-M configurations if RRH have a
capability of transmitting 3 carriers.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 36/171
1015
4.3.2 MIMO solution with distributed BTS sector with Twin RRH (preliminary)
1017
1018
1019
1020
1021
1022
The basic MIMO solution shall be developped for the dBTS+CPRI Twin RRH architecture.
One MIMO sector is built with one Twin RRH in 2T2R configuration as shown in the following figure.
As the CPRI Twin RRH has two PAs, and 2 RX paths (Main and Div) per PA, one MIMO sector can be
built with one Twin RRH.
STRS3-M configurations are supported if the Twin RRH has the capability of transmitting 3 carriers.
Div Antenna
(Ant #2)
Main Antenna
(Ant #1)
1016
1023
1024
1025
1026
Figure 6: MIMO sector using one Twin RRH (star or daisy chaining)
Fiber 1
Twin RRH 1
d2U
Fiber 2
Fiber 3
Twin RRH 2
1027
1028
1029
1030
1031
1032
Twin RRH 3
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 37/171
Fiber 1
Fiber 1
Fiber 1
d2U
Twin RRH 1
1033
1034
1035
1036
1037
1038
Twin RRH 2
Twin RRH 3
Figure 8: d2U MIMO configuration using Twin RRH STSR2-M in daisy chain
This architecture is derived from the Paired RRH in daisy chain configuration with STSR x+y
feature, each paired RRH being replaced with one Twin RRH.
Example: Twin RRH 1 is associated to sector1 (, ).
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 38/171
1039
1040
1041
1042
1043
MIMO solutions with TRDU are similar to MIMO solutions with RRH described in the previous
paragraph.
This solution is illustrated on the next figure for STSR2 MIMO sector with 6 TRDU in star
Main
Div
Main
Div
Main
Div
Main
Div
Same
Main
Div
antennaAccessId
Main
Div
Same
Duplexor
Duplexor
Duplexor
Duplexor
antennaAccessId
Same
Duplexor
Duplexor
Duplexor
antennaAccessId Duplexor
Duplexor
Duplexor
Duplexor
Duplexor
TX
RX
TX
RX
pathTX
pathRX
RX
pathTX
pathRX
RX
=pathTX
=pathRX pathRX
=pathTX
=pathRX pathRX
TX Div=path RX Div
=path unused
pathRX
TX Main
=path RX Main
=path unused
pathRX
f1,TXf2Div=
f1,RX
f2 Div
unused
=
path
f1,
f1,
TXf2
Main
RXf2Main
unused
=
=
path
f1,TXf2Div
f1,RX
f2 Div
unused
f1,
f1,
TXf2
Main
RXf2Main
unused
f1, f2
f1, f2
f1, f2
f1, f2
TRDU n
TRDU n
TRDU n
One sector
One sector
One sector
TRDU n+1
TRDU n+1
TRDU m
(i/d)BTS
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 39/171
1066
1067
4.3.4 STRS2-M on iBTS with adjacent frequencies (Not requested for the 1st
commercial delivery)
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
This architecture is derived from the classical STSR2 iBTS architecture where the two frequencies are
adjacent.
A second xTRM is added to generate the TX div signals to the three sectors.
3 MCPA are added to have two MCPA per sector.
6 Rx
signals
iBTS
Div
Main
xTRM
eCEM
f1,f2
TX f1, f2 Main
Rx f1, f2 Main,
Div
xCCM
f1,f2 Main
MCPA
f1,f2 Div
DDM
MCPA
HSSPC
MCPA
DDM
MCPA
xTRM
TX f1, f2 Div
No RX
processed
MCPA
signals
f1, f2 are adjacent
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 40/171
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
If frequencies are not adjacent (operator spectrum constraint), a possible architecture is:
Since one xTRM processes only one frequency in reception, f1, and f2 may be not adjacent.
Support of this configuration would correspond to a new development to enforce RX paths allocation on
both xTRM. It is not a nominal behaviour as the behaviour of figure Figure
In case of xTRM failure, the reconfiguration scenario of this configuration would be a new software
behaviour to develop.
This configuration is not supported.
iBTS
6 Rx
signals
Div
Main
f1,f2 Main
MCPA
f1,f2 Div
xTRM
DDM
eCEM
TX f1, f2 Main
Rx f1 Main, Div
MCPA
MCPA
HSSPC
xCCM
DDM
MCPA
xTRM
TX f1, f2 Div
Rx f2 Main, Div
No
or
p
p
su
MCPA
ed
DDM
MCPA
6 Rx
signals
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 41/171
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
The iBTS is currently limited to 2xTRM due to the TRM mastership algorithm to manage the DDM and
their RF cabling findings. This limitation should be extended. Consequently, the TRM mastership
function and RF cabling test should be reworked to allow 3xTRMs.
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
FRS 81204 Dual Cell HSDPA is a pre-requisite for the development of MIMO.
The functional dependencies concern the following aspects:
Common OAM parameter DualCellHsdpaMimoMaxNumberUserEcem: it is assumed that this
parameter was already introduced by DualCell feature.
Common L1/PQ3 interface: Is is assumed that the interface is partially compliant (i.e. includes
parameters for DualCell)
iBTS
6 Rx
signals
Div
Main
xTRM
TX M f1, f2, f3 S1,
TX D f1, f2, f3 S1
Rx MD f1 S1S2S3
eCEM
p
su
t
No
d
rt e
o
p
HSSPC
xCCM
xTRM
TX M f1, f2, f3 S2,
TX D f1, f2, f3 S2
Rx MD f2 S1S2S3
f1,f2,f3 Main
f1,f2,f3
Main MCPA
f1,f2,f3 Div
DDM
f1,f2,f3
Div MCPA
MCPA
DDM
MCPA
xTRM
TX D f1, f2, f3 S3
TX D f1, f2, f3 S3
RxMD f3 S1,S2,S3
MCPA
DDM
MCPA
MIMO is supported on BTS equipped with eCEM boards (ie: no mixity with ix/CEM). Before introducing
MIMO in an existing site i/xCEM boards shall be replaced by eCEM boards.
With MIMO only 3 sectors are supported (see section 4.3)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 42/171
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
A MIMO user is at first an HSDPA user. Introduction of MIMO does not change deeply the CallP
scenarios to establish, reconfigure or delete a MIMO call compare to an HSDPA call.
This section will highlight mainly uses cases which are interesting to understand MIMO aspects but is
not exhaustive. For example the call scenario where DCH part and HSPA part are not collocated is not
depicted as not adding value compare to co-located case in the context of MIMO.
eCEM SLOAM acts only as a relay between CCM OAM and eCEM PQ2 CallP and then it is not
represented to simplify the uses cases.
For MIMO calls uses cases the exchanges between eCEM/PQ3 and eCEM CE do not change
compared to what is done for a non MIMO call (HSDPA call) so to avoid overloading of the figures this
is not represented.
To simplify uses cases
its associated RESPONSE.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 43/171
1210
CCM OAM
Inform CCM CallP
about MIMO cell
capability of a cell
that is reported to
RNC.
CCM CallP
OMIU_ADD_LOCAL_CELL_REQ
(Cell 1, MIMOActivation=true)
OMIU_ADD_LOCAL_CELL_ACK
OMIU_MODIFY_LOCAL_CELL_REQ
(Cell 1, MIMOActivation=false)
OMIU_MODIFY_LOCAL_CELL_ACK
- Store the
information regarding
MIMO in the cell
context of Cell 1.
1211
1212
1213
1214
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 44/171
1215
1216
1217
eCEM CE
CCM OAM
CCM CallP
eCEM PQ2 CallP
eCEM PQ3
1218
Local Cell Config Req (VamEnabled, VAM Coeff,
1219
Store
IsPrecodingWeightSetRestriction)
1220
InternalDualPaUsage
& VAM coefficients
1221
Local Cell Config Resp
1222
1223
OMIU_ADD_LOCAL_CELL_REQ
1224
MIMOActivation=true)
1225
OMIU_ADD_LOCAL_CELL_ACK
1226
1227 RSI-SI (MIMO capable, MaxTxpower = min(PA1, PA2) + 3dBm)
1228
1229
Cell Setup
Program VAM
1230
Request
enabled in FPGA
Cell Setup Request
(MIMO
1231
Combiner
Cell
Setup
Request
S-CPICH
(MIMO,
1232
UcuMgrCellCreateReq
)
S-CPICH
1233
(VamEnabled, VAM Coeff
MaxTxpower =
Take into account
MaxTxPower,
PA1 + PA2)
1234
InternalDualPaUsage
IsPrecodingWeightSetRestriction CellConfigReq
1235
& VAM coefficients
1236
UcuMgrCellCreateRsp
1237
psbCellSetupReq
1238
SCH Setup
(S-CPICH)
1239
1240
P-CPICH Setup
1241
1242
S-CPICH Setup
1243
psbCellSetupRsp
1244
Cell Setup Response
Cell Setup Response
1245
TRM2
TRM1
1246
Cell Setup Response
1247
Cell_config_req (MaxTxpower/2)
1248
1249
Cell_config_req (MaxTxpower/2)
1250
1251
1252
1253
Hsdpa Config Req (MIMO parameters)
Hsdpa Config Resp
PSCR Request
PSCR Request
Store MIMO
parameters
Take into
account
MaxTxPower
from Cell Setup
PSCR Request
HsdpaPhyShareChannelSetupReq
CellConfigReq
HsdpaPhyShareChannelSetupRsp
PSCR Response
PSCR Response
PSCR Response
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 45/171
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
CCM CallP
eCEM CE
eCEM PQ3
Store
InternalDualPaUsage
& VAM coefficients
OMIU_ADD_LOCAL_CELL_REQ
MIMOActivation=false)
OMIU_ADD_LOCAL_CELL_ACK
RSI-SI (MaxTxpower = min(PA1, PA2) + 3dBm)
Cell Setup Request
Cell Setup Request
MaxTxpower =
PA1 + PA2)
Program VAM
enabled in FPGA
Combiner
CellConfigReq
UcuMgrCellCreateRsp
psbCellSetupReq
SCH Setup
P-CPICH Setup
psbCellSetupRsp
Cell Setup Response
Cell Setup Response
TRM1
TRM2
PSCR Request
PSCR Request
Take into
account
MaxTxPower
from Cell Setup
PSCR Request
HsdpaPhyShareChannelSetupReq
CellConfigReq
HsdpaPhyShareChannelSetupRsp
PSCR Response
PSCR Response
PSCR Response
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 46/171
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
CCM CallP
eCEM CE
eCEM PQ3
psbCellReconfReq
S-CPICH Reconf
psbCellReconfRsp
Failure case
PA failure
OMIU_MODIFY_LOCAL_CELL_ACK
Cell Reconf Request
Cell Reconf Request
(S-CPICH Power Offset)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 47/171
1327
1328
CCM OAM
CCM CallP
eCEM CE
eCEM PQ3
From OMC-B
TEE(SET:BtsCell:VAMparameters, PrecodingWeightSetRestriction )
REE(SET:OK)
Local Cell Config Req (VAM Coeff, PrecodingWeightSetRestriction,)
Store
InternalDualPaUsage
& VAM coefficients
Update VAM
parameters in
FPGA Combiner
UcuMgrCellUpdateReq
(VAM Coeff,) PrecodingWeightSetRestriction
UcuMgrCellUpdateRsp
From OMC-B
TEE(SET:Bts:HsdpaConf:nCqiTypeAMCqiRatio )
REE(SET:OK)
Hsdpa Config Req (nCqiTypeAMCqiRatio )
HsdpaSchedulerParamUpdateReq
(:nCqiTypeAMCqiRatio )
HsdpaSchedulerParamUpdateRsp
Take into account by MAC-ehs
scheduler:
* hsScchType3SingleStreamSnr
and hsScchType3DualStreamSnr at
next scheduler activation
Take into account by HSD-BBR:
* nCqiTypeAMCqiRatio at next
HSD setup
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 48/171
1329
1330
CCM CallP
eCEM CE
eCEM PQ3
UcuMgrCellDeleteReq
Cell Hardware Config Delete
UcuMgrCellCreateRsp
Cell Delete Response
Cell Delete Response
Cell Delete Response
OMIU_DELETE_LOCAL_CELL_REQ
OMIU_DELETE_LOCAL_CELL_ACK
TRM2
TRM1
Cell_delete_req
Cell_delete_req
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 49/171
1331
1332
RNC
CCM CallP
DCC
eCEM PQ3
BRM
- Do semantic &
logical checks
- Run load balancing
algorithm to find
suitable eCEM
- Allocate resources
for MIMO HSDPA call
> HS-PDSCH RL ID
> C-ID
> MIMO Activation Indicator
Do semantic &
logical checks
for the NBAP
message
CEM_FULL_RL_SETUP_REQ
MIMO Activation Indicator
Indicator
Exchanges
between
eCEM/PQ3 and
eCEM/CE are not
represented to
avoid overloading
of the figure
Allocate resources
for MIMO HSD (2
HSPDA resources)
Resource Request
(HSU)
Resource Response
HSD_SETUP_REQ
MIMO Activation Indicator
HSU_SETUP_REQ
HSU_SETUP_RESP
HSD_SETUP_RESP
HARQ Memory Partitioning,
MIMO N/M Ratio
FP_CON_SETUP_REQ (HSU)
FP_CON_SETUP_RESP (HSU)
FP_CON _SETUP_REQ (HSD)
FP_CON_SETUP_RESP (HSD)
CEM_FULL_RL_SETUP_RSP
Note: The above figure is drawn for a case where DCH part and HSxPA part of the call are allocated on
same eCEM board. In case DCH is allocated on a different eCEM board, then only HSxPA part would
be established on this CEM along with silent DCH part. Also, we may only have DCH + HSDPA part and
no HSUPA part.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 50/171
1338
1339
RNC
CCM
Indicator
1340
1341
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 51/171
1342
1343
RNC
CCM CallP
DCC
eCEM PQ3
BRM
Do semantic &
logical checks
for the NBAP
message
CEM_ RL_RECONF_PREPARE
MIMO Activation Indicator
CEM_RL_RECONF_PREP_HSPA_REQ
MIMO Activation Indicator
- Do semantic &
logical checks
- Allocate HSDPA
resources for MIMO
HSDPA user
Resource Request
(MIMO HSD)
Resource Response
Allocate resources
for MIMO HSD (2
HSPDA resources)
HSD_SETUP_PREP_REQ
MIMO Activation Indicator
HSD_SETUP_PREP_RESP
(HARQ Memory Partitioning,
MIMO N/M Ratio)
CEM_ RL_RECONF_READY
(HARQ Memory Partitioning,
MIMO N/M Ratio)
1344
1345
UMT/BTS/DD/028488
02.01 / EN
Preliminary
Exchanges
between
eCEM/PQ3 and
eCEM/CE are not
represented to
avoid overloading
of the figure
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 52/171
1346
1347
1348
RNC
CCM CallP
DCC
eCEM PQ3
BRM
HSD_COMMIT_RESP
CEM_RL_RECONF_COMMIT_HSPA_IND
If it is the Setup of the first MIMO RL, Reconfigure the S-CPICH Power to
Power Offset For Secondary CPICH for MIMO
See section 4.5.20
CEM_ RL_RECONF_CANCEL
CEM_RL_RECONF_CANCEL_HSPA
CHANNEL_RELEASE_REQ
1349
1350
(HSD Resource)
CHANNEL_RELEASE_RESP
Resource Release Ind
- De-allocate
resources for DCHSDPA call
UMT/BTS/DD/028488
(HSD Resource)
CEM_RL_RECONF_CANCEL_HSPA_IND
Exchanges
between
eCEM/PQ3 and
eCEM/CE are not
represented to
avoid overloading
of the figure
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 53/171
1351
4.5.11 R99 to MIMO HSDPA Setup (RL-Reconf-Prepare CCM CallP Failure case)
1352
RNC
CCM CallP
DCC
eCEM PQ3
BRM
}
CEM_ RL_RECONF_PREPARE
Do semantic &
logical checks
for the NBAP
message
- Do semantic &
logical checks
- Allocate MIMO
resource for serving
HS-DSCH RL)
- Resource allocation
failure for serving
HS-DSCH RL Cause:
-- MIMO not capable
-- DL radio resources
not available or
-- UL radio resources
not available or
-- Node B Resources
Unavailable
CEM_ RL_RECONF_FAIL
(Cause)
1353
1354
1355
1356
1357
1358
1359
1360
1361
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 54/171
1362
CCM CallP
DCC
eCEM PQ3
BRM
HS-DSCH Information To
Modify IE
MIMO Mode indicator=
Deactivate
}
CEM_ RL_RECONF_PREPARE
(MIMO Mode indicator= Deactivate)
CEM_RL_RECONF_PREP_HSPA_REQ
(MIMO Mode indicator= Deactivate)
HSD_RECONF_PREP_RESP
CEM_RL_RECONF_PREP_HSPA_RSP (HS-DSCH FDD Information Response)
(HS-DSCH FDD Information Response)
CEM_ RL_RECONF_READY
(HS-DSCH FDD Information Response)
Exchanges
between
eCEM/PQ3 and
eCEM/CE are not
represented to
avoid overloading
of the figure
CEM_ RL_RECONF_COMMIT
CEM_RL_RECONF_COMMIT_HSPA
HSD_COMMIT_REQ
HSD_COMMIT_RESP
CEM_RL_RECONF_COMMIT_HSPA_IND
1363
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 55/171
1364
CCM CallP
DCC
eCEM PQ3
BRM
HS-DSCH Information To
Modify IE
MIMO Mode indicator=
Activate
}
CEM_ RL_RECONF_PREPARE
(MIMO Mode indicator= Activate)
CEM_RL_RECONF_PREP_HSPA_REQ
(MIMO Mode indicator= Activate)
BRM : Update
HSDPA resource
usage from single
HDSPA user to
MIMO HSDPA user
HSD_RECONF_PREP_REQ
(MIMO Mode indicator= Activate)
HSD_RECONF_PREP_RESP
CEM_RL_RECONF_PREP_HSPA_RSP(HARQ Memory Partitioning, MIMO N/M Ratio)
(HARQ Memory Partitioning, MIMO N/M Ratio)
CEM_ RL_RECONF_READY
(HARQ Memory Partitioning, MIMO N/M Ratio)
Exchanges
between
eCEM/PQ3 and
eCEM/CE are not
represented to
avoid overloading
of the figure
CEM_ RL_RECONF_COMMIT
CEM_RL_RECONF_COMMIT_HSPA
HSD_COMMIT_REQ
HSD_COMMIT_RESP
CEM_RL_RECONF_COMMIT_HSPA_IND
If it is the Setup of the first MIMO RL, Reconfigure the S-CPICH Power
to Power Offset For Secondary CPICH for MIMO
See section 4.5.20
1365
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 56/171
1366
1367
RNC
CCM CallP
DCC
eCEM PQ3
BRM
RL Information:
> RL ID
}
Delete AAL2
micro-channels
for HSD MacD
flows
CEM_ RL_DELETION_REQ
CEM_RL_DELETION_HSPA_REQ
Exchanges
between
eCEM/PQ3 and
eCEM/CE are not
represented to
avoid overloading
of the figure
CHANNEL_RELEASE_REQ
(HSD Resource)
CHANNEL_RELEASE_RESP
CEM_RL_DELETION_HSPA_RSP
(MIMO HSD)
CEM_RL_DELETION_RSP
1368
1369
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 57/171
1370
1371
RNC
CCM CallP
DCC
eCEM PQ3
BRM
}
Request to delete
all MAC-d flows
CEM_ RL_RECONF_PREPARE
(HS-DSCH MAC-d Flows To Delete)
CEM_RL_RECONF_PREP_HSPA_REQ
HSD_RECONF_PREP_REQ
CEM_RL_RECONF_PREP_HSPA_RSP
Exchanges
between
eCEM/PQ3 and
eCEM/CE are not
represented to
avoid overloading
of the figure
CEM_ RL_RECONF_READY
NBAP: RL RECONF READY
HSD_COMMIT_REQ
HSD_COMMIT_RESP
CEM_RL_RECONF_COMMIT_HSPA_IND
- Update the UE
context with Reconf
context
- De-allocate MIMO
HSDPA resources
1372
1373
1374
Remove Reconf
context
UMT/BTS/DD/028488
HSD_CANCEL_IND
CEM_RL_RECONF_CANCEL_HSPA_IND
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 58/171
1375
1376
1377
CCM OAM
CCM CallP
eCEM PQ2 CallP
1378
1379
PA2
1380
Failure
1381
OMIU_MODIFY_LOCAL_CELL_REQ
1382
MIMOActivation=false)
1383
1384
OMIU_MODIFY_LOCAL_CELL_ACK
1385
1386
1387 RSI-SI (MIMO not capable, S-CPICH disabled, new MaxTxpower = PA1)
1388
Cell_delete_req
1389
1390
1391
eCEM CE
eCEM PQ3
TRM2
MAC-ehs scheduler
is updated with new
Max TxPower
No impact in CE.
UcuMgrCellUpdateReq
(MaxTxPower)
UcuMgrCellUpdateRsp
Cell Reconf Response
Cell ReconfResponse
Cell Reconf Response
Local Cell Config (VamDegradedToMainOnly)
UcuMgrCellUpdateReq
(VamDegradedToMainOnly)
UcuMgrCellUpdateRsp
PSCR Request (new HSDPAmax power)
PSCR Request
PSCR Request
HsdpaPhyShareChannelReconfReq
PSCR is
optional
(RNC
behavior)
MAC-ehs scheduler
is updated with the
new HSDPA max
power
No impact in CE
HsdpaPhyShareChannelReconfRsp
PSCR Response
PSCR Response
PSCR Response
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 59/171
1392
1393
1394
1395
1396
1397
CCM CallP
eCEM CE
eCEM PQ3
PA2 Recovery
OMIU_MODIFY_LOCAL_CELL_REQ
MIMOActivation=true)
OMIU_MODIFY_LOCAL_CELL_ACK
RSI-SI (MIMO capable, S-CPICH enabled, new MaxTxpower = PA1 + PA2)
Program VAM
enabled in FPGA
Combiner
MAC-ehs scheduler is
updated to
VamAndMimoEnabled
No impact in CE
UcuMgrCellUpdateReq
(Vam Enable)
UcuMgrCellUpdateRsp
Cell Reconf Request
UcuMgrCellUpdateReq
(MaxTxPower)
UcuMgrCellUpdateRsp
Cell Reconf Response
Cell ReconfResponse
TRM2
MAC-ehs scheduler
is updated with the
new HSDPA max
power
No impact in CE
PSCR Request
HsdpaPhyShareChannelReconfR
PSCR is
optional
(RNC
behavior)
HsdpaPhyShareChannelReconfRs
PSCR Response
PSCR Response
PSCR Response
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 60/171
1398
1399
1400
CCM OAM
CCM CallP
1401
1402
PA2
1403
Failure
1404
1405 RSI-SI (new MaxTxpower = PA1)
1406
1407
1408
Cell_delete_req
1409
1410
1411
1412
1413
1414
1415 Cell Reconf Request (MaxTxPower )
Cell Reconf Request
eCEM PQ3
eCEM CE
TRM2
UcuMgrCellUpdateRsp
Cell Reconf Response
Cell ReconfResponse
Cell Reconf Response
UcuMgrCellUpdateReq
(VamDegradedToMainOnly)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 61/171
1416
1417
1418
CCM CallP
eCEM CE
eCEM PQ3
PA2 Recovery
UcuMgrCellUpdateReq
(VamAndMimoEnabled)
UcuMgrCellUpdateRsp
Cell Reconf Request
UcuMgrCellUpdateRsp
Cell Reconf Response
Cell Reconf Response
TRM2
Cell_config_req (MaxTxpower/2)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 62/171
1419
1420
1421
1422
1423
1424
CCM CallP
eCEM PQ3
eCEM CE
CCC
Triggers:
CEM_RL_SETUP_RSP
CEM_RL_RECONF_COMMIT_HSPA_IND
CEM_RL_DELETION_HSPA_RSP
psbCellReconfReq
(Secondary CPICH Power)
If (noOfMIMOUser = 0)
Secondary CPICH Power
= Secondary CPICH
Power
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 63/171
1425
1426
eCEM PQ2 CallP
CCM CallP
eCEM PQ3
eCEM CE
CCC
Triggers:
CEM_RL_SETUP_RSP
CEM_RL_RECONF_COMMIT_HSPA_IND
CEM_RL_DELETION_HSPA_RSP
SCPICH_POWER_OFFSET_RECONF_REQ
(Secondary CPICH Power)
psbCellReconfReq
(Secondary CPICH Power)
CCM OAM
RESET_SLAVE_BOARD_IND
TIMEOUT on
non response from eCEM
CCM OAM
RESET_SLAVE_BOARD_IND
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 64/171
1427
CCM CallP
eCEM PQ3
eCEM CE
CCC
PA2
Failure
OMIU_MODIFY_LOCAL_CELL_REQ
MIMOActivation=false)
OMIU_MODIFY_LOCAL_CELL_ACK
Secondary CPICH Power
= minimum power offset
SCPICH_POWER_OFFSET_RECONF_REQ
(Secondary CPICH Power)
psbCellReconfReq
(Secondary CPICH Power)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 65/171
1428
CCM CallP
eCEM CE
eCEM PQ3
Store
InternalDualPaUsage
& VAM coefficients
OMIU_ADD_LOCAL_CELL_REQ
MIMOActivation=true)
OMIU_ADD_LOCAL_CELL_ACK
RSI-SI (MIMO capable, MaxTxpower = min(PA1, PA2) + 3dBm)
Cell Setup
Request
(MIMO
S-CPICH
)
Program VAM
enabled in FPGA
Combiner
(MIMO,
S-CPICH
UcuMgrCellCreateReq
MaxTxpower =
PA1 + PA2)
CellConfigReq
UcuMgrCellCreateRsp
psbCellSetupReq
SCH Setup
(S-CPICH)
P-CPICH Setup
S-CPICH Setup
psbCellSetupRsp
Cell SetupFailure
Cell Setup Failure
Cell Setup Failure
TRM1
TRM2
Cell_config_req (MaxTxpower/2)
Cell_config_req (MaxTxpower/2)
Case 2: PA Failure
OMIU_MODIFY_LOCAL_CELL_REQ
OMIU_MODIFY_LOCAL_CELL_ACK
RSI-SI (MIMO not capable, S-CPICH disabled, new MaxTxpower = PA1)
1429
1430
1431
1432
1433
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 66/171
1434
1435
1436
1437
1438
1439
MIMO can be activated by setting the new parameter DualPAUsage (BTSCell) to VamAndMimo. MIMO
is supported only on eCEM and requires two transmit path on each sector. If the cell configured for
MIMO is served by an xCEM or an iCEM, MIMO is not enabled for that cell and an alarm is raised as
mentioned in section 4.6.1.1.
1440
1441
OAM also ensures that for a MIMO activated cell, VAM parameters are configured. This VAM
parameters are passed on to eCEM for VAM activation.( Refer section 4.6.1.10).
1442
1443
CCM OAM informs CCM-CallP about whether a cell is MIMO capable or not. CCM CallP is notified
whenever there is a change in MIMO capability of a cell.
1444
1445
OAM configures the SBBLINK needed for the additional tx path needed in MIMO configurations. Delay
adjustments are performed to make sure that the delay between two transmit path is less that Tc/4.
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
Parameter Check
HW Configuration Validation
NBAP Interface and procedure impacts for Audit Response and Resource Status Indication
SBBLINK routing map changes
Interface with CCM-CallP and eCEM SLOAM
Radio Modules (xTRM, TRDU, RRH) timing Delay Adjustment
Counter Management
Capacity Licensing
STSRx+y configurations are not supported. Hence frequency group id of all the carriers will be set to 0.
Hot plugin of TRM is not supported as before.
1465
4.6.1.1
1466
1467
1468
1469
MIMO is not supported on STSR2+1, STSR2+2, STRS3-M macro iBTS configurations. Hence
configuration file is checked to ensure that if MIMO is activated, no more than 2 frequencies are
configured. However STRS3-M is supported on configurations mentioned in Section 4.3. In such
scenarios, the above check for the number of frequencies does not hold true.
1470
1471
1472
1473
For each MIMO/VAM activated cell (DualPaUsage = VamAndMimo or DualPaUsage = Vam), check
shall be done to ensure that there are two PA Resources associated to it and that the PA resource ids
are valid ( i.e PA resource instance must exist). Conversely if dualPAUsage is set to none, then there
should be only one PA resource associated to this.
1474
1475
1476
1477
1478
1479
1480
If BtsCell.antennaConnection <= 6
// Local Sector
If BtsCell. DualPAUsage = VamAndMimo or Vam
The number of paResource of this BtsCell shall be = 2
Else
The number of paResource of this BtsCell shall be = 1
EndIf
Else // remote or CPRI sectors
MIMO requires two transmit paths and a cell is MIMO capable only if all the following conditions are
true:
The parameter dualPaUsage is set to VamAndMimo
The cell has two PA resources or two PAResourceRRHs attached.
The cell is served by an eCEM
Two transmit paths are enabled.
Parameter Check
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 67/171
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
If a cell is configured with DualPaUsage = VamAndMimo or Vam, then the VAM parameters shall be
present.
1494
1495
If there is at least 1 BtsCell with MIMO or VAM, then the parameter RfCarrier.hspaHardwareAllocation
should be set to xCemOnly
1496
1497
If there is at least 1 BtsCell with MIMO or VAM, then the parameter eCemxCemPreference.should be
set to eCEM.
1498
1499
1500
If dualPaUsage of a BTSCell is set to vamAndMimo or vam, all BTSCell(s) mapped on the same
sector as that BTSCell should have their dualPaUsage parameter set to vamAndMimo or vam.
Failure of the above condition would make all the cells on that sector as MIMO not capable
1501
1502
When either of these checks fails, BTS would set MIB in state KO and report the alarm INVALID
CONFIGURATION DATA.
1503
4.6.1.2
1504
1505
1506
1507
When there is atleast one BTSCell with MIMO or VAM configured, mixity of eCEM with iCEM/xCEM is
not allowed. If there is an iCEM/xCEM along with an eCEM at BTS startup or if an iCEM/xCEM is
plugged in, the iCEM/xCEM board object is set to disabled (operationalState set to disabled) and an
alarm UNSUPPORTED EQUIPMENT/CEM(271_4) is reported on the associated BOARD object
1508
1509
1510
Mimo is supported only on xCCM/u. if alpha/iCCM is present, cells will not be MIMO capable. Audit
Response / RSI ( to RNC) and ADD/MODIFY_LOCAL_CELL (to CCM- Callp), will indicate that MIMO is
not capable for the cells.
1511
4.6.1.3
1512
Audit response
1513
1514
1515
1516
1517
1518
1519
The Node B shall include the MIMO Capability IE and set the MIMO Capability IE value to "MIMO
Capable" for every MIMO capable Local Cell which is on an eCEM and has two transmit paths. The
message shall include the MIMO Power Offset For S-CPICH Capability IE set to "S-CPICH Power
Offset Capable for every MIMO capable cell. If 64 QAM is enabled, the NodeB shall include the IE
SixtyfourQAM DL and MIMO Combined Capability and set the value as SixtyfourQAM DL and MIMO
Combined Capable. The message shall include the IE Precoding weight set restriction set to true if OMC
parameter IsPrecodingWeightSetRestriction (BTSCell) is true, else false.
1520
1521
1522
1523
1524
1525
1526
1527
When the Local Cell is enabled, the Node B shall include the MIMO Capability IE and set the MIMO
Capability IE value to "MIMO Capable" for every MIMO capable Local Cell which is on an eCEM and
has two transmit paths. The message shall include the MIMO Power Offset For S-CPICH Capability IE
set to "S-CPICH Power Offset Capable for every MIMO capable cell. If 64 QAM is enabled, the NodeB
shall include the IE SixtyfourQAM DL and MIMO Combined Capability and set the value as
SixtyfourQAM DL and MIMO Combined Capable.The message shall include the IE Precoding weight set
restriction set to true if OMC parameter IsPrecodingWeightSetRestriction (BTSCell) is true, else false.
EndIf
The pair of PA resource Ids for a mimo cell with same antenna connection shall be the same.
Conversely, two mimo cells having different antenna connection shall not have the same PA resource
ids.
HW Configuration Validation
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 68/171
1528
1529
Tx path failure
1530
1531
1532
1533
1534
1535
When any of the Tx path of a MIMO cell goes down, RSI SI has to be sent for that cell with MIMO
Capability IE as "MIMO Not Capable" and with maxDlPowerCapability set to the max power of the
remaining Tx path. The RSI shall include the MIMO Power Offset For S-CPICH Capability IE set to "SCPICH Power Offset Not Capable. RSI shall include also Secondary CPICH Individual Information IE
populated with Common Physical Channel ID as received in NBAP Cell Setup/Reconfiguration request
message, Resource Operational State : disabled and Availability Status : power off.
1536
1537
1538
1539
1540
1541
When the failed Tx path is restored, RSI SI will be sent for the cell with MIMO Capability IE as "MIMO
Capable" ", Power Offset For S-CPICH Capability IE set to "S-CPICH Power Offset Capable and with
maxDlPowerCapability as sum of both Tx paths. RSI shall include also Secondary CPICH Individual
Information IE populated with Common Physical Channel ID as received in NBAP Cell
Setup/Reconfiguration request message, Resource Operational State : enabled and Availability Status
: empty.
1542
maxDLPowerCapability Computation
1543
1544
1545
1546
1547
maxDLPowerCapability is computed by deducting the internal and external losses from the PA power (
based on PAratio for that cell and maxPowerAmplification of the PA or maxRRHPowerAmplification of
the RRH). For Mimo it is quite possible that the external losses of the two paths are different and though
PA power is the same, maxDLPowerCapability would be different for both the tx paths. Hence for MIMO
cells, maxDLPowerCapability reported to RNC would be:
1548
1549
1550
1551
1552
1553
1554
1555
The maxPowerAmplification value of both the PAresource attached to a MIMO or VAM capable cell is
recommended to be the same. However if maxPowerAmplification of either of PA is changed to such
effect that the newly computed MaxDLPowerCapability value becomes different than the one which was
reported to RNC before, RSI with the new MaxDlPowerCapability is sent to RNC.
1556
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 69/171
1557
4.6.1.4
1558
1559
CCM OAM shall configure FLINK and RLINK connections (BBLINK) specific to MIMO configurations.
There is no change in the way SBBLINK is configured.
1560
Following figures gives the sBBLINK routing map for the two supported configurations:
1561
STRS2-M Macro
1562
1563
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 70/171
1565
1564
STRS2-M Distributed:
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
UMT/BTS/DD/028488
Page 71/171
1566
1567
1568
1569
1570
1571
STSR3 configurations can be supported if RRH has the capability of transmitting 3 carriers. The SBBlink
configurations are quite similar to STSR2 distributed shown above. ST1 of the third frequency will be on
the next even channel/AxC for the RRH on the main Tx path and corresponding ST2 will be on the next
odd channel/AxC for the RRH on the div Tx path.
1572
1573
1574
1575
1576
1577
1578
1579
PMM Cells:
1580
1581
PMM cells shall contain power information on both main and diversity path. For simplification, main and
diversity can be configured in AddPmmForwarding routine for all cases (MIMO or not MIMO)
1582
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 72/171
1583
4.6.1.5
TRM / PA defense
iBTS
Div
Main
xTRM1
eCEM
HSSPC
xCCM
TX f1ST1, f2
ST1Rx f1,f2
Main, Div
M
C
M
C
M
C
xTRM2
TX f1ST2,
f2ST2
Rx None
DDM
M
C
F1stream 2,
F2 stream 2
M
C
6 Rx
signals
DDM
DDM
M
C
1584
1585
Tx Path Defense
1586
1587
1588
1589
1590
In case of xTRM2 or PA2 failure, no reconfiguration is required. However if xTRM1 or PA1 fails, CCM
OAM has to reconfigure the Tx path carrying stream 1 on the remaining path. (xTRM2, PA2). CCM
OAM will need to reconfigure the sBBLINK for this failure (similar to STSR2 non-MIMO scenario). CCM
OAM will configure RX paths on TRM2. However in both the cases, the MIMO capability of the cell will
be lost. Same is the case during lock or plug out scenario.
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
In case of a PA failure, CCM_OAM has to send the new maxDlPowerCapability ( of the remaining PA)
to RNC along with MIMO Capability IE as "MIMO Not Capable" and S-CPICH Op-State as disabled, SCPICH Availability status as power off.
An alarm PARTIAL TX PATH FAILURE is raised to indicate that a MIMO Tx path has failed.
CCM OAM instructs TRM to perform a cell delete on the failed PA.
CCM OAM forwards the Cell Reconfig Request message received from RNC to CCM CallP.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 73/171
1603
1604
1605
1606
1607
1608
Along with this CCM OAM sends LocalCellConfig to CEM to instruct it to stop VAM for the tx path.
In case of failure of the first Tx branch, the VAM coefficients for the cell shall be to eCEM in order to
autonomously reconfigured the channels being fed to the first virtual antenna to use the second Tx
branch. VAM coefficients shall be changed as following:
V12 a1 e j1
V
VAM _ Matrix = 11
=
j
V 21 V 22 a 3 e 3
a1
Amplitude _ coefficients =
a 3
1609
a 2 e j2
a 4 e j4
a 2 0 1
=
a 4 0 0
2 0 0
Phase _ coefficients (deg ) = 1
=
3 4 0 0
1610
1611
1612
1613
1614
1615
1616
In case of failure of the second Tx branch, the VAM coefficients for the cell shall be sent to eCEM in
order to autonomously reconfigure the channels being fed to the second virtual antenna to use the first
Tx branch. VAM coefficients shall be changed as following:
V12 a1 e j1
V
VAM _ Matrix = 11
=
j
V 21 V 22 a 3 e 3
a1
Amplitude _ coefficients =
a 3
1617
a 2 e j2
a 4 e j4
a 2 1 0
=
a 4 0 0
2 0 0
Phase _ coefficients (deg ) = 1
=
3 4 0 0
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
In case of a timeout, the existing defense mechanism would hold good and the alarm is cleared.
For a VAM only cell, above mentioned procedure is still maintained, except that the MIMO information is
not passed to RNC in RSI message.
When PA recovers, similar reverse procedure is applied.
Rx Path Defense
This is same as TRM defense
1629
1630
1631
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 74/171
1632
1633
1634
1635
1636
1637
4.6.1.7.1 additionalRadioPerSector
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
There is no change in the computation of HW and SW capacities. However, MIMO paths have to be
taken into consideration while computing the needed tokens.
For a MIMO cell, one additionalRadioPerSector token is required, since it has two radio paths. For
UA8.0, the configuration would be either STSR x+y or MIMO. For STSR x+y current algorithm for
computing the needed tokens are used. For MIMO configurations, the needed tokens would be the
number of sectors which support the MIMO cells.
Resource Allocation:
In addition to UA7 criteria, the algorithm will take into account the number, of sectors on which two
PAs/RRHs/TRDUs are configured. If a MIMO and/or VAM sector cannot be configured with two
Radios, the cell is not considered as a MIMO cell and CapacityLicensing alarm is raised.
License Increase:
When the license is increased, as in UA 7.0, an additional tx path is setup. It may be possible that a non
MIMO cell can become a MIMO cell. See open issue [16].
If so procedure pertaining to PA/tx path recovery is performed, as described in section 4.6.1.5
License decrease:
When the license is decreased, as in UA 7.0, an additional tx path may be brought down and BTS is
reset as per current 7.0 algorithm.
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
For a MIMO cell, power from both PAs/RRHs is added in the capacity algorithm. There is no change in
the computation of HW and SW capacities.
Resource Allocation:
There is no change from UA7 but in case one or more PAs/RRHs/TRDUs have to be disabled, the
BTS should first disable one of the two PAs/RRHs/ configured in MIMO sectors so that BTSCell(s)
that are mapped on the impacted sector will still work with one PA/RRH/TRDU. The defense mechanism
mentioned in section 4.6.1.5 is followed.
License Increase:
When the license is increased, as in UA 7.0, an additional PA/RRH may be enabled. It may be possible
that a non MIMO cell can become a MIMO cell. If so procedure pertaining to PA/tx path recovery is
performed, as described in section 4.6.1.5
License decrease:
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 75/171
1682
1683
1684
When the license is decreased, as in UA 7.0, a PA/RRH may be disabled. It may be possible that a
MIMO cell may lose its MIMO capability. If so procedure pertaining to PA/Tx path failure is performed,
as described in section 4.6.1.5
1685
4.6.1.8
1686
1687
The CCM OAM will have to get the TX Power for Main and Div to fill the txPowerSector and txPowerCell
for MIMO and VAM Cell
1688
4.6.1.9
1689
1690
1691
1692
1693
1694
1695
4.6.1.10
1696
1697
1698
MIMO information is required by eCEM PQ3. This information has to be passed on ITF-3 to eCEM
SLOAM in LOCAL_CELL_CONFIG_REQ message. CCM OAM shall set DLMapping with main and
diversity bits per cell.
1699
1700
1701
1702
OAM: DualPaUsage
Hardware
available
InternalDualPaUsage
Vam coefficients
None
PA1 (Main)
VamDisabled
Amplitude (1,0;0,0)
Phase (0,0;0,0)
Vam or VamAndMimo
Vam or VamAndMimo
VamEnabled
PA2 failure
VamDegradedToMainOnly
O&M vamAmplitudeCoeff
O&M vamPhaseCoeff
Amplitude (1,0;0,0)
Phase (0,0;0,0)
Vam or VamAndMimo
PA1 failure
VamDegradedToDivOnly
Amplitude (0,1;0,0)
Phase (0,0;0,0)
1703
1704
1705
1706
CCM shall update the eCEM via a LOCAL_CELL_CONFIG_REQ each time there is a change in this
configuration (startup, PA failure, Pa recovery, TRM failure ). CCM OAM shall set DLMapping with
Main and Diversity bits per cell.
1707
4.6.1.11
1708
1709
Timing alignment is needed for MIMO activated cells, since the two tx path come from two different
TRMs /RRHs/ TRDUs. The delay calculations and compensations are described in the section 12.1.
1710
1711
The delay aligment procedure is always performed whatever type of radio board used. The only
difference is the way the delays are provides by the radio board.
Timing alignment
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 76/171
1712
4.6.1.12
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
Existing PM counter #10205 shall be modified for a MIMO capable cell to have screening for two different
power amplifiers.
1726
Counters
Counter #10225 is retained with its existing functionality, but for Cells with Tx diversity such as MIMO
cells this counter reports the distribution curve of the combined power information for the Main PA and
the Div PA.
Two new counters #10228 & #10229 (as an example) are added in order to report separated distribution
curves for the Main PA and the Div PA. Their format is the same as for counter #10225.
PM module needs to ensure that it retrieves the values for these new screening ids from Radio
counters..
PM should also ensure that all these new screening ids are added as part of PM observation file (XDR).
PM currently provides the decoding mechanism to convert the XDR (binary) file to ASCII file and display
the ASCII file. Both decoding and display mechanism should include these new screenings.
See section 6.3.1.
1727
1728
1729
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 77/171
1730
1731
4.6.2.1
1732
1733
1734
1735
4.6.2.2
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
The NBAP Manager is enhanced to process the new IEs introduced to manage MIMO. NBAP manager
shall do the semantic checks defined in section 4.1.2.
NBAP Manager
The following checks need to be done by CCM CallP for call admission control:
Cell Setup
See section 4.1.2.3 for NBAP checks to be done.
In complement to these checks:
Err_Mess 4.6.2.2-1
If Node B receives Transmit Diversity Indicator for S-CPICH set to active it shall send a NBAP CELL
SETUP FAILURE with Radio Network Layer Cause set to Requested Tx Diversity Mode not
supported (VAM and Transmit Diversity are exclusive).
Err_Mess 4.6.2.2-2
If the IE Pilot Configuration included in MIMO Pilot Configuration IE or MIMO Pilot Configuration
Extension IE is set to Normal and Diversity Primary CPICH NodeB shall send a NBAP CELL SETUP
FAILURE with Radio Network Layer Cause set to Requested Configuration not supported
If all the checks pass then CCM CallP shall proceed with the procedure and send the related ITF2
request message to eCEM CallP
When CCM CallP received the ITF2 Cell Setup Response message from the eCEM it shall propagate
the response to the RNC in the NBAP Cell Setup Response message.
In order to reduce the MIMO impact on legacy UEs and to coexist with MIMO UEs which use the PCPICH and S-CPICH 3GPP propose to use different power offset for the s-CPICH configured for MIMO.
Node B shall be capable of applying different power offsets (w.r.t P-CPICH) to S-CPICH in MIMO mode
and in non MIMO mode. This means the configured S-CPICH will be transmitted with different power
depending upon whether there is any UE in MIMO mode in the cell.
eCEM CallP does not manage the IE MIMO Pilot Configuration Extension directly. CCM CallP shall
provide the S-CPICH Power configured via Cell Setup or Cell Reconfiguration Request with:
Value from S-CPICH power IE if there is no MIMO call in the cell
Value from Power Offset For Secondary CPICH for MIMO if there is at least one MIMO call in
the cell.
Cell Reconfiguration
See section 4.1.2.4 for NBAP checks to be done.
In complement to these checks:
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 78/171
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
Err_Mess 4.6.2.2-3
If Node B receives Transmit Diversity Indicator for S-CPICH set to active it shall send a NBAP CELL
RECONFIGURATION FAILURE with Radio Network Layer Cause set to Requested Tx Diversity
Mode not supported (VAM and Transmit Diversity are exclusive).
If all the checks pass then CCM CallP shall proceed with the procedure and send the related ITF2
request message to eCEM CallP
When CCM CallP received the ITF2 Cell Reconfiguration Response message from the eCEM it shall
propagate the response to the RNC in the NBAP Cell Reconfiguration Response message.
Radio Link Setup
See section 4.1.2.4 for NBAP checks to be done.
Err_Mess 4.6.2.2-4
If the Local cell is not MIMO-capable then CCM CallP shall reject the procedure by sending a Radio
Link Setup Failure with cause MIMO not available
Err_Mess 4.6.2.2-5
If the RADIO LINK SETUP REQUEST message contains the MIMO Activation Indicator IE and/or
Sixtyfour QAM Usage Allowed Indicator IE set to "Allowed", but does not contain the HS-DSCH MAC-d
PDU Size Format IE set to "Flexible MAC-d PDU Size", then CCM CallP shall reject the procedure using
the RADIO LINK SETUP FAILURE message with Protocol Cause set to Semantic error.
Err_Mess 4.6.2.2-6
If the RADIO LINK SETUP REQUEST message contains the MIMO Activation Indicator IE and Sixtyfour
QAM Usage Allowed Indicator IE set to "Not Allowed", but does not contain the HS-PDSCH Physical
Layer Category IE in the range [15, 20] then the Node B shall reject the procedure using the RADIO
LINK SETUP FAILURE message with Protocol Cause set to Semantic error.
Err_Mess 4.6.2.2-7
If the RADIO LINK SETUP REQUEST message contains the MIMO Activation Indicator IE and Sixtyfour
QAM Usage Allowed Indicator IE set to "Allowed", but does not contain the HS-PDSCH Physical Layer
Category IE in the range [19, 20] then the Node B shall reject the procedure using the RADIO LINK
SETUP FAILURE message with Protocol Cause set to Semantic error.
CCM CallP uses the Load Balancing services to allocate MIMO HSDPA resources.
Err_Mess 4.6.2.2-8
In case of allocation failure when max number of MIMO users on one eCEM exceeds the limit, CCM
CallP shall reject the procedure using Radio Link Setup Failure with cause FDD - MIMO Not Available
when the RL is MIMO.
If all checks pass then CCM CallP shall send the related ITF2 request message
(CEM_xxx_RL_SETUP_REQ) to eCEM CallP
When CCM CallP received the ITF2 Radio Link Setup Response message from the eCEM it shall
forward the MIMO N/M Ratio and the HARQ Memory Partitioning IE (if contained) in the HS-DSCH
FDD Information Response IE of the RADIO LINK SETUP RESPONSE message to the RNC.
If it is the Setup of the first MIMO call configured in the cell CCM Call shall reconfigure the S-CPICH
power to Power Offset For S-CPICH for MIMO.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 79/171
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
4.6.2.3
1884
1885
1886
1887
1888
CCM CallP shall manage the S-CPICH power as defined in section 4.1.2.8.
CCM CallP shall generate a CemScpichPowerOffsetReconfReq message with parameter Secondary
CPICH Power filled with Secondary CPICH Power or Power Offset For Secondary CPICH for MIMO
(see use case 4.5.20)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 80/171
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
4.6.2.4
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
The common NBAP measurement Transmit Carrier Power (TCP) is managed by CallP. TCP
measurement result is given as a percentage of the maxTxPower configured by RNC. In a Vam or
VamAndMimo cell the power is balanced on the two PA then:
TCP cell = (TCP_MAIN + TCP_DIV)/2 = TCP_MAIN = TCP_DIV
Launching the measurement on the Main path (TRM, RRH, TRDU or MC-TRX) is sufficient to report the
good result.
CCM CallP shall use the information provided by CCM CallP in OMIU_ADD_LOCAL_CELL_REQ and
OMIU_MODIFY_LOCAL_CELL_REQ to know which the TX Main is. The detailed content of these
messages needs further investigations (see open issue [2]).
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 81/171
1937
4.6.2.5
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
The Load Balancing (LB) entity needs to manage allocation/de-allocation of HSDPA resources for
MIMO calls. Each MIMO call costs 2 HSDPA resources compared to a non MIMO call even if only one
OCP resource is allocated in the Channel Element
The capacity of the eCEM board is impacted in term of the number of HSDPA users that can be
supported and LB shall verify that:
Where:
nb of single HSDPA users : number of HSDPA users which are not MIMO or DC-HSDPA users
nb DC-HsdpaMIMO : combined number of Dual Cell HSDPA and MIMO users.
Parameter internalMaxDualCellHsdpaMIMOUsersAllowed is received in Capacity Response
message from eCEM boards. See section 6.1.7.
Parameter dualCellHsdpaMimoMaxNumberUserEcem is a new OAM parameter introduced for
Dual-Cell and MIMO features (i. e. one single parameter shared by the 2 features). See section
6.1.7.
If S-CPICH has different SF Code, then may be extra resources shall be allocated on CE for SCPICH, see open issue [9].
The latest inputs from CE design indicate that the resource needed in the uplink is not the same for
MIMO and DualCell calls (only 1 resource for MIMO calls). This may impact to the definition of the
common DualCell + MIMO parameters. See open issue [14].
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 82/171
1971
1972
4.6.3.1
1973
1974
1975
1976
1977
1978
1979
SLOAM shall forward LocalCellConfigRequest message received from CCM OAM to Modem Controller
(OAL part)
SLOAM shall forward LocalCellConfigResponse message received from OAL to CCM OAM.
SLOAM shall forward HsdpaConfigRequest message received from CCM OAM to Modem Controller
(OAL part)
SLOAM shall forward HsdpaConfigResponse message received from OAL to CCM OAM.
1980
4.6.3.2
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
OAL shall process the new parameters of LocalCellConfigRequest message (see section: 5.2.3).
OAL checks the range of the parameters and sends back a LocalCellConfigResponse Nack in case of
error.
If checks are successful OAL propagates these parameters to CCC and sends back a
LocalCellConfigResponse Ack to CCM OAM via SLOAM.
SLOAM
OAL
OAL shall process the new parameters of HsdpaConfigRequest message (see section: 5.2.3).
OAL checks the range of the parameters and sends back a HspdaConfigResponse Nack in case of
error.
If checks are successful OAL propagates these parameters to CCC and sends back a
HspdaConfigResponse Ack to CCM OAM via SLOAM.
New tunables for MIMO Ack/Nack thresholds are defined in CPIF interface (see section 5.2.4) and are
provided by AO MCtl to CCC at eCEM startup.
1995
4.6.3.3
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
NBAPR
NBAPR shall decode MIMO UE aspects in NBAP procedures at ITF1 and ITF2:
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 83/171
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
eCEM CallP does not manage the IE MIMO Pilot Configuration Extension nevertheless NBAPR can
verify the semantic of the IE in conformance to 3GPP NBAP (already done by CCM CallP) but does not
propagate it to CE Controller.
If all checks pass NBAPR shall forward the Cell Setup Request/Reconfiguration Request to CCC.
If all checks pass NBAPR shall forward the Radio Link Setup Request or Radio Link Reconfiguration
Prepare to DCC.
When receiving the response from DCC NBAPR shall encode MIMO aspects in NBAP procedures at
ITF1 and ITF2:
Radio Link Setup Response, Radio Link Reconfiguration Ready,Radio Link Setup Failure:
o IE HARQ Memory Partitioning
o IE MIMO N/M Ratio
2037
4.6.3.4
BRM
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
BRM needs to manage allocation/de-allocation of HSDPA resources for MIMO calls. Each MIMO call
costs 2 HSDPA resources compared to a non MIMO single cell call even though only one HSD BBR
resource is allocated for a MIMO call.
The coast being the same for DualCell and MIMO calls, the same operations have to be performed for
DualCell and MIMO.
But in order to make easier code evolutions, it is recommended to distinguish DualCell and MIMO calls
with separated objects HSD MIMO and HSD DualCell. This appears in figures in chapter Uses
Cases.
The number of HSDPA users allocated on an eCEM is verified by the Load Balancing (see section:
4.6.2.4) nevertheless BRM shall verify that:
Nb of single HSDPA users + 2 * nb of DualCellHsdpaMIMO users <= 128
Nb of DualCellHsdpaMIMO users <= num_dual_cell_hsdpa_MIMO_users
Where num_dual_cell_hsdpa_MIMO_users indicates the maximum combined number of DualCell and
MIMO calls that can be supported by eCEM board. BRM retrieves this parameter from UCU Manager
via UcuMgrGetCeCapabilityResp message and propagates it to CCM CallP in CemCapacityResp
message.
This parameter has already been introduced with feature DualCell capacity Increase.
Note: the verification at the BRM level only takes into account the physical limitations of the eCEM, the
limitation introduced by OAM parameter dualCellHsdpaMimoMaxNumberUserEcem is not concerned.
Normally as this check has already been done by LB on CCM then allocation/de-allocation should be
always successful. Nevertheless on a ResourceReq message from DCC in case of no available
resource BRM answers by a Resource Failure.
The interface between DCC and BRM needs to evolve for resource allocation/de-allocation for MIMO
calls.
The following proposal is compliant with DC-HSDPA introduction:
Resource-Request (HSD, Normal): This would indicate to BRM to allocate 1 HSDPA resource
for single cell HSDPA setup as done today. (R99 => non MIMO HSDPA scenario)
Resource-Request (HSD, MIMO): This would indicate to BRM to allocate 2 HSDPA resources
for MIMO setup. (R99 => MIMO scenario)
Update Resource-Request (HSD, MIMO, ResourceId): This would indicate to BRM to allocate
1 more HSDPA resource for Reconfiguration of the call from non MIMO to MIMO. The
parameter ResourceId would tell the resource Id of previously established HSDPA call. (non
MIMO => MIMO scenario)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 84/171
2075
2076
2077
2078
2079
2080
2081
2082
2083
Update-Resource-Request (HSD, Normal, ResourceId): This would indicate to BRM to deallocate HSDPA resource for MIMO removal. The parameter ResourceId would tell the
resource Id of previously established single cell HSDPA call. (MIMO => non MIMO scenario)
Resource-Release-Ind (HSD): This would indicate to BRM to de-allocate all HSDPA
resources. (1 HSDPA resource for SC-HSDPA or 2 HSDPA resources for MIMO)
Note: The terminology Normal is used here to indicate a single cell HSDPA call (i.e. non MIMO
HSDPA call)
2084
4.6.3.5
CCC
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
CCC shall propagate the VAM configuration received in LocalCellConfigRequest message received
from CCM OAM via OAL to Cell BBR via UcuMgrCellCreateReq/ UcuMgrCellUpdateReq message.
CCC shall propagate tunables MIMO Ack/Nack thresholds retrieved from AO MCtl to Cell BBR in
UcuMgrCellCreateReq message.
CCC shall process S-CPICH Information IE contained in Cell Setup Request (respectively Cell Setup
Reconfiguration Request) and propagate the S-CPICH information via PsbCellSetupReq (respectively
PsbCellReconfReq) message to the PSB BBR.
CCC shall process S-CPICH Power Offset parameter contained in CemScpichPowerOffsetReconfReq
and propagate the information via PsbCellReconfReq message to the PSB BBR.
CCC shall propagate the new parameters received from OAL to CE Controller (HSDPA BBR) via CPIF
messages in:
2104
4.6.3.6
DCC
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
DCC shall use the BRM allocation/de-allocation messages enhanced to managed MIMO users (see
section 4.6.3.4)
DCC shall request a HSD-BBR to BRM when MIMO is configured via a Radio Link Setup or a Radio
Link Reconfigure. In case of Resource Failure from BRM DCC shall fail the procedure with a Radio Link
Setup Failure or a Radio reconfiguration Failure.
DCC shall provide MIMO IEs decoded by NBAPR to HSD-BBR at CPIF interface in the relevant
messages:
DCC shall provide MIMO IEs received from HSD-BBR at CPIF interface to be encoded by NBAPR in
the relevant messages:
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 85/171
2125
2126
4.6.4.1
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
The UCU Manager is responsible for managing all resources on the UCU, namely the BBRs, CEs and
cells. The BBRs are managed with the help of the various BBR objects, each CE with the help of a CE
Manager and each cell with the help of a Cell Manager.
For setting up cells the UCU Manager forwards Cell Create Requests to one of the Cell Manager
instances depending on the cell index.
Control Plane
The Cell Manager class stores cell related parameters, namely all information that is received in the Cell
Create Request and in the Cell Update Request.
Since the SCPICH Setup Request (see 4.6.4.1.2) contains the new parameters
Tx_Accumulator_Indicator with the value Tx_accumulator_B (see 4.6.5.3), this one must be configured
in the CellHwConfigSetupReq as it is currently done for the Tx_accumulator_A. These two parameters
indicate the stream index associated to the primary and secondary antenna stream (respectively
Tx_accumulator_a and Tx_accumulator_b). As explained in the section 4.6.5.4, these two values will be
used to inform the VAM Stream Pair Selection parameter provided to the CE by the PQ3 (see the
paragraph following).
The CellConfigReq contains a new parameter, CQI Delay Distance for MIMO users. The value of this
field shall be the same that the CQI Delay Distance use for legacy users.
Cell Manager shall use the InternalDualPaUsage, VAMAmplitudeCoeff and VAMPhaseCoeff to
configure the VAM accordingly (see section: 4.6.1.10)
These parameters are used to inform new ones in the CE (see section 4.6.5.6 and [R13] table 15-3) :
- VAM Coefficients, Float 0..1 step 0.000000001 obtained thanks to the polar to cartesian
conversion. (see section 4.6.5.7) for details concerning the calculation and the PA failure case). The
calculation is detailed below.
- VAM Stream Pair Selection (2*stream indexes with the stream index a number between 0 and
11) corresponds to the value of the Tx_accumulator_a and the Tx_accumulator_b (see section 4.6.5.7
for details)
- Update_flag: Boolean to indicate to the CE a new update of the VAM coefficient.
These parameters are available thanks to a dedicated access to the FPGA Combiner. This
development is provided by BCS Platform.
The PQ3 provides to the CE a 2x2 complex matrix.
2163
2164
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 86/171
2165
In case of one PA failure, the VAM Coefficients to provide to the CE shall be:
2166
V12 0 1
V
st
If 1 Tx branch failure: VAM Coefficients = 11
=
V 21 V 22 0 0
2167
V12 1 0
V
nd
If 2 Tx branch failure: VAM Coefficients = 11
=
V 21 V 22 0 0
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
New Hsdpa ACK/NACK thresholds (see section 5.2.4) provided in UcuMgrCellSetupReq message and
used by HSD-BBR (see section 4.6.4.1.4) shall be stored in cell related parameters.
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
A pilot/sync/broadcast (PSB) BBR instance is responsible for providing the synchronization channel
(SCH), primary common pilot channel (PCPICH), secondary common pilot channel (SCPICH), and
primary common control physical channel (PCCPCH).
At eCEM startup UCU Manager shall fill the maxDualCellHsdpaMIMOUsersAllowed with the capacity
of the board (see section 4.8.3) that can be supported on the eCEM board in
UcuMgrGetCeCapabilityResp message sent to eCEM CallP in response to UcuMgrGetCeCapabilityReq
message.
There is a new parameter IsPrecodingWeightSetRestrictionPreferred in the UcuMgrCellCreateReq
message (CellParamInd structure) and UcuMgrCellUpdateReq message(CellUpdate structure). This
parameter is forwarded to the mac-ehs scheduler.
On reception of a PSB cell setup request or a PSB cell reconfigure request, the PSB BBR take into
account Secondary CPICH Power (in Secondary CPICH Information structure).
Currently, the parameters are not transmitted from the eCEM CallP to the PQ3 over CPIF. A structure
must be added in PQ3 CPIF interface in the common data, in the PsbCellReq structure:
secondaryCPICHInformation (optional) refer to 5.2.4 ITF7: CPIF.
The structure secondaryCPICHInformation shall be used to fill the structure sent to CE in SCPICH
Setup Request or SCPICH Reconfiguration Request (existing messages not used up to now)
In the SCPICH Setup Request, a new field TA(Tx_Accumulator_Indicator) is added and corresponds to
the value Tx_accumulator_B. The field Transmit_Diversity_Indicator shall be put to inactive.(see section
4.6.5.3).
Cell Reconfiguration
PSB BBR does not manage the IE MIMO Pilot Configuration Extension directly (see section 4.6.2.2).
eCEM CallP shall provide the S-CPICH Power configured via PsbCellSetupReq or PsbCellReconfReq
with Secondary CPICH Power set :
PSB BBR shall update the CE via SCPICH Reconfiguration Request message.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 87/171
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
The HSDPA BBR instance is responsible for providing the resources to support the HSDPA Shared
Channels (HS-SCCHs and HS-PDSCH) for one cell.
Within the PhysicalSharedChannelSetup message, it receives the information that is necessary to
configure the MAC-hs and OC+ CE. This is mainly information about the OVSF codes as well as the
total transmit power for HSDPA.
The PhysicalSharedChannelSetup and HsdpaSchedulerParamUpdateReq contain a HsdpaCellParams
field where ncqiTypeAMCqiRatio(which be used in the response structure),
hsScchType3SingleStreamSnr and hsScchType3DualStreamSnr are used to calculate HS-SCCH
power.
MAC-ehs shall calculate the demanded power taking into account the two Tx branches in case of MIMO
(see section 4.6.4.2.1). HSDPA BBR shall use the field InternalDualPaUsage part of
UcuMgrCellCreateReq or UcuMgrCellUpdateReq message to know which Tx branches are valid in
PMM cells received from CCM concerning the demanded power:
VamDisabled
: Main branch
VamEnabled
: Main and Diversity branches
VamDegradedToMainOnly
: Main branch
VamDegradedToDivOnly
: Diversity branch
The PMM cells are managed by the BCS Platform so this information would be usefull for the platform
when decoded the PMM cells.(to be verify!!)
Fault management: case of one of the Tx branch fails and failure recovery
The CRNC shall recalculate max HSDPA power (corresponds to HS-PDSCH, HS-SCCH, E-AGCH, ERGCH, and E-HICH total power IE) according to the new Maximum Transmission Power (Reconfigured
with NBAP CELL RECONFIGURATION REQUEST). This new max HSDPA power is reconfigured using
PhysicalSharedChannelReconfiguration procedure.
As soon as a PA failure is detected thanks to the variable internalDualPaUsage, the BBR updates the
maxTxPower (received in UcuMgrCellUpdateReq) and max HSDPA power dividing it by two (the
scheduler can react quickly and we dont wait for the HsdpaPhysicalShareChannelReconfReq which is
optional). Then if HsdpaPhysicalShareChannelReconfReq is received, the BBR takes into account the
new value of max HSDPA power. The SINGLE_STREAM_ONLY flag will be set to TRUE and the
indication of PA failure is sent to BCS platform to update the Tx Branches to use.
The HSDPA BBR shall send the information to HSD BBR to update the maximum bit rate in the framing
protocole for this UE.
When PA recovery is detected thanks to to the variable internalDualPaUsage, the BBR updates the
maxTxPower (received in UcuMgrCellUpdateReq) and max HSDPA power multiplicating the actual
value by 2 (it permits to react as HsdpaPhysicalShareChannelReconfReq is optional). Then if
HsdpaPhysicalShareChannelReconfReq is received, the BBR takes into account the new value of max
HSDPA power.
The scheduler takes into account the indication of PA recovery provided by the HSDPA BBR and no
more forces the SINGLE_STREAM_ONLY flag.
BCS platform will use the new indication to update the Tx Branches to use.
2258
2259
2260
The HSD BBR instance is responsible for providing the dedicated resources to support the HSDPA
connection for an individual UE.
2261
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 88/171
2262
HSDSetupReq : On response to a NBAP Radio Link Setup or NBAP Radio Link Reconf.
2263
2264
HSDSetupPrepReq : On response to a NBAP Radio Link Reconfiguration. Request which results to the
addition of a HSD radio link to the already existing DCH connection.
2265
2266
2267
2268
2269
2270
2271
2272
At HSD Setup, the HSD BBR checks whether the HsdInformationMimoActivationIndicatorPresent flag is
present or not. - If present, MIMO shall be activated, the MIMO usage bit in the UE context is set to
true and the response message includes the HsdInfoResponse IE with nCQITypeAMCqiRatio and
the Number of Processes in HarqMemory-Partitioning. In case of use of Harq Memory Partitioning
explicit, the field HarqMemoryPartitioningInfoExtensionForMIMO (optional) shall be included in
HarqMemoryPartioningExplicit. (Today, only the Harq Memory Partitioning mode implicit is supported.)
2273
2274
2275
2276
The HSD BBR checks whether the SixtyfourQamUsageAllowedInd is present or not. If it is present, the
64QAM usage bit in the UE context is set to true and sixtyfourQamDlUsageInd IE is included in the
response message with value SixtyfourQamDlUsed .
2277
2278
2279
2280
2281
2282
The presence of MAC-ehs mode (HS-DSCH MAC-d PDU Size Format present in the HS-DSCH
Information with the value Flexible MAC-d PDU Size) and the test on the category (HS-PDSCH
Physical Layer Category IE with a value of 15, 16, 17, 18, 19 or 20 and a value of 19 or 20 for MIMO +
64QAM) are done by CCM CallP (see section 4.6.2.2). It might be necessary to repeat these checks at
PQ3 side in order to detect the inconsistencies in PQ3 specific test environment. The decision is left to
the development team.
2283
HSD Reconf
2284
2285
2286
For a call reconfiguration from MIMO to NON-MIMO, on a NBAP radio link reconfiguration, the field
MimoModeIndicator contained in HsdDschInfoToModify is set to MimoModeIndicatorDeactivate. The
MIMO usage bit is set to false in the UE Context and MIMO shall be deactivated.
2287
2288
2289
2290
2291
The HsdReconfPrepResp does not include the nCqiTypeAMCqiRatio in HsdInfoResponse and the
Number of Processes contained in HarqMemoryPartitioning corresponds to the non-MIMO scenario. In
case of use of Harq Memory Partitioning explicit, the structure HarqMemoryPartitioningExplicit does not
include the HarqMemoryPartitioningInfoExtensionForMimo field. (Today, only the Harq Memory
Partitioning mode implicit is supported.)
2292
2293
2294
For an Intra NodeB Cell Change Procedure with both source and target cells are MIMO capable and
MIMO configured on the call, the field MIMO Mode Indicator shall not be include in
HsdDschInfoToModify.
2295
2296
2297
For a call reconfiguration from NON-MIMO to MIMO, the field MimoModeIndicator contained in
HsdDschInfoToModify is set to MimoModeIndicatorActive. The MIMO usage bit is set to true in the
UE Context and MIMO shall be activated.
2298
2299
2300
2301
2302
2303
In the configuration message sent to the CE, new parameters shall be added (see section 4.6.5.6) :
2304
MIMO Activation (Boolean) set according the MIMO usage bit of the UE Context
2305
2306
2307
Dual ACK/NACK Threshold (5*16bits values) provided by the field HsdpaUcuParams during the
cell create (see section 4.6.4.1.1).
2308
HSD Migration
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 89/171
2309
2310
2311
2312
In response of an NBAP Radio Link Reconfiguration Request that demands a change of HSDPA Cell,
this news HSDPA cell is served by a scheduler on another modem controller.
At Hsd Migration Prepare, the HSD BBR checks whether the MimoActivationIndicator is set to true or
false.
2313
2314
2315
2316
2317
- If true, MIMO shall be activated, the MIMO usage bit in the UE context is set to true and the response
message includes the HsdInfoResponse IE with nCqiTypeAMCqiRatio and the Number of Processes
in HarqMemoryPartitioning. In case of use of Harq Memory Partitioning explicit, the field
HarqMemoryPartitioningInfoExtensionForMIMO
(optional)
shall
be
included
in
HarqMemoryPartioningExplicit. (Today, only the Harq Memory Partitioning mode implicit is supported.)
2318
2319
2320
The HSD BBR checks whether the SixtyfourQamUsageAllowedInd is present or not. If it is present, the
64QAM usage bit in the UE context is set to true and sixtyfourQamDlUsageInd IE is included in the
response message with value SixtyfourQamDlUsed .
2321
2322
2323
The BBR Monitor shall support the CDM changes for this feature (se section 9.2).
2324
2325
2326
2327
2328
2329
ExtendedTbSize: With MIMO, MAC-ehs scheduler shall support TB size up to 27464 bits with 16 QAM
and 42192 bits with 64 QAM.
The measurements for the two transport blocks for one user in case of dual stream.
The measurement of the ratio in percentage between dual stream transmission out of the total (single
and dual stream) transmission per TTI shall be forwarded through CPIF (see 5.2.4)
2330
4.6.4.2
2331
2332
2333
User Plane
2334
HARQ Process
2335
2336
2337
2338
2339
2340
2341
4.6.4.2.1.1
PARAMETER UPDATES
2342
There are two new parameters provided by HSDPA BBR(see section 4.6.4.1.3):
2343
2344
2345
2346
2347
2348
HsScchType3DualStreamSnr defines the additional SNR requirement due to higher code rate of
HS-SCCH type 3 of dual stream transmission. Used to Calculate the required HS-SCCH power
HS-SCCH
Ptx
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 90/171
2349
4.6.4.2.1.2
2350
2351
2352
CCM reports eCEM periodically with demanded power PCell. In a VAM capable cell (sector-carrier,
MIMO or non-MIMO), the demanded power shall be based on both Tx branches (i.e. PA1+PA2). There
is no impact in the scheduler with the introduction of VAM.
2353
2354
In case of one Tx branch failure, the reported power is from the working Tx branch (i.e either PA1 or
PA2, whichever is working).
2355
4.6.4.2.1.3
2356
The Channel Element (CE) shall provide following information to the HsScheduler every TTI:
2357
- Flag to indicate Type-A or Type-B CQI/PCI report (not used by the scheduler see section 4.6.5.5.4)
2358
- Flag to indicate single or dual stream CQI/PCI report (SS/DS see section 4.6.5.5.4)
2359
2360
- CQI_predicted (EcNt format, as done for legacy HSDPA scheduler) (one value for single stream
(CQI_S) and two values for dual stream CQI_1 and CQI_2 see section 4.6.5.5.4)
2361
2362
2363
2364
2365
2366
The timing constrains concerning the CQI measurement delay (the delay from the start of the CQI
measurement period in the UE to the start of the TTI in which the corresponding DL HS-PDSCH
transmission occurs) for MIMO users shall be same as legacy users. The CQI value shall be provided
with a delay of 9ms for all MIMO and non MIMO users.
2367
2368
2369
2370
2371
2372
The content of the ACK/NACK packet is described in section 4.6.5.5.3. Three ACK/NACK fields are
received (in MIMO, the CE does not perform hard decision regarding ACK/NACK for single and dual
streams and this decision is left to scheduler. It means the CE does not know if it is a single or dual
stream transmission). The scheduler shall have memorised the flag single/dual stream for the
transmission corresponding to know which field(s) to use.
2373
2374
2375
2376
The content of the CQI packet is described in section 4.6.5.5.4. A test is done on the SS/DS field to
know which CQI fields to use. In case of single stream, the CQI_s field shall be decoded, in case of dual
stream, the CQI_1 and CQI_2 shall be decoded. The decoded CQI value(s) shall be mapped into SINR
value.
2377
4.6.4.2.1.4
2378
2379
2380
2381
2382
2383
2384
For a scheduled user configured in MIMO mode, two HARQ processes are pre-selected (see TN-MAChs-803).
2385
2386
Harq Process 1(HP1) and HARQ Process 2 (HP2) are the two pre-selected HARQ Process. HP2 is
defined by:
2387
2388
2389
2390
The MAC-ehs scheduler must followed additional rules for the HARQ Process pre-selection phase (see
TN-MAC-hs-804):
UL PROCESSING
HARQ PROCESS
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 91/171
2391
2392
2393
2394
If there is a retransmission ready to transmit, because of its priority, choose HARQ Process 1 as the
process with the oldest packet.
2395
The mapping with the stream is done during TFRC phase (see section 4.6.4.2.2.2.2).
2396
4.6.4.2.1.5
2397
2398
2399
2400
2401
A test is done on the flag which indicates a single or dual stream CQI/PCI report provided by the
CE. If it indicates a single stream CQI/PCI report or if HP2 is not available to transmit (HP selected
previously see section 4.6.4.2.1.4), then :
2402
2403
2404
2405
4.6.4.2.2 UeContext
2406
4.6.4.2.2.1
2407
2408
In a first step, the UEContext receives the (N)ACK data. It calculates the target subframe number and
check the UL sync status.
2409
Then, the UeContext performs different actions for a specific HARQ process.
2410
2411
In MIMO mode, in case of dual stream transmission, the UeContext will contain two ACK/NACK datas
with two specific HARQ Processes. The process must be done for the two ACK/NACK datas.
2412
2413
In a second step, the UE Context receives the CQI value(s).(see UL Processing of HSDPA Scheduler
section 4.6.4.2.1.3).
2414
2415
2416
2417
In MIMO mode, the existing LUT table is used for 'single transport block Type A CQI' or 'Type B CQI'
(see UL Processing of HSDPA Scheduler section 4.6.4.2.1.3) testing SINGLE_STREAM_ONLY =
TRUE.
2418
2419
2420
In MIMO mode, a new LUT table is used when 'dual Transport block Type A CQI' is reported by UE
(means dual CQI/PCI report) testing SINGLE_STREAM_ONLY = FALSE. Refers to TN-MAC-hs-786
for the values of this news table:
UL PROCESSING
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 92/171
2421
2422
4.6.4.2.2.2
2423
2424
2425
2426
2427
2428
DL PROCESSING
HS-SCCH
2429
2430
2431
Because of the amount of information contained in the HS-SCCH type 3, 3 extra bits in single stream
and another 8 extra bits in dual stream are needed comparing to HS-SCCH type 1. It results that
additional power is required.
2432
2433
The following equation shall be used to calculate power for HS-SCCH type 3 used with MIMO (TNMAC-hs-788):
2434
128
HS SCCH
CPICH
PTx,
(u i ) = snrHS-SCCH_Type3 + PTx,PdBm
+ SINR Map,dB (u i ) + HS-SCCH (u i ) 10 log 10
- 10 log 10 (AOC coeff )
dBm
16
2435
Where,
2436
snrHS-SCCH_Type3
2437
2438
snrHS-SCCH_Type3
2439
2440
2441
SINRMap,dB(ui) is as defined in [A3] #145 converted to dB. The CQI value to be considered is the latest
single CQI (i.e. latest type A CQI with single TB or type B CQI).
2442
2443
HS-SCCH(ui) is as defined in [A3] #177. The input parameters to LUT, provided by CE every sub-frame,
are based on latest single CQI.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 93/171
2444
is defined as following :
2445
PHS PDSCH
MIMO =
PP CPICH + PS CPICH dB
2446
Where :
2447
PHS PDSCH is the total (i.e. across both Tx branches) allocated power.
2448
2449
P-CPICH
S-CPICH
2450
2451
2452
HS-PDSCH
2453
2454
2455
2456
2457
On a VAM capable cell (MIMO or non-MIMO), it is expected that the PA usage will be balanced
between PA-1 and PA-2. Available power for HSDPA shall be based on combined power of PA1 and
PA2. Under balanced PA usage (possible when all the common channels and all the existing
HSDPA
dedicated/shared channels are transmitted through VAM), Pav
shall be derived considering both Tx
branches (i.e. PA1 +PA2)
2458
2459
is available power for HSDPA considering both the Tx branches of VAM capable cell
Where, Pav
(sectorcarrier, MIMO or non-MIMO).
2460
2461
2462
2463
2464
2465
There are additional rules to the current procedure (TN-MAC-hs-182) of allocated power to HS-PDSCH
for a call configured in MIMO mode (refers to TN-MAC-hs 891).
HS-PDSCH
HSDPA
In MIMO mode, the calculation of Pav
(ui) (TN MAC-HS #183) is done as following using Pav
and considering both Tx branches (i.e. PA1+PA2) :
HSDPA
HS SCCH
PavHSDPA PTx
(u i )
2466
PavHS PDSCH (u i ) =
2467
2468
2469
2470
2471
Pav
shall be updated by the MAC-ehs scheduler as following (TN MAC-HS #247) whenever a user
HSDPA
has been selected from the ranking list. Pav
is initialised at the start of a HS-DSCH TTI according to
TN MAC-HS #169.
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
1
HSDPA
av
HSDPA
PTx
(ui) shall be calculated for MIMO or non-MIMO UE taking into account the total (i.e. across
both Tx branches) allocated power.
HS-SCCH
PTx
(ui) is total (i.e. across both Tx branches) HS-SCCH power for MIMO or non-MIMO UE.
HSDPA
W av
is updated according to (TN MAC-HS #248)
Note 1: In a call configured in MIMO, the transport block on each Tx Branch has the same total power
allocated than the other one. Available to both single and dual stream transmissions.
Note 2: In case of dual stream transmission, the power per OVSF code is divided evenly among the two
transport blocks. The power per OVSF code for each transport block is the same for all the OVSF codes
used. The power per transport block is the same for both transport blocks.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 94/171
2487
2488
2489
2490
2491
Note 3: The estimated SIR is computed by the scheduler based on the CQI, which is computed at the
UE assuming halving of power for dual stream transmission compared to single stream MIMO. So the
UE already accounts for the fact that power is split evenly among the two codewords.
2492
2493
2494
If SINGLE_STREAM_ONLY = TRUE (see section 4.6.4.2.1.5), the spectral efficiency SE(ui) for
the user is obtained using the existing algorithm and set SE(ui) = SE_single(ui)
2495
2496
2497
First calculating the SINRdB(ui) thanks to the SINRmap(ui) (using the CQI from the
latest single stream CQI report).(see the equation following or the TN-MAC-hs-815)
2498
2499
2500
2501
2502
2503
2504
2505
2506
First calculating the SINR1dB(ui) thanks to the SINRmap(ui) from the primary
stream(using the CQI1 from the latest dual stream CQI report).(see the equation
following or the TN-MAC-hs-815)
2507
2508
2509
2510
2511
2512
First calculating the SINR2dB(ui) thanks to the SINRmap(ui) from the secondary
stream(using the CQI2 from the latest dual stream CQI report).(see the equation
following or the TN-MAC-hs-815)
2513
2514
2515
2516
Following equation is used for MIMO UEs when single Type-A or Type-B CQI is received from UE :
2517
HS PDSCH
CPICH
CPICH
SINR dB (u i ) = SINR Map,dB (u i ) + Pav,
(u i ) PTx,PdBm
PTx,
dBm
dBm + (u i ) + 10 log 10 (AOC coeff )
2518
2519
2520
2521
2522
2523
2524
Following equation is used for MIMO UEs when dual Type-A CQI is received from UE (applicable
independently to both CQI values) :
2525
HS PDSCH
CPICH
CPICH
SINR dB (u i ) = SINR Map,dB (u i ) + Pav,
(u i ) PTx,PdBm
PTx,
dBm
dBm + (u i ) + 10 log 10 (AOC coeff )
2526
2527
2528
2529
Pav,dBm
is the value as taken from TN-MAC-hs-183 in dBm considering power from both PAs.
S-CPICH
PTx,dBm
is the Tx power of the S-CPICH for MIMO in dBm.
Other terms are as defined in TN-MAC-hs-188.
HS-PDSCH
Pav,dBm
is the value as taken from TN-MAC-hs-183 in dBm considering power from both PAs.
S-CPICH
PTx,dBm
is the Tx power of the S-CPICH for MIMO in dBm.
Other terms are as defined in TN-MAC-hs-188.
HS-PDSCH
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 95/171
2530
2531
2532
2533
2534
2535
2536
Note: The equation at present is the same for single stream and dual stream transmissions in MIMO
mode. It is an open issue whether to modify measurement power offset ( ) in accordance with reported
PCI for single stream transmission in MIMO mode. If it is decided to implement this, the equations for
single stream and dual stream transmissions in MIMO mode will be different as well.
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
Note: The modulation order of the primary transport block is always larger or equal to the modulation
order of the secondary transport block.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 96/171
2581
2582
2583
2584
2585
Note1: If UE reports dual CQI but the scheduler, decides to send a single stream transmission, the SE it
uses for single TB selection corresponds to CQI1. It happens if there is no paired HARQ Process
available or the case describes previously.
2586
2587
2588
2589
2590
2591
If the parameter isPrecodingWeightsetRestrictionPreferred provided by the bbr is set to true and if the
UE preferres a dual stream transmission (means SS/DS set to DS in the CQI packet received from the
CE), there is no modification of the PCI value.
2592
2593
2594
If the If the parameter isPrecodingWeightsetRestrictionPreferred provided by the bbr is set to true and
if the UE preferres a single stream transmission (means SS/DS set to SS in the CQI packet received
from the CE):
2595
2596
2597
2598
2599
If the PCI value is invalid (different than 0 or 3), the scheduler enforces the
valid PCI by sending to the CE the last valid PCI value received. If no valid
PCI value has been received before, the scheduler shall use the valid PCIs
alternatively in consecutive TTIs until valid PCI is received.
2600
2601
Note2 : In case of TFRC selection failure, set the flag SINGLE_STREAM_ONLY = TRUE. (TN MAC-HS
will be updated in Sept/October 2010)
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
Insufficient HSDSCH power, which resulted in low SINR. (since power is one of the input while
calculating SINR).
Low CQI reported by UE is not sufficient to transmit the retransmission TB.
Available codes are not sufficient for the retransmission TB. Number of codes is one of the input
for LUT lookup.
Primary TFRC lookup failure: set the flag SINGLE_STREAM_ONLY = TRUE. HP2 is
transmitted using the best CQI out of dual CQI report, if TFRC selection for this HARQ is
successful. Note that TFRC lookup is not performed for secondary stream in case both
transmissions are re-transmissions.
If secondary stream PDSCH codes are less than primary stream PDSCH codes, then set the
flag SINGLE_STREAM_ONLY = TRUE. Note that TRFC lookup for new transmissions cannot
fail.
Primary stream TFRC lookup failure: Transition set the flag SINGLE_STREAM_ONLY = TRUE
and transmit HP2 using best CQI out of dual CQI report, if TFRC chain for this HARQ passes.
If secondary stream PDSCH codes are less than primary stream PDSCH codes, then set the
flag SINGLE_STREAM_ONLY = TRUE. Note that secondary stream is new transmission and
hence TFRC lookup cannot fail.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 97/171
2632
2633
2634
2635
2636
The last step is to update the still left scheduling resources (used power and used codes) which would
be available to the next UE to be scheduled.
2637
2638
2639
2640
2641
2642
Store data to be sent in HARQ Process (according the rules seen previously)
2643
2644
These actions must be done for the two HARQ Processes in the UeContex in case of dual stream.
2645
2646
2647
2648
2649
2650
2651
2652
For MIMO Single stream users with QPSK or 16QAM, reservation of HS-SCCH index list will be
removed. 64 QAM users will be treated like any non-MIMO 64 QAM user
2653
For MIMO users with dual stream, following actions are taken.
2654
2655
2656
2657
2658
Reserve HS-SCCH index based on parity checks. Let Codes_WithP be the codes available
with parity
2659
2660
2661
2662
2663
2664
Note: TFRC_primary == PASS means, TFRC lookup for primary stream has returned valid TFRC
combination. It is same for TFRC_secondary as well.
2665
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 98/171
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
Else
o
2682
2683
2684
2685
There is a new CQI to SINR LUT for MIMO mode, dual transport block type A CQI report. See
4.6.4.2.2.1 UeContext Ul Processing.
2686
4.6.4.3
2687
2688
2689
2690
2691
The HSD BBR configures the flow control function, part of the framing protocol with a maximum bit rate
for the UE.
The HSD BBR takes into account the maximum data rate which depends on the HS-DSCH Physical
Layer Category. It shall take into account the MIMO activation which can transmit two transport blocks
within a TTI.
FRAMING PROTOCOL
UMT/BTS/DD/028488
HS-DSCH
category
Peak
data
(Mbps)
15/17
16/18
19
23.37
27.95
35.28
02.01 / EN
rate
Peak
data
rate for two
transport
blocks
(Mbps)
46.74
55.90
70.56
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 99/171
20
42.19
84.38
2692
2693
2694
2695
2696
In case of reconfiguration of the UE context (MIMO->non MIMO and non MIMO->MIMO), HSD BBR
informs the flow control instance associated to the Framing Protocol instance about the new maximum
bit rate.
2697
4.6.4.4
2698
2699
4.6.4.4.1 Power Reservation with MIMO for HS I/B Configured with minBR (fair
sharing)
2700
2701
2702
2703
2704
For PS I/B MAC-d flows having a GBR (through minBR when minBR is considered to be a GBR), the
power consumption is updated based on the NBAP measurement HS-DSCH Required Power Value;
The HS-DSCH Required Power Value indicates the minimum necessary power for a given priority class
to meet the Guaranteed Bit Rate for all the established HS-DSCH connections belonging to this priority
class i.e. per SPI. This measurement definition does not differentiate between users with/without MIMO.
2705
4.6.4.4.2 Power Reservation with Vam for R99 DCH (fair sharing)
2706
2707
2708
2709
2710
2711
2712
2713
The NBAP measurement Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, EAGCH, E-RGCH or E-HICH transmission is used to obtain the DCH power usage.
The Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or
EHICH transmission measurement reported by a VAM capable cell (MIMO or non-MIMO) shall be the
ratio between the sum of the total transmitted powers of all codes not used for HS-PDSCH, HS-SCCH,
EAGCH, E-RGCH or E-HICH transmitted on the cell (sector-carrier) and the maximum transmission
power the cell (sector-carrier). Here, the maximum transmission power is the mean power [W] on one
carrier from both the PAs.
2714
4.6.4.5
2715
Uplink
2716
There are changes because of the multiple values of CQI and ACK/NACK packets. See 4.6.4.2.1.
2717
2718
2719
In case of inconsistencies between the information already known by the scheduler and the information
provided by the CE, the packet will be ignored and a warning is generated (example: MT field == 0 for a
call configured in MIMO Mode).
2720
Downlink
2721
The HSDPA Scheduler send HS-SCCH+ and HS-PDSCH data to the OC+ CE.
2722
2723
Power Reservation
2724
2725
Xms give the modulation scheme(QPSK, 16QAM or 64QAM) for the primary transport block and
Xms stb, the modulation scheme for the secondary transport block
2726
2727
2728
Xtbs and Xtbs stb contain the transport bloc size information for the primary transport block and
secondary transport block
2729
2730
Xrv and Xrv stb contain the redundancy and constellation version coding for the primary block
and secondary block
2731
Xhap represents the HARQ Process identifier included between 0 and 15 for MIMO
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 100/171
2732
2733
2734
HS-PDSCH base addresses and HS-PDSCH base addresses stb correspond to the base
address of the corresponding HS-PDSCH packet for the primary transport block and the
secondary transport block.
2735
2736
The way to fill these fields doesnt change comparing with the existing except for the HS-PDSCH
Transmit Power.
2737
2738
2739
where
2740
2741
2742
2743
2744
Until now, this number of transport blocks was always one but now with MIMO, it can be two
transport blocks.
2745
2746
2747
The description of the changes in the HS-PDSCH is precised in section 4.6.5.5.7. It concerns the
indication of the MIMO mode in MT field and if the packet is for a primary transport block or a secondary
transport block thanks to P/S field. There is one HS-PDSCH packet per transport block.
2748
4.6.4.6
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
Among the counters described in section 6.3.1, MAC-ehs scheduler shall take into account:
Counters
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 101/171
2766
4.6.5 eCEM/Layer 1
2767
4.6.5.1
2768
2769
The OCPlus CE shall be capable of supporting HSDPA MIMO users with the following capabilities &
configurations:
Layer 1 Overview
2770
2771
2772
2773
Each MIMO user consumes 2 HSDPA resources (out of 128), remaining resources being
available for non-MIMO users.
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
(*)
2785
2786
CQI measurement delay is the same as for Dual Cell HSDPA: variable delay 9ms or 11ms.
2787
2788
2789
2790
2791
2792
2793
2794
2795
(*): With Feature 89411 Aggregate Throughput Increase, the max number of HS-PDSCH is extended to
90.
2796
(**): In a given subframe, a mix of HS-SCCH type 1 and type 3 can be supported.
2797
2798
2799
2800
The maximum number of HS-SCCH per subframe is also limited to the maximum number of
HSPDSCH CE resources. Example: 48 HS-SCCH with 2 transport blocks cannot be supported because
2x48>90.
2801
4.6.5.2
2802
2803
2804
The CE has two interfaces to the PQ3: one for the OC and one for the OCPlus. They are covered by the
OC Message Catalogue and the OCPlus Message Catalogue. The following sections detail these two
interfaces.
2805
4.6.5.3
2806
2807
The OC/PQ3 interface is modified in order to include the additional parameters for the configuration of
the S-CPICH.
CE Message Interface
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 102/171
2808
2809
2810
2811
On the reception of a NBAP message Cell Setup Request, when the cell is MIMO, one additional CE
Message SCPICH Setup Request is used. This message already exists but was not used in precedent
releases.
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
A new field Tx_Accumulator_Indicator is also added into the SCPICH Setup Request message in
order to indicate whether the S-CPICH is to be generated onto Tx_accumulator_A or
Tx_accumulator_B, as detailed in section 4.6.5.4.
Tx_Accumulator_Indicator can be equal to: Tx_accumulator_A, Tx_accumulator_B or Absent
Tx_Accumulator_A sums all transmitter output streams that will be sent to antenna A (also called
primary antenna). See Figure .
In the same manner Tx_Accumulator_B sums all transmitter output streams that will be sent to antenna
B (also called secondary antenna).
During a MIMO Cell Setup the SCPICH Setup Request is used with parameters:
Transmit_Diversity_Indicator = Inactive.
Tx_Accumulator_Indicator = Tx_accumulator_B.
In case of PA failure: Activation/Deactivation of the S-CPICH
2827
2828
2829
The activation/desactivation of the S-CPICH is done by changing its power level thanks to the NBAP
message Cell reconfiguration Request. On reception of this message, one CE message SCPICH
reconfiguration request is send to the OneChip.
2830
2831
2832
2833
2834
Note that despite the fact that the VAM will be reconfigured on a PA failure and so the S-CPICH no
more will be transmitted, the S-CPICH power level is reduced anyway for consistency. This is required
because the S-CPICH power level is used by the MAC-ehs scheduler for the SINR calculation
2835
4.6.5.4
2836
2837
The OCC procedure associated to the CE message SCPICH Setup Request shall be modified in order
to take into account the new parameter Tx_Accumulator_Indicator.
2838
2839
2840
In the OC, the 2 parameters Tx_accumulator_A and Tx_accumulator_B, which are provided by the
Cell Hardware Setup request message, indicate the stream index associated to the primary antenna A
and the stream index associated to the secondary antenna B that was reserved for the TxDiv modes.
2841
In case of a MIMO cell setup the S-CPICH channel is configured as shown in the following figure.
2842
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 103/171
TX_Accumulator_A
OneChip
Tx
Tx
Stream to VAM
Virtual Antenna 1
B
antenna A
A
B
TX_Accumulator_B
S-CPICH
A
Tx
Stream to VAM
Virtual Antenna 2
antenna B
No TxDiv mode
2843
2844
2845
2846
2847
2848
2849
2850
The two output streams Antenna A and Antenna B are sent to the VAM element inputs streams Virtual
antenna 1 and Virtual antenna 2 respectively.
2851
4.6.5.5
2852
The OCPlus/PQ3 interface is modified in order to include the additional parameters for MIMO.
2853
2854
2855
2856
2857
2858
2859
The 5 Ack/Nack thresholds of the VIE are mapped for MIMO as follows :
2860
2861
2862
2863
2864
The Ack/Nack user info field of uplink ACK/NACK packets shall contain 4 indicators:
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 104/171
2865
2866
2867
User configuration
(MT=bit1) , (DCT=bit0)
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
00 : Normal
01: DC
10: MIMO
UE in MIMO Mode
11: reserved
This naming convention is used in the present document not be necessarily in the OC Plus
Message Catalogue, which is the official specification document.
UE_Mode is not needed by PQ3, which has the information already, but may be used for alarm
management.
2879
2880
The 3 Ack/Nack indicators correspond to the outputs of the HS-DPCCH decoder that are systematically
decoded by the OC+.
2881
2882
It is up to the PQ3 to read them depending on UE_Mode and the existence of the secondary transport
block.
2883
2884
The table below indicates the list of fields in the Ack/Nack user info that have to be interpreted
depending on UE_Mode.
UE_Mode
Field
00
01
10
Normal
DC
MIMO
SC/DC
HDSC
Ack/Nack
Ack/Nack
Ack/Nack DS_PTB
Ack/Nack SS
Ack/Nack DS_PTB
Ack/Nack SC/DS_STB
Ack/Nack DS_STB
2885
New field added for MIMO
2886
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 105/171
Ack/Nack
Ack/Nack
DS_PTB
Ack/Nack
SSC/DS_STB
HDSC
SC/DC
The following figure is a proposal for the definition of Ack/Nack User. The official specification is given
in OC Plus Message Catalogue [R6].
UE_Mode
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
Type A: Contains the CQI for either one transport format or two transport formats depending on the
preferred number of transport blocks.
2897
2898
2899
2900
Type B: Contains the CQI for one transport format (i.e. CQI = CQI_s)
2901
2902
2903
The 2 types are multiplexed in time, using a dynamic ratio between the number of type A and type B.
This time multiplex, as detailed in 3GPP TS25.214 section 6A.1.2.2, depends on parameter MIMO
N/M Ratio and is known by the OCPlus.
2904
2905
The OCPlus decodes the composite PCI/CQI, depending on its type A or B and returns the following
indicators in the CQI user info field of uplink CQI packets:
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
Total DTX: True when the CQI/PCI has not been reported by the UE (i.e. PCI/CQI is seen
DTXed in all subframes of the CQI repeat interval)
During compress mode on DPCH or F-DPCH, the UE shall use DTX in conditions given in
3GPP TS25.214 section 6A.3.
Basically the behaviour with CM in MIMO is the same as for non-MIMO case.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 106/171
2923
2924
2925
CQI Single stream information: Set of information associated to the single stream (CQI_s)
It is always reported and updated (i.e. whatever the type decoded SS or DS)
It is composed of the following elements:
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
CQI Dual stream information: Set of information associated to the dual stream.
It is updated and reported only when dual stream is decoded.
It is composed of 2 sets of information, one set for the PTB and one set for the STB. Each set
is composed of the following elements:
2936
2937
2938
2939
2940
2941
2942
2943
2944
CQI Quality metric: Quality metric computed onto the joint PCI/CQI ????
The format of this metric is described in algorithm document [R4]
The format of the CQI user info field should be consistent with Dual Cell
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 107/171
2945
2946
The table below indicates the list of fields in the CQI user info field that have to be interpreted
depending on UE_Mode.
UE_Mode
Field
00
01
10
Normal
DC
MIMO
SS/DS
TypeA/B
Total DTX
Old/New
Erasure
SC/DC=Dual or SS/DS=Dual
SS/DS=Dual
SS/DS=Dual or SC/DC=Dual
SS/DS=Dual
SS/DS=Dual or SC/DC=Dual
SS/DS=Dual
CQI2 NMSE
CQI Mean
SC/DC=Dual
SC/DC=Dual
CQI2 Mean
SC/DC=Dual
PCI
2947
New field added for MIMO
2948
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 108/171
2949
2950
Mapping of MIMO elements into the PCI/CQI User Info Format (proposal):
Information Element
Field
CQI Mean
CQI NMSE
2951
2952
2953
The following figure is a proposal for the definition of PCI/CQI User. The official specification is given in
OC Plus Message Catalogue [R6].
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 109/171
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
PCI
SS/
DS
CQI
Erase
CQI
Old/New
CQI
Total DTX
Type
A/B
UE_
Mode
2964
Precoding Weight Set Restriction has not been configured by RNC on the UE,
2965
2966
Precoding Weight Set Restriction has been configured by RNC on the UE but it is noncompliant,
2967
2968
2969
2970
2971
The timing constraints are detailed in document OCPlus Tier0 document [R5] in section CQI Timing.
2972
2973
The CQI handling should be the same for Dual Cell and MIMO, this is mainly due to the fact that a cell
may handle DC and MIMO UEs simultaneously.
2974
So the CQI measurement delay for MIMO is variable (i.e. 9ms or 11ms) as for Dual Cell.
2975
2976
With a CQI Measurement delay of 9ms (resp. 11 ms), the scheduler uses CQI from subframe N-1
(resp. N-2) when making decisions associated with the Ack interrupt for subframe N.
2977
Since MIMO feature is requested on eCEM board, the interrupt mode is always set to latest cell.
2978
The CQI interrupt shall be positioned as it is done for Dual Cell case.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 110/171
2979
2980
2981
2982
2983
2984
In order to include new parameters introduced by HS-SCCH Type 3, the HS-SCCH+ Packet is
modified as follows:
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
Note (*): PCI is proposed to be communicated to and from the scheduler because the NodeB can
potentially override the UE recommendation, and it is currently not clear whether the scheduler would
play a part in that decision in a future version of the algorithm. The way the algorithm is defined
currently, the scheduler does not need to know the PCI - the CE can use whatever the UE reported, or
can potentially use a PCI predictor to recommend a precoder index different from the one reported by
the UE.
The decoding of HS-SCCH orders is not supported by the OC Plus.
3008
3009
Introduction
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
The format of the Hybrid-HARQ process information (Xhap) is different for non-MIMO and MIMO (range
0..7 for non-MIMO and range 0..15 for MIMO).
The HS-PDSCH is generated in the OCPlus CE using information coming from PQ3 thanks to HSPDSCH and HS-SCCH+ Packets. These packets contain the following additional fields for MIMO:
For MIMO there are 2 separate HS-PDSCH Packets for the transmission of the 2 transports blocks. The
2 packets can be distinguished thanks to P/S flag.
Behavior of the CE in case of a missing HS-PDSCH packet
If the HS-PDSCH packet for the secondary transport block is not received there will be no
secondary transport block transmitted. Note however that the primary transport block will be
transmitted if the HS-PDSCH packet for the primary transport block is received within the
allowable window (i.e. 1 ms before the HS-PDSCH subframe boundary). The CE does not
know or care that two transport blocks (primary transport block and secondary transport
block) are paired for MIMO.
Behavior if any HS-PDSCH packet is received late
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 111/171
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
In the current pre-MIMO HSTX implementation, a late error is flagged to the DSP if the
scheduler attempts to write to the HS-PDSCH Traffic Packet Buffer outside the write window in
which the scheduler owns the buffer (outside the write window = a scheduler write
attempt within 1 ms of the HS-PDSCH subframe boundary). In the specific case of MIMO with
two transport blocks where the HS-PDSCH packet for the secondary transport block is received
late, the CE behavior does not change from that described for pre-MIMO.
As documented in section 2.5.2.2.2 CQI Timing of the Tier 0, for MIMO with only a primary transport
block transmission the HS-SCCH encoding time in the CE increases. In the worst case (all HS-SCCH
are for MIMO with only a primary transport block) the total encoding time increases from ~.015 ms to
~.018 ms). This reduces the amount of time available to the scheduler for providing HS-SCCH packets
to the CE by ~.003 ms.
3039
4.6.5.6
3040
3041
This section gives the list of new parameters needed for MIMO and modifications done for existing
parameters.
CE Configuration parameters
3042
Parameter
Message
Type
Comments
Integer
S-CPICH activation
Boolean
MIMO activation
HS-DSCH Information
Element
Boolean
New parameter
Tx_Accumulator_Indicator
Boolean
HS-DSCH Information
Element
Dual ACK/NACK
Threshold
HS-DSCH Information
Element
5 x 16-bit values
New parameters
VAM coefficients
Ack Threshold
Nack Threshold
Ack/Ack(*) Threshold
Ack/Nack & Nack/Ack
Nack/Nack Threshold
3043
3044
4.6.5.7
3045
Introduction
3046
3047
The aim of the VAM function is to create 2 virtual antennas seen by the UEs, thanks to the 2 physical
antennas and with a weighting matrix as shown in the following figure.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 112/171
Cross polarized
antenna
3048
3049
3050
3051
v a e j1
v
VAM = 11 12 = 1 j
v21 v22 a3e 3
3052
a 2 e j2
a4 ej j4
3053
3054
3055
a1 a 2
Amplitudes =
=
a3 a 4
1
2
1
2
2 , Phases = 1 2 = 0 0
1
3 4 0 0
2
3056
3057
In case of a PA failure, the coefficients are reconfigured by the CCM OAM with the following values that
do not depend on coefficients a1 to a4 and 1 to 4:
3058
0 1
0 0
st
In case of 1 Tx branch failure: Amplitudes =
, Phases =
0
0
0 0
i.e. P2 <= V1
3059
1 0
0 0
nd
In case of 2 Tx branch failure: Amplitudes =
, Phases =
0 0
0 0
i.e. P1 <= V1
3060
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 113/171
3061
3062
3063
Due to the summation stages in the eCEM boards and xCCM, the VAM function is implemented in a
distributed manner as illustrated in the following block diagram.
3064
3065
3066
3067
In case of a non-VAM cell, the associated VAM element should be bypassed (P1<=V1; P2<=V2).
3068
3069
In case of multiple distributed VAM elements for one cell, it is not needed to synchronize their
configuration at a specific frame boundary.
3070
3071
3072
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 114/171
3073
complex multipliers
complex
complex
+
X
X
X
registers
+
BFN boundary
complex
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 115/171
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
For this reason, a direct mapping shall be implemented as represented in figure above.
Each VAM element is either activated when it is associated to one cell or not used.
Each VAM element for a non-VAM cell is bypassed. The bypass is directly performed by changing
coefficients.
The figure represents here functional multiplexers that will be certainly implemented thanks to a time
multiplexed mechanism.
VAM Configuration Parameters at FPGA Interface
VAM Parameters should be programmed by the PQ3 during start-up and during a cell setup or cell
reconfiguration.
Parameter
V11, V12, V21, V22
Update_Flag
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
Type
6x
2x2 Complex Matrix
Each coefficient is a
Complex <16,1,t>
6x
Boolean
Description
Per VAM element coefficient matrix
Timing Constraints:
There is no particular timing constraint concerning the VAM parameters update. Since other modules in
the FPGA combiner are updated on the BFN boundary, the same synchronization mechanism shall be
used for the VAM coefficients. PQ3 being able to write to VAM coefficients at any time (no constraint for
PQ3), a double-buffer mechanism is to be implemented using an update flag.
Since the cell reconfiguration is performed by independent per cell processes in PQ3, and since the
processes are not synchronized with BFN boundaries, update flag shall be separated per VAM element
(i.e. there is one update flag per VAM element at separated address).
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 116/171
3114
3115
3116
3117
3118
3119
Since this feature is supported only on eCEM and not xCEM, the interface changes are restricted to
eCEM-CCM and not xCEM-CCM ITF2. Nevertheless for compatibility UCU Manager on xCEM/PQ3
shall set maxDualCellHsdpaMIMOUsersAllowed to 0 in UcuMgrGetCeCapabilityResp message. xCEM
CallP shall propagate this information in CemCapacityResp message to CCM CallP so that it knows it is
an xCEM which cannot support MIMO (see section 4.6.3.4).
3120
3121
3122
3123
3124
3125
3126
No impact.
The remaining fractional part of the delay is compensated by the TRM in DL is already implemented in
the context of DC-HSDPA.
The fact that there are two DL paths Main and Div from CCM OAM point of view instanciated on 2 TRM
is transparent for TRM itself which is always configured with Main path.
3127
3128
3129
3130
3131
The remaining fractional part of the delay is compensated by the RRH. For DL this is already
implemented in the context of DC-HSDPA. For UL this has to be implemented.
3132
4.6.9 Loader
3133
No impact
3134
3135
No Impact.
RRH shall handle RE_SetDelayRequest message (Refer to section 12.1.4.2 for more details)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 117/171
3136
3137
3138
MIMO feature is not compatible with STSR x+y configurations (these two features use 2PA per sector
but in a different manner)
3139
3140
3141
To achieve maximum possible throughput from each Modem board for each MIMO cell, feature
Multiple xCEM per Carrier should be used.
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
It is possible to configure simultaneously a cell DC-HSDPA and MIMO capable for iBTS configurations
supporting MIMO which is a subset of iBTS configurations supporting DC-HSDPA.
A given UE can be DC capable, MIMO capable or both DC and MIMO capable but a call cannot be
configured in DC+MIMO simultaneously (Not allowed in Rel-8 standard).
Simultaneous DualCell-MIMO calls shall be rejected as detailed in section 4.1.2.5 Radio Link Setup.
Since such calls will be introduced in 3GPP Rel-9, for future compliancy, information elements for
DualCell and MIMO at all interfaces should not be exclusive.
3157
3158
3159
3160
Dual Cell HSDPA feature is supported in UA07.1 with some limitations. These limitations are removed in
UA08. The major impact to MIMO is the introduction of additional parameters used to indicate the
maximum number of users MIMO and DualCell that can be simultaneously handled by the eCEM board.
3161
3162
PsbSetup message is enhanced with S-CPICH power offset (see section 4.6.2.3).
3163
3164
3165
It is possible to activate PA Power Pooling with MIMO if the R99 cell associated to the MIMO cell is
configured with DualPaUsage set to Vam. (checked by CCM OAM see section 4.6.1.1).
3166
3167
3168
3169
3170
3171
This feature introduces a new parameter eCemxCemPreference. The interaction with MIMO is to add
the following check:
This parameter should be different from xCEM when there is 1 BtsCell MIMO or VAM on the
HsxpaResource.
3172
3173
3174
3175
3176
3177
3178
3179
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 118/171
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
Interactions:
With MIMO, one cell is being served by more than one PA/TRM.
Let's say cell 101 is being served by PAs 1 and 2, Cell 101 is MIMO capable. I propose the following if
there is an AC failure,
"PA 1" is part of the PAs that can be switched Off:iBTS can't send block resource request since RNC will trigger the cell delete after this request.
iBTS shall send RSI-SI for this cell with the MaxTxPower of PA2 and it shall also indicate that MIMO is
not capable. RNC would trigger cell reconfig request to iBTS with the modified MaxTxPower. This
reconfig request would inturn translate into Cell delete request for PA1/TRM1. This is similar to PA1
Failure sceanrio.
"PA 2" is part of the PAs that can be switched Off:
We can't send block resource request since RNC will trigger the cell delete after this message.
iBTS shall send RSI-SI for this cell with the MaxTxPower of PA1 and it shall also indicate that MIMO is
not capable. RNC would trigger cell reconfig request to iBTS. This reconfig request would in-turn
translate into Cell delete request on PA2. This is similar to PA2 Failure scenario.
Both PA1 and PA2 are part of the PAs that can be switched Off:No impact here. iBTS shall send Block resource request to RNC for the list of cells that are
served by these PAs.
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
This feature specifies the use of the Twin RRH equipement RRH2x40_2100MHz in WCDMA
applications in UA8/UA8.1/UA9 releases. This feature specifies the usage of the Twin RRH for the
configuration of a MIMO cell.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 119/171
3227
3228
3229
3230
MIMO feature tends to achieve up to 43.2 Mbps user peak throughput in ideal conditions (single UE
scenario) for a 3GPP Rel-8 Category 20 MIMO enabled UE.
3231
3232
With eCEM, it should be possible to achieve peak throughput of 43.2 Mbps for conditions mentioned
above. This assumes that 21.6 Mbps can be achieved for Category 14 UE.
3233
Nevertheless this section shall be updated to take into account DC HSDPA measur
3234
3235
3236
As done (or going to be) in the DC FN, the real throughput should be highlighted here. There are some
limitations implemented for 64QAM. The actual max throughput is not and will never be 21.6Mbps! So
the max MIMO throughput will never be 43Mbps.
3237
3238
3239
Also, for Dual cell there are some ongoing discussions wrt the achievable throughput depending if the
xCCM has a FE MDA or a GE MDA. Conclusions of these discussions/tests will have to be highlighted
in this FN as well see open issues [10] and [11].
3240
4.8.2 Dimensioning
3241
3242
To achieve 43.2 Mbps Mac-ehs throughput per cell on eCEM, each eCEM board should have one
sector only. Thus, cabinet should have eCEM boards in proportion of configured MIMO enabled sectors.
3243
4.8.3 Capacity
3244
3245
The hardware of the eCEM board can support up to 64 simultaneous MIMO and DualCell combined
users at maximum.
3246
In UA07.1.2, for eCEM board, the max number of DualCell users in 4 and MIMO is not supported.
3247
In UA8.0, for theCEM board, the maximum combined number of MIMO and DualCell users is 15.
3248
3249
3250
3251
3252
With eCEM: up to 43.2 Mbps MAC-ehs throughput per cell can be supported.
3253
4.8.4 Dependability
3254
Not impacted.
3255
3256
3257
This is the same in case of TRM failure we keep all cells alive but with less power.
3258
4.9 SECURITY
3259
Not impacted.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 120/171
3260
INTERFACES
3261
3262
3263
3264
3265
3266
3267
Note: Following data/structure definitions are just a proposal. Design teams shall discuss and finalize
the exact structure definitions. These finalized interfaces shall be maintained in the dedicated Interface
documents.
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 121/171
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
The messages HsdpaConfigRequest and LocalCellConfigRequest are modified as defined at ITF4 (see
section 5.2.3)
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
The following existing messages are enhanced with the new parameters:
HsdpaConfigRequest:
nCqiTypeAMCqiRatio
(enum) nCqiTypeAMCqiRatio : N_M_Ratio_1_2, N_M_Ratio_2_3, N_M_Ratio_3_4,
N_M_Ratio_4_5, N_M_Ratio_5_6, N_M_Ratio_6_7, N_M_Ratio_7_8, N_M_Ratio_8_9,
N_M_Ratio_9_10, N_M_Ratio_1_1
Default {N_M_Ratio_1_1}
(word32) hsScchType3SingleStreamSnr
(word32) hsScchType3DualStreaamSnr
LocalCellConfigRequest:
InternalDualPaUsage: (enum)
o VamDisabled,
o VamEnabled,
o VamDegradedToMainOnly,
o VamDegradedToDivOnly
UMT/BTS/DD/028488
02.01 / EN
Default{VamDisabled}
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 122/171
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
UcuMgrCellUpdateReq:
>> CellUpdate
>>>(enum)InternalDualPaUsage: VamDisabled, VamEnabled, VamDegradedToMainOnly,
VamDegradedToDivOnly default{VamDisabled}
>>>(word32)VAMAmplitudeCoeff [4] Range [0..1*10e9] * 10e-9 Default {707106781,
707106781, 707106781, 707106781}
>>>(word16)VAMPhaseCoeff[4] - Range [0..359] step 1 Default {0,135,45,0}
>>>(word8)IsPrecodingWeightSetRestrictionPreferred True, False Default{True} Optional
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 123/171
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
PsbCellSetupReq, PsbCellReconfReq:
>>PsbCellReq
>>> SecondaryCPICHInformation (optional)
>>>> CommonPhysicalChannelId Range[0..255]
>>>> secondaryCPICHPower (*) Range[-350..150] and FF not significant (S-CPICH not
configured)
>>>> txDiversityIndicator Enum: txDiversityActive, txDiversityInactive Default{
txDiversityInactive}
>>>> (word32) FDD DL Channelisation Code Number
>>>> (word32) secondaryScramblingCode (same as primary scrambling code)
(*) see note in next section.
3463
5.2.5 OC Interface
3464
3465
When
On reception of
Message to OC
Interface
SCPICH Setup
UMT/BTS/DD/028488
02.01 / EN
Additional Parameters
See
Section
4.6.5.3
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 124/171
3466
3467
3468
3469
3470
3471
3472
3473
NBAP
Cell Setup Request
Request (Message
Added)
On reception of
NBAP
Cell
Reconfiguration
Request
SCPICH
Reconfiguration
Request (Added)
DL Scrambling code
DL Channelization Number
CE Cell Index
Transmit Diversity Indicator=false
Tx_Accumulator_Indicator=Tx_Accumulator_B
(New parameter)
Secondary CPICH power(*)
4.6.5.3
3474
3475
3476
3477
The changes concern the Ack/Nack, PCI/CQI reporting and the VAM configuration.
When
On reception of NBAP Cell Setup
Request
On reception of NBAP Cell Setup
Request
See Section
4.6.5.5.1
HS Configuration Request
Bearer Traffic
Five Ack/NackThresholds
MIMO Activation indicator
MIMO N/M Ratio
UE_Mode
Ack/Nack SS
Ack/Nack DS_PTB
Ack/Nack DS_STB
UE_Mode
SS/DS
TypeA/B
Single Stream:CQI decoded, CQI
decoded EcNt format, CQI predicted,
CQI mean, CQI nvar, CQI Nmse
Dual Stream: 2 sets (CQI decoded,
CQI decode EcNt format, CQI
predicted EcNt format)
4.6.5.5.2
Bearer Traffic
UE_Mode
PTB/STB
Precoding Weight Info
HS-PDSCH base address for the STB
Transport block size index for the STB
Modulation scheme & Nbr of TB
HARQ process information
Size,RV & Constellation version
MT : MIMO Mode
P/S: Primary or Secondary TB
VAM Activation
VAM Coefficients
VAM Coefficients
4.6.5.5.6
Bearer Traffic
HS-SCCH+ Packet
Bearer Traffic
HS-PDSCH Packet
3478
3479
4.6.5.5.3
4.6.5.5.4
4.6.5.5.7
4.6.5.7
4.6.5.7
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 125/171
3480
3481
3482
3483
3484
3485
3486
3487
3488
13
14
15
13 + (nTrm*3)
14 + (nTrm*3)
type: SPECIFIC_REQ
Sub-type: ADD_LOCAL_CELL
MODIFY_LOCAL_CELL
Master_id:
Length _hi
Length_lo
Spare1
Spare2
Offset_ie
Local Cell Identifier
Number of TRM paths (nTrm)
(For each Trm path)
TRM path type
TRM number
Channel number
Logical Frequency Index
Cell Size
15 + (nTrm*3)
antennaConfiguration
16 + (nTrm*3)
17 + (nTrm*3)
dualCellActivation
18 19 20 21 +
(nTrm*3)
secondaryServingCellId
22 + (nTrm*3)
MimoActivation
2
3
4
5
6
7
8 9 10 11
12
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
(8-11)
..
..
(22 + nTRM*3)
MimoActivation
3500
3501
3502
3503
3504
3505
3506
3507
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 126/171
3508
5.2.9 CPRI
3509
3510
3511
3512
CPRI interface is impacted by UL delay alignment. The impact on existing interface definition is under
study.
See open issue [15].
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 127/171
3513
3514
3515
3516
3517
OAM
1..N
BTS Cell
1..N
1..N
RDN
1..N
0..N
Antenna Access
RemoteRadioHead
1..N
Local Cell Group
R99 RESOURCE
RDN
RDN
Antenna Connection
List
1
N
repeaterCellList
1..N
PA RESOURCE RRH
1
RDN
0..1
0..1
RDN
1..N
hsxpaResourceId
HSDPA RESOURCE
Antenna
Connection
paResourceIdList
RDN
1..N
1..N
rfCarrierId
RF CARRIER
1..N
RDN
1
r99ResourceId
1..N
RDN
Local Cell Id
HSDPA CONF
EDCH CONF
hsdpaResourceId
edchResourceId
1..N
PA RESOURCE
DualCellActivation
RDN
HSXPA RESOURCE
1..N
RDN
3518
3519
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 128/171
3520
3521
6.1.1 dualPaUsage
Source
Domain
object name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Upgrade rule
Check rule
Creation
BTS
BTSCell
dualPaUsage
The parameter defines whether the cell (sector-carrier) is configured with
two PAs.
Optional feature
No
0
Enum (None, Vam, VamAndMimo)
None
No
If this parameter is set to Vam or VamAndMimo and the cell (sectorcarrier) is equipped with one PA/RRH/TRDU, the BTS rejects the
configuration.
If this parameter is set to Vam or VanAndMimo and VAM Parameters are
not present or invalid, the BTS rejects the configuration.
If this parameter is set to none and two PAs/RRHs/TRDUs are used for
that cell (sector-carrier), the BTS rejects the configuration.
3522
3523
6.1.2 vamParameters
3524
3525
A new object will be supported for VAM related parameters. This object will be named VamParams and
its definition is the following:
Object
Path
Children
Link(s)
Identifier(s)
Cardinality
Create (off-line)
Create on-line
Delete on-line
MO presence
Object to lock
Property
BTSEquipment BTSCell
VamParameters
N/A
N/A
rdnId
0..1
Yes
NotAllowed
NotAllowed
Optional
N/A
Comments
SMO
3526
3527
3528
3529
3530
3531
3532
3533
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 129/171
3534
6.1.2.1
vamAmplitudeCoeff
3535
Source
Domain
object name
Sub-Managed Object
name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Upgrade rule
Check rule
3536
3537
3538
3539
Creation
BTS
BTSCell
VAMParameters
vamAmplitudeCoeff
The parameter defines four amplitude coefficients applicable to VAM matrix
in a MIMO or non-MIMO cell.
Optional feature
No
3
Fixed(4) List of Float 0..1 step 0.000000001 (i.e. step 10exp-9)
{0.707106781, 0.707106781, 0.707106781, 0.707106781}
No
Note: This is RAN model. in the BTS model and ASN1, the VAM parameter are INTEGER. The PQ3
receives the parameters with this format and shall do a conversion (multiply the parameter by 10exp9)
as detailed in the algorithm document [R12].
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 130/171
3540
6.1.2.2
vamPhaseCoeff
Source
Domain
object name
Sub-Managed Object
name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Creation
BTS
BTSCell
VAMParameters
vamPhaseCoeff
The parameter defines four phase coefficients applicable to VAM matrix in
a MIMO or non-MIMO cell.
Optional feature
No
3
Fixed(4) List of INTEGER 0..359 step 1
degree
{ 0, 135, 45, 0 }
{0, 135, 45, 0} is THE tuning to be used on a MIMO cell with PCI codebook
restriction in UA08.
Other tunings are problematic in a MIMO cell in terms of PA usage balance
and throughput degradation (see attachment for some W*VAM results) :
{0, 90, 90, 0} leads to PA usage imbalance.
{0, 0, 0, 0} is optimum for legacy non-MIMO UEs but results in ~24% cell
throughput degradation with MIMO UE (see attached ppt).
Upgrade rule
Check rule
3541
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 131/171
3542
6.1.3 IsPrecodingWeightSetRestrictionPreferred
Source
Domain
object name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Upgrade rule
Check rule
Creation
BTS
BTSCell
isPrecodingWeightsetRestrictionPreferred
The parameter defines whether precoding weight set restriction is preferred
at the cell (sector-carrier). If enabled, the NodeB conveys the preference
to RNC in NBAP AR/RSI message.
Optional feature
No
3 A1
Boolean (TRUE, FALSE)
TRUE
No
3543
3544
3545
6.1.4 nCqiTypeAMCqiRatio
Source
Domain
object name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Upgrade rule
Check rule
Creation
BTS
HsdpaConf
nCqiTypeAMCqiRatio
The parameter defines of ratio between the number N of dynamic
single/dual (Type A) CQI reports out of a sequence of M CQI reports in
case the UE is configured in MIMO mode.
Optional feature
No
3
Next RL Setup or Reconfiguration
ENUMERATED (1/2, 2/3, 3/4, 4/5, 5/6, 6/7, 7/8, 8/9, 9/10, 1/1)
1/1
None
3546
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 132/171
3547
6.1.5 hsScchType3SingleStreamSnr
Source
Domain
object name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Upgrade rule
Check rule
Creation
BTS
HsdpaConf
hsScchType3SingleStreamSnr
The parameter defines the symbol level SNR requirement of HS-SCCH
Type 3 of single stream transmission.
Optional feature
No
3
Real [-5.0..19.0] step 0.1 dB
1.4 dB
None
3548
3549
6.1.6 hsScchType3DualStreamSnr
Source
Domain
object name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Upgrade rule
Check rule
Creation
BTS
HsdpaConf
hsScchType3DualStreamSnr
The parameter defines the symbol level SNR requirement of HS-SCCH
Type 3 of dual streams transmission.
Optional feature
No
3
Real [-5.0..19.0] step 0.1 dB
2.3 dB
None
3550
3551
6.1.7 DualCellHsdpaMimoMaxNumberUserEcem
3552
3553
3554
3555
3556
3557
3558
3559
It is not strictly speaking a new parameter because this BTS parameter is shared with the 2 features
Dual Cell HSDPA Capacity Increase and MIMO.
It is used by the operator in order to limit the real maximum number of DC and MIMO users combined
that can be handled by the eCEM board.
Warning: This parameter is unconnected with a possible way to limit, at the RNC level, the number of
users per cell, as suggested in requirement R1 of FRS Dual Cell HSDPA Capacity Increase [R14].
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 133/171
Source
Domain
object name
parameter name
Definition
activationFlag
Optional
Category
Class
Associated Event
Range
Unit
Initial values
Recommended value
Upgrade rule
Check rule
Creation
BTS
BTSEquipement
dualCellHsdpaMimoMaxNumberUserEcem
This parameter represents the Maximum number of DC-HSDPA and MIMO users
combined (logical channel) allowed per eCEM board. Each DC-HSDPA or MIMO
user takes two resources, e.g. if value 15 is given, actually 30 resources will be
taken from ECEM board and thus, number of legacy HSDPA users is 128 30
(rather than 128 15). For UA08 release, there will be an internal limit on max
number of combined DC-HSDPA MIMO users per ECEM. This limit is named
internalMaxMIMODualCellHsdpaUsersAllowed, its value is limited to 15.
Moreover, internalMaxMIMODualCellHsdpaUsersAllowed is not configurable. If
value of dualCellHsdpaMimoMaxNumberUserEcem is greater than the internal
limit, the kept value is the MIN(dualCellHsdpaMimoMaxNumberUserEcem,
internalMaxMIMODualCellHsdpaUsersAllowed).
Optional feature
No
3-A1
[1..64]
Integer
15
15
No
No
3560
3561
3562
3563
3564
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 134/171
3565
3566
6.2.1 Alarms
3567
3568
3569
3570
3571
3572
3573
3574
3575
UNSUPPORTED EQUIPMENT / CEM alarm is used to indicate that the BTS hardware (CEM or PA) is
not compatible with MIMO configuration as described I section 4.6.1.2. The description (Reason field) of
this alarm shall be updated in order to include MIMO case, i.e. add the following text "the CEM is iCEM
or xCEM and the cell is configured with MIMO and/or VAM".
The existing TX Path Failure alarms cannot be used in the context of MIMO because those alarms
reflect a total outage of the BTSCells while in MIMO configuration, the service is still possible although
in degraded mode. A new alarm PARTIAL TX FAILURE is created for this purpose:
(1) Alarm cause M (v3)
(2) Cause value
(3) Object class M
(4) Equipment type M
(5) Description M
(6) Reason M
(7) Impacts M
PARTIAL TX FAILURE
TBD
ANTENNA ACCESS
SECTOR
This alarm indicates that one of the two TX paths has failed on a sector
One of the two Tx paths is lost for the cells configured on this sector
(vam or vamAndMimo)
Associated BTS cell works only with a single Tx path.
Check radio equipment and restart them if necessary. If the
equipment has to be replaced, refer to UMTS BTS Hardware
Maintenance Guides.
equipmentAlarm
equipmentMalfunction
Minor/Cleared
All
UA 08
FRS 83984
3576
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 135/171
3577
3578
3579
3580
3581
The following table sums up the errors associated to MIMO. It shows also the relationship with other
features for interworking (e.g. Dual Cell Capacity Increase).
Not a new Error message
3582
Received message
CELL SETUP
REQUEST
CELL SETUP
REQUEST
CELL
RECONFIGURATION
RADIO LINK
RECONF PREPARE
RADIO LINK
RECONF PREPARE
RADIO LINK
ADDITION
CELL SETUP
REQUEST
CELL SETUP
REQUEST
CELL SETUP
REQUEST
Presence of IEs
IE MIMO Pilot
Configuration
or
IE MIMO Pilot
Configuration Extension
IE Secondary CPICH
Information
IE MIMO Pilot
Configuration
or
IE MIMO Pilot
Configuration Extension
IE MIMO Activation
Indicator
And/or
IE Sixtyfour QAM usage
Allowed
IE MIMO Activation
And
IE Additional HS cell
Information RL Setup
Error Reference
Err_Mess 4.1.2.3-1
Err_Mess 4.1.2.3-2
Err_Mess 4.1.2.4-1
RL SETUP FAILURE
Logical error
Semantic error
Err_Mess 4.1.2.5-1
RL SETUP FAILURE
Logical error
MIMO not available
RL RECONF FAILURE
IE MIMO Activation
And
IE Additional HS cell
Information RL Reconf
Prepare
IE HS-DSCH FDD
Information
IE Primary CPICH
Information
>Transmit Diversity
Indicator
IE MIMO Pilot
Configuration
IE Secondary CPICH
Information
> Transmit Diversity
Indicator
Error/Type/Cause
CELL SETUP FAILURE
Logical error
MIMO not available
IE MIMO Activation
IE MIMO Activation
UMT/BTS/DD/028488
Err_Mess 4.1.2.5-2
RL SETUP FAILURE
Logical error
MIMO not available
Err_Mess 4.1.2.6-1
Err_Mess 4.1.2.6-2
RL ADDITION FAILURE
Requested configuration
not supported
CELL SETUP FAILURE
Requested Tx Diversity
Mode not supported
IE present
Err_Mess 4.1.2.7-1
Err_Mess 4.6.2.2-1
Err_Mess 4.6.2.2-2
Err_Mess 4.6.2.2-4
IE Sixtyfour QAM
Usage=Allowed
And
IE HS-DSCH MAC-d PDU size
Format
IE HS-PDSCH Physical layer
Err_Mess 4.6.2.2-5
CELL
RECONFIGURATION
FAILURE
Radio network Layer cause
= Requested Tx Diversity
not supported
RADIO LINK SETUP
FAILURE
MIMO Not Available
RADIO LINK SETUP
FAILURE
Protocol cause=Semantic
error
RADIO LINK SETUP
02.01 / EN
Preliminary
Err_Mess 4.6.2.2-3
Err_Mess 4.6.2.2-6
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 136/171
REQUEST
And
IE Sixtyfour QAM
Usage=Not Allowed
RADIO LINK
RECONF PREPARE
RADIO LINK
RECONF PREPARE
FAILURE
IE MIMO Activation
And
IE Sixtyfour QAM
Usage=Allowed
IE MIMO Activation
HS-DSCH Physical
layer Category
> HS-DSCH Information
to modify
HS-DSCH Physical
layer Category
> HS-DSCH Information
to modify
HS-DSCH Physical
layer Category
> HS-DSCH Information
to modify
3583
3584
3585
3586
3587
Protocol cause=Semantic
error
RADIO LINK SETUP
FAILURE
Protocol cause=Semantic
error
RADIO LINK SETUP
FAILURE
FDD MIMO not Available
RADIO LINK
RECONFIGURATION
FAILURE
MIMO not available
Err_Mess 4.6.2.2-7
Err_Mess 4.6.2.2-8
RADIO LINK
RECONFIGURATION
FAILURE
Err_Mess 4.6.2.2-10
RADIO LINK
RECONFIGURATION
FAILURE
Protocol cause=Semantic
error
Err_Mess 4.6.2.2-11
Err_Mess 4.6.2.2-9
3588
3589
6.3.1 Counters
3590
6.3.1.1
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
Counter #10205 shall be modified in order to report 2 separated screenings for the mean power
information for the Main PA (i.e. Physical antenna 1) and the Div PA (.i.e. Physical antenna 2).
The sum of the 2 screenings gives the operator the combined mean power for the cell.
Counter #10225 is retained with its existing functionality, but for Cells with Tx diversity such as MIMO
cells this counter reports the distribution curve of the combined power information for the Main PA and
the Div PA.
Avoid misunderstanding: the operation to be performed here is not the combining of the distribution
curves of powers but the distribution curve of the combined powers.
Just add to the counter description: For Cells with Tx diversity such as MIMO cells, this counter
provides the distribution curve of the combined power of Main & Div Tx transmitters.
It is up to the OAM CCM to sum the two powers from Main PA and Div PA, which come from separated
radio boards.
Two new counters #10228 & #10229 (as an example), under object BTSCell, are added in order to
report separated distribution curves for PA Main and PA Div. Their format is the same as for counter
#10225.
Since the radio boards ignore which PA is Main or Div, it is up to the CCM OAM to peg the 2 PA power
measurements to the appropriate counters #10228 and #10229.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 137/171
3613
6.3.1.2
3614
3615
3616
3617
Counters #10825 and #10826 are not modified but associated screening is modified to take into account
UE categories 19 and 20 (already done for DC-HSDPA which added categories 21, 22, 23 and 24).
3618
6.3.1.3
Counters that shall take into account dual streams for MIMO UEs.
3619
Counter_Name
#10806
HsdpaMACdPDUAckBits
#10807
HsdpaRxDataBitsMAChs
#10808
HsdpaTxDataBitsMAChs
#10809
HsdpaTxDataBitsSchedTot
al
#10810
HsdpaNbrACKRcv
Meaning
Number of successfully transmitted MAC-d
PDU bits (an ACK has been received for the
corresponding transport block).
Number of data bits received by the NodeB.
It corresponds to the bits of all the MAC-d
PDUs received in every FP data frame
Number of data bits (transport block size) first
transmitted by the MAC-hs. The
retransmissions are then not taken into
account, meaning that a block retransmitted
several times is only taken into account once
at the first transmission.
Number of data bits (transport block size)
scheduled any TTI, taking into account the
retransmissions. Any time a block is
retransmitted, its bits are added.
Number of acknowledged transport blocks
('ACK' received for a transmitted transport
block).
#10811
HsdpaNbrNACKRcv
#10812
HsdpaNbrDTX
#10813
HsdpaDiscMACdPDUsTime
rExpiry
#10814
HsdpaDiscTransportBlocks
OnMaxRetrans
#10815
HsdpaMeanNbrRetrans
UMT/BTS/DD/028488
Preliminary
Impact
For MIMO UE, calculate
bits transmitted per cell.
Same as for legacy UE.
For MIMO UE, calculate
bits received per cell.
Same as for legacy UE.
For MIMO UE, calculate
bits transmitted per cell.
Same as for legacy UE.
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 138/171
#10816
HsdpaDataBufferedNodeB
#10819
HsdpaReceivedCQI
#10825
HsdpaTTIperUEcat
#10826
HsdpaTxDataBitPerUEcat
#10828
HsdpaNbUserWithDataTTI
#10829
HsdpaBufferDelay
#10830
HsdpaMACdPDUAckBitsFo
rGbr
#10833
HsdpaGbrDeficitRatioPerSp
i
#10834
HsdpaGbrSatisfiedFlows
#10837
HsdpaMACdPDUAckBitsPe
rSPI
#10841
HsdpaModulationType
#10844
HsdpaGbrCodeRatio
#10846
HsdpaProvidedBitRate
#10848
HsdpaGbrFailedFlows
3620
3621
3622
6.3.1.4
3623
3624
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 139/171
#10850
Counter_Name: HsdpaMimoDualStreamFraction
FRS: 83984
FRS_name: MIMO
Standard: No
Apply to: BTSCellHSDPA
Unit: Percentage
Range:
Type: CUM
0 - 100
Meaning: Define fraction of HSDPA MIMO dual stream transmission out of the total (single and
dual stream) transmitted in 2 ms TTI
Triggering event: Updated at each TTI: +1 only if data to be transmitted (per category)
First release: UA8.0
Last release:
Family: HSDPA statistics
Screening: according to the UE category - table SCR_11
Notes:
Evolution:
3625
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 140/171
3626
3627
3628
3629
3630
3631
O&M PROCEDURES
Feature activation
3632
3633
3634
3635
3636
3637
Feature activation should not affect processing for legacy non-MIMO capable UEs. No functional
regression should be required for these legacy UEs. However, as mentioned in Section 4.8.3, total
number of HSDPA users supported per modem board gets affected due to extra resources required for
MIMO users.
3638
3639
3640
3641
Feature de-activation should not affect processing for legacy non MIMO capable UEs. In this case, even
the number of HSDPA users supported per modem board should not degrade (isofunctional as preMIMOHSDPA feature implementation). Note that to achieve isofunctionality, all HSDPA cells hosted on
that modem board should have feature deactivated.
3642
3643
3644
Feature de-activation will also declare corresponding local cells as MIMO Not Capable to RNC. RNC
should not place any call requiring MIMO capability for this local cell, but if this happens (inconsistent
RNC behavior), iBTS will reject such calls.
3645
3646
No impacts.
3647
3648
3649
3650
WIPS tool shall be modified to check the consistency between MIMO activation and HW available. The
objective is to make sure that verification is done within the configuration tool before the RNC and NodeB
configuration parameters are downloaded in the equipment.
3651
3652
WIPS tools is out of the scope of this document and checks for MIMO are described in the FTS
document [A1].
3653
3654
3655
3656
8.2 MS INTERWORKING
3657
3GPP Rel-8 UE supporting the feature (Categories 15, 16, 17, 18, 19, 20).
FIELD INTRODUCTION
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 141/171
3658
TOOLS IMPACTS
3659
3660
No impacts
3661
3662
3663
3664
The following structures shall take into account the reports of measurement for two streams.
3665
3666
3667
3668
3669
3670
For the moment, these structures evoluate with Dual Cell feature to consider two measurement reports
per UE Context (one per cell). With MIMO, we add two measurement reports per UE context in the
same cell. The constant CDM_MAX_NUM_HSD_CELLS_PER_UE_CXT should be extended for MIMO
and replaced by CDM_MAX_HSD_REPORTS_PER_UE_CXT (value 4). For the structure only impacted
by MIMO, the constant CDM_MAX_NUM_HSD_STREAMS_PER_UE_CXT (value 2) shall be used to
take into account the two measurements report per UE Context.
3671
3672
CdmHsdReportInd_t
3673
>CdmHsdReport
3674
>>CdmHarqAckSummaryData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3675
>> CdmHarqAckDetailData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3676
>>CdmDeltaUiDetailData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3677
>>CdmCqiValueDetailData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3678
>> CdmHsdpaAckNackInfoDetailData[CDM_MAX_NUM_HSD_STREAMS_PER_UE_CXT]
3679
>>> ack_nack_info_flags[CDM_MAX_HSD_MEAS] :
3680
3681
3682
3683
3684
>>CdmHsScchDataDetailData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3685
>>CdmSinrDbDetailData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3686
>>CdmSeDetailData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3687
>> CdmHsDschTbSizeDetailData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3688
>>CdmHarqAckSummaryData[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3689
>>CdmCqiCpichMeasurementDetailData
3690
3691
>>>CQI_Info[CDM_MAX_HSD_REPORTS_PER_UE_CXT] [CDM_MAX_HSD_MEAS]
>> CdmCqiValueSummaryData
3692
>>> cqi_value_min[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3693
>>> cqi_value_max[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 142/171
3694
3695
>>> cqi_value_mean[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
>>CdmCqiValueSummaryDataReduced
3696
>>> cqi_value_min[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3697
>>> cqi_value_max[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3698
>>> cqi_value_mean[CDM_MAX_HSD_REPORTS_PER_UE_CXT]
3699
3700
CdmHsdpaCellReportInd
3701
>CdmHsdpaCellReport
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
>> CdmHsdpaCellAllUesReportFullDetailData
>>> CdmHsdpaCellUeFullDetailedData[][CDM_MAX_NUM_HSD_STREAMS_PER_UE_CXT]
>>CdmHsdpaCellAllUesReportHarqDetailData
>>>CdmHsdpaCellUeHarqDetailedData[][CDM_MAX_NUM_HSD_STREAMS_PER_UE_CXT]
>>CdmHsdpaCellAllUesReportSchedulingInfoDetailData
>>>CdmHsdpaCellUeSchedulingInfoDetailedData[][CDM_MAX_NUM_HSD_STREAMS_PER_UE_CXT
]
>>CdmHsdpaPerfMeasSummaryData
>>>CdmHsdpaMacHsPerfMeasReport
3712
3713
3714
3715
>>>>(word8)HsdpaMimoDualStreamFraction[NBAP_MAX_HSDSCH_PHYSICAL_LAYER_CATEGORY
+1]; : Defines fraction of HSDPA MIMO dual stream transmission out of the total (single and dual
stream)
3716
3717
3718
3719
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 143/171
3720
10
OPEN ISSUES
Item
1.
Status
CLOSED
3.
Description
Counters #10205 and #10225 are duplicated for Main and Div Tx transmitters but the exact
way the PM provides screens is to be detailed
For TCP measurement CCM CallP needs to know which the Tx Main to launch the
measurement is. The way this information is provided by CCM OAM needs further
investigations.
CDM impacts are not defined.
4.
CLOSED
5.
CLOSED
If S-CPICH has different SF Code, then why extra resources are not allocated on CE for SCPICH? Load Balancing impacts?
To be checked. PSB-BBR is used to manage SCH, P-CPICH and S-CPICH. The SF for SCPICH is 256.
As done (or going to be) in the DC FN, the real throughput should be highlighted here. There
are some limitations implemented for 64QAM. The actual max throughput is not and will
never be 21.6Mbps ! So the max MIMO throughput will never be 43Mbps.
Also, for Dual cell there are some ongoing discussions wrt the achievable throughput
depending if the xCCM has a FE MDA or a GE MDA. Conclusions of these discussions/tests
will have to be highlighted in this FN as well.
Are we sure EVM requirements allow top achieve those peak throughput values even in very
ideal radio conditions?
According to the issues we already had to be able to achieve 20 Mbps with 64 QAM only, I
doubt that it is possible to achieve 43 Mbps with MIMO on top of 64 QAM.
Inorder to anticipate such issues, a study should be carried on about the EVM impact on
performance, and what are the realistic figures we can get, and what has to be done
specifically to avoid similar issues observed when testing 64 QAM.
New iteration 1.6 of FRS 83984 is not taken into account in the document.
OPEN
2.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
OPEN
CLOSED
CLOSED
OPEN
CLOSED
OPEN
OPEN
CLOSED
OPEN
CLOSED
OPEN
OPEN
3721
3722
3723
3724
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 144/171
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
11
3GPP
ALCAP
ALTP
DR1
FRS
FTS
AWGN
BBR
BLER
BRM
CAC
CCC
CCM
CE
CEM
CPIF
CPRI
CQI
CR
CRC
DCC
DDM
DDU
DTX
DTxAA
FA
FPGA
GBR
HARQ
HSDPA
HS-DSCH
HS-PDSCH
HS-SCCH
HSSL
IE
iMCTA
LUT
M*N
MCPA
MIMO
MMSE
MRC
NBAP
NBAPR
NMSE
N/M Ratio
NVAR
OAL
rd
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 145/171
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
OAM
OCC
OVSF
P-CPICH
PA
PCI
PDU
PQ
PTB
16QAM
64QAM
QPSK
R&CV
RL
RRH
SBBLINK
SCM
S-CPICH
SE
SINR
SLOAM
SPI
STB
STSR 2/3
STTD
TC
TFRC
TFRI
TRDU
TRM
TTI
TxAA
TxD
Twin RRH
UE
VAM
Wrt
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 146/171
3815
12
ANNEX
3816
This section is left for information but is not part of the MIMO specification.
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
When associating two MCPA/DDM or RRH or TRDU in MIMO in one sector, the main issue is the
uncertainty in the calibration data of the MCPA/DDM or RRH or TRDU in case of heterogeneous family
/vendor/ variant.
3830
3831
12.1.2.1
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
2 MCPA (MCPA 1 and MCPA2 are of any kind among all models),
o If the MCPAs used are of the same model, the delay dispersion is low and we will not need
any realignment. In case where MCPA are model different, we shall realign delays, Delay
provisioned on each MCPA has been verified in Lab.
3855
12.1.2.2
3856
3857
3858
3859
The modem compensates for the mean delay (model1) and mean delay(model2), the difference of
delays will have an average of zero but with a certain dispersion (variance) of the MCPA populations
What is the dispersion of delay difference? Mean () and standard deviation ().
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 147/171
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
Notations:
D1= delay of MCPA model1
D2= delay of MCPA model2
Variance =
Standard deviation = square root of variance
Standard deviation =
Tc= 1/3840000 = 260ns
Tc/4= 65ns
The square root of variance of the difference of delays (D1-D2) must be compatible of the accuracy of
+/- (Tc/4)
Variance (D1-D2) = Variance(D1)+ Variance(D2)
Variance (D1-D2) < (TC/4)
As we are looking for a constraint on an individual radio unit, we assume here that they are all
respecting a same limit of variation:
Variance(D1)= Variance(D2)
Variance(D1)+ Variance(D2) < (TC/4)
2 Variance (Di) < (TC/4)
Variance (Di) < (1/2)*(TC/4)
<(1/ 2) (Tc/4)
Finally
< 46ns
A radio unit (MCPA or RRH or TRDU) should have a delay variation
smaller than 46ns across the product population
3887
3888
3889
3890
3891
3892o
3893o
3894o
Population 3: TRDUs
3895
12.1.2.3
3896
3897
MCPA vendors have given statistics of delay dispersion across the population of MCPA, RRH, TRDU
that they deliver; these statistics are in the following table (focused on 2100MHz band)
Radio
module
Manufactu
rer
Pec code
Population
deployed
3898
Delay
statistics
requested
to product
manufactu
rer
Delay
statistics
(known /
Unknown
By Alcatel
Lucent)
Average
delay
in ns
Delay
variation
(standard
deviation
)
Are
delays
stable
enough
to use
this unit
in MIMO
sector?
in ns
<46ns
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 148/171
Radio
module
Manufactu
rer
Pec code
Population
deployed
Delay
statistics
requested
to product
manufactu
rer
Delay
statistics
(known /
Unknown
By Alcatel
Lucent)
Average
delay
in ns
Delay
variation
(standard
deviation
)
Are
delays
stable
enough
to use
this unit
in MIMO
sector?
in ns
<46ns
NTUM30AA
Yes (mail JL
th
Galiez 7
July 2008,
th
17 Sept
2008)
MCPA 45W
Powerwave
MCPA 45W
Powerwave
Unknown
MCPA 45W
Remec
Unknown
NTUM30CA
MCPA 45W
TAZ1.0
23491
Unknown
Delay not
declared by this
PA. Default
value to be used
by CCM OAM
42240
Andrew
Yes
MCPA 45W
MCPA-3
TAZ1.5
Andrew
NTUM90EA
37600
MCPA60WB (BBPD)
AlcatelLucent
NTUM30WA
2800
MCPA60WA
Andrew
NTUM30FM
10500
Yes
RRH 60-21
TRDU 40-21
Counted on
331 units
82.256
OK
73.79
0.17
OK
Not
supported
Yes
RRH 40-21
TX path
RRH 40-21
RX path
Counted on
364 units
0.136
Min
81.886
Max
82.668
Yes
AlcatelLucent
Yes
Counted on
140 units
74.50
Counted on
798 units
798 units)
Yes
Unknown
Andrew
Yes
(Message to
Andrew A
th
Pierrard 10
Sept 2008)
Unknown
OK
13.23
OK
140
This is a
hw bug
that will be
corrected
for most of
the
population
Counted on
Andrew
0.21
OK
after bug
correction
3899
3900
3901
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 149/171
3902
12.1.2.4
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
The following table compares real MCPA delays and delays declared by MCPA firmware
Real delays have been measured in Alcatel-Lucent radio laboratory on the following MCPA models:
V01.06
measured
delay
(B/M/T) in
ns
34
85 / 82 /
84
19 / 19 /
20
85 / 82 /
84
19 / 19 /
20
75 all
19
ANDREW
V01 04
(012710):
V01.10
75
73,17
3JR 21001 BA
ANDREW
not exist
ANDREW
V04 08
89 / 82 /
89
81,3
900MHz/55W/2C
NTUM30GA
3JR 21000 HA/
NTUM30EM
90 / 81/ 89
81,3
850MHz/45W/2C
NTUM30EA
ANDREW
1800MHz/45W/3C
NTUM30DA
ANDREW
1900MHz/45W/3C
NTUM30PA
ANDREW
code
Original
design
HW
release
SW release
2100MHz/45W/4C
NTUM30AA
PW
V2 25
2100MHz/45W/4C
NTUM30AA
ANDREW
V04 01
2100MHz/45W/4C
NTUM30AA
REMEC
2100MHz/45W/4C
NTUM30CA
ANDREW
2100MHz/45W/4C
NTUM30CA
REMEC
2100MHz/45W/3C
NTUM90EA
ANDREW
2100MHz/45W/3C
NTUM90EA
POWERWAVE
2100MHz/60W/3C
3JR 21100 AA
ANDREW
2100MHz/60W/3C
NTUM30FM
1900MHz/60W/2C
900MHz/55W/1C
UMT/BTS/DD/028488
??
V04 01
??
V03 02
Kirk 01
ANDREW
02.01 / EN
V03 02
Preliminary
84 / 83 /
85
74 /74 / 77
32 to 34 ns
delay
coded
(ns)
Difference
None
None
81,3
< 4ns
16,26
81,3
16,26
73,17
16,26
81,3
73,17
32,52
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
< 4ns
< 4ns
< 4ns
< 2ns
< 3ns
< 4ns
< 2ns
< 8ns
< 8ns
< 4ns
< 4ns
< 2ns
Page 150/171
2100MHz/60W/2C
3926
3927
3928
3929
3930
NTUM30WA
10
NORTEL
8,13
< 2ns
This table shows that real MCPA delays are very close to delays declared by MCPA firmware: the
difference is always below 8 ns while the acceptable tolerance is 46ns.
3931
12.1.2.5
3932
3933
3934
3935
3936
3937
3938
As firmware delays are trustable, we can define mixity rules for MCPA in MIMO solutions.
The 2 MCPA in a sector may be of different types (PEC code) MCPA delays will adjusted in xTRM
according to MCPA delay in firmware (from the previous table, we know that this declared delay is very
close to real delay). In case of MCPA mixity, if we need to realign transmit paths, we will use the
TX_INT_DELAY value of BBPD FPGA, it enables the xTRM/xTRM2 to delay its TX path up to 1.5 Tc
(394 ns)
3939
12.1.2.6
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
This chapter deals with transmit realignment (Mandatory for MiMo or Tx div configuration), in case of
transmit realignment, we shall take into account the delay difference between Main Path & Diversity
Path.
Dl_Delay_Realignment_Main
Dl_Delay_Realignment_Div
= 0;
= 0;
As the radio delay reported to CEM can be different from original delay (due to modem compensation of
fiber)
Realignment (due to Fiber)
If (T12(Main path) >= T12(Div path) )
Delay_Realignment_Main += T12(Main path) - T12(Div path);
Else
Delay_Realignment_Div += T12(Div path) - T12(Main path) ;
RRH delays are modified in order to provide, to the CEM, delays multiple of UMTS Chip (Tc), as the
delays are provided in Tc/32, the value provided must be a multiple of 32.
Integer DL Delay Main Path X = 32*ceil( (Global DL Delay Main Path X+ Dl_Delay_Realignment_Main) /32); next integer part
Integer DL Delay Div Path X = 32*ceil( (Global DL Delay Div Path X + Dl_Delay_Realignment_Div /32); // next integer part
RRH_OAM_DL_Delay_Main += (Integer DL Delay Main Path X - Global DL Delay Main Path X) ; // RRH delays to CEM
RRH_OAM_DL_Delay_Div += (Integer DL Delay Div Path X - Global DL Delay Div Path X);
// RRH delays to CEM
RRH adjustment DL Delay Main Path X= (Integer DL Delay Main Path X - (Global DL Delay Main Path
X+Delay_Realignment_Main ))
RRH adjustment DL Delay Div Path X = (Integer DL Delay Div Path X - (Global DL Delay Div Path X +
Delay_Realignment_Div));
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 151/171
3979
3980
3981
3982
3983
3984
3985
As the delay between CEM and antenna is equal to the static delay DL delay, the difference for Main &
Div path will be compensated by the modem. Once Fractional delay part is added to the RRH we get a
global delay which is equal to the integer part:
Global DL Delay Main Path
Global DL Delay Div Path
Type: SPECIFIC_REQ
Sub-type: LOCAL_CELL_DELAY
Generic part
Nb of Local Cell Id
Local Cell Id #1
DL Delay Main Path #1 = CCM DL + RRH_OAM_DL_Delay_Main
DL Delay Div Path #1 = CCM DL + RRH_OAM_DL_Delay_Div
UL Delay Main and Div Path #1
UL Delay Div Path #1
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 152/171
4000
4001
In this example :
Site 1
RRH
RRH
CPRI
BTS
Site 2
RRH
RRH
Site 3
RRH
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
RRH
First RRH:
T12 = (T14(1) Toffset(1))/2;
= 710
T34 = (T14(1) Toffset(1))/2;
= 710
CCM_UL_BBLINK_OFFSET
= mod(T14(1), 800);
= 643
Second RRH:
T12 = (T14(1) + Nframe_diff(1) Toffset(2) + TBdelayDL(1) - TBdelayUL(1) )/2 ;
T12 = (1443 + 96 23 + 5 67)/2
= 727
T34 = (T14(1) + Nframe_diff(1) Toffset(2) - TBdelayDL(1) + TBdelayUL(1) )/2 ;
T34 = (1443 + 96 23 -5 +67)/2
= 789
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 153/171
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
CCM_UL_BBLINK_OFFSET
1) OAM CCM collects all different delays (startup & RF inventory ..):
Tx Main path:
iCCMu(902) + RRH_T2A (1843);
Tx Div path:
iCCMu(902) + RRH_T2A (1843);
Realignment (due to Fiber)
T12(Div path) = 727
T12(Main path) = 710
Dl_Delay_Realignment_Div += T12(Div path) - T12(Main path) ;
= 17;
It means that Div Signal arrives 17Tc/32 after Main path, which is correct (+5 for TBDL & +12 for
20meters of cable)
RRH_OAM_DL_Delay_Main += (Integer DL Delay Main Path X - Global DL Delay Main Path X) ; // RRH delays to CEM
= 1843 + (2752 - (902+1843)=
= 1850
RRH_OAM_DL_Delay_Div += (Integer DL Delay Div Path X - Global DL Delay Div Path X);
// RRH delays to CEM
= 1843 + (2784 - (902+1843)=
= 1882
RRH adjustment DL Delay Main Path X= (Integer DL Delay Main Path X - (Global DL Delay Main Path
X+Delay_Realignment_Main ))
=( 2752 - (902+1843+0))
= 7;
//we have to add 7Tc/32 on the xTRM Main
RRH adjustment DL Delay Div Path X = 2784 - (902+1843+17) ;
= 22;
//we have to add 22Tc/32 on the xTRM Div
0
1
2...7
8
9-12
13-15
16-18
19-21
4083
4084
4085
4086
4087
= mod(T14(1), 800);
= 643
Type: SPECIFIC_REQ
Sub-type: LOCAL_CELL_DELAY
Generic part
Nb of Local Cell Id
Local Cell Id #1
DL Delay Main Path #1 = 2752
DL Delay Div Path #1 = 2784
UL Delay Main and Div Path #1
UL Delay Div Path #1
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 154/171
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
5) Bilan
The CEM will delay its main path of (109Tc) round(2752 / 32 ) = 23 Tc
The CEM will delay its Div path of (109Tc) round(2784 / 32 ) = 22 Tc
The RRH Main will have an additional delay of 7 Tc/32
The RRH Div will have an additional delay of 22 Tc/32
Delay DL main =CEM(23*32) + iCCM(902) + Fiber_1km(614)+ RRH (1843 + 7) = 4102 Tc/32
Delay Div =CEM(22*32) + iCCM(902) + Fiber_1km(614) + TBdelayDL(5) + Fiber_20m(12) + RRH
(1843 + 22) = 4102 Tc/32
Note: The final downlink delay is equal to static delay (109) + T12(1)
4107
4108
4109
Results are :
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
Tx Delay
Measured at centre frequency.
Number of RRHs measured = 798
Variation = 13.53ns.
ACTION ITEM: The specification for the allowable measurement tolerance needs updated. It is
currently at +/- 40 ns. It appears from the factory test that this tolerance can be tightened up quite a bit.
The HW development team needs to confirm an achievable value that will avoid the issue with not
meeting the differential delay requirements and at the same time not impact the yield level from the
factory.
4124
4125
12.1.4.1
4126
4127
There should be no issue on filter side for MIMO2*2 as the same DDM is driving the 2 antennae on the
same DDM for a sector.
4128
12.1.4.2
4129
This chapter describes how to realign UL signal data path of data flow i(extracted from STSRx+y FN)
4130
4131
In the MiMo configuration, there are two UL data paths from different RRH for each local cell, the UL
delay difference between Main Path and Diversity Path is determined by these two factors:
4132
4133
4134
4135
CCM_UL_BBLINK_OFFSET
The CCM_UL_BBLINK_OFFSET corresponds to the delay mismatch of the CCM due to the BBLINK
reframing, the UL CCM propagation delay may be different for each optical link, the UL real CCM
propagation delay = Fixed_VALUE - CCM_UL_BBLINK_OFFSET.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 155/171
4136
4137
4138
4139
4140
4141
The optical fibers paired RRH used may have different length, in order to multiply UL signal from main
and diversity path correctly, the UL optical delay offset should also be considered.
4142
4143
4144
Uplink: T34
4145
4146
Where
4147
4148
4149
4150
4151
As data flow is sampled at 3.84 Mbps in the modem, so modem is easy to adjust the delay which is
integer of Tc, and because RRH samples the radio signal at a higher speed, it is easy to delay the
signal of fractional of Tc, so we propose is that the integer part of delay can be forwarded to CEM to
adjust, and the decimal fraction part can be forwarded to RRH to adjust.
x-CEM
i-CEM
OAM
CPRI RE
GetDelayt
Req
GetDelayR
CPRI RE provides :
-T2A,TA3, Toffset,
NFramediff, TB DL,TB UL
OAM perform
realignment if needed
LocalCellDela
SetDelatR
eq
SetDelay
Rsp
LocalCellDela
LocalCellConfigReq
LocalCellConfigRsp
4155
4156
4157
For both star mode and daisy chaining mode, the Uplink delay offset is determined by CCM UL dynamic
delay ( mod (T14(1) ,800 ) ,because of CPRI RTT ) and UL Optical link delay (T34), therefore the Uplink
delay realignment formula is applicable for star and daisy chaining configuration.
4158
4159
Our Uplink realignment proposal is that the integer part of Tc is compensated in modem side, the
fractional part is compensated in Radio module side.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 156/171
4160
1)
4161
UL_Delay_Realignment_Main = 0
4162
UL_Delay_Realignment_Div = 0
4163
4164
4165
4166
Else
4167
4168
4169
4170
4171
UL_Delay_Realignment_Div
CCM_UL_BBLINK_OFFSET (Div)
4172
Else
4173
4174
UL_Delay_Realignment_Main
CCM_UL_BBLINK_OFFSET (Main)
+=
+=
CCM_UL_BBLINK_OFFSET
(Main)
(Div)
CCM_UL_BBLINK_OFFSET
4175
2)
4176
4177
4178
To achieve to a perfect correction of Main & Div path in the modem, we shall provide to the CEM delays
which are multiple of Tc, as the delays are provided in Tc/32, the delays provided to the CEM shall be a
multiple of 32.
Integer UL Delay Main Path = 32*ceil ((Global
UL_Delay_Realignment_Main) /32) //next integer part
4181
4182
4183
4184
Note (1): Global UL Delay Main Path & Global UL Delay Div Path is the sum of all the different delays
collected by OAM CCM:
4185
4186
4187
4188
UL
Delay
Main
Path
(1)
4179
4180
As the delay between CEM and antenna is equal to the static delay, the difference for Main & Div path
will be compensated by the modem. Once Fractional delay part is added to the RRH we get a global
delay which is equal to the integer part:
4189
4190
4191
3)
4192
4193
RRH UL delay value should be modified because of UL delay offset and the decimal part compensation
in order to provide CEM multiply of Tc delay.
4194
RRH_OAM_UL_Delay = Ta3
4195
4196
// RRH
4197
4198
// RRH
4199
4200
RRH adjustment UL Delay Main Path = (Integer UL Delay Main Path X - (Global UL Delay Main Path
+UL Delay_Realignment_Main ))
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 157/171
4201
4202
RRH adjustment UL Delay Div Path = (Integer UL Delay Div Path - (Global UL Delay Div Path + UL
Delay_Realignment_Div));
4203
The UL delay should be adjusted in RRH will be sent via CPRI C&M command RE_SetDelay_Request
4204
4205
4206
4207
4208
4209
4210
Current CCM OAM thought for all cells in one Tx Path/ Rx Path have the same DL/ UL delay, identically
for different carriers, and although each cells UL delay (Ta3) is carrier dependant for ex-Lucent RRH,
this value is similar with the delay (mid band delay) retrieved before carrier configuration (the offset is
less than 100ns), therefore CCM OAM use the mid band delay value to replace each carriers delay.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 158/171
4211
4212
4213
4214
4215
Figure
below describes the process to calculate the UL delay offset for a paired RRH, trigger
Set Delay Sequence for RRH to adjust the fractional part of UL delay offset, and trigger
Local cell delay sequence for all corresponding cells.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 159/171
4216
4217
4218
4219
4220
1)
At the beginning of Rx Path configure sequence, if the radio module is CPRI RE,
send the RE_Get Delay Request to CPRI RE to retrieve detail delay values
(Toffset, TBdelayDL, TBdelayUL, N_Framediff) and store them in the
corresponding RRH instance, get the T14(1) value via call function
CPRI_R21_Coarse_Timer provided by CPRI Driver
4221
4222
4223
4224
4225
4226
4227
2)
4228
4229
4230
4231
3)
According to the formula: RRH adjustment UL Delay Path = (Integer UL Delay Path
- (Global UL Delay Path +UL Delay_Realignment) calculate the fractional part
delay for paired RRHs. If the delay is not zero, trigger the Set Delay sequence to
notify RRH to align the delay.
4232
4233
4234
4235
4236
4237
4)
For each cell, if the cells delay state is in CELL_CEM_DELAY_OK, which means
this cells delay info has previously sent to modem and will be updated after Set
Delay Sequence, trigger a local cell delay sequence to update its integer part of UL
delay to modem. If cells delay state is in NO_CEM_DELAY_SENT, no need to
trigger local cell delay sequence, because after the physical cells operational state
is ok, CCM OAM will trigger this sequence.
4238
4239
4240
1)
4241
USequenceParameters
4242
4243
SParamForSetDelaySeq setDelayParam;
4244
4245
typedef struct
4246
4247
CAbstractRrh * pRrh;
4248
u32 DLdelay;
4249
U32 ULdelay
// unit: Tc/32
4250
} SParamForSetDelaySeq
4251
4252
4253
4254
2)
During the CPRISetDelay Sequence, CCM OAM will build the RE_SetDelay
Request message to CPRI RE according to the delay value and Rrh instance, and
until receives RE_SetDelay Response close the sequence, If the set delay failure,
raise a alarm HW not consistent
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 160/171
4255
4256
4257
4258
4259
According to the formula Integer UL Delay Path = 32*ceil ((Global UL Delay Path +
UL_Delay_Realignment) /32) supply the function to calculate the integer part UL delay
sent to modem.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 161/171
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 162/171
{
if( rfchain == MAIN )
ULOffset = T14Div - T14Main;
}
else
{
if( rfchain == DIV )
ULOffset = T14Main- T14Div;
}
if( T34Main >= T34Div ) //get T34 offset
{
if( rfchain == MAIN)
ULOffset + = T34Main - T34Div;
}
else
{
if (rfchain == DIV)
ULOffset + = T34Div - T34DMain;
}
4261
return ULOffset;
UMT/BTS/DD/028488
}
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 163/171
4262
4263
4264
4265
In the case of daisy chaining configuration, the UL delay offset is also caused by the
CCM dynamic delay and UL optical link delay.
4266
4267
4268
4269
4270
4271
4272
4273
4274
The RRHxs UL optical link delay calculation depends on that REC should have already
obtained the RRHs dealy info in previous rank.
4275
4276
4277
4278
4279
4280
4281
4282
One main principle of software upgrade in daisy chaining is that if RRH in higher rank
starts up faster than the previous RRH, CCM OAM will not allow to start the Rf Inventory
Sequence, until after all RRH in the chain are software updated, this principle avoids the
case that REPROXY report the RRH delay info in higher rank while it can not obtain the
previous RRHs delay info. Therefore CCM OAM can calculate RRHx s UL optical link
delay via retrieving the TBdelayDL & TBdelayUL value in lower Rank RRHs( i =1,..x-1).
In a simple word, the UL delay alignment proposal is general for star and daisy chaining
configuration.
),
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
Rx delay
4298
4299
12.1.5.1
4300
4301
4302
4303
4304
4305
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 164/171
4306
12.1.5.2
4307
4308
4309
4310
4311
4312
xTRM provide its delay at startup using BoardInitRsp () used during the start up sequence
PA , DDM and TX splitter delays are recovered through TRM during the inventory process
RF_Inventory_Req ()
4313
12.1.5.3
4314
4315
4316
Delay is provided to the modem through the LocalCellConfig (xCEM) and LocalCellDelay (iCEM).
Delay is provided to xTRM through new message SetAdditionalDelay.
(i/x)
CCM
(i/x)
CEM
(i) CEM programs static and
dynamic registers with default
values
BoardInitReq
BoardInitRsp
StatusReq
StatusRsp
CellMappingReq
All the cells must be here declared
CellMappingRsp
CellDelayReq
Static and dynamic registers
are reprogrammed with real
values
CellDelayRsp
4317
4318
4319
4320
4321
4322
Delay is provided to the modem through the CellDelayReq (iCEM) or via LocalCellConfig (xCEM)):
0
1
2...7
8
9-12
13-15
16-18
19-21
Type: SPECIFIC_REQ
Sub-type: LOCAL_CELL_DELAY
Generic part
Nb of Local Cell Id
Local Cell Id #1
DL Delay Main Path #1
DL Delay Div Path #1
UL Delay Main and Div Path #1
4323
4324
4325
4326
4327
4328
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 165/171
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
The integer part is compensated in the modem when OAM CCM provides the delay.
DL Delay Main Path & DL Delay Div Path are the sum of all the different delays collected by OAM CCM:
DL = DL (CCM) + DL(CEM) + DL (TRM) + DL (PA) + DL (DDM) + DL (TMA) + DL (TxSplitter) + DL (Cable)
The Radio Module delay is adjusted such a way the delay provided to the modem is a multiple of
WCDMA chip, such a way the compensation is done in modem part.
DL Delay Main Path
DL Delay Div Path
As a consequence of reducing the delay provided to the modem the modem will compensate the delay
path to reach a fix delay.
4360
4361
4362
4363
4364
To achieve to a perfect correction of Main & Div path in the modem, we shall provide to the CEM delays
which are multiple of Tc, as the delays are provided in Tc/32, the delays provided to the CEM shall be a
multiple of 32.
4365
4366
To achieve that we will compensate at xTRM side such global downlink delay achieve the next multiple
of 32.
4367
4368
4369
The compensating part of the delay is compensated by the xTRM using a SetAdditionalDelay_req (shall
be introduced), this new request will act on the BBPD FPGA of the xTRM (present also in xTRM2), the
signal pass through the BBPD FPGA even if we dont use predistorsion.
4370
4371
With the actual BBPD FPGA implementation it is possible without any new FPGA delivery to modify the
transmit path via register configuration.
4372
4373
SetAdditionalDelay_req will act on register ALG_MNGT_REGISTER bits 5 to 0 are used to set 64fc
extra delay of the Tx path.
4374
4375
4376
4377
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 166/171
4378
4379
4380
The SetAdditionalDelay_req will provide the delay to be added in Tc/32, the xTRM shall perform a
translation in 64fc clock cycle:
4381
4382
4383
4384
4385
4386
=> BBPD_FPGA_WRITE(
4387
(ALG_MNG_IDX == 10) ,
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
Tx Main path:
iCCM(902) + xTRM (1955) + MCPA powerwave 2100MHz/45W/3C NTUM90EA delay (2) + DDM(3) + cable (1)
Tx Div path:
iCCM(902) + xTRM (1955) + MCPA ANDREW 2100MHz/45W/4C NTUM30AA delay (10) + DDM(3) + cable (1)
1) OAM CCM collects all different delays (startup & RF inventory ..):
Main
Div
= 2863
= 2871
Main path adjustment:
Integer DL Delay Main Path X
= 2880 - 2863 ;
= 17
// additional delay set on xTRM
// to reach global delay provided to modem
= 2880 - 2871 ;
= 9
// additional delay set on xTRM
// to reach global delay provided to modem
0
1
2...7
8
9-12
13-15
16-18
19-21
Type: SPECIFIC_REQ
Sub-type: LOCAL_CELL_DELAY
Generic part
Nb of Local Cell Id
Local Cell Id #1
DL Delay Main Path #1 = 2880
DL Delay Div Path #1 = 2880
UL Delay Main and Div Path #1
4423
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 167/171
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
SetAdditionalDelay_req(17 );
SetAdditionalDelay_req(9 );
5) Global delays
The CEM will delay its main path of (102Tc) round(2880 / 32 ) = 12 Tc
The CEM will delay its Div path of (102Tc) round(2880 / 32 ) = 12 Tc
The xTRM main will have an additional delay of 17 Tc/32
The xTRM div will have an additional delay of 9 Tc/32
Delay main
=
=
Delay Div
=
=
4450
4451
4452
4453
No additional work is needed as these modules shall support delay adjustment via the RE_Set_Delay
Request commands.
4454
4455
12.2.2.1
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
UA7.1 or UA8: xTRM will be commanded to adjust TX paths delays Main and Div. the command Set
delay will be introduced. The delay adjustment is done by the BBPD FPGA (even if Base Band
Predistorsion is not used) .This will allow general mixity across the MCPA populations and types.
4469
12.2.2.2
4470
4471
For STRS3-M MIMO on iBTS: The iBTS is currently limited to 2xTRM due to the TRM mastership
algorithm to manage the DDM. This limitation should be extended to 3xTRM. Consequently, the TRM
TRM delays depends on the number of configured carriers in sector. The delay changes as the TX
channelizers are cascaded in another manner and if some frequencies are switched in the base band
filtrer.
CEM/CCM/TRM use cases must be reworked to define the messages to reconfigure delay values when
they are changing in TRM for the previous reasons.
Specific issue to be looked at in the possibility to support mixity between xTRM and xTRM2.
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 168/171
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
This paragraph describes how to make a STRS3-M MIMO configuration. See next figure. MIMO
requires twice more TX channelizers resources for TX Main+ div than for TX Main only:
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 169/171
This architecture assumes also that the STRS3-M configuration in WIPS is completely recabled, and
reconfigured from scratch.
On the RX side, each of the three xTRM may be assigned a single frequency in reception. This
eliminates the xTRM constraint of frequency adjacency: f1, f2, f3 may be not adjacent since assigned
on different xTRMs.
As 3 slots are taken for xTRMs, 4 slots remain available for xCEMs in Macro iBTS
iBTS
6 Rx
signals
Div
Main
xTRM
TX M f1, f2, f3 S1,
TX D f1, f2, f3 S1
Rx MD f1 S1S2S3
xCEM
xCCM
HSSPC
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
xTRM
TX M f1, f2, f3 S2,
TX D f1, f2, f3 S2
Rx MD f2 S1S2S3
f1,f2,f3 Main
f1,f2,f3
Main MCPA
f1,f2,f3
Div MCPA
DDM
f1,f2,f3 Div
MCPA
DDM
MCPA
xTRM
TX D f1, f2, f3 S3
TX D f1, f2, f3 S3
RxMD f3 S1,S2,S3
MCPA
DDM
MCPA
Figure 23: MIMO solution for iBTS Macro STRS3-M (not supported)
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 170/171
4569
4570
4571
4572
4573
iBTS
Div
Main
TRM or
(i/x)TRM f1,f2
xCEM
processes
TX f1, f2 M
Rx f1,f2
Main1, Div1
MCPA
DDM
MCPA
DDM
MCPA
DDM
MCPA
DDM
MCPA
DDM
MCPA
DDM
4 antennas
per sector
HSSPC
xCCM
4574
4575
4576
ot
rte
o
pp
su
TRM or
(i/x)TRM
processes
TX f1, f2 Div
Rx f1,2 Main2,
Div2
f3
Figure 24: MIMO solution for iBTS Macro STSR1+1 TX2, RX4 (not supported)
4577
4578
UMT/BTS/DD/028488
02.01 / EN
Preliminary
09/08/2010
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel-Lucent written authorization
Page 171/171