Plan the right test
Confirm route, operator, RAT, direction, test case, access, vehicle, people, timing, and the latest customer-approved scope.
Hovah Yii
RAN field playbook
Huawei × MobiFone Vietnam · Hanoi · 2026
Hanoi drive test field guide
An intern-ready operating guide for moving from a tentative plan to a safe field run, complete logs, actionable analysis, and a customer-ready report.
Core tools: PHU · PHU Assistant Lite · OsmAnd · Tracklia
- VIP benchmark routes
- 9
- Operators compared
- 3
- LTE and NR
- 4G + 5G
- Core test scope
- UL · DL · MOS
KMZ route preview
“test path 1” · 14 points
Start: 21.0180095, 105.8296793
End: 21.0161248, 105.8321694
Browse this guide
Authorized project use
This page consolidates a project handover dated 1 September 2026. Group IDs, account IDs, test identifiers, routes, and issue counts are historical operational references. Verify them in WeLink before acting, follow Huawei and MobiFone information-security rules, and never forward logs, customer data, access photos, credentials, or restricted-site details outside approved channels.
01 · Mission and context
What an intern is expected to deliver
A drive test is complete only when the route is covered, the requested test cases are valid, the raw evidence is safe, the team can find it, and the report explains what should happen next.
Collect trustworthy evidence
Maintain GPS lock and continuous logging; capture RSRP, SINR, PCI, throughput, events, BasicInfo, screenshots, and trace IDs where required.
Close the loop
Upload promptly, state incomplete items visibly, request analysis, include root cause and optimization suggestions, and track every dependency to confirmation.
Project scope captured in the handover
Essential vocabulary
DTDrive Test
A mobile field measurement along a planned road or indoor route.
CDTContinuous / walk drive test
A moving test that follows a route or floor map while the logger records continuously.
CQTCall Quality Test
A fixed-point campaign covering accessibility, retainability, coverage, RxQual, one-way audio/crosstalk, and voice quality.
MOSMean Opinion Score
A voice-quality KPI, usually 1–5. The handover treats ≥3.0 as acceptable and ≥4.0 as good; always follow the current customer threshold.
FTP DL / ULDownlink / uplink throughput
File-transfer tests used to measure user-plane speed and stability.
RSRPReference Signal Received Power
A primary LTE/NR coverage-strength KPI.
SINRSignal-to-Interference-plus-Noise Ratio
A quality KPI that helps distinguish weak coverage from interference.
PCIPhysical Cell ID
Identifies the serving or detected cell and helps reveal handover, overlap, and pollution behavior.
IBCIn-building coverage
The indoor coverage layer; compare IBC serving behavior with outdoor macro coverage.
BasicInfoRadio information screen
Capture LTE and NR serving-cell details at the same place and time as a static or speed test.
VUE TraceNetwork-side UE trace
A trace used when deeper analysis is required; record the trace ID and exact test window.
02 · Required tool stack
Know which tool owns each part of the job
PHU collects the field evidence, PHU Assistant Lite checks the logs, and OsmAnd or Tracklia keeps the team on the approved route. A navigation app never replaces the drive-test logger.
Primary field collection
PHU
Use the approved Huawei PHU project and task to run the assigned LTE/NR, FTP, idle, voice, or mobility test and record the radio/GPS log.
- Sync the correct project and assigned task.
- Map one accepted task to the correct phone/UE.
- Verify GPS, SIM/operator, RAT/test script, storage, and log-size settings.
- Watch task state and recording health throughout the route.
Post-test log verification
PHU Assistant Lite
Open the PHU log after the run to check route continuity, events, RSRP, SINR, PCI, throughput, test status, and whether the file is suitable for upload and reporting.
- Confirm the expected KPIs and map trace are present.
- Identify gaps, wrong RAT/operator, failed service, or invalid trials.
- Use the project-approved workspace/profile and export settings.
- Do not modify or delete the only raw copy of a log.
Offline route following
OsmAnd
Correct product spelling; sometimes written “OmsAnd” in team messages.
Import the project KML/KMZ, which OsmAnd converts to a GPX track, download the Hanoi offline map, and use Follow track so the driver can see the approved path without depending on mobile data.
- Check the imported start/end and travel direction.
- Keep the original geometry visible; do not snap it to roads unless the plan owner approves.
- Use offline maps as a resilience measure.
- Record detours in the DT event notes, not only in the navigation app.
Route inspection and repair
Tracklia
Use Tracklia on Android to import, inspect, combine, or carefully edit GPX/KML/KMZ tracks and waypoints. It is especially useful when a supplied path needs checking before field execution.
- Inspect every point and segment before departure.
- Keep an untouched copy of the customer route.
- Export the corrected route only after approval.
- Use it for route data—not as the RF measurement source.
STEP 1
Route file
Open and verify in OsmAnd or Tracklia.
STEP 2
Field task
Collect the assigned test in PHU.
STEP 3
Log QA
Inspect the result in PHU Assistant Lite.
STEP 4
Delivery
Back up, upload, analyze, and report.
PHU and PHU Assistant Lite are project-controlled Huawei tools. Screens, task names, permissions, and menus vary by build; use the current project APK/license/profile and the team’s approved SOP.
03 · Field runbook
One checklist, organized by field phase
This replaces the repeated workflow and checklist sections. Run it top to bottom for benchmark routes, walk tests, store tests, and VIP complaint verification.
Before departure
- 1Confirm the latest route, operator × RAT × test-case matrix, direction, deadline, and report owner.
- 2Import the KML/KMZ into OsmAnd or Tracklia; verify start, end, direction, closures, and an alternate path.
- 3Secure restricted-area access, field partner, vehicle, driver, meeting point, and test window.
- 4Charge and label every phone; map each UE to its SIM, operator, RAT, and PHU task.
- 5Prove SIM balance/quota, 4G/5G registration, data service, and VoLTE/MOS function with a real test.
- 6Open PHU, sync the correct project/task, check GPS, storage, time, license, script, and log-size settings.
- 7Send the tentative plan and state that it may change.
During collection
- 1Run a short proof log, then confirm PHU is recording, GPS is stable, and the correct task is active.
- 2Follow the approved track in OsmAnd/Tracklia while watching PHU for gaps, crashes, heat, or storage errors.
- 3Record every deviation or anomaly with time, location, reason, impact, and retest need.
- 4Capture BasicInfo/screenshots at static points and repeat inconsistent trials two or three times.
- 5The driver drives; the tester operates the phones and logger.
Before close-out
- 1Before leaving, compare the PHU trace and task matrix with the planned route and confirm no log is truncated.
- 2Back up raw logs, then inspect them in PHU Assistant Lite for route continuity, KPI visibility, and valid trials.
- 3Upload to the approved dated folder, share the exact path, and identify incomplete or retest items.
- 4Notify analysis/report owners; include the issue, suspected cause, evidence, next action, owner, and due time.
- 5Recharge and hand over every phone, SIM, cable, power bank, and key.
SIM pre-flight
Correct operator
Enough balance/quota
4G/5G registers
VoLTE/MOS works
Correct phone/slot
Real traffic passes
28 Aug snapshot: two VNPT data + two voice SIMs; two Viettel data + two voice SIMs; MobiFone SIMs available at stores. Reconfirm current inventory.
Known equipment references
- Collection / QA
- PHU · PHU Assistant Lite
- Route apps
- OsmAnd · Tracklia
- Log format
- .gen.zip
- Handover DT phone
- 841212953022
- Recorded VUE trace
- 977718
Stop and escalate when validity or safety is at risk
Wrong SIM/task, no GPS, broken PHU logging, unknown RAT lock, expired access, unsafe traffic, missing permission, or an unapproved route change are stop conditions.
04 · Execution recipes
How to run each test method
Use the same discipline—exact location, known configuration, synchronized evidence, and repeatable naming—while adapting the movement pattern and KPI focus.
Indoor static test · CQT
- 1.Stand at the agreed counter, desk, or marked point.
- 2.Record floor, exact position, operator, UE, time, and indoor/outdoor condition.
- 3.Run the requested 4G and 5G FTP DL/UL or idle cases.
- 4.Run two to three trials when results vary.
- 5.Capture LTE and NR BasicInfo and any customer-visible symptom.
- 6.Start VUE trace when requested and record the trace ID and test window.
Walk test · CDT
- 1.Load the current floor map/KMZ and identify public versus restricted areas.
- 2.Start only after GPS/position and logger status are stable.
- 3.Walk at a steady pace; do not cut corners or skip wings without a note.
- 4.Run separate 4G/5G and DL/UL tasks as required.
- 5.Mark macro-to-IBC handovers, coverage holes, route mismatch, and inaccessible areas.
- 6.Upload each floor/test case separately and label pre- or post-optimization.
Outdoor benchmark route
- 1.Verify the exact start/end direction and route version with the plan owner.
- 2.Map each phone to operator, RAT, and test case before entering the vehicle.
- 3.Run a short start-point proof log, then follow the KML.
- 4.Keep the tester—not the driver—responsible for devices and event notes.
- 5.Record detours and missed turns; they change time and spatial comparability.
- 6.At the end, reconcile the operator × RAT × UL/DL/MOS matrix before leaving.
Ookla 5G store test
- 1.The handover specifies 5G speed tests at both indoor and outdoor positions.
- 2.Confirm real NR connection; a 5G icon alone may be “false 5G.”
- 3.Capture download, upload, latency, server, time, and location.
- 4.Capture LTE/NR BasicInfo at the same position.
- 5.Compare indoor and outdoor results before concluding that coverage is weak.
- 6.Escalate persistent indoor gaps to VIP care and optimization.
Minimum evidence package
Spatial
KML/floor map, trace, direction, start/end time, deviations, public/restricted coverage.
Radio and service
Operator, RAT, band/lock, RSRP, SINR, PCI, throughput, latency, drops, MOS, BasicInfo.
Traceability
UE/SIM mapping, test-case name, raw log, screenshot, VUE trace ID, event notes, valid-trial marker.
05 · Benchmark control
Nine-route benchmark matrix
The 29–31 August benchmark compared Viettel, MobiFone, and Vinaphone across LTE/NR FTP UL/DL. MOS remained incomplete because voice-test SIMs malfunctioned.
| Route | Description | FTP status | Operational note |
|---|---|---|---|
| 1 | MobiFone Office → Government Office | Completed | FTP UL/DL completed; MOS pending in the 29–31 Aug run. |
| 2 | MobiFone Office → MPS Branch Office | Completed | Also recorded as a pre-FTPDL benchmark on 30 Aug. |
| 3 | MobiFone Office → MPS HQ | Completed | The handover history also records Route 3 to Government Office; verify the latest route master before departure. |
| 4 | MPS Branch Office → MPS HQ | Completed | Pre-FTPDL benchmark recorded on 30 Aug. |
| 5 | MPS Branch Office → Government Office | Completed | Pre-FTPDL benchmark recorded on 30 Aug. |
| 6 | MobiFone Office → Northern MobiFone Network Center | Completed | Separate pre-FTPDL and pre-FTPUL runs recorded on 30 Aug. |
| 7 | MPS HQ → Government Office | Completed | Separate FTP DL and FTP UL runs recorded on 31 Aug. |
| 8 | MPS HQ → Vinhomes Riverside | Retest | FTP UL completed; FTP DL blocked by low Viettel 4G / VNPT 4G balance. |
| 9 | MPS HQ → National Data Center | Completed | Longest route: about 2.5 hours; consider splitting the segment or reducing test scope. |
Route quality-control matrix
Before leaving the endpoint, mark every required combination—not just the route—as complete.
Viettel LTE
Viettel NR
MobiFone LTE
MobiFone NR
Vinaphone LTE
Vinaphone NR
FTP UL
FTP DL
MOS / VoLTE
Event notes
Route trace
Upload path
06 · August 2026 lessons
Real cases and what they teach
Use these examples to recognize common failure patterns: false 5G, macro cross-coverage, interference, access constraints, incomplete reporting, and missing resource follow-up.
16 Aug
Noi Bai Airport T2 · Shop 1 / Shop 2 uplink
Shop 1 improved after optimization. Shop 2 remained below the >10 Mbps UL target. A nearby VNPT antenna was about 12–15 m horizontally from the referenced building floor; the team requested interference and load checks.
Intern takeaway
Do multiple static trials, preserve comparison points, and do not call the problem solved when one location improves.
13 & 19 Aug
MobiFone store · 21B Ba La
Indoor 5G was poor or absent while outdoor service was normal. One screenshot showed a 5G icon without a real NR connection.
Intern takeaway
Verify serving NR in BasicInfo. An icon is not proof of a 5G bearer. Compare indoor and outdoor under the same evidence package.
20 Aug
MobiFone store · 16 Dien Bien Phu
Indoor and outdoor 5G Speedtest plus FTP DL were collected at 21.0298, 105.8422 and combined with Ba La into one report.
Intern takeaway
Keep location identity and indoor/outdoor context clear when several stores share one deliverable.
25 Aug
Noi Bai Airport T1 · post-optimization walk test
Public areas on floors 1–3 were tested with 4G and 5G FTP DL. IBC improved, but some areas still handed over to macro. Restricted access had expired; Floor 3 public-area shape differed from the PPTX. 3G was not tested.
Intern takeaway
Report actual access and route coverage, state untested layers, and reconcile map mismatches before interpreting coverage.
26 Aug
VIP Cluster 21 · Riverside complaint
Immediate DT required a local MobiFone staff member because interns could not enter the VIP area.
Intern takeaway
Access is a test dependency. Coordinate through Phan Tuan Anh and never attempt unapproved entry.
27–28 Aug
VIP residential complaint report
The report showed poor 4G/5G coverage but initially lacked analysis and optimization suggestions. The suspected root cause was severe cross-coverage; post-DT optimization was pending and relocation/transmission work was needed first.
Intern takeaway
A customer report needs cause, evidence, proposed action, dependency, owner, and next verification—not screenshots alone.
29 Aug–1 Sep
VIP nine-road benchmark
Most LTE/NR FTP UL/DL completed across three operators. Route 8 FTP DL failed because of low balance; all MOS tests failed because voice SIMs malfunctioned; Route 9 took about 2.5 hours and a missed turn added distance.
Intern takeaway
Test SIM balance and MOS function before departure, split long routes, brief the driver, and keep incomplete cells visibly red with a reason.
07 · Communication and reporting
Make the result easy to scan and act on
The source notes use a fixed six-block email structure, an operator-by-RAT status table, explicit failure colors, and a report template aligned before customer output.
1
Greeting + overview
State whether this is a plan, result, or update. For plans: “This is just a plan (tentative) and may change.”
2
Change / precondition
Explain route, timing, access, SIM, vehicle, or scope changes before the table.
3
Test-plan/result table
Use No. · Route · Operator · RAT · Test case · Status · Remarks. Expand every route by operator and LTE/NR.
4
Reference images
Attach or CID-inline route maps, floor plans, BasicInfo, and screenshots with clear captions.
5
Vehicle / people / time
List driver, testers, field partner, start/end time, and access contact when relevant.
6
Notice + action + signature
State the one core request, owner, deadline, disclaimer, and fixed signature.
Result email pattern
Lead with the conclusion, then show the matrix
Subject: VIP 9 Road Benchmark Drive Test Result (29–31 Aug) – Viettel / MobiFone / Vinaphone
Opening: Please find below the benchmark drive test result for VIP 9 Road conducted from 29 to 31 Aug 2026, covering three operators: Viettel, MobiFone and Vinaphone.
Complete
Green ✓
Green ✓
Not tested
Red ✗
Red ✗
Incomplete
Reason in remarks
Reason in remarks
Action wording: Route 8 FTP DL could not be completed because the Viettel 4G and VNPT 4G SIM cards had insufficient balance. New SIM cards have been requested; arrange the retest when availability is confirmed.
Rule: The table carries the complete facts. The body carries the conclusion, risk, and one actionable request.
Report templates
- Primary: Standard Template for VIP T1 Assurance_20260810 V1.pptx
- Statistics reference: MBF RF Performance_20260808.pptx
- Both front-line and GSC teams produce reports. Confirm the latest version before editing.
- Customer output must include poor-area analysis and optimization suggestions.
Pre-send gate
- Correct subject and recipients
- Latest route and report template
- Status colors match facts
- Failure reason in remarks
- Analysis and optimization
- Owner and follow-up date
- Images render in Outlook
- Fixed signature and disclaimer
08 · Operational directory
Where work lives and who closes it
Use role-based escalation first, then confirm the current person and account in WeLink. Never assume a historical contact still owns the task.
DT Management
936714420879622473
Main coordination group for all drive-test activity.
10/08–16/08 Drive Test Record
997212977222389807
Noi Bai Airport T2 shop testing.
Hanoi Airport DT Assurance
994063112594419792
Airport T1 assurance and MobiFone store testing.
Approved log path
Group Space > DT Management > North > Benchmark DT Log > [date] > [location]Open the handover Onebox location | Name | Account | Role | Use this contact for |
|---|---|---|---|
| Miao Peiqian | m00907087 | RF Delivery Leader | Direct leader for DT tasks; interference, load, and RF follow-up. |
| Ouyang Changjun | o60125604 | Delivery Leader | Overall delivery, VIP complaints, MobiFone coordination, and SIM purchase arrangement. |
| Hoang Minh Thao | h00708566 | Local MobiFone RF | Approves DT plans and reviews reports before customer delivery. |
| Phan Tuan Anh | p60120025 | Local engineer | Coordinates MobiFone/VIP access and tracks cross-feeder updates. |
| Su Xiaobo | s00921749 | GSC engineer | Performs log analysis and report writing. |
| Nguyen Ha Phan | n50066043 | Local engineer | Field-testing partner. |
| Phan Truong Khang | p50065883 | Local engineer | Field-testing partner. |
| Luo Yanyang | l00947656 | RF engineer | VIP complaint testing and Riverside DT support. |
Open issue register · 27–28 Aug snapshot
ITC cross-feeder
64 issued · 40 resolved · historical counts do not fully reconcile; confirm current tracker.
MobiFone-S cross-feeder
75 issued · 66 resolved.
ITC hardware
93 issued · 36 resolved.
MobiFone-S hardware
51 issued · 27 resolved.
The handover totals 104 pending items. Phan Tuan Anh supplied ongoing updates.
Outstanding handover actions
CQT report retest
Installation-quality issues require a retest.
VIP residential analysis
Add optimization suggestions and address relocation/transmission dependencies.
Shop 2 uplink
Interference and load check requested; target was >10 Mbps.
Route 8 FTP DL
Wait for confirmed Viettel/VNPT SIM balance.
MOS for routes 1–9
Replace or repair voice/MOS SIMs, then complete all operators.
Fast escalation map
VIP access
Phan Tuan Anh · send access documents only through approved channels.
Site on-air check
Nguyen Trong Giap · 00079600; also check [War Room] MBF 5G project – Ha Noi cutover.
More SIMs
Ouyang Changjun coordinates with Dang Hong Quan / Thai Huu Tuan Ha.
Interference / load
Miao Peiqian for RF checks; Su Xiaobo for log analysis.
09 · Original handover files
Download the working references
Use the live team workspace as the operational source of truth. These files are the dated references used to build this guide.
MarkdownDT handover documentDetailed August 2026 project history, groups, contacts, methods, storage, equipment, and open items.ExcelDrive test checklistThe before, during, and after field checklist in an editable workbook.WordVIP 9 road field notesChinese-language benchmark retrospective covering routes, SIM failures, email structure, MOS/CQT, and follow-up actions.KMZTest routeThe original KMZ route named “test path 1,” containing 14 coordinate points.
Before you leave for the field
If the route, SIM, access, logger, and owner are not confirmed, the test is not ready.
Scope confirmedSIM provenAccess approvedRoute openedLogger validatedUpload owner named