WO2008115784A2 - Rfid reader enclosure and man-o-war rfid reader system - Google Patents

Abstract

An apparatus including an enclosure for an RFID reader to be affixed to a storage container; an RFID reader that scans a first storage container using a first antenna and a second storage container using a second antenna; and a networked system of RFID apparatuses including a primary RFID apparatus and secondary RFID apparatuses that are controlled by the primary RFID apparatus.

Description

RFID READER ENCLOSURE AND MAN-O-WAR RFID READER SYSTEM

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is a continuation-in-part of U.S. Patent Appln. No. 11/687,272 filed March 16, 2007.

FIELD OF THE INVENTION

[0003] The present invention relates to an RFID reader apparatus, system, and method.

[0004] BACKGROUND OF THE INVENTION

[0005] An RFK) reading system has been developed which can, for example, read RFK) tags stored within a cabinet, a refrigerator, a room, etc. Based on the tags read, the system can determine inventory information. One example of such a system is Dearing, et al.'s US 2002/0183882 Al from Promega Corporation.

[0006] SUMMARY OF THE INVENTION

[0007] In one aspect, the present invention relates to an apparatus comprising: (a) an enclosure; and (b) an RFID reader disposed in the enclosure, wherein the enclosure is configured to be mounted on an exterior surface of a storage container, wherein the RFK) reader is configured to perform RFID reading for an area inside the storage container using an RFID antenna external to the enclosure, wherein the RFID antenna is disposed in the storage container, wherein the enclosure has an opening on a side of the enclosure, and wherein an electrical connection between the RFK) reader and the RFID antenna extends through the opening of the enclosure in such a manner that the electrical connection is not externally accessible when the enclosure is mounted on the exterior surface of the storage container. Preferably, the apparatus further comprises a human-machine interface including a display screen. Preferably, the apparatus further comprises a controller that is configured to (a) send an instruction to the RFlD reader to perform RFID reading, (b) receive a RFID scanning result from the RFID reader, and (c) send information in response to the RFID scanning result to a database system via a network connection. Preferably, the RFID antenna is disposed within a wall of the storage container but it is not required that it be so disposed. Preferably, the storage container is a cabinet. Preferably, the cabinet is a refrigerated cabinet. A human-machine interface for the apparatus may use a display provided separately from the enclosure. Preferably, the opening of the enclosure communicates with an opening on the exterior surface of the storage container when the enclosure is mounted on the exterior surface of the storage container.

[0008] In another aspect, the present invention relates to an apparatus comprising: an RFID reader configured (a) to perform RFID reading for an area within a first storage container using a first antenna and (b) to perform RFlD reading for an area within a second storage container using a second antenna. Preferably, the apparatus is connected to the first storage container and the second storage container. Preferably, the apparatus is disposed between the first storage container and the second storage container. Preferably, the apparatus is connected to the first storage container and the second storage container so that an electrical connection between the RFID reader and the first antenna is not externally exposed and an electrical connection between the RFID reader and the second antenna is not externally exposed. Preferably, wherein the first storage container is a cabinet and the second storage container is a cabinet, which cabinets may be refrigerated or ambient, for example. [0009] In yet another aspect, the present invention relates to a system comprising three of the aforementioned apparatuses, each scanning a respective one of three pairs of cabinets. [0010] In a still further aspect, the present invention relates to a method comprising performing RFlD reading for an area within a first storage container and an area within a second storage container using an RFID reader connected both to a first antenna and a second antenna, the first antenna being used for performing reading for the area within the first storage container and the second antenna being used for performing reading for the area within the second storage container.

- ? - [0011] In yet another aspect, the present invention relates to a system comprising: (1) a first apparatus comprising a first RFID reader configured to perform RFID reading using a first antenna; and (2) a second apparatus comprising (a) a second RFID reader configured to perform RFID reading using a second antenna, and (b) a controller configured to (i) control the first RFID reader and the second RFID reader and (ii) communicate via a network connection with an inventory management system. Preferably, the first apparatus and the second apparatus are connected via a local area network, and the second apparatus further comprises a network connection between the second RFID reader and the controller. Preferably, the controller comprises a user interface for controlling the first RFID reader and the second RFID reader. Preferably, the controller is configured to control the first RFID reader to perform plural RFID scans, to obtain a first RFID scanning result in accordance with the plural RFID scans by the first RFID reader, to control the second RFID reader to perform plural RFID scans, to obtain a second RFID scanning result in accordance with the plural scans by the second RFID reader, and to communicate with the inventory management system in accordance with the first RFID scanning result and the second RFID scanning result. Preferably, the first RFID scanning is based on a difference between plural RFID scans. [0012] In a still further aspect, the present invention relates to means for attaching an RFID reader to a refrigerator so that wiring between the RFID reader and an RFID antenna in the refrigerator is not externally exposed. [0013] Yet another aspect of the present invention is a system comprising: (1) a master RFID reading apparatus comprising an RFID reader and (2) one or more secondary RFID reading apparatuses each comprising a respective RFID reader, wherein the master RFID reading apparatus further comprises control means for controlling (a) the RFID reader of the master RFID reading apparatus and (b) via networking between the master RFID reading apparatus and the one or more secondary RFID reading apparatuses, the RFID reader of each of the one or more secondary RFID reading apparatuses. Preferably, the master RFID reading apparatus uses the RFID reader to perform RFID scanning of a storage container, and the one or more secondary RFID reading apparatuses use their respective RFID readers to perform RFID scanning of a respective plurality of other storage containers. [0014] These and other objects, aspects, advantages and features of the present invention will become more apparent from the following detailed description of the presently preferred embodiments taken in conjunction with the accompanying drawings.

[0015] BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG. 1 is a perspective view showing an embodiment of the present invention, an

RFID apparatus which is mounted on a storage container such as a refrigerator;

[0017] FIG. 2 is a schematic diagram showing the interconnection of parts of the RFID apparatus according to an embodiment of the present invention; [0018] FIG. 3 is a cross-sectional view showing the mounting of an RFID antenna in a wall of the storage container;

[0019] FIG. 4 is a perspective view showing the front and top sides of an enclosure of the

RFID apparatus according to an embodiment of the present invention;

[0020] FIG. 5 is a perspective view showing the rear and top sides of the enclosure of the RFID apparatus according to an embodiment of the present invention;

[0021] FIG. 6 is a perspective view showing the bottom side of the enclosure of the RFID apparatus according to an embodiment of the present invention;

[0022] FIG. 7 is a perspective view showing a top side of the storage container;

[0023] FIG. 8 is a perspective view from front to back of the enclosure, with the front side of the enclosure removed;

[0024] FIG. 9 is a schematic diagram showing a preferred circuit arrangement for the RFID apparatus according to an embodiment of the present invention;

[0025] FIG. 10 is a schematic diagram showing a system of three RFID scanning apparatuses, one of which has a controller; [0026] FIG. 11 is a view of a preferred network interface for the enclosure of an embodiment according to the present invention;

[0027] FIG. 12 is a side view showing a system of three RFID scanning towers, two of which are slaves and one of which is a master; [0028] FIG. 13 is a perspective view showing a human-machine interface, called the

"8-ball", for use with an embodiment according to the present invention;

[0029] FIG. 14 is a rear view of the 8-ball human-machine interface of FIG. 13;

[0030] FIG. 15 is a schematic view showing a multi-antenna RFID apparatus according to the present invention for scanning two shelves in a museum to check for tagged objects or artifacts;

[0031] FIG. 16 is a flowchart showing operation of the software of the apparatus where a human-machine interface is available, in a normal mode;

[0032] FIG. 17 is a flowchart showing operation of the software of the apparatus where a human-machine interface is available, but the normal mode is bypassed;

[0033] FIG. 18 is a flowchart showing operation of the software of the apparatus in an apparatus where no human-machine interface is available;

[0034] FIG. 19 is a perspective view showing the front of an RFID apparatus of another embodiment of the present invention, with the front panel removed; [0035] FIG. 20 is a perspective view showing the back of the RFID apparatus of that embodiment;

[0036] FIG. 21 is a perspective view showing the front of the RFID apparatus of that embodiment with the front panel present;

[0037] FIG. 22 is a schematic diagram showing another preferred circuit arrangement for the RFID apparatus according to an embodiment of the present invention; and

[0038] FIG. 23 is a schematic view showing the front panel of an enclosure of an embodiment of the present invention, with a key lock.

[0039] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0040] Fig. 1 shows an embodiment of the present invention. In that figure, reference numeral 100 denotes an RFID apparatus for performing RFID reading; reference numeral 101 denotes an enclosure of the apparatus 100; reference numeral 200 identifies a storage container; reference numeral 201 indicates a door of the storage container 200 that can open and close; and reference numeral 202 indicates the interior of the storage container 200, which is an area to be RFID scanned to determine the presence of any RFID tag or tags therein. [0041] As will be discussed hereinbelow in more detail, preferably, the apparatus further includes one or more of an ethernet connection (used for, e.g., TCP/IP communication over a network), a serial connection, an IEEE1394 connection, a USB connection, and a telephone connection. The foregoing can be used to send an RFID scanning result to a remote backend inventory management system (e.g., database, ERP system, or financial packages such as Microsoft Dynamics or Quickbooks), or to allow a plurality of the apparatuses to communicate with each other.

[0042] The storage container

[0043] The storage container may be, for example, a cabinet, ambient cabinet (i.e., room temperature cabinet), refrigerated cabinet (e.g., conventional refrigerator or freezer), etc.

[0044] The RFID apparatus

