Hovah Yii
RF case study
Huawei x U Mobile · 5G Swap & Mod · Malaysia · On-going

U Mobile 5G — swap & modernization traffic assurance

When U Mobile swapped and modernized its 4G sites for 5G, someone had to prove the traffic actually moved. I built HW-LTE-Traffic-Volume — a daily tool that verified the migration sector by sector and drove the field follow-up.

daily monitoring cycles
23
regional reports
46
regional dashboards
2
migration threshold
>20%
Browse this case study
01 · Overview

Proving the 5G migration, site by site

U Mobile is one of Malaysia's major mobile operators. The 5G rollout runs on a swap & modernization (Swap & Mod) workstream: live 4G sites are converted or modernized so their users can move onto the new 5G configuration.

Swap & modernization rollout

U Mobile is converting and modernizing live 4G sites so users can move onto the new 5G configuration — one site at a time, across the country.

The measurement problem

A site that changes configuration does not prove its users moved. If traffic does not shift, something is wrong — coverage, steering, or the activity itself.

The approach

Daily automated traffic-volume monitoring of every activity site, a clear >20% migration rule, and a shared follow-up list owned by the field PICs.

02 · My role

Tool owner and daily-cycle operator

I owned the measurement side of the workstream — from building the tool to keeping the daily list actionable for the field.

Built & owned the tool

Designed and built HW-LTE-Traffic-Volume end-to-end — the data rules, the filters, and the two regional dashboards.

Ran the daily cycle

Owned the full daily run for ten weeks: 23 monitoring cycles, every report verified before it was posted to the operations channel.

Coordinated the field

Kept the shared work-site list moving with the regional field PICs (SR, NR, Central, Eastern) — from daily updates to same-day defect action.

03 · The tool

HW-LTE-Traffic-Volume

A daily traffic-volume monitoring and verification tool built for the Swap & Mod workstream. Every morning it answers one question: did the users on each activity site actually move?

Input — per-sector LTE traffic volume

Sector-level LTE traffic volume for every site in the swap & modernization list, measured before and after each activity.

Flagging — the >20% rule

Sectors whose traffic reduced by more than 20% after the activity are flagged: the reduction is the signal that users have moved to the new configuration. Anomalies — for example a site stuck under optimization while still losing traffic — are flagged separately for action.

False-positive filters

Sectors already in the modernization tracker are excluded, and critical sites carrying customer comments are removed, so the daily list only ever contains new, actionable items.

Output — two daily dashboards

Regional dashboards for SR & NR and for Central & Eastern, posted to the operations channel before the start of the workday, with the shared work-site list kept current by the regional field PICs.

04 · How it works

The daily cycle

One automated run per day, published before the field starts work.

  1. 01

    Pull traffic volumes

    Sector-level LTE traffic volume for the full swap/mod site list — before and after each activity.

  2. 02

    Apply the >20% rule

    Flag sectors where post-activity traffic reduced by more than 20% — the confirmation that users shifted to the new configuration.

  3. 03

    Filter the noise

    Remove sectors already in the modernization tracker and critical sites with customer comments.

  4. 04

    Publish two dashboards

    SR & NR and Central & Eastern dashboards go to the operations channel — every morning, same cadence.

  5. 05

    Field follow-up

    Regional PICs update the shared work-site list and action items the same day.

05 · Timeline

Ten weeks of daily monitoring

  1. 03 Jun 2026

    First daily cycle

    The first two-region report (SR & NR, Central & Eastern) goes out — the daily cadence is established.

  2. 04 Jun 2026

    First anomaly caught

    A site stuck under optimization for 27 days with >20% traffic loss is flagged with the trend evidence and routed for action.

  3. 08 Jun 2026

    Reporting tightened

    Tracker-known sectors are auto-excluded from the daily list — only new, actionable detections are reported from then on.

  4. 06 Jul 2026

    COPA80 cleared, COPA90 starts

    The COPA80 site pool runs out of sites; the tool pivots to COPA90 site inputs as the next wave begins.

  5. 13 Jul 2026

    KV 4G MOD closed

    No more sites for 4G MOD in the KV workstream — regional PICs take over ownership of the remaining regions.

  6. 05 Aug 2026

    Final daily cycle

    The 23rd daily cycle of the swap/mod phase is delivered, closing the monitoring window.

  7. 27 Aug 2026

    Field defect triage

    A sector-swap direction defect is raised through the operations channel and resolved with the field team — the channel keeps working past the swap/mod window.

06 · Achievements

What the daily cycle delivered

Jun - Aug 2026

23 daily monitoring cycles

Built the tool and ran the full daily cycle from 3 Jun to 5 Aug 2026 — 46 regional reports across two regions, day after day.

From 03 Jun 2026

Automation over manual checks

Replaced manual before/after traffic verification with one automated run: pull, flag, filter, publish — delivered before the start of the workday.

13 Jul 2026

4G MOD workstream closed

The daily migration evidence underpinned the KV 4G MOD workstream reaching "no more sites" on 13 Jul 2026.

Jun & Aug 2026

Same-day anomaly detection

Caught a 27-day optimization stall with >20% traffic loss (4 Jun) and a sector-swap direction defect (27 Aug) — both routed for same-day action.

Daily cadence

Two-region coverage

Daily dashboards for SR & NR and Central & Eastern kept every regional field PIC working from the same list.

Jun - Aug 2026

Actionable output, not noise

Tracker and comment filters kept the daily list to genuinely new items — the work-site list stayed current through two months of daily operations.

07 · Tool stack

What the cycle runs on

HW-LTE-Traffic-Volume

The daily LTE traffic-volume monitoring & verification tool — built for this project

Sector-level LTE traffic data

Before/after traffic volume per sector for the swap/mod site list

Modernization tracker

Site-level master tracker, used as the false-positive filter

Shared work-site list

Cloud-based list kept current by the regional field PICs

Operations channel

Daily dashboard distribution and issue triage with the field teams

08 · Deliverables

What was produced

46 regional monitoring dashboards

SR & NR and Central & Eastern, 3 Jun - 5 Aug 2026.

Daily work-site list upkeep

The shared list kept current through the full swap/mod phase.

Anomaly & defect reports

27-day optimization stall (4 Jun) and sector-swap direction defect (27 Aug).

4G MOD close-out evidence

Migration data supporting the KV 4G MOD workstream close on 13 Jul 2026.