Deutsche Telekom IoT: acceptance, nuSIM and Cloud of Things

Author Hugues Orgitello Last updated 11 July 2026 ~14 min read

Guide · Deutsche Telekom IoT

Deutsche Telekom (DT) is one of the European telecom operators most engaged in cellular IoT, with a strategy combining a multi-country footprint, a proprietary acceptance programme, the Cloud of Things application platform, and a specific innovation: nuSIM, its integrated SIM (iSIM) hosted inside the cellular SoC. For a manufacturer aiming at the European market with a cellular product, 3GPP conformance through GCF is not enough: passing DT IoT acceptance conditions listing in the DT certified hardware catalogue and eligibility for carrier offers. This page describes the DT footprint relative to T-Mobile US, the DT IoT acceptance programme, the nuSIM versus SGP.32 eUICC trade-off, the positioning of Cloud of Things, cellular module qualification, the technologies covered, and the pitfalls that delay listing.

Deutsche Telekom footprint and demarcation from T-Mobile US

The Deutsche Telekom group operates mobile networks in several European countries under distinct brand names. T-Mobile US, a separately listed company in which DT holds a majority stake, operates as an independent entity for certification matters and must be addressed in a separate dossier.

Country	Brand	Network	Position
Germany	Telekom Deutschland	2G (switch-off announced for 30 June 2028), LTE, LTE-M, NB-IoT, 5G NR	Primary market, programme reference
Austria	Magenta Telekom	LTE, 5G NR; NB-IoT and LTE-M depending on offer	DT group subsidiary, own APNs
Czech Republic	T-Mobile CZ	LTE, 5G NR; NB-IoT and LTE-M depending on offer	DT group subsidiary
Hungary	Magyar Telekom	LTE, 5G NR; NB-IoT and LTE-M depending on offer	DT group subsidiary
Greece	Cosmote (OTE subsidiary)	LTE, 5G NR; NB-IoT and LTE-M depending on offer	DT group subsidiary, distinct Cosmote scope
Poland	T-Mobile Polska	LTE, 5G NR; NB-IoT and LTE-M depending on offer	DT group subsidiary
Slovakia	Slovak Telekom	LTE, 5G NR; NB-IoT and LTE-M depending on offer	DT group subsidiary
Croatia	Hrvatski Telekom	LTE, 5G NR; NB-IoT and LTE-M depending on offer	DT group subsidiary
United States	T-Mobile US	LTE, 5G NR, n41/n71 bands	Separate device programme

NB-IoT and LTE-M availability is checked market by market, for instance through the IoT Solution Optimizer, DT's online tool for modelling an NB-IoT or LTE-M design on the group's networks.

For European manufacturers, the key point is that DT IoT certification does not open T-Mobile US. The US programme is independent, aligned with PTCRB and its own requirements. A product targeting both geographies must plan two distinct acceptance dossiers.

Within the European DT footprint, subsidiaries share a common technical structure but retain local APN policies, IMSI numbering plans and roaming agreements. A module accepted in Germany is not automatically testable without complementary verifications in the Czech Republic or Greece, particularly on NB-IoT chains.

The DT IoT acceptance programme, scope

The DT IoT acceptance programme rests on two foundations: 3GPP conformance via GCF or PTCRB depending on the module, and a DT-specific test plan covering interactions with its networks and its provisioning systems.

Comparison with PTCRB and GCF

Criterion	PTCRB / GCF	DT IoT acceptance
Nature	Cross-carrier 3GPP radio conformance	Deutsche Telekom IoT proprietary programme
Reference	3GPP TS 36.521, TS 38.521	Superset: 3GPP baseline + DT network tests, nuSIM/eUICC, APNs, intra-group roaming
Scope	Generic radio conformance	DT network interoperability, security, device management, no harm to network (GSMA TS.34)
Granted by	PTCRB (CTIA) and GCF schemes	Deutsche Telekom IoT, acceptance team
Identifier	PTCRB or GCF certification	Listing in the DT certified hardware catalogue
Required for DT catalogue eligibility	Yes	Yes, in addition to GCF/PTCRB

PTCRB and GCF are prerequisites but not sufficient. Without valid 3GPP certification, DT does not open the acceptance phase. With PTCRB or GCF only, the product remains functional on the network but is not eligible for DT's turn-key IoT offers, and certain scenarios (nuSIM, intra-DT NB-IoT roaming, Cloud of Things profiles) cannot be validated.

