1xEV-DO Rev.B Test Specification For PTCL

1xEV-DO Rev.
B Test Specification for PTCL
1xEV-DO RevB Test Specification for PTCL
ZTE Co. Ltd., P. R. China
December, 2009
ATTENTION: All rights reserved. No part of this publication can be excerpted, reproduced, translated, annotated or edited, in any form or by any means, without the prior written permission of the copyright owner.
1xEV-DO Rev.B Test Specification for PTCL
Table Of Contents
1 1.1 1.2 1.3 2 3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.8 3.1.9 INTRODUCTION ................................................................................................................ 1 SCOPE .................................................................................................................................. 1 TERMS AND DEFINITIONS ...................................................................................................... 2 REFERENCES ......................................................................................................................... 2 TEST INSTRUMENTS AND TOOLS ................................................................................. 3 TEST SPECIFICATION ...................................................................................................... 3 APPLICATION LAYER PERFORMANCE TEST ............................................................................. 4 One Carrier Rev.B Terminal Ping Delay Test ...................................................................... 4 Two Carrier Rev.B Terminal Ping Delay Test ...................................................................... 6 Three Carrier Rev.B Terminal Ping Delay Test .................................................................... 7 One Carrier Rev.B Terminal FL data performance ............................................................... 9 Two CHD0 Two Carriers Rev.B Terminal FL data performance......................................... 10 One CHD0 Two Carriers Rev.B Terminal FL data performance ......................................... 12 Three Carrier Rev.B Terminal FL data performance .......................................................... 13 Packet Error Rate And Packet Loss Test ............................................................................ 15 One Carrier Rev.B Terminal RL data performance ............................................................ 16
3.1.10 Two CHD0 Two Carriers Rev.B Terminal RL data performance ........................................ 18 3.1.11 One CHD0 Two Carriers Rev.B Terminal RL data performance......................................... 19 3.1.12 Three Carriers Rev.B Terminal RL data performance ........................................................ 21 3.1.13 Channel Element Inter Carrier Pooling ............................................................................. 22 3.1.14 Dormant Status to Active State Time Test.......................................................................... 24 3.1.15 Web Response Time Test .................................................................................................. 25 3.1.16 All kinds of DRC Value Test in Multi Carrier System ........................................................ 27 3.1.17 Adjust C/I to Test the DRC Value Apply and FL Performance ........................................... 28 3.1.18 Inter Sector Softer Handoff ............................................................................................... 30 3.1.19 Inter Carrier Handoff ........................................................................................................ 32 3.1.20 Handoff Between Single-Carrier and Multi-Carrier With RevA Ternimal ........................... 34 3.1.21 Inter BTS Soft Handoff .................................................................................................... 36 3.2 3.2.1 3.2.2 3.2.3 BACKWARD COMPATIBILITY TO DO REV.A CAPABLE AT AND CDMA2000 1X TEST ................. 39 Backward Compatibility to DO Rev.A Capable AT............................................................ 39 Handoff Handoff Between DO Rev.B and DO Rev. A .................................................................. 45 Between DO Rev.B and CDMA2000 1X .......................................................... 49
II
1
1.1
Introduction
Scope
In order to verify the maturity of ZTE 1xEV-DO RevB system for commercial use, PTCL and ZTE will cooperate to start a 1xEV-DO RevB Phase I trial. Tests will be planned to verify single-carrier/multi carrier 1xEV-DO infrastructure, network functionality and performance at a system level. According to the roadmap of QUALCOMM, EV-DO RevB Phase I services can be got by a SW upgrade ONLY of current infrastructure on EV-DO Rev-A system.
The Theoretical figures for Rev-B are shown in the following table: FL Peak Modem Type CarrierRL Peak FL Avr APP Layer APP Layer APP Layer Sector Capacity CarrierCarrierCarrier(FTP Full Sector Sector Sector buffer) @ Throughput Throughput Throughput 64Kpbs avr. Thr. Rev-B, 1 carrier 3.1Mbps 2.6Mbps 1.5Mbps 2.3Mbps Rev-B, 2 carriers 6.2Mbps 5.2Mbps 3.0Mbps 4.6Mbps Rev-B, 3 carriers 9.3Mbps 7.8Mbps 4.5Mbps 6.9Mbps
RL Avr. APP Layer CarrrierSector Throughput
1.2Mbps 2.4Mbps 3.6Mbps
Assumption: 1. Terminal is close to BTS and the SINR >13dB; 2. Test with FTP download/upload; 3. DO Rev-B aggregate 3 DO Rev-A carriers in the DL to get peak speed. The cost-effective DO Rev-B upgrade is shown in the following figure:
Following is summary table of possible Rev-B BTS configuration options for current Rev-A configuration: Current Rev-A BTS Configuration 1 CHD0, 1 Rev-A DO Carrier Possible Rev-B future Configuration with SW upgrade ONLY No need to upgrade, because Rev-B is
1 CHD0, 2 Rev-A DO Carriers 2 CHD0, 2 Rev-A DO Carriers 3 CHD0, 3 Rev-A DO Carriers 3 CHD0, 4 Rev-A DO Carriers
just aggregated Rev-A carriers. It is better to directly upgrade Rev-B Phase II for single carrier. 1 CHD0, 2 Rev-B DO carriers 2 CHD0, 2 Rev-B DO Carriers 3 CHD0, 3 Rev-B DO Carriers 3 CHD0, 4 Rev-B DO Carriers
Following table is the summary of tests to be conducted: Modem Type Ping FL FTP RL FTP Rev-B, 1 carrier <60ms 2.3Mbps 1.2Mbps Rev-B, 2 carriers <60ms 4.6Mbps 2.4Mbps Rev-B, 3 carriers <60ms 6.9Mbps 3.6Mbps
1.2
AAA AN AT BSC BTS CHAP C/I DRC DSC HRPD IP IPCP MAC NAI PCF PDSN SINR TCP UATI UDP
Terms and Definitions

