Deutsche Telekom makes it easy to get started with IoT.
Our IoT network has been built to ensure that your sensor data arrives quickly, reliably and secure.
The thing for IoT Creators allows you to easily register and activate your devices and connections, verify the communication over the network (2-way communication) and provide a callback URL to your own application environment where you can process the data into actions. Via HTTP post you send your sensor data to your own application environment. We even support some pre-integrations with existing cloud platforms. This way it will take you almost no development time to connect your devices to your application environment.
Four simple steps
to have your IoT device sending data to your application.
1. CONFIGURE YOUR HARDWARE
Configure your hardware to connect to our network and insert the SIM card.
2. REGISTER YOUR DEVICE
Register your device’s IMEI number through The Thing for IoT Creators or our API.
3. SET UP AN ENDPOINT
Set your own (cloud) server as a destination so our network knows where you want to receive your data.
4. YOU ARE READY TO SEND DATA
Congratulations! Your IoT connection is ready to use!
Ready to grow
We help you to easily set up and manage connections in our ‘thing’. This way you can send your sensor data securely from your device to your own cloud environment and vice versa. This makes setting up a connection almost as easy as setting up a Wi-Fi connection and also gives you the benefits of our very energy efficient and secure networks.
You can easily manage your connectivity for your devices by registering or removing devices on our network. For these devices you can also directly verify the status of the device and the last message.
Our ‘thing’ is part of Deutsche Telekom’s IoT Hub, thus very scalable and it grows easily with your demand. This means, you can start small with a few devices and easily scale it up (or down) when needed.
We support multiple communication protocols (CoAP, UDP and NON-IP), which makes it very flexible when choosing hardware. You can easily switch to another protocol anytime. This could be the case if you, for example, would like to switch to other hardware and the corresponding communication protocol.
For sending your sensor data to your own application environment we currently support HTTP(S) posts, which is used by most cloud platforms. So you are very flexible in setting up your own application environment.
Your favorite protocol is not supported yet? Don’t worry, we always actively strive to expand the amount of supported protocols. Let us know in the forum which procotol you are missing.
The sensor data from your devices can be sent to multiple endpoints. This way you can send your data to your own environment, but also directly to the environment of a customer. This way you can easily use and share your data in parallel and in multiple ways. This can be useful, for example, for setting up a test environment next to a production environment, for creating a backup database or for multiple applications in the value chain.
Our Service Capability Server can also be accessed via a REST API for integration into your own environment. For example, you can register and delete your devices on our IoT network, you can specify the destination to which the sensor data should be sent, you can request a list of your registered devices and much more, all via API calls.
IoT Creators use NB-IoT as access connectivity
Our IoT access includes a fully managed LPWA (Low Power Wide Area) network service.
Our IoT network enables communication of small amounts of data over large distances. Compared to GSM (2G, 3G and 4G) NB-IoT provides 10x better coverage.
This good coverage is achieved by a high-power density, because radio transmissions are concentrated in a narrow bandwidth of only 180 kHz. The Coverage Enhancement (CE) functionality also offers the possibility to repeat the transmission of a message if necessary. This is at the expense of a lower data rate and can influence battery life. There are 3 different CE levels defined. CE level 0 is equal to the GSM coverage. CE level 1 is up to 10 dB higher gain and EC level 2 is up to 20 dB higher gain compared to GSM.
NB-IoT uses licensed frequencies. Because we are the only party allowed to use these frequencies (at least until 2033), there is no interference from other networks. For you, it means an extremely high availability of our IoT network.
In Europe, NB-IoT uses the 800MHz and the 900MHz band. In Austria, Germany and the Netherlands the 900MHz (band 8) is used. In Croatia, Poland and Slovakia, the 80 MHz (band 20) is used. The nice thing is that a lot of devices and an…
d antennas are suitable for the 900Mhz band, because this frequency range has been used for GSM since 1980.
Roaming with excellent coverage
NB-IoT networks coverage in Europe
NB-IoT is an international (3GPP) standard and developed in such a way that it can be used by any mobile operator worldwide. Within a few years an NB-IoT network will be active in most countries, so you are assured of a scalable application of your IoT solution.
On a global level, there are already several initiatives running with different operators and different countries to enable roaming. This will initially be made possible for pilot testing as NB-IoT is not yet fully deployed in many countries. In parallel there are already talks with the GSMA and other operators to standardize the roaming arrangements.
Deutsche Telekom has signed its first NarrowBand IoT (NB-IoT) roaming agreements with several European operator partners, offering roaming services in 18 countries. The cooperation with Swisscom, Telia Company and Vodafone brings Mobile IoT roaming services to a further nine European countries. Deutsche Telekom currently offers NB-IoT roaming in nine of its own markets.
Our NB-IoT network is set up as a dedicated network separate from the 2G, 3G and 4G network. The NB-IoT network is optimised for devices that send or receive small data messages every once in a while. In addition, these devices are not accessible to the network for most of the time because they are asleep. So even if it is very busy on the 4G network (where relatively large amount of data is streamed and devices are always accessible), this has absolutely no effect on the operation and performance of our NB-IoT network.
|Scalable to millions of devices and messages||High uptime|
|Low packet loss1||24×7 monitored to quickly intervene in any problematic events and thus guarantee a very high availability of the network|
|Low latency2||Use of licensed spectrum|
1 The messages sent from the device arrive on the network in almost all cases. Coverage is also important here. In tests we performed ourselves with good coverage where 30 devices on the same antenna sent a message of 250 bytes every second, the packet loss was on average below 1%. Should this occur, then your device will send the packet again. This is taken care of by our network and technology.
2 The latency when sending and receiving messages is generally less than 10 seconds. The latency is highly dependent on the coverage and load of the network. With very good coverage, the latency is often no more than a few seconds, but with a device that is underground and therefore has less coverage, the latency can sometimes exceed 10 seconds. The latencies for sending and receiving the data are the same, provided the device is not in deep sleep for receiving the message.
Extremely Energy Efficient
NB-IoT is designed for long distance data communication with the lowest possible energy consumption.
Our IoT network has several features that enable this extra low power consumptions (subject to availability per country and local conditions):
- PSM: to set your radio module in sleep mode.
- eDRX: extend the listening intervals of your radio module
- Long Periodic TAU: reduce the amount of Tracking Area Updates
These features make you independent of a fixed power connection and allows your device to run on a battery for years (e.g. on two AA batteries for up to 10 years)
Using the PSM, the radio module in the device can be put to sleep for 310 hours. During this sleep time the energy consumption is a few microamperes. The device will not communicate with the network during this time. If the device does want to send data, for example because a sensor has taken a measurement that exceeds a certain value, the radio module can automatically exit sleep mode and directly send the desired data over the network without first having to establish a connection with authentication and authorization. The security is maintained in the network during ‘sleep’. By regulating this sleep time as optimally as possible, energy consumption is reduced to a minimum.
For some use cases, where the device mainly receives data from the network and sends almost no data, the time the device listens to the network can be adjusted. This ‘listening appointment’ between the device and the network can be extended with eDRX every 10 seconds to once every three hours. Examples of these use cases are systems such as an irrigation system, which can then be operated remotely.
A device should give a Tracking Area Update to the network occasionally so that the network knows that this device is still ‘alive’ and with which cell it communicated the last time. The security keys are also quickly updated.
For our IoT network this TAU now takes place once every 310 hours and will soon be adjustable so you can make it happen less frequently. The TAU is connected to the PSM. After the PSM expires a TAU will automatically take place to let the network know that the device still has (and needs to keep) a connection to the network. If this doesn’t happen, another network attach will have to take place. This takes longer and consumes more time (and energy).
- Our radio network uses complex and difficult to crack SIM encryption (128 – 256 bits) to send your data encrypted by default.
- The data is encrypted between the NB-IoT device and our network using the standard LTE encryption. Between the network and the application environment, the data is protected using standard TLS encryption
- Your device is less vulnerable to hackers, because it is not directly connected to the internet. Our service capability server ensures secure data transportation between your device and your IoT platform.
- Out IoT network has an integrated overload flood protection when a device sends too many messages in a short period of time. By detecting this, the network can be protected against overloading, so that the other devices that do function properly do not suffer from this.