CN107667395B

CN107667395B - Automatic removal anti-theft device for retail environments

Info

Publication number: CN107667395B
Application number: CN201680025691.8A
Authority: CN
Inventors: E·P·埃勒斯; T·Z·施杜欧维奇; W·D·阿德力; M·A·路瑞欧
Original assignee: Tyco Fire and Security GmbH
Current assignee: Xianxun Meizi Electronics Co ltd
Priority date: 2015-03-04
Filing date: 2016-03-02
Publication date: 2020-03-17
Anticipated expiration: 2036-03-02
Also published as: US10121338B2; WO2016141039A1; US10522016B2; ES2746916T3; US20190073886A1; EP3265631B1; EP3265631A1; US10121339B2; US20160260303A1; CN107667395A; US20160260302A1

Abstract

A system (100) and method (1500) for operating a security tag. The method involves: converting rotational movement of the pinion gear in a first direction into linear movement of the rack gear in a second direction, thereby transitioning the pin from an unengaged state in which the pin is retracted into the first portion of the housing to an engaged state in which an end of the pin is located in a bore formed in a second portion of the housing, wherein the second portion of the housing is spaced apart from the first portion of the housing; mechanically retaining the pin in the engaged position using a pawl that prevents movement of the pinion in a third direction opposite the first direction; and automatically releasing the pawl in response to receiving the wireless signal at the security tag, thereby returning the pin to the unengaged state.

Description

Automatic removal anti-theft device for retail environments

Technical Field

This document relates generally to security tags used in electronic article surveillance ("EAS") systems. More particularly, the present disclosure relates to security tags and methods for preventing unauthorized removal of items from a given location (e.g., a retail store).

Background

A typical EAS system in a retail establishment may include a monitoring system and at least one security tag or label attached to an item to be protected from unauthorized removal. The monitoring system establishes a monitoring zone in which the presence of security tags and/or labels may be detected. The monitoring area is typically established at an access point (e.g., adjacent to a retail store entrance and/or exit) of the controlled area. If an item with an active security tag and/or indicia enters the monitored area, an alarm may be triggered to indicate that it may be unauthorized removed from the controlled area. In contrast, if an item is authorized to be removed from a controlled area, its security tag and/or marker may be detached therefrom. Thus, items may be carried through the monitoring area without being detected by the surveillance system and/or without triggering an alarm.

Radio frequency identification ("RFID") systems may also be used in retail establishments for inventory management and related security applications. In an RFID system, a reader transmits a radio frequency ("RF") carrier signal to an RFID device. The RFID device responds to the carrier signal with a data signal encoded with information stored by the RFID device. Passive RFID tags are increasingly used in conjunction with EAS tags in retail applications.

As is known in the art, security tags for security and/or inventory systems may be constructed in a number of configurations. The desired configuration of the security tag is often determined by the nature of the article to be protected. For example, an EAS and/or RFID tag may be enclosed in a rigid tag housing that may be secured to an object being monitored (e.g., an article of clothing in a retail store). The rigid housing typically includes removable pins that are inserted through the fabric and secured in place on the opposite side by a mechanism deployed within the rigid housing. The shell cannot be removed from the garment without destroying the shell, except by using a dedicated removal device.

A typical retail sales transaction occurs at a fixed point of sale ("POS") station that is responsible for store sales clerks. Store clerks assist the customer in the checkout process by receiving payment for the merchandise. If the item is associated with an EAS/RFID element, the store clerk removes the security tag from the purchased item using a dedicated removal device.

Alternatively, a retail sales transaction may be performed using a mobile POS unit. Currently, there is no convenient way to remove security tags using mobile POS units. The options include: using a mobile detacher unit in addition to the mobile POS unit; the use of a fixed remover unit located within the retail store, which reduces the mobility of the mobile POS unit; or using a fixed remover unit located at the exit of the retail store, which burdens the customer with post-POS tasks. None of these options are satisfactory for large-scale mobile POS adaptation in the retail industry.

Disclosure of Invention

The present disclosure relates to implementing systems and methods for operating security tags. The method involves: converting rotational movement of the pinion gear (piniongear) in a first direction into linear movement of the rack gear in a second direction, thereby transitioning the pin from an unengaged state in which the pin is retracted into the first portion of the housing to an engaged state in which an end of the pin is located in a bore formed in the second portion of the housing, wherein the second portion of the housing is separated from the first portion of the housing by a gap; mechanically retaining the pin in the engaged position using a pawl that prevents movement of the pinion in a third direction opposite the first direction; and automatically releasing the pawl in response to receiving a wireless signal at the security tag transmitted from a remote external device, thereby returning the pin to the unengaged state, wherein the pin is retracted into the first portion of the housing.

In some scenarios, the rotational motion of the pinion is controlled by a user via a knob disposed on an outer surface of the housing and coupled to the pinion. The spring is disposed on the pin. When the pin is in the unengaged state, the spring is in an at least partially uncompressed state, and when the pin is in the engaged state, the spring is in a compressed state. The pin returns to the unengaged state due to the automatic decompression of the spring immediately after pawl release. The pawl is automatically released by a pushing force applied to the first end of the pawl by a post traveling toward the pawl, which rotates the pawl about the pivot member. The column is driven by an electric solenoid or gear motor. The urging force is of sufficient magnitude to overcome the urging force simultaneously applied to the second end of the pawl, opposite the first end, by the spring plate.

