STISS ASB RRH2 60W 21C PowerSaving v1.1

ISS Test Strategy for PowerSaving RRH60 21C iBTS (FRS
131826)
Document number:
Document issue:
Document status:
Date:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
UMT/BTS/DJD/044741
V01.01/EN
Approved standard
11/Nov/2014
Alcatel-Lucent Proprietary Use pursuant to applicable agreementsPassing on or copying of this document, use and communication of its
contents not permitted without AlcatelLucent written authorization
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other
trademarks are the property of their respective owners
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for
inaccuracies contained herein.
Copyright 2010 Alcatel-Lucent. All rights reserved.
34
35
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made
available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization.
36
Not to be used or disclosed except in accordance with applicable agreements.
STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826
37
38
PUBLICATION HISTORY
24/September/2014
39
Issue V01.00 / EN, Draft, created by Shen Yi
40
41
Modified by Shen YI base on STISS_for_ASB_RRH_V01.02.docName are

changed and add cases for PowerSaving feature test.
42
43
11/November/2014
44
Issue V01.01 / EN, Approved standard, modified by Shen Yi
45
Modified by Shen YI according to the review opinions
46
Passing on or copying of this document, use and communication of its contents not permitted without AlcatelLucent written
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 2/174
CONTENTS
47
48
INTRODUCTION ........................................................................................................................ 6
49
1.1 OBJECT...................................................................................................................................... 6
50
1.2 SCOPE OF THIS DOCUMENT .............................................................................................................. 6
51
1.3 AUDIENCE FOR THIS DOCUMENT ........................................................................................................ 6
52
2.1
53
54
DOCUMENTS............................................................................................................................. 6
REFERENCE DOCUMENTS ...................................................................................................... 6
GENERAL TEST CONSIDERATION.............................................................................................. 7
55
3.1
IBTS CONFIGURATIONS
56
3.2
TEST ENTRY AND EXIT CRITERIA .................................................................................................... 7
57
58
59
3.2.1
ENTRY CRITERIA: ........................................................................................................... 7
3.2.2
EXIT CRITERIA: .............................................................................................................. 7
3.3 TEST ENVIRONMENT .................................................................................................................. 7
60
3.4
DEFECT AND TRACKING .............................................................................................................. 9
61
3.5
FRS REQUIREMENTS AND COMPLIANCES ........................................................................................ 11
3.5.1
3.5.2
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
.............................................................................................................. 7
FRS REQUIREMENTS AND MAPPING ................................................................................... 11

ISS TEST COVERAGE ................................................................................................. 11
TESTS DESCRIPTION............................................................................................................... 13
4.1
REGRESSION TEST ................................................................................................................... 13
4.1.1.
OAM TEST ................................................................................................................ 13
4.1.1.1. PM_COUNTER .................................................................................................. 13
4.1.1.2. OMCB OPERATION ............................................................................................... 18
4.1.1.3. TIL OPERATION .................................................................................................... 20
4.1.2.
RADIO TEST .............................................................................................................. 22
4.1.2.1. BASIC CALL ......................................................................................................... 22
4.1.2.2. RADIO POWER TEST ............................................................................................. 29
4.1.2.3. R99 TEST ............................................................................................................ 30
4.1.2.4. HSUPA RESOURCE .............................................................................................. 32
4.1.2.5. MOBILITY TEST ..................................................................................................... 32
4.1.2.6. RADIATING ........................................................................................................... 35
4.1.3.
ENDURANCE .............................................................................................................. 39
4.1.3.1. OAM EDURANCE .............................................................................................. 39
4.1.3.2. RADIO EDURANCE ........................................................................................... 42
4.1.4.
UA6.0 FEATURE TEST ................................................................................................ 43
4.1.4.1. MIX MODE ........................................................................................................... 43
4.1.4.2. AISG-LITE........................................................................................................... 43
4.1.4.3. 10/20KM FIBER .................................................................................................... 44
4.1.4.4. 6 CPRI LINK ....................................................................................................... 47
4.1.4.5. POWER POOLING .................................................................................................. 58
4.1.5.
UA7.1 GENERAL TEST DESCRIPTION FOR FRS33519 DAISY CHAIN ................................. 61
4.1.5.1. LINK STATUS ........................................................................................................ 61
4.1.5.2. LOOP BACK .......................................................................................................... 63
4.1.5.3. ALARM ................................................................................................................ 64
4.1.5.4. PLUG IN/OUT ........................................................................................................ 65
4.1.5.5. SW UPGRADE ...................................................................................................... 66
4.1.5.6. DOWNLOAD ......................................................................................................... 69
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 3/174

4.1.5.7. START-UP............................................................................................................ 70
4.1.5.8. RESET................................................................................................................. 72
4.1.5.9. CELL PROCEDURE ................................................................................................ 76
4.1.5.10. RADIO FOR DAISY CHAIN ..................................................................................... 77
4.1.6.
UA7.1 GENERAL TEST DESCRIPTION FOR FRS73695 STSRX+ Y .................................... 80
4.1.6.1. START-UP............................................................................................................ 80
4.1.6.2. PLUG IN/OUT ........................................................................................................ 82
4.1.6.3. RESET................................................................................................................. 84
4.1.6.4. OMC-B OPERATION.............................................................................................. 86
4.1.6.5. CELL PROCEDURE ................................................................................................ 88
4.1.6.6. TMA MANAGEMENT .............................................................................................. 92
4.1.6.7. FAULT MANAGEMENT ............................................................................................ 94
4.1.6.8. COMMON MEASUREMENT ...................................................................................... 95
4.1.6.9. DELAY MANAGEMENT ............................................................................................ 96
4.1.7.
FRS 34454 CAPACITY LICENSE ENHANCEMENT ............................................................ 98
4.1.8.
FRS 34396 RRH PA AUTO SWITCH OFF .................................................................. 102
4.1.8.1. LED FOR ASB RRH .......................................................................................... 102
4.1.8.2. VSWR .............................................................................................................. 103
4.1.8.3. SINGLE RX PORT................................................................................................ 105
4.1.8.4. ASB RRH EXTERNAL ALARM TEST ....................................................................... 106
4.1.8.5. ASB RRH INTERNAL ALARM TEST ........................................................................ 107
4.1.8.6. UNBLANCE RF POWER TEST ................................................................................ 158
4.1.8.7. AC POWER TEST ................................................................................................ 159
4.1.8.8. POWER CONSUMPTION TEST ................................................................................ 159
4.1.9.
AISG FULL .............................................................................................................. 160
4.1.9.1. RESET............................................................................................................... 161
4.1.9.2. DEVICE DATA ..................................................................................................... 161
4.1.9.3. UPLOAD ............................................................................................................ 162
4.1.9.4. TILT ................................................................................................................. 163
4.1.9.5. TMA ................................................................................................................. 165
4.1.9.6. ABNORMAL CASES .............................................................................................. 167
4.2 POWERSAVING FEATURE ......................................................................................................... 168
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
125
126
127
128
129
130
131
132
SETUP/DELETE ONE CELL ON 21C RRH WITH ASB PA VENDOR ........................................ 168
SETUP/DELETE TWO CELLS ON 21C RRH WITH ASB PA VENDOR ...................................... 169
SETUP/DELETE THREE CELLS ON 21C RRH WITH ASB PA VENDOR .................................... 169
SETUP/DELETE FOUR CELLS ON 21C RRH WITH ASB PA VENDOR ..................................... 170
SETUP/DELETE ONE CELL ON 21C RRH WITH GEWEI PA VENDOR ..................................... 171
SETUP/DELETE TWO CELLS ON 21C RRH WITH GEWEI PA VENDOR ................................... 171
SETUP/DELETE THREE CELLS ON 21C RRH WITH GEWEI PA VENDOR ................................. 172
SETUP/DELETE FOUR CELLS ON 21C RRH WITH GEWEI PA VENDOR................................... 173
133
5.
TEST CROSS REFERENCE ................................................................................................ 174
134
6.
ABBREVIATIONS................................................................................................................ 174
135
136
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 4/174
137
138
139
140
141
142
143
List of Figures
FIGURE 1: ISS TEST ENVIRONMENT FOR STAR MODE ............................................................. 8
FIGURE 2 ISS TEST ENVIRONMENT FOR DAISY CHAIN MODE ............................................ 9
FIGURE 3: STARTUP WITHOUT FIRST SCAN FAST ................. ERROR! BOOKMARK NOT
DEFINED.
FIGURE 4: AISG IN TIL ................................................ ERROR! BOOKMARK NOT DEFINED.
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
List of Tables
TABLE 1: REGRESSION CASE COVERAGE LIST ............................................................... 11
TABLE 2 : FEATURE CASE COVERAGE LIST ..................................................................... 12
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 5/174
160
1 INTRODUCTION
161
1.1 OBJECT
162
163
This document mainly describes the test strategy, test cases and cases description for FRS
131826.
164
165
166
The purpose of this document is to describe the ISS test that should to be done in order to
validate ASB_RRH60W 21C used in UMTS. The test platforms are on rack (2U, 2UV2, 2UV3,
and V5 if it is possible) in release LR15.2.
167
168
1.2 SCOPE OF THIS DOCUMENT
169
The scope of this document is to give:
170
Test configuration, test coverage, test cases list and cases description.
171
172
1.3 AUDIENCE FOR THIS DOCUMENT
173
1.
This document can be a reference for ASB_RRH60W 21C PowerSaving DEV team
174
2.
This document can be a reference for ASB_RRH60W 21C PowerSaving PRI_INT team
175
3.
This document can be a reference for ASB_RRH60W 21C PowerSaving ISS team
176
177
4.
This document can be a reference for ASB_RRH60W 21C PowerSaving ST team
178
2 DOCUMENTS
179
2.1
REFERENCE DOCUMENTS
180
[R1]
STISS_FOR_ASB_RRH_v01.02
181
[R2]
FN131825&131826_Power_saving_for_RRH60_21C&RRH2x60
182
[R3]
HLD_LLD_PowerSaving_131825_131826
183
[R4]
UMT/BTS/DD/021952 CPRI Radio Module Management v1.6
184
[R5]
ARD546 RF Transceiver Unit External Software Description v4.5
185
[R6]
UMT/BTS/DD/00371 UMTS OMC-B / NodeB Interface Data Model
186
[R7]
UMT/BTS/DD/0260 iBTS Alarm Dictionary
187
[R8]
UMT/BTS/DD/0420 iBTS Observation SFS
188
189
[R9]
BTS/DD/025375V05 STSRx+y RRH supported functional specification

v01.05
190
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 6/174
191
3 GENERAL TEST CONSIDERATION
192
3.1
193
All configurations include STSR1/2/3, STSR1+1/2+1/2+2 in star and daisy chain mode.
IBTS CONFIGURATIONS
194
195
3.2
TEST ENTRY AND EXIT CRITERIA
196
3.2.1
Entry Criteria:
197
Global Pre-integration gives the GREEN flag
198
Basic Pre-Init testing (GA testing) are completed.
199
200
All test tools (including Lamp, Lamp, TM500, UE, and so on) should be ready and work
well
201
3.2.2
202
100% of identified tests executed with >85% pass rate at TCFP without critical CR
203
>95% pass rate at DR4 without critical CR
204
Any failed test cases documented via CR
205
206
ISS Test Report- identifies feature testing done and any problems found
207
3.3
TEST ENVIRONMENT
In this section, it describes the configuration of test environment.
208
209
210
211
Exit Criteria:
1.
Star Mode
During the test campaign of ASB RRH, we will config RRH as Star mode as following
figure 1.
212
213
In this configuration, it is possible to config platform with STSR1, STSR2, STSR3, STSR4,
STSR x+y.
214
215
216
217
Note: There are some restrictions of SW, the max cell is 12 on BTS. So we can config 12
cells or less than 12 cells on BTS. For STSRx+y, we should be config paried RRH as
following configuration: 01 and 04, 02 and 05, 03 and 06 with paired RRH, 01,02,03 is
Main RRH, and 04,05,06 is Diversity RRH.
218
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 7/174
Optical
Fiber Line
RRH01
RRH02
PCM
Cable
catapult
ATM switch
RRH03
dBTS/2UV1/2UV2
RRH04
Ethernet Line
Ethernet switch
Ethernet Line
Ethernet Line
RRH05
RRH06
OMC-B
TIL
219
Figure 1 ISS test environment for star mode
220
221
222
223
224
2.
Daisy Chain Mode

During the test campaign of ASB RRH, we will config RRH as Daisy Chain mode as
following Figure 2.
225
226
In this configuration, it is possible to config platform with STSR1,STSR2,STSR3,STSR4,

