This article has been accepted for publication in a future issue of this journal, but has not been
fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS
An Open Source Framework for Smart Meters:
Data Communication and Security Traffic Analysis
Rodrigo T. Caropreso, Ricardo A. S. Fernandes, Member, IEEE, Diana P. M. Osorio, Member, IEEE,
Ivan N. Silva, Member, IEEE
Abstract—In this paper, it is proposed a structured methodol-
ogy to define the architecture for a communication framework
with multi-frame capability, which can be embedded in a resi-
dential smart meter hardware for Smart Grid applications. This
framework is based on TCP/IP protocol, and it is considered
that data is exchanged via wireless. The architectural model
was based upon the state of the art in Software Engineering,
making use of Design Patterns and the principles of low coupling
and high cohesion which result in a solution that is both, more
reliable and maintainable. A security module is also provided
and the framework performance is evaluated, in terms of packet
throughput and computational effort of the security layer on the
processing device, via practical experiments of some laboratory
scenarios. Furthermore, errors on some frames are introduced
in order to evaluate the feasibility of this framework in real
field applications. Results show that this framework architecture
supports acceptable transfer rates even with extra computational
cost due to the use of data encryption and separated processing
modules, making it a feasible proposal for the considered appli-
cation context.
Index Terms—client/server framework, data exchange, embed-
ded algorithm, encryption, private key, smart meters.
I. I NTRODUCTION
R ECENTLY, Smart Grids (SG) have received great at-
tention by industry, regulatory agencies, and scientific
community for being recognized as the major evolution of
power systems. This concept allows the integration among
electrical power systems and communication technologies in
order to improve power production, management and con-
sumption in an intelligent, sustainable, and reliable manner [1].
In this context, smart meters represent a key component of
a SG, being designed to monitor and record the electrical
energy consumption and enabling a utility to gather this
information [2]. Thus, smart meters provide a communication
interface for the grid’s last mile consumers, composing the
so-called Advanced Measurement Infrastructure (AMI) [3].
As a result, data collected and processed by a smart meter
must eventually be exchanged with another grid node, such as
a concentrator, which will create a huge traffic demand, mak-
ing the evaluation of this data traffic a major concern on the
aspects of reliability (QoS), standardization, and security [4].
It is worthy to mention that concepts such as Neighborhood
Area Networks (NAN) and Building Area Networks (BAN)
Manuscript received October 13, 2017; revised November 27, 2017; ac-
cepted February 01, 2018.
Rodrigo de T. Caropreso and Ivan N. Silva are with the Department of
Electrical Engineering, University of São Paulo, São Carlos, 13566-590,
Brazil. (e-mails: rcaropreso@usp.br, insilva@sc.usp.br).
Ricardo A. S. Fernandes and Diana P. M. Osorio are with the Department of
Electrical Engineering, Federal University of São Carlos, São Carlos, 13565-
905, Brazil. (e-mails: ricardo.asf@ufscar.br, dianamoya@ufscar.br).
0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
1
increase greatly data network traffic, assuming a relevant role
for the evaluation of data exchange on smart metering and
AMI [5].
There are several communication technologies such as
Bluetooth, Power Line Communication (PLC) and wireless
mesh networks using ZigBee under consideration with no
clear consensus for a standard so far. Some work has gotten
acceptable results using simulation analysis for mesh networks
and ZigBee [5], [6], whilst some research on data reliability
related to AMI has presented good results on analyzing
residential load control [7], [8].
In addition, side-by-side with data reliability issues, there
is a special concern on security aspects of grid data traffic,
where cyber-attacks may cause eavesdroppers to get access
on sensitive information collected by smart meters, which may
result in financial losses to companies or householders.
In this sense, several recommendations and guidelines were
proposed (and some of them are still under development), such
as European Union Directive (2017/27/EU) which establishes
a common framework of measures for the energy efficiency
within EU and security issues for smart meter and data
communication, and privacy of final consumers [9]. On United
States, the Energy Independence and Security Act of 2007
provided by the Department of Energy with the responsibility
of developing the smart grid program, which derives from
the US-FIPS-140 Publication Series to coordinate the require-
ments and standards for cryptography modules that include
both hardware and software components. The IEEE 1547 and
2030 series of publications and development activities address
priority engineering topics such as energy storage systems
security, conformance, and testing [10].
On the other hand, the Computer Systems Engineering is a
field under research for more than 40 years, focused on both
hardware and software development. In this context, hardware
development decisions are closely related to its embedded
software decisions [11], [12]. Also, a design problem known
as partitioning [13] states that it is a recurrent lack of vision
over the implemented requirements on hardware and software,
and there is not a deterministic solution for this problem [14].
It is important to notice that community efforts are oriented
to define algorithms or communication evaluation (infrastruc-
ture) though there is a lack for works that present, in details,
the model of their methodologies in terms of data com-
munication and standardization with no application protocol
defined to exchange data. Thus, one of the major obstacles
when designing a smart meter with such functionalities is
the interoperability on the grid using distinct communication
devices.
Following the above context, this paper proposes a multi-
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS
frame communication framework architecture model, which is
open and scalable.
The main contributions of this paper is three-folded: 1)
to propose a structured architecture definition for a data
process and communication framework. This framework has
Client/Server multi-frame capability by using TCP/IP protocol
on a wireless network. 2) to define an inter operable and op-
erating system module-based architecture for the framework,
which can be embedded in a residential smart meter hard-
ware for Smart Grid applications as well as on concentrator
nodes. 3) to evaluate proposed architecture via experimental
measures, when the majority of related literature is focused on
network simulations.
The wireless network was defined because it is easy to
configure and deploy, when compared to wired networks
(and throughput tends to be lower which configures a ’worst
case scenario’ evaluation). A security model based on the
OpenSSL Library is also implemented and evaluated in order
to establish the computational cost of encryption algorithms on
bidirectional communication. Furthermore, the entire proposed
methodology is based upon Object Oriented Model and Design
Patterns principles where all schemes being presented on
Unified Modeling Language (UML) diagrams which can be
easily reproduced and reused.
The rest of the paper is organized as follows. Section
II presents some related works on the area. Fundamental
concepts on Client/Server Architecture are presented on Sec-
tion III. Section IV describes the main aspects concerning
security and how it was implemented on framework. Section
V describes the object oriented implementation of framework
modules. Section VI presents the practical experiments and
analysis on packet transfer rate and, finally, Section VII
concludes the paper.
II. R ELATED W ORKS
A number of data exchange techniques have been investi-
gated in distinct context for SG and its challenges related to
data communication and security [4], [15].
Regarding data privacy and grid security, some proposals
addressing security solutions and authentication protocols for
SG have been presented in the literature [16], [17]. In
[18], a Transport Protocol for Smart Grid is proposed and
the concept of aggregation at the communication transport
level is introduced to address traffic issues. In [6] data
communication interference analysis is conducted through a
theoretical approach on ZigBee network.
It is important to highlight that on aforementioned works,
there is a lack of software modeling in order to reproduce
the communication layer and embed it on a meter. In [19], a
software model for a smart metering gateway is presented and
discussed. However, the model is not implemented and tested
for performance evaluation.
The approach followed by this paper aims to overcome
the lack of modeling for an open communication and service
layer which is the presented framework. Thus, some of the
main characteristics of the aforementioned works can be
summarized on a table:
0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
2
TABLE I
C OMMUNICATION F RAMEWORK CHARACTERISTICS
ID IC SC MF SM ToE TR
A [18] N N N N Sim 500 kbps
B [19] N/A Y N Y N/A N/A
C [16] N Y N N Sim N/A
D [6] Y N N N HW/Sim 4.5 Mbps
Table I identifies the following characteristics for each
framework: if it interoperability capabilities (IC); security
capabilities (SC); multi-frame capabilities (MF), if it was
provided a software model (SM), type of experiment executed
(ToE) where HW means hardware and ’Sim’ indicates that a
simulation tool was used; and the transfer rate when applicable
(TR).
III. C LIENT /S ERVER A RCHITECTURE
According to the Internet Protocol (IP), which is commonly
employed for data exchange, the communication can be per-
formed by two different protocols, namely [20], [21]:
1) Transmission Control Protocol (TCP): a connection-
oriented data exchange with ”delivery assurance”;
2) User Datagram Protocol (UDP): a connectionless data
exchange for streaming communication or asynchronous
events, i.e. alarms triggering and publisher-subscriber
messages.
For each of the above protocols, a limit size for pack-
age transmission, the so-called Maximum Transmission Unit
(MTU), is defined. Thus, for the Ethernet frames of the
proposed framework, the maximum size of the package, when
it reaches the Logical Link Control layer (just before being
sent as an electrical signal), is 1500 bytes.
In this sense, in order to offer a reliable data exchange
in a SG environment and to support interoperability between
device manufacturers, which is required by SG standards or
recommendations such as IEC 61850. Then, in addition to
the communication aspects, the qualitative properties of the
devices must be observed by considering its configuration and
management [22]. Such issues must be implemented on the
Communication Framework, as a Data Exchange Middleware,
which is a set of services associated to the Protocol Stack
located between network and application layers. Therefore,
these services can be divided into the following categories:
1) Client/Server – centralized and connection-oriented
model between two network devices. It is focused on
synchronous message exchanging, where a Client sends
data and waits for the Server response [23];
2) Publisher/Subscriber – distributed and non-connection-
oriented model, where two or more network devices
may be involved. Herein, the message exchanging flows
asynchronously, where data is delivered from a Publisher
to the Client, subscribed for receiving that specific
message [23].
It is worthwhile to mention that the amount of data for
gathering and processing is going to define the assertiveness
of the decisions regarding energy and consumption on the
entire SG. Therefore, a higher volume of data collection,
storage, traffic and processing is required. Hence, to comply
with this, it is necessary to embed a multi-frame capability
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS
on the framework services in order to make it capable of
sending pieces of information beyond the MTU limitation in a
controllable way. Taking this into account, for the framework
proposed on this research, the Client/Server architecture was
modeled first, since it provides a better control on the measured
throughput as well as the security issues described on the next
section.
The object-oriented implementation proposed on this paper
enfolds a Client/Server architecture with synchronous data
exchange and support for high speed multi-frame traffic. Thus,
one of the key aspects of the Server Application is, precisely,
supporting multiple connections. Therefore, the implementa-
tion must have multi-threading capability. Hence, it is possible
to model the connection mechanism as well as the iterations
and procedures involved in a Client/Server connection.
These procedures can be understood by the sequence di-
agram depicted in Fig. 1, where it can be noticed that the
Server creates a socket object through the Socket() method,
followed by the TCP initialization by using the methods Bind()
and Listen(). Then, the Server stays on a wait state until a
Client establishes a connection through the Accept() method.
Meanwhile, the Client application establishes a connection
with the Server through the Connect() method, after creating
its own socket object. At this moment, the Server creates a
thread for handling the connection with the Client and returns
to listen for new connections.
Fig. 1. Connection flow for client/server multi-frame data exchange.
Moreover, it is important to mention that Send() and Re-
ceive() events are the effective transport-frame core, where a
number of N frames can be exchanged until a fail occurs or
the Client forwards a Close() event indicating the end of the
current connection.
IV. DATA S ECURITY
A device capable of gathering information on energy con-
sumption, as the smart meter, may provide several advantages
for the analysis and performance of the SG, since it can
define user profile and prediction for energy usage [24], [25].
However, all data generated and transmitted by such devices
0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
3
is vulnerable of being analyzed by untrusted entities. Hence, a
framework providing a common and extensible interface, with
multi-frame and security capabilities, is attractive from a safe
Data Analytics perspective. Considering this, a security model
is proposed regarding usual encryption algorithms related to
data exchange, which are summarized as follows:
• Symmetric-key algorithm – it considers that both sender
and receiver share a unique key, which is used to encrypt
or decrypt the message. The drawback of this algorithm
is that if a third party has access to the key, the security
of data is lost;
• Asymmetric-key algorithm – it is also called “Public-
key cryptography” as it makes use of two distinct keys
(mathematically related), a public key that can be dis-
tributed and a private key that must be safely stored by
its owner. A message encrypted with the public key can
only be decrypted by its correspondent private key and
vice-versa.
Thus, the security protocol proposed in this paper follows
the three-step handshake depicted in Fig. 2.
Fig. 2. Procedures of security socket layer (SSL) 3-way handshake.
As can be noticed in Fig. 2, the security handshake on the
framework is performed as follows:
1 - The Client starts a connection to Server and sends
its own certificate encrypted with the Server’s public key. In
turn, Server decrypts the certificate using its private key, and
sends its own certificate encrypted back to Client (if Client’s
certificate is valid);
2 - After both sides have validated their respective certifi-
cates, Client creates a symmetric key for the current session,
encrypting it with the Server’s public key, and sends it to
Server where it is decrypted by Server’s private key;
3 - Finally, Client encrypts a pass phrase with the session
key and sends it to Server, which decrypts, validates the pass
phrase, and returns its own pass phrase for Client validation,
providing an additional level of authentication. Both Client
and Server can use this step to check if the encryption data
exchange services are fully-functional.
It is worthwhile to mention that symmetric key compu-
tational cost is lower when compared to asymmetric key
algorithm. For this reason, the asymmetric key is only applied
on the handshake phase, leaving the Smart Meter hardware
with more resources to perform other tasks. After handshake
phase is completed, all data transfer is performed upon sym-
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS
metric key algorithm. The algorithm used for Symmetric-
key encryption/decryption is the AES (Advanced Encryption
Standard), a block cypher standard; whilst the algorithm used
for Asymmetric-key encryption/decryption is the RSA (which
stands for Ron Rivest, Adi Shamir and Leonard Adleman)
[26], based on prime numbers factoring, widely applied on
communication networks.
Finally, the “certificates” used for client and server instances
are Global Unique Identifier (GUID) strings which can be
generated and validated for experiments. However, this kind of
certificate is not recommendable for real applications –where
a digital certificate provided by a certification authority is the
usual protocol to be followed. But, since one of the purposes
of this paper is to evaluate the performance of encryption algo-
rithms implemented on the multi-frame architecture embedded
on the smart meter, from technical perspective, the use of
encrypted GUID does not affect the results of the realized
experiments.
V. O BJECT-O RIENTED I MPLEMENTATION OF F RAMEWORK
The benefits of Object-Oriented Programming as well as
design patterns on systems’ modeling –to ensure reusability,
robustness, expansion and maintenance of a system– are
widely known [27], [28]. Therefore, it is important to mention
that the following model makes use of techniques available
on Software Engineering in order to have an extensible model
with low coupling level among the modules, which can be
incrementally implemented whenever necessary. In addition,
principles such as low coupling and high cohesion, when
correctly applied to an architectural design, may result in a
solution that is more reliable and maintainable [29], [30].
In this sense, for data exchange, the basic transport datagram
of the framework is depicted in Fig. 3.
Fig. 3. Transport data frame.
In this datagram, the iCommand attribute represents the
operation code to be executed, iFrameStatus is the current
communication state and enFrameType describes the class of
transferred frame (numeric or text, as an example). The fields
lQtyofTypedElements and iSizeOfTypeOnFrame are used to
describe any specific aspect regarding interoperability (size of
an integer, as an example).
The security issues are addressed by the fields deviceID,
which is the sender identification (usually encrypted as de-
scribed below) and udpSessionKey containing the payload
0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
4
encryption key for UDP message transfer (the key is also
encrypted as described below).
The payload is transferred on the pDataBuffer array and the
attributes iFrameIndex, iTotalFrames, and iTotalbytes provide
the dimension of this payload. Finally, the iDataBufferLength
is the size of data on current frame, which will be also used
for security purposes.
The extensibility contribution of this paper regarding the
framework communication model is provided by the Abstract-
Factory Design Pattern [28] which is depicted in Fig. 4.
By using this pattern it is possible to create several concrete
instances of Clients as well as Servers (respectively CSock-
etClient and CSocketServer) implementing the methods of
basic interfaces (CSocketClientBase and CSocketServerBase,
respectively). This pattern allows interoperability, since only
the concrete classes have to deal with issues such as Socket
communication, which has distinct procedures to be called
when running on Windows or Linux, for example. In addition,
the existence of distinct factories on the model provides a
decoupling between Server and Client behaviors and can be
extended individually as needed (to create a Broker Server, for
instance).
Fig. 4. Abstract client/server factory pattern.
The framework communication model is supported by Sock-
etCommLibrary depicted in Fig. 5.
It is possible to notice that the library is composed by
classes needed to instantiate a Client application CSocketClient
as well as a Server application CSocketServer, following the
pattern previously described (AbstractFactory). These classes
are responsible for supporting the connection and commu-
nication initialization procedures. It is important to mention
that a fundamental class for managing data exchange is the
CSocketManager class, which provides services capable of
performing a full-duplex multi-frame communication.
Finally, both Server and Client classes make use of
CSSLManager, which is a proxy for the SecurityLibrary.
It is important to highlight that one relevant distinction
between Client and Server classes is that CSocketClient is
a single-thread descriptor, which means it has only a single
instance of a CSocketManager object whilst CSocketServer
class is modeled as a multi-threaded connection server, thus
supporting multiple instances of CSocketManager objects.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS
An additional library was created to provide socket com-
munication and data access, namely SecurityLibrary, which is
depicted in Fig. 6. The security package is composed by Proxy
Design Pattern classes, which encapsulate the basic encryp-
tion/decryption services needed by the framework, where the
cryptographic algorithms are implemented by the openSSL, an
open-source toolkit.
Fig. 5. Framework client/server model.
Fig. 6. Security model.
All the models were implemented in C++, using the Stan-
dard Template Library (STL), C common libraries, and POSIX
functions, which simplifies the interoperability across distinct
platforms. Therefore, the classes were developed on Qt Creator
v3.5.1 as IDE and the final applications were cross compiled
for Linux (ARM Architecture) and natively compiled for
Windows. Thus, the same firmware can run on a PC or
embedded in a prototyping device.
The Beagle Bone Black Rev. B was used as the Smart
Meter for the initial experiments on the framework model due
to its ”open-hardware” characteristics. In this sense, it is a
prototyping board that can be easily customized for specific
0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
5
purposes. In addition, by modeling an architecture based on a
common Operating System (OS), rather than an specific Real-
Time Operating System (RTOS) or CPU instruction set, it may
attain a larger set of platforms with minor constraints.
Moreover, it is important to point out that while the man-
ufacturing characteristics of a commercial smart meter must
ensure a set of standards compliance, this paper has focused
on the design of a framework model for data processing and
transfer, which may be embedded in a low-cost customizable
hardware.
Regarding the proposed architecture, the smart meter is able
to execute specific and more complex tasks in a timely manner
as presented in [31] and provides a middleware interface for
hardware access so-called Hardware Abstraction Layer (HAL).
In this sense, developers may focus only on meter operation
and data processing, while data transfer and security is already
assured by the previously defined interface proposed in this
paper.
VI. A NALYSIS ON DATA PACKET T RANSFER R ATE
In order to evaluate the reliability and feasibility of the
multi-frame Client/Server architecture proposed in this paper,
a set of tests was performed taking into consideration scenarios
related to data traffic as well as packet loss. On both scenarios,
the Client application was running on the Beagle Bone Black
whilst the server was running on a Desktop Intel Core-i5-
3470M@3.20 GHz CPU with 8.0 GB RAM and Windows
10. The router used on this configuration is an IEEE 802.11g
wireless access point for 10/100 Base-T connections.
The parameters of each application can be configured
through a file of properties and, for the first experiment,
the SSL encryption was disabled to work as a reference
measurement. Both applications were capable of saving the
binary data on a file for further comparisons. Considering
this, it was possible to verify through experiments if both
encrypted and decrypted data were being transferred without
errors, avoiding false positives.
For Client and Server applications, it is necessary to config-
ure the Server IP and Port used for connection. Additionally,
to configure the Beagle Bone Black as a Client, it is necessary
to setup the sampling time which simulates data acquisition
on its analogical input. Since the main purpose of this paper is
to evaluate the performance of encryption algorithms, the data
frames were generated at the Client application by considering
the following rule:
N = Ts × 16000, (1)
where N is the number of samples to be sent to the Server with
each sample being a random number generated on the range
[0,1,800], and Ts represents the sampling time. This approach
corresponds to a sampling rate of 16 kHz, which is used to
capture analog signals on the Beagle Bone Black board A/D
converter that operates between 0 and 1,800 mV. Therefore,
the transferred data is composed by integers, each one of 4
bytes long, then, for a Ts = 10 s, there are N = 160,000
samples of 4 bytes resulting in a 640,000 byte data frame to
be transferred.
The transport datagram is capable of transporting a 1.024-
byte payload, which means that this particular example will
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS 6

