物联网时代的传感Web标准_IT168文库.pptVIP

In the future, we may see a rise in smart appliances and devices that are accessible utilizing the IoT. Take your refrigerator for example. It already has a sensor that knows when the door is open or closed and temperature/humidity sensors to ensure that food remains stored in the optimal environment. It has a sensor that tells you when the water filter needs to be changed. In the future, if manufacturers start embedding RFID chips in product packaging, it may even have an RFID reader that knows what products it is currently housing (there are already refrigerators out there that have RFID readers). It is a system of sensors that can be described using SensorML. Information from those sensors could be accessed from an SOS, sensors/actuators could be controlled via an SPS, and alerts could be subscribed to and received via an SAS. If my refrigerator and its associated SWE services were available over the Internet, I could be at the grocery store and use my mobile phone to ask my refrigerator what it contains or doesn’t contain. My refrigerator could alert me when a product has been stored too long and has expired. Or, my refrigerator or some SWE-enabled smart agent acting on my behalf could text me with a grocery list (generated for me based on my habits and current inventory) or e-mail me that I need to purchase a new water filter (via a WNS), or maybe the refrigerator or smart agent could even go to A or some other online store and order a new water filter for me. In this case, the use of SWE allows IoT software on my mobile device or within my home to be reusable, assuming that all of the smart appliances in my home are SWE-enabled. This simple use case extends to multiple application areas in the home like power management: smart meters, outlets, and the smart grid. A user utilizing the same SWE Client application from the previous example could access information on home power usage by outlet, retrieve the current temperature and environmental conditions