STSRx+y.
227
228
229
230
231
Note: There are some restrictions of SW, the max cell is 6 on one fiber chain. So we can
config 6 cells or less than 6 cells on one fiber chain. For STSRx+y, we should be config
paried RRH with conjoint RRH, and set RRH with minor reuid as Main RRH, and larger
reuid as Divesity RRH. For example: 01 and 02, 03 and 04, 05 and 06 with paired RRH,
01,03,05 is Main RRH, and 02,04,06 is Diversity RRH.
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 8/174
PCM
Cable
catapult
Optical
Fiber Line
ATM switch
RRH01
RRH02
RRH03
RRH04
RRH05
RRH06
dBTS/2UV1/2UV2
Ethernet Line
Ethernet switch
Ethernet Line
Ethernet Line
OMC-B
TIL
232
233
234
Figure 2 ISS test environment for daisy chain mode
235
Hardware Requirement:
236
1)
D2UV2/3 and V5 if available
237
2)
ASB_RRH60W 21C with ASB and Gewei PA,Others vendors RE
238
3)
AISG Full 2.0:Dual TMA AISG2.0,Single RET AISG2.0,Multi RET AISG2.0,ETC
239
4)
RNC simulator :Lamp or Lamp
240
5)
UE simulator:TM500 or data card
241
6)
WMS (OMCB) server
242
7)
Performance Spectrum Analyser
243
Software Requirement:
244
245
1)
Test
platform
package,TIL,etc )
246
2)
Lamp scripts(for auto case test)
247
Link Setup:
248
1)
CPRI LINK BETWEEN ASB_RRH60W 21C AND D2U
249
2)
CPRI LINK BETWEEN ASB_RRH60W 21C AND other REs
250
3)
Ethernet cable between TIL and D2U
251
4)
RF cable between TwinRRH and UE/UE simulator
252
5)
Backhaul cable between D2U and RNC simulator
2UV2/3/5
package(included
ASB_RRH2X60W_850/1900/2100
253
254
3.4
DEFECT AND TRACKING
255
The following rules will be adopted for feature ASB RRH 60 21C test progress tracking:
256
257
Weekly project synchronization meeting

Daily testing synchronization meeting
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 9/174

258
Test case execution progress daily check via Quality Center.
259
DCT will be used as defect tracking tool
authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 10/174
260
3.5
FRS REQUIREMENTS AND COMPLIANCES
261
3.5.1
FRS requirements and mapping
263
3.5.2
ISS TEST COVERAGE
264
1.
262
regression coverage:
Basic functions
Specific functions
V7 features
AISG
21
BASIC RADIO CALL
COMMEN MEASUREMENT
FAULT MANAGEMENT
FUNCTIONMODE MANAGEMENT
3
4
OAM
RADIO MOBILITY
DOWNLOAD PHASE 3
LONG FIBER
TMA
CAPACITY LICENSE IMPROVEMENT
DAISY CHAIN
20
STSR X+Y
15
SUM
90
26%
32%
42%
100%
Table 1: regression case coverage list
265
266
Passing on or copying of this document, use and communication of its contents not permitted without AlcatelLucent written authorization
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 11/174
267
268
2.
feature coverage:
AISG
21
13.3%
ALARM
35
22.2%
FAULT MANAGEMENT
1.9%
BASIC RADIO
1.9%
MOBILITY
1.2%
RADIATING
1.9%
RADIO POWER
0.6%
MIX MODE
0.6%
LONG FIBER
1.2%
6 CPRI LINK
3.1%
POWER POOLING
1.2%
DAISY CHAIN
20
12.7%
STSRX+Y
15
9.5%
CAPACITY LICENSE
1.2%
PA AUTO SWITCH OFF
0.6%
LED FOR ASB RRH
1.2%
VSWR
3.1%
SINGLE RX PORT
1.2%
EXTERNAL ALARM
0.6%
UNBLANCE RF POWER
0.6%
AC POWER
1.9%
PM COUNTER
3.1%
OAM
2.5%
POWER SAVING
5%
STABILITY
10
7.4%
Total
157
100%
Table 2 : feature case coverage list
269
270
271
272
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 12/174
273
TESTS DESCRIPTION
274
4.1
275
4.1.1.
276
4.1.1.1.
277
Test label 1:PM_COUNTER_10201_RADIO_WBAND_RX_MAIN_PWR
278
Purpose:
279
The purpose of this test is to check the management of RadioWBandRxMainPwr counters
280
Requirement:
281
Platform configuration applicable
282
Lamp connection
283
At least 2 RRH/TRDU connections
284
Discussion:
285
286
287
This load counter is used to measure the min/max/avg of the WideBand received power per sector per
frequency at the Rx Main Channelizer as detected by RRH/TRDU. The values are shown in 10^-12
mW.
288
Procedure:
289
Step1:connecte NodeB to OMC-B, make sure ASU connected
290
Step2:setup 1 cell
291
Step3:in PM menu, activate the fastclock for pm file generation, PMFastclock a, check Result1&2
292
Step4:delete this cell, setup 1 cell on the other RRH/TRDU, check Result3
293
Expectable results:
294
Result1:check that the min/max/avg values shown by counter #10201 under PM>display
295
Result2:the values are shown in 10-12 mW, and as same as what is reported from RRH/TRDU
296
297
Result3:after cell setupcell deletioncell setup, the counter could collect and report continuously
Regression Test
OAM TEST
PM_COUNTER
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 13/174
298
299
Test label 2:PM_COUNTER_10202_RADIO_WBAND_RX_DIV_PWR
300
Purpose:
301
The purpose of this test is to check the management of RadioWBandRxDivPwr counter
302
Requirement:
303
304
Lamp connection
305
306
Discussion:
307
308
This load counter is used to measure the min/max/avg of the WideBand received power per sector per
frequency at the Rx Div Channelizer as detected by TRM. The values are shown in 10-12 mW.
309
Procedure:
310
311
Step2:setup 1 cell
312
313
314
Expectable results:
315
316
Result2:the values are shown in 10-12 mW, and as same as what is reported from RRH/TRDU
317
318
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 14/174
319
320
References :
Test label 1:PM_COUNTER_10204_MCPA_PWR
321
Purpose:
322
The purpose of this test is to check the management of MCPAPwr counter
323
Requirement:
324
325
Lamp connection
326
327
Discussion:
328
329
This load counter is used to measure the min/max/avg of the output MCPA Power detected by
RRH/TRDU. The values are shown in mW.
330
Procedure:
331
332
Step2:setup 1 cell
333
334
335
Expectable results:
336
337
Result2:the values are shown in mW. In cpri mode, RRH/TRDU wont report PA power to Rack2u. Now
cell n
Txpower
338
the implemetion is that min/max value=0, avg/evt=
339
340
341
Result3:after cell setupcell deletioncell setup, the counter could collect and report continuously the
occurence of ./Board/RRH or ./Board/TRDU should be equal to physical number of RRH/TRDU when
its status is L3_connected && Unlocked && SoftStateOk, nothing with cell setup and cell deletion
342
343
RRH/TRDU object identifier should be correct in pm files
cell 0
/frequency number
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 15/174
344
345
Test label 4:PM_COUNTER_10205_RADIO_TX_CARRIER_PWR
346
Purpose:
347
The purpose of this test is to check the management of the RadioTxCarrierPwr counter
348
Requirement:
349
350
Lamp connection
351
352
Discussion:
353
354
This load counter is used to measure the min/max/avg of the total transmitted power per sector per
frequency at the Tx channelizer as detected by RRH/TRDU. The values are shown in mW.
355
Procedure:
356
357
Step2:setup 1 cell
358
Step3:in PM menu, activate the fastclock for pm file generation, PMFastclock a, check result1&2
359
Step4:delete this cell, setup 1 cell on the other RRH/TRDU, check result3
360
Expectable results:
361
362
Result2:the values are shown in mW, and as same as what is reported from RRH/TRDU
363
364
counter #10205 screening 0 is correspond to maxpower, counter #10205 screening 1 is correspond to

current tx power. Basic check:all the observed max powers have to be geater than the used powers
365
366
367
Test label 5:PM_COUNTER_10403_CPU_Load
368
Purpose:
369
The purpose of this test is to check the CPU load counter.
370
Requirement:
371
372
Lamp connection
373
374
Discussion:
375
376
This load counter is used to measure the min/max/avg of the output CPU load detected by RRH/TRDU.
The values are shown in percentage.
377
Procedure:
378
379
Step2:setup 1 cell
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 16/174
380
Step3:in PM menu, activate the fastclock for pm file generation, PMFastclock a,
381
Step4:delete this cell, setup 1 cell on the other RRH,
382
383
384
Expectable results:
-
The values are shown in percentage as same as that reported from RRH/TRDU. And the cpu load
should not be very high, about 50-60%
385
386
387
388
389
After cell setupcell deletioncell setup, the counter could collect and
report continuously
the occurence of ./Board/RRH or ./Board/TRDU should be equal to physical number of

RRH/TRDU when its status is L3_connected && Unlocked && SoftStateOk, nothing with cell setup
and cell deletion
390
391
RRH/TRDU object identifier should be correct in pm files.
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 17/174
392
393
4.1.1.2.
OMCB OPERATION
394
Test label 6:OAM_OMCB_BTS_LOCK_UNLOCK
395
Purpose:
396
397
Check BTS will under control of OMCB when unlock BTS while BTS will out of control of OMB when
lock BTS
398
Requirement:
399
The NodeB is connected to the lamp and configured
400
Procedure:
401
Step1:lock the BTS
402
Step2:unlock the BTS
403
Step3:lock BTS in OMCB and restart the BTS
404
Expectable results:
405
Result1:Check BTS could be unlocked from OMCB
406
407
When BTS is unlock, BTS could be controlled from OMCB(SW upgrade,

Equipment Monitor, etc.)
408
In emo->bts, show OMCB connection
409
Check on lamp, all local cells status wont be impacted
410
Result2:Check BTS could be locked from OMCB
411
412
When BTS is lock, BTS could not be controlled from OMCB(SW upgrade,
Equipment Monitor, etc.)
413
In emo->bts, show OMCB disconnection
414
Check on lamp, all local cells status wont be impacted
415
416
Result3:After BTS startup, the BTS is keeping locked.
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 18/174
417
Test label 7:OAM_OMCB_RRH_LOCK_UNLOCK
418
Purpose:
419
Check the cell(s) are correctly configured when RRH (in STSR-1) is locked and unlocked
420
Requirement:
421
The NodeB is connected to the lamp and configured
422
Procedure:
423
Step1:lock the RRH, check result1
424
Step2:unlock the RRH, check result2
425
426
Step3:send commands from lamp in order to configure the Cells, Fach and Rach channels, check
result3
427
Step4:send a Radio Link Setup command, check result4
428
Step5:lock the RRH and restart the NodeB, check result5
429
Expectable results:
430
431
Result1:check that all the local cells are disabled (Audit Response message raised to the lamp
including all the local cells to delete)
432
Check RRH administrative state on CCM menu
433
Check RRH object appears as locked on the OMC-B
434
435
Result2:when RRH is up, check that all the local cells are enabled (RSI message raised to the lamp
including the local cells to add)
436
Check RRH object appears as unlocked on the OMC-B
437
Check RRH administrative state on CCM menu
438
Result3:check cell setup response, Fachsetup response and Rachsetup response are successful.
439
Result4:check Radio Link setup response message is raised to the lamp
440
441
Result5:when NodeB is up, check the RRH remains locked (no local cell enabled raised to the lamp)
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 19/174
442
443
4.1.1.3.
TIL OPERATION
444
Test label 8: OAM_TIL_UPGRADE
445
Purpose:
446
Check the TIL restarts correctly after an upgrade
447
Requirement:
448
TIL connection
449
Procedure:
450
Step1:connect TIL download a new s/w to NodeB
451
Step2:once download is completed, give activation and reset from TIL, then check result1&2
452
Expectable results:
453
Result1:check whether NodeB comes up properly with the new upgraded load
454
Result2:connect to TIL and check the board states
455
456
Test label 2:OAM_TIL_RESET_RRH
457
Purpose:
458
Check Reset command for RRH from TIL
459
Requirement:
460
TIL connection
461
Lamp connection
462
Procedure:
463
Step1:On TIL, send a reset to the RRH on the CxOIM.
464
465
Step 2:On TIL, send a reset to the RRH on the RRH display
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 20/174
466
467
Step 3:Repeat this action several times
468
Expectable results:
469
470
Result1:RRH chould be reset and up normally, check that all the local cells are enabled (Audit
response message raised to the lamp including the local cells to add).
471
472
Result2:RRH chould be reset and up normally, check that all the local cells are enabled (Audit
response message raised to the lamp including the local cells to add).
473
474
Result3:BTS should work stable afer repeat RRH reset
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 21/174
475
476
Test label 9:OAM_TIL_SNAPSHOT
477
Purpose:
478
Check SnapShot information provided by TIL
479
Requirement:
480
481
TIL connection
482
Procedure:
483
Step1:TILRight Click RRH/TRDUSnapShot, check result1
484
485
Expectable results:
486
Result1:check that the RRH/TRDU SnapShot displayed is full and correct
487
4.1.2.
488
4.1.2.1.
489
Test label 10:R99_Call
490
Purpose:
491
492
Check that the NodeB can correctly communicate with a TM500 on both UL and DL for a designated
Radio Bearer
493
Requirement:
494
RNC simulator (lamp)
495
496
Test mobile (TM500)
497
The radio configuration is STSRx+y in star/chain mode or STSRz in daisy chain mode
498
Procedure:
499
Step1:send a CELL SETUP REQUEST from lamp, check Result1
RADIO TEST
BASIC CALL
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 22/174
500
501
Step2:establish a radio link (AMR_12k2, ps32k, ps64k, ps128k and ps384k) each cell on the NodeB
and on the TM500, check Result2
502
Step3:generate AAL2 traffic and check the BLER value, on Uplink and Downlink, Check Result3
503
Expected results:
504
Result1:lamp receive a CELL SETUP RESPONSE
505
Result2:radio link setup response received by both lamp and TM500
506
Result3:BLER value on both UL and DL should be inferior to 0.1%
507
(The below is an example of Lamp command and TM500 script by manual test)
AMR_12k2
Lamp
TM500
cellset 0
fachset 0
rachset 0
rlset 0 1 amr_12k2_6
cellsearch
UBI_SETUP_BCH_SC1
UBI_SETUP_AMR_12K2_6TFC_OVSF65_SC1
test 1
//check Bler on capa
UBI_CLEARSTATS
GETSTATS_CELL
GETSTATS_DCH
508
PS_32k
Lamp
TM500
cellset 0
fachset 0
rachset 0
rlset 0 1 ps_32k_10
cellsearch
UBI_SETUP_BCH_SC1
UBI_SETUP_PS_32K_10TFC_OVSF5_SC1
test 1
UBI_CLEARSTATS
GETSTATS_CELL
GETSTATS_DCH
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 23/174
509
PS_64k
Lamp
TM500
cellset 0
fachset 0
rachset 0
rlset 0 1 ps_64k_10
cellsearch
UBI_SETUP_BCH_SC1
test 1
UBI_CLEARSTATS
GETSTATS_CELL
GETSTATS_DCH
510
PS_128k
Lamp
TM500
cellset 0
fachset 0
rachset 0
rlset 0 1 ps_128k_10
cellsearch
UBI_SETUP_BCH_SC1
test 1
UBI_CLEARSTATS
GETSTATS_CELL
GETSTATS_DCH
511
PS_384k
Lamp
TM500
cellset 0
fachset 0
rachset 0
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 24/174
rlset 0 1 ps_384k_12 initialsir=150

cellsearch
UBI_SETUP_BCH_SC1
test 1
UBI_CLEARSTATS
GETSTATS_CELL
GETSTATS_DCH
512
513
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 25/174
514
515
Test label 11:HSDPA_Call
516
Purpose:
517
Check that the NodeB can correctly communicate with a TM500 on both UL and DL for an hsdpa128
518
Requirement:
519
520
521
Test mobile (TM500)
522
523
Procedure:
524
525
526
Step2:establish a radio link respectively (hsdpa128) on each cell of HSDPA activation and on the
TM500, check Result2
527
Step3:generate AAL2 traffic and check the BLER value, on Uplink and Downlink, check Result3
528
Expected results:
529
530
531
532
HSDPA
Lamp
TM500
cellset 0
fachset 0
rachset 0
physcrec 0
rlset 0 1 hsdpa128
cellsearch
UBI_SETUP_BCH_SC1
UBI_SETUP_HSDPA_ASSOCIATED_DCH_UL128_OVSF65_SC1
FORCE_NACK_9ACK_CQI
UBI_SETUP_HSDPA_RL_L1_SC1_CAT12
test 1 mode=1 capareq=1 delay=100
//check DL rate by TM500
UBI_CLEARSTATS
GETSTATS_CELL
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 26/174
GETSTATS_DCH
GETSTATS_HSDPA
533
534
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 27/174
535
536
Test label 12:HSUPA_Call
537
Purpose:
538
Check that the NodeB can correctly communicate with a TM500 on both UL and DL for an hsdpa_edch
539
Requirement:
540
541
542
Test mobile (TM500)
543
544
Procedure:
545
546
547
Step2:establish a radio link respectively (hsdpa_edch) on each cell of HSUPA activation and on the
TM500, check Result2
548
Step3:generate AAL2 traffic and check the BLER value, on Uplink and Downlink, check Result3
549
Expectable results:
550
551
552
553
HSUPA ( L1)
Lamp
TM500
cellset 0
fachset 0
rachset 0
physcrec 0 type=full
rlset 0 1 hsdpa_edch
cellsearch
UBI_SETUP_BCH_SC1
UBI_SETUP_SRB_3K4_OVSF65_SC1
UBI_SETUP_HSDPA_EDCH_PN_ALL_N_TABLE_1_SC1_n1
test 1 mode=1 edch_mode=1
//check DL and UL rate by TM500
UBI_CLEARSTATS
GETSTATS_CELL
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 28/174
GETSTATS_DCH
GETSTATS_HSDPA
GETSTATS_HSUPA
554
HSUPA ( L2)
Lamp
TM500
cellset 0
fachset 0
rachset 0
physcrec 0 type=full
rlset 0 1 hsdpa_edch
cellsearch
L2_SETUP_BCH_10612_9662_SC1
L2_SETUP_DCH_SC1
L2_SETUP_HSDPA_SC1
L2_SETUP_EDCH_SC1
test 1 mode=1 edch_mode=1
L2_config_MAC_e
L2_SI_0_20
L2_SI_0_97
//check DL and UL rate by TM500
555
556
4.1.2.2.
RADIO POWER TEST
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 29/174
557
Test label 13:Radio_RSSI_Verification
558
Purpose:
559
560
The goal of this test case is to verify the RSSI reported at RRH/TRDU side is as expected at any case
561
562
1. Platform configuration applicable:

2. The BTS is connected to the lamp and configured
563
Procedure:
564
565
Step1:Thanks to Lamp, cellset without any signal injection, then Start the common measurement with
the command:
Requirements:
Startcmeas cellid measurementid
566
567
Step2:Check RTWP reported on RRH/TRDU side and Lamp side
568
569
Step3:Disconnect one antenna connection. Thanks to Lamp, cellset without any signal injection, then
Start the common measurement with the command:
Startcmeas cellid measurementid
570
571
Step4:Check RTWP reported on RRH/TRDU side and Lamp side
572
573
574
Expectable results:
575
4.1.2.3.
576
Test label 14:RADIO_DCH_PS_1_NIGHT
577
Step2:the RTWP reported should around -106dbm

Step4:the RTWP reported on the broken antenna should 0dbm
R99 TEST
Purpose:
578
Check a DCH Packet Switch (PS) call during 1 night.
579
Requirement
580
581
1. A RNC simulator (Lamp) to send the NBAP procedures to the NodeB.

2. A UE simulator (Ubinetics TM500).
582
Test inputs:
583
CPRI Interface type:Electric / Optic
584
CEM type:xCEM only / iCEM only / xCEM iCEM mix
585
RF Configuration:STSR1 / STSR2 / STSR3
586
Frequency:B / M / T
587
Bearer:ex:PS_64K_10
588
Cell:0 / 1 / 2
589
The UL & DL SIR targets should relate to good radio conditions, ex:5 dB in DL / 10 dB in UL.
590
Only one cell need to be up.
591
Setup the PS call as described in [R12] (PS_64K_10 tab for instance).
592
All the NBAP messages should be processed successfully by the NodeB.
593
The DL BLER should be equal to 0 on the UE simulator.
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 30/174
594
The UL BLER should be equal to 0 on the RNC simulator.
595
The NodeB debug information should be consistent (cap > ctx).
596
597
The call must be checked during 1 night (the AAL2 traffic should not be disrupted during the
night).
598
599
No alarm should be raised on the NodeB.
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 31/174
600
601
4.1.2.4.
602
603
Test label 15:RADIO_HSUPA_1_NIGHT
604
Purpose:
605
Check a HSUPA call.
606
Requirement
607
608
1. A RNC simulator (Lamp) to send the NBAP procedures to the NodeB.

2. A UE simulator (Ubinetics TM500).
HSUPA RESOURCE
609
610
Test inputs:
611
CPRI Interface type:Electric / Optic
612
CEM type:xCEM only / iCEM only / xCEM iCEM mix
613
RF Configuration:STSR1 / STSR2 / STSR3
614
Frequency:B / M / T
615
Cell:0 / 1 / 2
616
617
The UL & DL SRB SIR targets should relate to good radio conditions, ex:5 dB in DL / 10 dB in UL.
618
Only one cell need to be up.
619
A HSDPA UE category 12 will be simulated.
620
621
The default values for the HSDPA parameters will be applied in the NodeB MIB (DLU), except the
hsdpaCqiBlerAdjustmentAlgorithm that will be turned off (0).
622
The default values for the EDCH parameters will be applied in the NodeB MIB (DLU).
Procedure :
623
624
Setup the HSUPA call as described in [R12] (HSUPA_L1L2 tab).
625
626
All the NBAP messages should be processed successfully by the NodeB.
627
The DL DCH SRB & HS-DSCH BLER should be equal to 0 on the UE simulator.
628
The UL PS SRB & EDCH BLER should be equal to 0 on the RNC simulator.
629
The NodeB debug information should be consistent (cap > ctx).
630
631
The UE simulator debug information should be consistent (MACESND logging window -> PDU
size, PDU Txed/ACK/NACK, BLER).
632
633
634
The call must be checked during 1 night (the AAL2 traffic should not be disrupted during the
night).
No alarm should be raised on the NodeB.
635
4.1.2.5.
636
MOBILITY TEST
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 32/174
637
638
Test label 16:Mobility_Softer_HO_HSDPA_to_R99
639
Purpose:
640
641
Check that a complete procedure of softer handover from a cell supporting HSDPA service to a cell
supporting only R99 is successfully
642
Requirement:
643
644
Lamp connection
645
TM500 connection
646
The radio configuration in Daisy chain mode or STSRx+y mode or both mixed mode
647
Make sure two cells which will do the softer handover have the same frequency
648
Procedure:
649
Step1:setup a RL on cell1 with HSDPA and synchronize the UE with it
650
Step2:the mobile should synchronize on this RL
651
Step3:add RL2 (DCH leg on the target cell) which is identical to the ADCH link
652
653
Step4:perform a SRLR procedure that will delete the HS-DSCH on the source cell and modify
associated parts of both legs to DCH
654
Step5:delete initial leg
655
Expectable results:
656
657
Result1:all these procedures must be successful and the RL established in DCH on the target cell
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 33/174
658
659
Test label 17:Mobility_Softer_HO_R99_to_HSDPA
660
Purpose:
661
662
Check that a complete procedure of softer handover from a cell in R99 to a cell supporting HSDPA is
successfully
663
Requirement:
664
665
Lamp connection
666
TM500 connection
667
668
669
Procedure:
670
Step1:setup a RL on cell1 in DCH and synchronize the UE with it
671
672
Step3:add a leg, to the initial DCH bearer, on the target cell
673
674
Step4:perform a SRLR procedure that will reconfigure initial leg to an ADCH and the target leg to
HSDPA, adding the HSDSCH part
675
Step5:delete the initial leg
676
Expectable results:
677
678
Result1:all these procedures must be successful and the RL established in HSDPA on the target cell
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 34/174
679
680
4.1.2.6.
RADIATING
681
Test label 18:RADIATING_RADIATING_ON_ONE_CELL
682
Purpose:
683
Check the radiating user interface on TIL displays and works correctly
684
685
686
687
688
Requirement:
2. TIL connection
3. Spectrum analyzer connection at antenna output
4. The TIL is started and the BTS is not built.
689
Procedure:
690
Step 1:Start BTS in stand-alone mode
691
Step 2:TILToolsRadiating BTS, the radiating Pop-up window looks like:
692
693
694
Step 3:Configure the BTS with a downlink frequency value within the authorized range(Ndl = 5 Fdl, Ndl
= downlink frequency expressed as a number, Fdl = downlink frequency expressed in MHz)
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 35/174
BAND
I
II
IV
V
Carrier frequency (FUL)

range [MHz]
FUL_low
FUL_high
1922.4
1977.6
1852.4
1907.6
1712.4
1752.6
826.4
846.6
Carrier frequency (FDL)

range [MHz]
FDL_low
FDL_high
2112.4
2167.6
1932.4
1987.6
2112.4
2152.6
871.4
891.6
695
Step 4:RRH/TRDU cell selected
696
697
Step 5:Configure Max Trasmission Power, Primary Scrambling Code, Primary CPICH code, Priamry
SCH Power, Secondary SCH Power as the authorized range
698
Step 6:Activate radiating mode with all only 1 cell enabled.
699
Expectable results:
700
Check that the BTS resets in stand-alone mode when radiating mode is activated;;
701
702
Check Downlink Frequency, Max Trasmission Power, Primary Scrambling Code, Primary CPICH code,
Priamry SCH Power, Secondary SCH Power field could be edited
703
704
705
Check that RRH/TRDU cell could radiating successfully after activating radiating
Verify that the resulting spectrum corresponds to expected frequency and power levels displays
correctly on spectrum analyzer.
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 36/174
706
707
Test label 19:RADIATING_UPPER_LIMIT_OF_DOWNLINK _FREQUENCY
708
Purpose:
709
Radiate the BTS in STSR1 configuration with upper limit of downlink frequency.
710
711
712
713
714
Requirement:
715
Procedure:
716
Step 1:The TIL is started and the BTS is starting in stand-alone mode and not built.
717
718
Step 2:Configure the BTS with the upper downlink frequency value referring to below table (Ndl = 5 Fdl,
Ndl = downlink frequency expressed as a number, Fdl = downlink frequency expressed in MHz).
1.
2.
3.
Platform configuration applicable:

TIL connection
BTS is in STSR configuration
Spectrum analyzer connection at antenna output
BAND
I
II
IV
V

range [MHz]
FUL_low
FUL_high
1922.4
1977.6
1852.4
1907.6
1712.4
1752.6
826.4
846.6

range [MHz]
FDL_low
FDL_high
2112.4
2167.6
1932.4
1987.6
2112.4
2152.6
871.4
891.6
719
Step 3:Activate radiating mode with all 3 cells enabled.
720
Expectable results:
721
Check that the BTS resets in stand-alone mode when radiating mode is activated;
722
Check that cell states are properly updated on TIL GUI.
723
724
Verify that the resulting spectrum corresponds to expected frequency and power levels from CAP menu
and spectrum analyzer.
725
726
Check that the BTS radiates on 3 sectors with spectrum analyzer.
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 37/174
727
Test label 20:RADIATING_LOWER LIMIT_OF_DOWNLINK_FREQUENCY
728
Purpose:
729
Radiate the BTS in STSR1 configuration with lower limit of downlink frequency.
730
731
732
733
734
Requirement:
735
Procedure:
736
Step 1:The TIL is started and the BTS is starting in stand-alone mode and not built.
737
738
Step 2:Configure the BTS with the lower downlink frequency value referring to below table (Ndl = 5 Fdl,
Ndl = downlink frequency expressed as a number, Fdl = downlink frequency expressed in MHz).
4.
5.
6.

TIL connection
BTS is in STSR configuration
BAND
I
II
IV
V

range [MHz]
FUL_low
FUL_high
1922.4
1977.6
1852.4
1907.6
1712.4
1752.6
826.4
846.6

range [MHz]
FDL_low
FDL_high
2112.4
2167.6
1932.4
1987.6
2112.4
2152.6
871.4
891.6
739
Step 3:Activate radiating mode with all 3 cells enabled.
740
Expectable results:
741
Check that the BTS resets in stand-alone mode when radiating mode is activated;
742
Check that cell states are properly updated on TIL GUI.
743
744
Verify that the resulting spectrum corresponds to expected frequency and power levels from CAP menu
and spectrum analyzer.
745
Check that the BTS radiates on 3 sectors with spectrum analyzer.
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 38/174
746
747
Test label 21:Radio_RSSI_Verification
748
Purpose:
749
The goal of this test case is to verify the RSSI reported at RRH/TRDU side is as expected at any case
750
Requirement:
751
752
NodeB is connected to the lamp and configured
753
Procedure:
754
755
Step1:thanks to Lamp, cellset without any signal injection, then Start the common measurement with
the command:Startcmeas cellid measurementid, check result1
756
Expectable results:
757
758
Result1:check RTWP reported on RRH/TRDU side and Lamp side, the RTWP
reported should around -106dbm
759
760
4.1.3.
ENDURANCE
761
4.1.3.1.
762
Test label 22:ENDURANCE_POWER_ON/OFF_BTS
763
Purpose:
764
The purpose of this test is to check the robustness of the power off/on procedure of the BTS.
765
Requirements
766
767
2. OMC-B connection
768
3.
769
Step 1:
Power on Rack2u.
770
Step 2:
Check AuditRequest and AuditResponse from Lamp.
771
Step 3:
Power off Rack2u.
772
Step 4:
Repeat Step 1 and Step 3 10 times.
773
774
Time duration without problem in hour Occurrences
OAM EDURANCE
Lamp connection
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 39/174
775
Test label 23:ENDURANCE_RESET_xCCMU BTS
776
Purpose:
777
The purpose of this test is to check the robustness of the reset procedure of the BTS.
778
Requirements
779
780
2. OMC-B connection
781
3.
Lamp connection
782
4.
Boards are unlocked with no alarm present.
783
The BTS is already downloaded in correct load and built.
784
785
Reset the BTS in the loop for n times and check whether BTS comes up fine and that radio resources
can be setup.
786
Lamp script name is ISS_signal.d and WAFIT script name is 02F.
787
From WAFIT, launch the corresponding script (WAFIT_KPI_MAIN_SCRIPT.pl).
788
789
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 40/174
790
Test label 24:ENDURANCE_SLAVE_RESET_RRH BTS
791
Purpose:
792
The purpose of this test is to check the robustness of the reset procedure of the slave RRH.
793
Requirements
794
795
2. OMC-B connection
796
3.
Lamp connection
797
4.
798
799
800
Reset the slave RRH in the loop for n times and check whether slave comes up fine and that radio
resources can be setup.
801
Lamp script name is ISS_signal.d and WAFIT script name is 03D.
802
From WAFIT, launch the corresponding script (WAFIT_KPI_MAIN_SCRIPT.pl,).
803
804
805
Purpose:
806
Purpose of the test is to test the stability of the BTS with continuous download of correct load.
807
Requirements
808
809
2. OMC-B connection
810
3.
Lamp connection
811
4.
812
5.
Generate a V5edX load where the TOKEN TYP is set to FFS in the FILE0.
813
6.
Generate a V5edY load where the TOKEN TYP is set to FFS in the FILE0.
814
7.
Generate a V5edZ load where the TOKEN TYP is set to FFS in the FILE0.
815
816
Script has to Upgrade and activation:
817
from V5edX to V5edY
818
from V5edY to V5edZ
819
from V5edZ to V5edX
820
Lamp script name is ISS_signal.d and WAFIT script name is 04D.
821
From WAFIT, launch the corresponding script(WAFIT_KPI_MAIN_SCRIPT.pl,).
822
823
824
825
826
(* When the BTS restarts, the bootl3 detects that data partition is using FFS. This partition is formatted
in FFS. The content present in data partition is temporarily duplicated in RAM, before to be copy back
into data partition.)
Test label 25:ENDURANCE_DOWNLOAD_BTS
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 41/174
827
4.1.3.2.
RADIO EDURANCE
828
Test label 26:Nuscm DCH
829
Purpose:
830
831
Purpose of this test is to test the stability of BTS with the NUSCM command by setting the level 5 using
the lamp
832
Requirements
833
834
2.
Lamp connection
835
3.
Boards are unlocked with no alarm present
836
From Lamp, use the ISS signal script and run the nuscm command for the level 5
837
838
839
Ensure that nuscm endurance run for at least 2 hours without any traps or abnormal behaviors on the
BTS
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 42/174
840
Test label 27:ENDURO DCH
841
Purpose:
842
843
Purpose of this test is to test the stability of BTS with the ENDURO command by setting the level 5
using the lamp
844
Requirements
845
846
2.
Lamp connection
847
3.
Boards are unlocked with no alarm present
848
849
850
From Lamp, use the ISS signal script and run the enduro command for the level 5
Ensure that enduro endurance run for at least 2 hours without any traps or abnormal behaviors on the
BTS
851
4.1.4.
852
4.1.4.1.
853
Test label 28:OAM_START_UP_WITH_Mix_RRH
854
Purpose:
855
856
Check the NodeB starts correctly after power on for both Rack2U and ASB RRH, inhouse
RRH(2100MHz),TRDU,Adrew RRH
857
Requirement:
858
NodeB is connected to the lamp and configured
859
NodeB is connected to the OMC-B
860
Procedure:
861
862
Step1:execute a Switch-off / Switch-on both RACK2U and ASB RRH, inhouse RRH(2100MHz),
TRDU,Adrew RRH,check result1
863
864
Step2:when Audit procedure is done, send commands from lamp in order to configure the Cells, Rach
and Fach channels on every RRH, check result2
865
Step3:send a Radio Link Setup command and every RRH, check result3
866
Step4:Make call on every RRH, check result4
867
Expectable results:
868
Result1:when the NodeB is up, check the connection with OMC-B and lamp is done correctly
869
Result2:check cell setup response, Fachsetup response and Rachsetup response are successful
870
Result3:check Radio Link setup response message is raised to the lamp
871
872
Result4:check the call service work smoothly on every RRH.
873
4.1.4.2.
874
875
Test label
29:AISG_TMA_START-UP_WITH-TMA-CONFIGURATION_BUT-NO-TMA
UA6.0 FEATURE TEST

MIX MODE
AISG-LITE
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 43/174
876
Purpose:
877
Check the alarm about TMA.
878
Requirement:
879
880
OMC-B connection
881
TMA and RRH is suited.
882
Procedure:
883
Step1:Rack2u+RRH/TRDU connection without TMA
884
Step2:Configure TMA access in DLU, then reset the rack2u.
885
TmaAccessType :tmaUmtsOnly.
886
Check Result1.
887
4.1.4.3.
10/20KM FIBER
888
Test label 30:10KM_Fiber_For_CPRI_RRH_With_iCEMu
889
Purpose:
890
Check Rach Access and call setup could be successful with 10KM fiber connection
891
Requirement:
892
893
Lamp connection
894
TM500 connection
895
Procedure:
896
897
Step1:calculate the acceptable value of chip delay with 10km fiber, and assuming the propagation
speed over the fiber is 1.5 times slower than in the air. Formula as follows:
898
Chip delay * 260.42ns* (3*10 /1.5 km/ns) =10 km
899
Tc = 260.42 ns(1/3.84Mchips/s)C = 3*10-4 km/ns(velocity of light)
900
So, the values of chip delay around 192 chips
901
Step2:cell setup, fach setup, rach setup on Lamp
902
903
Step3:on TM500, set the parameter of setcellpathdelay x to the propagation delay near 192 chips on
script and then trigger the UL rach access
904
Step4:on Lamp side, type the command rachtest to accept the PRACH message part. Check Result1
-4
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 44/174
RACH test procedure

CATAPULT
UBINETICS
Setup cell on cata
cellset 0
fachset 0
rachset 0
Setup cell on ubi

UBI_SETUP_BCH_SC1.txt
IN SYNC INDICATION
+Check stats on CCB 0
Setup RACH on ubi
Enter RACH test mode on CATA

rachtest
Send RACH procedure on UBI

UBI_RACH_ACCESS.txt
CELL 0 RACH MESSAGE OK
Delete RACH on UBI

UBI_DELETE_RACH.txt
905
906
907
908
Step5:if Rach access is successful. And then setup a RL with the propagation delay received in
PRACH message part. Such as:rlset 0 1 amr_12k2_6 propdelay = 64 (In case of 20km fiber, propdelay
is 128), check Result 2
909
910
911
Expectable results:
Result1:lamp part could receive and show PRACH message part with propagation
delay around x/6
912
Result2:basic call could be made successfully
913
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 45/174
914
Test label 31:20KM_Fiber_For_CPRI_RRH_With_xCEMu
915
Purpose:
916
Check Rach Access and call setup could be successful with 20KM fiber connection on one chain.
917
Requirement:
918
Platform configuration applicable;
919
Lamp connection;
920
TM500 connection;
921
922
Make sure the radio configuration in daisy chain mode, and the distance between dBTS and the last
RRH is 20km.
923
Procedure:
924
925
Step1:Calculate the acceptable value of chip delay with 20km fiber, and assuming the propagation
speed over the fiber is 1.5 times slower than in the air;
926
Formula as follows:
927
Chip delay * 260.42ns* (3*10-4/1.5 km/ns) = 20 km
928
Tc = 260.42 ns(1/3.84Mchips/s)C = 3*10-4 km/ns(velocity of light)
929
So, the values of chip delay around 384 chips.
930
Step2:Cell setup, FACH setup, RACH setup on Lamp;
931
932
Step3:On TM500, set the parameter of setcellpathdelay x to the propagation delay near 384 chips on
script and then trigger the UL RACH access;
933
934
Step4:On Lamp side, type the command rachtest to accept the PRACH message part. Check
Result1;
RACH test procedure

CATAPULT
UBINETICS
Setup cell on cata
cellset 0
fachset 0
rachset 0
Setup cell on ubi

UBI_SETUP_BCH_SC1.txt
IN SYNC INDICATION
+Check stats on CCB 0
Setup RACH on ubi
Enter RACH test mode on CATA

rachtest
Send RACH procedure on UBI

UBI_RACH_ACCESS.txt
CELL 0 RACH MESSAGE OK
Delete RACH on UBI

UBI_DELETE_RACH.txt
935
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 46/174
936
937
938
Step5:If Rach access is successful. And then setup a RL with the propagation delay received in
PRACH message part. Such as:rlset 0 1 amr_12k2_6 propdelay = 128 (In case of 10km fiber,
propdelay is round 64), check Result 2.
939
940
Expectable results:
941
Result2:Basic call could be made successfully.
Result1:Lamp part could receive and show PRACH message part with propagation delay;
942
943
4.1.4.4.
6 CPRI LINK
944
Test label 32:OAM_6_CPRI_LINK_I&C_PARAMETERS
945
Purpose:
946
947
The purpose of this test is to check that whether I &C RRH/TRDU type chould be changed and
displayed correctly on TIL according to ccm board type
948
Requirement:
949
950
TIL connection
951
Suppose 6 RRH/TRDU connected
952
Procedure:
953
Case1:xCCMU 1W+CPRI RRH/TRDU
954
Step1:open TIL, click the I&C menu
955
956
Step2:select Display I&C parameters menuclick RRH/TRDU Tab, check the RRH/TRDU type
display correctly
957
958
Step3:select Change I&C parameters menuclick RRH/TRDU Tab, change the RRH/TRDU type to
HSSL, reset rack2u
959
960
CPRI, reset rack2u
961
Step5:set up a basic call
962
Case2:xCCMU 0D+CPRI RRH/TRDU
963
Step1:open TIL, click the I&C menu
964
965
Step2:select Display I&C parameters menuclick RRH/TRDU Tab, check the RRH/TRDU type
display correctly
966
967
HSSL, reset rack2u
968
969
CPRI, reset rack2u
970
Step5:set up a basic call
971
Expectable results:
972
973
According to different hardware version for XCCMu, the mapping relation between I&C parameter and
link mode as following:
974
975
1W (old HW version):If the parameter value is 0, means link mode in optical 5, 6 is HSSL mode, else is
CPRI mode
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 47/174
976
977
0D (new HW version):If the parameter value is 0, means link mode in optical 4, 5, 6 is HSSL mode, else
is CPRI mode
978
So
979
Case1:xCCMU 1W+CPRI RRH/TRDU
980
Result1:RRH/TRDU type shows CPRI correctly
981
982
983
Result2:RRH/TRDU type parameter can be changed to HSSL, and after rack2u reset and up, CPRI
RRH/TRDU on optical link 5, 6 can not be up normally, but CPRI RRH/TRDU on optical link 1,2,3,4
should be up normally
984
985
Result3:RRH/TRDU type parameter can be changed to CPRI, and after rack2u reset and up, all 6
CPRI RRH/TRDU can be up normally
986
Result4:the basic call is successful
987
Case2:xCCMU 0D+CPRI RRH/TRDU
988
Result1:RRH/TRDU type shows CPRI correctly
989
990
991
Result2:RRH/TRDU type parameter can be changed to HSSL, and after rack2u reset and up, CPRI
RRH/TRDU on optical link 4, 5, 6 can not be up normally, but CPRI RRH/TRDU on optical link 1, 2, 3
should be up normally
992
993
Result3:RRH/TRDU type parameter can be changed to CPRI, and after rack2u reset and up, all 6
CPRI RRH/TRDU can be up normally
994
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 48/174
995
996
Test label
33:OAM_6_CPRI_LINK_DLU_CHECK_MAX_6_SECTORS_SUPPORTED
997
Purpose:
998
Configure file is checked during startup to make sure that max 6 sectors are supported
999
Requirement:
1000
1001
OMC-B connection
1002
Procedure:
1003
Step1:configure DLU like
1004
### Start Section - BTS Sector
1005
nbSector:7
1006
Sector [0]:
1007
AntennaAccessInstance
:0
1008
AntennaConnection
:11/1011
1009
1010
Sector [5]:
1011
:0
1012
AntennaConnection
:61/1061
1013
1014
### Start Section - RRH

nbRemoteRadioHead:7
1015
RemoteRadioHead [0]:
1016
remoteRadioHeadInstance
1017
1018
RemoteRadioHead [5]:
1019
:11/1011
:61/1061
1020
Step2:reset the Rack2U, check result1.
1021
Step3:change the nbSector to 6, nbRemoteRadioHead to 6 like:
1022
1023
nbSector:6
1024
1025
nbRemoteRadioHead:6
1026
Step4:reset the Rack2U, check result2
1027
Step5:set up a basic call, check result3
1028
Expectable results:
1029
1030
Result1:after Rack2u startup, BTS will be in BULD KO state, type emo->ala>chk, error information will
show for reason that max 6 remote sectors supported
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 49/174
1031
1032
Result2:new antennaAccessInstance 41, 51, 61 or 1041, 1051, 1061 could be accepted, cofigure file is
built. If 6 RRHs/TRDUs connected, all local cell status should be enabled
1033
1034
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 50/174
1035
1036
Test label 34:OAM_6_CPRI_LINK_DLU_CHECK_Max_12_CELLS_SUPPORTED
1037
Purpose:
1038
Configure file is checked during startup to make sure that max 12 cells are supported
1039
Requirements:
1040
1041
OMC-B connection
1042
Procedure:
1043
Step1:configure DLU like:
1044
6 sectors:
1045
1046
nbSector:6
1047
Sector [0]:
1048
:0
1049
AntennaConnection
:11/1011
1050
1051
Sector [5]:
1052
:0
1053
AntennaConnection
:61/1041
1054
1055

nbRemoteRadioHead:6
1056
remoteRadioHead [0]:
1057
1058
1059
remoteRadioHead [5]:
1060
remoteRadioHeadInstance:61/1061
1061
13 cells:
1062
### Start Section - BTS Cell
1063
nbBtsCell:13
1064
btsCell [0]:
1065
LocalCellId
1066
1067
1068
:11/1011
:191
btsCell [12]:
LocalCellId
:303
1069
1070
Step3:change the remove btscell [12] configuration, like
1071
### Start Section - BTS Cell

UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 51/174
1072
1073
1074
nbBtsCell:12
btsCell [12]:
LocalCellId
:303
1075
1076
Step5:set up a basic call, check result3
1077
Expectable results:
1078
1079
Result1:after Rack2u startup, cofigure file is not built, type emo->ala>chk, error information will show
for reason that max 12 cells supported with 6 sectors
1080
1081
Result2:cofigure file is built without error. If 6 RRHs/TRDUs connected, all local cell status should be
enabled
1082
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 52/174
1083
Test label 35:OAM_6-CPRI-LINK_TIL GUI connection to Rack2u & RRH
1084
Purpose:
1085
1086
The purpose of this test is to check that TIL can be connected to Rack2u & RRH and that visual check
is correct on the Graphical User Interface under 6 cpri link.
1087
Requirement:
1088
1089
2. TIL connection
1090
Connect the TIL.
1091
The figure below describes the GUI expected on the TIL if a xCOB is inserted in the rack.
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
A child-window appears when a

right click is done on the xCOB
board:
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 53/174
1104
1105
1106
This window presents the same information for Optical interfaces and all RRHs on the link (only one for
star configuration). Contextual menus are available when clicking on those objects:
1107
For the optical interface, interface is provided to
1108
- require the display of alarms detected on the xCOB board,
1109
- require the hard reset of all RRHs on the link
1110
- disable optical transmission (and re-enable it)
1111
For the RRH, interface is similar to the information available in contextual menus for FTR boards.
1112
xCOB POPUP MENUS:
1113
- Alarms
1114
Display the xCOB alarms
1115
- Stop all Tx emission
1116
1117
Run all Tx emission)
1118
- Reset
, OI2 ,OI3,OI4,OI5,OI6 are powered off (the popup menu command becomes
1119
1120
OPTICAL INTERFACE POPUP MENUS:
1121
- Return to main GUI
1122
Return to the main GUI window

UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 54/174
1123
- RRH alarms
1124
1125
its RRH number)
1126
- Stop Tx emission
x is powered off (the popup menu command becomes Run Tx emission)
1127
1128
- Reset all RRH
1129
1130
RRH POPUP MENUS:
1131
- Marking
1132
1133
Software versions for active FFS and passive FFS

