1xev-do rev.b test specification for ptcl

1xEV-DO Rev.B Test Specification for PTCL

I

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.


II

Table Of Contents

1 INTRODUCTION ................................................................................................................ 1

1.1 SCOPE .................................................................................................................................. 1

1.2 TERMS AND DEFINITIONS ...................................................................................................... 2

1.3 REFERENCES ......................................................................................................................... 2

2 TEST INSTRUMENTS AND TOOLS ................................................................................. 3

3 TEST SPECIFICATION ...................................................................................................... 3

3.1 APPLICATION LAYER PERFORMANCE TEST ............................................................................. 4

3.1.1 One Carrier Rev.B Terminal Ping Delay Test ...................................................................... 4

3.1.2 Two Carrier Rev.B Terminal Ping Delay Test ...................................................................... 6

3.1.3 Three Carrier Rev.B Terminal Ping Delay Test .................................................................... 7

3.1.4 One Carrier Rev.B Terminal FL data performance ............................................................... 9

3.1.5 Two CHD0 Two Carriers Rev.B Terminal FL data performance......................................... 10

3.1.6 One CHD0 Two Carriers Rev.B Terminal FL data performance ......................................... 12

3.1.7 Three Carrier Rev.B Terminal FL data performance .......................................................... 13

3.1.8 Packet Error Rate And Packet Loss Test ............................................................................ 15

3.1.9 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 BACKWARD COMPATIBILITY TO DO REV.A CAPABLE AT AND CDMA2000 1X TEST ................. 39

3.2.1 Backward Compatibility to DO Rev.A Capable AT............................................................ 39

3.2.2 Handoff Between DO Rev.B and DO Rev. A .................................................................. 45

3.2.3 Handoff Between DO Rev.B and CDMA2000 1X .......................................................... 49


1

1 Introduction

1.1 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: Modem Type Carrier-

Sector Capacity (FTP Full buffer) @ 64Kpbs avr. Thr.

FL Peak APP Layer Carrier- Sector Throughput

RL Peak APP Layer Carrier- Sector Throughput

FL Avr APP Layer Carrier- Sector Throughput

RL Avr. APP Layer Carrrier- Sector Throughput

Rev-B, 1 carrier 3.1Mbps 2.6Mbps 1.5Mbps 2.3Mbps 1.2Mbps Rev-B, 2 carriers 6.2Mbps 5.2Mbps 3.0Mbps 4.6Mbps 2.4Mbps Rev-B, 3 carriers 9.3Mbps 7.8Mbps 4.5Mbps 6.9Mbps 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 Possible Rev-B future Configuration

with SW upgrade ONLY 1 CHD0, 1 Rev-A DO Carrier No need to upgrade, because Rev-B is


2

just aggregated Rev-A carriers. It is better to directly upgrade Rev-B Phase II for single carrier.

1 CHD0, 2 Rev-A DO Carriers 1 CHD0, 2 Rev-B DO carriers 2 CHD0, 2 Rev-A DO Carriers 2 CHD0, 2 Rev-B DO Carriers 3 CHD0, 3 Rev-A DO Carriers 3 CHD0, 3 Rev-B DO Carriers 3 CHD0, 4 Rev-A 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 Terms and Definitions AAA Authentication, Authorization and Accounting AN Access Network AT Access Terminal BSC Base Station Controller BTS Base Transceiver System CHAP Challenge Handshake Authentication Protocol C/I Carrier / Interference DRC Data Rate Control DSC Data Source Control HRPD High Rate Packet Data IP Internet Protocol IPCP Internet Protocol Control Protocol MAC Media Access Control NAI Network Access Identifier PCF Packet Control Function PDSN Packet Data Serving Node SINR Signal to Interference and Noise Ratio TCP Transmission Control Protocol UATI Unicast Access Terminal Identifier UDP 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


3

2 Test instruments and tools

No Item Description Qty

1. Access Terminal DO Rev. B Terminal：AC2790 produced by ZTE 1

2. Laptop 1 3. Test software Qualcomm QXDM 1

3 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 ZTE’s configuration. Trial test will be held on PTCL reference platform, the involved equipments are shown in the following table:

S/N Equipment Notes 1 PDSN No change in trial 2 AAA/AN-AAA No change in trial, We need the access permination to registe the test terminals. 3 OMC Upgrade SW to support DO Rev-B parameter configuration 3 BSC Upgrade SW, add one SDU2 to get peak speed (SDU2 capability is higher than

SDU) 4 B8800 Configured as S3 to aggregate 3 DO Rev-A carriers 5 Antenna 3 800M/1.9GHz test antenna. 6. Abis interface

transmission 6 E1s to get peak speed

7 Rev-B Modem AC2790 produced by ZTE 8 FTPServer Need to permission to acces this computer so to modify the computer’s 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:


4

BSC BTS6 E1

PDSN

AN-AAA

AAA

FTP SERVER

Rev-B ModemAC2790

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

3.1 Application Layer Performance Test 3.1.1 One Carrier Rev.B Terminal Ping Delay Test

No. 3.1.1 Application Layer Performance Test

Test Name one Carrier Rev.B Terminal Ping Delay Test in lab.


5

Test Objective The purpose of the test is to verify Rev-B Terminal Ping performance in Rev-B Network.

Test Configuration

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.

2. One OMC system. 3. One FTP server, which has one hop away from the

PDSN.

Test Set Up

1. All equipments work normally 2. AT info such as the NAI correctly provisioned in

AN-AAA for A12 authentication purpose 3. Ensure that the AT is in an area with excellent

RF coverage (SINR>13dB).

Procedure

1. AT establishes packet data session with PDSN successfully.

2. Open DOS prompt and log in application sever; 3. Use the Ping program of Windows to application server

1/100/1000 times. 4. Repeat step3 for three times.

Action Response

1 Check the BSC, BTS, PDSN system. 1 Make sure the system is working normally.

2 AT originates a packet data call. 2 Packet data call is setup successfully.

3 Use the Ping program of Windows to application server 1/100/1000 times.

3 Make a record of the ping.

4 Stop the packet data call. 4 Termination is normal.

Expected Data Logs

Notes

Expected Result The average Ping delay less then 60ms.


6

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


Test Name 2 Carriers Rev-B Terminal Ping Delay Test

Test Objective The purpose of the test is to verify Rev-B Terminal Ping performance in Rev-B Network.

Test Configuration

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.


PDSN.

Test Set Up

1. All equipments work normally. 2. AT info such as the NAI correctly provisioned in



Procedure



1/100/1000 times. 4. Do step 3 again 2 times.

Action Response


7






Expected Data Logs

Notes


Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.3 Three Carrier Rev.B Terminal Ping Delay Test


Test Name Three Carrier Rev-B Terminal Ping Delay Test in lab.

Test Objective The purpose of the test is to verify Rev-B Terminal Ping performance in Rev-B network


8

Test Configuration

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.


PDSN.

Test Set Up

1. All equipments work normally. 2. AT info such as the NAI correctly provisioned in



Procedure



1/100/1000 times. 4. Do step 3 again 2 times..

Action Response






Expected Data Logs

Notes



9

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.4 One Carrier Rev.B Terminal FL data performance


Test Name One Carrier Rev.B Terminal FL data performance

Test Objective The purpose of the test is to verify FL data performance.

Test Configuration

1. One 1xEV-DO RNC, one BTS with one carrier on one CHD0, one PDSN, one AN-AAA upgraded appropriately for RevB support.


PDSN.

Test Set Up

1. All equipments work normally. 2. Dial-up user exists in AN-AAA. 3. 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.

4. Modify the dial-up and FTP Server computer’s regedit to modify TCP window size

Procedure

1. AT establishes packet data session with PDSN successfully

2. Open DOS prompt and log in application sever 3. Download a 100M Byte file from application server 4. Keep the down link peak data rate and down link

average data rate 5. Repeat step3 for three times


10

Action Response



3 Download a 100M Byte file from application sever by DOS prompt;

3 Make a record of the avg. rate and peak rate.


Expected Data Logs

Notes

Expected Result The application layer average rate can reach 2.3Mbps and Peak application layer rate can reach 2.6Mps.

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.5 Two CHD0 Two Carriers Rev.B Terminal FL data performance


Test Name Two CHD0 Two Carriers Rev-B Terminal FL data performance

Test Objective The purpose of the test is to verify FL data performance with two CHD0.