Portals and entry points

DT IoT exposes several portals depending on the entry angle:

• iot.telekom.com, the DT IoT product portal (connectivity, SIM, platforms);
• DT IoT Hardware Ecosystem (hardware.iot.telekom.com), the certified hardware catalogue and its documentation;
• T IoT Hub, the orchestration portal for multi-platform connectivity and device management;
• IoT Solution Optimizer, the modelling tool for NB-IoT and LTE-M designs on the group's networks;
• the developer documentation (hub.iot.telekom.com), which describes among other things the device certification process.

Opening an acceptance dossier generally goes through a DT IoT commercial contact, with a prior qualification: expected volume, target geography, object type and chosen SIM solution.

Cellular module qualification

Deutsche Telekom invests in the certification of cellular chipsets, modems and modules for its IoT catalogue, following a pyramid logic: few chipsets, more modules, many devices. The goals stated in DT's documentation are interoperability with the networks, compliance with 3GPP and Telekom requirements, security, device management and no harm to network (per GSMA TS.34). Certified hardware is listed in the DT IoT Hardware Ecosystem. The process primarily concerns module manufacturers (Quectel, u-blox, Telit Cinterion, Sierra Wireless, Murata, Sequans, Fibocom and others) who wish to list their module as a pre-accepted building block.

Typical steps:

1. Technical submission by the module manufacturer: datasheet, GCF report, PTCRB report where applicable, nuSIM support statement where applicable, SGP.32 eUICC support.
2. Documentary review: coverage of European DT bands (B1, B3, B7, B8, B20, B28; n1, n28, n78), LTE-M and NB-IoT support where applicable, minimum 3GPP Release.
3. Test campaign in a DT-recognised laboratory: network interoperability for DE and a representative subset of subsidiaries, nuSIM behaviour where applicable, eUICC profile handling, NB-IoT in the lab and under partner roaming conditions.
4. Validation and listing in the DT certified hardware catalogue.

Once a module is certified, downstream integrators can use it in their products with a faster and cheaper device-level acceptance. The module becomes a pre-validated brick, much like Verizon's AML or other carriers' approved-module lists (see Verizon Open Development for a comparable North American logic).

Note: the DT certified hardware list evolves. Before a project, manufacturers must ask the module supplier for the current DT certification status, not only the GCF status, to avoid surprises at device acceptance.

nuSIM, the Deutsche Telekom iSIM

nuSIM is Deutsche Telekom's technical signature in cellular IoT. It is an iSIM in the GSMA sense, that is to say a SIM application hosted directly in a secure zone of the cellular SoC, without a card or a dedicated eUICC chip. It is optimised for NB-IoT and very-low-cost objects, with compact profiles (under 1 KB according to DT).

nuSIM, SGP.32 eUICC and physical SIM compared

Criterion	Physical SIM	SGP.32 eUICC	nuSIM (DT iSIM)
Form factor	SIM card or MFF2	Dedicated chip	Secure zone inside the cellular SoC
Standard	ETSI TS 102 221	GSMA SGP.32	DT proprietary specification (open-source reference Loader)
Provisioning	Physical exchange or classical OTA	IoT RSP: SM-DP+, eIM, IPA	Encrypted profile loaded at factory (DT Data Preparator, Loader Application)
Operator portability	Possible with a new card	Multi-operator via GSMA profiles	Turn-key DT, limited portability
BOM cost	Highest (card + holder)	Mid-range (chip + integration)	Lowest (no external component)
Volume target	All volumes	Mid and large IoT volumes	Very large mono-operator DT volumes
Expected lifetime	Short to medium	Long (10 years and beyond)	Long, tied to the SoC
LPA / IPA	Not applicable	Required on the device	Not applicable (DT-side orchestration)

The nuSIM commercial model assumes a three-way partnership: the cellular SoC vendor that integrates the nuSIM application, the product manufacturer that selects this SoC and signs a DT IoT connectivity agreement, and Deutsche Telekom which drives provisioning. Current partner SoCs cover several LPWAN and LTE-M vendors (the list evolves, to be checked directly with DT at the start of any project). At MWC 2025, DT presented with Nordic Semiconductor and PSsystec the MECC initiative (Make Everything Cellular Connected): modules with embedded nuSIM, pre-provisioned at the factory and activated on demand.

