# Performance and Challenges of Service-Oriented Architecture for Wireless Sensor Networks
## 9 Analysis
### Service-Oriented Architectures for WSNs  
The SOA comprises of diverse notions, concepts, and technologies from a wide range of studies. Tables 5-7 show the comparative analysis of service-oriented architectures for WSNs. In this paper, state-of-the-art approaches based on SOA design for WSN are presented. Even though most well-known examples of SOA are web services, it is important to know that it is not limited to it. The biggest issue of applied traditional SOA into WSNs is that those are built on different platforms/operating systems (OS) without the use of middleware. The approach is considered to support general core functionalities independent of the platform and OS. None of these approaches supported the multi-service composition except for the FSONA approach. Table 5 shows the approaches that applied traditional SOA into WSNs that do not support middleware architectures. Some of these approaches provide general architecture with some limitations as shown in Table 6. In Table 7, the requirements and benefits of traditional SOA for WSNs. \begin{table}
\begin{tabular}{c c c c} \hline \hline
**SOA Architectures** & \multicolumn{2}{c}{**The Requirements**} & \multicolumn{2}{c}{**The Purpose of Middleware Architecture**} \\ \hline TinySOA [53] & 1. & The heterogeneity of underlying environments is hidden by applying abstraction such as protocols and languages & 1. & Discovery data readings \\
2. & The consumer service supported to detect and use & 2. & Actuators management, and \\  & 3. & Can integrates with other system & \\ \hline SensorsMW [49] & 1. & The heterogeneity of underlying environments is hidden by applying abstraction such as protocols and languages & \\  & 2. & Configurable services & 1. & Supports dynamic management of \\  & 3. & Can integrates with other system & \\  & 4. & Dealing with a large amount of data and increase & 2. & Provides QoS configuration by \\  & & communication load efficiently & & service level \\  & 5. & Interoperability with different device or system & \\  & 6. & Support requirement for QoS & & \\ \hline Mob-WS [48] & 1. & Used as back end resources to reduce the complex & Provides the best management and \\  & 2. & Asynchronous services & representation of wireless networks \\ \hline SOMM & 1. & Support Multimedia & \\  & 2. & Support QoS, Virtual machine (VM), Mobile Agents, and & \\  & 1. & Tuple space & \\  & 3. & provides highly scalable platform by using SOA & 1. & Provides Security \\  & 4. & Energy efficiency is increased for the & 2. & Hardware resource management \\  & 5. & The Mobile Agents and Code Repositories are used to & 3. & Supports QoS \\  & 6. & Enable the Node to be reprogrammed & & \\ \hline SAWM & 1. & The architecture is easy to update & \\  & 2. & used less memory for processing the programming codes & \\  & 3. & processed in real-time & 1. & Provides secure architecture \\  & 4. & Provide low cost during the transmission & & \\  & 5. & decrease power consumption & \\ \hline ESOA [54] & 1. & Support requirement for QoS & Coordination, Monitoring, Conformance, QoS \\  & 2. & Interoperability with different device or system & & and Service Discovery \\ \hline \hline \end{tabular}
\end{table} 
Table 4: _Cont._  
\begin{table}
\begin{tabular}{c c c c} \hline \hline
**SOA Approaches** & **Operating System/Platform Independence** & **Type of Software Applications** & **Multi-Service Composition** \\ \hline SODA for Smart Environment [71] & \multirow{2}{*}{ \begin{tabular}{c} Multi-Sensor Platform \\ (resource constrained sensor platform) \\ \end{tabular}  } & Built upon the gSOAR toolkit & Not Supported \\  & & & with TCP/IF stack-hvf & Not Supported \\ \hline SOA Model for & \multirow{2}{*}{ \begin{tabular}{c} NoA Model for \\ Sensor Networks [72] \\ \end{tabular}  } & \multirow{2}{*}{\ \begin{tabular}{c} Not Supported \\ and Multi-gateway \\ \end{tabular}  } & \multirow{2}{*}{ \begin{tabular}{c} Built on different applications \\ such as Agent Register, Resource Manager, \\ and Multi-gateway \\ \end{tabular}