Docstoc

Methode DT

Document Sample
Methode DT Powered By Docstoc
					2G Cluster KPI Drive Test Methodology




                                        I
                                        TABLE OF CONTENTS

1. Introduction.................................................................................................. 1

2. General ......................................................................................................... 2

3. TO1 Call Setup Success Rate (A1) ............................................................. 3

4. TO2 Call Setup Time MO – MT (A2) ............................................................ 4

5. TO3 PDP Activation Success Rate (A4) ..................................................... 5

6. TO4 SGSN Attach Success Rate (A5) ........................................................ 6

7. TO5 PDTCH Drop Rate (A6) ........................................................................ 7

8. TO6 Drop Call Tate (R1) .............................................................................. 8

9. TO7 Handover Success Rate (R5) .............................................................. 9

10. TO8 Round Trip Delay Initial Ping (I2)................................................... 10

11. TO9 Round Trip Delay Continuous Ping (I3) ........................................ 11

12. T10 Throughput GPRS (I4) ..................................................................... 12

13. T11 Throughput Edge (I5) ...................................................................... 13

14. T12 Block Error Rate - BLER (I8) ........................................................... 14

15. T13 Outdoor 2G Coverage (CQ1) .......................................................... 15

16. T14 Receive Quality (CQ3) ..................................................................... 16

17. ANNEX .............. Error! Bookmark not defined.Error! Bookmark not defined.




                                                                                                                     II
1. Introduction

         This methodology will be employed in all the regions to ensure consistency of results
         across those regions.

         The document is designed to address all the agreed Cluster Drive Test KPI’s as
         previously addressed and signed off between the parties.

         The Cluster Drive Test Report will be prepared based on the results of the drive tests
         being completed in accordance with this methodology




                                                                                              1
2.   General

          The following points document some general instructions to follow prior to the
          beginning the Cluster Drive Test. All Drive Test Teams will follow all these instructions
          in order to minimize re-work and speed up the data collection process.

                  All working sites in a cluster will be confirmed as being operational prior to
                   starting the cluster drive test. This can be done by using Managed Services or
                   other means at your disposal. It should be done before driving to the area of
                   interest.

                  The drive test kit will be fitted to the vehicle and tested for correct operation
                   prior to leaving the depot. This includes all scanners, handsets, antennae etc.
                   Where possible you should take spares antenna and handset if possible.

                  Ensure that you have all the material that you require at your disposal before
                   undertaking a drive test including site lists, scrambling code plans, frequency
                   plans, any telephone numbers that you require, notepad to document issues
                   that are observed during the drive test.

                  Where possible (and time permitting) you should plan to undertake multiple
                   cluster drives in a region. This will save time driving back and forwards to the
                   depot.

                  If you observe obvious performance problems during your drive you must
                   report back to the RF Manager or even the MS team immediately rather than
                   wait until you return to the depot. We need to make sure that problems are
                   actioned as quickly as possible.




                                                                                                   2
3.    TO1 Call Setup Success Rate (A1)


 Preset Conditions

 1. GSM and Core Network system is in normal operation.
 2. Driver Test Tools is connect with GPS and Test MS is ready and operate
     normally.
 3. The drive test route is ready and should be satisfied for good wireless coverage.
 4. The test MS is put in the test car, The mobile set’s antennas will be outside the
     vehicle, and moved around within the predetermined and agreed drive test route.
 5. Use short call dedicated mode, call duration 50s, interval 10s.
 6. Perform this testing in non-busy hour, to avoid the call setup failure due to congestion.

 Test Procedure

 1.   MO-MT, Set the called party number in drive test system TEMS, start short call
      dedicated mode.
 2.   Start TEMS data record.
 3.   Count ”Channel Request” and “Alerting” Message.

 Data Record

 1.   ‘Call Attempt’ event (The first ‘Channel Request’ L3 message of the call).
 2.   “Call Setup” event (‘Alerting’ L3 message).


 Remarks


 1.   Call Setup Success Rate = Total (Call Setup) / Total (Call Attempt) * 100%.
 2.   Perform the test when the traffic is low (non busy hour), eliminate the access
      failure problem caused by admission failure.




                                                                                                3
