Patent Description:
In retail environments, EAS systems are employed. A typical EAS system in a retail setting may comprise a monitoring system and at least one security tag or label attached to an article to be protected from unauthorized removal. The monitoring system establishes a surveillance zone in which the presence of security tags and/or labels can be detected. The surveillance zone is usually established at an access point for the controlled area (e.g., adjacent to a retail store entrance and/or exit). If an article enters the surveillance zone with an active security tag and/or label, then an alarm may be triggered to indicate possible unauthorized removal thereof from the controlled area. In contrast, if an article is authorized for removal from the controlled area, then the security tag and/or label thereof can be deactivated and/or detached therefrom. The security tag and/or label is(are) detected and deactivated using a handheld device. An example of such a handheld device is described in <CIT> ("the '<NUM> patent"). Consequently, the article can be carried through the surveillance zone without being detected by the monitoring system and/or without triggering the alarm.

<CIT> discloses a portable deactivator for security tag deactivation having a corresponding identifier.

The present document concerns systems and methods for transitioning a handheld device from a partially inoperative state to a fully operative state. The methods comprises the step of claim <NUM>.

In some scenarios, operations are performed by the second communication device to wait for a trigger event that occurs when a trigger of the second communication device is actuated by a person. The trigger is actuated to: request a detection and deactivation of the active security tag; or cause a first communication to be transmitted from the second communication device to a scanner. In the later scenario, scanning operations are performed by the scanner in response to a reception of the first communication to obtain information from an object to which the active security tag is coupled. A second communication is transmitted from the scanner to the second communication device when the information is obtained from the object. The second communication device performed operations to detect and deactivate the active security tag in response to the reception of the information sent from the scanner.

In those or other scenarios, the first communication device comprises a smart device facilitating an identification of a person in possession of the first communication device. The second communication device is a handheld tag reader. The scanner comprises a barcode scanner, a Radio Frequency Identification ("RFID") reader, or a Near Field Communication ("NFC") device.

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

The present invention may be embodied in other specific forms without departing from its 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 of the claims are to be embraced within their scope.

Furthermore, the described features, advantages and characteristics of the invention may be combined in any suitable manner in one or more embodiments.

Some conventional handheld devices are able to detect and deactivate security tags and/or labels (e.g., EAS security tags). However, such handheld devices are only functional when mated to a scanner of a specific type, which is provided by a first company other than the second company which supplies the handheld device. As such, any potential customer of the second company needs to interface with the handheld device technology and the scanner technology. This is a cumbersome and costly process for the potential customer.

The handheld device's detection and deactivation operations are triggered by the attachment of the scanner thereto so that unauthorized use thereof for theft is unlikely. Special firmware is implemented by the handheld device to trigger the handheld device's detection and deactivation. In order to expand the handheld device's functionality beyond the scanners, a novel handle has been designed for the handheld device. The handle generally comprises a trigger and a wireless communication module. The wireless communication module is provided to maintain the security of the handheld device and to facilitate the enablement of the handheld device's detection and deactivation operations. In some scenarios, the wireless communication module is a Bluetooth® based communication module. Communication protocols other than Bluetooth® can be used herein without limitation. Also, it should be appreciated that the wireless communication module may be disposed in a portion other than the handle of the handheld device in accordance with a particular application. Still, the handle based configuration is discussed herein for ease of explanation.

The novel handle is described herein in relation to handheld detectors/deactivators for security tags. The present invention is not limited in this regard. The novel handle can also be used with other mobile devices, such as iOS or android devices. These other mobile devices may implement tag deactivation software. In some scenarios, the handheld/mobile devices and corresponding controlling devices communicate indirectly through a WiFi network via a wireless router.

Referring now to <FIG>, there are provided illustrations that are useful for understanding an exemplary handheld device <NUM>. Handheld device <NUM> is generally configured to detect the presence of an active EAS security tag <NUM>, as well as deactivate the EAS security tag at certain select times. The EAS security tag <NUM> is coupled to an object <NUM> to be protected. For example, in a retail store, the EAS security tag is attached to a retail item so as to prevent theft thereof by causing an alarm to be issued when the object travels into a surveillance zone located near an exit of the retail store. If the retail item is successfully purchased, then the EAS security tag is deactivated such that the object can be removed from the retail store without alarm issuance.