Drawings

Embodiments will be described with reference to the following drawings, wherein like reference numerals represent like items throughout the several views, and wherein:

FIG. 1 is a schematic diagram of an exemplary system useful for understanding the present invention.

FIG. 2 is a block diagram of an exemplary architecture of the security tag shown in FIG. 1.

FIG. 3 is a front perspective view of an exemplary security tag.

FIG. 4 is a rear perspective view of the security tag shown in FIG. 3.

Fig. 5 is a top view of the security tag shown in fig. 3-4.

Fig. 6 is a right side view of the security tag shown in fig. 3-5.

Fig. 7 is a left side view of the security tag shown in fig. 3-6.

Fig. 8 is a bottom view of the security tag shown in fig. 3-7.

Fig. 9-11 provide schematic diagrams useful for understanding the operation of various mechanical components deployed within the security tag shown in fig. 3-8.

FIG. 12 is a schematic diagram useful for understanding how a detent of a security tag is released.

FIG. 13 is a top view of the pawl and pinion.

FIG. 14 is a perspective view of another exemplary security tag.

FIG. 15 is a flow diagram of an exemplary method for operating a security tag.

16A-16D (collectively referred to herein as "FIG. 16") provide a flow chart of another exemplary method for operating a security tag.

Detailed Description

It will be readily understood that the components of the embodiments as generally described herein, and illustrated in the figures, could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the various embodiments, as represented in the figures, is not intended to limit the scope of the disclosure, as claimed, but is merely representative of various embodiments. While various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by this detailed description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present invention should be or are in any single embodiment of the invention. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present invention. Thus, discussion of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same embodiment.

Furthermore, the described features, advantages, and characteristics of the invention 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 invention may 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 invention.

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

As used herein, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art. As used in this document, the term "including" means "including, but not limited to".

The present disclosure relates to a self-detaching solution for a security tag. The self-removal solution allows a customer to select and securely pay for desired items (e.g., using a payment instrument)

Or other cloud-based online service). Once the retail store system has verified the purchase transaction, a wireless command signal is transmitted from the retail store system to the security tag. In response to the wireless command signal, one or both of the following events occur: mechanical components (e.g., solenoids and/or gear motors) are actuated so that a customer can remove the security tag from the purchased item. For example, actuation of the mechanical member causes a catch (captive) pin to be released, whereby the security tag may be removed from the article. The capture pin is fixedly coupled to the housing of the security tag so that it is not likely to be lost or stolen by a customer, or requires the use of two hands to couple/decouple the security tag from the item. This capture pin arrangement also ensures that the security tag is secure without any sharp objects being exposed to the customer during the customer's shopping experience or to store personnel during their routine maintenance.

Notably, the self-removal solution is compatible with existing acousto-magnetic ("AM") detection systems and RFID-enabled inventory tracking systems. Also, it is not necessary or required for a store clerk to remove the security tag from the merchandise. Furthermore, the self-detaching solution facilitates mobile point-of-sale applications because the need for a dedicated detacher device (i.e., a device in which a security tag must be deployed to detach it from the merchandise) has been eliminated.

Exemplary System for customer detachment of Security tags

The present disclosure relates generally to systems and methods for operating a security tag of an EAS system. The method involves: receiving a request to detach a security tag from an item; generating a signal comprising a command to actuate a detachment mechanism of the security tag; and wirelessly transmitting the signal to the security tag to actuate the detachment mechanism. The detachment mechanism may include, but is not limited to, an electromechanical detachment mechanism. The operation of the electromechanical detachment mechanism will be described in detail below. The mechanical detachment portion of the electromechanical detachment mechanism may include, but is not limited to, a pin.

Referring now to FIG. 1, a schematic diagram of an exemplary system 100 useful for understanding the present invention is provided. System 100 is generally configured to allow a customer to purchase an item 102 using a mobile communication device ("MCD") 104 and its optional peripheral device ("PD") 190. The PD190 is designed to be mechanically attached to the MCD 104. In some scenarios, the PD190 surrounds at least a portion of the MCD 104. Communication between MCD 104 and PD190 is implemented using wireless short-range communication ("SRC") technology, such as bluetooth technology. PD190 may also employ other wireless SRC technologies to facilitate purchase of item 102. Other wireless SRC technologies may include, but are not limited to, near field communication ("NFC") technologies, infrared ("IR") technologies, wireless fidelity ("Wi-Fi") technologies, radio frequency identification ("RFID") technologies, and/or ZigBee technologies. The PD190 may also employ barcode technology, electronic card reader technology, and wireless sensor network ("WSN") communication technology.

