Onomondo

- Onomondo Core Network
- Device: applicable to all

How to test Mobile Terminated (MT) traffic on the Onomondo network?

I want to test the Mobile Terminated scenario, where the NB-IoT device is <code>EPS Attached</code> and in <code>RRC Idle</code> mode. Is this supported?

How can I ensure that the connection is kept alive, even when the device is idle and there are incoming messages from the server sent to device IP every X minutes?

- How to test Mobile Terminated (MT) traffic on the Onomondo network?
- I want to test the Mobile Terminated scenario, where the NB-IoT device is <code>EPS Attached</code> and in <code>RRC Idle</code> mode. Is this supported?
- How can I ensure that the connection is kept alive, even when the device is idle and there are incoming messages from the server sent to device IP every X minutes?

There are multiple options to test MT traffic and maintain the NAT mapping.

Send keepalives from the device every 5–10 minutes to prevent <a href="https://help.onomondo.com/en/articles/221982-what-is-the-nat-timeout-on-the-onomondo-network">NAT timeout</a>.

- Fx., a single <code>0xFF</code> byte — from the device to your server.

Use MQTT or CoAP to maintain sessions with built-in keepalives.

- These maintain live sessions and help keep NAT open with built-in keepalives.

Adjust for PSM/eDRX (if applicable) so keepalives are sent during active windows.

- If the device is asleep, it won’t send the keepalive — and the NAT mapping will expire.

1. Send keepalives from the device every 5–10 minutes to prevent <a href="https://help.onomondo.com/en/articles/221982-what-is-the-nat-timeout-on-the-onomondo-network">NAT timeout</a>.
 - Fx., a single <code>0xFF</code> byte — from the device to your server.
2. Use MQTT or CoAP to maintain sessions with built-in keepalives.
 - These maintain live sessions and help keep NAT open with built-in keepalives.
3. Adjust for PSM/eDRX (if applicable) so keepalives are sent during active windows. 
 - If the device is asleep, it won’t send the keepalive — and the NAT mapping will expire.

The NAT mapping is created when the device sends Mobile Originated (MO) traffic. 

- The connection has to be initiated by the device first. 
- It’s not “true MT” in a 3GPP-core-initiated sense, but for many use cases, it’s more than sufficient.

Set up an <a href="https://help.onomondo.com/en/articles/212007-setting-up-an-ipsec-connection">IPSec connector</a>.

This eliminates the need to worry about NAT timeout.

IPSec connectors are currently in beta.

- This eliminates the need to worry about NAT timeout.
- IPSec connectors are currently in beta.

Using the API, <a href="https://docs.onomondo.com/#1c02e2f8-bc94-4234-bac7-62d8d12bd245" rel="nofollow noopener noreferrer" target="_blank">POST a message</a> to the device every time you need to send data to the device.

This solution also eliminates the need to worry about NAT timeout.

If the protocol is <code>udp</code> - the packet will be sent to the receiving port.

If the protocol is <code>tcp</code> - connection will be established with the device on that port, and the data will be sent.

If the device does not accept incoming connections on that port - the data will be discarded.

- This solution also eliminates the need to worry about NAT timeout.
- If the protocol is <code>udp</code> - the packet will be sent to the receiving port. 
- If the protocol is <code>tcp</code> - connection will be established with the device on that port, and the data will be sent. 
- If the device does not accept incoming connections on that port - the data will be discarded.

How to test Mobile Terminated (MT) traffic on the Onomondo network?

Environment

Question

Answer