As shown in <FIG>, the handheld device <NUM> comprises a housing <NUM> with a handle <NUM>. Various electronic components are disposed in the housing. The electronic components include a detector <NUM> and an activator/deactivator <NUM>. The detector <NUM> detects the presence of active EAS security tags <NUM> located in proximity thereto. Such a detector <NUM> is useful in retail settings. For example, when an alarm issues, an employee approaches the person in possession of the active EAS security tag which is located in the surveillance zone. The detector <NUM> allows the employee to quickly identify which EAS security tag of a plurality of EAS security tags is active. The deactivator <NUM> allows the employee to deactivate the active EAS security tag so that the person can exit the retail store without another alarm issuance.

In some scenarios, the detector <NUM> may be a Radio Frequency Identifier ("RFID") label detector for detecting the active EAS device in the form of an RFID label within a working range of the detector <NUM>. The detector <NUM> can also be an acoustomagnetic or electromagnetic tag detector. With the detector <NUM>, the active EAS device can be readily detected in a group of items, through a container <NUM> (e.g., a gift box or shopping bag) or through clothing (e.g., a coat). Techniques for detecting active EAS devices are well known in the art. Any known or to be known technique can be used herein without limitation.

In those or other scenarios, the handheld device <NUM> comprises at least one output device <NUM>, <NUM> for outputting a detection indicator. The detection indicator includes, but is not limited to, a visual indicator, an auditory indicator and/or a vibrational indicator. As such, the output device <NUM> comprises a display screen and/or light emitting diode. The output device <NUM> comprises a speaker.

As noted above, the handheld device <NUM> comprises an activator/deactivator <NUM>. The activator/deactivator <NUM> is generally configured to change the state of the EAS security tag <NUM> from an active state to an inactive state, and vice versa. Such a state changing function facilitates: the activation of an inactive EAS security tag when coupled to an object to be protected; the deactivation of an active EAS security tag coupled to an object which has been successfully purchased or otherwise no longer needs to be protected; and/or the reuse of a reusable EAS security tag. Techniques for activating and deactivating EAS security devices are well known in the art. Any known or to be known technique for activating and deactivating an EAS security device can be employed herein without limitation.

Referring again to <FIG>, the handheld device <NUM> also comprises a Data Capture and Storage ("DCS") device <NUM> for capturing and storing data related to detected, activated and/or deactivated EAS security tags. In this regard, the DCS device <NUM> may include, but is not limited to, a manual data entry device (e.g., a device including a processor, a keypad <NUM>, a touch screen, a joystick and/or a stylus), a barcode scanner, and/or an RFID reader. In all cases, the DCS device <NUM> captures at least one of: times at which EAS security tags are detected; unique identifiers of detected EAS security tags; zones within a facility in which EAS security tags are detected; unique identifiers of objects to which detected EAS security tags are coupled; reasons for the active states of the EAS security tags; and/or information associated with Point-Of-Sale ("POS") transactions associated with the objects. The DCS device <NUM> may capture and store information other than that listed above.

Notably, the handheld device <NUM> includes a rechargeable battery (not shown). Accordingly, a base <NUM> is provided for facilitating the recharging of the rechargeable battery and/or storing the handheld device <NUM> when not in use. The base <NUM> may also act as a connection point between the handheld device <NUM> and a network, such as for data downloading from the handheld device <NUM> to a remote device (e.g., a remote server). In this regard, the handheld device <NUM> comprises a connector <NUM> which mates to corresponding connection (not shown) of the base <NUM>.

The handheld device <NUM> further comprises a Network Access Provider ("NAP") <NUM>. NAP <NUM> facilitates communication between the handheld device <NUM> and a network <NUM> for sending data to the network and receiving data from the network. Network <NUM> can include, but is not limited to, a Local Area Network ("LAN"). Network <NUM> may be further connected to another network <NUM>. Network <NUM> includes, but is not limited to, a Wide Area Network <NUM> ("WAN"). Network <NUM> may be used to communicate data to a client computer <NUM>, <NUM> remote from the handheld device <NUM>.

In the example depicted in <FIG>, NAP <NUM> is a wireless NAP. With NAP <NUM>, the data captured by DCS device <NUM> may be transferred wirelessly in accordance with a wireless technology. The wireless technology includes, but not limited to, WiFi, Bluetooth, Global System for Mobile communications ("GSM") and/or General Packet Radio Service ("GPRS"). With NAP <NUM>, the handheld device <NUM> may connect directly with a retailer's in-store, wired or wireless network for real-time communication and decision making. In the retailing example, the wireless networking allows the handheld device <NUM> to be used virtually anywhere in the retail store to speed up alarm handling at exits, move customers more quickly during purchasing, replace inefficient and inaccurate paper logging, and provide data for evaluating and improving retail operations.

