Patent Description:
The present disclosure relates generally to Electronic Article Surveillance (EAS). Examples related to EAS using a Radio Frequency Identification (RFID) tag.

The document <CIT> relates to a method for detecting proximity of an electronic article surveillance (EAS) tag. A proximity detection system detects a presence of an object within a first area. In response to detecting the proximity of the object, an EAS tag reader alters characteristics of an EAS tag detection signal that is produced by the EAS tag reader in order to detect an EAS tag within range of the EAS tag reader.

The document <CIT> relates to an RFID loss-prevention system (LPS) based on based on synthesized-beam readers (SBRs). The RFID loss-prevention system permits authorized items to leave a facility and may perform a security action if an unauthorized item leaves the facility.

Electronic article surveillance (EAS) systems are used to control inventory and to prevent or deter theft or unauthorized removal of articles from a controlled area. Such systems establish an electromagnetic field or "interrogation zone" that defines a surveillance zone (for example, entrances and/or exits in retail stores) encompassing the controlled area. The articles to be protected are tagged with an EAS security tag. Tags are designed to interact with the field in the interrogation zone. e.g., established by an EAS portal. The EAS portal includes one or more EAS readers (e.g., transmitter/receiver, antennas), and an EAS detection module/controller. The presence of a tag in the interrogation zone is detected by the system and appropriate action is taken. In most cases, the appropriate action includes the activation of an alarm.

In the retail industry, it is common to "source tag" articles with RFID tags, either at the time of packaging/manufacture, or at some other point in the in the supply chain. At the same time, EAS technology and devices have proven critical to the reduction of theft and so called "shrinkage. " Since many articles arrive at the retailer with RFID tags, it is desirable that RFID tag be used also to provide EAS functionality in addition to their intended function of providing capabilities such as inventory control, shelf reading, non-line of sight reading, etc..

In some implementations, an RFID tag can be used to simulate EAS functionality by sending special codes when a reader interrogates the RFID tag. This arrangement advantageously eliminates the need for a separate EAS component, such an acousto-magnetic (AM) component, within the tag, or a separate EAS tag. Various schemes can be used to enable the use of RFID tags to simulate EAS functionality. In some such systems, the RFID tag indicates in some way that the item to which the tag is attached has been purchased at point of sale (POS). If the RFID tag is a detachable tag, the RFID tag can be simply detached at the point of sale. In such a system, the RFID readers at the exit would trigger an alarm if any tags are detected. In some such systems, data is written to the RFID chip at the POS to confirm the item was purchased. One common method is encoding a bit-flip at the POS, with the changed bit indicating that the item is authorized for removal. Other systems may read a unique ID from the tag, and store the unique ID in the enterprise system when the tagged item is purchased, so that the purchase can be verified by RFID readers as the tag exits the premises. If the purchase of the item cannot be verified based on tag data when the tag passes out of the store, an alarm can be triggered.

The present invention relates to a method of electronic article surveillance according to independent claim <NUM>, as well as to a electronic article surveillance system according to independent claim <NUM>, wherein further developments of the inventive method and the inventive system are provided in the sub-claims, respectively.

This summary is not an extensive overview of all contemplated aspects and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects.

Examples of the technology disclosed herein include methods, systems, and apparatuses of electronic article surveillance (EAS). In some examples, an RFID portal of an EAS system first interrogates in a first zone extending into a controlled area beyond a threshold distance from an interrogating antenna of the RFID portal. The RFID portal defines an exit from the controlled area, the threshold distance being less than a width of the exit. The RFID portal first detects, in response to the first interrogating, a first response of a particular RFID tag. The RFID portal second interrogate, subsequent to the first detecting, in a second zone extending into the controlled area at least to the threshold distance. The RFID portal second detects, in response to the second interrogating, at least one second response of the particular RFID tag indicating a received signal strength of the second interrogating at the particular RFID tag corresponding to a distance from an interrogating antenna of the RFID portal less than the threshold distance. The EAS system alarms in response to the second detecting.

In some examples, first detecting includes determining, by the EAS system, that the particular tag is moving in a direction exiting the controlled area. In such examples, second interrogating is in response to the first detecting. In some examples, alarming includes displaying information relating to at least one of: the particular RFID tag, and an article associated with the particular RFID tag. In some such examples, displaying includes displaying on one of the RFID portal or a mobile communication device.

In some examples, indicating a received signal strength comprises responding with a received signal strength indicator (RSSI). In some examples, the threshold distance is no greater than one foot, in others the threshold distance is no greater than two feet. In some examples, the EAS system receives, prior to the first interrogating, selection of the threshold distance. In some examples, the first interrogating is multi-session interrogating during which the particular RFID tag would not be guaranteed to respond to a subsequent interrogation.

In such examples, the second interrogating includes interrogating in which all RFID tags within the threshold distance are allowed to respond. In some examples, the second detecting includes at least a predetermined threshold number, greater than one, of second responses. In some examples, the alarming further requires an indication of at least one person in the exit concurrent with the first detecting.

The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the present solution is indicated by the appended claims rather than by this detailed description.

Furthermore, the described features, advantages, and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize, in light of the description herein, that the present solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.

Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the indicated embodiment is included in at least one embodiment of the present solution. Thus, the phrases "in one embodiment", "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

As used in this document, the singular form "a," "an," and "the" include plural references unless the context clearly dictates otherwise. As used in this document, the term "comprising" means "including, but not limited to.

Currently, using RFID as an EAS exit solution is limited by stray or reflected alarms when transmission powers are increased. People walking through the EAS portal may trigger alarms even if they are not removing articles from the premises without authorization. Alarms can be caused by stationary RFID tags located some distance from the exit. Further, such an approach limits the ability for the retailer to place articles too close to an EAS portal due to false alarms. The large read ranges of the RFID technology coupled with RF reflections makes it very difficult to control the RFID system's detection area at the exit from the controlled area.

In real-world environments, with changing RF reflections may be subject to constant change to store fixtures, furniture, support columns, doors, customers in motion, shopping carts etc. These types of systems sometimes have a hard time properly discriminating between actual tags that are read outside (or detected going outside), and tags on items properly inside the store that are falsely read outside due to RF reflections, multipath/backscattering, or missed inventory attempts due to temporary interferers.

As RFID transmission levels are increased in a RFID-as-EAS system, the number of false alarms caused by stray or reflected may also increase, which can compromise the accuracy and effectiveness of the system. With increased transmission power levels, people walking through the EAS portal may appear to be triggering alarms, even if they are not trying to remove articles from the premises without authorization. These false alarms can be triggered by stationary RFID tags located some distance from the exit, not the person exiting the store.

Further, there are situations in which human judgment is useful to determine if am RFID-as-EAS alarm is indicative of theft, or if the alarms is simply a false alarm. Typically, a retail store will station human guard or monitor at the point of exit to interact with customers exiting the store, and this the human guard or monitor is tasked with providing the last line of defense against theft. If there is an alarm caused by detection of an unauthorized RFID tag, the guard must quickly determine what articles may have been stolen, and by which people. This can be difficult in crowded, fast-moving situations.

Typically, the guard/monitor takes into account that there may be a case of a false alarm as can occur when the detected tag is on an article inside the store and there is no actual theft. In this case, the retail store would not want a guard to detain unfairly a customer who has properly purchased their article in an attempt to determine if they have stolen the article.

Another challenge for the guard or monitor is when multiple people are near the exit gate. If more than one customer is traveling through or near the exit gate and an alarm is triggered, the guard or monitor typically attempts to determine, quickly and accurately, which customer/person could be stealing an article. In order to help the guard, make this decision it would be useful for the EAS system to supply more information than just sounding the alarm, preferably communicating to the guard or monitor in close to real time.

Examples of the technology disclosed herein can provide for the near real-time collection/display of additional data that is related to the detection of an unauthorized RFID tag moving through an RFID exit portal in near real-time, where such additional data is can be used to determine a probability that the detection of the tag indicates theft. In another aspect of the technology disclosed herein, solutions are disclosed wherein the RFID detection system is adapted to alarm based on logic that appears (to the guard) similar to the logic used in AM EAS systems, thus making it easier for a guard or monitor stationed at the scene to determine if a theft is in progress. In another aspect of the invention, examples of the technology disclosed herein provide a directive to the guard or human monitor to indicate that a person should be intercepted and questioned before they reach the exit.

These and other features of the present disclosure are discussed in detail below with regard to FIGS. <NUM>-<NUM>.