[0045] We will now describe RFID apparatus 100 in more detail. Preferably, apparatus 100 includes a modular enclosure 101 that can be mounted (i.e., is mountable) on storage container 200. Enclosure 101 preferably contains at least an RFID reader. [0046] Enclosure 101 may be mounted on storage container 200 in a variety of ways. For example, enclosure 101 may be mounted horizontally (e.g., on a side surface of storage container 200) or vertically (e.g., on a top or bottom of storage container 200). Preferably, enclosure 101 has corner holes through which enclosure 101 can be bolted to an exterior surface of storage container 200 (e.g., freezer, refrigerator, cabinet, etc.). Alternatively, magnets could be used. Preferably, enclosure 101 is securely mounted so it will not easily move around or fall off.

[0047] An advantage of the enclosure design is that it is a portable, retrofitable modular enclosure that can be connected by a field engineer to any type of storage container, cabinet, shelf, or the like in the field. For example, the engineer could install an RFK) antenna in the wall of a standard, conventional refrigerator and could bolt the enclosure to an exterior surface of the refrigerator.

[0048] Another advantage of the foregoing is that since the RFID reader with its circuitry for driving and controlling the RFID antenna preferably is all contained within the enclosure, rather than being disposed, for example, in the storage cabinet itself, it should be much cheaper and easier to access the RFID reader for servicing, upgrade, and the like. [0049] Fig. 2 depicts apparatus 100 in more detail. In this figure and all other figures, reference numerals that are the same as those in other figures have the same meaning, unless otherwise specified. In Fig. 2, reference numeral 102 denotes the RFID reader; reference numeral 103 denotes a controller (or controller circuit); reference numeral 104 denotes an ethernet hub; reference numeral 106 is an RFID antenna; reference numeral 107 is an electrical connection between RFID reader 102 and RFID antenna 106; reference numeral 110 is an I/O block; and reference numeral 1011 is an access port, opening, or hole in enclosure 101. [0050] The depicted connection between ethernet hub 104 and RFID reader 102 is an ethernet connection, and the connection between ethernet hub 104 and controller 103 also is an ethernet connection, preferably. In other words, in the preferred embodiment, controller 103 communicates with RFID reader 102 (via ethernet hub 104) using an ethernet network connection. Thereby, controller 103 can control, for example, the timing of initiation of an RFID scan by RFID reader 102 by sending a command across the connection, and, through the connection, controller 103 can, for example, receive the results of the scan from RFID reader 102. However, the invention is not limited to use of ethernet. Other communication techniques could instead be used (e.g., USB). [0051] As mentioned above, preferably the enclosure 101 contains at least RFID reader 102; optionally, controller 103, ethernet hub 104, and I/O block 110 may also be included along with RFK) reader 102, or they may be omitted. Preferably, all are included, or I/O block 110 is included with RFID reader 102 while controller 103 and ethernet hub 104 are omitted. [0052] As mentioned above, reference numeral 1011 denotes an access port, opening, or hole of enclosure 101 (e.g., an opening on the exterior surface of enclosure 101) through which electrical connection (e.g., wire or wiring) 107 passes to connect RFID reader 102 and an RFID antenna 106. By means of this electrical connection, RFID reader 102 can drive and control RFID antenna 106 to send and receive signals. Preferably, RFID antenna 106 is external to enclosure 101.

[0053] While we have described using one RFID antenna 106 for a storage container 200, the invention is not so limited. Instead, multiple RFID antennae 106 could be used for one storage container 200. Depending upon the type of products stored within the storage container 200, it may be preferable to have multiple RFID antennae 106 to scan one storage container 200.

[0054] The I/O Block

[0055] Preferably, apparatus 110 includes an I/O block 110. Preferably, I/O block 110 is connected to ethernet hub 104 by ethernet, and controller 103 is also connected to ethernet hub 104 by ethernet, so controller 103 can send and receive signals to and from I/O block 110. Preferably, I/O block 110 has a plurality of inputs and outputs (such as digital, analog, etc.) and has a built-in two-port ethernet hub. If controller 103 and ethernet hub 104 are omitted, the ethernet hub of I/O block 110 can be used to forward commands received from an external controller 103 to RFID reader 102. I/O block 110 can connect to an authentication unit such as a passreader which reads any of a passcard, biometric information, etc. of the user, and provides the information read to controller 103. I/O block 110 can also provide temperature information to controller 103. I/O block 110 can also control a lock of storage container 200, at the direction of controller 103, to lock and unlock the door of storage container 200 to control access to the storage container 200. [0056] The RFID reader

[0057] RFID readers are commercially available and a conventional RFID reader may be used as RFID reader 102. RFID reader 102 includes (a) circuitry to drive an RFID antenna to send RF signals and (b) circuitry to process any responses received back from an RFID tag or tags, i.e., RFID reader 102 performs RFID scanning. The RFID reader that we prefer to use is capable of connecting to a plurality of RFID antennae. Preferably, RFID reader 102 also has an ethernet port providing a network connection by which it can be controlled. In particular, RFID reader 102 has a command set by which it can be controlled, and commands can be sent to RFID reader 102 via its ethernet port to instruct RFID reader 102 to, for example, perform an RFID scan using RFID antenna 106 and return a list of tags read based on signals received from an RFID tag or RFID tags.

[0058] The controller [0059] Preferably, but optionally, the apparatus 100 may include the controller 103. Controller 103 preferably is a device, circuit, or computer (such as, for example, an embedded computer) for controlling RFID reader 102. Preferably, controller 103 authenticates a user seeking access to the storage container 200, sends a signal to unlock a door of the storage container 200 in response to authentication of the user, instructs RFID reader 102 to perform a scan in response to closing of the door, and calculates a difference between an RFID scan result returned by RFID reader 102 and an earlier RFID scan result returned by RFID reader 102 to determine if any RFID tags have been removed or added. [0060] Preferably, to determine whether a user has taken from a storage container or added to the storage container any tags or tagged items, controller 103 calculates a difference (referred to as a "delta") between a first RFID scanning result obtained before the door of the storage container is opened (referred to as the "baseline" scan) and a second RFID scanning result obtained after the door of the storage container has been closed again. However, the determination is not so limited. For example, another possibility would be to perform an additional RFID inventory scan after the user's passkey is read but before the door is opened. This additional scan could be combined with the baseline scan to form a superset (i.e., containing any tags found in one or both of the baseline scan and the additional scan), to which the second RFID scanning result could be compared. An advantage of this arrangement is to aid in scanning what we call "blinking tags". A "blinking tag" is a tag which might be read during one scan but not during another, for whatever reason. For example, a blinking tag might be read during 50% of scans. By performing both a baseline scan and the additional scan, it might be possible to discover the blinking tag even if it were not read during the baseline scan.

[0061] Preferably, controller 103 communicates with RFID reader 102 via ethernet, and most preferably through an ethernet hub 104 that interconnects controller 103 and RFID reader 102 and that interconnects controller 103 and I/O Block 110. Most preferably, the controller 103, RFID reader 102, I/O Block 110, and ethernet hub 104 are all disposed inside enclosure 101. [0062] Preferably, as will be discussed below with respect to Fig. 9, controller 103 has a second ethernet controller (network interface) for connecting to a backend inventory management system through, for example, the internet. [0063] Preferably, controller 103 is a computer that uses an operating system such as

Windows CE or Linux, and that executes a computer-executable computer program stored in a computer-readable memory associated with the computer to effect all of the actions, signals, and communication discussed in this application. However, controller 103 is not so limited, and may take other forms of hardware or software as long as it supports the requirements of the system.

[0064] Preferably, controller 103 will provide a human- machine interface (i.e., user interface), and controller 103's operating system will be Windows CE 5.0. Controller 103 preferably will also have Microsoft's .NET Compact Framework version 2.0 at a minimum installed. Of course, other operating systems can be used in place of Windows CE 5.0. Preferably, those other operating systems would also support the .NET Framework. This makes the software portable so that it may run on any Windows operating system that has .NET framework installed on it.

[0065] Most preferably, controller 103 is in the form of an all-in-one HMI (human-machine interface)/Embedded PC running Microsoft Windows CE 5.0. Future units may have the HMI separate from the controller or no HMI at all, depending on the needs of the individual customer. The Windows CE image can either be provided by the vendor of apparatus, or a custom image can be created, tailed to the specific needs of a particular apparatus 100. [0066] As mentioned above, preferably a computer program executed by controller 103 provides the functionality of apparatus 100 such as RFID scanning, inventory management, communication, etc. We will refer to this program as the Application Program. [0067] Another related application developed for the apparatus 100 is simply referred to as the bootstrapper, which handles the updating of the Application Program, and its related files.

[0068] The Application Program

[0069] We will now describe the Application Program in more detail.

[0070] Preferably, the Application Program is written on top of the Microsoft .NET Compact Framework version 2.0, using industry standard best practices. Development using the Compact Framework allows the Application Program to be redeployed on any Windows CE 5.0 device that has the compact framework installed. This includes devices that have a different underlying architecture such as ARM 4, x86 and MIPS. This level of flexibility allows the manufacturer of apparatus 100 to select or change controller 103 depending on customer needs, new technology offerings, and lower prices. In addition to moving from device to device, the Compact Framework will allow a smooth transition to newer versions of Windows CE, such as the new version 6.0. As an added benefit, the majority of the

Application Program can be easily recompiled to run under the full version of the Microsoft .NET Framework, and because of this, run on standard x86 hardware running Windows operating systems, such as Microsoft Windows XP, or Embedded Windows XP. This provides two key benefits, the first being additional flexibility for customers, the second being excellent opportunities for code reuse.

