On Wed, Sep 16, 2015 at 3:48 PM, Sachith Withana <[email protected]> wrote:
> Hi Ayoob, > > Just to clarify, when you said "each sensor has its own stream > definition", you meant each sensor type ( ex: temperature, GPRS ...etc) or > for each sensor for each device ( mobile phone temp sensor vs fire alarm > sensor?) would have their own stream definitions? > > On Tue, Sep 15, 2015 at 4:50 PM, Ayyoob Hamza <[email protected]> wrote: > >> Hi, >> >> In IoT Server, we have a requirement of identifying the event streams >> that a specific device-type caters (eg: Temperature, Humidity, GPRS). >> Currently we don't have a separate way of identifying this on CDMF. At an >> abstract level a device type can be thought of as having multiple sensors. >> A specific sensor can exist in multiple device types. >> >> As a suggestion we can implement $subject by defining a sensor module >> where each sensor has its own stream definition. Doing so we can create an >> association between the device-type and sensors. >> >> eg: >> Fire alarm has a temperature sensor and Mobile Phone has a GPRS plus a >> temperature sensor, so we need to able to plot this information by >> identifying corresponding sensors from each device type. >> >> Therefore this brings about the need of separately managing sensors and >> device types which will ensure zero duplication of sensor information. >> >> >> This is just a thought as to how we can extend CDMF to cater sensor >> management. Please give us your comments and suggestions on $subject >> > I think there is a broader question to ask whether we do need to support sensor management holistically? For example - do we consider temperature sensors in a floor as individual sensors or a floor of sensors. My idea is - a collection of sensors can be considered as a device. To explain it further - I see two scenarios where sensors are in play:- a device has a sensor (or the sensor is a smart sensor), dumb sensors connected to a hub(device). So in that understanding - we can simplify the proposed model to have DM_DEVICE table and SENSOR table with Device ID. To take my previous example where I used the floor - there is a device (hub) for that particular floor. And the sensors are connected to the device. We manage the sensor details and device details. Counter argument to my proposal would be - will it be useful or important to manage sensor details without corresponding device details? >> Thanks, >> *Ayyoob Hamza* >> *Software Engineer* >> WSO2 Inc.; http://wso2.com >> email: [email protected] cell: +94 77 1681010 <%2B94%2077%207779495> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sachith Withana > Software Engineer; WSO2 Inc.; http://wso2.com > E-mail: sachith AT wso2.com > M: +94715518127 > Linked-In: <http://goog_416592669> > https://lk.linkedin.com/in/sachithwithana > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dulitha Wijewantha (Chan) Software Engineer - Mobile Development WSO2 Inc Lean.Enterprise.Middleware * ~Email [email protected] <[email protected]>* * ~Mobile +94712112165* * ~Website dulitha.me <http://dulitha.me>* * ~Twitter @dulitharw <https://twitter.com/dulitharw>* *~Github @dulichan <https://github.com/dulichan>* *~SO @chan <http://stackoverflow.com/users/813471/chan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
