Civil Engineering Reference
In-Depth Information
Figure 3.4 SOA stack as given by DPWS
new applications or services can be created based on those provided by one or more
devices/services.
SOA protocols are considered to be large, heavy protocols and thus are not well
suited for resource-constrained mobile and pervasive devices. The reason for this is
the use of XML (Wikipedia, 2012). An interesting open source project developing a
smaller SOA DPWS stack intended for devices is SOA4D (Wikipedia, 2010f).
Current research has also shown that DPWS can be implemented on very tiny
devices (Wikipedia, 2010a). The introduction of CoAP has generated a very fast
move by many towards the use of CoAP.
The use of SOA in real-time applications has recently been pushed by efforts to
compress the large SOA XML messages. Here EXI (Bournez, 2009; Peintner and
Pericas-Geertsen, 2009) with the EXIP (Bournez, 2009; Kuskow, 2011) implemen-
tation shows very promising results.
Further, the migration from legacy to SOA and security in SOA architectures are
foreseen as very important topics. Some recent work on the migration has been
described elsewhere (Peintner and Pericas-Geertsen, 2009).
3.6 Proprietary buses and protocols
For a long time a large number of proprietary solutions has been developed for use
in industry. Some examples include:
*
M-Bus or Meter-Bus (Wikipedia, 2010f);
*
LonWorks (Wikipedia, 2010a); and
*
BACnet (Wikipedia, 2010a).
Each of these defines some or all of the layers in the OSI model. These approaches
are essentially incompatible with each other and with any open standards. Because
compatibility is increasingly necessary today, gateway products have been
Search WWH ::
Custom Search