11

Test Configuration

1. One BSC, one BTS with two carriers on two CHD0, one PDSN, one AN-AAA. Every carrier/sector is configured to one CHD0.

2. One OMC system. Six E1s. 3. One FTP server, which has one hop away from the

PDSN

Test Set Up


coverage(C/I>13dB). Make sure that SINR on the AT is such that it can request DRC 14 on each carrier.

4. Modify the computer’s regedit

Procedure


2. Open DOS prompt and log in application sever; 3. Download a 100M Byte file from application sever 4. Keep the down link peak data rate and down link

average data rate 5. Repeat step3 for three times.

Action Response






Expected Data Logs

Notes


Actual Result


12

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.6 One CHD0 Two Carriers Rev.B Terminal FL data performance


Test Name One CHD0 Two Carriers Rev-B Terminal FL data performance


Test Configuration

1. One BSC, one BTS with two carriers with one CHD0, one PDSN, one AN-AAA.

2. One OMC system. Six E1s. 3. One FTP server, which has one hop away from the

PDSN

Test Set Up


coverage(C/I>13dB). Make sure that SINR on the AT is such that it can request DRC 14 on each carrier.

4. Modify the computer’s regedit

Procedure


2. Open DOS prompt and log in application sever; 3. Download a 100M Byte file from application sever 4. Keep the down link peak data rate and down link

average data rate 5. Repeat step3 for three times.

Action Response



13





Expected Data Logs

Notes


Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.7 Three Carrier Rev.B Terminal FL data performance


Test Name Three Carriers Rev-B Terminal FL data performance


Test Configuration

1. One BSC, one BTS with three carriers on three CHD0, one PDSN, one AN-AAA.

2. One OMC system. Six E1s. 3. One FTP server, which has one hop away from the PDSN.


14

Test Set Up


coverage(C/I>13dB).Make sure that SINR on the AT is such that it can request DRC 14 on each carrier

4. Modify the computer’s 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.

Procedure

1. AT establishes packet data session with PDSN successfully 2. Open DOS prompt and log in application sever 3. Download a 100M Byte file from application sever 4. Keep the down link peak data rate and down link average data rate 5. Repeat step3 for three times.

Action Response

1 Check the BSC, BTS, PDSN system.

1 Make sure the system is working normally.

2 AT originates a packet data call.

2 Packet data call is setup successfully.




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


15

WITNESSED BY VENDOR

PASS / FAIL

3.1.8 Packet Error Rate And Packet Loss Test


Test Name Packet Error Rate And Packet Loss Test

Test Objective The purpose of the test is to verify Packet Error Rate And Packet Loss

Test Configuration



PDSN.

Test Set Up


coverage(C/I>13dB). 4. Ensure that only one user in the EVDO sector.

Procedure


2. Open DOS prompt and log in application sever. 3. Download 100M Byte file from the application sever. 4. Keep the down link peak data rate and down link

average data rate， keep the packet error rate and packet loss

5. Repeat step3 for three times.

Action Response




16

3 Download 100M Byte file to the application sever by DOS prompt;



Expected Data Logs

Notes

Expected Result the packet error rate no more the 0.1%

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.9 One Carrier Rev.B Terminal RL data performance


Test Name One Carrier RL data performance in lab

Test Objective The purpose of the test is to verify RL data performance.

Test Configuration

1. One BSC, one BTS with one carrier, one PDSN, one AN-AAA.


PDSN. 4. Set the T2Pinflow Range, PowerParameters, TxT2P

Max configuration at the BSC to achive peak throughput according to “revB_PeakThroughputConfiguration.pdf”.


17

Test Set Up



Procedure


2. Open DOS prompt and log in application sever. 3. Upload 50M Byte file to the application sever. 4. Keep the up link peak data rate and up link average data

rate 5. Repeat step3 for three times.

Action Response



3 Upload 50M Byte file to the application sever by DOS prompt;



Expected Data Logs

Notes

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 VENDOR


18

PASS / FAIL

3.1.10 Two CHD0 Two Carriers Rev.B Terminal RL data performance


Test Name Two CHD0 Two Carriers RL data performance in lab.


Test Configuration

1. One BSC, one BTS with two carriers, one PDSN, one AN-AAA.Two carriers on same cell, and on different CHD0, TRX.