4.     TO2 Call Setup Time MO – MT (A2)


 Preset Conditions

      1. GSM and Core Network system is in normal operation.
      2. Core Network “TMSI RELOCATION” is not enabled.
      3. Select one cell per site, and include all the site in a cluster..
      4. Total 200 samples are taken in one cluster.
      5. Test is performed in static test mode.
      6. Perform this testing in non-busy hour, to avoid the long call setup time due to congestion.
 Test Procedure

 1.        Set MS2 number as the called party number of MS1 in drive test system TEMS.
 2.        Start TEMS data record.
 3.        Stop data recording after taking enough samples.


 Data Record

 1.        Calculate the delay time between “channel request” and “alerting” on the trace file
           for the test MS as setup time.

 Remarks
 1.        Call setup time = from MS1 sending “Channel Request” to MS1 receiving
           “Alerting” .




                                                                                                       4
5.     TO3 PDP Activation Success Rate (A4)


 Preset Conditions
      1.   C/I >=15dB.
      2.   Enough PDCH,At least one PDCH can be allocated for each MS.
      3.   Static test.
      4.   The subscriber is a normal user, no prepaid procedure involved.
      5.   Switch off PTMSI reallocation function.
      6.   GPRS system is in normal operation.
      7.   The subscriber information in HLR is correct.
      8.   Selected one cell from each site, and include all the site in a cluster, total 200
            samples in a cluster.
 .
 Test Procedures

 1.        Test MS initiates PDP Activate operation from TEMS.
 2.        Test MS PDP Deactivate. wait for 10 seconds, then Reactivate PDP.
 3.        Repeat step 1) to 2).
 4.        Count the “Activate PDP Context Request” and “”Activate PDP Context Accept”
           message from TEMS.


 Data Record
 1.        “Activate PDP Context Request”.
 2.        “Activate PDP Context Accept”.

 Remarks
 1.        PDP Activation Success Rate = Total (Activate PDP Context Accept) / Total
           (Activate PDP Context Request) * 100%.
2.         No "missing or unknown APN" cause failure.
3.         No "unknown PDP address or PDP type" cause failure.
4.         At low traffic conditions and excludes blocked calls due to insufficient traffic
           channel or poor air interface quality.




                                                                                                5
6.        TO4 SGSN Attach Success Rate (A5)


 Preset Conditions


     1.   C/I >=15dB.
     2.   Enough PDCH,At least one PDCH can be allocated for each MS.
     3.   Static test..
     4.   The subscriber is a normal user, no prepaid procedure involved.
     5.   Switch off PTMSI reallocation function.
     6.   GPRS system is in normal operation.
     7.   The subscriber information in HLR is correct.
     8.   Selected one cell from one site, and include all the site in a cluster, total 200
           samples in a cluster.


 Test Procedures

 1.       Test MS initiate Attach operation from TEMS. I
 2.       Test MS Detach. wait for 10 seconds, then Reattach.
 3.       Repeat step 1) to 2).
 4.       Count the “Attach Request” and “Attach Accept” message from TEMS


 Data Record

 1.        “Attach Request”
 2.       “Attach Accept”

 Remarks
 1.       SGSN Attach Success Rate = Total (Attach Accept) / Total (Attach Request) *
          100%
2.        Authorized subscriber and Subscribed Data is accurate,
3.        At low traffic conditions and excludes blocked calls due to insufficient traffic
          channel or poor air interface quality.




                                                                                              6
7.    TO5 PDTCH Drop Rate (A6)


 Preset Conditions
     1. Use Session Error Rate from TEMS to instead PDTCH Drop Rate.
     2. The measurement is extracted from the layer 3 message of “Session Start” and
        “Session Error”.
     3. Drive test the predetermined and agreed drive test route.
     4. Start EDGE FTP DL sessions from TEMS, download 50k byte file from the
         server.
     5. Test is performed at low traffic period.

 Test Procedures

 1.    Start PS dedicated mode and data record.
 2.    Count “Session Start” and “Session Error” message from TEMS.

 Data Record

 1.    “Session Start”.
 2.    “Session Error”.
 3.    Exclude the session error due to mobile phone problem and the file server
       problem, i.e. exclude casues contains ‘Session aborted by user’, ’Session
       already open or in use’, ‘Socket creation failed’, ‘Socket error’, and ‘The address
       is not valid’.

 Remarks
 PDTCH Drop Rate = Total[Session Error] / Total[Session Start] * 100%




                                                                                             7
8.    TO6 Drop Call Tate (R1)


Preset Conditions
 1. GSM system is in normal operation.
 2. Network Optimization work is end.
 3. Driver Test Tools is connect with GPS and Test MS is ready and operate normally..
 4. The drive test route is ready and should be satisfied for good wireless coverage..
 5. The test MS is put in the test car, The mobile set’s antennas will be outside the
     vehicle, and moved around within the predetermined and agreed drive test route.
 6. Use short call dedicated mode, call duration 50s, interval 10s.