The main benefit of nuSIM lies in integration cost and the removal of a hardware failure point: no SIM holder, no extra eUICC chip, no re-soldering if a card loosens. For a high-volume product deployed within a single operator ecosystem (DT and its roaming partners), it is economically the most rational option.

The downside is its relative closure: the nuSIM profile is bound to DT and its orchestrator. If commercial strategy shifts (operator change, international distribution outside the DT footprint), portability is less immediate than with a standard SGP.32 eUICC. The decision must therefore be made during commercial scoping, not mid-development.

nuSIM provisioning pitfalls

Three recurring pitfalls:

• Misaligned root key between the SoC manufacturing chain and the DT orchestrator: the product ships with a profile that DT does not recognise. Detection is late (first customer activation) and remediation is expensive (RMA or in-field re-flashing).
• Incomplete personalisation at end-of-line test: the nuSIM IMSI or ICCID is not correctly injected into the secure zone, the module attaches but does not authenticate.
• No re-provisioning channel planned in case of error: nuSIM cannot be reconfigured via a standard SM-DP+ flow. Re-provisioning goes through a firmware update or a device management protocol (LwM2M for instance), which must be planned from the design phase.

The nuSIM provisioning flow is scoped with DT upstream of the project; it is a major point of vigilance for first-time submitters.

Cloud of Things, application platform

Cloud of Things (CoT) is Deutsche Telekom's application IoT platform, historically built on Cumulocity IoT through a partnership with Software AG; Cumulocity has been an independent company since early 2025, following a management buyout. The DT offer comes as Cloud of Things SMART, ENTERPRISE and PRIVATE. It offers:

• multi-device, multi-vendor fleet management;
• telemetry collection and storage;
• rules, alerts, dashboards;
• firmware OTA campaign management;
• integration with DT IoT connectivity for billing and SIM management.

CoT is not mandatory to use DT IoT connectivity. An object on DT connectivity can integrate with AWS IoT Core, Azure IoT Hub, or a third-party platform without interfering with network acceptance. CoT is positioned as an option in some turn-key plans bundling connectivity + platform + SIM/nuSIM in a single contract.

For a product whose application strategy is already committed to a hyperscaler, CoT is not a blocking matter. For a product in scoping that seeks an integrated partner, CoT and DT connectivity form a quick vertical offer with no multi-vendor contracts.

Cellular technologies covered

DT IoT drives its acceptance on technologies actively listed in the catalogue. Others remain operable on DT networks (because the radio is conformant) but are not commercially promoted.

LTE Cat-M (LTE-M)

LTE-M (Cat-M1, and Cat-M2 in some cases) is DT's preferred LPWAN technology for moderately mobile objects with moderate throughput and potential VoLTE. LTE-M availability is checked market by market across the group's European footprint, for instance through the IoT Solution Optimizer. LTE-M acceptance verifies PSM and eDRX support, RAI (Release Assistance Indication) behaviour and attach with the target IoT APN.

NB-IoT

NB-IoT is the ultra-low-power technology for stationary or barely mobile objects. DT completed with Vodafone, under the GSMA Mobile IoT Initiative, the first international NB-IoT roaming trials in Europe, and remains a driving force on inter-operator NB-IoT roaming agreements. NB-IoT acceptance verifies attach, PLMN-locking support, long-session stability and behaviour during intra-DT roaming (across group subsidiaries). It is also the scenario where pitfalls are most frequent.

LTE Cat-1bis

Cat-1bis (LTE Cat-1 throughput with a single antenna) is positioned by DT as an alternative to LTE-M where LTE-M coverage is still uneven and where the product needs higher throughput than LTE-M offers. Cat-1bis acceptance highlights the cell edge issue: without antenna diversity, sensitivity is lower, and a product assuming nominal throughput in real conditions can be deeply disappointing. DT recommends real-world testing beyond lab testing for this category.

LTE Cat-4 and above

For gateways, POS terminals and high-throughput medical devices, DT acceptance covers LTE Cat-4, Cat-6 and Cat-7+. VoLTE and IMS requirements then become stricter, and integration with Telekom DE voice services may be required for some categories.

5G NR