[0071] Windows CE supports multi-threaded applications, and the Application Program takes advantage of this to provide a robust and interactive experience to the user of the apparatus 100. The Application Program can, for example, (a) handle communications between apparatus 100 and peripherals, (b) handle communications between apparatus 100 and backend system 1057, (c) display a user interface to the user, and (d) accept input from the user. This is considered a best practice, and will be what a user/customer expects. [0072] Turning to the architecture of the Application Program, preferably the program is separated into a main executable, which contains the user interface screens, compiled for the Compact Framework, and several satellite assemblies (e.g., class libraries in the form of compiled DLL files). Great care was taken in the architecture of the Application Program with regard to the separation of functionality between components, which allows for code re-use in the Application Program itself, as well as in other related applications, ease of maintainability, and ease of upgradeability. [0073] One of the key features in the separation of components is the use of an Object Orientated design using Interfaces and Abstract Base Classes to build a foundation upon which the rest of the application can be built. The use of Interfaces allows for the main application logic of the Application Program to remain isolated from changes in hardware (RFID Readers, RFID Transponders, I/O blocks), as well as other pieces of software, such as communications and the data store. Building upon the interfaces are Abstract Base classes which implement the signatures of the various interfaces to provide shared functionality. In the event that a situation arises where the Abstract class is too specific, we have the interface to fall back on. [0074] An example of this design is the implementation of the logic in the Application Program to interface with the RFID reader 102. The preferred model of RFID reader 102 that we use is the Magellan MARS reader (of course, we mention this model by way of example and not of limitation). An Interface named IDevice was created, which all device logic must implement. An abstract base class called DeviceBase implements IDevice and provides common functionality seen in the majority of devices we will be using. Another Interface named IScanner provides the starting point for all RFID scanners, and again, the abstract class ScannerBase provides base functionality. Finally, the concrete class MarsReader was implemented to provide a specific implementation that conforms to the signatures of the interfaces, but in a way that allows for interaction with the Mars Reader. The main application logic in the Application Program does not have to be changed at all once the interfaces (which are used for all devices and all scanners) are defined. [0075] As a result, is that it is extremely easy to add new pieces of hardware to the apparatus 100 (e.g., to use a different model of RFID reader 102). To do so, one can simply create a new class library that implements the required interfaces, compile, and deploy. This is a major advancement over conventional systems, where new hardware would most likely result in a complete re-write of the application.

[0076] As with the current controller and software, the Application Program supports remote updates of configuration parameters, as well as updates to the application itself. This is handled by the bootstrapper, which runs in place of the Application Program, so that the Application Program files can be updated (generally, one cannot update files that are in use). In addition to updates related to the Application Program, new device drivers, OS hot fixes, and new advertisements can be downloaded to the apparatus 100 (e.g., via a network connection).

[0077] Preferably, the data store for the Application Program is in the form of a Microsoft SQL 2005 Compact Edition database, the latest version of the mobile line of databases offered by Microsoft. The database will store configuration information, transactions, and logging information. The latest version of SQL mobile offers features usually found only in desktop and server versions of database, key among those being atomic transactions. An atomic transaction guarantees that a group of data written to the database is either completely written, or none of it is written. This helps maintain consistency within the database, and makes the Application Program that much more robust. While SQL2005 is preferred, other data stores could be used. For example, a flat file could be used, or XML, among others. [0078] Communication between the Application Program and peripherals associated with apparatus 100 is done over USB, Serial, or Ethernet, for example. Given the USB interface, there is the option to hook up non-standard communication busses (such as RS-485) through the use of a USB converter. Some of the devices that hook up via USB actually emulate an network interface card (NIC), or a virtual COM port. This is made possible due to the open, standards based approach taken with Windows CE. Peripherals can be configured manually thru editing the configuration parameters via the HMI, or a semi- automated method can be used. In the semi-automated method, a user can instruct the Application Program to scan for new devices. The Application Program will report back devices that it has discovered but are currently not configured. The user can then select the device to associate and configure it with the Application Program. Peripherals can be identified by the COM port they are plugged into, their USB ID, or their Ethernet MAC address.

[0079] The human-machine (user) interface

[0080] As mentioned above, controller 103 may also provide a human-machine interface (HMI) (or user interface) to allow a user to interact with or control the apparatus 100. (Where controller 103 does support the HMI interface, the controller 103 and HMI may be integrated together, in which case references herein to HMI or controller should be considered the same device.) For example, the controller 103 could drive a display provided on the enclosure to display the user interface. Such a display could be mounted, for example, on a front surface of the enclosure 101, as shown by reference numeral 1052 in Fig. 12. The display 1052 could be an LCD screen. Preferably, the HMI comprises, as the display 1052, a VGA 5.7" touch screen mounted to the front removable panel. The display 1052 could show the status of the apparatus. Controller 103 could also cause the display to display diagnostic information to allow an engineer to check the status of the machine or otherwise troubleshoot it.

[0081] Localization [0082] The Application Program will support a variety of user personalization including but not limited to, localization (multiple language support), and target advertisements. [0083] As for localization, each user preferably will be able to choose a default language they wish to use when interacting with the UI portion of the Application Program; controller 103 could select a language for display based on the identity of the user. For example, controller 103 might display the user interface in Spanish if controller 103 concluded that such was the user's preferred language.

[0084] This will increase the number of international markets apparatus 100 will be able to be deployed to, as well as meet customer and possibly government requirements. [0085] Targeted and general advertising

[0086] The Application Program will also support targeted advertising, to allow for sellers of apparatus 100 to configure and display advertisements to users of apparatus 100 based on their past and current purchases, and any ongoing sales promotions. For example, display 1052 could provide marketing advertisements targeted at a user of the apparatus, e.g., if it were recognized (e.g., by controller 103) that a user had purchased an item before, then controller 103 might control display 1052 to display an advertisement offering a sale price on that item to encourage the user to purchase the item again. [0087] Targeted advertising may be, but is not limited to, a small area on the screen when the user is selecting which unit (i.e., storage container) they are trying to gain access to, a full screen advertisement after they select which unit they are going into, or a popup style advertisement that appears when the user first presents their pass. [0088] In more detail, controller 103 preferably also shall have the ability to run general advertising in addition to targeted advertising. General advertising will run while the unit is sitting not doing anything that requires a user present.

[0089] Users will be able to select an advertisement, and request more information. This will be handled by the Application Program sending a transaction back to the backend system 1057 in accordance with the selection. The backend system 1057 will forward the request on to the appropriate sales staff.

[0090] "Headless" configuration

[0091] It is not required that the HMI be included. Instead, the apparatus 100 could be "headless", i.e., it would not have a display of its own. Instead, the apparatus could be configured so that it could be controlled remotely, e.g., across an ethernet, USB, or serial connection.

[0092] Externally-provided HMI

[0093] It is not required that the HMI function or controller 103 be integrally provided in enclosure 101. In an alternative construction shown in Figs. 13 and 14, controller 103 and the HMI function thereof have been transferred out of enclosure 101 into an external enclosure 1054. That enclosure is a pumpkin- shaped enclosure that we call an "8-ball", which includes a display screen 1052 and ethernet ports 1055 and 1056. By transferring controller 103 with its HMI, along with a pass reader for authenticating the user, to enclosure 1054, enclosure 101 can be made smaller. Enclosure 1054 can be placed anywhere in the vicinity of the units (i.e., storage container or containers) it is controlling. Functionality is the same in all respects. To connect the 8-ball enclosure 1054, an Ethernet cable is used to connect from ethernet port 1055 to one of the ethernet ports on enclosure 101. Ethernet port 1056 is used as an external network connection for reporting to the back end inventory management systems, depicted by reference numeral 1057 in Fig. 14.

[0094] Communications with backend system

[0095] Preferably, communication between controller 103 and the backend system 1057 is through an ethernet interface using via standard web services provided on TCP port 80 or secure web services over TCP port 443 (SSL). Such communication includes but is not limited to software upgrades, diagnostic information, inventory transactions, and advertising. [0096] Preferably, communications are initiated from apparatus 100 only, e.g., from apparatus 100 to backend system 1057. For example, apparatus 100 could send inventory information via a network connection to backend system 1057. An advantage of this is to provide a firewall-friendly and network administrator-friendly communication mechanism. In more detail, generally, whereas outbound communication is acceptable (for a firewall), unsolicited inbound connections are considered taboo and could limit placement of the apparatus 100. However, there are times where a persistent connection between apparatus 100 and backend system 1057, and possibly multiple apparatuses 100 at different locations, would be desirable. In order to accomplish this, apparatus 100 and backend system 1057 will implement an HTTP reflector that allows for a persistent, firewall-friendly connection to be established. An example of this type of connection can be seen in online meeting service such as WebEx, and Microsoft Live Communications Server. In fact, Microsoft Live Communications Server is one option we have for implementing this type of functionality. [0097] Dynamically-configured networking

[0098] Preferably, the system's software shall support the dynamic discovery of devices as the number of connected secondary apparatuses 100 (as discussed below) increases. The controller 103 shall (either by its operating system or by the Application Program) implement a DHCP server to handle IP addressing of devices (e.g., dynamic addressing) as they are connected. In other words, controller 103 will provide IP addresses to the secondary apparatuses 100 as they are connected. Controller 103 will then attempt to establish connections to the new devices (i.e., apparatuses 100). The devices will be initialized and recognized by the controller 103 for use by attempting to send a given command set to see how the remote device responds. If the device accepts these commands, it will be initialized and installed for controller 103 to control. If the device does not accept these commands, controller 103 will move on to a next set of commands and repeat this process.