consume 625 frames. Considering this, simulations were exe- deviation of ± 3.53 KB/s. This represents a 5% loss in transfer
cuted based on variations of the Ts by starting at Ts = 10 s rate when security is enabled which is a very acceptable result
and doubling the value on each subsequent data transmission. when considering the benefits on data security.
This procedure ends when the Smart Meter hardware used on
the tests threw a memory allocation exception representing the
maximum multi-frame size that can be managed at once on
the device’s memory.
A. Data Traffic Tests
The scenario for experiments is depicted in Fig. 7. For the
performance evaluation, the data transfer time was measured
considering the time spent to process each data frame and
reconstruct all data, and the time spent to decrypt the frames
after data reconstruction (for Server) and the CPU time versus
wall-clock time taken to perform the full data transfer (for
Client). It is important to verify hardware limitations and Fig. 8. Transfer rate for SSL ON/OFF considering 0% and 15% of
requirements for real field applications since a smart meter packet losses.
should not be an expensive device with a huge amount of
In Fig. 9 presents the real-time measured for a complete
memory, but it must be still capable of performing data
data transfer versus the number of bytes used on payload.
processing. Therefore, there is a trade-off between hardware
The experiment was performed with SSL OFF and SSL ON in
capability and computational overhead.
order to compare the overhead caused by encryption algorithm
as well as error rate on the processing time.