Test Set Up



Procedure


2. Open DOS prompt and log in application sever. 3. Upload 50M Byte file to the application sever 4. Keep the up link peak data rate and up link average data


Action Response






19


Expected Data Logs

Notes


Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.11 One CHD0 Two Carriers Rev.B Terminal RL data performance


Test Name Two CHD0 Two Carriers RL data performance in lab.


Test Configuration

1. One BSC, one BTS with two carriers, one PDSN, one AN-AAA.Two carriers on same cell and CHD0, and on different TRX.



Max configuration at the BSC to achieve peak throughput according to “revB_PeakThroughputConfiguration.pdf”.


20

Test Set Up



Procedure




Action Response






Expected Data Logs

Notes


Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL


21

3.1.12 Three Carriers Rev.B Terminal RL data performance


Test Name Three Carriers RL data performance


Test Configuration





Test Set Up



Procedure




Action Response






Shahid

Highlight


22

Expected Data Logs

Notes

Expected Result The application layer average rate can reach 3.6Mps and application layer peak rate can reach 5.0Mbps.

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.13 Channel Element Inter Carrier Pooling


Test Name Channel Element Inter Carrier Pooling

Test Objective The purpose of the test is to verify same Channel Element can be use by different Carrier/Sectors.

Test Configuration



PDSN.


23

Test Set Up 1. All equipments work normally. 2. Dial-up user exists in AN-AAA. 3. Ensure that only one user in the EVDO sector.

Procedure


2. Block the CEs only left one. 3. Block the carrier only left one and try every carrier. 4. Dial-up the AT.

Action Response



3 Block the CEs only left one; Block the carrier only left one and try every carrier.

3 Make a record


Expected Data Logs

Notes

Expected Result The same Channel Element can be use by different Carrier/Sectors.

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

Shahid

Highlight


24

3.1.14 Dormant Status to Active State Time Test


Test Name Dormant Status to Active State time test

Test Objective The purpose of the test is to verify the time from dormant status to active state

Test Configuration

1. One BSC, one BTS with two CHD0, one PDSN, one AN-AAA.


PDSN. 4. Set AN Dormancy Timer to 5s


Procedure


2. Wait 5s makesure AT enter into dormant state. 3. 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

4. Calculate the the time from dormant status to active state, RTD_dormant－RTD_active

5. Repeat 1-4 three times Action Response



3 Make sure AT enter into dormant state

3

Shahid

Highlight

Shahid

Highlight

Shahid

Highlight


25

4 Ping ftp server two times 4 Keep records,calculate the time from dormant status to active state

Expected Data Logs

Notes

Expected Result Keep the time from dormant status to active state

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.15 Web Response Time Test


Test Name Web response time test

Test Objective The purpose of the test is to verify the web response time

Test Configuration



PDSN.


26


Procedure


2. Visiting www.Youtube.com, play a video on the netting,watching for a long time,the play still fluent.

Action Response



3 Visiting www.Youtube.com, play a video on the netting,watching for a long time

3 The play still fluent

Expected Data Logs

Notes

Expected Result The play still fluent

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL


27

3.1.16 All kinds of DRC Value Test in Multi Carrier System


Test Name All kinds of DRC Value Test in Multi Carrier System

Test Objective The purpose of the test is to verify the performance for all kinds of DRC Value in Multi Carrier System

Test Configuration



PDSN.


Procedure

1. Use terminal order write the DRC Value to a fixed value form 1 to E.

2. With the fixed DRC Value to download from ftp in one carrier,two carrier and three carrier

3. Keep the download performance 4. Repeat 1-3 three times

Action Response


2 Write the terminal’s DRC Value to a fixed value

2 AT use the DRC Value apply FL data.

Shahid

Highlight


28

3 Download from ftp with the fixed DRC Value

3 Keep the record

Expected Data Logs

Notes

Expected Result The download performance near the fixed DRC Value

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.1.17 Adjust C/I to Test the DRC Value Apply and FL Performance


Test Name Adjust C/I to Test the DRC Value Apply and FL Performance

Test Objective The purpose of the test is to adjust C/I to verify the DRC Value apply and FL performance

Test Configuration



PDSN.


29


Procedure

