The term "DAB certification" actually conflates two things. One is the WorldDAB voluntary logo testing – you get logo authorisation, and retailers/OEMs use it as a supply requirement. The other is the EU RED statutory market‑access – receiver RF follows ETSI EN 303 345‑4 – the legal baseline for selling in the EU. Mixing them up – clients think a WorldDAB certificate is enough for export – RED testing is missed – customs detention follows.
1.1 Account and product registration
First, register on the WorldDAB platform – submit company information, product category, and target market. Product registration requires specifications, receiver module details, and antenna configuration. Review: 1–2 weeks – then you get a product ID.
Trap: the product ID is not a testing prerequisite. The ID is used for uploading reports, applying for certificates, and trademark usage. Most accredited labs start testing first and register the ID later – saving weeks in parallel. Waiting for the ID before sending samples wastes time.
1.2 Technical document pre‑review
Before sample submission, do a technical document pre‑review – confirm product feature scope, DAB version (DAB/DAB+/DMB), and band configuration. European in‑vehicle DAB almost exclusively uses Band III (174‑240 MHz) – L‑Band (1452‑1492 MHz) is only used in a few regions. Testing all bands blindly drives up costs.
2. DAB Certification – Conformance Testing Phase
2.1 RF performance testing
Receiver RF tests: sensitivity, selectivity, adjacent‑channel rejection, intermodulation rejection. The receiver RF standard is ETSI EN 303 345‑4 – the RED harmonised standard. EN 300 401 is a transmitter standard – for broadcast base stations – using it for receivers makes the report invalid.
RF testing: 1–2 weeks. Sensitivity non‑conformance is the #1 failure – directly tied to antenna matching circuit and front‑end filter design. Remediation requires hardware changes – timeline extends.
2.2 Protocol conformance testing
Protocol layer tests: FIC, MSC, PAD data structure parsing – inject standard streams and verify output. 2–3 weeks – depending on product feature complexity.
DAB+ adds AAC audio decoding verification compared to DAB. If your product supports both DAB+ and DAB, the test scope is fully covered – there is no fixed "3–5 days extra" difference. Do not hardcode this number into budgets.
2.3 Lab scheduling
Labs with full DAB conformance test capability are limited globally – RadioMX (Europe), NMMA (Germany) are key players. Domestic labs with WorldDAB‑accredited receiver testing are very few – many can only do pre‑testing – not formal reports accepted for upload. Confirm that the lab's report is accepted by the platform before submitting.
DAB protocol testers are globally scarce – peak‑season queue waits can be 2–4 weeks. Single‑item retest scheduling: 7–14 days – not a few days.
3. DAB Certification – Application and Issuance
3.1 Test report submission
After all tests pass, the lab issues a conformance report – submit to the WorldDAB platform for certificate application.
Emphasis: a WorldDAB certificate is not a statutory market‑access document. The UK, Germany, and Norway legally require RED CE compliance (EN 303 345‑4). There is no such thing as "ZMK DAB certification" or "NKOM DAB special certification" – NKOM is the Norwegian communications regulator – not a DAB certification. Automotive Tier‑1s – do not be pushed into unnecessary country‑specific certifications.
3.2 Certificate issuance
WorldDAB certificate issuance: 1–2 weeks. One report covers multiple WorldDAB‑recognised markets. If your target market accepts WorldDAB reports as a supply requirement – one report is sufficient.
4. DAB Certification – Variables Affecting Timeline
4.1 Product maturity
Mature solutions with properly tuned antenna matching – high first‑pass rate. Immature solutions – sensitivity borderline, protocol parsing bugs – repeated remediation and retesting – timeline doubles or more.
4.2 In‑vehicle integration impact
For standalone DAB modules or head‑unit components – WorldDAB or RED testing – standard test antennas are sufficient. Only during whole‑vehicle WVTA type approval are vehicle‑level chamber environments required to simulate in‑vehicle antennas. Module manufacturers – do not allocate extra whole‑vehicle testing time unnecessarily.
4.3 Firmware change management
WorldDAB certificates have version management. Firmware changes affecting FIC/MSC parsing or audio decoding – require a change assessment. Major changes require retesting – do not assume the certificate is permanent.
4.4 Module derivation path
If a module already holds a WorldDAB report, the whole product can apply for derivation – testing scope is significantly reduced – timeline cut. Most people miss this acceleration route.
5. DAB Certification – Timeline Compression Recommendations
5.1 Pre‑testing
Before formal submission, run pre‑tests with a DAB tester – sensitivity, selectivity, audio decoding – identify issues early. Products that pass pre‑tests have a higher first‑pass rate – saving 2–3 weeks of retesting.
5.2 Parallel execution
Run WorldDAB registration concurrently with document preparation. Schedule lab tests concurrently with document pre‑review. Prepare certification materials during testing. With full parallelisation, the fastest WorldDAB certificate can be obtained in 6 weeks – provided first‑pass, zero remediation, and documents pass review first time. Repeated remediation – 4 months or more.
For DAB certification timelines, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
Related News