Notably, an authentication feature <NUM> is provided with the handheld device <NUM>. The authentication feature <NUM> ensures that only authorized personal can use the handheld device <NUM>. In this regard, the authentication feature <NUM> comprises a Short Range Communication ("SRC") device. The SRC device can include, but is not limited to, a Bluetooth device. The SRC device <NUM> communicates with another SRC enabled device <NUM> disposed on or coupled to a person (not shown) authorized to use the handheld device <NUM>. The communication between the two SRC enabled devices <NUM>, <NUM> involve: obtaining a unique identifier associated with the person; comparing the unique identifier to a plurality of pre-stored unique identifiers; and pairing the two SRC enabled devices when a unique identifier match is found. Techniques for pairing two SRC enabled devices are well known in the art. Any known or to be known pairing technique can be used herein without limitation.

For example, in a retail environment, the authentication feature <NUM> is employed at the beginning of an employee's shift. The employee possesses a Bluetooth device (e.g., SRC device <NUM> of <FIG>) with a unique identifier stored thereon that is useful for identifying the employee. Once the Bluetooth device is in range of the handheld device <NUM>, a device pairing process begins. The pairing process initiates a communication session between the Bluetooth device and the authentication feature <NUM> of the handheld device <NUM>. As a result of the device pairing, the handheld device <NUM> changes states from an inoperable state to an operable state. When the handheld device <NUM> enters its operable state, it waits for a trigger event. The trigger event can occur when a trigger <NUM> is depressed. If the Bluetooth device travels out of range of the authentication feature <NUM>, then the handheld device <NUM> transitions back to its inoperable state.

Referring now to <FIG>, there is provided a block diagram of exemplary electronic components <NUM> disposed within a handheld device, such as the exemplary handheld device <NUM> shown in <FIG>. The electronic components <NUM> comprise a processor <NUM>, a memory <NUM>, an EAS module <NUM>, a data capture device <NUM> and at least one Input/Output ("I/O") data transmission module <NUM>. The processor <NUM> can have an embedded operating system (e.g., a Microsoft Windows Embedded CE operating system).

The EAS module <NUM> includes a detector <NUM> and an activator/deactivator <NUM>. The detector <NUM> detects the presence of an active EAS device in proximity thereto. The detector <NUM> can include, but is not limited to, a transmitter for transmitting an interrogation signal and a receiver for receiving signals that are useful to detect alarm patterns. The activator/deactivator <NUM> is operable to change the state of an EAS security device. For example, the activator/deactivator <NUM> can cause an EAS security tag to transition from an inactive state to an active state, and/or from an active state to an inactive state. The activator/deactivator <NUM> can include, but is not limited to, a contact deactivator and/or a proximity deactivator.

The data capture device <NUM> collects data relevant to an alarm event triggered by an EAS device. The collected data may be stored in local memory <NUM> or external memory (not shown) to provide an electronic alarm event log. At least one I/O data transmission module <NUM> is provided to facilitate the transfer of logged alarm event data and/or other data to a remote device (e.g., a central server). The data transmission can be effected by direct electronic coupling of the I/O data transmission module <NUM> to the remote device using any suitable conventional communication link. The communication link can include, but is not limited to, a telephone line, an Institute of Electrical and Electronics Engineers ("IEEE") based connection, an Ethernet based connection, a Universal Serial Bus ("USB") based connection, an Infrared Data Association ("IrDA") based connection, and/or a fiber optic based connection.

Referring now to <FIG>, there is provided a flow diagram of an exemplary method <NUM> for transitioning a handheld device (e.g., handheld device <NUM> of <FIG>) from a partially inoperative state to a fully operative state. Method <NUM> begins with step <NUM> and continues with step <NUM> where a first SRC enabled device (e.g., a SRC enabled device <NUM> of <FIG>) is set to discoverable mode. In some scenarios, the first SRC enabled device includes an SRC enabled device in the possession of a person (e.g., an employee). In discoverable mode, the first SRC enabled device announces its presence to other second SRC enabled devices within its range, as shown by step <NUM>. At least one second SRC enabled device (e.g., the handheld device <NUM> of <FIG>) searches for the first SRC enabled device in step <NUM>. When the second SRC enabled device finds the first SRC enabled device, the user of the second SRC enabled device (e.g., the handheld device) is optionally prompted to enter a passkey in step <NUM>. The passkey can include, but is not limited to, an N digit number where N is an integer (e.g., <NUM>). Thereafter, step <NUM> is performed where the second SRC enabled device (e.g., the handheld device) optionally performs operations to verify the passkey. If the passkey is not verified [<NUM>:NO], then step <NUM> is performed where method <NUM> continues to step <NUM>. In step <NUM>, method <NUM> ends or other processing is performed.