1. Adjust the C/I to make the terminal apply the DRC Value form 1 to E.

2. With applied DRC Value to download from ftp in one carrier,two carrier and three carrier

3. Keep the download performance 4. Repeat 1-3 three times

Action Response


2 Adjust the C/I 2 make the terminal apply the DRC Value form 1 to E.

3 Download from ftp with the fixed DRC Value

3 Keep the record

Expected Data Logs

Notes

Expected Result The download performance near the fixed DRC Value

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL


30

3.1.18 Inter Sector Softer Handoff


Test Name Inter Sector Softer Handoff

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 a different cell, and that the data transfer continues when there is a change between serving sectors.

Test Configuration

1. One BSC, one BTS, one PDSN, one AN-AAA. 2. One OMC system. 3. One FTP server, which has one hop away from the

PDSN. 4. Sector configurations see next Table 1.

Test Set Up

1. The system runs normally, and EVDO data call can be made,

2. Configure the AN to support the 1xEV-DO Rev.B, and the AN runs normally.

3. Configure all the AT’s for Rev.B. Set the AT in HDR only mode.

4. Carrier configuration for softer handoff tests (All sectors in the following table 1 configurations are assumed to Multi-Carrier EV-DO capable)

Shahid

Highlight


31

Procedure

1. Clear the session on the AN. 2. Configure the appropriate log mask for the test case and

start logging. 3. Set up a Dial up networking connection and start a ping

ftp server. 4. Adjust the antenna power through the specified sectors

to complete handoff. 5. Repeat steps 1 to 4 for all cases listed in Table 1.

Action Response



3 Ping the application sever. 3 Make sure still sustain the data call.


Expected Data Logs

Notes

Expected Result

1. Verify that AT and the AN are able to add the new sector to the ASET and sustain the data call.

2. 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


32


WITNESSED BY VENDOR

PASS / FAIL

Table 1: Softer handoff carrier configuration Carrier configuration

Minimum number of Cells

Minimum number of Sectors per Cell

Number of Carriers per Sector

CC1 1 1 Cell A, Sector 0 – 1 carrier

Cell A, Sector 1 – 1 carrier

CC2 1 1 Cell A, Sector 0 – 2 carriers

Cell A, Sector 1 – 2 carriers


Cell A, Sector 1 – 3 carriers

3.1.19 Inter Carrier Handoff


Test Name Inter Carrier Handoff

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 a different cell, and that the data transfer continues when there is a change between serving sectors.

Test Configuration



Shahid

Highlight


33

Test Set Up



3. Configure all the AT’s for Rev.B. Set the AT in HDR only mode.

4. Carrier configuration for handoff tests (All sectors in the following table 1 configurations are assumed to Multi-Carrier EV-DO capable)

Procedure





Action Response





Expected Data Logs

Notes


34

Expected Result



Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL








Cell B, Sector 1 – 3 carriers

3.1.20 Handoff Between Single-Carrier and Multi-Carrier With RevA Ternimal


Test Name 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

Shahid

Highlight


35

Test Configuration



Test Set Up



3. Configure the AT for Rev.A. 4. Carrier configuration for handoff tests

Procedure





Action Response





36


Expected Data Logs

Notes

Expected Result



Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL








Cell B, Sector 1 – 3 carriers

3.1.21 Inter BTS Soft Handoff


Test Name Inter BTS Soft Handoff


37

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



Test Set Up



3. Configure the AT for Rev.B. Set the AT in HDR only mode.

4. Carrier configuration soft handoff tests (All sectors in the following table 1 configurations are assumed to be Multi-Carrier EV-DO capable).

Procedure





Action Response

Shahid

Highlight


38





Expected Data Logs

Notes

Expected Result


2. 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.

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

Table 1: Soft handoff carrier configuration

Carrier configuration





Cell B, Sector 1 – 1carriers

CC2 2 1 Cell A, Sector 0 – 2carriers





39

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

No. 3.2.1.1 Backward Compatibility to DO Rev.A Capable AT and Cdma2000 1x Service Test

Test Name Session Negotiation of DO Rev.A Capable AT on a Multi-Carrier EV-DO System

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.

Test Configuration 1. One BSC, one BTS, one PDSN, one AN-AAA. 2. One OMC system. 3. One FTP server.

