
“No complex adaptive system will succeded in adapting in a reasonable amount of time unless the adaptation can proceed subsystem by subsystem, each subsystem relatively independent of the others.” — Christopher Alexander, Notes on the Synthesis of Form
Service Oriented Device Architecture (SODA)
The purpose of SODA is to enable developers to incorporate sensors and actuators into service oriented architecture (SOA). We are, in essence, connecting the Internet, or digital realm, to the physical realm, and vice versa.
The objective is to enable a programmer to incorporate a sensor or actuator into his business logic without prior knowledge or intervention of the programmer of the sensor or actuator. This objective is directly akin to the objective of SOA in electronic commerce.
We are doomed to failure by a direct assault on the problem. If we attempt to make a custom webservice for every device that can be attached to the Internet, then we have only increased the complexity of our challenge and solved nothing. More than an architecture, we need a philosophical approach to connecting the Internet or digital realm to the physical realm. Of course, one cannot achieve great architecture without philosophy.
SODA is an approach to designing and building software for the distributed mobile wireless embedded Internet. At the simplest level, SODA enables programmers to deal with sensors and actuators as services. SODA is focused on the boundary layer that exists between the physical realm and the digital realm. To understand SODA, we must first establish a shared model for thinking about our world. We call this model the Transducer Reference Model.
A sensor is an electromechanical device that translates the energy of a physical phenomenon into a signal. Examples of sensors are digital thermometers and video cameras. An actuator is an electromechanical device that translates a signal into a physical phenomenon. Sensors and actuators are both instances of transducers. A transducer translates between a signal in the digital realm and energy in the physical realm. Sensors and transducers combine into systems. For example, radar is a system that combines transmitters and receivers.

When discussing sensor fusion, it is convenient to use the terms physical realm and digital realm. The phenomena occur in the physical realm. The sensor reacts to the phenomena to produce an electronic signal, either analog or digital. The signal is interpreted into data and it exists in the digital realm. Thus, we would say that the sensor translates a phenomenon in the physical realm into a corresponding data in the digital realm.
There would be no need to think in terms of the digital realm without the Internet. Before the Internet, a signal would exist inside a single isolated machine or a well-defined isolated system. With the advent of the Internet, a single processor can access the signals from any number of sensors. Thus, the challenge of sensor fusion is predicated upon the existence of an Internet, a universal network of networks.
Before the Internet, the association between two or more sensors would only occur within a single well-defined system. The engineers would be able to determine and define the interdependencies of the sensor signals in the design of the system. With the Internet, we can now access the signals of several sensors on an ad hoc basis. This capability is useless, however, without some means to determine the interdependencies of the sensors.
The transducer reference model is key to understanding sensor fusion. Look at it carefully. The model shows that:
- A phenomenon produces energy
- The sensor creates a signal that corresponds with the energy
- The signal is captured as data in the digital realm
Many times we catch ourselves thinking about the data as the energy or the phenomenon itself. Such thinking only leads to confusion and overly complicated systems that do not work.
Munen muso is a Japanese phrase that translates roughly to no design, no concept. When thinking of sensor fusion, it is important to keep this phrase in mind. Sensor data is just data, nothing more. A sensor does not know what it is observing, and sensor data has no concept of what it represents. Sensor data is in the digital realm. What sensor data represents is in the physical realm. It requires some type of processing to equate one to the other, even in the simplest cases. GPS data is a good example for applying this concept. GPS data is not position, it is just data. Position is a concept that exists in the physical realm. GPS data exists in the digital realm. We know GPS data is position data because we as humans have processed the data and placed it into context. However, with sensor fusion, we want the computers to process the information for us. When we start imposing our processing of data onto the data itself, then we hamper the computer’s processing of the data.
Sensor data is just data. Treat it as such. Remember that when discussing sensor fusion, you are discussing the digital realm, not the physical realm. The confusion arises because we are discussing things in the digital realm that have a correlation with things in the physical realm. It is only a correlation; they are not the same thing, and the correlation can only be achieved through some level of processing, human or otherwise.
References
- “Service Oriented Device Architecture“, IEEE Pervasive Computing September 2006. Full article
- EclipseCon 2007, “Service Oriented Device Architecture”, 6 March 2007, Santa Clara, CA. Slides (PDF, 9MB)
- Melanie Martella, Smells Like Convergence, Sensors Magazine May 17, 2007
Leave a Reply
You must be logged in to post a comment.