Patent Description:
Electronic Article Surveillance ("EAS") systems are often used by retail stores in order to minimize loss due to theft. One common way to minimize retail theft is to attach a security tag to an article such that an unauthorized removal of the article can be detected. In some scenarios, a visual or audible alarm is generated based on such detection. For example, a security tag with an EAS element (e.g., an acousto-magnetic element) can be attached to an article offered for sale by a retail store. An EAS interrogation signal is transmitted at the entrance and/or exit of the retail store. The EAS interrogation signal causes the EAS element of the security tag to produce a detectable response if an attempt is made to remove the article without first detaching the security tag therefrom. The security tag must be detached from the article upon purchase thereof in order to prevent the visual or audible alarm from being generated.

One type of EAS security tag can include a tag body which engages a tack. The tack usually includes a tack head and a sharpened pin extending from the tack head. In use, the pin is inserted through the article to be protected. The shank or lower part of the pin is then locked within a cooperating aperture formed through the housing of the tag body. In some scenarios, the tag body may contain a Radio Frequency Identification ("RFID") element or label. The RFID element can be interrogated by an RFID reader to obtain RFID data therefrom.

The EAS security tag may be removed or detached from the article using a detaching unit. Examples of such detaching units are disclosed in <CIT> ("the '<NUM> patent), <NUM>,<NUM>,<NUM> ("the '<NUM> patent"), <NUM>,<NUM>,<NUM> ("the '<NUM> patent"), <NUM>,<NUM>,<NUM> ("the '<NUM> patent") and <NUM>,<NUM>,<NUM> ("the '<NUM> patent"). The detaching units disclosed in the listed patents are designed to operate upon a two-part hard EAS security tag. Such an EAS security tag comprises a pin and a molded plastic enclosure housing EAS marker elements. During operation, the pin is inserted through an article to be protected (e.g., a piece of clothing) and into an aperture formed through at least one sidewall of the molded plastic enclosure. The pin is securely coupled to the molded plastic enclosure via a clamp disposed therein. The pin is released by a detaching unit via a probe. The probe is normally retracted within the detaching unit. Upon actuation, the probe is caused to travel out of the detaching unit and into the enclosure of the EAS security tag so as to release the pin from the clamp or disengage the clamp from the pin. Once the pin is released from the clamp, the EAS security tag can be removed from the article.

While EAS security tags help reduce retail theft, improper use of the detaching unit is an ever growing problem that is inhibiting the effectiveness of the security tags. For example, an unscrupulous store employee may conspire to allow customers to steal merchandise by a practice known as "sweethearting". "Sweethearting" involves collusion between the store employee and a customer. Typically, a cashier scans an inexpensive item for the customer to ring a sale and apparently complete the transaction. But then the cashier uses a detaching unit to remove the EAS security tag from a much more expensive item which was not scanned. The customer is then free to leave the premises with the expensive item without having paid therefore. In effect, "sweethearting" can cost businesses a relatively large amount of dollars each year.

<CIT> discloses a security tag and method of using same facilitates authorized removal of items from a controlled area where the items have been marked with an item identification code. The method involves providing a transaction software application to facilitate use of a PMCD to obtain the item identification code and participate in a wireless communication session with a transaction server to receive an authorization for release of the item from the controlled area.

The present invention is defined by the method and system of the independent claims <NUM> and <NUM>. A method according to the invention comprises: receiving, by the security tag, an authorization code comprising a security tag identifier signed using a cryptographic key of a plurality of cryptographic keys that are respectively assigned to a plurality of security tags (e.g., from a Point Of Sale ("POS") terminal), wherein the authorization code is received by the security tag from a Point of Sale (POS) terminal; performing operations by the security tag to determine if the security tag identifier matches an internally stored identifier and if so, performing operations by the security tag to verify a signature of the authorization code; and performing detach operations or deactivation operations by the security tag, responsive to the signature's verification. The detach operations cause a mechanical detachment of the security tag from an item and the deactivation operations cause a disablement of a response by the security tag to an interrogation signal from an RFID and/or EAS system.

According to the invention, upon verification of the signature, a status bit is set to a value indicating that the security tag is coupled to an article that no longer constitutes inventory to be sold or loaned. The detach operations further may comprise withdrawing a pin of the security tag, withdrawing a pad of the security tag, or actuating a first mechanical component of the security tag to allow motion of a second mechanical component of the security tag.

Further according to the invention, the method also comprises: performing operations by the security tag to notify an enterprise system of the security tag's mechanical detachment from an item or the disablement of the security tag's ability to respond to the interrogation signal; Embodiments of the method may comprise performing operations by the enterprise system to verify that the security tag was actually removed from the article. The security tag's removal may be verified based on contents of captured images and/or system intelligence of the security tag's motion, the security tag's path of travel through a facility, and the security tag's last known location within the facility. The system intelligence may be obtained using information received from the security tag when the security tag was in motion and during time slots of a plurality of time slots that are allocated to other security tags. An alert is output from the security tag when authorization of the security tag's detachment is not verified by the enterprise system.

The present solution will be described with reference to the following drawing figures, in which like numerals represent like items throughout the figures.

The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the present solution is, therefore, 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.

Mobile shopping apps, shopping websites and self-checkout solutions are becoming more prevalent in retail stores. Presently, there is no way for a retail store to provide a customer with authorization to detach and/or deactivate security tags attached to protected retail items. Accordingly when a customer uses a Mobile Point Of Sale ("MPOS") device or a self-checkout kiosk, the security tags attached to the purchased products trigger an alarm at a retail store's exit. For tag deactivation, some retailers have a deactivation device tied to a fixed POS. Deactivation of a security tag is only enabled when there is a scanned Unique Product Code ("UPC"). However, there is no verification that the correct security tag is deactivated.

The systems and methods discussed herein allow authorization of security tag detachment/deactivation by a customer after completing a successful purchase transaction. Accordingly, the present solution facilitates the use of mobile shopping applications, shopping websites and self-checkout solutions in retail establishments that would not be possible due to the use of security tags. The present solution provides advantages to retailers by (<NUM>) reducing labor costs for checkout and security tag detachment/deactivation and (<NUM>) allowing better management of influx of customers due to mobile checkout options available. The present solution also provides advantages to customers by (<NUM>) allowing customers to self-pay using a mobile shopping applications, shopping websites and self-checkout solutions in store with products protected by security tags. As such, there is no need for the customers to stand and wait in checkout lines.

The present solution can be implemented in any known or to be known a Radio Frequency Identification ("RFID") system, EAS, and/or inventory system. In some scenarios, the present solution is employed in a novel time slot based inventory system. Such a system is described below. Thereafter, various methods for security tag detachment and/or deactivation are described.

One aspect of the present solution generally concerns systems and methods for determining and tracking inventory using time slotted tag communications. This aspect of the present solution solves the following problems:.

The present solution can use standard RFID tags and readers (with a software update) but could be designed to incorporate the functioning into a new and compatible RFID tag chip as well. Initially, the RFID tag would need to be supplemented with a rechargeable power source (e.g., a battery and/or a capacitor), a Central Processing Unit ("CPU"), an accelerometer and/or motion detector.

Just as in normal RFID implementations, RFID tag readers are constantly scanning their Field Of View ("FOV") and requesting that all tags in its coverage area respond to interrogation signals. The present solution solves these problems with two novel features: (A) time based RFID tag communications control (e.g., disabling a receiver, disabling a transceiver or transmitter, disabling a communications operation, bypassing a communications device or operation, and/or disabling a response from the RFID tag); and (B) motion based RFID tag communications control. The RFID tag control of (A) involves controlling the RFID tag so that it only enables its communications functionality (e.g., enables a receiver, enables a transceiver or transmitter, enables at least one communications operation, and/or discontinues a bypass of a communications device or operation) periodically under system control. This is for improved static inventory counting. The RFID communications control of (B) involves turning on, enabling or no longer bypassing the RFID receiver, the RFID transceiver/transmitter and/or at least one communications operation when motion is detected and continuing to receive interrogation signals while in motion. This is for loss prevention and tag location tracking.

Novel feature (A) provides better full inventory counts. In the present solution, the RFID chip is scheduled to only enable (or turn on) or no longer bypass its communication device (e.g., a transceiver) or communications operation(s) one or two times a day, and to disable (or turn off) or bypass its communication device (e.g., transceiver) or communications operation(s) after communication with a tag reader completes or a timing window expires. The timing of the RFID tag communications is distributed over a given time period (e.g., a day or <NUM> hours) so that any time slot will only be assigned to a very small percentage of the RFID tags. This enables fast reading cycles, minimizes communications collisions, and enables identifying every tag.

Novel feature (A) also vastly reduces the RFID tags' battery drain. The main power drain on the battery is from the receiver and CPU. In the present solution, these components are only active for a few seconds per day (out of <NUM>,<NUM> seconds). The rest of the time the RFID tags can capture energy for charging the battery from the received RF energy and other sources of energy harvesting. This allows for a very small, low cost rechargeable battery or capacitor. A rechargeable energy storage is not required. For some applications, a primary battery (e.g., a lithium coin cell) can be used without recharging. If a small battery can supply energy for the expected life time of the tag, then a fixed battery could be used to reduce the costs. For example, a swing ticket could have a small battery that lasts less than one year.

Novel feature (A) further improves tag read range which reduces infrastructure costs. Using battery assisted tags changes the tag read range from, for example, <NUM>-<NUM> meters to <NUM>-<NUM> meters. This significantly reduces infrastructure installation costs since less tag readers are needed to cover a given area as compared to that needed in conventional systems, while improving overall performance in previously hard to read areas.

Novel feature (B) ensures that tags in motion respond to interrogation signals even at times when they are not scheduled to communicate during time slots. The system can now track an RFID tag while it is in motion and also detect where/when this tag motion stops. Novel feature (B) also facilitates better inventory counts, improved read ranges, and reduced infrastructure costs.

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 need to be located and/or tracked.

The system <NUM> is generally configured to allow improved inventory counts of objects and/or items located within a facility. As shown in <FIG>, system <NUM> comprises a Retail Store Facility ("RSF") <NUM> in which display equipment <NUM><NUM>,. , <NUM>M (collectively referred to as "<NUM>") is disposed. The display equipment is provided for displaying objects (or items) <NUM><NUM>-<NUM>N (collectively referred to as "<NUM>"), <NUM><NUM>-<NUM>X (collectively referred to as "<NUM>")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 securing areas of the RSF <NUM>. The RSF can also include emergency equipment (not shown), checkout counters, an EAS system (not shown), an RFID system, and/or an RFID/EAS system. Emergency equipment, checkout counters, video cameras, people counters, EAS systems, RFID systems, and/or RFID/EAS systems are well known in the art, and therefore will not be described herein.

At least one tag reader <NUM> is provided to assist in counting the objects <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X located 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 not be described herein. Any known or to be known RFID reader can be used herein without limitation.

RFID tags <NUM><NUM>-<NUM>N (collectively referred to as "<NUM>"), <NUM><NUM>-<NUM>X (collectively referred to as "<NUM>") are respectively attached or coupled to the objects <NUM><NUM>-<NUM>N, <NUM><NUM>-<NUM>X. The RFID tags are described herein as comprising single-technology tags that are only RFID enabled. The present solution is not limited in this regard. The RFID tags can alternatively or additionally comprise dual-technology tags that have both EAS and RFID capabilities. In some scenarios, the RFID enabled tags comprise RFID thread based tags.

Notably, the tag reader <NUM> is strategically placed at a known location within the RSF <NUM>. 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 location of objects <NUM><NUM>,. , <NUM>N, <NUM><NUM>,. , <NUM>X within the RSF <NUM>. The tag reader's known coverage area also facilitates object location determinations. Accordingly, RFID tag read information and tag reader location information is stored in a data store <NUM>. This information can be stored in the data store <NUM> using a server <NUM>. Server <NUM> will be described in more detail below in relation to <FIG>.

Referring now to <FIG>, there is an illustration of an illustrative architecture for a tag <NUM>. RFID tags <NUM><NUM>,. , <NUM>N, <NUM><NUM>,. , 118x 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. 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> 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 (is)are employed: Radio Frequency ("RF") communication technology; Bluetooth technology; 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 at a later time, 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 and/or a SRC 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, location and/or tracking of an item (e.g., object <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 and/or in response 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), a last known location of the security tag, an tag's internal bit value indicating whether the tag is coupled to a purchased item, 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> 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, item description, item price, a currency symbol and/or location information to an external device. The external device (e.g., server) 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 input/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, within 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 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 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 securely or removably couple the tag <NUM> 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 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 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 or not 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 data <NUM> to determine if a match exists therebetween. More specifically, a motion pattern specified by the sensor data can be compared to a plurality of motion patterns specified by the stored motion data <NUM>. The plurality of motion patterns can include, but are not limited to, a motion pattern for walking, a motion pattern for running, a motion pattern for vehicle transport, and/or a motion pattern for vibration caused by equipment or machinery in proximity to the tag (e.g., an air conditioner or fan). The type of movement (e.g., vibration or being carried) is then determined based on which stored motion data matches the sensor data. This feature of the present solution 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 can be transitioned from its sleep state in response to expiration a defined time period, the tag's reception of a control signal from an external device, and/or the tag's 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) 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's <NUM> electronics based on the energy source's status. For example, if harvested energy is sufficient to run the tag's <NUM> function, the power management circuit <NUM> confirms that all of the tag's <NUM> storage sources are fully charged such that the tag's <NUM> electronic components can be run directly from the harvested energy. This ensures that the tag <NUM> always 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) so that (s)he can investigate the issue. It may be that other merchandise are obscuring the harvesting source or the item 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) bypass 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 present 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 an antenna <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>,. , 118x 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) 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. 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 are present within a facility, where the RFID tags are located within a facility, and/or which RFID tags 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 and management. As such, the server <NUM> of <FIG> implements at least a portion of a method for determining inventory using time slotted tag communications in accordance with the present solution.

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, within 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 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 locations within a facility; the direction of travel of RFID tags in motion; and the mapping of the RFID tag locations and movements in a virtual three dimensional space. Other functions of the software application <NUM> will become apparent as the discussion progresses. Such other functions can relate to tag reader control and/or tag control.