Fig. 7. Data traffic tests with SSL ON and OFF.

The packet loss was also simulated in order to evaluate
system’s performance in scenarios closer to real field applica-
tions. This was implemented at the Server as an algorithm
that randomly refuses packages and requests the Client to
retransmit them, thus simulating a frame transfer error that
may occur on field applications. The error rate was set in
2 values: 0% and 15% of error packages. These values can
be also configured by command line, thus optimizing the
whole experiment duration, without the need of recompile any
module of the framework.
Given the above context, Table II synthesizes the data
collected from the experiments, including the payload size
(number of frames) versus the Transfer Rate and Transfer
Times (Real Clock and CPU Clock) considering the minimum
and maximum error rates of the experiments (0% and 15%,
respectively). The experiments were performed with no data
encryption (SSL OFF) and using data encryption (SSL ON) in
order to compare the overhead caused by encryption algorithm
as well as error rate on overall transfer rate.
To analyze the Transfer Rates, Fig. 8 depicts the payload
size (number of frames) versus the transfer rate from II.
Considering the scenario with SSL OFF and error rate of
0% and 15%, respectively, it can be observed on Table II an
average transfer rate of 213.71 KB/s with standard deviation
of ±2.45 KB/s. On the other hand, considering the scenario
with SSL ON (error rate of 0% and 15%, respectively), Table
II shows an average transfer rate of 202.47 KB/s with standard
Fig. 9. Real-time versus payload with SSL ON/OFF.
When the Beagle Bone Black is operating as a Client (Smart
Meter), the transfer times based on real time (wall clock) did
not suffered significant changes caused by the use of security
module. This can be explained by examining the amount of
generated encrypted data before the network transfer. The
overhead caused by AES-256 encryption algorithm on payload
just added 1 extra data frame and this can be negligible
considering only the transfer time itself. Thus, the results show
that there is no significant overhead caused by the use of
security module.
However, as expected, the transfer time increases for higher
payloads and it was observed that the physical limit for data
transfer on the proposed framework architecture is 160,000
frames, which corresponds to a single 163 MB file transfer
at once for SSL OFF. It was also observed that the physical
limit for data transfer on the proposed framework architecture
is 40,000 frames for SSL ON, which corresponds to a single
40 MB file transfer at once.
It is important to highlight that both observed data transfer
capability are very acceptable considering real operation of
a smart meter, where such burst of data transfer should be
avoided.

