# Performance and Challenges of Service-Oriented Architecture for Wireless Sensor Networks
## 9 Analysis
### Service-Oriented Architectures for WSNs
 } & Not Supported \\ \cline{1-1} \cline{3-4} \cline{6-4} \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**SOA Approaches** & \multicolumn{2}{c}{**The Features and Advantages**} & \multicolumn{2}{c}{**Disadvantages**} \\ \hline  & 1. & Support the Security, and & 1. & Performance overhead communication \\  & & heterogeneities at low level & & while processing of SOAP messages but \\ SODA for smart environment [71] & 2. & Not required additional middleware & not as much as messages transmission \\  & 3. & transmission time is reduced and & 2. & Performance measurement effect \\  & & battery life is increased by using Sensor & 3. & on latency \\  & & data aggregation & 3. & SOAP-based web services are required \\  & & & parse verbose XML documents \\ \hline SOA Model for Sensor Networks [72] & 1. & Provide an efficient architecture & & \\  & 2. & Secure communication protocol & & Does not test in real time \\  & 3. & Efficiently collecting data from WSNs & & \\ \hline WSNs Cloud User Interaction [73; 74; 75] & 1. & WSN-SOrA and SOA have solutions & & \\  & & and the ability to support infrastructure & & Overhead \\  & & reuse [73] & & \\  & 2. & Enable data sharing in efficiently [74; 75] & & \\ \hline FSONA [79] & \multicolumn{2}{c}{Process heterogeneous wireless mobile} & \multicolumn{2}{c}{Overhead} \\ \hline  & & provides a flexible distribution of resources & & \\  & & SPLPH and capable during performance time & & \\  & & to add new component [64] & & \\  & & Decreases memory space, interoperability of & & \\  & & service, maintenance cost, fast response, time, & & \\  & & high privacy, and throughput. This technique & & \\  & & was improved the QoS to make decision and & & \\  & & time warning generation the authentication & & XML and SOAP in the system [65] \\  & & mechanism and lightweight and efficient & & Not support Security [66] \\  & & biosensor [65] & & \\  & & Collecting and managing then & & \\  & & analyzing data [66] & & \\  & & Cost reduces [66] & & \\  & & it modify the requirement of monitoring [66] & & \\ \hline  & & **WASP** & & \\  & & It process the raw data from WSNs [68; 70] & & \\  & & **SeNoMa-cloud**[70; 71] & & \\  & & & communicate with each other by using & \\  & & MQTT broker and ActiveMQ Apollo & & \\  & & & Small packet handles by using & \\  & & MQTT protocol & & \\  & & 3. & Deals with raw data [64; 65] & & \\  & & **SensorML** & & \\  & & & & \\  & & & & \\  & & & & \\  & & & & \\  & & & & \\  & & & & \\  & & & & \\ \hline \hline \end{tabular}
\end{table} 
Table 6: Advantages and Disadvantages of SOA for WSNs. \begin{table}
\begin{tabular}{c c c c} \hline \hline
**SOA Approaches** & \multicolumn{2}{c}{**Operating System/Platform Independence**} & **Type of Software Applications** & **Multi-Service Composition** \\ \hline Healthcare & 1. & SYLPH [64] & Built on ambient intelligence (AI) [64] & \\ Approaches & 2. & Wireless Body Sensor Networks (WBSNs) [65] & Java (IDK 1.6, Apache format & Supported \\  & 3. & SunShine [66] & systemer 6.0) [65] & \\ \hline  & & **WASP** has two sides & \\  & & 1. & ZigBene enables nodes communicate hop by & \\ OGC-SWE standards & & hop with each other & \\ (Web Service) & 2. & Software service using HTTPS protocol [68; 69] & Built smart home system & None \\  & & **SeNoMa-Cloud**[70; 71] & & \\  & & A MQTT broker, ActiveMQ Apollo & & \\  & 3. & **SensorML**[72] & & \\ \hline Configuration & & & \\ Service [76] & & Middleware Framework & Evaluation in CORE and EMANE & Not Available \\ \hline \hline \end{tabular}
\end{table} 
Table 5: _Cont._Security challenges and performance of data aggregation are not supported in most of approaches while only SODA and SYLPH approaches support security at a low level. In conclusion of this analysis, it is fair to comment that none of the reviewed approaches accomplishes all the requirements globally. The scalability, security, QoS, data aggregation, integration, and overhead limitations should be taken into account during the implementation processes of future designs.