Deutsche Telekom IoT: module certification and nuSIM
Deutsche Telekom (DT) does not run a device acceptance programme in the way most guides describe it. What it runs is a chipset and module certification: DT tests the cellular module inside your product against its own radio and core networks, and its tariffs require customers to use DT-certified modules. 3GPP conformance through GCF changes the grade a module can reach, but it is not an entry condition. This page is built from the documents DT itself publishes on its IoT Hardware Ecosystem portal: the certification process deck, the detailed list of certified modules (dated September 23, 2026), and the No Harm to Network guideline version 2.9 (September 7, 2026). It covers what DT certifies, the Full and Limited grades, the 10K-unit limit tied to the GSMA TS.34 Radio Policy Manager, the countries and technologies in scope, the traffic limits your firmware must respect, and where nuSIM, SGP.32 and Cloud of Things fit.
What Deutsche Telekom certifies
Section titled “What Deutsche Telekom certifies”The DT IoT Hub documentation and the process deck give the same five goals. DT invests in chipset and modem certification to ensure:
- interoperability with networks;
- compliance to 3GPP and Telekom requirements;
- security;
- device management;
- no harm to network, as per GSMA TS.34.
The model is a pyramid: few chipsets, more modules, many devices. DT certifies the protocol stack at chipset level and the module integration at module level. Mobile IoT chipsets (NB-IoT, LTE-M) are always certified in advance, before DT starts testing the modules built on them; for 2G, 3G, 4G and 5G, most of the work is on modules.
The commercial consequence is stated twice in the deck: "DT SIM contracts require customers to only use of DT-certified chipsets/modules", and, in the FAQ, "DT tariffs require customers to use DT-certified modules". For a product maker, the first question is therefore not "how do I get my device accepted" but "is the module I picked on the DT list, with which firmware and which conditions".
Where the tests run
Section titled “Where the tests run”DT operates instances of its RAN, EPC and 5GC networks at its Group Test Facility in Germany; a facility in Poland can patch into this environment. Rohde & Schwarz CMW500 units simulate negative scenarios and complex cases such as cell reselection and access barring. DT validates end-to-end interoperability against multiple DT radio and core network configurations deployed across Europe. The deck does not mention third-party laboratories for this certification.
Layer 3 focus and the GCF position
Section titled “Layer 3 focus and the GCF position”DT certification "focuses on Layer 3 procedures, as well as overall device performance". In the words of the deck: "Unlike most European operators, DT does not require module suppliers to present GCF certification. Chipset providers submit evidence that they pass GCF test cases for Layers 1-2." In the FAQ, DT adds that GCF certification of a module is not good enough on its own: "From experience we know that GCF does not prevent most of the critical interoperability issues we find."
| Layer | Who covers it | Evidence DT expects |
|---|---|---|
| Layers 1 and 2 (PHY, MAC, RLC, PDCP) | GCF test cases | Chipset supplier evidence of passing GCF test cases |
| Layer 3 (RRC, NAS) | DT certification | DT tests against its radio and core configurations |
| Performance | DT certification | Latency, throughput and power consumption analysis |
| Network protection | DT certification | GSMA TS.34 Radio Policy Manager, "TS.34 RPM" in the test scope |
PTCRB does not appear anywhere in the DT process. It is the certification scheme of the North American operators (see the PTCRB hub); see PTCRB vs GCF for that side.
Certification grades and the 10K-unit limit
Section titled “Certification grades and the 10K-unit limit”The deck defines the grades per supplier type. Firmware with showstoppers on layer 3 interoperability, or serious deviations in latency, throughput or power consumption, is not certifiable at all.
| Supplier | Grade | GCF | GSMA TS.34 RPM | Volume |
|---|---|---|---|---|
| Module | Full Certification | GCF certification available | Implemented | No limit stated |
| Module | Full Certification | GCF certification available | Not implemented | 10K units per IoT application |
| Module | Limited Certification | No GCF certification | Implemented | No limit stated |
| Module | Limited Certification | No GCF certification | Not implemented | 10K units per IoT application |
| Chipset | Full Certification | GCF internal test results with no major issues | Implemented | No limit stated |
| Chipset | Limited Certification | GCF internal test results with no major issues | Not implemented | 10K units per IoT application |
All grades also require no showstoppers on layer 3 interoperability and no performance issues. A footnote exempts LTE mobile broadband and 5G SA/NSA chipsets and modules from the RPM requirement.
The detailed module list shows how the grades are used in practice. Each entry carries up to eleven successive certification dates, each with its firmware version and approval conditions, for instance "NB-IoT: Limited certification (...) for pilot usage" or "GCF certification outstanding". A module certified on one firmware is not certified on the next until DT has tested it, which is why the list tracks firmware versions.
What the supplier sends and what it receives
Section titled “What the supplier sends and what it receives”To start, the supplier provides one or two modules or chipsets with the latest firmware, one or two evaluation kits, antenna connectors, a flashing tool, a trace tool able to analyse at least layer 3 radio messages (RRC, NAS), and documentation: product description (3GPP release, supported bands, UE categories), firmware release notes and known issues, AT command reference, flashing and logging guidelines.
On success, the vendor receives a DT Certification Letter, a DT Certification Report (issues, workarounds, performance analysis), notification of DT Group product management, and a listing in the online list of certified IoT chipsets and modules.
| Scope | Fee according to DT |
|---|---|
| Mobile IoT (NB-IoT, LTE-M) chipsets and modules | Free of cost |
| 5G chipsets and modules | Free of cost |
| 5G modules for DT private (Campus) networks | Certified automatically at no cost |
| 4G (Cat.1/1bis to Cat.4, Cat.6+ mobile broadband), 3G, 2G | Paid service on request, quote from the DT Certification Program |
| VoLTE | Paid service on request |
| 4G IoT modules for Campus networks | Paid service on request |
| Partner device onboarding | Free of charge (onboarding deck, May 2021) |
DT publishes no prices for the paid services.
Countries and technologies in scope
Section titled “Countries and technologies in scope”The process deck gives the certified countries per technology. Its FAQ defines the footprint as the DT Group (Austria, Croatia, Czech Republic, Germany, Greece, Hungary, Montenegro, North Macedonia, Poland, Slovakia) plus T-Mobile Netherlands plus 1NCE, and marks the United States as "not covered by DT Certification".
| Technology | Countries certified (process deck) |
|---|---|
| 5G NR (NSA) | AT, CZ, DE, GR, HR, HU, NL, PL, SK, Campus |
| 4G LTE | AT, CZ, DE, GR, HR, HU, ME, MK, NL, PL, SK |
| 3G UMTS | AT, HR, HU, ME, MK, NL, PL |
| 2G GSM | AT, CZ, DE, GR, HR, HU, ME, MK, NL, PL, SK |
| LTE-M (eMTC) | AT, DE, NL, HU (planned) |
| NB-IoT | AT, CZ, DE, HR, NL, PL, SK |
The detailed module list (September 23, 2026) matches this: LTE-M approvals read "Full certification (AT, DE, NL)" or "(DE)", NB-IoT approvals list AT, CZ, DE, HR, NL, PL, SK. The list also has columns for NTN-NB, NTN-NR and satellite, VoLTE, TS.34 RPM, Campus network certification (4G/5G NSA and 5G SA), and IoT Solution Optimizer support. Its band columns cover LTE Bands 1, 2, 3, 4, 5, 7, 8, 12, 20 and 5G NR n1, n3, n28, n77, n78.
The DT guideline "5G for IoT Connectivity" (version 1.2) states that, at the time of writing, DT 5G networks are deployed in Non-Standalone configuration (3GPP option 3x) in FR1, with the LTE anchor on Bands 28, 20, 8, 3, 1, 7 and/or 38 and the NR carrier on n28, n3, n1, n7, n38 or n78, with Dynamic Spectrum Sharing on LTE Bands 1 and 3. Because the EN-DC band combinations differ between DT affiliates, the guideline recommends that module selection consider the spectrum bands and EN-DC combinations each affiliate has deployed.
2G in Germany
Section titled “2G in Germany”Deutsche Telekom announced on October 22, 2024 that its 2G network is expected to be completely switched off by June 30, 2028, and that the freed 900 MHz spectrum will go to 4G and 5G. The press release tells IoT and M2M users to plan the replacement of remaining 2G radio modules now, moving to 4G, 5G, NB-IoT or LTE-M. The date is for Germany; other affiliates are not covered by that announcement.
No Harm to Network: the limits your firmware must respect
Section titled “No Harm to Network: the limits your firmware must respect”The DT guideline "No Harm to Network for IoT Device Applications" version 2.9 (September 7, 2026) turns GSMA TS.34 into DT requirements. "SHALL" items are mandatory, "SHOULD" items are recommended. Note that it cites TS.34 version 6.0 and requirement IDs from versions 4.0 to 6.0, while the GSMA has published TS.34 v14.0 (March 30, 2026).
| Annex limit (per device) | NB-IoT | LTE-M | LTE (all categories) | 5G NR NSA |
|---|---|---|---|---|
| Connection requests (network attach) per day | 24 | 144 | 144 | 144 |
| Application messages per day | 120 | 720 | 720 | 720 |
| Average data volume per month | 6.5 MB | 500 MB | No restriction unless the tariff defines one | No restriction unless the tariff defines one |
Firmware update traffic is excluded from the volume figures, and tariff-specific restrictions may apply on top.
Selected mandatory requirements from the same document:
| Requirement | What the DT text says |
|---|---|
| Attach randomisation on NB-IoT | Randomisation time of at least 40 seconds for the attach procedure |
| Devices in one cell, NB-IoT | No batch of more than 100 devices triggered to communicate within one hour on the same cell |
| Simultaneous traffic, NB-IoT | At most 60 devices per second per cell in good coverage, at most 40 in moderate or poor coverage |
| SMS on NB-IoT | Communication over an NB-IoT bearer SHALL NOT use SMS on the DT network |
| Frequent senders | Inactivity periods shorter than two hours: keep a persistent PDP/PDN connection |
| Roaming keep-alive | When camping two hours or more on a roaming network, send small data at randomised intervals of less than two hours |
| Last-gasp messages | No simultaneous transmission from more than 100 devices after a system-wide failure such as a power outage |
| Reject cause #26 | Handle the T3396 back-off timer per 3GPP TS 24.008; with a timer between 1 and 1,116,000 seconds, do not power off the module |
| IP stack | Support IPv4/v6 dual stack (PDN type IPv4v6) |
Device onboarding, separate from module certification
Section titled “Device onboarding, separate from module certification”Finished devices follow a different path, described in the DT deck "Device Onboarding and Supplier Partnerships" (May 2021). It is a partnership process, free of charge, in six stages: onboarding prioritised, supplier documentation provided, documentation review completed, internal test started, internal test passed, onboarding completed. The supplier provides certification documents (CE, WEEE, battery, FCC and so on), a firmware release candidate and test devices. Only devices with high or very high sales potential go through the extended tests: radio module check, no harm to network test, interoperability tests, physical and security tests, stress and stability tests. The result is a listing in the DT device portfolio, as "preferred device" for the extensively tested ones, and promotion on the IoT Hardware Ecosystem site.
nuSIM, the Deutsche Telekom iSIM
Section titled “nuSIM, the Deutsche Telekom iSIM”nuSIM is the DT iSIM: the SIM function is integrated directly into the radio module hardware, with no separate SIM card or SIM chip. DT lists three nuSIM radio modules on its page: Nordic nRF9151, Nordic nRF9160/nRF9161 and Quectel BG95-M3, and offers "IoT Embedded Connect", a bundle of radio module, nuSIM and pre-configured connectivity.
What the DT nuSIM FAQ says:
- To keep profiles small, DT removed OTA access, the SIM toolkit, Java Card applet support and unneeded parts of the SIM file system.
- A Data Preparator creates encrypted profiles on behalf of a network operator, much like an SM-DP+; a Loader Application at the module or device maker loads them into the modules, for example at end-of-line test. DT provides an open-source reference Loader Application free of charge.
- Binding specifications define the nuSIM function, the loading interfaces and the cryptography, so that any nuSIM profile can be loaded onto any nuSIM chip by any Data Preparator; COMPRION developed the compliance test suite.
- Profiles can be replaced in the field, through FOTA or through LwM2M device management: OMA SpecWorks standardised two nuSIM objects for this.
- Every nuSIM implementation is tested and certified by TÜViT, and profiles go through GSMA SAS-accredited data preparation partners.
- DT sees the main use in NB-IoT and LTE-M, including multimode with 2G.
nuSIM, SGP.32 eUICC and physical SIM compared
Section titled “nuSIM, SGP.32 eUICC and physical SIM compared”| Criterion | Physical or MFF2 SIM | SGP.32 eUICC | nuSIM |
|---|---|---|---|
| Hardware | Plug-in card or soldered chip SIM (MFF) | Soldered eUICC chip | No separate component, inside the radio module |
| Specification | ETSI UICC | GSMA SGP.32 (v1.2 June 27, 2024; v1.3 May 22, 2026) | nuSIM specifications, not a GSMA RSP specification |
| Profile change | Swap the card | Remote, eIM and IPA with an SM-DP+ | Replacement through FOTA or LwM2M; no OTA in the SIM |
| DT support | Yes | Yes (DT states support for SGP.22 and SGP.32) | Yes, DT product |
GSMA SGP.22 remains the GSMA consumer eSIM specification; DT lists it as supported alongside SGP.32. DT publishes nothing on a retirement of the older M2M architecture, SGP.02.
Cloud of Things and T-IoT
Section titled “Cloud of Things and T-IoT”Cloud of Things is the DT IoT application platform, offered as Cloud of Things SMART, ENTERPRISE and PRIVATE. The certification deck places certified modules under three offer types: DT IoT platform, third-party IoT platform, and connectivity only. Certification does not depend on the platform.
T-IoT was launched by T-Mobile US and Deutsche Telekom on February 21, 2022 as an enterprise offer for global IoT connectivity, announced across 188 destinations on 383 networks, with a single view over T-Mobile Control Center and the DT M2M Service Portal. It is a commercial offer: the DT deck is explicit that DT and T-Mobile US certification processes remain separate.
NB-IoT roaming
Section titled “NB-IoT roaming”On June 4, 2018, the GSMA announced that Deutsche Telekom and Vodafone had completed the first international NB-IoT roaming trial in Europe, using DT global SIMs on Vodafone Spain and Vodafone SIMs on T-Mobile Austria, with test cases covering PSM, long periodic TAU, throughput and round-trip time. A trial is not a roaming agreement: check NB-IoT roaming coverage per country with DT before relying on it. The No Harm to Network guideline adds the roaming keep-alive rule shown above.
Claims the texts contradict
Section titled “Claims the texts contradict”| Common claim (including on earlier versions of this page) | What the DT and GSMA documents say |
|---|---|
| "GCF or PTCRB is a prerequisite; without it DT does not open the acceptance phase" | DT does not require module suppliers to present GCF certification. Without GCF, a module can reach Limited Certification. PTCRB is not part of the DT process. |
| "GCF certification is enough to use a module on DT" | DT says GCF does not prevent most of the critical interoperability issues it finds, and DT tariffs require DT-certified modules. |
| "DT runs a device acceptance programme listing finished products" | DT certifies chipsets and modules. Devices go through a separate, free partner onboarding for listing and promotion. |
| "Tests run in a DT-recognised laboratory" | Tests run at the DT Group Test Facility in Germany, with a facility in Poland able to patch in. |
| "LTE-M is certified across the group footprint" | LTE-M certification covers Austria, Germany and the Netherlands, with Hungary planned. |
| "nuSIM is closed and cannot be re-provisioned" | nuSIM profiles can be replaced in the field through FOTA or LwM2M, any Data Preparator can serve any nuSIM chip, and DT ships an open-source reference Loader. What nuSIM lacks is OTA access inside the SIM. |
| "nuSIM profiles are under 1 KB" | The DT pages say profiles are "very small"; they give no figure. |
| "DT steers products away from SGP.02 on a set schedule" | DT publishes no SGP.02 schedule; it states support for SGP.22 and SGP.32. |
| "No Harm to Network is an informal best practice" | The DT guideline makes "SHALL" items mandatory and sets numeric per-device limits. |
| "A DT dossier also opens T-Mobile US" | DT: separate certification processes; the US is not covered. |
Practical sequence for a product maker
Section titled “Practical sequence for a product maker”- Pick the module from the DT list: open the detailed overview on the IoT Hardware Ecosystem and check the grade, the countries per technology, the RPM column and the certified firmware version.
- Check the volume: if the module lacks the TS.34 RPM, the certification caps you at 10K units per IoT application.
- Freeze the firmware on a certified version, or plan for DT to certify the next one; the list tracks each firmware release.
- Design the application to the No Harm to Network limits: attach and message budgets, randomisation, back-off, dual stack.
- Choose the SIM: physical or MFF SIM, SGP.32 eUICC, or nuSIM on one of the listed nuSIM modules.
- Onboard the device as a partner if you want it listed and promoted in the DT portfolio.
For timing and budget across carriers, see the certification timeline and certification costs. For the European regulatory side, see CE vs FCC EMC and EU + US dual certification. For terminology, see the spilma glossary.
See also
Section titled “See also”- GCF, Global Certification Forum
- Vodafone Global IoT acceptance
- Orange Live IoT certification
- 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
- Verizon Open Development
Sources & references
- DT Certification Process for Chipsets and Modules (PDF), Deutsche Telekom IoT GmbH hardware.iot.telekom.com/attachment/subject_attachments/dt_chipset__module_certification_process.pdf
- Deutsche Telekom certified chipsets and modules, detailed overview (XLSX), Deutsche Telekom IoT GmbH hardware.iot.telekom.com/attachment/subject_attachments/deutsche_telekom_certified_chipsets_modules_-_detailed_overview_external.xlsx
- IoT Solution Guidelines, No Harm to Network for IoT Device Applications, version 2.9 (PDF), Deutsche Telekom IoT GmbH hardware.iot.telekom.com/attachment/subject_attachments/iotsol4.pdf
- IoT Solution Guidelines, 5G for IoT Connectivity, version 1.2 (PDF), Deutsche Telekom IoT GmbH hardware.iot.telekom.com/attachment/subject_attachments/iot_solution_guidelines_-_5g_for_iot_connectivity_en_v1.2.pdf
- Device Onboarding and Supplier Partnerships (PDF, May 2021), Deutsche Telekom IoT GmbH hardware.iot.telekom.com/attachment/subject_attachments/device_onboarding_and_supplier_partnerships.pdf
- Telekom IoT Hardware Ecosystem, user guides, Deutsche Telekom hardware.iot.telekom.com/Learn/UserGuides
- IoT Device Certification, T IoT Hub documentation, Deutsche Telekom hub.iot.telekom.com/docs/device-to-cloud/general-info/iot-device-certification/
- nuSIM, the integrated SIM for the Internet of Things, Deutsche Telekom iot.telekom.com/en/iot-connectivity/isim
- IoT and M2M SIM cards (eSIM, SGP.22 and SGP.32 support), Deutsche Telekom iot.telekom.com/en/iot-connectivity/iot-sim-cards
- Cloud of Things, IoT device management, Deutsche Telekom iot.telekom.com/en/iot-connectivity/iot-device-management
- Deutsche Telekom IoT, product portal, Deutsche Telekom iot.telekom.com/
- T-Mobile and Deutsche Telekom launch T-IoT (archive), Deutsche Telekom web.archive.org/web/20260311002351/https://www.telekom.com/en/media/media-information/archive/t-mobile-and-deutsche-telekom-launch-t-iot-648228
- More speed on old frequencies: 2G switch-off ensures better network, Deutsche Telekom www.telekom.com/en/media/media-information/archive/more-speed-on-old-frequencies-2g-switch-off-ensures-better-network-1081866
- GSMA announces completion of first European NB-IoT roaming trial (archive), Deutsche Telekom web.archive.org/web/2021/https://www.telekom.com/en/media/media-information/archive/completion-of-first-european-nb-iot-roaming-trial-526404
- TS.34 IoT Device Connection Efficiency Guidelines, v14.0, GSMA www.gsma.com/get-involved/working-groups/gsma_resources/ts-34/
- eSIM Consumer and IoT specifications (SGP.31, SGP.32 versions), GSMA www.gsma.com/solutions-and-impact/technologies/esim/esim-specification/
- IoT Device Certification Landscape, GSMA www.gsma.com/iot/resources/iot-device-certification-landscape/
- GCF, Global Certification Forum, GCF www.globalcertificationforum.org/
- PTCRB Certification Program, PTCRB www.ptcrb.com/
Frequently asked questions
- Does Deutsche Telekom require GCF or PTCRB certification?
- Not as an entry ticket. The Deutsche Telekom (DT) certification process deck states that, unlike most European operators, DT does not require module suppliers to present GCF certification; chipset suppliers submit evidence that they pass GCF test cases for layers 1 and 2. GCF status decides the grade: a module with GCF certification can reach Full Certification, a module without it can only reach Limited Certification. DT also says that GCF certification of a module is not good enough on its own, because it does not prevent most of the critical interoperability issues DT finds. PTCRB is not mentioned in the DT process.
- Does DT certify my device or my module?
- DT certifies chipsets and modules, following the logic "few chipsets, more modules, many devices". The tests focus on layer 3 procedures (RRC, NAS) and overall performance in latency, throughput and power consumption, run against DT radio and core configurations at the DT Group Test Facility in Germany. DT tariffs and SIM contracts require customers to use DT-certified modules. Finished devices are handled separately, through a free partner onboarding that lists them in the IoT Hardware Ecosystem.
- What does DT certification cost?
- According to the DT process deck, certification of Mobile IoT (NB-IoT, LTE-M) and 5G chipsets and modules is free of cost. 4G, 3G, 2G and VoLTE certification is a paid service on request, with a quote from the DT Certification Program. The device onboarding deck describes partner device onboarding as completely free of charge. DT publishes no price for the paid services.
- What happens if a module does not implement the GSMA TS.34 Radio Policy Manager?
- It can still be certified, but with a volume limit of 10K units per IoT application, at both the Full and Limited grades and for chipsets too. The RPM is not required for LTE mobile broadband and 5G SA/NSA chipsets and modules. The RPM requirement comes from GSMA TS.34, the IoT Device Connection Efficiency Guidelines.
- Does DT certification cover T-Mobile US?
- No. The DT process deck answers this directly: T-Mobile US and Deutsche Telekom (Europe) have separate certification processes, and DT-certified modules are not thereby certified for T-Mobile US, or the reverse. The deck marks the US as not covered by DT certification. T-IoT, launched by both companies on February 21, 2022, is a commercial connectivity offer, not a shared certification.
- What is the difference between nuSIM and an SGP.32 eUICC?
- nuSIM is the DT iSIM: the SIM function sits in the radio module hardware, with no SIM card or separate SIM chip. DT removed over-the-air access, the SIM toolkit and Java Card applet support to keep profiles small. Profiles are prepared by a Data Preparator and loaded by a Loader Application at the module or device maker, and can be replaced in the field through FOTA or LwM2M device management. An SGP.32 eUICC is the GSMA standard for remote profile management on IoT devices; DT states it supports SGP.22 and SGP.32.
- Which countries and technologies does DT certification cover?
- The process deck lists 5G NR (NSA), 4G LTE, 3G, 2G, LTE-M and NB-IoT, with country lists per technology across Austria, Croatia, Czech Republic, Germany, Greece, Hungary, Montenegro, North Macedonia, the Netherlands, Poland and Slovakia. LTE-M certification covers Austria, Germany and the Netherlands, with Hungary planned. Certification covers the DT Group networks, T-Mobile Netherlands and 1NCE. There is a separate certification for 5G and 4G Campus private networks.
- Is Cloud of Things mandatory?
- No. The DT process deck shows certified modules used with the DT IoT platform, with a third-party IoT platform, or in connectivity-only offers. Cloud of Things is the DT IoT application platform, sold as SMART, ENTERPRISE and PRIVATE. The DT No Harm to Network guideline likewise says the IoT service provider may host its application on its own server or cloud platform, or integrate with the DT IoT platform.