As shown in fig. 1, system 100 includes a retail store facility 150, retail store facility 150 including EAS 128. EAS128 includes a monitoring system 134 and at least one security tag 132. Although not shown in FIG. 1, the security tag 132 is attached to the item 102, thereby protecting the item 102 from unauthorized removal from the retail store facility 150. The monitoring system 134 establishes a monitoring zone (not shown) within which the presence of the security tag 132 may be detected. The monitoring area is established at an access point (not shown) of the retail store facility 150. If security tag 132 is carried into the monitoring area, an alarm is triggered indicating that item 102 may be removed from retail store facility 150 without authorization.

During store hours, customer 140 may desire to purchase item 102. The customer 140 may purchase the item 102 without using a conventional fixed POS station (e.g., a checkout counter). Alternatively, the purchase transaction may be effected using MCD 104 and/or PD 190. The MCD 104 (e.g., a mobile phone or tablet computer) may be owned by the customer 140 or the store clerk 142 when the purchase transaction is in progress. Notably, the MCD 104 has a retail transaction application installed thereon that is configured to facilitate purchase of the item 102 and management/control of PD190 operations for attaching/detaching the security tag 132 to/from the item 102. The retail transaction application may be a pre-installed application, an add-on application, or a plug-in application.

To initiate a purchase transaction, a retail transaction application is launched via user-software interaction. The retail transaction application facilitates data exchange between the item 102, the security tag 132, the customer 140, the store clerk 142, and/or the retail transaction system ("RTS") 118. For example, after the retail transaction application is launched, the

user

140, 142 is prompted to begin a retail transaction process for purchasing the item 102. The retail transaction process may be initiated simply by performing a user software interaction, such as pressing a key on a keypad of MCD 104 or touching a button on a touch screen display of MCD 104.

The

user

140, 142 may then manually enter item information into the retail transaction application. Alternatively or additionally,

users

140, 142 place MCD 104 near item 102. As a result of such placement, MCD 104 and/or PD190 obtain item information from item 102. The item information includes any information useful for purchasing the item 102, such as an item identifier and an item purchase price. In some scenarios, the item information may even include an identifier of the security tag 132 attached to the security tag 132. Item information may be transferred from item 102 to MCD 104 and/or PD190 via short-range communication, such as barcode communication 122 or NFC 120. In a barcode scenario, the item 102 has a barcode 128 attached to its exposed surface. In the NFC scenario, the item 102 may include an NFC-enabled device 126. If the PD190 obtains the article information, it forwards it to the MCD 104 via a wireless SRC (such as bluetooth communication).

Payment information is thereafter entered by the

user

140, 142 into the retail transaction application of the MCD 104. Upon obtaining payment information, MCD 104 automatically executes a transaction session for establishing a retail with RTS 118The operation of the word. The retail transaction session may involve: communicating the item information and payment information from the MCD 104 to the RTS 118 via the RF communication 124 and the public network 106 (e.g., the internet); the purchase transaction is completed by the RTS 118; and transmit a response message from the RTS 118 indicating that the item 102 has been successfully or unsuccessfully purchased to the MCD 104. The purchase transaction may involve the use of an authorized payment system, such as an automated clearing house ("ACH") payment system, a credit/debit card authorization system, or a third party system (e.g.,

SolidTrust

or Google

)。

The purchase transaction may be completed through the RTS 118 using the item information and the payment information. In this regard, such information may be received by the computing device 108 of the RTS 118 and thereby forwarded to a subsystem of the private network 100 (e.g., an intranet). For example, the item information and purchase information may also be forwarded to and processed by the purchasing subsystem 112 to complete the purchase transaction. When the purchase transaction is completed, a message indicating whether the item 102 has been successfully or unsuccessfully purchased is generated and sent to the MCD 104.

If the item 102 has been successfully purchased, the security tag detachment process may be initiated automatically by the RTS 118 or by the MCD 104. Alternatively,

users

140, 142 may begin the security tag detachment process by performing a user-software interaction using MCD 104. In all three scenarios, the item information may optionally be forwarded to lock release subsystem 114 and processed by lock release subsystem 114 to retrieve a detach key or detach code useful for detaching security tag 132 from item 102. A teardown key or code is then sent from the RTS 118 to the MCD 104 so that the MCD 104 can perform or cause the PD190 to perform a tag teardown operation. The tag detachment operation is generally configured to cause security tag 132 to actuate a detachment mechanism (not shown in FIG. 1). In this regard, the MCD or PD generates a detach command and sends a wireless detach signal including the detach command to security tag 132. Security tag 132 authenticates the detach command and activates the detach mechanism. For example, the detach command retracts the pin so that the security tag may be removed from the article 102. Once security tag 132 has been removed from item 102, customer 140 may carry item 102 through the monitoring area without raising an alarm.

Referring now to FIG. 2, a schematic diagram of an exemplary architecture of a security tag 132 is provided. Security tag 132 may include more or fewer components than shown in fig. 2. The components shown, however, are sufficient to disclose an illustrative embodiment for practicing the invention. Some or all of the components of security tag 132 may 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 hardware architecture of fig. 2 represents an embodiment of a representative security tag 132 configured to facilitate preventing unauthorized removal of an item (e.g., item 102 of fig. 1) from a retail store facility (e.g., retail store facility 150 of fig. 1). In this regard, security tag 132 may have a barcode 138 attached thereto to allow data to be exchanged with an external device (e.g., PD190 of fig. 1) via barcode technology.