0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS 7

TABLE II
B EAGLE B ONE AS A C LIENT - C OLLECTED DATA
Transfer Rate KB/s Transfer Times Real (ms) Transfer Times CPU (ms)
Fail Rate 0% 15% 0% 15% 0% 15%
Frames SSL OFF SSL ON SSL OFF SSL ON SSL OFF SSL ON SSL OFF SSL ON SSL OFF SSL ON SSL OFF SSL ON
625 159.55 159.75 148.46 180.84 3917.2 3639.4 4209.8 3999.3 259.9 244.9 296.1 283.5
1250 200.20 179.99 182.35 176.57 6243.8 6448.9 6854.9 7198.9 500.4 496.0 583.9 582.2
2500 231.11 191.80 195.24 178.41 10817.2 11308.3 12804.5 13063.2 996.3 998.0 1175.6 1163.9
5000 242.20 206.11 206.13 178.75 20644.5 21797 24256.4 25200.9 1999.1 1990.6 2318.45 2342.08
10000 244.57 208.47 212.42 173.28 40888.4 42657 47076.9 49593.4 3981.29 3998.68 4671.9 4689.2
20000 230.71 150.82 214.50 175.10 86690 83299.3 932380 98700.9 7979.8 7950.0 9394.4 9365.3
40000 236.23 214.17 215.94 174.94 169323 175055 369259 196610 15913.0 15992.4 18764.9 18781.2
80000 249.49 216.29 216.65 N/A 320656 N/A 737812 N/A 31691 N/A 37186.9 N/A
160000 238.50 210.72 216.86 N/A 670863 N/A 742642 N/A 63625.6 N/A 74363.1 N/A