- BIST results
1134
1135
- Alarms
1136
1137
- Display alarms mask
1138
1139
- Reset
1140
1141
Expectable results:
1142
TIL:
1143
TIL is connected.
1144
Digital shelf is correctly displayed (slots and board types)
1145
No transparent message is rejected (no popup window)
1146
Software Reference is correct
1147
PCM Led state is correct
1148
For each optical interface, the GUI presents
1149
- The standby status of the RRH on the link
1150
- Green if RRH is providing service
1151
- Orange if RRH in cold-standby
1152
- The administrative state
1153
- Green:unlocked
1154
- Orange:Locked
1155
- The alarm status
1156
- Green:No alarm
1157
- White:No RRH connected:(no light on optical link)
1158
- Black:RRH Bists KO:RRH not running
1159
- Red:Major alarm preventing service has been sent to the BTS.
1160
-Tx and Rx status of link:

UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 55/174
1161
- Green:ON:Laser is powered.
1162
- White:OFF:Laser is unpowered
1163
1164
-3 LEDs managed on RRH

LED display should match the actual status on RRH
1165
- Number of RRH on the link (1 on the picture) is not required for star configurations.
1166
For xCOB board, the GUI presents
1167
-- The standby status of the xCOB on the link
1168
- Green if xCOB is providing service
1169
- Orange if xCOB in cold-standby
1170
- The administrative state
1171
- Green:xCOB unlocked
1172
- Orange:xCOB Locked
1173
- Alarm status
1174
- Green:OK:xCOB is ok
1175
- Red:Alarm:xCOB is in alarm
1176
-Tx and Rx status of link:
1177
- Green:ON:Laser is powered.
1178
- White:OFF:Laser is unpowered
1179
OMC-B:
1180
OMC-B connection state is correct
1181
Site Data display is correct
UMT/BTS/DJD/044741
01.01/EN
Preliminary
24/Sep/2014
Page 56/174

1182
Test label 36:OAM_6-CPRI-LINK_OMCB GUI connection to RRH
1183
Purpose:
1184
1185
The purpose of this test is to check that Rack2U & RRH visual display correctly on the OMCB
Graphical User Interface under 6 cpri link.
1186
Requirements:
1187
1188
2. OMC-B connection
1189
Procedure:
1190
Step1:Open OMCBEquipment Monitor
1191
Expectable results:
1192
The visual display of Rack2U & RRH on OMCB should like:
1193
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 57/174

1194
1195
4.1.4.5.
POWER POOLING
1196
1197
Test label
37:POWER_POOLING_CHANGE_THE_POWER_OF_EACH_FREQUENCY
1198
Purpose:
1199
1200
Check the PA allows some overbooking of the power of the carrier where HSDPA/E-DCH is
deployed over the carrier where legacy R99 is deployed
R99
Static power sharing
F2 max power
R99
Maximum PA Power
F1 max power
Power
not used
F2 max power
Maximum power
HSDPA
F1 max power
R99 &
GBR
R99 &
GBR
HSDPA
Dynamic Power pooling
1201
1202
Requirement:
1203
1204
Lamp is connected
1205
1206
UDT script for TM1
1207
Configuration:
1208
Currently only support STSR-2 with only maximum 1 carrier per PA with HSDPA activated
1209
Both cells are mapped on xCEMu
1210
Set paPoolingActivation=True
1211
Set paRatio=80(HSDPA cell) and paRatio=50(R99 cell). Sum(paRatio)<=130
1212
Procedure:
1213
Step1:setup both HSDPA cell and R99 cell with Lamp, check result1
1214
Step2:run TM1 scripts for 2 cells with UDT, check result2

authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 58/174

1215
Step3:remove the R99 cell with Reproxy commands since Lamp is no more available
1216
CellDelete
Linkid, Reuid, LocalCellId
1217
Linkid
:1 to 6
1218
Reuid
:1 to 1
1219
LocalCellId
:must be already configured by cell mapping
1220
Check result3
1221
Step4:remove the HSDPA cell and Setup the R99 cell with Reproxy commands
1222
CellMappingFlex & CellConfig, take care of following parameters
1223
Carrier 1:Tx Main=0 Tx Div=0xFF Rx Main=0 Rx Div=1
1224
Carrier 2:Tx Main=1 Tx Div=0xFF Rx Main=2 Rx Div=3
1225
Check result4
1226
Expectable results:
1227
1228
1229
Result1:check HSDPA cell is setup with CPICH/MaxPower=35.1/45.1 dBm, and R99 cell is
setup with CPICH/MaxPower=33.0/43.0 dBm. Although MaxPower together is greater than
46.0 dBm, no alarm reported and both cell established successfully
1230
1231
Result2:check UDT script is running successfully. Then check the total power of both HSDPA
cell and R99 cell. HSDPA cell should be 43.9 dBm, and R99 cell should be 41.9 dBm
1232
1233
Result3:check the R99 cell is removed, and total power of HSDPA cell changes to 45.1dBm
dynamically
1234
1235
1236
Result4:check the HSDPA cell is removed, and total power of R99 cell changes to 43.0 dBm
dynamically
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 59/174