Security tag 132 also includes an antenna 202 and an NFC-enabled device 136 to allow data to be exchanged with external devices via NFC technology. The antenna 202 is configured to receive NFC signals from external devices and transmit NFC signals generated by the NFC-enabled device 136. The NFC-enabled device 136 includes an NFC transceiver 204. NFC transceivers are well known in the art and will not be described here. However, it should be understood that the NFC transceiver 204 processes the received NFC signal to extract the information therein. Such information may include, but is not limited to, a request for certain information (e.g., unique identifier 210), and/or a message including information specifying a removal key or code for removing security tag 132 from an item. The NFC transceiver 204 may pass the extracted information to the controller 206.

If the extracted information includes a request for certain information, controller 206 may perform operations to retrieve unique identifier 210 and/or item information 214 from memory 208. The item information 214 may include a unique identifier of the item and/or a purchase price of the item. The retrieved information is then transmitted from security tag 132 to the requesting external device (e.g., PD190 of fig. 1) via NFC communication.

Conversely, if the extracted information includes information specifying a one-time-use key and/or instructions for programming the security tag 132 to actuate the demolition mechanism 250 of the electromechanical lock mechanism 216, the controller 206 may perform an operation using the one-time-use key to simply actuate the demolition mechanism 250. Alternatively or additionally, the controller 206 may: parsing information from the received message; retrieve the tear down key/code 212 from the memory 208; and comparing the parsed information with the teardown key/code to determine if there is a match between them. If there is a match, the controller 206 generates and sends a command to the electromechanical lock mechanism 216 for actuating the demolition mechanism 250. When detachment mechanism 250 is actuated, an audible or visual indication may be output by security tag 132. If there is no match, controller 206 may generate a response message indicating that the teardown key/code specified in the extracted information does not match the teardown key/code 212 stored in memory 208. The response message may then be transmitted from security tag 132 to the requesting external device (e.g., PD190 of fig. 1) via wireless short-range communication or wired communication via interface 260. The message may also be transmitted to another external device or network node via interface 260.

In some scenarios, the connections between the

components

204, 206, 208, 216, 260 are unsecure connections or secure connections. As used herein, the phrase "unsecure connection" refers to a connection that does not employ a password and/or tamper-resistance measures. As used herein, the phrase "secure connection" refers to a connection that employs a password and/or anti-tampering measures. Such anti-tampering measures include encapsulating a physical electrical link between two components in a tamper-resistant enclosure.

Notably, the memory 208 can be volatile memory and/or non-volatile memory. For example, the memory 208 may include, but is not limited to, random access memory ("RAM"), dynamic random access memory ("DRAM"), static random access memory ("SRAM"), read only memory ("ROM"), and flash memory. The memory 208 may also include unsecure memory and/or secure memory. As used herein, the phrase "unsecure memory" refers to memory configured to store data in plain text form. As used herein, the phrase "secure memory" refers to memory configured to store data in encrypted form and/or memory having or disposed in a secure or tamper-resistant enclosure.

The electromechanical lock mechanism 216 is operable to actuate the detachment mechanism 250. The detachment mechanism 250 may include a lock configured to move between a locked state and an unlocked state. Such a lock may include, but is not limited to, a pin. The electromechanical lock mechanism 216 is shown indirectly coupled to the NFC transceiver 204 via the controller 206. The present invention is not limited thereto. The electromechanical lock mechanism 216 may additionally or alternatively be coupled directly to the NFC transceiver 204. One or more of the

members

204, 206 may transition the lock of the detachment mechanism 250 between states based on information received from an external device (e.g., the PD190 of fig. 1). The members 204, 208, 260 and the battery 220 may be collectively referred to herein as the NFC-enabled device 136.

The NFC enabled device 136 may be incorporated into a device that also houses the electromechanical lock mechanism 216, or may be a separate device that communicates directly or indirectly with the electromechanical lock mechanism 216. The NFC enabled device 136 is coupled to a power source. The power source may include, but is not limited to, a battery 220 or an A/C power connection (not shown). Alternatively or additionally, the NFC-enabled device 136 is configured as a passive device that derives power from an RF signal inductively coupled to the device.

Exemplary Security tag architecture

An exemplary architecture for security tag 300 will now be described in detail in conjunction with fig. 3-12. Security tag 134 is the same as or similar to security tag 300. Thus, the following discussion of security tag 300 is sufficient to understand the various features of security tag 134.

As shown in fig. 3-8, security tag 300 includes a hard EAS tag formed from a molded plastic housing 302. EAS and/or RFID elements (not shown in fig. 3-12) may be housed within the housing 302. The housing 302 is defined by first and

second housing portions

304, 306 fixedly coupled to one another (e.g., via an adhesive, ultrasonic welding, and/or a mechanical coupler 400 such as a screw).

