Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the limit-login-attempts-reloaded
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php on line 6114
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/functions.php:6114) in /mnt/web214/a1/45/52254245/htdocs/akoriot/WordPress_02/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":3696,"date":"2022-01-26T09:57:32","date_gmt":"2022-01-26T09:57:32","guid":{"rendered":"https:\/\/www.akoriot.com\/antenna\/nb-iot_and_lte_part-1-2\/"},"modified":"2022-01-30T16:09:10","modified_gmt":"2022-01-30T16:09:10","slug":"nb-iot_and_lte_part-2","status":"publish","type":"post","link":"https:\/\/www.akoriot.com\/antenna\/nb-iot_and_lte_part-2\/","title":{"rendered":"Energy-saving with NB-IoT and LTE-M part 2"},"content":{"rendered":"
[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”3.22″ global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_row admin_label=”row” _builder_version=”3.25″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”3.25″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||” theme_builder_area=”post_content”][et_pb_text admin_label=”Text” _builder_version=”4.14.5″ background_color=”#FFFFFF” background_size=”initial” background_position=”top_left” background_repeat=”repeat” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” sticky_enabled=”0″]<\/p>\n
<\/p>\n
In this series of three blog articles, adapted from the IoT M2M Times, we take a closer look at the energy consumption of NB-IoT and LTE-M. On their own, these physical layer standards do not deliver energy savings. The IoT developer has to choose the right AT commands and the right protocol with the right strategy for their chosen application. Sometimes we have to do without NB-IoT and LTE-M and take a different path. We hope that you have fun reading and learning.<\/p>\n
This second article compares LWM2M and MQTT.\u00a0 In a simple summary: MQTT can do practically nothing and LwM2M can do everything.<\/p>\n
So what can MQTT do?<\/strong><\/p>\n Message Queuing Telemetry Transport (MQTT) can, as the name suggests, only transport data with 14 control commands. Unfortunately, MQTT does not transport the data in an energy-optimised way for battery-operated devices. MQTT is a compromise between energy-saving and safety when transporting data having been developed by IBM for oil pipelines. Compared to the energy-hungry HTTP, MQTT requires less energy. HTTP was developed to transfer web pages based on TCP and therefore does not need to save energy. TCP is inherently very hungry because it repeats packets if there is no acknowledgement. Unfortunately, with MQTT, only the complex page description language HTML has been trimmed and the main problem caused by TCP has not been eliminated. MQTT makes it possible to work on the protocol layer with and without acknowledgements, however the layer below is TCP and continues to acknowledge. In addition, TCP servers have a time-out window that can often not be met via radio protocols leading to further energy-sapping retransmissions. #NBIoT<\/a>\u00a0and\u00a0#LTEM<\/a>\u00a0with a latency of up to 20 seconds are difficult to use with high energy consumption. The Power Saving modes of (PSM) with up to 310 hours and Extended Discontinuous Reception (eDRX) of up to 40 minutes cannot be operated at all with MQTT. The developers had a good idea in 1999 and unfortunately missed the chance to develop the MQTT protocol on User Datagram Protocol (UDP) instead of TCP.<\/p>\n What can CoAP do?\u00a0<\/strong><\/p>\n CoAP was published 10 years later in December 2009 as “CoAP Feature Analysis draft-shelby-6lowapp-coap-00<\/em>“. Like MQTT, it can transport data. It was specified as a transmission protocol for use in restricted networks and nodes for M2M applications. These constrained nodes often use 8-bit microcontrollers with little memory. Wireless networks such as 6LoWPAN often have a high packet error rate. The special conditions and packet loss were taken into account in the specification of CoAP from experience in the 6LoWPAN world. CoAP used UDP instead of TCP. It has only four control commands (Get, Put, Delete and Post). UDP does not acknowledge at its protocol layer. An acknowledgement is only made one level higher with CoAP. Within CoAP, commands can be sent with or without an acknowledgement. Because the fill level of a tank or a water meter is sent cyclically, an acknowledgement is usually unnecessary. Packet loss is not critical. Since CoAP on UDP or SMS has no time-out, a few minutes delay with SMS or hours and days with NB-IoT PSM and NB-IoT eDRX are no problem. NB-IoT Release Assistance Indication (RAI) immediately switches off the receiver after sending and thus fits perfectly with CoAP without acknowledgement. CoAP is in perfect symbiosis with NB-IoT and LTE-M. The first version of the specification had 14 pages, but had grown to 110 pages over several adaptations by 2013.<\/p>\n What can LwM2M do?\u00a0<\/strong><\/p>\n