DT is rolling out 5G NSA and progressively 5G SA on European commercial bands (mainly n1, n28, n78). 5G NR acceptance for IoT primarily targets gateways, FWA and industrial terminals. For low-bandwidth objects, staying on LTE-M and NB-IoT remains preferable.

2G

2G (GSM) is in progressive retirement across the DT footprint, on a schedule specific to each subsidiary; in Germany, Telekom has announced the complete 2G switch-off for 30 June 2028. A new 2G-only product no longer makes sense on this footprint. Multi-tech modules (for instance 2G + LTE-M) remain useful to ease the transition, but 2G is no longer a commercial argument in any roadmap.

Pan-European roaming and the global T-IoT offer

Beyond the DT footprint, two dimensions deserve attention.

Classic MNO roaming. DT has roaming agreements with most European operators for 2G, 3G (in retirement), 4G LTE and 5G. LTE-M and NB-IoT coverage in roaming is not guaranteed by default, even where LTE is. An international IoT product must clarify the LPWAN coverage country by country with DT IoT.

Global T-IoT offer. Since February 2022, Deutsche Telekom and T-Mobile US jointly market T-IoT, a global enterprise IoT connectivity offer, announced at launch across 383 networks and 188 destinations, managed through the T-Mobile Control Center and DT's M2M Service Portal. It is the commercial vehicle for deployments outside the group's own network footprint (France, Italy, Spain and the UK notably), through the group's roaming agreements. The quality and reach of LPWAN services in roaming vary with the local host operator, which can create asymmetries in the behaviour of the same product across countries.

For manufacturers with broader targets, see also the Verizon Open Development programme for the United States, and the multi-operator logic documented in the certification timeline and certification costs.

eUICC, profiles and orchestration

For products that do not use nuSIM, DT IoT acceptance enforces current GSMA standards.

• GSMA SGP.22 remains the Consumer RSP standard, used for products with a UI (gateways, M2M terminals with a screen, for instance). DT supports SGP.22 for compatibility but steers new IoT deployments towards SGP.32.
• GSMA SGP.32 is the IoT RSP standard, expected on all new headless products. It introduces the eIM (eSIM IoT Manager) for fleet management without user intervention; the IPA must be correctly implemented on the device side.
• SGP.02 (the historical M2M architecture) is being progressively retired. DT, like the other large operators, steers new products towards SGP.32; SGP.02 retirement schedules are scoped directly with DT.

The LPA or IPA must talk to the DT SM-DP+, with root certificates provided by DT. An incomplete TLS chain or an outdated cipher suite is a recurring rejection cause, and the root cause is often an embedded TLS stack that is no longer maintained.

APNs and IP addressing plan

DT typically offers several APN families: public IPv4 APN, public dual-stack IPv4/v6 APN, private APN with customer VPN attach, NB-IoT-dedicated APN, LTE-M-dedicated APN, Cloud of Things APN for pre-integrated objects. APN choice affects:

• IP addressing (public, private, RFC 1918, IPv6 range);
• latency and routing (DT apex direct, or through an MVNO);
• application integration (Cloud of Things, AWS IoT Core via private link, other);
• billing (volumes, plans, tariff profiles).

Acceptance verifies that the module attaches to the target APN without falling back to a wrong default APN, negotiates the IP stack correctly (including IPv6 where required), and handles disconnects and restarts without leaking orphan PDP sessions (a classic cause of quota leakage and network-firewall blocking).

Frequent pitfalls

1. Confusing DT acceptance with T-Mobile US acceptance

This is the strategic pitfall. A successful DT IoT dossier does not waive T-Mobile US's programme, and vice versa, even though the two operators jointly market the T-IoT offer. Any product schedule must separate these two geographies from the very start of scoping.

2. Over-trusting NB-IoT roaming

Many IoT programmes assume NB-IoT roams like LTE. In 2026, that is false in most cases. Any promise of international NB-IoT coverage must be validated country by country, operator by operator, leaning on DT IoT roaming information and the NB-IoT agreements actually in place.

3. nuSIM scoped poorly on the commercial side

Choosing nuSIM purely for BOM savings, without validating long-term commercial strategy (volume, geography, operator portability), is a frequent mistake. If reselling the product to an international customer is on the horizon, SGP.32 eUICC keeps more options open.

4. Idealised Cat-1bis