The housing 302 has an insertion space 402, the insertion space 402 being sized and shaped to receive at least a portion of an article (e.g., the article 102 of FIG. 1) such that the security tag 300 may be fixedly attached or coupled thereto. Security tag 300 is fixedly coupled to an article by transitioning pin 308 from the unengaged state shown in fig. 9 to the engaged state shown in fig. 3-9 and 11. The transition is accomplished by moving the pin 308 out of the first portion 310 of the housing 302, through the insertion space 402, and into the second portion 312 of the housing 302. A knob 314 is provided to allow the user to control the transition. The knob may be disposed on a side surface of the housing 302, as shown in fig. 3-11, or alternatively on another surface (e.g., a top surface) of the housing, as shown in fig. 12. A mechanical mechanism (shown in fig. 3-8) holds the pin 308 in its engaged state.

Referring now to fig. 9-11, the internal components of security tag 300 will be described. As noted above, the EAS/RFID element, the NFC-enabled device (e.g., NFC-enabled device 136 of fig. 1-2), and/or the electromechanical lock mechanism (e.g., electromechanical lock mechanism 216 of fig. 2) are disposed within the security tag 300. The EAS/RFID element and NFC-enabled device are not shown in fig. 9-11 merely to simplify the schematic thereof.

As shown in fig. 9, electromechanical lock mechanism 900 of security tag 300 includes pin 308,

linear actuators

902, 906, spring 904, spring plate 908, pawl 922, and electric solenoid 910. The electromechanical lock mechanism 900 is not limited to these components. For example, the electric solenoid 910 may be replaced by a gear motor. Electric solenoids and gear motors are well known in the art and will not be described herein. Any known or to be known electric solenoid and/or gear motor may be used herein without limitation so long as its overall dimensions conform to the dimensional requirements of security tag 300.

The linear actuator includes a pair of

gears

902 and 906 that convert the rotational motion of the circular gear 906 into linear motion of the linear gear 902. The circular gear 906 is referred to herein as a pinion gear, while the linear gear 902 is referred to herein as a rack gear. The knob 314 facilitates user-controlled rotational movement of the pinion 906. Thus, the pinion 902 is coupled to the knob 314 such that it rotates with the knob 314. For example, when the knob 314 is rotated by a user in the direction indicated by arrow 912, the pinion 902 rotates in that direction.

The pinion gear 902 has a plurality of teeth 914 that mesh with a plurality of teeth 916 of the rack 902. The meshing of the teeth 914, 916 allows rotational motion applied to the pinion 906 via the knob 314 to cause the rack 902 to move, thereby transforming the rotational motion of the pinion 906 into linear motion of the rack 902.

The rack 902 is fixedly coupled to the pin 308. Thus, linear movement of the rack 902 in the direction 918 causes the pin 308 to move linearly in the same direction. Likewise, linear movement of the rack 902 in the direction 920 causes the pin 308 to move linearly in the same direction. As the rack 902 moves in the direction 920, the pin 308 transitions from its unengaged position shown in fig. 9 to an intermediate position shown in fig. 10.

In the intermediate position, the end 1002 of the pin 308 extends into the insertion space 402. Also, the rack 902 applies a pushing force to the spring 904, which compresses the spring. In practice, the pin/gear arrangement is spring loaded and it is desirable to return to the unengaged position when the pin 208 is in its neutral position (and when in its fully engaged position).

The pin 308 is held in its intermediate position via a pawl 922. In this regard, the pawl 922 engages the pinion 902 and is pivotally coupled to the housing via the pivot member 924. A schematic diagram useful for understanding the mechanical relationship between these

members

902, 922 is provided in fig. 13. As shown in FIG. 13, the pawl includes a protrusion 1306 that slidingly engages the teeth 914 of the pinion gear 902. The sliding engagement is facilitated by the chamfered surfaces 1304 of the protrusions 1306 and the chamfered surfaces 1302 of the teeth 914. As the pinion gear 902 rotates in direction 912, the chamfered surface 1304 slides along an outer surface of the pinion gear 902, which is at least partially defined by the chamfered surface 1302 of the teeth 914. In effect, the protrusion 1306 of the pawl enters and exits the space 1308 existing between adjacent teeth 914 of the pinion gear 902. The spring tabs 908 facilitate the travel of the projections back into the spaces 1308.

When the protrusion 1306 resides in the space 1308, the pin 308 remains in a given position because the pawl 922 prevents the pinion from rotating in a direction opposite the direction 912. Preventing rotation of the pinion gear in a direction opposite direction 912 is at least partially facilitated by straight surface 1310 of pawl 922, wherein pawl 922 meshes with teeth 914 in a manner that does not allow protrusion 1306 to enter and exit space 1308 due to pinion gear travel in a direction opposite direction 912.

Referring now to FIG. 11, a schematic illustration of the pin 308 in its fully engaged position is provided. As shown in fig. 11, the end 1002 of the pin 308 extends into a hole 1102 formed in the second portion 312 of the housing 302. Also, the spring 904 is in its fully compressed state. In practice, the pin/gear arrangement is spring loaded and it is desired to return to the unengaged position. Thus, when the pawl 922 is released, the pin is retracted into the first portion 310 of the housing 302, which causes the spring to automatically transition from its compressed state to its natural uncompressed state. During this transition, the rack 902 is able to travel freely in direction 918.

