Is PTCRB or GCF enough to run on the Vodafone network?

No. PTCRB and GCF attest 3GPP radio conformance. Vodafone layers its own Global IoT acceptance programme on top to verify interoperability with its core network, APNs, the GDSP (Global Data Service Platform), the Vodafone eSIM profile and the device behaviour under PSM, eDRX and NIDD. Without that acceptance, the device may attach in partner roaming but it is not qualified for a deployment on the Vodafone connectivity bill of materials.

What is the difference between Vodafone Business IoT and the GDSP?

Vodafone Business IoT designates the commercial division that sells IoT connectivity (SIM, eSIM, global contracts, application IoT Hub). GDSP, the Global Data Service Platform, is the underlying technical platform that drives activation, consumption tracking, diagnostics, the Vodafone SM-DP+ and multi-MNO and MVNO orchestration. Device acceptance primarily targets device behaviour on GDSP, not only on the radio network.

Should I implement SGP.22 or SGP.32 for an IoT product on Vodafone?

Vodafone aligns its acceptance on SGP.22 (consumer RSP, eSIM with local LPA) for products with a user interface, and on SGP.32 (IoT RSP, eIM role) for headless products and industrial fleets. Legacy SGP.02 designs (M2M push-mode) are being retired on Vodafone, with retirement windows communicated to GDSP customers. Picking SGP.22 on a headless product creates an activation UX problem; picking SGP.32 without a conformant IPAd blocks acceptance.

What is the status of 3G networks on Vodafone?

The schedule varies by country. Vodafone Germany switched off 3G in 2021, Vodafone UK has scheduled a national 3G sunset, Vodafone Italy and Vodafone Spain have published their own roadmaps. A device dependent on a 3G UMTS fallback for voice or data is no longer viable on most European Vodafone networks today. Designs should target LTE Cat-1, LTE-M or NB-IoT as primary coverage, with 2G GSM only where it is still maintained.

Is NIDD mandatory in NB-IoT on Vodafone?

No, but it is very frequently tested at acceptance. NIDD (Non-IP Data Delivery) allows small payloads to be exchanged via SCEF without an IP stack on the device, saving power and reducing signalling. Vodafone supports NIDD on GDSP for NB-IoT profiles, and acceptance verifies that the device-side configuration is coherent with the provisioned APN profile. NIDD enabled at profile level but not implemented in firmware is a classic acceptance failure.

What does the Vodafone IoT Hub cover?

The IoT Hub is the application brick of Vodafone Business IoT that aggregates IoT streams on top of GDSP connectivity. It exposes MQTT, HTTP and CoAP, handles routing and transformation rules, and maps to customer cloud platforms (Azure, AWS, GCP). Device acceptance does not validate the IoT Hub itself; it verifies that the device can connect securely to it if the customer integrates that brick, or that it can push directly to its own cloud via the Vodafone APN.

What external certifications does Vodafone require on top of its acceptance?

Vodafone requires a module or device already certified [PTCRB](/en/ptcrb/) for North America when targeted, GCF for the rest of the world, and the applicable national radio approvals per target country (CE and RED for Europe, FCC for the United States, ISED for Canada, ACMA for Australia and so on). Vodafone acceptance sits on top, it replaces neither the 3GPP radio passport nor the national regulatory marking.

Why does acceptance often fail on PSM and eDRX?

Because PSM (Power Saving Mode) and eDRX (extended Discontinuous Reception) parameters are negotiated between device and network, and the default device configuration does not always match the values supported by the provisioned Vodafone profile. Typical outcome, the device requests T3324 or T3412 timers that are too long, the network refuses, the device falls back into permanent connected mode and power consumption explodes; or PSM exit fails and the device becomes unreachable. Acceptance specifically tests these transitions.

Vodafone Global IoT: device acceptance and eSIM

Author Hugues Orgitello Last updated 27 May 2026 ~12 min read

Guide · Vodafone Global IoT

