## 3 Self-Configuration Management (SCM)
### Data and Radio Model
Table 4 lists a sample of the alarm system's reactions during the implementation of deployment round No. 22. The data clarify that the system transferred alert responses to the cluster head, to avoid receiving such misleading readings/system faults from the sensor elements in the cluster. The alert system acts as a check circuit that checks all outgoing readings from the network elements throughout the duty cycle in every round. It organizes the traffic of the readings to each CH in the designated network. Additionally, the alarm catches the temperature-encapsulated data packets corresponding to a predefined default time (t = 300 \(\mu\)) coming from all network elements in that round. Then, it sorts normal nodes and abnormal nodes according to the difference formula:

\[S_{i}-S_{j}=\{N\,|\,N\in S_{i}\text{ and }S_{j}\
otin s\} \tag{16}\]

where \(S_{i}\) and \(S_{j}\) must be compatible and have the same cluster-parity. Behind that, the alert system operates as a clock measuring the elapsed access time compared to t. If the elapsed inward time exceeds t and has happened at elapsed times 317, 316, 316, 314; it considers the system fault and coded it as rank 2. Whereas, if the inward time repeats in the sending \begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Alarm** & **Incoming** & **Inward Passed** & **Mac Address** & **Status** & **CH**_Alert_ & **Hearbeat Rank** \\ \hline Alarm ON & 29 & 257 & 192.168.16.1 & Normal & & \\ Alarm ON & 29 & 253 & 192.168.3.2 & Normal & & \\ Alarm ON & 41 & 255 & 192.168.5.3 & Ab Normal & 0 & 11100000-5 \\ Alarm ON & 38 & 255 & 192.168.3.2 & Normal & 000-000 & \\ Alarm ON & 29 & 253 & 192.168.3.5 & Normal & & \\ Alarm ON & 42 & 252 & 192.168.10.1 & Ab Normal & 0 & 1000000-10 \\ Alarm ON & 30 & 317 & 192.168.12.2 & Ab Normal & 000 & 1100000-12 \\ Alarm ON & 30 & 316 & 192.168.11.3 & Ab Normal & 000 & 1110000-11 \\ Alarm ON & 29 & 316 & 192.168.9.4 & Ab Normal & 000 & 1110000-9 \\ Alarm ON & 29 & 214 & 192.168.2.2 & Normal & & \\ Alarm ON & 42 & 314 & 192.168.20.1 & Ab Normal & 000 & 1000000-20 \\ Alarm ON & 42 & 312 & 192.168.2.2 & Ab Normal & 000-000 & 1100000-2 \\ Alarm ON & 29 & 246 & 192.168.16.3 & Normal & & \\ Alarm ON & 29 & 257 & 192.168.20.4 & Normal & & \\ Alarm ON & 29 & 255 & 192.168.14.5 & Normal & & \\ \hline \hline \end{tabular}
\end{table} 
Table 4: The detection-chain mechanism of the number alarm: alert status; heartbeat status is sent for the cluster head; node status. period or other epochs, it logs the fault in rank 3 and sends an alert with code \"000-000\". The head node receives the \(\mathrm{S_{F}}\) alert status and heartbeat status to prepare the configuration model for these detected sensors and complete the software fault tolerance measurements. In this phase, all alert messages were realized in SCM and tolerated up to 98.86% of the injected system faults. #### 4.2.2 Fault Configuration Method

The CH attempts to supply software replication for system failure states infecting the surprise operation of active nodes in the system during this period. In a configuration-enabled distributed system, nodes are arranged sequentially, with one node serving as the head (or leader node) and the rest serving as secondary (or clustering nodes). It is important to note that any eligible node in the system can become primary by switching from secondary to primary (often when a primary node fails). The goal is for the leading node to use the emitter packet's gain to assist all honest nodes in achieving state-aware coverage. A practical system configuration model was used, as long as the maximum number of failed nodes is less than or equal to one-third of the total number of nodes in the system. The system gains confidence as the number of nodes grows. We divided the configuration model's rounds into five phases. 1. The alarm system sends an alert message M1 enclosed by heartbeat status within each round to the cluster head (primary node); one message exchange (M1). 2.