For vehicle OEMs targeting Saudi and Gulf markets, in‑vehicle eCall emergency‑call certification is now a threshold that cannot be ignored. OEMs and Tier‑1 suppliers entering the Middle East should plan certification projects in 2026–2027. This article – based on July 2026 current requirements – covers the regulatory framework, test items, certification process, timeline, and costs – practical, actionable information.

eCall – in‑vehicle emergency calling – after a crash, automatically or manually triggers an emergency call – transmitting vehicle location and status data to rescue dispatch – reducing response times. The EU mandated it from 2018 – Gulf countries have been adopting similar rules since 2023.

From the 2025 model year, Saudi‑bound light vehicles must be equipped with eCall systems – meeting SASO 2944:2020. Emergency number: 911 – communication module: 4G – HMI: at least Arabic and English. In June 2026, the GCC issued a notification on vehicle eCall technical requirements – covering passenger and light vehicles with ≤8 seats (excluding driver) and GVW <3,500kg.

1. Regulatory Framework

1.1 UN R144 – international framework

UN R144 – UNECE regulation on Accident Emergency Call Systems – the full title is Uniform provisions concerning the approval of motor vehicles with regard to the Accident Emergency Call System (AECS) – an international framework. Contracting parties may add local provisions.

UN R144 specifies core eCall metrics:

·Minimum Set of Data (MSD): fixed at 140 bytes – containing location, time, VIN, fuel type, estimated occupant count, etc.

·Positioning error ≤15m.

·Automatic triggering after crash – plus manual activation.

Call‑trigger logic, data format, and link‑establishment rules are consistent across contracting regions – differences are mainly in communication technology and local adaptation.

1.2 Saudi SASO 2944

SASO 2944:2020 – Saudi eCall technical requirements – adds local requirements on top of UN R144:

·Communication module: 4G mandatory.

·Emergency number: 911.

·HMI: Arabic and English.

UN R144 itself does not restrict communication technology – 3G/4G both accepted – but Saudi requires 4G. This has been debated in EU industry circles – UN R144 revisions are slow – no immediate technology restriction is expected.

Extension: SASO has postponed mandatory enforcement to 1 January 2027 – giving companies more preparation time. Note: the extension only applies to the enforcement date – for 2025 model‑year applications, technical solutions must still be designed and verified against SASO 2944.

1.3 GCC unified requirements

In June 2026, Saudi, Kuwait, UAE, Oman, Bahrain, Qatar, and Yemen jointly issued a draft GCC vehicle eCall technical requirements notification – applicable to passenger and light vehicles registered in GCC member states – with exemptions for small‑volume models.

Public consultation closes 1 August 2026 – final approval and effective dates are yet to be confirmed. Once in force, the seven GCC countries will have unified eCall technical standards. For current projects, we recommend designing against GCC unified specifications – avoiding country‑by‑country retrofits later.

  2. Core Test Items

2.1 Crash‑trigger testing

During high‑speed impacts – the eCall system must auto‑activate. Whole‑vehicle crash validation – verifying sensor signal acquisition, auto‑dialling, and data‑transmission link stability. After the crash, the system must establish an emergency call within the specified timeframe and upload the MSD.

In‑vehicle audio equipment must be impact‑resistant – clear voice communication between occupants and the rescue centre. Crash testing requires dedicated test sites and fixtures – a significant cost item – and additional test vehicles (crashed vehicles cannot be reused).

2.2 Positioning testing

Positioning accuracy is a core eCall metric.

·General: dynamic positioning error ≤150m.

·Saudi: ≤50m.

Cold‑start requirements: after power‑off/reboot – position capture within specified time. Weak‑signal scenarios (urban canyons, tunnels) are difficult to replicate in labs – road‑testing is required.

Some regions mandate multi‑constellation positioning:

·Russia ERA-GLONASS: requires GLONASS compatibility – and from 2025, BeiDou.

·Saudi/Gulf: primarily GPS – but multi‑constellation solutions are accepted.

For multi‑market vehicle models – choose multi‑constellation positioning modules – one hardware solution covers multiple regions.

2.3 Communication module testing