Referring now to <FIG>, there are provided illustrations that are useful for understanding certain advantages of the present solution. As noted above, the present solution provides RFID tags which can be read by a tag reader located farther away therefrom as compared to that of conventional systems. <FIG> shows a tag reader layout for a conventional system. In <FIG>, there are <NUM> tag readers <NUM> with overlapping coverage areas <NUM>. The distance <NUM>, <NUM> between adjacent tag readers is relatively small (e.g., <NUM>-<NUM> feet apart). In contrast, <FIG> shows a tag reader layout for a system implementing the present solution. In <FIG>, there are advantageously a significantly smaller number of tag readers <NUM> needed to cover the same area. Accordingly, the distances <NUM>, <NUM> (e.g., <NUM>-<NUM> feet apart) between adjacent tag readers <NUM> is much greater than the distances <NUM>, <NUM> of <FIG>. Consequently, the present solution has a less resource intensive and less costly infrastructure.

Referring now to <FIG>, there are provided illustrations that are useful for understanding methods for determining inventory using time slotted tag communications. As shown in <FIG>, a period of time <NUM> (e.g., a <NUM> hour period) is segmented into a plurality of time slots <NUM><NUM>, <NUM><NUM>,. , <NUM>Y having equal lengths (e.g., <NUM> second). During each time slot, at least one RFID tag (e.g., RFID tag <NUM><NUM> of <FIG>) (A) receives ("Rx") an interrogation signal transmitted from a tag reader (e.g., tag reader <NUM> of <FIG>) and (B) transmits ("Tx") a response signal.