Vodafone Group operates one of the largest global IoT networks through Vodafone Business IoT and the Global Data Service Platform (GDSP). A cellular device intended to roam on Vodafone networks (United Kingdom, Germany, Italy, Spain, plus the partner-roaming mesh) typically needs a Vodafone Global IoT device acceptance on top of PTCRB or GCF certification and the relevant national radio approvals. This page situates the programme against 3GPP certifications, describes GDSP and the IoT Hub, details the SGP.22 and SGP.32 eUICC requirements, and lists the pitfalls that delay multi-country deployments.

Topic timeline

Vodafone structured its IoT offer around GDSP from the mid-2010s, a platform inherited from the Cable & Wireless acquisition and then deeply refactored. The 2023 to 2025 shift moved the technical centre of gravity onto IoT eSIM (GSMA SGP.32 specification), the generalisation of NB-IoT and LTE-M as managed coverage, and the progressive sunset of 3G UMTS in several European countries. Vodafone device acceptance reflects this trajectory: 2025 and 2026 test plans emphasise power-saving modes (PSM, eDRX), IoT eSIM provisioning, and device behaviour under Vodafone APN and NIDD policies.

Vodafone Business IoT and GDSP, the right split

Three distinct bricks must be set before discussing acceptance.

Brick	Role	Technical status
Vodafone Business IoT	Commercial division: contracts, SIM, eSIM, support, IoT Hub	Business layer
GDSP (Global Data Service Platform)	Connectivity management platform, activation, diagnostics, SM-DP+	Network and connectivity layer
Vodafone IoT Hub	MQTT and HTTP application brick above GDSP	Optional application layer

Device acceptance primarily targets the GDSP layer. It validates that the device knows how to attach, activate, manage its eSIM profile and respect the APN policies provisioned by GDSP. The IoT Hub is commercially optional: any customer can choose to pull traffic to their own cloud via the Vodafone APN, without IoT Hub.

GDSP differs from a classic MNO core network because it aggregates Vodafone as MNO (UK, Germany, Italy, Spain, Portugal, Netherlands, Ireland, Romania, Greece, Turkey, Egypt, South Africa) and a wide MVNO and partner-roaming mesh. The Vodafone eSIM profile delivered by GDSP gives access to that mesh via a single multi-IMSI profile or via internal orchestration rules, without requiring local profiles per country.

Vodafone acceptance vs PTCRB and GCF

PTCRB and GCF are carrier consortia that certify radio conformance. Vodafone recognises these certifications as prerequisites but adds its own programme on top.

Criterion	PTCRB	GCF	Vodafone acceptance
Nature	North American carrier consortium	Global carrier consortium (Europe, APAC, Middle East)	Vodafone-specific programme
Reference	PTCRB test plans on 3GPP TS 36.521 and TS 38.521	GCF test cases derived from 3GPP	Vodafone IoT test plan (superset)
Scope	Multi-carrier radio conformance, US and Canada	Multi-carrier radio conformance, global	Vodafone network interop, GDSP, eUICC, NIDD, PSM, eDRX, APN
Identifier	PTCRB EPC	GCF Field Trial ID	Vodafone device acceptance ID
Required to deploy on Vodafone	Recommended (often required for the US zone)	Yes for the covered markets	Yes, in addition

A simple reading: PTCRB and GCF certify that the radio respects 3GPP. Vodafone acceptance certifies that the device and its eSIM profile work on GDSP and across the group's MNOs. The second requires the first; the first does not include the second. For the broader EU and US sequencing, see EU and US dual certification.

Vodafone Global SIM, eUICC and the RSP flow

The 2025 to 2026 device acceptance is strongly eSIM-oriented. Vodafone provides several SIM form factors, the traditional multi-IMSI physical SIM remaining available for some contracts but eUICC being the target scenario for any multi-country deployment.

Two relevant GSMA references

