September 16, 2005
Application-level Events
RFID readers can scan tags for an enormous amount of data; however, the raw data produced is of a low level and not of much use to decision making applications. These applications require answers to specific questions such as "how much, where, when, how, etc." The process of arriving at meaningful data involves filtering the raw data. However, there is a need to create standards that would be applicable for applications with different needs and would require different levels of filtering of data.
On the whole, the filtering needs of most applications include removal of redundant data, combining the data gathered over a period of time, segregating, counting, etc. This led to the development of Application-Level Events that allowed the applications to communicate their requirements to an interface. These requirements could include data from particular locations, time intervals between the data gathered and data collected in response to external events, type of filtration and collation desired, etc.
The request can be either a standing request or a one-time request and data is sent to the application accordingly. ALE operates in a manner not very different how SQL works. SQL too provides applications with access to data. Like SQL, ALE eliminates the need for applications to grapple with more than necessary data. ALE can also be used to handle requests from multiple applications. rfidjournal.com reports:
ALE truly represents a significant advance in the way RFID infrastructure and applications are built. More than 60 companies participated in the EPCglobal working group that created the specification.
Read More: ALE: A New Standard for Data Access
--
Did you enjoy this post?
« RFID and consumer privacy | Main | Need-focused predeployment »
