Seven Castles

3G Testing- -

                                      

October 27, 2001

 

9.4 Equipment management functions
9.4.1 Equipment status display function
Testing No:
Reference:
Item: Equipment status display function
Sub-item: Equipment status display function
Objective: Check the status display function of RNC and Node B
Preset conditions for testing: Equipment is in normal operation
Testing procedures:
Inquire equipment status through operation and maintenance terminals
Alter equipment status, observe changes of equipment status
Testing notes:
Observe single board status reporting through operation and maintenance terminals
Check point A: Enable correct single board status display
Check point B: Enable timely refresh of equipment status, promptly monitor changes of equipment status

9.4.2 Function for equipment blocked
Testing No:
Reference:
Item: Function for equipment blocked
Sub-item: Function for equipment blocked
Objective: Check the function for RNC equipment blocked
Preset conditions for testing: Equipment is in normal operation
Testing procedures:
Perform blocking operation of cell, communication control ports, interface relay or path through man-machine commands
Originate call flow, observe weather blocked cell, communication control ports, interface relay or paths are taken
Testing notes:
Check point A: After interface or paths being blocked, inquire weather cell, communication control ports, interface or path are in state of being blocked, through man-machine commands
Check point B: When call flow originated, blocked cell, communication control port, interface or path should not be assigned for use

Testing No. 9.4.2.2
Reference:
Item: Function for equipment blocked
Sub-item: Function for equipment unblocked
Objective: Check the function for RNC equipment unblocked
Preset conditions for testing: Equipment is in normal operation
Testing procedures:
Perform unblocking operation of cell, communication control port, interface relay or path through man-machine commands
Originate call flow, observe weather unblocked cell, communication control ports, interface relay or paths are taken
Testing notes:
Check point A: After interface or paths being unblocked, inquire weather the status of cell, communication control ports, interface or path should be the same as expected, through man-machine commands
Check point B: When call flow originated, unblocked cell, communication control port, interface or path should not be assigned for use

9.4.3 Software loading function
Testing No. 9.4.3.1:
Reference:
Item: Software loading function
Sub-item: Software loading function
Objective: Check the software loading function of RNC and Node B
Preset conditions for testing: Equipment is in normal operation
Testing procedures:
Send designated equipment reset commands status through operation and maintenance terminals and acknowledge the response has been received
Observe loading process
Software loading can be done through being powered up, manual reset, manual plug-in, etc, in addition to man-machine commands
Testing notes:
Check loading function through man-machine interface output information
Check point A: After equipment reset, there should be information associated with the software loading of the equipment on the man-machine interface

9.4.4 Resource status inquiry
Testing No. 9.4.4.1:
Reference:
Item: Resource status inquiry function
Sub-item: Resource status inquiry function
Objective: Check the resource status inquiry function of RNC and Node B
Preset conditions for testing: Equipment is in normal operation
Testing procedures:
Inquire designated resource status (e.g. cell channel, communication control port, circuit, CPU occupancy, RAM utilization etc), through man-machine commands
Testing notes:
Check point A: After inquiry operation, resource status to be inquired should be displayed correctly

9.5 Maintenance management functions
9.5.1 Data backup management
Testing No. 9.5.1.1:
Reference:
Item: Maintenance management
Sub-item: Data backup management
Objective: Check if the data backup management function of RNC and Node B is correct
Preset conditions for testing: Equipment is in normal operation
Testing procedures:
Execute data backup commands, e.g. configuration of data backup, through man-machine interface of console
Check returned results and executed results of data backup commands through man-machine command operation
Testing notes:
Observe command execution through system reaction
Check point A: All the man-machine command operation functions specified in the above-mentioned testing procedures
Check point B: The result of data backup command execution is the same to what is expected

9.5.2 Operation log management
Testing No. 9.5.2.1:
Reference:
Item: Maintenance management
Sub-item: Operation log management
Objective: Check the operation log management function of RNC and Node B
Preset conditions for testing: Equipment is in normal operation
Testing procedures:
Execute addition, deletion, modification, etc of configuration data and succeed in data modification. Check if the operation log is recorded correctly
Perform maintenance operation, e.g. deletion of historic alarming record. Check if operation log is recorded correctly
Testing notes:
Observe command execution through system reaction
Check point A: Log can correctly record all kinds of operation that have impact on the system
Check point B: Log information should include operation time, operation result, operation commands, operator's account, etc.

9.5.3 Operation rights management
Testing No.9.5.3.1:
Reference:
Item: Maintenance management
Sub-item: User operation rights management
Objective: Check if the operation and maintenance system of RNC and Node B is secure, and if the system has reasonable control over operation of different classes
Present conditions for testing: Equipment is in normal operation
Testing procedures:
Log on to the system as an unauthorized user or an authorized user with wrong passwords.
Log on to the system as an authorized user with correct password and perform operation with or without rights to do.
Log on to the system as a system administrator, perform user setup, user rights setup, etc.
Testing notes: 
Check point A: User without rights are not allowed to perform system operation
Check point B: Enable correct setup of rights of different users
Check point C: Enable different operation with different rights
Check point D: Allow system administrator to perform flexible setup of different operation rights for users

10 Interface testing
10.1 Iu interface testing
See "Specification for Interface Testing in 3G Mobile Communication Experiment - Iu Interface" for the specification for Iu interface testing.
10.2 Iub interface testing
See "Specification for Interface Testing in 3G Mobile Communication Experiment - Iub Interface" for the specification for Iub interface testing.
10.3 Iur interface testing
See "Specification for Interface Testing in 3G Mobile Communication Experiment - Iur Interface" for the specification for Iur interface testing.

Appendix A Measurement channels
A.1 Summary of reference measurement channels
Table A.1 specifies the key parameters of UL reference measurement channels. Figures from A.2 to A.6 show the detailed channel coding of all the measurement channels.
Table A.1: UL DCH reference measurement channels
Parameters              Unit
Data bit-rate
Physical channels
Spread spectrum factors
Interweaving
DPDCH number
Dedicated pilot frequency
Power control
Spread spectrum factors
DPCCH/DPDCH power ratio
DPCCH/DPDCH multitude ratio

A.2 12.2-kbps UL reference measurement channel
Parameters of 12.2-kbps UL reference measurement channel are listed in Table A.2. See Figure A.2 for the details of channel coding.
Figure A.2
Table A.2: UL reference measurement channel (12.2 kbps)
Parameter       Criteria       Unit
Data bit-rate
Power control

A.3 64-kbps UL reference measurement channel
Parameters of 64-kbps UL reference measurement channel are listed in Table A.3.See Figure A.3 for the details of channel coding.
Figure A.3
Table A.3: UL reference measurement channel (64 kbps)
Parameter     Criteria        Unit
Data bit-rate
Power control

A.4 144-kbps UL reference measurement channel
Parameters of 144-kbps UL reference measurement channel are listed in Table A.4.See Figure A.4 for the details of channel coding.
Figure A.4
Table A.4: UL reference measurement channel (144 kbps)
Parameter     Criteria        Unit
Data bit-rate
Power control

A.5 384-kbps UL reference measurement channel
Parameters of 384-kbps UL reference measurement channel are listed in Table A.5.See Figure A.5 for the details of channel coding.
Figure A.5
Table A.5: UL reference measurement channel (384 kbps)
Parameter     Criteria        Unit
Data bit-rate
Power control
Punch

A.6 2048-kbps UL reference measurement channel
Parameters of 2048-kbps UL reference measurement channel are listed in Table A.6.See Figure A.6 for the details of channel coding.
Figure A.6
Table A.6: UL reference measurement channel (2048 kbps)
Parameter     Criteria        Unit
Data bit-rate
Power control
Punch

Appendix B Propagation conditions
B.1 Static propagation condition
Static propagation means AWGN channel. There is no fading effect, no multi-path effect with this propagation model.

B.2 Multi-path fading propagation conditions
Table B.1 lists propagation conditions for measuring receiver demodulation features in multi-path fading environment. All the taps are with classic Doppler spectrum.
Table B.1 Propagation conditions in multi-path fading environment
Condition 1            Condition 2      Condition 3
Relative delay   average power

B.3 Mobile propagation condition
The dynamic propagation condition for base-band feature testing is the non-fading channel with two taps. Mobile propagation condition is with two taps, i.e. a static one and a dynamic one. These two taps, also known as the relative delay between signal paths, change in accordance with the formula (B.1). The signal strength and phase of these two taps are the same.
Figure B.1: Mobile propagation condition
Parameters in the formula (B.1) are with the values specified in Table B.2:
Table B.2

B.3 Generating/eliminating propagation condition
The dynamic propagation condition for base-band feature testing is the non-fading channel with two taps. Generating/eliminating propagation condition is with two taps that alternates in the states of "generating" and "eliminating". The position of the time axis where these taps appear are random, and with the same possibility, as the Figure B.2 shows.
Figure B.2 Generating/eliminating propagation condition
1. Two signal paths of Path 1 and Path 2 are randomly selected from a group of relative delay [-5,-4,-3,-2,-1,0,1,2,3,4,5] μs and with the same multitude and phase;
2. Path 1 disappears after 191ms, and appears immediately at a new delay position, randomly selected from a group [-5,-4,-3,-2,-1,0,1,2,3,4,5] μs, with the position where Path 2 is currently at excluded. The multitude and phase of the tap coefficient of the two signal paths (Path 1 and Path 2) stay unchanged;
3. Path 2 disappears after another 191ms, and appears immediately at a new delay position, randomly selected from a group [-5,-4,-3,-2,-1,0,1,2,3,4,5] μs, with the position where Path 1 is currently at excluded. The multitude and phase of the tap coefficient of the two signal paths (Path 1 and Path 2) stay unchanged;
4. Repeat the above-mentioned procedures of 2 and 3.
  

- 作者： zhangliping 访问统计：　2005年03月18日, 星期五 05:18 加入博采