In some scenarios such as that shown in <FIG>, a single RFID tag is assigned to each time slot. For example, a first RFID tag is assigned to the first time slot <NUM><NUM>. A second RFID tag is assigned to a second time slot <NUM><NUM>. A third RFID tag is assigned to a third time slot <NUM><NUM>. This time slot assignment can be performed in accordance with a chaotic, random or pseudo-random number algorithm. Alternatively, the time slot assignment can be determined based on the unique codes of the tags (e.g., EPCs, Cyclic Redundancy Check ("CRC") codes, hash codes or outputs of randomizing algorithms). The time slot assignment can be performed by the RFID tags (e.g., RFID tags <NUM><NUM>,. , <NUM>N, <NUM><NUM>,. , 118x of <FIG>), tag readers (e.g., tag reader(s) <NUM> of <FIG>), and/or a remote server (e.g., server <NUM> of <FIG>).

In some scenarios, the time slot allocations can be dynamically changed during system operations. For example, a relatively large number of tag read collisions are occurring in the system (e.g., system <NUM> of <FIG>). Accordingly, the time slot allocations are changed so as to minimize such tag read collisions. The manner in which time slots are re-allocated can be determined by a single device (e.g., server <NUM> of <FIG>) or by a plurality of devices (e.g., RFID tags <NUM><NUM>,. , <NUM>N, <NUM><NUM>,. , <NUM>X, tag readers <NUM> and/or server <NUM> of <FIG>).

Referring now to <FIG>, there is a flow diagram of an illustrative method <NUM> for determining an inventory using a time slotted communications scheme such as that shown in <FIG>. Method <NUM> begins with <NUM> and continues with <NUM>-<NUM> where an RFID tag (e.g., RFID tags <NUM><NUM>,. , <NUM>N, <NUM><NUM>,. , or 118x of <FIG>) is activated and placed in a time slot determining mode.

In the time slot determining mode, the RFID tag is assigned to a time slot (e.g., time slot <NUM><NUM> of <FIG>) of a plurality of time slots (e.g., time slots <NUM><NUM>, <NUM><NUM>,. , <NUM>Y of <FIG>). This is achieved through (I) operations performed by the RFID tag and/or (II) operations performed by a remote device (e.g., tag reader <NUM> of <FIG> or server <NUM> of <FIG>).

In the first case (I), operations <NUM>-<NUM> are performed by the RFID tag. These operations involve: determining the RFID tag's unique code (e.g., unique ID <NUM> of <FIG>); and using the unique code to determine which time slot(s) the RFID tag should listen for an interrogation signal from a tag reader and respond to the same. In this regard, the RFID tag can be programed with an algorithm for translating the unique code to a time slot value or with a look-up table indicating a mapping of unique codes to time slot values. The translation can be achieved by using the unique code as an input to a pre-defined algorithm to compute a time slot value.

In the second case (II), operations are performed by the remote device(s). These operations involve: selectively assigning at least one time slot to the RFID tag; and communicating information identifying the selectively assigned time slot(s) to the RFID tag. The time slot assignment can be on a chaotic/random/pseudo-random algorithm and/or in accordance with a unique code-to-time slot translation or mapping scheme. Accordingly, <FIG> includes optional block <NUM> where the RFID tag receives time slot information from a remote device.

Upon completing <NUM> or <NUM>, method <NUM> continues with <NUM> where an operational mode of the RFID tag is transitioned from the time slot determining mode to a power recharging mode. In some scenarios, the operational state or mode change is achieved by changing the binary value of at least one state or mode bit (e.g., from <NUM> to <NUM>, or vice versa) for causing certain communication control operations to be performed by the RFID tag. Additionally or alternatively, a switch can be actuated for creating a closed or open circuit. The present solution is not limited in this regard.

In the power recharging mode, a rechargeable power source (e.g., power source <NUM> of <FIG>) is recharged using energy (e.g., RF energy) harvested by an energy harvesting circuit (e.g., energy harvesting circuit <NUM> of <FIG>) of the RFID tag. Notably, at least one communication operation and/or the RFID tag's communication device (e.g., communication device <NUM> of <FIG>) is disabled or bypassed in the power recharging mode. Other functions/operations of the RFID tag may also be disabled in this mode for power conservation purposes.

Next, a decision is made as to whether it is time for the RFID tag to communicate with a tag reader. This decision can be achieved using knowledge of the time slot(s) assigned to the particular tag. If it is not the RFID tag's time to communicate with a tag reader [<NUM>:NO], then method <NUM> returns to <NUM>. In contrast, if it is the RFID tag's time to communicate with a tag reader [<NUM>:YES], then method <NUM> continues with <NUM> where the operational mode of the RFID tag is transitioned from the power recharging mode to a communications mode in which at least one communications operations and/or communication device (e.g., transceiver) is enabled or no longer bypassed. Thereafter in <NUM>, an interrogation signal is received at the RFID tag. Interrogation signals are well known in the art, and therefore will not be described herein. In response to the interrogation signal, the RFID tag generates and transmits a tag response message, as shown by <NUM>. Tag response messages are well known in the art, and therefore will not be described herein. Still, it should be noted that the tag response message can include the RFID tag's unique identifier (e.g., unique identifier <NUM> of <FIG>) therein. The present solution is not limited to the particulars of <NUM>-<NUM>. For example, a number of iterations of communications operations (e.g., transmit and receive operations) can be performed prior to continuing to <NUM>.