1237
1238
1239
1240
1241
1242
1243
1244
Test label 38:POWER_POOLING_HSDPA_on_2_Carriers
1245
Step1:Step1:change the parameter paPoolingActivation=True;configure to STSR2 in DLU;
1246
1247
1248
1249
1250
Step2:HSDPA enabled in both carriers; reset 2u

Expected results:
Result1:D2U can not startup normally, have alarm about Papooling
NodeB will send an alarm INVALID_CONFIGURATION_DATA to OMCB.
Purpose:
Power polling is failed with HSDPA on both 2 carriers
Requirement:
STSR2
2UV2P2+6*RRH/2UV2P2+6*TRDU
The two cells can be setup
Procedure:
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 60/174

1251
1252
1253
4.1.5.
UA7.1 GENERAL TEST DESCRIPTION FOR FRS33519 DAISY

CHAIN
1254
4.1.5.1.
1255
Test label 39:Daisy_Chain_Link_Status_With_RRH_Plugin
1256
Purpose:
1257
1258
This test is to check the message exchange between new RRH and Reproxy when it is
plugged into the chain as the last RRH
1259
Requirement:
1260
1261
D2U and 1 RRH connected to NodeB
1262
Procedure:
1263
Step1:NodeB and the first RRH startup successfully
1264
Step2:open terminal tool, telnet to CCM board.Open the trace "/lib_cpri/oem_lib_cpri> Trace"
1265
Step3:plug in a new RRH to daisy chain as the last one
1266
Step4:check the RE messges in CCM traces, check Result 1~4
1267
Expectable results:
1268
1269
Result1:after step4, RE_GetAlarm_Indication (Alarm Master Port=OFF) can be seen in CCM

traces and this alarm should be listed on the "/emo/alarm> GlobalAlarms"
1270
1271
Result2:check that the Reuid in RE_GetAlarm_Indication message from first RRH should be
correct
1272
1273
Result3:within 100 seconds, RE_GetAlarm_Report (Alarm Master Port=ON) for the last RRH
can be seen soon from. Or last RRH startup failed
1274
1275
1276
Result4:check that the Reuid in RE_GetAlarm_Report message from last RRH should be
correct
LINK STATUS
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 61/174

1277
1278
Test label 40:Daisy_Chain_Link_Status_With_RRH_Plugout
1279
Purpose:
1280
1281
This test is to check the message exchange between last RRH and Reproxy when it is plugged
out from the fiber chain
1282
Requirement:
1283
1284
D2U and n (2=<n<=6) RRHs in one fiber chain connected
1285
Procedure:
1286
Step1:NodeB and the RRHs startup successfully
1287
Step2:open terminal tool, telnet to CCM board. Open trace
1288
Step3:plugout an RRHn from daisy chain
1289
Step4:check the RE messges in CCM traces
1290
Expectable results:
1291
1292
Result1:after plugout RRHn, RE_GetAlarm_Indication (Alarm Master Port=ON) can be seen

in CCM traces
1293
1294
1295
Result2:check that the Reuid in RE_GetAlarm_Indication message should be the one of RRH
(n-1)
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 62/174

1296
1297
4.1.5.2.
LOOP BACK
1298
Test label 41:Daisy_Chain_RRH_Loop_Back_Test
1299
Purpose:
1300
1301
This test is to validate the digital transmission on RRH in Loopback mode after connecting the
NodeB to the RRHs
1302
Requirement:
1303
1304
D2U and all RRHs in Daisy Chain work smoothly
1305
TIL connected
1306
NodeB not in service, no cell configured
1307
Lamp is connected
1308
TM500 is connected
1309
Procedure:
1310
1311
Step1:open TIL, select one RRH in one fiber chain, send a cpri loopback test (loopback in
RRH) command, check Result1
1312
Step2:redo the test steps on the other RRHs in the same chain
1313
Step3:after loopback test, reset the NodeB to the normal status
1314
Step4:setup cell and call via lamp and TM500, check Result2
1315
Expectable results:
1316
Result1:all No error results are shown on TIL terminal
1317
1318
Result2:NodeB startup successfully, cell configuration and call setup is successful now
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 63/174

1319
1320
4.1.5.3.
ALARM
1321
Test label 42:Daisy_Chain_Alarm_of_RRH_Master_Link_Error
1322
Purpose:
1323
1324
This test is to check the Master link error alarm when RRH L1/L2 error is detected on RRH
master port. If RRH to be tested is the last one in fiber chain, no Master link error reported
1325
Requirement:
1326
1327
D2U and n RRHs in Daisy Chain work smoothly
1328
TIL connected
1329
OMCB connected
1330
Procedure:
1331
Step1:NodeB and all Daisy chain RRHs startup successfully
1332
1333
Step2:plug out fiber from master port of RRHn (RRHn is not the last one in this chain) in the
fiber chain
1334
1335
Step3:check downstream RRHs status and the result from bci command, TIL and OMC-B,
check Result1~Result4
1336
Step4:plug in fiber to this RRHn, check TIL, OMC-B and NodeB status, and check Result5
1337
Step5:trigger any other alarms, check Result6
1338
Expectable results:
1339
1340
Result1:the Master Link Error alarm from RRHn is shown with the bci command emo/alarm>
GlobalAlarms
1341
Result2:alarm is shown in TIL terminal with link error daisy chain segment alarm description
1342
Result3:alarm is shown in OMCB with link error daisy chain segment alarm description
1343
1344
Result4:all the downstream RRHs will be reset, RRH objects in TIL and OMC-B will be
deleted
1345
1346
Result5:all RRH objects plugged in will be created in TIL and OMC-B, NodeB will work
smoothly
1347
1348
Result6:all alarms will be displayed in TIL and OMC-B
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 64/174

1349
1350
4.1.5.4.
PLUG IN/OUT
1351
Test label 43:Daisy_Chain_RRH_Plug-out_and_Plug-in
1352
Purpose:
1353
1354
Check the cells are correctly configured when RRHx in the chain is plugged out/plugged in at
any time
1355
Requirement:
1356
1357
1358
OMCB is connected to the NodeB
1359
Lamp is connected to NodeB
1360
TM500 is connected to NodeB
1361
Procedure:
1362
1363
Step1:plug-out the optical fiber of RRHx(x = 1 n, 1<n<=6), type auditrequest on lamp then
check Result1
1364
Step2:after 3 Mins, plug-in the optical fiber of RRHx, check Result2
1365
Step3:Setup cells and make calls on RRHx or its downstream RRHs. Check Result3
1366
1367
Step4:repeat step1 ~ step3 with Next RRHx+1, till to the last RRHn in the chain. Check
Result4
1368
Expectable results:
1369
Result1:
1370
1371
Audit Response message raised to the lamp excludes cells of all downstream RRHx
and itself
1372
1373
Check RRHx object and the downstream RRH objects dont appear any more on the
OMC-B
1374
Result2:
1375
RRHx and all its downstream RRHs in this chain will reset
1376
1377
Type auditrequest on lamp then check Audit Response message raised to the lamp
includes cells of all downstream RRHx and itself
1378
Check RRHx object and the following RRHs objects appear again on the OMC-B
1379
Result3:Cell setup and call are both OK
1380
1381
Result4:same expected results as Result1~ Resul3
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 65/174

1382
1383
4.1.5.5.
SW UPGRADE
1384
Test label 44:Daisy_Chain_SW_Upgrade_On_RRH_Not_Need
1385
Purpose:
1386
1387
Check RRHs in the same chain with correct version, no need to update SW, these RRHs will
startup successfully and twice reset will not happen
1388
Requirement:
1389
1390
NodeB and all RRHs in Daisy Chain work smoothly
1391
OMC-B is connected to the NodeB
1392
Procedure:
1393
Step1:NodeB in power off status with the correct NodeB package
1394
Step2:ensure all RRHs with correct SW version, that is consistant with NodeB package
1395
1396
Step3:plug all RRHs in NodeB with Daisy Chain mode, then power on NodeB and to observe
the status of all RRHs. check Result1
1397
Step4:setup cells and voice call in these RRHs in the same chain. Check Result2
1398
Expectable results:
1399
Result1:all RRHs in this chain will do nothing. RRHs Reset will not happen
1400
1401
Result2:cell setup successfully and call will be successful also
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 66/174

1402
1403
Test label 45:Daisy_Chain_SW_Upgrade_Downstream_RRH
1404
Purpose:
1405
1406
Check the daisy chain RRH2 upgrade scenario when RRH1 has the correct SW version but
RRh2 has outdated SW version
1407
Check DWL procedure is OK when pluging in RRH3 during RRH2 is downloading
1408
Requirement:
1409
1410
D2U and 2 RRHs in Daisy Chain work smoothly
1411
RRH1 has correct SW version with NodeB package, but RRH2 has outdated one
1412
RRH3 has outdated SW version
1413
Procedure:
1414
Step1:power on NodeB and all RRHs
1415
Step2:check RRH1 status, check Result1
1416
Step3:check the status of RRH2 and its SW version, check Result2&3
1417
Step4:repeat Step1, and plug in RRH3 during RRH2 is downloading, check Result4
1418
Expectable results:
1419
Result1:NodeB and RRH1 work smoothly
1420
Result2:after RRH2 startup, it will download the correct SW version
1421
Result3:RRH2 reset again and till startup successfully. Its SW version is the same as RRH1
1422
1423
1424
Result4:after download is finished, RRH2 and RRH3 reset once, and it with correct SW
version after startup
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 67/174

1425
1426
Test label 46:Daisy_Chain_SW_Upgrade_by_OMC-B
1427
Purpose:
1428
Check the daisy chain RRH upgrade scenario that requested by OMC-B
1429
Requirement:
1430
1431
D2U and at least 2 RRHs in Daisy Chain work smoothly
1432
1433
Prepare two different NodeB loads that it include different RRH SW version
1434
Procedure:
1435
1436
Step1:NodeB and RRHs in Daisy Chain mode work smoothly with SW version A, check
Result1
1437
Step2:download SW version B to NodeB via OMCB
1438
Step3:after NodeB re-startup and NodeB work smoothly, check Result2
1439
Expectable results:
1440
Result1:NodeB and all RRHs work smoothly in Daisy Chain with SW version A
1441
1442
Result2:NodeB and all RRHs work smoothly in Daisy Chain with SW version B
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 68/174

1443
1444
4.1.5.6.
DOWNLOAD
1445
Test label 47:Daisy_Chain_PowerOff_PowerOn_Platform_During_RRH_Download
1446
Purpose:
1447
Check the impact that power off the platform when downloading SW for a new plug-in RRH
1448
Requirement:
1449
1450
1451
OMCB is connected to the NodeB
1452
Procedure:
1453
Step1:plug-in the optical fiber of RRHx(x = 2n, 2<n<=6), check Result1
1454
Step2:in the download procedure, power off the platform
1455
Step3:power on the platform and check Result2
1456
Expectable results:
1457
Result1:D2U and all other RRHs in Daisy Chain are not impact
1458
Download SW for the new plug-in RRH automatically
1459
1460
Result2:all RRHs will reset and download SW for RRHx uccessfully
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 69/174

1461
1462
4.1.5.7.
START-UP
1463
Test label 48:Daisy_Chain_RRH_Power_ON_Power_OFF
1464
Purpose:
1465
1466
Check the impact for downstream RRHs after RRH (n-1) Power on/Power off and not any
impact for upstream RRHs
1467
Requirement:
1468
1469
More than 2 RRHs connect to single fiber chain
1470
1471
Procedure:
1472
Step1:power off RRH (n-1), not the 1st RRH and not the last one, then check Result1
1473
Expectable results:
1474
1475
1476
Result1:after step1, RRH (n) will reset autonomously in 5 seconds, and every 5 seconds later,
the next RRH will reset automonously. This action will repeat to the last RRH
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 70/174

1477
1478
Test label 49:Daisy_Chain_in_Physical_But_not_Configured_in_DLU
1479
Purpose:
1480
It is configured as normal mode in DLU; add new RRH downstream doesnt impact the call
1481
Requirement:
1482
1483
NodeB is configured as normal mode
1484
Procedure:
1485
Step1:power on NodeB, check Result1
1486
Step2:setup cell in one RRH from lamp, check Result2
1487
Step3:setup a call in this cell from lamp, check Result3
1488
Step4:add a downstream RRH to this RRH (master port for RRH11 is enable), check Result4
1489
Step4:delete this call and cell
1490
Expectable results:
1491
Result1:NodeB is start up successfully
1492
Result2:make sure the cell setup is OK
1493
Result3:make sure this call can be setup successfully
1494
1495
Result4:call is still on going
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 71/174

1496
1497
4.1.5.8.
RESET
1498
Test label 50:Daisy_Chain_Reset_RRH_By_L1_Reset
1499
Purpose:
1500
1501
Check after RRH (n) reset by CPRI_L1_Reset, RRH (n) and all the downstream RRHs should
be reset. And all upsteam RRHs are not impact
1502
Requirement:
1503
1504
More than 2 RRH connect to the single fiber chain
1505
D2U and all RRH in Daisy Chain work smoothly
1506
Procedure:
1507
1508
Step1:reset RRH1 by CPRI_L1_Reset via bci command /pltf/cpri> ResetRE, then give
related link ID
1509
Step2:when all RRHs startup normally, check Result1
1510
1511
1512
Step3:reset RRH (n) which is not 1st RRH and not last one by Re_Reset_Request
(REid=Next_re) via bci command /reproxy/HardResetNextRE, then give related ID. Check
Result2
1513
Expectable results:
1514
Result1:all RRHs will reset in the chain
1515
1516
1517
Result2:the RRH (n) and all downstream RRHs will reset, and all upstream RRHs are not
impact
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 72/174

1518
1519
Test label 51:Daisy_Chain_Reset_RRH_due_to_Lock/Unlock_by_OMC-B
1520
Purpose:
1521
Check RRH (n) will reset after lock/unlock RRH (n) by OMC-B
1522
Requirement:
1523
1524
1525
D2U NodeB and all RRH in Daisy Chain work smoothly and connect to OMC-B
1526
Procedure:
1527
Step1:lock RRH (n) by OMC-B
1528
Step2:unlock RRH (n) by OMC-B, check Result1
1529
Expectable results:
1530
1531
1532
Result1:after step 2, RRH (n) will reset, but no any impact tofor other RRH (Include upstream
RRHs and downstream RRHs) in the chain
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 73/174

1533
1534
Test label 52:Daisy_Chain_Reset_BTS
1535
Purpose:
1536
Check RRH can be re-startup normally after NodeB reset
1537
Requirement:
1538
1539
1540
1541
Procedure:
1542
Step1:reset NodeB via telnet tool/ or OMC-B/ or TIL, check Result1
1543
Expectable results:
1544
1545
1546
Result1:all RRH in the chain will reset, the platform will startup smoothly, including NodeB and
all RRHs in the chain
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 74/174

1547
1548
Test label 53:Daisy_Chain_Reset_RRH_by_TIL
1549
Purpose:
1550
Check Reset RRH by TIL
1551
Requirement:
1552
1553
1554
1555
TIL is connected normally
1556
Procedure:
1557
Step1:reset RRH by TIL, check Result1&2
1558
Expectable results:
1559
Result1:after step 1, the RRH will be reset, and it can be startup normally
1560
1561
1562
Result2:this RRH reset will not impact any other RRH in same fiber chain, including
downstream RRHs and upstream RRHs
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 75/174

1563
1564
4.1.5.9.
CELL PROCEDURE
1565
Test label 54:Daisy_Chain_Cell_Setup
1566
Purpose:
1567
1568
The purpose of this test is to check that whether NodeB can setup the cell successfully on
RRHs which are on the same or different chain
1569
Requirement:
1570
1571
1572
Procedure:
1573
Step1:setup cells in each RRH from lamp. Check Result1&2&3
1574
Step2:delete cells
1575
Expectable results:
1576
Result1:info of CELL SETUP RESPONSE can be received in lamp
1577
1578
Result2:type in cap/ctx/cell/Detail on CCM, check whether includes the info of cells which is
created by lamp, and other cells information is OK
1579
1580
1581
Result3:after cell is setup successfully, check the Tx frequency and channel power indicated
in PSA are consistent with the ones in lamp
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 76/174

1582
1583
Test label 55:Daisy_Chain_Cell_Delete
1584
Purpose:
1585
1586
The purpose of this test is to check that whether NodeB can delete the cell correctly on RRHs
which are on the same or different chain
1587
Requirement:
1588
1589
More than 2 RRH connect to the single fiber chain.
1590
Procedure:
1591
1592
Step1:setup cells in each RRH from lamp. Make sure the cell setup successfully. Check
Result 1
1593
For example:cellset 0 and 1, cell 0 on one RRH, cell 1 on another RRH
1594
Step2:delete cell 0, check Result 2&3
1595
Step3:delete cell 1, check Result 2&4
1596
Expectable results:
1597
1598
1599
Result2:info of CELL DELETE RESPONSE can be received in lamp
1600
Result3:type in cap/ctx/cell/Detail on CCM, just the info of cell 1 is still reserved
1601
Result4:type in cap/ctx/cell/Detail on CCM, no any cell info is reserved
1602
4.1.5.10.
1603
Test label 56:Daisy_Chain_PlugIn_PlugOut_RRH_During_Call
1604
Purpose:
1605
1606
Check that the plug-in and plug-out activities of a new RRH (with different load) will not impact
to the existing calls
1607
Requirement:
1608
1609
1610
1611
Lamp is connected to NodeB
1612
TM500 is connected to NodeB
1613
Procedure:
1614
Step1:setup cells and make a call on RRHx(x = 1 , n, 1<n<=6)
1615
Step2:plug-in the optical fiber of a new RRH (with different load), check Result1
1616
1617
Step3:after 3 minutes, plug-out the optical fiber of a new RRH (with different load), check
Result2
RADIO FOR DAISY CHAIN
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 77/174

1618
1619
Step4:repeat step1 ~ step3 with Next RRHx+1, till to the last RRHn in the chain. Check
Result3
1620
Expectable results:
1621
Result1:
1622
Check RRHx object appear correctly on the OMC-B
1623
Cell setup and call are both OK
1624
Result2:
1625
Check RRHx object disappears on the OMC-B
1626
Cell setup and call are both OK
1627
1628
Result3:same expected results as Result1~ Resul2
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 78/174

1629
1630
Test label 57:Daisy_Chain_Reset_Upstream_RRH_During_Call
1631
Purpose:
1632
Check that the call is still successful when SW reset the upstream RRH.
1633
1634
1635
1636
Requirement:
1637
Procedure:
1638
Step 1:NodeB and all RRHs are start-up with the correct NodeB package;
1639
Step 2:Do an AMR call on RRH2, check Result 1;
1640
Step 3:SW reset RRH1 via TIL or OMCB, check Result 2.
1641
Expectable Results:
1642
Result 1:The amr call is OK;
1643
1644
1645
Result 2:RRH1 will be OK after SW reset, and the amr call on RRH2 is still running
successfully.
1. Platform configuration applicable;

2. NodeB and RRHs (More than 2 RRHs) on the Daisy Chain are working smoothly, for
example, RRH1 is upstream RRH and RRH2 is downstream RRH on the same chain.
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 79/174

1646
1647
4.1.6.
UA7.1 GENERAL TEST DESCRIPTION FOR FRS73695 STSRX+Y
1648
4.1.6.1.
1649
Test label 58:STSRx+y_Startup_In_Normal_Mode
1650
Purpose:
1651
1652
The purpose of this test is to check that NodeB with STSRx+y configuration in normal mode
can be startup successfully
1653
Requirement:
1654
1655
NodeB is configured as STSRx+y either in daisy chain or in star mode
1656
STSR1+1, 2+1, 2+2 are supported
1657
Procedure:
1658
Step1:power on NodeB with all of RRHs, open the CCM trace, and check Result1&2
1659
Expectable results:
1660
Result1:telnet to CCM board:
START-UP
1661
1662
type emo/bts, check that MIBState is Build, CheckDLU is OK. Tx and Rx path are
all enable
1663
1664
type emo/data/cfiledump, check AntennaConnectionId for both RRH should be the

same as in DLU
1665
1666
Result2:after NodeB startup successfully, cell and basic call should be setup successfully
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 80/174

1667
1668
Test label 59:STSRx+y_Startup_In_Degrade_Mode
1669
Purpose:
1670
1671
The purpose of this test is to check that NodeB with STSRx+y configuration in degrade mode
can be startup successfully
1672
Requirement:
1673
1674
1675
1676
Procedure:
1677
Step1:power on NodeB with main RRH, open the CCM trace, and check Result1&2&4
1678
Step2:power on NodeB with div RRH, and check Result3
1679
Expectable results:
1680
1681
type emo/bts, check that MIBState is Build, CheckDLU is OK
1682
1683