GSMA SGP.22: Consumer RSP. The device has a local LPA (LPAd), downloads a profile from the SM-DP+ via QR code or application, manages enable, disable and delete locally. Relevant for IoT products with a screen or UI (industrial tablets, POS terminals, connected medical devices with UI).
GSMA SGP.32: IoT RSP. Designed for large fleets and headless devices. Introduces the eIM (eSIM IoT Manager) which remotely orchestrates profile operations, and the split between IPAd (IoT Profile Assistant device) and IPAe (IoT Profile Assistant eUICC).

Vodafone aligns its acceptance on SGP.22 for products with UI and on SGP.32 for headless products. Legacy SGP.02 designs (M2M push-mode) are being retired on GDSP, with windows communicated to existing customers.

Simplified RSP flow on GDSP

The device contains a GSMA-certified eUICC, empty or with a bootstrap profile.
At boot, on eIM command (SGP.32) or user trigger (SGP.22), the LPAd or IPAd contacts the Vodafone SM-DP+ (specific URL and root certificate).
ES9+ (on the SM-DP+ side) and ES10b (on the eUICC side) drive profile download and installation.
The Vodafone profile carries the IMSI, credentials, provisioned APNs (notably data APN, NIDD APN, management APN), roaming policies and the MNO selection rule.
The device attaches to the most relevant Vodafone network per rule and opens its data session on the provisioned APN.

Vodafone SM-DP+ and IoT Manager

The Vodafone SM-DP+ is part of the GDSP infrastructure. Device acceptance verifies:

ability to set up a conformant ES9+ TLS session with the SM-DP+ (cipher suites, root certificate);
correct reading of the Vodafone profile metadata, notably mode indicators (consumer or IoT) and default APNs;
correct activation sequence after download (profile enable, attach, APN session opening);
clean rollback on network failure during download (no hardware lockup, actionable log);
for SGP.32, ability to receive and execute eIM orders (download, enable, disable, delete) without user intervention.

On the eUICC chip side, the component must be SAS-UP certified and the eUICC OS must support the functions called by the device-side LPA or IPA. An SGP.22 eUICC on Vodafone typically also requires an SGP.22-conformant LPA on the product side (LPAd integrated in the module, or third-party certified implementation).

Acceptance test categories

The Vodafone IoT test plan groups into five main families. The structure is close to that of other IoT carrier programmes (cf. Verizon OPC) but with a specific emphasis on multi-country coverage and roaming behaviour.

1. Radio conformance (inherited)

PTCRB or GCF is consumed as a prerequisite. Vodafone does not re-execute these tests but requires the report and the band scope. Any band gap (band useful in a target Vodafone country but not covered in the PTCRB or GCF report) must be closed before acceptance.

2. Network behaviour and roaming

This is the most Vodafone-specific category:

attach behaviour on the primary Vodafone MNO of the target country;
inter-Vodafone-MNO roaming behaviour (UK to Germany for example) without eSIM renegotiation;
partner roaming behaviour in countries without a Vodafone MNO (USA via partners, Asia via Vodafone Partner Markets);
initial attach time and re-attach after reset;
re-selection behaviour after extended signal loss;
PLMN locking management when Vodafone enforces it (specific case for some GDSP profiles).

3. APN and data

Acceptance checks that the device respects the APNs provisioned by GDSP:

session opening on the default Vodafone data APN;
switch to management or NIDD APN per profile;
no attempt to use a non-provisioned APN (frequent case when a device reuses a hard-coded APN in firmware);
behaviour when the provisioned APN changes after an OTA profile update.

4. Power optimisation: PSM, eDRX, NIDD

Low-power modes sit at the heart of the modern IoT test plan.

Mechanism	Goal	Key parameter	Acceptance risk
PSM (Power Saving Mode)	Deep sleep with retained context	T3324 and T3412 timers	Requested values incompatible with GDSP profile, faulty PSM exit
eDRX (extended Discontinuous Reception)	Spaced paging windows	eDRX cycle value	Cycle too long for application SLA, lost reachability
NIDD (Non-IP Data Delivery)	Short payloads via SCEF, no device-side IP stack	NIDD APN, payload size	Enabled at profile but not implemented in firmware
Cat-M and NB-IoT band selection	Target radio technology choice	Priority band list	Selection not aligned with Vodafone country coverage