Referring now to <FIG>, there is provided a schematic illustration of an illustrative system <NUM> that is useful for understanding the present solution. The present solution is described herein in relation to a retail store environment. The present solution is not limited in this regard, and can be used in other environments. For example, the present solution can be used in distribution centers, factories and other commercial environments. Notably, the present solution can be employed in any environment in which objects and/or items/articles need to be located and/or tracked.

The system <NUM> is generally configured to allow (a) improved inventory counts and surveillance of objects and/or items/articles located within a facility, and (b) improved customer experiences. As shown in <FIG>, system <NUM> comprises a Retail Store Facility ("RSF") <NUM> in which display equipment <NUM><NUM>-<NUM>M is disposed. The display equipment is provided for displaying objects (or items/articles) <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X to customers of the retail store. The display equipment can include, but is not limited to, shelves, article display cabinets, promotional displays, fixtures, and/or equipment se-curing areas of the RSF <NUM>. The RSF <NUM> can also include emergency equipment (not shown), checkout counters, and other equipment and fixtures typical for the facility type. Emergency equipment, checkout counters, video cameras, people counters, and conventional EAS systems are well known in the art, and therefore may not be described at a sufficient level of detail herein for understanding of the claimed invention.

At least one tag reader <NUM> is provided to assist in counting and tracking locations the articles <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X within the RSF <NUM>. The tag reader <NUM> comprises an RFID reader configured to read RFID tags. RFID readers are well known in the art, and therefore will be described at a sufficient level of detail herein for understanding of the claimed invention.

RFID tags <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X (hereinafter "<NUM>," generally) are respectively attached or coupled to the articles <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X (hereinafter "<NUM>," generally). This coupling can be achieved via an adhesive (e.g., glue, tape, or sticker), a mechanical coupler (e.g., straps, clamps, snaps, etc.), a weld, chemical bond, or other means. The RFID tags <NUM> can alternatively or additionally comprise dual-technology tags that have both EAS and RFID capabilities as described herein.

Notably, the tag reader <NUM> is strategically placed at a known location within the RSF <NUM>, for example, at an exit/entrance. By correlating the tag reader's RFID tag reads and the tag reader's known location within the RSF <NUM> it is possible to determine the general location of articles <NUM> within the RSF <NUM>. The tag reader's known coverage area also facilitates article <NUM> location determinations. Accordingly, RFID tag read information and tag reader <NUM> location information is stored in a datastore <NUM>. This information can be stored in the datastore <NUM> using a server <NUM> and network <NUM> (e.g., an Intranet and/or Internet).

System <NUM> also comprises a Mobile Communication Device ("MCD") <NUM>. MCD <NUM> includes, but is not limited to, a cell phone, a smart phone, a table computer, a personal digital assistant, and/or a wearable device (e.g., a smart watch). Each of the listed devices is well known in the art, and therefore will not be described herein. In accordance with some examples, the MCD <NUM> has a software application installed thereon that is operative to: facilitate the provision of various information <NUM>-<NUM> to the individual <NUM>; facilitate a purchase transaction; and/or facilitate the detachment of the RFID tags <NUM> from the articles <NUM>; and/or facilitate the detachment of an anchored chain or cable from the articles <NUM>.

The MCD <NUM> is generally configured to provide a visual and/or auditory output of item/article level information <NUM>, accessory information <NUM>, related product information <NUM>, discount information <NUM>, and/or customer related information <NUM>. The item level information includes, but is not limited to, an item description, item nutritional information, a promotional message, an item regular price, an item sale price, a currency symbol, and/or a source of the item.

An accessory includes, but is not limited to, a useful auxiliary item that can be attached to or removed from an item/article (e.g., a drill bit or battery of a drill). The accessory information includes, but is not limited to, an accessory description, accessory nutritional information, a promotional message, an accessory regular price, an accessory sale price, a currency symbol, a source of the accessory, and/or an accessory location in the facility.

A related product includes, but is not limited to, a product/article that can be used in conjunction with or as an alternative to another product/article (e.g., diaper rash cream which can be used when changing a diaper, or a first diaper can be used as an alternative to another diaper). The related product information includes, but is not limited to, a related product description, related product nutritional information, a promotional message, a related product regular price, a related product sale price, a currency symbol, a source of the related product, and/or a related product location in the facility.

The discount information can include, but is not limited to, a discount price for an article/product based on a loyalty level or other criteria. The customer related information includes, but is not limited to, customer account numbers, customer identifiers, usernames, passwords, payment information, loyalty levels, historical purchase information, and/or activity trends.

The item level information, accessory information, related product information and/or discount information can be output in a format selected from a plurality of formats based on a geographic location of the item/article <NUM>, a location of the MCD, a date, and/or an item pricing status (i.e., whether the item/article is on sale). In a display context, the format is defined by a font parameter, a color parameter, a brightness parameter, and/or a display blinking parameter. In an auditory context, the format is defined by a volume parameter, a voice tone parameter, and/or a male/female voice selected parameter.

The MCD <NUM> can also be configured to read barcodes and/or RFID tags <NUM>. Information obtained from the barcode and/or RFID tag reads may be communicated from the MCD <NUM> to the server <NUM> via network <NUM>. Similarly, the stored information <NUM>-<NUM> is provided from the server <NUM> to the MCD <NUM> via network <NUM>. The network <NUM> includes an Intranet and/or the Internet.

Server <NUM> can be local to the facility <NUM> as shown in <FIG> or remote from the facility <NUM>. Server <NUM> will be described in more detail below in relation to <FIG>. Still, it should be understood that server <NUM> is configured to: write data to and read data from datastore <NUM>, RFID tags <NUM>, and/or MCD <NUM>; perform language and currency conversion operations using item level information and/or accessory information obtained from the datastore, RFID tags <NUM>, and/or MCD; perform data analytics based on inventory information, tag read information, MCD tracking information, and/or information <NUM>-<NUM>; perform image processing using images captured by camera(s) <NUM>; and/or determine locations of RFID tags <NUM> and/or MCDs in the RSF <NUM> using beacon(s) <NUM>, tag reader <NUM> or other devices having known locations and/or antenna patterns.

In some examples, one or more beacons <NUM> transmitting an RF signal (second RF signal that is non-RFID) other than the RFID interrogation signal are placed to cover a zone of interest also covered by a tag reader <NUM> placed to cover an RFID interrogation zone, e.g., at a portal of the retail facility <NUM>. The system <NUM> can detect and derive any number of relevant indicators based on second RF signal. The tag <NUM> response to the second RF signal is analyzed and compared to data collected by the RFID signal response that occurred concurrently with tag <NUM> passage through the portal.

The server <NUM> facilitates updates to the information <NUM>-<NUM> output from the MCD <NUM>. Such information updating can be performed periodically, in response to instructions received from an associate (e.g., a retail store employee <NUM>), in response to a detected change in the item level, accessory and/or related product information, in response to a detection that an individual is in proximity to an RFID tag <NUM>, and/or in response to any motion or movement of the RFID tag <NUM>. For example, if a certain product/article is placed on sale, then the sale price for that product/article is transmitted to MCD <NUM> via network <NUM> and/or RFID tag <NUM>. The sale price is then output from the MCD <NUM>. The present solution is not limited to the particulars of this example.

Although a single MCD <NUM> and/or a single server <NUM> are shown in <FIG>, the present solution is not limited in this regard. It is contemplated that more than one computing device can be implemented. In addition, the present solution is not limited to the illustrative system architecture de-scribed in relation to <FIG>.

During operation of system <NUM>, the content displayed on the display screen of the MCD <NUM> is dynamically controlled based upon various tag <NUM> or item <NUM> related information and/or customer related information (e.g., mobile device identifier, mobile device <NUM> location in RSF <NUM>, and/or customer loyalty level). Tag <NUM> or item level information includes, but is not limited to, first information indicating that an RFID tag <NUM> is in motion or that an article <NUM> is being handled by an individual <NUM>, second information indicating a current location of the RFID tag <NUM> and/or the MCD <NUM>, third information indicating an accessory or related product of the article <NUM> to which the moving RFID tag <NUM> is coupled, and/or fourth information indicating the relative locations of the accessory and the moving RFID tag <NUM> and/or the relative locations of the related article <NUM> and the moving RFID tag <NUM>. The first, second and fourth information can be derived based on sensor data generated by sensors local to the RFID tag <NUM>. Accordingly, the RFID tags <NUM> include one or more sensors to detect their current locations, detect any individual in proximity thereto, and/or detect any motion or movement thereof. The sensors include, but are not limited to, an Inertial Measurement Unit ("IMU"), a vibration sensor, a light sensor, an accelerometer, a gyroscope, a proximity sensor, a microphone, and/or a beacon communication device. The third information can be stored local to the RFID tags <NUM> or in a remote datastore <NUM> as information <NUM>, <NUM>.