If the passkey has been verified [<NUM>:YES], then the first and second SRC enabled devices are paired. Once the two devices are paired, operations are performed to transition the second SRC enabled device from a partially inoperative state to a fully operative state, as shown by step <NUM>. In the fully operative state, the second SRC enabled device waits for a trigger event in step <NUM>. In some scenarios, the trigger event occurs when a trigger (e.g., trigger <NUM> of <FIG>) of the second SRC enabled device is depressed. The trigger may be triggered to request the detection and/or deactivation of active EAS security tags (e.g., EAS security tag <NUM> of <FIG>) that are located in proximity to the second SRC enabled device, as shown by optional step <NUM>. The detection and/or deactivation operations are disabled when the second SRC enabled device is in its partially inoperative state. Upon completing optional step <NUM>, step <NUM> is performed where method <NUM> ends or other processing is performed.

Notably, the present invention is not limited to the paring process described above. For example, in other scenarios, the first SRC enabled device sends a request to pair with the second SRC enabled device. In response to the request, the first and/or second SRC enabled device prompts a user to enter a passkey. Thereafter, the first and/or second SRC enabled device verifies the passkey. When the passkey is verified by the first and/or second SRC enabled device the user is provided access to the second SRC enabled device (i.e., the second SRC enabled device is placed in a fully operative mode).

Referring now to <FIG>, there is provided a flow diagram of an exemplary method <NUM> for deactivating an EAS security tag (e.g., EAS security tag <NUM> of <FIG>). Method <NUM> begins with step <NUM> and continues with step <NUM> where first and second SRC enabled devices are paired. The first SRC enabled device (e.g., SRC enabled device <NUM> of <FIG>) comprises a device in the possession of a person, such as an employee. In some scenarios, the first SRC enabled device includes, but is not limited to, a mobile phone, a wrist band and/or a smart card. The second SRC enabled device includes a handheld device (e.g., handheld device <NUM> of <FIG>) that is configured to deactivate EAS security tags.

Once the first and second SRC enabled devices have been paired, step <NUM> is performed where the second SRC enabled device changes its state from a partially inoperative state to a fully operative state. In the fully operative state, the second SRC enabled device waits for a trigger event, as shown by step <NUM>. In step <NUM>, a trigger (e.g., trigger <NUM> of <FIG>) of the second SRC enabled device is actuated (e.g., depressed, rolled, slid, etc.). As a result, a first SRC (e.g., a Bluetooth signal) is transmitted in step <NUM> from the second SRC enabled device to a scanner so as to cause the scanner to perform scanning operations. The scanner includes, but is not limited to, a barcode scanner, an RFID reader, and/or a Near Field Communication ("NFC") device. The scanner can be local to the second SRC enabled device or remote from the second SRC enabled device. In response to the reception of the first SRC, the scanner performs scanning operations in step <NUM> to obtain information from an object to which an EAS security tag is coupled. A second SRC is communicated in step <NUM> from the scanner to the second SRC enabled device when information is obtained from scanning the object. The second SRC may include the information obtained from the object (e.g., a unique identifier for the object) and/or other information. In response to the reception of the second SRC, the second SRC enabled device performs operations in step <NUM> to detect and deactivate the EAS security tag coupled to the object. Thereafter, method <NUM> ends or other processing is performed.

Claim 1:
A method for transitioning a handheld device (<NUM>) from a partially inoperative state to a fully operative state, characterized by:
obtaining a unique identifier from a first communication device (<NUM>) that is in range of a second communication device (<NUM>), wherein the handheld device (<NUM>) comprises the second communication device (<NUM>);
comparing the unique identifier to a plurality of pre-stored unique identifiers identifying authorized users of the handheld device (<NUM>);
performing operations to pair the first communication device (<NUM>) with the second communication device (<NUM>) in the handheld device (<NUM>) when results of the comparing indicate that the unique identifier matches one of the plurality of pre-stored unique identifiers;
in response to the pairing of the first device (<NUM>) with the second communication device (<NUM>) in the handheld device (<NUM>), transitioning the handheld device (<NUM>) from the partially inoperative state in which deactivation operations for deactivating an active Electronic Article Surveillance ("EAS") security tag (<NUM>) are disabled to the fully operative state in which said deactivation operations are enabled; and
transitioning the handheld device (<NUM>) back to the partially inoperative state when the first communication device (<NUM>) travels out of range of the second communication device (<NUM>) in the handheld device (<NUM>).