Acceptance tests the transitions: PSM entry, PSM exit on timer or Mobile Terminated trigger, eDRX cycle negotiation, NIDD session open and close. An incoherent configuration between firmware and eSIM profile is a very common acceptance blocker here.

5. Security and provisioning

The product must demonstrate secure provisioning: no plain-text credentials, correct Vodafone SM-DP+ certificate management, isolation of the test profile during acceptance, and factory settings disposed for clean production activation.

Vodafone IoT Hub, application brick

The IoT Hub is not mandatory in device acceptance but is worth situating because many Vodafone customers integrate it into their connectivity bill of materials.

The IoT Hub typically exposes:

MQTT and HTTP ingestion, sometimes CoAP for NB-IoT profiles;
message routing and transformation rules;
bridges to customer clouds (Azure IoT Hub, AWS IoT Core, Google Cloud IoT, industrial platforms);
fleet health visualisation (session state, position, last connection) integrated with GDSP;
device certificate management when the customer requires TLS mutual authentication.

For a device targeting the IoT Hub, acceptance adds an end-to-end application validation: TLS handshake, payload format, disconnect handling, coverage-loss behaviour. For a device preferring to push directly to its own cloud via the Vodafone APN, the IoT Hub is not evaluated.

End-of-life of cellular technologies on Vodafone

The horizon differs by country.

Country	2G GSM	3G UMTS	Note
Germany	Maintained for IoT and legacy use	Switched off in 2021	Cat-1 and NB-IoT recommended
United Kingdom	Industry alignment on national sunset in progress	Sunset schedule published	LTE and 5G migration priority
Italy	Maintained per use case	Sunset schedule published	Cat-M and NB-IoT growing
Spain	Maintained per use case	Sunset schedule published	Active LTE migration
Partner countries	Variable per partner MNO	Variable	Depends on roaming agreement

The structural message for design: do not depend on a 3G UMTS fallback for a new product, do not depend on 2G GSM outside regions where it is explicitly maintained, target LTE Cat-1, Cat-M or NB-IoT for primary coverage according to the application profile. Exact country-level schedules evolve and must be checked on the GDSP portal at T0 of each project.

Articulation with national regulatory certifications

Vodafone acceptance is not a regulatory certification. It does not replace:

CE marking and RED for the European Union;
FCC for the United States (when the device is also sold there);
ISED for Canada;
ACMA or RCM for Australia;
ICASA for South Africa (Vodacom subsidiary);
the applicable national approvals in other Vodafone Partner Markets.

For a product targeting the multi-country Vodafone Business catalogue, the manufacturer must accumulate PTCRB or GCF, Vodafone acceptance, and the national regulatory markings of each target country. See EU and US dual certification for combined planning.

Common pitfalls

1. NIDD enabled at profile level, not implemented in firmware

The Vodafone eSIM profile provisions a NIDD APN for a power-efficient NB-IoT use case. The application firmware keeps opening an IP session on the classic data APN because the stack does not implement the NIDD API. Result: consumption explodes, the supposed NB-IoT benefit disappears, and acceptance fails because the observed behaviour does not match the tested profile.

2. Mis-negotiated PSM

Firmware requests T3324 or T3412 outside the ranges supported by the GDSP profile of the target country. The network refuses and the device stays in permanent connected mode. Power consumption is multiplied by an order of magnitude. Acceptance detects this drift on a calibrated battery-life test.

3. Non-SGP.32 eUICC on a modern IoT product

An SGP.22-only eUICC on a headless industrial product struggles to pass recent acceptance, because eIM orchestration is not possible and the customer has to manage the profile via local activation, which does not scale to a fleet. Verifying the eUICC certification on the GSMA list is a very early prerequisite.

4. Proprietary non-conformant LPA