same as in DLU
1684
Result2:after NodeB startup successfully:
1685
star mode:Tx and Rx path for main RRH are enable
1686
1687
daisy chain mode:upstream RRHs of this main RRH are startup successfully, and
downstream RRHs are not startup
1688
Result3:after NodeB startup successfully:
1689
star mode:Tx and Rx path for div RRH are enable
1690
1691
daisy chain mode:only Tx and Rx path for the upstream RRHs are enable, no this
paired RRH
1692
1693
Result4:cells and basic call should be setup successfully
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 81/174

1694
1695
4.1.6.2.
PLUG IN/OUT
1696
Test label 60: STSRx+y_RRH_Plugout_Plugin
1697
Purpose:
1698
1699
The purpose of this test is to check the correct configuration when plug out/in main or div RRH
at any time
1700
Requirement:
1701
1702
1703
1704
Procedure:
1705
Step1:power on NodeB with both main and div RRH. Check Result1&4
1706
Step2:plug out any RRH in the paired RRH. Check Result2&4
1707
Step3:plug in this RRH. Check Result3&4
1708
Expectable results:
1709
1710
1711
all enable
1712
1713

same as in DLU
1714
1715
Result2:check the Tx and Rx path by typing emo/bts on CCM, the behaviour is different
according to the topology:
1716
1717
star mode:if plug out the main RRH, only Tx and Rx path for div RRH are enable; if
plug out div RRH, only Tx and Rx path for main RRH are enable
1718
1719
1720
daisy chain mode:if plug out the main RRH, only Tx and Rx path for the upstream
RRHs are enable; if plug out div RRH, Tx and Rx path for main RRH and upstream
RRHs are enable
1721
Result3:after RRH startup successfully, check Tx and Rx path of all the RRHs are all enable
1722
1723
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 82/174

1724
1725
Test label 61: STSRx+y_Plugin_RRH_With_Different_Load
1726
Purpose:
1727
1728
The purpose of this test is to check the correct configuration when plug in div/main RRH with
different load
1729
Requirement:
1730
1731
NodeB is configured as STSRx+y either in daisy chain mode or in star mode
1732
1733
Procedure:
1734
Step1:main or div RRH in the paired RRH is plugged in, and the other is not
1735
Step2:power on NodeB. Check Result1&2&4
1736
Step3:plug in the other RRH with different load. Check Result3&4
1737
Expectable results:
1738
1739
type emo/bts, check that MIBState is Build, CheckDLU is OK
1740
1741

same as in DLU
1742
1743
Result2:check the Tx and Rx path by typing emo/bts on CCM, the behavior is different
according to the topology:
1744
1745
1746
star mode:if div RRH is plug in and main RRH is not, only Tx and Rx path for div RRH
are enable; if main RRH is plug in and div RRH is not, only Tx and Rx path for main
RRH are enable
1747
1748
1749
daisy chain mode:if main RRH is not plug in, only Tx and Rx path for the upstream
RRHs are enable; if div RRH is not plug in, Tx and Rx path for main RRH and
upstream RRHs are enable
1750
Result3:when plugging-in the RRH with different load:
1751
1752
star mode:this RRH will upgrade to the same load with the RRH which is already
plug-in, after this RRH reset, Tx and Rx path of all the RRHs are all enable
1753
1754
daisy chain mode:this RRH and the downstream RRHs will upgrade and reset, then
all the Tx and Rx path are enable
1755
1756
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 83/174

1757
1758
4.1.6.3.
RESET
1759
Test label 62: STSRx+y_RRH_Reset_By_OMC-B
1760
Purpose:
1761
Check the RRH can startup correctly when reset by OMC-B
1762
Requirement:
1763
1764
1765
1766
Procedure:
1767
1768
Step2:reset main RRH from OMC-B. Check Result2&4&5
1769
Step3:reset div RRH from OMC-B. Check Result3&4&5
1770
Expectable results:
1771
1772
1773
all enable
1774
1775

same as in DLU
1776
1777
1778
Result2:check the Tx and Rx path by typing emo/bts on CCM, when main RRH is resetting,
Tx and Rx path for main RRH are disable; after main RRH startup successfully, Tx and Rx
path of main RRH are enable
1779
1780
1781
Result3:check the Tx and Rx path by typing emo/bts on CCM, when div RRH is resetting, Tx
and Rx path for div RRH are disabled; after div RRH startup successfully, Tx and Rx path of
div RRH are enable
1782
1783
1784
Result4:if it is in daisy chain mode, this RRH reset will not impact any other RRH in same fiber
chain, including downstream RRHs and upstream RRHs. If in star mode, this RRH reset will
not impact any other RRH
1785
1786
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 84/174

1787
1788
Test label 63: STSRx+y_RRH_Reset_By_TIL
1789
Purpose:
1790
Check the RRH can startup correctly when reset by TIL
1791
Requirement:
1792
1793
1794
1795
Procedure:
1796
1797
Step2:reset main RRH from TIL. Check Result2&4&5
1798
Step3:reset div RRH from TIL. Check Result3&4&5
1799
Expectable results:
1800
1801
1802
all enable
1803
1804

same as in DLU
1805
1806
1807
Result2:check the Tx and Rx path by typing emo/bts on CCM, when main RRH is resetting,
Tx and Rx path for main RRH are disable; after main RRH startup successfully, Tx and Rx
path of main RRH are enable
1808
1809
1810
Result3:check the Tx and Rx path by typing emo/bts on CCM, when div RRH is resetting, Tx
and Rx path for div RRH are disabled; after div RRH startup successfully, Tx and Rx path of
div RRH are enable
1811
1812
1813
Result4:if it is in daisy chain mode, this RRH reset will not impact any other RRH in same fiber
chain, including downstream RRHs and upstream RRHs. If in star mode, this RRH reset will
not impact any other RRH
1814
1815
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 85/174

1816
1817
4.1.6.4.
OMC-B OPERATION
1818
Test label 64: STSRx+y_OMC-B_DLU_Check
1819
Purpose:
1820
1821
Check that if antennaConnectionId of any one RRH is not null, antennaConnectionId of all
others should not be null
1822
Check whether a RemoteRadioHead instance is in an AntennaAccess
1823
Check the maximum number of RemoteRadioHeads within a sector
1824
1825
If 2 RRH have the same antennaConnectionId, the rxCabling type of corresponding

AntennaAccess should be set as mainAndDiversityInput
1826
Requirement:
1827
1828
1829
1830
Procedure:
1831
Step1:power on NodeB with both main and div RRH. Check Result1
1832
1833
Step2:after NodeB get a full starup, through OMC-B, antennaConnectionId in one RRH has a
correct value and in other RRH does not present, then rebuild. Check Result2
1834
1835
Step3:after NodeB get a full starup, through OMC-B, antennaConnectionId in one RRH has a
special value which does not in any AntennaAccess, then rebuild. Check Result3
1836
1837
Step4:after NodeB get a full starup, through OMC-B, antennaConnectionId in three RRH has
the same value, then rebuild. Check Result4
1838
1839
Step5:after NodeB get a full starup, through OMC-B, rxCabling in AntennaAccess is set to
mainInputOnly, then rebuild. Check Result5
1840
Expectable results:
1841
1842
1843
all enable
1844
1845

same as in DLU
1846
Result2:
1847
1848
In xCCM, typing /emo/alarm/ChkConfigFile, report an alarm INVALID CONFIGURATION

DATA with manufacture information of alarm Not Exist Antenna Connection. Rebuild failed
1849
Typing /emo/Iconfig, MIBState is Build KO, and DLUCheck is KO
1850
1851
In OMC-B, there is the alarm "INVALID CONFIGURATION DATA", in Addtional Test there is
the alarm description Not Exist Antenna Connection.
1852
Result3:
1853
1854
1855
In xCCM, typing /emo/alarm/ChkConfigFile,report an alarm INVALID CONFIGURATION

DATA with manufacture information RRH Not Present In Antenna Access. Rebuild
failed.Report RRH Not Present In NodeBCell at the same time.
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 86/174

1856
Typing /emo/Iconfig, MIBState is Build KO, and DLUCheck is KO.
1857
1858
In OMC-B, there is the alarm "INVALID CONFIGURATION DATA", in Addtional Test there is
the alarm description RRH Not Present In Antenna Access.
1859
Result4:
1860
1861
1862
In xCCM, typing /emo/alarm/ChkConfigFile, report an alarm CONFIGURATION FILE

INCONSISTENT WITH HARDWARE with manufacture information Too many RRH in
AntennaAccess. Rebuild failed.
1863
1864
1865
In OMC-B, there is the alarm " CONFIGURATION FILE INCONSISTENT WITH HARDWARE ",
in Addtional Test there is the alarm description Too many RRH in AntennaAccess.
1866
Result5:
1867
1868
In xCCM, typing /emo/alarm/ChkConfigFile,report an alarm INVALID CONFIGURATION

DATA RxCabling type out of range. Rebuild failed.
1869
1870
1871
1872
In OMC-B, there is the alarm " INVALID CONFIGURATION DATA ", in Addtional Test there is
the alarm description RxCabling type out of range.
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 87/174

1873
1874
4.1.6.5.
CELL PROCEDURE
1875
Test label 65: STSRx+y_Cell_Setup_In_Normal_Mode
1876
Purpose:
1877
Check that cell setup scenario is correct in STSRx+y normal mode
1878
Requirement:
1879
1880
1881
1882
Procedure:
1883
Step1:power on NodeB with both of main and div RRH. Check Result1
1884
1885
Step2:setup cells in main and div RRH from lamp, for example cell1 in main RRH and cell7 in
div RRH. Check Result2&3&4
1886
Step3:delete cells
1887
Step4:re-do step2 and step3.
1888
Expectable results:
1889
1890
1891
all enable
1892
1893

same as in DLU
1894
Result2:CELL SETUP RESPONSE can be received in lamp
1895
1896
Result3:after cells setup successfully, telnet to main and div RRH, use commands
fcpcTipTxFreqDataShow and fcpcTipRxFreqDataShow, check:
1897
1898
in main RRH, for cell1, both Tx and Rx carrier are exist; for cell7, only Rx carrier is
exist
1899
in div RRH, for cell7, both Tx and Rx carrier are exist; for cell1, only Rx carrier is exist
1900
1901
1902
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 88/174

1903
1904
Test label 66: STSRx+y_Cell_Setup_In_Degrade_Mode
1905
Purpose:
1906
Check that cell setup scenario is correct in STSRx+y degrade mode
1907
Requirement:
1908
1909
1910
If in daisy chain mode, do not plug out main RRH in any paired RRH
1911
1912
Procedure:
1913
1914
Step1:power on NodeB with one RRH (RRH1) of any paired RRH (RRH1+RRH2), meet
requirement3. Check Result1
1915
Step2:setup cell in RRH1 from lamp, check Result2&4
1916
Step3:power on RRH2, check Result3&4
1917
Step4:delete cell
1918
Expectable results:
1919
1920
1921
type emo/bts, check that MIBState is Build, CheckDLU is OK. Tx and Rx path of
RRH1 are enable
1922
1923

same as in DLU
1924
Result2:CELL SETUP RESPONSE can be received in lamp
1925
1926
1927
Result3:after RRH2 startup successfully, telnet to this RRH, use commands

fcpcTipTxFreqDataShow and fcpcTipRxFreqDataShow, check no Tx carrier but only Rx
carrier for this cell is exist in RRH2
1928
1929
1930
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 89/174

1931
1932
Test label 67: STSRx+y_Cell_Delete_In_Normal_Mode
1933
Purpose:
1934
Check that cell delete scenario is correct when STSRx+y configuration in normal mode
1935
Requirement:
1936
1937
1938
1939
Procedure:
1940
1941
1942
Step2:setup cells in main and div RRH respectively from lamp, for example cell1 in main RRH
and cell7 in div RRH. Check Result2
1943
Step3:delete cell1 from lamp, check Result3&4
1944
Step4:delete cell7 from lamp, check Result3&5
1945
Expected results:
1946
1947
1948
all enable
1949
1950

same as in DLU
1951
1952
Result3:CELL DELETE RESPONSE can be received in lamp
1953
1954
Result4:after cell1 is deleted successfully, telnet to main and div RRH, and use commands
fcpcTipTxFreqDataShow and fcpcTipRxFreqDataShow to check:
1955
in main RRH, only Rx carrier for cell7 is exist, no other carrier information
1956
in div RRH, only Tx and Rx carrier info for cell7 are exist, no carrier info for cell1
1957
1958
1959
1960
Result5:after cell7 is deleted successfully, telnet to main and div RRH, use commands
fcpcTipTxFreqDataShow and fcpcTipRxFreqDataShow to check no carrier info exist on
both paired RRH
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 90/174

1961
1962
Test label 68: STSRx+y_Cell_Delete_By_RRH_Reset
1963
Purpose:
1964
Check cells can be deleted when Tx path of this cell is disable
1965
Requirement:
1966
1967
1968
1969
Procedure:
1970
1971
1972
Step2:setup cells in main and div RRH from lamp, for example cell1 in main RRH and cell7 in
div RRH. Check Result2
1973
1974
Step3:reset main RRH from TIL, check Result3&4&5. (Note:reset div RRH could have the
similar result as main RRH.)
1975
Step4:delete cells
1976
Expectable results:
1977
1978
1979
all enable
1980
1981

same as in DLU
1982
1983
1984
Result3:after main RRH is startup successfully, telnet to main and div RRH, and use
commands fcpcTipTxFreqDataShow and fcpcTipRxFreqDataShow to check:
1985
in main RRH, only Rx carrier for cell7 is exist, no other carrier information
1986
in div RRH, only Tx and Rx carrier info for cell7 are exist, no carrier info for cell1
1987
Result4:after NodeB startup successfully, basic call can be setup in cell7 successfully
1988
1989
1990
Result5:if in daisy chain mode, this RRH reset will not impact any other RRH in same fiber
chain, including downstream RRHs and upstream RRHs
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 91/174

1991
1992
4.1.6.6.
1993
Test label 69: STSRx+y_TMA_Startup
1994
Purpose:
1995
Check the correct behaviour with/without TMA equipment and with/without TMA configuration
1996
Requirement:
1997
1998
1999
2000
Procedure:
2001
Step1:NodeB+RRH/TRDU connection without TMA
2002
2003
Step2:configure TMA access in DLU by OMC-B, for example, TMA configured in

AntennaConnection11
2004
TMA MANAGEMENT
Sector [0]:
2005
2006
AntennaConnection
2007
TmaAccessType
:0
:11
:1
2008
Step3:reset NodeB. Check Result1&2
2009
Step4:TMA equipment is connected to the RRH
2010
2011
Step5:configure TMA access in DLU by OMC-B, for example, TMA configured in

AntennaConnection11
2012
Sector [0]:
2013
2014
AntennaConnection
2015
TmaAccessType
:0
:11
:1
2016
Step6:power on this RRH and reset NodeB. Check Result3&4&5
2017
2018
Step7:configure no TMA access in DLU by OMC-B, for example, TMA hasnt been configured
in AntennaConnection11
2019
Sector [0]:
2020
2021
AntennaConnection
2022
TmaAccessType
:0
:11
:0
2023
Step8:reset NodeB. Check Result4&5
2024
Expectable results:
2025
2026
Result1:after NodeB is starting up, TMA alarm on main RRH will be reported to TIL and
OMC-B, and no TMA alarm in div RRH.
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 92/174

2027
2028
Result2:telnet to CCM, type emo/bts, check that local cells configured in

AntennaConnection11 are enabled, because only Rx path on mian RRH have been impacted.
2029
Result3:
2030
2031
2032
In CCM trace, check TmaAccessReq, if using inhouse RRH, main RRH is in TMA Umts
mode and div RRH is in TMA Mix mode; if using TRDU, both main and div RRH are in TMA
Umts mode
2033
2034
2035
In lamp, typing auditrequest, the maxpower for cells in this antennaAccess is decreased. The
descreased value is 3.5 dB which means 35 should be descreased from original value. For
example, the maxpower is 430 without TMA, and it changed to 395 with TMA.
2036
2037
Result4:check NodeB could startup normally without alarm and error. Telnet to CCM, type
emo/bts, check that local cells configured in AntennaConnection11 are enabled
2038
2039
Result5:after NodeB startup successfully, basic call can be setup successfully
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 93/174

2040
2041
4.1.6.7.
FAULT MANAGEMENT
2042
Test label 70: STSRx+y_Fault_Management_VSWR
2043
Purpose:
2044
Check VSWR alarm in STSRx+y mode
2045
Requirement:
2046
2047
2048
2049
Procedure:
2050
Step1:power on NodeB with both main and div RRH
2051
Step2:RRH-ih:run the OCI tool for main RRH
2052
Step3:
2053
RRH-ih:click the mode to ON, select the alarm Tx VSWR Level 2 Alarm, check Result1
2054
2055
Step4:RRH-ih:stop other alarms, click the mode to ON, select the alarm Tx VSWR Alarm,
check Result2
2056
Step5:RRH-ih:run the OCI tool for div RRH
2057
2058
Step6:RRH-ih:stop other alarms, click the mode to ON, select the alarm Tx VSWR Level 2
Alarm, check Result3
2059
2060
Step7:RRH-ih:stop other alarms, click the mode to ON, select the alarm Tx VSWR Alarm,
check Result5
2061
Note, refer to the latest TRDU alarm document for TRDU VSWR alarm
2062
Expectable results:
2063
Result1:in OMC-B, VSWR LEVEL Main is reported;
2064
2065
From CCM trace, type /emo/alarm> GlobalAlarms, and RRH VSWR MAIN can be found for
main RRH;
2066
In TIL, VSWR Level 3 MAIN
2067
2068
Result2:From CCM trace, type /emo/alarm> GlobalAlarms, and RRH VSWR MAIN can be
found for main RRH;
2069
In TIL, VSWR Level 2 MAIN
2070
Result3:in OMC-B, VSWR LEVEL Div is reported;
2071
2072
From CCM trace, type /emo/alarm> GlobalAlarms, and RRH VSWR DIV can be found for
main RRH;
2073
In TIL, VSWR Level 3 DIV
2074
2075
Result5:From CCM trace, type /emo/alarm> GlobalAlarms, and RRH VSWR DIV can be
found for main RRH;
2076
2077
In TIL, VSWR Level 2 DIV
<TX VSWR Level2 Alarm> is reported in this mian RRH
<TX VSWR Alarm> is reported in this mian RRH
<TX VSWR Level2 Alarm> is reported in this div RRH.
<TX VSWR Alarm> is reported in this div RRH.
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 94/174

2078
2079
4.1.6.8.
COMMON MEASUREMENT
2080
Test label 71: STSRx+y_Common_Measurement_Normal_Mode
2081
Purpose:
2082
Test the stability of NodeB with the startcmeas command including all measurement types
2083
Requirement:
2084
RNC Simulator (Lamp)
2085
The radio configuration is STSRx+y in star or chain mode
2086
Procedure:
2087
Step1:power on NodeB and paired RRHs
2088
2089
2090
Step2:set up cell and start common measurement for both transmit carrier power and receive
carrier power, keep this test continuously running at least 12 hours without any traps or
abnormal behaviors on the NodeB, check Result1
2091
Expectable results:
2092
Result1:value in lamp (RTWP, TCP) should be correct from beginning to ending
2093
2094
2095
If value of Received Total Wide-band Power (RTWP) is between 60 and 65, the test
result is acceptable. If it is too high or too low, the test result is abnormal.
(RTWP(dBm)=RTWP value * 0.1 + (-112) )
2096
Transmit carrier power(TCP) =10[cpICH(dBm)-cell(dBm)]
(dBm=10log(mw))
2097
For example:cellset 0 330 430 9640 10590
2098
2099
Cell (dBm) =4.3, cpICH (dBm) =3.3, TCP =10-1 =10%
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 95/174

2100
2101
4.1.6.9.
DELAY MANAGEMENT
2102
Test label 72: STSRx+y_Total_Delay_Management_Normal_Mode
2103
Purpose:
2104
Test whether the delay management of NodeB is correct in STSRx+y normal mode.
2105
Requirement:
2106
RNC Simulator (Lamp)
2107
The radio configuration in STSRx+y
2108
The paired RRHs in star or chain mode
2109
Both main RRH and div RRH exist in the sector
2110
Procedure:
2111
Step1:reset the NodeB
2112
Step2:when NodeB starts up, check result1
2113
Step3:watch the delay value in the menu (bci/emo/bts), check result2
2114
Expectable results:
2115
Result1:type bci/emo/bts, check that local cells operational state changes to ok
2116
Result2:the delay value should be changed, but the local cells operational state is still ok
2117
2118
DL delay value =Ccm+Trm+RFoutput to Antenna

authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 96/174

2119
2120
UL delay value is an alignment of main and div Rx delay, it nearly equal to 1792.
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 97/174

2121
2122
4.1.7.
2123
2124
NOTE:In following test cases, we will encounter some cases that NOT have enough capacity
license. In this condition, it will follow these rules to confirm which cell is enabled.
2125
2126
2127
2128
FRS 34454 CAPACITY LICENSE ENHANCEMENT
Sort BTS Cells:

First => the BTS Cell supporting the higher LCG priority
Second, for the same LCG priority => BTS Cell belonging to the sector supporting the most
frequencies
2129
Third, for the same LCG priority, the same frequencies rank in their sector => sort by LCG Id
2130
Fourth, for the same LCG, the same frequencies rank in their sector => sort by Local CellId
2131
Test label 73: Capacity_Licensing_rrhCarrierCapacityLicensing_Increase
2132
Purpose:
2133
Verify the 2nd carrier Capacity License usage when the license is increased
2134
Requirement:
2135
NodeB is startup
2136
STSRx+y, Daisy Chain, Star mode are supported
2137
Config 3 RRHs on DLU, with 2nd carrier on every RRH
2138
rrhCarrierCapacityLicensing = 0
2139
rrhCarrierCapacityLicensing is determined by the number of RRHs
2140
All LCG prority is same.
2141
Procedure:
2142
Take 3RRHs for example
2143
Step1:NodeB startup with 3 Sectors, check Result1
2144
Step2:set online rrhCarrierCapacityLicensing = 1, check Result2
2145
2146
2147
2148
Step6:verify counter 10215, check Result6
2149
Expectable results:
2150
Result1:check that all the cells on 2
2151
2152
rrhCarrierHwCapacity = 3, rrhCarrierSwCapacity = 0. Check it from Dynamic Data of Capacity

from OMC-B
nd
carrier are disabled
2153
2154
RRHSecondCarriersCapacity (10215) counter is non-zero

authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 98/174

2155
Result2:check that cells on two 2nd carrier are disabled,
2156
The Cell is enabled that the Cell ID is min in 2nd carrier.
2157
2158

from OMC-B
2159
2160
2161
Result3:check that cells on one 2nd carrier are disabled
2162
2163

from OMC-B
2164
2165
2166
Result4:check that cells on all 2nd carriers are enabled
2167
2168

from OMC-B
2169
No Alarm on OMC-B about Capacitylicense
2170
2171
Result5:check that there is no change; cells on all 2nd carriers are enabled
2172
2173

from OMC-B
2174
No Alarm on OMC-B about Capacitylicense
2175
RRHSecondCarriersCapacity(10215) counter is non-zero
2176
2177
Result6:using the menu RTC => PM => FastClock:A => Display in a telnet console, check that
the
2178
2179
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 99/174

2180
2181
2182
Test label
74:Capacity_Licensing_rrhCarrierCapacityLicensing_Decrease
2183
Purpose:
2184
Verify the 2 Carrier Capacity License when the license is decreased
2185
Requirement:
2186
NodeB is startup
2187
STSRx+y, Daisy Chain, Star mode are supported
2188
Config 3 RRHs on DLU, with 2nd carrier on every RRH
2189
rrhCarrierCapacityLicensing = infinite
2190
rrhCarrierCapacityLicensing is determined by the number of RRHs
2191
Procedure:
2192
Take 3 RRHs for example.
2193
Step1:NodeB startups with 3 sectors successfully, check Result1
2194
2195
2196
2197
2198
Step6:verify counter 10215, check Result6
2199
Expectable results:
2200
Result1:check that all the cells are enabled
2201
2202
rrhCarrierHwCapacity = 3, rrhCarrierSwCapacity = 3, Check it from Dynamic Data of Capacity

from OMC-B
2203
2204
Result2:check that there is no change and NodeB does not reset
2205
Result3:check that there is no change and NodeB does not reset
2206
Result4:the NodeB should reset. Check that two cells on 2 carrier are disabled
2207
2208

from OMC-B
nd
nd
2209
2210
2211
Result5:the NodeB should reset. Check that all the cells on all 2nd carrier are disabled
2212
2213

from OMC-B
2214
2215
2216
2217
Result6:using the menu RTC => PM => FastClock:A => Display in a telnet console, check that
the
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 100/174

2218
2219
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 101/174

2220
2221
4.1.8.
FRS 34396
RRH PA AUTO SWITCH OFF
2222
Test label 75: STSRx+y_PA_Auto_Switch_Off
2223
Purpose:
2224
Check the functionality of FRS 34396
2225
Requirement:
2226
Platform:2UV2 rack + xCCM-U + xCEM-U
2227
Procedure:
2228
Step1:configure NodeB and RRH in STSRx+y mode
2229
Step2:NodeB and RRH are working properly
2230
Step3:setup one or more cells on both of the Main RRH and Diversity RRH
2231
Step4:delete cells on either of the Main RRH or Diversity RRh only
2232
Step5:check the following result
2233
Expectable results:
2234
Result1:while all cells in one RRH were deleted, this RRH would be powered off automatically
2235
Result2:the delay time that RRH power off after cell delete is more than 120s
2236
Result3:compare the power when cell set up with the power RRH power off
2237
2238
4.1.8.1.
LED FOR ASB RRH
2239
Test label 76: ASB RRH LED turn On/Off
2240
Purpose:
2241
Check to turn on/off led.
2242
Requirement:
2243
The TIL is started,
2244
NodeB is connected.
2245
Procedure:
2246
On TIL, turn on/off led via RRH or NodeB(OP: It decides by the RRH and NodeB architecture.).
2247
2248
2249
2250
2251
Expectable results:
2252
Purpose:
2253
Check LED status of ASB RRH via telnet to ASB RRH from Ethernet port.
2254
Check LED status of ASB RRH via telnet to ASB RRH from D2U.
2255
Requirement:
After turn off led, no led displayed on Til.

After turn on led, the led information should be display correctly
Test label 77: Get_LED_status_from_RRH
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 102/174

2256
NodeB is connected, ASB RRH work smoothly.
2257
Procedure:
2258
1. Startup platform, ensure D2U and RRH work smoothly;
2259
2260
2. Telnet to RRH via Ethernet port to check the LED status with command of
ledTipMlDisplayState, Check Result1;
2261
2262
3. Telnet to RRH via D2U to check the LED status with command of
2263
Expectable results:
2264
Result1: The LED status should be correct with current RRH status.
2265
2266
Note: The LED status information please refer to document of ARD_0546
2267
4.1.8.2.
2268
Test label 78: VSWR_Measurement_every_2s_on_ASB_RRH
2269
Purpose:
2270
Check the VSWR measurement report from RRH.
2271
Requirement:
2272
2273
Procedure:
VSWR
2274
2275
2276
2. Telnet to RRH via Ethernet port or D2U to check the LED status with command of
2277
Expectable results:
2278
2279
Result1: From the trace of RRH, the VSWR measurement report should
be report every 2s.
2280
2281
Test label 79:VSWR_ alarm_Transmit_to_D2U_in_10s
2282
Purpose:
2283
Check the VSWR alarm report to D2U in 10s.
2284
Requirement:
2285
2286
Procedure:
2287
2288
2. Trigger VSWR alarm and check it from D2U, Check Result1;
2289
Expectable results:
2290
2291
2292
Result1: From the trace of RRH and trace of D2U, the VSWR alarm report
D2U within 10s.
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 103/174

2293
Test label 80: Call_service_after_Tx_RF_Port_Open_Test
2294
Purpose:
2295
2296
Check RRH work smoothly after Tx RF port open.
2297
2298
2.
TIL connection
2299
3.
OMCB connection
2300
4.
Lamp connection and configured
2301
Procedure:
2302
Step1:Tx/Rx RF port open;
2303
Step2:Cell setup at lamp and keep it 3Mins;
2304
Step3:Cell delete;
2305
Step4: Connect radio cable to TM500;
2306
Step5: Make Basic call. Check Result1;
2307
Expectable results:
2308
Result1: Basic Call service work smoothly;
2309
2310
Test label 81: TX-VSWR_Level 2-alarm_RRH
2311
Purpose:
2312
2313
2314
Check TX VSWR level 2 alarm will report if RRH with 4db attenuation and short cut connector
at the antenna
2315
2316
2.
TIL connection
2317
3.
OMCB connection
2318
4.
2319
Procedure:
2320
Step1:Add 4db attenuation and short cut connector at the RRH antenna
2321
Step2:Cell setup at lamp
2322
Step3:Wait for several minutes
2323
2324
Expectable results:
2325
2326
After several minutes VSWR level 2 medium alarm will report to TIL and OMCB, RRH in
degrade status
2327
Cell still is up, and it wont be impacted
2328
2329
VSWR measurement values display on OCI(ASB RRH local maintence tool) should be
correctly
Requirements:
Requirements:
Cell setup should be successful
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 104/174

2330
2331
Test label 82: TX-VSWR_Level 3-alarm_RRH
2332
Purpose:
2333
2334
2335
Check TX VSWR level 3 alarm will report if RRH with 1db attenuation and short cut connector
at the antenna
2336
2337
2.
TIL connection
2338
3.
OMCB connection
2339
4.
2340
Procedure:
2341
Step1:Add 1db attenuation and short cut connector at the RRH antenna
2342
Step2:Cell setup at lamp
2343
Step3:Wait for several minutes
2344
2345
Expectable results:
2346
2347
After several minutes VSWR level 3 major alarm will report to TIL and OMCB, RRH in broken
status
2348
Cell will be down (RSI will send to lamp to indicate the impacted cell)
2349
2350
VSWR measurement values display on OCI(ASB RRH local maintence tool) should be
correctly
Requirements:
Cell setup should be successful
2351
2352
4.1.8.3.
SINGLE RX PORT
2353
Test label 83: Call_service_on_Single_Rx_port_only
2354
Purpose:
2355
2356
Check call service with single Rx port only;
2357
2358
2. TIL connection
2359
3. OMCB connection
2360
4. Lamp connection and configured
2361
5. Disconnect Rx RF port between RRH and TM500
2362
Procedure:
2363
2364
2365
2366
Step1:Basic call service on single Rx port only, check Result1:
2367
Purpose:
Requirements:
Test label 84:

Mobility_Softer_HO_HSDPA_to_R99_on_Single_Rx_port_only
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 105/174

2368
2369
Check that a complete procedure of softer handover from a cell supporting HSDPA service to
a cell supporting only R99 is successfully
2370
Requirement:
2371
2372
Lamp connection
2373
TM500 connection
2374
2375
2376
Disconnect Rx RF port between RRH and TM500
2377
Procedure:
2378
Step1:setup a RL on cell1 with HSDPA and synchronize the UE with it
2379
2380
Step3:add RL2 (DCH leg on the target cell) which is identical to the ADCH link
2381
2382
Step4:perform a SRLR procedure that will delete the HS-DSCH on the source cell and modify
associated parts of both legs to DCH
2383
2384
Step5:delete initial leg
2385
4.1.8.4.
2386
2387
In this section, it describe all external alarm that simulate it with external alarm board. For ASB
RRH, maybe we need .
ASB RRH EXTERNAL ALARM TEST
2388
2389
Test label 85: External Alarms_ASB RRH
2390
Purpose:
2391
Check that the External Alarms can be reported to TIL and OMCB correctly.
2392
2393
2394
2395
2396
Requirement:
2397
Procedure:
2398
Step 1:
Connect the External Alarm Board with RRH.
2399
Step 2:
Enable External Alarm Mask from TIL
TIL connection
OMCB connection
External Alarm Board
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 106/174
2400
2401
Step 3:
Press the button for each different External Alarm on external alarm board.
2402
Step 4:
Check the alarm information from TIL and OMCB.
2403
Step 5:
2404
Step 6:
2405
Expectable results:
2406
2407
2408
Step 4: All the 6 External Alarms can be displayed in TIL corresponding to the External alarm
board. External alarms will report to OMCB correctly also.
Step 6: After rack2u reset, external alarm still report to OMCB and TIL correctly
2409
4.1.8.5.
2410
2411
In this section, it describe all internal alarm that simulate it with OCI tools. For ASB RRH,
maybe no OCI tools to trigger these alarms. We can trigger it with command of ASB RRH.
Reset Rack2u
Check the alarm information from TIL and OMCB.
ASB RRH INTERNAL ALARM TEST
2412
2413
Test label 86: ASB RRH_Internal-Alarm-Family
2414
Purpose:
2415
2416
2417
2418
2419
2420
2421
2422
Check all ASB RRH internal alarm
Requirement:
TIL connection
OMCB connection
OCI Tool
Procedure&Expected Results:
Refer to test label
Slave Link Low Optical Signal Level_ASB RRH
Slave Link Loss of Framing (LOF) _ASB RRH
Slave Link Loss of Signal (LOS) _ASB RRH
Slave Link Port Transceiver Failure_ASB RRH
Slave Link Remote Alarm Indication (RAI) _ASB RRH
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 107/174

Master Link Low Optical Signal Level_ASB RRH
Master Link Loss of Framing (LOF) _ASB RRH
Master Link Loss of Signal (LOS) _ASB RRH
Master Link Port Transceiver Failure_ASB RRH
Master Link Remote Alarm Indication(RAI) _ASB RRH
Communication Failure_ASB RRH
Under Temperature_ASB RRH
Warm-up_ASB RRH
Over Temperature-Warning_ASB RRH
Over Temperature-Critical_ASB RRH
Self Test Partial Failure_ASB RRH
Self Test Critical Failure_ASB RRH
Initialization Failure _ASB RRH
Software Failure _ASB RRH
Message Throttling _ASB RRH
Receiver Fail_ASB RRH
Gain Control Warning _ASB RRH
Transmitter Failure _ASB RRH
Gain Control Failure _ASB RRH
RF Output Overdrive _ASB RRH
Receiver 1 Failure_ASB RRH
Receiver 2 Failure _ASB RRH
Diversity Imbalance_ASB RRH
Equipment Failure_ASB RRH
Input Voltage Failure_ASB RRH
Power Converter Failure_ASB RRH
C&M Timer Expired_ASB RRH
Clock Failure_ASB RRH
RF Synthesizer Failure_ASB RRH
Digital Input Overdrive_ASB RRH
Simulate all ASB RRH internal alarms at the same time
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 108/174
STISS V5.5 Test Specification

2423
2424
Test label 87: Slave Link Low Optical Signal Level_ASB RRH
2425
Purpose:
2426
2427
This test is to report alarm when received optical signal on the slave (upstream)
link port is unexpectedly low, though communication is still possible.
2428
2429
2430
2431
2432
Requirement:
2433
Run the OCI tool;
2434
Select the related alarm Slave Link Low Optical Signal Level in the RRH/Procedures,
2435
Click the mode to ON;
2436
Then check the result from RTC and TIL and OMC-B
2437
The below figure is the OCI alarm figure.
TIL connection
OMCB connection
OCI Tool
2438
2439
See the expected alarm from the RTC tool.
2440
No alarm report to TIL
2441
No alarm report to OMCB
2442
Check LED flashing on RRH is Flash Yellow, Flash Green
2443
Check LED display on TIL is Flash Yellow, Flash Green

ASSOCIATED CRPI GENERIC ALARM
Alarm Id
Alarm Type
Alarm Severity
alarm
informantion
LED exptected
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 109/174
1 Slave Link Error
Slave Link Low

Optical Signal
Level
Medium
Flash
Yellow,
Flash Green
2444
2445
Test label 88:Slave Link Loss of Framing (LOF) _ASB RRH
2446
Purpose:
2447
2448
2449
This test is to report alarm when locally-detected slave link port alarm, framing
cannot be recovered at the slave link port. This alarm is enabled only after the
link has first been established.
2450
2451
2452
2453
2454
Requirement:
2455
Run the OCI tool;
2456
Select the related alarm LOF in the RRH/Procedures,
2457
2458
2459
2460
2461
2462
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 110/174

2463
2464
2465

Alarm Id
Alarm Type
Alarm Severity
2 Slave Link Error
Major
alarm
informantion
LED exptected
Slave Link Loss

of Framing
(LOF)
Flash
Yellow,
Flash Green
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 111/174

2466
Test label 89: Slave Link Loss of Signal (LOS) _ASB RRH
2467
Purpose:
2468
2469
2470
This test is to report alarm when locally-detected slave link port alarm, no
signal is detected at the slave link port. This alarm is enabled only after the link
has first been established.
2471
2472
2473
2474
2475
Requirement:
2476
Run the OCI tool;
2477
Select the related alarm LOS in the RRH/Procedures,
2478
2479
2480
TIL connection
OMCB connection
OCI Tool
2481
2482
2483
2484
2485

authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 112/174

2486

Alarm Id
Alarm Type
Alarm Severity
3 Slave Link Error
alarm
informantion
Slave Link Loss

of Signal (LOS)
Major
LED exptected
Flash
Yellow,
Flash Green
2487
2488
Test label 90:Slave Link Port Transceiver Failure_ASB RRH
2489
Purpose:
2490
2491
This test is to report alarm when slave link optical transceiver has failed and
communication to the REC is probably not available
2492
2493
2494
2495
2496
Requirement:
2497
Run the OCI tool;
2498
Select the related alarm Slave Link Port Transceiver Failure in the RRH/Procedures,
2499
2500
2501
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 113/174
2502
2503
2504
2505
2506
Check LED flashing on RRH is RED
2507
Check LED display on TIL is RED

Alarm Id
Alarm Type
Alarm Severity
4 Slave Link Error
alarm
informantion
Slave Link Port

Transceiver
Failur
Major
LED exptected
Red
2508
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 114/174

2509
2510
Test label 91:Slave Link Remote Alarm Indication (RAI) _ASB RRH
Purpose:
2511
2512
This test is to report alarm when one or more of the incoming slave link LOS,
LOF, or RAI bits is set.
2513
2514
2515
2516
2517
Requirement:
2518
Run the OCI tool;
2519
Select the related alarm Slave Link Remote Alarm Indication (RAI) in the RRH/Procedures,
2520
2521
2522
2523
2524
2525
2526
2527
2528

TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 115/174

Alarm Id
Alarm Type
Alarm Severity
6 Slave Link Error
Major
alarm
informantion
LED exptected
Slave Link
RemoteAlarm
Indication (RAI)
Flash
Yellow,
Flash Green
2529
2530
2531
Test label 92: Master Link Low Optical Signal Level_ASB RRH
Purpose:
2532
2533
This test is to report alarm when received optical signal on the slave (upstream)
link port is unexpectedly low, though communication is still possible.
2534
2535
2536
2537
2538
Requirement:
2539
Run the OCI tool;
2540
Select the related alarm Master Link Low Optical Signal Level in the RRH/Procedures,
2541
2542
2543
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 116/174
2544
2545
2546
2547
2548
2549

Alarm Id
Alarm Type
Alarm Severity
9 Master Link Error
Medium
alarm
informantion
LED exptected
Master Link
Low Optical
Signal Level
Flash
Yellow,
Flash Green
2550
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 117/174

2551
2552
Test label 93: Master Link Loss of Framing (LOF) _ASB RRH
Purpose:
2553
2554
2555
This test is to report alarm when locally-detected master link port alarm,
framing cannot be recovered at the master link port. This alarm is enabled only
after the link has first been established.
2556
2557
2558
2559
2560
Requirement:
2561
Run the OCI tool;
2562
Select the related alarm LOF in the RRH/Procedures,
2563
2564
2565
2566
2567
2568
2569
2570
2571

TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 118/174

Alarm Id
Alarm Type
Alarm Severity
10 Master Link Error
alarm
informantion
LED exptected
Master Link
Flash
Loss of Framing Yellow,
(LOF)
Flash Green
Major
2572
2573
Test label 94: Master Link Loss of Signal (LOS) _ASB RRH
2574
Purpose:
2575
2576
2577
This test is to report alarm when locally-detected master link port alarm, no
signal is detected at the master link port. This alarm is enabled only after the
link has first been established.
2578
2579
2580
2581
2582
Requirement:
2583
Run the OCI tool;
2584
Select the related alarm LOS in the RRH/Procedures,
2585
2586
2587
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 119/174
2588
2589
2590
2591
2592
2593

Alarm Id
Alarm Type
Alarm Severity
Major
alarm
informantion
LED exptected
Master Link
Loss of Signal
(LOS)
Flash
Yellow,
Flash Green
2594
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 120/174

2595
Test label 95: Master Link Port Transceiver Failure_ASB RRH
2596
Purpose:
2597
2598
This test is to report alarm when master link optical transceiver has failed and
communication to the REC is probably not available
2599
2600
2601
2602
2603
Requirement:
2604
Run the OCI tool;
2605
Select the related alarm Master Link Port Transceiver Failure in the RRH/Procedures,
2606
2607
2608
2609
2610
2611
2612
2613
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 121/174

2614

Alarm Id
Alarm Type
Alarm Severity
alarm
informantion
Master Link
Port
Transceiver
Failure
Major
LED exptected
Red
2615
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 122/174

2616
Test label 96: Master Link Remote Alarm Indication(RAI) _ASB RRH
2617
Purpose:
2618
2619
This test is to report alarm when one or more of the incoming slave link LOS,
LOF, or RAI bits is set.
2620
2621
2622
2623
2624
Requirement:
2625
Run the OCI tool;
2626
Select the related alarm Master Link Remote Alarm Indication (RAI) in the RRH/Procedures,
2627
2628
2629
TIL connection
OMCB connection
OCI Tool
2630
2631
2632
2633
2634
2635

Alarm Id
Alarm Type
Alarm Severity
alarm
informantion
LED exptected
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 123/174
Master Link
Remote Alarm
Indication (RAI)
Major
Flash
Yellow,
Flash Green
2636
2637
Test label 97: Communication Failure_ASB RRH
2638
Purpose:
2639
2640
This test is to report alarm when there have been no management messages
received in the past 30 seconds, or there is no active C&M TCP connection.
2641
2642
2643
2644
2645
Requirement:
2646
Run the OCI tool;
2647
Select the related alarm Communication Failure in the RRH/Procedures,
2648
2649
2650
TIL connection
OMCB connection
OCI Tool
2651
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 124/174

2652
2653
2654
2655
2656