Authentication, Authorization and Accounting Access Network Access Terminal Base Station Controller Base Transceiver System Challenge Handshake Authentication Protocol Carrier / Interference Data Rate Control Data Source Control High Rate Packet Data Internet Protocol Internet Protocol Control Protocol Media Access Control Network Access Identifier Packet Control Function Packet Data Serving Node Signal to Interference and Noise Ratio Transmission Control Protocol Unicast Access Terminal Identifier User Datagram Protocol
1.3
References
[1] C.S0024-B_v2.0 [2] A.S0008-A_v1.0 [3] C.S0029 Test Application Specification (TAS) for High Rate Packet Data Air Interface [4] C.S0054-A_v1.0
2
No 1. 2. 3.
Test instruments and tools

Item Description Qty
Access Terminal Laptop Test software
DO Rev. B TerminalAC2790 produced by ZTE
1 1
Qualcomm QXDM
Test Specification
All the test case will be made in lab and in stationary conditions. Except the parameters in revB_PeakThroughputConfiguration.pdf, other parameters are come from 80-H0881-1_F_master system parameter of IS-856-A&B.pdf and ZTEs configuration. Trial test will be held on PTCL reference platform, the involved equipments are shown in the following table: S/N 1 2 3 3 4 5 6. 7 8 Equipment PDSN AAA/AN-AAA OMC BSC B8800 Antenna Abis interface transmission Rev-B Modem FTPServer Notes No change in trial No change in trial, We need the access permination to registe the test terminals. Upgrade SW to support DO Rev-B parameter configuration Upgrade SW, add one SDU2 to get peak speed (SDU2 capability is higher than SDU) Configured as S3 to aggregate 3 DO Rev-A carriers 3 800M/1.9GHz test antenna. 6 E1s to get peak speed AC2790 produced by ZTE Need to permission to acces this computer so to modify the computers regedit: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters Add a key, name is TcpWindowsize, value is 40000 in hex. Add a key of Tcp1323Opt of value 3.
The involved equipments in the reference platform is shown in the following figure:
FTP SERVER
AAA PDSN AN-AAA
BSC
6 E1
BTS
Rev-B Modem AC2790

Node BTS-BSC PDSN AAA Current SW Load Need to check in reference platform Need to check in reference platform Need to check in reference platform Required SW Load Version: V8.20.XX No need to upgrade No need to upgrade
3.1
3.1.1
Application Layer Performance Test

One Carrier Rev.B Terminal Ping Delay Test Application Layer Performance Test one Carrier Rev.B Terminal Ping Delay Test in lab.
No. 3.1.1 Test Name
Test Objective
The purpose of the test is to verify Rev-B Terminal Ping performance in Rev-B Network. 1. One 1xEV-DO RNC, one BTS with one carrier on one CHD0, one PDSN, and one AN-AAA upgraded appropriately for 1xEV-DO Rev-B. One OMC system. One FTP server, which has one hop away from the PDSN. All equipments work normally AT info such as the NAI correctly provisioned in AN-AAA for A12 authentication purpose
Test Configuration
2. 3.
1. 2. Test Set Up
3.
Ensure that the AT is in an area with excellent RF coverage (SINR>13dB).

AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever; Use the Ping program of Windows to application server 1/100/1000 times. Repeat step3 for three times. Response 1 Make sure normally. the system is working
1. 2. 3. 4. Action 1 Check the BSC, BTS, PDSN system.
Procedure
2 3
AT originates a packet data call. Use the Ping program of Windows to application server 1/100/1000 times. Stop the packet data call.
2 3
Packet data call is setup successfully. Make a record of the ping.
Termination is normal.
Expected Data Logs Notes
Expected Result
The average Ping delay less then 60ms.
Actual Result Problems/Issues Execution Date WITNESSED BY OPERATOR WITNESSED BY VENDOR PASS / FAIL
3.1.2
Two Carrier Rev.B Terminal Ping Delay Test Application Layer Performance Test 2 Carriers Rev-B Terminal Ping Delay Test The purpose of the test is to verify Rev-B Terminal Ping performance in Rev-B Network. 1. One 1xEV-DO RNC, one BTS with two carriers on two CHD0, one PDSN, and one AN-AAA upgraded appropriately to support multicarrier RevB. One OMC system. One FTP server, which has one hop away from the PDSN.
No. 3.1.2 Test Name Test Objective
Test Configuration
2. 3.
1. 2. Test Set Up
All equipments work normally. AT info such as the NAI correctly provisioned in AN-AAA for A12 authentication purpose
3.
1. 2. 3. 4.
Procedure
AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever; Use the Ping program of Windows to application server 1/100/1000 times. Do step 3 again 2 times.
Action
Response
Check the BSC, BTS, PDSN system.
Make sure normally.
the
system
is
working
2 3
2 3
Expected Result
3.1.3
Three Carrier Rev.B Terminal Ping Delay Test Application Layer Performance Test Three Carrier Rev-B Terminal Ping Delay Test in lab. The purpose of the test is to verify Rev-B Terminal Ping performance in Rev-B network
1.
One 1xEV-DO RNC, one BTS with three carriers on three CHD0, one PDSN, and one AN-AAA upgraded appropriately to support multicarrier RevB. One OMC system. One FTP server, which has one hop away from the PDSN.
Test Configuration
2. 3.
1. 2. Test Set Up
All equipments work normally. AT info such as the NAI correctly provisioned in AN-AAA for A12 authentication purpose
3.
1. 2. 3. 4.
Procedure
AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever; Use the Ping program of Windows to application server 1/100/1000 times. Do step 3 again 2 times..
Action 1 Check the BSC, BTS, PDSN system.
Response 1 Make sure normally. the system is working
2 3
2 3
Expected Result
3.1.4
One Carrier Rev.B Terminal FL data performance Application Layer Performance Test One Carrier Rev.B Terminal FL data performance The purpose of the test is to verify FL data performance. 1. One 1xEV-DO RNC, one BTS with one carrier on one CHD0, one PDSN, one AN-AAA upgraded appropriately for RevB support. One OMC system. One FTP server, which has one hop away from the PDSN.
Test Configuration
2. 3.
1. 2. 3. Test Set Up
All equipments work normally. Dial-up user exists in AN-AAA. Ensure that the AT is in an area with excellent RF coverage (SINR>13dB). Make sure tha SINR on the AT is such that it can request DRC 14 on each carrier. Modify the dial-up and FTP Server computers regedit to modify TCP window size
4.
1. 2. 3. 4. 5.
Procedure
AT establishes packet data session with PDSN successfully Open DOS prompt and log in application sever Download a 100M Byte file from application server Keep the down link peak data rate and down link average data rate Repeat step3 for three times
9
AT originates a packet data call.
Packet data call is setup successfully.
Download a 100M Byte file application sever by DOS prompt; Stop the packet data call.
from
Make a record of the avg. rate and peak rate. Termination is normal.
Expected Result
The application layer average rate can reach 2.3Mbps and Peak application layer rate can reach 2.6Mps.
3.1.5
Two CHD0 Two Carriers Rev.B Terminal FL data performance Application Layer Performance Test Two CHD0 Two Carriers Rev-B Terminal FL data performance The purpose of the test is to verify FL data performance with two CHD0.
10
1.
Test Configuration
2. 3.
One BSC, one BTS with two carriers on two CHD0, one PDSN, one AN-AAA. Every carrier/sector is configured to one CHD0. One OMC system. Six E1s. One FTP server, which has one hop away from the PDSN
Test Set Up
1. 2. 3.
All equipments work normally. Dial-up user exists in AN-AAA. Ensure that the AT is in an area with excellent RF coverage(C/I>13dB). Make sure that SINR on the AT is such that it can request DRC 14 on each carrier. Modify the computers regedit
4.
1. 2. 3. 4. 5. Action 1 Check the BSC, BTS, PDSN system.
Procedure
AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever; Download a 100M Byte file from application sever Keep the down link peak data rate and down link average data rate Repeat step3 for three times. Response 1 Make sure normally. the system is working
2 3
AT originates a packet data call. Download a 100M Byte file application sever by DOS prompt; Stop the packet data call. from
2 3
Packet data call is setup successfully. Make a record of the avg. rate and peak rate. Termination is normal.
Expected Data Logs Notes The application layer average rate can reach 4.6Mbps and Peak application layer rate can reach 5.2Mps.
Expected Result
Actual Result
11
Problems/Issues Execution Date WITNESSED BY OPERATOR WITNESSED BY VENDOR PASS / FAIL
3.1.6
One CHD0 Two Carriers Rev.B Terminal FL data performance Application Layer Performance Test One CHD0 Two Carriers Rev-B Terminal FL data performance The purpose of the test is to verify FL data performance. 1. One BSC, one BTS with two carriers with one CHD0, one PDSN, one AN-AAA. One OMC system. Six E1s. One FTP server, which has one hop away from the PDSN All equipments work normally. Dial-up user exists in AN-AAA. Ensure that the AT is in an area with excellent RF coverage(C/I>13dB). Make sure that SINR on the AT is such that it can request DRC 14 on each carrier. Modify the computers regedit
Test Configuration
2. 3.
1. 2. 3. Test Set Up 4.
1. 2. 3. 4. 5. Action 1 Check the BSC, BTS, PDSN system.
Procedure
AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever; Download a 100M Byte file from application sever Keep the down link peak data rate and down link average data rate Repeat step3 for three times. Response 1 Make sure normally. the system is working
12
2 3
AT originates a packet data call. Download a 100M Byte file application sever by DOS prompt; Stop the packet data call. from
2 3
Expected Data Logs Notes The application layer average rate can reach 4.6Mbps and Peak application layer rate can reach 5.2Mps.
Expected Result
3.1.7
Three Carrier Rev.B Terminal FL data performance Application Layer Performance Test Three Carriers Rev-B Terminal FL data performance The purpose of the test is to verify FL data performance. 1. One BSC, one BTS with three carriers on three CHD0, one PDSN, one AN-AAA. One OMC system. Six E1s. One FTP server, which has one hop away from the PDSN.
Test Configuration
2. 3.
13
1. 2.
All equipments work normally. Dial-up user exists in AN-AAA.
3.
Test Set Up
4.
Ensure that the AT is in an area with excellent RF coverage(C/I>13dB).Make sure that SINR on the AT is such that it can request DRC 14 on each carrier Modify the computers regedit
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Add a key, name is TcpWindowsize, value is 40000 in hex. Add a key of Tcp1323Opt of value 3. 1. 2. 3. 4. 5. AT establishes packet data session with PDSN successfully Open DOS prompt and log in application sever Download a 100M Byte file from application sever Keep the down link peak data rate and down link average data rate Repeat step3 for three times.
Procedure
Action 1 Check the BSC, BTS, PDSN system. AT originates a packet data call. Download a 100M Byte file from application sever by DOS prompt; Stop the packet data call.
Response 1 Make sure the system is working normally.
Make a record of the avg. rate and peak rate.
Expected Data Logs Notes Expected Result The application layer average rate can reach 6.9Mbps and Peak application layer rate can reach 7.8Mps.
Actual Result Problems/Issues Execution Date WITNESSED BY
14
WITNESSED BY VENDOR PASS / FAIL 3.1.8 Packet Error Rate And Packet Loss Test
Application Layer Performance Test Packet Error Rate And Packet Loss Test The purpose of the test is to verify Packet Error Rate And Packet Loss
1. Test Configuration 2. 3.
One BSC, one BTS with three carriers on three CHD0, one PDSN, one AN-AAA. One OMC system. One FTP server, which has one hop away from the PDSN.
Test Set Up
1. 2. 3. 4. 1. 2. 3. 4.
All equipments work normally. Dial-up user exists in AN-AAA. Ensure that the AT is in an area with excellent RF coverage(C/I>13dB). Ensure that only one user in the EVDO sector. AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever. Download 100M Byte file from the application sever. Keep the down link peak data rate and down link average data rate keep the packet error rate and packet loss
Procedure
5.
Repeat step3 for three times.
AT originates a packet data call.
15
Download 100M Byte file to the application sever by DOS prompt; Stop the packet data call.
Make a record of the avg. rate and peak rate. Termination is normal.
Expected Result
the packet error rate no more the 0.1%
3.1.9
One Carrier Rev.B Terminal RL data performance
Application Layer Performance Test One Carrier RL data performance in lab The purpose of the test is to verify RL data performance. 1. 2. 3. One BSC, one BTS with one carrier, one PDSN, one AN-AAA. One OMC system. One FTP server, which has one hop away from the PDSN. Set the T2Pinflow Range, PowerParameters, TxT2P Max configuration at the BSC to achive peak throughput according revB_PeakThroughputConfiguration.pdf. to
Test Configuration 4.
16
Test Set Up
1. 2. 3. 4. 1. 2.
All equipments work normally. Dial-up user exists in AN-AAA. Ensure that the AT is in an area with excellent RF coverage(C/I>13dB). Ensure that only one user in the EVDO sector. AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever. Upload 50M Byte file to the application sever. Keep the up link peak data rate and up link average data rate Repeat step3 for three times. Response 1 Make sure normally. the system is working
Procedure
3. 4. 5.
2 3
AT originates a packet data call. Upload 50M Byte file to the application sever by DOS prompt;
2 3
Packet data call is setup successfully. Make a record of the avg. rate and peak rate.
Stop the packet data call.
Expected Result
The application layer average rate can reach 1.2Mps and Peak application layer rate can reach 1.5Mbps.
Actual Result Problems/Issues Execution Date WITNESSED BY OPERATOR WITNESSED BY VENDOR
17
PASS / FAIL
3.1.10 Two CHD0 Two Carriers Rev.B Terminal RL data performance
Application Layer Performance Test Two CHD0 Two Carriers RL data performance in lab. The purpose of the test is to verify RL data performance. 1. One BSC, one BTS with two carriers, one PDSN, one AN-AAA.Two carriers on same cell, and on different CHD0, TRX. One OMC system. One FTP server, which has one hop away from the PDSN. Set the T2Pinflow Range, PowerParameters, TxT2P Max configuration at the BSC to achive peak throughput according to revB_PeakThroughputConfiguration.pdf. All equipments work normally. Dial-up user exists in AN-AAA. Ensure that the AT is in an area with excellent RF coverage(C/I>13dB). Ensure that only one user in the EVDO sector. AT establishes packet data session with PDSN successfully. Open DOS prompt and log in application sever. Upload 50M Byte file to the application sever Keep the up link peak data rate and up link average data rate Repeat step3 for three times.
Test Configuration
2. 3. 4.
1. 2. Test Set Up 3. 4. 1. 2. 3. 4. 5.
Procedure
2 3
2 3
18
Expected Data Logs Notes The application layer average rate can reach 2.5Mps and Peak application layer rate can reach 3.0Mbps.
Expected Result
3.1.11 One CHD0 Two Carriers Rev.B Terminal RL data performance
Application Layer Performance Test Two CHD0 Two Carriers RL data performance in lab. The purpose of the test is to verify RL data performance. 1. One BSC, one BTS with two carriers, one PDSN, one AN-AAA.Two carriers on same cell and CHD0, and on different TRX. One OMC system. One FTP server, which has one hop away from the PDSN. Set the T2Pinflow Range, PowerParameters, TxT2P Max configuration at the BSC to achieve peak throughput according revB_PeakThroughputConfiguration.pdf. to
2. 3. Test Configuration 4.
19
Test Set Up
1. 2. 3. 4. 1. 2.
Procedure
3. 4. 5.
2 3
2 3
Expected Data Logs Notes The application layer average rate can reach 2.5Mps and Peak application layer rate can reach 3.0Mbps.
Expected Result
20
3.1.12 Three Carriers Rev.B Terminal RL data performance
Application Layer Performance Test Three Carriers RL data performance The purpose of the test is to verify RL data performance. 4. 5. 6. One BSC, one BTS with three carriers on three CHD0, one PDSN, one AN-AAA. One OMC system. One FTP server, which has one hop away from the PDSN. Set the T2Pinflow Range, PowerParameters, TxT2P Max configuration at the BSC to achive peak throughput according to revB_PeakThroughputConfiguration.pdf.
Test Configuration 7.
Test Set Up
1. 2. 3. 4. 1. 2. 3. 4. 5.
Procedure
2 3
AT originates a packet data call. Upload 50M Byte file to the application sever by DOS prompt; Stop the packet data call.
2 3
21
Expected Data Logs Notes The application layer average rate can reach 3.6Mps and application layer peak rate can reach 5.0Mbps.
Expected Result
3.1.13 Channel Element Inter Carrier Pooling
Application Layer Performance Test Channel Element Inter Carrier Pooling The purpose of the test is to verify same Channel Element can be use by different Carrier/Sectors.
1. 2. 3.
Test Configuration
One BSC, one BTS with three carriers on three CHD0, one PDSN, one AN-AAA. One OMC system. One FTP server, which has one hop away from the PDSN.
22
Test Set Up
1. 2. 3.
All equipments work normally. Dial-up user exists in AN-AAA. Ensure that only one user in the EVDO sector.
1. Procedure 2. 3. 4.
AT establishes packet data session with PDSN successfully. Block the CEs only left one. Block the carrier only left one and try every carrier. Dial-up the AT.
2 3
AT originates a packet data call. Block the CEs only left one; Block the carrier only left one and try every carrier. AT originates a packet data call.
2 3
Packet data call is setup successfully. Make a record
Expected Data Logs Notes The same Channel Element can be use by different Carrier/Sectors.
Expected Result
23
3.1.14 Dormant Status to Active State Time Test
Application Layer Performance Test Dormant Status to Active State time test The purpose of the test is to verify the time from dormant status to active state
1. 2. 3. 4.
One BSC, one BTS with two CHD0, one PDSN, one AN-AAA. One OMC system. One FTP server, which has one hop away from the PDSN. Set AN Dormancy Timer to 5s
Test Configuration
Test Set Up
1. 2. 3.
1. 2. 3. Procedure 4. 5. Action 1 Check the BSC, BTS, PDSN system.
AT establishes packet data session with PDSN successfully. Wait 5s makesure AT enter into dormant state. Ping ftp server use this order ping ftpip l 8 n 2,keep the first ping is dormant time and keep the second ping is active time Calculate the the time from dormant status to active state, RTD_dormantRTD_active Repeat 1-4 three times Response 1 Make sure normally. the system is working
2 3
AT originates a packet data call. Make sure AT enter into dormant state
2 3
24
Ping ftp server two times
Keep records,calculate the time from dormant status to active state
Expected Result
Keep the time from dormant status to active state
Actual Result Problems/Issues Execution Date WITNESSED BY OPERATOR WITNESSED BY VENDOR PASS / FAIL 3.1.15 Web Response Time Test
Application Layer Performance Test Web response time test The purpose of the test is to verify the web response time
One BSC, one BTS with two CHD0, one PDSN, one AN-AAA. One OMC system. One FTP server, which has one hop away from the PDSN.
25
Test Set Up
1. 2. 3.
1. Procedure 2.
AT establishes packet data session with PDSN successfully. Visiting www.Youtube.com, play a video on the netting,watching for a long time,the play still fluent.
2 3
AT originates a packet data call. Visiting www.Youtube.com, play a video on the netting,watching for a long time
2 3
Packet data call is setup successfully. The play still fluent
Expected Result
The play still fluent
26
3.1.16 All kinds of DRC Value Test in Multi Carrier System
Application Layer Performance Test All kinds of DRC Value Test in Multi Carrier System The purpose of the test is to verify the performance for all kinds of DRC Value in Multi Carrier System
Test Set Up
1. 2. 3.
1. 2. Procedure 3. 4.
Use terminal order write the DRC Value to a fixed value form 1 to E. With the fixed DRC Value to download from ftp in one carrier,two carrier and three carrier Keep the download performance Repeat 1-3 three times
Write the terminals DRC Value to a fixed value
AT use the DRC Value apply FL data.
27
Download from ftp with the fixed DRC Value
Keep the record
Expected Result
The download performance near the fixed DRC Value
Actual Result Problems/Issues Execution Date WITNESSED BY OPERATOR WITNESSED BY VENDOR PASS / FAIL 3.1.17 Adjust C/I to Test the DRC Value Apply and FL Performance
Application Layer Performance Test Adjust C/I to Test the DRC Value Apply and FL Performance The purpose of the test is to adjust C/I to verify the DRC Value apply and FL performance
28
Test Set Up
1. 2. 3.
Adjust the C/I to make the terminal apply the DRC Value form 1 to E. With applied DRC Value to download from ftp in one carrier,two carrier and three carrier Keep the download performance Repeat 1-3 three times
Adjust the C/I
make the terminal apply the DRC Value form 1 to E. Keep the record
Download from ftp with the fixed DRC Value
Expected Result
The download performance near the fixed DRC Value
29
3.1.18 Inter Sector Softer Handoff No. 3.1.18 Test Name Application Layer Performance Test Inter Sector Softer Handoff
This test case verifies that AN and AT in connected state for a multiple carrier configuration scenario can successfully Test Objective perform addition of a new sector on a different cell, and that the data transfer continues when there is a change between serving sectors.
Test Configuration
1. 2. 3. 4.
One BSC, one BTS, one PDSN, one AN-AAA. One OMC system. One FTP server, which has one hop away from the PDSN. Sector configurations see next Table 1.
1. 2. Test Set Up 3. 4.
The system runs normally, and EVDO data call can be made, Configure the AN to support the 1xEV-DO Rev.B, and the AN runs normally. Configure all the ATs for Rev.B. Set the AT in HDR only mode. Carrier configuration for softer handoff tests (All sectors in the following table 1 configurations are assumed to Multi-Carrier EV-DO capable)
30
1. 2. 3. 4. 5.
Procedure
Clear the session on the AN. Configure the appropriate log mask for the test case and start logging. Set up a Dial up networking connection and start a ping ftp server. Adjust the antenna power through the specified sectors to complete handoff. Repeat steps 1 to 4 for all cases listed in Table 1.
2 3
AT originates a packet data call. Ping the application sever.
2 3
Packet data call is setup successfully. Make sure still sustain the data call.
1. Expected Result 2.
Verify that AT and the AN are able to add the new sector to the ASET and sustain the data call. Verify that AT is able to maintain the EV-DO Air Link connection with the network as the AT moves through the specified sectors during the route.
Actual Result Problems/Issues Execution Date
31
WITNESSED BY OPERATOR WITNESSED BY VENDOR PASS / FAIL
Table 1: Softer handoff carrier configuration
Carrier configuration
Number of Carriers per Minimum number Minimum number of Sector of Cells Sectors per Cell
1 1 Cell A, Sector 0 1 carrier Cell A, Sector 1 1 carrier Cell A, Sector 0 2 carriers Cell A, Sector 1 2 carriers Cell A, Sector 0 3 carriers Cell A, Sector 1 3 carriers
CC1
CC2
CC3
3.1.19 Inter Carrier Handoff No. 3.1.19 Test Name Application Layer Performance Test Inter Carrier Handoff
This test case verifies that AN and AT in connected state for a multiple carrier configuration scenario can successfully Test Objective perform addition of a new sector on a different cell, and that the data transfer continues when there is a change between serving sectors.
Test Configuration
1. 2. 3. 4.
32
1. 2. Test Set Up 3. 4.
The system runs normally, and EVDO data call can be made, Configure the AN to support the 1xEV-DO Rev.B, and the AN runs normally. Configure all the ATs for Rev.B. Set the AT in HDR only mode. Carrier configuration for handoff tests (All sectors in the following table 1 configurations are assumed to Multi-Carrier EV-DO capable)
1. 2. 3. 4. 5.
Procedure
2 3
2 3
33
Minimum number Minimum Number of Carriers per of Cells number of Sector Sectors per Cell
1 1 Cell A, Sector 0 1 carrier Cell A, Sector 1 3 carrier Cell A, Sector 0 1 carriers Cell B, Sector 1 3 carriers
CC1
CC2
3.1.20 Handoff Between Single-Carrier and Multi-Carrier With RevA Ternimal No. 3.1.20 Test Name Application Layer Performance Test Handoff Between Single-Carrier and Multi-Carrier With RevA Ternimal
Test Objective
This test case verifies that RevA Terminal can handoff Between Single-Carrier and Multi-Carrier
34
Test Configuration
1. 2. 3. 4.
1. 2. 3. 4.
Test Set Up
The system runs normally, and EVDO data call can be made, Configure the AN to support the 1xEV-DO Rev.B, and the AN runs normally. Configure the AT for Rev.A. Carrier configuration for handoff tests
1. 2. 3. 4. 5.
Procedure
2 3
2 3
35
Minimum number Minimum Number of Carriers per of Cells number of Sector Sectors per Cell
1 1 Cell A, Sector 0 1 carrier Cell A, Sector 1 3 carrier Cell A, Sector 0 1 carriers Cell B, Sector 1 3 carriers
CC1
CC2
3.1.21 Inter BTS Soft Handoff No. 3.1.21 Test Name Application Layer Performance Test Inter BTS Soft Handoff
36
Test Objective
This test case verifies that AN and AT in connected state for a multiple carrier configuration scenario can successfully perform addition of a new sector on the current cell, and that the data transfer continues when there is a change between serving sectors.
Test Configuration
1. 2. 3. 4.
1. 2. 3. 4.
Test Set Up
The system runs normally, and EVDO data call can be made, Configure the AN to support the 1xEV-DO Rev.B, and the AN runs normally. Configure the AT for Rev.B. Set the AT in HDR only mode. Carrier configuration soft handoff tests (All sectors in the following table 1 configurations are assumed to be Multi-Carrier EV-DO capable).
1. 2. 3. 4. 5.
Procedure
Action
Response
37
Make sure normally.
the
system
is
working
2 3
2 3
Verify that AT and the AN are able to add the new sector to the ASET and sustain the data call. Verify that AT is able to maintain the EV-DO Air Link connection with the network as the AT moves through the specified sectors during the test.
Table 1: Soft handoff carrier configuration
Number of Carriers per Minimum number Minimum of Cells number of Sector Sectors per Cell
2 1 Cell A, Sector 0 1 carriers Cell B, Sector 1 1carriers Cell A, Sector 0 2carriers Cell B, Sector 1 2carriers Cell A, Sector 0 3 carriers Cell B, Sector 1 3carriers
CC1
CC2
CC3
38
3.2
Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Test
3.2.1 Backward Compatibility to DO Rev.A Capable AT 3.2.1.1 Session Negotiation of DO Rev.A Capable AT on a Multi-Carrier EV-DO System Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test Session Negotiation of DO Rev.A Capable AT on a Multi-Carrier EV-DO System
No. 3.2.1.1
Test Name
Test Objective
To verify that AN can successfully setup/configure a session for a DO Rev. A capable AT on a Multi-Carrier EV-DO System.
One BSC, one BTS, one PDSN, one AN-AAA. One OMC system. One FTP server.
Test Set Up
1. 2.
The whole system runs normally. Configure the AT to operate as a DO Rev. A capable device.
39
Place the AT in a location with good Multi-Carrier EV-DO coverage. Set the log masks as required for the device under test. Start Logging. Clear the session on the AT and reset the AT. Verify the successful negotiation of personality/personalities based on the AT mode of operation as specified in the test.
Response 1 Make sure normally. Start Logging. AN should be able to configure a session with a Rev. A capable AT. the system is working
2 3
Set the log masks. Clear the session on the AT.
2 3
Expected Result
In step 4, the packet data call is made successfully. AN should be able to configure a session with a Rev. A capable AT.
Actual Result Problems/Issues Execution Date WITNESSED BY OPERATOR
40
WITNESSED BY VENDOR PASS / FAIL
3.2.1.2
Connection Setup of DO Rev.A Capable AT on a Multi-Carrier EV-DO System Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test Connection Setup of DO Rev.A Capable AT on a
No. 3.2.1.2
Test Name
Multi-Carrier EV-DO System
Test Objective
To verify that AN can successfully setup a connection for a DO Rev. A capable AT on a Multi-Carrier EV-DO System.
Test Configuration
1. 2. 3.
Test Set Up
1. 2.
The whole system runs normally. Configure the AT to operate as a 1xEV-DO Rev. A Capable device.
41
Place the AT in a location with good Multi-Carrier EV-DO coverage. Set the log masks as required for the device under test. Start Logging. Make a 1xEVDO call on the test AT. Verify the successful connection setup based on the AT mode of operation as specified in the test.
Response 1 Make sure normally. Start Logging. AN should be able to setup a connection with a Rev. A capable AT. the system is working
2 3
Set the log masks. Dial up the AT.
2 3
Expected Result
In step 4, the packet data call is made successfully. AN should be able to setup a connection with a Rev. A capable AT.
Actual Result Problems/Issues Execution Date WITNESSED BY OPERATOR
42
WITNESSED BY VENDOR PASS / FAIL
3.2.1.3
Data Transmission of DO Rev.A Capable AT on a Multi-Carrier EV-DO System Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test Data Transmission of DO Rev.A Capable AT on a Multi-Carrier EV-DO System
No. 3.2.1.3
Test Name
Test Objective
To verify that AN can successfully transmit data over connection for a DO Rev. A capable AT on a Multi-Carrier EV-DO System.
Test Configuration
1. 2. 3.
Test Set Up
1. 2.
The whole system runs normally. Configure the AT to operate as a DO Rev. A Capable device.
43
Place the AT in a location with good Multi-Carrier EV-DO coverage. Set the log masks as required for the device under test. Start Logging. Make an 1xEVDO call on the test AT. Start the data transfer for the AT and download a 100 MB file from a FTP server within the AN.
Response 1 Make sure normally. Start Logging. AN should be able to setup a connection with a Rev. A capable AT. AT should be able to download a file from FTP server. the system is working
2 3
Set the log masks. Dial up the AT.
2 3
Start the data transfer for the AT and download a 100 MB file from a FTP server.
Expected Result
In step 4, the packet data call is made successfully. AT should be able to download a file from FTP server.
Actual Result Problems/Issues
44
Execution Date WITNESSED BY OPERATOR WITNESSED BY VENDOR PASS / FAIL
3.2.2 3.2.2.1
Handoff Between DO Rev.B and DO Rev. A Different BSC Handoff From DO Rev.A To DO Rev.B in Active Data Session Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test Different BSC Handoff Active Data Session. From DO Rev.A To DO Rev. B in
No. 3.2.2.1
Test Name
Test Objective
To verify that AT can successfully handoff from Rev. A personality to Rev. B personality in Active Data Session in different BSC.
Test Configuration
1. 2. 3. 4.
Two BSC, Two BTS, one PDSN, one AN-AAA. One OMC system. One FTP server. Soft Version must be V8.20.85
1. 2. Test Set Up
AN support REV. B and run normal. AN configuration: a) b) BSC1:BTS1: S1, f1, support Rev. B BSC2:BTS2: S2, f1, only support Rev. A
45
1. 2. 3.
4. 5. 6. 7.
Clear the session on the AT and reset the AT. Set the log masks as required for the device under test. Start Logging. Set up a Dial up networking connection.AT successfully session several personality and submit Rev. A personality. Start ping the ftp server continuously in S2, Active Set = S2(f1). Up the power in S1 and down the power in S2, till AT handoff to BTS1 S1. Close the connection ,dial up renewedly in BTS1 S1. AN send AttributeUpdateRequest in which token SessionConfigToken handoff AT from Rev. A
Procedure
personality to Rev. B personality.set up EVDO Rev.B connection. 8. repeat step 4-7 several times.
Action 1 Set up a Dial up.
Response 1 Make sure submit Rev. A personality. . AT handoff to BTS1 S1.
Up the power in S1 and down the power in S2. Dial up renewedly in BTS1 S1.
Make sure AT
handoff from Rev. A
personality to Rev. B personality.set up EVDO Rev.B connection. 4 .
46
Expected Result
Successfully handoff, ping ftp server still continue.
3.2.2.2
Different BSC Handoff
From DO Rev.B To DO Rev.A in Active Data Session Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test Different BSC Handoff Active Data Session. From DO Rev.B To DO Rev. A in
No. 3.2.2.2
Test Name
Test Objective
To verify that AT can successfully handoff from Rev. B personality to Rev. A personality in Active Data Session in different BSC.
Test Configuration
1. 2. 3. 4.
Two BSC, Two BTS, one PDSN, one AN-AAA. One OMC system. One FTP server. Soft Version must be V8.20.85
47
1. 2. Test Set Up
AN support Rev. B and run normal. AN configuration: a) b) BSC1:BTS1: S1, f1, support Rev. B BSC2:BTS2: S2, f1, only support Rev. A
1. 2. 3.
Clear the session on the AT and reset the AT. Set the log masks as required for the device under test. Start Logging. Set up a Dial up networking connection.AT successfully session several personality and submit Rev.B personality. Start ping the ftp server continuously in S1, Active Set = S1(f1). Up the power in S2 and down the power in S1, till AT handoff to BTS1 S2. AN send AttributeUpdateRequest in which token SessionConfigToken handoff AT from Rev. B
4. 5. Procedure 6.
personality to Rev A personality. 7. Make sure AT send AttributeUpdateAccept, AN send ConnectionClose. 8. Make sure AT close connection and set new connection in RevA AN, Active Set=S2(f1). 9. The ping ftp server still continue. 10. repeat step 3-9 several times.
Up the power in S1 and down the power in S2.
AT handoff to BTS1 S1.
Dial up renewedly in BTS1 S1.
Make sure AT
handoff from Rev. B
personality to Rev. A personality.set up Rev.A connection.
48
Expected Result
3.2.3 3.2.3.1
Handoff Between DO Rev.B and CDMA2000 1X Handoff From CDMA2000 1X To DO Rev.B in Dormant Session Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test Handoff Session From CDMA2000 1X To DO Rev.B in Dormant
No. 3.2.3.1
Test Name
Test Objective
To verify that AT can successfully handoff from CDMA2000 1X to DO Rev.B in dormant session
49
1. 2. 3. 4.
Test Configuration
One BSC, Two BTS, one PDSN, one AN-AAA,one MSC. One OMC system. One FTP server. AN Surpport 1X
1. 2. Test Set Up 3.
Set up AT in Hybrid. AN support EV-DO Rev.B and CDMA2000 1X data service ,run normal. AN configuration: 1X+DO,1X and DO use different RRU
1. 2. 3. 4. Procedure 5.
Set up AT in 1X system successfully. Set the log masks as required for the device under test. Start Logging. Ping ftp server continuously. Up the RRU power used by DO and down the RRU power used by 1X. AT handoff successfully capture DO system,PPP connection not break off.
6. 7.
Ping ftp server continuously. repeat step 1-6several times.
Action
Response
50
Make sure normally.
the
system
is
working
2 3
Set up AT in 1X. Adjust the power of DO and 1X Cell..
2 3
Make sure AT in 1X system. Make sure AT handoff successfully capture DO system, PPP connection not break off.
Expected Result
Successfully handoff, ping ftp server continue.
3.2.3.2
Handoff From DO Rev.B To CDMA2000 1X in Dormant Data Session Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test Handoff Session From DO Rev.B To CDMA2000 1X in Dormant
No. 3.2.3.2
Test Name
51
Test Objective
To verify that AT can successfully handoff from DO Rev.B to CDMA2000 1X in dormant session.
1. 2. 3. 4.
Test Configuration
One BSC, Two BTS, one PDSN, one AN-AAA,one MSC. One OMC system. One FTP server, which has one hop away from the PDSN. AN Surpport 1X .
1. 2. Test Set Up 3.
Set up AT in Hybrid. AN support EV-DO REV. B and CDMA2000 1X data service ,run normal. AN configuration: 1X+DO,1X and DO use different RRU
52
1. 2. 3. 4. 5. 6. 7.
Set up AT in DO system successfully. Set the log masks as required for the device under test. Start Logging. AT enter dormant state. Up the RRU power used by 1X and down the RRU power used by DO. AT handoff successfully to 1X. Ping ftp server confirm AT use 1X system. repeat step 1-6 several times.
Procedure
2 3
Set up AT in 1X. Adjust the power of DO and 1X Cell..
2 3
Make sure AT in DO system. Make sure AT handoff successfully to 1X.
Expected Result
53
54