However, the overhead of memory by the use of the are showed on Table III which synthesizes the payload size
encryption algorithm was very significant, which may lead to (number of frames) versus the CPU time employed on run-
possible enhancements and optimizations on the framework ning the client application. The Overall CPU Time (OCT) is
itself, but also it is an indicator that the encryption is a very compared with Data Encryption Time (DET) considering the
computing demanding for large files. analyzed situations for minimum and maximum error rates of
It can be observed that for the worst scenario (15% of the experiments (0% and 15%, respectively).
error rate and 160,000 frames with SSL OFF) the real-time
for full data transfer was measured as 736.6 s. In this case,
no significant overhead was observed for processing data after
building all the frames.
Finally, combining the worst scenario (15% of error rate
and 40,000 frames) the real-time for full data transfer was
measured as 196.6 s. On the same situation (40,000 frames
and 15% of error rate) for SSL OFF, the transfer time was
185.2 s, or approximately 6% faster.

B. Framework overall performance analysis

In order to explore in more detail how the Beagle Bone
CPU is impacted by framework services the performance of Fig. 10. CPU time versus real-time for data transfer (SSL ON/OFF).
the framework can be evaluated and, on this sense, the CPU Considering the CPU time spent on client application, the
time measurements followed the same trend of Fig. 9 with a results on Table II show that Smart Meter CPU time allocated
lower magnitude as can be seen on Table II. for encrypting data was approximately 70% of the overall CPU
It is possible to compare the relative time consumption data whilst remaining 30% CPU time on client application
by CPU (Real-Time and CPU Time) versus the number of was spent on internal processing and data communication, as
frames for the previously described scenarios and this result presented by Table III. This result confirm the computational
is depicted by Fig. 10. onus caused by security module, which is an indicator that it
On this figure it is easy to notice that, from the complete may heavily affect the performance of the hardware. Thus, it is
transmission time perspective, there is no significant distinc- positive to highlight the modular aspect of the proposed frame-
tion between SSL ON or OFF (each one takes approximately work architecture, where the security layer can be exchanged
50% of the x-axis). or extended, without a relevant impact on the communication
It can be also observed that CPU time for processing the process, minimizing further development efforts.
data transfer was very small, which corresponds to a non- When compared to the related works from Table I which
demanding effort. However, due to multiprocessing features also has a performance analysis based on transfer rates it
of hardware, the real-time for transfer oscillates between 16 is possible to note numerical results of [18] has showed a
and 25 times the time spent for the CPU itself, which can consistent throughput of 500 kbps whilst [6] presented a 4.5
be noticed by comparing the values on Table II. Thus, this is Mbps.
an indicator that the hardware configuration can support much TABLE III
DATA P ROCESSING T IMES (CPU)
more processing over collected data, although this architecture OCT x DET on CPU (ms)
cannot be recommended if real-time response is an imperious Fail Rate 0% 15%
requirement. Frames OCT DET OCT DET
However, it is important to highlight that this small impact 625 835.246 640.70 891.91 639.55
1250 1708.92 1226.92 1758.27 1196.74
on overall transfer time caused by the security module, is 2500 3576.89 2328.75 3588.11 2381.19
due to the minimum footprint generated by the security 5000 6823.53 4761.17 7018.76 4603.90
proxy classes. Thus, the communication module is minimally 10000 13440.5 9314.76 14330.60 9510.14
20000 27226.6 19019.20 28044.50 18411.60
affected by the utilization of the security module. However, 40000 53364 36808.90 57354.30 38025.30
it is necessary to evaluate the impact on data processing 80000 N/A N/A N/A N/A
tasks caused by the security module. These measurements 160000 N/A N/A N/A N/A

