UDP Connector
Connector Details – UDP
The UDP connector allows the platform to receive device updates over the UDP protocol. This is typically used by devices communicating via NB-IoT, Cat-M, or similar wireless technologies, though direct wired UDP connections are also supported.
Incoming data must be a HEX-encoded string that includes an embedded identifier to determine the source device.
Required Information
To configure a UDP connection, the following must be provided:
-
Integration name
Specifies how the platform processes and validates incoming UDP data. It identifies the type of device sending the data and ensures correct matching on the platform. -
Port number
The UDP port where the platform listens for incoming data.
Important:
All UDP ports are closed by default. A support request must be submitted to open the desired port.
There are 65,536 available UDP ports (0–65535).
Security Considerations
UDP data is transmitted unencrypted and can be intercepted once it travels over public networks.
Even though the payload is HEX-encoded, it is not secure by default.
Do not use UDP-only communication for sensitive data over public networks.
To secure the data, the platform supports DTLS (Datagram Transport Layer Security). DTLS can be enabled if the connected IoT devices also support it.
Physical UDP Device Configuration
When setting up the physical UDP device, configure the following on the device:
- The platform’s URL or static IP address
- The UDP port number opened for the connector
You can verify the platform's IP address via a domain lookup service. The IP is static and does not change.
Make sure the port configured in the device exactly matches the connector’s port.
When using NB-IoT or Cat-M, make sure to record the SIM card’s IMSI number so it can be assigned to the correct device in the platform at a later stage.
Creating UDP Devices
To register a UDP-connected device:
- Create a standard generic node in the platform.
- Use the corresponding integration identifier, as defined below.
| Integration Name | Identifier |
|---|---|
| IMBuildings | sensorId |
If NB-IoT or Cat-M is used, make sure to add the SIM card's IMSI number to the device's contextual parameters in the platform.
If no data is received, it’s important to know which SIM card the device is using. This allows you to verify in the SIM provider’s portal that:
- The SIM is active
- Data traffic is correctly routed through the expected APN - Access Point Name
Data Format & Translation
The received data must be a HEX string.
A translator must be selected or created to decode the data and assigned to the UDP device configuration.