Currentdevelopments in embeddedsystems in domainssuch as home appliances, sensor net, or simple everydayobjectbeingtaggedwith RFID:Show thatthey are gettingincreasinglysmarter and connectedwhichlead to a very large ecosystem of smart thingsLet us think of an electronic article surveillance system in a store thatwouldleveragethiseco-system: tag objectswith RFID trigger the RFID readerswith a proximitysensor trigger the security camera if somethingwasstolenbroadcast the information to the staff on their mobile phones
This leads to a problemresearched by many, showing:ToomuchprotocolsheterogeneityExpensive and time-consumingexpertknowledgeRequirements for application layer for the IoT
Four layers but: Not OSI:layers are flexible, eacheases a little more building applications: from Embedded Syst. Dev to End-UsersContribution: LayersBuilding blocks: each block is a Web APIApplications testingthese blocks
Resource Tree:functionality of the sun spot identified by resolvableURIsNot bound to one representation. We use HTML for browsability, JSON for mashups, HTTP has a content-negotiationmechanism for selecting the right representation.GET on temperature => retrieves the representation of the tempsensorPUT on LED => changes the state of the LED (on/off)http://vs3.inf.ethz.ch:8083/sunspots/
Withthis layer wewant to achievetwothings:MakethingsfindableusingsearchenginesAllow the semi-automaticintegrationintomashuptoolsGuinard, D., Trifa, V., Mattern, F., & Wilde, E. (2011). From the Internet of Things to the Web of Things: Resource-oriented Architecture and Best Practices. In D. Uckelmann, M. Harrison, & F. Michahelles (Eds.), Architecting the Internet of Things (pp. 97-129). Berlin, Heidelberg: Springer Berlin Heidelberg. Retrieved from http://www.springerlink.com/content/p314x13322qnw276
Smart things are securedbased on HTTP Basic AccessAuthentication or HTTP DigestAuthenticationAuthenticationthroughOauthUsing the social network API (OpenSocial if supported, otherwise social network proprietary API)
List of resources (i.e., services) thatcanbesharedisautomaticallygenerated by crawling (see sharing layer)
Manualmashupdev:Wetake a device on whichappscanbedeveloped by domainspecialists and, using the otherlayers, bringit to Web developers
We provide a Web page that loads the real-world data into global variables, developers then just have to create widgets by combining this data with services on the Web.
Bringingdevelopment as close as possible to endusersWecreated a frameworkthatallows the creation of dedicatedmashup editorsi.e., Web toolthat let usersbuildmashupssimply by visuallycomposingwidgetsThanks to the otherlayerseachwidgetisreduced to an HTTP call and canevenbeautomaticallygenerated.This is the EAS mashup.
Yes you could start with serving up generic information on nutrition, or recipes or product history/provenance to help aid initial purchase in storeBut in fact what you’re doing iscreating a unique relationship between a product and a consumer. How? By encouraging consumers to take digital possession of their product by identifying themselves – through FB etc – in order to link the unique tag on each product to the individual consumerSo when a consumer ‘checks into’ their bottle of olive oil, the product becomes your passport to a world of content, services, experiences based on the lifestyle territory the brand wants to own. For instance:-- Gets you discounts on bookings at Jamie Oliver restaurants-- Suggests nearby cookery classes, and so on.
Think of it as a Facebook for Things Where all things have unique identities, which are represented online. This is what we at EVRYTHNG call an Active Digital Identity This allows us to… Attach content to them To communicate via them To connect apps and services to themWhich enables things to be part of the real-time social flow of digital conversations which happens around us every day