0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS
It is important to highlight that the first one has used
small frames and the second performed experiments using
heavy traffic generator. However, the proposed framework
have shown a transfer rate of 200 KB/s it is expected a
reduction on this performance when all wireless interferences
come to play. Also, the congestion control situation was
not evaluated and remains as an open issue to be furthered
evaluated against proposed architecture.
And the software model presented on previous sections may
allow any researcher or developer to implement and execute
basically the same operations, which stands as an advantage
over the other models, where the communication layer should
be modeled and implemented from the scratch prior to any
algorithm development.
VII. C ONCLUSION
This paper evaluates the feasibility and performance of
implementing a security layer extension for a multi-frame
Client/Server framework, which can provide data exchange
for residential smart meters. The obtained results demonstrate
that the system performance suffers around 6% of reduction
on transfer rate when the security algorithm is running on
application data. In addition, the encryption algorithm takes
around 70% of CPU time only for encrypting data after the
multi-frame has been built. The higher impact was noticed over
memory constraints, since the transfer capability was reduced
by a factor of 4 from the maximum file size, which can be
transferred in a single transaction.
The wireless choice was defined since wireless technologies
like WLAN and ZigBee have low cost rapid deployment.
However, since a common drawback is the interference with
other devices and due to distance between endpoints, a wired
communication technology, such as Power Line Communica-
tions (PLC) should be considered. In this sense, a DUAL-PHY
Smart Meter (using a wireless and a wired interface) might
be a better approach to mitigate the challenges imposed by
distance and/or signal interferences.
Following this idea, an extension of the architecture can
be analyzed by evaluating the DUAL-PHY model and in-
corporating support for the Function Block paradigm, widely
used on automation systems, as well as model adapters for
international smart grid standards such as IEC 61850 or even
a local standard.
Since there is an intrinsic concern among smart metering
communication in smart grid, another relevant scenario which
can be explored includes the connection between several me-
ters in communication with a server, to evaluate latencies and
throughput values for the framework dealing with a number of
simultaneous connections, where the Beagle Bone Black will
behave as a server or concentrator node.
Finally, it should be pointed out that the use of a structured
framework model enabled the stratification of the tasks carried
out by the smart meter, manufacturers, and developers.
R EFERENCES
[1] R. Ma, H. H. Chen, Y. R. Huang, and W. Meng, “Smart grid commu-
nication: Its challenges and opportunities,” IEEE Transactions on Smart
Grid, vol. 4, no. 1, pp. 36–46, 2013.
0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
8
[2] Y. Yan, Y. Qian, H. Sharif, and D. Tipper, “A survey on smart grid com-
munication infrastructures: Motivations, requirements and challenges,”
IEEE Communications Surveys and Tutorials, vol. 15, no. 1, pp. 5–20,
2013.
[3] E. Ancillotti, R. Bruno, and M. Conti, “Reliable Data Delivery With
the IETF Routing Protocol for Low-Power and Lossy Networks,” IEEE
Transactions on Industrial Informatics, vol. 10, no. 3, pp. 1864–1877,
2014.
[4] Z. Fan, P. Kulkarni, S. Gormus, C. Efthymiou, G. Kalogridis,
M. Sooriyabandara, Z. Zhu, S. Lambotharan, and W. H. Chin, “Smart
grid communications: Overview of research challenges, solutions, and
standardization activities,” IEEE Communications Surveys and Tutorials,
vol. 15, no. 1, pp. 21–38, 2013.
[5] H. Y. Tung, K. F. Tsang, K. T. Chui, H. C. Tung, H. R. Chi, G. P.
Hancke, and K. F. Man, “The generic design of a high-traffic advanced
metering infrastructure using zigbee,” IEEE Transactions on Industrial
Informatics, vol. 10, no. 1, pp. 836–844, 2014.
[6] P. Yi, A. Iwayemi, and C. Zhou, “Developing zigbee deployment
guideline under wifi interference for smart grid applications,” IEEE
Transactions on Smart Grid, vol. 2, no. 1, pp. 110–120, March 2011.
[7] N. Gatsis and G. B. Giannakis, “Residential load control: Distributed
scheduling and convergence with lost ami messages,” IEEE Transactions
on Smart Grid, vol. 3, no. 2, pp. 770–786, 2012.
[8] H. Li and W. Zhang, “QoS Routing in Smart Grid,” Electrical Engi-
neering, vol. 58105, pp. 1–6, 2010.
[9] E. E. Directive, “Directive 2012/27/eu of the european parliament and of
the council of 25 october 2012 on energy efficiency, amending directives
2009/125/ec and 2010/30/eu and repealing directives 2004/8/ec and
2006/32,” Official Journal, L, vol. 315, pp. 1–56, 2012.
[10] G. J. FitzPatrick and D. A. Wollman, “Nist interoperability framework
and action plans,” in Power and Energy Society General Meeting, 2010
IEEE. IEEE, 2010, pp. 1–4.
[11] T. Noergaard, Embedded systems architecture: a comprehensive guide
for engineers and programmers. Newnes, 2012.
[12] J. Catsoulis, Designing Embedded Hardware: Create New Computers
and Devices. ” O’Reilly Media, Inc.”, 2005.
[13] J. Ganssle, The art of designing embedded systems. Newnes, 2008.
[14] M. López-Vallejo and J. C. López, “On the hardware-software parti-
tioning problem: System modeling and partitioning techniques,” ACM
Transactions on Design Automation of Electronic Systems (TODAES),
vol. 8, no. 3, pp. 269–297, 2003.
[15] K. De Craemer and G. Deconinck, “Analysis of state-of-the-art smart
metering communication standards,” in Proceedings of the 5th young
researchers symposium, 2010.
[16] Y. Yan, R. Hu, S. Das, H. Sharif, and Y. Qian, “An efficient security
protocol for advanced metering infrastructure in smart grid,” IEEE
Network, vol. 27, no. 4, pp. 64–71, 2013.
[17] A. Anzalchi and A. Sarwat, “A survey on security assessment of
metering infrastructure in smart grid systems,” in SoutheastCon 2015.
IEEE, 2015, pp. 1–4.
[18] T. Khalifa, K. Naik, M. Alsabaan, A. Nayak, and N. Goel, “Transport
protocol for smart grid infrastructure,” in Ubiquitous and Future Net-
works (ICUFN), 2010 Second International Conference on. IEEE, 2010,
pp. 320–325.
[19] M. P. Shopov, “Iot gateway for smart metering in electrical power
systems - software architecture,” in 2017 40th International Conven-
tion on Information and Communication Technology, Electronics and
Microelectronics (MIPRO), May 2017, pp. 974–978.
[20] E. C. Douglas and D. L. Stevens, “Internetworking with tcp/ip,” Prin-
ciples, protocols and architecture, Prentice Hall International Editions,
vol. 1, pp. 183–185, 1991.
[21] I. N. Group, “User datagram protocol,” IETF Network Group, 1980.
[22] G. Manassero, E. L. Pellini, E. C. Senger, and R. M. Nakagomi,
“Iec61850–based systems—functional testing and interoperability is-
sues,” IEEE Transactions on Industrial Informatics, vol. 9, no. 3, pp.
1436–1444, 2013.
[23] C. R. Ozansoy, Modelling and object oriented implementation of IEC
61850: the new international standard on sustration communications
and automation. Lambert Academic Publishing, 2010.
[24] S. Barker, S. Kalra, D. Irwin, and P. Shenoy, “Empirical characterization,
modeling, and analysis of smart meter data,” IEEE Journal on Selected
Areas in Communications, vol. 32, no. 7, pp. 1312–1327, 2014.
[25] V. Bassilious, C. Ozveren, and A. Birch, “Using smart metering
for load aggregation: towards an integrated smart grid/active network
management framework,” in Proceedings of 2011 46th International
Universities’ Power Engineering Conference (UPEC). VDE, 2011,
pp. 1–6.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TIE.2018.2808927, IEEE
Transactions on Industrial Electronics
IEEE TRANSACTIONS ON INDUSTRIAL ELECTRONICS 9