Alarm Id
17
Alarm Type
Alarm Severity
Communication
Error
Medium
alarm
informantion
Communication
Failure
LED exptected
Flash
Yellow,
Flash Green
2657
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 125/174

2658
Test label 98: Under Temperature_ASB RRH
2659
Purpose:
2660
2661
The RRH is report alarm when below its normal operating temperature but still
capable of transmitting.
2662
2663
2664
2665
2666
Requirement:
2667
Run the OCI tool;
2668
Select the related alarm Under Temperature in the RRH/Procedures,
2669
2670
2671
2672
2673
2674
2675
2676
Check LED flashing on RRH is Green, Flash RED
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 126/174

2677
Check LED display on TIL is Green, Flash RED

Alarm Id
18
Alarm Type
Alarm Severity
Temperature
Alarm
Medium
alarm
informantion
LED exptected
Under
Temperature
Green,Flash
Red
2678
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 127/174

2679
Test label 99: Warm-up_ASB RRH
2680
Purpose:
2681
2682
The RRH is report alarm when below its normal operating temperature but still
capable of transmitting.
2683
2684
2685
2686
2687
Requirement:
2688
Run the OCI tool;
2689
Select the related alarm Warm-Up in the RRH/Procedures,
2690
2691
2692
2693
2694
2695
2696
2697
Check LED flashing on RRH is Flash RED
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 128/174

2698
Check LED display on TIL is Flash RED
2699
Alarm Id
19
Alarm Type
Alarm Severity
alarm
informantion
LED exptected
Temperature
Alarm
Major
Warm-up
Flash Red
2700
2701
Test label 100: Over Temperature-Warning_ASB RRH
2702
Purpose:
2703
2704
The RRH is report alarm when RRH temperature is rising near the shutdown
limit.
2705
2706
2707
2708
2709
Requirement:
2710
Run the OCI tool;
2711
Select the related alarm Over Temperature-Warning in the RRH/Procedures,
2712
2713
2714
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 129/174
2715
2716
2717
See the expected alarm from the TIL tool.
2718
See the expected alarm from the OMC-B.
2719
Check LED flashing on RRH is Green,Flash Red
2720
Check LED display on TIL is Green,Flash Red

Alarm Id
20
Alarm Type
Alarm Severity
alarm informantion
LED
exptected
Temperature
Alarm
Medium
Over
Green,Flash
Temperature-Warning Red
2721
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 130/174

2722
Test label 101: Over Temperature-Critical_ASB RRH
2723
Purpose:
2724
2725
The RRH is report alarm when the RRH temperature is above operating range,
and the transmitter has shut down to attempt to reduce the temperature.
2726
2727
2728
2729
2730
Requirement:
2731
Run the OCI tool;
2732
Select the related alarm Over Temperature-Critical in the RRH/Procedures,
2733
2734
2735
2736
2737
2738
See the expected alarm from the TIL tool
2739
See the expected alarm from the OMC-B
2740
Check LED flashing on RRH is Flash Red
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 131/174

2741
Check LED display on TIL is Flash Red

Alarm Id
21
Alarm Type
Alarm Severity
alarm informantion
LED
exptected
Temperature
Alarm
Major
Over
Flash Red
Temperature-Critical
2742
2743
Test label 102: Self Test Partial Failure_ASB RRH
2744
Purpose:
2745
2746
The RRH is report alarm when at least one failure was detected during power
on self test, but the unit may still be functional, though in a degraded state.
2747
2748
2749
2750
2751
Requirement:
2752
Run the OCI tool;
2753
Select the related alarm Self Test Partial Failure in the RRH/Procedures,
2754
2755
2756
TIL connection
OMCB connection
OCI Tool
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 132/174
2757
2758
2759
2760
2761
Check LED flashing on RRH is Green, RED
2762
Check LED display on TIL is Green, RED

Alarm Id
Alarm Type
Alarm Severity
24 Self Test Failure
alarm
informantion
Self Test Partial

Failure
Medium
LED exptected
Red,Green
2763
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 133/174

2764
Test label 103: Self Test Critical Failure_ASB RRH
2765
Purpose:
2766
2767
2768
The RRH is report alarm when the power-on self test detected a critical failure
that prevents the RRH from transmitting. The RRH must be reset to unlatch
this alarm.
2769
2770
2771
2772
2773
Requirement:
2774
Run the OCI tool;
2775
Select the related alarm Self Test Critical Failure in the RRH/Procedures,
2776
2777
2778
TIL connection
OMCB connection
OCI Tool
2779
2780
2781
2782
2783

authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 134/174

2784

Alarm Id
Alarm Type
Alarm Severity
25 Self Test Failure
alarm
informantion
Self Test
Critical Failure
Major
LED exptected
Red
2785
2786
Test label 104: Initialization Failure _ASB RRH
2787
Purpose:
2788
2789
2790
The RRH is report alarm when FPGA download failures, or PLLs are not
locked. Note that this is evaluated during initialization and the unit is never
enabled. The RRH must be reset to unlatch this alarm.
2791
2792
2793
2794
2795
Requirement:
2796
Run the OCI tool;
2797
Select the related alarm Initialization Failure in the RRH/Procedures,
2798
2799
2800
TIL connection
OMCB connection
OCI Tool
2801
2802

authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 135/174

2803
2804
See the expected alarm from the OMCB tool
2805
2806

Alarm Id
Alarm Type
26 PLL Failure
Alarm Severity
alarm
informantion
Initialization
Failure
Major
LED exptected
Red
2807
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 136/174

2808
Test label 105: Software Failure _ASB RRH
2809
Purpose:
2810
2811
2812
The RRH is report alarm when Indicates general software failures, including
TCP/IP stack errors or TCP/IP Allocate Packet errors.This alarm remains
asserted for a minimum of 30 seconds.
2813
2814
2815
2816
2817
Requirement:
2. TIL connection
3. OMCB connection
4. OCI Tool
2818
5. Run the OCI tool;
2819
6. Select the related alarm Software Failure in the RRH/Procedures,
2820
7. Click the mode to ON;
2821
8. Then check the result from RTC and TIL and OMC-B
2822
2823
2824
2825
2826
2827
Check LED flashing on RRH is Green,Flash RED
2828
Check LED display on TIL is Green,Flash RED

authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 137/174

Alarm Id
Alarm Type
Alarm Severity
27 Software Failure
Minor
alarm
informantion
LED exptected
Software
Failure
Green,Flash
Red
2829
authorization
UMT/BTS/DJD/024788
V01.01/EN
Standard
04/12/2014
Page 138/174

2830
Test label 106: Message Throttling _ASB RRH
2831
Purpose:
2832
The RRH is report alarm when the number of EVENT messages exceeds threshold.
2833
2834
2835
2836
2837
Requirement:
2838
Run the OCI tool;
2839
Select the related alarm Message Throttling in the RRH/Procedures,
2840
2841
2842
TIL connection
OMCB connection
OCI Tool
2843
2844
2845
2846
2847
Check LED flashing on RRH is Green,Flash RED
2848
Check LED display on TIL is Green,Flash RED

Alarm Id
Alarm Type
Alarm Severity
alarm
informantion
LED exptected
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 139/174
28
Communication
Error
Message
Throttling
Minor
Green,Flash
Red
2849
2850
Test label 107: Receiver Fail_ASB RRH
2851
Purpose:
2852
2853
The RRH is report alarm when any error is dectected on the Radio Receiver
side(channelizer,synthetiser..)
2854
2855
2856
2857
2858
Requirement:
2859
Run the OCI tool;
2860
Select the related alarm Receiver Fail in the RRH/Procedures,
2861
2862
2863
TIL connection
OMCB connection
OCI Tool
2864
2865
2866
2867
2868

UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 140/174

2869

Alarm Id
Alarm Type
31 Rx Path Failure
Alarm Severity
alarm
informantion
LED exptected
Major
Receiver Fail
Red
2870
2871
Test label 108: Gain Control Warning _ASB RRH
2872
Purpose:
2873
The RRH is report alarm of Gain control error
2874
2875
2876
2877
2878
Requirement:
2879
Run the OCI tool;
2880
Select the related alarm Gain Control Warning in the RRH/Procedures,
2881
2882
2883
2884
2885
2886
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 141/174

2887
2888
Check LED flashing on RRH is Flash Green,Flash RED
2889
Check LED display on TIL is Flash Green,Flash RED

Alarm Id
32
Alarm Type
Alarm Severity
Gain Control
Alarm
Medium
alarm
informantion
Gain Control
Warning
LED exptected
Flash
Red,Flash
Green
2890
2891
Test label 109: Transmitter Failure _ASB RRH
2892
Purpose:
2893
The RRH is report alarm when any error is dectected on the Radio Transmitter side
2894
2895
2896
2897
2898
Requirement:
2899
Run the OCI tool;
2900
Select the related alarm Transmitter Fail in the RRH/Procedures,
2901
2902
2903
TIL connection
OMCB connection
OCI Tool
2904
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 142/174

2905
2906
2907
2908
2909

Alarm Id
Alarm Type
Alarm Severity
33 Tx Path Failure
alarm
informantion
Transmitter
Failure
Major
2910
2911
Test label 110: Gain Control Failure _ASB RRH
2912
Purpose:
2913
The RRH is report alarm of Gain control error
2914
2915
2916
2917
2918
Requirement:
2919
Run the OCI tool;
2920
Select the related alarm Gain Control Failure in the RRH/Procedures,
2921
2922
2923
LED exptected
Red
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 143/174
2924
2925
2926
2927
2928
2929
2930
Alarm Id
34
Alarm Type
Alarm Severity
Gain Control
Alarm
Major
alarm
informantion
Gain Control
Failure
2931
2932
Test label 111: RF Output Overdrive _ASB RRH
2933
Purpose:
2934
The RRH is report alarm of RF output overdrive
2935
2936
2937
2938
2939
Requirement:
2940
Run the OCI tool;
LED exptected
Red
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 144/174

2941
Select the related alarm RF Output Overdrive in the RRH/Procedures,
2942
2943
2944
2945
2946
2947
2948
2949
2950

Alarm Id
Alarm Type
Alarm Severity
35 RF Signal Alarm
alarm
informantion
RF Output
Overdrive
Major
2951
2952
Test label 112: Receiver 1 Failure_ASB RRH
2953
Purpose:
2954
The RRH is report alarm of Receiver 1 failure
LED exptected
Flash Red
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 145/174

2955
2956
2957
2958
2959
Requirement:
2960
Run the OCI tool;
2961
Select the related alarm Receiver 1 Failure in the RRH/Procedures,
2962
2963
2964
TIL connection
OMCB connection
OCI Tool
2965
2966
2967
2968
2969
2970
2971
Alarm Id
Alarm Type
Alarm Severity
36 Rx Path Failure
alarm
informantion
Receiver 1
Failure
Medium
LED exptected
Red,Green
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 146/174

2972
2973
Test label 113: Receiver 2 Failure _ASB RRH
2974
Purpose:
2975
The RRH is report alarm of Receiver 2 failure
2976
2977
2978
2979
2980
Requirement:
2981
Run the OCI tool;
2982
Select the related alarm Receiver 2 Failure in the RRH/Procedures,
2983
2984
2985
2986
2987
2988
2989
2990
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 147/174

2991

Alarm Id
Alarm Type
Alarm Severity
37 Rx Path Failure
alarm
informantion
Receiver 2
Failure
Medium
2992
2993
Test label 114: Diversity Imbalance_ASB RRH
2994
Purpose:
2995
The RRH is report alarm of low rssi
2996
2997
2998
2999
3000
Requirement:
3001
Run the OCI tool;
3002
Select the related alarm Diversity Imbalance in the RRH/Procedures,
3003
3004
3005
LED exptected
Red,Green
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 148/174
3006
3007
3008
3009
3010
Check LED flashing on RRH is Flash RED,Flash Green
3011
Check LED display on TIL is Flash RED,Flash Green
3012
Alarm Id
Alarm Type
38 Low rssi
Alarm Severity
alarm
informantion
Diversity
Imbalance
Minor
3013
3014
Test label 115: Equipment Failure_ASB RRH
3015
Purpose:
3016
The RRH is report alarm of equipment failure
3017
3018
3019
Requirement:
LED exptected
Flash
Red,Flash
Green
TIL connection
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 149/174

3020
3021
OMCB connection
OCI Tool
3022
Run the OCI tool;
3023
Select the related alarm equipment failure in the RRH/Procedures,
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
Alarm Id
Alarm Type
Alarm Severity
40 Hareware Failure
alarm
informantion
Equipment
Failure
Major
LED exptected
Red
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 150/174

3034
3035
Test label 116: Input Voltage Failure_ASB RRH
3036
Purpose:
3037
The RRH is report alarm of Input Voltage Failure
3038
3039
3040
3041
3042
Requirement:
3043
Run the OCI tool;
3044
Select the related alarm Input Voltage Failure in the RRH/Procedures,
3045
3046
3047
3048
3049
3050
3051
3052
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 151/174

3053

Alarm Id
Alarm Type
Alarm Severity
41 DC Voltage Alarm
alarm
informantion
Input Voltage
Failure
Major
3054
3055
Test label 117: Power Converter Failure_ASB RRH
3056
Purpose:
3057
The RRH is report alarm of Power Converter Failure
3058
3059
3060
3061
3062
Requirement:
3063
Run the OCI tool;
3064
Select the related alarm Power Converter Failure in the RRH/Procedures,
3065
3066
3067
LED exptected
Flash Red
TIL connection
OMCB connection
OCI Tool
3068
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 152/174

3069
3070
3071
3072
3073

Alarm Id
Alarm Type
Alarm Severity
42 DC Voltage Alarm
alarm
informantion
Power
Converter
Failure
Major
3074
3075
Test label 118: C&M Timer Expired_ASB RRH
3076
Purpose:
3077
The RRH is report alarm of C&M Timer Expired
3078
3079
3080
3081
3082
Requirement:
3083
Run the OCI tool;
3084
Select the related alarm C&M Timer Expired in the RRH/Procedures,
3085
3086
3087
LED exptected
Red
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 153/174
3088
3089
3090
3091
3092
3093

Alarm Id
Alarm Type
Alarm Severity
44 Software Failure
C&M Timer
Expired
Major
3094
3095
Test label 119: Clock Failure_ASB RRH
3096
Purpose:
3097
The RRH is report alarm of Clock Failure
3098
3099
3100
3101
3102
Requirement:
3103
Run the OCI tool;
alarm
informantion
LED exptected
Red
TIL connection
OMCB connection
OCI Tool
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 154/174

3104
Select the related alarm Clock Failure in the RRH/Procedures,
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
Alarm Id
Alarm Type
47 PLL Failure
Alarm Severity
alarm
informantion
LED exptected
Major
Clock Failure
Flash Red
3115
3116
Test label 120: RF Synthesizer Failure_ASB RRH
3117
Purpose:
3118
The RRH is report alarm of RF Synthesizer Failure

UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 155/174

3119
3120
3121
3122
3123
Requirement:
3124
Run the OCI tool;
3125
Select the related alarm RF Synthesizer Failure in the RRH/Procedures,
3126
3127
3128
TIL connection
OMCB connection
OCI Tool
3129
3130
3131
3132
3133
3134

Alarm Id
Alarm Type
48 PLL Failure
Alarm Severity
alarm
informantion
RF Synthesizer
Failure
Major
LED exptected
Flash Red
3135
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 156/174

3136
Test label 121: Digital Input Overdrive_ASB RRH
3137
Purpose:
3138
The RRH is report alarm of Digital Input Overdrive
3139
3140
3141
3142
3143
Requirement:
3144
Run the OCI tool;
3145
Select the related alarm Digital Input Overdrive in the RRH/Procedures,
3146
3147
3148
3149
3150
3151
3152
3153
3154
TIL connection
OMCB connection
OCI Tool
3155
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 157/174

Alarm Id
Alarm Type
Alarm Severity
49 Hareware Failure
alarm
informantion
Digital Input
Overdrive
Medium
LED exptected
Flash Red
3156
3157
Test label 122: Simulate all ASB RRH internal alarms at the same time
3158
Purpose:
3159
3160
Check Rack2u could process and report alarms normally without error when all RRH internal alarms
report at the same time
3161
3162
3163
3164
3165
Requirement:
3166
Run the OCI tool;
3167
Select the all alarms(around 30 alarms) in the RRH/Procedures,
3168
3169
3170
3171
Rack2u could process and report alarms normally without error and reset
3172
4.1.8.6.
3173
3174
Test label 123: Unbalanced-RF-Power_STSR2
3175
3176
Check unbalanced RF power per carrier allocation is supported in STSR2 configuration

Requirement:
3177
1. The NodeB is connected to the lamp and configured
3178
3179
2. Rack2u is in STSR2 configuration

Procedure:
3180
3181
Step1:Configure PaRatio parameters per cell(same sector) from 50%-50% to 20%-80%, check Result
1
3182
Step2: Lamp, cellset, fachset, rlset per carrier, check Result 2
3183
3184
Step3: Configure PaRatio Parameters per cell to 19%-81%, check Result 3.

Expectable results:
3185
3186
Result1: D2U should startup successfully, the new paratio parameters should be taken into consider
after rack2u is up
3187
Result2: Cellset, fachset, rlset per carrier should be successful, call could be made successfully
3188
3189
3190
Result3: Alarm should be raised for the unavailable configuration.
TIL connection
OMCB connection
OCI Tool
UNBLANCE RF POWER TEST
Purpose:
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 158/174

3191
3192
4.1.8.7.
AC POWER TEST
3193
3194
Test label 124: AC_Power_Voltage_Out_Of_Range
3195
3196
Check RRH behavior while the AC power is abnormal.

Requirement:
3197
1. Platform configuration applicable
3198
3199
Procedure:
3200
Step1: Power up RRH with AC power
3201
Step2: Set AC voltage to 170V, check Result 1
3202
3203
3204
3205

Expectable results:
3206
3207
Result1: RRH shutdown automatically

Result2: RRH re-start automatically
3208
4.1.8.8.
3209
3210
Test label 125: Power_Consumption_Without_ALD
3211
3212
3213
Typical power consumption shall be less than as shown in the table below. Percentages are different
RF output levels relative to the max 60W. No more than 8% is allowed for the AC version than DC
version.
Purpose:
POWER CONSUMPTION TEST
Purpose:
Percentage
DC Power Consumption
AC Power Consumption
20%(12W)
135W
145.8W
50%(30W)
185W
199.8W
100%(60W)
Requirement:
260W
280.8W
3214
3215
3216
3217
2. Lamp is connected to NodeB

Procedure:
3218
Step1: Configure platform with DC power, STSR1, max power 60W
3219
Step2: Setup cell and radiolinks to make RF output reach 20%(12W), check Result 1
3220
Step3: Setup cell and radiolinks to make RF output reach 50%(30W), check Result 2
3221
Step4: Make RF full output 100% with UDT scripts, check Result 3
3222
3223
Step5: Configure platform with AC power, STSR1, max power 60W, repeat step 2~step 4
Expectable results:
3224
Result1: RRH power consumption should be no more than Row 2 in the table.
3225
3226
3227
3228
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 159/174

3229
3230
Test label 126: Power_Consumption_With_ALD
3231
3232
Check the maxium DC power consumption including ALDs connected.

Requirement:
3233
3234
2. Lamp is connected to NodeB
3235
3236
3. ALDs(RET+TMA) are connected to RRH.

Procedure:
3237
Step1: Configure platform with DC power, STSR4, max power 15W for each carrier.
3238
3239
3240
Step2: Make RF full output 100% with UDT scripts, check Result 1
Expectable results:
Result1: RRH power consumption should be no more than 300W.
3241
4.1.9.
Purpose:
AISG FULL
3242
Test label 127: AISG_OMCB_aisgScan_With_RET
3243
Purpose:
3244
3245
Check AISG scan information is correct when doing OMC-B aisgScan.

Requirement:
3246
1, Platform is available
3247
2, RET is available
3248
3, TIL is connected
3249
4, OMC-B is connected
3250
Procedure:
3251
Step1: NodeB startup with RET connected to RRH, check Result1.
3252
Step2: open OMC-B and do bus scan, check Result2.
3253
Result:
3254
Result1: NodeB startup successfully.
3255
3256
Result2: RET can be scanned and the information is correct.(check the info is
consistent to TIL)
3257
3258
Test label 128: AISG_OMCB_aisgScan_With_TMA
3259
Purpose:
3260
3261
Check AISG scan information is correct when doing OMC-B aisgScan.

Requirement:
3262
3263
2, TMA is available
3264
3, TIL is connected
3265
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 160/174

Procedure:
3266
3267
Step1: NodeB startup with TMA connected to RRH, check Result1.
3268
Step2: open OMC-B and do bus scan, check Result2.

Result:
3269
3270
3271
3272
Result2: TMA can be scanned and the information is correct (check the info is
consistent to TIL).
3273
3274
3275
4.1.9.1.
RESET
3276
Test label 129: AISG_OMCB_aisgDeviceReset
3277
Purpose:
Check device can be reset by OMC-B successfully. (aisgDeviceReset?)
3278
Requirement:
3279
3280
3281
2, RET and TMA are available
3282
3, TIL is connected
3283
Procedure:
3284
Step1: Reset Aisg including TMA and RET device from OMCB.
3285
Result:
3286
Result1: Aisg devices reset successfully and power on normally.
3287
3288
3289
4.1.9.2.
DEVICE DATA
3290
Test label 130: AISG_TIL_Set_One_DeviceData_For_RET
3291
Purpose:
3292
3293
Check device data for RET can be set successfully.