Next in <NUM>, the operational mode of the RFID tag is transitioned back to the power recharging mode in which at least communications operations and/or device (e.g., transceiver) is/are disabled and/or bypassed. Subsequently, <NUM> is performed where method <NUM> ends or other processing is performed (e.g., return to <NUM>).

The method <NUM> described above provides a solution to real time inventory, but does not include a way to detect changes to inventory due to removal of RFID tags from an RSF (e.g., RSF <NUM> of <FIG>) between respective adjacent time slots (e.g., because of sale or theft). Accordingly, method <NUM> can be modified to include additional operations for detecting and accounting for tag movement at all times during an inventorying process. Such a modified method is discussed below in relation to <FIG>.

Referring now to <FIG>, there is provided an illustration that is useful for understanding methods for determining inventory using motion triggered time slotted tag communications. As shown in <FIG>, the third tag performs communication (e.g., transceiver) operations in time slots <NUM>V, <NUM>V+<NUM>, <NUM>V+<NUM> in addition to its assigned time slot <NUM><NUM>. These time slots <NUM>V, <NUM>V+<NUM>, <NUM>V+<NUM> occur during a period of time when the third tag is in motion. This allows tag readers to see moving RFID tags quickly, as well as helps at a Point Of Sale ("POS") and to determine whether the RFID tags were moved into a high risk area (e.g., a fitting room or bathroom).

Referring now to <FIG>, there are provided illustrations that are useful in understanding the contents of tag response messages. In some scenarios, the tag response message <NUM> includes only a unique tag identifier <NUM> (e.g., unique ID <NUM> of <FIG>). In other scenarios, the tag response message <NUM> includes a motion indicator <NUM> in addition to the unique tag identifier <NUM>. The motion indicator <NUM> indicates whether the tag is currently in motion, is in a given operational state/mode, and/or has a given motion sensor state.

Referring now to <FIG>, there is provided a flow diagram of an illustrative method <NUM> for determining inventory using time slotted tag communications. Method <NUM> begins with <NUM> and continues with <NUM>-<NUM>. <NUM>-<NUM> are the same as or substantially similar to <NUM>-<NUM> of <FIG>. The above discussion of <NUM>-<NUM> is sufficient for understanding <NUM>-<NUM>. Notably, a new block <NUM> is provided in which method <NUM> continues to <NUM> of <FIG> when a determination is made in <NUM> that it is not the RFID tag's time to communicate with the tag reader.

Upon completing <NUM>, method <NUM> continues with <NUM> of <FIG>. As shown in <FIG>, <NUM> involves performing operations by a motion sensor (e.g., motion sensor <NUM> of <FIG>) to detect motion of the RFID tag (e.g., RFID tag <NUM><NUM>,. , <NUM>N, <NUM><NUM>,. , or 118x of <FIG>). Next in <NUM>, the motion sensor performs operations to notify a controller (e.g., controller <NUM> of <FIG>) of the RFID tag that motion has been detected. The motion sensor also provides motion sensor data to the controller. In <NUM>, the motion sensor data is analyzed to determine if the RFID tag is traveling through a facility. This analysis can be performed by the RFID tag's controller and/or a remote device (e.g., a tag reader or server). The analysis can involve detecting pre-defined patterns of movement specified in the motion sensor data (e.g., a walking pattern, a running pattern, or a vehicle traveling pattern). If a determination is made that the RFID tag is not traveling through a facility (e.g., RSF <NUM> of <FIG>) [<NUM>:NO], then <NUM> is performed where method <NUM> ends or other processing is performed (e.g., return to <NUM>).

In contrast, if a determination is made that the RFID tag is traveling through a facility [<NUM>:YES], then <NUM> is optionally performed where a WOT is determined during which the RFID tag's communication operation(s) and/or communication device (e.g., transceiver) is to be operational, enabled or no longer bypassed. <NUM> is optional since the RFID tag can be pre-programed with a WOT value. In other scenarios, a value for the WOT is determined by the RFID tag and/or a remote device. The WOT value is determined based on environmental conditions and/or system conditions. Notably, the WOT value is variable. This feature of the present solution allows minimization of the RFID tag's system power, minimizes tag read collisions, and identification of moving RFID tags without reading all static/stationary RFID tags.

Once the RFID tag has knowledge of the WOT value, then <NUM> is performed where its operational mode is transitioned from the power recharging mode to the communications mode in which at least one communication operation and/or communication device (e.g., transceiver) is enabled or no longer bypassed. In the communications mode, the RFID tag uses an internal clock/timer (e.g., clock/timer <NUM> of <FIG>) to determine if the WOT has expired. If not [<NUM>:NO], then the RFID tag performs operations in <NUM> to receive and respond to at least one interrogation signal. If so [<NUM>:YES], then <NUM>-<NUM> are repeated until motion is no longer detected, a stationary state signal has been communicated from the tag to a tag reader, a power source (e.g., power source <NUM> of <FIG>) has a certain level of charge, and/or a control signal is received from an external device to disable or bypass the communication operations and/or device (e.g., transceiver). Subsequently, <NUM> is performed where method <NUM> ends or other processing is performed (e.g., return to <NUM> of <FIG>).

The present solution has many advantages. For example, the present solution: solves real time, daily, accurate inventory with a low cost tag reader infrastructure; solves an overhead RFID as EAS problem; is able to accurately track moving tags; identify tags leaving a store even when there are a relatively large number of tags in proximity to the exit; and improves ecommerce processes by providing accurate inventory count and RFID tag locations at all times. The present solution is also greener since it limits the amount of time RF devices are enabled.

The present solution can be used in conjunction with other sensors, such as proximity sensors. For example, if proximity sensors detect the presence of individuals in the facility, then the stationary tag readers can be temporarily disabled (e.g., until there are no more people in the facility).

The RFID tags of the present solution are relatively small with good read range. This allows the RFID tags to be added to animals (e.g., humans, pets, etc.). In this case, the RFID tags can be configured to have enabled communication operations and/or devices (e.g., transceivers) only during times of detected movement thereof. The RFID tags could also be placed on wearable items (e.g., hats, belts, etc.) in a manner that does not interfere with the wearing humans.

As noted above, the present solution uses a mobile shopping app, shopping website or self-checkout station to enable purchase transactions. The purchase transactions involve the scanning of the UPC or Electronic Product Codes ("EPC") associated with a product. The solution may use multiple tagging technologies in conjunction with each other or a single technology. The security tag protects the product and a secondary tag has a unique product identifier. The secondary tag could be an RFID tag that uniquely identifies the product by including the EPC. The RFID tag may be incorporated into the security tag as a dual technology tag for a single security tag option or as a separate tag on the product. The dual technology security tag may have a barcode identifying the encoded EPC. Alternatively or additionally, the EPC may be encoded in a way where the UPC is included in the EPC.