Test Set Up 1. The whole system runs normally. 2. Configure the AT to operate as a DO Rev. A capable

device.


40

Procedure

1. Place the AT in a location with good Multi-Carrier EV-DO coverage.

2. Set the log masks as required for the device under test. Start Logging.

3. Clear the session on the AT and reset the AT. 4. Verify the successful negotiation of

personality/personalities based on the AT mode of operation as specified in the test.

Action Response


2 Set the log masks. 2 Start Logging.

3 Clear the session on the AT. 3 AN should be able to configure a session with a Rev. A capable AT.

Expected Data Logs

Notes

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



41

WITNESSED BY VENDOR

PASS / FAIL

3.2.1.2 Connection Setup of DO Rev.A Capable AT on a Multi-Carrier EV-DO System


Test Name Connection Setup of DO Rev.A Capable AT on a 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 Set Up

1. The whole system runs normally. 2. Configure the AT to operate as a 1xEV-DO Rev. A

Capable device.


42

Procedure



3. Make a 1xEVDO call on the test AT. 4. Verify the successful connection setup based on the AT

mode of operation as specified in the test.

Action Response



3 Dial up the AT. 3 AN should be able to setup a connection with a Rev. A capable AT.

Expected Data Logs

Notes

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



43

WITNESSED BY VENDOR

PASS / FAIL

3.2.1.3 Data Transmission of DO Rev.A Capable AT on a Multi-Carrier EV-DO System


Test Name Data Transmission of DO Rev.A Capable AT on a Multi-Carrier EV-DO System

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 Set Up

1. The whole system runs normally. 2. Configure the AT to operate as a DO Rev. A Capable

device.


44

Procedure



3. Make an 1xEVDO call on the test AT. 4. Start the data transfer for the AT and download a 100

MB file from a FTP server within the AN.

Action Response



3 Dial up the AT. 3 AN should be able to setup a connection with a Rev. A capable AT.

4 Start the data transfer for the AT and download a 100 MB file from a FTP server.

4 AT should be able to download a file from FTP server.

Expected Data Logs

Notes

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


45

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.2.2 Handoff Between DO Rev.B and DO Rev. A

3.2.2.1 Different BSC Handoff From DO Rev.A To DO Rev.B in Active Data Session


Test Name Different BSC Handoff From DO Rev.A To DO Rev. B in Active Data Session.

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. Two BSC, Two BTS, one PDSN, one AN-AAA. 2. One OMC system. 3. One FTP server. 4. Soft Version must be V8.20.85

Test Set Up

1. AN support REV. B and run normal. 2. AN configuration:

a) BSC1:BTS1: S1, f1, support Rev. B

b) BSC2:BTS2: S2, f1, only support Rev. A

Shahid

Highlight

Shahid

Highlight


46

Procedure

1. Clear the session on the AT and reset the AT. 2. Set the log masks as required for the device under test.

Start Logging. 3. Set up a Dial up networking connection.AT successfully

session several personality and submit Rev. A personality.

4. Start ping the ftp server continuously in S2, Active Set = S2(f1).

5. Up the power in S1 and down the power in S2, till AT handoff to BTS1 S1.

6. Close the connection ,dial up renewedly in BTS1 S1.

7. AN send AttributeUpdateRequest in which token

SessionConfigToken handoff AT from Rev. A

personality to Rev. B personality.set up EVDO Rev.B

connection.

8. repeat step 4-7 several times.

Action Response

1 Set up a Dial up. 1 Make sure submit Rev. A personality. .

2 Up the power in S1 and down the power in S2.

2 AT handoff to BTS1 S1.

3 Dial up renewedly in BTS1 S1. 3 Make sure AT handoff from Rev. A

personality to Rev. B personality.set up

EVDO Rev.B connection.

. 4

Expected Data Logs

Notes

Shahid

Highlight

Shahid

Highlight


47

Expected Result Successfully handoff, ping ftp server still continue.

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.2.2.2 Different BSC Handoff From DO Rev.B To DO Rev.A in Active Data Session


Test Name Different BSC Handoff From DO Rev.B To DO Rev. A in Active Data Session.

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. Two BSC, Two BTS, one PDSN, one AN-AAA. 2. One OMC system. 3. One FTP server. 4. Soft Version must be V8.20.85

