## 2 Background
Inadequate firmware and software updates expose devices to known vulnerabilities, while  
Figure 3: Estimated number of connected devices vs. world population [37]. insecure communication channels and weak credentials increase the risk of unauthorized access and data breaches. The issue of physical access, along with concerns about user privacy and vendor security practices, further compounds the security landscape as mentioned in [39]. To navigate these challenges, a comprehensive approach is necessary, involving robust authentication, encryption, user education, regular updates, and industry-wide collaboration to establish a more secure PIoT ecosystem, as detailed in Table 3. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Communication Requirement** & **Description** & **Parameters** \\ \hline Real-time Data Exchange & Facilitate real-time exchange of data between smart meters, sensors, and control centers. & 1-s data updates \\ \hline Scalability and Flexibility & Support a growing number of devices and adapt to changing technology standards and communication needs. & Support for 1 million devices \\ \hline Reliability and Redundancy & Ensure communication networks have built-in redundancy and fault tolerance to prevent data loss. & 99.99\% network uptime \\ \hline Low Latency & Minimize delays in data transmission to enable timely response to grid events and demands. & Latency under 50 ms \\ \hline Security and Privacy & Implement strong encryption, authentication, and access control to protect sensitive grid data. & AES-256 encryption \\ \hline Interoperability & Enable different devices and systems from multiple vendors to communicate seamlessly. & IEEE 2030.5 protocol \\ \hline Quality of Service (QoS) & Prioritize critical data traffic to ensure essential grid commands and responses are not delayed. & QoS for control commands \\ \hline Wide Coverage & Provide coverage across a wide geographical area, including urban and remote regions. & Coverage across entire city \\ \hline Bidirectional Communication & Support two-way communication to enable demand-response, remote control, and data feedback. & Monthly peak-load adjustment \\ \hline Multi-Protocol Support & Accommodate various communication protocols (e.g., cellular, Wi-Fi, power-line, Zigbee) for flexibility. & Supports Zigbee and LoRaWAN \\ \hline Data Aggregation & Aggregate data from various sources for comprehensive grid monitoring, analysis, and decision-making. & Hourly energy consumption data \\ \hline Network Management & Allow remote monitoring, diagnostics, and management of communication networks and devices. & Remote firmware updates \\ \hline Over-the-Air Updates & Enable remote firmware and software updates to keep devices secure and up to date. & Quarterly firmware updates \\ \hline Low Power Consumption & Optimize communication protocols for devices with limited power sources, such as sensors and meters. & Sensors with 5-year battery life \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Recommended PIoT communication requirements for smart grid systems [17]. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Message Type** & **Description** & **Parameters** \\ \hline Command Messages & Instructions sent from the control center to the substation to initiate actions or switch operations. & Open Breaker 1, Close Tap Changer 2 \\ \hline Status and Acknowledgment Messages & Messages confirming the successful receipt and execution of commands. & Command Received, Operation Successful \\ \hline Measurement Reports & Data from sensors and meters in the substation, providing real-time information on grid conditions. & Voltage: 123 kV, Current: 50 A \\ \hline Alarm and Alert Messages & Notifications of abnormal conditions, such as equipment failures or abnormal voltage levels. & Overcurrent Detected, Transformer Fault \\ \hline Event and Log Messages & Records of significant events, faults, or changes in the substation, useful for diagnostics. & Circuit Breaker Trip, Voltage Variation \\ \hline \hline \end{tabular}
\end{table}