This application related to co-pending U.S. patent application Ser. No. 11/464,127 filed Aug. 11, 2006, and hereby incorporated by reference, which is a Continuation-In-Part of U.S. patent application Ser. No. 10/722,954, filed Nov. 26, 2003 (now U.S. Pat. No. 7,167,892), which claims the benefit of U.S. Provisional Application No. 60/429,756, filed Nov. 27, 2002 and U.S. Provisional Application No. 60/480,626, filed Jun. 23, 2003, and which is a Continuation-In-Part of U.S. patent application Ser. No. 09/971,170, filed Oct. 4, 2001 (now U.S. Pat. No. 7,181,501), which is a Continuation-in-Part of U.S. patent application Ser. No. 09/267,254, filed Mar. 12, 1999 (now U.S. Pat. No. 6,457,038), which claims the benefit of U.S. Provisional Application No. 60/078,645, filed Mar. 19, 1998 and U.S. Provisional Application No. 60/099,434, filed Sep. 8, 1998.
The present invention relates in general to the field of monitoring remote field assets and, more particularly, the monitoring of the performance of field assets.
Machine to machine (M2M) technology refers generally to the ability of machines, devices, and assets, particularly those that are distributed or remote, to exchange information with people and/or with a corporate management system. Although a precise definition of M2M is difficult to formulate, M2M generally encompasses the use of telemetry via networks including, but not limited to, public wireless networks.
Historically, telemetry systems were limited to applications for conglomerates and other well financed organizations. Large oil and gas companies and electric utilities, through the use of extensive customer built dedicated data networks, were among the first private organizations to use telemetry widely. More recently, however, the cost of access to public wireless data networks has been dropping while the capabilities of these networks has been increasing thus making M2M concepts feasible for a much larger audience.
The M2M systems described herein generally include remotely located machines or devices referred to as field assets. Although field assets may encompass any variety of specific types of machines (oil rigs, cellular phone system base stations, ATM machines, and weather monitors), the specific embodiments described herein are in the field of vending machines. Vending machines are unmanned, electromechanical devices that dispense products including consumable products such as soft drinks and snack foods in exchange for cash or other form of payment. Vending machines are generally deployed as remotely located field assets by a company that manages a plurality of such devices.
In the field of vending machines, the traditional extent of automation consisted primarily of the ability retrieve “snapshots” of inventory data from a vending machine using a wired, hand held device and a specialized, industry standard, data exchange (DEX) protocol and interconnect. DEX is a communication protocol (DEX) for the electronic retrieval of machine-level transactions via data polling. While DEX has served its purpose well for a considerable period of time, DEX is not capable of analyzing vending machine sales beyond the most superficial level. Nor is DEX capable of providing information that could be used to manage a vending machine from a maintenance perspective. Moreover, a DEX polling event effectively takes a vending machine off line, even if for only a short duration. This limitation prevents it from serving as a real time transaction monitoring protocol.
More recently, the Multi Drop Bus/Internal Communication Protocol (MDB/ICP or, more simply MDB) vending machine technology has evolved. MDB defines a bus interface and standard for electronically controlled vending machines. Unlike DEX, MDB provides a control mechanism and standard for the various peripheral devices typically encountered in a vending machine. Moreover, MDB supports a level of time stamping that enables insight into information that is potentially valuable to a vending machine company. Despite the opportunities for expanded functionality and data insight offered by MDB, conventional MDB-compliant vending machines tend to utilize MDB merely as an interconnect between a VMC and one or more peripherals and, possibly, a source of DC power.
Nevertheless, some efforts have been devoted to adding functionality to conventional vending machines. For example, U.S. Pat. No. 7,167,892, referred to above, describes a processor-based audit device having access to the MDB bus and to the VMC via a DEX port. Using this audit device, a vending machine can greatly improve the amount and quality of information concerning sales. If, for example, sales of a particular vending machine vary considerably from day to day and even within a day, conventional DEX polling, which might take place on a weekly basis, for example, will not be able to identify these variations and the inability to do so could result in lost sales opportunities.
Using such an audit device, a vending machine can retrieve and store a plurality of DEX downloads together with information from which time stamps can be derived for each DEX download. While the ability to place DEX data in a timing context represents an advance a vending machine management, it would be still further desirable to continue to extend the functionality of vending machines to encompass information that is outside the scope of DEX or to capture and enhance traditional DEX data without performing a DEX download.
As another example, U.S. patent application Ser. No. 11/464,127, referred to above, describes a packet capture agent (also referred to therein as a snoop agent or an MDB Offload Engine (MOE)) to capture MDB packets. Capturing packets directly from the MDB serves a variety of purposes including, as examples, enabling feedback of field asset performance and customer behavior in real time, without requiring a DEX polling event, uncoupling field asset monitoring from the DEX standard, and facilitating the gathering of quantifiable, time-based consumer behavior data.
In accordance with the teachings of the present disclosure, disadvantages and problems associated with the monitoring of field assets may be substantially reduced or eliminated.
In accordance with one embodiment of the present disclosure, a method for monitoring the performance of a field asset is provided. Packets transmitted on a shared bus located in a field asset may be captured. The captured packets may be analyzed to determine one or more operational parameters associated with one or more peripheral devices coupled to the shared bus. The one or more operational parameters may be analyzed to determine an operational efficiency of the field asset.
In accordance with another embodiment of the present disclosure, a field asset may include a machine controller configured to function as a master of a shared bus, one or more peripheral devices communicatively coupled to the bus, a snoop agent, and an audit agent. The machine controller may transmit packets to the peripheral devices via the shared bus. The snoop agent may be configured to capture packets transmitted on the shared bus. The audit agent may be configured to analyze the captured packets to determine one or more operational parameters associated with the one or more peripheral devices and analyze the one or more operational parameters to determine an operational efficiency of the field asset.
In accordance with a further embodiment of the present disclosure, system for monitoring the performance of a field asset may include a field asset. The field asset may include a machine controller configured to function as a master of a shared bus, one or more peripheral devices communicatively coupled to the bus, a snoop agent, and an audit module. The machine controller may transmit packets to the peripheral devices via the shared bus. The snoop agent may be configured to capture packets transmitted on the shared bus. The audit agent may be configured to analyze the captured packets to determine one or more operational parameters associated with the one or more peripheral devices and analyze the one or more operational parameters to determine an operational efficiency of the field asset.
Other technical advantages will be apparent to those of ordinary skill in the art in view of the following specification, claims, and drawings.
A more complete and thorough understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:
Preferred embodiments of the invention and its advantages are best understood by reference to
The term “wire-line transmissions” may be used to refer to all types of electromagnetic communications over wires, cables, or other types of conduits. Examples of such conduits include, but are not limited to, metal wires and cables made of copper or aluminum, fiber-optic lines, and cables constructed of other metals or composite materials satisfactory for carrying electromagnetic signals. Wire-line transmissions may be conducted in accordance with teachings of the present disclosure over electrical power lines, electrical power distribution systems, building electrical wiring, conventional telephone lines, Ethernet cabling (10 baseT, 100 baseT, etc.), coaxial cables, T-1 lines, T-3 lines, ISDN lines, ADSL, etc.
The term “wireless transmissions” may be used to refer to all types of electromagnetic communications which do not require a wire, cable, or other types of conduits. Examples of wireless transmissions which may be used include, but are not limited to, personal area networks (PAN) (e.g., BLUETOOTH), local area networks (LAN), wide area networks (WAN), narrowband personal communications services (PCS), broadband PCS, circuit switched cellular, cellular digital packet data (CDPD), radio frequencies, such as the 800 MHz, 900 MHz, 1.9 GHz and 2.4 GHz bands, infra-red and laser.
Examples of wireless transmissions for use in local area networks (LAN) include, but are not limited to, radio frequencies, especially the 900 MHZ and 2.4 GHz bands, for example IEEE 802.11 and BLUETOOTH, as well as infrared, and laser. Examples of wireless transmissions for use in wide area networks (WAN) include, but are not limited to, narrowband personal communications services (nPCS), personal communication services (PCS such as CDMA, TMDA, GSM) circuit switched cellular, and cellular digital packet data (CDPD), etc.
The term “data processing system” may be used to refer to any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an data processing system may be a personal computer, a PDA, a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. A data processing system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of a data processing system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. A data processing system may also include one or more buses operable to transmit communication between the various hardware components.
The term “computer-readable media” may be used to refer to any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), a PCMCIA card, flash memory, direct access storage (e.g., a hard disk drive or floppy disk), sequential access storage (e.g., a tape disk drive), compact disk, CD-ROM, DVD, and/or any suitable selection of volatile and/or non-volatile memory and/or storage.
In some embodiments, field assets 102 and 103 may comprise one or more vending machines in which transactions likely include the sale of consumer goods stocked in the vending machine. Vending machines are ubiquitous machines historically used as an unmanned source of perishable and nonperishable consumer products including canned and bottled drink products, snack foods, and so forth.
In the embodiment depicted in
Field asset 102-1 is depicted as being capable of communicating with a hand held device 130 via a network 140 or “directly” with transaction processing server 110 via network 120. As depicted in
Transaction server 110 may be implemented as a set of one or more server class computers operable to process many transactions. Transaction server 110 may include, as an example, a database management application (e.g., Oracle, DB2, etc.)
A data processing system 170 is depicted in
Each of network 120, 140 and 160, may be any network and/or fabric configured to couple one or more field assets 102 and/or 103, hand held devices 130, transaction servers 110, and/or computing devices (e.g., computer 170) in accordance with the present disclosure. Each of network 120, 140 and 160 may be implemented as, or may be a part of, a storage area network (SAN), personal area network (PAN), local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wireless local area network (WLAN), a virtual private network (VPN), an intranet, the Internet or any other appropriate architecture or system that facilitates the communication of signals, data and/or messages (generally referred to as data), or any combination thereof. Each of network 120, 140 and 160 may transmit data using any storage and/or communication protocol, including without limitation, Fibre Channel, Frame Relay, Asynchronous Transfer Mode (ATM), Internet protocol (IP), other packet-based protocol, small computer system interface (SCSI), Internet SCSI (iSCSI), advanced technology attachment (ATA), serial ATA (SATA), advanced technology attachment packet interface (ATAPI), serial storage architecture (SSA), integrated drive electronics (IDE), and/or any combination thereof. Each of network 120, 140 and 160 and their various respective components may be implemented using hardware, software, or any combination thereof.
In certain embodiments of system 100, network 120 may be implemented as a wireless network using any of a variety of long-range wireless transmission technologies, e.g., cellular technology. Such embodiments may include the well-known use of multiple base stations positioned in specified locations to communicate wireless signals across a wide geographic area. Similarly, in certain embodiments of system 100, network 160 may be implemented as (or part of) the Internet and/or an intranet.
In certain embodiments of system 100, network 140 may be implemented as a wireless network using any of a variety of short range wireless transmission technologies including, without limitation, Bluetooth and WiFi (e.g., IEEE 802.11b, IEEE 802.11g, and their derivatives). In such embodiments, an operator may convey hand held device 130 to a location that is in close proximity to a field asset 102. Field asset 102 and hand held device 130 may establish a local wireless signal enabling communication between the two. After establishing a local wireless communication channel, field asset 102 and hand held device 130 may exchange data or information. Field asset 102 may, as an example, transmit sales transaction information to hand held device 130. Hand held device 130 may then convey the information it has received from field asset 102 to transaction server 110 via network 120. Alternatively, transfer of information from field asset 102-1 to transaction server 110 could be achieved by transferring the data from field asset 102-1 to hand held device 130 using network 140, transporting hand held device 130 to a location in proximity to transaction server 110, and transmitting the information in hand held device 130 to interaction server 110 via transfer (e.g., a wireless or wireline transfer). As another alternative, information may be passed from field asset 102-1 to hand held device 130 and/or from hand held device 130 to transaction server 110 using wireline transmissions, e.g., a cable or other wired connection, possibly to enhance the security of confidential information.
The type of information conveyed or otherwise exchanged between field assets 102 and interaction server 110 varies depending upon the manner in which and the purpose for which field asset 102 is implemented, but the information most likely includes information about transactions that occur or have occurred using field assets 102. In embodiments where field assets 102 and 103 include a vending machine, the transaction information referred to may include, as examples, information about when a transaction occurs and other transaction details, for example, what product or combination of products were purchased, what consumer or customer purchased the product (if known, e.g., by reading a name from a magnetic strip of a credit card), the dollar amount of the purchase, the amount of time required to complete the purchase, the manner of payment, the operational status of vending machine components (e.g., correct change events, compressor failure, bill validator failure, coin mechanism failure, card reader failure, mechanical jams, etc.), and other information that may be useful to vending machine operators and/or the providers of goods sold through field assets 102.
As depicted in
As described in greater detail with respect to
As described in greater detail with respect to
As shown in
MDB 211 may be compliant with the Multi-Drop Bus/Internal Communication Protocol (the MDB protocol) maintained by the National Automatic Marketing Association (NAMA). The MDB protocol is an interface standard that allows the various components of a vending machine to communicate to the VMC. The MDB protocol determines the way in which the VMC learns what coins are accepted by coin mechanism 214, what bills are accepted by bill validator 216, and how much credit is available through card reader 212. It is a way for the VMC to communicate to coin mechanism 214 how much change to pay out or to communicate to card reader 212 how much credit to return to a swiped credit card and/or other cashless payment medium.
Unlike many shared bus protocols, the MDB protocol may define VMC 210 as the one and only master of the MDB and all other peripherals as slaves. VMC 210 may address packets to any of the peripheral devices, but peripheral devices cannot communicate with each other and only transmit packets to VMC 210 in response to receiving a packet from VMC 210. Also, as suggested previously, MDB is a polling-based protocol. A significant percentage of MDB traffic may consist of polling packets issued by VMC 210 and acknowledge packets from the peripheral devices. In most shared bus architectures, e.g., Ethernet and PCI, devices can act as masters or slaves and polling is not an inherent feature of the architecture.
EFA 200, as its name suggests, includes application extensions that enhance the features of field asset 102. In conjunction with VMC 210, EFA 200 may include an audit agent 302 suitable for retrieving DEX data 220 from VMC 210. In addition, EFA 200 may include an MDB snoop agent 301 enabled to capture and buffer or otherwise store MDB packets.
The ability to capture MDB packets enables a variety of different applications. MDB packet traffic may be captured and analyzed to achieve time-based and DEX-independent auditing capabilities. As another example, MDB packet traffic may also be used to monitor system health. Moreover, by combining MDB packet capture capabilities in conjunction with EFA 200 as described below, field asset 102 may facilitate the collection and analysis of data communicated within field asset 102. When further implemented in conjunction with networking and communication capabilities, field asset 102 may represent a highly intelligent component of an automated network of field assets.
EFA 200, as depicted in
As described in greater detail in U.S. patent application Ser. No. 11/464,127, referenced above, MDB snoop agent 301 may include hardware, software, and/or firmware support to capture MDB packets as they appear on MDB 211 and provide them to an audit engine or application for further study (e.g., at audit agent 302, transaction server 110, and/or data processing system 170) and may be implemented, at least in part, as a daughter board that attaches to EFA 200 and may also include a microcontroller and other circuitry required to implement packet capture in an MDB environment.
According to one embodiment, method 350 preferably begins at step 352. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of system 100. As such, the preferred initialization point for method 350 and the order of the steps 352-366 comprising method 350 may depend on the implementation chosen.
At step 352, MDB snoop agent 301 may capture MDB information from MDB 211. The captured MDB information may include packets of data communicated between VMC 210 and peripherals coupled to MDB 211, such as card reader 212, coin mechanism 214, and bill validator 216, for example. In certain embodiments, some or all of the information captured by MDB snoop agent 301 may be indicative of an operational state of peripherals coupled to MDB 211. For example, a portion of the captured MDB information may indicate whether each of card reader 212, coin mechanism 214, and bill validator 216 are fully operational, or whether any of such peripherals has failed. At step 354 the captured MDB information may be communicated from MDB snoop agent 301 to audit agent 302.
At step 356, VMC 210 may capture DEX data 220. The captured DEX information may include data indicative of an operational state of components of field asset 102 not coupled to MDB 211. For example, a portion of captured DEX data 220 may indicate whether inventory items of field asset 102 are in stock, whether or not field asset 102 is operating in an exact change mode (e.g., if field asset 102 is depleted of sufficient coins of particular denominations, field asset 102 may not be able to give change for certain purchases), whether a vending mechanism of field asset 102 is jammed or obstructed, whether a compressor operating to chill inventory is operation, as well as any other parameters. At step 358, the captured DEX data 220 may be communicated from VMC 210 to audit agent 302.
At step 360, audit agent 302 may analyze captured MDB information to determine one or more operational parameters associated with peripherals coupled to MDB 211. For example, audit agent 302 may analyze the captured MDB information to determine periods of time in which each of card reader 212, coin mechanism 214, and bill validator 216 are fully operational, as depicted in
At step 362, audit agent 302 may analyze captured DEX data 220 to determine one or more operational parameters associated with other components of field asset 102. For example, audit agent 302 may analyze captured DEX data 220 to determine periods of time in which all inventory items of field asset 102 were in stock. To illustrate, audit agent 302 may analyze captured DEX data 220 to determine that in a given week, all items were in stock from Monday morning through Wednesday morning, and again from Thursday morning through Saturday evening, as shown in
At step 364, audit agent 302 may analyze the various operational parameters to determine the overall operational efficiency of field asset 102. For example, referring again to
At step 366, field asset 102 may communicate, via one more of networks 120, 140, and 160, the operational parameters, periods of full operational efficiency, overall operational efficiency and/or other data to management application 175, where such data can be reviewed and/or further analyzed by management application 175 and or a person using data processing system 170. For example, in one embodiment, all of a portion of
Although
Method 350 may be implemented using system 100 or any other system operable to implement method 350. In certain embodiments, method 350 may be implemented partially or fully in software embodied in tangible computer readable media.
Although audit agent 302 is described above as analyzing MDB information and DEX data 220 to determine one or more operational parameters associated with peripherals and other components of field asset 102, and also described above as analyzing operational parameters to determine periods of full operational efficiency and overall operational efficiency, it is understood that any other component of system 100, referred to generally as an “audit module,” may perform one or more of such analyses and determinations (e.g., transaction server 110, data processing system 170, and/or management application 175 may be used as an audit module). For example, in certain embodiments, “raw” MDB information and/or DEX data 220 may be communicated from field asset 102 to data processing system 170, and management application 175 (and/or another component of data processing system 170) may then analyze MDB information and/or analyze DEX data 220 to determine one or more operational parameters associated with peripherals and other components of field asset 102. In the same or alternative embodiments, management application 175 (and/or another component of data processing system 170) may also analyze operational parameters to determine periods of full operational efficiency and/or overall operational efficiency of field asset 102.
For the sake of simplicity, only particular examples of operational parameters for peripherals and components of field asset 102 were discussed above (e.g., items in stock, not in exact change mode, card reader 212 operational, coin mechanism 214 operational, and bill validator 216 operational). However, is it understood that greater or fewer operational parameters may be utilized in accordance with the present disclosure. For example, in some embodiments, the determination of periods of full operational efficiency and/or the determination of overall operational efficiency may be determined independent of any periods that field asset 102 is not in exact change mode. As another example, captured MDB information and/or DEX data may analyzed to determine operational parameters other than those discussed above (e.g., mechanical jams in a vending mechanism, compressor failure, etc.) and such operational parameters may also be analyzed to determine periods of full operational efficiency and/or determine the overall operational efficiency of field asset 102.
Also, for the sake of simplicity, operational parameters, periods of operational efficiency, and overall operational efficiency in relation to field asset 102 were discussed with reference to
Utilizing the methods and systems disclosed herein, one may be able to track the operational efficiency of one or more field assets 102 and 103, as well as individual components thereof. By analyzing such operational efficiency (manually and/or automatically), one may be able to establish effective service, maintenance and repair schedules for each field asset 102 and 103, so as to increase the operational efficiency of such field asset, and potentially increase revenues realized from such field asset.
Although the present disclosure has been described with respect to specific preferred embodiments thereof, various changes and modifications may be suggested to one skilled in the art and it is intended that the present invention encompass such changes and modifications fall within the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
3784737 | Waehner | Jan 1974 | A |
4369442 | Werth et al. | Jan 1983 | A |
4412292 | Sedam et al. | Oct 1983 | A |
4454670 | Bachmann et al. | Jun 1984 | A |
4553211 | Kawasaki et al. | Nov 1985 | A |
4611205 | Eglise | Sep 1986 | A |
4661862 | Thompson | Apr 1987 | A |
4677565 | Ogaki et al. | Jun 1987 | A |
4766548 | Cedrone et al. | Aug 1988 | A |
4850009 | Zook et al. | Jul 1989 | A |
4926996 | Eglise et al. | May 1990 | A |
4954697 | Kokubun et al. | Sep 1990 | A |
5029098 | Levasseur | Jul 1991 | A |
5050769 | Levasseur | Sep 1991 | A |
5077582 | Kravette et al. | Dec 1991 | A |
5090589 | Brandes et al. | Feb 1992 | A |
5091713 | Horne et al. | Feb 1992 | A |
5117407 | Vogel | May 1992 | A |
5184179 | Tarr et al. | Feb 1993 | A |
5207784 | Schwartzendruber | May 1993 | A |
5239480 | Huegel | Aug 1993 | A |
5255819 | Peckels | Oct 1993 | A |
5282127 | Mii | Jan 1994 | A |
5323155 | Iyer et al. | Jun 1994 | A |
5337253 | Berkovsky et al. | Aug 1994 | A |
5339250 | Durbin | Aug 1994 | A |
5371348 | Kumar et al. | Dec 1994 | A |
5386360 | Wilson et al. | Jan 1995 | A |
5400246 | Wilson et al. | Mar 1995 | A |
5418945 | Carter et al. | May 1995 | A |
5445295 | Brown | Aug 1995 | A |
5505349 | Peckels | Apr 1996 | A |
5507411 | Peckels | Apr 1996 | A |
5561604 | Buckley et al. | Oct 1996 | A |
5608643 | Wichter et al. | Mar 1997 | A |
5620079 | Molbak | Apr 1997 | A |
5649308 | Andrews | Jul 1997 | A |
5671362 | Cowe et al. | Sep 1997 | A |
5701252 | Facchin et al. | Dec 1997 | A |
5708223 | Wyss | Jan 1998 | A |
5769269 | Peters | Jun 1998 | A |
5787149 | Yousefi et al. | Jul 1998 | A |
5790431 | Ahrens et al. | Aug 1998 | A |
5794144 | Comer et al. | Aug 1998 | A |
5805997 | Farris | Sep 1998 | A |
5815652 | Ote et al. | Sep 1998 | A |
5818603 | Motoyama | Oct 1998 | A |
5822216 | Satchell, Jr. et al. | Oct 1998 | A |
5841866 | Bruwer et al. | Nov 1998 | A |
5842597 | Kraus et al. | Dec 1998 | A |
5844808 | Konsmo et al. | Dec 1998 | A |
5850187 | Carrender et al. | Dec 1998 | A |
5860362 | Smith | Jan 1999 | A |
5862517 | Honey et al. | Jan 1999 | A |
5867688 | Simmon et al. | Feb 1999 | A |
5892758 | Argyroudis | Apr 1999 | A |
5898904 | Wang | Apr 1999 | A |
5905442 | Mosebrook et al. | May 1999 | A |
5905882 | Sakagami et al. | May 1999 | A |
5907491 | Canada et al. | May 1999 | A |
5909183 | Borgstahl et al. | Jun 1999 | A |
5915207 | Dao et al. | Jun 1999 | A |
5918213 | Bernard et al. | Jun 1999 | A |
5924081 | Ostendorf et al. | Jul 1999 | A |
5930770 | Edgar | Jul 1999 | A |
5930771 | Stapp | Jul 1999 | A |
5941363 | Partyka et al. | Aug 1999 | A |
5943042 | Siio | Aug 1999 | A |
5949779 | Mostafa et al. | Sep 1999 | A |
5950630 | Portwood et al. | Sep 1999 | A |
5956487 | Venkatraman et al. | Sep 1999 | A |
5957262 | Molbak et al. | Sep 1999 | A |
5959536 | Chambers et al. | Sep 1999 | A |
5959869 | Miller et al. | Sep 1999 | A |
5979757 | Tracy et al. | Nov 1999 | A |
5982325 | Thornton et al. | Nov 1999 | A |
5982652 | Simonelli et al. | Nov 1999 | A |
5986219 | Carroll et al. | Nov 1999 | A |
5991749 | Morrill, Jr. | Nov 1999 | A |
5997170 | Brodbeck | Dec 1999 | A |
6003070 | Frantz | Dec 1999 | A |
6005850 | Moura et al. | Dec 1999 | A |
6012041 | Brewer et al. | Jan 2000 | A |
6021324 | Sizer, II et al. | Feb 2000 | A |
6021437 | Chen et al. | Feb 2000 | A |
6029143 | Mosher et al. | Feb 2000 | A |
6032202 | Lea et al. | Feb 2000 | A |
6038491 | McGarry et al. | Mar 2000 | A |
6052667 | Walker et al. | Apr 2000 | A |
6052750 | Lea | Apr 2000 | A |
6056194 | Kolls | May 2000 | A |
6057758 | Dempsey et al. | May 2000 | A |
6061668 | Sharrow | May 2000 | A |
6068305 | Myers et al. | May 2000 | A |
6070070 | Ladue | May 2000 | A |
6072521 | Harrison et al. | Jun 2000 | A |
6084528 | Beach et al. | Jul 2000 | A |
6085888 | Tedesco et al. | Jul 2000 | A |
6108700 | Maccabee et al. | Aug 2000 | A |
6109524 | Kanoh et al. | Aug 2000 | A |
6119053 | Taylor et al. | Sep 2000 | A |
6119100 | Walker et al. | Sep 2000 | A |
6124800 | Beard et al. | Sep 2000 | A |
6131399 | Hall | Oct 2000 | A |
6151582 | Huang et al. | Nov 2000 | A |
6161059 | Tedesco et al. | Dec 2000 | A |
6163811 | Porter | Dec 2000 | A |
6181981 | Varga et al. | Jan 2001 | B1 |
6185545 | Resnick et al. | Feb 2001 | B1 |
6199753 | Tracy et al. | Mar 2001 | B1 |
6230150 | Walker et al. | May 2001 | B1 |
6272395 | Brodbeck | Aug 2001 | B1 |
6289453 | Walker et al. | Sep 2001 | B1 |
6304895 | Schneider et al. | Oct 2001 | B1 |
6317649 | Tedesco et al. | Nov 2001 | B1 |
6324520 | Walker et al. | Nov 2001 | B1 |
6338149 | Ciccone, Jr. et al. | Jan 2002 | B1 |
6339731 | Morris et al. | Jan 2002 | B1 |
6341271 | Salvo et al. | Jan 2002 | B1 |
6356794 | Perin, Jr. et al. | Mar 2002 | B1 |
6385772 | Courtney | May 2002 | B1 |
6397247 | Shirakawa et al. | May 2002 | B1 |
6427912 | Levasseur | Aug 2002 | B1 |
6434534 | Walker et al. | Aug 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6442532 | Kawan | Aug 2002 | B1 |
6446123 | Ballantine et al. | Sep 2002 | B1 |
6457038 | Defosse | Sep 2002 | B1 |
6462644 | Howell et al. | Oct 2002 | B1 |
6467685 | Teicher | Oct 2002 | B1 |
6502131 | Vaid et al. | Dec 2002 | B1 |
6505095 | Kolls | Jan 2003 | B1 |
6525644 | Stillwagon | Feb 2003 | B1 |
6550672 | Tracy et al. | Apr 2003 | B1 |
6553336 | Johnson et al. | Apr 2003 | B1 |
6581986 | Roatis et al. | Jun 2003 | B2 |
6584309 | Whigham | Jun 2003 | B1 |
6585622 | Shum et al. | Jul 2003 | B1 |
6604086 | Kolls | Aug 2003 | B1 |
6604087 | Kolls | Aug 2003 | B1 |
6606602 | Kolls | Aug 2003 | B1 |
6609113 | O'Leary et al. | Aug 2003 | B1 |
6615623 | Ormerod | Sep 2003 | B1 |
6695166 | Long | Feb 2004 | B2 |
6704714 | O'Leary et al. | Mar 2004 | B1 |
6712266 | Bartley et al. | Mar 2004 | B2 |
6714977 | Fowler et al. | Mar 2004 | B1 |
6735630 | Gelvin et al. | May 2004 | B1 |
6738811 | Liang | May 2004 | B1 |
6748296 | Banerjee et al. | Jun 2004 | B2 |
6751562 | Blackett et al. | Jun 2004 | B1 |
6754558 | Preston et al. | Jun 2004 | B2 |
6772048 | Leibu et al. | Aug 2004 | B1 |
6816813 | Tan et al. | Nov 2004 | B2 |
6826607 | Gelvin et al. | Nov 2004 | B1 |
6832251 | Gelvin et al. | Dec 2004 | B1 |
6837436 | Swartz et al. | Jan 2005 | B2 |
6844813 | Hardman | Jan 2005 | B2 |
6850252 | Hoffberg | Feb 2005 | B1 |
6859831 | Gelvin et al. | Feb 2005 | B1 |
6867685 | Stillwagon | Mar 2005 | B1 |
6876988 | Helsper et al. | Apr 2005 | B2 |
6900720 | Denison et al. | May 2005 | B2 |
6901347 | Murray et al. | May 2005 | B1 |
6925335 | May et al. | Aug 2005 | B2 |
6934673 | Alvarez et al. | Aug 2005 | B2 |
6959265 | Candela et al. | Oct 2005 | B1 |
6973475 | Kenyon et al. | Dec 2005 | B2 |
6996502 | De La Cruz et al. | Feb 2006 | B2 |
7017085 | Braun | Mar 2006 | B2 |
7076329 | Kolls | Jul 2006 | B1 |
7131575 | Kolls | Nov 2006 | B1 |
7894938 | Arora et al. | Feb 2011 | B1 |
20010002210 | Petite | May 2001 | A1 |
20010034566 | Offer | Oct 2001 | A1 |
20010042121 | Defosse et al. | Nov 2001 | A1 |
20010047410 | Defosse | Nov 2001 | A1 |
20010054083 | Defosse | Dec 2001 | A1 |
20020016829 | Defosse | Feb 2002 | A1 |
20020024420 | Ayala et al. | Feb 2002 | A1 |
20020032470 | Linberg | Mar 2002 | A1 |
20020077724 | Paulucci et al. | Jun 2002 | A1 |
20020082665 | Haller et al. | Jun 2002 | A1 |
20020107610 | Kaehler et al. | Aug 2002 | A1 |
20020169539 | Menard et al. | Nov 2002 | A1 |
20020194387 | Defosse | Dec 2002 | A1 |
20030003865 | Defosse et al. | Jan 2003 | A1 |
20030013482 | Brankovic | Jan 2003 | A1 |
20030050841 | Preston et al. | Mar 2003 | A1 |
20030061094 | Banerjee et al. | Mar 2003 | A1 |
20030074106 | Butler | Apr 2003 | A1 |
20030088474 | Hoffman et al. | May 2003 | A1 |
20030097474 | Defosse et al. | May 2003 | A1 |
20030101257 | Godwin | May 2003 | A1 |
20030101262 | Godwin | May 2003 | A1 |
20030128101 | Long | Jul 2003 | A1 |
20030204391 | May et al. | Oct 2003 | A1 |
20040133653 | Defosse et al. | Jul 2004 | A1 |
20040207509 | Mlynarczyk et al. | Oct 2004 | A1 |
20050043011 | Murray et al. | Feb 2005 | A1 |
20050131577 | Ota et al. | Jun 2005 | A1 |
20050161953 | Roatis et al. | Jul 2005 | A1 |
20050179544 | Sutton et al. | Aug 2005 | A1 |
20060106490 | Howell et al. | May 2006 | A1 |
20060195567 | Mody et al. | Aug 2006 | A1 |
20060219777 | Arora et al. | Oct 2006 | A1 |
20070096867 | Denison et al. | May 2007 | A1 |
20070100696 | Illingworth | May 2007 | A1 |
20080140515 | Godwin | Jun 2008 | A1 |
20090094081 | Wittern et al. | Apr 2009 | A1 |
20090112672 | Fl mig et al. | Apr 2009 | A1 |
20100312611 | Henderson et al. | Dec 2010 | A1 |
Number | Date | Country |
---|---|---|
41 40 450 | Jun 1993 | DE |
0 564 736 | Oct 1993 | EP |
0 602 787 | Oct 1993 | EP |
0 817 138 | Jan 1998 | EP |
0 999 529 | May 2000 | EP |
1096408 | May 2001 | EP |
2 744 545 | Feb 1996 | FR |
2 755776 | May 1998 | FR |
04253294 | Sep 1992 | JP |
6296335 | Oct 1994 | JP |
9198172 | Jul 1997 | JP |
10105802 | Apr 1998 | JP |
WO 8907807 | Aug 1989 | WO |
WO 9504333 | Feb 1995 | WO |
WO 9505609 | Feb 1995 | WO |
WO 9709667 | Mar 1997 | WO |
WO 9845779 | Oct 1998 | WO |
WO 9923620 | May 1999 | WO |
WO 9927465 | Jun 1999 | WO |
WO 9936751 | Jul 1999 | WO |
WO 9948065 | Sep 1999 | WO |
WO 0004475 | Jan 2000 | WO |
WO 0004476 | Jan 2000 | WO |
WO 0031701 | Jun 2000 | WO |
WO 0219281 | Mar 2002 | WO |
Entry |
---|
Skywire Provides Details of Wireless ‘VendView’ System; Vending Times, Sep. 1994. |
Wireless Communications Forum; vol. III, No. 1 pp. 25-30, Apr. 1995. |
Left high and dry? Sold-out machine sends for Cokes; Nashville Banner, Aug. 16, 1995. |
Leitch, Carolyn, “Coke machines signal when it's time for a refill”; The Globe & Mail, Toronto, Ontario, Aug. 30, 1995. |
Meet the Smart Coke Machine; The Sacramento Bee Business Technology; Wednesday, Aug. 30, 1995. |
Skywire allows vendor tracking of pop stock and sales details; RCR, vol. 14, No. 17, Sep. 4, 1995. |
International Search Report for PCT/US99/05983 7 pages, Aug. 13, 1999. |
American Power Conversion Internet Article, “Lightning Advisor”, at internet ,<http://lightning.apcc.com>, May 10, 2000. |
American Products Internet Article, “Product Information”, at internet, <http://www.apc.com>, May 10, 2000. |
NetBotz Internet Article, “Welcome to Netbotz” at internet <http:www.netbotz.com>, May 10, 2000. |
BT redcare Telemetry Vending Interface Unit (VIU), Antronics Ltd Case Study, <http:www.antronic.co.uk/portfolio/viu>, 4 pgs, 2001. |
International Search Report PCT/US01/16749, Dec. 20, 2001. |
International Search Report PCT/US01/15522, May 16, 2002. |
International Search Report PCT US 01/41640, Aug. 21, 2002. |
International Search Report PCT/US 01/31381, Nov. 7, 2002. |
International Preliminary Examination Report PCT/US01/31381 (3 pages), May 12, 2003. |
NAMA White Paper: Cashless Vending, The National Automatic Merchandising Association (34 pages), 2004. |
International Search Report PCT/US 03/37776, May 17, 2004. |
What is an iButton?, Maxim/Dallas, http://www.maxim-ic.com/products/ibutton/ibuttons/, 3 pages, Dec. 29, 2005. |
Office Action dated Apr. 1, 2010 in connection with U.S. Appl. No. 12/035,074. |
Office Action dated Nov. 15, 2010 in connection with U.S. Appl. No. 11/299,607. |
Office Action dated Mar. 29, 2013 in connection with U.S. Appl. No. 12/035,074, filed Feb. 21, 2008. |
Extended European Search Report dated Nov. 29, 2012 in connection with European Patent Application No. 09712876.3, 6 pages. |
Number | Date | Country | |
---|---|---|---|
20090113038 A1 | Apr 2009 | US |