The present disclosure relates to shelving and product display and a system for aiding in determining the inventory on the shelf in a retail store.
A major cost in the operation of retail stores relates to inventory management, which includes the tracking and storing of inventory. A significant portion of this cost relates to product inventory management in the selling area of the store. A considerable portion of inventory management cost is the periodic counting of product on the store shelves. This counting is necessary to determine the amount of product on the shelf and to help ensure the shelves are fully stocked.
Historically, the counting of inventory on store shelves was done manually, and the results were recorded on paper. More recently, however, inventory has been counted manually with the use of a small hand-held computer that can be configured to transmit the entered data to a central computer that compiles data and can be programmed to make decisions regarding the purchase of products for restocking the shelves. These recent advances have helped reduce the cost of inventory management; however, counting inventory still requires significant manual labor. It would be beneficial to reduce the amount of manual labor required to count the inventory.
Another significant cost relating to inventory management is product theft. Certain items are relatively small but represent a high value to potential thieves who can either resell the items or use them for other illegitimate purposes, as in the case of certain pharmaceutical products. The losses generated by such thefts have a negative impact on the profitability of retail stores.
Theft can be the result of both customers' and employees' actions and has been difficult to eliminate. Attempts to deter and prevent theft have proven to be only partially effective. For instance, in-store cameras often do not observe the theft clearly enough to catch or prosecute the thief. In addition, in-store security personnel are rarely in the correct position to actually observe a thief in action. As a result, theft continues to be a significant problem and cost in the management of inventory. It would be beneficial to provide aid in monitoring for theft.
Currently, retail stores can track the amount of product sold based on a number of items scanned at the checkout counter. While this ability has proven useful, certain inherent disadvantages result from the use of such a system. One inherent disadvantage is that the scanner only counts the number of products that are legitimately purchased. Therefore, if product is removed from the shelf but not purchased, the store is unable to determine the fact that product has been misplaced or stolen without visual inspection or detection. It would be useful to compare changes in product level on the shelves with the amount of product sold.
A second inherent disadvantage relates to store-run product promotions. A typical promotion will have a product located at the end of an aisle or in some type of promotional location that increase customer awareness of the product. Usually the product is also placed on the shelf in its traditional location so that customers familiar with the product placement of the store can find the product without undue searching. Therefore, customers can obtain the product being promoted in multiple places, and it can be difficult to determine the effectiveness of a particular promotional display, i.e., the effect of a promotional discount offered for the product versus the normal purchasing of the product. It would be beneficial to more accurately determine the effectiveness of in-store promotions.
Another major cost of inventory management is associated with having to maintain more inventory in the store then is actually needed to meet customer demand. As current systems of inventory do not automatically indicate that a shelf is empty, retail stores tend to rely on output measured through the checkout or, alternatively, through visual inspection to determine if additional product needs to be placed on the shelf. In order to ensure the shelves are stocked with product, often more product than is typically needed for a given period of time will be placed on the shelf, sometimes in multiple facings on each shelf. The use of multiple facings tends to take up valuable shelf space that could otherwise be allocated towards additional product choices so as to maximize consumer satisfaction. It would be beneficial to reduce the amount of inventory of a particular product in the retail store.
Methods of minimizing the amount of required shelf space are known. For example, U.S. Pat. No. 6,041,720 to Hardy and U.S. Pat. No. 4,830,201 to Breslow, which are incorporated by reference in their entirety, teach a system for organizing and displaying items on a shelf through the use of a pusher assembly.
In one aspect, this disclosure includes a display management system having a mechanism that may be configured to move in response to a product being removed from the display management system. This movement may be used to generate electronic data that may be detected. Further, this electronic data may be used to detect a security event, such as an attempted theft.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. The Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Several embodiments of the present invention are illustrated by way of example, but are not limited to the accompanying figures in which like reference numerals indicate similar elements and in which:
Before the embodiments of the invention are explained in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments and of being practiced or being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein are for the purpose of description and should not be regarded as limiting. The use of “including” and “comprising” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items and equivalents thereof.
The present disclosure may be used with the shelf and pusher assembly system described in either U.S. Pat. No. 6,041,720 to Hardy or U.S. Pat. No. 4,830,201 to Breslow. The present disclosure may also be used with other pusher assemblies and shelf configurations known in the art.
As depicted
The indicia strip 21 is depicted in
The representations in the pattern contained on the indicia strip 21 can be optically readable or can be read based on other methods, including but not limited to passive variable capacitance, inductance, resistance, or magnetic, or active signal detection.
In another alternative embodiment, the sensor assembly 30 may be mounted within or on the pusher 25 and configured to read the indicia strip 21. In this embodiment, the indicia strip 21 is not mounted to or part of the coil spring; rather, the indicia strip 21 may be positioned along the top of the floor 24 or along the underside of the floor 24 and is read by the sensor assembly 30. In one aspect of this embodiment, the indicia strip 21 is of the type that may have variable magnetic or capacitive characteristics. The sensor assembly 30 may incorporate an analog oscillator whose frequency is determined by the magnetism or capacitance of the indicia strip 21 at the particular position of the pusher 25. The oscillator can directly modulate the radio frequency signal and send that signal to a central access point, as discussed below. The central access point can then demodulate the signal and use the signal to determine the position of the pusher 25.
For a black/white printed indicia strip 21, an optical infrared or visible light LED retro-reflective sensor array can be used. In an embodiment, the indicia strip 21 pattern containing the various representations could be 6 bits wide. In an alternative embodiment, depending on the width of the shelf and the desired precision, the pattern on the indicia strip could be more than 6 bits wide.
In yet another alternative embodiment, the indicia strip 21 could be less than 6 bits wide. Reducing the number of bits on the indicia strip 21 reduces the precision regarding the position of the pusher 25 but has the advantage of potentially avoiding the need to determine the dimension of the product. An embodiment with a reduced number of bits will be discussed below. The indicia strip will preferably include at least two representations so that the two representations can be used to reflect at least two positions of the pusher.
Depending on the indicia strip 21 and the sensor assembly 30, the number of measurable positions of the pusher 25 can be varied. For example, a configuration of a 6 bit wide pattern on an indicia strip 21 with a sensor assembly 30 that can scan 6 bits could scan at least 64 representations associated with 64 positions of the pusher 25. The representations in the pattern on the indicia strip 21 can be in many symbologies but a Gray Code provides that only one bit will change in each increment of movement, reducing potential errors. The sensor assembly 30 and the indicia strip 21 can be configured depending on the distance of travel of the pusher 25 and the expected size of the product.
In an embodiment, the coil spring 20 has a width of about 1 inch and the indicia strip 21 covers approximately 80% of the width of the coil spring 20. One skilled in the art will understand that other widths of the coil spring 20, and other dimensions of the indicia strip 21 are possible with the invention.
In an embodiment, the number of products on the shelf could be measured by the number of measurable positions of pusher 25. In such an embodiment, the position of the pusher 25 could be used to determine the amount of product on the shelf without the need to manually count the product. In an alternative embodiment, the number of measurable positions could exceed the number of products that can be placed in a facing. In this alternative embodiment, it would be preferable to have the number of measurable positions be an integer multiple of the number of products for ease of calculating the amount of product on the shelf. Increasing the number of measurable positions can therefore improve the ability of the system to precisely calculate the amount of product in a facing. This can become more important when a product package is unusually thin and therefore the incremental movement of the pusher 25 from one code to the next becomes a large percentage of the thickness of each product package that it is pushing.
Thus, as different products have different dimensions, a configuration of the sensor assembly 30 and indicia strip 21 might be desired with an increased number of measurable positions. For example, a configuration where 256 positions of the pusher 25 are measured might be desirable. Such a configuration could be used to determine the actual number of product on the shelf for a wide variety of product dimensions.
In an alternative embodiment, the sensor assembly 30 and indicia strip 21 can be configured to provide a decreased number of measurable positions. In an embodiment, four positions of the pusher 25 are measurable. In such a configuration, the shelf would provide information regarding how full the shelf was but would not provide the actual quantity of items on the shelf (assuming that 4 products would not fill the facing). This configuration could be useful in providing an automatic notification that a shelf was running out of product and needed to be restocked without the need to determine the product dimensions.
For a black/white printed indicia strip 21, the sensor 50 can include, but is not limited to, an optical infrared or visible light LED retro-reflective sensor. Preferably, for a 6 bit wide pattern, a linear array of 6 emitters/sensors will be used where one emitter/sensor is aligned with each bit position printed on the indicia strip 21. In an embodiment, the sensor 50 is positioned approximately 0.1 inches from the surface of the printed strip mounted on the indicia strip 21. As each emitter/sensor pair illuminates its bit position, a binary code can be assembled by the controller 55 that corresponds to the representation on the indicia strip 21, the representation associated with a position of the pusher 25.
Regardless of how the position of the pusher 25 is determined, the controller 55 generates a pusher code that represents the position of the pusher 25. The pusher code can be in digital or analog form and reflects the position of the pusher 25. In addition, the pusher code can be processed data or unprocessed data. Thus, the pusher code can be, but is not limited to, the scanned representation or a controller processed representation. Alternatively, the pusher code can be some other data that reflects the relative position of the pusher 25.
The controller 55 is powered by a power source 75. The power source 75 can be, but is not limited to, a long life battery, a wired power supply, or a solar panel. As can be appreciated, the type of power supply will have an impact on the functionality of the sensor assembly 30. If the power source 75 is a long life battery, a system configuration designed to utilize less energy will be preferable to avoid the need to change the battery on a frequent basis. If the power source 75 is a wired power source, the sensor 50 can be used more frequently without the need to replenish the power supply and the sensor assembly 30 can even be configured to provide real time information.
The controller 55 can be manufactured with a unique serial number. In this embodiment, each pusher 25 would be associated with a unique serial number or identity code. Alternatively, each indicia strip 21 can include a unique identity code along with the representation associated with the position of the pusher 25. Encoding the indicia strip 21 with a unique identity code can reduce the complexity of the controller 55 but typically will result in increased complexity of the sensor 50. Regardless, when the information is transmitted from the sensor assembly 30, the information may include an identity code and the pusher code representative of the pusher 25 position. In addition, information such as time of sending and the status of the circuitry or the status of the power source may also be transmitted.
In this embodiment, an input signal is provided to the controller 155. The input signal can be a signal generated by the timing device 170 or can be from some other source. The controller 155, in response, activates the sensor 150 by sending a signal to the power management circuit 148. The controller 155 receives data from the sensor 150 which is used to form the pusher code representative of the position of the pusher 25. The controller 155 compares the data scanned by the sensor 150 with the previous data scanned by the sensor 150, which is data residing in the memory 156. Depending on the configuration of the system, if the data scanned by the sensor 150 is the same as the previous scanned data, the controller 155 can be configured to wait until the end of the next interval of the timer. If the data scanned by the sensor 150 is different, the controller 155 can then activate the communication control 157 and provide the pusher code to the communication control 157 for transmission. The communication control 157 can then transmit the pusher code for further processing. The terms “transmit” and “transmission,” unless otherwise specified, include sending of information over a wire or via a wireless system and can be direct or indirect (i.e. through a network). If the power source 175 is not a wired power supply, however, it is preferable to use a method of communication that consumes relatively little power.
In general, the power required to transmit wireless signals increases as the transmission distance increases. Thus, especially with a battery powered controller, the preferred wireless communication configuration will transmit low powered signals over a short distance. As depicted in
In an alternative embodiment, the controller 55 corresponding to each pusher 25 can be hard-wired to an access point 80 so that the controller 55 transmits the data to access point 80 over one or more wires. The access point 80 can then transmit the data to the store computer 90. In another alternative embodiment, the data is transmitted directly from the sensor assembly 30 to the store computer 90. In this embodiment, the transmission can be either wireless, such as an infrared, ultrasonic or electromagnetic wave transmission, or can be hard-wired. Depending on the method of transmission, it may be desirable to transmit the data from the sensor assembly 30 to the store computer 90 via a network protocol that can compensate for, or minimize, communication errors.
The use of a wired connection can provide a useful source of power and can reduce the possibility of communication collisions, especially if the signals are directly to the store computer 90. In addition, by providing additional power, the controller 55 can be configured to provide a real time update on the level of product on the shelf or in the store so that more accurate decisions regarding the need to order additional product can be made. This configuration also makes it possible to recognize and send alerts regarding potential theft situations based on the real-time movement of the pusher 25. The real time product information may make it possible to provide a more responsive inventory system so as to lower the amount of inventory in the store and therefore reduce the cost of inventory.
Wireless systems, on the other hand, provide increased flexibility in installation and can be readily installed in existing shelves without the need to install wires for either power or communication. In addition, the use of a wireless system allows for the gradual installation of an inventory system. For example, items of high value (and therefore suffering from an increased likelihood of being stolen) or items that tend to have significant variations in customer demand can be monitored first.
In an embodiment, the sensor assemblies 30 may be networked together via a series of wireless access points 80 where each access point 80 accepts transmissions from any sensor assembly 30 in the vicinity of the access point 80. Thus, in an embodiment, there exist a number of wireless access points 80 and the access points 80 are connected via a network, where the network transmits the data to the store computer 90. In an alternative embodiment, each wireless access point 80 transmits the data directly to the store computer 90.
Naturally, some combination of network and direct transmission is also possible and is considered within the scope of the present invention. For example, a battery powered sensor assembly 30 could communicate via a low powered wireless transmission to an access point 80, the access point 80 being powered by a wired power supply. The access point would transmit a wireless signal to a central access point 85 that was powered by a wired power supply. The central access point 85 could be connected via a wire to the store computer 90.
Referring back to
In an alternative embodiment, the sensor 50 continuously monitors the indicia strip 21. When a product is removed from the shelf, the pusher 25 will move and the sensor 50 can scan a new representation on the indicia strip 21 corresponding to the new position of the pusher 25. The controller 55 can then send a transmission including the new position of the pusher 25 to the store computer 90 (i.e. the controller 55 can send a new pusher code). In this alternative embodiment, the store computer 90 can monitor the amount of product on the shelf in real time.
As depicted in
For example, the store computer 90 could query a particular controller 55 about the position of the associated pusher 25. The controller 55 could activate the sensor 50 in response to the query and determine a pusher code reflecting the position of the pusher 25. The controller 55 could then transmit the pusher code along with the identity code of the controller 55 to the store computer 90. Based on the pusher code, the store computer 90 could determine the inventory level of a product. To avoid activating the wrong controller 55, the store computer 90 could include the identifying code in the transmission. The store computer 90 may store, access, and perform functions with the identifying codes of all or a subset of the controllers or pusher systems in the store.
In an embodiment, all the controllers 55 associated with products purchased from the same vendor could be queried just before the order to the respective vendor was placed. The order to that vendor could then be updated with the latest product inventory information. In this manner, the order placed to the vendor could be made more accurate without the need for laborious counting of products on the shelf.
Some vendors are responsible for stocking the shelves in a retail store instead of the store personnel. In a situation where a vendor was responsible for stocking the shelves, an embodiment of the present invention could provide the vendor with updates in response to queries from the vendor's computer. In an embodiment, the vendor could track the amount of product available on the shelves as frequently as desired, even in real time.
For example, a vendor could send a query to a controller 55 via a wide area network (“WAN”). The controller 55 could determine the position of the pusher 25 and transmit a signal back to the vendor via the WAN. In an alternative embodiment, the vendor could communicate with the store computer 90 to obtain information regarding the inventory level of products on the shelf.
In an embodiment, the vendor could control the manufacturing process of the product in response to inventory levels on the shelves. As can be appreciated, the vendor would have an increasingly effective inventory system if multiple stores were networked to the vendor's computer so that the aggregate amount of product on all the store shelves could be determined. If the vendor was only connected to a single store, the information, while less indicative of the total inventory, could provide valuable details regarding patterns of behavior of the consumers.
Information from the security camera could be sent to a television or other visual display device that is located near the location where the potential theft is occurring. The visual display device could display an image of the potential thief such that the potential thief could appreciate the fact that the thief was being watched.
As can be appreciated, the controller 155 preferably monitors the position of pusher 25 on a frequent or even real time basis so as to provide a more timely response. If a power source 75 consisting of a long life battery is utilized, it may be beneficial to utilize a controller that can determine a potential theft situation without the need to transmit data to the store computer 190. In such an embodiment, the controller can be configured to transmit data to provide inventory level updates and also to provide security notifications.
As can be appreciated, the position of the potential theft relative to the security camera 195 would be beneficial to provide an instruction to the security camera 195 to focus on a particular position. This positional information could be generated by a number of methods, including providing the store computer 190 with the security camera coordinate system for the security camera 195. The position of the controller 155 relative to the security camera 195 could be determined during setup and during a potential theft situation; the position of the controller 155 could be used to direct the focus of the security camera 195. Alternatively, the security camera 195 could be configured to focus in several positions, such as three points along an aisle, and the store computer 190 could indicate which position was the most appropriate for the particular situation. The described methods are illustrative because of the numerous methods of controlling the security camera 195 that exist.
In an embodiment with a two-way transmission between the store computer 190 and the controller 155, the store computer 190 could signal to the controller 155 to activate a device capable of providing an audible warning tone.
In another embodiment, the controller 155 could determine that a potential theft had occurred and could provide a notification, including the sounding of an audible warning tone. In addition, the controller 155 could transmit a signal to the store computer 190. In this alternative embodiment, the sensor assembly 30 would preferably include a timing device 70 so as to allow the controller 155 to more readily determine whether the rate of movement of pusher 25 exceeds a preset level.
In another embodiment, a two-tiered response could be implemented. If the change in position of the pusher 25 was greater than normal, a signal could be transmitted to the security camera 195. In addition, an inaudible notification could be provided directly to security personnel. If the positional change of the pusher 25 more clearly indicated a potential theft, an audible alarm and flashing lights could also be activated. Thus, the response could be configured to more carefully match the situation.
In step 410, the sensor 50 scans the representation contained in the pattern on the indicia strip 21 so that the controller 55 can generate the pusher code representative of the position of the pusher 25. In step 415, the controller 55 generates the pusher code in response to the pattern scanned by the sensor 50. In step 420, the controller 55 transmits a signal that can include the unique serial number of the controller 55 and the pusher code, to the store computer 90.
Next, in step 430, the store computer 90 receives the data from the controller 55. In an embodiment, the transfer of data from the controller 55 to the store computer 90 is direct. In another embodiment, the controller 55 transmits data to the store computer 90 indirectly through an access point or a network.
Then, in step 440, the store computer 90 calculates the amount of product on the shelf based on the position of the pusher 25. The store computer 90 also updates the inventory list at this point. In an embodiment where multiple facings have the same product, the total amount of product on all of the facings that have that product can be calculated. In an embodiment, the calculation of product in a facing can be accomplished through the use of a database of products and the relevant dimensions of a product, and the position of the pusher. In another embodiment, the number of products placed in the facing can be provided during setup of the controller 55 for that product. The position of the pusher 25 and the number of products corresponding to that position of the pusher 25 can be used to calculate the quantity of remaining products based on a later position of the pusher 25 through the use of well known extrapolation techniques.
In another embodiment, the position of the pusher 25 can be one of four positions representing X>¾, ¾≥X>½, ½≥X>¼, and X≤¼. This latter embodiment provides less precise information but also requires less computation effort to provide the approximate inventory level. In addition, this embodiment can be used to manage inventory without the need to determine and track the dimension of the product. In an embodiment, the amount product on the shelf can be roughly determined based the number of facings containing the product and whether the pusher 25 for each facing is in a position representative of a full, mostly full, low or almost empty facing.
In step 450, the store computer 90 determines whether any action is required. In an embodiment, a potential theft, a decrease in the inventory below a pre-set level or the emptying of a facing of product while ample product still remains on the shelf in other facings would indicate that some action was required. For example, the store computer 90 could determine that, based on historical usage and the average delivery time and the cost per delivery, the current level of inventory was low. In an alternative embodiment, the minimum inventory level could be preset and once the inventory level drops below a preset level, the store computer 90 could determine that the product level was low.
In step 460, the store computer 90 would determine if a potential theft was taking place. In an embodiment, the store computer 90 could compare the current level of inventory, based on the position of the pusher 25, to the previous level of inventory. If the rate of change in inventory level exceeded a preset level, the store computer 90 would determine that a potential theft was taking place. In step 465, the store computer 90 would notify security. The notification could include a page to security or a signal to a security camera 195 to focus in a particular direction.
Next, in step 470, the store computer 90 would determine if the existing order needed to be modified. The store computer 90 could compare the current product requirement to the current order. If the store computer 90 determined that an amount of product ordered was insufficient, the store computer 90 would proceed to step 475. In step 475, the store computer 90 would update the current inventory order so that the inventory order matched the current product requirements.
Next, in step 480, the store computer 90 would determine if a facing on a shelf was empty. If there was an empty facing, the store computer 90 would then notify the store management that there was an undesirable empty facing in step 485. The store management could then decide the appropriate action to take depending on the type of product and the availability of substitute goods. If the facing was not empty, the store computer 90 would wait until the next product update.
In step 520, the sensor assembly 30 receives the query from the store computer 90. In response to the query, the controller 55 activates the sensor 50 and prepares to receive data reflecting the position of the pusher 25. In step 530, the sensor 50 scans the indicia strip 21 and the controller 55 generates a pusher code representative of the position of the pusher 25.
In step 540, the sensor assembly 30 transmits the pusher code representative of the position of the pusher 25 along with the unique serial number of the controller 55 to the store computer 90.
Next, the store computer 90 receives this transmission in step 550. This transmission can be sent directly from the sensor assembly 30 to the store computer 90 or, preferably, it can be indirectly through a network. The transmission can be sent in a wireless manner, over wires, or some combination of a wireless and wired transmission.
Then, in step 560, the store computer 90 determines the level of inventory on the shelf. In an embodiment, the determination can be based on the product dimension and the position of the pusher 25. In an alternative embodiment, the determination can be based solely on the position of the pusher 25.
In step 620, a set-up button on a hand-held device is pressed. The hand-held device is configured to transmit a signal to a store computer 90 indicating that the user of the hand-held device is about to associate a product with a serial number or identifying code of a controller 55. Preferably, the transmission of signals between the hand-held device and the store computer 90 is done in a wireless manner. In an embodiment, the store computer 90 provides feedback to the user indicating that the store computer 90 is ready to proceed. In an alternative embodiment, no feedback is provided.
Next, in step 630, the UPC code of the product is scanned and transmitted to the store computer 90. Then, in step 640, the store computer 90 looks up the product dimension based on the UPC code. If the UPC code does not have a listed dimension, the store computer 90 checks if the user can input the needed dimension in step 642. If the user cannot, the setup is terminated and the user can try to setup a new product. If the user can determine the dimension, the user enters the dimension in step 644.
Next, in step 646, a dimension is associated with the UPC code. Then, in step 650 the store computer 90 sends a signal to the hand-held device to indicate that the user should proceed with the setup.
Next, in step 660 the user activates the controller 55 with the hand-held device. In an embodiment, an optical setup sensor is mounted on the pusher assembly and is connected to the controller 55. Preferably, the setup sensor is recessed in the pusher 25 but could be mounted in other locations such as on the top or the side of the pusher 25. The hand-held device will be configured to transmit a signal to the setup sensor. The act of transmitting the setup signal to the setup sensor will cause the controller 55 to awake from a dormant state.
Then in step 670, the controller 55, in response to the setup signal, will send data indicating that the controller 55 is being setup to the store computer 90. The data will include the unique serial number of the controller 55. The data may also include a generic setup code or a setup code corresponding to the hand-held scanner and can include a pusher code representative of the position of the pusher 25. In the event that multiple hand-held devices are being utilized at the same time, it may be beneficial to provide a setup code associated with a particular hand-held device.
Next, in step 680, the store computer 90 will receive the data from the controller 55. If the data includes the pusher code, the store computer 90 can calculate the amount of product in the facing at this time. In step 685, the store computer 90 sends a signal to the hand-held device indicating that the controller 55 has been setup and associated with the UPC code of a particular product. In addition, if the position of the pusher 25 was originally included, the store computer 90 can also provide a calculation of the current quantity of product in the facing that was just set up. In addition, the store computer 90 requests that the user verify that the setup information is correct.
Finally, in step 690, the user indicates the information is correct. Upon verification, the setup for the controller 55 is complete. To change the product associated with the controller 55, the process can be repeated.
In step 720, the hand-held device is used to scan the UPC code of the product and transmit the information to the store computer 90. Next, in step 730, the store computer 90 looks to see if a product dimension is listed for that scanned UPC code. In the event that no dimension is associated with the UPC code, the computer, in step 732, transmits a signal to the hand-held device requesting the user to input the appropriate product dimension.
If the user does not know the product dimension or cannot measure the dimension, the user can cancel the setup and start over with a new product in step 734.
If the user does know the dimension or is able to measure the dimension, the user then enters the dimension and transmits the information to the store computer 90 in step 736. After the product dimension is determined, in step 740, the store computer 90 sends a signal to the hand held device indicating that the user should proceed.
Next, in step 750, the user scans the serial number of the controller 55. Preferably, the serial number of the controller 55 is printed in a black/white code on a sticker mounted to the sensor assembly 30. After scanning the serial number, the hand held device transmits the serial number to the store computer 90.
Then, in step 760, the store computer 90 associates the UPC code of the product with the serial number of the controller 55. The store computer 90 then signals the hand held device that the setup for the device is complete. To avoid potential communication problems during setup, all communications between the hand-held device and the store computer 90 can include a code representing the hand-held device.
In an alternative embodiment, the method of associating a product with a controller 55 could be done without sending a signal to the store computer 90. In this embodiment, the data would be uploaded from the hand-held device once the user had associated the various controllers with the various products.
As can be appreciated, numerous methods of product association with a controller 55 are possible, thus the above methods are illustrative.
A system for determining the location of the pusher with an indicia strip and sensor has been described. Numerous additional methods exist for measuring the distance between the front or rear of a shelf and the pusher or the final product in a facing of products. Based on this distance, and understanding the dimension of the products in the facing, a simple calculation can be performed to determine the number of products in the facing. This calculation can be performed by a microprocessor, store computer, controller or some other processing device which has received the information regarding the distance between the shelf front and the last product in a facing. Moreover, the pusher assembly has been described to include a spring. However, some other biasing method, such as gravity or magnetism, would also work to move the pusher and the product forward.
In an embodiment of the present invention, as illustrated in
A corresponding receiver is incorporated into a location that is stationary in relation to the pusher 725. The receiver 712 can be incorporated into a front rail or another location at or near the front of the shelf, a receiver 730 can be incorporated into a rear rail or other location at or near the rear of the shelf, it also can be incorporated into the floor of the shelf, the track of the pusher, the roof of the shelf or the divider wall. The receiver detects the signal that is sent from the transmitter. For example, a LED may radiate light having a particular intensity. A phototransistor acting as a receiver detects the light signals being emitted from the LED. The sensitivity of the phototransistor and the intensity of the LED may be adjusted by the microprocessor in order to adjust the overall sensitivity of the optical components. In an embodiment, the adjustment can be done remotely. Thus, the transmitter can communicate in a wireless fashion with the receiver through RF, IR or other known means such as magnetic fields, electrical fields, sound waves and the like.
The transmitter and receiver may be in communication with a controller that tracks the time of sending and receiving. This data can be provided to a processing device such as a microprocessor or a store computer, thus in this embodiment the pusher code would include the time interval between sending and receiving. Information regarding the time at which the signal was sent and the time at which it was received may be utilized by a processing device to determine the time between the transmission and the receipt of the signal. Based on this length of time, the processing device can calculate the distance between the transmitter and the receiver. Knowing the dimensions of the shelf, the pusher system and the components thereof, this distance can then be translated into the distance between the front side 6 of the shelf and the face of the pusher 25 that is biased against the back of the facing of products. Such a translation is well known and within the knowledge of one of ordinary skill. If the relevant dimension of the products in the facing is known, the processing device can then calculate the number of products in the facing based on the known dimension of the products.
In an alternative embodiment, the transmitter and the receiver switch locations. The transmitter can be placed at or near the front or the rear of the shelf or other relatively stationary position and the receiver can be placed on or near the pusher. In an alternative embodiment, the transmitter and the receiver can be incorporated into the same device which merely bounces a signal off a stationary position. For example, a reflector can be placed on the pusher and a transmitter/receiver using a laser, or some other light source, can determine the distance between the reflector and the transmitter/receiver based on the time of travel. Examples of possible transmitter/receivers include, but are not limited to, optical displacement measurement sensors and reflective laser sensors. As can be appreciated, if a transmitter and a receiver are used to determine distance, it is preferable that the location of either the part that is stationary be located near the front side or the rear side of the shelf so as to make the distance calculation simpler and to avoid problems with symmetric distances on both sides of the stationary unit mounted to the shelf. For example, mounting a transmitter halfway between the front and rear of the shelf would make determining the location of the pusher more complicated because there would be two possible locations for a given distance.
In an embodiment, depicted in
A receiver is located at a position that is fixed in relation to the movement of the pusher 725. The receiver may be a phototransistor and can be located on the front of the shelf 705, such as receiver 710 or on a front rail 708 connected to the front of the shelf, such as receiver 712. The receiver can further be located on the floor of the shelf at any number of positions as represented by 714, on the floor of the pusher track at 716 or at a location above the shelf 705 such as on another shelf (not shown) mounted above the shelf 705. The receiver can be located on the divider wall at 720 or 722 or other location on the divider wall. The receiver also can be located near the rear side 707 at 730 or at 732. Preferably, the receiver will be mounted near the either front side 706 or the rear side 707 so as to make distance calculation simpler.
The receiver and the transmitter can also switch locations. The pusher can incorporate a receiver, and a transmitter can be incorporated at any of the locations 710-732 as well as in any other location that is fixed in relation to the movement of the pusher. Preferably, however, the location of the transmitter will be near either the front side 706 or the rear side 707 so as to make calculation of distance simpler.
In an embodiment, the transmitter is located at 700 and the receiver is located at 710. When the pusher moves backward or forward on the shelf, the transmitter 700, mounted on the pusher 725, moves with the pusher 725. When the pusher 725 is located near the back of the shelf, a signal will take a certain amount of time to travel from the transmitter 700 to the receiver 710. When the pusher 725 is located closer to the front of the shelf, a signal will take less time to travel from the transmitter 700 to the receiver 710. Data regarding the transmission and receipt of the signal (i.e. the pusher code) is sent to a microprocessor or other processing device. The processing device determines the amount of time it takes the signal to travel from the transmitter to the receiver. Knowing the signal travel speed, the processing device determines the distance between the transmitter and the receiver.
With an understanding of the location of the transmitter in relation to the products and an understanding of the location of the receiver in relation to the front or back of the shelf, the processing device will be able to determine the distance between the pusher and the front of the shelf. Using the dimension of the products, the processing device can then determine the number of products in the facing. The light emitting diode or other transmitter can be set to function periodically, continuously or on command from a remote location.
Alternatively, the processing device may control both the LED and phototransistor. The processing device may record a time T1 in which the microprocessor issues a command to generate a pulse from the LED and a time T2 in which the light signal is detected by the phototransistor. Both of these times T1 and T2 may be stored in memory and used to determine the number of product in the facing, using the above described relationships.
In an alternative sensing environment, a capacitive proximity sensor may be utilized to measure the distance between the front of the shelf and the pusher or the final product in a facing of products. The capacitive proximity sensor detects the pusher which acts as a target for the capacitive proximity sensor. The capacitive proximity sensor generates an electrostatic field which is directed at the target. As the distance of the pusher changes with respect to the location of the capacitive proximity sensor, the capacitive proximity sensor reacts to the changes in capacitance caused by the movement of the pusher in relation to the sensor.
Additional sensing environments may also include the use of magnetic proximity sensor or an inductive proximity sensor. In both sensing environments, the proximity sensors may be utilized to measure the distance between the front of the shelf and the pusher or the final product in a facing of product.
An inductive proximity sensor is useful in detection of metal targets as the inductive proximity sensor uses an induced field to sense the target object. In an embodiment with an inductive proximity sensor, the proximity of a pusher in relation to the inductive proximity sensor can be detected as the distance of the pusher changes with respect to the location of the inductive proximity sensor. Similarly, a magnetic proximity sensor based on the Hall Effect principle may also be utilized to sense the location of the pusher.
In an embodiment, a proximity sensor could be mounted near the rear side 707, the proximity sensor configured to sense the distance to the pusher 25. A processing device, such as the store computer or microprocessor, could determine the distance between the pusher 725 and the front side 706 and use that distance to determine how much product was left on the shelf.
In an alternative embodiment, a Radio Frequency Identifying Transponder (“RFIT”) having a unique identity code is mounted to the pusher 725. A sensor assembly including a transmitter/receiver can be mounted on the rear side 707 of the shelf 705. The transmitter/receiver, when activated, transmits an activation signal that activates the RFIT. The RFIT, upon activation, transmits a responsive signal that includes the unique identifying code. The transmitter/receiver receives the responsive signal from the RFIT. The sensor assembly is equipped with a timing device and measures the time between the initial transmission of the signal from the transmitter/receiver until the receipt of the responsive signal from the RFIT. In an embodiment, a controller can initiate the transmission of the signal and record the receipt of the responsive signal into memory. The controller is also equipped with a timing device to measure the delay. The delay in time can be used to calculate the distance between the transmitter/receiver and the RFIT. In an embodiment, the controller can calculate the distance and provide a pusher code that includes the distance. Alternatively, the pusher code will include data regarding the delay and the pusher code will be forwarded to a processing device for distance calculation. As discussed above, the distance between the pusher 25 and the transmitter/receiver can be used to calculate the amount of product remaining in the shelf.
An advantage of using an RFIT in combination with a transmitter/receiver is that it can be easily retro-fitted to existing systems. As the RFIT does not require internal power, this embodiment eliminates the need to provide a powered device on the pusher 725. The transmitter/receiver, however, is powered. Preferably, the transmitter/receiver transmits a focused or low powered signal so that only the RFIT associated with the transmitter/receiver is activated. Alternatively, the transmitter/receiver ignores responsive signals from RFIT's that do not include the proper unique identifying code.
In another alternative embodiment, a low powered, one-chip radar sensor may be used to determine the distance between the radar sensor and the pusher 725. Preferably the radar sensor may be mounted near the rear side 707 so as to make distance determinations less complex.
In an alternative embodiment of the present invention, a device for measuring the tension of the spring used for pushing the products can be used. The tension on the spring will, at least in part, be dependent upon the number of products in front of the pusher. As more products are placed in front of the pusher, the spring either further compresses or expands. In the case of a coil spring, as more products are placed in front of the pusher, the two ends of the spring move further apart and the spring further uncoils. As the spring uncoils, the amount of tension or pressure within the remaining coil of the spring increases. By measuring the tension of the spring, the length of the spring that is uncoiled can be determined.
The spring tension measuring device can incorporate a processing device or can transmit the information it measures to a microprocessor or other processing device. With a previous understanding of how the tension on the spring relates to the length of the spring, the processing device can determine the amount or length of spring that is uncoiled. For example, if the coil spring has a fixed spring constant, “k”, then the formula F=−kX can be used to calculate the length of spring that is uncoiled. This information can be used to determine the distance between the front of the shelf and the pusher. Understanding the dimensions of the products, the computing device can then determine the number of products in a facing.
A spring tension measuring device may include a force measuring unit that includes, but is not limited to, strain gauges, tensiometers, torque transducers or some other force measuring device to determine the tension exerted on the coil spring. The force measuring unit is preferably connected to a controller, where the controller is configured to convert the data from the force measuring unit into a force value. The controller could then transmit the force value to a processing device. In this embodiment, the pusher code would include a force value. Numerous other methods of measuring spring tension will be apparent to one of skill in the art and are within the scope of the invention.
In an alternative embodiment of the present invention, the number of products remaining in a particular facing is determined in part through the use of one or more transmitter(s) and receiver(s) placed on opposite lateral sides of the products. In one embodiment the transmitters or receivers may be placed on divider walls that separate facings of products. In one embodiment, a series of transmitters is incorporated into or onto the base of a divider wall. A series of receivers in incorporated into or onto the other side of the divider wall. In this manner, when products are on a shelf, those products that are being pushed are between the transmitters on one divider wall and the receivers on another divider wall.
Periodically, when prompted, or continuously, the transmitter sends a signal. If there is no product between the transmitter and the receiver, the receiver will receive the signal. If there is a product between the transmitter and the receiver, the product will block the signal, and the signal will not be received by the receiver.
A microprocessor receives the information regarding whether or not the various receivers received a signal. Based on this information, the microprocessor can determine the approximate distance between the front of the facing and the last product in the facing. With an understanding of the dimension of the products, the information regarding receipt and non-receipt of signals can be translated into an understanding of the approximate number of products in the particular facing. In an embodiment, one transmitter and one receiver is used to indicate that a particular shelf is running low on the associated product. In this embodiment, the location of the transmitter/receiver is preferably closer to the front side 706 then the rear side 707. Preferably a controller with a unique identifying code is associated with the transmitter and receiver so that the unique identifying code can be associated with the product.
The transmitter and the receiver can be incorporated into the same device which attempts to bounce a signal off a predetermined target affixed to a particular location. If the signal bounces as expected, it indicates that there is no product between the transmitter and the target location. If the signal does not bounce as expected, a product exists between the transmitter and the target location.
In one embodiment of the present invention, the pusher contacts a variety of sensing devices as it moves backward or forward on a shelf. Sensing devices are placed on a surface below, above, or on the sides of a pusher. These sensing devices include devices that are mechanical, electrical and electromechanical, optical and magnetic, and can include spring loaded latches, electrical contacts, light emitting diodes or metal wires or other sensors such as linear position sensors.
As the pusher moves backward or forward on a shelf, it interacts with the sensing devices. The pusher may interact with the devices through the mechanical contact of the pusher and the devices. The pusher may also be equipped with a separate sensing device that interacts with the stationary sensing devices as the pusher moves backward or forward.
Information regarding the interaction between the pusher and the sensing devices (i.e. the pusher code) is sent to a processing device. Based on the determination of the devices with which the pusher interacted, the processing device can determine the approximate position of the pusher in relation to the front of the shelf. With an understanding of product data, such as the dimension of the product, a processing device can then determine the approximate number of products that are in the particular facing related to the pusher and the sensing devices.
In an embodiment, as depicted in
In an alternative embodiment, as depicted in
For example, while contact 816 is activated, the processing device can determine that the amount product is equal to the amount of product that can fit in the space between the contact 816 and the front side 806 of the shelf 801. In the event that the contact 816 is activated and then deactivated, the processing device can determine that the pusher 825 is between contacts 815 and 817. This, therefore, provides an approximate position of the pusher 825 and the approximate position can be used to determine the approximate quantity of product remaining on the shelf. In an embodiment, the contacts can be spaced closer together near the front side 806 of the shelf 801 so that more accurate measurements can be taken as the amount of product on the shelf decreases. Alternatively, enough contacts can be used to provide a relatively precise location of the pusher 825.
In an alternative embodiment, as depicted in
In an alternative embodiment similar to the embodiments described above, a shelf management system 900 for detecting and communicating the position of a pusher assembly on a shelf is depicted in
As depicted, the pusher assembly 915 may include a biasing mechanism such as a coil spring. The pusher assembly 915 may include an integral divider wall 922 and a floor section 920 on one or both sides of the divider wall 922. The coil spring may be operatively connected or associated with a pusher 925 and can be used to urge the pusher 925, and the associated product 910, toward the front side of the shelf. The pusher assembly 915 may be modular and can include a divider wall or an additional floor section that fits or mates in place. Additionally, since the present invention has no connection to the pusher assembly 915, the present invention may work with any product shelving system.
The light assembly may include a light channel 930 and a light transceiver 932. The light transceiver 932 may be one of many light transceivers located on the light channel 930. The light transceiver 932 may be located behind the product 910 to be measured on a shelf. The light transceiver 932 may consist of a light transmitter 934 and a light sensor 936. The light transmitter 934 is configured to send a light signal 935 towards the pusher 925, while the light sensor 936 is configured to receive the light signal 935 from the pusher 925. In an alternative embodiment, the light transmitter 934 and the light sensor 936 may be the same component as part of the light transceiver 932. The spacing of the light transmitters 934 and the light sensors 936 on the light channel 930 may ensure that at least one light transmitter 934 and one light sensor 936 is focused on or sees every pusher 925. Additionally, the light channel 930 may include an electronic connection 938.
Without departing from this invention, the light assembly may utilize one of many different types of light, with one type of light being utilized is in the “infrared spectrum.” For example, the light assembly could include an infrared (IR) transceiver, wherein the IR transceiver may consist of an IR transmitter and an IR sensor.
As illustrated in
As illustrated in
In an aspect of the invention, the microcomputer in the control module 940 may compare the most current position of the pusher 925 with a previous position of the pusher. The difference in positions of the pusher 925 may result in the microcomputer determining a condition of the shelf management system 900. First, the microcomputer may determine that no activity has occurred since the last reading. Second, the microcomputer may determine that a normal shopping instance has occurred, and if so how many product packages are still being urged by the pusher 925. Third, if more than a predetermined number of product packages have been removed in less than a predetermined amount of time, the microcomputer may determine that a potential theft situation is in progress. Another condition that may be communicated is a low product condition. For example, the microcomputer may determine a low product condition if any pusher location is empty of product packages or less than a predetermined number of product packages are still being urged by the pusher 925.
As illustrated in
Additionally, for the shelf system 900 illustrated in
The thickness of the product also may be determined by the system when products are initially stocked in the system. The light transceiver 932 transmits the light signal 935 to the pusher 925 when no product is on the shelf. The light signal 935 may then be reflected back to the light transceiver 932 to determine the location of the pusher 925 by measuring and calculating the time to receive the light signal 935 at the light transceiver 932. When one product is added to the shelf, for example by an employee, the time to receive the light signal 935 back at the light transceiver 932 decreases a particular amount. Based on this decrease in the amount of time, the control module can calculate the thickness of the product.
In an alternative embodiment similar to the embodiments described above,
The pusher assembly 1015 may include a biasing mechanism such as a sheet coil spring. The pusher assembly 1015 may include an integral divider wall 1022 and a floor section 1020 on one or both sides of the divider wall 1022. The sheet coil spring may be operatively connected to a pusher 1025 and can be used to urge the pusher 1025, and the associated product 1010, toward the front side of the shelf. The pusher assembly 1015 may be modular and can include a divider wall or an additional floor section that fits or mates in place.
The laser assembly may include a rear reflector strip 1030 and a single light transceiver or laser scanner 1032. The laser scanner 1032 may emit or transmit a laser light or output beam 1035. The laser scanner 1032 may include a moving mirror or rotating mirror (not shown) located within or associated with the laser scanner 1032. Without departing from this invention, in place of or in addition to the moving mirror, the laser scanner 1032 may include an integrated circuit mirror technology, such as microelectromechanical systems (MEMS) mirrors used in the Digital Light Projector (DLP) field, wherein an array of tiny microscopic mirrors are used to direct and alter the output beam 1035. The moving mirror may rotate within the laser scanner to alter the output beam 1035 being emitted from the laser scanner 1032. The transmission and angles of the output beam 1035 may also be altered by other various ways. The moving mirror may be controlled by a microcomputer within the control module 1040. The moving mirror may direct the output beam 1035 from the laser scanner 1032 at various angles, thereby creating a swept beam 1037. The swept beam 1037 may be directed along the rear reflector strip. An example of a portion of the swept beam 1037 is illustrated in
As further illustrated in
As illustrated in
As illustrated in
The microcomputer in the control module 1040 may compare the most current position of the pusher 1025 with a previous position. The difference in positions of the pusher 1025 may result in the microcomputer determining a condition of the shelf management system 1000. First, the microcomputer may determine that no activity has occurred since the last reading. Second, the microcomputer may determine that a normal shopping instance has occurred, and if so how many product packages are still being urged by the pusher 1025. Third, if more than a predetermined number of product packages have been removed in less than a predetermined amount of time, the microcomputer may determine that a potential theft situation is in progress. Another condition that may be communicated is a low product condition. For example, the microcomputer may determine a low product condition if any pusher location is empty of product packages or less than a predetermined number of product packages are still being urged by the pusher 1025.
As illustrated in
In another embodiment similar to the embodiments described above, as illustrated in in
Additionally, the microcomputer may execute an algorithm which determines that multiple readings represent only one wide pusher 1125. This might be the case if readings are taken every 1 inch along the length of an example 48 inch-long shelf. A product position 1110 in front of a pusher 1125 on the shelf may be six inches wide. Therefore, in this example, five or six readings may be taken across the back of the pusher 1125 and product as the mirror sweeps and directs the swept beam 1137. If one of the six-inch wide products is removed from the pusher 1125, the microcomputer detects that at least five or six sensing positions essentially simultaneously changed an equal amount. The microcomputer may then be able to determine that all five or six readings represent one product width. This can be a learned aspect of the shelf management system 1100 which can change as different products are merchandised on the shelf over time.
In another embodiment similar to the embodiments described above, as illustrated in
For example, as specifically illustrated in
Additionally, for the shelf system illustrated in
The advantage of the invention illustrated in
The sensors of the various sensing configurations discussed in the above embodiments may output a signal representing the sensed parameter in either analog or digital format. The analog output may in the form of a voltage or current signal. As one skilled in the art will realize, an analog-to-digital converter may be utilized to transform the analog signal to a digital signal for use by a controller or processing device.
Variations and modifications of the foregoing are within the scope of the present invention. It should be understood that the invention disclosed and defined herein extends to all alternative combinations of two or more of the individual features mentioned or evident from the text and/or drawings. All of these different combinations constitute various alternative aspects of the present invention. The embodiments described herein explain the best modes known for practicing the invention and will enable others skilled in the art to utilize the invention. The clauses are to be construed to include alternative embodiments to the extent permitted by the prior art.
The display management system 1800 may comprise a pusher 1804. In one implementation, pusher 1804 may be generally referred to as a movable mechanism of a display management system, such as display management system 1800. As depicted in
In one implementation, and as depicted in
In one implementation, and as depicted in
The capacitive sensor 1822 may be utilized to determine a position of the pusher 1804 within the display management system 1800, independently of specific geometrical features of the display management system 1800. As such, the systems and methods described herein related to the capacitive sensor 1822 may be practiced with alternative display management systems described throughout this paper, as well as U.S. patent application Ser. No. 14/444,357, which has been incorporated herein by reference. In one implementation, the capacitive sensor 1822 may be configured to be positioned along the divider length 1816 on the floor structure 1810, and such that an uncoiled length 1823 of the coiled spring 1820 makes contact with a portion of the capacitive sensor 1822 extending along the divider length 1816. Accordingly, the capacitive sensor 1822 is described in further detail in relation to
In one example, a conductive material (in one example, a metal or alloy) from which the coiled spring 1820 in constructed makes contact with the capacitive sensor 1822. In one implementation, the extent to which the coiled spring 1820 makes contact with the capacitive sensor 1822 is proportional to an uncoiled length, such as, in one example, uncoiled length 1904 or 1906. In turn, an output signal from the capacitive sensor 1822 may vary based upon a length of the coiled spring 1820 in contact with the capacitive sensor 1822. In another example, a position of the pusher 1804 may be detected based on a point of contact of a portion of the coiled spring 1820 with the capacitive sensor 1822. Accordingly, an output signal from the capacitive sensor 1822 may vary based upon a position of the pusher 1804, and correspondingly, a number of display products (1902a-1902f) retained within the display management system 1800.
In one example, the capacitive sensor 1822 may be configured to output a signal proportional to a capacitance value, and such that the capacitance value may be based upon an uncoiled length (e.g. uncoiled lengths 1904 and 1906) of the coiled spring 1820. In one example, the control circuit 2006 comprises electronic elements configured to calculate one or more capacitance values associated with the capacitive sensor elements 2004a-2004f In another implementation, the control circuit 2006 may be referred to as a transmitter circuit, and configured to transmit one or more data points received from the capacitive sensor elements 2004a-2004f to a remote processor, such as the display management system controller device 2400 from
In one implementation, the circuit board 2002 may comprise a substantially insulating material configured to electrically insulate the capacitive sensor elements 2004a-2004f from one another. Further, the capacitive sensor elements 2004a-2004f may be connected to the control circuit 2006 by electrical conductors (not depicted in
In one example, a separation distance, such as separation distance 2018 and/or 2020, between a pair of capacitive sensor elements, selected from capacitive sensor elements 2004a-2004f, may determine a resolution of the capacitive sensor 1822. As such, a resolution of the capacitive sensor 1822 may be proportional to a precision with which the capacitive sensor 1822 can determine a location of a pusher, such as pusher 1804. In particular, as a number of capacitive sensor elements, such as capacitive sensor elements 2004a-2004f, is increased, the precision with which the capacitive sensor 1822 can determine the location of a pusher on the floor structure 1810 may also increase.
In one implementation, the capacitive sensor 1822 may be utilized to calculate an absolute location of the pusher 1804 on the floor structure 1810. As such, the location of the pusher 1804 may not be calibrated based upon a zeroed position on the floor structure 1810. Accordingly, a location of pusher 1804 may not be determined relative to another location on the capacitive sensor 1822, and the like.
In yet another implementation, the control circuit 2006 may be utilized to calculate a position of the pusher 1804 on the capacitive sensor 1822 using interpolation methodology. In particular, the control circuit 2006 may receive signals (otherwise referred to as sensor data) from multiple capacitive sensor elements, from the capacitive sensor elements 2004a-2004f, and by processing the received signals, determine that the location of the pusher 1804 lies between a pair of the capacitive sensor elements, selected from capacitive sensor elements 2004a-2004f Specifically, the control circuit 2006 may be utilized to interpolate a closeness of a pusher 1804 to a first capacitive sensor element versus a second, adjacent, capacitive sensor element. In this way, those of ordinary skill in the art will recognize that the capacitive sensor 1822 may be implemented, in one example, using a single pair of capacitive sensor elements 2004 spaced apart between the first end 1812 and the second end 1814 of the floor structure 1810.
Memory 2010 may be a form of persistent memory, or a form of volatile memory, or a combination thereof. As such, memory 2010 may comprise a form of random access memory (RAM) that is cleared by a power cycle or other reboot operation of the control circuit 2006. In other embodiments, memory 2010 may be non-volatile, such that it does not require power from power supply 2008 to maintain information. As such, memory 2010 may comprise a form of read only memory (ROM), or flash memory. Generally, memory 2010 may be referred to as a form of a non-transitory, computer-readable medium and utilized to store instructions that may be executed by processor 2014.
Interface 2012 may comprise hardware and/or firmware configured to facilitate communication between the control circuit 2006 and one or more external devices. For example, interface 2012 may be utilized to facilitate communication between processor 2014 and an external computer device across a network. In this way, interface 2012 may be configured to communicate via one or more of a wired connection, such as utilizing an Ethernet connection, or a wireless connection, such as utilizing a Bluetooth connection, a Wi-Fi connection, or the industrial, scientific, and medical (ISM) radio bands. Interface 2012 may be configured to facilitate communication between the control circuit 2006 and any wired or wireless link or network, and using any communication protocol.
In one implementation, processor 2014 comprises a microprocessor having one or more processing cores. As such, processor 2014 may be configured to execute instructions stored within memory 2010. Further, one or more processes executed by processor 2014 may be utilized to drive one or more electrical circuits associated with the circuit board 2002 and the plurality of capacitive sensor elements 2004a-2004f. Additionally, processor 2014 may be configured to receive and process, via interface 2012, one or more sensor readings from the plurality of capacitive sensor elements 2004a-2004f In one specific example, a capacitive sensor element, from the plurality of capacitive sensor elements 2004a-2004f may be configured to output an analog signal (voltage, current, and the like) or a digital signal (for example, a binary signal, among others).
In one example, one or more signals communicated from the plurality of capacitive sensor elements 2004a-2004f may be received by processor 2014. In turn, the processor 2014 may execute one or more processes on the received signals before communicating, via the interface 2012, the received signals to a remote processor, such as that processor 2404 associated with the display management system controller device 2400 described in
In one implementation, control circuit 2006 may be configured to communicate directly with a mobile device. As such, in one specific example, control circuit 2006 may be configured to establish a Bluetooth connection with a smart phone or tablet of a shopper in a store in order to receive one or more pieces of biographic information associated with the shopper. In this way, upon activation of pusher 1804 as one or more display products, such as display products 1902a-1902f, are removed from the display management system 1800, the control circuit 2006 may be configured to query a mobile device of a user removing the one or more display products to receive one or more pieces of biographic information associated with the user. The biography information may include, among others, a name, a gender, a preferred spoken language, an age, or an approximate age range. In another implementation, upon activation of the pusher 1804 as one or more display products are removed from the display management system, the control circuit 2006 may be configured to communicate with the display management system controller device 2400. In turn, the display management system controller device 2400 may attempt to establish a connection (via Bluetooth, and the like) to a mobile device associated with a user removing said one or more display products.
In one example, the capacitive sensor 1822 may be configured to operate within a low power mode until the pusher 1804 is moved as a result of one or more display products, such as display products 1902a-1902f, or removed from the display management system 1800. In particular, this low power mode may include processor 2014 operating in a low power configuration that continuously monitors the sensor outputs from the capacitive sensor elements 2004a-2004f Accordingly, in this example, the processor 2014 may execute one or more processes to enter a high power configuration upon receiving one or more sensor signals indicative of movement of the pusher 1804. Specifically, the high power configuration may include executing one or more processes to deliver additional electrical power to memory 2010, interface 2012, and/or processor 2014 in order to execute additional processes on the received sensor data and/or communicate the received sensor data to a remote processor. In this way, the capacitive sensor 1822 may be configured to consume a reduced amount of electrical energy while the pusher 1804 remains stationary. As such, this low power configuration may be utilized to prolong a battery life associated with power supply 2008. In another example, the capacitive sensor 1822 may be configured to operate within a low power configuration while the pusher 1804 remains stationary, and such that the low power configuration delivers electrical energy to one or more of the plurality of capacitive sensor elements 2004a-2004f Accordingly, in response to motion of the pusher 1804, one or more of the capacitive sensor elements 2004a-2004f may be configured to communicate a wake signal to the control circuit 2006 in order to enter a high power configuration. As such, the wake signal may be received by the control circuit 2006, and in response, additional power may be delivered to one or more of the memory 2010, interface 2012, and/or processor 2014. In this way, maintaining the capacitive sensor 1822, and in particular, the control circuit 2006, within a low power configuration for a period of time during which the pusher 1804 is stationary may allow for decreased overall energy consumption, and in one example, increased battery life of the capacitive sensor 1822.
A slidable shelf 2112 is mounted to one or more tracks 2114, which may be supported at least in part by the sides 2104. As depicted, the slidable shelf 2112 may include a support surface 2116 that supports a divider 2118. In one example, the support surface 2116 may support one or more display management systems, such as systems 1800 described previously. In one implementation, the support surface 2116 includes a rail 2120 mounted to the front of the shelf 2112. The rail, in turn, supports a retainer 2122. As depicted, a door 2124 with one or more handles 2126 may be mounted to the top 2102 via a hinge system 2128. In another implementation, the door 2124 may be referred to as a flip window 2124, and such that the flip window 2124 may be partially or wholly transparent to visible light. In this way, flip window 2124 may facilitate viewing of one or more display products within the box-shelf display management system 2100. In one specific example, the box-shelf display management system 2100 may be similar to the box-shelf 3405 described in U.S. application Ser. No. 14/046,385 filed 4 Oct. 2013, now U.S. Pat. No. 9,167,913, the entire contents of which are incorporated herein by reference for any and all non-limiting purposes. It is further contemplated that the display management system 3400, described in relation to
In one implementation, the box-shelf display management system 2100 may be configured to retain one or more display products, such as display products 1902a-1902f schematically depicted in
In one implementation, the box-shelf display management system 2100 may be configured with a sensor 2130. In particular, sensor 2130 may be an accelerometer. Further, the accelerometer sensor 2130 may be sensitive to accelerations (due to gravity or otherwise) along a single axis (one-axis accelerometer), along two mutually-perpendicular axes (a 2-axis accelerometer), or along three mutually-perpendicular axes (a 3-axis accelerometer). Those of ordinary skill in the art will recognize various specific implementations of one-axis, two-axis and three-axis accelerometer electronic circuits that may be utilized with the box-shelf display management system 2100, or other display management systems, such as systems 1800 and 2300, without departing from the disclosures described herein. Further, those of ordinary skill in the art will recognize that an accelerometer sensor 2130 may be utilized to determine an orientation of a structure to which it is affixed. As such, accelerometer sensor 2130 from
In one implementation, an accelerometer sensor, such as accelerometer sensor 2130, may be utilized to determine an orientation of the flip window 2124. As such, those of ordinary skill in the art will recognize that the accelerometer sensor 2130 may be located on the flip window 2124 at any location configured to move in conjunction with the movement of the flip window 2124, without departing from the scope of the disclosures described herein. Additionally, those of ordinary skill in the art will recognize that the accelerometer sensor 2130 may be generally utilized to determine an orientation of a flip window, similar to flip window 2124, as part of any display management system. As such, display management system 2100, having flip window 2124, is merely one example of a display management system with which an accelerometer sensor 2130 may be utilized. Accordingly, those of ordinary skill in the art will readily recognize various additional or alternative implementations of a display management structure similar to the housing 2106 having a movable feature similar to the flip window 2124 that is configured to be moved in order to remove one or more products from the display management structure. In turn, the accelerometer sensor 2130 may be coupled to a movable feature of the various additional or alternative implementations of display management structures that may be envisioned by those of ordinary skill in the art.
In one example, accelerometer sensor 2130 may be implemented as part of an integrated accelerometer device, as schematically depicted in
In one implementation, the integrated accelerometer device 2130 may be configured to output one or more sensor signals (otherwise referred to as motion data) indicative of an orientation of the flip window 2124. In one example, the one or more sensor signals may comprise an analog or a digital signal indicative of an acceleration along one or more of the axes to which the integrated accelerometer device 2130 is sensitive. Accordingly, in one example, the sensor signal output from the integrated accelerometer device 2130 may be as a result of an acceleration due to gravity resolved along one, two, or three mutually perpendicular axes (x-, y-, and/or z-axis) to which the integrated accelerometer device 2330 is sensitive. In one example, the integrated accelerometer device 2130 is configured to communicate a sensor signal (otherwise referred to as motion data) via the interface 2203 to a control circuit, such as control circuit 2006 depicted in
In one example, accelerometer sensor (otherwise referred to as an integrated accelerometer device) 2130 may be configured to operate in a low power configuration while a movable structure to which the accelerometer sensor 2130 is coupled remains stationary. As such, the accelerometer sensor 2130 may be configured to operate in this low power configuration while an output from the accelerometer circuit board 2200 is unchanging (indicative of, in one example, the flip window 2124 remaining at a fixed orientation). Accordingly, upon detection of motion of the flip window 2124, one or more of the accelerometer circuit board 2200, the control circuit 2006, and/or the display management system controller device 2400 may be configured to implement a high power configuration. As such, this high power configuration may be configured to execute one or more processes in response to movement of the flip window 2124, wherein movement of the flip window 2124 may be indicative of one or more display products, such as display products 1902a-1902f, being removed from a display management system, such as system 2100, 1800, and/or 2300.
In one example, upon application of a manual rotational force to the knob 2304 in a first direction (e.g. that direction indicated by arrow 2318), spiral rail 2302 may be configured to rotate about the center axis of bearing 2316. In turn, based upon the rotation of the spiral rail 2302, one or more display products supported by (hanging from) support rail 2310 may be urged by the spiral rail 2302 towards the front structure 2314. Conversely, upon application of a manual rotational force to the knob 2304 in a second direction (e.g. a direction opposite to by arrow 2318), spiral rail 2302 may be configured to urge one or more display products hanging from support rail 2310 towards the back structure 2306.
In one example, the spiral peg hook security device 2301 may be configured to display one or more products within a store. As such, in one embodiment, the spiral peg hook security device 2301 may be utilized to prevent multiple products that are supported by support rail 2310 from being quickly removed from the spiral peg hook security device 2301. In this way, the spiral peg hook security device 2301 may be utilized to deter theft of one or more products hanging from support rail 2310, due to the extended time needed to rotate knob 2304 and spiral rail 2302 in order to remove the one or more products from the device 2301.
In one implementation, an accelerometer sensor 2130 may be utilized with the display management system 2300 in order to detect motion of the knob 2304 and/or spiral rail 2302. As previously described, the spiral rail 2302 may be rotated in order to insert and/or remove one or more display products from the display management system 2300. In this way, the accelerometer sensor 2130 may be coupled to a structure that is configured to rotate upon application of a manual force to knob 2304. In one specific example, the accelerometer sensor 2130 may be coupled within a structure of the knob 2304, as schematically depicted in
Similar to the display management system 2100, display management system 2300 may utilize the accelerometer sensor 2130 to detect motion, and in response, execute one or more processes. In one example, a motion of the spiral rail 2302 may execute one or more processes to transition the accelerometer sensor 2130 from a low power configuration into a high power configuration, as described previously.
Generally, the display management system controller device 2400 may be configured to execute one or more processes in response to receiving sensor information from one or more of a capacitive sensor 1822 (via control circuit 2006), or from an accelerometer sensor 2130 (directly, or via control circuit 2006). In one example, communication between one or more of the control circuit 2006, the accelerometer sensor 2130, and the display management system controller device 2400 may be unidirectional, or may be bi-directional. In one implementation, the display management system controller device 2400 may be referred to as a remote processor, and may be positioned remotely from one or more display management systems (1800, 2100 and/or 2300) to which one or more sensors (1822, 2130) are attached for detection of motion indicative of one or more display products being removed. As such, a distance between the display management system controller device 2400 and one or more sensors with which it may be in communication may be any given distance, without departing from the scope of the disclosures described herein. For example, the display management system controller device 2400 may be positioned within a same geographic location (in one example, a same store) as the one or more sensor devices with which the display management system controller device 2400 is in communication. In another example, the display management system controller device 2400 may be positioned at a different geographic location to one or more display management systems (e.g. 1800, 2100, and/or 2300) with which the device 2400 in communication via network 2408.
In one implementation, the display management system controller device 2400 may be configured to calculate a position of a pusher 1804, a flip window 2124, and/or a spiral rail 2302. Accordingly, the display management system controller device 2400 may be configured to calculate a number of display products removed from one or more display management systems (e.g. 1800, 2100, and/or 2300) based upon detected motion of one or more pushers 1804, flip windows 2124, and/or spiral rails 2302.
In one specific example, the display management system controller device 2400 may be configured to determine a number of display products removed from the display management system 1800 based upon comparison of a first position of a pusher 1804 with a second position of said pusher 1804. In particular, processor 2404 may calculate a distance moved by pusher 1804, and execute one or more processes to consult a lookup table (stored, for example, in memory 2402) for a depth dimension associated with a plurality of products held within the display management system 1800. As such, processor 2404 may determine a product type held within display management system 1800 based upon information input by a user, or information sensed by one or more sensors 2410 (e.g. by scanning a barcode on the one or more products, or detecting a RFID signal associated with the one or more products within the display management system 1800, among others). In this way, upon receiving, from a lookup table within memory 2402, a depth dimension of a product held within the display management system 1800, and having calculated a distance moved by the pusher 1804, the processor 2404 may determine a number of products removed from the display management system 1800. Similarly, the processor 2404 may be utilized to determine a number of products inserted into a display management system 1800 (e.g. during a restocking process, and the like).
In another example, the display management system controller device 2400 may infer a depth dimension of a product type stored within a display management system 1800. In particular, without having information available within a lookup table stored in memory 2402, processor 2404 may determine a depth dimension of a product based upon one or more discrete motions of the pusher 1804. Specifically, after repeated instances of products being removed from the display management system 1800, processor 2404 may execute one or more processes to recognize a consistent distance moved by pusher 1804, and from this recognized distance, infer a depth dimension of a product to be utilized in determining a number of products removed from the display management system 1800 in response to future movements of pusher 1804.
Accordingly, the display management system controller device 2400 may be configured to execute one or more processes based upon information received from one or more control circuits, such as control circuit 2006, or accelerometer sensors, such as accelerometer sensor 2130. In addition, the display management system controller device 2400 may be configured to communicate with device 2410. In one example, device 2410 may comprise a camera, a speaker, a microphone, a proximity sensor, a motion sensor, an ambient light sensor, or an electronic display, among many others. In one specific example, the display management system controller device 2400 may be configured to display, on an electronic display device 2410, a message associated with one or more products stored within a display management system (e.g. system 1800, 2100, or 2300).
The display management system controller device 2400 may be configured to communicate with one or more mobile devices, such as mobile device 2412. As such, communication between the display management system controller device 2400 and one or more of a control circuit 2006, an accelerometer sensor 2130, device 2410, and/or mobile device 2412 may be via a network 2408. In turn, network 2408 may be a wired or wireless network that may utilize any communication protocol. As such, network 2408 may be the Internet, a wide area network (WAN), a local area network (LAN), or a Bluetooth connection, among many others. In one specific example, network 2408 may utilize one or more bands of the industrial, scientific and medical (ISM) radio bands.
In one implementation, the display management system controller device 2400 may execute one or more processes to receive and store one or more pieces of biographic information associated with a user, such as a user removing one or more display products from one or more display management systems (e.g. 1800, 2100, and/or 2300) in communication with the device 2400. In one example, the display management system controller device 2400 may receive one or more pieces of biographic information associated with the user, and received from a mobile device 2412 carried by the user. Specifically, the mobile device 2412 may comprise a smart phone or tablet carried by a user, and configured to communicate with the display management system controller device 2400 via one or more of a Bluetooth connection, an NFC connection, or a Wi-Fi connection, among others.
In one implementation, the display management system controller device 2400 may execute one or more processes to receive data from an additional sensor 2410, in response to receiving motion data from one or more sensors (e.g. one or more sensors 1822 and/or 2130) associated with one or more display management systems (e.g. 1800, 2100, and/or 2300). In one specific example, the display management system controller device 2400 may communicate with a camera device 2410, and execute one or more facial recognition processes to determine, in one example, an identity of a customer from a database of customers who are members of a store loyalty program. In another example, the display management system controller device 2400 may communicate with the camera device 2410, and execute one or more facial recognition processes to determine one or more points of information associated with a user removing the one or more products from the display management systems from which motion data is received. This information may include a gender and/or an approximate age range of the user removing the one or more products from the display management systems from which motion data is received. In this way, the display management system controller device 2400 may be utilized to collect shopper behavior information that may be utilized to plan product displays within a store, to determine a popularity of a given product for a given age range, and/or gender, and the like.
In yet another implementation, the display management system controller device 2400 may execute one or more processes to recognize one or more patterns from the data received from sensors associated with motion of one or more display management systems (e.g. systems 1800, 2100, and/or 2300). As such, processor 2404 may receive motion data from a plurality of sensors (e.g. one or more sensors 1822 and/or 2130), and based upon the received motion data, determine whether the sensor data represents a recognized pattern (stored in memory 2402) resulting from products being removed from the one or more display management systems (e.g. systems 1800, 2100, and/or 2300).
In one specific example, the display management system controller device 2400 may receive motion data from a single display management system (e.g. system 1800, 2100, or 2300) and determine that the received motion data represents removal of a plurality of a same product from the display management system. Further, the display management system controller device 2400 may calculate a rate at which products are being removed from this display management system. In one example, if a rate at which the products are being removed from this display management system is above a threshold level, the display management system controller device 2400 may determine that the removal of products may represent an attempted theft. In response, the display management system controller device 2400 may execute one or more processes to communicate a warning message to security personnel. In one example, this warning message may be communicated as an electronic message delivered via network 2408. Additionally or alternatively, the display management system controller device 2400 may, in response to determining that motion data represents a pattern associated with an attempted theft, communicate with a camera device 2410 to capture one or more images of a user of the display management system from which the motion data has been received. In this way, one or more images of a suspected thief may be recorded. Further, the display management system controller device 2400 may, in response to determining that received motion data may represents an attempted theft, execute one or more processes to sound an audible message and/or siren.
In another example, the display management system controller device 2400 may receive sensor data, otherwise referred to as motion data, from a plurality of sensors (e.g. one or more sensors 1822 and/or 2130, among others) associated with a plurality of display management systems (e.g. 1800, 2100, and/or 2300). Accordingly, the display management system controller device 2400 may execute one or more processes to recognize one or more patterns from the data received from the sensors. In this way, the display management system controller device 2400 may determine, in response to a rate at which products are being removed from the display management systems in close proximity to one another within a store being above a threshold rate level, that the received sensor data may represent an attempted theft. In response, the display management system controller device 2400 may communicate with a camera 2410, or communicate a message to security personnel, among others.
In one implementation, the display management system controller device 2400 may receive sensor data from an accelerometer sensor 2130 coupled to a flip window 2124. As such, data received from the accelerometer sensor 2130 may represent an orientation of the flip window 2124. In one embodiment, the display management system controller device 2400 may be configured to recalibrate a rest position (otherwise referred to as a zeroed position) associated with the accelerometer sensor 2130. In particular, the processor 2404 may execute one or more processes to recognize that the flip window 2124 is positioned at a specific angle when the flip window 2124 is not being moved. As such, this specific angle may not be equal to a 0° angle from a vertical orientation. In response, the processor 2404 may determine that the specific angle represents a rest position from which motion of the accelerometer sensor 2130 is to be calculated.
In one implementation, the display management system controller device 2400 may be configured to postpone one or more processes associated with recognition of an attempted theft. As such, processor 2404 may execute one or more processes to allow for restocking of one or more display management systems in communication with the display management system controller device 2400, and the like. In one example, a physical key may be utilized to disarm communication between a display management system (1800, 2100 and/or 2300) and the display management system controller device 2400. In another example, and electronic communication device (not shown) may be carried by a user restocking one or more of the display management systems in communication with the display management system controller device 2400. As such, the electronic medication device may communicate across network 2408 to identify the user as a person engaged in restocking a display management system. In yet another example, one or more security features associated with the display management system controller device 2400 configured to identify potential attempted thefts may be temporarily suspended based upon instructions received by the display management system controller device 2400 from a user. In one specific example, this user may be a store manager, and the like. As such, a temporary suspension may be applied to a subset of display management systems (e.g. one or more of the display management systems 1800, 2100 and/or 2300) in communication with the display management system controller device 2400.
In yet another example, display management system controller device 2400 may be connected to an inventory control system (not shown). As such, information gathered by the display management system controller device 2400 related to a number of products removed from one or more display management systems (e.g. one or more of the display management systems 1800, 2100 and/or 2300) may be communicated to an inventory control system such that information related to an inventory held within a store may be updated in real-time, and the like.
In another example, the display management system controller device 2400 may communicate with one or more devices configured to provide data associated with one or more display management systems (e.g. one or more of the display management systems 1800, 2100 and/or 2300), one or more individuals within a store (e.g. customers removing one or more products from the display management systems), and/or one or more communication devices (e.g. cameras, electronic display screens, microphones, ambient light sensors, motion sensors, mobile devices, and the like), among others. As such, the display management system controller device 2400 may communicate with one or more of devices 2006, 2330, 2410, and/or 2412. However, in one implementation, communication between one or more of the devices 2006, 2130, 2410, and/or 2412 may not be using a direct network connection. As such, in one example, communication between one or more of the depicted devices 2006, 2130, 2410, and/or 2412 may utilize mesh networking methodologies, without departing from the scope of the disclosures described herein.
Upon determining a source of received sensor data, processor 2404 may execute one or more processes to calculate a motion of a mechanism of a display management system. In particular, the processor 2404 may calculate a position of one or more of a pusher 1804, a flip window 2124, and/or a spiral rail 2302. From this position information, processor 2404 may calculate a distance moved by one or more of the respective mechanisms (1804, 2124, and/or 2302). As such, these one or more processes to calculate a motion of a mechanism of a display management system may be executed at block 2506 in accordance with motion calculation methods previously described in this document.
Further, process 2500 may calculate a number of products removed from the display management system. In particular, processor 2404 may execute one or more processes to infer, or lookup, from a lookup table stored within memory 2402, a depth of a product. Using this information, processor 2404 may compare a depth of a product to a distance moved by, in one example, a pusher 1804. In turn, processor 2404 may calculate the number of products removed from a display management system 1800. Similarly, processor 2404 may utilize substantially similar processes to determine a number of products inserted into a display management system 1800. Accordingly, this determination of a number of products removed from a display management system may be executed at block 2508 of process 2500.
In one example, upon calculation of a number of products removed from a display management system, processor 2404 may execute one or more processes to attempt to identify a pattern from the received sensor data. As such, processor 2404 may execute one or more processes to attempt to identify a product removal pattern from one or more display management systems, such as systems 1800, 2100, and/or 2300. In particular, processor 2404 may identify one or more product removal pattern indicative of a potential attempted theft based upon one or more product removal rates being above one or more threshold rate levels, and/or products being removed from a same display management system and/or multiple display management systems within a predetermined physical radius of one another. In one example, processor 2404 may attempt to identify one or more patterns from received sensor data at block 2510. Accordingly, decision block 2512 represents one or more processes executed by processor 2404 two check whether one or more one or more product removal patterns have been found from received sensor data. In one example, if a product removal pattern is identified by processor 2404, process 2500 may proceed to block 2516, wherein processor 2404 may communicate an alert message. As such, this alert message may be an audible message and/or siren emitted by a local audio box, such as local audio box 950. In another example, this alert message may be an electronic message communicated to security personnel within a store, among others. In another example, if a product removal pattern is not identified by processor 2404, process 2500 may proceed to block 2514, and such that display management system controller device 2400 may communicate with an external device, such as device 2410 and/or 2412.
In one implementation, and at decision block 2606, the processor 2014 may compare the calculated change in the output signal from the sensor to one or more predetermined threshold values. As such, the one or more predetermined threshold values may represent motion thresholds below which processor 2014 may discard the sensor data received at block 2602. Specifically, if the received sensor data is below the one or more predetermined threshold values, it may not be as a result of a product removal from a display management system, and may be due to random motion/vibration of a store shelf, among others. As such, in one example, block 2606 may have the behavior of an electronic filter, among others.
In one example, the processor 2014 may execute those processes associated with blocks 2602 and 2604 while operating in a low power configuration. In this way, assessment of received sensor data may be carried out while consuming a reduced amount of electrical energy, and thereby prolonging, in one example, the battery life of a sensor 1822, and/or 2130. Accordingly, if, at decision block 2606, it is determined that the received sensor data does not represent motion of a mechanism of a display management system above one or more threshold values, process 2600 proceeds to block 2608, and the processor 2014 remains in a low power configuration. If, however, it is determined that the received sensor data represents a motion of a mechanism of a display management system above the one or more threshold values, process 2600 proceeds to block 2610, and the processor 2014 may enter a high power configuration. In one example, the high power configuration may include communication of the sensor data to a remote processor, such as processor 2404. In another example, the high power configuration may include execution of one or more additional processes by the same processor 2014, wherein these additional processes may consume electrical energy at a higher rate than the processor 2014 consumers in a low power configuration.
In one example, process 2600 includes calculation of a position of a movable mechanism (e.g. pusher 1804, flip window 2124, and/or spiral rail 2302, among others) of a display management system. In particular, this calculation of a position of a movable mechanism of the display management system may be executed at block 2612. As such, calculation of a position of a movable mechanism of a display management system may include execution of one or more sub-processes to convert received sensor data into an indication of a position of the movable mechanism. Specifically, block 2612 may include execution of one or more processes to convert a value proportional to a capacitance of sensor 1822 into a position of pusher 1804. Additionally or alternatively, block 2612 may include execution of one or more processes to convert a value proportional to an acceleration sensed by accelerometer 2130 into a position of flip window 2124 or spiral rail 2302.
Upon calculation of a position of a movable mechanism of a display management system, processor 2014 and/or processor 2404 may query a lookup table, stored in memory 2010 and/or 2402 for information associated with one or more products stored within the display management system. This information may include a depth dimension of the product stored within the display management system. Accordingly, using this information, the processor 2014 and/or 2404 may calculate a number of products removed from the display management system. In particular, processor 2014 and/or 2404 may compare a distance moved by a movable mechanism of the display management system with the specific product dimensions. In one specific example, a distance moved by pusher 1804 may be divided by a depth dimension of a product stored within the display management system 1800. In one example, this calculation of a number of products removed from the display management system may be executed at block 2616.
The label holder 2712 may comprise a display plate 2716 that has a front surface 2718 and a back surface 2720. In one example, the front surface 2718 of the display plate 2716 may be configured to receive a display label (not shown in
In one example, the display management system 2700 may comprise a sensor device configured to output data responsive to a motion of the label holder 2712. As such,
In one implementation, the label holder rotation sensor device 2902 and can predict certain conditions of the label holder 2712. Specifically, in certain instances, the label holder rotation sensor device 2902 may execute one or more processes to detect a pattern from the received sensor data which may be indicative of an attempted theft of one or more products from the display management system 2700. For example, the label holder rotation sensor device 2902 may detect high-frequency movement of the label holder 2712 above a threshold frequency (it will be understood that any special frequency may be utilized without departing from the scope of these disclosures), which may be indicative of an attempted theft. In another example, the label holder rotation sensor device 2902 may detect that the whole display management system 2700 has been removed from a surface to which it was coupled (not depicted in
In one example, the label holder rotation sensor device 2902 may include one or more sensors on an integrated circuit. In another example, the label holder rotation sensor device 2902 may receive sensor data from a sensor element positioned elsewhere on the display management system 2700. For example,
As will be discussed in further detail below with respect to
In one example, and as schematically depicted in
In one example, the display management system 3400 may be used in combination with a peg board 3406. However, it is contemplated that additional or alternative display hardware may be used, such as a wire grid, grid wall panels, a slat wall, or shelf surface, among others. As depicted, the example products are displayed to a user (e.g. a shopper or store employee) while hanging below peg hook structures 3408a-3408h. In one example, each of the peg hook structures 3408a-3408h may be similar to one or more of display management system 2700, display management system 3000, display management system 3100, and/or display management system 3200. As such, each of the peg hook structures 3408a-3408h may include a label holder rotation sensor device similar to device 2902.
Additionally, the display management system 3400 may include a control module 3410, which may otherwise be referred to as a router 3410. In one example, the control module 3410 may be similar to control module 940, control module 1040, control module 1140, and/or control module 1240. In one implementation, the control module 3410 may include a wired power supply and a processor that executes instructions received from a remote computer device, or stored in on-board memory. The control module 3410 may be configured to communicate with the peg hook structures 3408a-3408h, an annunciator device 3412, and a user interface controller 3414 As such, the peg hook structures 3408a-3408h, the annunciator device 3412, and the user interface controller 3414 may each communicate with the control module 3410 using one or more wireless, digital or analog communication protocols or methodologies, such as Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, a cellular network, ZigBee, Z-Wave, 6LoWPAN, Thread, WiFi-ah, NFC, NB-IoT, EnOcean, Dash7, WireslessHART, infra-red, and RFID, among others.
In one implementation, the control module 3410 may be used to receive sensor information and determine if a security event, such as an attempted theft of products from a display system, is taking place within a store. In one example, the control module 3410 may determine if a security event, such as an attempted theft, is occurring based on a frequency at which one or more products are being removed from a display, such as display management system 3400. The control module 3400 may be configured to communicate with and receive sensor data from a label holder rotation sensor device 2902 that is coupled to one or more of the peg hook structures 3408a-3408h. It is further contemplated that the control module 3410 may be configured to wirelessly communicate, or communicate using a wired channel with and receive sensor data from sensor 2130 that may be coupled to a spiral peg hook security device 2301, or door or flip window 2124. Additionally or alternatively, the control module 1040 may be configured to receive data, by wireless or wired communication channels, from any of the sensors described throughout these disclosures, such as sensors 30, 50, 130, 150, 230, 250, 936, 1822, 2004, 2130, 2902, 3002, 3102, 3104, 3202, and/or 3204.
In one example, each of the label holder rotation sensor devices (e.g., device 2902) associated with each of the peg hook structures 3408a-3408h may be configured to function in a low-energy state when stationary for a predetermined timeout duration. A label holder rotation sensor device is configured to transition from a low-energy state to a high-energy state when motion is detected. When in the low-energy state, a label holder rotation sensor device may consume a comparatively reduced amount of energy from an integrated battery, and when in the high-energy state, the label holder rotation sensor device is configured to process the data generated by a sensor as a result of motion of the label holder rotation sensor device, and communicate a signal to the control module 3410.
The annunciator device 3412 may include a light output device 3416 and/or a speaker device 3418. The light output device 3416 may be configured to generate and output a visible alert. It is contemplated that this visible alert may include one or more different colors and a persistent or intermittent illumination of a light source. It is further contemplated that the intermittent illumination of the light source may include any pattern of illumination, and the light source may include any light source technology, including one or more LEDs, among others. Further, it is contemplated that the speaker device 3418 may output an audible signal of any type (e.g. a siren, a persistent or intermittent tone, a musical sequence, one or more messages in a spoken language, among others), additionally, the audible signal from the speaker device 3418 may be outputted at any volume, and the volume may be adjusted during or between audible signal outputs. Similar to the peg hook structures 3408a-3408h, the annunciator device 3412 may be configured to transition between a low-energy state when not in use, to a high-energy state upon receipt of a specific data type from the control module 3410. In one example, the annunciator device 3412 may be powered by an integrated battery.
The user interface controller 3414 may include a remote control device for receiving user input control commands. It is contemplated that the controller 3414 may have any number of user interface controls, and use any interface technology, including one or more buttons, touch screens, or switches, among others. In one example, the user interface controller 3414 may include a smartphone device, a tablet device, a laptop, or a personal computer, among others. Additionally or alternatively, control module 3410 of the display management system 3400 maybe configured to receive voice control commands from a user, among others.
In one example, each peg hook structure, from the peg hook structures 3408a-3408h may be saved into memory of the control module 3410, or another computer device that is wired or wirelessly connected to the control module 3410. Further, each peg hook structure may be associated in memory with a product section in a store. The association of the peg hook structure with a product section may be detected by a sensor within a label holder rotation sensor device (e.g. detected by a location sensor, an RFID sensor, among others). Additionally or alternatively, the association of peg hook structure with a product section may be user-inputted using the user interface controller 3414.
In one example, motion sensor data may be received from a sensor of a peg hook structure, such as a label holder rotation sensor 2902. The received motion data may be indicative of a motion of a label holder 2712. In one example, the one or more processes executed to receive motion sensor data may be executed at block 3602 of flowchart 3600.
The motion data received at block 3602 may be processed to determine if it is a motion that corresponds to a product being removed from (or added to) a lower rail 2706 of a display management system 2700, 3000, 3100, and/or 3200. Accordingly, one or more processes may be executed at block 3604 in order to analyze the received motion sensor data. This analysis may include comparing the received motion sensor data to one or more threshold values (e.g., orientation angle, duration of motion, speed of motion threshold values, among others) above which the motion data is determined to correspond to a product being removed from (or added to) a lower rail 2706.
If the received motion data is determined to correspond to a product being removed from a display management system, one or more processes may be executed to output a label holder activation signal. This label holder activation signal may include an indication that a motion sensor has been activated, and a unique identifier associated with the sensor and a given display management system (e.g., display management system 2700, 3000, 3100, and/or 3200). These one or more processes to output a label holder activation signal may be executed at block 3606. The control module 3410 may, in turn, execute one or more processes to receive the label holder activation signal at block 3612.
In one example, control data may be received from a user interface. The user interface may include the user interface controller 3414, which may be a handheld remote or smart phone device, a tablet, a laptop, or a personal computer, among others. One or more processes to receive the control data may be executed at block 3608.
The received control data may include instructions to activate a control module operational mode. From the received control data, one or more instructions to activate a control module operational mode may be identified. One or more processes executed to identify the control module operational mode may be executed at block 3610. In one implementation, the control module operational modes may include: a security operational mode, which may be activated at block 3614, a pairing operational mode, which may be activated at block 3616, a restocking operational mode, which may be activated at block 3618, and a status operational mode, which may be activated at 3620.
The control module 3410 may identify a security event from the received label holder activation signal. The security event may be identified based upon a threshold number of label holder activations received within a timeout period, or an anomalous signal received from a label holder, which may correspond to a label holder 2712 being held in an open position for a prolonged, and predetermined period of time, among others. One or more processes to identify the security event may be executed at block 3704. In response, the control module 3410 may output a security alert signal. This security alert signal may be, in one example, communicated to the annunciator device 3402 and/or a remote computer device, such as the user interface controller 3414.
In one example, a rotation sensor electronic signal may be generated in response to a threshold amount of motion of a label holder, and it is contemplated that any threshold amount of motion of the label holder may be used, without departing from the scope of these disclosures. In one example, the rotation sensor electronic signal may be communicated from a wireless or wired communication interface of the label holder rotation sensor device, and received by a wireless or wired communication interface of the control module 3410. In one example, one or more processes executed by the control module 3410 to receive the rotation sensor electronic signal may be executed at block 4102.
Upon receipt of the rotation sensor electronic signal, the control module 3410 may increment a counter stored in memory. This counter may be implemented using any known methodology, and may include a software, a firmware, and/or a hardware counter, or combinations thereof. In one example, the counter may be configured to reset to a null or zero count upon expiration of a threshold timeout period. It is contemplated that this threshold timeout period may be configured with any value, and may be adjustable by a user in software, firmware or hardware, or a combination thereof. In one example, one or more processes may be executed by the control module 3410 to increment the counter upon receipt of the rotation sensor electronic signal at block 4104 of flowchart 4100.
The control module 3410 may, upon receipt of the rotation sensor electronic signal, determine if the counter has reached a threshold value corresponding to a threshold number of rotations signals received within the timeout period. In one implementation, the threshold value may be determined to correspond to, among others, an attempted theft of one or more products from a display management system within a store. In another example, the threshold value may be determined to correspond to a user who is having difficulties removing one or more products from a display management system, and who may be in need of assistance from an employee within a store. These one or more processes to check if the counter has reached the threshold value may be executed at decision block 4106.
If the control module 3410 determines that a threshold number of rotation signals have been received within a timeout period, the control module 3410 may execute one or more processes to output an annunciator device electronic signal. This annunciator device electronic signal may include one or more instructions that are received by the annunciator device 3412. In response to receipt of the annunciator device electronic signal, the annunciator device 3412 may output one or more audible or visible signals that may include, among others, a siren, a tone, a sequence of musical notes, a sequence of flashing lights, a spoken language security announcement, or a spoken language announcement that assistance is needed for a customer at a specific location within a store, or combinations thereof. The one or more processes executed by the control module 3410 to output the annunciator device electronic signal may be executed at block 4108. Additionally or alternatively, if the control module 3410 determines that a threshold number of rotation signals have been received within a timeout period, the control module 3410 may communicate a signal to a remote device without indicating to a user who has caused the label holder to move that a threshold number of rotation signals have been received. In one example, the remote device may be associated with, among others, security personnel and/or management of a store.
The sensor device 4202 may be configured to detect motion of the flip window 4204. For example, the sensor device 4202 may detect when a user rotates the flip window 4204 about the hinge 4208. In one example, the sensor device 4202 may output a sensor activation signal or motion signal for any motion of an element to which it is coupled. In another example, the sensor device 4202 may output a sensor activation signal or motion signal when motion of an element to which it is coupled is above one or more fixed of user-definable motion thresholds. Further, the sensor device 4202 may be configured to communicate information to a remote device using one or more wireless communication channels. In one example, the sensor device 4202 may be configured to communicate with the control module 3410, as previously described. As such, the sensor device 4202 may be used in combination with the display management system 3400, as previously described. Accordingly, the sensor device 4202 may be utilized in one or more of the processes described in relation to
The sensor device 4202 may comprise a circuit board that integrates an accelerometer (single axis, two axis, or three axis accelerometer), a gyroscope, a light sensor (including an infra-red sensor and/or a sensor of light in the visible spectrum), a capacitive sensor, and/or a mechanical switch. Additionally, the sensor device 4202 may include any analog and/or digital circuitry used to facilitate the functionality of the one or more integrated sensors. The sensor device 4202 may include a power source. This power source may be in the form of a cell or battery 4206. Additionally or alternatively, the sensor device 4202 may include an energy harvesting device configured to convert kinetic energy from the motion of the flip window 4204 into electrical energy that may be stored in the battery 4206 and/or used to power the one or more electronic elements of the sensor device 4202. This energy harvesting device may be in the form of a dynamo that is implemented with any known electromechanical design, without departing from the scope of these disclosures. Additionally or alternatively, the sensor device 4202 may include one or more photovoltaic cells configured to convert light energy into electrical energy may be stored within the battery 4206 and/or used to power the one or more electronic elements of the sensor device 4202.
The sensor device 4202 may additionally include a transmitter or transceiver, hereinafter referred to as a transceiver, configured to facilitate one-way or two-way communication from, or from and to, the sensor device 4202. The transceiver may include any adapter hardware, firmware and/or software for communication using any wireless communication protocol, such as BLUETOOTH, BLUETOOTH LOW ENERGY (BLE), WI-FI, A CELLULAR NETWORK, ZIGBEE, Z-WAVE, 6LOWPAN, THREAD, WIFI-AH, NFC, NB-IOT, ENOCEAN, DASH7, WIRESLESSHART, INFRA-RED, AND RFID.
The sensor device 4202 may be coupled to the flip window 4204 by any mechanical coupling element, which may include, among others, an adhesive, a screw, a bolt, a rivet, a staple, a hook and loop fastener. Additionally or alternatively, the sensor device 4202 may be positioned within a slot or cutout of the flip window 4204 and may be loosely held within said slot or cutout, or held by way of an interference fit.
In another example, the sensor device 4202 may be coupled to a stationary portion of the display management system 4200, and the sensor device may detect products removed from or added to the display management system 4200 as a result of vibrations being propagated through one or more mechanical elements of the display management system 4200 to the sensor device 4202.
In one implementation, the sensor device 4202 may include firmware and/or processes stored within a non-transitory computer-readable medium (that may be any form of volatile memory, or any persistent form of memory). This firmware and/or processes may facilitate functionality to: filter, compress, interpolate or otherwise process data outputted from a sensor of the sensor device 4202, and/or identify patterns within sensor data received from the sensor of sensor device 4202. Additionally, the firmware and/or processes stored with in a non-transitory computer-readable medium may be used to communicate with a remote device through the transceiver.
In one example, the sensor device 4202 may be used in combination with any of the security systems, and attached to any of the movable window or other elements described in U.S. application Ser. No. 14/046,385, filed 4 Oct. 2013, now U.S. Pat. No. 9,167,913, the entire contents of which are incorporated herein by reference for any and all non-limiting purposes.
The communication device 4402 may be used in combination with the display management system 3400, as previously described. Accordingly, the communication device 4402 may be utilized in one or more of the processes described in relation to
The communication device 4402 may include elements similar to control sensor 2130, system controller device 2400, and/or communication device 4402, as previously described. In one example, the communication device 4402 may include a power source, such as a battery, an energy harvesting device, and/or one or more photovoltaic cells. The communication device 4402 may additionally include one or more logic circuits and/or microprocessors configured to receive, process and/or interpret sensor data received through terminals 4304. It is contemplated that any sensor data processes may be implemented by the communication device 4402, including, among others, filtering, interpolating, compressing, identifying one or more patterns within sensor data, and/or storage of multiple sensor activations. The communication device 4402 may additionally include a wireless transmitter or transceiver, which is hereinafter referred to as a transceiver. This wireless transceiver may include hardware, such as one or more antennae, and supporting firmware and software configured to communicate using any wireless communication channel and/or protocol. In one example, the communication device 4402 may communicate using one or more of BLUETOOTH, BLUETOOTH LOW ENERGY (BLE), WI-FI, A CELLULAR NETWORK, ZIGBEE, Z-WAVE, 6LOWPAN, THREAD, WIFI-AH, NFC, NB-IOT, ENOCEAN, DASH7, WIRESLESSHART, INFRA-RED, AND RFID. Additionally, the communication device may be configured to connect to a control module, similar to control module 3410, such that sensor hardware already installed within a display management system using a wired connection to terminals 4304 may be upgraded to having a wireless connection to control module 3410.
In one aspect, a display management system may include a support structure with an upper rail connected to a lower rail at a first, or proximal end. The support structure may be configured to be removably coupled to a surface at the first end, and the lower rail may be configured to support a hanging product that is added to and removed from the lower rail at a second, or distal end. The display management system may have a label holder that is pivotably coupled to a second, or distal end of the upper rail, with the label holder pivoting between a closed position and an open position. The label holder may further have a display plate that has a front surface for receiving a display label, and a back surface. Additionally, the label holder may have an arm structure extending from the back surface of the display plate, with the arm structure having a geometry that prevents more than one product from being removed from, or added to, the lower rail each time the label holder is pivoted from the closed position to the open position. The label holder of the display management system may additionally include a label holder rotation sensor device that is configured to output a rotation sensor electronic signal when the label holder is moved from a closed position to an open position. The display management system may additionally include an annunciator device, and a control module that is connected to the label holder rotation sensor device and the annunciator device. The control module may have a non-transitory computer-readable medium that has computer-executable instructions that are executed by a processor to receive the rotation sensor electronic signal from the label holder rotation sensor device. Further, the control module may be configured to output an annunciator device electronic signal upon receipt of a threshold number of rotation holder electronic signals from the label holder rotation sensor device within a threshold time period. The annunciator device, in turn, may be configured to receive the annunciator device electronic signal, and output an audible or visible signal.
The control module may communicate with the label holder rotation sensor device and the annunciator device using one or more wireless communication channels.
In one example, the control module may include a router device.
In another example, the label holder rotation sensor device may include an accelerometer sensor.
In one aspect, this disclosure includes a display management system having a mechanism that may be configured to move in response to a product being removed from the display management system. The display management system may additionally have a sensor that outputs motion data in response to movement of the mechanism. Further, the display management system may have a control circuit that receives the motion data and communicates the motion data to a remote processor if it exceeds a threshold value. Additionally, the display management system may have a non-transitory computer-readable medium comprising computer-executable instructions that may be executed by the remote processor to calculate the current position of the mechanism from the motion data, and calculate the number of products removed from the display management system based on the position of the mechanism.
In another aspect, this disclosure includes a display management system that may have a mechanism configured to move in response to a product being removed from the display management system. The display management system may further have a sensor that outputs motion data in response to movement of the mechanism. Additionally, the display management system may have a transmitter circuit that transmits the motion data to a remote processor, and a non-transitory computer readable medium comprising computer-executable instructions that may be executed by the remote processor to calculate the current position of the mechanism and calculate a product removal pattern.
In yet another aspect, this disclosure includes a non-transitory computer-readable medium comprising computer-executable instructions that when executed by a processor may be configured to receive sensor data from sensors associated with one or more display management systems. Additionally, the sensor data may be used to calculate a number of products removed from the one or more display management system, and may be used to detect product removal pattern based on the number of products removed from the display management systems.
In another aspect, this disclosure includes a display management system that has a support structure with an upper rail connected to a lower rail, the lower rail configured to support a hanging product. The display management system may have a label holder that is pivotably coupled to one end of the upper rail, with the label holder pivoting between a closed position and an open position. The label holder may further have a display plate that has a front surface for receiving a display label, and a back surface. Additionally, the label holder may have an arm structure extending from the back surface of the display plate, with the arm structure having a geometry that prevents more than one product from being removed from, or added to, the lower rail each time the label holder is pivoted from the closed position to the open position.
In another aspect, this disclosure relates to a display management system that has a support structure with an upper rail coupled to a lower rail, with the lower rail configured to support a hanging product. The display management system may have a label holder that is pivotably coupled to one end of the upper rail, with the label holder pivoting between a closed position and an open position. The label holder may also include a display plate that has a front surface configured to receive a display label, and a back surface. Additionally, the label holder may have a sensor device and a non-transitory computer-readable medium that has computer-executable instructions. When executed by a processor, the computer-executable instructions may receive data from the sensor device, and calculate a product removal pattern from the display management system.
In one aspect, a display management system may include a support structure with an upper rail connected to a lower rail at a first, or proximal end. The support structure may be configured to be removably coupled to a surface at the first end, and the lower rail may be configured to support a hanging product that is added to and removed from the lower rail at a second, or distal end. The display management system may have a label holder that is pivotably coupled to a second, or distal end of the upper rail, with the label holder pivoting between a closed position and an open position. The label holder may further have a display plate that has a front surface for receiving a display label, and a back surface. Additionally, the label holder may have an arm structure extending from the back surface of the display plate, with the arm structure having a geometry that prevents more than one product from being removed from, or added to, the lower rail each time the label holder is pivoted from the closed position to the open position.
The display management system may also include a label holder rotation sensor device in operative communication with a sensor. The label holder rotation sensor device may have a first non-transitory computer-readable medium with computer-executable instructions that are executed by a processor to receive motion data from the sensor, detect from the received motion data, a motion of the label holder, and output a label holder activation signal indicating that the label holder has been moved.
In one example, the display management system may include a control module that has a second non-transitory computer-readable medium with computer-executable instructions that are executed by a processor to receive control data from a user interface controller, and identify from the received control data and instruction to activate a control module operational mode.
The control data received from the user interface controller may include an instruction to operate the control module in a security operational mode. As such, the second non-transitory computer-readable medium may include computer-executable instructions that are executed by a processor to activate the security mode of the display management system. Additionally, the instructions may receive the label holder activation signal from the label holder rotation sensor device may identify, based on the received label holder activation signal, a security event, and output, based on the identified security event, a security alert signal.
The identification of the security event may further include identifying, based on the received label holder activation signal, a threshold number of activation signals received within a predetermined period of time from the label holder rotation sensor device, or from multiple label holder rotation sensor devices within a same product section.
The display management system may additionally include an annunciator device that has at least one of a speaker output device and a light output device. The annunciator device may also include a third non-transitory computer-readable medium that stores computer-executable instructions that are executed by a processor to receive a security alert signal, and output at least one of an audible or visible alert indication.
The control data received from the user interface controller may include an instruction to operate the control module in a pairing operational mode. As such, the second non-transitory computer-readable medium may include computer-executable instructions that are executed by a processor to activate a pairing mode of the display management system, receive a label holder activation signal, receive data from the user interface controller indicating a product section with which to associate the label holder rotation sensor device, and save into memory a record associating the product section and the label holder rotation sensor device.
The control data received from the user interface controller may include an instruction to operate the control module in a restocking operational mode. As such, the second non-transitory computer-readable medium may include computer-executable instructions that are executed by a processor to receive data from a user interface controller indicating a product section and a time delay during which the product section is to be restocked. Additionally, the processor may execute instructions to deactivate a security mode for the product section for a duration of the time delay and ignore the received the label holder activation signal for the duration of the time delay.
The control data received from the user interface controller may include an instruction to operate the control module in a status operational mode. As such, the second non-transitory computer-readable medium may include computer-executable instructions that are executed by a processor to output status data associated with the label holder rotation sensor device. The status data may include a battery charge level and a number of activations of the label holder rotations sensor device.
In one example, the sensor of the display management system may be an accelerometer or a product contact sensor coupled to the arm structure.
The various embodiments described herein may be implemented by general-purpose or specialized computer hardware. In one example, the computer hardware may comprise one or more processors, otherwise referred to as microprocessors, having one or more processing cores configured to allow for parallel processing/execution of instructions. As such, the various disclosures described herein may be implemented as software coding, wherein those of skill in the art will recognize various coding languages that may be employed with the disclosures described herein. Additionally, the disclosures described herein may be utilized in the implementation of application-specific integrated circuits (ASICs), or in the implementation of various electronic components comprising conventional electronic circuits (otherwise referred to as off-the-shelf components). Furthermore, those of ordinary skill in the art will understand that the various descriptions included in this disclosure may be implemented as data signals communicated using a variety of different technologies and processes. For example, the descriptions of the various disclosures described herein may be understood as comprising one or more streams of data signals, data instructions, or requests, and physically communicated as bits or symbols represented by differing voltage levels, currents, electromagnetic waves, magnetic fields, optical fields, or combinations thereof.
One or more of the disclosures described herein may comprise a computer program product having computer-readable medium/media with instructions stored thereon/therein that, when executed by a processor, are configured to perform one or more methods, techniques, systems, or embodiments described herein. As such, the instructions stored on the computer-readable media may comprise actions to be executed for performing various steps of the methods, techniques, systems, or embodiments described herein. Furthermore, the computer-readable medium/media may comprise a storage medium with instructions configured to be processed by a computing device, and specifically a processor associated with a computing device. As such the computer-readable medium may include a form of persistent or volatile memory such as a hard disk drive (HDD), a solid state drive (SSD), an optical disk (CD-ROMs, DVDs), tape drives, floppy disk, ROM, RAM, EPROM, EEPROM, DRAM, VRAM, flash memory, RAID devices, remote data storage (cloud storage, and the like), or any other media type or storage device suitable for storing data thereon/therein. Additionally, combinations of different storage media types may be implemented into a hybrid storage device. In one implementation, a first storage medium may be prioritized over a second storage medium, such that different workloads may be implemented by storage media of different priorities.
Further, the computer-readable media may store software code/instructions configured to control one or more of a general-purpose, or a specialized computer. Said software may be utilized to facilitate interface between a human user and a computing device, and wherein said software may include device drivers, operating systems, and applications. As such, the computer-readable media may store software code/instructions configured to perform one or more implementations described herein.
Those of ordinary skill in the art will understand that the various illustrative logical blocks, modules, circuits, techniques, or method steps of those implementations described herein may be implemented as electronic hardware devices, computer software, or combinations thereof. As such, various illustrative modules/components have been described throughout this disclosure in terms of general functionality, wherein one of ordinary skill in the art will understand that the described disclosures may be implemented as hardware, software, or combinations of both.
The one or more implementations described throughout this disclosure may utilize logical blocks, modules, and circuits that may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The techniques or steps of a method described in connection with the embodiments disclosed herein may be embodied directly in hardware, in software executed by a processor, or in a combination of the two. In some embodiments, any software module, software layer, or thread described herein may comprise an engine comprising firmware or software and hardware configured to perform embodiments described herein. Functions of a software module or software layer described herein may be embodied directly in hardware, or embodied as software executed by a processor, or embodied as a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read data from, and write data to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user device. In the alternative, the processor and the storage medium may reside as discrete components in a user device.
Accordingly, it will be understood that the invention is not to be limited to the embodiments disclosed herein, but is to be understood from the following clauses, which are to be interpreted as broadly as allowed under the law.
The instant application is a continuation of U.S. patent application Ser. No. 16/135,151, filed Sep. 19, 2018, which claims the benefit of and priority to U.S. Provisional Patent Application No. 62/560,498, filed Sep. 19, 2017, and U.S. Provisional Patent Application No. 62/622,560, filed Jan. 26, 2018, and is a continuation-in-part of U.S. patent application Ser. No. 14/939,220, filed Nov. 12, 2015 and issued as U.S. Pat. No. 10,339,495 on Jul. 2, 2019, which claims priority to U.S. Provisional Patent Application No. 62/078,809, filed Nov. 12, 2014, the disclosures of which are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
154940 | Adams | Sep 1874 | A |
355511 | Danner | Jan 1887 | A |
632231 | Blades | Dec 1905 | A |
808067 | Briggs | Dec 1905 | A |
847863 | Watts | Mar 1907 | A |
1156140 | Hair | Oct 1915 | A |
1682580 | Pratt | Aug 1928 | A |
1703987 | Butler | Mar 1929 | A |
1712080 | Kelly | May 1929 | A |
1714266 | Johnson | May 1929 | A |
1734031 | Carlston | Nov 1929 | A |
1786392 | Kemp | Dec 1930 | A |
1964597 | Rapellin | Jun 1934 | A |
1971749 | Hamilton | Aug 1934 | A |
1991102 | Kernaghan | Feb 1935 | A |
2057627 | Ferris | Oct 1936 | A |
2079754 | Waxgiser | May 1937 | A |
2085479 | Shaffer et al. | Jun 1937 | A |
2110299 | Hinkle | Mar 1938 | A |
2111496 | Scriba | Mar 1938 | A |
2129122 | Follett | Sep 1938 | A |
2185605 | Murphy | Jan 1940 | A |
2218444 | Vineyard | Oct 1940 | A |
2499088 | Brill | Feb 1950 | A |
2516122 | Hughes | Jul 1950 | A |
2538165 | Randtke | Jan 1951 | A |
2555102 | Anderson | May 1951 | A |
2563570 | Williams | Aug 1951 | A |
2652154 | Stevens | Sep 1953 | A |
2670853 | Schneider | Mar 1954 | A |
2678045 | Erhard | May 1954 | A |
2732952 | Skelton | Jan 1956 | A |
2738881 | Michel | Mar 1956 | A |
2750049 | Hunter | Jun 1956 | A |
2775365 | Mestman | Dec 1956 | A |
2893596 | Gabrielsen | Jul 1959 | A |
2918295 | Milner | Dec 1959 | A |
2934212 | Jacobson | Apr 1960 | A |
2948403 | Vallez | Aug 1960 | A |
2964154 | Erickson | Dec 1960 | A |
3083067 | Vos et al. | Mar 1963 | A |
3103396 | Portnoy | Sep 1963 | A |
3151576 | Patterson | Oct 1964 | A |
3161295 | Chesley | Dec 1964 | A |
3166195 | Taber | Jan 1965 | A |
3285429 | Propst | Nov 1966 | A |
3308961 | Chesley | Mar 1967 | A |
3308964 | Pistone | Mar 1967 | A |
3348732 | Shwarz | Oct 1967 | A |
3405716 | Cafiero | Oct 1968 | A |
3452899 | Libberton | Jul 1969 | A |
3481482 | Wilkens | Dec 1969 | A |
3497081 | Field | Feb 1970 | A |
3501020 | Krikorian | Mar 1970 | A |
D219058 | Kaczur | Oct 1970 | S |
3550979 | Protzmann | Dec 1970 | A |
3598246 | Galli | Aug 1971 | A |
3652154 | Gebel | Mar 1972 | A |
3667826 | Wood | Jun 1972 | A |
3698568 | Armstrong | Oct 1972 | A |
3709371 | Luck | Jan 1973 | A |
3724715 | Auriemma | Apr 1973 | A |
3751129 | Wright et al. | Aug 1973 | A |
3767083 | Webb | Oct 1973 | A |
3814490 | Dean et al. | Jun 1974 | A |
3815519 | Meyer | Jun 1974 | A |
3830169 | Madey | Aug 1974 | A |
3848745 | Smith | Nov 1974 | A |
3868021 | Heinrich | Feb 1975 | A |
3870156 | O'Neill | Mar 1975 | A |
4007841 | Seipel | Feb 1977 | A |
4042096 | Smith | Aug 1977 | A |
4106668 | Gebhardt et al. | Aug 1978 | A |
4269326 | Delbrouck | May 1981 | A |
4300693 | Spamer | Nov 1981 | A |
4303162 | Suttles | Dec 1981 | A |
4314700 | Dylag | Feb 1982 | A |
4331243 | Doll | May 1982 | A |
4351439 | Taylor | Sep 1982 | A |
4378872 | Brown | Apr 1983 | A |
4448653 | Wegmann | May 1984 | A |
4454948 | Spamer | Jun 1984 | A |
4460096 | Ricci | Jul 1984 | A |
4463854 | MacKenzie | Aug 1984 | A |
4467927 | Nathan | Aug 1984 | A |
4476985 | Norberg et al. | Oct 1984 | A |
4482066 | Dykstra | Nov 1984 | A |
4488653 | Belokin | Dec 1984 | A |
4504100 | Chaumard | Mar 1985 | A |
4588093 | Field | May 1986 | A |
4589349 | Gebhardt et al. | May 1986 | A |
4602560 | Jacky | Jul 1986 | A |
4615276 | Garabedian | Oct 1986 | A |
4620489 | Albano | Nov 1986 | A |
4629072 | Loew | Dec 1986 | A |
4651883 | Gullett et al. | Mar 1987 | A |
4685574 | Young et al. | Aug 1987 | A |
4705175 | Howard et al. | Nov 1987 | A |
4706821 | Kohls et al. | Nov 1987 | A |
4724968 | Wombacher | Feb 1988 | A |
4729481 | Hawkinson et al. | Mar 1988 | A |
4730741 | Jackle, III et al. | Mar 1988 | A |
4742936 | Rein | May 1988 | A |
4762235 | Howard et al. | Aug 1988 | A |
4762236 | Jackle, III et al. | Aug 1988 | A |
4768661 | Pfeifer | Sep 1988 | A |
4775058 | Yatsko | Oct 1988 | A |
4776472 | Rosen | Oct 1988 | A |
4790037 | Phillips | Dec 1988 | A |
4809856 | Muth | Mar 1989 | A |
4828144 | Garrick | May 1989 | A |
4830201 | Breslow | May 1989 | A |
4836390 | Polvere | Jun 1989 | A |
4846367 | Guigan et al. | Jul 1989 | A |
4883169 | Flanagan, Jr. | Nov 1989 | A |
4899668 | Valiulis | Feb 1990 | A |
4901853 | Maryatt | Feb 1990 | A |
4901869 | Hawkinson et al. | Feb 1990 | A |
4907707 | Crum | Mar 1990 | A |
4934645 | Breslow | Jun 1990 | A |
4954697 | Kokubun et al. | Sep 1990 | A |
5009334 | Bodkins | Apr 1991 | A |
5012936 | Crum | May 1991 | A |
5025936 | Lamoureaux | Jun 1991 | A |
5027957 | Skalski | Jul 1991 | A |
5082125 | Ninni | Jan 1992 | A |
5088607 | Risafi et al. | Feb 1992 | A |
5110192 | Lauterbach | May 1992 | A |
5111942 | Bernardin | May 1992 | A |
5123546 | Crum | Jun 1992 | A |
5148927 | Gebka | Sep 1992 | A |
5161702 | Skalski | Nov 1992 | A |
5172314 | Poland et al. | Dec 1992 | A |
5178258 | Smalley et al. | Jan 1993 | A |
5183166 | Belokin, Jr. et al. | Feb 1993 | A |
5190186 | Yablans et al. | Mar 1993 | A |
5203463 | Gold | Apr 1993 | A |
5215199 | Bejarano | Jun 1993 | A |
5240126 | Foster et al. | Aug 1993 | A |
5255802 | Krinke et al. | Oct 1993 | A |
5257090 | Meinzer et al. | Oct 1993 | A |
5265738 | Yablans et al. | Nov 1993 | A |
5316154 | Hajec, Jr. | May 1994 | A |
5341945 | Gibson | Aug 1994 | A |
5351839 | Beeler et al. | Oct 1994 | A |
5366099 | Schmid | Nov 1994 | A |
5381908 | Hepp | Jan 1995 | A |
5390802 | Pappagallo et al. | Feb 1995 | A |
5413229 | Zuberbuhler et al. | May 1995 | A |
5415297 | Klein et al. | May 1995 | A |
5448226 | Failing, Jr. et al. | Sep 1995 | A |
5450969 | Johnson et al. | Sep 1995 | A |
5458248 | Alain | Oct 1995 | A |
5464105 | Mandeltort | Nov 1995 | A |
5469975 | Fajnsztajn | Nov 1995 | A |
5469976 | Burchell | Nov 1995 | A |
5537312 | Sekiguchi et al. | Jul 1996 | A |
5542552 | Yablans et al. | Aug 1996 | A |
5548282 | Escritt et al. | Aug 1996 | A |
5562217 | Salveson et al. | Oct 1996 | A |
5613621 | Gervasi et al. | Mar 1997 | A |
D378888 | Bertilsson | Apr 1997 | S |
5615780 | Nimetz et al. | Apr 1997 | A |
5634564 | Spamer et al. | Jun 1997 | A |
5638963 | Finnelly et al. | Jun 1997 | A |
5665304 | Heinen et al. | Sep 1997 | A |
5671362 | Cowe et al. | Sep 1997 | A |
5671851 | Johnson et al. | Sep 1997 | A |
5673801 | Markson | Oct 1997 | A |
D386363 | Dardashti | Nov 1997 | S |
5685664 | Parham et al. | Nov 1997 | A |
5702008 | Thalenfeld et al. | Dec 1997 | A |
5711432 | Stein et al. | Jan 1998 | A |
5730320 | David | Mar 1998 | A |
5737504 | Yamada | Apr 1998 | A |
5738019 | Parker | Apr 1998 | A |
5740944 | Crawford | Apr 1998 | A |
5743428 | Rankin, VI | Apr 1998 | A |
5746328 | Beeler et al. | May 1998 | A |
5788090 | Kajiwara | Aug 1998 | A |
5803276 | Vogler | Sep 1998 | A |
5826731 | Dardashti | Oct 1998 | A |
5839588 | Hawkinson | Nov 1998 | A |
5855283 | Johnson | Jan 1999 | A |
5859414 | Grimes et al. | Jan 1999 | A |
5873473 | Pater | Feb 1999 | A |
5878895 | Springs | Mar 1999 | A |
5880449 | Teicher et al. | Mar 1999 | A |
5906283 | Kump et al. | May 1999 | A |
5933813 | Teicher et al. | Aug 1999 | A |
5963134 | Bowers et al. | Oct 1999 | A |
5971204 | Apps | Oct 1999 | A |
5992652 | Springs | Nov 1999 | A |
5992653 | Anderson et al. | Nov 1999 | A |
6006678 | Merit et al. | Dec 1999 | A |
6041720 | Hardy | Mar 2000 | A |
6076670 | Yeranossian | Jun 2000 | A |
6082557 | Leahy | Jul 2000 | A |
6082558 | Battaglia | Jul 2000 | A |
6089385 | Nozawa | Jul 2000 | A |
6105004 | Halperin et al. | Aug 2000 | A |
6105791 | Chalson et al. | Aug 2000 | A |
6112938 | Apps | Sep 2000 | A |
6124851 | Jacobson | Sep 2000 | A |
6129218 | Henry et al. | Oct 2000 | A |
6142317 | Merl | Nov 2000 | A |
6158598 | Josefsson | Dec 2000 | A |
6164491 | Bustos et al. | Dec 2000 | A |
6173845 | Higgins et al. | Jan 2001 | B1 |
6209733 | Higgins et al. | Apr 2001 | B1 |
6227385 | Nickerson | May 2001 | B1 |
6234325 | Higgins et al. | May 2001 | B1 |
6234326 | Higgins et al. | May 2001 | B1 |
6234328 | Mason | May 2001 | B1 |
6253190 | Sutherland | Jun 2001 | B1 |
D445615 | Burke | Jul 2001 | S |
6253954 | Yasaka | Jul 2001 | B1 |
6269285 | Mignault | Jul 2001 | B1 |
6289326 | LaFleur | Sep 2001 | B1 |
6357606 | Henry | Mar 2002 | B1 |
6378727 | Dupuis et al. | Apr 2002 | B1 |
6382431 | Burke | May 2002 | B1 |
6389991 | Morrisson | May 2002 | B1 |
6401942 | Eckert | Jun 2002 | B1 |
6405880 | Webb | Jun 2002 | B1 |
6409026 | Watanabe | Jun 2002 | B2 |
6409027 | Chang et al. | Jun 2002 | B1 |
6409028 | Nickerson | Jun 2002 | B2 |
6464089 | Rankin, VI | Oct 2002 | B1 |
6484891 | Burke | Nov 2002 | B2 |
6497326 | Osawa | Dec 2002 | B1 |
6497367 | Conzola et al. | Dec 2002 | B2 |
6507352 | Cohen et al. | Jan 2003 | B1 |
6523664 | Shaw et al. | Feb 2003 | B2 |
6523703 | Robertson | Feb 2003 | B1 |
6527127 | Dumontet | Mar 2003 | B2 |
6533131 | Bada | Mar 2003 | B2 |
6536658 | Rantze | Mar 2003 | B1 |
D472411 | Burke | Apr 2003 | S |
6550674 | Neumark | Apr 2003 | B1 |
6598754 | Weiler | Jul 2003 | B2 |
6622874 | Hawkinson | Sep 2003 | B1 |
6655536 | Jo et al. | Dec 2003 | B2 |
6666533 | Stavros | Dec 2003 | B1 |
D485699 | Mueller et al. | Jan 2004 | S |
6717516 | Bridgelall | Apr 2004 | B2 |
6738628 | McCall et al. | May 2004 | B1 |
6772888 | Burke | Aug 2004 | B2 |
6830157 | Robertson et al. | Dec 2004 | B2 |
6866156 | Nagel et al. | Mar 2005 | B2 |
6886699 | Johnson et al. | May 2005 | B2 |
6889854 | Burke | May 2005 | B2 |
6897763 | Schulmerich et al. | May 2005 | B2 |
6914648 | Niiyama et al. | Jul 2005 | B2 |
6948900 | Neuman | Sep 2005 | B1 |
6964235 | Hardy | Nov 2005 | B2 |
7002451 | Freeman | Feb 2006 | B2 |
7084769 | Bauer et al. | Aug 2006 | B2 |
7090125 | Goel et al. | Aug 2006 | B2 |
7093546 | Hardy | Aug 2006 | B2 |
7114606 | Shaw et al. | Oct 2006 | B2 |
7152040 | Hawthorne et al. | Dec 2006 | B1 |
7152791 | Chappidi et al. | Dec 2006 | B2 |
7155238 | Katz | Dec 2006 | B2 |
7216770 | Mueller et al. | May 2007 | B2 |
7252230 | Sheikh et al. | Aug 2007 | B1 |
7319397 | Chung et al. | Jan 2008 | B2 |
7400251 | Czyszczewski et al. | Jul 2008 | B2 |
7458473 | Mason | Dec 2008 | B1 |
7493336 | Noonan | Feb 2009 | B2 |
7520429 | Koster | Apr 2009 | B2 |
7526762 | Astala et al. | Apr 2009 | B1 |
7542283 | Curran et al. | Jun 2009 | B1 |
7565108 | Kotola et al. | Jul 2009 | B2 |
7580845 | Burman et al. | Aug 2009 | B2 |
7614065 | Weissmueller, Jr. et al. | Nov 2009 | B2 |
7641057 | Mueller et al. | Jan 2010 | B2 |
7675422 | Stevens et al. | Mar 2010 | B2 |
7686185 | Zychinski | Mar 2010 | B2 |
7743984 | Olsen et al. | Jun 2010 | B2 |
7768399 | Hachmann et al. | Aug 2010 | B2 |
7775130 | Harish et al. | Aug 2010 | B2 |
7775430 | Lin | Aug 2010 | B2 |
7792711 | Swafford, Jr. et al. | Sep 2010 | B2 |
7815060 | Iellimo | Oct 2010 | B2 |
7823734 | Hardy | Nov 2010 | B2 |
7837106 | Fabre et al. | Nov 2010 | B2 |
7853477 | O'Shea et al. | Dec 2010 | B2 |
7864041 | Godlewski | Jan 2011 | B2 |
7896172 | Hester | Mar 2011 | B1 |
7904333 | Perkowski | Mar 2011 | B1 |
7982622 | Burchell et al. | Jul 2011 | B2 |
8047385 | Hardy | Nov 2011 | B2 |
8089357 | Irmscher et al. | Jan 2012 | B2 |
8135482 | Caldwell et al. | Mar 2012 | B2 |
8144245 | Vik | Mar 2012 | B2 |
8171142 | Kolin et al. | May 2012 | B2 |
8184005 | Kamel | May 2012 | B2 |
8207819 | Bonner et al. | Jun 2012 | B2 |
8219558 | Trandal et al. | Jul 2012 | B1 |
8231017 | Clontz et al. | Jul 2012 | B2 |
8255500 | Cacheria, III et al. | Aug 2012 | B2 |
8280784 | Hurtis et al. | Oct 2012 | B2 |
8284059 | Ross | Oct 2012 | B2 |
8284061 | Dione | Oct 2012 | B1 |
8312999 | Hardy | Nov 2012 | B2 |
8321302 | Bauer et al. | Nov 2012 | B2 |
8322544 | Hardy | Dec 2012 | B2 |
8342340 | Rataiczak, III et al. | Jan 2013 | B2 |
8376154 | Sun | Feb 2013 | B2 |
8410931 | Petite et al. | Apr 2013 | B2 |
8463431 | Segal et al. | Jun 2013 | B2 |
8489452 | Warner et al. | Jul 2013 | B1 |
8534469 | Northrup, Jr. et al. | Sep 2013 | B2 |
8602224 | Casey | Dec 2013 | B2 |
8629772 | Valiulis et al. | Jan 2014 | B2 |
8655795 | Kolchin | Feb 2014 | B1 |
8662325 | Davis et al. | Mar 2014 | B2 |
8698606 | Choi et al. | Apr 2014 | B2 |
8739984 | Hardy | Jun 2014 | B2 |
8751318 | Kim et al. | Jun 2014 | B2 |
8781622 | Mockus et al. | Jul 2014 | B2 |
8810392 | Teller et al. | Aug 2014 | B1 |
8823521 | Overhultz | Sep 2014 | B2 |
8844431 | Davis et al. | Sep 2014 | B2 |
8978904 | Hardy | Mar 2015 | B2 |
9072394 | Hardy | Jul 2015 | B2 |
9167913 | Hardy | Oct 2015 | B2 |
9167916 | Grant et al. | Oct 2015 | B2 |
9275361 | Meyer | Mar 2016 | B2 |
9318007 | Valiulis et al. | Apr 2016 | B2 |
9318008 | Valiulis et al. | Apr 2016 | B2 |
9468315 | Ha et al. | Oct 2016 | B2 |
9576417 | Christianson | Feb 2017 | B2 |
9697709 | King et al. | Jul 2017 | B2 |
9706857 | Hardy et al. | Jul 2017 | B2 |
9820587 | Cheng et al. | Nov 2017 | B1 |
9898712 | Johnson et al. | Feb 2018 | B2 |
10007892 | Jahn et al. | Jun 2018 | B1 |
10210478 | Johnson et al. | Feb 2019 | B2 |
10262293 | Prater et al. | Apr 2019 | B1 |
10271666 | Taylor et al. | Apr 2019 | B2 |
10334964 | Hachmann | Jul 2019 | B2 |
10410277 | Bynum et al. | Sep 2019 | B2 |
10420427 | Hachmann | Sep 2019 | B2 |
20010010302 | Nickerson | Aug 2001 | A1 |
20010017284 | Watanabe | Aug 2001 | A1 |
20010051901 | Hager et al. | Dec 2001 | A1 |
20020036178 | Tombu | Mar 2002 | A1 |
20020108916 | Nickerson | Aug 2002 | A1 |
20020148794 | Marihugh | Oct 2002 | A1 |
20020158133 | Conzola et al. | Oct 2002 | A1 |
20020170866 | Johnson et al. | Nov 2002 | A1 |
20020178013 | Hoffman et al. | Nov 2002 | A1 |
20030000956 | Maldonado | Jan 2003 | A1 |
20030010732 | Burke | Jan 2003 | A1 |
20030053014 | Niiyama et al. | Mar 2003 | A1 |
20030055727 | Walker et al. | Mar 2003 | A1 |
20030057167 | Johnson et al. | Mar 2003 | A1 |
20030061973 | Bustos | Apr 2003 | A1 |
20030078691 | Holt et al. | Apr 2003 | A1 |
20030085187 | Johnson et al. | May 2003 | A1 |
20030106867 | Caterinacci | Jun 2003 | A1 |
20030141265 | Jo et al. | Jul 2003 | A1 |
20030150829 | Linden et al. | Aug 2003 | A1 |
20030193481 | Sokolsky | Oct 2003 | A1 |
20030217980 | Johnson et al. | Nov 2003 | A1 |
20030233288 | Sweeney et al. | Dec 2003 | A1 |
20040104239 | Black et al. | Jun 2004 | A1 |
20040118795 | Burke | Jun 2004 | A1 |
20040119681 | Albert et al. | Jun 2004 | A1 |
20040140278 | Mueller et al. | Jul 2004 | A1 |
20040140279 | Mueller et al. | Jul 2004 | A1 |
20040145451 | Failing | Jul 2004 | A1 |
20040178156 | Knorring et al. | Sep 2004 | A1 |
20040245197 | McElvaney | Dec 2004 | A1 |
20040260572 | George et al. | Dec 2004 | A1 |
20050033645 | DuPhily et al. | Feb 2005 | A1 |
20050040123 | Ali | Feb 2005 | A1 |
20050077259 | Menz | Apr 2005 | A1 |
20050086133 | Scherer et al. | Apr 2005 | A1 |
20050092702 | Nagel | May 2005 | A1 |
20050108098 | Syed et al. | May 2005 | A1 |
20050131578 | Weaver | Jun 2005 | A1 |
20050165649 | Mahaffey et al. | Jul 2005 | A1 |
20050168345 | Swafford et al. | Aug 2005 | A1 |
20050190072 | Brown et al. | Sep 2005 | A1 |
20050195081 | Studnicki et al. | Sep 2005 | A1 |
20050228718 | Austin | Oct 2005 | A1 |
20050279722 | Ali | Dec 2005 | A1 |
20060049122 | Mueller et al. | Mar 2006 | A1 |
20060071774 | Brown et al. | Apr 2006 | A1 |
20060102718 | Kajino et al. | May 2006 | A1 |
20060131401 | Do et al. | Jun 2006 | A1 |
20060157431 | Nagelski et al. | Jul 2006 | A1 |
20060163272 | Gamble | Jul 2006 | A1 |
20060163349 | Neugebauer | Jul 2006 | A1 |
20060186064 | Merit et al. | Aug 2006 | A1 |
20060237381 | Lockwood et al. | Oct 2006 | A1 |
20060279527 | Zehner et al. | Dec 2006 | A1 |
20060289637 | Brice et al. | Dec 2006 | A1 |
20070016494 | Brown et al. | Jan 2007 | A1 |
20070024551 | Gelbman | Feb 2007 | A1 |
20070034581 | Weck et al. | Feb 2007 | A1 |
20070095903 | Suenbuel | May 2007 | A1 |
20070159298 | Zegelin et al. | Jul 2007 | A1 |
20070194037 | Close | Aug 2007 | A1 |
20070278164 | Lang et al. | Dec 2007 | A1 |
20070283615 | Mastakis et al. | Dec 2007 | A1 |
20070289344 | Fawcett et al. | Dec 2007 | A1 |
20080074264 | Sharpe et al. | Mar 2008 | A1 |
20080136647 | Brown | Jun 2008 | A1 |
20080142458 | Medcalf | Jun 2008 | A1 |
20080164310 | Dupuy et al. | Jul 2008 | A1 |
20080208695 | Condron | Aug 2008 | A1 |
20080228346 | Lucas et al. | Sep 2008 | A1 |
20080249658 | Walker et al. | Oct 2008 | A1 |
20080250464 | Masucci et al. | Oct 2008 | A1 |
20080255894 | Falls et al. | Oct 2008 | A1 |
20080303637 | Gelbman et al. | Dec 2008 | A1 |
20090020548 | VanDruff | Jan 2009 | A1 |
20090084812 | Kirschner | Apr 2009 | A1 |
20090095695 | Moock et al. | Apr 2009 | A1 |
20090101606 | Olson | Apr 2009 | A1 |
20090133301 | Saxena et al. | May 2009 | A1 |
20090134103 | Saxena et al. | May 2009 | A1 |
20090139945 | Jacobson et al. | Jun 2009 | A1 |
20090157515 | Lafauci et al. | Jun 2009 | A1 |
20090179825 | Enarvi et al. | Jul 2009 | A1 |
20090248198 | Siegel et al. | Oct 2009 | A1 |
20090287992 | Bresolin et al. | Nov 2009 | A1 |
20090313365 | Whitehead | Dec 2009 | A1 |
20090319399 | Resta et al. | Dec 2009 | A1 |
20100017025 | Lockwood et al. | Jan 2010 | A1 |
20100072152 | Kim | Mar 2010 | A1 |
20100100460 | Aronson | Apr 2010 | A1 |
20100106588 | Jones et al. | Apr 2010 | A1 |
20100106662 | Ramaswamy | Apr 2010 | A1 |
20100108624 | Sparkowski | May 2010 | A1 |
20100133214 | Evans | Jun 2010 | A1 |
20100138304 | Boyarsky et al. | Jun 2010 | A1 |
20100169189 | Allison et al. | Jul 2010 | A1 |
20100169190 | Allison et al. | Jul 2010 | A1 |
20100175438 | Sankey | Jul 2010 | A1 |
20100176075 | Nagel et al. | Jul 2010 | A1 |
20100200526 | Barkdoll | Aug 2010 | A1 |
20100205045 | Zhang et al. | Aug 2010 | A1 |
20100206829 | Clements et al. | Aug 2010 | A1 |
20100258513 | Meyer et al. | Oct 2010 | A1 |
20100262554 | Elliott | Oct 2010 | A1 |
20100276383 | Hardy | Nov 2010 | A1 |
20110010271 | Black et al. | Jan 2011 | A1 |
20110017532 | Langford et al. | Jan 2011 | A1 |
20110018685 | Tanaka et al. | Jan 2011 | A1 |
20110022980 | Segal et al. | Jan 2011 | A1 |
20110106624 | Bonner et al. | May 2011 | A1 |
20110106653 | Wein | May 2011 | A1 |
20110128378 | Raji | Jun 2011 | A1 |
20110161146 | Walker et al. | Jun 2011 | A1 |
20110178863 | Daigle | Jul 2011 | A1 |
20110215060 | Niederhuefner | Sep 2011 | A1 |
20110234514 | Gothard | Sep 2011 | A1 |
20110251920 | Watson | Oct 2011 | A1 |
20110304316 | Hachmann et al. | Dec 2011 | A1 |
20120000869 | Hardy | Jan 2012 | A1 |
20120004769 | Hallenbeck et al. | Jan 2012 | A1 |
20120044056 | Byun et al. | Feb 2012 | A1 |
20120120327 | Marx et al. | May 2012 | A1 |
20120147055 | Pallakoff et al. | Jun 2012 | A1 |
20120204458 | Goehring | Aug 2012 | A1 |
20120223943 | Williams et al. | Sep 2012 | A1 |
20120228240 | Gentile et al. | Sep 2012 | A1 |
20120245969 | Campbell | Sep 2012 | A1 |
20120246023 | Starr | Sep 2012 | A1 |
20120273442 | Hardy | Nov 2012 | A1 |
20120280810 | Wheeler | Nov 2012 | A1 |
20120284085 | Walker et al. | Nov 2012 | A1 |
20120284132 | Kim et al. | Nov 2012 | A1 |
20120286937 | Cote et al. | Nov 2012 | A1 |
20120330781 | Borrero | Dec 2012 | A1 |
20130002422 | Wiese et al. | Jan 2013 | A1 |
20130024023 | Siegel et al. | Jan 2013 | A1 |
20130030953 | Marsic | Jan 2013 | A1 |
20130037562 | Close | Feb 2013 | A1 |
20130041752 | Crum | Feb 2013 | A1 |
20130057404 | Thibault | Mar 2013 | A1 |
20130109323 | Ruutu et al. | May 2013 | A1 |
20130132216 | Aihara et al. | May 2013 | A1 |
20130141240 | Valiulis et al. | Jun 2013 | A1 |
20130157569 | Torvmark et al. | Jun 2013 | A1 |
20130210360 | Ljung et al. | Aug 2013 | A1 |
20130214909 | Meijers et al. | Aug 2013 | A1 |
20130226742 | Johnson et al. | Aug 2013 | A1 |
20130235206 | Smith et al. | Sep 2013 | A1 |
20130275261 | Yoked | Oct 2013 | A1 |
20130317903 | Majrani | Nov 2013 | A1 |
20130332271 | Hay | Dec 2013 | A1 |
20140006225 | Bowman et al. | Jan 2014 | A1 |
20140006229 | Birch et al. | Jan 2014 | A1 |
20140043162 | Siciliano et al. | Feb 2014 | A1 |
20140055243 | Kerai | Feb 2014 | A1 |
20140100769 | Wurman et al. | Apr 2014 | A1 |
20140100999 | Mountz et al. | Apr 2014 | A1 |
20140110584 | Campbell | Apr 2014 | A1 |
20140113560 | Graube et al. | Apr 2014 | A1 |
20140139548 | Byers | May 2014 | A1 |
20140145828 | Bassan-Eskenazi et al. | May 2014 | A1 |
20140197953 | Valiulis | Jul 2014 | A1 |
20140201042 | Meyer | Jul 2014 | A1 |
20140210692 | Waters et al. | Jul 2014 | A1 |
20140214195 | Worsley | Jul 2014 | A1 |
20140220883 | Emigh et al. | Aug 2014 | A1 |
20140239061 | Smith et al. | Aug 2014 | A1 |
20140247116 | Davidson | Sep 2014 | A1 |
20140258028 | Bynum et al. | Sep 2014 | A1 |
20140268949 | Kayser | Sep 2014 | A1 |
20140291405 | Harkes | Oct 2014 | A1 |
20140299620 | Swafford, Jr. et al. | Oct 2014 | A1 |
20140299663 | Shah et al. | Oct 2014 | A1 |
20140305891 | Vogler et al. | Oct 2014 | A1 |
20140316561 | Tkachenko et al. | Oct 2014 | A1 |
20140316916 | Hay | Oct 2014 | A1 |
20140352372 | Grant et al. | Dec 2014 | A1 |
20140360953 | Pichel | Dec 2014 | A1 |
20150039477 | O'Neil | Feb 2015 | A1 |
20150088306 | Varrasso | Mar 2015 | A1 |
20150090675 | Vosshernrich | Apr 2015 | A1 |
20150091729 | Phillips et al. | Apr 2015 | A1 |
20150112827 | Davis et al. | Apr 2015 | A1 |
20150186982 | Higgins et al. | Jul 2015 | A1 |
20150356657 | Pas | Dec 2015 | A1 |
20150356666 | Pas et al. | Dec 2015 | A1 |
20150382150 | Ansermet et al. | Dec 2015 | A1 |
20160048798 | Meyer et al. | Feb 2016 | A1 |
20160132822 | Swafford | May 2016 | A1 |
20160132823 | Swafford et al. | May 2016 | A1 |
20160132949 | Adoni et al. | May 2016 | A1 |
20170024756 | Hulth | Jan 2017 | A1 |
20170061525 | McCoy et al. | Mar 2017 | A1 |
20200351474 | Gaudiano Del Bosque | Nov 2020 | A1 |
Number | Date | Country |
---|---|---|
2007233199 | Oct 2007 | AU |
906083 | Apr 1987 | BE |
1008382 | Apr 1996 | BE |
2693874 | Jul 2011 | CA |
2822926 | Feb 2014 | CA |
2822926 | Mar 2018 | CA |
223095 | Aug 1942 | CH |
412251 | Apr 1966 | CH |
1787003 | Jun 2006 | CN |
1906644 | Jan 2007 | CN |
1972228 | May 2007 | CN |
101208718 | Jun 2008 | CN |
101472509 | Jul 2009 | CN |
101507380 | Aug 2009 | CN |
103703476 | Apr 2014 | CN |
107105905 | Aug 2017 | CN |
969003 | Apr 1958 | DE |
1819158 | Oct 1960 | DE |
2002720 | Jul 1971 | DE |
7311113 | Aug 1973 | DE |
2232398 | Jan 1974 | DE |
2825724 | Dec 1979 | DE |
3116145 | Nov 1982 | DE |
8308485 | Sep 1983 | DE |
3211880 | Oct 1983 | DE |
8426651 | Feb 1985 | DE |
8520125 | Jan 1986 | DE |
3628609 | Feb 1988 | DE |
4307082 | Sep 1994 | DE |
19745813 | Apr 1999 | DE |
299026888 | Jul 1999 | DE |
102004037365 | Mar 2006 | DE |
102006061135 | Jun 2008 | DE |
0004921 | Oct 1979 | EP |
0018003 | Oct 1980 | EP |
0048479 | Mar 1982 | EP |
0176209 | Apr 1986 | EP |
0224107 | Jun 1987 | EP |
270016 | Jun 1988 | EP |
298500 | Jan 1989 | EP |
0337340 | Oct 1989 | EP |
0408400 | Jan 1991 | EP |
0454586 | Oct 1991 | EP |
0572119 | Dec 1993 | EP |
0587059 | Mar 1994 | EP |
0806749 | Nov 1997 | EP |
986980 | Mar 2000 | EP |
0779047 | Apr 2000 | EP |
1057164 | Dec 2000 | EP |
1249804 | Oct 2002 | EP |
1356425 | Oct 2003 | EP |
1395152 | Mar 2004 | EP |
1973034 | Sep 2008 | EP |
2309377 | Apr 2011 | EP |
2367101 | Sep 2011 | EP |
2385365 | Oct 1978 | FR |
2526338 | Nov 1983 | FR |
2617385 | Jan 1989 | FR |
2859364 | Mar 2005 | FR |
697994 | Oct 1953 | GB |
740311 | Nov 1955 | GB |
881700 | Nov 1961 | GB |
1082150 | Sep 1967 | GB |
1088654 | Oct 1967 | GB |
2027339 | Aug 1982 | GB |
2180527 | Apr 1987 | GB |
2 232 398 | Dec 1990 | GB |
D2037553 | Jul 1994 | GB |
2281289 | Mar 1995 | GB |
2290077 | Dec 1995 | GB |
2297241 | Jul 1996 | GB |
2283407 | Oct 1997 | GB |
2392667 | Mar 2004 | GB |
2480462 | Nov 2011 | GB |
54168195 | Nov 1979 | JP |
59218113 | Aug 1984 | JP |
62060521 | Mar 1987 | JP |
6329463 | Feb 1988 | JP |
6056224 | Mar 1994 | JP |
6209945 | Jul 1994 | JP |
7257714 | Sep 1994 | JP |
H07-017608 | Jan 1995 | JP |
H11342054 | Dec 1999 | JP |
2007525393 | Sep 2007 | JP |
2007-284238 | Nov 2007 | JP |
2012-058854 | Mar 2012 | JP |
2012-089140 | May 2012 | JP |
10-2005-0066397 | Jun 2005 | KP |
1020040089123 | Oct 2004 | KR |
10-2005-0066397 | Jun 2005 | KR |
1020060123497 | Jun 2008 | KR |
1020090054501 | Dec 2010 | KR |
1020100022890 | Aug 2011 | KR |
1020100041969 | Nov 2011 | KR |
10-1507380 | Apr 2015 | KR |
106617 | Nov 1963 | NL |
2007073334 | Jun 2007 | NO |
2101731 | Jan 1998 | RU |
394537 | Jun 1977 | SE |
1600615 | Oct 1990 | SU |
9115141 | Oct 1991 | WO |
9311449 | Jun 1993 | WO |
0061438 | Oct 2000 | WO |
0071004 | Nov 2000 | WO |
02091885 | Nov 2002 | WO |
03016938 | Feb 2003 | WO |
2003032775 | Apr 2003 | WO |
03039301 | May 2003 | WO |
2004104951 | Dec 2004 | WO |
2005033645 | Apr 2005 | WO |
2005057444 | Jun 2005 | WO |
2006023954 | Mar 2006 | WO |
06133487 | Dec 2006 | WO |
2007024639 | Mar 2007 | WO |
07140800 | Dec 2007 | WO |
2007149967 | Dec 2007 | WO |
10082835 | Jul 2010 | WO |
10137883 | Dec 2010 | WO |
11001024 | Jan 2011 | WO |
2011089452 | Jul 2011 | WO |
2012095825 | Jul 2012 | WO |
2012166613 | Dec 2012 | WO |
14080252 | May 2014 | WO |
2014144631 | Sep 2014 | WO |
Entry |
---|
Apr. 2, 2014—(RU)—Office Action—App 2013109955. |
Sep. 5, 2013—(US)—Office Action—U.S. Appl. No. 12/876,919. |
FFrR Yellow pp. 02003 Product Catalog, “Merchandising Ideas Made Easy for Every Retail Environment!”, Cover p. 9-11, 48-49, 52-58, Back Cover. |
Letter from Maria Comninou of Harness Dickey to Stephanie Knapp dated Nov. 11, 2009. |
Document entitled “Relevant Prior Art for U.S. Appl. No. 10/772,010”. |
Shelf-edge digital price tags invade the South of France http://www.digitalsignagetoday.com/article/196299/Shelf-edge-digital-price-tags-invade-the-South-of-France. |
ESignage http://www.episys.com/page/25/esignage.htm. |
Electronic Shelf-Edge Labels (“Realprice system”) http://www.hitech-LCD.com/ESL.html. |
Segmented Dot Matrix Electronic Shelf Label –SM Model and Segmented Dot Matrix Electronic Narrow Facing Label — MM http://www.ilid.com.au/product-range.php#sm. |
Electronic Shelf-Edge Labels http://www.fujitsu.com/downloads/EU/uk/pdf/industries/retail/retail-solutions-electronic-self-edge-labels.pdf. |
The NZ ESL range from pricer http://www.electronicshelflabelling.co.nz/products/. |
Retailer introduces electronic shelf-edge labelling http://www.conveniencestore.co.uk/news/retailer-introduces-electronic-shelf-edge-labelling/231511.article. |
Revolutionary Shelf Edge Displays from in the UK http://crystal-display.com/digital-signage/shelf-edge-displays/. |
XDS-1068: 10-inch All-in-One Multi-touch Signboard with Power-over-Ethernet http://www.iadea.com/product/xds-1068. |
ZBD Solutions, Shelf Edge Labelling http://www.zbdsolutions.com/solutions/index.html (printed Jan. 29, 2013). |
Vectron, Speedy POS Solutions to make ezi-profits. 15 pages. |
“How physics drives the supermarket industry,” IOP Institute of Physics, Physicsworks. 4 pages. |
John Ross, “Retail technology and the evolving shopper,” Shopper Sciences. 11 pages. |
Altierre Digital Retail, Altierre Corp., “Altierre Unveils E-Paper Product Family For Digital Signs and Price Tags.” 2 pages, http://www.altierre.com/pr_e-paper.html (printed Jan. 31, 2013). |
Suzanne Vita Palazzo, “New life for ESLs?, Advanced capabilities being buill into electronic shelf labels may help overcome retailers' concerns about ROI.”, Grocery Headquarters (www.groceryheadquarters.com), Mar. 2007, pp. 97-100. |
Scott D. Walkins & Megan E. Henriksen of Anderson Economic Group, LLC, “Michigan's Item Pricing Law: The Price Tag for Retailers and Consumers,” Dec. 11, 2010 (http://www.AndersonElectronicGroup.com) 39 pages. |
“Product Range :: I LID—The next generation in electronic shelf labels,” : http://www.ilid.com.au/product-range.php, printed on Mar. 5, 2013, dale of website unknown but prior to the filing of the present matter. |
“Electronic Shelf Label controlling various information in real lime (ESL),” hllp:l/cesl.co.kr/eng/product-introduction/cest-esl.hlml, CEST—Center for Embedded Software Technology, printed on Mar. 5, 2013, dale of website unknown out prior to the filing of the present matter. |
Jun. 24, 2014—(MX)—Office Action—App MX/a/2013/001455—Eng Tran. |
Mar. 3, 2015—(AU) Office Action—App 2011285929. |
Mar. 3, 2015—(AU) Office Action—App 2013205058. |
Apr. 6, 2015—(PCT) International Search Report—App PCT/US14/29124. |
Dec. 14, 2015—(EP) Exam Report—App 11745636.8. |
Apr. 19, 2016—(KR) Office Action—App 10-2015-7027591. |
Apr. 22, 2016—(PCT)—International Search Report—App PCT/US2015/060404. |
Apr. 22, 2016 (PCT) ISR and Written Opinion—App PCT/US2015/060404. |
Jun. 22, 2016—(AU) Search Report—App 2014225837. |
Jun. 28, 2016—(AU) Examination Report—App 2014228923. |
Aug. 18, 2016—(EP) Office Action—App 14716461.0. |
Jun. 10, 2014—(PCT) ISR & Written Opinion—App PCT/US2014/020797. |
Sep. 19, 2016—(PCT) International Search Report—App PCT/US2016/032328. |
Robertson, “Food Packaging: Principles and Practice, Second Edition”, CRC Press, XP055301114, ISBN: 978-0-8493-3775-8, vol. 0, p. 308, dated Sep. 22, 2005. |
George Coulouris et al., “Distributed Systems: Concepts and Design (5th Edition)”, Addison-Wesley, US, XP055261658, ISBN: 978-0-13-214301-1 pp. Ch01-Ch06, Ch09-Ch10, ch13,, Chapters 1, 3 and 19, dated May 7, 2011. |
Oct. 27, 2016—(KR) Final Rejection—App 10-2015-7027591. |
Nov. 18, 2016—(US) Final Office Action—U.S. Appl. No. 14/308,989. |
Jul. 10, 2013—(US) Non-Final Office Action—U.S. Appl. No. 13/194,649. |
Jan. 15, 2014—(US) Final Office Action—U.S. Appl. No. 13/194,649. |
Jan. 3, 2014—(US) Final Office Action—U.S. Appl. No. 12/876,919. |
Mar. 4, 2008—(US) Non-Final Office Action—U.S. Appl. No. 10/772,010. |
Sep. 3, 2008—(US) Final Office Action—U.S. Appl. No. 10/772,010. |
Mar. 9, 2009—(US) Non-Final Office Action—U.S. Appl. No. 10/772,010. |
Aug. 19, 2009—(US) Final Office Action—U.S. Appl. No. 10/772,010. |
Feb. 2, 2010—(US) Non-Final Office Action—U.S. Appl. No. 10/772,010. |
Jun. 2, 2010—(US) Final Office Office Action—U.S. Appl. No. 10/772,010. |
Oct. 7, 2015—(US) Non-Final Office Action—U.S. Appl. No. 14/308,989. |
Jun. 2, 2020—(KR) Office Action—App. No. 10-2020-7002962. |
Jul. 14, 2020—(EP) Office Action—App. No. 17177125.6. |
Jun. 29, 2020—(CN) Third Office Action (w/translation)—App 201580072899.0. |
Jan. 28, 2021—(AU) Office Action—AU 2018336797. |
Dec. 2, 2020—(CN) First Office Action—CN 2018800734745. |
Dec. 10, 2020—(KR) Office Action—App. No. 10-2020-7002962. |
McAndrew, Sean T., et al., “Potential use of real-time data capture and job-tracking technology in the field,” Facilities 2005, 23, pp. 31-46. |
May 20, 2021—(AU) Examination Report—App 2020203256. |
Jan. 5, 2021—(AU) Examination Report—App 2019271906. |
Jan. 14, 2021—(CN) Notice of Re-examination—App 201480024831.0. |
Jan. 27, 2021—(EP) Office Action—EP18783266.2. |
Feb. 10, 2021—(AU) First Examination Report—App 2020203256. |
Nov. 15, 2019—(WO) International Search Report and Written Opinion—PCT/US2019/051724. |
Mar. 26, 2021—(EP) Second Office Action—App. No. 17177125.6. |
Mar. 23, 2021—(WO) IPRP and Written Opinion—App. No. PCT/US2019/051724. |
May 4, 2016—(US) Non-Final Office Action—U.S. Appl. No. 14/308,989. |
Dec. 15, 2016—(US) Final Office Action—U.S. Appl. No. 13/836,680. |
Jun. 2, 2016—(US) Non-Final Office Action—U.S. Appl. No. 13/836,680. |
Sep. 23, 2014—(US) Non-Final Office Action—U.S. Appl. No. 13/836,680. |
Mar. 24, 2015—(US) Non-Final Office Action—U.S. Appl. No. 13/836,680. |
Dec. 14, 2015—(EP) Examination Report—U.S. Appl. No. 11/745,636. |
Mar. 20, 2008—(WO) ISR and Written Opinion—App. No. PCT/US05/02836. |
Jan. 28, 2011—(EP) Supplementary Search Report—App. No. 05712322.6-2221. |
Dec. 6, 2011—(EP) Office Action—App. No. 05712322.6-2221. |
May 25, 2011—(EP) Office Action—App. No. 05712322.6-2221. |
Nov. 24, 2011—(WO) ISR and Written Opinion—App. No. PCT/US2011/046209. |
Feb. 21, 2013—(WO) IPR and Written Opinion—App. No. PCT/US2011/046209. |
Apr. 2, 2014—(RU) Office Action—App. No. 2013109955. |
Sep. 24, 2015—(WO) IPRP and Written Opinion—App. No. PCT/US2014/29124. |
Apr. 6, 2015—(WO) Written Opinion—App. No. PCT/US2014/29124. |
Mar. 1, 2017—(AU) Second Office Action—App. No. 2014228923. |
Aug. 19, 2016—(EP) Extended ESR—App. No. 14723571.7-1903. |
Apr. 6, 2015—(WO) ISR—App. No. PCT/US2014/29124. |
Jun. 19, 2017—(CN) First Office Action and ISR—App. No. 201480026575.9. |
Jun. 7, 2017—(CN) ISR—App. No. 201480026575.9. |
Jul. 18, 2017—(KR) Office Action—App. 10-2015-7029832. |
Sep. 7, 2017—(US)—Final Office Action—U.S. Appl. No. 14/591,421. |
Nov. 7, 2017—(EP) Extended Search Report—App. No. 17177125.6. |
Nov. 7, 2017—(EP)—Communication 94(3) EPC—App 14716461.0. |
Nov. 28, 2017 (US)—Non-Final Office Action—U.S. Appl. No. 14/713,809. |
Feb. 23, 2018—(CN) Second Office Action—App. No. 201480026575.9. |
Mar. 14, 2018—(EP) Communication Pursuant to Article 94(3) EPC—App 15798644.9. |
Apr. 6, 2018—(KR) Office Action—App 10-2017-7015819. |
Jan. 18, 2018—(AU) Examination Report—App 2015346254. |
Apr. 2, 2018—(CN) First Office Action—App 201480024831.0. |
May 30, 2018—(AU) Examination Report—App 2015346254. |
Jul. 26, 2018 (US)—Non-Final Office Action—U.S. Appl. No. 14/939,220. |
Jul. 6, 2018—(CN) Third Office Action—App 201480026575.9. |
FFr Yello pp. 02003 Product Catalog, “Merchandising Ideas Made Easy for Every Retail Environment!”, Cover p. 9-11, 48-49, 52-58, Back Cover. |
Oct. 28, 2018—(KR) Final Rejection—App 10-2017-7015819. |
Dec. 17, 2018—(US) Final Office Action—U.S. Appl. No. 14/591,421. |
Dec. 26, 2018—(KR) Notice of Allowance—App 10-2017-7015819. |
Jan. 11, 2019—(KR) Notice of Allowance—App 10-2015-7027591. |
Jan. 31, 2019—(CN)—Second Office Action—App 201480024831.0. |
Feb. 11, 2019—(KR) Office Action—App 10-2017-736152. |
Mar. 15, 2019—(EP) Extended Europen Search Report and European Search Opinion—App 19153057.5. |
Jan. 10, 2019—(WO) International Search Report and Written Opinion—App. No. PCT/US2018/051775. |
Apr. 22, 2019—(KR) Office Action—App. No. 10-2018-7015060. |
Jun. 14, 2019—(EP) Partial European Search Report—App 19158063.8. |
Jul. 5, 2019—(CN) Office Action—App. No. 201580072899.0. |
Jul. 30, 2019—(EP) Examination Report—App 16744914.9. |
Iddo Genuth, “The Future of Electronic Paper,” Oct. 15, 2007, XP002513292, Down oaded from http://thefutureofthings.com/articles/1000/the-future-of-electornic-paper.html, 7 pages. |
Aug. 28, 2019—(AU) First Examination Report—App 2018241074. |
Aug. 16, 2019—(CN) Third Office Action—App 201480024831.0. |
Nov. 5, 2019—(AU) Second Examination Report—App 2018241074. |
Nov. 27, 2019—(KR) Office Action—App 10-2017-7036152. |
Jan. 7, 2020—(CN) Rejection Decision—App 201480024831.0. |
https://smartshelf.com/retail_solutions.html#led. |
https://www.youtube.com/watch?v=ULucc1ZVBnM&feature=youtu.be. |
Oct. 15, 2020—(EP) Office Action—App 16744914.9. |
Brazilian Patent Office Action for Application No. BR112021004525-2 dated Jun. 20, 2023 (5 pages). |
Chinese Patent Office First Office Action for application 201980074582.9, dated Feb. 7, 2023 (31 pages with translation). |
Number | Date | Country | |
---|---|---|---|
20200065755 A1 | Feb 2020 | US |
Number | Date | Country | |
---|---|---|---|
62622560 | Jan 2018 | US | |
62560498 | Sep 2017 | US | |
62078809 | Nov 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16135151 | Sep 2018 | US |
Child | 16671894 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14939220 | Nov 2015 | US |
Child | 16135151 | US |