Requirement:
3294
3295
2, RET is available
3296
3, TIL is connected
3297
Procedure:
3298
3299
Step2: open TIL and set device data for RET, check Result2.
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 161/174

Result:
3300
3301
3302
Result2: device data for RET can be set successfully.
3303
3304
Test label 131: AISG_TIL_Set_One_DeviceData_For_TMA
3305
Purpose:
Check device data for TMA can be set successfully.
3306
Requirement:
3307
3308
3309
2, TMA is available
3310
3, TIL is connected
Procedure:
3311
3312
Step1: NodeB startup with TMA connected to RRH, check Result1.
3313
Step2: open TIL and set device data for TMA, check Result2.
Result:
3314
3315
3316
Result2: device data for TMA can be set successfully.
3317
3318
4.1.9.3.
UPLOAD
3319
Test label 132: AISG_TIL_Upload_Configure_File_To_RRH
3320
Purpose:
3321
3322
Check the configure file upload to the RRH from TIL would be supported.
Requirement:
3323
3324
3325
3, TIL is connected
3326
3327
Procedure:
3328
Step1: NodeB startup with RET and TMA connected to RRH, check Result1.
3329
Step2: open TIL and trigger configure file upload.
3330
3331
Step3: fill the username, password, file needs to be uploaded, as well as the remote
directory, select upload, check Result2.
3332
Step4: get RET and TMA info from TIL, check Result3.
3333
Step5: get RET and TMA info from OMC-B, check Result4.
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 162/174

Result:
3334
3335
3336
Result2: configure file can be uploaded successfully.
3337
3338
Result3: the info got form TIL is consistent with the configure file which has been
uploaded.
3339
3340
Result4: the info got form OMC-B is consistent with the configure file which has been
uploaded.
3341
3342
4.1.9.4.
TILT
3343
Test label 133: AISG_TIL_Set_Tilt
3344
Purpose:
3345
3346
Verify the tilt can be set by TIL.

Requirement:
3347
3348
2, RET is available
3349
3, TIL is connected
3350
3351
Procedure:
3352
Step1: NodeB startup with RET connected to RRH.
3353
3354
Step2: open TIL, double click RRH, right click and select AISG -> Set Tilt, set the
value beyond the range, check Result1.
3355
Step3: redo step2 to set tilt in the range, check Result2.
3356
Step4: open OMC-B to get Tilt, check Result3.
3357
Result:
3358
Result1: it is failed to set tilt and some alarm will be reported.
3359
Result2: it is successful to set tilt.
3360
Result3: The Tilt value is consistent with the value which has been set in TIL.
3361
3362
Test label 134: AISG_TIL_Calibrate_Tilt
3363
Purpose:
3364
3365
Verify the tilt can be calibrated correctly by TIL.

Requirement:
3366
3367
2, RET is available
3368
3, TIL is connected
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 163/174

3369
3370
Procedure:
3371
3372
3373
Step2: open TIL, double click RRH, right click and select AISG -> Calibrate Tilt,
check Result1.
3374
Step3: open OMC-B and get AISG Tilt, check Result2.
3375
Result:
3376
Result1: Tilt can be calibrated correctly.
3377
Result2: The Tilt value is consistent with the value which has been calibrated in TIL.
3378
3379
Test label 135: AISG_OMCB_aisgTILT
3380
Purpose:
3381
3382
Check aisgTilt by OMC-B.

Requirement:
3383
3384
2, RET is available
3385
3386
Procedure:
3387
3388
Step2: get Tilt from OCM-B, check Result1.
3389
3390
Result:
Result1: Tilt value can be got correctly.
3391
3392
Test label 136: AISG_OMCB_aisgSetTILT
3393
Purpose:
3394
3395
Check AISG TILT can be set by OMCB successfully.

Requirement:
3396
3397
2, RET is available
3398
3399
Procedure:
3400
3401
Step2: open OMC-B and set AISG Tilt, check Result1.
3402
Step3: get Tilt from OMC-B, check Result2.
3403
Result:
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 164/174

3404
Result1: Tile can be set successfully.
3405
Result2: the Tilt value get from OMC-B is correct.
3406
3407
Test label 137: AISG_OMCB_aisgDeviceCalibrate
3408
Purpose:
Check Tilt can be calibrated by OMC-B correctly.
3409
Requirement:
3410
3411
3412
2, RET is available
3413
3, TIL is connected
3414
Procedure:
3415
3416
3417
Step2: open OMC-B and calibrate Tilt, check Result2.
3418
Step3: get Tilt from OMC-B, check Result3.

Result:
3419
3420
3421
Result2: Tilt can be calibrated successfully.
3422
Result3: The Tilt value is consistent with the value which has been calibrated.
3423
3424
4.1.9.5.
TMA
3425
Test label 138: AISG_TIL_Set_TMA_Gain
3426
Purpose:
3427
3428
Verify the TMA mode and gain can be set by TIL.

Requirement:
3429
3430
2, TMA is available
3431
3, TIL is connected
3432
3433
Procedure:
3434
Step1: NodeB startup with TMA connected to RRH.
3435
3436
Step2: open TIL, double click RRH, right click and select AISG -> Get/Set TMA Gain,
select Reload to set the TMA parameters, check Result1.
3437
Step3: open OMC-B and get TMA gain, check Result2.

UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 165/174

3438
3439
Step4: redo step2~3 if more than one TMA exist.

Result:
3440
Result1: TMA gain can be set correctly.
3441
Result2: The TMA gain got form OMC-B is consistent with the value set in TIL.
3442
3443
Test label 139: AISG_OMCB_aisgSetTMAGain
3444
Purpose:
3445
3446
Check TMA gain can be set successfully by OMC-B.

Requirement:
3447
3448
2, TMA is available
3449
3, TIL is connected
3450
3451
Procedure:
3452
3453
Step2: open OMC-B and set TMA gain, check Result1.
3454
Step3: open TIL and get TMA gain, check Result2.
3455
Result:
3456
Result1: TMA gain can be set correctly.
3457
Result2: The TMA gain got form TIL is consistent with the value set in OMC-B.
3458
3459
Test label 140: AISG_OMCB_aisgSetTMAMode
3460
Purpose:
3461
3462
Check TMA mode can be set successfully by OMC-B.

Requirement:
3463
3464
3465
3, TIL is connected
3466
3467
Procedure:
3468
3469
Step2: open OMC-B and set TMA mode, check Result1.
3470
Step3: get TMA mode from OMC-B, check Result2.
3471
Result:
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 166/174

3472
Result1: TMA mode can be set correctly.
3473
Result2: the TMA mode got from OMC-B is the value which has been set.
3474
3475
4.1.9.6.
ABNORMAL CASES
3476
Test label 141: AISG_ALD_Hot_Plugout
3477
Purpose:
3478
3479
Check ALD info does not change after hot plug out before scan.
Requirement:
3480
3481
2, ALD are available
3482
3, TIL is connected
3483
3484
Procedure:
3485
Step1: NodeB startup with ALD connected to RRH.
3486
Step2: hot plug out ALD.
3487
Step3: open TIL/OMC-B, get inventory/device data/Tilt info/TMA info, check Result1.
3488
Step4: open TIL/OMC-B, set Tilt/TMA info, check Result2.
3489
3490
Step5: open TIL, double click RRH, right click and select AISG -> Scan bus, check
Result3.
3491
3492
3493
Result:
3494
Result1: the info for the ALD which has been plugged out still exists.
3495
Result2: error will be reported.
3496
Result3: scan info is correct and no info for the ALD which has been plugged out.
3497
Result4: no info for the ALD which has been plugged out.
3498
Result5: Tilt/TMA info can be set successfully.
3499
3500
Test label 142: AISG_ALD_Hot_Plugin
3501
Purpose:
3502
3503
Check ALD info does not change after hot plug in before scan.
Requirement:
3504
3505
2, ALD are available

UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 167/174

3506
3, TIL is connected
3507
Procedure:
3508
3509
Step1: NodeB startup with ALD connected to RRH.
3510
Step2: hot plug in ALD.
3511
3512
3513
3514
Step5: open TIL, double click RRH, right click and select AISG -> Scan bus, check
Result3.
3515
3516

Result:
3517
3518
Result1: no info for the ALD which has been plugged in.
3519
Result2: error will be reported.
3520
Result3: scan info includes the info for the ALD which has been plugged in.
3521
Result4: the info for the ALD which has been plugged in is correct.
3522
Result5: Tilt/TMA info can be set successfully.
3523
3524
3525
3526
4.2
PowerSaving Feature
3527
4.2.1
Setup/Delete One Cell On 21C RRH With ASB PA Vendor
3528
3529
3530
3531
3532
3533
3534
Test Label: 143 SETUP/DELETE ONE CELL ON 21C RRH WITH ASB PA VENDOR
Purpose:
Checking setup/delete one cell with different power on 21C RRH with ASB PA Vendor.
Requirement:
Platform: 2UV2/3 rack + x/eCCM-U + x/eCEM-U
Lamp and omcb connection
3535
3536
3537
3538
Procedure:
Configure cell parameter as below:
3539
In DLU file: paRatio=100 maxRrhPowerAmplification=fullMode
3540
3541
3542
In
Lamp
file:
configure
MAXDLPOWER
(unit=0.1dBm)
as
300(1W)/369(5W)/400(10W)/417(15W)/430(20W)/444(28W)/447(30W)/454(35W)/460(
40W)/465(45W)/469(50W)/471(52W)/477(60W) respectively.
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 168/174

3543
1. Setup the cell and make a R99 call on this cell. Check result 1.
3544
2. Delete the cell.check result 2.
3545
3546
3547
Result:
1. Cell is setup successfully and the call is normal. Check output power through PSA, it
is the same value as configured above.
2. Cell is delete and no power output anymore.
3548
3549
3550
4.2.2
Setup/Delete Two Cells On 21C RRH With ASB PA Vendor
3551
3552
3553
3554
3555
3556
3557
Test Label: 144 SETUP/DELETE TWO CELLS ON 21C RRH WITH ASB PA VENDOR
Purpose:
Checking setup/delete two cells with different power on 21C RRH with ASB PA vendor.
Requirement:
3558
3559
3560
Procedure:
3561
3562
3563
In Lamp file: For 2 cell, configure (cell1, cell2) MAXDLPOWER (unit=0.1dBm) as (300,
400)/(400, 400)/(417, 430)/(430, 430)/(447, 447) respectively.
3564
3565
1. Setup the cell and make a R99 call on cell1.
3566
2. Delete the cell2.check result 2.
3567
3. Make R99 call on cell1. Check result 3.
3568
4. Delete cell1. Check result 4.
3569
3570
3571
3572
Check result 1.
Result:
3573
2. Cell2 is deleted and cell1 is normal.
3574
3. Call on cell1 is normal.Check output power, it is same as cell1 configured.
3575
4. No cell exists and no power output.
3576
3577
3578
3579
3580
4.2.3
Setup/Delete Three Cells on 21C RRH With ASB PA Vendor
Test Label: 145 SETUP/DELETE THREE CELLS ON 21C RRH WITH ASB PA VENDOR
Purpose:
Checking setup/delete three cells with different power on 21C RRH with ASB PA vendor.
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 169/174

3581
3582
3583
3584
3585
3586
Requirement:
Procedure:
3587
3588
3589
In Lamp file: For 3 cell, configure (cell1, cell2, cell3) MAXDLPOWER (unit=0.1dBm) as
(300, 400, 400)/(400,400,400)/(417, 430, 430)/(430, 430,430) respectively.
3590
1. Setup the cell and make a R99 call on cell1. Check result 1.
3591
2. Delete the cell2/cell3.check result 2.
3592
3. Make R99 call on cell1.check result 3.
3593
3594
3595
3596
Result:
3597
2. Cell2/cell3 is deleted and cell1 is normal.
3598
3599
3600
3601
4.2.4
Setup/Delete Four Cells on 21C RRH With ASB PA Vendor
3602
3603
3604
3605
3606
3607
3608
3609
Test Label: 146 SETUP/DELETE THREE CELLS ON 21C RRH WITH ASB PA VENDOR
3610
3611
3612
Procedure:
Purpose:
Checking setup/delete four cells with different power on 21C RRH with ASB PA vendor.
Requirement:
3613
3614
3615
3616
3617
In Lamp file: For 4 cell, configure (cell1, cell2, cell3, cell4) MAXDLPOWER
(unit=0.1dBm)
as
(300,400,400,400)/(400,400,400,400)/(418,430,430,418)/(439,430,439,430)
respectively.
3618
3619
2. Delete the cell2/cell3/cell4.check result 2.

UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 170/174

3620
3621
3622
3623
3624
Result:
3625
2. Cell2/cell3/cell4 is deleted and cell1 is normal.
3626
3627
3628
3629
3630
4.2.5
Setup/Delete One Cell On 21C RRH With Gewei PA Vendor
3631
3632
3633
3634
3635
3636
3637
Test Label: 143 SETUP/DELETE ONE CELL ON 21C RRH WITH GEWEI PA VENDOR
Purpose:
Checking setup/delete one cell with different power on 21C RRH with Gewei PA Vendor.
Requirement:
3638
3639
3640
3641
Procedure:
3642
3643
3644
3645
In
Lamp
file:
configure
MAXDLPOWER
(unit=0.1dBm)
as
300(1W)/369(5W)/400(10W)/417(15W)/430(20W)/444(28W)/447(30W)/454(35W)/460(
40W)/465(45W)/469(50W)/471(52W)/477(60W) respectively.
3646
1. Setup the cell and make a R99 call on this cell. Check result 1.
3647
2. Delete the cell.check result 2.
3648
3649
3650
Result:
2. Cell is delete and no power output anymore.
3651
3652
3653
4.2.6
Setup/Delete Two Cells On 21C RRH With Gewei PA Vendor
3654
3655
3656
3657
3658
Test Label: 144 SETUP/DELETE TWO CELLS ON 21C RRH WITH GEWEI PA VENDOR
Purpose:
Checking setup/delete two cells with different power on 21C RRH with Gewei PA vendor.
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 171/174

3659
3660
Requirement:
3661
3662
3663
Procedure:
3664
3665
3666
In Lamp file: For 2 cell, configure (cell1, cell2) MAXDLPOWER (unit=0.1dBm) as (300,
400)/(400, 400)/(417, 430)/(430, 430)/(447, 447) respectively.
3667
3668
1. Setup the cell and make a R99 call on cell1.
3669
2. Delete the cell2.check result 2.
3670
3. Make R99 call on cell1. Check result 3.
3671
3672
3673
3674
3675
Check result 1.
Result:
3676
2. Cell2 is deleted and cell1 is normal.
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
4.2.7
Setup/Delete Three Cells on 21C RRH With Gewei PA Vendor
Test Label: 145 SETUP/DELETE THREE CELLS ON 21C RRH WITH GEWEI PA VENDOR
Purpose:
Checking setup/delete three cells with different power on 21C RRH with Gewei PA vendor.
Requirement:
Procedure:
3690
3691
3692
In Lamp file: For 3 cell, configure (cell1, cell2, cell3) MAXDLPOWER (unit=0.1dBm) as
(300, 400, 400)/(400,400,400)/(417, 430, 430)/(430, 430,430) respectively.
3693
3694
2. Delete the cell2/cell3.check result 2.
3695
3696

UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 172/174

3697
3698
3699
Result:
3700
2. Cell2/cell3 is deleted and cell1 is normal.
3701
3702
3703
3704
4.2.8
Setup/Delete Four Cells on 21C RRH With Gewei PA Vendor
3705
3706
3707
3708
3709
3710
3711
3712
Test Label: 146 SETUP/DELETE THREE CELLS ON 21C RRH WITH GEWEI PA VENDOR
3713
3714
3715
Procedure:
Purpose:
Checking setup/delete four cells with different power on 21C RRH with Gewei PA vendor.
Requirement:
3716
3717
3718
3719
3720
In Lamp file: For 4 cell, configure (cell1, cell2, cell3, cell4) MAXDLPOWER
(unit=0.1dBm)
as
(300,400,400,400)/(400,400,400,400)/(418,430,430,418)/(439,430,439,430)
respectively.
3721
3722
2. Delete the cell2/cell3/cell4.check result 2.
3723
3724
3725
3726
3727
Result:
3728
2. Cell2/cell3/cell4 is deleted and cell1 is normal.
3729
3730
3731
3732
3733
3734
UMT/BTS/DJD/044741
V01.01/EN
Standard
04/12/2014
Page 173/174
STISS ASB RRH2X60W PowerSavingFRS131825
3735
5. TEST CROSS REFERENCE
3736
6. ABBREVIATIONS
3737
ATM
Asynchronous Transfer Mode
3738
AWS
Advanced Wireless Spectrum
3739
BTS
Base Transceiver Station
3740
CCM
Core Controller Module
3741
CEM
Channel Element Module
3742
CPRI
Common public Radio Interface
3743
CTCH
Common Traffic Channel
3744
DCH
Dedicated Channel
3745
FACH
Forward Access Channel
3746
GUI
Graphical User Interface
3747
HSDPA
High Speed Downlink Packet Access
3748
HSUPA
High Speed Uplink Packet Access
3749
NBAP
Node B Application Part
3750
NodeB
Base Transceiver Station
3751
OAM
Operation and Maintenance
3752
OMC-B
Operations and Management Console for Node B
3753
PCH
Paging Channel
3754
PCM
Pulse Code Modulation
3755
RF
Radio Frequency
3756
RNC
Radio Network Controller
3757
RRH
Remote Radio Head
3758
SHO
Soft Handover
3759
SrHO
Softer Handover
3760
STSR
Sectorized Transmit Sectorized Receive
3761
TIL
Local installation terminal
3762
TRDU
Transmit Receive Duplexer Unit
END OF DOCUMENT
3763
UMT/BTS/DJD/044741
01.01/EN
Preliminary
30/Nov/2013
Page 174/174

STISS ASB RRH2 60W 21C PowerSaving v1.1

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

STISS ASB RRH2 60W 21C PowerSaving v1.1

Încărcat de

Drepturi de autor:

Formate disponibile

ISS Test Strategy for PowerSaving RRH60 21C iBTS (FRS

Not to be used or disclosed except in accordance with applicable agreements.

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

Issue V01.00 / EN, Draft, created by Shen Yi

Modified by Shen YI base on STISS_for_ASB_RRH_V01.02.docName are

Issue V01.01 / EN, Approved standard, modified by Shen Yi

Modified by Shen YI according to the review opinions

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

1.2 SCOPE OF THIS DOCUMENT .............................................................................................................. 6

1.3 AUDIENCE FOR THIS DOCUMENT ........................................................................................................ 6

REFERENCE DOCUMENTS ...................................................................................................... 6

GENERAL TEST CONSIDERATION.............................................................................................. 7

TEST ENTRY AND EXIT CRITERIA .................................................................................................... 7

DEFECT AND TRACKING .............................................................................................................. 9

FRS REQUIREMENTS AND COMPLIANCES ........................................................................................ 11

FRS REQUIREMENTS AND MAPPING ................................................................................... 11

REGRESSION TEST ................................................................................................................... 13

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

TEST CROSS REFERENCE ................................................................................................ 174

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

1.2 SCOPE OF THIS DOCUMENT

The scope of this document is to give:

1.3 AUDIENCE FOR THIS DOCUMENT

This document can be a reference for ASB_RRH60W 21C PowerSaving ST team

UMT/BTS/DD/021952 CPRI Radio Module Management v1.6

ARD546 RF Transceiver Unit External Software Description v4.5

UMT/BTS/DD/00371 UMTS OMC-B / NodeB Interface Data Model

UMT/BTS/DD/0260 iBTS Alarm Dictionary

UMT/BTS/DD/0420 iBTS Observation SFS

BTS/DD/025375V05 STSRx+y RRH supported functional specification

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

3 GENERAL TEST CONSIDERATION

TEST ENTRY AND EXIT CRITERIA

Global Pre-integration gives the GREEN flag

Basic Pre-Init testing (GA testing) are completed.

>95% pass rate at DR4 without critical CR

Any failed test cases documented via CR

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

Figure 1 ISS test environment for star mode

Daisy Chain Mode

In this configuration, it is possible to config platform with STSR1,STSR2,STSR3,STSR4,

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

Figure 2 ISS test environment for daisy chain mode

D2UV2/3 and V5 if available

ASB_RRH60W 21C with ASB and Gewei PA,Others vendors RE

AISG Full 2.0:Dual TMA AISG2.0,Single RET AISG2.0,Multi RET AISG2.0,ETC

RNC simulator :Lamp or Lamp

UE simulator:TM500 or data card

WMS (OMCB) server

Performance Spectrum Analyser

Lamp scripts(for auto case test)

CPRI LINK BETWEEN ASB_RRH60W 21C AND D2U

CPRI LINK BETWEEN ASB_RRH60W 21C AND other REs

Ethernet cable between TIL and D2U

RF cable between TwinRRH and UE/UE simulator

Backhaul cable between D2U and RNC simulator

DEFECT AND TRACKING

Weekly project synchronization meeting

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826

Test case execution progress daily check via Quality Center.

DCT will be used as defect tracking tool

STISS ASB RRH60W 21C PowerSaving for iBTSFRS131826