In some scenarios, the MCD <NUM> facilitates the server's <NUM> (a) detection of when the individual <NUM> enters the RSF <NUM>, (b) tracking of the individual's movement through the RSF, (c) detection of when the individual is in proximity to an article <NUM> to which an RFID tag <NUM> is coupled, (d) determination that an RFID tag <NUM> is being handled or moved by the individual <NUM> based on a time stamped pattern of MCD movement and a timestamped pattern of RFID tag <NUM> movement, and/or (e) determination of an association of moving RFID tags <NUM> and the individual <NUM>.

When a detection is made that an RFID tag <NUM> is being moved, the server <NUM> can, in some scenarios, obtain customer related information (such as a loyalty level) <NUM> associated with the individual. This information can be obtained from the individual's MCD <NUM> and/or the datastore <NUM>. The customer related information <NUM> is then used to retrieve discount information <NUM> for the article <NUM> to which the RFID tag <NUM> is coupled. The retrieved discount information is then communicated from the server <NUM> to the individual's MCD <NUM>. The individual's MCD <NUM> can output the discount information in a visual format and/or an auditory format. Other information may also be communicated from the server <NUM> to the individual's MCD <NUM>. The other information includes, but is not limited to, item level information, accessory information, and/or related product information.

In those or other scenarios, a sensor embedded in the RFID tag <NUM> detects when an individual is handling the article <NUM> to which the RFID tag <NUM> is coupled. When such a detection is made, the RFID tag <NUM> retrieves the object's unique identifier from its local memory, and wirelessly communicates the same to the tag reader <NUM>. The tag reader <NUM> then passes the information to the server <NUM>. The server <NUM> uses the object's unique identifier and the item/accessory relationship information (e.g., table) <NUM> to determine if there are any accessories associated therewith. If no accessories exist for the article <NUM>, the server <NUM> uses the item level information <NUM> to determine one or more characteristics of the article <NUM>. For example, the article <NUM> includes a product of a specific brand. The server <NUM> then uses the item/related product information (e.g., table) <NUM> to identify: other products of the same type with the same characteristics; and/or other products that are typically used in conjunction with the object. Related product information for the identified related products is then retrieved and provided to the MCD <NUM>. The MCD <NUM> can output the related product information in a visual format and/or an auditory format. The individual <NUM> can perform user-software interactions with the MCD <NUM> to obtain further information obtain the related product of interest. The present solution is not limited to the particulars of this scenario.

Referring now to <FIG>, there is an illustration of an illustrative architecture for a tag <NUM>. RFID tags <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X are the same as or similar to tag <NUM>. As such, the discussion of tag <NUM> is sufficient for understanding the RFID tags <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X of <FIG>. Tag <NUM> is generally configured to perform operations to (a) minimize power usage so as to extend a power source's life (e.g., a battery or a capacitor), (b) minimize collisions with other tags so that the tag of interest can be seen at given times, (c) optimize useful information within an inventory system (e.g., communicate useful change information to a tag reader), and/or (d) optimize local feature functions.

The tag <NUM> can include more or less components than that shown in <FIG>. However, the components shown are sufficient to disclose an illustrative embodiment implementing the present solution. Some or all of the components of the tag <NUM> can be implemented in hardware, software and/or a combination of hardware and software. The hardware includes, but is not limited to, one or more electronic circuits. The electronic circuit(s) may comprise passive components (e.g., capacitors and resistors) and active components (e.g., processors) arranged and/or programmed to implement the methods disclosed herein.

The hardware architecture of <FIG> represents a representative tag <NUM> configured to facilitate improved inventory management/surveillance and customer experience. In this regard, the tag <NUM> is configured for allowing data to be exchanged with an external device (e.g., tag reader <NUM> of <FIG>, a beacon <NUM> of <FIG>, a Mobile Communication Device ("MCD") <NUM> of <FIG>, and/or server <NUM> of <FIG>) via wireless communication technology. The wireless communication technology can include, but is not limited to, a Radio Frequency Identification ("RFID") technology, a Near Field Communication ("NFC") technology, and/or a Short Range Communication ("SRC") technology. For example, one or more of the following wireless communication technologies are employed: Radio Frequency ("RF") communication technology; Bluetooth technology (including Bluetooth Low Energy (LE)); WiFi technology; beacon technology; and/or LiFi technology. Each of the listed wireless communication technologies is well known in the art, and therefore will not be described in detail herein. Any known or to be known wireless communication technology or other wireless communication technology can be used herein without limitation.

The components <NUM>-<NUM> shown in <FIG> may be collectively referred to herein as a communication enabled device <NUM>, and include a memory <NUM> and a clock/timer <NUM>. Memory <NUM> may be a volatile memory and/or a non-volatile memory. For example, the memory <NUM> can include, but is not limited to, Random Access Memory ("RAM"), Dynamic RAM ("DRAM"), Static RAM ("SRAM"), Read Only Memory ("ROM"), and flash memory. The memory <NUM> may also comprise unsecure memory and/or secure memory.

In some scenarios, the communication enabled device <NUM> comprises a Software Defined Radio ("SDR"). SDRs are well known in the art, and therefore will not be described in detail herein. However, it should be noted that the SDR can be programmatically assigned any communication protocol that is chosen by a user (e.g., RFID, WiFi, LiFi, Bluetooth, BLE, Nest, ZWave, Zigbee, etc.). The communication protocols are part of the device's firmware and reside in memory <NUM>. Notably, the communication protocols can be downloaded to the device at any given time. The initial/default role (being an RFID, WiFi, LiFi, etc. tag) can be assigned at the deployment thereof. If the user desires to use another protocol later, the user can remotely change the communication protocol of the deployed tag <NUM>. The update of the firmware, in case of issues, can also be performed remotely.

As shown in <FIG>, the communication enabled device <NUM> comprises at least one antenna <NUM>, <NUM> for allowing data to be exchanged with the external device via a wireless communication technology (e.g., an RFID technology, an NFC technology, a SRC technology, and/or a beacon technology). The antenna <NUM>, <NUM> is configured to receive signals from the external device and/or transmit signals generated by the communication enabled device <NUM>. The antenna <NUM>, <NUM> can comprise a near-field or far-field antenna. The antennas include, but are not limited to, a chip antenna or a loop antenna.

The communication enabled device <NUM> also comprises a communication device (e.g., a transceiver or transmitter) <NUM>. Communication devices (e.g., transceivers or transmitters) are well known in the art, and therefore will not be described herein. However, it should be understood that the communication device <NUM> generates and transmits signals (e.g., RF carrier signals) to external devices, as well as receives signals (e.g., RF signals) transmitted from external devices. In this way, the communication enabled device <NUM> facilitates the registration, identification, and location and/or tracking of an item (e.g., article <NUM> or <NUM> of <FIG>) to which the tag <NUM> is coupled.

The communication enabled device <NUM> is configured so that it: communicates (transmits and receives) in accordance with a time slot communication scheme; and selectively enables/disables/bypasses the communication device (e.g., transceiver) or at least one communications operation based on output of a motion sensor <NUM>. In some scenarios, the communication enabled device <NUM> selects: one or more time slots from a plurality of time slots based on the tag's unique identifier <NUM> (e.g., an Electronic Product Code ("EPC")); and/or determines a Window Of Time ("WOT") during which the communication device (e.g., transceiver) <NUM> is to be turned on or at least one communications operation is be enabled subsequent to when motion is detected by the motion sensor <NUM>. The WOT can be determined based on environmental conditions (e.g., humidity, temperature, time of day, relative distance to a location device (e.g., beacon or location tag), etc.) and/or system conditions (e.g., amount of traffic, interference occurrences, etc.). In this regard, the tag <NUM> can include additional sensors not shown in <FIG>.

The communication enabled device <NUM> also facilitates the automatic and dynamic modification of item level information <NUM> that is being or is to be output from the tag <NUM> in response to certain trigger events. The trigger events can include, but are not limited to, the tag's arrival at a particular facility (e.g., RSF <NUM> of <FIG>), the tag's arrival in a particular country or geographic region, a date occurrence, a time occurrence, a price change, and/or the reception of user instructions.