The security tags can include, but are not limited to, pin based tags (e.g., security tag <NUM> shown in <FIG>, security tag <NUM> shown in <FIG>, and/or security tag <NUM> shown in <FIG>), pad based tags (e.g., security tag <NUM> shown in <FIG>, security tag <NUM> shown in <FIG>, and/or security tag <NUM> shown in <FIG>), and/or pin less tags (e.g., security tag <NUM> shown in <FIG>). The security tags are designed to be easily detached, relatively inexpensive, and are each a single unit.

The pin based tags <NUM>, <NUM>, <NUM> can be implemented with push buttons <NUM>, <NUM> having two states similar to a pen (i.e., a first state in which a pin <NUM> is extended out of a tag body <NUM> and a second state in which the pin <NUM> is withdrawn into the tag body <NUM>). A disable toggle switch <NUM> may be provided to disable operations of the push button. Toggle switches are well known in the art, and therefore will not be described in detail herein. Any known or to be known toggle switch can be used herein without limitation. The disable toggle switch <NUM> can be manually controlled or electronically controlled (e.g., via a motor and a rotatable lever arm <NUM> that can stop a downward motion of the push button). The push buttons can be replaced with threaded actuators <NUM> as shown in <FIG>. The pad based tags <NUM>, <NUM>, <NUM> are similar to the pin based tags except that a pad <NUM> is provided at the free end of the pin. The pad <NUM> may have groves, protrusions or indents formed thereon for gripping an object.

In some scenarios, the security tag is provided with an actuator that is designed to have two modes of operation, namely a first mode of operation in which the actuator acts as a rotary knob and a second mode of operation in which the actuator acts as a push button. An illustrative security tag <NUM> with this design is provided in <FIG>. This tag design makes it difficult for children to detach the security tag <NUM> from an object. In this regard, it should be understood that the clockwise or counter clockwise rotation of an actuator <NUM> enables a button depression feature. If the button depression feature of the actuator <NUM> is disabled, then depression thereof causes the same to contact a stop mechanism <NUM> that is in its protruding positon so as to prevent movement thereof in downward direction <NUM>. If the button depression feature is enabled, then the stop mechanism <NUM> is in its retracted positon in which it no longer prevents downward movement of the actuator <NUM>.

The tag design of <FIG> also provides additional security features to the tag. In this regard, it should be understood that a level <NUM> security protocol is initiated when the actuator <NUM> is rotated in a direction <NUM> at a time when the object (to which it is coupled) has not been successfully purchased. In response to the level <NUM> security protocol initialization, the security tag <NUM> outputs an alarm (e.g., auditory, visual and/or tactile alarm), sets a bit to a value indicating that a detachment attempt was made, and/or communicates a signal to an enterprise system device for notifying store personnel. The alarming can be disabled by rotating the actuator <NUM> from its rotated positon back into its original non-rotated position. The alarming will continue if the actuator <NUM> is thereafter depressed. When the actuator <NUM> is in its depressed position, the security tag level <NUM> security protocol is initialized. The level <NUM> security protocol requires special operations to be performed by store personnel for resetting the security tag's operational mode back into its normal operational mode (i.e., a simple return of the actuator <NUM> to its original non-rotated/undepressed position will not transition the tag from a security protocol mode to a normal operational mode).

The pin less tags can be implemented as spring loaded tags or tags that are detached by breaking a string. An illustration of an illustrative spring loaded tag <NUM> is shown in <FIG>. The spring loaded tag <NUM> operates in a manner similar to an alligator clip such that a spring <NUM> facilitates the holding of an object in a grip area <NUM>.

Cryptography may be employed to provide secure communications between the security tags and other devices (such as mobile devices and an enterprise system). Cryptographic techniques are well known in the art, and therefore will not be described herein in detail. Any known or to be known cryptographic technique can be used herein without limitation. For example, in some scenarios, an encryption technique is employed that requires a challenge/response where the security tag generates a pseudo-random number and combines the same with a unique identifier. The encrypted unique identifier is then sent to the cloud through a mobile device (e.g., a smart phone) where a response from a proper authority is returned for validation within the security tag. In a symmetric key system, the device unique key is used to generate the pseudo-random number. In a public/private key system, the private key is used to generate the pseudo-random number and the public key is stored in the security tag. For low cost CPUs, symmetric keys may be used to preserve power and consumption time at the tag. Either method results in a unique, validated response from the cloud to the security tag. The present solution is not limited to the particulars of the above described example and key based scenarios.

The security model for most tags today depends on the assumption that a special tool is needed to remove the tags. However, these tools are accessible to the general public. Therefore, relying on this security only stops the honest people. If the security tags are designed to have more intelligence and are used with other security means (e.g., cameras, security personnel, and/or artificial intelligence), then a better overall level of security is provided. Additional benefits are provided if the security tags are also designed to be easily removed by the customers. Restrictions may be provided with regard to where the security tags can be detached or deactivated by customers. For example, a person can detach a security tag from an item only when present in a given area of a retail store which comprises RFID readers, cameras and collection bins for detached security tags. The present solution is not limited to the particulars of this example.

The present solution: allows a customer to purchase a product using a mobile device (e.g., a smart phone); provides a customer with a way to detach a security tag using the mobile device or to mark the security tag as being attached to a sold item; eliminates the need for a separate pin that creates a hole in the item; and eliminates the need for a special tool to detach the security tags from items.

The present solution is at least partially achieved by: providing a self-detaching tag; providing a pin less security tag; including a Central Processing Unit ("CPU") with energy harvesting in the security tag that is configured to control a near field data path; including a barcode along with the security tag which can be read by a mobile device; including secure RFID communication capabilities with the security tag; and/or providing a method to mark the security tag as being associated with a sold item.

Referring now to <FIG>, there is provided an illustration of system <NUM>. System <NUM> comprises an EAS system <NUM> disposed in the retail store facility <NUM>. Retail store facility <NUM> can comprise retail store facility <NUM> described above in relation to <FIG>. The EAS system <NUM> comprises a monitoring system <NUM> and security tags <NUM>. The security tags <NUM> can include one or more types of security tags. For example, the security tags include, but are not limited to, the security tags <NUM>, <NUM> described above in relation to <FIG> and/or other security tags (e.g., EAS security tags and/or dual technology EAS/RFID security tags that do not employ time slotting as described above). Although not shown in <FIG>, the security tags <NUM> are respectively attached to objects <NUM> (which may include objects <NUM>, <NUM> of <FIG>), thereby protecting the objects from an unauthorized removal from the retail store facility <NUM>.

The monitoring system <NUM> establishes a surveillance zone (not shown) within which the presence of the security tags <NUM> can be detected. The surveillance zone is established at an access point (not shown) for the retail store facility <NUM>. If a security tag is carried into the surveillance zone, then an alarm is triggered to indicate a possible unauthorized removal of the object <NUM> from the retail store facility <NUM>.

