Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
VESPER
Vesper CDMA2000 1xEV-DO Network
Sao Paulo, Brazil
Document Reference:
Version:
Document Status:
Issue Date:
Author:
Contributors:
Department:
Contact:
Authorizing Managers:
Rubianto Satrio, Miro Budic, Scott Tran, Muhieddin Najib, Jim Oliver, Doug
Klymyshyn, Eric Jerumanis, Brian Troup, Michael Woodmansee and David
Paranchych
REVISION HISTORY
Version
Issue Date
No. of
Pages
Initials
1.0
10/29/2002
67
RV
1.1
11/11/2002
68
RV
1.2
11/16/2002
75
RV
1.3
11/19/2002
75
RV
Updated section 3
1.4
11/20/2002
83
RV
1.5
11/21/2002
83
RV
1.6
11/22/2002
86
RS
1.7
12/09/2002
99
RS
1.8
12/12/2002
98
RV
1.9
01/22/2003
98
RV
2.0
01/23/2003
97
RV
2.1
02/04/2003
101
RV
2.2
02/12/2003
101
RV
2.3
02/19/2003
102
RV
Title:
Signature:
Date:
Title:
Signature:
Date:
TABLE OF CONTENTS
1. INTRODUCTION.................................................................................................................................3
1.1 PURPOSE ..................................................................................................................................3
1.2 SCOPE ......................................................................................................................................3
1.3 RELATED DOCUMENTS ...............................................................................................................3
2. ACCEPTANCE PROCESS.................................................................................................................3
2.1 VESPER ACCEPTANCE TESTS .....................................................................................................3
2.1.1 RF Performance Tests ...............................................................................................3
2.1.2 Application Performance Tests ..................................................................................3
2.1.3 Supplementary Tests .................................................................................................3
2.2 ACCEPTANCE TEST ENTRANCE CRITERIA ....................................................................................3
2.3 EXCLUSION AREA CRITERIA........................................................................................................3
3. PERFORMANCE METRICS...............................................................................................................3
3.1 RF PERFORMANCE PARAMETERS ...............................................................................................3
3.1.1 RF Coverage ..............................................................................................................3
3.1.2 Connection Drop Rate................................................................................................3
3.1.3 Handoff Failure Rate ..................................................................................................3
3.1.3.1 Forward Link Sector Switching Delay ...................................................................... 3
3.1.3.2 Reverse Link Soft Handoff Failure........................................................................... 3
1. INTRODUCTION
1.1 Purpose
This document explains the Vesper EV-DO RF Acceptance Test procedures as agreed
between Nortel Networks and Vesper.
Customer will be timely updated on any improvements to the Acceptance Test Procedures
as described in this document.
1.2 Scope
This document explains the RF performance acceptance parameters, test procedures and
related tools to evaluate network performance for Vesper EV-DO Network, comprising of 30
sites in downtown Sao Paulo, Brazil.
Document Title
Core RF Engineering
Qualcomm Tools
Net iQ
3GPP2
Core RF Engineering
AT Analyzer Tool
Qualcomm Tools
2. ACCEPTANCE PROCESS
Network Acceptance is the final performance verification test to validate Network
Performance before handing over the network to customer.
Before staring the Acceptance test, each Access Point will be tested for correct installation
and commissioning. This will help in identifying any problem that might otherwise affect the
network performance. Following are major functions that will be tested.
a. AT originated data connection on each sector
b. Sector switching and handoff to the neighbor site
c. Average RX, TX and Ec/Io values close to the site
Please refer to Appendix-D. AP Functionality Test form will be filled for each AP.
If any problems are identified, a root cause analysis will be performed and the test will be
repeated after correcting the problem.
6. Areas where the actual coverage margins fall short of the original design requirements
due to deployment restrictions (appropriate site availability, antenna-mounting
restrictions, antenna sharing limitations, etc.) will be pre-determined. Vesper and Nortel
Networks will review maps, and an agreement will be reached on the existing coverage
and coverage holes.
7. Maps of the exclusion i.e. non-warranty areas reviewed by Vesper and agreed with
Nortel Networks. Both Nortel Networks and Vesper regional prime will sign for these
areas.
8. All the RF Measurement and post processing tools are accepted and approved by Nortel
Networks and Vesper.
9. Maps of the measurement points (for stationary tests) and acceptance drive routes (for
mobility tests) for data collection has been reviewed and agreed by Vesper and Nortel
Networks.
10. Databases of system design/propagation tool have been updated and verified to reflect
optimized system configuration. Maps of the coverage margins achieved in the design
will be generated using RF design tool as per the optimized system configuration.
11. Network must be locked from any hardware, software, parameter or other changes
during the network acceptance test period. To get a realistic view of system
performance, there will be no phones (Access Terminals) other than the acceptance test
ATs operating in the network during acceptance period.
12. All Network Performance Acceptance tests and performance numbers will be based on a
single user (AT) on the network wide average performance. Multiple ATs will be used
only for three simultaneous applications and sector capacity tests.
13. All logistical requirements for acceptance test are ready. Test equipment calibration,
coordination procedures both internal to Nortel Networks and between Nortel Networks
and Vesper are in place.
14. If due to any unforeseen Network event beyond Nortel's control, or equipment malfunctioning (e.g. unplanned outages, GPS loss etc.) the collected data seems
erroneous, the Acceptance test will be repeated for the affected area.
15. Notice to begin network acceptance test is given by Vesper regional prime.
If above conditions are not met, or due to any other unexpected circumstances, it becomes
necessary to deviate from the Acceptance process as described in this document; Nortel
Networks and Vesper will jointly agree to an alternate feasible process that is mutually
acceptable to both parties.
These areas will be identified using iPlanner, PlaNet (or similar RF prediction tool) and
further verified and finalized using drive-test measurements during coverage test.
Application performance numbers will be measured in areas where Ec/Nt is better than 2.5
dB (i.e. Ec/Io > -2dB) to validate the performance numbers as committed by Nortel
Networks.
Measurements for performance acceptance assessment will not include exclusion areas. If
the drive-test measurements include exclusion areas, then they will be excluded from
acceptance data. To ease the execution of the acceptance without many interruptions, it is
suggested that the drive-test need not be stopped unless the size of the exclusion/nonwarranted area is larger than 10 percents of the cell radius. In this case, the data collected
from non-warranted areas will be excluded during post-processing.
Similarly, stationary measurements will not be conducted in exclusion area.
3. PERFORMANCE METRICS
After successful completion of Network deployment and optimization, a date that is
acceptable to both parties would be agreed to begin Network Acceptance. Acceptance
testing will cover five applications as described in following table for various performance
parameters.
S.N.
Test /
Performance Parameter
Application
Mobility /
Stationary
Vesper Contract
ATP Test #
test #
RF Link
RF Tests
SP11/SPM1
Test 1
System RF Coverage
FWD
FWD
SP9
FWD
REV
SP10
AT Originated
SP8
Test 3
FWD
REV
FWD
REV
SP1
Test 4
FWD
REV
SP2
Test 5
SP3
Test 6
SP4
Test 7
SP5
Test 8
Test 2
FTP
HTTP
FWD
FWD
10
FWD
11 Email
FWD
12
FWD
13
FWD
14 NRTV
FWD
REV
15
FWD
REV
16
FWD
REV
17 FTP / IPSec
FWD
REV
18
FWD
REV
19
FWD
REV
FWD
REV
SPM2
21
FWD
REV
SPM3/SP18
FWD
FWD
FWD
22
23
24
FTP, HTTP
and NRTV
(Simultaneously)
Test 9*
SP6
Test 10
SP7
Test 11
25 Additional
Sup. Tests
26
FWD
SP12
Test 12
27
Idle Handoff
REV
SP13
Test 13
28
REV
SP14
29
FWD
REV
SP15, SP16
30
DRC Statistics
FWD
SP17
AT Terminated
Test 9*
Table 1
Please refer to section 3.1 for the definition of these performance parameters. Traffic models
as agreed in section 4.2 will be used for these tests.
Any exclusion areas identified during the RF design and Network Optimization process will
not be accounted towards performance degradation or included for any acceptance test
measurements. Please refer to section 2.3 for exclusion area definition.
Since the warranted coverage is targeted to perform at 90% or better area reliability, 10%
(100-90=10) of the worst performance data samples will be discarded and the remaining
data will be considered for performance calculation purpose. This will apply to all the
performance parameters in Table-1.
A statistical confidence interval for varying sample size to validate the final result for 99%
reliability will be applied.
Acceptance test performance results will be based on network wide average performance.
3.1.1 RF Coverage
RF Coverage verification will be performed to validate Networks coverage reliability. The
objective of this test is to validate that network provides sufficient coverage such that the
Access Terminal can generate data call (irrespective of data rate) across warranted
coverage area with acceptable performance in the network.
System coverage performance verification will be accessed via FTP download call using the
throughput and call setup performance within the network coverage area.
Exclusion areas where despite best optimization efforts, a data call cannot be generated will
be identified and a report will be prepared for Vespers review. There is no pass or fail
criteria for coverage test.
Same setup as connection drop test can be used for Handoff Failure test. Please refer to
sections 5.1.3 and 5.1.3.4 for Handoff Failure Rate measurement test procedures.
TCP trace logs will be generated through Windump and Snoop logs
Only transmitter side logs will be used for TCP SER calculation. Please refer to section 9 for
Packet Loss Rate measurement test procedure using windump and snoop logs.
Please refer to section 8 for Chariot tool details.
Drive test areas, Data collection tools including desktops and vans should be divided
into definite sets to have better process/inventory control, identifying mal functioning
equipments and avoid delays related to the equipment repair and replacement.
The data should be processed and analyzed as early as possibly to keep good track of
the network performance and nature of data.
All the processed and raw data must be backed up on CDs using CD writer. Each CD
must be clearly labeled about site/sector number, date, test type, engineer etc.
APPLICATION
SERVER &
Chariot
Radio Network Controller (RNC) Logs will be collected for reverse link information as
required.
Chariot console PC will be used to run the Chariot scripts. Snoop logging will be conducted
via Telnet or directly at the application server.
Following are the basic tool requirements to conduct ATP Test:
a) Network setup with application server as mentioned above
b) Data collection Tools: CAIT-2.9 with entire peripherals and GPS unit installed and
calibrated
c) Calibrated Access Terminals: Qualcomm Chesters units with enabled receive diversity
d) Calibrated LG LST-D400 terminals
e) Application emulation tool as Chariot with 200 license capacity
f)
j)
Email:
NRTV:
IPSec:
Application Throughput results are directly dependent on its Traffic Models. Application
throughput will be lower than the raw physical layer throughput for a number of reasons.
Following are some considerations in relating the physical layer and application layer
throughputs.
Ec/Io > -2 dB. This will provide a realistic view to validate Nortel Networks performance
numbers and measure network performance.
Emphasis will be placed on residential and office areas, around main streets where
customer traffic is expected to be high. If there is no access to a particular measurement
point, nearest available location will be used for measurement.
Nortel unwarranted exclusion areas should be taken into consideration during drive route
and measurement point selection. Data collected over any exclusion zone would be
excluded from the analysis and performance assessment.
Appendix-E form will be used during data collection process.
A laptop computer running the CAIT-2.9 tool through Access Terminal will be used for FTP
download purpose. Application server will be used for FTP. A sample file of 500MB will
reside at this server for FTP purpose.
a. Turn the AT off to allow any session associated with it to be released, and allow a
new set of statistics to be generated when the AT requests a new session. This
will also configure the AT to open new connections in variable reverse rate mode.
b. Go to the starting point.
c. Configure the CAIT log mask for forward link measurements
d. Start the CAIT logs
e. Start FTP by invoking a connection setup request. Start downloading a 500 MB
file.
f.
Drive around the expected coverage area following the drive route.
i.
Stop logging at the point where either link fails or a data call cannot be setup
anymore i.e. outside the cell coverage area.
j.
Note down any coverage holes, coverage boundary and time to complete each
download.
FileSize(kbps)
Total time for download (sec.)
Packer error rate is the ratio of error packets to the total packets sent.
This test will be used to verify the reverse link system performance. The test will measure
following:
A laptop computer running the CAIT-2.9 tool through Access Terminal will be used for FTP
upload purpose. Application server will be used for FTP. A sample 50MB file for FTP will
reside on the CAIT laptop.
a. Turn the AT off to allow any session associated with it to be released, and allow a
new set of statistics to be generated when the AT requests a new session. This
will also configure the AT to open new connections in variable reverse rate mode.
b. Go to the starting point.
c. Configure the CAIT log mask for reverse link measurements
d. Telnet to RNC and start the Reverse Link FER measurement script. See section
5.1.2.2
e. Start the CAIT logs
f.
g. Drive around the expected coverage across the network following the drive route.
h. Note down the connection state, signal strength and throughput.
i.
Start the FTP uploads again if the original session is completed before
completing the drive run.
j.
Stop logging at the point where either link fails or a data call cannot be setup
anymore i.e. outside the cell coverage area.
k. Note down any coverage holes, coverage boundary and time to complete each
upload.
l.
FileSize(kbps)
Total time for upload (sec.)
Use the script logrlfer to get FER statistics from the RNC.
Use the script getrlfer to thin out just the timestamps and FER
measurements.
Log at the xterm to run logrlfer and rename the log to rlfer-measurements.
Replacing the UATI below with your actual UATI, enter the following on the
command line:
kermit
take logrlfer 0x3F2
When the run is complete, enter <ctrl-c> in the xterm window to stop the script.
Use <ctrl-middle_button> and select the logging menu item to stop logging.
Click the mouse in the old xterm window from which you invoked the new xterm
session.
Enter the following on the command line:
ls -ltr
This should show only one file - the log from the xterm session.
Using the actual filename from the above list, enter the following to rename the file:
mv Xtermfile.123 rlfer-measurements
Run the thinning script to leave just the timestamps and FER measurements:
getrlfer
To convert the file to a datapoint format having timestamps and FER
measurements on one line, separated by tabs, use search-and-replace in MS Word
or other application, and replace line-feeds preceding The Frame Error Rate text
with tab characters. In the MS Word dialog, a line feed is ^p and a tab is ^t.
Handoff performance
WS-FTP PING application with one continuous connection will be used for this test. Quick
reconnection will be established upon interruption.
A laptop computer running the CAIT-2.9 tool through Access Terminal will be used to run
PING application.
a. Turn the AT off to allow any session associated with it to be released, and allow a
new set of statistics to be generated when the AT requests a new session. This
will also configure the AT to open new connections in variable reverse rate mode.
Nortel Networks Proprietary
13_Performance_Acceptance_Test_Plan_Verma.doc
Configure the CAIT log mask for forward and reverse link measurements
g. Take the RNC counter snap shot for reverse link handoff performance. See
section 5.3.3.
h. Start the CAIT logs
i.
j.
k. Each run should be for about 15-20 minutes, to limit the log file size. Thereafter
stop the run and save AT logs.
l.
Stop the Ping application and close the dialup connection. This will force the
connection to close (which has a timeout of 0) and cause traffic messages to be
logged, capturing the statistics for the run.
IdleTime
Total Call Time
The following picture shows an example of the Connection Drop Rate window in AT
Analyzer tool.
The Reverse Link Soft Handoff Success Rate measurement process is as follows:
Telnet to RNC.
At the RNC, record the UATI of the session using the following command:
show 1xevdo session all 1001 200
Check the UATI number corresponding to the test ATs
Get the initial RNC counter connection statistics for the test AT.
In the Privileged EXEC Mode, type:
AIRVANA-07#show session 0x3FF 1xevdo counters all
Where 0x3FF is the UATI (example)
Setup the laptop and the AT. Start the laptop and the AT. Using the 1xEV-DO Dialup
icon, connect/login to the network.
Start the CAIT log and test as given in section 5.2.1
At the end of drive test, stop the FTP and the CAIT logs.
Get the final RNC counters.
In the Privileged EXEC Mode, type:
AIRVANA-07#show session 0x3FF 1xevdo counters all
Data Analysis
Reverse Link Soft Handoff Success Rate is defined as:
Reverse Link Soft Handoff Success Rate = Rev. Link SHO Successes / Rev. Link SHO
Attempts
The Reverse Link Soft Handoff Success Rate is calculated from the RNC counters as
follows (from the measurement above):
From the initial RNC counters, find out the following numbers:
o Reverse Link Soft Handoffs:
Attempts
Successes
Find out the same numbers from the final RNC counters.
Subtract the initial numbers from the final numbers to obtain the statistics just for the test
session.
======================================================
Statistics
Reverse Link Soft Handoffs :Attempts
Successes
: 13
: 13
======================================================
Example of RNC counter statistics
Example using the numbers above:
Nortel Networks Proprietary
13_Performance_Acceptance_Test_Plan_Verma.doc
j.
Connection Releases and Access Attempts will be logged by AT and AN, which
will capture messaging for individual attempts as well as store cumulative
statistics.
Note:
Stop the PING application. This will cause traffic messages to be logged,
capturing the stats.
A single AT connected to EV-DO Data collection tool (Qualcomm, CAIT) and Chariot Client
will be used for these tests. In addition Windump or Snoop logs will also be logged for TCP
Segment error rate (Packet Loss) measurement at the data transmitter side.
Chariot tool will be used for Average Single User Throughput and TCP trace logs will be
used for Average packet loss and Latency measurement. For UDP application (NRTV),
latency will be measured through Chariot tool.
Following section describes the test procedures for performance measurement for each
application. Traffic models associated to each Application are defined in section 4.2.
Start the Chariot Forward Link FTP script at the Chariot Console and run
for five (5) complete transactions.
j.
Go to the next measuring point (sector) and repeat from point c until all
the measurement points in a zone are completed
m. CAIT log along with the Chariot output will be used for FTP performance
analysis
The Chariot test results will be used to determine average Single user Throughput. This will
be directly calculated from Chariot. Please refer to Chariot user manual for calculation
details. Snoop logs will be used to determine the TCP Segment Error Rate for Packet Loss
and Latency.
5.2.1.2 Reverse Link FTP Measurement
For the reverse link test, the Laptop computer running the Chariot and CAIT-2.9 through
Access Terminal would be used to emulate the FTP Upload application and serve as Client.
FTP traffic call model as defined in section 4.2 will be used.
a. Go to the measurement point under the serving sector
b. Power cycle the AT
c. Open connections in variable rate mode to the AT
Nortel Networks Proprietary
13_Performance_Acceptance_Test_Plan_Verma.doc
Co-ordinate and start the Chariot Reverse Link FTP script at the Chariot
Console port and run for five (5) complete transactions.
j.
Go to the next measuring point (sector) and repeat from point c until all
the measurement points in a zone are completed
m. CAIT logs along with the Chariot output will be used for FTP performance
analysis
The Chariot test results will be used to determine the average Single user Throughput. This
will be directly calculated from Chariot. Please refer to Chariot user manual for calculation
details. Windump logs will be used to determine the TCP Segment Error Rate for Packet
Loss and Latency.
e. Start the Chariot Forward Link HTTP script at the Chariot Console and run
for fifteen (15) complete transactions.
f.
g. At the Chariot Console: Wait for the Chariot script to complete. When
completed, save the Chariot results and export in text format.
h. Stop and save the snoop logs (Ctrl C)
i.
j.
k. Go to the next measuring point (sector) and repeat from point c until all
the measurement points in a zone are completed
l.
CAIT log along with the Chariot output will be used for HTTP performance
analysis
The Chariot test results will be used to determine the average Single user Throughput. This
will be directly calculated from Chariot. Please refer to Chariot user manual for calculation
details. Snoop logs will be used to determine the TCP Segment Error Rate for Packet Loss
and Latency.
f.
Start the Chariot Forward Link Email script at the Chariot Console and
run for ten (10) complete transactions.
j.
Go to the next measuring point (sector) and repeat from point c until
all the measurement points in a zone are completed
m. CAIT log along with the Chariot output and Snoop logs will be used for
FTP performance analysis
The Chariot test results will be used to determine the average Single user Throughput. This
will be directly calculated from Chariot. Please refer to Chariot user manual for calculation
details. Snoop logs will be used to determine the TCP Segment Error Rate for Packet Loss
and Latency.
5.2.3.2 Reverse Link Email Measurement
For the reverse link test, the Laptop computer running the Chariot and CAIT-2.9 through
Access Terminal would be used to emulate the Email Upload application. While the
Application server will serve as Client. Email traffic call model as defined in section 4.2 will
be used.
a. Go to the measurement point under the serving sector
b. Power cycle the AT
c. Open connections in variable rate mode to the AT
d. Start the CAIT log (Alt L)
e. Start the TCP Windump log on the laptop (transmitter side)
f.
Co-ordinate and start the Chariot Reverse Link Email script at the
Chariot Console port and run for ten (10) complete transactions.
j.
Go to the next measuring point (sector) and repeat from point c until
all the measurement points in a zone are completed
m. CAIT logs along with the Chariot output will be used for Email
performance analysis
The Chariot test results will be used to determine the average Single user Throughput. This
will be directly calculated from Chariot. Please refer to Chariot user manual for calculation
details. Windump logs will be used to determine the TCP Segment Error Rate for Packet
Loss and Latency.
Start the Chariot Forward Link NRTV script at the Chariot Console
and run for one complete transaction.
j.
k. Go to the next measuring point (sector) and repeat from point c until
all the measurement points in a zone are completed
l.
CAIT log along with the Chariot output will be used for NRTV
performance analysis
The Chariot test results will be used to determine Single user Throughput, latency and lost
data information. Please refer to Chariot user manual for calculation details.
6. SUPPLEMENTARY TESTS
Two of Supplementary Tests (SPM2 and SPM3) are covered while performing Performance
Acceptance tests as explained before.
Following additional supplementary tests that are to be tested for information purpose only
with no pass or fail criteria for Vesper ATP:
To meet the Vesper Supplementary Tests requirement, following additional tests will be
required:
Three separate laptops running Qualcomm CAIT and Chariot tool will be used for this test.
Same procedure as explained in section 5.3 will be used.
ConnectionSuccessRate
TotalSuccessfulOpens
TotalPage Re questsSentToAT
Verify that PNs are changing as the AT moves from sector to sector.
Save the CAIT log in case it is needed for playback later.
Note: The serving sector PN in 1xEV AT Status window may not change as the AT moves
in idle mode, because the forward link handoff only happens when the AT is in Connected
state.
DRC Statistics
Same test setup as in section 5.1.1 will be used but in a mobile environment around the
warranted coverage area in the network. CAIT and RNC performance counters will be used
with FTP download application from the server.
Setup the laptop and the AT. Start the laptop and the AT. Using the 1xEV-DO Dialup
icon, connect/login to the network.
Run CAIT, setup the appropriate logmasks.
Wait until the AT is idle, then start the CAIT (AT) log.
Start the Ping application in WS-FTP Pro using the following parameters:
o Host: IP address of the FTP server
o Packet count = 99999
o Packet size = 50
o Delay = 15 s
Do the following in CAIT:
o Check the 1xEV AT Status window and verify that the AT state is changing
between connected and idle and the session state is open.
o Monitor the 1xEV Pilot Sets window and verify the AT is served by the right
sector.
At the end test period, stop the Ping and the CAIT logs.
Get the final RNC counters.
In the Privileged EXEC Mode, type:
AIRVANA-07#show 1xevdo counters all
Change the RNC Connection Inactivity Timer to the original value.
Data Analysis
1xEV-DO Session Setup Success Rate is defined as:
Session Setup Success Rate = Session Setup Successes / Valid Session Setup Attempts
The Session Setup Success Rate is calculated from the RNC counters as follows (from the
measurement above):
From the initial RNC counters, find out the following numbers:
o (Total) Session Setup:
Attempts
Successful
o Sessions Terminated:
Receiving UATI Request
Find out the same numbers from the final RNC counters.
Subtract the initial numbers from the final numbers to obtain the statistics just for the test
session.
======================================================
Statistics
Num Current Sessions Established
: 3
: 2
: 1
: 0
Session Setup:Attempts
: 26
Successful
: 23
...
Sessions Terminated :Keep Alive Timeout
: 13
AT Close
: 0
: 0
======================================================
Example of RNC counter statistics.
Example using the numbers above:
Session Setup Success Rate = 23/(26-0) = 88.5%
Session Drop rate = 1 Session Success Rate
3. Power up the PC/LapTop and Power up the AT (Chester) and connect the USB
cable to the AT and to the PC/LapTop.
4. After the USB cable is connected to both PC/LapTop and AT, MS (MicroSoft)
Window will detect the new hard ware and MS Window will pop up Welcome to the
Found New Hardware Wizard window. Then click Next.
5. Then select the directory that has the four files mentioned above. Then click Next.
6. Then the MS window will display Driver Files Search Results window as indicated
below.
7. Click Next; the Digital Signature Not Found is displayed. Then click Yes.
8. Then the software driver will be installed. There are two files requiring to be installed.
9. After the software driver is installed. The four mentioned files are to be resided in the
path: C:\WINNT\system32\drivers.
Turn the power on for the test laptop/PC. The test laptop should be running the
Windows2000 operating system.
Ensure that the appropriate USB driver for the AT that is being used is installed on the
test laptop/PC.
Insert the CAIT key/hardware WIBU-key onto the parallel port of the test laptop/PC.
Insert the USB cable connecting the AT to the laptop into the USB port on the test
laptop/PC. Connect the other end of the USB cable to the ATs USB port.
Go to Start > Settings -> Network and Dial-up Connections -> Make New
Connection
The Network Connection Wizard will be displayed, as shown Figure A1 below.
Select Next.
Select Dial-up to private network, and chose Next as shown in Figure A2 below.
Select the appropriate modem for the Qualcomm USB 1xEVDO AT, and select
Next as shown in Figure A3 below.
Under Phone number: enter #777, and ensure that Use dialing rules is NOT
checked. Then select Next as shown in Figure A4 below.
Select For all users, under Create this connection, and select Next as shown in
Figure A5 below.
Type a name for the network connection, and add a shortcut to the desktop.
Then select Next to close the connection wizard as shown in Figure A6 below.
Double-click on the dial-up networking icon that was created in the previous
steps, and you will see Dial up window popped up as shown in Figure A7 below.
Then Click on Properties.
Select the correct modem for the Qualcomm USB port and uncheck any
other modems.
Ensure that all boxes are unchecked, and that the maximum speed is set to
115200. Select OK to return to the previous screen as shown in Figure A9
below.
Under the Options tab, check the following options as indicated in Figure A10
below):
Under the Security tab of your dial-up networking connection, ensure that the
security options are set as indicated in Figure A11 below:
Figure A13: General Tab via Internet Protocol (TCP/IP) Property window
Select Settings, and ensure that the settings are similar to Figure A14 below.
Then click OK.
o
o
o
Under the Sharing tab of your dial-up networking connection, ensure that
sharing is turned off as indicated in Figure A15 below.
Select OK to close the window and return to the dial-up adapter window.
Now 1xEV DO dial up is ready to communicate with DO network via AT.
9. Enter correct User name and password as shown in Figure B2 below. Then click on
the Dial soft key for network connection.
10. Once the PDSN has established the PPP session with the AT, check from CAITs
11. AT Status window (Figure B1), which the AT state is connected. If no data is
transferred for some time, the active PPP session will go to Dormant and the AT
state will go back to idle.
12. To ensure that the dial up session is still up check the small network connection
icon at the lower right corner of the Window display.
13. Launch the application (e.g. FTP). Provide the correct server IP address; Enter the
correct User ID and correct Password.
14. Select the desired directory corresponding to the network application server side
that you want to use to FTP a file to the Laptop and select the desired director
corresponding to the Laptop side for receiving a file. This step is for Forward Link
tests with FTP.
15. For Reverse Link FTP tests, select the desired directory corresponding to the Laptop
side that you want to use to FTP a file to the network server and select the desired
director corresponding to the network side for receiving a file.
1.
2.
3.
4.
Handoff State
Mobility testing only, Data generated only when changes in Active or Candidate set.
Strength of the pilot(s) in the active set also includes(s).
Active Pilot Set
This supplies the details of the serving pilots for the AT, the Active Set Pilots, the DRC cover
& SNR of the serving pilot.
Data Rate Control Channel ARQ Buffer
DRC rate requested by the AT. DRC cover (i.e. which sector is active on the FL) ACK/NAK
and if ACK/NAK enabled on the RL ACK channel.
ARQ Effective Receive Rate
Provides Rate at which the packet (physical layer) was decoded. DRC value requested and
the number of slots required to receive the packet at the requested rate. A physical layer
packet can contain from 1 to 4 MAC packets depending on data rate. The number of MAC
packets per frame depends on how many bits are to be sent during that frame. For example
for 38.4 only 1024 (including header bits) is needed so only one MAC packet per physical
layer frame. For 2457.6, 4096 bits are needed so there are 4 MAC packets per physical
layer frame.
Forward Traffic Rate Slot Count
Can create a histogram of what rate traffic channel packets were received and the number
of slots required to decode that packet.
Air Link Summary
PERInst - Instantaneous Packet Error Rate (calculated once 16 packets are received).
Shows PNs of pilots in the Active set.
FWD Rate Stat
Forward Rate Statistics CC & TC count & TC PER (physical layer packets). Also, shows
AvgFwdThroughput (always shows zero at this time).
Note: TC307200Long_Good, 1863,, is an excerpt from the log. The 1863 value is in units of
slots. Since this a 307200 DRC it requires 4 slot per MAC packet (in this case 1 MAC per
Physical). The number of slots per data rate needs to be factored in when determining the
number of physical layer packets between log timestamps.
Session Attempt
This holds a record containing Session attempt information. Counters are reset when AT is
power cycled.
Access Attempt
This contains access probe sequence information. Attempts, Success, and Failure counters
are reset at start of session.
Connection Attempt
This contains the connection attempt information such as traffic channel allocation
success/failure and the reason for such. Counters are reset when AT is power cycled.
Page Message
This provides the statistic for the number of page messages received by the AT. Page
message is received on Control Channel. Counters are reset when AT is power cycled
session.
Connection Release
This logs the reverse activity (RA) bits received for all pilots in the active set. Data for this
packet is sampled one every slot (1.67 ms). The data is logged once every PN roll (16 slots)
when in Connected State.
Reverse Activity Bits Information
This provides information about the reverse activity bit (RAB). The information given here is
obtained from the Traffic Channel Assignment Message.
Reverse Link Packet Summary
This provides a summary of the reverse link packet at the level of the physical layer. Every
frame that is sent out at the AT is logged. Turning on this log may result in a drop in other
log packets.
Reverse Traffic Rate Count
This contains the number of reverse link traffic packets transmitted at various rates. The
data is logged every 1 sec. Counters are reset at the start of the session.
RLP Statistics
This contains information relevant to the transmit and receive chains of the RLP stack.
Counters are reset at start of session.
RX Partial RLP
This contains RX partial RLP logging information. The data is logged asynchronously every
RLP packet that is received. The log is sent when the log buffer is full.
TX Partial RLP
This contains TX partial RLP logging information. The data is logged asynchronously every
RLP packet that is transmitted. The log is sent when the log buffer is full.
Logging mask profiles
Forward Link Throughput Testing Log Mask
Handoff State
Active Pilot Set
Data Rate Control Channel ARQ Buffer
ARQ Effective Receive Rate
Forward Traffic Rate Slot Count
Air Link Summary
Session Attempt
Access Attempt
Connection Attempt
Page Message
Connection Release
Reverse Link Testing Log Mask
Pilot Sets
Reverse Activity Bits Buffer
Reverse Activity Bits Information
Reverse Link Packet Summary
Reverse Traffic Rate Count
Reverse Power Control
Session Attempt
Access Attempt
Connection Attempt
Page Message
Connection Release
Signaling Access Channel
Signaling Reverse Traffic Channel
Signaling Control Channel Directed
Signaling Forward Traffic Channel
Traffic Channel Assignment Info
Signaling Control Channel Broadcast
Power
RLP Statistics
RLP Testing Log Mask
RLP Statistics
RX Partial RLP
TX Partial RLP
Session Attempt
Access Attempt
Connection Attempt
Page Message
Connection Release
Signaling Access Channel
Signaling Reverse Traffic Channel
Signaling Control Channel Directed
Signaling Forward Traffic Channel
Traffic Channel Assignment Info
Signaling Control Channel Broadcast
From CAIT main menu, select Option --> Configure CAIT. Then CAIT Configuration
window is popped up as shown in Figure E1 below.
Then select GPS Setting Tab and set all the fields as indicated Figure E1.
Then connect the GPS receiver to the serial Com Port of the Laptop.
Turn the GPS receiver ON. Then we will see the pop menu with Continue display and
then the Acquiring Stats Display.
Then we will see the display with Message: Need to Select Init Method. Then we need to
press enter.
Then we need to select which Method option we want to use: Map Method or
Autolocate Method.
If we have electronic map then select Map Method if not then select AutoLocate
Method.
A Globe icon will show up on the low right corner of the Window 2000 display as shown
in Figure E2 below.
Right click on the Globe icon and then select the Communications Option to see the
COM Port menu as shown in Figure E3 below and select all the COM Ports that we
think the GPS receiver is interfaced with one of these COM Ports
Then right click on the Globe icon and then select the Raw GPS Data as shown in
Figure E4 below.
If the GPS receiver detects the Satellites, then we will see the Raw GPS Data shows up
in the Raw GPS Data window as shown in Figure E5 below.
Select
Start -> Programs -> QCTest CAIT -> Tools -> Friendly Viewer
Figure: F1
Select
Select the mdm file that needs to be converted to the Raw text format and click
OK
This will open a bart chart and it will take few seconds to read and open the file
Figure: F2
8. CHARIOT TOOL
Chariot tool will be used to emulate and measure the performance of following five
applications:
a. File Transfer Protocol (FTP)
b. Hyper Text Transfer Protocol (HTTP)
c. NRTV (Near Real Time Video)
d. Email
e. File Transfer Protocol (FTP) using IPSec
Chariot is used to validate the performance characteristics of a wireless operation. It works
by exactly emulating transaction traffic from real applications.
Select
Start -> Programs -> Chariot
Following window will appear.
Select
Open -> Select the location and open the configuration file
There will be a separate script for each application and related forward or reverse
link test. Script will simulated the test application with associated traffic model as
defined in section 4.1.
Open the script file
Once the script is opened, following window will appear:
Select
Run ->
At the Pair comment input the correct sign-in user number for the Access Terminal.
Input the correct IP address for the Access Terminal (using ipconfig command at the
AT, see section 9) for Endpoint 1 network address.
Similarly, input the correct IP address for the Application Server for Endpoint 2
network address.
Select Network Prococol. TCP for FTP, HTTP and Email. UDP for NRTV.
If no editing is required (since the scripts are predefined based on the application
and traffic model). Click OK
Select
Run -> Set Run Options,
Select
File -> Save as, and give the correct file name and location
It is also suggested to save the Chariot result in verbose HTML format. Select
File -> Export -> HTML; and save the HTML file
Various application performance results like single user Throughput and can be
directly read from the result file.
<ENTER>
4. Look for the NdisVan Bh and fine the number in front of it.
(In the example above, it is no.2).
5. Type c:\> windump i# -w filename <ENTER>
# is the number in front of NdisVan Bh
For above example the command would be:
c:\> windump i2 -w filename <ENTER>
This will start the Windump log. w here implies Write
6. To stop and save the log Ctrl C
The Windump log is saved in the specified directory.
For the reverse FTP/IPSec test, in step 5, substitute # with the number of the Extranet
Access Adapter.
Select
File - > Open -> Locate the correct location and Snoop log file to open
This can take few seconds to open.
Once the Snoop file is open, following window (example) will appear:
Select
File -> Save As ->
Click on the tab and select Libpcap (tcpdump, Ethereal etc.) as the format for the
output file (TCP Dump file)
Give the file TCP Dump file name and location
Click OK and save the file
The purpose of converting the Snoop log to TCP dump format was required so that it is
compatible with TCP Trace Tool.
Re traansmittedDataPackets *100
Actual Data Packets
Usually network congestion leads to a very high retransmission rate. Therefore, considering
there is no major congestion in the network, the Segment error rate can be correctly
substituted for TCP Re-transmission rate or Packet Loss rate performance.
10. DELIVERABLES
After successful completion of the Acceptance Test following deliverables will be produced.
All the results will be based on Network wide average performance with 99% statistical
confidence reliability.
h) DRC, PER, SINR, AT State TX, RX, Best Server plots on system wide
i)
j)
SPM1
Coverage
SPM2
RF
SPM3
PER
RF
RF
SP3
SP4
SP5
SP6
RF + CORE
Throughput / Latency /
Packet Loss Stationary
single AT(s): User
Application "HTTP"
RF + CORE
Throughput / Latency /
Packet Loss Stationary
single AT(s): User
Application "E-Mail"
RF + CORE
Throughput / Latency /
Packet Loss Stationary
single AT(s): "NRTV"
User Applications
Throughput / Latency /
Packet Loss Stationary
single AT(s): "IPSEC"
User Applications
Throughput / Latency /
Packet Loss Mobility
single AT(s): Three User
Applications
RF + CORE
RF + CORE
RF
SP8
SP9
SP10
SP11
SP12
AT Terminated
Verify the AT terminated connection success rate at a live
Connection Success Rate environment. Test procedure and configuration to be specified
by Nortel and agreed between the parties.
AT Origination
RF
RF
AT Dropped Connection Verify and compare, with agreed target values, the AT dropped
Rate
connection rate, at a live environment. Test procedure and
configuration to be specified by Nortel and agreed between the
parties.
RF
Soft Inter-cell and Inter- Verify and compare, with agreed target values, the soft / softer
sector Handoff
handoff failure rates, at a live environment. Test procedure and
Performance
configuration to be specified by Nortel and agreed between the
parties.
RF
Coverage
ANTS Capacity
RF
RF
SP13
RF
SP14
RF
SP15
IS-856 Section
Establishment Success
Rate
RF
SP16
Dropped IS-856 Session Verify IS-856 session drop rate at a live environment. Test
Rate
procedure and configuration to be specified by Nortel and
agreed between the parties.
SP17
DRC Statistics
SP18
PER
RF
Verify DRC statistics (DRC value, DRC lock, inter-DRC repointing) at a live environment. Test procedure and
configuration to be specified by Nortel and agreed between the
parties.
RF
RF
12. ABBREVIATIONS
1x EV-DO
3G
3GPP
AN
Access Network
AP
Access Point
ARQ
AT
ATP
BTS
CAIT
CDMA
CI
Confidence Interval
CL
Confidence Level
CN
Core Network
DNS
DO
Data Only
DOM
DRC
FER
FER
FTP
FWA
GLF
GPS
HDR
HTTP
ICMP
IP
Internet Protocol
IPSec
Kbps
KB
Kilo Bytes
LAN
LAU
MBL
Mobile Logs
MDM
msec
1000th of a second
NRTV
PC
PC
Power Control
PDN
PDSN
PER
PPP
Point-to-Point Protocol
PS
Packet Switched
QoS
Quality of Service
RAB
RF
Radio Frequency
RFO
RLP
RN
Radio Network
RNC
RNSM
RTD
RTP
RTT
SER
SNR
TCP
TCP RTT
TRT
UDP
VJC
VoIP
VPN
WWW
Test /
Performance Parameter
Application
Required Logs
RF Tests
System RF Coverage
FTP
7
8
9
HTTP
Test 1*
Test 2
AT
AT
AT
AT
Test 3
Test 4
AT
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Snoop
Chariot
AT
Snoop
Chariot
AT
Snoop
Chariot
AT
Snoop
Chariot
AT
Snoop
Chariot
AT
Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
10
11
12 Email
13
14
15 NRTV
16
17
20
Test 5
Test 6
Test 7
Test 8
22
and NRTV
Packet Loss (TCP Segment Error) Rate
(siml.)
Latency (TCP RTT)
Test 1*
M
M
Test 9
AT
AT
AT
AT
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
AT
Windump/Snoop
Chariot
-
26 RF Tests
27
28
29
30
31
DRC Statistics
32
AT
Test 10
AT
RNC Counters
Test 11
AT
RNC Counters
Idle Handoff
Test 12
Test 13
AT
RNC Counters
AT
RNC Counters
AT
RNC Counters
AT
RNC Counters
RNC Counters
1
47.135.201.244
lineout enable
lineout
lineout
lineout
lineout
show
show
show
show
power-control
power-control
power-control
power-control
config
configFER all
configFER user \%1
status \%1
lineout configure
lineout clear power-control stats \%1
lineout exit
while 1 {
lineout exit
lineout show sntp time
lineout enable
lineout show power-control stats \%1
input \m(PERIOD) WAIT
}
________________________________________________________________
Sample Log: from Xterm log, renamed to rlfer-measurements
________________________________________________________________
AIRVANA-07>show sntp time
Sntp Time Details - UTC
Timing Source = 47.135.201.245
Base Secs
= 3246722485 (c1850db5)
Base Nsecs
= 654816005 (2707b305)
Base TBH
= 381 (0000017d)
Base TBL
= 1367329457 (517fcab1)
Current Secs = 3246722490 (c1850dba)
Current Nsecs = 402755400 (18018f48)
Num Leap Secs (since 1980) = 13
Date = 2002:11:19
Time = 19:21:30.402
Local Time Offset = -300 minutes
AIRVANA-07>enable
AIRVANA-07#show power-control stats 0x3F1
The UATI is = 1009
The total # of received frames with Good CRC = 1026
The total # received frames with Bad CRC = 10
The # of empty frames from the last Rcvd packet = 0
The Frame Error Rate = 0.009653
---------------------------------------------------------------Time in RL Frames at which PCT was computed = 0x4d477ab9
Power Control Algorithm State = ACTIVE-STEADY
CRC of received Reverse Link Frame = GOOD
|Difference| between current & last PCT (1024th of a dB) = 5
Minimum Significant Step Size (1024th of a dB) = 0
Computed Power Control Threshold (1024th of a dB) = -22335
Computed Power Control Threshold (SET POINT) (8th of a dB) = -175
Current PCT value qualifies to be sent to BTS
---------------------------------------------------------------AIRVANA-07#exit
________________________________________________________________
Log Parsing Script: getrlfer
________________________________________________________________
egrep -i "(Time =|Frame Error Rate)" rlfer-measurements* > rlfer_data
________________________________________________________________
Sample Parsed Log: in file rlfer_data
________________________________________________________________
Time = 20:47:14.881
The Frame Error Rate
Time = 20:47:16.012
The Frame Error Rate
Time = 20:47:16.918
The Frame Error Rate
Time = 20:47:18.048
The Frame Error Rate
Time = 20:47:18.162
The Frame Error Rate
= 0.000000
= 0.000000
= 0.000000
= 0.000000
= 0.000000
LOOP
number_of_repetitions=1
CONNECT_ACCEPT
destination_port=AUTO
SEND
login_size=15
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
login_size=15
control_buffer_size=DEFAULT
SEND
login_size=15
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
login_size=15
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
200
control_buffer_size=DEFAULT
DISCONNECT
close_type=Reset
LOOP
number_of_timing_records=5
START_TIMER
LOOP
transactions_per_record=1
CONNECT_INITIATE
source_port=AUTO
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
control_buffer_size=DEFAULT
SEND
200
200
control_datatype=trans.cmp
send_data_rate=UNLIMITED
DISCONNECT
close_type=Reset
LOOP
number_of_timing_records=5
LOOP
transactions_per_record=1
CONNECT_ACCEPT
destination_port=AUTO
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
SLEEP
delay_before_responding=0
RECEIVE
size_of_record_to_send=10000000
receive_buffer_size=4096
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
DISCONNECT
close_type=Reset
INCREMENT_TRANSACTION
END_LOOP
END_TIMER
SLEEP
transaction_delay=12000
END_LOOP
CONNECT_INITIATE
source_port=AUTO
SEND
6
6
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
25
control_buffer_size=DEFAULT
DISCONNECT
close_type=Reset
END_LOOP
SEND
size_of_record_to_send=10000000
send_buffer_size=4096
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
DISCONNECT
close_type=Reset
END_LOOP
END_LOOP
CONNECT_ACCEPT
destination_port=AUTO
RECEIVE
6
control_buffer_size=DEFAULT
SEND
25
25
control_datatype=trans.cmp
send_data_rate=UNLIMITED
DISCONNECT
close_type=Reset
END_LOOP
LOOP
number_of_repetitions=1
CONNECT_ACCEPT
destination_port=AUTO
SEND
login_size=15
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
login_size=15
control_buffer_size=DEFAULT
SEND
login_size=15
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
login_size=15
control_buffer_size=DEFAULT
send_data_rate=UNLIMITED
RECEIVE
200
control_buffer_size=DEFAULT
DISCONNECT
close_type=Reset
LOOP
number_of_timing_records=5
START_TIMER
LOOP
transactions_per_record=1
CONNECT_INITIATE
source_port=AUTO
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
SLEEP
delay_before_responding=0
SEND
size_of_record_to_send=1000000
SEND
200
200
control_datatype=trans.cmp
send_data_rate=UNLIMITED
DISCONNECT
close_type=Reset
LOOP
number_of_timing_records=5
LOOP
transactions_per_record=1
CONNECT_ACCEPT
destination_port=AUTO
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
size_of_record_to_send=1000000
send_buffer_size=4096
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
RECEIVE
file_control_size=30
control_buffer_size=DEFAULT
DISCONNECT
close_type=Reset
INCREMENT_TRANSACTION
END_LOOP
END_TIMER
SLEEP
transaction_delay=12000
END_LOOP
CONNECT_INITIATE
source_port=AUTO
SEND
6
6
control_datatype=trans.cmp
send_data_rate=UNLIMITED
RECEIVE
25
control_buffer_size=DEFAULT
DISCONNECT
close_type=Reset
END_LOOP
receive_buffer_size=4096
SEND
file_control_size=30
control_buffer_size=DEFAULT
control_datatype=trans.cmp
send_data_rate=UNLIMITED
DISCONNECT
close_type=Reset
END_LOOP
END_LOOP
CONNECT_ACCEPT
destination_port=AUTO
RECEIVE
6
control_buffer_size=DEFAULT
SEND
25
25
control_datatype=trans.cmp
send_data_rate=UNLIMITED
DISCONNECT
close_type=Reset
END_LOOP
LOOP
number_of_timing_records=10
LOOP
transactions_per_record=1
CONNECT_ACCEPT
destination_port=AUTO
RECEIVE
size_of_record_to_send=300
size_of_record_to_send=300
SEND
file_size_main_page=10700
send_buffer_size=DEFAULT
send_datatype_main_page=news.cmp
send_data_rate=UNLIMITED
SEND
file_size_objects=7800
send_buffer_size=DEFAULT
send_datatype_objects=lena.cmp
send_data_rate=UNLIMITED
SEND
file_size_objects=7800
send_buffer_size=DEFAULT
send_datatype_objects=lena.cmp
send_data_rate=UNLIMITED
RECEIVE
file_size_objects=7800
receive_buffer_size=DEFAULT
RECEIVE
file_size_objects=7800
receive_buffer_size=DEFAULT
RECEIVE
file_size_objects=7800
receive_buffer_size=DEFAULT
DISCONNECT
close_type=Reset
INCREMENT_TRANSACTION
END_LOOP
END_TIMER
SLEEP
transaction_delay=12000
END_LOOP
SEND
file_size_objects=7800
send_buffer_size=DEFAULT
send_datatype_objects=lena.cmp
send_data_rate=UNLIMITED
SEND
file_size_objects=7800
send_buffer_size=DEFAULT
send_datatype_objects=lena.cmp
send_data_rate=UNLIMITED
SEND
file_size_objects=7800
send_buffer_size=DEFAULT
send_datatype_objects=lena.cmp
send_data_rate=UNLIMITED
DISCONNECT
close_type=Reset
END_LOOP
END_LOOP
Endpoint 2 = PC/laptop
Endpoint 2
----------
CONNECT_ACCEPT
destination_port=AUTO
LOOP
number_of_timing_records=1
START_TIMER
RECEIVE
file_size=17000000
receive_buffer_size=DEFAULT
END_TIMER
END_LOOP
DISCONNECT
close_type=Reset
CONNECT_ACCEPT
destination_port=AUTO
LOOP
number_of_timing_records=10
LOOP
transactions_per_record=1
RECEIVE
736
receive_buffer_size=DEFAULT
SEND
exchange_mail_size=100000
send_buffer_size=DEFAULT
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
END_LOOP
END_LOOP
DISCONNECT
close_type=Reset
CONNECT_ACCEPT
destination_port=AUTO
LOOP
number_of_timing_records=10
LOOP
transactions_per_record=1
RECEIVE
160
receive_buffer_size=DEFAULT
SEND
160
send_buffer_size=DEFAULT
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
RECEIVE
exchange_mail_size=22700
receive_buffer_size=DEFAULT
SEND
576
send_buffer_size=DEFAULT
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
RECEIVE
96
receive_buffer_size=DEFAULT
Vesper EV-DO RF Acceptance Test
Page 98
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
RECEIVE
432
receive_buffer_size=DEFAULT
INCREMENT_TRANSACTION
END_LOOP
END_TIMER
SLEEP
transaction_delay=12000
END_LOOP
DISCONNECT
close_type=Reset
SEND
432
send_buffer_size=DEFAULT
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
END_LOOP
END_LOOP
DISCONNECT
close_type=Reset
Problems Resolved?
_____________
Problems
Status:
Database Updated:
Comments/Observation
ALPHA (X)
Datafill
BETA (Y)
Observed
Datafill
GAMMA (Z)
Observed
Datafill
Pilot PN
Pilot PN
Pilot PN
Height
Height
Height
Orientation
Orientation
Orientation
Mech. DT
Mech. DT
Mech. DT
Antenna
Antenna
Antenna
Neighbor List
Neighbor List
Datafill
Observed
Datafill
Observed
Neighbor List
Observed
Datafill
Call Initiation/Term.
Call Initiation/Term.
Call Initiation/Term.
Coverage/HO
Coverage/HO
Coverage/HO
Observed
Test Information
Test Type: RF Performance, Application Performance
Application:
Technician/Engineer:
AT Kit Serial Number:
Data Collection Tool & Kit Serial Number:
BTS ID or Zone Number:
Run
Number
Test
Location
MIN
Log Filename
BTS #
Sector Test
Time
Performance Parameters:
Van/Test unit:
Vesper rep (if present):
Morphology:
Network Software:
Avg.
Throughput (kB)
AF / Drop