In the automotive voice, gateway and audio module world, one question stops people short: how long does my ITU-T test report last? Not being able to answer is perfectly normal, because this does not follow the same logic as a CCC or SRRC certificate with a fixed term. ITU-T does not issue certificates. It publishes technical Recommendations, and testing is done by ISO 17025 laboratories, which produce conformity reports. Sort out that relationship first, and validity and renewal start to make sense - and the myth of a "three-year validity" stops pulling you off course.
ITU-T publishes technical Recommendations, not certificates with a validity period. Testing is carried out by ISO 17025 laboratories, which issue conformity test reports.
The reports carry no expiry date, but there are preconditions. With fixed hardware, fixed firmware and a fixed standard version, the report document itself states no expiry date, and the "three-year validity" line is a myth: the root of the issue is not time but version and rules. That said, vehicle manufacturers, OEM clients and project tenders often set their own currency requirements in the contract, for example calling for a report issued within the last two or three years - so a ten-year-old report will not necessarily slot into a new project.
Three external causes can put a report out of use: the market mandatorily retiring an old version, a client contract requiring a newer version, or a change to your own product. None of them happens on its own.
ITU-T standards do not fully retire old versions. Amendments and corrigenda keep adding to them, so old and new coexist over the long term, and invalidity always comes from outside rather than from the standard reaching a date. That is why you cannot coast on the notion that standards are not retrospective - what matters is where your device sits in its product lifecycle.
P.1100 covers narrowband, the 200 to 3,400 Hz band for automotive hands-free. The current version is the 2019 edition, iterated through amendments, and the main tests bear on echo cancellation and double-talk test models.
P.1110 covers wideband, 50 to 7,000 Hz, and automotive hands-free mainly uses it. CarPlay and Android Auto voice evaluation largely takes P.1110 as the evaluation basis, but that is a vehicle-client project delivery requirement rather than a mandatory audit item inside the Google or Apple certification systems - neither Apple nor Google directly audits ITU-T reports.
P.1120 covers super-wideband, the SWB band from 50 to 14,000 Hz - not 20 to 20,000 Hz, which is fullband and outside P.1120's coverage. It is not a CarPlay mandatory item and applies only where fullband 48 kHz sampling is used. Some overseas premium car makers do add a basic link test at vehicle access, so bandwidth alone is not a reason to leave it out.
A hardware change is the clearest trigger. A significant change to the microphone array, the speaker unit or the DSP voids the old report and calls for a full retest.
A firmware change does it too. Where echo cancellation, noise reduction or the voice codec algorithm changes, the brand platform will require the corresponding ITU-T voice cases to be retested even though the hardware has not moved.
On laboratory accreditation, ISO 17025 is a laboratory accreditation system and does not extend the scope separately for each ITU-T Recommendation version. It is enough that the laboratory's accredited scope covers the test method; only a major method change adding new equipment or methods calls for a scope extension. The idea that a standard update automatically forces a fresh scope extension overstates it.
On the report itself, an ITU-T voice report has to attach the test scenarios, the equipment list and the calibration records for the HATS head-and-torso simulator, with the version number pinned on the cover. What the brand owner audits is the version and the scenario coverage, not simply a stamp. Contracts between companies often write the current mainstream version into the terms, so a supplier that synchs version changes proactively when it changes generation is better placed than one that waits to be asked. And a report issued when the laboratory's scope did not cover the method will not be accepted. Pinning the version on the cover is the key point: the report should state which year's edition of P.1110 applies, the brand owner accepts against that version number, and versions cannot simply be substituted for one another - a version change means a fresh queued report.
There is no traditional renewal, since the report has no expiry date. Upkeep means keeping up with the brand platform and the standard version; an unchanged product is simply archived.
One standard is easily confused with the P series: ETSI EG 202 396 is another automotive hands-free voice performance standard, also recognised by some European car makers' vehicle projects, so it cannot simply be dismissed. P.1100 and P.1110 can be combined into a single report with separate sections, but confirm that the laboratory's scope covers both, and note that some car makers require separate reports - do not assume the combination will always be accepted.
For vehicle models already certified, the existing reports stay valid. New filings should use the current mainstream version. Do not take the absence of retroactivity as licence to coast - what matters is where the product sits in its lifecycle.
One reminder: the version and scenario coverage of an ITU-T voice report are what the brand owner audits, so lock the version number before the report is produced and save a remediation round. For in-car connectivity programmes, BlueAsia runs the voice workstreams in parallel, which cuts down the number of sample rounds.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
Related News
