## 3 SDWSNs and IEEE 802.15.4e TSCH
### Software-Defined Wireless Sensor Networks (SDWSNs)  
SDWSNs result from the application of the SDN paradigm to the WSNs. These networks enable resource sharing and reuse and improve network management and configuration. They decouple the control plane from the data one, and all the management and control decisions are made using a centralized controller, in which the sensor nodes become forwarding devices [5]. The SDWSN architecture is divided into three planes: (i) the infrastructure plane, which includes the sensor nodes (that sense the environment and send data messages to the sink (s)) and communicates with the control plane using the southbound (SB) protocol; (ii) the control plane, which achieves all control and management tasks through a centralized controller; and (iii) the application plane, which communicates with the control plane using the northbound (NB) protocol.  
We adopt IT-SDN as the SDWSN framework. The IT-SDN uses three separated protocols: (i) the SB protocol, which ensures communication between the SDN nodes and the controller; (ii) the neighborhood discovery (ND) protocol, which obtains information about SDN node neighbors; and (iii) the controller discovery (CD) protocol, which specifies the next hop on the path between the current node and the controller. The SB protocol comprises the following packet types: flow request, flow setup, flowid register, neighbor report, acknowledgment, and data. The flow request packet requests the controller information about packets without entries in the flow table, and the controller replies using a flow setup packet with the associated configuration. The neighbor report packet carries the node neighborhood information, and the acknowledgment packet confirms the delivery of the control packets. All the routes are calculated with the controller according to the given  
\begin{table}
\begin{tabular}{c c c c c} \hline \hline \multirow{2}{*}{**Work**} & \multirow{2}{*}{**Addressed Issue**} & Traffic Isolation & Timeslots & Scalability \\  & & Type & Type & Support \\ \hline [PERSON] et al. (2015) [15] & Interference and multipath fading & None & — & No \\ \hline [PERSON] et al. (2017) [14] & Control and data traffic competition & Control and data & Dedicated & No \\ \hline [PERSON] et al. (2018) [17] & Mobility management & None & Dedicated & No \\ \hline [PERSON] et al. (2021) [18] & Ensure the QoS level & Control and data/ applications’ traffics & Dedicated & No \\ \hline [PERSON] et al. (2021) [9] & Control and data traffic competition & Control and data & Shared & Yes \\ \hline [PERSON] et al. (2022) [26] & Comparison among TSCH schedulers & — & — & — \\ \hline [PERSON] et al. (2022) [19] & Control the application requirements & Control and data/ application’s traffics & Dedicated & No \\ \hline [PERSON] et al. (2022) [20] & Scalability in the IWSNs & None & Dedicated & Yes \\ \hline [PERSON] et al. (2022) [16] & Application traffic competition & Control and data/ application’s traffics & Shared & Yes \\ \hline \hline \end{tabular}
\end{table}
Table 1: Summary of the related work.  
rules. IT-SDN was thoroughly evaluated [7] by varying several parameters, and the results confirmed its efficiency in comparison with the routing protocol for low-power and lossy networks (RPL) [8].