6

I am working with NB-IoT Modem - Quectel BC95 that will be used in a simple IoT sensor that will periodically (Once per hour) send measurements to our server.

Because of the restriction in place by the service operator, I can't use the hardware implementation of CoAP/M2M (Neil Messaging Protocol - as they call "it") and I am stuck with Raw UDP Messaging (Socket).

I want to keep it real simple and keep the "size" of the data at a minimum but still, be prepared that server can expect thousands of these sensors to stream data. I was thinking about just a simple JSON/CSV values inside a UDP message but have no idea if this solution is "Robust" or Secure enough.

Can you please point me into the right direction? Is there any "standardized" way to send data from IoT sensors to a server while using just a simple UDP socket and is easy to implement on the MCU side (We are very resource limited)?

  • the UDP protocol does not have a guaranteed delivery mechanism – jsotola Oct 26 '18 at 5:52
  • UDP is great if you're ok with losing packets now and then. It may work for you with sensors continously sending data. – Paulo Soares Oct 26 '18 at 9:20
  • 1
    What "restriction in place by the service operator" could prevent you to use a well-defined standard protocol? Rolling your own will just mean to re-invent what has already been invented. Eg. for privacy you'd have to use DTLS over UDP (coaps://), for reliability you'll need sequence numbers and retransmissino (part of CoAP), etc. – Gambit Support Oct 26 '18 at 14:31
  • What security protocol will you use to validate the data is real and not faked? – SeanJ Oct 28 '18 at 22:46

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.