Hi all, In my experience I think it is important to identify each sensor in the system separately if there are several of similar sensors exists. If each sensor and device in the system can be distinguish separately it is very easy to integrate any system.
For example: Think about a behavior analysis system or a smart building or a robot arm that uses IMU sensors for orientation recognition. All these scenarios require us to detect measurements coming from each sensor to identify separately. Even an application that doesn't require unique identification of sensors or devices will work fine with above capability. I think if dumb devices are connected to a smart device(A) and all such devices are connected to central system (B). Device A should be responsible of separating each data steams coming from dumb devices when sending data to B (It can use data frames when sending data [1]). Then if admin using those streams in B he can identify each sensor stream separately and do processing as needed. [1] Data Frame may be like this [--------Device ID--------|---------Sensor ID------|---------Data----------] Thanks, On Wed, Sep 16, 2015 at 2:43 PM, Ayyoob Hamza <[email protected]> wrote: > @Dulitha and @ Sachith > I see both your comments ends with the same question whether we need to > have event stream definition for each sensor type or do we need to maintain > a separate event stream for each sensor type on a device type ?. > > eg: stream definition: > Use Case 1 : org.wso2.devices.temperature (within payload send the device > type and device Id) > Use Case 2 : > org.wso2.devices.firealarm.temperature, org.wso2.devices.mobile.temperature > > This depends on the use case we think about and I see both scenarios can > be a valid argument. The question is to know whether we need to know the > sensor analysis within a device type or across device types. To cater both > scenario thought to have a sensor management as a separate module. > > This is just a thought process to bring up the concern of the problem. > This needs to be further discussed with the team. > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Viraj Senevirathne Software Engineer; WSO2, Inc. Mobile : +94 71 958 0269 Email : [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