Communication module: must support 4G. Tests cover:

·4G voice call setup time.

·Voice quality.

·Network compatibility with major Saudi operators – not just one operator.

Co‑existence testing with the vehicle's TPS system is also required – eCall must not interfere with other electronic systems – and other systems must not affect eCall. EMC testing follows ISO 11452 for radiated immunity – ensuring stable eCall in complex electromagnetic environments. In‑vehicle interference is significant – inverters, drive motors, and mmWave radar – co‑existence failures are common.

2.4 Privacy and data protection

eCall data involves occupant privacy. Tests verify:

·Data is transmitted only during emergency‑call triggers – not during normal driving.

·All transmitted data is encrypted – preventing interception.

MSD data (VIN, real‑time location) – transmission encryption and rescue‑service data‑storage controls – all assessed.

The vehicle system must have built‑in self‑diagnostics – on vehicle power‑up, the eCall system auto‑checks the communication module, positioning unit, microphone, and speaker. If faults are found – clear driver notification is required. Silent‑failure self‑diagnostic designs are likely to be judged non‑compliant during market surveillance.

  3. Certification Process

3.1 Pre‑certification stage

Required technical documents:

·Full technical specifications (chip model, supported bands, etc.).

·Circuit schematics, BOM.

·EMC test reports.

Samples: 2–3 finished units – for lab static testing and real‑vehicle road testing.

Specification band range, antenna gain, and transmit power must match the sample hardware – mismatches = application rejected.

Existing EU eCall test reports can reduce some duplicate testing – but Saudi‑specific items are still required:

·Local operator band compatibility.

·Arabic HMI validation.

EU eCall reports cannot directly substitute for Saudi certification – emergency numbers differ (112 vs. 911) – call‑routing configuration must be adjusted.

3.2 Submission and official review

Saudi eCall certification can be submitted through local agents or consultants. SASO reviews all technical documents – after approval, the type‑approval certificate is issued.

GCC mutual recognition is still under negotiation – for now, one GCC certificate cannot cover all seven countries.

·UAE: UAE.S 5019:2018 – emergency number 999 – plus TRA telecom type approval.

·UAE and Saudi requirements differ – one set of materials cannot cover all Gulf markets. For comprehensive Gulf coverage, do country‑by‑country difference assessments.

3.3 Timeline and costs

·Saudi eCall: 8–12 weeks.

·With crash testing: longer – crash‑test facility scheduling can add 2 months.

Costs: vary by test items – full suite + certification fees – roughly USD 20,000–50,000.

Products with existing EU eCall validation can reduce costs and timelines – but 4G module adaptation and Arabic HMI are Saudi‑specific – cannot be skipped. Budget for remediation and re‑testing – first‑pass full success is rare.

3.4 NG eCall trends

The EU opened NG eCall certification in 2025 – based on 4G/5G and IMS – supporting video and dynamic vehicle data – planned for full mandatory implementation in 2027 – phasing out 2G/3G. Saudi and Gulf countries are also following NG eCall. New projects should be designed on NG architecture – avoiding near‑term hardware retrofits.

NG eCall:

·Positioning accuracy: 1–3m – GNSS + vehicle sensor fusion.

·New dynamic data: collision severity, battery status.

·Dual‑link redundancy: automatic fallback to legacy CS eCall when 4G/5G fails.

Data volume is significantly higher – video compression and cloud upload strategies must be fully validated.

For Saudi‑bound OEMs, we recommend developing directly on NG eCall architecture. SASO's current baseline only requires 4G – NG's 4G/5G native architecture perfectly matches existing 4G access standards – future upgrades won't require major hardware changes.

  4. Project Planning Recommendations

·Lock communication module selection early – determines 4G compatibility and NG upgrade headroom.

·Order crash‑test vehicles in advance – align factory schedules with test‑facility availability.

·Start document preparation from the project kick‑off – don't wait for samples.

Although Saudi enforcement has been extended to January 2027 – vehicle type‑approval cycles are long – new projects starting in mid‑2026 will land right at the mandatory deadline. Work backwards – allow at least six months buffer for testing and remediation.

For Saudi eCall certification, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.