ReadCycle Class Hierarchy - Revision history

Matt: Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

2010-11-26T19:43:38Z

Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

Amesycyxa at 23:12, 23 November 2010

2010-11-23T23:12:28Z

Kyle: /* Extending the Hierarchy */

2009-10-14T19:21:08Z

‎Extending the Hierarchy

Kyle at 18:43, 14 October 2009

2009-10-14T18:43:57Z

Kyle: /* EpcGeneration2Event */

2009-10-14T18:39:55Z

‎EpcGeneration2Event

Kyle: /* EpcGeneration1Event */

2009-10-14T18:38:57Z

‎EpcGeneration1Event

Kyle: /* DatacontainerEvent */

2009-10-14T18:37:07Z

‎DatacontainerEvent

Kyle: /* TagReadEvent */

2009-10-14T18:35:49Z

‎TagReadEvent

Kyle: /* ReadCycle */

2009-10-14T18:30:39Z

‎ReadCycle

Kyle at 18:11, 14 October 2009

2009-10-14T18:11:39Z

@@ 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.
 [[Image:ReadCycle.png|thumb|400px]]
@@ Line 31: / Line 23: @@
 Furthermore, you can query the data in your esper statements.  For example, you can ask for all tags where the speed of the tag is greater than 4 m/s like this:
-&lt;pre&gt;
+<pre>
-Select * from ReadCycle[select * from tags(cast(speed?,Integer) &gt; 4)]
+Select * from ReadCycle[select * from tags(cast(speed?,Integer) > 4)]
-&lt;/pre&gt;
+</pre>
 ==Extending DatacontainerEvent==
 You would extend the DatacontainerEvent when the tag you are using in your RFID system is not an EPC Gen1 or Gen2 tag.  For example, if you are using active tags which do not follow the EPC Gen2 specification, then you will want to make up a new Class that represents the kind of tags you are using.
 ==Adding new Event Types in Esper==
 If you need to query the new event types that you created by extending the other classes, you will need to add those event types to Esper with code like this:
-&lt;pre&gt;
+<pre>
-esperService.getProvider().getEPAdministrator().getConfiguration.addEventType(&quot;MyNewEvent&quot;,MyNewEvent.class);
+esperService.getProvider().getEPAdministrator().getConfiguration.addEventType("MyNewEvent",MyNewEvent.class);
-&lt;/pre&gt;
+</pre>

@@ 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.
 [[Image:ReadCycle.png|thumb|400px]]
@@ Line 23: / Line 31: @@
 Furthermore, you can query the data in your esper statements.  For example, you can ask for all tags where the speed of the tag is greater than 4 m/s like this:
-<pre>
+&lt;pre&gt;
-Select * from ReadCycle[select * from tags(cast(speed?,Integer) > 4)]
+Select * from ReadCycle[select * from tags(cast(speed?,Integer) &gt; 4)]
-</pre>
+&lt;/pre&gt;
 ==Extending DatacontainerEvent==
 You would extend the DatacontainerEvent when the tag you are using in your RFID system is not an EPC Gen1 or Gen2 tag.  For example, if you are using active tags which do not follow the EPC Gen2 specification, then you will want to make up a new Class that represents the kind of tags you are using.
 ==Adding new Event Types in Esper==
 If you need to query the new event types that you created by extending the other classes, you will need to add those event types to Esper with code like this:
-<pre>
+&lt;pre&gt;
-esperService.getProvider().getEPAdministrator().getConfiguration.addEventType("MyNewEvent",MyNewEvent.class);
+esperService.getProvider().getEPAdministrator().getConfiguration.addEventType(&quot;MyNewEvent&quot;,MyNewEvent.class);
-</pre>
+&lt;/pre&gt;

← Older revision		Revision as of 19:21, 14 October 2009
Line 18:		Line 18:
	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=		=Extending the Hierarchy=
		+	The current hierarchy is flexible and can be extended to meet the various of different kinds of applications. The two places that extensions are forseen are TagReadEvent and DatacontainerEvent
		+	==Extending TagReadEvent==
		+	You might want to extend TagReadEvent if, for example, you are interested in data about a tag that is collected when the tag is read. For example, suppose the reader you are working with can give you the speed the tag is moving. The speed is not information that is stored on the tag, so it should go in The TagReadEvent. You can extend the TagReadEvent object to include a setSpeed() and getSpeed() methods. Now when you collect the data from the RFID reader in the Sensor Layer, you can store the speed data in your new TagReadEvent class.
		+
		+	Furthermore, you can query the data in your esper statements. For example, you can ask for all tags where the speed of the tag is greater than 4 m/s like this:
		+	<pre>
		+	Select * from ReadCycle[select * from tags(cast(speed?,Integer) > 4)]
		+	</pre>
		+	==Extending DatacontainerEvent==
		+	You would extend the DatacontainerEvent when the tag you are using in your RFID system is not an EPC Gen1 or Gen2 tag. For example, if you are using active tags which do not follow the EPC Gen2 specification, then you will want to make up a new Class that represents the kind of tags you are using.
		+	==Adding new Event Types in Esper==
		+	If you need to query the new event types that you created by extending the other classes, you will need to add those event types to Esper with code like this:
		+	<pre>
		+	esperService.getProvider().getEPAdministrator().getConfiguration.addEventType("MyNewEvent",MyNewEvent.class);
		+	</pre>

@@ 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.
 [[Image:ReadCycle.png|thumb|400px]]
-=ReadCycle=
+=Built-in Hierarchy=
 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.
-=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.
-=EpcGeneration1Event=
+==EpcGeneration1Event==
 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.

← Older revision		Revision as of 18:39, 14 October 2009
Line 14:		Line 14:

	=EpcGeneration2Event=		=EpcGeneration2Event=
		+	The EPCGeneration2Event extends the EPCGeneration1Event and represents the information read from an EPC Gen2 tag.

← Older revision		Revision as of 18:38, 14 October 2009
Line 11:		Line 11:

	=EpcGeneration1Event=		=EpcGeneration1Event=
		+	The EPCGeneration1Event represents the information read from an EPC Gen1 tag.
		+
	=EpcGeneration2Event=		=EpcGeneration2Event=