Patent Grant
11358621
The present invention relates to systems for tracking the movement and statuses of non-motorized vehicles, including but not limited to shopping carts.
A variety of commercially available cart containment systems exist for deterring the theft of shopping carts. Typically, these systems include a wire that is embedded in the pavement of a store parking lot to define an outer boundary of area in which shopping cart use is permitted. When a shopping cart is pushed over this wire, a sensor in or near one of the wheels detects an electromagnetic signal generated via the wire, causing the wheel to lock. To unlock the wheel, an attendant typically uses a handheld remote control to send an unlock signal to the wheel.
While existing cart containment systems are useful for deterring shopping cart theft, they are generally not capable of detecting other types of shopping cart misuse. As one example, existing systems are unable to detect that a shopping cart is being used to steal groceries or other merchandise. While merchandise theft can often be detected using an Electronic Article Surveillance (EAS) system, the cost and burden of attaching EAS tags to merchandise items is often impractical. As another example of misuse, merchants that use power-assisted cart retrieval units sometimes use these machines to retrieve too many carts at a time, or to push a cart having a locked or improperly oriented wheel.
This background section is not intended to suggest that the present invention is limited to shopping carts, or that the invention requires detection of the particular types of misuse described above.
The present invention comprises a system for tracking the locations and statuses of vehicles, such as shopping carts. Each vehicle includes a wheel or wheel assembly that includes sensor circuitry for sensing various types of events. (The term “invention” is used in this document to refer generally and collectively to various distinct inventions and inventive features, and its use herein does not limit the scope of protection.) The types of sensors included in the wheel assembly may vary widely, but may include, for example, any one or more of the following: (1) a wheel rotation sensor, (2) a vibration sensor for sensing wheel skid events, (3) a VLF (Very Low Frequency) signal detector for detecting signals used by conventional cart containment systems, (4) an EAS (Electronic Article Surveillance) signal detector capable of detecting conventional EAS towers, and/or (5) a magnetic field sensor capable of detecting encoded magnetic markers placed on or under store flooring or pavement to mark specific locations. The wheel may also include a braking mechanism that can be actuated to lock the wheel from rotating, although braking mechanisms may be omitted in some embodiments.
The wheel's sensor circuitry is coupled to a radio frequency (RF) transceiver system, which may but need not also be housed in the wheel or wheel assembly. The RF transceiver system provides a two-way data link that may be used to retrieve status information from, and send commands to, specific vehicles. The RF transceiver system is preferably capable of measuring and reporting the signal strengths of transmissions it receives, such as transmissions from wireless access points and/or other vehicles.
The retrieved status information may be used to track locations of the vehicles in real time or near real time, and to make decisions on whether to authorize or block particular vehicle actions. For example, in the context of a shopping cart that is exiting a store, the data acquired via two-way communications with the cart may be used to determine whether the cart passed through a checkout lane. If it did not, a lock command may be transmitted to the cart, or an “exit authorized” command withheld, to cause the wheel to lock. (Various other types of actions may additionally or alternatively be taken, such as sounding an alarm or activating a video surveillance system.) The determination of whether to treat the exit event as unauthorized may also be based on other types of data, such as any one or more of the following: (1) whether the corresponding checkout register/scanner was active, as may be determined, e.g., from a central store computer or via a network-connected sensor at the checkout station; (2) the average speed at which the cart passed through the checkout lane, as may be determined, e.g., from a rotation sensor in the wheel, (3) the amount of time spent in the store, (4) whether the cart passed through an area that includes high-priced or frequently stolen merchandise.
The sensor or sensor-based data collected from the vehicles may also be used for a variety of other applications. For example, in applications involving power-assisted cart retrieval, a vibration sensor may be included in the wheel to detect and report wheel skid events. Such skid events commonly occur when a retrieval unit retrieves a cart having a locked or improperly oriented wheel, and can cause damage to the wheels and the retrieval unit. The reported skid event message may be used to automatically disable the cart retrieval unit and/or to alert its operator.
As another example, signal strength measurements taken by the vehicle's RF transceivers can be analyzed collectively, such as by using a clustering algorithm, to estimate the number of carts currently queued or otherwise clustered at a checkout station, in a cart retrieval line, at a cart park area, or elsewhere. This information may be used for various purposes, such as to alert store personnel of the need to open a checkout lane or to retrieve carts, or to automatically disable a cart retrieval unit that is attempting to retrieve more than an authorized number of carts at a time.
In some shopping cart based embodiments, each cart may be provided with a display unit that contains or is coupled to the cart's RF transceiver. In these embodiments, the location data obtained via two-way communications with a cart may be used to select messages to present on the display unit to a customer. For instance, when a shopping cart enters a particular area or department of the store, an advertisement or other message may be displayed that is specific to that area or department. If the customer's identity is known (e.g., as the result of the customer swiping a customer loyalty card via the display unit), the ad or message may be targeted and/or personalized based, e.g., on the past shopping activities of the customer.
The data obtained via two-way communications with the carts may also be analyzed on an aggregated basis for store planning purposes. For example, the paths followed by customers, and the amounts of time spent in particular areas or departments, can be collectively analyzed to identify areas that are the most or least frequently visited by customers. As another example, when a checkout event is detected, the system may associate the customer/cart's path in the store with the associated transaction record, including identifiers of the products purchased; this data may be mined on an aggregated basis via data mining software to detect, e.g., that customers commonly have difficulty locating particular products, or to detect that customers commonly linger in a particular area without selecting an item to purchase.
The invention also comprises a mechanized cart retrieval unit that is capable of instructing the shopping carts it is pushing or pulling to maintain their wheels in an unlocked state. The cart retrieval unit may also instruct one or more carts at the front of the nest to apply weak or partial braking so that the carts do not become un-nested during retrieval. In addition, the invention comprises techniques for using directional antennas to create lock and unlock zones for containing vehicles in a defined area.
The various inventive features described herein are applicable to a wide range of different types of vehicles, including but not limited to shopping carts, luggage carts, wheelchairs, hospital beds, gurneys, pharmacy carts, and carts used for medical and other equipment.
Neither the foregoing summary nor the following detailed description defines or limits the scope of protection. The scope of protection is defined by the claims.
Specific embodiments of the invention will now be described with reference to the drawings summarized below. These specific embodiments are intended to illustrate, and not limit, the invention. The invention is defined by the claims.
I. Overview (
The system includes a set of cart transceivers (CTs) that communicate bi-directionally with a set of wireless access points (APs) to create two-way communications links with the shopping carts 30. In one embodiment, each cart transceiver (CT) is fully contained within one of the standard-size (5-inch diameter) wheels 32 (typically a front wheel) of a respective shopping cart 30, together with a braking unit that can be actuated by the cart transceiver to lock the wheel. One example of a braking unit that may be used for this purpose is described in U.S. Pat. No. 6,362,728, the disclosure of which is hereby incorporated by reference. (For purposes of this detailed description, the term “cart transceiver” refers collectively to the cart's RF transceiver and the associated sensor circuitry). Alternatively, a progressive or partial braking unit may be used that is additionally capable of inhibiting the wheel's rotation without placing the wheel in a locked state.
Some of the circuitry of the cart transceivers (CTs) may alternatively be provided elsewhere on the shopping carts 30. For example, as described below, some of the transceiver circuitry may alternatively be included in a display unit that attaches to the shopping cart's handle (see
The access points (APs) are generally responsible for communicating with the cart transceivers (CTs) for purposes of retrieving and generating cart status information, including information indicative or reflective of cart location. The types of cart status information that may be retrieved and monitored include, for example, whether the wheel 32 is in a locked versus unlocked state, whether the cart is moving; the wheel's average rotation speed (as may be sensed using a rotation sensor in the wheel 32); whether the cart has detected a particular type of location-dependent signal such as a VLF, EAS or magnetic signal (discussed below); whether the wheel 32 is skidding; the CT's battery level and a general wheel “health”; and the number of lock/unlock cycles experienced by the cart since some reference time. (The term “wheel 32” is used herein to refer specifically to a wheel that includes electronics as described herein, as opposed to the other wheels of the shopping cart.) The access points (APs) are also capable of generating and/or relaying commands to the cart transceivers (CTs), including lock and unlock commands that are sent to specific shopping carts.
In the embodiment shown in
The CCU may analyze the collected data in real time for purposes of making decisions, such as whether to send a lock command to a particular cart 30 or whether to send an alert message to personnel. For example, when a cart is approaching or passing through the store exit, the CCU may analyze the cart's recent history (e.g., path and speed) to evaluate whether a customer is attempting to leave the store without paying. (The access points may additionally or alternatively be responsible for making such determinations.) Based on the outcome of this determination, the CCU may send a lock command to the cart (typically via an access point), or may refrain from issuing a command that authorizes the cart to exit. As another example, if the CCU detects a rapid increase in the number of active carts, the CCU may alert personnel (e.g., over a store LAN) regarding the possible need to open an additional checkout station.
The CCU may also run data mining and reporting software that analyzes the data collected over time for purposes of detecting meaningful traffic patterns and trends. For example, the CCU may generate reports showing how customers typically progress through the store, and how much time they spend in each aisle or other shopping area. This information may be used to, for example, adjust the store layout.
The CCU may additionally or alternatively convey the data it collects over a cellular network or the Internet to a remote node that handles analysis and reporting tasks. For example, the CCU (and possibly one or more access points) may have an autonomous WAN link that uses a cellular data service such as GPRS to convey the collected data to a remote node for analysis and reporting. This feature can be used to monitor the system's health from a remote facility. The system may also be capable of being tested and configured via the WAN link from the remote facility.
As depicted in
In some implementations of the system, the CCU may be omitted. In these implementations, the access points (APs) may implement all of the real time analysis functionality that might otherwise be handled by the CCU. For example, an access point mounted in the vicinity of the store exit may be capable of detecting that a customer is attempting to exit the store without paying, and deciding whether to send a lock command to the cart. To accommodate both centralized and distributed of installations, each access point may be capable of operating both with and without a CCU. Implementations are also possible in which the access points are omitted, such that the CCU communicates directly with the cart transceivers.
The cart transceivers (CTs), access points (APs), and central control unit (CCU) all operate as uniquely addressable nodes on a wireless tracking network. As shown in
The various types of nodes (e.g., cart transceivers, access points, central control unit, and mobile control unit) communicate with each other using a non-standard wireless communications protocol that enables the cart transceivers to operate at very low duty cycles, without the need to maintain synchronization with the access points when inactive. Consequently, the cart transceivers can operate for extended periods of time (e.g., approximately 3 years with an average of 0.7 lock/unlock events per day) using a relatively small battery, such as one CR123A (LiMnO2) battery or two L91 (LiFeS2) batteries mounted in the wheel 32. The details of a particular communications protocol that may be used are described below under the heading “Communications Protocol.”
Each cart transceiver (CT) is preferably capable of measuring the received signal strength, in terms of an RSSI (received signal strength indication) value, of the transmissions it receives on the wireless tracking network. The system may use these RSSI measurements in various ways. For example, a cart transceiver may compare the RSSI value of an access point's transmission to a threshold value to determine whether to respond to the transmission. The cart transceiver may also report this RSSI value to the access point (together with the cart transceiver's unique ID) to enable the system to estimate the location of, or distance to, the shopping cart. As another example, the cart transceivers may be programmed to generate and report RSSI values of transmissions from other nearby cart transceivers; this information may in turn be used to estimate the number of carts that are queued at a checkout lane, in a cart storage structure, in a cart stack being retrieved with a mechanized cart retrieval unit 40, or elsewhere. One example of a method that may be used to estimate the number of queued or clustered carts in a particular area is described below under the heading “Queued Count Estimation.”
Three checkout stations 34 are shown in
Access points may additionally or alternatively be mounted to various other fixed and/or mobile structures in the vicinity of the store. For example, as shown in
As illustrated in
In one embodiment, the cart retrieval unit 40 is a battery powered cart pusher that is adapted to be positioned at the rear of a cart stack to be retrieved. The operator manually steers the cart stack by holding the front cart with one hand while holding the MCU in the other hand. Via a set of buttons on the MCU, the operator can control the forward and backward direction and speed of the retriever 40. Various type of status information may be displayed to the operator on a display of the MCU, such as the estimated number of carts being retrieved (as determined using the cluster analysis methods described below). If the retriever-mounted access point detects a misuse condition (e.g., a skid event or too many carts being pushed), it may disable the retriever 40 in various ways, such as by “spoofing” a manual throttle interface, or if the retriever 40 contains a motor controller with a digital external control interface, by issuing a stop command via this interface.
In the particular example shown in
The example store configuration in
While the present system does not require the use of a VLF signal line 44, the system is preferably capable of using one or more VLF lines as a mechanism for monitoring cart location. Specifically, cart transceiver (CT) preferably includes a VLF receiver. The VLF receiver may be capable of detecting a code transmitted on a VLF line, so that different lines can be used to uniquely identify different areas or boundaries. When the VLF signal is detected, the cart transceiver may take various actions, depending on the circumstances. For example, the cart transceiver may attempt to report the VLF detection event on the wireless tracking network and then wait for a command indicating whether to engage the brake. If no command is received within a pre-programmed time period in this example (e.g., 2 seconds), the cart transceiver may automatically engage the brake.
With further reference to
As will be apparent from the foregoing discussion, many of the components shown in
II. Detecting Unauthorized Exit Events (
The system supports a variety of different methods for assessing whether a customer is exiting the store without paying. The particular method or methods used may vary widely based on the types and the locations of the system components included in a given installation. For example, if the store does not include any Electronic Article Surveillance (EAS) Towers, magnetic markers (MAG), or VLF lines, the determination may be made based solely or primarily on cart location/path information determined from CT-AP communications, with wheel speed history optionally taken into consideration as an additional factor. If EAS towers, magnetic markers, and/or VLF signal lines are provided, they may be used as additional or alternative sources of information from which the decision can be made.
In the example shown in
In one embodiment, when a shopping cart 30 (i.e., its cart transceiver) detects that it has entered into a zone 46, 48 (as determined by monitoring the RSSI values of the corresponding access point's transmissions), it registers with the access point (AP) by responding to a periodic transmission from the access point. If this access point is located at a checkout station 34, the access point may instruct the cart transceiver to enter into a data collection mode in which it monitors and reports a wider range of events and conditions than usual. For example, if the cart transceiver includes an EAS receiver, it may power-up this receiver for purposes of detecting passage between a pair of EAS towers. In addition, if the wheel 32 includes a rotation sensor, the cart transceiver may monitor the wheel's rotation, such as by counting the number of rotation interrupts that occur. The cart transceiver may also periodically generate and store RSSI values for the access point transmissions it hears.
Upon passage through a set of EAS towers (if used) or entry into an exit zone 48, the cart transceiver may send the collected data (wheel speed history, RSSI values, magnetic marker or EAS detection events, etc.) to an access point for analysis to determine whether a payment event has occurred. The active/inactive state of the checkout register/station 34 corresponding to the cart's path may also be considered.
The task of evaluating the collected data is preferably handled primarily by the access points and/or the CCU, but could alternatively be handled partially or wholly by the cart transceivers (CTs). Data collected by two or more different access points, potentially including access points that are not near the checkout stations 34, may be analyzed in combination for purposes of assessing whether a payment event occurred. For example, as a cart moves from one zone to another, it may communicate with a number of different access points. The history of these communications may be aggregated (e.g., by the CCU) and analyzed to estimate the cart's navigation path over time, and this estimated path may in turn be considered in assessing whether the customer has paid.
In some configurations, checkout activity may be monitored without providing access points (APs) at the checkout stations 34. In these configurations, the system may detect that a cart has passed or is passing through a checkout lane based on one or more of the following: (1) detection by the wheel 32 of a magnetic marker that uniquely identifies a particular checkout lane; (2) if the store has VLF signal lines/transmitters or EAS towers in the checkout lanes, detection by the cart transceiver (CT) of a VLF or EAS signal, optionally in conjunction with location history information indicating that the cart is in the general vicinity of a checkout lane.
As depicted by blocks 60 and 62, if it is determined that the cart did not recently pass through a checkout lane, the wheel 32 is caused to lock. Otherwise, a determination is made whether the checkout station 34 detected as being used by the cart was in an active state at the time (block 64). This determination may be made in a variety of ways. For example, in some stores, the CCU may be able to get this information substantially in real time from a centralized store computer system that connects to the individual POS registers. Thus, for example, if magnetic markers (MAG) are provided in the checkout lanes, the wheel 32 may sense the unique magnetic code of its checkout lane and relay this information to the CCU via an access point; the CCU may then query the central store computer system to determine the state of the register. The active/inactive determination may alternatively be made by an access point (AP) mounted at the checkout station; for example, the access point may include or be locally connected to an acoustic sensor that senses the beep sound produced by the merchandise scanners, or may include a light-based sensor or pressure-sensitive floor mat that detects whether a cashier is present at the station.
If the checkout station 34 was inactive in the example shown in
As will be apparent, the decision logic shown in
Further, in addition or as an alternative to locking the wheel 32 as shown in
III. Cart Transceiver and Wheel Electronics (
As illustrated in
The RF transceiver 82 is preferably either a 2.4 GHz or 5.7-5.8 GHz transceiver, although other frequency bands such as UHF can be used. The RF transceiver 82 preferably has the following attributes: (1) very low power for periodic wakeup and receive, (2) modulation that is insensitive to phase reversal (e.g., Frequency Shift Keying or FSK), (3) log linear RSSI measurement, (4) hardware support for Clear Channel Assessment (CCA). One example of an RF transceiver that may be used is a TI/Chipcon cc2500. One useful feature of this RF transceiver device is that it is capable of receiving transmissions while the microcontroller 80 is in an inactive state, and waking up the microcontroller if the received transmission matches pre-programmed criteria. The RF transceiver 82 is coupled to an antenna 84, which preferably has a differential ended antenna port so that no balun is needed when using a preferred differential antenna 84.
As illustrated in
As shown in
The vibration sensor 94, if present, enables the microcontroller 80 to detect wheel vibration/skid events commonly caused when a motorized shopping cart retriever 40 pushes or pulls a cart whose wheel is locked or has an improper orientation. One example of a vibration sensor design that may be used is shown in
The magnetic field sensor 96, if present, enables the microcontroller 80 to detect magnetic markers (MAG) of the type described above. The magnetic sensor 96 may, for example, be one of the following: (1) a two-axis magnetic sensor capable of measuring the value of the two magnetic field components in an object's plane of motion; (2) a “2½ axis” sensor that can measure two magnetic field components and the algebraic sign of a third component, or (3) a three-axis magnetic field sensor that measures each of the three independent magnetic field components. When the magnetic field sensor 96 initially detects a likely magnetic marker in one embodiment, the microcontroller begins buffering the output of the magnetic field sensor, and continues such buffering until the microcontroller determines that the wheel 32 has likely finished passing over the marker. The cart transceiver (CT) then transmits the buffered data to an access point (AP) for analysis together with wheel rotation-sensor data. The access point or the CCU then analyzes this data to determine whether a magnetic marker was actually crossed, and if so, to identify the unique code of this marker. This analysis could alternatively be performed by the cart transceiver (CT), and the result transmitted to an access point.
One additional type of sensor that may be included in the wheel 32 is a heading sensor (not shown in
Various other types of sensors and receivers may additionally or alternatively be included in the wheel 32 or wheel assembly. For example, in some applications, it may be feasible to include a GPS (Global Positioning System) receiver in the wheel or wheel assembly, or to include another type of electronic device that is capable of calculating its position based on received RF, optical, or ultrasonic signals. Further, the wheel 32 could transmit a signal that is used by an external node or system to detect the wheel's location, and the wheel could then be notified of its location via an access point.
As illustrated in
As illustrated in
In some embodiments of the invention, the brake unit 100 may be omitted from the wheels 32. In these embodiments, the system may track and report the locations and statuses of the carts 30 or other vehicles without attempting to stop their movement.
Various other types of vibration sensors can alternatively be used. For example, a disturbance switch, such as a 10651-X-000 disturbance switch from Aerodyne Controls, may be used.
The rotation sensor, if included, may be similar to the vibration detector shown in
IV. Wheel Configuration and Antenna Radiation Pattern (
The antenna 84 is preferably formed on a printed circuit board 85 that remains stationary as the wheel rotates. This same printed circuit board also includes the various electronic components shown in
As illustrated in
In other embodiments, some or all of the electronic and braking components may reside outside the wheel 32, such as in an enclosed plastic housing that forms part of the caster.
V. Embodiment with RF Transceiver Circuitry in Display Unit (
The wheel electronics and the display unit 150 are connected by a pair of wires 154, which may be routed through or on the shopping cart's frame. These wires are used to supply power from the wheel's power generator subsystem 104 to the display unit 150, and are also used for two-way communications between the two microcontrollers 80A, 80B. The display unit 150 may also include a battery for enabling the display unit to continue to operate when the wheel's power reservoir is deeply discharged. The two-wire connection is made via a pair of coupling transformers 156A, 156B. One example of a mechanical coupling that may be used to pass the transformer coupled signals from the wheel's PCB to the cart frame and thence to the display unit 150 is described in the Power Generation Patent Application referenced above.
The two microcontrollers 80A, 80B communicate in half duplex mode using a one-wire protocol. A variety of suitable one-wire protocols are known in the art. One example is the protocol defined by the ISO 11898-1 Controller Area Network (CAN) specification. To transmit data from the display unit 150 to the wheel 32, the master microcontroller 80A sets the I/O port that is connected to the coupling transformer 156A to “output,” and the slave microcontroller 80B sets its I/O port to “input.” The master microcontroller then toggles its I/O port output on and off at one of two frequencies to generate an FSK signal. The AC component of that signal couples onto the power line through the coupling transformer 156A and passes through the other coupling transformer 156B. The slave microcontroller 80B can distinguish between the two FSK frequencies by counting the number of crossings per unit time. Transmissions in the opposite direction occur in the same manner. The two microcontrollers 80A and 80B may be programmed such that some or all of the events detected via the VLF receiver 88, vibration sensor 94, and rotation sensor 92 (and/or other sensors included in the wheel) are reported to the master microcontroller 80A so that they may, if appropriate, be reported to an access point.
The electrical coupling between the wheel 32 and the display unit 150 can be varied in a number of ways. For example, a third wire may be added to directly connect the two I/O ports, so that the two coupling transformers 156A, 156B can be omitted. As another example, the power generator may be omitted from the wheel 32, and the wheel electronics may be powered by a battery in the display unit. In yet another embodiment, the wired connection is omitted, and wheel 32 and the display unit 150 communicate with each other solely by RF and are powered by their own respective power sources.
In some implementations, the display unit 150 may have a card reader 160, such as a magnetic card reader or a barcode scanner, that enables a customer to swipe a customer loyalty card or another type of card that identifies the customer. In these implementations, the cart transceiver may be configured to convey the customer identifier to an access point such that this identifier can be associated with the other cart events detected during the customer's shopping session.
The display unit 150 may additionally or alternatively include or be connected to a merchandise ID reader 162, which may be a barcode scanner or RFID reader. In the case of an RFID reader, the CT may use cart movement data (e.g., as determined using a wheel rotation sensor) in combination with data from the RFID reader to identify products that are in the cart. For example, if the cart is has moved forward by a selected distance (e.g. 20 feet) and the RFID reader is still detecting the presence of a particular product, the product may be treated as being in the cart (as opposed, for example, to being on in a nearby cart or on a nearby shelf).
If a merchandise ID reader is provided and is used by the customer, the display unit 150 may, for example, display the names and prices of the items selected by the customer to purchase, and may convey this information to an access point (AP). The display unit may also display recommendations of related products. In some implementations, a single scanner or reader device such as a barcode scanner may serve as both a merchandise scanner 162 and a loyalty card reader 160. The display unit 150 may also include a beeper, chirper, or other audio signal generator (not shown) that outputs an audio signal when a new message is initially displayed, or when the customer's attention is otherwise desired.
VI. Access Point Design (
In one embodiment, the register activity sensor 172 is an acoustic sensor that is trained or trainable to detect the audible beep generated by conventional merchandise scanners. When this type of sensor is used, the access point (AP) treats the register as active when beep signals of sufficient amplitude and/or specific frequency content are being detected at regular intervals. Beep signals of adjacent registers/scanners can typically be filtered out and ignored based on their lower volume at the location of the access point. The acoustic register activity sensor may either be mounted inside the housing of the access point, or may be connected to the access point by a pair of small wires.
Various other types of register activity sensors 172 may alternatively be used. For example, an infrared or LED sensor, or a weight sensor positioned under a mat, may be used to detect whether a cashier is present at the register. As another example, the access point may passively monitor the register's wired interface (typically an RS-422 differential full duplex interface) to the store's point-of-sale central system, and may infer that the register is active when signals are detected that reflect common activity patterns. Further, in some installations, information about the active/inactive states of the registers/checkout stations may be obtained by querying a preexisting store computer that maintains such information, and thus without the use of a register activity sensor 172.
As illustrated in
The access point also includes a three-way switch 190 that enables the RF transceiver 182 to be connected to an internal antenna, a first external antenna port, or a second external antenna port. The internal antenna is preferably used primarily or exclusively for communications with other access points and/or the CCU. The external antenna ports may be used to connect one or two directional antennas to the access point. These directional antennas may be used to create zones for communicating with and tracking the locations of cart transceivers, as described above. One example of how an access point can use the two external antennas to create two different control zones is shown in
The access point also includes an interface 192 for enabling the microcontroller 180 to communicate with a store security system. This interface 192 may be used for various purposes, such as the following: (1) notifying the store security system of whether the AP is receiving AC power or has experienced an internal fault; (2) enabling the security system to place the APs in a “safe mode” in which the APs command all of the cart transceivers to remain unlocked at the building exits; this mode may be used when, for example, a fire alarm occurs; (3) activating a security system alarm, or generating a video surveillance capture event, in response to an inferred theft event.
The various components of the access point may be housed within a plastic or other housing that is adapted to be mounted to a fixed or mobile structure. The housing may, for example, be approximately the size of a standard chalk board eraser.
Where fine grain tracking of in-store customer activity is desired, access points can be positioned strategically throughout the store, such as in every department, aisle, checkout area, etc. Each such access point may be configured to periodically (e.g., once every 5 seconds) identify, and report to the CCU, all of the cart transceivers in its respective zone.
The design of the transceiver used in the CCU may be the same as or similar to the access point design shown in
VII. Communications Protocol (
One example of a protocol that may be used for wireless communications between “controllers” (devices that initiate transmissions) and “targets” (devices that respond to communications from a controller) will now be described with reference to
The protocol advantageously allows the cart transceivers to remain in a very low power state most of the time. For example, in one embodiment, each cart transceiver (CT) wakes up approximately every 1.8 seconds to listen for a transmission from an access point, and then returns to its low power state after one millisecond if it does not receive a transmission that requires a response or other action. If the cart transceiver detects an AP transmission that requires a response, it remains active until a response window occurs, and then transmits its response to the access point.
The cart transceiver (CT) can adjust the frequency with which it wakes up under specific conditions where lower communication latency is desirable and where the extra power consumption is acceptable, e.g. when passing through a very narrow exit zone or by a potential payment point. As one example, an access point that has a small antenna footprint or zone may command nearby CTs to wake up more frequently when detecting RSSI levels above a specified threshold.
The access points preferably use both unicast (target-specific) and multi-cast addressing to send messages to the cart transceivers. An example of a multi-cast message is a message addressed to “all cart transceivers that are locked,” or “all cart transceivers of carts that are moving.” Because multiple cart transceivers can respond to a multicast transmission, the response window is divided into multiple response slots, and the cart transceivers pseudo-randomly select between the available response slots. The access point acknowledges the responses it receives, enabling the cart transceivers to detect and retry unsuccessful responses (e.g., those that produced collisions).
In one embodiment, the RSSI threshold refers to a filtered RSSI value, so that a cart transceiver will not respond to an AP when the cart transceiver is not in the AP's antenna footprint or zone, even if anomalous RF propagation causes a single RSSI measurement to be anomalously high. The RSSI filtering method may be similar to the method described below in the section on queue count estimation, though the parameters of the method may be adjusted to reflect that this filter computation is preferably performed by the relatively low-power cart transceivers rather than the APs. A CT may generate a filtered RSSI value for a given AP from wakeup-packet-specific RSSI values generated by the CT during the wakeup sequence, and/or from RSSI values generated from recent transmissions of the AP.
The slot length is specified implicitly by the combination of the response window size and the number of slots. Typically, the AP will select a slot size that corresponds to the expected response size given the type of command being issued.
In cases where the command including its parameters is too long to fit in the space allocated in the wakeup message format, the command field present in the wakeup packet indicates the nature of a forthcoming command. The response window beginning time is then interpreted by the CT as the beginning of an additional transmission from the access point which contains the remainder of the command. The response window then follows immediately after the additional command information. Any CT which receives the wakeup and which is a potential addressee of the command based on the information present in the wakeup message will then wake up as if the CT did have a response, receive the additional command information, and then determine whether a response is required.
Table 1 lists some of the commands that can be issued to a cart transceiver. In general, these commands may be issued from either an AP or a MCU, though it is unlikely that certain commands would be issued from an MCU, e.g. Report zone entry.
With further reference to
The async field provides a mechanism for a cart transceiver to notify the access point that it has some unsolicited data to report. The cart transceiver may have such data to report when, for example, it detects a VLF field code, EAS signal, magnetic marker, or skid event. In one embodiment, the cart transceiver uses the async field to notify the access point of the type of the unsolicited data; the access point thereafter schedules a unicast interrogation of the cart transceiver to retrieve this data. Because the access points ordinarily transmit commands, such as “report zone entry” commands, on a regular basis (e.g., every few seconds), the async feature provides a mechanism for all types of cart status information to be retrieved substantially in real time.
In the example shown in
Because the access points (APs) are capable of transmitting at significantly higher power levels than the cart transceivers (CTs), a significantly higher bit rate is preferably used for the downlink to the carts than for the uplink to the access points. This reduces the disparity that would otherwise result between the transmission ranges of the two types of devices. The relatively high bit rate on the downlink also allows the access points to send out wakeup packets at a reasonably high rate (e.g., one every two milliseconds); consequently, the cart transceivers only have to listen for a wakeup packet for a very short time before re-entering a low-power state.
Frequency hopping may be used for transmissions in both directions. The access points preferably maintain synchronization with each other by monitoring transmissions from the CCU or each other.
VIII. Storage and Analysis of Cart History Data (
The CCU stores the event data in an event histories database 210, which may be a relational database. Each cart session record 212 shown in the event histories database corresponds to a particular cart and shopping session, and contains the event data associated with that shopping session. In one embodiment, the CCU treats a cart's entry into the store as the beginning of a shopping session, and treats the cart's subsequent exit from the store as the end of a shopping session; however, different criteria may be used for different store configurations and applications. The cart IDs may be the unique IDs or addresses of the corresponding cart transceivers.
The CCU also preferably accesses a database 220 of purchase transaction data and customer profile data maintained by or obtained from the store's central computer. As illustrated, this database 220 may contain records 222 of specific purchase transactions of specific customers, including identifiers of the purchased items.
As illustrated, a given session record 212 may, in some cases, include a store transaction ID and/or a customer number. The store transaction ID identifies the checkout transaction, if known, as produced by a conventional point-of-sale system and recorded in the database 220. The transaction IDs are attached to the corresponding session records 212 by an event-history/transaction correlation component 214 that runs on the CCU. In one embodiment, this component 214 compares purchase transaction data stored in database 220 with the cart event data to uniquely match specific transaction records 222 with specific cart session records 212. This may be accomplished by, for example, comparing the data/time stamp and register ID information contained in a store transaction record 222 to the cart event data reflective of a checkout event. If a sufficient degree of correspondence exists between time and location, a given session record 212 may be matched to a given transaction record 222.
If the recorded time and location information is insufficient to match the cart session under consideration to a particular transaction, the correlation component 214 may compare the items identifiers contained in the potentially matching transaction records 222 to the path taken by the cart. A database 230 of store and access point configuration data may be used for this purpose. If, for example, a particular transaction includes items (and especially bulky items) that are not available along the path followed by the cart, the transaction may be excluded as a candidate. If, on the other hand, the purchased items closely match the cart path, a match may be deemed to exist.
The customer number field in the cart session records 212 may be used to store a customer loyalty number, if known. This number may be obtained from the matching transaction record 222, or in embodiments in which the cart includes a display unit 150 with a card reader 160 (
The analysis components that run on the CCU in the example embodiment of
In embodiments in which the carts 30 include display units, the real time analysis component 240 may also select location-dependent ads or other messages to present to users. For example, upon entry into a particular store department, the CCU may instruct the cart to display a particular ad, promotion, offer, or other message that is specific to that department. If the customer's loyalty number is known at the time (e.g., as the result of entry via a card reader 160 on the display unit 130), the ad or message may also be based on the actions taken by this customer in prior sessions or visits. For example, if the customer regularly purchases milk on visits to the store, and has entered the checkout area without first entering the area where milk is sold, a message may be displayed reminding the customer to do so. The content that is available for display may be selected from a content database 260 and wirelessly downloaded to the cart transceivers, and/or may be cached in the display units.
The component 250 labeled “off-line statistical analysis” in
IX. Use of Lock and Unlock Zones to Set Boundaries (
With this configuration, a customer attempting to push a cart 30 through the parking lot exit will have to pass through the lock zone 286, causing the wheel 32 to lock. Upon encountering the lock event, the customer may attempt to drag the cart back to the front of the store, such as to get back a monetary deposit placed on the cart. If the customer does so, the cart will enter the unlock zone 288, causing the wheel 32 to unlock. Thus, the wheel damage that might otherwise occur from dragging the locked wheel is avoided.
A similar arrangement can be used to control the movement of carts through a building exit. Typically the lock zone 286 would be placed on the outside of the building exit and the unlock zone 288 on the inside. Alternatively, the lock zone 286 could be placed immediately inside of the exit and the unlock zone some greater distance inside the building.
With further reference to
Each AP also optionally creates a relatively large unlock zone that covers the majority of the parking area in from of the center store. To provide this third zone, each AP may be provided with a third external/directional antenna. Time slicing may be used to alternate between the three antennas, or two separate RF transceivers may be included in each AP—one which transmits the unconditional unlock command and the other which transmits the unconditional lock command. As another option, a separate AP or pair of APs could be provided to create the unlock zone.
As will be apparent, lock and unlock zones as described in this section may be implemented using receivers, rather than transceivers, on the shopping carts 30. Thus, for example, in some embodiments of the invention, the RF transceivers included in the locking wheels 32 may be replaced with RF receivers. In addition, lock and unlock zones that are created as described herein can also be used for the containment of other types of carts and vehicles, including but not limited to wheelchairs, hospital beds, gurneys, pharmacy carts, and luggage carts.
In embodiments in which the shopping carts include display units 150, the display unit of a cart 30 that is approaching a lock zone may be instructed to display a warning message. In addition, once the cart has entered a lock zone and the wheel 32 becomes locked, the display unit may instruct the user on how to restore the wheel to an unlocked state, including the location of the nearest unlock zone.
X. Queue Count Estimation (
As illustrated in block 300 of
As illustrated in block 302 of
In block 306, the AP assigns a set of k unique transmission timeslots to each participating CT, and initiates a process in which each CT uses its assigned timeslots to generate k transmissions, each of which preferably occurs at a different frequency. The use of multiple different transmission frequencies provides a mechanism for reducing errors caused by frequency-selective effects such as multi-path distortion and antenna shadowing. As depicted in blocks 308 and 310, when one CT transmits, the other participating CTs (as well as the AP) measure the RSSI of the transmission. Thus, during this process, each participating CT generates k(N−1) RSSI values. Although the k transmissions from a given CT need not be consecutive (e.g., the transmissions from different CTs may be interleaved), they are preferably sufficiently close in time such that significant cart movement does not occur between the first and last transmissions. In blocks 312 and 314, the AP retrieves the k(N−1) RSSI values generated by each participating CT.
In block 316, the AP generates a filtered RSSI value from each set of k RSSI values. In one embodiment, k=8, and the filtered RSSI value is generated by discarding the two highest and two lowest RSSI values and then taking the arithmetic average of the remaining four. Thus, for example, if CT1 and CT2 both participate, CT1 would generate a separate RSSI value for each of CT2's eight transmissions, and these eight RSSI values would be converted into a single filtered RSSI value. Since the RSSI values are preferably log linear, the arithmetic average of the RSSI readings is the log of the geometric mean of the four middle received RF power values. The task of generating the filtered RSSI values (designated hereinafter by the notation RSSI*) may alternatively be performed by the CTs that took the corresponding RSSI measurements, or by some other node such as the CCU. Although filtered RSSI values are used in the preferred embodiment, their use is not required.
The result of block 316 is a set of N(N−1) RSSI*i→j values, where RSSI*i→j is the filtered RSSI of the ith CT as measured at the jth CT. (Note that the term “CT” in this discussion may be replaced with “wheel 32” in embodiments in which the CT is contained within the wheel.)
In block 318, the AP (or some other node) calculates a pair-wise distance metric for each CT pair i≠j. The preferred method of calculating distance metrics takes advantage of, but does not require, temporal stability of the cluster of carts/CTs. The nth iteration distance metric d(i,j,n) may be defined by the following recurrence relations:
Several different ƒ and ƒ0 functions can be used in the above calculation. Over a statistical ensemble, RSSI* is an invertible monotonic function of distance which can be determined by straightforward experimentation. An AP-CT distance metric may also be calculated for each of the N cart transceivers.
In block 320 of
In some applications, the above process may be performed merely to estimate the total number of carts that are clustered together, without regard to how or whether these carts are queued. This may be the case where, for example, the number of carts in a cart storage area 36 is being estimated.
XI. Maintaining Carts in Unlocked State During Retrieval (
As mentioned above, the system may include a mechanized cart retrieval unit 40 (
As depicted by block 410, the retriever-mounted AP 40 may additionally or alternatively be configured to broadcast a “you are being retrieved” command when the retrieval operation is initiated. This command preferably includes a field indicating whether it is being sent from a directional antenna. In response to receiving this command, the CT determines whether either (1) the RSSI associated with the command transmission exceeds the AP-specified threshold, or (2) the command was transmitted via a directional antenna (block 412). If neither condition is true, no further action is taken (block 414).
If either of the conditions in block 412 is true, the CT unlocks the wheel if currently locked (blocks 416 and 418) and sets a “probable retrieval” flag (block 422). The CT then enters into a loop in which it either detects wheel movement or skidding, or times out (blocks 424 and 426). If wheel movement or skidding is detected, the CT follows the sequence depicted by blocks 402-408, discussed above. (If a skid event is detected, the CT may also send a skid event message to the retrieval unit, as described above). If a timeout event occurs in block 426, the probable retrieval flag is cleared and the process ends.
XII. Conclusion
The various functions described above as being performed by an access point, cart transceiver, CCU or MCU may be embodied in or controlled by executable software code that is stored in a computer memory or other computer storage device. Some of the functions may alternatively be embodied in application-specific circuitry. Any feasible combination of the various features and functions described herein may be embodied in a given system, and all such combinations are contemplated.
As will be recognized, the wheel braking mechanism described herein can be replaced with another type of electromechanical mechanism for inhibiting the motion of the cart, including mechanisms that cause one or more of the wheels of the cart 30 to be lifted off the ground.
Although this invention has been described in terms of certain embodiments and applications, other embodiments and applications that are apparent to those of ordinary skill in the art, including embodiments which do not provide all of the features and advantages set forth herein, are also within the scope of this invention. Accordingly, the scope of the present invention is intended to be defined only by reference to the claims.
This application is a continuation of U.S. application Ser. No. 17/225,830, filed Apr. 8, 2021, which is a continuation of U.S. application Ser. No. 16/995,471, filed Aug. 17, 2020, which is a continuation of U.S. application Ser. No. 16/224,046, filed Dec. 18, 2018 (now U.S. Pat. No. 10,745,040), which is a continuation of U.S. application Ser. No. 15/877,187, filed Jan. 22, 2018 (now U.S. Pat. No. 10,189,494), which is a continuation of U.S. application Ser. No. 15/191,303, filed Jun. 23, 2016 (now U.S. Pat. No. 9,914,470), which is a continuation of U.S. application Ser. No. 15/093,545, filed Apr. 7, 2016 (now U.S. Pat. No. 9,676,405), which is a continuation of U.S. application Ser. No. 14/821,244, filed Aug. 7, 2015 (now U.S. Pat. No. 9,322,658), which is a continuation of U.S. application Ser. No. 13/907,502, filed May 31, 2013 (now U.S. Pat. No. 9,758,185), which is a continuation of U.S. application Ser. No. 11/277,016, filed Mar. 20, 2006 (now U.S. Pat. No. 8,463,540), which claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Patent Appl. Nos. 60/663,147, 60/663,327, and 60/663,195, all filed on Mar. 18, 2005. The aforesaid applications are hereby incorporated by reference. In addition, the disclosures of the following non-provisional applications are hereby incorporated by reference: U.S. patent application Ser. No. 11/277,027, filed Mar. 20, 2006, titled NAVIGATION SYSTEMS AND METHODS FOR WHEELED OBJECTS, now U.S. Pat. No. 8,046,160 (hereinafter “the Navigation Patent Application”), and U.S. patent application Ser. No. 11/277,029, filed Mar. 20, 2006, titled POWER GENERATION SYSTEMS AND METHODS FOR WHEELED OBJECTS, now U.S. Pat. No. 8,820,447 (hereinafter “the Power Generation Patent Application”).
| Number | Name | Date | Kind |
|---|---|---|---|
| 4242668 | Herzog et al. | Dec 1980 | A |
| 4439772 | Van Kol | Mar 1984 | A |
| 4651156 | Martinez | Mar 1987 | A |
| 4656476 | Tavtigian | Apr 1987 | A |
| 4779321 | Black | Oct 1988 | A |
| 4831363 | Wolf | May 1989 | A |
| 4862160 | Ekchian et al. | Aug 1989 | A |
| 4973952 | Malec | Nov 1990 | A |
| 5053768 | Dix, Jr. | Oct 1991 | A |
| 5068654 | Husher | Nov 1991 | A |
| 5082074 | Fischer | Jan 1992 | A |
| 5250789 | Johnsen | Oct 1993 | A |
| 5283550 | MacIntyre | Feb 1994 | A |
| 5287266 | Malec et al. | Feb 1994 | A |
| 5295064 | Malec et al. | Mar 1994 | A |
| 5315290 | Moreno et al. | May 1994 | A |
| 5322306 | Coleman | Jun 1994 | A |
| 5357182 | Wolfe et al. | Oct 1994 | A |
| 5360094 | Adams et al. | Nov 1994 | A |
| 5406271 | Sonnendorfer et al. | Apr 1995 | A |
| 5432412 | Harris et al. | Jul 1995 | A |
| 5434781 | Alofs et al. | Jul 1995 | A |
| 5438319 | Zeytoonjian et al. | Aug 1995 | A |
| 5439069 | Beeler | Aug 1995 | A |
| 5485520 | Chaum et al. | Jan 1996 | A |
| 5512879 | Stokes | Apr 1996 | A |
| 5529163 | Decker et al. | Jun 1996 | A |
| 5557513 | Frey et al. | Sep 1996 | A |
| 5610586 | Zeytoonjian et al. | Mar 1997 | A |
| 5625569 | Trimmer et al. | Apr 1997 | A |
| 5630600 | Pasillas | May 1997 | A |
| 5640002 | Ruppert et al. | Jun 1997 | A |
| 5640146 | Campana, Jr. | Jun 1997 | A |
| 5646616 | Komatsu | Jul 1997 | A |
| 5719555 | Zeytoonjian et al. | Feb 1998 | A |
| 5806862 | Merryman et al. | Sep 1998 | A |
| 5821512 | O'Hagan et al. | Oct 1998 | A |
| 5821513 | O'Hagan et al. | Oct 1998 | A |
| 5825286 | Coulthard | Oct 1998 | A |
| 5835868 | McElroy et al. | Nov 1998 | A |
| 5844130 | Hilgrat | Dec 1998 | A |
| 5877962 | Radcliffe | Mar 1999 | A |
| 5881846 | French et al. | Mar 1999 | A |
| 5883968 | Welch et al. | Mar 1999 | A |
| 5934694 | Schugt et al. | Aug 1999 | A |
| 5944659 | Flach et al. | Aug 1999 | A |
| 5974312 | Hayes, Jr. et al. | Oct 1999 | A |
| 5999099 | Stobbe | Dec 1999 | A |
| 6002348 | Greene et al. | Dec 1999 | A |
| 6024655 | Coffee | Feb 2000 | A |
| 6070679 | Berg et al. | Jun 2000 | A |
| 6078826 | Croft et al. | Jun 2000 | A |
| 6102414 | Schweninger | Aug 2000 | A |
| 6123259 | Ogasawara | Sep 2000 | A |
| 6125972 | French | Oct 2000 | A |
| 6127927 | Durban et al. | Oct 2000 | A |
| 6168367 | Robinson | Jan 2001 | B1 |
| 6173817 | Gray | Jan 2001 | B1 |
| 6177880 | Begum | Jan 2001 | B1 |
| 6201473 | Schaffer | Mar 2001 | B1 |
| 6220379 | Schugt et al. | Apr 2001 | B1 |
| 6244366 | Otterson et al. | Jun 2001 | B1 |
| 6260643 | Schuchardt | Jul 2001 | B1 |
| 6310963 | Erdol et al. | Oct 2001 | B1 |
| 6362728 | Lace et al. | Mar 2002 | B1 |
| 6435803 | Robinson | Aug 2002 | B1 |
| 6446005 | Bingeman et al. | Sep 2002 | B1 |
| 6477542 | Papaioannou | Nov 2002 | B1 |
| 6502669 | Harris | Jan 2003 | B1 |
| 6529164 | Carter | Mar 2003 | B1 |
| 6563427 | Bero et al. | May 2003 | B2 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6659344 | Otto et al. | Dec 2003 | B2 |
| 6700493 | Robinson | Mar 2004 | B1 |
| 6809645 | Mason | Oct 2004 | B1 |
| 6820062 | Gupta et al. | Nov 2004 | B1 |
| 6832884 | Robinson | Dec 2004 | B2 |
| 6880652 | Holtan et al. | Apr 2005 | B2 |
| 6894614 | Eckstein et al. | May 2005 | B2 |
| 6911908 | Beart | Jun 2005 | B1 |
| 6928343 | Cato | Aug 2005 | B2 |
| 6945366 | Taba | Sep 2005 | B2 |
| 6971464 | Marino et al. | Dec 2005 | B2 |
| 6972683 | Lestienne et al. | Dec 2005 | B2 |
| 7053823 | Cervinka et al. | May 2006 | B2 |
| 7084765 | Clapper | Aug 2006 | B2 |
| 7147154 | Myers et al. | Dec 2006 | B2 |
| 7183910 | Alvarez et al. | Feb 2007 | B2 |
| 7199709 | Parsons | Apr 2007 | B2 |
| 7203579 | Yokota et al. | Apr 2007 | B2 |
| 7218225 | Wieth et al. | May 2007 | B2 |
| 7277010 | Joao | Oct 2007 | B2 |
| 7356357 | DeCost et al. | Apr 2008 | B2 |
| 7389836 | Johnson et al. | Jun 2008 | B2 |
| 7395886 | Berg et al. | Jul 2008 | B2 |
| 7397373 | Hunt | Jul 2008 | B2 |
| 7420461 | Nebolon et al. | Sep 2008 | B2 |
| 8046160 | Carter et al. | Oct 2011 | B2 |
| 8406993 | Hannah et al. | Mar 2013 | B2 |
| 8417445 | Hannah et al. | Apr 2013 | B2 |
| 8433507 | Hannah et al. | Apr 2013 | B2 |
| 8463540 | Hannah | Jun 2013 | B2 |
| 8473192 | Hannah et al. | Jun 2013 | B2 |
| 8478471 | Hannah et al. | Jul 2013 | B2 |
| 8558698 | Hannah et al. | Oct 2013 | B1 |
| 8570171 | Hannah et al. | Oct 2013 | B2 |
| 8571778 | Hannah et al. | Oct 2013 | B2 |
| 8606501 | Hannah et al. | Dec 2013 | B2 |
| 8700230 | Hannah et al. | Apr 2014 | B1 |
| 8718923 | Hannah et al. | May 2014 | B2 |
| 9091551 | Hannah et al. | Jul 2015 | B2 |
| 9322658 | Hannah et al. | Apr 2016 | B2 |
| 9403548 | Hannah et al. | Aug 2016 | B2 |
| 9630639 | Carter et al. | Apr 2017 | B2 |
| 9637151 | Hannah et al. | May 2017 | B2 |
| 9669659 | McKay et al. | Jun 2017 | B2 |
| 9676405 | Hannah et al. | Jun 2017 | B2 |
| 9758185 | Hannah et al. | Sep 2017 | B2 |
| 9783218 | Hannah et al. | Oct 2017 | B2 |
| 9784951 | Ichimura | Oct 2017 | B2 |
| 9914470 | Hannah et al. | Mar 2018 | B2 |
| 9963162 | Hannah et al. | May 2018 | B1 |
| 10023216 | Hannah et al. | Jul 2018 | B2 |
| 10189494 | Hannah et al. | Jan 2019 | B2 |
| 10745040 | Hannah et al. | Aug 2020 | B2 |
| 20010000959 | Campana, Jr. | May 2001 | A1 |
| 20010017588 | Symonds et al. | Aug 2001 | A1 |
| 20010028301 | Geiger et al. | Oct 2001 | A1 |
| 20020003501 | Kushida | Jan 2002 | A1 |
| 20020027531 | Brown | Mar 2002 | A1 |
| 20020097182 | Goren et al. | Jul 2002 | A1 |
| 20020161651 | Godsey et al. | Oct 2002 | A1 |
| 20020167916 | Clapper | Nov 2002 | A1 |
| 20020196151 | Troxler | Dec 2002 | A1 |
| 20030043073 | Gray et al. | Mar 2003 | A1 |
| 20030043941 | Johnson et al. | Mar 2003 | A1 |
| 20030059288 | Robinson | Mar 2003 | A1 |
| 20030102969 | Parsons | Jun 2003 | A1 |
| 20030155891 | Ishishita | Aug 2003 | A1 |
| 20030206102 | Joao | Nov 2003 | A1 |
| 20030206115 | Krumm et al. | Nov 2003 | A1 |
| 20030214419 | Reindl | Nov 2003 | A1 |
| 20030224759 | Burnett | Dec 2003 | A1 |
| 20030234578 | Takahashi et al. | Dec 2003 | A1 |
| 20040024730 | Brown et al. | Feb 2004 | A1 |
| 20040031650 | Taba | Feb 2004 | A1 |
| 20040130457 | Ueda et al. | Jul 2004 | A1 |
| 20040161026 | Jensen et al. | Aug 2004 | A1 |
| 20040169589 | Lea et al. | Sep 2004 | A1 |
| 20040192399 | DeCost et al. | Sep 2004 | A1 |
| 20040215532 | Boman et al. | Oct 2004 | A1 |
| 20040217166 | Myers | Nov 2004 | A1 |
| 20040230345 | Tzamaloukas | Nov 2004 | A1 |
| 20040230370 | Tzamaloukas | Nov 2004 | A1 |
| 20040243262 | Hofmann | Dec 2004 | A1 |
| 20050018543 | Fujisawa | Jan 2005 | A1 |
| 20050027443 | Cato | Feb 2005 | A1 |
| 20050046570 | Conzola et al. | Mar 2005 | A1 |
| 20050049914 | Parish | Mar 2005 | A1 |
| 20050104307 | Roseman | May 2005 | A1 |
| 20050138077 | Michael et al. | Jun 2005 | A1 |
| 20050194218 | D'Arca | Sep 2005 | A1 |
| 20050259240 | Goren | Nov 2005 | A1 |
| 20060042734 | Turner et al. | Mar 2006 | A1 |
| 20060067226 | Chandra et al. | Mar 2006 | A1 |
| 20060107486 | Andre | May 2006 | A1 |
| 20060136303 | Bell et al. | Jun 2006 | A1 |
| 20060145838 | Alvarez et al. | Jul 2006 | A1 |
| 20060152195 | Ishishita | Jul 2006 | A1 |
| 20060197295 | Holtan et al. | Sep 2006 | A1 |
| 20060208902 | Brey | Sep 2006 | A1 |
| 20060247847 | Carter et al. | Nov 2006 | A1 |
| 20060249320 | Carter et al. | Nov 2006 | A1 |
| 20060279421 | French et al. | Dec 2006 | A1 |
| 20070008068 | Brice et al. | Jan 2007 | A1 |
| 20070225879 | French et al. | Sep 2007 | A1 |
| 20080115997 | Banno et al. | May 2008 | A1 |
| 20080315540 | Hannah et al. | Dec 2008 | A1 |
| 20120320199 | Kundu et al. | Dec 2012 | A1 |
| 20130257000 | Hannah et al. | Oct 2013 | A1 |
| 20130264786 | Hannah et al. | Oct 2013 | A1 |
| 20140236410 | Takizawa et al. | Aug 2014 | A1 |
| 20150325093 | Hannah et al. | Nov 2015 | A1 |
| 20150344055 | Hannah et al. | Dec 2015 | A1 |
| 20160288811 | Hannah et al. | Oct 2016 | A1 |
| 20160332653 | Hannah et al. | Nov 2016 | A1 |
| 20180141577 | Hannah et al. | May 2018 | A1 |
| 20210171083 | Hannah et al. | Jun 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 19717375 | Oct 1998 | DE |
| 29909798 | Sep 1999 | DE |
| 1126421 | Aug 2001 | EP |
| 2258294 | Aug 1975 | FR |
| 2266643 | Nov 1993 | GB |
| 2367169 | Mar 2002 | GB |
| 2391098 | Jan 2004 | GB |
| WO 9834819 | Aug 1998 | WO |
| WO 9851197 | Nov 1998 | WO |
| WO-0016564 | Mar 2000 | WO |
| WO 2001027891 | Apr 2001 | WO |
| WO 2002085684 | Oct 2002 | WO |
| WO 2005020173 | Mar 2005 | WO |
| WO 2016114987 | Jul 2016 | WO |
| Entry |
|---|
| Matthew S. Gast, ‘802.11 Wireless Networks The Definitive Guide’, Apr. 2002, O'reilly, (Year: 2002). |
| 2004 Sales presentation of Gatekeeper Systems, Inc. for its Purchek™ push-out prevention system. |
| English translation, with attachments, of initial office action issued in counterpart Chinese application No. 200680016621.2, which corresponds to WO 2006/102183. |
| European Search Report dated Feb. 8, 2017, in European Application No. EP 16 17 9519. |
| European Search Report dated Feb. 1, 2017, in European Application No. EP 16 17 9514. |
| Office Action dated Aug. 6, 2009, in U.S. Appl. No. 12/200,735. |
| Press release dated Apr. 28, 2005, titled Purchek™—a Trolley-based Anti-theft Solution from Gatekeeper Garners Huge Attention at the 2005 Retail Middle East Exhibition. |
| Press release titled “Gatekeeper Systems announces new product launch,” dated Feb. 18, 2005. |
| Supplemental European Search Report dated Jan. 15, 2015, in European Application No. EP 06 74 8454. |
| Office Action in related Chinese Application No. 200680016621.2, dated Feb. 6, 2009. |
| Office Action in related Chinese Application No. 200680016621.2, dated Nov. 27, 2009. |
| Office Action in related Chinese Application No. 200680016621.2, dated Dec. 2, 2010. |
| Office Action in related Canadian Application No. 2,601,565, dated Feb. 1, 2013. |
| Office Action in related Canadian Application No. 2,601,565, dated Dec. 30, 2013. |
| International Preliminary Report on Patentability in related International Patent Application No. PCT/US2006/009921, dated Nov. 8, 2007. |
| International Search Report and Written Opinion for International Application No. PCT/US2016/012606, dated May 13, 2016, in 17 pages. |
| Complaint for patent infringement filed by Gatekeeper Systems, Inc. in the Southern District of California against Carttronics LLC, dated Oct. 21, 2013, (case No. 13CV2531 BEN JMA). |
| First Amended Answer and Counterclaim of Carttronics dated Jan. 13, 2014, in matter of Gatekeeper Systems, Inc. v. Carttronics LLC, (case No. 13CV2531 BEN JMA). |
| Gatekeeper's Reply to Carttronics' First Amended Counterclaim dated Feb. 12, 2014, in matter of Gatekeeper Systems, Inc. v. Carttronics LLC, (case No. 13CV2531 BEN JMA). |
| Invalidity Contentions of Carttronics LLC and Cartronics, Inc. dated May 16, 2014, in matter of Gatekeeper Systems, Inc. v. Carttronics LLC, (case No. 13CV2531 BEN JMA). |
| Gatekeeper Systems, Inc.'s Preliminary Invalidity Contentions dated May 16, 2014, in matter of Gatekeeper Systems, Inc. v. Carttronics LLC, (case No. 13CV2531 BEN JMA). |
| Defendants' Preliminary Proposed Claim Constructions, dated Jun. 25, 2014, in matter of Gatekeeper Systems, Inc. v. Carttronics LLC and Carttronics, Inc., (case No. 13CV2531-BEN). |
| Compatible Electronics, Report No. B41111D1, FCC Part 15 Subpart B and FCC Section 15.231 Test Report for Purchek Wheel, P/N: W-9400, Nov. 16, 2004, in 40 pages. |
| Gatekeeper Systems, LLC, Purchek™ Pushout Prevention System Quickstart Guide, available at least as early as Nov. 2004, in 2 pages. |
| Gatekeeper Systems, LLC, Purchek™ Presentation, 2004, in 17 pages. |
| Gatekeeper Systems, LLC, Transmittal Letter, Response, Declaration Supporting Substitute Specimens under 37 C.F.R. 2.20, and Substitute Specimen, trademark: Purchek, Jul. 12, 2004, in 12 pages. |
| Gatekeeper Systems, LLC, Transmittal Letter, Statement of Use Under 37 CFR 2.88, trademark: Purchek, Oct. 30, 2003, in 7 pages. |
| Gatekeeper Systems, LLC, From the Process of Evolution Comes a Revolution, available at least as early as Oct. 2003, in 1 page. |
| Gatekeeper Systems, LLC, GS1 Cart Containment System, User Manual, © 2003, in 16 pages. |
| Gatekeeper Systems, LLC, GS1 System, Shopping Cart Containment System, available at least as early as Mar. 12, 2004, in 2 pages. |
| Gatekeeper Systems, LLC, Installation Overview, GS1 Shopping Cart Containment System, available at least as early as Mar. 12, 2004, in 5 pages. |
| Gatekeeper Systems, LLC, GS1 System: How it Works, available at least as early as Mar. 19, 2004, in 1 page. |
| Gatekeeper Systems, LLC, About the Company, available at least as early as Mar. 12, 2004, in 1 page. |
| Gatekeeper Systems, LLC, Purchek, Stop profits from rolling out the door, in 1 page. |
| Gatekeeper Systems, LLC, Purchek, Pushout Solution, available at least as early as Oct. 2003, in 2 pages. |
| Gatekeeper Systems, LLC, Purchek: How it Works, System Functionality Scenarios, available at least as early as Mar. 19, 2004, in 1 page. |
| Gatekeeper Systems, LLC, Purchek, How It Works, available at least as early as Mar. 19, 2004, in 1 page. |
| Gatekeeper Systems, LLC, Purchek, Pushout Prevention System, available at least as early as Mar. 12, 2004, in 2 pages. |
| Gatekeeper Systems, LLC, postcard titled Contain costs and valuable shopping cart inventory by using the GS1 System, available at least as early as Oct. 2003, in 2 pages. |
| Gatekeeper Systems, LLC, GS1 Technical Analysis, available at least as early as Apr. 2002, in 2 pages. |
| Gatekeeper Systems, LLC, Handi-Helper Tote, available at least as early as Mar. 12, 2004, in 1 page. |
| Gatekeeper Systems, LLC, GS2 System, mailer for the United Kingdom, Jul. 2007, in 2 pages. |
| Gatekeeper Systems, LLC, GS2 System, mailer for France, Jul. 2007, in 2 pages. |
| Gatekeeper Systems, LLC, GS1 System, Shopping Cart Containment Solution, available at least as early as Nov. 7, 2003, in 2 pages. |
| Gatekeeper Systems, LLC, Technical Specifications, available at least as early as Oct. 22, 2002, in 1 page. |
| Trademark Electronic Search System (TESS), Word Mark: Purchek, First Use: Feb. 2003, Filing Date: Dec. 21, 2001, in 1 page. |
| Gatekeeper Systems, LLC, GS1 System, Shopping Cart Containment System, available at least as early as Dec. 17, 2003, in 2 pages. |
| Activerf Limited, Owl One Way Lowcost, Pushout Prevention System, believed to be publically available in 2002, in 18 pages. |
| Activerf Limited, ExitMonitor Installation Guide, Publication 840-000370-101, Issue 1.01, Nov. 2002, in 46 pages. |
| Activerf Limited, ExitMonitor ASDA Staff Training Guide, © 2000, in 8 pages. |
| Activerf Limited, Owl pushout prevention system, Sep. 17, 2002, in 1 page. |
| Gatekeeper Systems, Inc.'s Preliminary Proposed Claim Constructions, dated Jun. 25, 2014, in matter of Gatekeeper Systems, Inc. v. Carttronics LLC and Carttronics, Inc., (case No. 13CV2531 BEN JMA). |
| General Secretariat of the International Telecommunication Union: ITU Additional Radio Regulations (1968 ed.), pp. 27, 99. |
| The Authoritative Dictionary of IEEE Standards Terms (7th ed. 2000), pp. 92, 911, 914, and 1253. |
| 47 CFR § 2.106, Table of Frequency Allocations (Oct. 1, 2000 ed.), p. 489. |
| Texas Instruments, CC2500 Low-Cost Low-Power 2.4 GHz RF Transceiver, labeled GATE 01-004348 to 01-004444, © 2014. |
| John Graham, The Facts on File Publications Dictionary of Telecommunications, Facts on File Publications, 1983, p. 136. |
| Number | Date | Country | |
|---|---|---|---|
| 20220119027 A1 | Apr 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60663195 | Mar 2005 | US | |
| 60663327 | Mar 2005 | US | |
| 60663147 | Mar 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17225830 | Apr 2021 | US |
| Child | 17564648 | US | |
| Parent | 16995471 | Aug 2020 | US |
| Child | 17225830 | US | |
| Parent | 16224046 | Dec 2018 | US |
| Child | 16995471 | US | |
| Parent | 15877187 | Jan 2018 | US |
| Child | 16224046 | US | |
| Parent | 15191303 | Jun 2016 | US |
| Child | 15877187 | US | |
| Parent | 15093545 | Apr 2016 | US |
| Child | 15191303 | US | |
| Parent | 14821244 | Aug 2015 | US |
| Child | 15093545 | US | |
| Parent | 13907502 | May 2013 | US |
| Child | 14821244 | US | |
| Parent | 11277016 | Mar 2006 | US |
| Child | 13907502 | US |