Item level information <NUM> and a unique identifier ("ID") <NUM> for the tag <NUM> can be stored in memory <NUM> of the communication enabled device <NUM> and/or communicated to other external devices (e.g., tag reader <NUM> of <FIG> or <NUM> of <FIG> described below, beacon <NUM> of <FIG>, MCD <NUM> of <FIG>, and/or server <NUM> of <FIG>) via communication device (e.g., transceiver) <NUM> and/or interface <NUM> (e.g., an Internet Protocol or cellular network interface). For example, the communication enabled device <NUM> can communicate information specifying a timestamp, a unique identifier for an item/article <NUM>, item description, item price, a currency symbol and/or location information to an external device. The external device (e.g., server <NUM>, <NUM> or MCD <NUM>) can then store the information in a database (e.g., database <NUM> of <FIG>) and/or use the information for various purposes.

The communication enabled device <NUM> also comprises a controller <NUM> (e.g., a CPU) and in-put/output devices <NUM>. The controller <NUM> can execute instructions <NUM> implementing methods for facilitating inventory counts and management. In this regard, the controller <NUM> includes a processor (or logic circuitry that responds to instructions) and the memory <NUM> includes a computer-readable storage medium on which is stored one or more sets of instructions <NUM> (e.g., software code) configured to implement one or more of the methodologies, procedures, or functions described herein. The instructions <NUM> can also reside, completely or at least partially, with-in the controller <NUM> during execution thereof by the tag <NUM>. The memory <NUM> and the controller <NUM> also can constitute machine-readable media. The term "machine-readable media," as used here, refers to a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions <NUM>. The term "machine-readable media," as used here, also refers to any medium that is capable of storing, encoding, or carrying a set of instructions <NUM> for execution by the tag <NUM> and that cause the tag <NUM> to perform any one or more of the methodologies of the present disclosure.

The input/output devices <NUM> can include, but are not limited to, a display (e.g., an E Ink display, an LCD display, and/or an active matrix display), a speaker, a keypad, and/or light emitting diodes. The display is used to present item level information in a textual format and/or graphical format. Similarly, the speaker may be used to output item level information in an auditory format. The speaker and/or light emitting diodes may be used to output alerts for drawing a person's attention to the tag <NUM> (e.g., when motion thereof has been detected) and/or for notifying the person of a particular pricing status (e.g., on sale status) of the item/article <NUM> to which the tag is coupled.

The clock/timer <NUM> is configured to determine a date, a time, and/or an expiration of a pre-defined period of time. Technique for determining these listed items are well known in the art, and therefore will not be described herein. Any known or to be known technique for determining these listed items can be used herein without limitation.

The tag <NUM> also comprises an optional location module <NUM>. The location module <NUM> is generally configured to determine the geographic location of the tag at any given time. For example, in some scenarios, the location module <NUM> employs Global Positioning System ("GPS") technology and/or Internet based local time acquisition technology. The present solution is not limited to the particulars of this example. Any known or to be known technique for determining a geographic location can be used herein without limitation including relative positioning within a facility or structure.

The optional coupler <NUM> is provided to couple the tag <NUM> securely or removably to an item (e.g., object <NUM> or <NUM> of <FIG>). The coupler <NUM> includes, but is not limited to, a mechanical coupling means (e.g., a strap, clip, clamp, snap) and/or adhesive (e.g., glue or sticker). The coupler <NUM> is optional since the coupling can be achieved via a weld and/or chemical bond.

The tag <NUM> can also include a power source <NUM>, an optional EAS component <NUM>, and/or a passive/active/semi-passive RFID component <NUM>. Each of the listed components <NUM>, <NUM>, <NUM> is well known in the art, and therefore will not be described herein. Any known or to be known battery, EAS component and/or RFID component can be used herein without limitation. The power source <NUM> can include, but is not limited to, a rechargeable battery and/or a capacitor.

As shown in <FIG>, the tag <NUM> further comprises an energy harvesting circuit <NUM> and a power management circuit <NUM> for ensuring continuous operation of the tag <NUM> without the need to change the rechargeable power source (e.g., a battery). In some scenarios, the energy harvesting circuit <NUM> is configured to harvest energy from one or more sources (e.g., heat, light, vibration, magnetic field, and/or RF energy) and to generate a relatively low amount of output power from the harvested energy. By employing multiple sources for harvesting, the device <NUM> can continue to charge despite the depletion of a source of energy. Energy harvesting circuits are well known in the art, and therefore will not be described herein. Any known or to be known energy harvesting circuit <NUM> can be used herein without limitation.

As noted above, the tag <NUM> may also include a motion sensor <NUM>. Motion sensors are well known in the art, and therefore will not be described herein. Any known or to be known motion sensor can be used herein without limitation. For example, the motion sensor <NUM> includes, but is not limited to, a vibration sensor, an accelerometer, a gyroscope, a linear motion sensor, a Passive Infrared ("PIR") sensor, a tilt sensor, and/or a rotation sensor.

The motion sensor <NUM> is communicatively coupled to the controller <NUM> such that it can notify the controller <NUM> when tag motion is detected. The motion sensor <NUM> also communicates sensor data to the controller <NUM>. The sensor data is processed by the controller <NUM> to determine whether the motion is of a type for triggering enablement of the communication device (e.g., transceiver) <NUM> or at least one communications operation. For example, the sensor data can be compared to stored motion/gesture data <NUM> to determine if a match exists there-between. More specifically, a motion/gesture pattern specified by the sensor data can be compared to a plurality of motion/gesture patterns specified by the stored motion/gesture data <NUM>. The plurality of motion/gesture patterns can include, but are not limited to, a motion pattern for walking, a motion pattern for running, a motion pattern for vehicle transport, a motion pattern for vibration caused by equipment or machinery in proximity to the tag (e.g., an air conditioner or fan), a gesture for requesting assistance, a gesture for obtaining additional product information, and/or a gesture for product purchase. The type of movement (e.g., vibration or being carried) is then determined based on which stored motion/gesture data matches the sensor data. This feature allows the tag <NUM> to selectively enable the communication device (e.g., transceiver) or at least one communications operation only when the tag's location within a facility is actually being changed (e.g., and not when a fan is causing the tag to simply vibrate).

In some scenarios, the tag <NUM> can be also configured to enter a sleep state in which at least the motion sensor triggering of communication operations is disabled. This is desirable, for example, in scenarios when the tag <NUM> is being shipped or transported from a distributor to a customer. In those or other scenarios, the tag <NUM> can be further configured to enter the sleep state in response to its continuous detection of motion for a given period of time. The tag <NUM> transition from a sleep state in response to expiration of a defined time period, tag <NUM> reception of a control signal from an external device, and/or tag <NUM> detection of no motion for a period of time.

The power management circuit <NUM> is generally configured to control the supply of power to components of the tag <NUM>. In the event all of the storage and harvesting resources deplete to a point where the tag <NUM> is about to enter a shutdown/brownout state, the power management circuit <NUM> can cause an alert to be sent from the tag <NUM> to a remote device (e.g., tag reader <NUM> or server <NUM> of <FIG>). In response to the alert, the remote device can inform an associate (e.g., a store employee <NUM> of <FIG>) so that (s)he can investigate why the tag <NUM> is not recharging and/or holding charge.

The power management circuit <NUM> is also capable of redirecting an energy source to the tag <NUM> electronics based on the energy source's status. For example, if harvested energy is sufficient to run the tag <NUM> functions, the power management circuit <NUM> confirms that all of the tag <NUM> storage sources are fully charged such that the tag <NUM> electronic components can be run directly from the harvested energy. This ensures that the tag <NUM> has stored energy in case harvesting source(s) disappear or lesser energy is harvested for reasons such as drop in RF, light or vibration power levels. If a sudden drop in any of the energy sources is detected, the power management circuit <NUM> can cause an alert condition to be sent from the tag <NUM> to the remote device (e.g., tag reader <NUM> or server <NUM> of <FIG>). At this point, an investigation may be required as to what caused this alarm. Accordingly, the remote device can inform the associate (e.g., a store employee <NUM> of <FIG>) so that (s)he can investigate the issue. It may be that other merchandise are obscuring the harvesting source or the tagged article <NUM> is being stolen.

