This invention relates generally to radio-frequency identification (RFID) transceivers.
RFID tags are known in the art. These so-called tags often assume the form factor of a label or a literal “tag” but are also sometimes integrated with a host article and/or its packaging. RFID tags typically comprise an integrated circuit and one or more antennas. The integrated circuit typically carries out a variety of functions including modulating and demodulating radio frequency signals, data storage, and data processing. Some integrated circuits are active or self-powered (in whole or in part) while others are passive, being completely dependent upon an external power source (such as an RFID tag reader) to support their occasional functionality.
There are proposals to utilize RFID tags to individually identify individual items. The Electronic Product Code (EPC) as managed by EPCGlobal, Inc. represents one such effort in these regards. EPC-based RFID tags each have a unique serial number to thereby uniquely identify each tag and, by association, each item correlated on a one-for-one basis with such tags. (The corresponding document entitled EPC Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz Version 1.0.9 is hereby fully incorporated herein by this reference.)
RFID readers are devices that attempt to read any RFID tags within range of the reader. Typically, the RFID reader transmits electromagnetic energy through free space to any tags within range. The energy is received at any RFID tag in range, modulated with identification or other data stored in the RFID tag, and backscattered by the RFID tag back the reader. The RFID reader receives the backscattered energy and demodulates the energy to recover the data. In other forms, the RFID reader induces a response within the RFID tag using electromagnetic force, the induced response is then modulated with the data of the RFID tag which then induces a corresponding response back in the RFID reader which demodulates the response to recover the data. The data recovered by the RFID reader is then processed in accordance with the purpose of the reading.
Disclosed herein are embodiments of apparatuses and methods pertaining to the use of RFID tags and readers to automatically make certain determinations, e.g., to determine an open status of a sealed container. This description includes drawings, wherein:
Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments of the present invention. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. Certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. The terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions by persons skilled in the technical field as set forth above except where different specific meanings have otherwise been set forth herein.
Generally speaking, pursuant to various embodiments, a container is in a closed orientation and upon a given user action, the container can be moved to an at least a partially open orientation. Accordingly, in some embodiments, it is desired to automatically determine an open status of the container. In some embodiments, an RFID-tag reader and RFID tags located at or proximate to the container are used to indicate an open status of the container. In some embodiments, a first RFID tag is fixed to a first portion of the container and a second RFID tag is fixed to a second portion of the container. Upon a user action to at least partially open the container, the first and the second portions will be caused to move relative to each other, resulting in that one or more of the RFID tags will no longer be readable by the RFID-tag reader or will now be readable by the RFID-tag reader. The reading or cessation of reading of one or more RFID tags indicates at least one open status of the container. In some embodiments, the container is closed and in some embodiments, the container is closed and sealed. In some embodiments, the open status is at least one of a fully closed/sealed status, an unsealing confirmation, an open motion initiation status, an open motion confirmation, a partial open status and a fully open status. In some embodiments, the container may take the form of a container locked within a delivered-package vault such as described in U.S. patent application Ser. No. 14/052,102 filed Oct. 11, 2013 and entitled SECURE DELIVERY RECEPTACLE, which is incorporated herein by reference, where the container contains a package for delivery to a recipient, and where it is desired to automatically detect the open status of the container to determine delivery status/completion, for example. In some embodiments, the first portion and the second portion of the container are components that are fixed to the container. In a non-limiting example, the first and second portions components including are a sleeve and an insert coupled to portions of the container.
In some embodiments, one of more of the RFID tags incorporate principles embodied in RFID tags such as those described in U.S. patent application Ser. No. 12/721,527 filed Mar. 10, 2010, now U.S. Pat. No. 8,286,884 issued Oct. 16, 2012; U.S. patent application Ser. No. 13/653,324 filed Oct. 16, 2012, now U.S. Pat. No. 8,544,758 issued Oct. 1, 2013; U.S. patent application Ser. No. 13/828,821 filed Mar. 14, 2013; U.S. patent application Ser. No. 12/884,097 filed Sep. 16, 2010, now U.S. Pat. No. 8,286,887 issued Oct. 16, 2012; and U.S. patent application Ser. No. 13/653,331 filed Oct. 16, 2012, now U.S. Pat. No. 8,505,829 issued Aug. 13, 2013, all of which are incorporated herein by reference. Such RFID tags are designed such that the near field portion and the far field portion of the RFID tag may be coupled together and decoupled. When coupled, the RFID tag is readable by an RFID tag reader in both the near field of RFID communication and in the far field of RFID communication. When decoupled, the RFID tag is only readable by an RFID tag reader in the near field of RFID communication. In some cases, the near field portion of the RFID tag may be a pre-manufactured generic component which is cooperated with a far field antenna separately designed and manufactured for the application.
In some embodiments, a multi-tag RFID device is provided that includes first and second near field RFID tags implemented on a substrate and that are each coupled to and share a conductive element on the substrate. The conductive element functions as a far field antenna to both the first and second near field only RFID tags. In some embodiments, the RFID device is implemented in a single inlay. Such RFID devices may be used in some embodiments to indicate an open status of a container and/or may be used for other purposes.
As is well known in the art, referring initially to
In the near field region, the electromagnetic signal does not propagate as a waveform. The near field region has two sub-regions: a near field radiating sub-region 1204 and a near field reactive sub-region 1206. In the near field reactive sub-region 1206, energy is stored, but not radiated. The near field reactive sub-region 1206 is typically where the reader antenna and the tag are coupled within ½ wavelength of the carrier wave. This is typically very close to the reader antenna. The near field radiating sub-region 1204 is a transitional region between the near field reactive sub-region 1206 and the far field region 1202. The near field radiating sub-region 1204 is typically where the reader antenna and the tag are coupled between ½ to 1 full wavelength of the carrier wave. In the near field radiating sub-region 1204, while there is radiated electric and magnetic fields, these electric and magnetic fields do not propagate and are not perpendicular to each other and to the direction of propagation (if there were propagation). This is well understood in the art.
In many embodiments, the boundary between the near field region and the far field region can be defined as “r”, illustrated in
Generally, the near field and far fields of RFID communication are well known in the art. Many near field devices include devices complying with the Near Field Communication (NFC) Forum standards, High Frequency (HF) devices, Electronic Shelf Labels (ESLs), and so on. Other examples of devices that communicate in the near field are near field only tags such as those tags described in U.S. Pat. Nos. 8,286,884 and 8,286,887, both of which are incorporated herein by reference, i.e., tags that lack a far field antenna and magnetically, inductively or capacitively couple to a corresponding reader. Devices that communicate in the near field typically have a range of being detected at about an inch or so away up to about 1-2 feet maximum depending on the frequencies used.
In a typical ultra-high frequency (UHF) RFID system where the carrier frequency is in the range of 860-960 MHz, the effective near field is the region up to approximately 1-15 centimeters from the reader antenna, whereas the far field is the region from approximately 15-40 centimeters and beyond the reader antenna. In many cases, the reader can read tags in the near field up to about 15 centimeters away, whereas depending on the tag antenna, the reader can read tags in the far field up to about 20-30 feet or more away. These features are also well known in the art.
It is understood that the near field tags may be designed to operate with reader antennas operating at a variety of frequencies, such as low frequency (LF) at 125-134 kHz, high frequency (HF) at 13.56 MHz, ultra high frequency (UHF) at 860-960 MHz, microwave frequencies at 2.4 and 5.8 GHz, for example.
Another way to view near field and far field communications relates to how the reader and the tag are coupled together. The reader and a near field tag communicate through magnetic, inductive or capacitive coupling between the reader antenna and the tag antenna (typically a near field loop antenna). For example, a current is induced in the reader antenna (e.g., loop antenna), which when brought into close range with the tag antenna (loop antenna) induces a current in the tag antenna which is modulated according to the data of the tag and induced back to the reader antenna. This type of near field communication is well known in the art and may be considered the near field reactive sub-region 1206 of
With far field RFID devices, the reader and the tag communicate through the transmission of electromagnetic energy from the reader to the tag which is reflected back as transmitted electromagnetic energy to the reader. Far field communicating devices typically use dipole antennas or other antenna structures capable of transmitting energy and received transmitted energy in the far field. In many cases, the far field radiation decays as described in the far field region 1202 of
It is noted that in some embodiments, the read range of a given reader may be limited or changed by reducing or adjusting the power level of signals transmitted by the RFID reader. For example, far field RFID readers at normal operating power levels may be able to read far field RFID tags up to 20-30 feet. For example, the transmit power of the reader could be adjusted such that the reader can only read RFID tags at less than the normal range, e.g., up to 10-20 feet. This allows for the reading of the tag to occur only when the tag and tag reader are brought into a closer proximity compared to when the reader reads at normal power levels. Conversely, the increase of the read range results in the detection of a less precise (farther) location relationship between the reader and the tag than when the RFID reader operates at normal power.
Referring now to
In several embodiments, the RFID tag 110 is located on or proximate to a container which is normally in a closed orientation and is designed to be moved into an open orientation by a user. The RFID reader 102 is used to read the RFID tag 110. Information or signaling indicating whether the RFID tag 110 is read or not by the RFID reader 102 is passed to the control circuit 104 and in some embodiments, used to determine an open status of the container. In some embodiments, the RFID tag reader 102 is located in the far field of RFID communication relative to the location of the RFID tag 110. As such, in embodiments where the RFID tag 110 comprises decoupleable near field and far field components, the RFID tag 110 is readable by the RFID reader when the near field and far field components are coupled together. The RFID tag 110 is no longer readable by the RFID reader when the near field and far field components are decoupled, since the RFID tag would only be readable in the near field and the RFID reader is in the far field of RFID communication relative to the RFID tag.
In some embodiments, the control circuit 104 is integrated with or part of the device or apparatus including the RFID reader 102 (as indicated by the dashed box 116). In some embodiments, the control circuit 104 and the RFID reader 102 are integrated on the same integrated circuit device, e.g., on the same circuit board. In such cases, it is noted that when the RFID reader 102 and control circuit 104 are integrated, a function indicated herein as being performed by the control circuit may also be performed by the RFID reader 102. In other embodiments, the control circuit 104 is separate from and coupled to the RFID reader 102. For example, the control circuit 104 may be located at, integrated into or coupled to the central system 106. In such cases, the control circuit 104 is coupled by one or more wired and/or wireless communication links using the appropriate communicating devices. In some embodiments, the central system 106 may be at a physical location or local to the location of the control circuit 104 and/or reader 102, or may be at a remote location, for example, the central system 106 is a remote system (in the cloud) and coupled to the control circuit 104 via a network. Further, in some embodiments, the central system 106 may be used to store and monitor the open status of containers that are initially in a closed orientation, but are intended to be opened by a user, where such detection and determinations of open status are made by the control circuit 104. Such information and/or open statuses may be communicated for stored, display, communication, etc. to various user devices 108.
The processor 202 and the memory 204 may be integrated together, such as in a microcontroller, application specification integrated circuit, field programmable gate array or other such device, or may be separate devices coupled together. The I/O interface 206 allows communicational coupling of the control circuit to external components, such as the central system 106 and/or user devices 108. Accordingly, the I/O interface 206 may include any known wired and/or wireless interfacing device, circuit and/or connecting device. In some embodiments, a user interface 208 is included in the control circuit 200 which may be used for user input and/or output display. For example, the user interface 208 may include any known input devices, such a buttons, knobs, selectors, switches, keys, touch input surfaces and/or displays, etc. Additionally, the user interface 208 may include one or more output display devices, such as lights, visual indicators, display screens, etc. to convey information to a user, such as a given open status of a given container. The control circuit 200 is configured to communicate with the reader 102 to control its operation and to receive information from the RFID reader 102 regarding the reading of certain RFID tags. While
Generally, the control circuits 104 and 200 can comprise a fixed-purpose hard-wired platform or can comprise a partially or wholly programmable platform. These architectural options are well known and understood in the art and require no further description here. These control circuits 104 and 200 are configured (for example, by using corresponding programming as will be well understood by those skilled in the art) to carry out one or more of the steps, actions, and/or functions described herein.
Referring next to
In some embodiments, the first portion 302 includes one or more RFID tag devices. In the illustrated embodiments, a first RFID tag 306 is coupled (e.g., applied, formed, integrated, adhered, etc.) to a surface of the first portion 306, where the first RFID tag 306 is configured by itself to communicate only in a near field of RFID communication. For example, the first RFID tag 306 includes a chip and a near field antenna (e.g., loop antenna). In some embodiments, the first RFID tag may be referred to as a near field only RFID tag. A conductive element 308 is implemented (e.g., formed, printed, patterned, etched, adhered, etc.) at the second portion 304. The conductive element 308 is located in proximity to the first RFID tag 306 when the container is in the closed orientation. The conductive element 308 is configured to function as a far field antenna for the first RFID tag 306 such that the first RFID tag 306 is readable by an RFID reader in a far field of RFID communication when the container is in the closed orientation (illustrated in
As illustrated, the first RFID tag 306 extends from the space formed by the second portion, e.g., it is not covered by the second portion 304. In some embodiments, the conductive element 308 is formed at or near a periphery edge of the second portion 304 such that the conductive element 308 inductively, electrically or capacitively couples to the near field antenna (e.g., loop antenna) of the first RFID tag 306. In some embodiments, if the conductive element 308 were to cover the first RFID tag 306, it would electromagnetically shield the first RFID tag such that the first RFID tag 306 would not be readable in the far field of RFID communication.
A second RFID tag 312 is fixed to the first portion 302 such that the second RFID tag 312 is shielded by the second portion 304 and is not readable by the RFID reader when the container is in the closed orientation. For example, in some embodiments, the second portion 304 is made of a conductive material that substantially surrounds the second RFID tag 312 and functions as a Faraday cage making it unreadable in the far field of RFID communication. In some embodiments, an optional third RFID tag 314 is fixed to the first portion 302 such that the third RFID tag 314 is also shielded by the second portion 304 and is not readable by the RFID reader when the container is in the closed orientation. For example, in some embodiments, the second portion 304 substantially surrounds the third RFID tag 314 functioning as a Faraday cage and making it unreadable in the far field of RFID communication.
Thus, in some embodiments, as illustrated in
In some embodiments, the reading and cessation of reading of one or more RFID tags provides indications of an open status of the container. For example, in one embodiment, when the first RFID tag 306 is read in the far field by the RFID reader (e.g., see
In embodiments with the third RFID tag 314, when the first portion and the second portion are moved relative to each other at least a third amount (e.g., see
It is understood that while
In order to distinguish between tag reads, each tag can be encoded with a unique identifier known to the control circuit and that is provided by the reader when being read. In some embodiments, the tags may be encoded with an Electronic Product Code (EPC) such as a Serialised Global Trade Item Number (SGTIN) of the EPCGlobal Tag Data Standard as is well known in the art. In some embodiments, the unique identifiers are identical to each except for at least one bit, e.g., the last 1-2 bits of a SGTIN EPC code could be different. By using embodiments that allow automatic detection of the open status of a container, it can be determined automatically and without visual inspection if a given container has been opened, or has been unsealed but not fully opened.
While the first RFID tag 306 is illustrated as a decoupled design RFID tag such as described in the patent and applications incorporated herein by reference, the second and third RFID tags could be any RFID tag design known in the art that is readable in the far field of RFID communication. Further, in some embodiments, the second and third tags could be implemented as a multi-tag RFID device that includes first and second near field RFID tags implemented on a substrate and that are each coupled to and share a conductive element on the substrate that functions as a far field antenna to both the first and second near field only RFID tags, such as described with reference to
Referring to the plan views of
The first RFID tag 406 is configured to operate only in the near field of RFID communications. Accordingly, the first RFID tag 406 includes an integrated circuit or chip and near field antenna (e.g., loop antenna). For example, as is illustrated in more detail in
The second component 404 includes a portion thereof that implements a conductive element 408 that functions as a far field antenna. When the first component 402 is received within the second component 404 (see
The second RFID tag 412 can be any RFID tag device that is capable of being read in far field. For example, as shown in
Relative to the generic embodiments of
In some embodiments, the first component is an insert configured to fit within the second component which may be embodied as a sleeve. In some embodiments, the insert is at least partially flexible such that it can be removed from the sleeve but not easily re-inserted back into the sleeve. In some embodiments, a tool is provided to insert the first component within the sleeve. For example, an insert tool 502 is shown in
Referring next to
Generally, each of the near field RFID tag devices includes an integrated circuit device or chip and a near field antenna (e.g., a loop antenna), and optionally any coupling structure that may be needed or desired to couple the near field antenna to the conductive element. The conductive element 608 may be any far field antenna structure or pattern as is known in the arts. The conductive element 608 can be configured to couple to the antenna of each of the near field RFID tag devices through one of electrical, inductive and capacitive coupling. Such various coupling approaches are further described in the patents and patent applications incorporated herein by reference. In some embodiments, the near field RFID tag devices and the conductive element are manufactured together and implemented on a single inlay device.
Functionally, the first near field RFID tag device 602 couples with the conductive element 608 to form a first combination near field and far field RFID tag 610 that can be read in the near field as well as in the far field. Arrow 614 indicates the readability of the RFID tag 610 in the far field of RFID communication. The second near field RFID tag device 604 couples with the conductive element 608 to form a second combination near field and far field RFID tag 612 that can be read in the near field as well as in the far field. Arrow 616 indicates the readability of the RFID tag 512 in the far field of RFID communication.
It is understood that while two near field RFID tag devices are illustrated, three or more near field RFID tag devices could be implemented on the substrate and spaced apart from the other near field RFID tag devices and also share the conductive element.
In some embodiments, the multi-tag RFID device may be useful in applications where one or more of the near field RFID tag devices can be selectively shielded, e.g., by a conductive barrier positioned about the one or more near field RFID tag devices. Such can result in the selective readability of one or more of the near field RFID tag devices to an RFID reader, which can be used to make automated determinations and/or detections.
In some embodiments, a multi-tag RFID device may be implemented on the first portion (e.g., first component) of a container and useful to indicate one or more open statuses of the container. Referring to
When the first component 702 is fully inserted into the second component 404, the first RFID tag 406 couples to the conductive element 408 such that the first RFID tag 406 is readable in the far field. When the first component 402 is moved relative to the second component 404 a first amount (such as in
Reference is now made to the flow diagram of
Generally, the control circuit uses (or is configured to use) at least information received via the RFID reader regarding a reading of one or more RFID tags by the RFID reader, to determine one or more open statuses of a container normally in a closed orientation and which can at least be partially opened.
In Step 802, the control circuit receives a first indication from the RFID reader that a first RFID tag was read in a far field of RFID communication by the RFID reader. In some embodiments, the first RFID tag is fixed to a first portion of the container and configured by itself to communicate only in a near field of RFID operation. The first RFID tag is located in proximity to a conductive element implemented at a second portion of the container when the container is in the closed orientation, such that the conductive element is configured to function as a far field antenna for the first RFID tag when the container is in the closed orientation. In this arrangement and configuration, the first RFID tag is readable and is read in the far field of RFID communication (e.g. see the first RFID tag 306 in
Upon a user action to open the container at least a first amount (e.g., see
The container also includes a second RFID tag that is fixed to the first portion of the container such that the second RFID tag is shielded by the second portion and is not readable by the RFID reader when the container is in the closed orientation. Next, upon a user action to open the container at least a second amount (e.g., see
The container also includes a third RFID tag that is fixed to the first portion such that the third RFID tag is shielded by the second portion and is not readable by the RFID reader when the container is in the closed orientation. Upon a user action to open the container at least a third amount (e.g., see
Referring next to
In
In
While the container illustrated in
In a variation of
To further illustrate the coupling and decoupling of near field and far field components of an RFID device in accordance with some embodiment, reference is made to
In operation, each of the conductors 1324 and 1326 can function as a first electrode of a capacitor formed between itself and a far field or tag antenna, where a portion of the far field antenna forms the second electrode of the capacitor. Electromagnetic energy from the tag reader causes the voltage on the far field antenna (particularly at its end) to oscillate building a charge. This creates an oscillating potential difference at each elongated side of the near field RFID tag 1302, which causes a current to flow about the loop 1322. This flowing current allows the chip 1320 to operate and in turn, the conductive element 1308 functioning as the far field antenna capacitively coupled to the RFID tag 1302 to transmit an encoded backscattered signal to the tag reader.
In one embodiment, the near field RFID tag 1302 may be pre-manufactured. According to several embodiments, the near field RFID tag 1302 does not function as a far field RFID tag, i.e., on its own, it cannot be read in the far field by a reader. In preferred embodiments, the near field antenna 1322 is designed, shaped and/or configured to be suitable for use with a far field antenna capacitively coupled thereto. In some cases, the width or thickness of the conductors 1324 and 1326 is designed to ensure good capacitive coupling with the far field antenna.
The conductors 1324 and 1326 may extend from the near field antenna 1322 in a variety of ways and have varying lengths depending on the far field antenna it is intended to couple with. However, the coupling conductors 1324 and 1326 do not themselves function as far field antennas. Accordingly, while there is some additional conductive material apart from the near field antenna 1322, the near field RFID tag 1302 apart from a far field antenna is a near field only RFID tag that functions in the near field. For example, the conductors 1324 and 1326 cause the near field RFID tag 1302 to operate in the near field radiating sub-region 1204, whereas the near field antenna 1322 (e.g., loop) causes the near field RFID tag 1302 to operate in the near field reactive sub-region 1206.
When coupled with a far field antenna such as conductive element 1308, the resulting combination functions in both the near field and the far field. In some embodiments, to affect capacitive coupling, the near field RFID tag 1302 is coupled in a spaced relationship to one end 1304 of the conductive element 1308 (e.g., at a distal region 1310 of the conductive element as opposed to at or near the central region 1312). In operation, the voltage at the end 1304 (distal region 1310) oscillates due to the received electromagnetic energy from the reader. In some embodiments, the end 1304 and the conductor 1326 form two electrodes of a capacitor. As the voltage oscillates at the end 1304 building a charge, this creates an oscillating potential difference at the side of the tag 1302, which causes a current to flow about the near field antenna 1322. This flowing current allows the chip 1320 to operate and in turn, the conductive element 1308 capacitively coupled to the tag 1302 to transmit an encoded backscattered signal to the tag reader. When the end 1304 or distal region 1310 of the conductive element 1308 is capacitively coupled to the near field RFID tag 1302, the device becomes visible in the far field to an RFID reader.
As illustrated in
The near field RFID tag 1302 could be an embodiment of the first RFID tag 302 or 406, for example, and the conductive element may be an embodiment of conductive elements 308 and 408, for example. It is understood that while
In some embodiments, an application of one or more embodiments of the methods and structures to determine an open status of a container may be used in a secure delivery application in order to determine and/or verify opening of a package intended for delivery to a recipient (person). For example, the container may be delivered and locked within a delivered-package vault such as described in U.S. patent application Ser. No. 14/052,102 filed Oct. 11, 2013 and entitled SECURE DELIVERY RECEPTACLE, which is incorporated herein by reference. In some embodiments, the container contains the package for delivery to an intended recipient. The container is stored in the delivered package vault and locked therein, such that the intended recipient is not required to be physically present to accept delivery of the package. Such package vault may contain one or more structures and methods to determine that the container with package has been placed within the vault. In some embodiments, the container is pre-located in the vault (or part of the vault) and the package is delivered to the vault and inserted into the container within the vault by the delivery person. In some embodiments, the vault includes an RFID reader configured to read tags in the far field of RFID operation. When an intended recipient accesses the package vault to retrieve the package from the container (e.g., at the recipients convenience), one or more methods and/or apparatuses described herein may be used to determine the open status of the container. For example, the container includes a first RFID tag and the second RFID tag (and optional third or additional RFID tag/s) as variously described herein. If the first RFID tag is read by the vault's reader, the control circuit (coupled to the reader) can determine that the container is sealed/closed. However, once the first tag is no longer read by the reader, the control circuit can determine that the container is unsealed or that the container opening has been initiated or confirmed, for example. In some forms, the vault can distinguish a scenario where the first tag is not being read anymore because the container was moved from the vault out of range of the reader without opening the container (e.g., the container is fixed into the vault, opening size restriction, or there is another way (e.g., visual) to verify that the container is present in the vault). Once the second and optional third or more RFID tags are read by the reader (as they are exposed as described herein), the control circuit can determine one or more additional open status. Once the recipient has opened the container, the package may be retrieved therefrom, completing delivery. In some embodiments, measures can be taken to ensure that the right container has been opened by the right recipient. For example, by reader the various tags and using their identifiers, the control circuit can determine if the proper user (e.g., as determined at the point of access to the vault) has opened the proper container. If not, warning messages, emails, text messages or other electronic warnings may be issued to the appropriate system or person/s. In some embodiments, the container may be a refrigerated container or otherwise a container that requires sealing due to the package contained therein. Thus, in some embodiments, the reading or cessation of reading of the RFID tags can be used to determine an unsealed status. In the case of perishable packages (e.g., groceries, food items, refrigerated items, etc.), the control circuit (or other circuit or system in communication therewith) could start a timer and track whether the container has been fully opened within a specified time. For example, one could accidentally unseal a container but not open it fully, which would be detectable. In another example, someone may gain access to the vault and tamper with one or more containers, which could be detected in the opening/unsealing of the container. In some embodiments, since the first portion is flexible insert within a sleeve (second portion) and may even require an insertion tool, it would be difficult for one who tampered or accidentally unsealed a package to re-insert the first portion into the second portion. Corrective action could be taken or signaled to be taken, e.g., a warning message, refund of purchase, re-delivery of the item, etc. There are many alternatives and variations of these example applications that may use one or more embodiments of the methods and apparatuses described herein. It is understood that many other applications may use one or more embodiments of the methods and apparatuses described herein.
Those skilled in the art will recognize that a wide variety of other modifications, alterations, and combinations can also be made with respect to the above described embodiments without departing from the scope of the invention, and that such modifications, alterations, and combinations are to be viewed as being within the ambit of the inventive concept.
This application is a continuation of U.S. application Ser. No. 16/153,462, filed Oct. 5, 2018, which claims the benefit of U.S. application Ser. No. 15/300,915, filed Sep. 30, 2016, now U.S. Pat. No. 10,117,080, which is a 35 U.S.C. 371 national stage application of International Application No. PCT/2015/024024 filed Apr. 2, 2015, which claims the benefit of U.S. Provisional Application No. 61/974,381, filed Apr. 2, 2014, all of which are incorporated by reference in their entirety herein.
Number | Name | Date | Kind |
---|---|---|---|
5376778 | Kreft | Dec 1994 | A |
5898370 | Reymond | Apr 1999 | A |
5929760 | Monahan | Jul 1999 | A |
6176425 | Harrison | Jan 2001 | B1 |
6641036 | Kalinowski | Nov 2003 | B1 |
6680675 | Suzuki | Jan 2004 | B1 |
6888509 | Atherton | May 2005 | B2 |
6894660 | Sanogo | May 2005 | B2 |
6946951 | Cole | Sep 2005 | B2 |
6992567 | Cole | Jan 2006 | B2 |
7088248 | Forster | Aug 2006 | B2 |
7170415 | Forster | Jan 2007 | B2 |
7187267 | Cole | Mar 2007 | B2 |
7187288 | Mendolia | Mar 2007 | B2 |
7205896 | Wu | Apr 2007 | B2 |
7221259 | Cole | May 2007 | B2 |
7253734 | Moskowitz | Aug 2007 | B2 |
7410103 | Nagel | Aug 2008 | B2 |
7413124 | Frank | Aug 2008 | B2 |
7432817 | Phipps | Oct 2008 | B2 |
7528726 | Lee | May 2009 | B2 |
7557713 | Cox | Jul 2009 | B2 |
7576655 | Liu | Aug 2009 | B2 |
7589635 | Liu | Sep 2009 | B2 |
7592915 | Liu | Sep 2009 | B2 |
7633394 | Forster | Dec 2009 | B2 |
7642916 | Phipps | Jan 2010 | B2 |
7642917 | Tran | Jan 2010 | B2 |
7762472 | Kato | Jul 2010 | B2 |
7796041 | Petropoulos | Sep 2010 | B2 |
7800497 | Marusak | Sep 2010 | B2 |
7812729 | Copeland | Oct 2010 | B2 |
7823269 | Martin | Nov 2010 | B2 |
7880620 | Hatori | Feb 2011 | B2 |
7973662 | Phipps | Jul 2011 | B2 |
7991655 | Sacks | Aug 2011 | B1 |
7999751 | Iliev | Aug 2011 | B2 |
8063779 | Coveley | Nov 2011 | B2 |
8169318 | Atherton | May 2012 | B2 |
8258958 | Kang | Sep 2012 | B2 |
8286884 | Wilkinson | Oct 2012 | B2 |
8286887 | Wilkinson | Oct 2012 | B2 |
8410937 | Collins | Apr 2013 | B2 |
8427316 | Bielas | Apr 2013 | B2 |
8505829 | Wilkinson | Aug 2013 | B2 |
8544758 | Wilkinson | Oct 2013 | B2 |
8669915 | Wilkinson | Mar 2014 | B2 |
8854212 | Goidas | Oct 2014 | B2 |
8857724 | Wilkinson | Oct 2014 | B2 |
8857725 | Wilkinson | Oct 2014 | B2 |
9230145 | Jones | Jan 2016 | B2 |
9251488 | Jones | Feb 2016 | B2 |
9697711 | McIntosh | Jul 2017 | B2 |
1011708 | Wilkinson | Oct 2018 | A1 |
1044823 | Wilkinson | Oct 2019 | A1 |
20020044058 | Heinrich | Apr 2002 | A1 |
20030025636 | Chen | Feb 2003 | A1 |
20040046643 | Becker | Mar 2004 | A1 |
20050057341 | Roesner | Mar 2005 | A1 |
20050110674 | Mendolia | May 2005 | A1 |
20060065709 | Yamashita | Mar 2006 | A1 |
20060145710 | Puleston | Jul 2006 | A1 |
20060158311 | Hall | Jul 2006 | A1 |
20060187060 | Colby | Aug 2006 | A1 |
20060244608 | Cox | Nov 2006 | A1 |
20070026764 | Green | Feb 2007 | A1 |
20070096915 | Forster | May 2007 | A1 |
20070164868 | Deavours | Jul 2007 | A1 |
20070224939 | Jung | Sep 2007 | A1 |
20070290856 | Martin | Dec 2007 | A1 |
20080018431 | Turner | Jan 2008 | A1 |
20080048834 | Lenevez | Feb 2008 | A1 |
20080088459 | Martin | Apr 2008 | A1 |
20080094181 | Lenevez | Apr 2008 | A1 |
20080116256 | Martin | May 2008 | A1 |
20080129512 | Bielas | Jun 2008 | A1 |
20080129513 | Bielas | Jun 2008 | A1 |
20080201388 | Wood | Aug 2008 | A1 |
20080297349 | Leone | Dec 2008 | A1 |
20090008460 | Kato | Jan 2009 | A1 |
20090015480 | Shafer | Jan 2009 | A1 |
20090027208 | Martin | Jan 2009 | A1 |
20090066516 | Lazo | Mar 2009 | A1 |
20090102653 | McGinnis | Apr 2009 | A1 |
20090108993 | Forster | Apr 2009 | A1 |
20090206995 | Forster | Aug 2009 | A1 |
20090256680 | Kilian | Oct 2009 | A1 |
20090265106 | Bearman | Oct 2009 | A1 |
20100001079 | Martin | Jan 2010 | A1 |
20100045025 | Cote | Feb 2010 | A1 |
20100060425 | Rodriguez | Mar 2010 | A1 |
20100079245 | Perng | Apr 2010 | A1 |
20100079287 | Forster | Apr 2010 | A1 |
20100116365 | McCarty | May 2010 | A1 |
20100141386 | Kim | Jun 2010 | A1 |
20100201519 | Dagher | Aug 2010 | A1 |
20100230500 | Wilkinson | Sep 2010 | A1 |
20100277319 | Goidas | Nov 2010 | A1 |
20100277320 | Gold | Nov 2010 | A1 |
20110012713 | Wilkinson | Jan 2011 | A1 |
20110063113 | Hook | Mar 2011 | A1 |
20110282476 | Hegemier | Nov 2011 | A1 |
20110285507 | Nelson | Nov 2011 | A1 |
20110298591 | Mickle | Dec 2011 | A1 |
20120013440 | VonBose | Jan 2012 | A1 |
20120013441 | Ulrich | Jan 2012 | A1 |
20120050011 | Forster | Mar 2012 | A1 |
20120086553 | Wilkinson | Apr 2012 | A1 |
20120155349 | Bajic | Jun 2012 | A1 |
20120212327 | Torabi | Aug 2012 | A1 |
20120217307 | Martin | Aug 2012 | A1 |
20120274449 | Wilkinson | Nov 2012 | A1 |
20130040570 | Wilkinson | Feb 2013 | A1 |
20130043308 | Wilkinson | Feb 2013 | A1 |
20130206846 | Wilkinson | Aug 2013 | A1 |
20130299583 | Wilkinson | Nov 2013 | A1 |
20140144986 | Forster | May 2014 | A1 |
20140266632 | Jones | Sep 2014 | A1 |
20140279294 | Field-Darragh | Sep 2014 | A1 |
20140320265 | Jones | Oct 2014 | A1 |
20140320271 | Jones | Oct 2014 | A1 |
20150102903 | Wilkinson | Apr 2015 | A1 |
20170019754 | Wilkinson | Jan 2017 | A1 |
20190053025 | Wilkinson | Feb 2019 | A1 |
Number | Date | Country |
---|---|---|
101021894 | Aug 2007 | CN |
101076644 | Nov 2007 | CN |
2481156 | Dec 2011 | GB |
2004046904 | Feb 2004 | JP |
2008158569 | Jul 2008 | JP |
2008162120 | Jul 2008 | JP |
2009049763 | Mar 2009 | JP |
200412323 | Mar 2006 | KR |
20070026388 | Mar 2007 | KR |
2005073937 | Aug 2005 | WO |
2009018271 | Feb 2009 | WO |
2010104991 | Sep 2010 | WO |
2015153852 | Oct 2015 | WO |
Entry |
---|
Armstrong, Shain; “Understanding EPC Gen 2 Search Modes and Sessions”; http://blog.atlasrfidstore.com/understanding-epc-gen-2-search-modes-and-sessions; Dec. 19, 2011; pp. 1-9. |
EPCglobal; ‘EPC(TM) Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz Version 1.0.9;’ Specification for RFID Air Interface by EPCglobal Inc.; 94 pages, Jan. 2005. |
Impinj; UHF Gen 2 RFID Tag Antenna Designs; 2008, Impinj, Inc.; pp. 1-4. |
Khan, Goh Chean.; “Near-Field UHF RFID Antenna Design”; Department of Electrical and Computer Engineering; National University of Singapore; Thesis submitted 2009; pp. 1-215. |
Liu, Zhong-Min and Raymond R. Hillegass.; “A 3 Patch Near Field Antenna for Conveyor Bottom Read in RFID Sortation Application”; IEEE; Jul. 2006; pp. 1043-1046. |
Nikitin et al.; An Overview of Near Field UHF RFID; Feb. 2007; 8 pages; IEEE. |
PCT; App. No. PCT/US2015/024024; International Search Report and Written Opinion dated Jul. 8, 2015. |
RFIDSOUP.com; RFID Soup; Mar. 6, 2009; 12 pages; published at http://rfidsoup.pbwiki.com. |
Swedberg, Claire; RFID Puts Salt Lake City Drivers in the Fast Lane; RFID Journal; Oct. 1, 2010; 5 pages; published at http://www.rfidjournal.com/article/view/7907. |
tagsense.com, TagSene Frequently Asked Questions; Mar. 6, 2009; 3 pages; published at www.tagsense.com/ingles/faq/faq.html. |
Tagsys; AK Product Datasheet; Dec. 19, 2012; 1 page; published at www.tagsysrfid.com/products-services/rfid-tags/ak. |
Tagsys; AK Product Datasheet; Feb. 14, 2010; 1 page; published at webarchive.org/web/20100214004043/http://www.tagsysrfid.com/products-services/rfid-tags/ak. |
Tagsys; AK5 Converted Product Specification; Oct. 2012; 2 pages; published at www.tagsysrfid.com. |
Tagsys; AKTag UHF Tag Datasheet; Nov. 23, 2012; 2 pages; published at www.tagsysrfid.com. |
Tagsys; UHF AK Tag; Sep. 2008; 2 pages; published at www.tagsysrfid.com. |
technovelgy.com; Passive RFID Tag (or Passive Tag); Mar. 5, 2009, 5 pages; published at www.technovelgy.com. |
U.S. Appl. No. 15/300,915; Notice of Allowance dated Jun. 28, 2018; (pp. 1-7). |
U.S. Appl. No. 15/300,915; Office Action dated Dec. 6, 2017; (pp. 1-19). |
U.S. Appl. No. 16/153,462; Notice of Allowance dated Jun. 3, 2019; (pp. 1-7). |
Wikipedia; RFID; Mar. 6, 2009; 2 pages; published at http://rfidsoup.pbwiki.com. |
UKIPO; App. No. 1615898.2; Office Action dated May 27, 2020; (pp. 1-6). |
Number | Date | Country | |
---|---|---|---|
20200015055 A1 | Jan 2020 | US |
Number | Date | Country | |
---|---|---|---|
61974381 | Apr 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16153462 | Oct 2018 | US |
Child | 16573777 | US | |
Parent | 15300915 | US | |
Child | 16153462 | US |