Dear customer,

In the table below, you will find the latest configuration of the PSM timers (Activity timer T3324 and Extended TAU timer T3412) in the DT NB-IoT networks.
Note: all parameters provided below are subjected to change and are therefore only indicative and provided without guarantee. This table shall be seen as a snapshot of DT’s network configuration and values may evolve over time.

As mentioned above, we are currently checking the minimum value for the T3412 timer (reported by users as being set to 2 hours) and will confirm this value asap.

@Ronan-Lacroix said in LTE-Cat.M1 Rollout in Germany:

Hi Alfons, Hi Thomas,

I have the pleasure to announce that LTE-M is now available in Germany throughout the country.
Please take a look at https://t-map.telekom.de/tmap2/mobileiot for a detailed view of our coverage map, as well as at https://iot.telekom.com/ for the available pre-paid offerings.

Looking forward to getting your return of experience on our brand new IoT network!

Kind regards,

Ronan

Hi Stefan,

A press release should be issued soon, and more information about the network features and benefits will be posted on this forum in the weeks to come.

Best,

Hi Timo,

Those strong delays are most probably a consequence of the weak network signal strength at your test location.

In CE-Level 2, the device has to repeat the same signal over the radio interface multiple times (up to 2048 repetitions in downlink, and 128 repetitions in uplink!) in order to enhance the link budget and ensure a successful signal transmission.
This has a direct impact on both the data throughput and the communication latency, which you see reflected in the Ping RTT.

This can be solved by improving the signal quality, for instance by changing the location of the device or by using a better antenna.

Best regards,

Ronan

eDRX is being deployed as we speak across our German NB-IoT network, and will be enabled in TMNL shortly thereafter.
We will inform you as soon as it is commercially available there!
Note that eDRX for NB-IoT is already live nationwide in our Magenta network in Austria.

eDRX however is not yet available in our LTE-M networks, but we plan to deploy this feature across our LTE-M footprint (currently Germany, Netherlands and Austria) beginning of next year.

The LTE-M coverage map for Germany is available under: https://t-map-ta.telekom.de/tmap2/mobileiot/.
LTE-M unfortunately isn’t available in the T-Mobile Czech Republic network yet.

@inka-O,

1. As stated above, we will implement eDRX for LTE-M beginning of next year, but we cannot tell you exactly when right now (our current target is Q1 2021). As far as we know, most of the other European LTE-M operators haven’t yet enabled eDRX neither, but also plan to deploy it next year.
2. eDRX does not exist in 2G, only in LTE, and deployed primarily (if not exclusively) in its Low-Power Wide-Area categories (i.e. LTE-M and NB-IoT).
3. PSM is supported in all of DT’s LTE-M networks as well as in all of our roaming partner networks. Like eDRX, PSM has only been standardized in LTE networks and is not available for 2G.

Best regards,

Ronan

Hi MeneerJacco,

You may want to specify the PSM Timer value to be used before entering Power Saving.
If you want the module to enter PSM right after leaving its connected mode, use for instance the command:

AT+CPSMS=1,,,,"00000000"

You may also want to provide a longer TAU timer. To configure for instance a TAU Timer of 3 hours and a PSM of 0s, enter:

AT+CPSMS=1,,,"00100011","00000000"

Best,

Ronan

@Marijn

Title has been fixed!

@inka-O , for detailed information about our LTE-M network footprint and the supported features, please check our documentation library: https://docs.iotcreators.com/docs/introduction-to-lte-m.
You should find an answer to all your questions above!

All features (e.g. PSM, LP-TAU, eDRX) when deployed are available nationwide.

@JakubT,

This essentially depends on your SIM contract and associated tariff. If this tariff includes EU-Roaming for instance, then Roaming in all Roaming Partner networks should be possible, and not only in DT’s own affiliates’ network.
Best regards,
Ronan

@JakubT ,
May I ask you if you’re still encounting roaming connectivity issues?
If you do, please don’t hesitate to provide us more details about the exact problem you’re experiencing!
Best regards,
Ronan

Hi @Alessandro-Parmigiani ,
The RRC inactivity timer is set by the network and cannot be modified by the device. Its value is usually consistent within one network (there are exceptions, though!) but it is not necessarily identical across all network technologies (e.g. NB-IoT and LTE-M).
Note that for NB-IoT, the RRC inactivity timer may also have different values depending on the CE-Level in which the module is (CE0, 1 or 2).

In Germany, the timer is set to 10s for LTE-M and between 20s and 30s for NB-IoT depending on the area.
We are however reviewing those values at the moment and will most probably shorten the RRC inactivity timer for NB-IoT in the near future, especially for CE Level 0 and CE Level 1.
We will gladly inform you via this post whenever this change has been performed!

If your application however does not expect downlink data after sending an uplink message, we strongly recommend using the Release Assistance Indication on NB-IoT to bypass this RRC Inactivity period and immediatly switch to Idle mode (as mentioned by Stefan de Lange above).

RAI is supported across all DT NB-IoT networks, with some regional limitations within our Polish network.
This feature unfortunately isn’t yet available for LTE-M, but has been standardized by 3GPP. It is therefore likely to be implemented in the future both by module vendors and network providers.

Hope this can help!

Best regards,

Ronan

@JakubT,

This essentially depends on your SIM contract and associated tariff. If this tariff includes EU-Roaming for instance, then Roaming in all Roaming Partner networks should be possible, and not only in DT’s own affiliates’ network.
Best regards,
Ronan

@JakubT ,
Could you help us understand what you exactly mean with “SIM-based restrictions”? Which specific issues are you experiencing?
Are you also talking about a network technology specifically (e.g. NB-IoT or LTE-M)?
Best regards,
Ronan

Hi MeneerJacco,

You may want to specify the PSM Timer value to be used before entering Power Saving.
If you want the module to enter PSM right after leaving its connected mode, use for instance the command:

AT+CPSMS=1,,,,"00000000"

You may also want to provide a longer TAU timer. To configure for instance a TAU Timer of 3 hours and a PSM of 0s, enter:

AT+CPSMS=1,,,"00100011","00000000"

Best,

Ronan

@FrancoisD ,
Cell reselection is natively supported by the NB-IoT network, there is nothing to be done at the module level to enable this feature.

Best regards,

Ronan

@lorenz
Dear Lorenz,
Thanks a lot for the feedback and I’m glad to see eDRX is delivering its promise on energy saving!
Another tip maybe: please consider setting your preferred Periodic TAU Timer to save further energy.
This can be done without setting any PSM activity timer with the CPSMS command, with a TAU-timer of up to 310 hours.
To enable Long-Periodic TAU without PSM, use value “11100000” for parameter <Requested_Active-Time>.
Best regards,
Ronan

@lorenz ,
Looking one more time at your logs above, it looks like you have enabled PSM in parallel to eDRX with a PSM Activity Timer of 10s only.
If this is the case, then eDRX obviously cannot work past those 10 seconds. Do you confirm?
Best,
Ronan

@lorenz ,
We will try to reproduce this issue with a BC95-G and get back to you.
We tried earlier with a BG95 (that uses a different chipset), but all tests have been successful, also with a 1nce SIM-card.
Kind regards
Ronan

@lorenz ,
Could you please double-check that you are indeed registered in the TDG network (26201), e.g. with command AT+QNWINFO
eDRX is also available to 1nce SIM-cards in our German network and AT+CEDRXRDP should return:
+CEDRXRDP: 5,“0010”,“0010”,“0100”

Best,
Ronan