The present solution is not limited to that shown in <FIG>. The tag <NUM> can have any architecture provided that it can perform the functions and operations described herein. For example, all of the components shown in <FIG> can comprise a single device (e.g., an Integrated Circuit ("IC")). Alternatively, some of the components can comprise a first tag element (e.g., a Commercial Off The Shelf ("COTS") tag) while the remaining components comprise a second tag element communicatively coupled to the first tag element. The second tag element can provide auxiliary functions (e.g., motion sensing, etc.) to the first tag element. The second tag element may also control operational states of the first tag element. For example, the second tag element can selectively (a) enable and disable one or more features/operations of the first tag element (e.g., transceiver operations), (b) couple or decouple an antenna to and from the first tag element, (c) by-pass at least one communications device or operation, and/or (d) cause an operational state of the first tag element to be changed (e.g., cause transitioning the first tag element between a power save mode and non-power save mode). In some scenarios, the operational state change can be achieved by changing the binary value of at least one state bit (e.g., from <NUM> to <NUM>, or vice versa) for causing certain communication control operations to be performed by the tag <NUM>. Additionally or alternatively, a switch can be actuated for creating a closed or open circuit. The pre-sent solution is not limited in this regard.

Referring now to <FIG>, there is provided a detailed block diagram of an exemplary architecture for a tag reader <NUM>. Tag reader <NUM> of <FIG> is the same as or similar to tag reader <NUM>. As such, the discussion of tag reader <NUM> is sufficient for understanding tag reader <NUM>.

Tag reader <NUM> may include more or less components than that shown in <FIG>. However, the components shown are sufficient to disclose an illustrative embodiment implementing the present solution. Some or all of the components of the tag reader <NUM> can be implemented in hardware, software and/or a combination of hardware and software. The hardware includes, but is not limited to, one or more electronic circuits. The electronic circuit may comprise passive components (e.g., capacitors and resistors) and active components (e.g., processors) arranged and/or programmed to implement the methods disclosed herein.

The hardware architecture of <FIG> represents an illustration of a representative tag reader <NUM> configured to facilitate improved inventory counts and management within an RSF (e.g., RSF <NUM> of <FIG>). In this regard, the tag reader <NUM> comprises an RF enabled device <NUM> for allowing data to be exchanged with an external device (e.g., RFID tags <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X of <FIG>) via RF technology. The components <NUM>-<NUM> shown in <FIG> may be collectively referred to herein as the RF enabled device <NUM>, and may include a power source <NUM> (e.g., a battery) or be connected to an external power source (e.g., an AC mains).

The RF enabled device <NUM> comprises one or more antennas <NUM> for allowing data to be exchanged with the external device via RF technology (e.g., RFID technology or other RF based technology). The external device may comprise RFID tags <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X of <FIG>. In this case, the antenna <NUM> is configured to transmit RF carrier signals (e.g., interrogation signals) to the listed external devices, and/or transmit data response signals (e.g., authentication reply signals or an RFID response signal) generated by the RF enabled device <NUM>. In this regard, the RF enabled device <NUM> comprises an RF transceiver <NUM>. RF transceivers are well known in the art, and therefore will not be described herein. However, it should be understood that the RF transceiver <NUM> receives RF signals including information from the transmitting device, and forwards the same to a logic controller <NUM> for extracting the information therefrom.

The extracted information can be used to determine the presence, location, and/or type of movement of an RFID tag within a facility (e.g., RSF <NUM> of <FIG>). Accordingly, the logic controller <NUM> can store the extracted information in memory <NUM>, and execute algorithms using the extracted information. For example, the logic controller <NUM> can correlate tag reads with beacon reads to determine the location of the RFID tags within the facility. The logic controller <NUM> can also perform pattern recognition operations using sensor data received from RFID tags and comparison operations between recognized patterns and pre-stored patterns. The logic controller <NUM> can further select a time slot from a plurality of time slots based on a tag's unique identifier (e.g., an EPC), and communicate information specifying the selected time slot to the respective RFID tag. The logic controller <NUM> may additionally determine a WOT during which a given RFID tag's communication device (e.g., transceiver) or operation(s) is(are) to be turned on when motion is detected thereby, and communicate the same to the given RFID tag <NUM>. The WOT can be determined based on environmental conditions (e.g., temperature, time of day, etc.) and/or system conditions (e.g., amount of traffic, interference occurrences, etc.). Other operations performed by the logic controller <NUM> will be apparent from the following discussion.

Notably, memory <NUM> may be a volatile memory and/or a non-volatile memory. For example, the memory <NUM> can include, but is not limited to, a RAM, a DRAM, an SRAM, a ROM, and a flash memory. The memory <NUM> may also comprise unsecure memory and/or secure memory. The phrase "unsecure memory," as used herein, refers to memory configured to store data in a plain text form. The phrase "secure memory," as used herein, refers to memory configured to store data in an encrypted form and/or memory having or being disposed in a secure or tamper-proof enclosure.

Instructions <NUM> are stored in memory for execution by the RF enabled device <NUM> and that cause the RF enabled device <NUM> to perform any one or more of the methodologies of the present disclosure. The instructions <NUM> are generally operative to facilitate determinations as to whether or not RFID tags <NUM> are present within a facility <NUM>, where the RFID tags <NUM> are located within a facility <NUM>, which RFID tags <NUM> are in motion at any given time. Other functions of the RF enabled device <NUM> will become apparent as the discussion progresses.

Referring now to <FIG>, there is provided a detailed block diagram of an exemplary architecture for a server <NUM>. Server <NUM> of <FIG> is the same as or substantially similar to server <NUM>. As such, the following discussion of server <NUM> is sufficient for understanding server <NUM>.

Notably, the server <NUM> may include more or less components than those shown in <FIG>. However, the components shown are sufficient to disclose an illustrative embodiment implementing the present solution. The hardware architecture of <FIG> represents one embodiment of a representative server configured to facilitate inventory counts, inventory management, and improved customer experiences.

Some or all the components of the server <NUM> can be implemented as hardware, software and/or a combination of hardware and software. The hardware includes, but is not limited to, one or more electronic circuits. The electronic circuits can include, but are not limited to, passive components (e.g., resistors and capacitors) and/or active components (e.g., amplifiers and/or microprocessors). The passive and/or active components can be adapted to, arranged to, and/or programmed to perform one or more of the methodologies, procedures, or functions described herein.

As shown in <FIG>, the server <NUM> comprises a user interface <NUM>, a CPU <NUM>, a system bus <NUM>, a memory <NUM> connected to and accessible by other portions of server <NUM> through system bus <NUM>, and hardware entities <NUM> connected to system bus <NUM>. The user interface can include input devices (e.g., a keypad <NUM>) and output devices (e.g., speaker <NUM>, a display <NUM>, and/or light emitting diodes <NUM>), which facilitate user-software interactions for controlling operations of the server <NUM>.

At least some of the hardware entities <NUM> perform actions involving access to and use of memory <NUM>, which can be a RAM, a disk driver, and/or a Compact Disc Read Only Memory ("CD-ROM"). Hardware entities <NUM> can include a disk drive unit <NUM> comprising a computer-readable storage medium <NUM> on which is stored one or more sets of instructions <NUM> (e.g., software code) configured to implement one or more of the methodologies, procedures, or functions described herein. The instructions <NUM> can also reside, completely or at least partially, with-in the memory <NUM> and/or within the CPU <NUM> during execution thereof by the server <NUM>. The memory <NUM> and the CPU <NUM> also can constitute machine-readable media. The term "machine-readable media," as used here, refers to a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions <NUM>. The term "machine-readable media," as used here, also refers to any medium that is capable of storing, encoding, or carrying a set of instructions <NUM> for execution by the server <NUM> and that cause the server <NUM> to perform any one or more of the methodologies of the present disclosure.

In some scenarios, the hardware entities <NUM> include an electronic circuit (e.g., a processor) programmed for facilitating the provision of a three-dimensional map showing locations of RFID tags <NUM> within a facility and/or changes to said locations in near real-time. In this regard, it should be understood that the electronic circuit can access and run a software application <NUM> installed on the server <NUM>. The software application <NUM> is generally operative to facilitate the determination of RFID tag <NUM> locations within a facility, the direction of travel of RFID tags <NUM> in motion, and the mapping of the RFID tag <NUM> locations and movements in a virtual three-dimensional space.