Referring now to fig. 12, a schematic diagram is provided that is useful for understanding how the pawl 922 is released. As noted above, the detaching operation of security tag 300 is initiated via the receipt of a wireless detach signal by security tag 300 from an external device (e.g., PD190, MCD 104, and/or RTS 118 of fig. 1). Upon such receipt, security tag 300 authenticates the detach command and activates the detach mechanism (i.e., electrical solenoid 910). The electric solenoid 910 is activated by supplying power thereto. The electric solenoid 910 drives the post 1202 such that it moves in a direction 1204 to exert a pushing force on the pawl 1204. The urging force is of sufficient magnitude to overcome the urging force applied to the pawl 922 through the spring plate 908. Application of a pushing force through the post 1202 causes the pawl 922 to transition from its engaged state shown in fig. 9-11 to its disengaged state shown in fig. 12. In fact, the pinion 906 is free to move in direction 1206. Thus, the pin 308 can be retracted from its engaged state due to decompression of the spring 904. Once the pin 308 has been fully retracted, the security tag 300 may be removed from the article (e.g., article 102 of FIG. 1) to which it is attached. In this case, a customer (e.g., customer 140 of FIG. 1) may carry the item through the monitoring area without triggering an alarm.

Exemplary method for operating a Security tag

Referring now to FIG. 15, a flow diagram of an exemplary method 1500 for operating a security tag is provided. Method 1500 begins at step 1502 and continues with step 1504, where a security tag (e.g., security tag 132 of FIG. 1 or security tag 300 of FIG. 3) is attached to an article (e.g., article 102 of FIG. 1). This step involves rotating a knob (e.g., knob 314 of FIG. 3) of the security tag to transition a pin (e.g., pin 308 of FIG. 3) to an engaged position (as shown in FIG. 11). The manner in which the pin transitions to its engaged position is described above with respect to fig. 9-11.

At some time thereafter, a decision step 1506 is performed that determines whether the purchase transaction has been successfully executed. If the purchase transaction is unsuccessful [ 1506: no ], then the method 1500 returns to step 1504. Conversely, if the purchase transaction is successful [ 1506: yes ], then step 1508 is performed in which the security tag detachment process is initiated either automatically by the MCD (e.g., MCD 104 of fig. 1), the PD (e.g., PD190 of fig. 1), the RTS (e.g., RTS 118 of fig. 1), or in response to a user-software interaction with the MCD, PD, or RTS. The security tag removal process involves the operations performed in steps 1510-1520. These steps involve: generating and transmitting a signal to the security tag, the signal comprising a detach command for actuating a detach mechanism of the security tag; wirelessly receiving a signal at a security tag; and authenticating the detach command at the security tag.

If the tear down command is not authenticated [ 1516: no ], optional step 1518 is performed in which the MCD, PD, RTS, and/or user detach command is notified that it is not authenticated by the security tag. Subsequently, the method 1500 returns to step 1510.

If the tear down command is authenticated [ 1516: yes ], then the security tag's detachment mechanism (e.g., electric solenoid 910 of fig. 9) is activated, as shown at step 1520. Such activation may be accomplished simply by supplying power to the detachment mechanism such that a detent (e.g., detent 922 of fig. 9) is released. Release of the pawl may be accomplished in the manner described above with respect to fig. 12.

Referring now to FIG. 16, a flow diagram of another exemplary method 1600 for operating a security tag (e.g., security tag 132 of FIG. 1 or security tag 300 of FIG. 3) is provided. The method 1600 begins at step 1602. Although not shown in fig. 16, it should be understood that user authentication operations and/or function enablement operations may be performed prior to step 1602. For example, a user of an MCD (e.g., MCD 104 of fig. 1) may be authenticated, and thus one or more retail transaction operations of the MCD may be enabled based on a permission (clearance) level of the user and/or a location of the MCD within a retail store facility (e.g., retail store facility 150 of fig. 1). The location of the MCD can be determined using GPS information. In some scenarios, the "heartbeat" signal may be used to enable retail transaction operation(s) of the MCD and/or PD (e.g., PD190 of fig. 1). The "heartbeat" signal may be transmitted directly to the MCD or indirectly via the PD.

After step 1602, the method 1600 continues with step 1604 in which a customer (e.g., customer 140 of FIG. 1) enters the retail store facility and accumulates one or more items to be purchased (e.g., items 102 of FIG. 1). In some scenarios, the customer may request a store clerk (e.g., store clerk 142 of FIG. 1) to assist in purchasing the accumulated items. This may be performed when customer 140 does not have an MCD (e.g., MCD 104 of fig. 1) and/or a PD (e.g., peripheral device 190 of fig. 1) coupled thereto on which the retail transaction application is installed. If the customer owns such an MCD, the customer will not require the assistance of a store clerk to complete the purchase transaction and/or remove the security tag from the item, as shown in step 1606-1614.