[26] R. L. Rivest, A. Shamir, and L. Adleman, “A method for obtaining digital

signatures and public-key cryptosystems,” Communications of the ACM,
vol. 21, no. 2, pp. 120–126, 1978.
[27] D. C. Schmidt, “Using design patterns to develop reusable object-
oriented communication software,” Communications of the ACM,
vol. 38, no. 10, pp. 65–74, 1995.
[28] E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design patterns:
elements of reusable object-oriented software. Addison-Wesley, 1994.
[29] M. Hitz and B. Montazeri, “Measuring coupling and cohesion in object-
oriented systems,” 1995.
[30] G. Gui and P. D. Scott, “Coupling and cohesion measures for evaluation
of component reusability,” in Proceedings of the 2006 international
workshop on Mining software repositories. ACM, 2006, pp. 18–21.
[31] F. A. S. Borges, R. A. S. Fernandes, I. N. Silva, and C. B. S. Silva,
“Feature extraction and power quality disturbances classification using
smart meters signals,” IEEE Transactions on Industrial Informatics,
vol. 12, no. 2, pp. 824–833, April 2016.

Rodrigo de T. Caropreso was born in São Paulo,

Brazil, in 1976. He graduated in Electrical Engi-
neering from Polytechnic School of University of
São Paulo, in 1998. He received the M.Sc. degree in
Electrical Engineering from the University of São
Paulo, Brazil, in 2003. Currently, he is a Ph.D.
student at University of São Paulo, Brazil. His
research interests are within the field of smart grids,
embedded systems and intelligent systems.

