## 3 Proposed Fires Monitoring and Detection Framework
### The Proposed Sensor Deployment Scheme
This is because in the forest environment, it is highly possible that we cannot deploy all sensor nodes with a regular pattern. Some nodes have to be placed at distant locations from other sensor nodes due to geographic constraints. For example, there is a lake inside the forest. Therefore, in this case, a forest environmentally oriented communication protocol should be proposed. Before we discuss our proposed forest environmentally oriented communication protocol, we will describe our proposed clustered hierarchy network architecture. ### The Proposed Clustered Hierarchy Network Architecture

In this subsection, we describe the network architecture and topology adopted in the proposed framework with goals of efficient and effective forest fire monitoring and detection and the limitations of WSNs. In the proposed framework, a hierarchical clustered topology is used. Therefore, some nodes are designated as cluster heads, while others are designated as common nodes. The reason for choosing hierarchical clustered network architecture and topology is that from several simulations, it is observed that the hierarchical clustered network architecture and topology brings benefits in terms of achieving effective control of nodes depending on changing conditions, fast DT to the fire threat and energy and bandwidth efficiency. These are especially useful for fast forest fire monitoring and detection. Moreover, we also propose an enhanced version of the LEACH protocol called E-LEACH in the proposed hierarchical clustered network architecture. In the proposed E-LEACH, each node maintains its own features table. Table 1 shows the contents of each node. This table includes six parts: node ID, Alive, Sleep, Head, Active and Cluster. Node ID represents the unique number of the node; the node is randomly assigned in the network initialization. Alive indicates whether the node is a viable node, with a value of 0 (death) or 1 (survival). Sleep indicates whether the node is in the sleep mode, with a value of 0 (sleep) or 1 (active). Head indicates whether the node is a cluster head, with a value of 0 (no) or 1 (yes); the default value of the property is 0. The active represents whether the node participates the cluster head selection procedure. Three cases may cause active value to become 0: (1) the node is not elected as cluster head in current round; (2) the node did not receive the cluster head broadcast message; (3) the node received at least two cluster head broadcast messages and becomes a free node. Otherwise, if the value of active is 1, it means the node is elected as cluster head, or only received one cluster head broadcast message within the reference range. The default value of the property is 0. Cluster indicates that whether the node is in a cluster, with a value of 0 (not in the cluster) or 1 (already in the cluster), the default value of the property is 0. To avoid the situation of the node being unevenly distributed in random deployment, the proposed E-LEACH protocol selects the cluster head by comprehensively considering the residual energy of cluster head and the relative position among cluster heads. For the WSNs with the number of node \(N\), we assume that the percentage of cluster head is \(P\). After the initialization of the network, BS uses Formula (2) to assign reference distance \(\text{R}_{re}\) for each node by broadcasting. Those nodes whose active value is 0 will generate a random number between 0 and 1. If the generated number is less than the threshold in Formula (2) will be selected as cluster head. The first node that is selected as the \begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Node ID** & **Alive** & **Sleep** & **Head** & **Active** & **Cluster** \\ \hline int & byte & byte & byte & byte & int \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Contents of each node. cluster head becomes the first cluster head, and this node broadcasts a message to the surrounding nodes and set its head value to 1.