[0099] Watchdog feature [0100] Preferably, controller 103 shall also have a WatchDog timer available. This feature will allow the device to attempt to automatically recover if the software hangs.

[0101] The RFID antenna or antennae

[0102] Preferably, RFID antenna 106 is external to the enclosure 101. For example, RFID antenna 106 could be disposed in a wall of storage container 200. Fig. 3 depicts such an arrangement. In more detail, that figure shows two RFID antennae 106, each being located in a wall 203 of a respective one of a pair of storage containers 200 that sandwich apparatus 100.

[0103] That figure also shows another feature of the present invention. In particular, the invention is not limited to having one RFID antenna 106 connected to RFID reader 102.

Instead, RFID reader 102 may be attached to plural RFID antennae 106. The plural antennae may be used for reading areas within separate respective storage cabinets. For example, one antenna might be used to read an area within a first storage cabinet, while a second antenna might be used to read an area within a second storage cabinet. Again, such is shown in Fig. 3 which depicts a tower unit comprising top and bottom storage containers 200 sandwiching apparatus 100 and each having an RFlD antenna 106 connected to the same RFID reader 102 of apparatus 100.

[0104] Thereby, it is possible for a single RFID reader to be used for plural storage cabinets, as compared with conventional systems where each storage cabinet needs to have its own RFID reader including circuitry for controlling and driving an RFlD antenna. Because the present invention's circuitry can be used to scan plural storage cabinets, we think its utilization will be improved as compared to the conventional systems. [0105] Our idea of having one RFID reader using plural RFID antennae for plural storage cabinets is the genesis of the name "RFID man-of-war", given the vision of connections between the RFID reader and many respective plural antennae. If exactly eight antennae were provided, then the system might be referred to as an "RFlD octopus". [0106] When RFlD antenna 106 is a 13.56 MHz antenna, we prefer to provide a false back wall in the storage container 200, in which wall the antenna is integrally provided. When RFID antenna 106 is a 2.46 GHz antenna and storage container 200 is a refrigerator, we prefer to attach the antenna to the interior surface of the exterior metal chassis of the refrigerator. In that case, the antenna is disposed between the metal exterior wall of the refrigerator and the separate plastic wall of the interior of the refrigerator. [0107] Instead of being on or in a wall of the storage container 200, RFID antenna 106 could also be inside the storage container. For example, RFlD antenna 106 could be located on or within a shelf inside storage container 200. The location of RFID antenna 106 is not limited to any of the foregoing positions.

[0108] The enclosure and its mounting on the storage container [0109] Turning to Figs. 4 through 8, we will now describe a preferred embodiment of apparatus 100 and its enclosure 101 in more detail. In those figures, reference numeral 1001 denotes a front side of enclosure 101; 1002 denotes four screws for affixing front side 1001 to enclosure 101; 1003 denotes a top side of enclosure 101; 1004 denotes a back side of enclosure 101; 1005 denotes a ventilation system; 1006 denotes a power connector; 1007 denotes a power outlet; 1008 denotes an ethernet port; 1009 denotes a piano-style hinge that allows for the back side 1004 of enclosure 101 to fold down to grant access to the interior of enclosure 101 ; 1010 denote holes in enclosure 101 for use with bolts or screws; 1011 denote access ports (e.g., holes or openings) in enclosure 101, which can be used for wiring; 1012 denotes a Z bracket that allows for a tray with electronics to be slid in and out — it holds the tray in place as well; 1013 denote holes in storage container 200, which can be used for wiring; and 1014 denote holes in storage container 200, for use with bolts or screws. [0110] In more detail, as explained above, enclosure 101 is designed to hold the electronic components of apparatus 100. Access ports 1011 (i.e., openings or holes) are located on, for example, the bottom (exterior) side of enclosure 101 and/or the top (exterior) side of enclosure 101.

[0111] Preferably, two access ports or openings 1011 are located at the rear end of the bottom side, as shown in Fig. 6. These openings are used to run wiring from enclosure 101 into a storage container 200 located below apparatus 100. Such wiring may provide, for example, an electrical connection between RFK) reader 102 and RFID antenna 106 of this lower storage container (for the electrical connection, see item 107, as discussed above). [0112] Two additional access ports 1011 optionally may be located at the rear end of the top side 1001. These openings are used to run wiring from enclosure 101 to a storage container 200 located above apparatus 100. Such wiring may provide, for example, an electrical connection between RFID reader 102 and an RFID antenna 106 of this upper storage container (for the electrical connection, see item 107, discussed above). [0113] These wires (that run through access ports 1011) may include but are not limited to antenna cables (such as, for example, item 107 as discussed above), power cables, and wiring for unit security. These wires then go directly into a storage container above or below the apparatus through holes 1013 in storage container 200 (shown in Fig. 7); this prevents the wires from being tampered with.

[0114] In other words, an advantage of the present invention is that, as discussed above, the enclosure is configured to defend the apparatus from attack, e.g., to prevent a person with wire snippers from cutting an electrical connection such as a wire connecting the RFID reader and the RFK) antenna. To reiterate, preferably, the enclosure has an access port (e.g., opening) on a side of the enclosure that faces an exterior surface of the storage container. A wire from the RFID reader to the RFID antenna can pass through the opening and into the storage container through a corresponding opening in the storage container. Thus, when the enclosure is mounted on the exterior surface of the storage container, the wire is protected from attack because it is not externally accessible or exposed. Malcontents are prevented from tampering with or disabling the device — wiring can be made to be not externally accessible. [0115] Enclosure 101 is also designed to be portable so that it can be easily attached and removed from on top of storage container 200. This is accomplished by attaching screws in the enclosure 101 into the storage container 200 above and/or below. For example, screws could be used in conjunction with holes 1010 in enclosure 101, as shown in Fig. 6, and holes 1014 in enclosure 200, as shown in Fig. 7, to fixedly mount enclosure 101 to storage container 200. [0116] In more detail, to connect the apparatus 100 to the storage container 200, a bolt would be inserted from inside the enclosure 101 through holes 1010 and 1014 and be screwed into the storage container 200. The holes 1010 in the enclosure 101 will be slightly larger than the bolt so a washer will have to be placed on the bolt inside the enclosure 101. A wing nut will then be used to hold the storage container 200 and apparatus 100 together. As a result, the wiring holes 1011 will align with the wiring holes 1013 in the storage container 200. This allows for the wires to be secured inside the unit and not accessible on the outside. [0117] A storage container 200 (e.g., a cabinet) can also be attached to the top of the apparatus 100 using the exact same process. [0118] Screws or bolts do not have to be the only option; a magnetic locking mechanism using magnets, or some other locking mechanism could be used.

[0119] Combining two storage containers and one apparatus into a tower unit

[0120] Where two storage containers 200 (be they, for example, cabinets, freezers, refrigerators, cryo storage, etc.) are connected to one apparatus 100 with the apparatus 100 sandwiched in between, we refer to this combination as a tower unit. This tower will share all the electronic components thus reducing price and maintaining modularity. Fig. 12 shows three tower units 300. The first tower unit 300 comprises a storage container 200 labeled Al attached to the top of the apparatus 100 labeled A, with another storage container 200 labeled A2 attached to the bottom of the apparatus 100. The second tower unit 300 comprises a storage container 200 labeled Bl attached to the top of the apparatus 100 labeled B, with another storage container 200 labeled B2 attached to the bottom of the apparatus 100. The third tower unit 300 comprises a storage container 200 labeled Cl attached to the top of the apparatus 100 labeled C, with another storage container 200 labeled C2 attached to the bottom of the apparatus 100. In each of these tower units, the RFID reader 102 of the apparatus 100 can be connected to two RFID antennae, one for the top storage container 200 and one for the bottom storage container 200.

[0121] The enclosure's tray system [0122] Now we will describe a preferred arrangement within apparatus 100's enclosure 101. Inside the enclosure 101, preferably there are two trays. One tray is designed to hold the more stationary items (such as things that have wires running out the back of the apparatus) while the other holds all other components. [0123] Front side 1001 of apparatus 100 comes off when the four screws 1002 are removed in the front, as shown in Fig. 4. This provides access to the electronics.

[0124] Back side 1004 of the enclosure 101, as shown in Fig. 5, is on hinge 1009. When two screws are removed, this piece (i.e., back side 1004) folds down providing additional access. [0125] The front side 1001 and back side 1004 can be redesigned as necessary to change with hardware. This design does not affect the design of the enclosure 101's chassis, thus reducing the cost and maintaining modularity.

[0126] The trays in the apparatus 100 are on the rail mount system 1012. The trays themselves have a din rail mounted to them so that the electronics can be easily mounted. The trays are then able to slide out with the electronics on them so that the parts can be serviced. There will be quick connectors on the appropriate wires so that when a drawer is taken out, the wires are not strained. There will be slack in those wires that a quick connect cannot be used so that removal of a tray does not strain the wires. A multitude of trays can be installed in this configuration by adding the slide rails and appropriate tray to maintain the modular design. If hardware ever needs to be changed in the device, no work has to be done in the chassis itself; only the slidable electronics trays will need a redesign, thus reducing cost.

[0127] Other features of the enclosure