During store hours, a customer (not shown) may desire to purchase the object(s). The customer can purchase the object(s) using a Point Of Sale ("POS") <NUM>. The POS <NUM> can include, but is not limited to, a self-checkout POS station, a Mobile POS ("MPOS") station, or a MPOS device. In all scenarios, a retail transaction application executing on a computing device <NUM> of the POS <NUM> facilitates the exchange of data between the objects <NUM>, security tags <NUM>, customer, and/or Retail Transaction System ("RTS") <NUM> of a corporate facility <NUM>. For example, after the retail transaction application is launched, the customer is prompted to start a retail transaction process for purchasing the objects. The retail transaction process can be started simply by performing a user software interaction, such as depressing a key on a keypad of the computing device <NUM> or touching a button on a touch screen display of the computing device <NUM>.

In the MPOS scenarios, the computing device <NUM> comprises a handheld communication device running the retail transaction application. The handheld communication device includes, but is not limited to, a cellular phone, a smart phone, a portable computer, a tablet, or a personal digital assistant. In some scenarios, the retail transaction application performs a check at the time of installation on the computing device <NUM>. The check is performed to confirm that the computing device <NUM> has an NFC capability and that this capability is enabled. If the computing device <NUM> does not have an NFC capability, then the user is notified of this fact. The user may also be provided with information as to how to make the computing device <NUM> NFC enabled, and/or what versions of the computing device <NUM> are NFC enabled. If the NFC capability is not enabled, then the user of the computing device <NUM> is notified of this fact and instructed to enable the same. The retail transaction application allows the user to input payment information and set personal preferences.

Subsequently, the retail transaction application can optionally communicate with the RTS <NUM> to obtain information relating to sales and/or promotions being offered by the RSF <NUM>. This information is then displayed on a display screen of the computing device <NUM>.

When the customer is ready to purchase an item, the customer may manually input into the retail transaction application object information. Alternatively or additionally, the customer may place the computing device <NUM> of the POS <NUM> in proximity of the object, or vice versa. As a result of this placement, the POS <NUM> obtains object information from the object. The object information includes any information that is useful for purchasing the object, such as an object identifier and an object purchase price. In some scenarios, the object information may even include an identifier of the security tag attached thereto. The object information can be communicated from the object to the computing device <NUM> of the POS <NUM> via a wireless communication, such as a barcode communication, RFID communication, or an NFC.

In the barcode scenario, the object <NUM> has a barcode <NUM> attached to an exposed surface thereof. The term "barcode", as used herein, refers to a pattern or symbol that contains embedded data. Barcodes may include, for example, one-dimensional barcodes, two dimensional barcodes (such as matrix codes, Quick Response ("QR") codes, Aztec codes and the like), or three-dimensional bar codes. The embedded data can include, but is not limited to, a unique identifier of the object and/or a purchase price of the object. The barcode <NUM> is read by a barcode scanner/reader (not shown in <FIG>) of the POS <NUM>. Barcode scanners/readers are well known in the art. Any known or to be known barcode scanner/reader can be used herein without limitation.

In the RFID scenarios, the object information is obtained from the security tag <NUM>. If the security tag <NUM> comprises a time slot based security tag <NUM>, <NUM>, then the security tag is able to respond to signals from the POS <NUM> since its communications operations were enabled as a result of detected motion thereof, and the current time is still within the selected WOT.

In the NFC scenarios, the object <NUM> may comprise an NFC enabled device <NUM>. The NFC enabled device <NUM> can be separate from the security tag or comprise the security tag. An NFC communication occurs between the NFC enabled device <NUM> and the computing device <NUM> over a relatively small distance (e.g., N centimeters or N inches, where N is an integer such as twelve). The NFC communication may be established by touching components <NUM>, <NUM> together or bringing them in close proximity such that an inductive coupling occurs between inductive circuits thereof. In some scenarios, the NFC operates at <NUM> and at rates ranging from <NUM> kbit/s to <NUM> kbit/s. The NFC may be achieved using NFC transceivers configured to enable contactless communication at <NUM>. NFC transceivers are well known in the art, and therefore will not be described in detail herein. Any known or to be known NFC transceivers can be used herein without limitation.

After the POS <NUM> obtains the object information, payment information is input into the retail transaction application of POS <NUM>. The payment information can include, but is not limited to, a customer loyalty code, payment card information, and/or payment account information. The payment information can be input manually, via an electronic card reader (e.g., a magnetic strip card reader), or via a barcode reader. Electronic card readers and barcode readers are well known in the art, and therefore will not be described herein. Any known or to be known electronic card reader and/or barcode reader can be used herein without limitation. The payment information can alternatively or additionally be obtained from a remote data store based on a customer identifier or account identifier. In this case, the payment information can be retrieved from stored data associated with a previous sale of an article to the customer.

Upon obtaining the payment information, the POS <NUM> automatically performs operations for establishing a retail transaction session with the RTS <NUM>. The retail transaction session can involve: communicating the object information and payment information from the POS <NUM> to the RTS <NUM> via a public network <NUM> (e.g., the Internet); completing a purchase transaction by the RTS <NUM>; and communicating a response message from the RTS <NUM> to the POS <NUM> indicating that the object has been successfully or unsuccessfully purchased. The purchase transaction can involve using an authorized payment system, such as a bank Automatic Clearing House ("ACH") payment system, a credit/debit card authorization system, or a third party system (e.g., PayPal®, SolidTrust Pay® or Google Wallet®).

The purchase transaction can be completed by the RTS <NUM> using the object information and payment information. In this regard, such information may be received by a computing device <NUM> of the RTS <NUM> and forwarded thereby to a sub-system of a private network <NUM> (e.g., an Intranet). For example, the object information and purchase information can also be forwarded to and processed by a purchase sub-system <NUM> to complete a purchase transaction. When the purchase transaction is completed, a message is generated and sent to the POS <NUM> indicating whether the object has been successfully or unsuccessfully purchased.

If the object has been successfully purchased, then a security tag detaching/deactivation process can be started automatically by the RTS <NUM> or by the POS <NUM>. Alternatively, the user (not shown in <FIG>) can start the security tag detaching/deactivation process by performing a user-software interaction using the POS <NUM>. In all three scenarios, the object information can optionally be forwarded to and processed by an authorization sub-system <NUM> to generate one or more Tag Deactivate/Detach ("TDD") authorization codes that are useful for ensuring that security tags are only detached from or deactivated when attached to successfully purchased articles. Each TDD authorization code is generated using (a) the unique identifier of the security tag associated with an article which has been successfully purchased and (b) a cryptographic key assigned to the security tag. The TDD authorization code comprises the unique identifier signed using the cryptographic key. Methods for signing information using keys are well known in the art, and therefore will not be described herein. Any known or to be known method for signing data can be used herein without limitation. The TDD authorization code is then sent from the authorization sub-system <NUM> to the POS <NUM>. At the POS <NUM>, the TDD authorization code's signature is decrypted, read and validated. Once validated, the POS <NUM> causes a bit to be set in the security tag indicating that it is associated with a successfully purchased object. The POS <NUM> also stores information in the data store <NUM> (which can comprise data store <NUM> of <FIG>) indicating that the security tag is associated with a successfully purchased object.