Test Procedure
1.    Set “MS2” as the called party number of “MS1” in drive test system TEMS..
2.    Start data record in TEMS by using short call dedicated mode.
3.    If a call fails to establish, or drops, a new call attempt will not be made until 50s after
      the initial call attempt,
4.    Save the LOGFILE of TEMS,
5.    Count the “Call Drop” and “Alerting” event from LOGFILE.
.
Data Record
1.    “Call Drop”.
2.    “Alerting”.

Remarks
Drop Call Rate =Total [Call Drop] / Total [Alerting] * 100%




                                                                                                    8
9.    TO7 Handover Success Rate (R5)


 Preset Conditions
     1. Avoid busy hour when executing the test.
     2. The test MS is put in the test car, The mobile set’s antennas will be outside the
         vehicle,and moved around within the predetermined and agreed drive test route.

 Test Procedures
 1.    Set “199” as the called party number is drive test system TEMS, long call mode.
 2.    Put TEMS in a car and start auto test function in TEMS.
 3.    Count “handover command” and “handover complete” message from TEMS.

 Data record
 1.    “Handover Command”.
 2.    “Handover Complete”..

 Remarks
     1. Handover Success Rate = Total (handover complete) / Total (handover
         command).




                                                                                            9
10. TO8 Round Trip Delay Initial Ping (I2)


 Preset Conditions
  1. GSM system is in normal operation.
  2. MS should support uplink TBF function.(i.e. SE W600i, SE K790i).
  3. Select one cell from per site, and include all sites in the cluster, total 200 samples
      in a cluster.
  4. Perform this testing at non PS busy hour.

 Test Procedures
 1.   Test MS is arranged in the test place, make a dialup sequence in TEMS, create a
      ping command in the dialup session,
 2.   The ping address set to SGSN gateway address and packet size set as 20 Bytes.
 3.   Start dialup and data record.
 4.   the interval between “beginning of ping ”and “first ping response” called initial ping
      delay.
 5.   repeat step 1) to 4).
 6.   Change the test place, and repeat step 1) to 5).

 Data record
 1.   Initial ping delay

 Remarks




                                                                                               10
11. TO9 Round Trip Delay Continuous Ping (I3)

Preset Conditions
     1. GSM system is in normal operation.
     2. MS should support uplink TBF function.(like Nokia N Series and E Series).
     3. Select one cells from one sites, and include all sites in the cluster, total 200
          samples in a cluster.
     4. Perform this testing in non PS busy hour.

Test Procedures
1.     Test MS is arranged in the test place, make a dialup sequence in TEMS, create a
       ping command in the dialup session.
2.     The ping address set to SGSN gateway address and packet size set as 20 Bytes..
3.     Start dialup and data record.
4.     The interval between “ping response” called continuous ping delay.
5.     Repeat step 1) to 4).
6.     Change the test place, and repeat step 1) to 5)

Data record
1.     Continuous ping delay

Remarks




                                                                                           11
12. T10 Throughput GPRS (I4)


       Preset Conditions
        1. MultiSlot Capbility of MS is 4+2.
        2. Field Survey. Test conducted in multiple stationary location with C/I >
            30dB.
        3. The test cell is not configured as extended range or satellite transmission.
        4. CS3/CS4 are to be used. The cell has 4 available PDCHs during the test.
        5. Single user senario in the testing cell when performing the FA test, to
            avoid others subscriber share the PDCH bandwith, since one PDCH can
            be mutiple used by up to 8 subscriber.
        6. The size of file for upload or download is 256kbyte/512kbyte respectively.
        7. The resource of License,PCIC,Gb,Pb interface is enough.
        8. Setup a high performance FTP server in the Operator’s intranet, the FTP
            server is connect to the GPRS network via GGSN directly. download file
            from the FTP server with multiple threads . Make sure no other service is
            running on the FTP server while perform the test. No packet drop
            happen in core network.
        9. Select one cells from one sites, and include all sites in the cluster, each
            cell perfrom one download test.

       Test Procedures
       1.   Connected PC and MS(TEMS suite), PDP active.
       2.   Start auto test and recording function in TEMS.
       3.   Download file from server(the size of file about 512k BYTE).
       4.   Wait 10s.
       5.   Upload file to server(the size of file about 256k BYTE).
       6.   Stop recording.
       7.   Repeat step 2-5 on several other stationary locations.

       Data record
       1.   RLC Throughput DL (kbit/s).
       2.   RLC Throughput UL (kbit/s).
       3.   Average Used Timeslot UL and DL
       Remarks
       1. Filter out the throughput only between FTP ‘session start’ and ‘session
          end’, calculate the average value,
       2. Devide the average thoughput by average used timeslot from TEMS to
          calculate per timeslot value.




                                                                                          12
13. T11 Throughput Edge (I5)


Preset Conditions
1.   MultiSlot Capbility of MS is 4+2.
2.   Field Survey. Test conducted in multiple stationary location with C/I > 30dB.
3.   The test cell is not configured as extended range or satellite transmission.
4.   MCS9 are to be used. The cell has 4 available PDCHs during the test, and
     assuming the PDCH only occupy by the test MS, now capacity sharing with other
     MS.
5.   Single user senario in the testing cell when performing the FA test, to avoid others
     subscriber share the PDCH bandwith, since one PDCH can be mutiple used by up
     to 8 subscriber.
6.   The size of file for upload or download is 512kbyte/1024kbyte respectively.
7.   Setup a high performance FTP server in the Operator’s intranet, the FTP server is
     connect to the GPRS network via GGSN directly. download file from the FTP
     server with multiple threads . Make sure no other service is running on the FTP
     server while perform the test. No packet drop happen in core network.
8.   The resource of License,PCIC,Gb,Pb interface is enough.The MS should support
     EGPRS and the uplink of MS should support 8PSK and uplink 2 timeslot.
9.   Select one cells from one sites, and include all sites in the cluster, each cell
     perfrom one download test.

Test Procedures
1.   Connected PC and MS (TEMS suite), PDP active.
2.   Start auto test and recording function in TEMS.
3.   Download file from server(the size of file about 1024k BYTE).
4.   Wait 10s.
5.   Upload file to server(the size of file about 512k BYTE).
6.   Stop recording.
7.   Repeat step 2-5 on several other stationary locations.

Data record
1.   RLC Throughput DL (kbit/s).
2.   RLC Throughput UL (kbit/s)

Remarks
1. Filter out the throughput only between FTP ‘session start’ and ‘session end’,
   calculate the average value,
2. Devide the average thoughput by average used timeslot from TEMS to calculate
   per timeslot value.




                                                                                            13
14. T12 Block Error Rate - BLER (I8)


 Preset Conditions
  1.   GSM network is in normal state.
  2.   The test result is extracted from the GPRS throughput test log file.
  3.   Cells with extended range or satellite transmission are excluded.
  4.   GPRS network parameters have been optimized.
  5.   Use GPRS Coding Scheme 2 to measure the KPI.
  6.   Select one cells from one sites, and include all sites in the cluster.

 Test Procedures
 1.    Connected PC and MS(TEMS suite), PDP active , establish the trace function.
 2.    Start auto test and recording function in TEMS.
 3.    Start ftp download session from the laptop, file size is around 512k Byte.
 4.    Repeat ftp download session until get enough sampling.
 5.    Start a ftp upload session from the laptop, file size is around 256k Byte.
 6.    Stop recording.

 Data record
 1.    BLER/Timeslot (%) in TEMS
 2.    Select the timeslots which is related to PS service to calculate.
 Remarks




                                                                                     14
15. T13 Outdoor 2G Coverage (CQ1)


Preset Conditions
     1.   GSM system is in normal operation.
     2.   Network Optimization work is end.
     3.   Driver Test Tools is connect with GPS and Test MS is ready and operate
          normally.
     4.   The drive test route is ready and should be satisfied for good wireless
          coverage.
     5.   The test MS is put in the test car, The mobile set’s antennas will be outside
          the vehicle, and moved around within the predetermined drive test route.

Test Procedure
1.    Set the MS in idle mode.
2.    Start TEMS data record.

Data record
      1. Record the LOGFile,and output the Coverage Rata by post-process tool.
      2. Use 5m*5m area binning to process the data in TEMS Route Analysis

Remarks




                                                                                          15
16. T14 Receive Quality (CQ3)


Preset Conditions
     1.   GSM system is in normal operation.
     2.   Driver Test Tools is connect with GPS and Test MS is ready and operate
          normally.
     3.   The drive test route is ready and should be satisfied for good wireless
          coverage.
     4.   The test MS is put in the test car, The mobile set’s antennas will be outside.
          the vehicle, and moved around within the predetermined drive test route.
     5.   Use short call dedicated mode, call duration 50s, interval 10s.

Test Procedure
1.    Set the called party number in TEMS.
2.    Start TEMS data record.

Data record
      1. Record the LOGFile,and output the Receive Quality by post-process tool.
      2. Use 5m*5m area binning to process the data in TEMS Route Analysis




                                                                                           16
17

				
DOCUMENT INFO