Skip Headers

Oracle® Sensor Edge Server Guide 10g Release 3 (10.1.3) B25142-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# Glossary

antenna

Each tag has at least one antenna. On the other side of the communication link, the reader must also have an antenna. Some readers can drive multiple antennae at the same time. Depending on the protocol, frequency and application, these antennae vary from thin strips of metal laid across a surface, to a portal doorway antenna that is meters tall

chip

A silicon chip, with embedded memory, is used in a tag. The chip implements the wireless protocol and access functions to its embedded memory. Note that in Active Tags, this is not a single chip but an entire board. See tag.

device

An edge device is an end point of a sensor- based architecture, such as a Radio-Frequency Identification (RFID) reader, a dry contact, an laser diode, carousel, scale, robotic picker, or indication devices such as light sticks or message boards. Sensors are hardware or software end points that make observations of certain changes in state. While this is usually a physical change, such as a laser diode detecting that something has blocked the line of its beam, it can also a software observation of a change occurring within software, such as when a monitor daemon running on an edge controller exits. Sensors also observe defects in software. A device is an instance of a driver.

event

An event is a message that is sent from either a sensor device or an application that signals that a state has changed. The Sensor Edge Server, which receives the data from these sensor devices or applications, normalizes the contents of these event messages by putting them in a common data format and then applies filters to strip them of extraneous information or unwanted events.

Oracle Sensor Edge Server

The server that resides between all of the readers and the application middle tier. It is responsible for interfacing with all of the readers and sending normalized data back to the application server.

Radio Frequency Identification (RFID)

RFID is the use of small transponders with embedded Electronic Serial Numbers (ESNs) or memory, which transmit identifiers across one or more frequencies.

reader

A reader reads from, and writes to, the tags to which it is connected. Readers usually have serial interfaces used to communicate with a host computer. There is no widely-accepted standard for this protocol. The process of retrieving data stored on an RFID tag by sending radio waves to the tag and then converting the waves the tag sends back into data is known as a read.

reader field

The area of coverage for a reader. If tags are outside of a reader field, then they cananot receive radio waves and cannot be read.

Real Time Location System (RTLS)

A technology that uses radio-frequency to produce real-time location information for tagged items.

tag

(Also known as an RFID tag. ) A single unit that contains a chip, one or more antennae, and a power source. If it is battery-driven or from a external source, the tag is an Active Tag. If the power source is inductive-based (which means that it relies on photoelectric effect to generate power from remotely generated radio waves), the tag is a Passive Tag. A tag containing data that cannot be changed is a read-only tag. See chip.

Transport Library

A set of classes that abstracts a communication channel, such serial port or TCP/IP. The Transport Library allows the addition of third-party plug-ins.

transports.xml

The file located in the `edgeHome/config` directory which tells the Transport Library which transports are available. For example:

    <transports> <transport name="com" type="stream" class="oracle.edge.tools.io.SerialConnection"> <params> <param name='port' value='com1' /> <param name='driver' value='com.sun.comm.Win32Driver'/> </params> </transport>
    <transport name="tcp" type="stream" class="oracle.edge.tools.io.TcpConnection" />
    <transport name="file" type="stream" class="oracle.edge.tools.io.FileConnection" />
    <transport name="stdout" type="stream" class="oracle.edge.tools.io.StdoutConnection" />
    <transport name="http" type="stream" class="oracle.edge.tools.io.HttpConnection" > <params> <param name='proxyServer' value='www-proxy.us.oracle.com' /> <param name='proxyPort' value='80'/> </params> </transport>
    </transports>

Each `<transport>` element defines a new transport type. For each `<transport>` tag you must define name (a unique name for this transport, which is used in the URI) and class, which specifies which class to load. This class must implement the `oracle.edge.tools.io.Connection` interface.

You can also specify default parameters for transports using the `<param>` tag.