1xEV-DO Rev.B Test Specification For PTCL

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1xEV-DO Rev.B Test Specification For PTCL

Uploaded by

Copyright:

Available Formats

1xEV-DO Rev.

B Test Specification for PTCL

1xEV-DO RevB Test Specification for PTCL

ZTE Co. Ltd., P. R. China

1xEV-DO Rev.B Test Specification for PTCL

1xEV-DO Rev.B Test Specification for PTCL

RL Avr. APP Layer CarrrierSector Throughput

1.2Mbps 2.4Mbps 3.6Mbps

1xEV-DO Rev.B Test Specification for PTCL

Terms and Definitions

1xEV-DO Rev.B Test Specification for PTCL

Test instruments and tools

Access Terminal Laptop Test software

DO Rev. B TerminalAC2790 produced by ZTE

1xEV-DO Rev.B Test Specification for PTCL

AAA PDSN AN-AAA

Rev-B Modem AC2790

Application Layer Performance Test

No. 3.1.1 Test Name

1xEV-DO Rev.B Test Specification for PTCL

Ensure that the AT is in an area with excellent RF coverage (SINR>13dB).

1. 2. 3. 4. Action 1 Check the BSC, BTS, PDSN system.

Packet data call is setup successfully. Make a record of the ping.

Expected Data Logs Notes

