【正文】
August 11, 2022Jim Luan, Lin MubaoDate 1Drive Test ProcedureDrive TestNetplanFICSStatistics AnalysisProblem FindingVOT/GEPPreparation Date 2Preparation (1)? Definition File– Without it, it is impossible to observe overshooing neighbors– can convert FP to definition fileNeighbor list with definition fileNeighbor list without definition fileDate 3Preparation (2)? Frequency Plan amp。 Configuration map? Software:TEMS, FICS, GEP, VOT? Hardware: TEMS, GPS, Portable PC? Test Problem Sheet? Route? MapDate 4Drive Test? For Benchmark–2 minutes per call–10 – 15 minutes a log files–Force to appropriate band (GSM only, DCS only or Dual)? For Special Problem–Planning route–No limitationDate 5TEMS Introduction?Interface?FunctionsDate 6Log File Process TEMS Log FileNetPlanFICSVOT/GEP.Route Map.STAExcel VB.NP/.TXT Much shorter cycle time by VOT and GEP.Date 7TEMS .log file Analysis? Undecoded BCCH? BSIC Undecode in Other Site? No Handover? Delay Handover? Ping Pong Handover? Negative Handover? Overshooting? High Overlapping? No Dominant Server? Poor Coverage? Unreasonable Serving Area? Interference? Handover Failure? Handover Loss? UL Drop? Drop Call? Sudden Power Drop? MS Power Rapid IncreaseBelow lists mon problems which can be observed from Drive Test Log.Date 8Undecoded BCCH (1)Description:– BSICs can’t be decoded in 5s– Usually consider 3 strongest neighborsReason:– GCLK shift, only decode same site BSICs– Channel interference– NonBCCH carrier, no dedicated spectrum for BCCHDate 9Undecoded BCCH (2)Date 10BSIC Undecode in Other SiteDescriptio