Difference between revisions of "ReadCycle Class Hierarchy"
From RifidiWiki
(→EpcGeneration2Event) |
|||
| Line 1: | Line 1: | ||
The sensors plugins in the Sensor Abstraction Layer produce ReadCycle objects that are put into Esper. Because you query objects (rather than tables) in Esper, you need to know the class hierarchy of ReadCycle in order to write queries. | The sensors plugins in the Sensor Abstraction Layer produce ReadCycle objects that are put into Esper. Because you query objects (rather than tables) in Esper, you need to know the class hierarchy of ReadCycle in order to write queries. | ||
[[Image:ReadCycle.png|thumb|400px]] | [[Image:ReadCycle.png|thumb|400px]] | ||
| − | =ReadCycle= | + | =Built-in Hierarchy= |
| + | This section details the current classes that hold data gathered from sensors which can be queried in Esper. | ||
| + | ==ReadCycle== | ||
A ReadCycle represents one cycle of interaction with a sensor. It can contain 0 to many TagReadEvent objects. A cycle of interaction might entail polling the sensor for data or perhaps the sensor is pushing data to the edge server. It is also important to realize that since the Edge Server supports the concept of logical readers, a single ReadCycle might contain tag reads from multiple physical readers. | A ReadCycle represents one cycle of interaction with a sensor. It can contain 0 to many TagReadEvent objects. A cycle of interaction might entail polling the sensor for data or perhaps the sensor is pushing data to the edge server. It is also important to realize that since the Edge Server supports the concept of logical readers, a single ReadCycle might contain tag reads from multiple physical readers. | ||
| − | =TagReadEvent= | + | ==TagReadEvent== |
A TagReadEvent represents a single tag read from an RFID reader. The TagReadEvent object is a wrapper around a DataContainerEvent in order to provide information about the tag that is not written on the tag itself. For example, suppose you are interested in knowing the antenna that saw the tag. The antenna number is not information that is stored in the tag's memory bank. You can instead put this kind of information in the TagReadEvent object. | A TagReadEvent represents a single tag read from an RFID reader. The TagReadEvent object is a wrapper around a DataContainerEvent in order to provide information about the tag that is not written on the tag itself. For example, suppose you are interested in knowing the antenna that saw the tag. The antenna number is not information that is stored in the tag's memory bank. You can instead put this kind of information in the TagReadEvent object. | ||
| − | =DatacontainerEvent= | + | ==DatacontainerEvent== |
The DatacontainerEvent is an abstract class that represents information (such as the EPC) that is stored on the tag. This class is meant to be extended to support many kinds of tag types. | The DatacontainerEvent is an abstract class that represents information (such as the EPC) that is stored on the tag. This class is meant to be extended to support many kinds of tag types. | ||
| − | =EpcGeneration1Event= | + | ==EpcGeneration1Event== |
The EPCGeneration1Event represents the information read from an EPC Gen1 tag. | The EPCGeneration1Event represents the information read from an EPC Gen1 tag. | ||
| − | =EpcGeneration2Event= | + | ==EpcGeneration2Event== |
The EPCGeneration2Event extends the EPCGeneration1Event and represents the information read from an EPC Gen2 tag. | The EPCGeneration2Event extends the EPCGeneration1Event and represents the information read from an EPC Gen2 tag. | ||
| + | =Extending the Hierarchy= | ||
Revision as of 18:43, 14 October 2009
The sensors plugins in the Sensor Abstraction Layer produce ReadCycle objects that are put into Esper. Because you query objects (rather than tables) in Esper, you need to know the class hierarchy of ReadCycle in order to write queries.
Contents
Built-in Hierarchy
This section details the current classes that hold data gathered from sensors which can be queried in Esper.
ReadCycle
A ReadCycle represents one cycle of interaction with a sensor. It can contain 0 to many TagReadEvent objects. A cycle of interaction might entail polling the sensor for data or perhaps the sensor is pushing data to the edge server. It is also important to realize that since the Edge Server supports the concept of logical readers, a single ReadCycle might contain tag reads from multiple physical readers.
TagReadEvent
A TagReadEvent represents a single tag read from an RFID reader. The TagReadEvent object is a wrapper around a DataContainerEvent in order to provide information about the tag that is not written on the tag itself. For example, suppose you are interested in knowing the antenna that saw the tag. The antenna number is not information that is stored in the tag's memory bank. You can instead put this kind of information in the TagReadEvent object.
DatacontainerEvent
The DatacontainerEvent is an abstract class that represents information (such as the EPC) that is stored on the tag. This class is meant to be extended to support many kinds of tag types.
EpcGeneration1Event
The EPCGeneration1Event represents the information read from an EPC Gen1 tag.
EpcGeneration2Event
The EPCGeneration2Event extends the EPCGeneration1Event and represents the information read from an EPC Gen2 tag.