Once the security tag has knowledge that it is associated with a successfully purchased object, the security tag performs the following operations: entering an operational mode in which a user is allowed to remove the security tag from the object without alarm issuance (e.g., the alarm is disabled or bypassed); and/or initiating self-detachment operations so that the security tag can be removed from the object relatively easily. The self-detachment operations generally involve causing the security tag to actuate a detaching mechanism (e.g., a motor or a switch <NUM> of <FIG>). For example, operations are performed to (a) cause a mechanical component to no longer prevent downward movement of a push button and/or (b) cause a pin to be retracted such that the security tag can be removed from the object <NUM>. Once the security tag has been removed from the object, the customer can carry the object through the surveillance zone without setting off the alarm.

In some scenarios, the security tag <NUM> comprises a spring loaded tag that connects to the object with pressure. An electrical connection is made by a pin inserted through the object or no longer in contact with the object. A break in or creation of the electrical connection causes a notification and/or other information to be communicated to the server <NUM> (which may include server <NUM> of <FIG>) indicating that the security tag has been removed from the object. The pin may operate similar to a pen (e.g., every time it is clicked it stays in an extend position or in a withdrawn position). In other scenarios, the security tag <NUM> comprises a plastic loop or conductive loop facilitating its attachment/detachment from the object. An electrical connection is made when a free end of the loop is secured to the main body of the security tag. When this electrical connection is broken, the server is notified thereof.

The tag deactivation operations are generally configured to cause an RFID and/or EAS device of the security tag to be deactivated. In this regard, a deactivate command is communicated from the security tag's controller <NUM> to the RFID and/or EAS component (e.g., EAS component <NUM> of <FIG>) of the security tag. The RFID and/or EAS component authenticates the deactivate command and deactivates itself. Once the RFID and/or EAS device has been deactivated, the server is notified thereof (i.e., that the security tag can no longer response to interrogation signals). Also, the customer can carry the object through the surveillance zone without setting off the alarm.

The POS <NUM> and/or server <NUM> performs operations to verify that the security tag is the security tag authorized to be removed from a given object. This verification can be made prior to or subsequent to the tags detachment from the object. This verification is made based on: purchase transaction information; a security tag identifier; an object identifier; timestamped information indicating that the security tag has been removed from a given object; intelligence information specifying the security tags motion during a given period of time; the security tags and/or objects last known location(s); and historical information about the security tag's use, locations in and/or paths of travel through the RSF <NUM>. If such verification is not made, then the security tag is caused to issue an alarm (visual, auditory and/or tactile), and/or transition to a battery assisted mode to increase a read range. Alternatively or additionally, the POS <NUM> outputs an alarm (visual, auditory and/or tactile), and/or store personnel is notified of the unauthorized tag removal. Cameras <NUM> and other security equipment can be employed to correlate a time, place and person associated with the unauthorized tag removal. If such verification is made, then the POS <NUM> outputs instructions to the user to place the security tag in a collection bin <NUM>. Notably, the security tags are re-usable, and therefore can be reprogrammed and attached to other objects.

In some scenarios, a kiosk <NUM> can be employed to facilitate the detachment of the security tags from the objects. For example, a customer carries the already purchased objects to the kiosk <NUM>, and initiates a security tag detachment/disablement process. The kiosk <NUM> comprises a tag reader <NUM> (which can comprise tag reader <NUM> of <FIG>). The tag reader <NUM> communicates with the security tags to inform them that they are now in a location at which they can be removed from the objects. In response to this information, the security tags perform self-detachment or self-deactivation operations.

Referring now to <FIG>, there is provided a flow diagram of an exemplary method <NUM> for security tag detachment or deactivation. Method <NUM> provides a methodology to allow a consumer to remove a security tag from an article (or object) that has been successfully purchased. Currently, there is no process for allowing the customer to detach security tags from products that (s)he has successfully purchased.

As shown in <FIG>, method <NUM> begins with step <NUM> and continues with step <NUM> where a purchase transaction is initiated using a POS (e.g., POS <NUM> of <FIG>). Techniques for initiating such a purchase transaction are well known in the art, and therefore will not be described herein. After completing step <NUM>, step <NUM> is performed where the POS is used to obtain a UPC and/or an EPC for at least one product to be purchased. The UPC uniquely identifies a type of product. The EPC uniquely identifies a particular product. The UPC and/or EPC can be obtained using one or more scanning technologies. The scanning technologies include, but are not limited to, RFID technology, NFC technology and/or barcode technology. In some scenarios, the UPC and/or EPC is obtained from the security tag (e.g., security tag <NUM> of <FIG>). If the security tag is a time slot based security tag (e.g., tag <NUM> or <NUM> of <FIG>), then the communications operations thereof are enabled or no longer being bypassed (responsive to detected motion thereof) such that the tag can respond to messages received thereat from the POS.

The UPC and/or EPC is then communicated to a purchase sub-system (e.g., purchase sub-system <NUM> of <FIG>) to facilitate the retrieval of product information therefrom, as shown by step <NUM>. In this regard, the purchase sub-system may comprise or have access to a remote datastore in which product information was pre-stored. The product information includes, but is not limited to, product descriptions and purchase prices. The purchase sub-system then uses the UPC and/or EPC to obtain any associated product description and pricing information from the remote datastore, as shown by step <NUM>. The product description and pricing information is communicated in step <NUM> to the POS so that it can be displayed to the user thereof.

At this time, a decision <NUM> is made as to whether a UPC and/or EPC has(have) been obtained for each product that is to be purchased. If a UPC and/or EPC has(have) not been obtained for each product that is to be purchased [<NUM>:NO], then method <NUM> returns to <NUM>. In contrast, if the UPC and/or EPC has(have) been obtained for each product that is to be purchased [<NUM>:YES], method <NUM> continues with <NUM>. <NUM> involves completing the purchase transaction for the product(s) associated with the UPC(s) and/or EPC(s) previously obtained. If the purchase transaction was not successful [<NUM>:NO], then <NUM> is performed where the purchase transaction is canceled. If the purchase transaction was successful [<NUM>:YES], then <NUM> is performed for starting a security tag detachment/deactivation process.

<NUM> involves communicating the UPC(s) and/or EPC(s) from the POS to an authorization sub-system (e.g., authorization sub-system <NUM> of <FIG>). In some scenarios, only the UPCs are obtained from the articles to be purchased. In this case, the authorization sub-system will perform actions to identify the particular products that have been purchased using the UPC(s). For example, a look-up table can be used for this purpose. This step is performed so that the authorization sub-system has knowledge of the particular articles which (a) have been successfully purchased and (b) have security tags that need to be deactivated or detached therefrom.