[0128] Back side (removable service panel) 1004 has several pieces that will be designed into it. They include but are not limited to an IPC power connector 1006, a US style power outlet 1007, at least one Ethernet coupler 1008 (as will be discussed below in more detail, preferably there are at least two Ethernet couplers, and more preferably, even more than two), and a ventilation system with 80mm fans 1005. Specifically, the US style power outlet should be interchangeable with any outlet style from around the globe. Specifically, the 80mm fans should have a low noise level (< 45dBm) as well as a low to moderate air flow rating (25-60 cfm). One fan should blow air into the enclosure 101 while the other should blow air out. The fans should be 24V. Specifically, there should be at least one Ethernet coupler to interface with a network (e.g., WAN). Nominally, there should be at least four connectors such as Ethernet couplers — one of which supplies the WAN connection while the other three are to be used to communicate to secondary apparatuses 100 when plural apparatuses 100 are networked together. Fig. 11 shows that, for example, six ethernet connectors 1051 could be provided on the back side 1004 of enclosure 101 to provide connectivity such as that discussed above. [0129] Turning to the two trays (or drawers), the left drawer will hold the RFID reader 102, the Ethernet hub 104, and a 24V power supply. The right drawer will contain an optional 24V UPS system with battery, an Ethernet based I/O block and any other hardware that may be needed. The controller 103 is mounted to the inside of the front removable panel, preferably. [0130] Now, we will describe the preferred internal wiring in apparatus 100. One feature of our new modular hardware design is a modular scalable bus for all the components to communicate across. To meet this requirement, an Ethernet bus was chosen. Connections using an Ethernet based bus are as follows starting from the controller 103, as shown in Fig. 9.

[0131] Preferably, controller 103 has at least two ethernet ports — one for internal communications (e.g., to communicate with RFID reader 102 and ethernet I/O block 110) and one (e.g., a WAN link coupler) for connection to a network such as the internet for reporting back to headquarters (e.g., to a backend inventory management system database 1057). An advantage of providing dual ethernet ports is for network segregation. This protects the end user's network (which would typically be connected to the WAN link coupler) from traffic not bound for their network (i.e., traffic between internal components such as controller 103 and reader 102) and protects the equipment (such as, for example, reader 102) from malicious access. Controller 103 should act as an intermediary that allows access from outside apparatus 100 to internal components (e.g., reader 102) as necessary. Meanwhile, the network attached to apparatus 100's WAN link coupler will not be interrupted or interfered with by apparatus 100's traffic (i.e., traffic between components such as for example, reader 102 and controller 103). Preferably, ethernet hub 104 is an 8-port Ethernet din rail mountable hub and an ethernet cable connects controller 103 to hub 104. Another Ethernet cable connects the hub 104 to the RFID scanner 102 inside the apparatus 100. Another Ethernet cable connects the hub 104 to an Ethernet-based I/O block 110. Currently, the controller 103, ethernet hub 104, and I/O block 110 are being supplied by B&R Automation. Three more Ethernet cables connect to three Ethernet couplers (see item 1051) that are mounted on the back of the apparatus 100. These can then connect to other apparatuses 100 in the nearby vicinity; in other words, plural apparatuses 100 can be networked together. We will discuss this in detail below. [0132] Before doing so, however, we will continue our description of the Fig. 9 circuit arrangement. Preferably, incoming 120/240VAC power will connect through the switched IPC connector. Inside, this power will be split. One lead will run to a set of at least two outlets (these can be customized per country the system will be placed in) while the other will lead to a power supply. The output of the power supply is 24V DC @ a minimum of 7 amperes. This output has 3 possible options: (a) the power goes directly into a master relay that provides a hard reset capability; (b) the power goes into a battery charging system similar to the design of the current system then leading to a master relay that provides a hard reset capability; and (c) the power goes into a UPS system that controls the battery, charging and error reporting in relation to power. Power out of the UPS connects to a master relay that provides a hard reset capability. [0133] The master relay has a control line that flows from the local I/O block 110. Out from the master relay, power will be moved to a distribution block. This can then be pushed out to the controller 103, I/O block 110, Ethernet hub 104, and RFID scanner 102 as the primary power consumers. Any other devices requiring power can also be supplied power in this manner. [0134] The controller 103 at present has at least two USB ports. This acts as a primary (or secondary) interface into the controller 103 in case it is malfunctioning in some way. The access control method will connect into one of these ports — it may be a passkey (operating at 125KHz), a pin key (for those that do not have an HMI/controller 103 with a touch screen), a magnetic strip reader, or a biometric reader (retina, fingerprint, DNA, etc.), for example. The other USB port will not be available externally. A USB hub can be hooked up to either port on the controller 103 to expand USB usage. A keyboard, mouse, and flash drive could then be used in the troubleshooting process or software update process. This also provides expandability for future devices to connect to the controller 103. [0135] There is one serial port on the controller 103 at present. As serial is an older technology, it is becoming harder to find and support devices that use a serial connection. However, we will provide the port as a means of connecting some external peripheral. This port can also be used as a means to interface with any legacy hardware that may want to be included.

[0136] Networking plural apparatuses together

[0137] As mentioned above, plural apparatuses 100 can be networked together. We will now describe a preferred arrangement of such a network system, with reference to Fig. 10. That figure shows three apparatuses 100 networked tegether via ethernet connections. One of the apparatuses 100 is considered to be the primary apparatus, while all other apparatuses 100 that connect to the primary apparatus 100 are secondary and connect via Ethernet. The primary apparatus 100 is one that has the controller 103 in it. Preferably, primary apparatus 100 also includes ethernet hub 104 which connects to the RFID reader 102 and controller 103 in primary apparatus 100, as well as to the RFID readers 102 in each of the two secondary apparatuses. The secondary apparatuses 100 preferably do not have a controller 103 in them. There is also no Ethernet hub 104 inside the secondary apparatuses 100, although this does not mean one cannot be included. Instead, I/O block 110 is used as an ethernet hub. In the Fig. 10 arrangement, the controller 103 controls the RFID reader 102 that is in the primary apparatus 100 in which the controller 103 is located, as well as the RFID readers 102 that are in each of the secondary apparatuses 100. Such control includes, as discussed above, generating commands to instruct the RFID reader 102 to initiate a scan, obtaining a list of tags read from the RFID reader, and determining a difference between that list and an earlier list to determine a change in inventory.

[0138] More details of controller 103

[0139] Preferably, the I/O block 110 in Fig. 9 has a two port Ethernet hub built into it. An Ethernet line coming from the primary apparatus 100 would connect into a coupler on the secondary apparatus 100 and then connect to the I/O block 110. The second I/O Ethernet port on the I/O block 110 would then be used to connect to the RFID scanner (i.e., RFID reader 102) inside the secondary apparatus.

[0140] Preferably, controller 103's software program (i.e., the Application Program) shall be a multi-threaded program allowing access to one storage container 200 connected to one apparatus 100 in a network while another storage container 200 is being scanned by its RFID reader 102. This RFID reader 102 can be in a master or secondary apparatus 100. Therefore if a user has accessed one storage container 200, and that container is being RFID scanned, another user can immediately come up to the same apparatus 100 where the controller 103 is located, present a pass to authenticate himself or herself, and then gain access to another container 200 provided that container 200 is not actively being RFID scanned at the time of access. If the user tries to gain access to any container 200 while it is being scanned, a please wait message would be displayed. [0141] The Application Program flow control

[0142] We will now provide a more detailed discussion of the preferred flow control of the Application Program's software program code with reference to the drawings. Of course, this flow control represents a preferred embodiment, and our invention is not so limited.

[0143] Fig. 16 shows operation of the apparatus 100 and its Application Program in a case where a human-machine interface (HMI) is available; Fig. 17 shows operation in a case where a HMI is available, but a user bypasses normal operation to administer the apparatus; and Fig. 18 shows operation in a case where an HMI is not available. [0144] Turning to Fig. 16 in more detail, step 4000 represents the starting point of the flow control.

[0145] At step 4001, controller 103 powers up or reboots.

[0146] At step 4002, the operating system (OS) of controller 103 is started. For example, where the OS is Windows CE, controller 103 boots into Windows CE. [0147] At step 4003, the Application Program is started. Unless otherwise specified, the remaining steps discussed represent flow control in the Application Program. The Application Program shall store an information transaction to indicate that the Application Program has begun the startup sequence. [0148] At step 4004, the Application Program starts the Hardware Watchdog Timer. The Application Program should ping the Watchdog continuously otherwise the device will reboot.

[0149] At step 4005, the Application Program shall check to see if the Application Program was properly shutdown. The Application Program shall store an error transaction, if the Application Program was not properly shutdown. The Application Program shall also clear a flag (indicating shutdown status).

[0150] At step 4006, the Application Program will check to see if a human-machine interface (HMI) is present. The Application Program shall prevent denial-of-service (DoS) attacks against the unit (by letting a user continually try to bypass the sequence). The Application Program shall provide this functionality as early in the process as possible to minimize a problem from occurring that would prevent access to the diagnostics.

[0151] If it is determined at step 4006 that an HMI (e.g., touch screen display) is available for apparatus 100, then at step 4007, the Application Program shall wait for bypass. [0152] In more detail, the Application Program shall display a screen with the prompt, "Tap screen to bypass startup sequence". This screen shall allow the user the opportunity to interrupt the startup sequence for testing, diagnostics, tech support, etc. [0153] If in step 4008 it is determined that the user has tapped the screen to bypass the startup sequence within a predetermined amount of time (e.g., less than or equal to ten seconds), then flow control passes to step 4025 in Fig. 17, as discussed below.

[0154] If, on the other hand, it is determined in step 4008 that the user does not tap the screen to bypass the startup sequence within the predetermined amount of time, then flow control passes to step 4013. [0155] At step 4013, the Application Program loads communication configuration settings from a database so that the apparatus 100 can configure itself for communication.

