Links to Exploration step
Le document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en">An Internet of Things Example: Classrooms Access Control over Near Field Communication</title>
<author><name sortKey="Palma, Daniel" sort="Palma, Daniel" uniqKey="Palma D" first="Daniel" last="Palma">Daniel Palma</name>
</author>
<author><name sortKey="Agudo, Juan Enrique" sort="Agudo, Juan Enrique" uniqKey="Agudo J" first="Juan Enrique" last="Agudo">Juan Enrique Agudo</name>
</author>
<author><name sortKey="Sanchez, Hector" sort="Sanchez, Hector" uniqKey="Sanchez H" first="Héctor" last="Sánchez">Héctor Sánchez</name>
</author>
<author><name sortKey="Macias, Miguel Macias" sort="Macias, Miguel Macias" uniqKey="Macias M" first="Miguel Macías" last="Macías">Miguel Macías Macías</name>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">PMC</idno>
<idno type="pmid">24755520</idno>
<idno type="pmc">4029704</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4029704</idno>
<idno type="RBID">PMC:4029704</idno>
<idno type="doi">10.3390/s140406998</idno>
<date when="2014">2014</date>
<idno type="wicri:Area/Pmc/Corpus">000204</idno>
<idno type="wicri:explorRef" wicri:stream="Pmc" wicri:step="Corpus" wicri:corpus="PMC">000204</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title xml:lang="en" level="a" type="main">An Internet of Things Example: Classrooms Access Control over Near Field Communication</title>
<author><name sortKey="Palma, Daniel" sort="Palma, Daniel" uniqKey="Palma D" first="Daniel" last="Palma">Daniel Palma</name>
</author>
<author><name sortKey="Agudo, Juan Enrique" sort="Agudo, Juan Enrique" uniqKey="Agudo J" first="Juan Enrique" last="Agudo">Juan Enrique Agudo</name>
</author>
<author><name sortKey="Sanchez, Hector" sort="Sanchez, Hector" uniqKey="Sanchez H" first="Héctor" last="Sánchez">Héctor Sánchez</name>
</author>
<author><name sortKey="Macias, Miguel Macias" sort="Macias, Miguel Macias" uniqKey="Macias M" first="Miguel Macías" last="Macías">Miguel Macías Macías</name>
</author>
</analytic>
<series><title level="j">Sensors (Basel, Switzerland)</title>
<idno type="eISSN">1424-8220</idno>
<imprint><date when="2014">2014</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><textClass></textClass>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en"><p>The Internet of Things is one of the ideas that has become increasingly relevant in recent years. It involves connecting things to the Internet in order to retrieve information from them at any time and from anywhere. In the Internet of Things, sensor networks that exchange information wirelessly via Wi-Fi, Bluetooth, Zigbee or RF are common. In this sense, our paper presents a way in which each classroom control is accessed through Near Field Communication (NFC) and the information is shared via radio frequency. These data are published on the Web and could easily be used for building applications from the data collected. As a result, our application collects information from the classroom to create a control classroom tool that displays access to and the status of all the classrooms graphically and also connects this data with social networks.</p>
</div>
</front>
<back><div1 type="bibliography"><listBibl><biblStruct><analytic><author><name sortKey="Ramos, C" uniqKey="Ramos C">C. Ramos</name>
</author>
<author><name sortKey="Marreiros, G" uniqKey="Marreiros G">G. Marreiros</name>
</author>
<author><name sortKey="Santos, R" uniqKey="Santos R">R. Santos</name>
</author>
<author><name sortKey="Freitas, C F" uniqKey="Freitas C">C.F. Freitas</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Reijula, J" uniqKey="Reijula J">J. Reijula</name>
</author>
<author><name sortKey="Grohn, M" uniqKey="Grohn M">M. Gröhn</name>
</author>
<author><name sortKey="Muller, K" uniqKey="Muller K">K. Müller</name>
</author>
<author><name sortKey="Reijula, K" uniqKey="Reijula K">K. Reijula</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Doukas, C" uniqKey="Doukas C">C. Doukas</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Zhao, C" uniqKey="Zhao C">C. Zhao</name>
</author>
<author><name sortKey="Li, X S" uniqKey="Li X">X.S. Li</name>
</author>
<author><name sortKey="Chen, J S" uniqKey="Chen J">J.S. Chen</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Want, R" uniqKey="Want R">R. Want</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Ashton, K" uniqKey="Ashton K">K. Ashton</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Weiser, M" uniqKey="Weiser M">M. Weiser</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Koshizuka, N" uniqKey="Koshizuka N">N. Koshizuka</name>
</author>
<author><name sortKey="Sakamura, K" uniqKey="Sakamura K">K. Sakamura</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Conti, J P" uniqKey="Conti J">J.P. Conti</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Chui, M" uniqKey="Chui M">M. Chui</name>
</author>
<author><name sortKey="Loffler, M" uniqKey="Loffler M">M. Löffler</name>
</author>
<author><name sortKey="Roberts, R" uniqKey="Roberts R">R. Roberts</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Mellis, D" uniqKey="Mellis D">D. Mellis</name>
</author>
<author><name sortKey="Banzi, M" uniqKey="Banzi M">M. Banzi</name>
</author>
<author><name sortKey="Cuartielles, D" uniqKey="Cuartielles D">D. Cuartielles</name>
</author>
<author><name sortKey="Igoe, T" uniqKey="Igoe T">T. Igoe</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="O Reilly, T" uniqKey="O Reilly T">T. O'Reilly</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Yu, J" uniqKey="Yu J">J. Yu</name>
</author>
<author><name sortKey="Benatallah, B" uniqKey="Benatallah B">B. Benatallah</name>
</author>
<author><name sortKey="Casati, F" uniqKey="Casati F">F. Casati</name>
</author>
<author><name sortKey="Daniel, F" uniqKey="Daniel F">F. Daniel</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Miller, C C" uniqKey="Miller C">C.C. Miller</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Garcia, F D" uniqKey="Garcia F">F.D. Garcia</name>
</author>
<author><name sortKey="De Gans, G K" uniqKey="De Gans G">G.K. de Gans</name>
</author>
<author><name sortKey="Muijrers, R" uniqKey="Muijrers R">R. Muijrers</name>
</author>
<author><name sortKey="Van Rossum, P" uniqKey="Van Rossum P">P. van Rossum</name>
</author>
<author><name sortKey="Verdult, R" uniqKey="Verdult R">R. Verdult</name>
</author>
<author><name sortKey="Schreur, R W" uniqKey="Schreur R">R.W. Schreur</name>
</author>
<author><name sortKey="Jacobs, B" uniqKey="Jacobs B">B. Jacobs</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Weis, S A" uniqKey="Weis S">S.A. Weis</name>
</author>
<author><name sortKey="Sarma, S E" uniqKey="Sarma S">S.E. Sarma</name>
</author>
<author><name sortKey="Rivest, R L" uniqKey="Rivest R">R.L. Rivest</name>
</author>
<author><name sortKey="Engels, D W" uniqKey="Engels D">D.W. Engels</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Sima, I" uniqKey="Sima I">I. Sima</name>
</author>
<author><name sortKey="Tarmurean, D" uniqKey="Tarmurean D">D. Tarmurean</name>
</author>
<author><name sortKey="Greu, V" uniqKey="Greu V">V. Greu</name>
</author>
<author><name sortKey="Diaconu, A" uniqKey="Diaconu A">A. Diaconu</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Li, H" uniqKey="Li H">H. Li</name>
</author>
<author><name sortKey="Jia, Z" uniqKey="Jia Z">Z. Jia</name>
</author>
<author><name sortKey="Xue, X" uniqKey="Xue X">X. Xue</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="research-article"><pmc-dir>properties open_access</pmc-dir>
<front><journal-meta><journal-id journal-id-type="nlm-ta">Sensors (Basel)</journal-id>
<journal-id journal-id-type="iso-abbrev">Sensors (Basel)</journal-id>
<journal-title-group><journal-title>Sensors (Basel, Switzerland)</journal-title>
</journal-title-group>
<issn pub-type="epub">1424-8220</issn>
<publisher><publisher-name>MDPI</publisher-name>
</publisher>
</journal-meta>
<article-meta><article-id pub-id-type="pmid">24755520</article-id>
<article-id pub-id-type="pmc">4029704</article-id>
<article-id pub-id-type="doi">10.3390/s140406998</article-id>
<article-id pub-id-type="publisher-id">sensors-14-06998</article-id>
<article-categories><subj-group subj-group-type="heading"><subject>Article</subject>
</subj-group>
</article-categories>
<title-group><article-title>An Internet of Things Example: Classrooms Access Control over Near Field Communication</article-title>
</title-group>
<contrib-group><contrib contrib-type="author"><name><surname>Palma</surname>
<given-names>Daniel</given-names>
</name>
</contrib>
<contrib contrib-type="author"><name><surname>Agudo</surname>
<given-names>Juan Enrique</given-names>
</name>
<xref rid="c1-sensors-14-06998" ref-type="corresp"><sup>*</sup>
</xref>
</contrib>
<contrib contrib-type="author"><name><surname>Sánchez</surname>
<given-names>Héctor</given-names>
</name>
</contrib>
<contrib contrib-type="author"><name><surname>Macías</surname>
<given-names>Miguel Macías</given-names>
</name>
</contrib>
<aff id="af1-sensors-14-06998">University Center of Merida, University of Extremadura, Sta., Teresa de Jornet, 38, Mérida 06800, Spain; E-Mails:<email>dpalmage@alumnos.unex.es</email>
(D.P.);<email>sasah@unex.es</email>
(H.S.);<email>miguel@capi.unex.es</email>
(M.M.M.)</aff>
</contrib-group>
<author-notes><corresp id="c1-sensors-14-06998"><label>*</label>
Author to whom correspondence should be addressed; E-Mail: <email>jeagudo@unex.es</email>
; Tel.: +34-924-289-300 (ext. 82536); Fax: +34-924-301-212.</corresp>
</author-notes>
<pub-date pub-type="collection"><month>4</month>
<year>2014</year>
</pub-date>
<pub-date pub-type="epub"><day>21</day>
<month>4</month>
<year>2014</year>
</pub-date>
<volume>14</volume>
<issue>4</issue>
<fpage>6998</fpage>
<lpage>7012</lpage>
<history><date date-type="received"><day>28</day>
<month>1</month>
<year>2014</year>
</date>
<date date-type="rev-recd"><day>19</day>
<month>3</month>
<year>2014</year>
</date>
<date date-type="accepted"><day>09</day>
<month>4</month>
<year>2014</year>
</date>
</history>
<permissions><copyright-statement>© 2014 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2014</copyright-year>
<license><license-p>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</ext-link>
).</license-p>
</license>
</permissions>
<abstract><p>The Internet of Things is one of the ideas that has become increasingly relevant in recent years. It involves connecting things to the Internet in order to retrieve information from them at any time and from anywhere. In the Internet of Things, sensor networks that exchange information wirelessly via Wi-Fi, Bluetooth, Zigbee or RF are common. In this sense, our paper presents a way in which each classroom control is accessed through Near Field Communication (NFC) and the information is shared via radio frequency. These data are published on the Web and could easily be used for building applications from the data collected. As a result, our application collects information from the classroom to create a control classroom tool that displays access to and the status of all the classrooms graphically and also connects this data with social networks.</p>
</abstract>
<kwd-group><kwd>Internet of Things</kwd>
<kwd>NFC</kwd>
<kwd>Arduino</kwd>
<kwd>sensors</kwd>
<kwd>smart environment</kwd>
<kwd>classroom access control</kwd>
</kwd-group>
</article-meta>
</front>
<body><sec sec-type="intro"><label>1.</label>
<title>Introduction</title>
<p>The effective management of classrooms, halls, offices, and public spaces in any institution or building is often a difficult problem. There are many rooms of different types within a building; therefore, recording the activities undertaken in them in real-time is usually intricate. Thus the smart room concept described in this paper tries to solve this problem by using sensing solutions, intelligent environments or decision making environments [<xref rid="b1-sensors-14-06998" ref-type="bibr">1</xref>
,<xref rid="b2-sensors-14-06998" ref-type="bibr">2</xref>
]. Furthermore, there are many classrooms or labs in universities with a variety of equipment and purposes that are used for several subjects during an academic year. Though these classes are assigned at the beginning of the year, this can usually be changed throughout the course. When any change occurs, it is difficult to communicate within the institution and the wider university community.</p>
<p>In the light of the aforementioned context, there is an idea that has gained strength in recent years: the Internet of Things. The Internet of Things connects all the objects of everyday life such as washing machines, shoes, televisions, <italic>etc.</italic>
to the web, allowing us to access information in real time and from anywhere about this object [<xref rid="b3-sensors-14-06998" ref-type="bibr">3</xref>
]. There are many applications that are taking this technology whose major purpose is to facilitate the use and management of aspects of our daily life. One of the most extended uses is remote sensing such as fire control, which uses a sensor network throughout a forest to monitor the temperature in order to prevent potential fires [<xref rid="b4-sensors-14-06998" ref-type="bibr">4</xref>
].</p>
<p>In addition, we have other related Internet of Things technology, such as Near Field Communication (NFC) technology [<xref rid="b5-sensors-14-06998" ref-type="bibr">5</xref>
], a short range wireless technology that can be used to obtain information through identification labels. In some universities in Spain (including the University of Extremadura), the identification cards for both teachers and students possess this technology, which can be used to develop applications.</p>
<p>Related to the Internet of Things, there is free platform hardware closely linked to this technology, Arduino [<xref rid="b6-sensors-14-06998" ref-type="bibr">6</xref>
], a project whose goal is to provide simplicity in creating electronic applications. This platform has a good reputation as an electronic prototype development board because of its ease of use and the affordability of its components. Many of the applications developed with Arduino use Web 2.0 to display or collect information. There are a lot of developers in this community, sharing their knowledge through blogs and social networks and allowing anyone to use the applications they develop or the information they have managed. This information exchange is crucial as it allows the creation of projects based on this information to create or enhance new applications.</p>
<p>As already stated, the main objective of this work is to provide each classroom with a system to collect information about its real time use: establish a user identification method in each room that can be accessed from the centre, using items that the university already has, take advantage of the opportunities that the Internet of Things provides by creating an application to record the use of the classrooms. This article is organized as follows: in Section 2 the technologies involved are introduced. In Section 3 the proposed architecture for classroom access control is specified. Section 4 concludes with the work completed as well as the proposals for future work.</p>
</sec>
<sec><label>2.</label>
<title>Technologies at Work</title>
<p>In this section each of the technological aspects mentioned in this paper (the Internet of Things, Arduino, Web 2.0 and NFC) is analyzed in turn.</p>
<sec><label>2.1.</label>
<title>The Internet of Things</title>
<p>In the beginning, the Internet was only designed for communication in which computers could access websites, download content or communicate with other users. However, technologies evolve creating more powerful devices, faster and with more capabilities. Advances in electronics technology are also creating smaller devices with low power consumption which means that large networks of sensors can be created, with the ability to obtain information, process it and act accordingly. Here it is how the idea of the Internet of Things arises [<xref rid="b3-sensors-14-06998" ref-type="bibr">3</xref>
]. This term was coined in 1999 by Kevin Ashton, cofounder of Auto-ID Center at the Massachusetts Institute of Technology (MIT) [<xref rid="b7-sensors-14-06998" ref-type="bibr">7</xref>
] bearing in mind the concept of “ubiquitous computing” [<xref rid="b8-sensors-14-06998" ref-type="bibr">8</xref>
,<xref rid="b9-sensors-14-06998" ref-type="bibr">9</xref>
]. Under this term, computers and technologies are around users without noticing their presence, being able to cooperate and adapt their behaviors to the environment and enabling users to interact with technology without interfering with their everyday life. In this sense, the concept of computer as hardware device is diluted to integrate connected devices around and in cooperation with users' daily life. This research group was created with the idea of developing another emerging and innovative technology, RFID codes, and the belief that thoughts ideas and knowledge information are important and things and objects are crucial. However, the information we have today depends heavily on the data generated by users in their interactions with objects. Throughout the years, a lot of information (images, files, data, music, <italic>etc.</italic>
) has been kept which, thanks to the possibilities offered by the Internet, can be accessed from anywhere. The problem lies in the amount of time, dedication and precision required for the collection of all this information.</p>
<p>When the term “the Internet of Things” appeared it was done under the premise that if there were devices with the capacity to know everything about such objects or things. From all the data previously gathered we would be able to track and control everything and to know when things need to change [<xref rid="b10-sensors-14-06998" ref-type="bibr">10</xref>
,<xref rid="b11-sensors-14-06998" ref-type="bibr">11</xref>
]. If all our objects (shoes, appliances, books, <italic>etc.</italic>
) have small identifying devices, we may collect information from them constantly from any place. At the company level this would allow managers to have absolute control of products and stock. On a personal level, there would be improvements in many areas of our life, for example the end of thefts.</p>
<p>The characteristics of any device to be integrated into the Internet of Things are [<xref rid="b3-sensors-14-06998" ref-type="bibr">3</xref>
]:
<list list-type="bullet"><list-item><p>Collect and transmit data: the devices are in environments in which information can be collected and either sent to another device or directly to the Internet.</p>
</list-item>
<list-item><p>Operate action-based devices: devices can be programmed to act according to any condition.</p>
</list-item>
<list-item><p>Receive information: they can receive information from the network.</p>
</list-item>
<list-item><p>Support communication: the device belongs to a network of devices that can communicate with each other through other nodes in the same network.</p>
</list-item>
</list>
</p>
<p>One of the things that make it special and different is that the Internet of Things allows objects to communicate directly or indirectly to Internet. Furthermore, this information does not have to be used only by the user, but by other people for applications or studies. In terms of architecture, it is “event driven”, built from the bottom up (based on the context of processes and operations in real time) and takes into account any additional level. This implies that the Internet of Things would not be subject to certain rules and regulations, but able to handle exceptions and evolve based on the context of the event, but could also be adapted to common standards, if necessary.</p>
</sec>
<sec><label>2.2.</label>
<title>Arduino</title>
<p>The open hardware platform Arduino is closely related to the previous section [<xref rid="b12-sensors-14-06998" ref-type="bibr">12</xref>
]. Arduino is a platform that seeks simplicity when creating applications by using a combination of software and hardware; it is based on a board with a single microcontroller input/output pin for communication and control of physical objects and the environment. This kind of device has been developed to connect all kinds of objects and its functionality directly relates it to the Internet of Things.</p>
<p>This project was launched in 2005 in order to create control devices for projects that were easy to use and inexpensive to acquire. Initially the project sought to teach students electronics quickly and easily. Massimo Banzi, one of its creators, was asked to perform this task. The product consisted of cheap parts that users can easily find to create their own boards. However, the key decision was to ensure that Arduino was “plug-and-play” that someone could connect the board to one computer and use it immediately. The Arduino philosophy was that if someone wanted to learn electronics they could do it from day one without having to start from the beginning. Soon the project gained popularity for its simplicity as much as for its low price in basic models ($30). Due to its success, different versions with various capabilities have been developed (UNO, Mega, Leonardo, Mini, Due, Yún, <italic>etc.</italic>
) [<xref rid="b13-sensors-14-06998" ref-type="bibr">13</xref>
]. Arduino UNO has been chosen because of its compatibility with the other models since it is the last version of the original model. Also it offers enough capacity and functionalities to this project and in case more portability or connectivity issues are needed, we can expand it with extra shields or easily move to another board, for example Arduino Mini (smallest one) or Arduino Yún (Wifi connection). Arduino Ethernet is also used to provide Internet connectivity but it is simply an Arduino UNO that has Ethernet connector instead of USB connector.</p>
<p>Basic Arduino boards use Atmel AVR microcontrollers that have 8-bit modified Harvard RISC architecture. These microcontrollers are very simple and low cost which makes them ideal for this type of project. Arduino UNO is a microprocessor board with Atmega328 with 32 KB memory, 2 KB of RAM and 1 KB EEPROM. It also has 14 digital input/output pins (6 can be used as PWM outputs), 6 analog inputs, a ceramic resonator 16 MHz, a USB connection, a power jack, an ICSP header, and a button to restart [<xref rid="b6-sensors-14-06998" ref-type="bibr">6</xref>
].</p>
<p>Arduino shields are another of the key factors for Arduino success (<xref rid="f1-sensors-14-06998" ref-type="fig">Figure 1</xref>
). These boards allow easy assembly with Arduino models. Shields have the same pin at the same location as the Arduino models, so when they are used the pins don't have to be wired. This also enables its use by those without a great knowledge of electronics. With these shields we can also extend its communication capabilities via Ethernet, Wifi, GPRS or Xbee. Currently there are 317 shields by 125 different manufacturers in the Arduino Shield List [<xref rid="b14-sensors-14-06998" ref-type="bibr">14</xref>
].</p>
</sec>
<sec><label>2.3.</label>
<title>Web 2.0 and Mashups</title>
<p>The term Web 2.0, attributed to Tim O'Reilly [<xref rid="b15-sensors-14-06998" ref-type="bibr">15</xref>
], arises from the concept that the Web should be an “architecture of participation”, a platform for information that allows innovation by independent developers. The idea was also that it was free of use, to allow more people to participate, combined with the concept of mobility as many users from different places can be involved.</p>
<p>Web 2.0 refers to those websites that facilitate information sharing, interoperability, user-centered design and collaboration with the World Wide Web. This term includes communities, services and Web applications, social networking, video hosting services, wikis, blogs, mashups and folksonomie. Some of these associated services include:
<list list-type="bullet"><list-item><p>Blogs: they are personal spaces where authors can write articles and news in chronological order and a collaborative space where readers participate.</p>
</list-item>
<list-item><p>Wikis: a collective website construction with a specific topic, in which users are free to add, remove or edit content.</p>
</list-item>
<list-item><p>Social Networking: Web sites where each user has their own page which allows them to post content and communicate with other users.</p>
</list-item>
<list-item><p>Resource sharing environments: they are places to store all kinds of data in order to share and view them from anywhere (documents, videos, photos, <italic>etc.</italic>
).</p>
</list-item>
<list-item><p>Folksonomies: is the work of tagging Web content. The value of this action lies in that people can use their own vocabulary to explicitly add value to the content they are consuming.</p>
</list-item>
</list>
</p>
<p>In Web 2.0 there are two technologies widely used to exchange data between applications, JSON or XML:
<list list-type="bullet"><list-item><p>XML (eXtensible Markup Language) is a software technology based on information derived from SGML language and developed by the World Wide Web Consortium. The files are XML documents whose information is organized in a tree which is used for exchanging structured information on different platforms and could be validated with XML-Schemas. In fact XML is a meta-language that could be used to define our own communication language.</p>
</list-item>
<list-item><p>JSON, JavaScript Object Notation, is a lightweight alternative to XML format for sending or receiving data. JSON belongs to a subset of the object literal notation of JavaScript. JSON is a collection consisting of pairs of name/value. Since these structures are in any programming language, we can say that the exchange of data using JSON is independent of the programming language used. This has been one of the keys to its growing popularity if simplicity is sought.</p>
</list-item>
</list>
</p>
<p>The term “mashups” [<xref rid="b16-sensors-14-06998" ref-type="bibr">16</xref>
] refers to a page or Web application that takes data from one or more sources to present it in a totally different way to the original site. Integrating is quick and easy by using open source and shared data to create a distinct service from that initially provided. The architecture of a mashup consists of three parts: the content provider, that is the source of the data which may be available via API or different Web protocols such as RSS, REST or Web Services, the Site Mashup, which is the application that is created from the foreign data and, finally the client Web browser, which is the user interface of the mashup.</p>
<p>Google Maps [<xref rid="b17-sensors-14-06998" ref-type="bibr">17</xref>
] is one of the clearest examples of mashup, a web application server that offers images of maps and photographs from all over the world via satellite, from every street as well as routes between different locations. Google Maps relies on its development in JavaScript and XML. Google Maps allow free use but can also be customized. Changing the color of the maps, using your own pictures to display a particular place as well as the addition of information through tables or symbols are for example the way you can customize your map. Initially, the user uses the Google map server for viewing. Once downloaded, changes don't go through the server (which is obvious), so Google uses AJAX technology to make these changes without going through the server to create an interactive application. These applications run in a user's browser and communicate in the background. AJAX is an asynchronous technology, meaning that additional data is requested from the server and loaded in the background without interfering with the display and behavior of the page.</p>
</sec>
<sec><label>2.4.</label>
<title>Near Field Communication</title>
<p>Near field communication (NFC) is a wireless short-range and high frequency communication technology that allows the exchange of data between devices. This technology is based on electromagnetic fields [<xref rid="b5-sensors-14-06998" ref-type="bibr">5</xref>
] that usually communicate by using an identification card with a reader. The standard governing the use of electronic identification cards and smart cards is ISO 14443 (RFID), which is managed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) and FeliCa. NFC works in the field of 13.56 MHz and shares the characteristics of the ISO 14443.</p>
<p>NFC Smart cards are not used only in card format. This technology can be integrated into cards, keychains, bracelets and mobiles. In addition, Smartphones with this technology can also be used to exchange information or to read passive RFID tags. Its transfer rate can reach 424 kbit/s. This is somewhat limited, so its use is usually intended for other purposes. NFC is not used to transfer large amounts of data; their main aim is instant communication.</p>
<p>The maximum range of NFC is 20 cm. Although this may seem to be a disadvantage, it does not have to be, as this is what leads to improved security. Also NFC teams are able to send and receive information simultaneously. Because NFC devices must be in close proximity to each other, usually not more than a few centimeters, they have become a popular choice for secure communication between consumer devices such as Smartphones. Therefore peer-to-peer is a defining feature of NFC. An NFC device can act as both a reader and a label. This is one of the features for their use in mobile payment. In our case, MiFare cards are selected since are extensively used in access control for office buildings, payment systems for public transport, as well as other applications [<xref rid="b18-sensors-14-06998" ref-type="bibr">18</xref>
].</p>
</sec>
</sec>
<sec><label>3.</label>
<title>Architecture Design for Classrooms Access Control</title>
<p>The operation of this project is governed by the functionality of the Internet of Things [<xref rid="b3-sensors-14-06998" ref-type="bibr">3</xref>
]. Our classrooms registration system is based on a network of connected sensors that collect information that is then uploaded to the cloud so that any application can use this information when necessary. This scheme has two distinct parts which include:
<list list-type="bullet"><list-item><p>The “thing”, which contains in our case is the classroom and its access.</p>
</list-item>
<list-item><p>The cloud, which are Internet applications where the data is stored.</p>
</list-item>
</list>
</p>
<p>The overall process is described in <xref rid="f2-sensors-14-06998" ref-type="fig">Figure 2</xref>
, where each class collects the data of interest through NFC, which is sent through the RF and then stored in the cloud so that the information can be accessed by the application.</p>
<p>In more detail, the system would start working when trying to access a classroom (<xref rid="f3-sensors-14-06998" ref-type="fig">Figure 3</xref>
), a process where an ID card would be used for this purpose. The user uses an NFC card reader connected to the Arduino device that shows a message on the LCD screen and one of the LEDs lights up, showing that the classroom is in use (red LED).</p>
<p>Immediately afterwards, the Arduino device connects to another Arduino (Master) by radio to identify the user accessing the classroom system. The system will use this ID to connect to the database and check whether it is a teacher and retrieve their name.</p>
<p>The next step is sending the data to the cloud, transferring the name of the teacher and the classroom to the server platform Xively [<xref rid="b19-sensors-14-06998" ref-type="bibr">19</xref>
] to be conveniently stored.</p>
<p>From the data stored in Xively, two applications are created. On the one hand, Google Maps is used for retrieving data from Xively to create a map of the university showing the classroom information. This application can be accessed from any computer and the contents can be displayed on the university information screens (TV panels).On the other hand, an application could send messages with information from each classroom by taking advantage of the social network Twitter (tweets). To help us accomplish this task, the tool Zapier is used [<xref rid="b20-sensors-14-06998" ref-type="bibr">20</xref>
].</p>
<sec><label>3.1.</label>
<title>Hardware</title>
<p>In this section the hardware used in the two types of nodes is described. Classroom nodes that read the card sent by RF are composed of (<xref rid="f4-sensors-14-06998" ref-type="fig">Figure 4</xref>
):
<list list-type="bullet"><list-item><p>Arduino UNO.</p>
</list-item>
<list-item><p>NFC module for Arduino and communication shield from cooking-hacks [<xref rid="b21-sensors-14-06998" ref-type="bibr">21</xref>
].</p>
</list-item>
<list-item><p>LCD screen,</p>
</list-item>
<list-item><p>Two LEDs (Red and Green),</p>
</list-item>
<list-item><p>Radio Frequency module (433 MHZ).</p>
</list-item>
</list>
</p>
<p>On the other hand, the master node is responsible for receiving the RF information and sends it to the cloud through Ethernet so it includes (<xref rid="f5-sensors-14-06998" ref-type="fig">Figure 5</xref>
):
<list list-type="bullet"><list-item><p>Arduino Ethernet.</p>
</list-item>
<list-item><p>Radio Frequency module (433 MHZ).</p>
</list-item>
</list>
</p>
</sec>
<sec><label>3.2.</label>
<title>Reading Data (NFC)</title>
<p>The collection of data through user interaction with an NFC reader is the initial offstage in the system. The description of the reader and how it works is presented below. Our NFC reader consists of an Arduino Uno, a Xbee shield with an NFC reader, a radio frequency module, an LCD display and two LEDs. Before attempting to access the classroom, it could be either free or occupied. If it is free it will be possible to complete the identification process and access the classroom.</p>
<p><xref rid="f6-sensors-14-06998" ref-type="fig">Figure 6a</xref>
(see above) shows the reading process of cards. First the reader will read and identify two facts: ID and user name. In the NFC, and MiFare RFID technologies, the ID card is called UID. The UID is the first four bytes to be found in block 0 of sector 0. The other data should have been already saved. To record this information, keep in mind that each block is composed of sectors of 16 bytes. The write and read position is the address memory 4.</p>
<p>Once the player has collected this information, it displays a message on a screen with information on the user's name and ID in hexadecimal. If the state of the classroom is busy this is displayed on the LCD screen by turning on the red light and sending the information read by radio. To send data, the reader uses the NFC RF module on the computer using Arduino Uno pin 6 to send the data. Once the data has been sent, the reader saves the state of the class, occupied or empty. When a user wants to leave the classroom and thus change the status, they must swipe their card through the reader, which then follows the process described above and confirms the output of this with a new message and by lighting the green LED.</p>
<p>At this point a third use case is considered. It may be that a user leaves the classroom forgetting to swipe him/her card, making the status remains busy. In this case, a new user being aware of this condition, passes their card and the reader identifies the new ID and checks with the new user to ensure that this is a change. From here, the system will work just as described above.</p>
<p>Security solutions in RFID or RF communications have not been considered because of the information sent (card ID and classroom ID) and its use in this way is not critical. But in case that the system needs improving its security the RF communication could be encrypted [<xref rid="b22-sensors-14-06998" ref-type="bibr">22</xref>
] via software or choosing more secure transmission solutions as Zigbee. Regarding the software, the RMF12B library [<xref rid="b23-sensors-14-06998" ref-type="bibr">23</xref>
] could be used so that we just need a very small size algorithm for Arduino devices. Likewise, it provides encryption with XXTEA algorithm that operates with 64-bit blocks and uses 128-bit keys which is a strong alternative talking about small solutions [<xref rid="b24-sensors-14-06998" ref-type="bibr">24</xref>
]. In the Zigbee case, it includes the encryption as an option since it is based on a 128-bit AES algorithm incorporating the strong security elements of the IEEE 802.15.4 standard [<xref rid="b25-sensors-14-06998" ref-type="bibr">25</xref>
]. This option needs hardware modification, including an Xbee ZB device [<xref rid="b26-sensors-14-06998" ref-type="bibr">26</xref>
] and a Bee socket [<xref rid="b27-sensors-14-06998" ref-type="bibr">27</xref>
] in both nodes Zigbee module will communicate via serial with Arduino.</p>
</sec>
<sec><label>3.3.</label>
<title>Processing Data</title>
<p>The master node is the destination of the data that the NFC reader has obtained and sent by radio frequency. The master consists of an Arduino Ethernet and RF module with a receiving antenna (<xref rid="f7-sensors-14-06998" ref-type="fig">Figure 7</xref>
).</p>
<p>Initially, the receiver will connect to the network by using its Ethernet connection and prepare the necessary pin (pin 2) for receiving data via radio frequency. Once done, it will remain in standby until it receives the data.</p>
<p>Once the receiver has collected data by the NFC reader, it must perform processing to complete this information. Keep in mind that when reading NFC, it is transmitting the identification code for each user and the classroom they want to access, while finding the name of the user involves consulting the database hosted on the server. To place a PHP service in the same server through an HTTP request from our Arduino, the user name and related information will be returned when the ID is received from the reader. This information will be required to store data in the cloud, as discussed in the following section. In order to get a good performance in the master node, the data is uploaded to the cloud immediately and no information is saved on it (<xref rid="f6-sensors-14-06998" ref-type="fig">Figure 6(b)</xref>
).</p>
</sec>
<sec><label>3.4.</label>
<title>Data in the Cloud</title>
<p>Since the major goal of this project is mainly focused on the access to the classroom by teachers, the response from the server database to the http request can only contain the teacher's name. Thus, if the person were not registered in the database, it would imply that such user is not a teacher, or an authorized person, and access would not be consequently registered.</p>
<p>Once the data of an access are read, it is sent to our server to map the classrooms so that the results are displayed and are visible to everyone. This data is only sent to Xively when the state changes instead of updating it periodically.</p>
<p>The explanation of how the Xively server works is briefly described below. Xively provides a working environment in which you can create a new project for each application. Each project consists of a number of variables called “channels” that store the values of our applications. In our case, a channel for each classroom that we will use is created.</p>
<p>The program created in Arduino, takes the name of the teacher as a variable and uses the PUT function of Xively and the appropriate parameters (key to our account on the server and classroom ID) to update the server data (<xref rid="f8-sensors-14-06998" ref-type="fig">Figure 8</xref>
). To make use of these functions, first the Xively page is checked to obtain a password to use their API, then the project is identified as “feed” and the Xively library to Arduino is downloaded.</p>
</sec>
<sec><label>3.5.</label>
<title>Using the Data: Google Maps App</title>
<p>In this part, the data are already stored on the server, which means that they can be accessed from anywhere from any application. An application that makes use of that data is created. The application will consist of a combination of Google Maps with data stored in Xively. The application shows a map of the University Center of Merida in which information boxes for each classroom appear (<xref rid="f9-sensors-14-06998" ref-type="fig">Figure 9</xref>
). If a teacher is in a classroom, teacher's name will appear on the corresponding box.</p>
<p>To implement this application, three major elements are used: Xively API, Google Maps API and JSON technology. In order to use API Xively, it will be necessary to establish the same values as in the previous section: the project feed and the API key. As for the Google API, you can access Google Maps as developers to get the key and to work with the maps.</p>
<p>The JSON language is also used to combine both applications. In this case the XivelyJS library which allows us to use this system is used. Therefore the application will retrieve data from Xively to build information boxes in Google Maps. The application will be accessible from any browser and does not need to be refreshed as any change in the status of the classrooms will be reflected in the application instantly.</p>
</sec>
<sec><label>3.6.</label>
<title>Reusing Data: Social Networks</title>
<p>This section consists of creating an application that allows us to publish data stored in Xively in a social network by using the tool Zapier. This tool is easy to use and has been chosen for its high interoperability. At present you can connect over 250 Web apps. One only needs to decide [<xref rid="b20-sensors-14-06998" ref-type="bibr">20</xref>
] which application best suits his/her need.</p>
<p>Zapier is a service that allows us to combine several Web applications. With Zapier tasks can be performed automatically because it allows certain actions in the application or website to cause various tasks to be performed in a second application. Zapier defines this type of action as a zap: “When a new thing comes to A, B does something else”. Zapier allows great customization of tasks by defining each field within an application to be set: the text that is sent, regularity, parameters, <italic>etc.</italic>
</p>
<p>Besides customization, Zapier allows a large number of shares and a large number of tools to be used. Each of these services allows an action in an application (e.g., receiving an email in Gmail) to be reflected in another, separate application (for example by adding a reminder in Evernote).</p>
<p>One of these services, called Web hook is being used. Web hook involves taking data from Xively and posting it elsewhere-in this case in the social network Twitter (<xref rid="f10-sensors-14-06998" ref-type="fig">Figure 10</xref>
). Whenever a change occurs in any of the channels (classrooms), Zapier automatically sends a tweet to the account indicated showing the change and state.</p>
</sec>
</sec>
<sec><label>4.</label>
<title>Conclusions and Future Work</title>
<p>A tool and a device have been developed to manage classrooms in real time. To do this, a transmitter/receiver access control for each classroom has been created, data are uploaded to the cloud and a Web application to view the data has been built.</p>
<p>Arduino hardware has provided enormous simplicity in the development of the prototype. The different modules and shields are successfully integrated. The programming of the device was not complicated as the Arduino developer community is large and there are many tutorials that can be accessed via the net.</p>
<p>The most important part was the development of the Web application. Using Google API for their maps, combined with the data hosted on the Xively server, has been the key to this project. This work has shown an example of integrating different technologies by using the basic principles of the Internet of Things. The result is that a thing, the classroom, registers information in the cloud via a sensor network created with Arduino components. Different applications that make use of data by integrating them into an application that uses Google Maps to produce information published on Twitter has been developed. This not only shows the possibilities of the Internet of Things but also scalability and reuse of data that can be generated. Also NFC, RF, Arduino, Xively, Google Maps and Zapier technologies are combined in the same project with a successfull result that tests the power of the Internet of Things for managing and sharing data.</p>
<p>Therefore, it should be noted that the possibilities exist not only in controlling access to classrooms but in the use of information stored in the cloud to create new applications. This system offers the solution to a problem but also lays the foundation for a series of future projects that could lead to additional improvements as follows.</p>
<p>More roles for access to the classroom could be integrated into the project. In the project only the role of teacher is taken into account. However, one could add the roles of non-teaching staff and students, such as allowing access to staff without a record of activity in the Web application or allowing students access at set times.</p>
<p>The system functionality could be increased by placing a relay and automatic locks allowing the door of the classroom to open when a card with authorized access is swiped. In addition, by placing motion sensors, or sensors that measure temperature, sound or light, to detect use, would remove the need for the teacher to swipe a card when entering the classroom. In the application server and Xively, the subject and schedule of teacher could be added, as well as the equipment needed and the student roster.</p>
<p>Finally, the data shared in social networks could be used for additional purposes by combining it with other applications such as updating the school Google Calendar.</p>
</sec>
</body>
<back><ack><p>This work has been partly supported by “Gobierno de Extremadura” through the project GR10081.</p>
</ack>
<notes><title>Author Contributions</title>
<p>J.E.A. designed the whole platform and the integration of different systems. D.P. developed the software that runs on Arduino nodes, database, communications and client application. H.S. provided the software interface between the different components of the system. M.M.M. built the hardware of the nodes and chose their components. Finally, all the authors provided corresponding information for the manuscript preparation and collaborated in its redaction.</p>
</notes>
<notes><title>Conflicts of Interest</title>
<p>The authors declare no conflict of interest.</p>
</notes>
<ref-list><title>References</title>
<ref id="b1-sensors-14-06998"><label>1.</label>
<element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Ramos</surname>
<given-names>C.</given-names>
</name>
<name><surname>Marreiros</surname>
<given-names>G.</given-names>
</name>
<name><surname>Santos</surname>
<given-names>R.</given-names>
</name>
<name><surname>Freitas</surname>
<given-names>C.F.</given-names>
</name>
</person-group>
<article-title>Smart Offices and Intelligent Decision Rooms</article-title>
<source>Handbook of Ambient Intelligence and Smart Environments</source>
<person-group person-group-type="editor"><name><surname>Nakashima</surname>
<given-names>H.</given-names>
</name>
<name><surname>Aghajan</surname>
<given-names>H.</given-names>
</name>
<name><surname>Augusto</surname>
<given-names>J.C.</given-names>
</name>
</person-group>
<publisher-name>Springer</publisher-name>
<publisher-loc>New York, NY, USA</publisher-loc>
<year>2010</year>
<fpage>851</fpage>
<lpage>880</lpage>
</element-citation>
</ref>
<ref id="b2-sensors-14-06998"><label>2.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Reijula</surname>
<given-names>J.</given-names>
</name>
<name><surname>Gröhn</surname>
<given-names>M.</given-names>
</name>
<name><surname>Müller</surname>
<given-names>K.</given-names>
</name>
<name><surname>Reijula</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Human well-being and flowing work in an intelligent work environment</article-title>
<source>Intell. Build. Int.</source>
<year>2011</year>
<volume>3</volume>
<fpage>223</fpage>
<lpage>237</lpage>
</element-citation>
</ref>
<ref id="b3-sensors-14-06998"><label>3.</label>
<element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Doukas</surname>
<given-names>C.</given-names>
</name>
</person-group>
<source>Building Internet of Things with the Arduino</source>
<publisher-name>CreateSpace</publisher-name>
<publisher-loc>North Charleston, SC, USA</publisher-loc>
<year>2012</year>
</element-citation>
</ref>
<ref id="b4-sensors-14-06998"><label>4.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Zhao</surname>
<given-names>C.</given-names>
</name>
<name><surname>Li</surname>
<given-names>X.S.</given-names>
</name>
<name><surname>Chen</surname>
<given-names>J.S.</given-names>
</name>
</person-group>
<article-title>Study on the application of internet of things in the logistics in forest industry</article-title>
<source>Appl. Mech. Mater.</source>
<year>2011</year>
<volume>97–98</volume>
<fpage>664</fpage>
<lpage>668</lpage>
</element-citation>
</ref>
<ref id="b5-sensors-14-06998"><label>5.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Want</surname>
<given-names>R.</given-names>
</name>
</person-group>
<article-title>Near field communication</article-title>
<source>IEEE Pervasive Comput.</source>
<year>2011</year>
<volume>10</volume>
<fpage>4</fpage>
<lpage>7</lpage>
</element-citation>
</ref>
<ref id="b6-sensors-14-06998"><label>6.</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><collab>Arduino—HomePage</collab>
</person-group>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="http://arduino.cc/">http://arduino.cc/</ext-link>
</comment>
<date-in-citation>(accessed on 26 December 2013)</date-in-citation>
</element-citation>
</ref>
<ref id="b7-sensors-14-06998"><label>7.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Ashton</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>That “Internet of Things” Thing</article-title>
<source>RFiD J.</source>
<year>2009</year>
<volume>22</volume>
<fpage>97</fpage>
<lpage>114</lpage>
</element-citation>
</ref>
<ref id="b8-sensors-14-06998"><label>8.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Weiser</surname>
<given-names>M.</given-names>
</name>
</person-group>
<article-title>The Computer for the 21st Century</article-title>
<source>Sci. Am.</source>
<year>1991</year>
<volume>265</volume>
<fpage>94</fpage>
<lpage>104</lpage>
</element-citation>
</ref>
<ref id="b9-sensors-14-06998"><label>9.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Koshizuka</surname>
<given-names>N.</given-names>
</name>
<name><surname>Sakamura</surname>
<given-names>K.</given-names>
</name>
</person-group>
<article-title>Ubiquitous ID: Standards for ubiquitous computing and the internet of things</article-title>
<source>IEEE Pervasive Comput.</source>
<year>2010</year>
<volume>9</volume>
<fpage>98</fpage>
<lpage>101</lpage>
</element-citation>
</ref>
<ref id="b10-sensors-14-06998"><label>10.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Conti</surname>
<given-names>J.P.</given-names>
</name>
</person-group>
<article-title>The Internet of things</article-title>
<source>Commun. Eng.</source>
<year>2006</year>
<volume>4</volume>
<fpage>20</fpage>
<lpage>25</lpage>
</element-citation>
</ref>
<ref id="b11-sensors-14-06998"><label>11.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Chui</surname>
<given-names>M.</given-names>
</name>
<name><surname>Löffler</surname>
<given-names>M.</given-names>
</name>
<name><surname>Roberts</surname>
<given-names>R.</given-names>
</name>
</person-group>
<article-title>The internet of things</article-title>
<source>McKinsey Q.</source>
<year>2010</year>
<volume>2</volume>
<fpage>1</fpage>
<lpage>9</lpage>
</element-citation>
</ref>
<ref id="b12-sensors-14-06998"><label>12.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Mellis</surname>
<given-names>D.</given-names>
</name>
<name><surname>Banzi</surname>
<given-names>M.</given-names>
</name>
<name><surname>Cuartielles</surname>
<given-names>D.</given-names>
</name>
<name><surname>Igoe</surname>
<given-names>T.</given-names>
</name>
</person-group>
<article-title>Arduino: An open electronic prototyping platform</article-title>
<conf-name>Proceedings of the CHI Conference</conf-name>
<conf-loc>San Jose, CA, USA</conf-loc>
<conf-date>28 April–3 May 2007</conf-date>
<volume>Volume. 2007</volume>
</element-citation>
</ref>
<ref id="b13-sensors-14-06998"><label>13.</label>
<element-citation publication-type="webpage"><article-title>Arduino—Products</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="http://arduino.cc/en/Main/Products#.UxcW0YXEHd4">http://arduino.cc/en/Main/Products#.UxcW0YXEHd4</ext-link>
</comment>
<date-in-citation>(accessed on 5 March 2014)</date-in-citation>
</element-citation>
</ref>
<ref id="b14-sensors-14-06998"><label>14.</label>
<element-citation publication-type="webpage"><article-title>Arduino Shield List</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="http://shieldlist.org/">http://shieldlist.org/</ext-link>
</comment>
<date-in-citation>(accessed on 2 January 2014)</date-in-citation>
</element-citation>
</ref>
<ref id="b15-sensors-14-06998"><label>15.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>O'Reilly</surname>
<given-names>T.</given-names>
</name>
</person-group>
<article-title>What is Web 2.0: Design patterns and business models for the next generation of software</article-title>
<source>Int. J. Digit. Econ.</source>
<year>2007</year>
<volume>65</volume>
<fpage>17</fpage>
<lpage>37</lpage>
</element-citation>
</ref>
<ref id="b16-sensors-14-06998"><label>16.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Yu</surname>
<given-names>J.</given-names>
</name>
<name><surname>Benatallah</surname>
<given-names>B.</given-names>
</name>
<name><surname>Casati</surname>
<given-names>F.</given-names>
</name>
<name><surname>Daniel</surname>
<given-names>F.</given-names>
</name>
</person-group>
<article-title>Understanding Mashup Development</article-title>
<source>IEEE Internet Comput.</source>
<year>2008</year>
<volume>12</volume>
<fpage>44</fpage>
<lpage>52</lpage>
</element-citation>
</ref>
<ref id="b17-sensors-14-06998"><label>17.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Miller</surname>
<given-names>C.C.</given-names>
</name>
</person-group>
<article-title>A Beast in the Field: The Google Maps Mashup as GIS/2</article-title>
<source>Cartogr. Int. J. Geogr. Inf. Geovisualization</source>
<year>2006</year>
<volume>41</volume>
<fpage>187</fpage>
<lpage>199</lpage>
</element-citation>
</ref>
<ref id="b18-sensors-14-06998"><label>18.</label>
<element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Garcia</surname>
<given-names>F.D.</given-names>
</name>
<name><surname>de Gans</surname>
<given-names>G.K.</given-names>
</name>
<name><surname>Muijrers</surname>
<given-names>R.</given-names>
</name>
<name><surname>van Rossum</surname>
<given-names>P.</given-names>
</name>
<name><surname>Verdult</surname>
<given-names>R.</given-names>
</name>
<name><surname>Schreur</surname>
<given-names>R.W.</given-names>
</name>
<name><surname>Jacobs</surname>
<given-names>B.</given-names>
</name>
</person-group>
<article-title>Dismantling MIFARE Classic</article-title>
<source>Computer Security-ESORICS 2008</source>
<person-group person-group-type="editor"><name><surname>Jajodia</surname>
<given-names>S.</given-names>
</name>
<name><surname>Lopez</surname>
<given-names>J.</given-names>
</name>
</person-group>
<publisher-name>Lecture Notes in Computer Science; Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Berlin, German</publisher-loc>
<year>2008</year>
<fpage>97</fpage>
<lpage>114</lpage>
</element-citation>
</ref>
<ref id="b19-sensors-14-06998"><label>19.</label>
<element-citation publication-type="webpage"><article-title>Xively-Public Cloud for the Internet of Things</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="https://xively.com/">https://xively.com/</ext-link>
</comment>
<date-in-citation>(accessed on 4 January 2014)</date-in-citation>
</element-citation>
</ref>
<ref id="b20-sensors-14-06998"><label>20.</label>
<element-citation publication-type="webpage"><article-title>Automate the Web-Zapier</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="https://zapier.com/">https://zapier.com/</ext-link>
</comment>
<date-in-citation>(accessed on 4 January 2014)</date-in-citation>
</element-citation>
</ref>
<ref id="b21-sensors-14-06998"><label>21.</label>
<element-citation publication-type="webpage"><article-title>Cooking Hacks-Electronics for Arduino, Raspberry Pi and 3D Printers</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="http://www.cooking-hacks.com/">http://www.cooking-hacks.com/</ext-link>
</comment>
<date-in-citation>(accessed on 3 January 2014)</date-in-citation>
</element-citation>
</ref>
<ref id="b22-sensors-14-06998"><label>22.</label>
<element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Weis</surname>
<given-names>S.A.</given-names>
</name>
<name><surname>Sarma</surname>
<given-names>S.E.</given-names>
</name>
<name><surname>Rivest</surname>
<given-names>R.L.</given-names>
</name>
<name><surname>Engels</surname>
<given-names>D.W.</given-names>
</name>
</person-group>
<article-title>Security and Privacy Aspects of Low-Cost Radio Frequency Identification Systems</article-title>
<source>Security in Pervasive Computing</source>
<person-group person-group-type="editor"><name><surname>Hutter</surname>
<given-names>D.</given-names>
</name>
<name><surname>Müller</surname>
<given-names>G.</given-names>
</name>
<name><surname>Stephan</surname>
<given-names>W.</given-names>
</name>
<name><surname>Ullmann</surname>
<given-names>M.</given-names>
</name>
</person-group>
<publisher-name>Lecture Notes in Computer Science; Springer Berlin Heidelberg</publisher-name>
<publisher-loc>Berlin, German</publisher-loc>
<year>2004</year>
<fpage>201</fpage>
<lpage>212</lpage>
</element-citation>
</ref>
<ref id="b23-sensors-14-06998"><label>23.</label>
<element-citation publication-type="webpage"><article-title>LowPowerLab/RFM12B</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="https://github.com/LowPowerLab/RFM12B">https://github.com/LowPowerLab/RFM12B</ext-link>
</comment>
<date-in-citation>(accessed on 18 March 2014)</date-in-citation>
</element-citation>
</ref>
<ref id="b24-sensors-14-06998"><label>24.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Sima</surname>
<given-names>I.</given-names>
</name>
<name><surname>Tarmurean</surname>
<given-names>D.</given-names>
</name>
<name><surname>Greu</surname>
<given-names>V.</given-names>
</name>
<name><surname>Diaconu</surname>
<given-names>A.</given-names>
</name>
</person-group>
<article-title>XXTEA, an alternative replacement of KASUMI cipher algorithm in A5/3 GSM and f8, f9 UMTS data security functions</article-title>
<conf-name>Proceedings of the 9th International Conference on Communications (COMM)</conf-name>
<conf-loc>Bucharest, Romania</conf-loc>
<conf-date>21–23 June 2012</conf-date>
<fpage>323</fpage>
<lpage>326</lpage>
</element-citation>
</ref>
<ref id="b25-sensors-14-06998"><label>25.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Li</surname>
<given-names>H.</given-names>
</name>
<name><surname>Jia</surname>
<given-names>Z.</given-names>
</name>
<name><surname>Xue</surname>
<given-names>X.</given-names>
</name>
</person-group>
<article-title>Application and analysis of ZigBee security services specification</article-title>
<conf-name>Second International Conference on Networks Security Wireless Communications and Trusted Computing (NSWCTC)</conf-name>
<conf-loc>Wuhan, China</conf-loc>
<conf-date>24–25 April 2010</conf-date>
<volume>Volume 2</volume>
<fpage>494</fpage>
<lpage>497</lpage>
</element-citation>
</ref>
<ref id="b26-sensors-14-06998"><label>26.</label>
<element-citation publication-type="webpage"><article-title>XBee<sup>®</sup>
ZB-Digi International</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-zb-module">http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-zb-module</ext-link>
</comment>
<date-in-citation>(accessed on 18 March 2014)</date-in-citation>
</element-citation>
</ref>
<ref id="b27-sensors-14-06998"><label>27.</label>
<element-citation publication-type="webpage"><article-title>Grove—Bee Socket—Wiki</article-title>
<comment>Available online: <ext-link ext-link-type="uri" xlink:href="http://www.seeedstudio.com/wiki/Grove_-_Bee_Socket">http://www.seeedstudio.com/wiki/Grove_-_Bee_Socket</ext-link>
</comment>
<date-in-citation>(accessed on 18 March 2014)</date-in-citation>
</element-citation>
</ref>
</ref-list>
</back>
<floats-group><fig id="f1-sensors-14-06998" position="float"><label>Figure 1.</label>
<caption><p>Arduino UNO and Ethernet shield.</p>
</caption>
<graphic xlink:href="sensors-14-06998f1"></graphic>
</fig>
<fig id="f2-sensors-14-06998" position="float"><label>Figure 2.</label>
<caption><p>System communication scheme.</p>
</caption>
<graphic xlink:href="sensors-14-06998f2"></graphic>
</fig>
<fig id="f3-sensors-14-06998" position="float"><label>Figure 3.</label>
<caption><p>Overall system.</p>
</caption>
<graphic xlink:href="sensors-14-06998f3"></graphic>
</fig>
<fig id="f4-sensors-14-06998" position="float"><label>Figure 4.</label>
<caption><p>Classroom node hardware prototype: (<bold>a</bold>
) outside (<bold>b</bold>
) inside.</p>
</caption>
<graphic xlink:href="sensors-14-06998f4"></graphic>
</fig>
<fig id="f5-sensors-14-06998" position="float"><label>Figure 5.</label>
<caption><p>Master node hardware prototype: (<bold>a</bold>
) outside (<bold>b</bold>
) inside.</p>
</caption>
<graphic xlink:href="sensors-14-06998f5"></graphic>
</fig>
<fig id="f6-sensors-14-06998" position="float"><label>Figure 6.</label>
<caption><p>System flowchart diagram (<bold>a</bold>
) reading cards (<bold>b</bold>
) uploading data to cloud.</p>
</caption>
<graphic xlink:href="sensors-14-06998f6"></graphic>
</fig>
<fig id="f7-sensors-14-06998" position="float"><label>Figure 7.</label>
<caption><p>Processing data.</p>
</caption>
<graphic xlink:href="sensors-14-06998f7"></graphic>
</fig>
<fig id="f8-sensors-14-06998" position="float"><label>Figure 8.</label>
<caption><p>Putting data in the cloud.</p>
</caption>
<graphic xlink:href="sensors-14-06998f8"></graphic>
</fig>
<fig id="f9-sensors-14-06998" position="float"><label>Figure 9.</label>
<caption><p>Data in the map.</p>
</caption>
<graphic xlink:href="sensors-14-06998f9"></graphic>
</fig>
<fig id="f10-sensors-14-06998" position="float"><label>Figure 10.</label>
<caption><p>How Zapier sends tweets.</p>
</caption>
<graphic xlink:href="sensors-14-06998f10"></graphic>
</fig>
</floats-group>
</pmc>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Informatique/explor/SgmlV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 0002049 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 0002049 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Wicri/Informatique |area= SgmlV1 |flux= Pmc |étape= Corpus |type= RBID |clé= |texte= }}
![]() | This area was generated with Dilib version V0.6.33. | ![]() |