Shahid

Highlight

Shahid

Highlight


48

Test Set Up

1. AN support Rev. B and run normal. 2. AN configuration:

a) BSC1:BTS1: S1, f1, support Rev. B

b) BSC2:BTS2: S2, f1, only support Rev. A

Procedure

1. Clear the session on the AT and reset the AT. 2. Set the log masks as required for the device under test.

Start Logging. 3. Set up a Dial up networking connection.AT successfully

session several personality and submit Rev.B personality.

4. Start ping the ftp server continuously in S1, Active Set = S1(f1).

5. Up the power in S2 and down the power in S1, till AT handoff to BTS1 S2.

6. AN send AttributeUpdateRequest in which token

SessionConfigToken handoff AT from Rev. B

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.

Action Response


2 Up the power in S1 and down the power in S2.

2 AT handoff to BTS1 S1.

3 Dial up renewedly in BTS1 S1. 3 Make sure AT handoff from Rev. B

personality to Rev. A personality.set up

Rev.A connection.

Shahid

Highlight

Shahid

Highlight

Shahid

Highlight


49

4

Expected Data Logs

Notes


Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.2.3 Handoff Between DO Rev.B and CDMA2000 1X

3.2.3.1 Handoff From CDMA2000 1X To DO Rev.B in Dormant Session


Test Name Handoff From CDMA2000 1X To DO Rev.B in Dormant Session

Test Objective To verify that AT can successfully handoff from CDMA2000 1X to DO Rev.B in dormant session

Shahid

Highlight

Shahid

Highlight


50

Test Configuration

1. One BSC, Two BTS, one PDSN, one AN-AAA,one MSC.

2. One OMC system. 3. One FTP server. 4. AN Surpport 1X

Test Set Up

1. Set up AT in Hybrid. 2. AN support EV-DO Rev.B and CDMA2000 1X data

service ,run normal. 3. AN configuration:

1X+DO,1X and DO use different RRU

Procedure

1. Set up AT in 1X system successfully. 2. Set the log masks as required for the device under test.

Start Logging. 3. Ping ftp server continuously. 4. Up the RRU power used by DO and down the RRU

power used by 1X.

5. AT handoff successfully capture DO system,PPP

connection not break off.

6. Ping ftp server continuously. 7. repeat step 1-6several times.

Action Response

Shahid

Highlight

Shahid

Highlight

Shahid

Highlight

Shahid

Highlight

Shahid

Highlight


51


2 Set up AT in 1X. 2 Make sure AT in 1X system.

3 Adjust the power of DO and 1X Cell.. 3 Make sure AT handoff successfully capture DO system, PPP connection not break off.

4

Expected Data Logs

Notes

Expected Result Successfully handoff, ping ftp server continue.

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

3.2.3.2 Handoff From DO Rev.B To CDMA2000 1X in Dormant Data Session


Test Name Handoff From DO Rev.B To CDMA2000 1X in Dormant Session

Shahid

Highlight

Shahid

Highlight


52

Test Objective To verify that AT can successfully handoff from DO Rev.B to CDMA2000 1X in dormant session.

Test Configuration

1. One BSC, Two BTS, one PDSN, one AN-AAA,one MSC.


PDSN. 4. AN Surpport 1X .

Test Set Up

1. Set up AT in Hybrid. 2. AN support EV-DO REV. B and CDMA2000 1X data

service ,run normal. 3. AN configuration:

1X+DO,1X and DO use different RRU

Shahid

Highlight


53

Procedure

1. Set up AT in DO system successfully. 2. Set the log masks as required for the device under test.

Start Logging. 3. AT enter dormant state. 4. Up the RRU power used by 1X and down the RRU

power used by DO.

5. AT handoff successfully to 1X.

6. Ping ftp server confirm AT use 1X system. 7. repeat step 1-6 several times.

Action Response


2 Set up AT in 1X. 2 Make sure AT in DO system.

3 Adjust the power of DO and 1X Cell.. 3 Make sure AT handoff successfully to 1X.

4

Expected Data Logs

Notes



54

Actual Result

Problems/Issues

Execution Date


WITNESSED BY VENDOR

PASS / FAIL

1xev-do rev.b test specification for ptcl

Documents