The average Ping delay less then 60ms.

1xEV-DO Rev.B Test Specification for PTCL

No. 3.1.2 Test Name Test Objective

Ensure that the AT is in an area with excellent RF coverage (SINR>13dB).

1xEV-DO Rev.B Test Specification for PTCL

Check the BSC, BTS, PDSN system.

Make sure normally.

Packet data call is setup successfully. Make a record of the ping.

Expected Data Logs Notes

The average Ping delay less then 60ms.

No. 3.1.3 Test Name Test Objective

1xEV-DO Rev.B Test Specification for PTCL

Ensure that the AT is in an area with excellent RF coverage (SINR>13dB).

Action 1 Check the BSC, BTS, PDSN system.

Response 1 Make sure normally. the system is working

Packet data call is setup successfully. Make a record of the ping.

Expected Data Logs Notes

The average Ping delay less then 60ms.

1xEV-DO Rev.B Test Specification for PTCL

No. 3.1.4 Test Name Test Objective

1xEV-DO Rev.B Test Specification for PTCL

Action 1 Check the BSC, BTS, PDSN system.

Response 1 Make sure normally. the system is working

AT originates a packet data call.

Packet data call is setup successfully.

Expected Data Logs Notes

No. 3.1.5 Test Name Test Objective

1xEV-DO Rev.B Test Specification for PTCL

1. 2. 3. 4. 5. Action 1 Check the BSC, BTS, PDSN system.

1xEV-DO Rev.B Test Specification for PTCL

Problems/Issues Execution Date WITNESSED BY OPERATOR WITNESSED BY VENDOR PASS / FAIL

No. 3.1.6 Test Name Test Objective

1. 2. 3. 4. 5. Action 1 Check the BSC, BTS, PDSN system.

1xEV-DO Rev.B Test Specification for PTCL

No. 3.1.7 Test Name Test Objective

1xEV-DO Rev.B Test Specification for PTCL

All equipments work normally. Dial-up user exists in AN-AAA.

Response 1 Make sure the system is working normally.