In a next step 1606, the customer performs a user-software interaction with the MCD and/or the PD to cause a retail transaction application installed on the MCD to be run. The customer then scans each item for reimbursement using the MCD and/or PD. Scanning may be accomplished using a barcode scanner, RFID scanner, NFC tag scanner, or any other short-range communication device of the MCD and/or PD. Alternatively or additionally, the customer may enter a voice command to confirm each item he wants to purchase.

Once the item has been scanned, payment information is entered into the retail transaction application of the MCD, as shown in step 1610. The payment information may include, but is not limited to, customer loyalty codes, payment card information, and/or payment account information. The payment information may be manually entered using an input device of the MCD or PD, via an electronic card reader (e.g., a magnetic stripe card reader) of the MCD or PD, and/or via a barcode reader of the MCD or PD.

After the payment information is entered into the retail transaction application, a decision step 1612 is performed to determine if the purchase transaction has been completed. Web-based payment services may be used (e.g., using

Wallet or other cloud-based online service) completes the purchase transaction. The determination of step 1612 is made by the web-based payment service system based on information received from the MCD and/or the RTS (e.g., RTS 118 of fig. 1). If the purchase transaction is not complete [ 1612: whether or not]Then the method 1600 returns to step 1612. If the purchase transaction is complete [ 1612: is that]Then the method 1600 continues with step 1614.

In step 1614, the web-based payment service system generates and sends a purchase token to the MCD. The purchase token may also be transmitted from the web-based payment service system and/or the MCD to each security tag attached to the purchased goods. The purchase token stored in the memory device of the security tag may later be used to (1) assist in determining the cause of a failure that occurred with respect to the detachment of the security tag from the item and/or (2) whether the recently discovered security tag was removed from the purchased item or the stolen item. (1) The solutions of (1) and (2) will be discussed in detail below.

Upon completion of step 1614, the MCD transmits the purchase token and the unique identifier for each purchased product from the MCD to a server (e.g., server 108 of fig. 1) 1 located at a corporate facility (e.g., corporate facility 152 of fig. 1) via a secure communication link, as shown in step 1616. In a next step 1618, the server performs an operation of verifying the purchase token using the web-based payment service. If the purchase token is not verified [ I620: no ], then the method 1600 returns to step 1610. If the purchase token is verified [ 1620: yes ], then method 1600 continues with step 1622 of fig. 16B.

As shown in fig. 16B, step 1622 involves generating and transmitting a signal from a server located in the corporate facility to a server (e.g., server 192 of fig. 1) located in a retail store facility (e.g., retail store facility 150 of fig. 1). The signal includes a command to initiate a teardown procedure. The signal is forwarded to a gateway (e.g., gateway 190 of fig. 1), coordinator or sub-coordinator, as shown at step 1624. A wireless signal is generated at the gateway/coordinator/sub-coordinator, the wireless signal including a detach command for actuating a detach mechanism of the security tag(s) attached to the purchased item(s), as shown at step 1626. The wireless signal is then transmitted to the security tag(s).

After receiving the wireless signal in step 1630, the security tag authenticates the detach command. If the tear down command is not authenticated [ 1632: no ], optional step 1634 is performed in which the MCD, PD, RTS, and/or user detach command is notified that it is not authenticated by the security tag. Method 1600 then returns to step 1626. If the tear down command is authenticated [ 1632: yes ], a security tag detachment mechanism (e.g., the electrical solenoid 910 of fig. 9) may be activated, as shown in step 136. Such activation may be accomplished simply by supplying power to the detachment mechanism such that a detent (e.g., detent 922 of fig. 9) is released. Release of the pawl may be accomplished in the manner described above with respect to fig. 12.

Next, a decision step 1638 is performed to determine whether the pawl is actually released. If the pawl is actually released [ 1638: yes ], then method 1600 continues with step 1640. In step 1640, the security tag is removed from the item that has been successfully purchased. The removed security tag may be placed in a collection bin for later use or placed elsewhere in the retail store facility (e.g., a dressing room), as shown at step 1642. Method 1600 then continues to decision step 1644 of FIG. 16C where it is determined whether a security label is placed in the collection bin.

If the security tag is placed in the collection bin [ 1644: yes ], then step 1646 is performed, where the method 1600 ends. Conversely, if the security tag is not placed in the collection bin [ 1644: NO ], then step 1648-1650 is performed. These steps involve: looking for security tags (e.g., in a dressing room); and wirelessly communicating with the security tag to obtain purchase token and/or item information therefrom. The purchase token and/or item information is then used to determine whether a security tag is attached to the purchased item. If the security tag is attached to the purchased item [ 1652: yes ], then step 1654 is performed, where the method 1600 ends. If the security tag is not attached to the purchased item [ 1652: NO ], then step 1656-1660 is performed. These steps involve: identifying an item to which the security tag is attached using item information; optionally performing an act of reporting the stolen item; and optionally taking remedial action.

