# Smart Energy Meters for Smart Grids, an Internet of Things Perspective
## 3 Computational Platforms
\begin{table}
\begin{tabular}{p{128.0 pt} p{284.5 pt}} \hline \hline
**Protocol** & **Details** \\ \hline \multicolumn{3}{c}{**Protocols for data communication**} \\ \hline Data communication protocols are middleware layers that enable data pipelines to application interfaces. Network details are transparent to applications which see through all the infrastructure and receive the data from end nodes as if directly accessing those nodes. \\ \hline MQTT & **RESTful:** No. **Transport Protocol:** TCP. **Architecture:** publish/subscribe. **QoS:** yes. **XML support:** No. **Encoding:** Binary. **Latency:** low. **Bandwidth:** higher. **Message size:** lightweight, **Energy consumption:** lower. **Connectivity:** one-to-one, one-to-many, many-to-many \\ \hline HTTP & **RESTful:** Yes. **Transport Protocol:** TCP. **Architecture:** request/response. **QoS:** limited. **XML support:** yes. **Encoding:** text. **Latency:** largest. **Bandwidth:** higher. Message size:** highest, **Energy consumption:** highest. **Connectivity:** one-to-one \\ \hline DDS & **RESTful:** No. Transport Protocol: UDP. **Architecture:** broker-less publish/subscribe. **QoS:** elaborate mechanism consisting of 23 QoS profiles. **XML support:** No. **Encoding:** binary. **Latency:** low. **Bandwidth:** low. **Connectivity:** one-to-one, one-to-many, many-to-many, peer-to-peer. \\ \hline XMPP & **RESTful:** No. **Transport Protocol:** TCP. **Architecture:** Client/server request/response and publish/subscribe. **QoS:** none. **XML support:** yes. **Encoding:** text. **Latency:** low. **Bandwidth:** low. **Message size:** lightweight. **Energy consumption:** higher. **Connectivity:** one-to-one \\ \hline AMQP & **RESTful:** No. **Transport Protocol:** TCP/SCTP. **Architecture:** Client/server and client/broker, request/response and publish/subscribe. **QoS:** yes. **XML support:** No. **Encoding:** binary. **Latency:** lower. **Bandwidth:** high. **Message size:** lightweight, **Energy consumption:** slightly higher. **Connectivity:** point-to-point \\ \hline CoAP & **RESTful:** Yes. **Transport Protocol:** UDP. **Architecture:** request/response or publish/subscribe. **QoS:** yes. **XML support:** No. **Encoding:** binary. **Latency:** lowest. **Bandwidth:** lowest. **Message size:** lightweight, **Energy consumption:** least. **Connectivity:** one-to-one, many-to-many \\ \hline \hline \end{tabular}
\end{table} 
Table 8: _Cont._program for a smart meter is given in [191]; it is used in various techniques for smart grids, as mentioned earlier. In [192], an embedded energy meter is designed that can implement a prepaid electricity tariff, which uses inductive measurement techniques for measurement and a microcontroller for communication. An apparent energy calculation algorithm is designed in [193] for a smart meter. An Arduino-based GSM and ZigBee wireless communication smart meter is implemented in [194]. In [195], a GSM-based smart meter using an IEC 61,036 compliant power measurement meter is designed. An active energy meter with an MPC3905A microcontroller and a GSM network is implemented in [196]. An 8051-based energy meter consisting of an LCD, EEPROM, RTC (real-time clock), EMM (energy measuring module), temper detection unit, and GSM module is implemented in [197]. Another GSM-based smart meter using an 89C52 MCU, a DS12887 clock, X25045 timer, and a UART chip to interface to a GSM module is reported in [198]. To utilize a pre-built GSM-based AMR (automatic meter reading) infrastructure, a ZigBee interface is designed to collect metering data and relay to GSM collection modules in [199]. A ZigBee-based smart meter is designed in [200]; it has an interface protocol implemented for star topology. A power line communication (PLC) SoC-based watt-hour meter is reported in [201]. An ARM-based power and power quality meter using Wi-Fi is implemented in [202]. In [202], a legacy modem-based power meter is designed and implemented that uses a plain old telephony network system (POTS).