Nominal Cat-1bis throughput is never reached in real conditions when the signal is moderate. A product whose use case depends on bounded latency (payment, telemedicine, industrial control) must not rest on Cat-1bis without real mobility and cell-edge testing.

5. Lab testing only

DT IoT acceptance covers network scenarios that lab testing does not fully reproduce, in particular inter-subsidiary roaming and real APN attach. Skipping field testing leads to failures uncovered after commercial signing.

6. eUICC without SGP.32 IPA verification

A GSMA-certified eUICC is not enough if the IPA on the device side is not SGP.32-conformant. IPA integration is as much a software-product topic as a hardware one, and SGP.22 / SGP.32 confusion remains common.

7. Confusing Cloud of Things with a network obligation

Cloud of Things is an optional application platform. No DT IoT acceptance step requires its use. Conversely, signing for CoT does not waive network and SIM acceptance.

8. Ignoring DT programme evolutions

Like all carrier programmes, DT IoT acceptance evolves: newly accepted bands, gradual 2G retirement per subsidiary, APN updates, nuSIM profile evolutions. A long-cycle project must plan a periodic review of the DT documentation and certified hardware catalogue.

Project sequencing and timing

The recommended order for a cellular IoT product targeting DT:

1. DT IoT commercial scoping: volume, countries, technologies, SIM choice (nuSIM, SGP.32 eUICC or physical), CoT or third-party platform.
2. Module selection: verify the candidate module's presence in the DT certified hardware catalogue or schedule its submission. Cross-check against PTCRB (if US also in scope) and GCF.
3. Hardware design: antenna tuned to European DT bands, choice of an SoC compatible with nuSIM if retained.
4. Pre-validation: network testing on DE and CZ (representative sample), NB-IoT behaviour in the lab, simulated eUICC RSP or nuSIM provisioning.
5. DT IoT acceptance: dossier submission, campaign in a recognised lab, firmware iterations, catalogue listing.
6. Commercial activation: nuSIM SIM enrolment, APN opening, CoT integration if applicable.
7. Lifecycle tracking: declaration of firmware changes affecting radio or provisioning, monitoring of DT IoT programme evolutions.

For the broader EU view on RED, see CE vs FCC EMC and EU + US dual certification. For terminology (LPA, IPA, eUICC, eSIM, IMSI, ICCID, APN, NB-IoT, Cat-M, Cat-1bis), see the spilma glossary.

See also

• NTT DoCoMo, KDDI, SoftBank, Rakuten: Japan cellular
• China Mobile, Telecom, Unicom: cellular IoT acceptance
• Telstra, Optus, TPG: cellular IoT acceptance in Australia
• AT&T Network Ready: carrier homologation, cellular IoT
• T-Mobile US: cellular IoT device certification and DICE

Working on scoping a cellular IoT product targeting Deutsche Telekom for a real product? AESTECHNO can audit your design and certification plan. Get in touch →

Sources & references

1. Deutsche Telekom IoT, product portal , Deutsche Telekom iot.telekom.com/
2. IoT Device Certification, DT IoT Hub documentation , Deutsche Telekom hub.iot.telekom.com/docs/device-to-cloud/general-info/iot-device-certification/
3. nuSIM, integrated SIM by Deutsche Telekom , Deutsche Telekom iot.telekom.com/en/iot-connectivity/isim
4. Cloud of Things, DT application IoT platform , Deutsche Telekom iot.telekom.com/en/iot-connectivity/iot-device-management
5. T-Mobile and Deutsche Telekom launch T-IoT , Deutsche Telekom www.telekom.com/en/media/media-information/archive/t-mobile-and-deutsche-telekom-launch-t-iot-648228
6. 2G switch-off ensures better network (30 June 2028) , Deutsche Telekom www.telekom.com/en/media/media-information/archive/more-speed-on-old-frequencies-2g-switch-off-ensures-better-network-1081866
7. PTCRB Certification Program , PTCRB www.ptcrb.com/
8. GCF, Global Certification Forum , GCF www.globalcertificationforum.org/
9. GSMA SGP.32, eSIM IoT Technical Specification , GSMA www.gsma.com/esim/iot-esim/
10. First European NB-IoT roaming trial (GSMA, DT, Vodafone) , Deutsche Telekom www.telekom.com/en/media/media-information/archive/completion-of-first-european-nb-iot-roaming-trial-526404