[Type text]

1
1.1

DRIVE TESTING REQUIREMENTS

Drive Test Data Collections

requires outdoor drive test data when performing location estimations using both the Single Pathloss Receive Level LSQ and the Mixed Pathloss Receive Level LSQ methods. On the other hand, indoor data collection is only needed for the Mixed Pathloss Receive Level LSQ method. Outdoor Data Collection Requirements The outdoor drive test requirements are highlighted below: 1. Logs shall be collected in dedicated mode (i.e. during calls). 2. The GPS is attached to TEMS, and it is able receive signals from a number of satellites and produce location information. 3. Drive tests shall be conducted for the GSM900 and DCS1800 bands to ensure that all required logs are gathered. 4. External antennas connected to the TEMS mobiles and mounted in the middle of the car roof must be used. 5. Drive test routes shall cover the system as extensively as possible, including all major roads, highways, and special areas specified by customers. As a rule of thumb, each cell shall at least have 10% of its total coverage area sampled, i.e. driven. 6. Further, at least 5 MRs shall be collected in each grid, so that there are adequate samples to enable accurate RF propagation model correction. Assuming a cell radius of 0.5Km and a grid resolution of 20m, to obtain 5 MRs, the driving speed should be: S = 20m/5/0.48s = 8.33m/s or 30Km/h, where 0.48s is the MR report rate Therefore, drive test plans shall be customized and executed carefully to avoid jeopardizing the effectiveness of the RF model correction effort later due to insufficient MRs. Given the above considerations, during drive tests: a. It is suggested to employ multiple TEMS mobiles in order to collect sufficient MR samples in a shorter time. b. It should be noted that these TEMS mobiles may exhibit different receive sensitivities. Therefore, pre-verification shall be taken and the delta in receive power levels shall be recorded. Separate drive test logs shall be saved for different areas/roads. Drive test logs shall be collected on a 30-minute cycle to avoid extremely large files that may cause difficulties in file transfer and data processing. Supply the following three files along with drive test logs: a. Power Control Configuration File: this comma delimited CSV file indicates whether Power Control is disabled for each cell. The format is shown below in Table 1-2. Column Number 001 002 Parameter Name Cellid Command Description CellGlobalId (CGI) Mark NPC to indicate No Power Control, PC to indicate Power Control Data Type Long Char

7.

8. 9. 10.

Table 1-1 Power control configuration file format Below is a sample power control setting log file: Cellid,Command 460000410200544,NPC 460000410200545,NPC 460000410200546,NPC 460000410200547,NPC 460000410200548,NPC 460000410200549,NPC

[Type text]

[Type text]

b. System Configuration File: the file(s) submitted shall contain the correct system configuration information at the time of drive tests. c. DT Configuration File: the comma delimited CSV file submitted shall contain the correct system configuration information at the time of drive tests. The format is shown in Table 4-4. Parameter Name FileName Description The name and path of the DT file The name and path of the Power Control Configuration file DT Road Indication of indoor test or outdoor test Date of DT Name of the tester Mobile name used in DT User input description about the DT file Data Type Char Note Provided by User Mandatory, indicating the corresponding PC Config file of the DT file Optional Mandatory Optional Optional Optional Optional

Column Number 001

002

PCConfigFile

Char

003 004 005 006 007 008

Test Road Test Type Test Date Tester Test Mobile Comments

Char Char Char Char Char Char

Table 1-2 DT Configuration File format

Below is a sample DT configuration file:

DT Configuration File Template.csv

1.2

Outdoor Drive Test Procedures

The outdoor drive test procedures are explained below: 1. There are two options to ascertain a serving cell's BCCH power level by removing downlink power control information in resultant data. The changes must be set in the OMC before drive testing: a. disable the downlink power control of the serving cell in a test area, b. add the serving cell in the test area as a test neighbor into its own neighbor list. 2. Set up the drive test equipment and make sure that the GPS functions well. 3. Verify whether the new parameters (i.e. power control and/or neighbor list) are in effect by examining the RF broadcast messages. 4. Start drive testing by making calls and collecting drive test logs. Restart a call in 10 seconds upon a drop call. 5. Restore the original power control and/or neighbor list settings in the OMC. 6. Verify whether the parameters have been restored successfully by examining the RF broadcast messages.

1.3

Drive Test Tool

The following tools are needed during drive tests: GPS, TEMS Mobiles TEMS Notebooks

[Type text]

[Type text]

Maps marked with test route(s) and building(s)

1.4

Drive Test Log File Format

Table 1-3 denotes the drive test log file format required in . This format is based on the GSM Air Interface specification and the TEMS manual. All drive test logs that are not generated by TEMS shall be converted into this format so that the Data Loader is able to recognize them properly. Now version 4.1 supports TEMS Investigation version 98, 2.0, 3.2.4, 3.2.5, 4.0.1, 4.1.1, 5.1.1, 5.1.2, 6.1.1 and 7.1.1, by recognizing different column names in different TEMS version automatically. The table below shows the required columns.

Required Column

Type

Description Time of the measurement report Type of the log record

V98 & V2.0 Column Name

Format

V3.0 & above Column Name

Format 11:07:12 AM or 19:48:22:00 Measurement Report 105.954825 or E 10557.2895 20.96451333 or N 2057.8708

Time Message Type

string

TIME MESSAGE TYPE

0.6653472 MEASURE MENT REPORT

Time Message Type

string

Longitude

string

Longitude of the report

POSITION LON

E 10557.2895

All-Longitude

Latitude

string

Latitude of the report

POSITION LAT SERVING CELL MCC SERVING CELL MNC SERVING CELL LAC SERVING CELL CI

N 2057.8708

All-Latitude

MCC

string

Country code

460

All-MCC

460

MNC

string

Network code Location area code

All-MNC

LAC

string

5718(Hex)

All-LAC

54136

Cell Id

string

Cell identifier

4883(Hex)

All-Cell Id

23413

ARFCN TCH

string

TCH frequency number Indication of whether the cell adopts frequency hopping

DEDICATED CHANNEL CH NUM

32

All-ARFCN TCH

32

Hopping

string

DEDICATED CHANNEL HOPPING

YES or NO for 98, H: 12 34 56 for 2.0

All-Hopping

Yes or No

[Type text]

[Type text]

Hopping List

string

Frequency hopping list

N/A RADIO ENVIRONME NT TA RADIO ENVIRONME NT RXLEV SUB

N/A

All-Hopping List

H: 12 34 56

TA

string

Time advance

12

All-TA

12

Rxlev Sub Neighbor ARFCN (sorted) [1]~[6] Neighbor BSIC (sorted) [1]~[6] Neighbor Rxlev (sorted) [1]~[6]

string

Received signal strength ARFCN for neighbor cells, sorted by signal strength BSIC for neighbor cells, sorted by signal strength Rxlev for neighbor cells, sorted by signal strength Time slot used for current call

37

All-RxLev Sub All-Neighbor ARFCN (Sorted)[1]~[6 ] All-Neighbor BSIC (Sorted)[1]~[6 ] All-Neighbor RxLev (Sorted)[1]~[6 ]

53

string

NEIGHBOUR ING CELLS ARFCN

46

23

string

NEIGHBOUR ING CELLS BSIC

12

73 or 7-3

string

NEIGHBOUR ING CELLS RXLEV DEDICATED CHANNEL TN

39

27

Timeslot

string

All-Timeslot

Table 1-3 Drive test log format

[Type text]