Ricardo A. S. Fernandes (M’10) was born in

Barretos, Brazil, in 1984. He graduated in electrical
engineering from the Educational Foundation of
Barretos, in 2006. He received the M.Sc. and Ph.D.
degrees in electrical engineering from the University
of São Paulo, Brazil, in 2009 and 2011, respectively.
Currently, he is an Assistant Professor at the Federal
University of São Carlos. His research interests are
within the field of smart grids, power quality and
intelligent systems.

Diana P. M. Osorio (M’16) was born in Quito,

Ecuador. She received the B.Sc. degree in Elec-
trical and Telecommunications Engineering from
University-ESPE, Ecuador, in 2008, and the M.Sc.
and D.Sc. degrees in Electrical Engineering from the
University of Campinas, Brazil, in 2011 and 2015,
respectively. Currently, she is an Assistant Professor
at the Federal University of São Carlos, São Carlos,
SP, Brazil. Her research interests include wireless
communications and technologies for 5G networks.

Ivan N. Silva (M’98) was born in São José do

Rio Preto, Brazil, in 1967. He received both M.Sc.
and Ph.D. degree in electrical engineering from
the University of Campinas (UNICAMP), Brazil,
in 1995 and 1997, respectively. Currently he is an
Associate Professor at the University of São Paulo.
His research interests are within the fields of power
system automation, intelligent systems and optimiza-
tion. He is also Editor-in-chief of the Journal of
Control & Automation (Brazil).

0278-0046 (c) 2018 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.