Conversely, if the pawl is not released [ 1638: NO ], then the method 1600 proceeds to step 1662-1672 of FIG. 16D. These steps involve: wirelessly communicating with a security tag to obtain purchase token and/or item information therefrom; and using the purchase token and/or the item information to determine whether the security tag is associated with a successful purchase of the item to which it is attached. If the security tag is not associated with a successful purchase of the item to which it is attached [ 1666: NO ], then step 1668 is performed in which the method 1610 re-executes the purchase transaction associated with the particular item. If the security tag is associated with a successful purchase of the item to which it is attached [ 1666: yes ], then an operation is performed to repair any electrical and/or mechanical failure of the security tag in order to release the security tag from the article. Subsequently, step 1672 is performed, wherein method 1600 ends.

All of the devices, methods, and algorithms disclosed and claimed herein can be made and executed without undue experimentation in light of the present disclosure. While the invention has been described in terms of preferred embodiments, it will be apparent to those of ordinary skill in the art that variations may be applied to the apparatus, methods and in the sequence of steps of the method without departing from the concept, spirit and scope of the invention. More specifically, it will be apparent that certain components may be added to, combined with, or substituted for the components described herein while the same or similar results would be achieved. All such similar substitutes and modifications apparent to those skilled in the art are deemed to be within the spirit, scope and concept of the invention as defined.

The above-disclosed features and functions, and alternatives, may be combined in many other different systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art, each of which is also intended to be encompassed by the disclosed embodiments.

Claims

1. A method for operating a security tag, comprising:

converting rotational movement of a pinion gear in a first direction into linear movement of a rack gear in a second direction, thereby transitioning a pin from an unengaged state in which the pin is retracted into a first portion of a housing to an engaged state in which an end of the pin is located in a bore formed in a second portion of the housing, wherein the second portion of the housing is separated from the first portion of the housing by a gap;

mechanically retaining the pin in the engaged position using a pawl that prevents movement of the pinion in a third direction opposite the first direction; and

automatically releasing the pawl in response to receipt at the security tag of a wireless signal transmitted from a remote external device, whereby the pin returns to the unengaged state in which the pin is retracted into the first portion of the housing.

2. The method of claim 1, wherein the rotational movement of the pinion gear is controlled by a user via a knob disposed on an outer surface of the housing and coupled to the pinion gear.

3. The method of claim 1, wherein the rack is fixedly coupled to the pin.

4. The method of claim 1, wherein a spring disposed on the pin is in an at least partially uncompressed state when the pin is in the unengaged state, and the spring is in a compressed state when the pin is in the engaged state.

5. The method of claim 4, wherein the pin returns to the unengaged state due to automatic decompression of the spring immediately after release of the pawl.

6. The method of claim 1, wherein the pawl is automatically released by a pushing force applied to the first end of the pawl by a post traveling toward the pawl that rotates the pawl about a pivot member.

7. The method of claim 6, wherein the pushing force is of sufficient magnitude to overcome a pushing force simultaneously applied to a second end of the pawl by a spring tab abutting against the second end of the pawl opposite the first end.

8. The method of claim 6, wherein the post is driven by an electric solenoid or gear motor.

9. A security tag, comprising:

a housing having a first portion separated from a second portion by a gap;

a pinion pivotally disposed within the first portion of the housing;

a rack disposed within the first portion of the housing, the rack converting rotational motion of a pinion in a first direction to linear motion in a second direction;

a pin coupled to the rack for linear movement therewith in a second direction, thereby transitioning the pin from an unengaged state in which the pin is retracted into the first portion of the housing to an engaged state in which an end of the pin is located in a bore formed in the second portion of the housing;

a pawl configured to mechanically hold the pin in an engaged position by preventing the pinion from moving in a third direction opposite the first direction; and

an electronic circuit disposed in the housing, the electronic circuit operable to cause automatic release of the pawl in response to receiving a wireless signal at the electronic circuit.

10. The security tag according to claim 9, wherein the pin returns to the unengaged state when the pawl is released.

11. The security tag according to claim 9, wherein the rotational movement of the pinion gear is controlled by a user via a knob disposed on an outer surface of the housing and coupled to the pinion gear.

12. The security tag according to claim 9, wherein a spring disposed on the pin is in an at least partially uncompressed state when the pin is in the unengaged state, and the spring is in a compressed state when the pin is in the engaged state.

13. The security tag according to claim 12, wherein the pin returns to the unengaged state due to automatic decompression of the spring immediately after release of the pawl.

14. The security tag according to claim 9, wherein the pawl is automatically released by a pushing force applied to the first end of the pawl by a post traveling toward the pawl that rotates the pawl about a pivot member.

15. The security tag according to claim 14, wherein the urging force is of sufficient magnitude to overcome an urging force simultaneously applied to a second end of the pawl by a spring tab abutting against the second end of the pawl opposite the first end.

16. The security tag according to claim 14, wherein the post is driven by an electric solenoid or a gear motor.

17. The security tag according to claim 9, wherein the electronic circuit authenticates a command contained in the wireless signal prior to automatically releasing the pawl.

18. The security tag according to claim 9, wherein the automatic release of the pawl is facilitated by supplying power to an electric solenoid or gear motor.

19. The security tag of claim 9, wherein the electronic circuit is a near field communication ("NFC") enabled device.

20. The security tag of claim 9, wherein an electronic article surveillance ("EAS") marker or a radio frequency identification ("RFID") marker is disposed within the housing.