[0156] At step 4014, the Application Program will connect to the backend system and send all currently stored transactions (e.g., records showing that a certain user has taken a certain tag or tags from a certain storage container) that have not been sent. [0157] This step will also allow the unit to receive any updates (e.g., software updates) from the backend system. If so directed by the backend system, the Application Program will run an application update routine to update software such as the Application Program. The Application Program should reboot after the application update, and thus return to step 4000. [0158] At step 4015, the Application Program will start peripherals. In more detail, it shall initialize the RF reader 102, the transponder, and the I/O block 110. The Application Program shall connect to and initialize devices such as these based on the loaded configuration parameters. Preferably, the Application Program shall proceed as follows in this regard: (1) using reflection, create an instance of each required device library; (2) add device instance to device manager, verify that all devices successfully replied to ping command; and (3) engage locking mechanism. [0159] At step 4016, the Application Program starts background processing (BP). In BP, the

Application Program shall perform a standard diagnostic check, and the following additional diagnostics: (1) check door status and (2) perform a base inventory scan if the door is closed.

[0160] At step 4017, the Application Program shall then analyze diagnostics to determine if the unit should go into Interactive or Lockdown mode.

[0161] The following is a list of conditions considered in step 4017 which could cause the apparatus 100 to enter into Lockdown mode in step 4019:

[0162] (1) the Application Program shall enter Lockdown mode, if the interior temperature falls outside of specified range (as defined in the configuration); [0163] (2) the Application Program shall enter Lockdown mode, if a request has come in from the web service to enter this mode;

[0164] (3) the Application Program shall compare the results of the base inventory scans with the last known scan and enter Lockdown mode if more then X number of products have been removed (X shall be a configuration parameter); [0165] (4) the Application Program shall enter Lockdown mode if there is no more space to store transactions (the application shall need enough storage space left to store an info-transaction to indicate lockdown);

[0166] (5) the Application Program shall enter Lockdown mode if the door was open when the unit was turned on. [0167] Preferably, the Application Program needs to continue starting up and enter the interactive mode, so that the apparatus 100 can support multiple units (i.e., to support a configuration where one apparatus 100 handles multiple storage containers). In other words, if there are six storage containers, and one is open and five are closed, the apparatus 100 should not lockdown the five that are closed. Instead, the Application Program sends an information transaction to the backend system to indicate that the Application Program started up with the door open. Once the door is closed, the Application Program performs a baseline inventory scan (i.e., controls the RFID reader 102 to initiate RFID scanning to obtain a baseline inventory scan). [0168] At the end of step 4017, the Application Program shall send (e.g., to the backend system) a diagnostics message, such as a message indicating that the unit has completed its startup sequence and is entering either Interactive or Lockdown mode. The Application Program shall also send (as part of the same message) the results of the diagnostics. [0169] In step 4019, Lockdown Mode is carried out. The Application Program shall send a message to the web service (i.e., the backend system) that unit is in Lockdown mode. The Application Program shall show advertisements as normal, and shall provide a screen display indicating that the device is in Lockdown mode. The Application Program shall restrict the user from opening the door, unless the user authenticates to the full administrator role (i.e., authenticates himself as an administrator). The Application Program shall continue to send heartbeats at configured intervals as part of the background processing. The Application Program shall remain in Lockdown mode until the receipt of a Cancel Lockdown mode message from the web service (i.e., backend system). [0170] In step 4018, the Interactive Mode is initiated. If an HMI is present, the Application Program will start displaying advertisements to the user on the display screen, and shall wait for the user to authenticate.

[0171] In more detail, flow control will now pass to step 4009. At step 4009, the Application Program shall wait for a user to present a pass or credentials (e.g., PIN, biometrics, RFID badge, magnetic card, etc.) to authenticate himself. This allows the Application Program to check for an authorized user; the Application Program determines if the user has presented valid credentials.

[0172] At step 4010, the user is authenticated by the Application Program based on the pass presented. [0173] At step 4011, the Application Program determines if the user's credentials are valid or not. If the user's credentials are invalid, then flow control passes to step 4012.

[0174] At step 4012, the Application Program uses the HMFs display to inform the user that the user of his invalid login, and flow control returns to step 4009.

[0175] If the user's credentials are found in step 4011 to be valid, the flow control passes to step 4020. In this step, the Application Program enters a main processing loop that we refer to as the LaunchPad. In particular, preferably, the Application Program shall display a screen on the HMI in response to the user being authenticated. The screen shall include the following information: (1) welcome message with the user's first name; (2) a transaction confirmation screen; (3) an elevate permissions button — elevated permissions is the process of temporarily granting a user who is not a member of the full administrator role, full administration rights, after the completion of a challenge/response process (the duration of the elevated permission shall last until the user logs out); (4) a button for each storage container controlled by the Application Program (clicking the button will unlock that storage container); and (5) for limited and full administrator logins only, (a) an inventory restock button; (b) a maintenance button; and (c) a diagnostics button. In this LaunchPad mode, after the storage container or storage containers are unlocked, the user will be able to remove one or more tags or tagged items from the same or to add a tag or tagged item or items. After a storage container is locked, Application Program will generate a command for initiating RFID reading and communicate that command to the RFID reader responsible for that storage container.

[0176] If it is determined at step 4008 that the user has requested bypass (e.g., by tapping the screen within 10 or less seconds), then flow control continues with step 4025 in Fig. 17. In this figure, steps 4009, 4010, and 4012 are similar to those described above with respect to Fig. 16. Thus, the user will now need to authenticate himself. If the user is not authorized to bypass the startup sequence, then in step 4012, the Application Program shall display a screen with a message that reads, "You do not have access to bypass startup sequence" for 2 seconds indicating failure, and then continue the boot process, if the user presents invalid credentials or after 3 invalid attempts or 10 seconds have expired. If it is determined in step 4021 that the credentials are valid, then flow control continues to step 4022. In that step, a diagnostics screen is displayed to the user, along with an option to load the configuration settings (here, the user can administer apparatus 100 by performing diagnostics or changing the configuration settings). In step 4023, it is determined whether to shutdown the apparatus 100 or to reboot it. [0177] Fig. 18 shows the flow control where it is determined that an HMI is not available. This is similar to Fig. 16, but since there is no display, there is no advertising. When background processing is started in step 4016, the apparatus 100 is in a state where it is ready to unlock a storage container and, in response to closing of the door of the storage container, to perform RFID scanning as discussed above.

[0178] Of course, the foregoing represents the preferred flow control used by the Application Program, and is provided by way of example and not of limitation.

[0179] A network of tower units

[0180] Another network system is shown in Fig. 12. In that figure, there are three tower units 300, as discussed above. The middle tower unit 300 is a master tower that houses the controller 103 (and HMI), whereas the left and right tower units 300 are secondary towers that do not have controllers 103. The secondary towers connect to the master tower 300's controller 103 via ethernet so that controller 103 may control the RFID readers 102 of the two secondary towers. This enables the placement of several towers with the possibility of any storage type to be located in close proximity. This maintains the modular approach of mixing and matching the required storage while reducing the cost of hardware.

[0181] Additional or alternative embodiments or modifications of embodiments

[0182] While the invention has been discussed above with respect to a storage container, it is envisioned that the invention could also be applied to other areas intended to be RFID-scanned, such as, for example, an open-face shelf. In such a case, the enclosure 101 could be attached to the shelf. And RFID antenna 106 could be mounted on or in a shelf. [0183] Another embodiment is an application of the invention for museum use or the like. For example, a system could be set up where personnel have limited access or registered access to a room or an area. Access would be provided in accordance with an RFID pass, biometric scan, or magnetic card swipe, for example. Any movement or removal of tagged objects or artifacts in the room would be registered (i.e., charged) to that individual person, thus allowing check-in and check-out of objects/artifacts from the room or area. Preferably, wiring connecting the apparatus 100 to the RFID antenna 106 would not be visible or externally accessible. The antenna or antennae 106 could be placed on a shelf or shelves external to the apparatus 100.

[0184] This alternate embodiment is schematically depicted in Fig. 15. In that figure, reference numeral 2001 indicates two artifacts or objects, each having an RFID tag 2002, which are respectively placed on a pair of open shelves 2003, each shelf having an RFID antenna 106. Apparatus 100 uses the two RFID antennae 106 to detect the presence or absence of the tagged artifacts or objects. Reference numeral 2004 denotes an authentication unit, connected to apparatus 100, that authenticates a user using a pass such as an RFID pass or magnetic card or the like or by using biometrics, and permits access to a room (indicated by the dotted line) in which the artifacts or objects are located.

[0185] Still further embodiments

[0186] While we have described above an example in which three RFID reader apparatuses are used, each apparatus scanning a respective pair of cabinets (i.e., the first RFID reader apparatus scans one pair of cabinets, the second RFID reader apparatus scans a second pair of cabinets, and the third RFID reader apparatus scans a third pair of apparatuses), the present invention is not limited to using only three RFID reader apparatuses. Instead, many more RFID reader apparatuses could be used. Furthermore, the RFID reader apparatuses could be networked together as discussed above. In such a case, one RFID reader apparatus could be a primary apparatus and the other RFID reader apparatuses could be secondary apparatuses, as also discussed above. Preferably, the secondary apparatuses would be within an acceptable distance from the primary apparatus to facilitate their interconnection. [0187] While we have described above networking apparatuses 100 together using an Ethernet LAN as a preferred technique, they may also be connected by other techniques, such as WiFi (wireless), Bluetooth, etc. for operation.