The integrator buys a certified eUICC but re-implements a proprietary LPA that does not properly support ES9+ or ES10b, or that exposes legacy TLS behaviour (obsolete cipher suites). The Vodafone SM-DP+ refuses the connection. Solution: use the cellular module's LPA when integrated and certified, or a third-party LPA certified SGP.22 or SGP.32.

5. APN hard-coded in firmware

A device ported from a previous carrier programme keeps a hard-coded APN. The GDSP profile provisions a different APN, the device ignores provisioning and tries to open a session on its original APN. Acceptance flags the inconsistency and fails. The rule: firmware must always read the APN from the provisioned profile, not from a compile-time constant.

6. Missing Connection Manager (CMP)

Vodafone and modern IoT practice recommend a firmware-side Connection Manager that supervises the radio state, manages retries with exponential backoff, drives PSM or eDRX transitions per policy, and exposes connection metrics. A device without a CMP performs aggressive reattaches or generates network error loops visible at acceptance. This is a classic qualitative failure cause.

7. SGP.02 vs SGP.22 vs SGP.32 confusion

SGP.02 (M2M push-mode) is being retired on GDSP. SGP.22 is consumer (local pull-mode). SGP.32 is IoT (eIM orchestration). Attempting SGP.02 on a new product triggers an acceptance refusal. Attempting SGP.22 on a headless fleet product creates operational problems. The right alignment must be set in the module and eUICC design phase.

8. Late discovery of 3G retirement in a target country

A product designed with a 3G UMTS fallback for a country where Vodafone has already switched off 3G has no residual coverage. Acceptance may pass on the bench, but real deployment fails. The country-level sunset schedule must be checked in the design phase, not at production.

Project timing, the right sequence

The recommended order for a cellular device targeting a Vodafone Business IoT deployment:

Module and eUICC design phase: pick a cellular module already tested on Vodafone (most recent Quectel, u-blox, Telit, Sequans, Murata modules fit), pick an eUICC certified SGP.22 or SGP.32 per product scenario, pick a conformant LPA or IPA.
Hardware stabilisation phase: open the GDSP account on the customer side (through the Vodafone Business IoT team), provision a test profile, identify the acceptance lab.
Pre-acceptance phase: RF pre-tests (if PTCRB or GCF is not yet obtained), pre-tests against the Vodafone SM-DP+, bench validation of PSM, eDRX and NIDD.
PTCRB and GCF phase: obtain the multi-carrier radio passport applicable to the target zone.
National regulatory phase: CE and RED for Europe, FCC for the US, ISED for Canada, ACMA for Australia, ICASA for Vodacom South Africa.
Vodafone acceptance phase: GDSP submission, lab testing, firmware iterations if needed, acceptance ID granted.
Deployment phase: production Vodafone profile provisioning, IMEI registration, fleet activation, GDSP monitoring.
Lifecycle phase: monitoring of Vodafone technical bulletins (PSM or eDRX changes, SGP.32 evolution, 2G or 3G country retirement), declaration of significant changes.

For combined multi-zone planning, see also Verizon OPC if a US target exists, and EU and US dual certification for regulatory sequencing.

Connection with other cellular certifications

Vodafone acceptance sits above the common 3GPP baseline and alongside other carriers' own programmes:

PTCRB (US and Canada): prerequisite when the device also targets that zone, independent of Vodafone.
GCF (global): prerequisite for most Europe, APAC and Middle East markets.
Verizon OPC (US Verizon): MNO-specific programme, no equivalence with Vodafone acceptance.
Vodafone Global IoT acceptance (Vodafone): MNO-specific programme, no equivalence with OPC nor AT&T NDD nor T-Mobile 5G SA Certification.

A cellular device sold on the Vodafone Business IoT catalogue therefore accumulates: national regulatory markings per country, PTCRB or GCF radio (per zone), Vodafone device acceptance, and eSIM provisioning via GDSP. For the vocabulary (GDSP, eIM, IPAd, IPAe, LPA, SM-DP+, NIDD, PSM, eDRX), see the spilma glossary.