Ambient-Oriented Programming

User Tools

Site Tools

Trace:
research:rfid

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
research:rfid [2010/07/27 17:56]
kpinte 		research:rfid [2010/08/04 14:46]
kpinte
Line 1: Line 1:
-====== Software Abstractions for the Development of Mobile RFID-enabled Applications ======+====== Distributed Object-Oriented Programming with RFID Technology ======
 //Representing RFID-tagged physical objects as **mutable software objects**//. //Representing RFID-tagged physical objects as **mutable software objects**//.
  
 [[http://soft.vub.ac.be/soft/members/kevinpinte|Kevin Pinte]] and [[http://soft.vub.ac.be/~alombide|Andoni Lombide Carreton]] [[http://soft.vub.ac.be/soft/members/kevinpinte|Kevin Pinte]] and [[http://soft.vub.ac.be/~alombide|Andoni Lombide Carreton]]
  
 +<note>
 +This page is under construction, some sections are not yet completed. Please refer to the [[:research:rfid#further_reading|futher reading]] section for a full text.
 +</note>
  
 ==== RFID-enabled Library ==== ==== RFID-enabled Library ====
Line 31: Line 34:
  
 ==== Requirements ==== ==== Requirements ====
-To align physical objects tagged with writable RFID tags as true mutable software objects we model these objects as proxy objects acting as stand-ins for physical objects. For this model to be applicable to mobile RFID- enabled applications, it must adhere to the following requirements:+To align physical objects tagged with writable RFID tags as true mutable software objects we model these objects as proxy objects acting as stand-ins for physical objects. For this model to be applicable to mobile RFID-enabled applications, it must adhere to the following requirements:
  
-  - **Addressing physical objects** RFID communication is based on broad- casting a signal. However, to be able to associate a software object with one particular physical object, it is necessary to address a single designated physical object.+  - **Addressing physical objects** RFID communication is based on broadcasting a signal. However, to be able to associate a software object with one particular physical object, it is necessary to address a single designated physical object. Object identities of digital objects should always correspond to object identities of physical objects.
   - **Storing application-specific data on RFID tags** Since mobile RFID- enabled applications do not rely on a backend database, the data on the RFID tags should be self-contained and stored on the writable memory of the tags.   - **Storing application-specific data on RFID tags** Since mobile RFID- enabled applications do not rely on a backend database, the data on the RFID tags should be self-contained and stored on the writable memory of the tags.
-  - **Reactivity to appearing and disappearing objects** It is necessary to observe the connection, reconnection and disconnection of RFID tags to keep the proxy objects synchronized with their physical counterparts. Differen- tiating between connection and reconnection is important to preserve the identity of the proxy object. Furthermore, it should be possible to react upon these events from within the application. +  - **Reactivity to appearing and disappearing objects** It is necessary to observe the connection, reconnection and disconnection of RFID tags to keep the proxy objects synchronized with their physical counterparts. Differentiating between connection and reconnection is important to preserve the identity of the proxy object. Furthermore, it should be possible to react upon these events from within the application. 
-  - **Asynchronous communication** To hide latency and keep applications responsive, communication with proxy objects representing physical objects should happen asynchronously. Blocking communication will freeze the ap- plication as soon as one physical object is unreachable.+  - **Asynchronous communication** To hide latency and keep applications responsive, communication with proxy objects representing physical objects should happen asynchronously. Blocking communication will freeze the application as soon as one physical object is unreachable.
   - **Fault-tolerant communication** Treating communication failures as the rule instead of the exception allows applications to deal with temporary unavailability of the physical objects and makes them resilient to failures. For example, read/write operations frequently fail due hardware phenomena.   - **Fault-tolerant communication** Treating communication failures as the rule instead of the exception allows applications to deal with temporary unavailability of the physical objects and makes them resilient to failures. For example, read/write operations frequently fail due hardware phenomena.
  
Line 125: Line 128:
  
 == Multiway References == == Multiway References ==
 +
 +{{:research:typesoftags.png?400|:research:typesoftags.png}}
  
  
research/rfid.txt · Last modified: 2011/09/12 18:50 by kpinte

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki