# PINE: Post-Quantum Based Incentive Technique for Non-Cooperating Nodes in Internet of Everything
## 3 Proposed Approach--PINE Protocol
### Protocol Design
#### 3.3.2 Operational Phase
These results show that the protocol takes \(\approx\)180 s or 3 min to transmit 10,000 characters of information when considering almost 100 communication cycles. * In Table 4 and Figure 7, it can be seen that the protocol consumes more memory for 10 forwarding nodes compared to a higher number of forwarding nodes, namely, 20 and 30, due to the higher memory consumption involved in network stabilization; throughout the process, constant communication is required to perceive the status of the neighbour nodes until _InTab_ can be constructed for efficient node selection and nomination in further communication cycles, as outlined in Section 3.3.1. After stabilization, the results show that the memory consumption at each node is directly proportional to message size. Hence, it can be concluded that our proposed PINE protocol provides better results for greater message sizes when considering the trade-off. This result leads to the conclusion that \(\approx\)144.19 MB of memory is consumed by each node for transmission of up to 10,000 characters of message when considering 30 forwarding nodes. * In Table 5 and Figure 8, the results reveal that as the message size increases the average residual energy needed to execute the protocol decreases when considering up to 30 forwarding nodes. It can be observed that the average residual energy is inversely \begin{table}
\begin{tabular}{c c} \hline \hline
**Computer Model** & Dell Inspiron 3576 \\ \hline
**Operating System** & Microsoft Windows 10 Pro \\ \hline
**Processor** & Intel(R) Core(TM) i5-7200U CPU @ 2.50 GHz, 2.712 GHz, 2 Core(s), 4 Logical Processor(s) \\ \hline
**Random Access Memory (RAM)** & 16 Giga-Bytes \\ \hline
**Read Only Memory (ROM)** & 1 Tera-Bytes \\ \hline
**Solid-State Drive (SSD)** & 120 Giga-Bytes \\ \hline
**Python Environment IDE** & Scientific Python Development Environment (SPYDER)—Anaconda Platform \\ \hline
**MAC Layer** & 802.11 \\ \hline
**Number of Nodes (Excluding S and R)** & 10–50 Nodes \\ \hline
**Transmission Range** & 200 Metres \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Simulation environment. proportional to the message size, as \(\approx\)210.91 J of average residual energy is left among all the forwarding nodes when the message size is 10,000 characters. \begin{table}
\begin{tabular}{c c c c} \hline \hline \multirow{2}{*}{**Message Size**} & **Memory Consumption** & **Memory Consumption** & **Memory Consumption** \\  & **for Number of** & **for Number of** & **for Number of** \\  & **Nodes = 10** & **Nodes = 20** & **Nodes = 30** \\ \hline
10 & 136.67 MB & 135.85 MB & 135.98 MB \\ \hline
100 & 136.13 MB & 136.39 MB & 137.08 MB \\ \hline
1000 & 136.52 MB & 138.68 MB & 139.57 MB \\ \hline
10,000 & 137.44 MB & 141.31 MB & 144.19 MB \\ \hline \hline \end{tabular}
\end{table} 
Table 4: Comparison between memory consumption and message size. Figure 6: Execution time vs. message size. \begin{table}
\begin{tabular}{c c c c} \hline \hline \multirow{2}{*}{**Message Size**} & **Execution Time for** & **Execution Time for** & **Execution Time for** \\  & **Number of Nodes = 10** & **Number of Nodes = 20** & **Number of Nodes = 30** \\ \hline
10 & 22.89 s & 46.96 s & 81.42 s \\ \hline
100 & 30.17 s & 84.48 s & 129.15 s \\ \hline
1000 & 60.85 s & 104.21 s & 138.7 s \\ \hline
10,000 & 92.72 s & 146.33 s & 180.97 s \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Comparison between execution time and message size. Figure 7: Memory consumption vs. message size. ### Comparison of Execution Time, Memory Consumption, and Average Residual Energy with Number of Nodes

* In this analysis, the results were evaluated by varying the number of forwarding nodes to find the effect on the execution time (in Seconds) per device memory consumption (in Megabytes) and average residual energy (in Joules). * This proposed protocol evaluated the results by keeping the message size to a constant value of 1000 characters in order to obtain realistic observations by considering a number of sessions or communication cycles up to 300.