In those or other scenarios, the hardware entities <NUM> include an electronic circuit (e.g., a processor) programmed for facilitating item/article inventorying, merchandise sale, and/or customer satisfaction with a shopping experience. In this regard, the electronic circuit can access and run an inventorying software application <NUM> and an MCD display software application <NUM> installed on the server <NUM>. The software applications <NUM> are collectively generally operative to: obtain item level information and/or other information from MCDs and RFID tags <NUM>; program item level information, accessory information, related product information and/or discount information onto RFID tags <NUM> and/or MCDs; convert the language, pricing and/or currency symbol of item level information, accessory information, related product information and/or discount information; facilitate registration of RFID tags <NUM> and MCDs with an enterprise system; and/or determine when MCD display update actions need to be taken based on RFID tag <NUM> information. Other functions of the software applications <NUM> will become apparent as the discussion progresses. Such other functions can relate to tag reader control and/or tag control.

In <FIG> there is shown an RFID portal <NUM> (plan view in <FIG>, top view in <FIG>), which is useful for understanding certain aspects of the technology disclosed herein. The RFID portal <NUM> includes two RFID readers 506a, 506b (such as tag reader <NUM>, hereinafter "<NUM>," generally); each of them are respectively attached to antennas 502a, 502b (such as antenna <NUM>, hereinafter "<NUM>," generally) mounted on sides of the portal <NUM>. An RFID reader <NUM> as referenced herein is capable of generating RFID tag exciter signals to control and elicit responses from one or more of a plurality of RFID tags <NUM> (such as tag <NUM>) in a RFID portal zone. The RFID exciter signals can also serve as a source of power for energizing the RFID tags <NUM>. The exciter signals generated by the RFID readers <NUM> and responses received by each reader <NUM> will be in accordance with an RFID system standard that is now known or known in the future. The RFID readers <NUM> also can detect, identify, and/or process one or more the responses from the plurality of RFID tags <NUM> in a portal zone. The RFID readers <NUM> include suitable interface circuitry to facilitate communications with a system controller <NUM> (such as server <NUM>) as described below. For example, the interface circuitry can facilitate communication of information regarding detected responses received from RFID tags <NUM>. Such interface circuitry can also facilitate reception of interrogation commands and/or antenna beam control commands from the system controller <NUM>.

In the portal <NUM> shown, the antennas <NUM> are mounted on pedestals 503a, 503b (hereinafter "<NUM>," generally), but the technology disclosed herein is not limited in this regard. Antennas <NUM> can be mounted in the ceiling or in the ground, and the method described herein would still be applicable. There is no restriction regarding the type of antennas <NUM> that are used to produce the required field patterns. However, in this example portal <NUM>, antennas <NUM> are understood to be beam steerable so that multiple different antenna beam directions can be obtained from a single antenna <NUM>. Control over the required antenna field patterns can be facilitated by the RFID readers <NUM> as noted above. In addition, two antennas, 502a and 502b, are shown in <FIG>, but it should be understood that the technology disclosed herein is not limited in this regard. The inventive arrangements descried herein could be implemented using a single beam steerable antenna.

The RFID portal <NUM> can be placed in the vicinity of an exit point in a facility where articles <NUM> must pass through in order to transition from one space inside the facility <NUM> to a second space, which is outside of the facility <NUM>. In the example shown in <FIG> and <FIG>, the exit point is a doorway <NUM>, but the technology disclosed herein is not limited in this regard. The exit/choke point can also be a wide exit such as those seen in shopping malls, which is open to another interior space, which is not a part of the facility <NUM>. The RFID readers <NUM> can be operated under the command of a system controller <NUM>, such as server <NUM>, which facilitates the detection of one or more RFID tags <NUM> within a field of view of each antenna <NUM> as hereinafter described.

In the arrangement shown in <FIG> and <FIG>, a human guard or monitor will likely be stationed near the RFID portal <NUM> to observe and interact with shoppers exiting the retail store <NUM>. Referring now to <FIG>, a representation <NUM> of a human guard or monitor <NUM> (hereinafter "guard <NUM>") is shown in proximity of the RFID portal <NUM>. The guard <NUM> has one or more personal communication devices on their person, such as the device <NUM>. The device <NUM> enables one or more networked systems such as the network <NUM> to communicate with the guard <NUM> via the device <NUM>. Near-real time communications that may are relevant to the detection of unauthorized RFID tags <NUM> by the system <NUM> are sent to the device <NUM>. "Unauthorized RFID tags" are detected tags <NUM> where the tag data does not confirm that the article to which the tag <NUM> was attached was purchased prior to reaching the RFID portal <NUM>. In some examples, when an unauthorized RFID tag <NUM> is detected, an alarm event flag is set. If the alarm event flag is validated, a human-perceptible alarm is triggered. If the alarm event flag is not validated, it is assumed to be a false alarm, and the alarm event flag is cleared.

In some examples, the device <NUM> carried by the guard <NUM> is enabled for bidirectional voice-data communication, and includes a display, memory, and a processor. The device <NUM> can be a smart phone having an application running thereon, or otherwise it can a dedicated proprietary device <NUM>. The device <NUM> can display additional information useful to the guard <NUM> relating to the detected tag <NUM> to enable the guard <NUM> to make accurate decisions quickly as to whether to detain people based on suspected theft of an article <NUM>.

In some examples, additional related data can be collected by measuring the reflected energy, e.g., using a received signal strength indicator (RSSI) or a received channel power indicator (RCPI), from a detected RFID tag <NUM>. The RSSI can then be used as an estimate of the distance of the tag <NUM> from the interrogating antenna <NUM>. Based on testing and experimentation, a typical RF power at the antenna is <NUM> W conducted and <NUM>-<NUM> dB of antenna gain. This is considered to be a very large signal strength. Therefore, the reflected energy (RSSI) from a RFID tag is also very large. For most tags <NUM> and systems running at high power, the reflected energy will be -<NUM> dBm to -<NUM> dBm.

The transmitted signal strength typically drops off by <NUM>-<NUM> dB in the first meter of separation from the antenna <NUM>. Thereafter, the signal strength typically falls off <NUM> dB for every doubling of the distance away from the antenna <NUM>. At two meters away, the signal strength is down <NUM> dB, at four meters away it is down <NUM> dB, at eight meters away it is down <NUM> dB, etc. Therefore, if a person is within <NUM>-<NUM> feet of the face of the antenna <NUM> and proceeds to move a detectable tag <NUM> back and forth, then the RSSI value for the tag read should exceed any possible RSSI for a tag <NUM> greater than <NUM> feet away. These numbers are for illustration purposed only, and in practice, it may be necessary to adjust the values based on the frequency of the specific portal <NUM>. The rules and regulations for RFID transmissions vary by country and jurisdiction, resulting in the use of different frequencies and transmission strengths in different RFID portals <NUM>. The values also may be adjusted depending on the type and manufacturer of the RFID tags <NUM> on the products/garments.

One problem encountered at times with RFID portal <NUM> alarm detection is that the customers do not typically walk within one foot if the RFID antennas <NUM>. Also, in many RFID portals, a more complex algorithm can be used that reads into and out of the store <NUM> by beam steering the RFID read signals into and out of the store <NUM>. Such a system is described in <CIT> entitled "SYSTEM AND METHOD FOR READING RFID TAGS ACROSS A PORTAL," which is commonly owned with the present application (hereinafter "the '<NUM> patent").

As described in the '<NUM> patent, RFID tag <NUM> interrogation can involve interrogating tags <NUM> using the dual-target mode in one of the latched sessions S1, S2 or S3. In the dual-target mode, each of the tags <NUM> will be read continuously regardless of whether the tag is in state "A" or state "B. " The expectation in such scenarios is to be able to read all tags <NUM> within the field of view (FOV) of the reader antenna <NUM>, regardless of the inventoried flag state. Typically, the power level of the RFID electromagnetic exciter field is manually tuned to limit the reading of static tags that might be far from the RFID reader <NUM>. But as more time is spent by an RFID reader <NUM> to inventory the tags in the FOV of its steerable antenna <NUM>, the opportunities increase to miss a tag <NUM> that is crossing in an area that is not then covered by the antenna beam. This problem can become particularly noteworthy when many tags <NUM> are present. It also detracts from the ability of the portal <NUM> to focus attention on the tags <NUM> that are actually crossing through the portal (as opposed to static tags <NUM> which are not in motion).

