## 3 Self-Configuration Management (SCM)
### Data and Radio Model
The network status includes the connection status and each node's location and battery level. To check the network status, the CH needs to receive this information from the deployed nodes to confirm its test. Then, it establishes a status table of the attached clustering devices. Through the status table, CH in each cluster settles on defective nodes that issued the system fault in its cluster, and also the distance dimensions of that node for its location. Next, CHs in each cluster cooperate with the IoT service to cover the faulty nodes by dispatching the picked package to them across the network layer. The network layer encapsulates the software packet in datagrams and handles a message at the sending and receiving nodes. This includes the time to prepare the message (adding header, trailer, and error correction information), the time to execute the routing algorithm, and the time to establish an interface between the routing node and the receiving node. The delay incurred only once for a single packet transfer. This is known as startup time (\(t_{s}\)) and is the time that requires the _head_ to initiate configuration-communicate capability and accept to route that packet to the transport layer for delivering the packet to the decided node. Through that level, The CH could designate which device will receive the software packet, by deciding on it from the _status table_. The table comprehends:

1. Sensor ID and its distance;
2. Sensor Mac address;
3. Sensor energy level;
4. Activity mode (idle, active, sleep). The steps of installation for the problematic node may also be selected, as well as what would happen once the software installation is complete. Additionally, it has the ability to postpone the program installation and transfer in the event that significant obstacles arise at the same moment. Low battery life, limited computational power, and ineffective communication resource use are a few of these difficulties. Figure 1 depicts the key steps of the distributed configuration. The setup dialog that was carried out under the direction of the admin node, represented as CH at that phase, is highlighted in this figure. The CH chooses which device will receive the software replica first after determining the status table of the malfunctioning sensors that were sent to the BS (base station). The BS accepts the chosen course of action and grants permission for the networking system's setup and transfer processes. Following the approval log, CH creates a record containing a replica and installation details for each SF in its cluster after planning installation procedures and assigning sensor distances. The Byzantine sensor SFI receives the installation data via intranet networking, together with executable files, and the installation process works as follows. Byzantine sensor level:

The sensor (S\({}_{\text{FI}}\)) receives a configure notification message from CH. S\({}_{\text{FI}}\) accepts the notification issued by the configuration message and starts to prepare to establish a communication interface among them, which is needed to execute its reconfiguration progress. It is sent software packet as a request packet across a virtual circuit network from the source (CH) to the destination (S\({}_{\text{FI}}\)). The time taken for configuration/programming the node interface and transferring the routing information is independent of the packet length. The sequence of the self-configuration of S\({}_{\text{FI}}\) was implemented as:

1. Sensor S\({}_{\text{FI}}\) receives a configure notification from CH. 2. S\({}_{\text{FI}}\) knows that there is a software packet going from CH that comes out through the communication port established among them. 3. S\({}_{\text{FI}}\) opens the communication channels/sessions within the receiver module (R) for passing the packet, ensuring they remain open and functional while data is being transferred, and closing them when communication ends. 4. The receiver module (R) listens to the request packet through its amplifier. 5.