Once the UPC(s) and/or EPC(s) have been received by the authorization sub-system, <NUM> is performed where the authorization sub-system generates a Purchase Transaction Session ("PTS") authorization code and/or a TDD authorization code for each purchased item. The PTS authorization code is generated so as to provide a means for subsequently obtaining a list of TDD authorization codes for items that were successfully purchased during a particular purchase session. The PTS authorization code can include, but is not limited to, a numeric sequence, an alphanumeric sequence, or an alphabetic sequence that uniquely identifies a single purchase transaction process.

The TDD authorization code is generated so as to provide a means for subsequently authorizing the detachment or deactivation of security tags attached only to the previously purchased articles. The TDD authorization code includes, but is not limited to, a numeric sequence, an alphanumeric sequence, or an alphabetic sequence that uniquely identifies a single security tag detachment/deactivation process. The TDD authorization code is generated using a cryptographic key. The cryptographic key is generated using a chaotic, random or pseudo-random algorithm. Chaotic, random or pseudo-random algorithms are well known in the art, and therefore will not be described herein. Any known or to be known chaotic, random or pseudo-random algorithm can be used herein without limitation. In this regard, the TDD authorization code may be a single use code which is generated using a one-time use cryptographic key.

Upon completing <NUM>, method <NUM> continues with <NUM> of <FIG>. As shown in <FIG>, <NUM> involves communicating the PTS authorization code and/or TDD authorization code(s) from the authorization sub-system to the POS, a tag reader (e.g., tag reader <NUM> of <FIG>), or a kiosk (e.g., kiosk <NUM> of <FIG>). Next in optional <NUM>, a notification is output from the POS, tag reader or kiosk. The notification indicates that the authorization code(s) has(have) been successfully received and/or that the user should now proceed to the area of the facility (e.g., retail store facility <NUM> of <FIG>) which contains a security tag collection bin (e.g., security tag collection bin <NUM> of <FIG>), tag reader (e.g., tag reader <NUM> of <FIG>), camera (e.g., camera <NUM> of <FIG>), and/or kiosk (e. g, kiosk <NUM> of <FIG>) if (s)he is not already at the same. In response to the notification, the user optionally proceeds to the area, as shown by <NUM>.

In a next <NUM>, the PTS authorization code is communicated from the POS to the tag reader or kiosk. In turn, the PTS authorization code is communicated from the tag reader or kiosk to the authorization sub-system, as shown by <NUM>. At the authorization sub-system, the PTS authorization code is used in <NUM> to obtain one or more TDD authorization codes associated with items that were successfully purchased during the particular session. Each TDD authorization code includes a security tag identifier signed using a respective cryptographic key. Notably, the security tags have different cryptographic keys assigned thereto. Therefore, a different cryptographic key is used to sign each security tag identifier. In some scenarios, a security tag identifier is signed by combining the same with the respective cryptographic key (which can include, but is not limited to, a chaotic number, a random number, or a pseudo-random number). The signed security tag identifiers are those for the security tags associated with the articles (a) that were successfully purchased by the user and (b) which need to have their security tags detached/deactivated. The signed security tag identifiers can be pre-generated prior to <NUM> or generated in response to the PTS authorization code's reception by the authorization sub-system.

The TDD authorization codes (or signed security tag identifier(s)) is(are) then communicated to the POS, tag reader or kiosk in <NUM>. In <NUM>, the TDD authorization codes (or signed security tag identifier(s)) is(are) communicated to the respective security tag(s). In response to a signed security tag identifier, the security tag performs operations in <NUM> to determine if the unique identifier in the TDD code matches an internally stored identifier. If so, the security tag performs operations to verify the signature of the TDD authorization code (i.e., that the TDD code came from a given source). In a method according to the invention, upon verification of the signature, the security tag sets a status bit to a value (e.g., a "<NUM>" value or a "<NUM>" value) indicating that it is coupled to an article that no longer constitutes inventory to be sold or loaned. Once the status bit value is set, operations are performed by the security tag in <NUM> that may involve: withdrawing a pin (e.g., pin <NUM> of <FIG>) or pad (e.g., pad <NUM> of <FIG>); actuating a mechanical component (e.g., lever arm <NUM> of <FIG>) to allow downward motion of a push button (e.g. push button <NUM> of <FIG>); and/or temporarily disabling alarming functions (e.g., visual, auditory or tactile alarming features). Upon completing <NUM>, method <NUM> continues with <NUM> of <FIG>.

As shown in <FIG>, <NUM> involves optionally performing operations by an enterprise system (e.g., server <NUM> and/or computing device <NUM> of <FIG>) to verify that the security tag was removed from the article based on (a) images captured by at least one camera (e.g., camera <NUM> of <FIG>), (b) a signal received from the security tag indicating that it has been detached from the object, and/or (c) system intelligence of the security tag's motion, path of travel through a facility, and last known location in the facility. In some scenarios, the system intelligence is acquired using information obtained from moving tags as described above in relation to <FIG> (i.e., using information received from the security tag during time slots of a plurality of time slots that are allocated to other security tags, when the security tag is in motion).

If authorization of the security tags detachment was not verified [<NUM>:NO], then <NUM> is performed where an alarm is output from the security tag, tag reader and/or kiosk. Store personnel may also be notified. Thereafter, <NUM> is performed where method <NUM> ends or other processing is performed.

If authorization of the security tags detachment was verified [<NUM>:YES], then <NUM> is performed where the user is optionally presented with a request to place the security tag in the collection bin. Next in <NUM>, a decision is made as to whether the security tags for all articles have been detached. If not, method <NUM> returns to <NUM> of <FIG> as shown by <NUM>. If so, method <NUM> ends or other processing is performed as shown by <NUM>.

Claim 1:
A method for operating a security tag (<NUM>), comprising:
- receiving, by the security tag (<NUM>), an authorization code comprising a security tag identifier signed using a cryptographic key of a plurality of cryptographic keys that are respectively assigned to a plurality of security tags (<NUM>);
- performing operations by the security tag (<NUM>) to determine if the security tag identifier matches an internally stored identifier and if so, performing operations by the security tag (<NUM>) to verify a signature of the authorization code, wherein, upon verification of the signature, the security tag sets a status bit to a value indicating that it is coupled to an article that no longer constitutes inventory to be sold or loaned; and
- responsive to the signature's verification, performing detach operations or deactivation operations by the security tag (<NUM>), where the detach operations cause a mechanical detachment of the security tag (<NUM>) from an item and the deactivation operations cause a disablement of a response by the security tag (<NUM>) to an interrogation signal from a Radio Frequency Identification, RFID, system or an Electronic Article Surveillance, EAS, system (<NUM>);
wherein the authorization code is received by the security tag (<NUM>) from a Point Of Sale (POS) terminal (<NUM>);
further comprising performing operations by the security tag (<NUM>) to notify an enterprise system (<NUM>, <NUM>) of the security tag's mechanical detachment from an item or the disablement of the security tag's ability to respond to the interrogation signal.