The system described in the '<NUM> patent includes executing a combination of RFID tag reads using different sessions, power levels, and beam directions so as to improve RFID portal <NUM> accuracy in a dense tag population. The combination of read cycles allows an RFID portal <NUM> to detect the surrounding tags <NUM> and focus on the crossings tags <NUM>. But because there potentially are a lot of tags <NUM> that can be read inside the store <NUM>, the detection algorithms use session information and RSSI change information that requires multiple reads over time. As a result, if the guard <NUM> at the RFID portal <NUM> walks the bag with potentially stolen articles <NUM> back through the RFID portal <NUM>, then tags <NUM> therein have a very low probability of alarming again.

A problem that is prevalent in the industry is that store personnel, especially human exit guards such as guard <NUM>, expect the RFID portal <NUM> alarm to work in the same way as acousto-magnetic (AM) EAS systems that they may have become accustomed to working with.

Examples of the technology disclosed herein include offering some alarm detection logic similar to that of an AM EAS system. In some examples, the RFID portal <NUM> alarms when an RFID tag <NUM> (still attached to the article) is placed within a short distance (e.g., under <NUM>") the RFID portal <NUM> antennas <NUM>. While this approach differs slightly from the operation of an AM system (because the range of where the tags <NUM> would need to be placed would be much smaller: e.g., <NUM>-<NUM> feet, as opposed to <NUM>-<NUM> feet for the AM system), the example methods is useful for determining probable theft after an initial alarm event flag is set, and would help solve some of the problems set forth above.

In addition, consider that RFID tags <NUM> on the articles <NUM> each have a serial number and are unique to the article110 that they are attached to. Therefore, an Electronic Product Code (EPC) or Stock Keeping Unit (SKU) number can be sent in real-time to am MCM <NUM> (such as a mobile device, tablet, handheld RFID reader), or to a smart screen (e.g., on or near the RFID portal <NUM>). Then system can then query datastore <NUM> to obtain data describing the article110 associated with the detected tag <NUM>. The retrieved data can include a description of the article110, e.g., including, size, color, ID numbers, and price, along with an image file of the article110 associated with the alarming tag <NUM> that can be displayed to the guard <NUM>, e.g., on MCM <NUM>.

The image of the article110 and associated description may assist the guard <NUM> in validating the alarm event flag at the RFID portal <NUM>. The guard <NUM> may be able to quickly inspect the inside the customer's bag to visually determine if the article in question is inside the bag. In some examples of the technology disclosed herein, the system <NUM> retrieves data from one or more back end retail theft databases to provide still more information that the guard could use to determine if a theft is occurring. Such approaches can support the guard's <NUM> decision in at least two ways: (a) information acquired by the exit system logic, this is probability of this event being a theft as determined by the exit system and (b) such event combined with a backend system where a datastore can provide relevant data pertaining to theft.

In some examples, the data providing enriched information to the guard <NUM> can include: the frequency that the type of article <NUM> is stolen from all stores (e.g., store item stolen ranking), the frequency that such an article110 is stolen from that particular store (e.g., store neighborhood stole item ranking), customer information to help determine if this is a known good customer or a previous theft customer, historical information on how often such articles <NUM> are being stolen and during what time of day, the total count of articles <NUM> being stolen, and other relevant information.

The customer information can be obtained using any number of well-known methods. Cameras can be used to capture facial image data of the suspected thief, and the system can use facial recognition algorithms to compare this image with images in a database of known shoplifters. The customer's identity may be tracked from the point of sale (POS) where the customer used a credit or debit card, or a loyalty card associated with the customer. The identified customer can then be tracked to the point of exit using any suitable human tracking system. The customer can also be identified by responses from their mobile devices, and loyalty cards they may be carrying. For example, the customer may be logged into the store's Wi-Fi, or may be using running the store's application on their phone. It is not necessary to obtain the real legal identity of the customer. The identity data sensed from the customer and/or their phone can be compared on an anonymous basis with similar data in a known thief database.

A theft probability algorithm can assign weights to the various data parameters retrieved from a theft database. Some examples of the technology disclosed herein can use the theft probability algorithm to determine a percentage representing an estimated overall probability of theft relating to the alarm event flag. This probability of theft can be based at least in part on analysis of local data collected at the scene, in combination with historical and statistical data retrieved from the theft database.

The calculated probability of theft, represented as a percentage, can be transmitted to the guard via the MCD <NUM> and displayed thereon. In some examples, the retrieved data from the theft database can be displayed on the MCD <NUM> in a raw format, so that the guard <NUM> can view the actual data and make their own determination as to the probability that theft is occurring. In practice, both the calculated probability percentage and the raw data results can be simultaneously displayed on an MCD <NUM>.

In some examples of the technology disclosed herein, the calculated probability of theft can be used to provide an explicit directive to the guard <NUM> or additional employees that the person attempting to exit the premises should be stopped and questioned about their purchases and articles they may be carrying. This can be accomplished by setting a threshold on the calculated probability of theft where the interception of the customer is required. Other parameters can be used to instead of, or in addition to, the calculated probability of theft, to determine when a customer should definitely be stopped before exiting. For example, if the customer is identified as a known, habitual thief, this factor alone can trigger a directive to stop the customer if the customer is associated with an alarm event flag. The exact parameters to be used in a determination of when a customer should be stopped can be selected by the retailer.

Sending explicit notifications to one or more employees directing them that a customer is to be intercepted before exiting can provide many advantages. The technology reduces the need for subjective "on the spot" decisions by employees which may take too much time. The technology helps guards and other employees to more effectively do their jobs because they do not have to second-guess their own decision to stop a customer. A system-generated directive to stop the customer also saves time, because the window in which a customer can be stopped, between the time they set off the alarm to the time they exit the store, can be very short.

In accordance with some examples of the technology disclosed herein, the guard <NUM> receives, through device <NUM>, a system-generated message that they are to stop a particular customer. The system-generated "stop customer" message can be sent to multiple employees are once who may be in proximity of the exits. The notification message to stop the customer necessarily includes sufficient information on the customer to allow the guard to identify, quickly and accurately, the customer to be stopped. The information conveyed to the guard can include the display of real-time motion map showing representations of people and objects moving toward the exits, where the representation of the person to be stopped is highlighted. Other methods include sending a visual image of the person to the guard's mobile device, where the image was taken at the moment the RFID portal <NUM> alarmed. In one embodiment, the image can be taken by a camera mounted on the RFID portal <NUM>.

The guard <NUM> can also be equipped with a reader <NUM> that enables the guard <NUM> to scan a customer's receipt (e.g. using a barcode, QR, OCR etc.) to determine what articles <NUM> are in the customer's possession compared with those articles <NUM> processed at POS, and in comparison with the RFID "license plate," which is the tag data detected by the RFID portal <NUM>.

The guard <NUM> could use the additional information communicated to their device <NUM> to facilitate and improve upon their decisions. For example, if the alarm is on an article1 <NUM> that is near the RFID portal <NUM> and the guard <NUM> did not see the customer walk near the RFID portal <NUM>, then the guard <NUM> can, at their discretion, ignore this alarm event flag. If the RFID portal <NUM> has a camera and it can determine that the person leaving is known to have stolen before, then the guard <NUM> can stop that person and check their bags. If the guard <NUM> has a handheld RFID reader <NUM>, then this information can be sent to that device so that the guard can scan the customers to find the specific RFIID tags <NUM> that are being indicated as stolen.

In an example system <NUM>, the RSSI is set to a threshold of <NUM>. This corresponds to a read range of <NUM> inches at <NUM> dBm power with a <NUM>-<NUM> dB gain antenna, <NUM>-<NUM> inches at <NUM> dBm and <NUM>-<NUM> inches at <NUM> dBm. These values are approximate and depend on the power settings. In a variation, the power is set to <NUM> dBm on all of the antennas. It is believed that this setting will raise the RSSI threshold to make it harder to trigger an alarm, thus reducing the occurrences of false alarms.

To reduce the risk of multiple signals bouncing constructively into the store <NUM> and giving a high power to a tag <NUM> that is sitting inside the store, in some examples of the technology disclosed herein, a minimum number of high RSSI reads is required before an alarm event flag is triggered. In practice, minimum number of high RSSI read could be set to <NUM>, but in some cases, it should be set to <NUM> or <NUM> read events exceeding the threshold within a few seconds.

In some examples of the technology disclosed herein, the alarm event logic can also be gated by only triggering an alarm if one of the people counter/motion sensor detectors is triggered. In some examples, where an overhead people counter is the data source, an alarm is only triggered when a person is standing near the exit gate for a minimum time after the detection of an unauthorized tag. In some examples, the alarm logic is based on detecting motion near the pedestal and then determining that a person is within reach of a pedestal, and concurrently getting one or more high-RSSI reads. In some examples of the technology disclosed herein, if all three of the above criteria are met after an unauthorized tag <NUM> is detected, a rule is applied that the alarm is automatically triggered.

In the practice of examples of the technology, the value of the parameters to be set are selected based on the individual system, and the location of that system, so that the technology can be implemented for all of the different types of RFID tags <NUM>, articles <NUM>, tagging methods, regulatory regions, and use cases. For example, in the US there are <NUM> frequencies used for RFID protocols, and each one will have a slightly different optimal value. In these cases, logic can be added to change the threshold for each transmission frequency.

Referring to <FIG>, and continuing to refer to prior figures for context, methods <NUM> for electronic article surveillance (EAS) are shown. In such methods <NUM>, an RFID portal of an EAS system first interrogates in a first zone extending into a controlled area beyond a threshold distance from an interrogating antenna of the RFID portal - Block <NUM>. In such methods, the RFID portal defines an exit from the controlled area, the threshold distance being less than a width of the exit.

Consider, as a continuing example, a customer purchasing two articles <NUM> (tagged with tag X <NUM>) and article <NUM> (tagged with tag Y <NUM>) at a POS in store <NUM>. The POS updates datastore <NUM> with the "purchased" status of article <NUM>, authorizing the article <NUM> to leave the store <NUM>, but fails to update the purchase status of article <NUM>, which remains unauthorized to leave the store.

In the continuing example, RFID portal <NUM> interrogates in a first zone extending into the store <NUM> by executing a combination of RFID tag reads around using different sessions, power levels, and beam directions, e.g., per the '<NUM> patent. In the continuing example, the first interrogation zone at times extends outside the store <NUM>. The combination of read cycles allows an RFID portal <NUM> to detect the surrounding tags <NUM> and focus on the tags <NUM> crossing/about to cross through the RFID portal <NUM>. But because there potentially are a lot of tags <NUM> that can be read inside the store <NUM>, the detection algorithms use session information and RSSI change information that requires multiple reads over time. As a result, if the guard <NUM> at the RFID portal <NUM> walks a bag with potentially stolen articles <NUM> (tags <NUM> attached) back through the RFID portal <NUM>, then tags <NUM> therein have a very low probability of alarming again, i.e., a given tag <NUM> may not be guaranteed to respond to a subsequent interrogation during the multisession interrogation period. Yet, re-interrogating a bag or article is an expected practice of a guard <NUM>. In the continuing example, the threshold distance is about <NUM> ft. (corresponding to an expected drop off of about <NUM> dB in received power at a tag <NUM>), the power level of the first interrogation is <NUM> W (conducted), and with <NUM> dB of antenna gain in each of two beam steered antennas <NUM>.

Referring to <FIG>, in operation, EAS system <NUM> may perform the method <NUM> of electronic article surveillance, by such as via execution of application component <NUM> by processor <NUM> and/or memory <NUM> - wherein application component <NUM>, processor <NUM>, and/or memory <NUM> are components of computing device <NUM>. Computing device <NUM> can be one or more of a tag <NUM>, a tag reader <NUM>, and system controller <NUM> - as appropriate as explained elsewhere herein. In a separate example, application component <NUM> includes first interrogating component <NUM> that is configured to or may comprise means for first interrogating in a first zone extending into a controlled area beyond a threshold distance from an interrogating antenna of the RFID portal.

The RFID portal <NUM> first detects, in response to the first interrogating, a first response of a particular RFID tag - Block <NUM>. In the continuing example, RFID portal <NUM> detects Tag X <NUM> and tag Y <NUM> (about <NUM> ft. away from one of the antennas <NUM>, inside the store <NUM>), and further determines that tag X <NUM> is moving in the direction of the exit/RFID portal <NUM> without authorization to leave the store <NUM> - thereby setting an alarm event flag. The EAS system notifies a guard <NUM> stationed near the RFID portal <NUM>, through the guard's handheld mobile communication device <NUM> (a mobile phone), that an alarm event flag has been set - though the alarm is not yet sounded - and instructs the guard <NUM> to check for customers exiting through the RFID portal <NUM>, and to examine articles <NUM>, <NUM> carried by such customers. The guard <NUM> finds one customer carrying an article <NUM> still carrying a tag <NUM> and article <NUM> also still carrying a tag <NUM>. In the separate example, application component <NUM> includes first detecting component <NUM> that is configured to or may comprise means for first detecting, in response to the first interrogating, a first response of a particular RFID tag.

Subsequent to the first detecting, the RFID portal second interrogates in a second zone extending into the controlled area at least to the threshold distance - Block <NUM>. In the continuing example, the second interrogation is in response to the first detecting, and comprises interrogating in which all RFID tags <NUM> in the second interrogation field are allowed to respond. The same conducted power is used as in the first interrogation. In particular, the guard <NUM>, in response to the notification described above, passes each of the customer-carried article <NUM> still carrying a tag <NUM> (also as yet unidentified by the guard <NUM>) and then article <NUM> still carrying a tag <NUM> (as yet unidentified by the guard <NUM>) in turn within <NUM> ft. of an antenna <NUM> in a pedestal <NUM> of the RFID portal <NUM> (inside the threshold distance in the second interrogation zone) during this second interrogation period - in a fashion similar to procedures for AM EAS systems. In the separate example, application component <NUM> includes second interrogating component <NUM> that is configured to or may comprise means for second interrogating in a second zone extending into the controlled area at least to the threshold distance.

RFID portal second detects, in response to the second interrogating, at least one second response of the particular RFID tag indicating a received signal strength of the second interrogating at the particular RFID tag corresponding to a distance from an interrogating antenna of the RFID portal less than the threshold distance - Block <NUM>. In the continuing example, the RFID portal <NUM> detects tag Y <NUM> multiple times as the guard <NUM> passes article <NUM> with tag Y <NUM> attached within <NUM> ft. of antenna <NUM>, but since tag Y <NUM> was authorized to leave the store <NUM>, no action is taken by the EAS system <NUM>. The RFID portal <NUM> then detects tag X <NUM> multiple times as the guard <NUM> waves the article <NUM> (to which a tag X <NUM> remains attached) within <NUM> ft. of an antenna <NUM> of the RFID portal <NUM>. The detected response from tag X <NUM> both identifies the tag <NUM> as tag X <NUM> and includes an RSSI corresponding roughly to the expected received signal strength at a tag within <NUM> ft. of antenna <NUM>. In the separate example, application component <NUM> includes second detecting component <NUM> that is configured to or may comprise means for second detecting, in response to the second interrogating, at least one second response of the particular RFID tag indicating a received signal strength of the second interrogating at the particular RFID tag corresponding to a distance from an interrogating antenna of the RFID portal less than the threshold distance.

The EAS system alarms in response to the second detecting - Block <NUM>. In the continuing example, the detection of unauthorized tag X <NUM> sets of an alarm at the RFID portal <NUM>, notifying the guard that tag X <NUM> has not been authorized to leave the store <NUM>. In the continuing example, the guard <NUM> confirms that the POS system failed to record properly the article <NUM> to which tag X <NUM> was attached as "purchased. " In the separate example, application component <NUM> includes alarming component <NUM> that is configured to or may comprise means for alarms in response to the second detecting.

Claim 1:
A method of electronic article surveillance, EAS, comprising:
- first interrogating, by an RFID portal (<NUM>) of an EAS system (<NUM>), in a first zone, said first zone extending into a controlled area beyond a threshold distance from an interrogating antenna (<NUM>) of the RFID portal (<NUM>), the RFID portal (<NUM>) defining an exit from the controlled area, the threshold distance being less than a width of the exit;
- first detecting, by the RFID portal (<NUM>) and in response to the first interrogating, a first response of a particular RFID tag (<NUM>, <NUM>, <NUM>, <NUM>);
- second interrogating, by the RFID portal (<NUM>) and subsequent to the first detecting, in a second zone, said second zone extending into the controlled area at least to the threshold distance;
- second detecting, by the RFID portal (<NUM>) and in response to the second interrogating, at least one second response of the particular RFID tag (<NUM>, <NUM>, <NUM>, <NUM>) indicating a received signal strength of the second interrogating at the particular RFID tag (<NUM>, <NUM>, <NUM>, <NUM>) corresponding to a distance from an interrogating antenna (<NUM>) of the RFID portal (<NUM>) less than the threshold distance; and
- alarming, by the EAS system (<NUM>), in response to the second detecting.