[0188] While we have described above using any of an ethernet connection, serial connection, IEEE 1394 connection, USB connection, and telephone connection for connecting apparatus 100 to a remote backend inventory management system or another such apparatus, alternatively other techniques such as wireless (e.g., WiFi) or Bluetooth could be used. [0189] While we have described above connecting the RFID reader 102 to the controller 103 using an ethernet hub 104, it is not required that an ethernet hub 104 be used. Instead, RFID reader 102 and controller 103 could be connected by a cable such as, for example, a crossover cable. Such might be done if only one apparatus 100 were present. [0190] While we have described above connecting I/O block 110 via ethernet (to controller 103 via ethernet hub 104), the invention is not limited to use of ethernet. The controller 103 may also have other interfacing methods such as GPIO and I²C. Thus, an alternative to using the ethernet-based I/O block 110 would be to instead use a non-ethernet-based interface board for polling and controlling I/O points. These I/O points would be controlled by the GPIO and I²C bus from the controller 103. This non-ethernet-based interface board preferably would only be used in apparatus 100 where the controller 103 is present. Any remote I/O blocks preferably would remain Ethernet based. The non-ethernet-based interface board preferably has a plurality of inputs and outputs (such as digital, analog, etc.) as well, can also provide temperature information to the controller, and can also control a lock on a storage container 200, at the direction of the controller 103, to lock and unlock the door of storage container 200 to control access to the storage container 200.

[0191] Whether I/O block 110 is ethernet-based or not, as discussed above, preferably a door position sensor is provided (for apparatus 100), which sensor is connected to I/O block 110. The door position sensor can be used to detect when the door is open and closed. This allows for RFID reader 102 to only scan storage container 200 when the door is in a closed, locked position. The sensor can also inform controller 103 when there is an illegal entry into storage container 200.

[0192] Also, preferably an authentication reader is provided (for apparatus 100). The authentication reader is a device that interfaces with the controller 103 via serial, USB, etc., to authenticate an end system user (i.e., a user). The device could be an LF (125KHz) pass reader, magnetic stripe reader, a biometric device, etc. to name a few. [0193] While we have described above that controller 103 preferably communicates with RFID reader 102 via ethernet, the invention is not so limited. Alternatively, controller 103 could communicate with RFID reader 102 via Ethernet or USB. Likewise, instead of using ethernet, the VO block 110 (i.e., interface board) could connect to the controller 103 via the controller 103's GPIO port and I²C bus. Preferably, all these pieces (i.e., controller 103, RFID reader 102, I/O block 110, etc.) are disposed inside of enclosure 101. In this alternative scenario, there is no need for Ethernet hub 104, which may thus be omitted. [0194] While we have described above preferably using Windows CE 5.0, alternatively, controller 103's operating system could be Linux-based. A Java or C++ based program could be used on controller 103 as well, as an alternative.

[0195] While display 1052 has been described above in a preferred embodiment as an LCD screen, it could be, for example, a TTL or LVDS LCD screen, which would be connected to the controller 103.

[0196] While we have described above using DHCP for dynamic addressing of apparatuses 100, alternatively, where the controller 103 cannot implement a DHCP server, devices requiring IP addresses may be assigned statically. The Application Program would then scan the internal subnet looking for devices that are not already configured for use. Once new hardware devices are found, they would be configured for use in the system.

[0197] While we have described preferred antenna placement above, when 900MHz antennas are used, we prefer to attach the antenna to the interior surface of the exterior metal chassis of the refrigerator or cabinet. The antenna is preferably disposed between the metal exterior wall of the refrigerator and the separate plastic wall of the interior of the refrigerator. [0198] While we have described above using AC main power, alternatively, a 12V DC power system could be used to power the system. And the relay to provide a hard reset to the entire system is an optional device that may be omitted.

[0199] Furthermore, we have described above a preferred embodiment which uses two trays to hold various components. Alternatively, one tray could be used. Such is shown in another embodiment, which is depicted in Figs. 19 through 21. In this embodiment, one tray 1060 inside enclosure 101 could be used to hold all electronics. The front side 1001 of apparatus 100 is attached to the electronics tray 1060. The HMI screen 1058 (corresponding to screen 1052 in the first embodiment) is attached to front panel 1001. To open enclosure 101, eight screws 1002 have to be removed as shown in Fig. 21. The electronics tray 1060 and front panel 1001 then can slide out of enclosure 101 on drawer slides 1059 as shown in Fig. 20. This provides access to the electronics. In this embodiment, the back side 1004 of enclosure 101, as shown in Fig. 20, is on a hinge 1009. When the six screws 1002 are removed, the back panel folds down providing access to additional pieces. The power outlets 1007 are mounted to a panel 1061 that can be replaced to allow for different power outlets. An additional power switch 1062 controls AC power to the internal electronics. However, switch 1062 does not control power to outlets 1007. Several Ethernet couplers 1008 can be seen in Fig. 20. This design could be used when connecting several tower units 300. [0200] While we have described above using a controller 103 that is separate from the RFID reader 102, the invention is not so limited. Some RFID readers allow installation of an application (i.e., a software program) on the RFID reader itself. Thus, instead of providing a separate controller 103, one could omit that component and instead install an application onto the RFID reader 102 which would perform the steps described above with respect to the controller 103. An advantage of using a separate controller 103 is that RFID readers do not offer (a) a convenient way for analog input (e.g., reading the temperature) or (b) a video display. Another advantage of using a separate controller 103 is that it allows one to swap out RFID readers for different applications if needed.

[0201] While we have described above using a remote backend inventory management system such as, for example, a database, ERP system, or financial package such as Microsoft Dynamics or Quickbooks, the invention is not so limited. For example, instead of communicating with a backend database system, apparatus 100 might instead be configured to communicate with a middleware system (such as BizTalk RFID or some other middleware system).

[0202] While we have described above placing the RFID antenna in a wall, we do not mean to limit placement to a side wall — the antenna could also be located in other places such as the ceiling or the floor of a storage container, or in a shelf of the storage container, among other places. [0203] When we make reference above to cabinets, ambient cabinets, and refrigerated cabinets, we wish to emphasize that "cabinet" by itself is a broader term that encompasses any type of cabinet including ambient cabinets and refrigerated cabinets. [0204] While we have described above that the HMI can be provided in the controller 103, the invention is not so limited. We also envisage a handheld (i.e., portable) HMI that can communicate with apparatus 100 via WiFi or the like.

[0205] We have mentioned above that the apparatus 100 can monitor the temperature of a cabinet for example. The apparatus 100 can send such information via a network connection to a remote apparatus (e.g., backend 1057). System health information other than temperature can also be sent. Preferably, controller 103's Application Program should send back to the remote apparatus a health status document as to how the system is doing, including, for example, memory usage, internet connectivity state, etc., as well as how any connected enclosures are doing, e.g., temperature, door status, etc. [0206] Furthermore, there are many smart devices (e.g., a device external to apparatus 100) that people may use in conjunction with products or items stored in storage container 200. An example of such a smart device is a device that performs scientific testing upon a product or item stored in storage container 200. Preferably, these smart devices may allow for interfacing via a serial or USB connection. Thus, for example, such a smart device could be connected to controller 103 via a connection such as, for example, serial or USB. This would allow for interfacing to the smart device. The interfacing could be through the HMI or middleware/backend. The smart device would then enjoy the same benefits of the system being connected to the middleware/backend. The controller 103 could query the smart device for health information, e.g., how many runs the smart device had completed, and send on this report to the middleware/backend. From the report, maintenance could be scheduled in advance based on how many runs the smart device had completed or other information included in the health status reported back. The smart device could also be configured to send results of scientific tests the device had been performing to the end user (via the connection to the middleware/backend) once the tests had been completed. Or the smart device could receive remote updates (from the middleware/backend) to its running software. [0207] One example of a smart device as discussed above is Promega's Maxwell® 16 robotic DNA purification machine. This machine currently has a serial port integrated into the machine so that firmware upgrades can be performed on the machine. Thus, for example, the purification machine could be placed on top of enclosure 101 and connected to controller 103 via a serial connection. Fig. 22 is a schematic diagram showing the serial interconnection between controller 103 and the purification machine, which is identified in the drawing by reference numeral 5001. Of course, the invention is not limited to a serial connection and any other data connection could be used. In this embodiment, preferably, controller 103's Application Program knows that the purification machine 5001 is connected to it, and has established two way communication between controller 103 and the purification machine.

When the controller 103 communicates with the backend/middleware 1057 (via, for example, the Internet connection), it sees that the purification machine, which is connected to it by the serial connection, needs to have a new version of firmware applied. Therefore, the controller 103 downloads the update and then applies it to the purification machine via the serial connection. The controller 103 would then report back (to the backend/middleware 1057) the success or failure of the firmware upgrade.

