From radio measurements to acceptance reports: the AZENQOS drive-test pipeline

1 minute read

Published:

🌐 อ่านหน้านี้เป็นภาษาไทย →

I co-founded AZENQOS and was its main developer - a mobile-network test tool, first on Symbian OS 9 and then on Android, now Sigma-AQ under Meritech Solutions. This is how measurements taken on a phone become the reports a mobile network is accepted on - it used to be a long paragraph on my About page.

The pipeline

  1. Linux kernel driver modifications on the phone, to get at the radio.
  2. Radio measurement and signalling capture and parsing.
  3. Storage into SpatiaLite on the phone - measurements with position.
  4. ETL to Parquet on the server.
  5. Dynamic reports with DataFusion + Pandas: plot-on-map, with telecom KPI calculation via Python eval in drive-test report templates.

What the reports are for

The reports are essentially test certificates computed from raw measurements. They verify that a new cell site works properly - radio, signalling, voice and data quality - before the site is accepted for delivery. They are also used to benchmark mobile network operators against each other.

AZENQOS was used by a major network equipment vendor and mobile operators in Thailand, India, Hong Kong, Latin America and beyond.

Full disclosure: this post - and any code or tool it describes - was co-authored with Claude (Anthropic’s AI, via Claude Code). I directed, guided and reviewed. I don’t want to pretend otherwise.

Leave a Comment