Which protocol should I use for my NB-IoT / LTE-M Tracker?

Forums IoTStack News (IoTStack) Which protocol should I use for my NB-IoT / LTE-M Tracker?

  • This topic has 1 voice and 0 replies.
Viewing 0 reply threads
  • Author
    Posts
    • #35367
      Telegram SmartBoT
      Moderator
      • Topic 5959
      • Replies 0
      • posts 5959
        @tgsmartbot

        #News(IoTStack) [ via IoTGroup ]


        Headings…
        IoT M2M blog
        Which protocol should I use for my NB-IoT / LTE-M Tracker?
        Which is better: UDP, TCP, MQTT, CoaP or LWM2M?
        IoT protocolls comparison

        Auto extracted Text……

        Which is better: UDP, TCP, MQTT, CoaP or LWM2M?
        I am looking for the LWM2M protocol which consumes less energy & headers added to the data packet.
        MQTT & LWM2M are both lightweight & power-saving protocols.
        The akorIoT Group has a reference design for a tracker with an open block diagram using the BG96.
        IoT protocolls comparison
        The red area shows the necessary protocol overhead of the carrier: TCP/IP or UDP/IP.
        TCP/IP specifies that the telegram must be acknowledged automatically after transmission.
        If the transmission is negative or there is no acknowledgement, TCP/IP repeats the message several times automatically.
        However, if the acknowledgement is impossible for technical reasons, TCP/IP burns energy unnecessarily.
        However, data was already transmitted via radio before NB-IoT.
        6LoWPAN is a transmission protocol on IP (PPP) and was specified for radio and wire.
        The layer above it is UDP (not TCP).
        If you elect to user UDP, then the acknowledgement must be done in the protocol layer above it.
        The protocol layer above UDP is usually CoAP in the case of 6LoWPAN.
        CoAP regulates that a telegram is sent (with or without acknowledgement).
        We serve a customer who has been using GPRS for over ten years and transmits his position data with a proprietary protocol based on UDP.
        If you transfer this thinking to your design and use CoAP, then you can confidently do without the receipt, because 98% of the sent messages arrive on the server.
        LWM2M is based on CoAP.
        LWM2M is a protocol layer above CoAP.
        PPP => UDP/IP => CoAP => LWM2M
        PPP => UDP/IP => MQTT-SN => not defined
        PPP => TCP/IP => MQTT => not defined
        In the akorIoT Group, we decided for CoAP and defined the protocol layer above it ourselves.
        The most inconvenient way with the lowest energy consumption is NB-IoT NON-IP on UDP with its own protocol.
        If you plan like the akorIoT GROUP Internationally, then NB-IoT with CoAP is a good approach.
        Whether you then use LWM2M above, or your own protocol layer, is up to you


        Read More..
        AutoTextExtraction by Working BoT using SmartNews 1.0299999999 Build 26 Aug 2019

    Viewing 0 reply threads
    • You must be logged in to reply to this topic.