[0208] As another feature in this embodiment, the controller 103 could act as an intermediary between the purification machine and the backend/middleware 1057, i.e., to forward to the backend/middleware 1057 test results provided to controller 103 by the purification machine. Assume, for example, that the purification machine were running one of its purification runs. In conjunction with the purification machine printing out the results, the results could also be communicated by the purification machine to controller 103 via the serial connection. Controller 103 could then send the results back to the backend/middleware 1057 (via a network connection). An e-mail or other notification could be then sent (by the backend/middleware 1057) to the researcher who had started the run saying the run had been completed. The results could then be processed further or more calculations done on a computer that could not be performed on the purification machine. These in-depth results could then be e-mailed back to the researcher (from that computer). Or the results could be made available (by that computer) via a webpage. All previous results could also be saved and cross-referenced (by that computer). [0209] Furthermore, just as apparatus 100 can send its own system health information to the backend/middleware 1057, the purification machine could also report its system health information to controller 103 for sending back to the backend/middleware 1057 via a network connection. By way of example, assume that the purification machine has been operating under heavy load for some time. As with any mechanical device, parts and pieces may wear out. The purification machine 5001 could send a warning to controller 103 (via the serial connection) saying that there are problems occurring with some component of the purification machine. The component may not have failed, but may be close to failure. By reporting when a component is close to failure, this allows for a more proactive approach to remote service. Next, the controller 103 receives the warning, and sends a message to backend/middleware 1057 via a network connection. Once the backend/middleware 1057 receives the alarm or error, appropriate personnel can be alerted to fix the device or send replacement parts out. [0210] Furthermore, the backend/middleware 1057 could collect all this data (e.g., system health information from the purification machine 5001) and make it available to the end researchers. For example, information regarding how much the purification machine has been used in the past 30 days could be provided by the backend/middleware 1057 for display. Detailed results can also be made available for all experiments conducted by the purification machine. Any number of reports could be generated from this data. [0211] Of course, the purification machine is only one example of a smart device that could be connected to controller 103. Promega has several robotic devices that could be used in place of the Maxwell® 16 DNA purification machine. We envision that any lab device that could benefit from these types of services and reporting could be connected (to controller 103). [0212] We have described above using screws to secure the front panel 1001; however, where screws are not a sufficient mechanism to deny access to the inside of enclosure 101, several different locking mechanisms could be employed such as, for example, a physical key lock, an electromagnet, or a deadbolt. Any of these devices could be used to secure the front panel 1001 and/or the back panel 1004. Fig. 23 is a schematic view showing the front panel 1001 secured by a key lock 5002 in an embodiment of the present invention that uses a locking mechanism.

[0213] INDUSTRIAL APPLICABILITY [0214] The present invention provides an RFID reader with an enclosure that allows it be securely affixed to a storage container such as a refrigerator without exposing wiring to tampering, and thus has use as an improved mounting technique.

[0215] The present invention also provides an RFID reader that uses plural antennae to scan plural respective storage containers, thereby avoiding the need to have plural RFID readers, and thus has use as an improved RFID scanning technique.

[0216] And the present invention also provides a networked system of master and slave RFID apparatuses, wherein a master RFID apparatus contains a controller for controlling the slave RFID apparatuses which lack such a controller, and thus has use as an improved RFID scanning system.

[0217] CONCLUSION

[0218] Except as otherwise disclosed herein, the various components shown in outline or in block form in the figures are individually well known and their internal construction and operation are not critical either to the making or using of this invention or to a description of the best mode of the invention.

[0219] Although specific embodiments of the present invention have been described above in detail, it will be understood that this description is merely for purposes of illustration. When we have said that something "is", "shall", "will", or "should be" the case, for example, we do not mean to limit the invention, but are merely providing a specific example or specific examples. Various modifications of and equivalent structures corresponding to the disclosed aspects of the preferred embodiments in addition to those described above may be made by those skilled in the art without departing from the spirit of the present invention which is defined in the following claims, the scope of which is to be accorded the broadest interpretation so as to encompass such modifications and equivalent structures.

Claims

WHAT IS CLAIMED IS:

1. An apparatus comprising: an enclosure; and an RFID reader disposed in said enclosure, wherein said enclosure is configured to be mounted on an exterior surface of a storage container, wherein said RFID reader is configured to perform RFID reading for an area inside the storage container using an RFID antenna external to said enclosure, wherein the RFID antenna is disposed in the storage container, wherein said enclosure has an opening on a side of said enclosure, and wherein an electrical connection between said RFID reader and the RFID antenna extends through the opening of the enclosure in such a manner that the electrical connection is not externally accessible when said enclosure is mounted on the exterior surface of the storage container.

2. An apparatus according to claim 1, wherein said apparatus further comprises a human-machine interface including a display screen.

3. An apparatus according to claim 2, wherein the human-machine interface for said apparatus uses a display provided separately from said enclosure.

4. An apparatus according to claim 1 , wherein said apparatus is configured to perform RFID reading using said RFID reader, obtain a RFID scanning result comprising a list of tags read from said RFID reader, and send information in response to the RFID scanning result to a middleware system via a network connection.

5. An apparatus according to claim 1, wherein said apparatus further comprises a controller that is configured to perform steps comprising (a) send an instruction to said RFlD reader to perform RFlD reading, (b) receive a RFID scanning result comprising a list of tags read from said RFID reader, and (c) send information in response to the RFID scanning result to a database system via a network connection.

6. An apparatus according to claim 1, wherein the RFID antenna is disposed within a wall of the storage container.

7. An apparatus according to claim 1, wherein the RFlD antenna is disposed within a floor or ceiling of the storage container, or in a shelf of the storage container.

8. An apparatus according to claim 1, wherein the storage container is a cabinet.

9. An apparatus according to claim 8, wherein the cabinet is a refrigerated cabinet.

10. An apparatus according to claim 1, wherein the opening of said enclosure communicates with an opening on the exterior surface of the storage container when said enclosure is mounted on the exterior surface of the storage container.

11. An apparatus according to claim 1, wherein software used by said apparatus comprises software implemented using an abstract base class that interfaces with a concrete class particular to a given item of hardware of said apparatus.

12. An apparatus according to claim 11, wherein the given item of hardware is said

RFID reader.

13. An apparatus comprising: an RFID reader configured (a) to perform RFID reading for an area within a first storage container using a first antenna and (b) to perform RFID reading for an area within a second storage container using a second antenna.

14. An apparatus according to claim 13, wherein said apparatus is connected to the first storage container and the second storage container.

15. An apparatus according to claim 13, wherein said apparatus is disposed between the first storage container and the second storage container.

16. An apparatus according to claim 15, wherein said apparatus is connected to the first storage container and the second storage container so that an electrical connection between said RFID reader and the first antenna is not externally exposed and an electrical connection between said RFID reader and the second antenna is not externally exposed.

17. An apparatus according to claim 13, wherein the first storage container is a cabinet and the second storage container is a cabinet.

18. An apparatus according to claim 13, wherein the first storage container is a refrigerated cabinet and the second storage container is a refrigerated cabinet.

19. An apparatus according to claim 13, wherein the first storage container is an ambient cabinet and the second storage container is an ambient cabinet.

20. An apparatus according to claim 13, wherein the first storage container is an ambient cabinet and the second storage container is a refrigerated cabinet.

21. A system comprising: three or more of said apparatuses according to claim 13; and three or more pairs of cabinets, each pair of cabinets being scanned by a corresponding one of said three or more apparatuses.

22. A system according to claim 21, wherein each of said three or more apparatuses has one of said cabinets attached to the top of said apparatus and one of said cabinets attached to the bottom of said apparatus.

23. A system according to claim 21, wherein only one of said apparatuses comprises a controller that generates commands to RFK) readers in said apparatuses to initiate RFK) scanning.

24. A method comprising: performing RFID reading for an area within a first storage container and an area within a second storage container using an RFID reader connected both to a first antenna and a second antenna, the first antenna being used for performing reading for the area within the first storage container and the second antenna being used for performing reading for the area within the second storage container.

25. A system comprising: a first apparatus comprising a first RFK) reader configured to perform RFID reading using a first antenna; and a second apparatus comprising (a) a second RFID reader configured to perform RFK) reading using a second antenna, and (b) one of (1) a controller configured to (i) control said first RFK) reader and said second RFID reader and (ii) communicate via a network connection with an inventory management system and (2) a controller configured to (i) control said first RFK) reader and said second RFID reader and (ii) communicate via a network connection with a middleware system.

26. A system according to claim 25, wherein said first apparatus and said second apparatus are connected via a local area network, and said second apparatus further comprises a network connection between said second RFID reader and said controller.

27. A system according to claim 25, wherein said controller comprises a user interface for controlling said first RFID reader and said second RFID reader.

28. A system according to claim 25, wherein said controller is configured to control said first RFID reader to perform plural RFID scans, to obtain a first RFID scanning result in accordance with the plural RFID scans by said first RFID reader, to control said second RFID reader to perform plural RFID scans, to obtain a second RFID scanning result in accordance with the plural scans by said second RFID reader, and to communicate with the system in accordance with the first RFID scanning result and the second RFID scanning result.

29. A system according to claim 28, wherein the first RFID scanning result is based on a difference between plural RFID scans.

30. An apparatus comprising: means for attaching a device comprising an RFID reader to an exterior surface of a storage container so that wiring between the RFID reader and an RFID antenna in the storage container is not externally exposed.

31. An apparatus according to claim 30, wherein the storage container is a refrigerator.

32. An apparatus according to claim 30, wherein the device further comprises an enclosure in which the RFID reader is positioned, and wherein the enclosure comprises an exterior panel which is secured to the enclosure by a key lock.

33. An apparatus according to claim 30, wherein said device further comprises means for sending to a remote apparatus via a network connection RFlD scanning results obtained using the RFlD reader.

34. An apparatus according to claim 33, wherein said device further comprises means for receiving system health information of another device from the another device via a data connection between said device and the another device and for sending the system health information to the remote apparatus via the network connection.

35. A system comprising: a master RFID reading apparatus comprising an RFID reader; and one or more secondary RFID reading apparatuses each comprising a respective RFlD reader, wherein said master RFID reading apparatus further comprises control means for controlling (a) said RFID reader of said master RFID reading apparatus and (b) via networking between said master RFID reading apparatus and said one or more secondary RFID reading apparatuses, said RFID reader of each of said one or more secondary RFlD reading apparatuses.

36. A system according to claim 35, wherein said master RFID reading apparatus uses said RFID reader of said master RFID scanning apparatus to perform RFID scanning of a storage container, and wherein said one or more secondary RFID reading apparatuses use their respective RFlD readers to perform RFID scanning of a respective plurality of other storage containers.