Patent Grant
7132947
The field of the present invention relates to data reading systems and electronic article security (EAS) systems. In particular, a method and apparatus are described herein for controlling and operating a checkout system including both a data reading system such as a barcode scanner and an EAS system.
In both retail checkout and inventory control environments, items are typically provided with readable ID tags. These ID tags may comprise optical labels such as barcode labels or electronic tags such as RFID tags. Data reading devices such as barcode scanners and RFID readers are provided at the checkout station to read the ID tags and obtain the data contained therein. The data may be used to identify the article, its price, and/or other characteristics or information related to checkout or inventory control. These data readers automate the information retrieval to facilitate and speed the checkout process. Thus data readers such as barcode scanners are pervasive at retail checkout.
Scanners generally come in three types: (a) handheld, such as the PowerScan™ scanner, (b) fixed and installed in the countertop such as the Magellan® scanner, or (c) a hybrid scanner such as the Duet® scanner usable in either a handheld or fixed mode. Each of these scanners is manufactured by PSC Inc. of Eugene, Oreg. In a typical retail checkout operation, checkout clerk uses either a handheld scanner to read the barcode symbols on the articles one at a time or passes the articles through the scan field of the fixed scanner one at a time. The clerk then places the articles into a shopping bag or other suitable container.
Though barcodes provide for rapid and accurate item identification at checkout, the barcodes do not provide for item security against theft. Electronic article surveillance (EAS) systems have employed either reusable EAS tags or disposable EAS tags to monitor articles to prevent shoplifting and unauthorized removal of articles from store. Reusable EAS tags are normally removed from the articles before the customer exits the store. Disposable EAS tags are generally attached to the packaging by adhesive or are disposed inside item packaging. These tags remain with the articles and must be deactivated before they are removed from the store by the customer.
EAS tags are generally classified into two categories: so-called “hard” tags which can be sensed but not deactivated and so-called “soft” tags which can be sensed and deactivated. Hard tags are tags such as attached to clothing which must be removed by the store clerk using a special tool at the store checkout. Soft tags since they can be deactivated need not be removed. Certain types of soft EAS tags are reactivatable which is useful in applications such as library books and video rentals.
One type of EAS tag comprises a length of amorphous magnetic material which is positioned substantially parallel to a length of magnetizable material used as a control element. When an active tag, i.e., one having a magnetized control element, is placed in an alternating magnetic field, which defines an interrogation zone, the tag produces a detectable valid tag signal. When the tag is deactivated by demagnetizing its control element, the tag no longer produces the detectable tag signal and the tag is no longer responsive to the incident energy of the EAS system so that an alarm is not triggered.
Such deactivation of the tag, can occur, for example, when a checkout operator in a retail establishment passes an EAS tagged article over a deactivation device located at the checkout counter thereby deactivating the tag.
Generally, deactivation devices of tags include a coil structure energizable to generate a magnetic field of a magnitude sufficient to render the tag “inactive.” In other words, the tag is no longer responsive to incident energy applied thereto to provide an output alarm or to transmit an alarm condition to an alarm unit external to the tag.
Examples of deactivation devices include those sold under the trademarks Speed Station® and Rapid Pad® available from Sensormatic Electronics Corporation of Boca Raton, Fla. The Rapid Pad® deactivator, which generates a magnetic field when a tag is detected, has a single or planar coil disposed horizontally within a housing. Deactivation occurs when the tag is detected moving horizontally across in a coplanar disposition and within a four inch proximity of the top surface of the housing located on top of a check-out counter. The Speed Station® deactivator has-a housing with six coils orthogonally positioned therein to form a “bucket-like” configuration. The operator inserts an article or plurality of articles into the open side of the bucket. The operator then deactivates the inserted articles by manually triggering the deactivator.
U.S. Pat. No. 5,917,412 discloses an EAS tag deactivation device including a deactivating coil having first and second coil parts. The first coil part is positioned in angular adjacent relation to the second coil part so that the coil parts are adapted to transmit simultaneously a deactivating field. The deactivating field forms a deactivation zone having a configuration which permits for deactivation of an active EAS tag when the active EAS tag is situated within the deactivation zone.
There have been attempts to integrate the structure of a barcode scanner with an EAS deactivation system. In one system, an EAS deactivation coil is disposed around the horizontal scan window of a two-window “L” shaped scanner such as the Magellan® scanner. In such a system, barcode scanning and EAS tag deactivation are accomplished generally within the same volume. The deactivation either takes place at the same time as the scanning, or the deactivation may be controlled to activate after a successful barcode read.
Deactivation of a tag attached to an article is sometimes ineffective for various reasons. This failure to deactivate can result in false alarming of the EAS system which is undesirable. The present inventors have recognized the need for enhanced operation protocols for controlling operation of the scanner and deactivation unit to allow for handling of various operation scenarios, particularly where the EAS deactivation system is integrated within the scanner housing.
The present invention is directed to systems for and methods of operation of a data reader and security tag deactivation system. In a first preferred configuration, a data reader such as a barcode scanner is equipped with EAS deactivation coils or modules disposed in the vicinity of the read volume or generally proximate thereto and the system is operable to permit reading of the ID tag (such as the barcode label) on an item, and upon a successful read, the deactivation unit is operable to (1) sense the presence of an EAS tag; (2) if presence of an EAS tag is sensed, energize the deactivation coil/module to deactivate the EAS tag; and (3) sense if the EAS tag is deactivated. If the EAS tag is sensed to have been deactivated, the system signals as such and a next item may be scanned. If the EAS tag is sensed to have not been deactivated, the system proceeds to alternate operational steps to handle the exception.
In another function, the system may operate to enhance EAS tag deactivation by urging the operator to return the item to the read volume such as by delaying a good read acknowledgment, usually signified by an audible “beep” until the system determines that the EAS tag which may have been previously detected has subsequently been deactivated.
Preferred embodiments of the present invention will now be described with reference to the drawings. To facilitate description, any reference numeral representing an element in one figure will represent the same element in any other figure.
A deactivation device 10 as illustrated in
The coil(s) are adapted to transmit magnetic fields for altering the magnetic properties of an active EAS tag placed in proximity to the coil(s) 14. The power source unit 16 controls the operation of the deactivation unit 12 in terms of energizing the deactivating coil(s) 14. The power source unit 16 is connected to the unit 12 by a cable 24 and comprises a power generator 20 and a discharge switch 22 controlled via signal from a microprocessor 18.
The system is applicable to any type of EAS tags such as magnetoacoustic, magnetomechanical, magnetostrictive, RF (e.g. RFID tag), microwave, and harmonic type tags. One example tag 5 is illustrated in
During operation of the deactivation device 10, a microprocessor 18 receives an input signal over input line 40 indicating that a tag is present at the deactivation device for deactivation. The signal can be generated in a similar fashion as in prior art deactivators, such as the deactivator described in U.S. Pat. No. 5,341,125, hereby incorporated by reference. Such deactivators include transmit/receive coils and associated processing circuitry (not shown) for detecting the presence of a tag in the deactivation zone 30 and furnishing the signal over line 40.
Upon receipt of the signal on line 40, the microprocessor 18 initiates a deactivating sequence for the deactivation device 10 by closing a discharge switch 22 that allows the output of a power generator 20 to be connected to the deactivating coil(s) 14. A current then flows in the first and second deactivating coil(s) 14 causing deactivating electromagnetic fields to be transmitted by the coil(s) 14 and a resultant deactivation field is formed in the deactivation zone 30. The resultant deactivation field establishes flux lines along the length of the magnetizable control element 5c of the tag 5, thereby demagnetizing the element.
Though the system and operational methods described herein are applicable to any suitable type of data reader and deactivation system, they are particularly applicable to integrated configurations. Various configurations for integrated data reader and EAS deactivation systems are disclosed in U.S. application Ser. No. 10/062,274 filed Feb. 1, 2002 entitled “COMBINED DATA READER AND ELECTRONIC ARTICLE SURVEILLANCE (EAS) SYSTEM” hereby incorporated by reference.
In the embodiment of
In the device 100, the deactivation unit 150 comprises a central core of magnetically-active material (e.g. iron) with outer wire winding(s) through which current is passed to create the deactivating magnetic field. The housing for the coils can be made of a variety of materials but is preferably injection molded from a non-magnetically active material such as polystyrene or polycarbonate.
Usable with any suitable configuration of the deactivation unit and scanner, following is a description of an operation methodology according to a first preferred embodiment. With current systems, the user is at risk of re-sending product code information (known as a “double read”) if the user attempts to retry to deactivate a security device on a deactivator that is integrated or co-located with a scanner. The Sense-Deactivate-Sense (SDS) methodology of this first preferred embodiment provides a way to retry deactivation of the same article without sending multiple indications to the POS. This methodology provides for a secure interlock between a scanner and an EAS controller that assures that a product with a security device will be recognized and deactivated before processing the indicia of the next product.
The basic structure of the Sense-Deactivate-Sense (SDS) methodology requires that a valid barcode (or other indicia) be detected by the scanner, after which the scanner arms an EAS controller (Controller), allowing the EAS security device (Device) deactivation for a pre-determined period of time (Arming Period). Three outcomes are possible while the Controller is armed:
(1) The Controller senses an EAS Device and attempts deactivation. It then attempts to sense the EAS Device again and if it does not, reports Device Detected and Device Deactivated to the scanner. OR
(2) The Controller senses an EAS Device and attempts deactivation. It then attempts to sense the EAS Device again and if it does, it continues the deactivate-sense cycle while the arming period lasts until it either succeeds to deactivate, in which case it reports as in (1) above, or fails to deactivate in which case it reports Device Detected and Device not Deactivated to the scanner. OR
(3) The Controller attempts to sense an EAS Device for some pre-determined period of time (Detection Period) and fails. It reports Device not Detected and Device not Deactivated to the scanner.
The Controller reports one of the above results to the scanner via a communications channel or channels. In the case of result (1) and (3) the scanner continues normal operation and proceeds to look for the next indicia. If result (2) is reported the scanner alerts the operator to a security exception (Exception).
Exception Processing
In the case of an Exception as stated above, the operator may be alerted that an exception occurred. The operator would then place the scanner into an exception state by activating a switch (button, key switch, foot switch, or an audible-activation switch, etc. such as button 160 on the upper section 140 of FIG. 3), reading indicia, or initiating POS intervention (in EAS aware POS systems). While in the exception state the scanner will arm the controller until the Device is deactivated or the exception state is terminated by the operator. The scanner will optionally provide a visual or auditory indication to the operator while in the exception state. While in the exception state any indicia decoded by the scanner must match the indicia associated with the pre-exception deactivation attempt. Upon termination of the exception state the deactivator is disarmed and a deactivate status can optionally be sent to the POS for logging.
In another exception, if the EAS system fails during a transaction, the operator may be alerted and the operator may deactivate the EAS system to allow for the transaction to be completed.
A preferred methodology will now be described with reference to the flow charts of
Step 210—scanning a barcode on an item being passed through a scan volume;
Step 212—processing the barcode and obtaining a valid barcode read;
Step 214—starting the EAS deactivation period timer; typically on the order of about 500 ms, or the timer period may be user programmable as between about 10 ms and 10 seconds.
Step 216—sending an assert deactivation signal to the EAS controller, via arming the EAS controller at Step 218;
Step 220—monitoring the deactivation period timer (which was started at Step 214) and monitoring the communication channel from the EAS controller (from Step 250 described below), and if either (1) the deactivation timer has expired or (2) the deactivation status has been received from the EAS controller, then proceed to Step 222;
Step 222—sending a de-assert deactivation signal to the EAS controller, thus disarming the EAS controller at Step 224.
With the EAS controller being armed at step 218, the EAS controller is operated under the steps of:
Step 240—attempting to sense the presence of an EAS device in the deactivation zone;
Step 242—determining if an EAS device is detected, if “No” return to step 240, if “Yes” proceed to Step 244 (it is noted that the attempt of sensing the EAS tag at Steps 240 and 242 is normally “on” and does not require an activation signal);
Step 244—enabling the deactivation unit if both (1) an EAS device is detected at Step 242 and (2) it is detected per the arm/disarm Step 246 that the arming circuit is armed from Step 218, then proceed to Step 248;
Step 248—determining if the deactivation is still enabled, if “Yes” proceed to Step 252, if “No” (that is if detected at Step 246 that the arming circuit is disarmed per action of Step 224) then proceed to Step 250;
Step 252—generating a deactivation field, by energizing the deactivation coil(s) for deactivating the EAS device;
Step 254—attempting to sense the presence of an EAS device in the deactivation zone, that is confirming whether or not the EAS tag has been deactivated;
Step 256—if an EAS device is still sensed (“Yes”) returning to Step 248 for re-attempting deactivation, and if “No” device is sensed then it is determined that deactivation was successful and proceeding to Step 250 (alternately, Step 256 may be omitted and the method may proceed directly to Step 250 whether or not the EAS device has been detected);
Step 250—sending deactivation status to the scanner at Step 220 (that is, sending status information as to whether or not an EAS device has been detected and, if detected, whether it has been deactivated);
Step 226—once the deactivation status has been received at Step 222, if an EAS device was detected (per Step 242), proceed to Step 228, if an EAS device was not detected, then proceed to Step 230;
Step 228—determining if the EAS device has been deactivated (per Step 256 indication that the tag previously sensed can no longer be sensed), if “Yes” proceed to Step 230 and if “No” proceed to Step 232; also, optionally if “Yes” that a tag was sensed and deemed to have been deactivated, the system may provide for another announcement such as an audible beep tone (distinct from the frequency of the good read beep tone) thereby notifying the operator that a tag was successfully deactivated.
Step 232—signaling “Operator Exception 1” such as by signaling a suitable indicator (visible, audible, vibratory) to the operator and proceeding to the exception methodology 300 of
Step 230—(upon reaching this step, either the EAS device has been deactivated as decided per Step 228 or the system never sensed an EAS device on the item per Step 226 and assumes that there is no EAS device on the item) proceeding to read the next item in the transaction.
Exception Processing
Upon signaling the “Operator Exception 1” at Step 232 of
Step 310—alerting the operator by a suitable indicator (e.g. vibratory, audible, or visible, such as an indicator 162 positioned on the scanner housing illustrated in
Step 312—waiting for the operator to engage exception override (such as by actuating switch 160 on the scanner housing 110 of FIG. 3);
Step 313—starting the override period timer;
Step 314—determining if exception override has been asserted, if “Yes” continue to Step 316, if “No” (meaning that the operator has de-asserted the exception override) proceed to Step 326;
Step 326—de-asserting the deactivation signal via disarming EAS control circuit at Step 326, then proceeding to Step 330;
Step 316—sending an assert deactivation signal to the EAS controller, by arming the EAS control circuit at Step 318;
Step 320—reading the barcode on the item in the scan volume, determining whether the current barcode read is the same as the previous barcode and if “Yes” proceed to Step 332, or if “No” proceed to Step 322 (since the item scan volume is at least partially coexistent with the deactivation volume, during deactivation the barcode on the item may be read additional times, a “double read” prevention protocol prevents multiple reads of the same item from being sent to the POS, but this step also provides security from a user attempting to read the barcode on one item but deactivate the EAS device on another item);
Step 322—alerting the operator that the item being read is different from the item previously read in this exception processing procedure;
Step 324—waiting for operator intervention to handle this apparent switching of items according to store policy.
With the EAS control circuit being armed from Step 318, the EAS controller is operated by the steps of:
Step 342—attempting to sense the presence of an EAS device in the deactivation zone;
Step 344—determining if an EAS device is detected, if “No” return to Step 342, if “Yes” proceed to Step 346 (it is noted that the attempt of sensing the EAS tag at Steps 240 and 242 is normally “on” and does not require an activation signal);
Step 346—enabling the deactivation unit upon detecting at Step 348 that the EAS control circuit is armed and an EAS detection confirmation from Step 344;
Step 350—determining if the deactivation is enabled, if “Yes” proceed to Step 354, if “No” (that is if an EAS disarming signal is received or if no device is detected) then it is determined that deactivation is not successful, and proceed to Step 352 determining if the deactivation is still enabled, if “Yes” proceed to Step 354, if “No” (that it is, if detected at Step 348 that the EAS arming circuit is disarmed per action of Step 335 or 328);
Step 354—generating deactivation signal (i.e. energizing the deactivation coils);
Step 356—attempting to sense the presence of an EAS device in the deactivation zone;
Step 358—determining if an EAS device is still detected, if “Yes” return to step 350 and retry deactivation, if “No” deactivation is determined to be successful (because the EAS device previously detected at Step 344 is no longer detected) then proceed to Step 352 (alternately, Step 358 may be omitted and the method may proceed to directly to Step 352 whether or not the EAS device has been detected);
Step 352—sending deactivation status (that is, whether or not an EAS device has been detected at Step 344 and, if detected, whether it has been deactivated per Step 358) to the scanner at Step 332;
Step 334—de-asserting the deactivation signal via disarming EAS arming circuit at Step 335;
Step 336—if an EAS device was detected (“Yes”) per Step 344, proceed to Step 338, if an EAS device was not detected (“No”), then proceed to Step 330;
Step 338—determining if the EAS device has been deactivated (per Step 358, if an EAS device is not detected, it is believed that the EAS device previously sensed at Step 344 has been deactivated), if “Yes” proceed to Step 330 and if “No” proceed to Step 339;
Step 339—alerting the operator by a suitable indicator (audible, visible or vibratory) that the EAS device has been detected, but have been unable to deactivate;
Step 340—awaiting operator intervention;
Step 330—upon reaching this step (either from a “No” condition from Step 314, a “No” condition from Step 336, or a “Yes” condition from Step 338) optionally providing an indicator signal (e.g. visual or audible) of successful deactivation and permit continuation of normal processing of a next item in the transaction.
In the various embodiments described above, the data reader unit has been generally described as a barcode scanner, but other types of data readers may be combined with the EAS deactivation/activation system. The data reader may be for example a laser barcode scanner, an imaging reader, an RFID reader, or other type of reader for reading optical codes, reading tags, or otherwise identifying items being passed through a scan/read zone.
The housing 110 of the device of
In order for a soft EAS tag to be properly deactivated, the tag must remain in the deactivation field long enough for the deactivation field to complete the change in the tag. For example, in one type of EAS tag system, the EAS detection/deactivation system generates a field of RF energy (sense field) that causes an active EAS tag to resonate at a fixed frequency. Detection of this resonate RF signal allows the deactivation system to “sense” the presence of an EAS tag. A de-activated EAS tag is one that no longer resonates at the specified “sense” frequency. Deactivation may be accomplished when the EAS system generates an RF field (de-activation field) of sufficient energy that changes a tag's resonate frequency. Once deactivated, a tag can no longer be sensed by the EAS system.
Particularly where the deactivation system is integrated into a data reader as in many of the preceding embodiments, in order to ensure that a soft EAS tag is properly deactivated, the tag must remain in the deactivation field long enough for the resonant frequency of the tag to change.
In an alternate embodiment, the system delays providing the barcode “good read” indication (typically the audible “beep” tone) when there is evidence that an EAS tag has been sensed. Having not received a “good read” indication, the operator assumes that the barcode label has not yet been read and will continue to hold the item in the vicinity of the barcode scan volume, or alternately pass the item through the scan volume again. Where the scan volume (or the expected item path) coincides with the EAS sense and deactivation volumes, the scanner can continue to check the success of the deactivation by re-sensing the presence of an EAS tag. If a tag is seen after deactivation, the deactivation is tried again. This deactivate-sense sequence is retried for a configurable number of times. If a tag is sensed after every deactivation, it can be assumed that a hard tag is present and the operator can be alerted to correct the condition. Once the scanner starts to retry the deactivation-sense sequence, the retries are attempted for the configurable retry count, regardless of success of the deactivation-sense sequence.
Alternately, the operating technique of the scanner system may be used to enhance likelihood that an EAS tag on an item is deactivated. A preferred method may include the steps of:
(1) The Controller sensing an EAS tag and providing the sense state to the scanner.
(2) If the sense state is true (a tag has been sensed), the scanner starting a pre-read timer.
(3) If the pre-read timer is not running when barcode is read, asserting the deactivation signal to the Controller for a time period and setting pre-read flag to false and setting the retry flag to false. If the EAS security level is LOW, announcing the barcode read and transmitting the barcode data to the host device.
(4) If a barcode is read by the scanner and pre-read timer is running, asserting the deactivation signal to the Controller for a long time period and setting pre-read flag to true.
(5) If the Controller attempts deactivation during the deactivation time period (step 3 or 4 above), the Controller notifying the scanner, and the scanner de-asserting the deactivation signal to the Controller.
(6) When the Controller notifies the scanner that the sense state is valid, the scanner begins monitoring the sense state from the Controller, the scanner monitoring the sense state until the Controller notifies the scanner that it is ready to deactivate.
(7) If the tag is not sensed during the monitoring period in step (6), providing an indication that the barcode has been read (such as by the scanner emitting an audible “beep”) and transmitting the barcode data to the host device.
(8) If during this monitoring period a tag is sensed, setting the retry flag to true and incrementing a sense counter.
(9) For a programmable number of retries, the scanner reasserting the deactivation signal to the Controller for a long time period, the scanner continuing this process from step (5).
(10) After exhausting the retry attempts, if a tag is sensed after every retry attempt the scanner providing notification of a hard tag. That is, that the type of tag that has been sensed could not be deactivated, thus it is presumed to be a non-deactivatable hard tag which must be manually removed from the item by, for example, the store clerk using a suitable removal device.
(11) If the deactivation time period started in steps 3 or 4 expires, the scanner de-asserting the deactivation signal to the Controller.
(12) If the deactivation signal asserted in step 3 or 4 times out and pre-read flag is true then the scanner continuing this process from step (9).
(13) If no retries are attempted or total retries have been tried and the EAS Security level is HIGH, then the scanner indicating a barcode read (e.g. by audibly announcing the barcode by a “beep”) and transmitting the barcode to the host device.
It is noted that when the EAS controller sends its sense state to the scanner, the data sense may also include operating condition data indicating the operating status or health of the EAS controller. Thus, at initialization or periodically, the scanner monitors the operating health of the EAS controller and alerts the operator and/or the POS. For example, if the signal indicated that the deactivator is non-functional, then the scanner may indicate such failure to the operator and shut down scanner operation. In such a system, the user operates through a single interface of the scanner.
The actual announcing may occur at the scanner itself, which is typical because that is where the scanning of the item takes place, but it may alternately be at the POS terminal or cash register.
As for the delay in the good read announcement, such delay may be implemented in several alternate methods. For example, the system may operate that the good read “beep” is not actuated until (1) the scanner transmits data of a good read to the POS terminal; (2) the POS terminal determines that the barcode data identifies an item in the POS lookup table. The POS may function in combination with the scanner in making the decisions as to delaying announcing the good read. Thus the delaying step may be accomplished by any one or a combination of the following steps:
Referring to
Step 410—attempting to sense an EAS tag and determining if an EAS device is detected, if “Yes” proceed to Step 412, if “No” proceed to Step 414 (it is noted that the attempt of sensing the EAS tag at Step 410 is normally “on” and does not require an activation signal).
Step 412—setting the Sense variable to TRUE (indicating that an EAS tag was sensed at Step 410) then returning to Step 410 via the sense indicator 416.
Step 414—setting the Sense variable to FALSE (indicating that an EAS tag was not sensed at Step 410) then returning to Step 410 via the sense indicator 416.
The sense flag or indicator 416 provides for connection between the EAS controller side of the system and the scanner side of the system. As will be described below, the scanner at Step 442 will be able to receive indication from the flag 416 of the sense state, that is whether the sense state is set to TRUE or FALSE.
When the system is on, the EAS controller cycles through the tag sensing state at a speed of about ten millisecond (10 ms) per cycle. Thus the sense state at the flag 416 will change rapidly depending upon whether an EAS tag was sensed on a given cycle. The cycle speed may be selected based upon system design requirements or other criteria.
Turning to the scanner side, the scanner commences at start Step 440 either on power-up, re-awakening from sleep mode or otherwise being in an “ON” mode, and proceeds according to the following steps:
Step 442—determining whether the EAS tag sense is set to TRUE or FALSE; if set to TRUE (“Yes”), proceeding to Step 444 and if not set to True (“No”) skipping Step 444 and proceeding directly to Step 446.
Step 444—starting/restarting pre-read flag timer. The pre-read timer is a countdown timer which counts down a period of time within which certain barcode reading activities are to take place as described below. The countdown time may be a fixed amount (e.g. preset at time of manufacturers or programmable (e.g. set by the user or the store technician). The pre-read timer is typically set in a range of about 0.5 to 2.5 seconds. After the pre-read timer is started/restarted, the system proceeds to Step 446.
Step 446—looking for a barcode. The scanner seeks and attempts to find a barcode in its scan region.
Step 448—determining if a valid barcode has been read: if “No” returning to Step 442 and if “Yes” proceeding to Step 450.
It is worthwhile to note that the time for the system cycling through Steps 442 through 448 can vary depending upon system design, or may be set by the manufacturer, or may be a variable as set by the user or system technician. In one embodiment, the cycle speed of the scanner is about five millisecond (5 ms). This cycle speed is about twice the cycle speed of the EAS controller cycle—2× oversampling. Thus the scanner is checking for the most recent sense state for the EAS controller. Moreover, the system may also detect a transition signal within the sense state received from the flag 416. For example, if the flag is in the process of changing from “True” to “False”, that occurrence would more likely be an indication that an EAS tag is in the region. The system may thus consider a transition signal to be a “True” signal.
Step 450—if a barcode is read “YES” at step 448, determining if the pre-read timer is still running: if “Yes” proceed to Step 454, if “No” proceed to Step 452.
Step 452—if “YES” from Step 450, setting the pre-read flag to TRUE (meaning that the tag was detected before the barcode was read within the pre-read flag timer), canceling the pre-read timer (setting the flag timer to zero), and setting the retry timer to false (initializing the retry timer).
Step 454—asserting EAS deactivation signal for LONG period by sending an arming signal via 455 to the EAS arming control 418, then proceeding to Step 464. The LONG period allows for a longer period of arming the deactivator (relative to the SHORT period of Step 458) in the condition that a tag is believed more likely to be present.
Step 456—if “NO” from Step 450, setting pre-read flag to FALSE (meaning that a tag was not detected during the pre-read flag timer period) and setting retry flag to FALSE (initializing the retry flag to false); then proceeding to Step 458.
Step 458—asserting EAS deactivation signal for SHORT period (short arming period relative to LONG period); by sending an arming signal via 455 to the EAS arming control 418, then proceeding to Step 460.
The time that the EAS controller can deactivate (ARM time) is extended during the LONG period (Step 454) to allow for greater certainty of deactivation for items with tags. The SHORT period (Step 458) is used primarily to maximize item throughput (i.e., minimize average item time) for items without EAS tags. The LONG and SHORT periods may be either preset or customer configurable depending upon customer preference relating to a balance as between throughput speed and security. For example the SHORT period is typically on the order of about 500-1000 ms, and the LONG period is typically on the order of 3-5 seconds. These timer periods may be user programmable as between about 10 ms and 10 seconds.
These arming timers may be coordinated with other timers used in the decoding system. For example, in a decoding system where a timer is set to prevent multiple reads of the same item/barcode, that timer may be used to extend the ARM time to prevent premature expiration/termination of the arming period. Use of this decode timer may be particularly useful where the scan volume is not co-extensive with either the EAS sensing volume or the EAS deactivation volume.
Step 460—determining if EAS security level is LOW; if “NO” skip step 462 and proceed to Step 464; if “YES” proceed to Step 462.
This EAS security level setting may be another user configurable parameter allowing the user to choose security level depending upon customer preference relating to the balance as between throughput speed and security. A “LOW” security level is selected if faster throughput speed is preferred; a “HIGH” security level is selected if higher security is preferred.
Step 462—announcing barcode “good read” indication (typically the audible “beep” tone) and transmitting barcode data to the terminal. Thus at LOW security level, a good barcode read is acknowledged immediately after decoding, thereby enhancing throughput speed.
Step 464—following Step 462 or 454, determining whether the deactivation signal (which had been asserted in Step 458 or Step 454) has timed out; if “YES” proceed to Step 466, if “NO” proceed to Step 478.
Step 466—disarming EAS system (i.e. by sending a deassert deactivation signal to the EAS arm controller 420 via disarm controller signaler 467).
Steps 468, 470—determining whether pre-read flag (from Steps 452 and 456) is TRUE or FALSE; if pre-read flag is TRUE proceed to Step 470 and set RetryFlag to TRUE then proceed to Step 472; if pre-read flag is FALSE, skip Step 470 and proceed directly to Step 472.
Step 472—determining whether RetryFlag is set to TRUE or FALSE; if TRUE proceed to Step 482, if FALSE proceed to Step 474.
Step 474—determining if EAS security level is set to LOW (this setting is a user-configurable setting as described above); if “NO” proceeding to Step 482, if “YES” proceeding back to Start Step 440.
Returning to the EAS Controller, the controller includes an arming control 420 for receiving the arming/disarming signals from the scanner. The EAS deactivation sequence is operated by the steps of
Step 422—determining whether the deactivator is active, i.e. whether it has received an arming signal from the controller 420; if “NO” cycling back and checking again, if “YES” proceeding to Step 424.
Step 424—determining whether EAS tag has been sensed at Step 410 (i.e. from sense state 416 whether Set Sense=TRUE); if “NO” returning to Step 422, if “YES” passing to Step 426.
Step 426—firing deactivator (activating deactivator coil 14 from
Step 428—determining whether the system is ready to sense for an EAS tag; if “NO” cycling/repeating this Step 428, if “YES” passing to Step 430. When the deactivator 12 fires, the deactivator coil 14 generates a large magnetic field pulse for attempting to deactivate the EAS tag which has been sensed. This magnetic pulse is electromagnetically disruptive and takes a discrete amount of time to dissipate sufficiently that the EAS sensing at Step 410 is effective/reliable. This status check will allow for the system to delay attempting to sense during this period that the magnetic pulse is dissipating.
Step 430—Sending status that sensing system is operational again after deactivation pulse (Sense=OK).
Step 432—determining whether the deactivator is ready for deactivation; if “NO” cycling/repeating this step, if “YES” passing to Step 434.
Step 434—sending status that the deactivator is ready (Deactivator=READY). After the deactivator has fired, it takes a certain amount of time for the deactivator to recharge and be enabled to fire a new pulse. Steps 432 and 434 provide a status check to ensure that the deactivator has been recharged.
Returning to the scanner operation:
Step 478—determining if the deactivator has been fired; if “NO” returning to Step 464, if “YES” proceeding to Step 479.
Step 479—disarming the EAS system (i.e. sending a deassert deactivation signal to the EAS arm controller 420 via disarm controller signaler 480). It is noted that the deactivator fired status in the arm control 420 is reset by disarming.
Step 481—determining if it is ok to sense, i.e. that the signal has been received from EAS controller Step 430 that the magnetic field pulse has sufficiently dissipated; if “NO” cycle and repeat Step 481, if “YES” proceed to Step 482.
Step 482—determining whether an EAS tag was sensed from Step 416; if “YES” proceeding to Step 484, if “NO” passing to Step 483.
Step 483—determining whether ready status was received (Deactivator=ready from Step 434); if “NO” cycling back to Step 482, if “YES” proceeding to Step 488.
Step 484—(from “YES” decision in Step 482) setting RetryFlag to TRUE and incrementing SenseCount. SenseCount is a variable counting the occurrences each time an EAS tag is sensed.
Step 486—determining whether ready status was received (Deactivator=Ready from Step 434); if “NO” cycling this Step 486, if “YES” proceeding to Step 488.
Step 488—determining whether RetryFlag is TRUE; if “NO” proceeding to Step 498, if “YES” passing to Step 492.
Step 492—incrementing the RetryCount, then passing to Step 494. The RetryCount is the number of unsuccessful deactivation attempts (i.e. the number of times the deactivator has been fired in an attempt to deactivate a sensed EAS tag) whereby the EAS tag is nonetheless still sensed after the deactivation attempt.
Step 494—determining whether SenseCount is greater than or equal to MaxRetry; if “NO” pass to Step 498, if “YES” proceed to Step 497.
Step 497—announcing that a hard tag is present. Such announcing may be accomplished by sounding a certain audible tone, preferably distinct from the good barcode read “beep” tone of the scanner and/or visual indication to the operator such as an exception light 180 on the scanner 100. If a tag is continued to be sensed after the MaxRetry number of attempts to deactivate, it is presumed that the tag is a non-deactivatable hard tag which must be manually removed from the item by, for example, the store clerk.
Step 498—announcing a good read, and transmitting the barcode data to the terminal or host (such as the POS terminal); then returning to the start Step 440 for the next item read. Such announcing may comprise the typical good barcode read “beep” tone of the scanner.
The above methods/systems may provide one or more of the following advantages:
Though certain of the preferred embodiments have described systems and methods where the scanner subsystem and EAS controller subsystem operate along parallel processing paths, the system may comprise varying levels of integration. For example, the subsystems may be operated by separate processors with the subsystems communicating only along the various communication paths shown in the various flow charts. Alternately, the system may be constructed with a higher level of integration whereby the subsystems share the same processor and/or other electronics. In such a more integrated system, the communication paths may be internal or even deemed eliminated.
Though the preferred embodiments have been primarily described with respect to sensing and deactivating EAS tags, it would be understood that the systems and methods described herein may apply to other types of electronic tags such as RFID tags or security electronics incorporated into the electronics of a product itself, such as disclosed in U.S. patent application Ser. No. 09/597,340 hereby incorporated by reference.
Though the embodiments have been described primarily with respect to barcode readers, it is understood that they may comprise other types of data readers such as readers for reading other types of identification code labels (e.g. 1-D, 2-D, PDF-417), RFID tags, imaging readers such as have suggested for identifying items based on their physical images such as for identifying produce. The readers may also comprise hybrid combination readers that read multiple types of tags. Thus for purposes of this disclosure, an ID tag is defined as any suitable device which contains data which may be obtained by a reader. Suitable ID tags include, but are not limited to: optical code labels or tags, electronic tags such as RFID tags, or the like.
Thus the present invention has been set forth in the form of its preferred embodiments. It is nevertheless intended that modifications to the disclosed scanning systems may be made by those skilled in the art without altering the essential inventive concepts set forth herein.
This application claims priority to provisional application Ser. No. 60/353,139 filed Feb. 1, 2002 and to provisional application Ser. No. 60/443,421 filed Jan. 28, 2003 entitled SYSTEMS AND METHODS FOR OPTICAL READING AND EAS TAG SENSING AND DEACTIVATING AT RETAIL CHECKOUT.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4141078 | Bridges, Jr. et al. | Feb 1979 | A |
| 4575624 | Klinkhardt | Mar 1986 | A |
| 4652863 | Hultman | Mar 1987 | A |
| 4728938 | Kaltner | Mar 1988 | A |
| 4745401 | Montean | May 1988 | A |
| 4752758 | Heltemes | Jun 1988 | A |
| 4960651 | Pettigrew et al. | Oct 1990 | A |
| 4964053 | Humble | Oct 1990 | A |
| 5059951 | Kaltner | Oct 1991 | A |
| 5103235 | Clemens | Apr 1992 | A |
| 5139100 | Brauneis | Aug 1992 | A |
| 5142292 | Chang | Aug 1992 | A |
| 5210524 | Schwarz et al. | May 1993 | A |
| 5225807 | Zhou et al. | Jul 1993 | A |
| 5341125 | Plonsky et al. | Aug 1994 | A |
| 5376923 | Kindschy | Dec 1994 | A |
| 5377269 | Heptig et al. | Dec 1994 | A |
| 5410108 | Williams et al. | Apr 1995 | A |
| 5587703 | Dumont | Dec 1996 | A |
| 5588621 | Collins et al. | Dec 1996 | A |
| 5635906 | Joseph | Jun 1997 | A |
| 5747744 | Kraft et al. | May 1998 | A |
| 5837988 | Bobba et al. | Nov 1998 | A |
| 5841348 | Herzer | Nov 1998 | A |
| 5886336 | Tang et al. | Mar 1999 | A |
| 5917412 | Martin | Jun 1999 | A |
| 5939984 | Brady et al. | Aug 1999 | A |
| 5955951 | Wischerop et al. | Sep 1999 | A |
| 5963134 | Bowers et al. | Oct 1999 | A |
| 5978772 | Mold | Nov 1999 | A |
| 5984182 | Murrah | Nov 1999 | A |
| 5990794 | Alicot et al. | Nov 1999 | A |
| 6025780 | Bowers et al. | Feb 2000 | A |
| 6102290 | Swartz et al. | Aug 2000 | A |
| 6114961 | Denholm et al. | Sep 2000 | A |
| 6121878 | Brady et al. | Sep 2000 | A |
| 6154135 | Kane et al. | Nov 2000 | A |
| 6154137 | Goff et al. | Nov 2000 | A |
| 6169483 | Ghaffari et al. | Jan 2001 | B1 |
| 6206285 | Baitz et al. | Mar 2001 | B1 |
| 6208235 | Trontelj | Mar 2001 | B1 |
| 6234394 | Kahn et al. | May 2001 | B1 |
| 6237852 | Svetal et al. | May 2001 | B1 |
| 6252508 | Vega et al. | Jun 2001 | B1 |
| 6281796 | Canipe et al. | Aug 2001 | B1 |
| 6299702 | Herzer | Oct 2001 | B1 |
| 6333692 | Andersen et al. | Dec 2001 | B1 |
| 6335686 | Goff et al. | Jan 2002 | B1 |
| 6346884 | Uozumi et al. | Feb 2002 | B1 |
| 6356197 | Patterson et al. | Mar 2002 | B1 |
| 6429776 | Alicot et al. | Aug 2002 | B1 |
| 6497361 | Mason | Dec 2002 | B1 |
| 6499656 | Marsh et al. | Dec 2002 | B1 |
| 6507279 | Loof | Jan 2003 | B1 |
| 6517000 | McAllister et al. | Feb 2003 | B1 |
| 6854647 | Collins et al. | Feb 2003 | B1 |
| 6592037 | Clancy | Jul 2003 | B1 |
| 6595421 | Detwiler | Jul 2003 | B1 |
| 6598791 | Bellis et al. | Jul 2003 | B1 |
| 6764010 | Collins | Jul 2004 | B1 |
| 6783072 | Acosta et al. | Aug 2004 | B1 |
| 6809645 | Mason | Oct 2004 | B1 |
| 20020011933 | Andersen et al. | Jan 2002 | A1 |
| 20020123932 | Brehouse | Sep 2002 | A1 |
| 20030075602 | Wike, Jr. et al. | Apr 2003 | A1 |
| 20030135417 | Bodin | Jul 2003 | A1 |
| 20030146278 | Collins, Jr. et al. | Aug 2003 | A1 |
| 20030146280 | Acosta et al. | Aug 2003 | A1 |
| 20030209600 | Collins, Jr. et al. | Nov 2003 | A1 |
| 20040000591 | Collins, Jr. et al. | Jan 2004 | A1 |
| 20040189472 | Acosta et al. | Sep 2004 | A1 |
| Number | Date | Country |
|---|---|---|
| 19908880 | Sep 2000 | DE |
| 0 329 402 | Dec 1994 | EP |
| 1 098 276 | May 2001 | EP |
| 1 335 336 | Aug 2003 | EP |
| WO 8502285 | May 1985 | WO |
| WO 0026880 | May 2000 | WO |
| WO 0067193 | Nov 2000 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20030197611 A1 | Oct 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60443421 | Jan 2003 | US | |
| 60353139 | Feb 2002 | US |
