US20140143074A1 - Interactive interface effectuated vending - Google Patents
Interactive interface effectuated vending Download PDFInfo
- Publication number
- US20140143074A1 US20140143074A1 US14/071,021 US201314071021A US2014143074A1 US 20140143074 A1 US20140143074 A1 US 20140143074A1 US 201314071021 A US201314071021 A US 201314071021A US 2014143074 A1 US2014143074 A1 US 2014143074A1
- Authority
- US
- United States
- Prior art keywords
- data
- mdb
- vend
- interface
- vending
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F7/00—Methods or arrangements for processing data by operating upon the order or content of the data handled
- G06F7/06—Arrangements for sorting, selecting, merging, or comparing data on individual record carriers
- G06F7/08—Sorting, i.e. grouping record carriers in numerical or other ordered sequence according to the classification of at least some of the information they carry
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/18—Payment architectures involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F9/00—Details other than those peculiar to special kinds or types of apparatus
- G07F9/02—Devices for alarm or indication, e.g. when empty; Advertising arrangements in coin-freed apparatus
- G07F9/026—Devices for alarm or indication, e.g. when empty; Advertising arrangements in coin-freed apparatus for alarm, monitoring and auditing in vending machines or means for indication, e.g. when empty
Abstract
Description
- This application is a continuation application that claims priority of a U.S. continuation in part application Ser. No. 10/153,478, inventor H. Brock Kolls, entitled INTERACTIVE INTERFACE EFFECTUATED VENDING, filed May 22, 2002; which is a U.S. non-provisional continuation in part application that claims priority of a U.S. non-provisional application. Ser. No. 10/138,385, inventor H. Brock Kolls, entitled MDB TRANSACTION STRING EFFECTUATED CASHLESS VENDING, filed May 3, 2002; which is a continuation in part application that claims priority of a U.S. non-provisional application. Ser. No. 10/121,081, inventor H. Brock Kolls, entitled CASHLESS VENDING TRANSACTION MANAGEMENT BY A VEND ASSIST MODE OF OPERATION, filed Apr. 12, 2002; which is a continuation in part application that claims priority of a U.S. non-provisional application. Ser. No. 10/118,123, inventor H. Brock Kolls, entitled SYSTEM AND METHOD FOR LOCALLY AUTHORIZING CASHLESS TRANSACTIONS AT POINT OF SALE, filed Apr. 8, 2002; which is a continuation in part application that claims priority of a U.S. non-provisional application. Ser. No. 10/100,680, inventor H. Brock Kolls, entitled CASHLESS TRANSACTION PAYMENT MODULE, filed. Mar. 18, 2002; which is a continuation in part application the claims priority of a U.S. non-provisional application. Ser. No. 10/083,032, inventor H. Brock Kolls, entitled SEMICONDUCTOR WITH SELECTIVE INTEGRATED CASHLESS, CONNECTIVITY, AND DIGITAL CONTENT PRESENTATION CAPABILITIES, filed Feb. 26, 2002; which is a continuation in part application that claims priority of a provisional application. Ser. No. 60/278,599 inventor H. Brock Kolls, entitled VENDING MACHINE AUDIT AND CREDIT CONTROLLER, SYSTEM AND METHOD, filed Mar. 26, 2001.
- In addition, this U.S. non-provisional application is a continuation in part application that claims priority of a U.S. non-provisional application. Ser. No. 10/051,594, inventor H. Brock Kolls, entitled A WIRELESS SYSTEM FOR 5 COMMUNICATING CASHLESS VENDING TRANSACTION DATA AND VENDING MACHINE AUDIT DATA TO REMOTE LOCATIONS, filed Jan. 18, 2002; which is a continuation in part application that claims priority of a U.S. non-provisional application Ser. No. 09/888,797, inventor H. Brock Kolls, entitled. A METHOD OF PROCESSING
CASHLESS PAYMENT TRANSACTIONS 10 WORLDWIDE, filed Jun. 25, 2001; which is a continuation in part application that claims priority of a U.S. non-provisional application. Ser. No. 09/884,755, inventor H. Brock Kolls, entitled SYSTEM FOR PROVIDING REMOTE AUDIT, CASHLESS PAYMENT, AND INTERACTIVE TRANSACTION CAPABILITIES IN A VENDING MACHINE, filed Jun. 19, 2001, now U.S. Pat. No. 6,505,095 B1. - The present invention relates to a system and method which effectuates an interactive interface and protocol for interfacing a payment module (system 500) to and data communicating with a computing platform (computing platform 802), wherein the computing platform can elect to control by way of the interactive interface and protocol a vending transaction cycle or alternatively elect to monitor the payment module by way of the interactive interface and protocol allowing the payment module to control a vending transaction cycle.
- In addition, the present invention relates to a system and method that is scalable and configurable to include interfaces for vending equipment monitoring and control capabilities, interfaces for a card reader device and other identification devices to obtain payment identification data to be used for payment of goods and or services vended, an interactive interface and protocol for interconnecting the system to a computing platform, and support for a plurality of communication options that include wired, point-to-point wireless, and wireless networking including LAN/WAN/WCDMA/CDMA/CDPD/2G/2.5G and 3G solutions.
- Furthermore, the present invention also relates to a system and method of effectuating remote monitoring of vending equipment by gathering DEX and MDB audit data from the vending equipment, and data communicating with a plurality of remote locations, wherein a plurality of remote locations can be a plurality of global network based data processing resources.
- Recent trends in the vending industry have been to offer higher priced items out of vending equipment at traditionally unattended vending locations. Higher priced item offers can result from the desire to vend larger portions of products such as the twenty-ounce soda bottle verse the twelve-ounce soda can. In other cases the higher priced items can be items that until recently my not have been considered for sale through vending equipment such as phone cards, disposable cameras, and frozen food entrees to name a few.
- The vending industry's desire to vend higher priced items has given rise to issues related to currency and inventory. For example, with the shift to vending twenty-ounce bottles, many of the vending sales now involve more than one currency note, as an example two one-dollar bills to make a purchase. As a result the bill validator can fill to capacity with currency notes before all the items in the vending equipment have been sold. With a bill acceptor filled to capacity the vending equipment may not be able to transact another vending sale and place itself out-of-service. As a result vending operators can typically find themselves restocking vending equipment that still has product available for sale but because of the inability to take additional currency notes the vending equipment could not sell the inventory.
- In addition, with many beverage type vending machines the shift from the twelve-ounce can to the twenty-ounce bottle can create coin mechanism issues. In moving to the larger size beverage the average price can move from typically slightly less than a dollar where little change was required when a dollar note was used for payment to slightly more than a dollar where the better part of a dollar in change can be required when two one-dollar notes are used for payment for a vend. Resultant from this price move not only do the bill validators fill to capacity faster and stop working sooner, but the coin mechanism can be required to supply a customer with more change on each vend depleting a coin mechanism coin supply faster. Once the coin change supply is depleted the vending machine may be rendered out-of-service.
- In addition to the new burden on bill acceptors and coin mechanisms resultant from the sale of higher priced items other issues related to the vending of higher priced items can arise. One such issue can be that a customer may not have enough money on-hand to effectuate the vending purchase. In the case of phone cards, cameras, and frozen foods vend prices may range from several dollars to forty dollars, fifty dollars, or more. In many cases the customer may have the desire to purchase the high priced item but simply lacks the amount of currency required to effectuate the purchase. In other cases the customer may be reluctant to trust the vend worthiness of the vending equipment with what the customer considers to be a significant amount of money.
- As the proliferation of higher priced vend items continues to become more pervasive in today's society the vending industry has become increasingly concerned about tracking inventory and monitoring the operational status of the vending equipment remotely. It is considered a general belief within the vending industry that remotely monitoring vending equipment can optimize a route driver's daily activity and reduce operational costs associated with the sales and delivery of products to the vending equipment.
- To date auditing devices have been designed to be placed inside the vending equipment or held in the hand of a route collector for the purpose of gathering vending equipment inventory and operational data which can later be downloaded to a computer. These devices however have been costly to manufacture, install, maintain, and operate. As such the total cost of the technology verse the savings on the operational costs associated with the sales and delivery of products to date have not made for a sound or compelling business model. As a result the vending industry has been slow to adopt ‘audit’ only technology.
- The cost benefit model of the ‘audit’ hardware may not be the only issue hampering the proliferation of ‘audit’ only device. Data communication costs, the costs of getting the data back to a central computer center, can be a significant limitation on getting vending equipment remotely ‘audit’ capable or as it is commonly referred to in the vending industry as ‘online’.
- Such telecommunication costs can include the cost of running a telephone line to the vending equipment. In many cases the vending equipment may be in a location not conducive to having a dedicated phone line installed proximate to the vending equipment, such as in a concrete basement, on a golf course, in a shopping mall, or on a university campus to name a few. Once a telephone line is installed there can be monthly service charges incurred from the telecommunication company providing the service. These costs alone can in effect nullify the savings of having the vending equipment ‘online’.
- To avoid the high expense of running dedicated telephone lines to vending equipment the vending industry has pursued wireless wide area network (WAN) options. Implementing a wireless WAN has typically involved purchasing additional wireless hardware, and trying to integrate the wireless hardware with the ‘audit’ hardware. If the integration effort was successfully the hardware, service, and maintenance costs of the combined solution were typically significantly increased compared to the ‘audit’ device only solution costs. In addition, the service and maintenance required for the combined wireless system is typically different then the non-wireless ‘audit’ device only solution.
- In addition to the increased hardware costs for the wireless WAN solution, the wireless communication service fees paid to the wireless network provider can be more then those fees charged by the communication companies providing telephone line service. A technology solution and service fee structure that could effectively nullify the anticipated sales and delivery savings from having the vending equipment ‘online’.
- In part a long felt need exists for a solution related to a cost effective system and method for remotely auditing vending equipment, and for providing additional payment options at the point of sale for goods and services vended from vending equipment. This coupled with the industry's shortcoming in these areas and other areas, some of which were mentioned above give rise to the present invention.
- The present invention relates to a system and method which effectuates an interactive interface and protocol for interfacing a payment module (system 500) to and data communicating with a computing platform (computing platform 802), wherein the computing platform can elect to control by way of the interactive interface and protocol a vending transaction cycle or alternatively elect to monitor the payment module by way of the interactive interface and protocol allowing the payment module to control a vending transaction cycle.
- The present invention also relates to a
system 500 implementing a MDB TRANSACTION STRING in memory to effectuate cashless vending. The MDB TRANSACTION STRING allows thesystem 500 and orcomputing platform 802 to manage cashless vending by monitoring data fields within the MDB TRANSACTION STRING. - The MDB TRANSACTION STRING is constructed and managed in
system 500 memory. The MDB TRANSACTION STRING includes at least one of the following data fields: a VEND STATE field, a MAX VEND SALE field, a SALE PRICE field, a COLUMN field, or a VEND FLAG field. - In operation, the
system 500 obtains data from a vending machine and constructs and manages an MDB TRANSACTION STRING in memory. Utilization of the MDB TRANSACTION STRING occurs when thesystem 500 application code and or acomputing platform 802 interconnected with thesystem 500 reads the MDB TRANSACTION STRING to make certain determinations to effectuate cashless vending. - The present invention relates to a cashless transaction processing system implementing a VEND ASSIST mode of operation to effectuate a cashless vending transaction. The VEND ASSIST mode allows a
computing platform 802 to oversee, control, and authorize by way of asystem 500 the vend selection and sale price of a user selected vend item prior to fulfilling the user's request. - The cashless transaction processing system includes a
system 500 and acomputing platform 802. Thesystem 500 initiates a vending session when certain commands from aninterconnected computing platform 802 are received or in response to presentation, by a user, of valid payment identification data. -
Computing platform 802 communicates a VEND APPROVE or VEND DENY in response tosystem 500 initiating a REQUEST VEND APPROVE. A vend cycle is then initiated or preempted as appropriate. - The present invention also relates to a system and method that is scalable and configurable to include interfaces for vending equipment monitoring and control capabilities, interfaces for a card reader device and other identification devices as payment for items vended, an interactive interface and protocol for interconnecting the system to a computing platform, and support for a plurality of communication options that include wired, point-to-point wireless, and wireless networking including LAN (local area network), WAN (wide area network), GSM, WCDMA (wideband code division multiple access), CDMA-TDMA. (code-time division multiple access), CDPD, 2G-2.5G (second generation networks), 3G (third generation networks), and other wired and wireless network solutions. In an exemplary embodiment the system can be embodied in a semiconductor package or module package.
- The present invention also relates to a system and method of effectuating a payment device for accepting card ID data, authorizing the validity of the card ID data, facilitating a vending transaction, settling the transaction to effect payment for the vended goods and services, gathering DEX and MDB audit data from the vending equipment, and data communicating with a plurality of remote locations, where a remote location can be a global network based data processing resource.
- The present invention also relates to a system having a plurality of configurable communication options for data communicating to a plurality of remote locations. Such communication options include local area network connection, telephone line, wireless point-to-point where the system data communicates wirelessly to a local transceiver base unit which has access to a telephone line thereby give the system wireless access to a telephone line, and wireless network data communication access, wherein a data modem connects the system to a WAN for data communication access to a plurality of remote locations.
- The present invention also relates to a system and method for implementing an MDB protocol gateway for the purpose of supporting a plurality of peripheral devices each of which may be implementing a different version of MDB protocol then the vending equipment's vending machine controller (VMC).
- The present invention also relates to a system and method for authorizing and settling card transactions with a processing bureau where the authorization process can be performed by the system locally eliminating the need for data communication with a remote processing bureau, and for processing international card transactions from a single country, wherein international currency conversion processing fees are minimized.
- The present invention also relates to a store and forward data network system and method, wherein data gathered at a central server from a plurality of remote systems installed in a plurality of vending equipment is converted as required and made available to a plurality of other servers for the purpose of using the data to manage a vending business and or supplying data to a backend management system.
- The present invention also relates to the
system 500 being packaged in semiconductor or module creating a single chip orsingle module system 500 solution. The single chip orsingle module system 500 solution can be referred to assemiconductor 500. The functionality ofsemiconductor 500 can include at least one of the following: cashless payment functionality, network connectivity functionality, or digital content presentation functionality. - The present invention is best understood from the following detailed description when read in connection with the accompanying drawings. Included in the drawings are the following Figures:
-
FIG. 1A-1B there is shown a vendingmachine interface unit 100; -
FIG. 2A-2B there is shown a transceiver andmodem base unit 200; -
FIG. 3A there is shown a front view of a card reader assembly; -
FIG. 3B there is shown a left side view of a card reader assembly; -
FIG. 3C there is shown a right side view of a printer assembly; -
FIG. 3D there is shown a front view of a printer assembly; -
FIG. 3E there is shown a right side view of a card reader assembly and a right side view of a printer assembly being aligned for assembly together; -
FIG. 3F there is shown a right side view of the assembled card reader and printer assembly; -
FIG. 3G there is shown a front view of a payment module; -
FIG. 3H there is shown a left side view of a payment module; -
FIG. 31 there is shown a front view of a payment module with receipt printer slot; -
FIG. 3J there is shown a left side view of a payment module with display and communications board included; -
FIG. 3K there is shown a right side view of the payment module assembly and a right side view of a printer assembly being aligned for assembly together; -
FIG. 3L there is shown an external surface mountable payment module assembly; -
FIGS. 3M-3N and 3P there is shown a plurality of data processing devices embodiments; -
FIG. 4 there is shown a vending machine, vending machine interface unit, card reader and printer assembly, and transceiver and modem base unit; -
FIG. 5 there is shown an audit-credit-interactive system 500; -
FIG. 6A there is shown card reader anduser interface system 600; -
FIG. 6B there is shown a card reader anduser interface system 600 data communication routing switch. -
FIG. 7 there is shown a transceiver and modembase unit system 700 and a plurality of remote locations; -
FIG. 8 there is shown an audit-credit-interactive system 500 interfaced to computing platform; -
FIG. 9A there is shown a vending machine MDB interface with a plurality of peripheral devices; -
FIG. 9B there is shown an audit-credit-interactive system 500 interfacing to a vending machine MDB bus and interfacing to a plurality of peripheral devices by way of asystem 500 mimic MDB bus; -
FIG. 9C there is shown an audit-credit-interactive system 500 with card reader and audit functionality embodiment interfacing to a vending machine MDB bus and interfacing to a plurality of peripheral devices by way of asystem 500 mimic MDB bus; -
FIG. 9D there is shown a MDB TRANSACTION STRING withsystem 500 and vending equipment interface; -
FIG. 10A-10B there is shown asystem 500 semiconductor package, and asystem 500 module package; -
FIG. 10C-10D there is shown an audit-credit-interactive system 500 embodied in a semiconductor package; -
FIG. 11 there is shown an MDB initialization tuning routine 1100; -
FIG. 12A-12B there is shown a vending machine interface unit (VIU) 100 withsystem 500 and transceiver and modembase unit system 700 wireless protocoldata communication routine 1200; -
FIG. 13 there is shown a local transaction authorization routine 1300; -
FIG. 14 there is shown an international transaction authorization andsettlement routine 1400; -
FIG. 15 there is shown a data communication transaction message parsing routine 1500; -
FIG. 16A-16B there is shown a determination oftransaction completion routine 1600; -
FIG. 17 there is shown a data communication sweeping, processing, and data forwarding routine 1700; -
FIG. 18A-18B there is shown a mimic MDBinterface port routine 1800; -
FIG. 19A-19B there is shown a local authorizationdatabase management routine 1900; -
FIG. 20 there is shown a transceiver and modembase unit system 700 wireless protocoldata communication routine 2000; -
FIG. 21 there is shown a MDB TRANSACTION STRING updating routine 2100; -
FIG. 22A-B there is shown asystem 500 initiatedvending session routine 2200; -
FIG. 23A there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a hardware reset or is powered-up routine 2300; -
FIG. 23B there is shown button press string messaging when asystem 500 clears button flags and initiates button status polling routine 2400; -
FIG. 23C there is shownsystem 500 remote display messaging routine 2500; -
FIG. 23D there is shownsystem 500 remote printing routine 2600; -
FIG. 23E there is shown. MDB TRANSACTION STRING messaging when asystem 500 initiates a cashless vend while in the VEND ASSIST mode ‘ON’ routine 2700; -
FIG. 23F there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a cashless vend while in the VEND ASSIST mode ‘OFF’ routine 2800; -
FIG. 23G there is shown a computing platform andsystem 500 exchange to effectuate a VEND ASSIST transaction whensystem 500 is selectively interconnected with vending equipment or interconnected with a bill acceptor interface routine 2900; -
FIG. 23H there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a cashless vend while in the VEND ACTIVE mode ‘OFF’ routine 3000; -
FIG. 231 there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a cashless vend while in the VEND ACTIVE mode ‘ON’ routine 3100; -
FIG. 23J there is shown a computing platform andsystem 500 exchange to capture MDB bus messages routine 3200; and -
FIG. 23K there is shown a computing platform andsystem 500 exchange to capture DEX bus messages routine 3300. - A cashless transaction processing system can include a
system 500 and a plurality of data processing resources external tosystem 500. Such plurality of data processing resources can be global network based data processing resources. - In an exemplary embodiment a cashless transaction processing system accepts a plurality of payment identification data presented by a user, wherein the plurality of payment identification data presented by the user is intended to be utilized to effectuate payment for goods and services vended from vending equipment. The payment identification means can be locally authorized at the
system 500 or remotely authorized at a remote data processing resource. Locally authorizing user presented payment identification data can include utilizing locally stored databases and other authorization criteria or rules to validate or approve the user to vend goods and service from the associated vending equipment and subsequently pay for such items vended upon completion of the vending transaction. A payment module can be referred to as asystem 500, an audit-credit-interactive device,VIU 100, asemiconductor 500, ormodule 500. The terms payment module, audit-credit-interactive,VIU 100,semiconductor 500, andmodule 500 can be referred to as asystem 500. - Referring to
FIGS. 1A and IB there is shown a vending machine interface unit (VIU) 100.FIG. 1A shows anantenna 124 mounted perpendicular to the enclosures main body.FIG. 1B shows theantenna 124 mounted parallel to the enclosure main body. In an exemplary embodiment,antenna 124 is included in embodiments making use of thewireless VIII 100 connectivity and excluded in embodiments not requiringwireless VIU 100 connectivity. - The
VIU 100 is a control system that interfaces to a plurality of different kinds of vending machines by way of a plurality of different interface ports. One such interface port can be the NATIONAL AUTOMATED MERCHANDISING ASSOCIATION (NAMA) vending industry MULTI-DROP-BUS (MDB) interface. Other MDB interfaces can include derivative MDB bus specifications, where a derivative MDB bus specification can be one that supports less than the entire NAMA standard, or augments the NAMA standard with additional protocol commands and or features. A second such interface port can be the EUROPEAN VENDING ASSOCIATION'S (EVA) vending industry DATA EXCHANGE INTERFACE (DEX) interface. Additional interface ports include serial and pulse style bill validators, and coin mechanism interfaces. - Vending machine types suitable for interconnection to and operation with the
VIU 100 include vending beverage and snack machines, value adding equipment, and dispensing equipment that operates in connection with or makes available a MDB bus interface, or DEX interface, or a bill acceptor interface, or a coin mechanism interface. Such vending machines include for example and not limitation those manufactured by or for COKE-A-COLA, PEPSI, MARS, VENDO, ROYAL, DIXIE NARCO, GPL, CRANE NATIONAL, AUTOMATED PRODUCTS, CAVALIER, MARCONI or other similar vending machines. Such value adding equipment and dispensing equipment can include for example and not limitation those manufactured by or for ACT, XCP, MARS, SCHLUMBERGIL DAYNL, DEBITEK, GILBARCO, MARCONI, COPICO, PREPAID EXPRESS, or other similar value adding equipment and dispensing equipment. - For purposes of disclosure the term vending machine, value adding machine, and value dispensing machine can be referred to as a vending machine, vending equipment, and or vender. Other vending machine can include beverage style vending machines, snack style vending machines, specialty style vending machines, copiers, fax machines, personal computers (PC), data ports, office equipment, and or other types of vending, retail, office products, or business center types of equipment. Specialty style vending machines include for example and not limitation ice cream vending machines, amusement and arcade games, amusement ride games commonly found in store fronts and shopping malls, fresh produce machines, French fry vending machines, coffee machines, novelty product vending machines, consumer goods style vending machines, and or services type vending machine (such as name tag making, card making, polishing machines, and other service types of vending machines).
- Audit-credit-
interactive system 500 electronics are included within theVIU 100. For purposes of disclosure asystem 500 can be referred to as a vending machine interface unit,VIU 100, or audit-credit-interactive system 500. Many of the electrical interfaces, ports, and connectors shown inFIGS. 1A and IB are actually electrical connections to the audit-credit-interactive system 500 (system 500). The vending machine interface unit (VIU) 100 includes aninteractive interface port 102. Theinteractive interface port 102 provides an electrical connection to theinteractive interface 532. In an exemplary embodiment theinteractive interface port 102 enables other computing platforms to interface to and operational work with the vendingmachine interface unit 100. A computing platform is a microprocessor based system and can include the card readerinterface processor board 312, the card reader anduser interface system 600, or personal computer (PC) based systems. In addition a computing platform can include INTEL, MOTOROLA, MICROCHIP, AMD, UBICOM, ZILOG, IBM brand or other similar microprocessor based systems. A computing platform can operate on a plurality of operating systems including, assembler based, proprietary systems, MICROSOFT, LINUX, QNX., WIND RIVER, J9, BLACK DOWN, and other JAVA VIRTUAL MACHINE (JVM) based or other similar or suitable operating system. -
VIU 100 also includesauxiliary interface port exemplary embodiment Ports printer interface 532, andexternal modem interface 528 respectively. ThePorts ports auxiliary interface port 104 can be used for interfacing to a serial style printer andport 106 can be used to interface to external communication equipment such as data modem, CDMA modems, CDPD modem, wireless transceivers, wireless systems, or other types of communication devices. In an exemplary embodiment an AES wireless transceiver or other private radio network can be used to provide data communication to and from theVIU 100 as well as serve as a repeater to receive and re-transmit data communication to and fromother VIU 100 types of devices in the geographic area. - The
VIU 100 includes a MULTI-BUS-DROP (MDB)interface port 108, and a DATA EXCHANGE INTERFACE (DEX) 112.MDB port 108 and theDEX port 112 provide electrical connections to theMDB interface 518, and theDEX interface 520 respectively. The electrical characteristics and operation of theMDB port 108 are detailed in the NATIONAL AUTOMATED MERCHANDISING ASSOCIATIONS industry specification entitled MDB/ICP INTERFACE PROTOCOL version 1.0 and version 2.0. The electrical characteristics and operation of theDEX port 112 are detailed in the EUROPEAN VENDING ASSOCIATIONS EVA-DTS specification version 4.0. and 5.0.MDB interface 518,DEX interface 520, bill andcoin interface 506,mimic MDB interface 516, and office products interface 534 can be referred to as peripheral device interfaces. - The MDB interfaces allow the
VIU 100 by way of theMDB interface 518 andMDB port 108, to be original equipment manufactured (OEM) into or retrofitted into vending, valuing, and dispensing equipment that provide an MDB bus interface. Furthermore, theVIU 100 by way of theDEX interface 520 and theDEX port 112, can be original equipment manufactured (OEM) into or retrofitted into vending, valuing, and dispensing equipment that provide a DEX interface. -
VIU 100 includes cardreader interface ports card reader ports card reader interface 526. Card reader interface ports interface to industry standard bit strobe, and serial style track I, 2, and 3 card readers. Such card readers include for example and not limitation those manufactured for or by XICO, NEURON, MAGTEK, as well as compatible card readers manufactured by other companies. - The
VIU 100 also includes anRJ11 jack 116. The RJ11 jack provides electrical connections to themodem 522. In an exemplary embodiment the RJ11 jack 16 interconnects theVIU 100 to a telecommunication line, wherein data communication can occur between theVIU 100 and a plurality of remote hosts networks and locations. -
VIU 100 also includes a general-purpose input-output interface 118. The general-purpose input-output interface provides electrical connections to the bill andcoin interface 506. In an exemplary embodiment theVIU 100 can be interconnected with vending, valuing, and dispensing equipment by way of the host equipment's bill acceptor or coin interface port. This allows theVIU 100 by way of the bill andcoin interface 506 andinterface 118 to be original equipment manufactured (OEM) into or retrofitted to vending, valuing, and dispensing equipment that utilize a serial or pulse style bill acceptor, or a coin mechanism interface. Serial and pulse style bill acceptors include for example and not limitation those manufactured for or by MARS, COINCO, CONLUX, ARDAK, or other similar bill acceptor and manufacturers of bill acceptors. - The
VIU 100 includes aservice button 120 and aground terminal 122. The service button provides one of a plurality of electrical connections to the keypad andbutton inputs 510. Theground terminal 122 provides, as may be required, electrical connection to theVIU 100 enclosure. -
Antenna 124 can pass through theVIU 100 enclosure or be mounted to theVIU 100 enclosure. Theantenna 124 provides an antenna electrical connection to thetransceiver 524,data modem 514, or optionally an antenna electrical connection to an external modem interconnected withauxiliary interface port 106. - Referring to
FIGS. 2A and 2B there is shown a transceiver andmodem base unit 200. Transceiver andmodem base unit 200 includestransceiver unit 700 built in. Thetransceiver unit 200 withtransceiver unit 700 data communicates wirelessly with theVIU 100 and by way of a modem data communicates with a remote location. In an exemplary embodiment theVIU 100 withsystem 500 andtransceiver unit 200 withtransceiver unit 700 form a wireless data link, which has access to a modem for data communicating with a remote location. In this regard the reliance on having a telecommunication line in proximity to theVIU 100 or more generally in proximity to the vending equipment theVIU 100 is installed in is greatly reduced. - A remote location can be an Internet based resource, or Internet based data communication. Internet based connections and resources can be referred to as a global network based data processing resource. For purposes of disclosure a remote location can be referred to as an Internet connection, or a global network based data processing resource. A global network based data processing resource is a remote location.
- The
transceiver unit 200 has incorporated into it asystem 700 control system.FIG. 2 shows atelecommunication access port 202 in the side on the transceiver unit 15 200. Thetelecommunication access port 202 provides access by way of a plurality of electrical connections to themodem 704. Atelecommunication access port 202 can be an RJ11 style, or similar telecommunication connector. - Attached to the
transceiver unit 200 is anantenna 716. Theantenna 716 provides an antenna electrical connection to thetransceiver 708. Theantenna 716 can be an antenna manufactured by the ANTENNA FACTOR, or other similar or suitable antenna. - An indicator lamp is also viewable through an
indicator port 204 in thetransceiver unit 200 enclosure. An indicator lamp can be part of thetransceiver system 700. Such an indicator lamp being viewable throughindicator port 204 can be utilized to inform a user of correct operation of thetransceiver unit 700. - The
transceiver system 700 located inside thetransceiver unit 200 enclosure can obtain power for operation from an electrical connection by way ofAC connection 208. In an exemplary embodiment theAC connection 208 can be plugged into a standard 115VAC wall outlet. - Referring to
FIGS. 3A and 3B there is shown a card reader assembly.FIG. 3A shows a front view of the card reader assembly.FIG. 3B shows a left side view of the card reader assembly. In an exemplary embodiment the card reader assembly can be installed in a vending machine. A user having access to the front of the card reader assembly can insert cards, view display information, use a push button to provide system input and if equipped with a printer assembly obtain a receipt, coupon, or other print information dispensed to the user. - A
faceplate 302 is shown fastened to asupport bracket 318. Thefaceplate 302 is sized to fit the industry standard bill validator opening, which can be found on most brands and models of vending equipment. Thefaceplate 302 has a plurality of holes to allow fastening of the card reader assembly into the vending equipment. -
Faceplate 302 also has apaper exit slot 304 to allowreceipt printer 328 to dispense a printed receipt to a user of the system.Faceplate 302 also has adisplay slot 306 which allowsdisplay 606 mounted on the cardreader interface board 312 to be viewable from its mounting location behind the front surface offaceplate 302.Faceplate 302 also contains a plurality of threaded studs for mounting the card readerinterface processor board 312. - In addition,
faceplate 302 can be fastened to abracket 318.Bracket 318 has a plurality of threadedinserts 320 for fastening acard reader 310 to the card reader assembly. Thebracket 318 also has a threadedinsert 316 located in the rear of thebracket 318. Threadedinsert 316 can receivethumbscrew 334 in order to facilitate the fastening of theprinter assembly bracket 330 to the card reader assembly. - A
push button switch 308 can be fastened to thefaceplate 302 and electrically connected to the cardreader interface board 312 by way ofcable assembly 336. In addition,card reader 310 can be electrically connected to the cardreader interface board 312 by way ofcable assembly 314. - Referring to
FIGS. 3C and 3D there is shown a printer assembly.FIG. 3C shows a right side view of the printer assembly.FIG. 3D shows the front view of the printer assembly. In an exemplary embodiment the printer assembly can be slid onto the card reader assembly (seeFIG. 3F ) and secured to the card reader assembly by way of thethumbscrew 334. A card reader assembly having been equipped with a printer assembly can now print receipts, coupons and other print information for a user of the system. - At the top of
printer bracket 330 there is a cutout for receiving apaper holder rod 324. Thepaper holder rod 324 is typically inserted through a roll of paper, such aspaper roll 322.Printer bracket 330 also has a plurality of mounting holes to secure the printer themechanism 328 to theprinter bracket 330.Printer bracket 330 has a threadedthumbscrew 334 secured to thebracket 330. - The
printer mechanism 328 has apaper advance knob 326. Thepaper advance knob 326 can be used to position the paper. - Referring to
FIG. 3E there is shown a right side view of a card reader assembly and a right side view of a printer assembly being aligned for assembly together. In an exemplary embodiment a user of the card reader assembly can choose to add the ability to print receipts, coupons, and other print information by sliding the printer assembly onto the card reader assembly and making the appropriate electrical connections. Furthermore, the printer assembly can be securely fastened to the card reader assembly by way ofthumbscrew 334. - Referring to
FIG. 3F there is shown a right side view of the assembled card reader and printer assembly. - Referring to
FIGS. 3G and 3H there is shown a payment module (system 500). The payment module can be organized to provide scaled functionality. Ingeneral system 500 can be broken into modules of functionality and then combined as required by the application. In an exemplary embodiment a base level payment module may only implement the portion ofsystem 500 dedicated to the functionality of accepting a form of payment, interfacing to a vending machine, and interfacing to an external computing platform. A base level payment module may also make use of an LED display such asLEDs overall system 500 design. - Referring to
FIGS. 3G-3H there is shown a payment module assembly. In an exemplary embodiment the payment module assembly can be installed in a vending machine's dollar bill validator slot. In another exemplary embodimentFIG. 3L shows the payment module in an enclosure mountable on the outside surface of the vending machine. In this regard the dollar bill validator slot is not occupied and left available for other purposes. A user having access to the front of the payment module assembly can among other things insert cards, view transaction status information via the three LED display (340, 342, 344), and use apush button 308 to provide system input. Afaceplate 302 is shown fastened to asupport bracket 318. Thefaceplate 302 is sized to fit the industry standard bill validator opening, which can be found on most brands and models of vending equipment. Thefaceplate 302 has a plurality of holes to allow fastening of the card reader assembly into the vending equipment. Agraphical instruction overlay 356 can be attached to thefaceplate 302.Faceplate 302 also contains a plurality of threadedstuds 346 for mounting the card reader LCD display board (not shown). An LED displayassembly comprising LED - An
interface connection 348 on thepayment module board 350 provides an electrical interface to external data processing equipment and or other computing platforms. Such external data processing equipment and or computing equipment can include communication devices, display devices, telemetry devices, VIU's, interactive media devices, PC based platforms, and other types of computing platforms.Interface 348 can be an externalperipheral interface 536, anetwork interface 542, aninteractive interface 532, or other type of interface. - In addition,
faceplate 302 can be fastened to abracket 318.Bracket 318 has a plurality of bracket fasteners for fastening acard reader 310 to the card reader assembly. Thebracket 318 also has a threadedinsert 316 located in the rear of thebracket 318. Threadedinsert 316 can receive a thumbscrew in order to facilitate the fastening of the printer assembly bracket (not shown) to the card reader assembly. - A
push button switch 308 can be fastened to thefaceplate 302 and electrically connected to thepayment module board 350 by way of cable assembly or as a PCB mountable component.LED display payment module board 350 by way of cable assembly or as a PCB mountable component. In addition,card reader 310 can be electrically connected to thepayment module board 350 by way of cable assembly or as a PCB mountable component. - In an exemplary embodiment the firmware embedded in the base level payment module could support base level functionality as well as other payment module functionality available with an expansion daughter board (i.e. display, communication, and other function modules). Such base level functionality could include: the MDB Controller/G4 E-PORT/E-PORT (System 500) Interface Protocol And Specification, certified credit bureau protocol and transaction processing directly with a credit bureau when communication options allow, local authorization card processing options, a self managing local databases for use during local authorization processing, setup mode to configure MDB bus interface options and other card reader parameters and hardware options, DEX interface polling and data passing to USALIVE remote location and other remote locations when certain hardware options are available, communication support for modem, point-to-point, and external data modem when certain hardware options are available, active and passive modes of operation to support dial-a-vend, and other VIU initiated transactions, and or full transaction management which includes the steps of: 1) accept identification (for example a credit card, magnetic card, hotel room key card, wireless phone initiated, REID, PDA initiated, dial-a-vend communication, smart card, wireless device initiated, bio-metric, etc.) for cashless payment; 2) check identification data local or remote authorization (remote authorization via external communications means); 3) conduct transaction (remotely manageable single or multi vend options, max vend item limits, time-out limits, max authorization amount limits, accrue sale amounts, time stamp transactions, save in non-volatile memory transaction records); and 4) post process transaction (record inventory dispensed, and payment detail in transaction record, data communicate transaction information upon request to external communication platform).
- To allow functionality expansion of the base payment module, which could include printing capabilities, communication capabilities, control of an electronic lock, and other vending machine interface options and or capabilities (such as DEX, MDB, MDB mimic, etc.) a daughter board could be added to the base payment module. More specifically, additional payment module functionality through the use of one or more daughter cards could include; support for optional DEX interface and capabilities, MDB interface and capabilities, MDB mimic interface and capabilities, support for optional 16 character by 2 line LCD display or other types and styles of LCD or vacuum florescent displays, support for optional printer circuit card; and support for optional communication card (communication card could support point-to-point, modem, and external modem interfaces). Such daughter boards can be electrically connected to the payment module board by way of connection means 358. The daughter boards can be referred to as daughter cards. The payment module board can also be referred to as the base level payment module. Connection means 358 (shown in
FIG. 3J ) can include wired and wireless methods of electrically connecting to and data communicating between the payment module board and the daughter board. - Printing capabilities can include printing receipts, printing coupons, printing reports, and other types of printing, and printing capabilities.
- Referring to
FIGS. 31 and 3J there is shown how a payment module with communications daughter hoard, and optional LCD display could be incorporated into the base level payment module. Referring toFIGS. 31 and 3J there is shown a payment module assembly. In an exemplary embodiment the payment module assembly can be installed in a vending machine's dollar bill validator slot. A user having access to the front of the payment module assembly can insert cards, view transaction status information via the LCD display or the three LED display (340, 342, 344), and use apush button 308 to provide system input. - A
faceplate 302 is shown fastened to asupport bracket 318. Thefaceplate 302 is sized to fit the industry standard bill validator opening, which can be found on most brands and models of vending equipment. Thefaceplate 302 has a plurality of holes to allow fastening of the card reader assembly into the vending equipment. -
Faceplate 302 also has apaper exit slot 304 to allow a receipt printer (not shown) to dispense a printed receipt to a user of the system.Faceplate 302 also has adisplay slot 306 which allows the LCD display mounted on the threadedstuds 346 to be viewable from its mounting location behind the front surface offaceplate 302. An LED displayassembly comprising LED - An
interface connection 348 on thepayment module board 350 provides an electrical interface to external data processing equipment and or other computing platforms. Such external data processing equipment and or computing equipment can include communication devices, display devices, telemetry devices, VIU's, interactive media devices, PC based platforms, and other types of computing platforms.Interface 348 can be an externalperipheral interface 536, anetwork interface 542, aninteractive interface 532, or other type of interface. - A connection means 358 effectuates the connectivity of daughter boards to the payment module board. The daughter boards can be referred to as daughter cards. The payment module board can also be referred to as the base level payment module. Connection means 358 can include wired and wireless methods of electrically connecting to and data communicating between the payment module board and the daughter board.
- In addition,
faceplate 302 can be fastened to abracket 318.Bracket 318 has a plurality of bracket fasteners for fastening acard reader 310 to the card reader assembly. Thebracket 318 also has a threadedinsert 316 located in the rear of thebracket 318. Threadedinsert 316 can receivethumbscrew 332 in order to facilitate the fastening of the printer assembly bracket (not shown) to the card reader assembly. Anexpansion board 354 can be mounted to thebracket 318 and electrically interconnected to the base levelpayment module board 350 by way ofcable assembly 356 or as a PCB mountable component. - A
push button switch 308 can be fastened to thefaceplate 302 and electrically connected to thepayment module hoard 350 by way of cable assembly or as a PCB mountable component.LED display payment module board 350 by way of cable assembly or as a PCB mountable component. In addition,card reader 310 can be electrically connected to thepayment module board 350 by way of cable assembly or as a PCB mountable component. - Referring to
FIG. 3K there is shown a payment module and printer assembly being aligned for assembly together. In an exemplary embodiment support for a printer option can be accomplished with the addition of a daughter card or interconnection of a printer mechanism with the base levelcard reader board 350, and the addition of the printer assembly. Shown in.FIG. 3K is aprinter assembly plate 330, interconnected with apaper roll holder 324, aprinter mechanism 328, and athumbscrew fastener 332. Also shown is apaper roll 322 being held by thepaper roll holder 324 and apaper feed adjuster 326, which is part ofprinter mechanism 328. - In an exemplary embodiment a user of the payment module assembly can choose to add the ability to print receipts, coupons, and other print information by sliding the printer assembly onto the card reader assembly and making the appropriate electrical connections to the daughter board 226 or
card reader card 350. Furthermore, the printer assembly can be securely fastened to the card reader assembly by way ofthumbscrew 332. - A connection means 358 effectuates the connectivity of daughter boards to the payment module board. The daughter boards can be referred to as daughter cards. The payment module board can also be referred to as the base level payment module. Connection means 358 can include wired and wireless methods of electrically connecting to and data communicating between the payment module board and the daughter board.
- Referring to
FIG. 3L there is shown a vendingsnack style machine 402 with asystem 500. Avending machine 402 can be asystem 500. Avending machine 402 can be operationally related to asystem 500. Alternatively, avending machine 402 can be integrated with, but separate from asystem 500 for retrofit purposes. Abill acceptor 360, acoin acceptor 362, and auser keypad 364 can be optionally interconnected with and operationally related to thevending machine 402.Suitable vending machine 402 can include those manufactured by or for COKE, PEPSICO, CRANE NATIONAL VENDORS, KRH, AP, AMS, DIXIE NARCO, CAVALIER, ROYAL, MARS, VENDO, or other vendingsnack style machine 402 manufacturers or suppliers. - In an exemplary embodiment a
system 500 can be embodied in an enclosure resident on the outside surface of the vending machine. In this regard, fastening to the vending machine can occur without thesystem 500 device requiring or occupying the vending machine dollar bill validator hole. This can enable the coexistence of a dollar bill validator and asystem 500 attached to the same vending without requiring additional cutting of the vending machine and or encountering form or fit problems in vending equipment with restrictive front door areas to support both devices. - Referring to
FIGS. 3M-3N and 3P there is shown a plurality of data processing devices embodiments. - In
FIG. 3M there is shown awireless phone 368. Awireless phone 368 can be a data processing device. Furthermore, awireless phone 368 can be operationally related to asystem 500. Alternatively, awireless phone 368 can be integrated with, but separate from asystem 500 wherein data can be transferred, data communicated and or physically transported between the vending machine having asystem 500 and a plurality of remote location including a plurality of global network based data processing resources.Suitable wireless phone 368 can include those manufactured by GENERAL ELECTRIC, AT&T, NYNEX, SPRINT, MCI, BELL TELEPHONE (BELL SOUTH, BELL ATLANTIC, ETC.), SONY, AUDIOVOX, QUALCOM, NOKIA, ERICKSON, MOTOROLA, 3COM, SHARP, PANASONIC, TEXAS INSTRUMENTS, CABLE AND WIRELESS, LDI, or other wireless telephone manufacturers or suppliers. In an exemplary embodiment awireless phone 368 can hardwire to or wirelessly data communicate with asystem 500. - In an exemplary embodiment, for example and not limitation a
wireless phone 368 can be utilized to data communicate with asystem 500 wired or wirelessly. Such data communication can include configuration data, transaction data, and other data.Wireless phone 368, can then be physically carried to a remote location for further data communication. Such further data communication can includewireless phone 368 at the remote location data communicating with a data processing device. Such data communication can include data communicating the configuration data, transaction data, and other data obtained in part from thesystem 500. The data processing device can further process and or data communicate with additional data processing devices, and or remote locations. In this regard, a wireless network can be effectuated between thesystem 500 and the remote location, wherein the wireless component of the network is the use ofwireless phone 368 as a data carrier coupled with thewireless phone 368 being physically carried to a remote location. - One advantage in an exemplary embodiment can be in reducing or eliminating the need to provide a wide area network connection or other dedicated communication access to the
system 500 for the purpose of processing transaction and communicatingsystem 500 configuration data, with a remote location, in real time. As an example,local authorization routines 1300 and 1900 can be utilized to authorize a cashless transaction—no real time remote location access required to authorize the validity of the cashless ID (magnetic card, RFID, biometric ID, etc.). The vending session can be completed and at some later date, preferably upon the arrival of vending equipment service personnel the transaction data can be downloaded intowireless phone 368. In addition,optionally system 500 configuration data can be uploaded to thesystem 500. The vending equipment service person can then physically care thewireless phone 368 to a remote location where the transaction data and other data can be downloaded into a data processing device. Such a data processing device can be a PC, or a global network based data processing resource. The transaction data can then be data communicated to a second remote location as required or processed locally. Such processing can include authorizing the locally authorized transaction with a credit bureau or other bureau and or settling the transaction to effect payment to the merchant. - Referring to
FIG. 3N there is shown apager 370. Apager 370 can be a data processing device. Furthermore, apager 370 can be operationally related to asystem 500. Alternatively, apager 370 can be integrated with, but separate from asystem 500 wherein data can be transferred, data communicated and or physically transported between the vending machine having asystem 500 and a plurality of remote location including a plurality of global network based data processing resources. Apager 370 can be a SKYTEL, MOTOROLA, or other similar brand ofpager 370. In an exemplary embodiment apager 370 can hardwire to or wirelessly data communicate with asystem 500. - In an exemplary embodiment, for example and not limitation a
pager 370 can be utilized to data communicate with asystem 500 wired or wirelessly. Such data communication can include configuration data, transaction data, and other data.Pager 370 can then be physically carried to a remote location for further data communication. Such further data communication can includepager 370 at the remote location data communicating with a data processing device. Such data communication can include data communicating the configuration data, transaction data, and other data obtained in part from thesystem 500. The data processing device can further process and or data communicate with additional data processing devices, and or remote locations. In this regard a wireless network can be effectuated between thesystem 500 and the remote location, wherein the wireless component of the network is the use ofpager 370 as a data carried coupled with thepager 370 being physically carrier to a remote location. - One advantage in an exemplary embodiment can be in reducing or eliminating the need to provide a wide area network connection or other dedicated communication access to the
system 500 for the purpose of processing transaction and communicatingsystem 500 configuration data, with a remote location, in real time. As an example,local authorization routines 1300 and 1900 can be utilized to authorize a cashless transaction—no real time remote location access required to authorize the validity of the cashless ID (magnetic card, RFID, biometric ID, etc.). The vending session can be completed and at some later date, preferably upon the arrival of vending equipment service personnel the transaction data can be downloaded intopager 370. In addition,optionally system 500 configuration data can be uploaded to thesystem 500. The vending equipment service person can then physically carry thepager 370 to a remote location where the transaction data and other data can be downloaded into a data processing device. Such a data processing device can be a PC, or a global network based data processing resource. The transaction data can then be data communicated to a second remote location as required or processed locally. Such processing can include authorizing the locally authorized transaction with a credit bureau or other bureau, and or settling the transactions to effect payment to the merchant. - Referring to
FIG. 3P there is shown a personal data assistant (PDA) 372. APDA 372 can be a data processing device. Furthermore, APDA 372 can be operationally related to asystem 500. Alternatively, aPDA 372 can be integrated with, but separate from asystem 500 wherein data can be transferred, data communicated, and or physically transported between the vending machine having asystem 500 and a plurality of remote locations, including a plurality of global network based data processing resources. APDA 25 372 can be a CASIO, HEWLETT PACKARD, POCKET PC BRAND, 3COM, EPSON, SEIKO, PANASONIC, IBM, SHARP, MOTOROLA, or other similar brand orPDA 372. In addition a PALM PILOT brand manufactured by 3COM can be aPDA 372.PDA 372 can be referred to as a portable digital device. In an exemplary embodiment aPDA 372 can hardwire to or wirelessly data communicate with asystem 500. - In an exemplary embodiment, for example and not limitation, a
PDA 372 can be utilized to data communicate with asystem 500 wired or wirelessly. Such data communication can include configuration data, transaction data, and other data.PDA 372 can then be physically carried to a remote location for further data communication. Such further data communication can includePDA 372 at the remote location data communicating with a data processing device. Such data communication can include data communicating the configuration data, transaction data, and other data obtained in part from thesystem 500. The data processing device can further process and or data communicate with additional data processing device, and or remote locations. In this regard, a wireless network can be effectuated between thesystem 500 and the remote location, wherein the wireless component of the network is the use ofPDA 372 as a data carrier coupled with thePDA 372 being physically carried to a remote location. - One advantage in an exemplary embodiment can be in reducing or eliminating the need to provide a wide area network connection or other dedicated communication access to the
system 500 for the purpose of processing transaction and communicatingsystem 500 configuration data with a remote location in real time. As an example,local authorization routines 1300 and 1900 can be utilized to authorize a cashless transaction—no real time remote location access required to authorize the validity of the cashless ID (magnetic card, MID, biometric 1D, etc.). The vending session can be completed and at some later date, preferably upon the arrival of vending equipment service personnel the transaction data can be downloaded intoPDA 372. In addition,optionally system 500 configuration data can be uploaded to thesystem 500. The vending equipment service person can then physically care thePDA 372 to a remote location where the transaction data and other data can be downloaded into a data processing device. Such a data processing device can be a PC, or a global network based data processing resource. The transaction data can then be data communicated to a second remote location, as required, or processed locally. Such processing can include authorizing the locally authorized transactions with a credit bureau or other bureau, and or settling the transactions to effect payment to the merchant. - Referring to
FIG. 4 there is shown avending machine 402, vendingmachine interface unit 100, card reader withoptional printer assembly 406, and transceiver andmodem base unit 200. - In an exemplary embodiment a
VIU 100 can be located inside the vending equipment, such asvending equipment 402. In addition, the card reader assembly with optional printer assembly can be mounted inside the vending equipment in such a way that a user has access to the card reader assembly. During operation a communication line can be interconnected directly with theVIU 100. Alternatively theVIU 100 can wireless data communicate with atransceiver base unit 200. There is shown inFIG. 4 atransceiver unit 200 plugged into an electrical outlet onwall 202. Also shown is atelecommunication line 408 interconnect withtransceiver unit 200. - Referring to
FIG. 5 there is shown an audit-credit-interactive system 500. In an exemplary embodiment the audit-credit-interactive system 500 electronics can be located in theVIU 100 enclosure and in general be referred to as asystem 500 orVIU 100. In addition, aVIU 100 having an audit-credit-interactive system 500 can be referred to as a MDB controller, a computing platform, a USA TECHNOLOGIES E-PORT, or aUSA 25 TECHNOLOGIES G4 E-PORT or payment module. - The audit-credit-
interactive system 500 provides three major components of functionality. As an audit device the audit-credit-interactive system 500 can audit inventory, sales, operational and other vending machine performance by way of the MDB and DEX interfaces. This gathering and forwarding to a plurality of remote locations of the DEX and or MOB data can be referred to as vending equipment telemetry, or as telemetry data. - When the card reader assembly is added to the system the audit-credit-
interactive system 500 provides audit and card processing functionality. The card functional allows cashless vending transactions to occur. Cashless vending transactions are effectuated by allowing various forms of identification (ID), and payment medium to be accepted as or for payment at the vending equipment. Other forms of ID can include, for example and not limitation, smart and magnet cards, radio frequency (RF) ID devices (RFID), user personal identification numbers (PIN) numbers or accounts, or wireless data communication access by way of wireless phone, Bluetooth, 802.11, 802.1 IB, as well as other suitable protocols or devices. For purposes of disclosure cashless vending refers to non-coin and non-cash transactions. - The audit-credit-
interactive system 500 includes numerous mutually exclusive interfaces and control means. In a plurality of customer specifications and where customer cost considerations demand, there may arise a situation where an audit-credit-interactive system 500 maybe manufactured in such a way as to not contain or require the use of certain features, functions, interfaces, and or control means. Accordingly, an audit-credit-interactive system 500 can easily be manufactured to include or exclude a specific combination of features, functions, interfaces, and or control means to produce the desired system performance at a desirable cost to a customer. For example and not limitation, a customer may desire to operate an audit-credit-interactive system 500 without anRFID interface 504. In such a case, an audit-credit-interactive system 500 could be manufactured with the omission of theRFID interface 504. In any combination, the same inclusion or exclusion of features, functions, interfaces and or control means can be applied to other audit-credit-interactive system 500 features, functions, interfaces, and or control means. - Interconnected with
microcontroller 502 can be anREID interface 504. TheREID interface 502 can data communicate with wired or wireless devices that are proximate to theRFID interface 504. In an exemplary embodiment, these wired and wireless devices include, for example and not limitation, touch devices from DALLAS SEMICONDUCTOR, and wireless devices such as the MOBIL SPEED PASS, or other similar or suitable wired or wireless REID devices.Microcontroller 502 can be any suitable microcontroller, or microprocessor. In an exemplary embodiment, amicrocontroller 502 can be a ZILOG Z8038220FSC, ZILOG eZ80 type, INTEL, MICROCHIP, MOTOROLA, AMD, UBICOM, or other similar brand or type of microcontroller.RFID interface 504 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - Interconnected with
microcontroller 502 can be bill acceptor andcoin mechanism interface 506. The bill acceptor andcoin mechanism interface 506 emulate industry standard bill acceptor and coin mechanism interfaces. In this regard, the audit-credit-interactive system 500 can be interconnected to vending equipment by way of theinterface 506. The audit-credit-interactive system 500 mimicking industry standard bill acceptor and coin mechanism electrical control system and signal timing can then operate the vending equipment. Industry standard bill acceptors include serial and pulse style. Serial style bill acceptors typically utilize INTERRUPT, SEND, ACCEPT ENABLE, and DATA control signal lines. Pulse style bill acceptors, and coin mechanisms send electrical pulses to an attached control system to indicated the receipt of coin and currency. Serial and pulse style bill acceptors and coin mechanisms can include for example and not limitation, MARS, COINCO, CONLUX, or other similar bill acceptors and or coin mechanisms. - Interconnected with
microcontroller 502 can be adisplay interface 508. Adisplay interface 508 can be a liquid crystal display (LCD), a vacuum florescent display, an RS232 connection, and or an electrical interface for driving a display. In an exemplaryembodiment display interface 508 can be, for example and not limitation, an RS232 serial connection. Such a serial connection can be utilized to data communicate display data as well as other types of data to a cardreader interface board 312. - Interconnected with
microcontroller 502 can be a plurality of keypad andbutton inputs 510. Keypad andbutton inputs 510 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - Interconnected with
microcontroller 502 can bememory 512.Memory 512 can be a plurality of different types of memory. In anexemplary embodiment memory 512 can comprise non-volatile random access memory (NOVRAM), random access memory (RAM), flash memory, and serial flash memory. In addition, the RAM/NOVRAM can include a timekeeper function for maintaining date and time RAM/NOVRAM can be a DALLAS SEMICONDUCTOR DS1644, DS1646, or DS1647, or other similar or suitable RAM. Flash memory can be an ATMEL or STS brand AT29E010 or other similar style, different size, other brand, or suitable substitute. The serial flash memory can be an ATMEL brand AT45D081, a MICROCHIP 93LC66, or other similar style, different size, other brand, or suitable substitute. - In an exemplary embodiment the timekeeper feature can be effectuated to time and date stamp the transactions as they occur. From the vending equipment's MDB interface CASH VEND transactions, if supported by the VMC, as well as cashless vend transactions can be monitored and recorded. Adding a time and date time stamp to the each transaction as they occur can result in a detailed inventory utilization record showing the date and time the products were vended.
- Interconnected with
microcontroller 502 can be anoffice product interface 534. Anoffice product interface 534 can include, for example and not limitation, an optoisolator for counting pulses generated by a fax machines, copy machine, and other office product equipment. In addition,office product interface 534 can include, for example and not limitation, a DTMF decoder for decoding telephone touch-tones and subsequently billing for the use of a telephone line. DTMF decoding can be used in connection with a fax machine to bill for usage based in part on local, long distance, and international dialed locations. - In an exemplary embodiment, in addition to monitoring and billing for use of office products, office products interface 534 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of the
system 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and services vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - Interconnected with
microcontroller 502 can be an externalperipheral interface 536. The externalperipheral interface 536 includes a plurality of configurable input and output line for interfacing to external peripheral devices. Externalperipheral interface 536 can support serial peripheral interfaces (SPI), serial interfaces such as RS232, RS485, I2C, and other types of peripheral interfaces and communication protocols and standards. - In an exemplary embodiment, in addition to interfacing to external peripheral devices, external
peripheral interface 536 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - Interconnected with
microcontroller 502 can be anetwork interface 542. Anetwork interface 542 can be a local area network connection, a wide area network connection, an Ethernet, token ring, FIREWIRE, or other similar or suitable type of network interface. - In an exemplary embodiment, in addition to providing network connectivity,
network interface 542 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A
data modem 514 can be interconnected withmicrocontroller 502. Adata modem 514 can effectuate wired and wireless data communications with a plurality of remote locations. Wireless data modems include, for example and not limitation, MOTOROLA, ERICKSON, QUALCOM, and NOKIA brands of data modems, as well as SPRINT PCS, CDMA, CDPD, 2G type wireless device, 2.5G type wireless devices, 3G type wireless devices, research in motion (RIM) type wireless device, or other similar or suitable brands or types of wireless data modem. - In an exemplary embodiment, in addition to effectuating wired and wireless data communications with a plurality of remote locations,
data modem 514 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A multi-drop-bus (MDB)
interface 518 is interconnected withmicrocontroller 502. In an exemplary embodiment anMDB interface 518 electrically interconnects with the vending equipment's MDB bus. AnMDB interface 518 can be implemented with a universal asynchronous receiver transmitter (UART). In addition anMDB interface 518 can include a buffer circuit to handle the physical interface requirement to connect thesystem 500 to the MDB bus. A suitable buffer circuit can be an opto-isolated circuit or other suitable buffer circuit interface. - In an exemplary embodiment the UART can be configured to operate with eight data bit and one address bit in addition to start and stops bits (nine bit serial). In this regard in accordance with NAMA MDB specifications the
MDB interface 518 can operate in and support the multi mode-multi processor addressing requirements in operation the UART under control of themicrocontroller 502 detects a valid address byte being data communicated from the VMC. The valid address byte indicates to thesystem 500 that the data following from the VMC should be captured and stored, parsed, responded to and or in general thesystem 500 should data communicate with the VMC as appropriate. - In an exemplary embodiment, to handle MDB communications an MDB message routine can be implemented in firmware under the control of the
microcontroller 502. In this regard a series of interrupt routines can be utilized to first detect the message and then trigger a routine to parse and respond to the received message. A UART receive routine can be effectuated to capture and store data being communicated from the VMC. Upon detection of data and or MDB message data a one-shot MDB MESSAGE RESPONSE timer can be initiated. The one-shot MDB MESSAGE RESPONSE timer timeout period is the amount of time after receiving an MDB message from the VMC thesystem 500 will wait before sending a MDB message response. When the MDB MESSAGE RESPONSE timer times out an interrupt can be initiated to start an MDB message parsing and response routine. The MDB message parsing and response routine decodes the message sent from the VMC and takes the appropriate action and sends the appropriate response to the VMC. - In accordance with NAMA and other derivative MDB specifications the
MDB interface 518 operates in the slave mode being responsive to the vending machine controller (VMC). The VMC typically resides in the vending equipment and operates as the vending equipment's control system. Interconnection with the MDB bus in combination with NAMA and other derivative MDB standards data communications allows theVIU 100 audit-credit-interactive system 500 to reside as a peripheral device to the vending equipment's control system in an auditing and payment device mode of operation. - In an exemplary embodiment a VMC can include peripheral device interface support for
MDB interface 518,DEX interface 520, bill andcoin interface 506, andoffice products interface 534. - In an exemplary embodiment the audit-credit-
interactive system 500 is implemented as a cashless reader device on the MDB bus. As a cashless reader thesystem 500 can audit and transact cashless vending transactions. - A
mimic MDB interface 516 can be interconnected withmicrocontroller 502.Mimic MDB interface 516 unlikeMDB interface 518 can operate in both the master and slave modes of operation in accordance with the NAMA and other derivative MDB specifications. Themimic MDB interface 516 can support peripheral devices. Amimic MDB interface 516 can be implemented with a universal asynchronous receiver transmitter (UART). In addition amimic MDB interface 516 can include a buffer circuit to handle the physical interface requirement to connect thesystem 500 to the MDB bus. A suitable buffer circuit can be an opto-isolated circuit or other suitable buffer circuit interface. - In an exemplary embodiment the UART can be configured to operate with eight data bit and one address bit in addition to start and stops bits. In this regard in accordance with NAMA MDB specifications the
mimic MDB interface 516 can operate in and support the multi mode-multi processor addressing requirements. In operation the 15 UART under control of themicrocontroller 502 detects a valid address byte being data communicated from the VMC. The valid address byte indicates to thesystem 500 that the data following from the VMC should be captured and stored, parsed, responded to and or in general thesystem 500 should data communicate with the VMC as appropriate. - In an exemplary embodiment, to handle MDB communications an MDB message routine can be implemented in firmware under the control of the
microcontroller 502. In this regard a series of interrupt routines can be utilized to first detect the message and then trigger a routine to parse and respond to the received message. A UART receive routine can be effectuated to capture and store data being communicated from the VMC. Upon detection of data and or MDB message data a one-shot MDB MESSAGE RESPONSE timer can be initiated. The one-shot MDB MESSAGE RESPONSE timer timeout period is the amount of time after receiving an MDB message from the VMC thesystem 500 will wait before sending a MDB message response. When the MDB MESSAGE RESPONSE timer times out an interrupt can be initiated to start an MDB message parsing and response routine. The MDB message parsing and response routine decodes the message sent from the VMC and takes the appropriate action and sends the appropriate response to the VMC. - One advantage of this dual mode of operation is that the
mimic MDB interface 516 can support proprietary or different versions of MDB protocol and appear to a peripheral device as a VMC. In this regard peripheral devices that are not compatible with the vending equipment's VMC control system can be interconnected withsystem 500'smimic MDB bus 516. Through software resident on thesystem 500 the peripheral device by way of themimic MDB interface 516 can data communicate with thesystem 500 and or through thesystem 500's (with protocol interpolation)MDB interface 518, over the vending equipment's MDB bus to the vending equipment's VMC control system. - A second advantage of the dual mode of operation of the
mimic MDB interface 516 is that features supported by a peripheral resultant from the implementation of a derivative MDB specification can be utilized by data communication first to thesystem 500 by way of themimic MDB interface 516. If the MDB protocol command is a command supported by the vending equipment's VMC controller thesystem 500 can then relay the message received from the peripheral device to the VMC control system by way of thesystem 500'sMDB interface 518. In this regard thesystem 500 essentially acts as a MDB interface gateway sending and receiving non-VMC support portions of a peripheral's implemented MDB specification. In addition, the MDB gateway implemented by thesystem 500 can allow the peripheral device data communication access to the VMC controller for portions of the peripheral implemented MDB specification supported by the vending equipment's VMC controller. - In an exemplary embodiment,
mimic MDB interface 516 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and services vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A data exchange (DEX)
interface 520 is interconnected withmicrocontroller 502. TheDEX interface 520 is a serial connection interface for interfacing thesystem 500 to the VMC control system. In an exemplary embodiment the DEX interface conforms to the EVA-DTS version 4.0 and version 5.0 specifications. In this regard thesystem 500 can ‘DEX’ vending equipment and obtain marketing, sales, and operational data as well as other types of data related to the vending equipment operation and performance. In addition, theDEX interface 520 can be utilized to program the VMC control system. VMC programming can include setting prices and parameters, setting operational data, clearing error codes or messages, and programming the VMC firmware. - In an exemplary
embodiment DEX interface 520 can be configured as a transistor-to-transistor level (TTL) or RS232 style serial connection. Furthermore, the transmit line from thesystem 500 can be independently signal level configurable such that during non-data communication idle time the signal level of thesystem 500 DEX transmit line can be set to a high impedance state or a low signal level state as opposed to the tradition idle high signal level state. The advantage can be that most VMC equipment is configure to detect the insertion of a plug into the DEX port. The insertion of the plug places a high signal level from the DEX port transmit line onto the VMC receive line. This can invoke the VMC to begin a DEX session with the device plugged into the DEX port. The ability to selectively configure the non-communication idle state signal level of thesystem 500 DEX transmit line to a high impedance state or low signal level state allows thesystem 500 DEX connection to be made with the VMC DEX port without the DEX port detecting the connection has been established. In this regard thesystem 500 only needs to change the state of thesystem 500 DEX transmit line to trigger a DEX session with the VMC controller. In addition aDEX interface 520 can include a buffer circuit to handle the physical interface requirement to connect thesystem 500 to the DEX bus. A suitable buffer circuit can be an opto-isolated circuit, TTL RS232 converter, or other suitable buffer circuit interface. - In an exemplary embodiment,
DEX interface 520 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A
modem 522 can be interconnected withmicrocontroller 502.Modem 522 can be utilized to data communicate to a plurality of remote locations.Modem 522 can include CERMETEK, XECOM, ZILOG, or other similar brands and types of modems and modem chip sets. - A
transceiver 524 can be interconnected withmicrocontroller 502. In anexemplary embodiment transceiver 502 can effectuate wireless data communication betweensystem 500 and a plurality of remote locations by way of transceiver unit's 200system 700. Atransceiver 524 can be a LINX, or MAX STREAM 430 Mhz, 800 Mhz, 900 MHZ, 2.40 hz, single frequency or spread spectrum RF module, and or other similar or suitable types of transceiver modules. - Additionally,
transceiver 524 can be interconnected withantenna 538.Antenna 538 can be any suitable antenna configured to perform optimally with the selected transceiver and frequency.Antenna 538 can be an ANTENNA FACTOR brand antenna or similar or suitable antenna. - Interconnected with
microcontroller 502 can be acard reader interface 526.Card reader interface 526 can support a variety of card reader interfaces and protocols including for example and not limitation bit strobe type of card readers. Bit strobe type of card readers read predefined tracks of data from a magnetic card. To read track data the card reader can incorporate a plurality of DATA-IN lines and DATA CLOCK lines to transfer magnetic card data.Card reader interface 526 can also support serial communication style card readers. Serial communication style card readers can incorporate TRANSMIT, RECEIVE, CLEAR TO SEND, and REQUEST TO SEND control lines to transfer card data tosystem 500. Such magnetic card readers can include those manufactured for or by XICO, MAGTEK, NEURON, or other similar or suitable card reader. - In addition to accepting magnet cards
card reader interface 526 can implement a smart card reader interface, credit cards, a hotel room card reader. In thisregard system 500 by way ofcard reader interface 526 can read, write, and execute embedded applications on a plurality of types and brands of smart cards. - In an exemplary embodiment, magnetic
card reader interface 526 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and services vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - An
external modem interface 528 can be interconnected withmicrocontroller 502. In an exemplary embodiment anexternal modem interface 528 can be an RS232 serial communication interface for interfacing to a plurality data modems, transceivers, and other communication type peripherals. Such data modems, transceivers, and other communication type peripherals can include for example and not limitation MOTOROLA., QUALCOM, ERICKSON, NOKIA, SPRINT, AT&T, LINX, MAX STREAM, or other similar or suitable data communication devices. - In an exemplary embodiment,
external modem interface 528 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and services vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A
printer interface 530 can be interconnected withmicrocontroller 502, Aprinter interface 530 can be a serial communication style or Centronic style interface. In an exemplaryembodiment printer interface 530 can be utilized to print receipts, coupons, and other print data. - An infrared communication interface (IRDA) 550 can be interconnected with
microcontroller 502.IRDA interface 550 can support BLUETOOTH, and other optical wireless standards and protocols. - In an exemplary embodiment,
IRDA interface 550 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A personal data assistant interface (PDA) 552 can be interconnected with
microcontroller 502. In this regard,PDA interface 552 can enable a PDA device, such asPDA 372 to data communicate withsystem 500. Inaddition pager 370, andwireless phone 368 can data communicate by way ofPDA interface 552 tosystem 500. - In an exemplary
embodiment PDA interface 552 can be an IRDA interface, or a radio frequency (RF) interface. Such interface types can include BLUETOOTH, WAP, 802.11, 802.1 IB, wireless LAN, wireless WAN, 2G type or compliant communications, 2.5G type or compliant communications, 3G type or compliant communications, or other suitable type or compliant communications. - In an exemplary embodiment,
PDA interface 552 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and services vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A
biometric interface 554 can be interconnected withmicrocontroller 502. In this regard, biometric data such as iris scans, finger prints, voice data, and other biometric data can be data communicated tosystem 500. - In an exemplary embodiment,
biometric interface 554 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and service vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - A touch or
contact interface 556 can be interconnected withmicrocontroller 502. Such a touch orcontact interface 556 can accept proximity devices, such as MUTTONS and other touch or contact related identification devices. Touch or contact devices that interface to touch orcontact interface 556 can be referred to as touch devices. - In an exemplary embodiment, touch or
contact interface 556 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and services vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - An
interactive interface 532 can be interconnected tomicrocontroller 502. Theinteractive interface 532 can be utilized in combination with the interactive interface communication protocol shown in the table below to interconnect thesystem 500 to a computing platform. The card reader assembly having a cardreader interface board user interface system 600, can be referred to as a computing platform. In addition, PC based devices, handheld devices, and other microprocessor-based devices are also computing platforms. - In an exemplary embodiment,
interactive interface 532 can be referred to as a payment interface, wherein a user can present a plurality of payment identification data to effectuate the use of thesystem 500. In addition, the payment identification data can be utilized to authorize the use of and payment for goods and services vended from vending equipment interconnected withsystem 500. Such payment identification data can be locally authorized at thesystem 500, and or remotely authorized at a remote data processing resource or other remote locations. In addition, the payment identification data may be retained at thesystem 500 and utilized in the local authorization databases to authorize a user presenting the same payment identification data for subsequent cashless transactions. - In an exemplary embodiment for example and not limitation a computing device can be interfaced to a
system 500 by way of theinteractive interface 532. In this regard the two interconnected devices can data communicate by way of an interactive device interface protocol. This protocol can be implemented in an exemplary embodiment as disclosed below as an example and not limitation where asystem 500 can be referred to as a MDB controller or G4, andhost network center 808 can be referred to as USALIVE; - The MDB controller is the microcontroller-based system, which can interface to the vending machines MDB interface and to a computing platform. Such computing platforms include E-PORT. Certain versions of the E-PORT may incorporate the MDB controller and computing platform into a single board solution. In such a case serial communications between the computing platform and the MDB microcontroller occur over the devices serial peripheral interface (SPI), serial interface or other similar or suitable communication interface.
- The G4 (system 500) version of E-PORT can utilize a single microcontroller to serve as an MDB controller or a semiconductor module as well as a cashless payment system platform. The G4 device incorporates an RS232 serial interface by which other computing platforms can interface to and control the functionality of the G4 and associated vending equipment. The G4 version can operate in two modes of operation. In a first mode of operation the G4 provides all the MOB interface control, audit/cashless payment support, and network connectivity. In this mode a computing platform can interact with the G4 in a hybrid role to monitor a string of user text prompts (see DISPLAY PROTOCOL) as well as execute commands (see below).
- In a second mode of operation the G4 can be configured and serve as an MDB controller (system 500) only. In this mode both the MDB-CONTROL and NON-MDB-CONTROL commands can be executed. While in this mode of operation the computing platform operates as a master device controlling the operation and process flow of the system. While in this mode the G4 serves as a slave device interfacing to the vending machine and managing the control of the MDB interface. COMMUNICATION INTERFACE details the electrical interconnections required to allow the G4 to data communicate with a computing platform.
- The MDB controller/G4 communicate to a computing platform by way of serial communications or other similar or suitable method of communication. In this regard a set of commands issued from the computing platform implement a level of control via the MOB controller/G4 and the MDB/ICP protocol to transact a cashless transaction, obtain DEX data information, and other vending machine related data. The communication protocol implemented between the system 500 (also referred to as the G4, G4 eport, or MDB controller) and the computing platform can be referred to as the Interactive Interface Communication. Protocol.
- Serial communications between the computing platform and the MDB controller/G4 are set at 9600 baud, 8 data bits, No Parity, and 2 Stop bits. Required serial port communications lines include transmit (Txd), Receive (Rxd) and Ground (Gnd).
- The “master” computing platform can initiate any ‘@’. ‘#’ ‘AAA’, or ‘BBB’ command listed in the command disclosure below. Commands are case sensitive. In response to a complete command the MDB controller/G4 will process and return the result string. The result string shall start with a start character (STX) hex $02, and conclude with an ETX character hex $03. A LRC check byte will immediately follow the ETX character.
-
STX hex $02 ETX hex $03 <esc> ESCAPE character hex $1B LRC all bytes XORed excluding the STX character and including the ETX character. - It is recommended that the ‘@’ or ‘#’ commands be executed by inserting a leading space prior to the or ‘#’. For example sending ‘@<esc>H’ instead of ‘@<esc>H’ the differencing being a leading space. The leading space will decrease command communication errors by allowing the MDB Controller/G4 to sync on the leading space.
- @<esc>T—REQUEST FOR CARD READER DATA.
If no card reader data is available then the result string will return: -
- STX+[CARD-NOCARDDATA]+ETX+LRC
Else the result string will return: - STX+[CARD-][UPTO 37 BYTES MAX OF CARD ATA]+ETX+LRC
Example of valid card data - STX+[CARD-41324199913243132=9182999937463764372]+ETX+LRC
@<esc>Z—CLEAR CREDIT CARD DATA. The credit card buffer will be cleared and
The result NOCARDDATA will be inserted in the buffer and returned in response to the @<esc>T command. The result string will return. - STX+[OK-Z]+ETX+LRC
@<esc>V—REQUEST FOR MDB TRANSACTION STRING DATA. Referring toFIG. 9D there is shown a MDB TRANSACTION STRING withsystem 500 and vending equipment interface.
- STX+[CARD-NOCARDDATA]+ETX+LRC
- In an exemplary embodiment the MDB TRANSACTION STRING is constructed and managed in memory accessible by
microcontroller 502. The MDB TRANSACTION STRING includes at least one of the following data fields; a VEND STATE field, a MAX VEND SALE field, a SALE PRICE field, a COLUMN field, or a VEND FLAG field. - The VEND STATE field is a one-character field that indicates the current state of the vending equipment. Valid VEND STATE can include T for inactive state, ‘D’ for disable state, ‘E’ for enable state, ‘S’ for in session state, or ‘V for vend state, as well as other vend states.
- The MAX VEND SALE is the value of the highest priced item in the vending machine as reported by the vending machine to the
system 500 during the MDB setup sequence. The MAX VEND SALE value is typically part of theMDB 11 00 (as defined in the NAMA MDB specification) setup command but can be set by thesystem 500 or data communicated to thesystem 500 in other ways. - The SALE PRICE is the vend sale price of the vend item selected from the vending machine as reported by the vending machine during an MDB VEND REQUEST message transaction with
system 500. Typically the SALE PRICE is part of the MDB VEND REQUEST command 13 00 (as defined in the NAMA MDB specification) but can be set by thesystem 500 or data communicated to thesystem 500 in other ways. The VEND REQUEST command is typically sent from the VMC to thesystem 500 when a user selects an item from the vending machine. In general, the vending machine reports the SALE PRICE and the COLUMN information while in a vend session and does not dispense products or services until the vend approved message sent by thesystem 500 is received by the vending machine (received by the vending machine's VMC). - The COLUMN field is the column identification (the column the vended item is residing in within the vending machine typically used to track inventory) of the vend item selected from the vending machine as reported by the vending machine during an MDB VEND REQUEST message transaction with the
system 500. - The VEND FLAG field is a one-character field that indicates the status of a vend cycle. The VEND FLAG field can include: ‘C for clear flag, ‘$’ for currency vend flag, ‘P’ for vend pending flag, ‘A’ for vend approved flag, ‘D’ for vend declined flag, ‘V for cashless vend occurrence flag, ‘U’ for user selected amount, ‘R’ request for vend approve, ‘F’ for vend fail flag, as well as other vend flags.
- In an exemplary embodiment, during execution of firmware by microcontroller 502 a mutually exclusive routine 512C (mutually exclusive routine operating independently of other routines, procedures, applications, 512B application code, or systems) can be utilized to manage and report on the state and operation of the VMC. In 25 this regard, a wide variety of application code (running on
microcontroller 502 or other system and or microcontrollers) andcomputing platforms 802 can manage and monitor the vending machine state and operation characteristics with respect to the vend process. - In operation a data communication connection between a
vending machine 402 andsystem 500 includes a connection between thevending machine 402 and at least one of the vending equipment interfaces (516, 518, and 536 are shown). Data communication in the way of MDB initialization, setup, polling, session, as well as other types of data communication occur between thevending machine 402 and thesystem 500.Microcontroller 502 having data communication access tomemory 512A constructs and manages the MDB TRANSACTION STRING in memory. As data is exchanged between thevending machine 402 and thesystem 500,microcontroller 502 updates the MDB TRANSACTION STRING as required. - Utilization of the MDB TRANSACTION STRING occurs when application code running in
memory 512B, and orcomputing platform 802 interconnected withsystem 500 by way of theinteractive interface 532 read the MDB TRANSACTION STRING to make certain determinations. For example and not limitation, an application running in 15memory 512B can read the MDB string VEND STATE FLAG field and determine the current state is MDB VEND STATE ‘D’ for disable. This can cause the application code to display a message by way ofdisplay interface 508 that the vending machine is DISABLED and can not transact a vend. Upon thevending machine 402 data communicating with thesystem 500 by Way of the various vending equipment interfaces thevending machine 402 may communicate the MDB reader enable 14 01 (as defined in the NAMA MDB specification) command. Themicrocontroller 502 would then update the MDB TRANSACTION STRING with the ‘E’ for enable. The application code running inmemory 512B upon reading the MDB VEND STATE field would now determine the vending machine is MDB VEND STATE ‘E’ for enabled and could 25 display a message by way ofdisplay interface 508 that the vending machine is ENABLED and ready for vending. - In another exemplary embodiment a
computing platform 802 can monitor the MDB TRANSACTION STRING to determine the current state and condition of thevending machine 402. In addition, thecomputing platform 802 can data communicate by way of theinteractive interface 532 commands to be executed bymicrocontroller 502. Such commands are referred to as the ‘#’, AAA, and BBB commands disclosed herein. - As an example and not limitation,
computing platform 802 can monitor and controlvending machine 402 by way ofinteractive interface 532 by utilizing the @<esc>I, @<esc>V, @<esc>T, and or the @<esc>H commands to monitor the presence of card data and the current MDB TRANSACTION STRING setting. One advantage of invoking the @<esc>I interrupt command is the once invoked any time the MDB TRANSACTION STRING or card reader buffer change the MDB TRANSACTION STRING and or card reader buffer will be data communicated from thesystem 500 to thecomputing platform 802. In this configuration thecomputing platform 802 does not need to poll to determine whether card data or MDB TRANSACTION STRING status has changed—the data will be sent to thecomputing platform 802 when it does. - The
computing platform 802 can determine from the MDB TRANSACTION STRING that the vending machine is MDB VEND STATE ‘E’ enabled and ready for a vend cycle. The computing platform can then data communicate to thesystem 500 one of the @<esc>S, @<esc>B, or one of the @<esc>A (session commands) commands. These commands instruct thesystem 500 to take certain actions that can include having thesystem 500 by way of the vending equipment interfaces data communicated to vending 25machine 402 the MDB BEGIN SESSION (as defined in the NAMA MDB specification) command. The vending machine will responds by starting a session. Themicrocontroller 502 will update the MDB TRANSACTION STRING to reflect that thevending machine 402 is in session MDB VEND STATE FLAG set to ‘S’. - When a user presses a button on the
vending machine 402, thevending machine 402 data communicates an MDB VEND REQUEST 13 00 (as defined in the NAM A MDB specification) with SALE PRICE and COLUMN detail information attached.System 500 upon receipt of the command can update the MDB TRANSACTION STRING to reflect the SALE PRICE, COLUMN, and VEND FLAG ‘R’ vend request (VEND ASSIST mode ‘ON’). The computing platform can either read the MDB TRANSACTION STRING (non interrupt mode) or the MDB TRANSACTION STRING will be data communicated upon change to the computing platform 802 (interrupt mode). In the VEND ASSIST ON mode thecomputing platform 802 will have to send the #<esc>Q command to deny the vend request or the #<esc>R with sales detail to approve the vend request. Thesystem 500 will respond to thecomputing platform 802 #<esc>Q and #<esc>R command by updating the MDB TRANSACTION string accordingly and sending the VEND DENIED 06 (as defined in the NAMA MDB specification) command to thevending machine 402, or the VEND APPROVED 05 (as defined in the NAMA MDB specification) to thevending machine 402 respectively. - In the VEND ASSIST OFF mode the VEND APPROVED 05 (as defined in the NAMA. MDB specification) may be automatically generated and sent to the
vending machine 402 by thesystem 500 in response to the VEND REQUEST message from thevending machine 402. - In the event of the VEND APPROVED being sent to the
vending machine 402 the MDB TRANSACTION STRING will be updated to MDB VEND FLAG ‘P’ for vend pending while the vending machine is dispensing the goods and or services. An MDB VEND FLAG ‘V for vended or ‘F’ for vend failed will indicate the conclusion of a vending cycle, upon vend success completion or vend attempt failed respectively. Thecomputing platform 802 can read the MDB TRANSACTION STRING and take the appropriate actions including sending the @<esc>C command to clear the MDB TRANSACTION STRING to prepare for the next vend cycle. - Referring to
FIG. 21 there is shown a MDB TRANSACTION STRING updating routine 2100. Processing begins inblock 2102. - In
block 2102 the MDB TRANSACTION string is updated insystem 500 memory. As previously described the updating occurs based in part on data communications between thesystem 500 and thevending machine 402, wherein thevending machine 402 is interconnected to thesystem 500 by way of thevending machine 402 VMC and the vending equipment interfaces 506, 516, 518, and or 520. Processing then moves todecision block 2104. - In decision block 2104 a determination is made at the
system 500 as to whethercomputing platform 802 or application code running onmicrocontroller 502 is requesting the MDB TRANSACTION STRING by data communicating to the requesting destination. If the resultant is in the affirmative that is thecomputing platform 802 or application code running onmicrocontroller 502 is requesting the MDB TRANSACTION STRING, processing moves to block 2106. If the resultant is in the negative that is thecomputing platform 802 or application code running onmicrocontroller 502 is not requesting the MDB TRANSACTION STRING then processing moves to block 2108. - In
block 2106 the command received from thecomputing platform 802 or the application code is received and the MDB TRANSACTION STRING is data communicated to the requesting destination. Processing moves back toblock 2102. - In
block 2110 thesystem 500 parses the received command. The various commands can include the ‘@’, ‘#”, AAA’, and ‘BBB’ detailed herein. Processing then moves todecision block 2112. - In decision block 2112 a determination is made as to whether the command the system 500-received required an MDB command be data communicated to the
vending machine 402. If the resultant is in the affirmative that is the command received requires an MDB command be data communicated to the vending machine then processing moves block 2114. If the resultant is in the negative that is the command received does not require an MDB command be data communicated to the vending machine then processing moves back toblock 2102. - In
block 2114 the appropriate MDB command or command sequence (as defined in the NAMA MDB specification) is data communicated between thesystem 500 and the 15vending machine 402. Processing moves back toblock 2102. - In an exemplary embodiment when the MDB TRANSACTION STRING is data communicated. The result string will return;
-
- STX+[S]+[
xxxxxx Field # 1 6 bytes]+[xxxxxx Field # 2 6 bytes]+[xxxx Field # 3 4 bytes]+[F]+ETX+LRC
- STX+[S]+[
- Where ‘xxx . . . ’ denotes fixed length fields. These fields should be right justified and have leading zeros added to fix the length of each field. For example $1.50 should e 25 represented as 000150.
- The ‘S’ field is the state current MDB VEND STATE field. Valid states include:
-
Valid Vending States State Description I Inactive D Disable E Enabled S In Session V Vend
Field # 1 is the MAX VEND PRICE as reported by the vending machine controller (VMC) during the MDB initialization process. The MAX VEND PRICE is the value of the highest priced item in the vending machine as reported by the vending equipment during an MDB initialization process. This can be a 6 byte field.
Field # 2 is the SALE PRICE. The SALE PRICE is determined in the MDB protocol for the VEND-Request Command (See. Multi Drop Bus (MDB)/Internal Protocol Version 1.0 and 2.0 specification). The SALE PRICE is the vend sale price of the vend item as reported by the vending equipment during an MDB vend request transaction.
Field # 3 is the COLUMN information. The COLUMN information is determined in the MDB protocol for the VEND-Request Command (See. Multi Drop Bus (MDB)/Internal Protocol Version 1.0 and 2.0 specification). The column identification of the vend item as reported by the vending equipment during an MDB vend request transaction.
The ‘F’ field is the MDB TRANSACTION CONDITION FLAG or VEND FLAG field. Valid flag states include: -
MDB TRANSACTION CONDITION FLAG; or VEND FLAG field State Description C Clear $ Currency vend has occurred P Vend Pending A Vend Approved D Vend Declined V Cashless vend has occurred u. USER SELECTED AMOUNT R REQUEST VEND APPROVE F Vend fail - The ‘C flag is set when the MDB TRANSACTION STRING is cleared. The ‘$’ flag is set when a VEND CASH MDB transaction occurs. The ‘P’ flag is set when a VEND-APPROVED MDB command is issued and remains valid until the VEND SUCCESSFUL or VEND FAIL MDB command is issued. The ‘F’ flag is set when a VEND FAILS.
- The ‘A’, ‘D’ and ‘R’ state flags are only valid when the G4 (system 500) is in the VEND ASSIST MODE (VEND ASSIST MODE=‘ON’ (TRUE)). In the VEND ASSIST MODE=‘OFF’ (FALSE) the VEND APPROVED response will automatically be issued to the VMC upon receiving the VEND REQUEST MDB command. When the G4 is in the VEND ACTIVE MODE=‘ON’ (TRUE) and the VEND ASSIST MODE=15 ‘OFF’ (FALSE) the ‘A’, ‘D’, and ‘R’ state flags will not appear and are not valid state conditions.
- The ‘R’ flag state will appear when the VEND ASSIST MODE=‘ON’. In this regard, when the MDB VEND REQUEST command is received (MDB interface applications) or the transaction is approved (BILL PULSE and BILL SERIAL applications) the MDB flag state will be changed to ‘R’ REQUEST VEND APPROVE. To complete the transaction the @<esc>A+STX+SALE command must be sent. Sale amount can range from $0.00 to $99.99 and is formatted as five numeric characters with no decimal point. For example $99.99 is sent as ‘09999’.
-
-
- STX+[E0001500000000000C]+ETX+LRC->Enabled, MAX Vend price $1.50, transaction string in cleared state
- STX+[SOOO 1500000000000C+ETX+LRC->In session, MAX Vend price $1.50, transaction string in cleared state
- STX+[V0001500001000002P]+ETX+LRC->Vend state, MAX Vend price
- $1.50, sale price $1.00, vend from
column 2, vend pending STX+[E0001500001000002V]+ETX+LRC->Enable state, MAX Vend price $1.50, sale price $1.00, vend fromcolumn 2, vend complete STX+[EOOO1500001250003$]+ETX+LRC->Enable state, MAX Vend price $1.50, sale price $1.25, vend fromcolumn 3, currency vend
NOTE: (If you are not using un MDB interface this may not apply) The MDB microcontroller/G4 MDB interface will continuously manage the changes to the MDB TRANSACTION STRING. For example, as the MDB state changes theMDB state field 25 will automatically be updated. There are however two scenarios that require the execution of the @<esc>C—CLEAR MDB TRANSACTION STRING DATA command. These two scenarios include when a currency vend has occurred and the ‘F’ field has been set to ‘$’, and when a cashless vend has occurred and the ‘F’ field has been set to ‘V’ or ‘F’. In both these cases the @<esc>C command will have to executed to clear the MDB TRANSACTION STRING before a new cash transaction can be tracked or a new cashless vending session can be started.
- If the G4 is used in the VEND ACTIVE ‘ON’ mode the above does not apply in that the G4 will clear the MDB TRANSACTION string as appropriate. If the G4 is used in the G4 VEND ACTIVE ‘OFF’ mode the above will apply.
- @<esc>C—CLEAR MDB TRANSACTION STRING DATA. The MDB controller/G4 will clear the SALE PRICE field, COLUMN information field, and the transaction condition flag is set to ‘C. The result string will return:
-
- STX+[OK-C]+ETX+LRC
<esc>H—HYBRID COMMAND FOR SEND CARD DATA AND MDB STRING. The MDB controller/G4 will send both the card reader data (see @<esc>T above) followed by the MDB string (see @<esc>V). The result string will return:
STX+[@<esc>T response]+ETX_LRC+STX+[@<esc>V RESPONSE]+ETX+LRC
STX+[@<esc>T response]+ETX+LRC+STX+[@<esc>V RESPONSE]+ETX+LRC
@<esc>S—BEGIN A SESSION COMMAND. The MDB controller/G4 will begin an MDB session (see NAMA MDB specification V1.0, V2.0 for BEGIN SESSION command). The result string will return; - STX+[oK-S]+ETX+LRC
The G4 must have the MDB state set to for ENABLED in order to start a session. If a session cannot be started the result string will return; - STX+[UNABLE-S]+ETX+LRC
@<esc>X—END A SESSION COMMAND. The MDB controller/G4 will END an MDB session (see NAM A MDB specification V1.0, V2.0 for SESSION CANCEL command). The result string will return; - STX+[OK-X]+ETX+LRC
@<esc>F—SET MDB CONTROLLER STATE TO INACTIVE. The MDB controller/G4 will set the MDB state to INACTIVE. The result sting will return: - STX+[OK-F]+ETX+LRC
@<esc>D—SET MDB CONTROLLER STATE TO DISABLE. The MDB controller/G4 will set the MDB state to DISABLE. The result sting will return: - STX+[OK-D]+ETX+LRC
@<esc>E—SET MDB CONTROLLER STATE TO ENABLE. The MDB controller/G4 will set the MDB state to ENABLE. The result sting will return; - STX+[OK-E]+ETX+LRC
@<esc>K—PERFORM A HARDWARE MDB CONTROLLER RESET. The MDB controller/G4 will return the result string and then go through a hardware reset. The result string will return: - STX+[OK-K]+ETX+LRC
@<esc>I—TOGGLE MDB INTERRUPT MODE. The MDB controller/G4 will return the result string below toggling between ‘ON’ and ‘OFF’ of the interrupt mode. - STX+[ON-I]+ETX+LRC->When toggling into the interrupt mode STX+[OFF-I]+ETX+LRC->When toggling out of the interrupt mode
@<esc>I—turns mode ‘ON’
- STX+[OK-C]+ETX+LRC
- STX+[ON-I]+ETX+LRC->When toggling into the interrupt mode
- @<esc>i—turns mode ‘OFF’
- STX+[OFF-I]+ETX+LRC->When toggling out of the interrupt mode
- While in the interrupt mode the MDB controller/G4 will send the result string for the @<esc>T and the @<esc>V commands shown above each time the respective data fields change.
For example, while in the interrupt mode the MDB controller/G4 will send the @<esc>T result string on the successful read of a magnetic card.
In addition, while in the interrupt mode the MDB controller/G4 will send the @<esc>V result string each time any field in the MDB TRANSACTION STRING changes.
<esc>1—TOGGLE MDB CODE CAPTURE MODE. The MDB controller/G4 will return the result string below toggling between ‘ON’ and ‘OFF’ of the MDB CODE CAPTURE mode. This command is for diagnostic purposes only and should not be used during normal G4 operation. The intended purpose for this command is to diagnosis MDB related transaction issues during development and or testing.
STX+[0N-1]+ETX+LRC->When toggling into the MDB code capture mode.
STX+[OFF-1]+ETX+LRC->When toggling out of the MDB code capture mode
When the MDB code capture mode is switched to the ‘ON’ mode the following sequence of events begins: - The RAM/NOVRAM memory dedicated to the storage of vending transactions is cleared. All data (transactions) currently being stored will be erased to make room for the MDB bus codes.
- The G4 will begin recording both the received MDB codes from the vending machine controller (VMC) and the sent MDB codes from the G4. There is RAM room for approximately 15 seconds of recording time.
- When the MDB code capture mode is switched to the ‘OFF’ mode the G4 will stop recording the MDB bus codes. A buffer dump of the MDB codes exchanged between the G4 and the VMC can be viewed by executing @<esc>2 the MDB CAPTURED CODE BUFFER DUMP command.
- NOTE: When you are ready to return the G4 system to the normal operation mode you should I) insure that the MDB CODE CAPTURE mode is ‘OFF’ and 2) Execute the @<esc>J CLEAR MAIN MEMORY command to clear and reset the G4 main memory. The CLEAR MAIN MEMORY command is important in that the MDB codes captured are stored in the RAM/NOVRAM area and may interfere with the G4 normal record management procedures.
- In addition, when the MDB capture mode is switched to ‘ON’ the G4 will stay in this state until either 1) the buffer area for MDB codes is filled (about 15 seconds) or 2) the MDB capture mode is switched to ‘OFF’. Even if the G4 is powered ‘OFF’ or the @<esc> K HARDWARE RESET command is issued the MDB capture mode state will not change. The reason for this is to allow the MDB capture mode to be turned ‘ON” and remain ‘ON’ capturing MDB transaction codes between the vending machine and the G4 while the vending machine and or G4 go through a power up or reset procedure.
- If the G4 is in a vending transaction the TOGGLE MDB CODE CAPTURE MODE command cannot be executed to turn ‘ON’ the MDB capture feature. If the TOGGLE MDB CODE CAPTURE MODE command is executed during a vending session the MDB capture mode will be turned ‘OFF’ and the result string will return;
-
- S TX+[OFF-1]+ETX+LRC
@<esc>2—MDB CAPTURE MODE BUFFER DUMP. The MDB controller/G4 will return the result string below dumping the MDB codes passed between the G4 and the vending machine controller (VMC). The output will be formatted to indicate which codes were transmitted by the VMC and which codes were transmitted by the G4. This command is for diagnostic purposes only and should not be used during normal G4 operation. The intended purpose for this command is to diagnosis MDB related transaction issues during development and or testing.
- S TX+[OFF-1]+ETX+LRC
-
STX+[MDB]+ -> Header [VMC-1+VMC -> Data transmitted by the VMC [G4 −]+G4 transmitted data − transmitted data -> Data transmitted by the G4 ETX+LRC
@<esc>Y—TOGGLE G4 VEND ACTIVE MODE ON/OFF. The G4 can operate in two modes of operation. In the VEND ACTIVE ‘ON’ mode of operation the G4 provides all the MDB interface control, audit/cashless payment support, and network connectivity. In this mode a computing platform can interact with the G4 in a hybrid role to monitor a string of user text prompts (see DISPLAY PROTOCOL) as well as execute the NON-MDB-CONTROL and some MDB-CONTROL commands. - In the VEND ACTIVE ‘OFF’ mode of operation the G4 can be configured and serve as an MDB controller only. In this mode both the MDB-CONTROL and NON-MDB-CONTROL commands can be executed. While in this mode of operation the computing platform operates as a master device controlling the operation and process flow of the system, and the G4 serves as a slave device interfacing to the vending 15 machine and managing the control of the MDB interface. The result string will return;
- STX+[ON-R]+ETX+LRC->When toggling into the VEND ACTIVE mode.
- STX+[OFF-R]+ETX-LRC->When toggling out of the VEND ACTIVE mode
- @<esc>Y—turns mode ‘ON’
- STX+[ON-R]+ETX+LRC->When toggling into the VEND ACTIVE mode.
- @<esc>y—turns mode ‘OFF’
- STX+[OFF-R]+ETX+LRC->When toggling out of the VEND ACTIVE mode
- #<esc>R—TOGGLE G4 VEND ASSIST MODE ON/OFF. The G4 can operate in two vending modes of operation (while the VEND ACTIVE mode is ‘OFF’). In the VEND ASSIST ‘ON’ mode of operation the G4 will set the VEND REQUEST state flag in the MDB TRANSACTION STRING-VEND FLAG field when the G4 receives the VEND REQUEST MDB command from the vending machine's VMC. It is then the responsibility of the attached computing platform to issue either the @<esc>A+SALE-[xxxxx] command to approve the vend and provide the sale amount, or the #<esc>Q command to DECLINE the vend, referred to as VEND DENY the vend. The MDB TRANSACTION STRING should be monitored to determine when the ‘R’ VEND REQUEST state is set. After the determination that the REQUEST VEND APPROVE state is set the VEND APPROVED or VEND DECLINED command should be executed.
- In the VEND ASSIST ‘OFF’ mode of operation the G4 will automatically provide the VEND APPROVED response to the vending machine's VMC when the VEND REQUEST command is received from the VMC. The result string will return:
- STX+[ON-R]+ETX+LRC->When toggling into the VEND AS SIST mode.
- STX+[OFF-R]+ETX+LRC->When toggling out of the VEND ASSIST mode
- #<esc>R—turns mode ‘ON’
- STX+[ON-R]+ETX+LRC->When toggling into the VEND ASSIST mode.
- #<esc>r—turns mode ‘OFF’
-
- STX+[OFF-R]+ETX+LRC->When toggling out of the VEND ASSIST mode
Default: The default condition on microcontroller reset is ‘OFF’
@<esc>$—SIMULATE CASH VEND TRANSACTION. The G4 will simulate a CASH VEND transaction (see MDB spec V1.0 for CASH VEND command). The result sting will return: - STX+[OK-$]+ETX+LRC
To simulate the CASH VEND the MDB TRANSACTION STRING will be set to the following: - STX+[E0005000001250001S]+ETX+LRC
- STX+[OFF-R]+ETX+LRC->When toggling out of the VEND ASSIST mode
- If the G4 is in a vending transaction a SIMULATE CASH VEND transaction cannot be executed. If a SIMULATE CASH VEND transaction cannot be executed the result string will return:
-
- STX+[UNABLE-$]+ETX+LRC
@<esc>#—SIMULATE CASHLESS VEND TRANSACTION. The G4 will simulate a CURRENCY VEND transaction (see NAMA MDB spec V1.0 and V2.0 for VEND REQUEST and VEND APPROVED commands). The result sting will return; - STX+[OK-#]++ETX+LRC
To simulate the CASHLESS VEND the MDB TRANSACTION STRING will be set to the following: - STX+[E0005000001250001V]+ETX+LRC
- STX+[UNABLE-$]+ETX+LRC
- If the G4 is in not in a vending transaction a SIMULATE CASHLESS VEND transaction cannot be executed. If a SIMULATE CASHLESS VEND transaction cannot be executed the result string will return:
-
- STX+[UNABLE-#]+ETX+LRC
@<esc>M—TOGGLE MODEM COMMUNICATION ACCESS. The G4 will switch the serial communication ports being utilized by the computing platform to the MDB controller/G4 communication port. In this regard, the computing platform can utilize the communication port (modem and or wireless) of the MDB controller/G4. The result sting will return: - STX+[ON-M]+ETX+LRC->When toggling into the communication mode-allowing the computing platform to use the MDB controller/G4 communication port. A communication hardware reset will also be invoked in the G4 to prepare the communication device to receive data.
- STX+[OFF-M]+ETX+LRC->When toggling out of the communication mode
NOTE: The communication parameters between the G4 are outlined above as 9600, no parity, 8 data bits, and 2 stop bits. Upon executing the @<esc>M command ‘ON’ the G4 switches direct access to the communication device. If for example, a 2400 baud modem is being used the device issuing the @<esc>M command will have to first change its baud rate to 2400 before the G4 modem can respond to the requests. Furthermore, upon the conclusion of a communication session before the @<esc>M command can be issued and interpreted by the G4 to switch the communications ‘OFF’ the baud rate of the device issuing the @<esc>M command should change its baud rate back to 9600 N, 8, 2.
@<esc>Q—SEND CURRENT TRANSACTION RECORD. The G4 will return the current transaction record. The current transaction record is a fixed length record. The parsed fields are listed below. The result sting will return: - STX+[RECORD NUMBER-TRANSACTION RECORD]+ETX+LRC
- STX+[UNABLE-#]+ETX+LRC
- If the G4 is not in a vending transaction a SEND CURRENT TRANSACTION RECORD transaction cannot be executed. If a SEND CURRENT TRANSACTION RECORD transaction cannot be executed the result string will return;
-
- STX+[UNABLE-Q]+ETX+LRC
Where the parsed [record number-transaction record] fields are as follows:
- STX+[UNABLE-Q]+ETX+LRC
-
Transaction Record Format RECORD TYPE BYTES DESCRIPTION RECORD NUMBER 4 bytes Current transaction record number SEPARATOR 1 byte Field separator CARD DATA/ID DATA 37 bytes Card data or Dial-A-Vend data MERCHANT ID 1 byte Merchant ID Prefix (G4 specific typically set to ‘1’) REFERENCE SALE AMOUNT 5 bytes Transaction sale amount APPROVAL CODE 8 bytes Transaction approval code (typically starts with AP) CAPTURE ID FLAG 1 byte Transaction Capture Flag/Transaction ID 0 = 00 NOT CAPTURE TRANSACTION 1 = CREDIT CARD TRANSACTION 2 = SETTLEMENT DATA 3 = ERROR RECORD 4 = SETTLED CREDIT CARD TRANSACTION 5 = PRIVATE SYSTEM TRANSACTIONS 6 = NOT USED 7 = EMAIL TRANSACTION START TIME 8 bytes Transaction Start Date and Time (MMDDHHMM) COUNT 1 4 bytes Event counter #1 i.e. copy or print count (XXXX) STOP TIME 8 bytes Transaction Stop Date and Time (MMDDHHMM) COUNT 2 4 bytes Event counter #2 i.e. copy or print count (XXXX) INVENTORY TOTAL 2 bytes Total vended inventory count ITEM COLUMN 1 2 bytes Vended item #1 column data ITEM COLUMN 2 2 bytes Vended item #2 column data ITEM COLUMN 3 2 bytes Vended item #3 column data ITEM COLUMN 4 2 bytes Vended item #4 column data ITEM COLUMN 5 2 bytes Vended item #5 column data ITEM COLUMN 6 2 bytes Vended item #6 column data ITEM COLUMN 7 2 bytes Vended item #7 column data ITEM COLUMN 8: 2 bytes Vended item #8 column data ITEM COLUMN 9 2 bytes Vended item #9 column data ITEM COLUMN 10 2 bytes Vended item #10 column data SPARE DATA 2 bytes Not Implemented LRC CHECK BYTE 1 byte LRC check byte
@<esc>W—SEND ALL TRANSACTION RECORD. The MDB controller/G4 will return all the transaction records beginning with 0000. The G4 will return the message ‘DONE’ when complete. The transaction records are a fixed length records and follow the format shown above in the @<esc>Q command. The result sting will return: -
STX+[0000-TRANSACTION RECORD]+ETX+LRC ... ... ... STX+[xxxx-TRANSACTION RECORD]+ETX+LRC DONE - Where ‘0000’ is the first transaction record and ‘xxxx’ is the last transaction record.
- If the G4 is in a vending transaction a SEND ALL TRANSACTION RECORD transaction cannot be executed. If a SEND ALL TRANSACTION RECORD transaction cannot be executed the result string will return:
-
- STX+[UNABLE-W]+ETX+LRC
@<esc>R—TOGGLE VERBOSE TEXT PROMPTS ON/OFF. The G4 will switch between providing a stream of text prompts (see DISPLAY PROTOCOL) when the VERBOSE mode is turned ‘ON’ and disabling the transmission of the text prompts when the VERBOSE mode is ‘OFF’. The result sting will return: - STX+[ON-R]+ETX+LRC->When toggling into the VERBOSE mode.
- STX+[OFF-R]+ETX+LRC->When toggling out of the VERBOSE mode
- STX+[UNABLE-W]+ETX+LRC
- @<esc>R-turns mode ‘ON’
-
- STX+[ON-R]+ETX+LRC->When toggling into the VERBOSE mode.
- @<esc>r—turns mode ‘OFF’
-
- STX+[OFF-R]+ETX+LRC->When toggling out of the VERBOSE mode
- @<esc>U—RETURN TO DEFAULT CONDITIONS. The G4 will return all settings to the power on/system reset default condition. The result sting will return;
- STX+[OK-U]+ETX+LRC
- Reset Default Conditions Include:
- INTERRUPT MODE=OFF’
- VERBOSE MODE=‘ON’
- VEND ACTIVE MODE=‘ON’
- VEND ASSIST MODE=‘OFF’
@<esc>P—RETURN G4 TIME AND DATE STAMP. The G4 will return the current time and date. The time and date are set by the USALIVE (host network center 808) server each time the G4 communicates with the network servers. The result sting will return:
- STX+[TIME-HHMMSS-MMDDYY]+ETX+LRC
Where ‘HHMMSS’ is the current hour, minute, and seconds, and ‘MMDDYY’ is the current month, day, and year. - @<esc>G—PRINT A TEST RECEIPT FOR CURRENT TRANSACTION. The G4 will internally call the print receipt routine to print a test receipt. The result sting will return:
- STX+[OK-G]-ETX+LRC
@<esc>J—CLEAR MAIN MEMORY TRANSACTIONS. The G4 main memory will be cleared. The result sting will return:
- STX+[OK-G]-ETX+LRC
- STX+[OK-J]+ETX+LRC
@<esc>N—FIND A BLANK RECORD. The G4 finds and sets active the next available blank transaction record. The result string will return: - STX+[OK-N]+ETX+LRC
- The G4 must have the MDB state set to ‘E’ for ENABLED in order to find a blank record. A new record cannot be started while in a vending transaction. If a FIND BLANK RECORD command cannot execute the result string will return:
-
- STX+[UNABLE-N]+ETX+LRC
@<esc>B—START A VEND SESSION. Provided the G4 VEND ACTIVE ‘ON’ mode is set, the G4 will start a vend session. The sequence to starting a vend session includes: - 1. G4 finds the next available blank transaction record
- 2. G4 loads the default data into the transaction record
- 3. G4 loads as the CARD DATA/ID DATA->‘G4-VEND’
- 4. G4 issues the BEGIN SESSION command to the MDB interface.
- The result string will return:
- STX+[OK-B]+ETX+LRC
The G4 must have the MDB state set to ‘E’ for ENABLED in order to start a session. If a session cannot be started the result string will return:
- STX+[OK-B]+ETX+LRC
- STX+[UNABLE-B]+ETX+LRC
@<esc>A+STX+DIAL-+[ID DATA Up to 30 bytes]+ETX+LRC—START A DIAL-A-VEND SESSION. Provided the G4 VEND ACTIVE ‘ON’ mode is set, the G4 will start a vend session. The sequence to starting a vend session includes: - 1. G4 finds the next available blank transaction record,
- 2. G4 loads the default data into the transaction record,
- 3. G4 loads as the CARD DATA/ID DATA the ‘[DV-DIAL-MID DATA Up to 30 bytes]’ sent as part of the command.
- 4. G4 issues the BEGIN SESSION command to the MDB interface.
The result string will return: - STX+[OK-A]+ETX+LRC
- STX+[UNABLE-N]+ETX+LRC
- The G4 must have the MDB state set to ‘E’ for ENABLED in order to start a dial-a-vend vending transaction. A new vending transaction cannot be started while in a vending transaction. If a dial-a-vend command cannot be executed the result string will return:
-
- STX+[UNABLE-A]+ETX+LRC
If the LRC character does not match, or the correct ETX+LRC combination does not occur at all or in a timely fashion the result string will return: - STX+[NAK-A]+ETX+LRC
@esc>A+STX+CARD-+[UP TO 37BYTE TRACK 2 DATA]+ETX+LRC—START A CASHLESS TRANSACTION OR CREDIT CARD TRANSACTION.
Provided the G4 VEND ACTIVE ‘ON’ mode is set, the G4 will start a vend session. The sequence to starting a vend session includes: - 1. G4 finds the next available blank transaction record,
- 2. G4 loads the default data into the transaction record,
- 3. G4 loads as the CARD DAT A/ID DATA the ‘[CREDIT CARD DATA Up to 37 bytes]’ sent as part of the command.
- 4. Upon credit card APPROVAL the G4 issues the BEGIN SESSION command to the MDB interface.
- The result string will return:
- STX+[OK-A]+ETX+LRC
- STX+[UNABLE-A]+ETX+LRC
- The G4 must have the MDB state set to ‘E’ for ENABLED in order to start a vending transaction, A new vending transaction cannot be started while in a vending transaction. If a credit card command cannot be executed the result string will return:
-
- STX+[UNABLE-A]+ETX+LRC
- If the LRC character does not match, or the correct ETX+LRC combination does not occur at all or in a timely fashion the result string will return:
-
- STX+[NAK-A]+ETX+LRC
@<esc>A+STX+SALE-+[5 BYTES OF DATA]+ETX+LRC—The VEND APPROVED command has two modes of operation. If the vender interface is set to MDB INTERFACE only the ‘R’ REQUEST VEND APPROVAL mode is supported. That is the G4 is connected to vending equipment by way of the MDB INTERFACE connector and the firmware select is the MDB INTERFACE and the VEND ASSIST MODE=‘ON’.
- STX+[NAK-A]+ETX+LRC
- If the vending interface is set to the BILL PULSE INTERFACE or the BILL SERIAL INTERFACE the ‘R’ REQUEST VEND MODE and the ‘U’ USER SELECTED AMOUNT MODES are supported. That is the G4 is not connected to vending equipment by way of the MDB INTERFACE connector and the firmware select is set to either the BILL SERIAL INTERFACE or the BILL PULSE INTERFACE then the VEND APPROVED command operates as described above when the VEND ASSIST MODE=‘ON’.
- ‘R’-REQUEST VEND APPROVE MODE—The VEND APPROVE response should be sent in response to the MDB TRANSACTION STRING indicating the ‘R’ REQUEST VEND APPROVE flag state. The ‘R’ REQUEST VEND APPROVE flag state is set when the VMC sends the G4 the VEND REQUEST MDB command and the VEND ASSIST MODE-‘ON’. The data bytes should be in the form ‘00000’ and should be the desired amount for the G4 to charge for the vended item. The VMC will report by way of the MDB TRANSACTION STRING the price and column of the vended item requested, in accordance with the MDB transactions formatting. The price reported would be the value of the item as set in the vending machine. If a charge equal to the vending machines reported price is desired, 15 for example ‘00125’ for $1.25, then the correct VEND APPROVED response should be as follows:
-
- <esc>A+STX+S ALE-00125+ETX+LRC
- If a different price is to be charged for the item the VEND APPROVED response can be altered. For example:
-
- @<esc>A+STX+SALE-00000+ETX+LRC—For a free vend $0.00
- @<esc>A+STX+SALE-00300+ETX+LRC—For a $3.00
- @<esc>A+STX+S ALE-09999+ETX+LRC—For a $99.99
NOTE: In lieu of having to send the @<esc>A+STX+S ALE command as a VEND APPROVE response, a NON-RESPONSE format can also be implemented. In a NON-RESPONSE format not responding to asystem 500 REQUEST VEND APPROVE within a preset time period can be interpreted as VEND APPROVE with a sale amount of the MDB TRANSACTION STRING-SALE PRICE amount. In this regard, the MDB TRANSACTION STRING-SALE PRICE amount is typically the sale price reported by the vending equipment when a user makes a selection and a MDB VEND REQUEST is generated.
‘U’-USER SELECTED AMOUNT—To start a vending session in the BILL SERIAL INTERFACE or BILL PULSE INTERFACE configurations the VEND APPROVED command can be used to select a USER amount (The amount to charge the user). Successive VEND APPROVED commands can be issued to change the USER SELECTED AMOUNT. In this regard, the MDB TRANSACTION STRING will reflect the VEND SALE AMOUNT and the VEND FLAG field state will be set to ‘U’. This indicates that a transaction amount has been selected. Provided the INHIBIT pin is enabled (LOW STATE) the G4 will now accept a card for payment. If or when the card is approved the ‘U’ VEND FLAG field state will change to ‘R’ REQUEST VEND APPROVAL if the VEND ASSIST MODE ̂‘ON’. If the VEND ASSIST MODE=‘OFF” then upon transaction approval the vend will be completed.
- If the G4 terminal is connected to a BILL SERIAL INTERFACE or BILL PULSE INTERFACE upon card approval and or REQUEST VEND APPROVE the users selected amount will be transferred via the bill interface or vending equipment interface and the sale amount of the transaction adjusted accordingly. If the G4 is configured such that no connection is made to the BILL interface connector then consideration should be given to either providing a control signal to the INHIBIT line to enable and disable the terminal accordingly or jumping GND to INHIBIT to enable the G4 terminal. The range of the sale amount can be from $0.00 formatted as ‘00000’ to $99.99 formatted as ‘09999’. Other sales ranges can be implemented.
- The G4 will issue the VEND APPROVED MDB command to the VMC and the MDB TRANSACTION STRING will be updated as appropriate. The G4 will return the result string:
-
- STX+[OK-A]+ETX+LRC
@<esc>A+STX+VIEW-+[‘M’ 1 BYTE MEMORY CODE]+[‘xxxxxxxx’ 8 BYTES MEMORY LOCATION]+ETX+LRC—The MEMORY VIEW command provides a means for requesting and obtaining current memory values from the G4 terminal. The 1 byte MEMORY CODE selects the memory device to return the value from. Valid MEMORY CODES are shown in the table below. The eight byte hexadecimal value that represents the MEMORY LOCATION is the physical address in memory to be viewed. The MEMORY VALUE returned in the result code is the value currently store, in the MEMORY LOCATION.
- STX+[OK-A]+ETX+LRC
- The table below indicates the valid MEMORY CODES and a description of which device each code access.
-
MEMORY CODE Memory device description A EEROM upper word byte B EEROM lower word byte C Main flash memory (Application Code) D Main RAM memory - @<esc>A+STX+VIEW-AOOOOOOC1+ETX+LRC will return the value stored in the EEROM upper byte of address $C1.
- The G4 will return the result string and I byte memory value as follows:
-
- STX+[OK-A-]+[‘x’ 1 BYTE MEMORY VALUE]+ETX+LRC
@<esC>A+STX+SAVE-+[<M’ 1 BYTE MEMORY CODE]+[‘xxxxxxxx’ 8 BYTES MEMORY LOCATION]+[<x’ 1 BYTE OF DATA]+ETX+LRC—The MEMORY SAVE command provides a means for writing data into the G4 memory. The 1 byte MEMORY CODE selects the memory device to write the DATA. Vand MEMORY CODES are shown in the table above. The eight byte hexadecimal value that represents the MEMORY LOCATION is the physical address in memory to be written. The MEMORY VALUE returned in the result code is the value currently stored in the MEMORY LOCATION—if the write was successful the value returned should be the same as the intended byte of DATA to be written.
- STX+[OK-A-]+[‘x’ 1 BYTE MEMORY VALUE]+ETX+LRC
-
-
- @<esc>A+STX+S AVE-AOOOOOOC 1FF+ETX+LRC
will write the hex value $FF to the EEROM upper byte address location $C1.
The G4 will return the result string and 1 byte memory value as follows: - STX+[OK-A-]+[
V 1 BYTE MEMORY VALUE]+ETX+LRC
* note if the write was successful the BYTE MEMORY VALUE should be $FF—the byte that was desired to be written to memory.
@<esc>A+STX+DISP-+[1BYTE LCD LINE (‘1’ or ‘2’)]+[UP TO ‘xxxxxxxxxxxxxxxx’ 16 BYTES OF DATA]+ETX+LRC—The display command allows data to be written to the G4 auxiliary display board, such as card readerinterface processor board 312. Electrically a card reader assembly having a card reader, display board and optional printer can be plugged into the G4-epott auxiliary printer port, such a board can be card readerinterface processor board 312. In this regard when the display command is executed data is sent out the printer port to the attached card reader assembly. In addition to providing 2 lines of 16 character alphanumeric text a series of card reader assembly control codes are available. The card reader assembly (card reader 15 interface processor board 312) control codes (shown below) enable control of the LED on the face of the card reader and transaction button, beep the beeper, clear the screen, and control print functionality, among other things.
- @<esc>A+STX+S AVE-AOOOOOOC 1FF+ETX+LRC
-
Table of Card Reader Control Codes CARD READER CONTROL CODES (hex) $0E + $0E + $0E Beep Beeper $0D + $0D + $0D Indicates print data is to follow (start print data) $0C + $0C + $0C indicates print data is concluded (end print data) $0B + $0B + $0B Turn ‘ON’ - blink transaction button LED $0A + $0A + $0A Turn ‘OFF’ transaction button LED $09 + $09 + $09 Clear LCD display screen $08 + $08 + $08 Turn ‘ON’ card reader LED $07 + $07 + $07 Turn ‘OFF’ card reader LED - To issue a control command to the card reader assembly the appropriate code must be sent successive at least three character in a row. For example to beep the beeper the following display command can be issued:
-
- @<esc>A+STX+DISP-1+$OE+$OE+$OE+ETX+LRC
To display ‘Sample Message 1’ text ofline 1 of the LCD display the following display command, can be issued: - @<esc>A+STX+DISP-1+
Sample Message 1+ETX+LRC
To display ‘Message Line 2’ text ofline 2 of the LCD display the following display command can be issued: - @<esc>A+STX+DISP-2+
Message Line 2+ETX+LRC
In each case the result string will return: - STX+[OK-A]+ETX+LRC
NOTE: When the card reader assembly is first powered up the current version of software running on the display card will appear on the LCD display. The LCD will not display any text until a display line of text is written toline 1. More specifically the display board is initialized upon receipt of the $80 character that is part of theline 1 formatting. Until the $80 character is received the card reader display codes will operate but no text writes toLCD line 2 will be displayed. Consideration should be given to writing a line of text (or blank spaces) toLCD line 1 with the DISP-1 display command to initialize the display board after power-up.
@<esc>L—REQUEST US ALIVE SETTING DATA. The G4 will return a string of USALIVE setting data. USALIVE setting data can be referred to assystem 500 terminal management data. USALIVE can be referred to as thehost network center 808. The USALIVE setting data includes terminal configuration, setting, and parameter data maintained on the USALIVE network and passed to the terminal each time the terminal 10 communicates to the USALIVE network. USALIVE setting data can include transaction data. Changes to the data are managed on the server. The result sting will return: - STX+[START-]+[USALIVE SETTING DATA]+[-END]+ETX+LRC
@<esc>3—DEX CODE CAPTURE MODE (FULL FORMAT). The DEX controller/G4 will return the result string below toggling between ‘ON’ and ‘OFF’ of the DEX CODE CAPTURE mode. This command is for diagnostic purposes only and should not be used during normal. G4 operation. The intended purpose for this command is to diagnosis DEX related transaction issues during development and or testing. The @<esc>3 command obtains DEX data in a free format capturing the handshake and protocol exchanges (ACK, NAK, DLL, etc.) in addition to the DEX data. At the conclusion of the DEX data transfer the DEX CAPTURE MODE is automatically toggled ‘OFF’. In most cases there will be no need to execute a second @<esc>3 command to toggle the DEX mode ‘OFF’. - STX+[ON-3]+ETX+LRC->When toggling into the DEX code capture mode
- STX+[OFF-3]+ETX+LRC->When toggling out of the DEX code capture mode
When the DEX code capture mode is switched to the ‘ON’ mode the following sequence of events begins:
The RAM/NO VRAM memory dedicated to the storage of DEX data is cleared.
- @<esc>A+STX+DISP-1+$OE+$OE+$OE+ETX+LRC
- The G4 will begin recording both the received DEX codes from the vending machine controller (VMC) and the sent DEX codes from the G4. There is RAM room for approximately 6K bytes of recorded DEX data.
- When the DEX code capture mode is switched to the ‘OFF’ mode or automatically switches to the ‘OFF’ mode at the end of the DEX transfer the G4 will stop recording the DEX bus codes. A buffer dump of the DEX codes exchanged between the G4 and the VMC can be viewed by executing the @<esc>5 the DEX CAPTURED CODE B UFFER DUMP command.
- @<esc>4—DEX CODE CAPTURE MODE (PARSED FORMAT). The DEX controller/G4 will return the result string below toggling between ON and ‘OFF’ of the DEX CODE CAPTURE mode. This command is for diagnostic purposes only and should not be used during normal G4 operation. The intended purpose for this command is to diagnosis DEX related transaction issues during development and or testing. The @<esc>4 command obtains DEX data in a parsed, pure format (free from all handshake and protocol exchanges (ACK, NAK, DLE, etc.)). At the conclusion of the DEX data transfer the DEX CAPTURE MODE is automatically toggled ‘OFF’. In most cases there 25 will be no need to execute a second @<esc>4 command to toggle the DEX mode ‘OFF’.
-
- STX+[ON-4]+ETX+LRC->When toggling into the DEX code capture mode
- STX+[OFF-4]+ETX+LRC->When toggling out of the DEX code capture mode
When the DEX code capture mode is switched to the ‘ON’ mode the following sequence of events begins:
The RAM/NO VRAM memory dedicated to the storage of DEX data is cleared.
- The G4 will begin recording both the received DEX codes from the vending machine controller (VMC) and the sent DEX codes from the G4. There is RAM room for approximately 6K bytes of recorded DEX data.
- When the DEX code capture mode is switched to the ‘OFF’ mode or automatically switches to the ‘OFF’ mode at the end of the DEX transfer the G4 will stop recording the DEX bus codes. A buffer dump of the DEX codes exchanged between the G4 and the VMC can be viewed by executing the @<esc>5 the DEX CAPTURED CODE BUFFER DUMP command.
- @<esc>5—DEX CAPTURE MODE BUFFER DUMP. The DEX controller/G4 will return the result string below dumping the DEX codes passed between the G4 and the vending machine controller (VMC). The output will be formatted to indicate the codes transmitted by the VMC and the G4. This command is for diagnostic purposes only and should not be used during normal G4 operation. The intended purpose for this command is to diagnosis DEX related transaction issues during development and or testing.
-
STX+[DEX]+ -> Header [VMC−]+VMC transmitted data - > Data transmitted by the VMC [G4 −]+G4 transmitted data -> Data transmitted by the G4 ... ETX+LRC - If DEX data is obtained with the @<esc>4 command the DEX data will be parsed to remove all handshake data and VMC/G4 protocol passing. The DEX data will be pure and presented in ASCII format. If the DEX data is obtained with the @<esc>3 command the DEX data will include all the handshaking data and VMC/G4 protocol passes (ACK, NAK, DLE, etc.).
- #<esc>C—ENTER SERVICE MODE ROUTINE—The G4 will return the following result string and then enter the service mode.
-
- STX+[OK-C]+ETX+LRC
#<esc>D—SYSTEM INITIALIZATION COMMAND—The G4 will return the following result string and then perform a system initialization sequence. - STX+[OK-D]+ETX+LRC
- STX+[OK-C]+ETX+LRC
- The system initialize sequence will clear memory and reload initial condition registers. The US ALIVE default phone number will be loaded into memory and the G4 will be placed in the CALL HOME mode. Before correct terminal operation can be restored the G4 will require communication with the USALIVE servers.
- #<esc>E—DISPLAY SERIAL NUMBER AND FIRMWARE VERSION—The G4 will return the following result string showing the G4 serial number and firmware version number.
-
- STX+[OK-E]+ETX+LRC
- Followed by the G4 serial number and firmware version number.
- #<esc>F—SET CALL HOME FLAG TRUE—INITIATE CALL HOME—The G4 CALL HOME flag will be set directing the terminal to begin a timer. The timer is a USALIVE setting that delays the call in process after the CALL HOME flag is set. The result code returned will be as follows:
-
- STX+[OK-F]ETX+LRC
The G4 will then in time attempt a communication to the USALIVE server.
#<esc>G—RETURN CURRENT STATE OF CALL HOME FLAG—The G4 will return the following result code indicating the current state of the CALL HOME flag. The states can be either TRUE or FALSE. TRUE indicating the G4 is preparing to place a call to the USALIVE servers. - STX+[TRUE-F]+ETX+LRC
- or . . .
- STX+[F ALSE-F]+ETX+LRC
#<esc>H-CLEAR THE CALL HOME FLAG-SET TO FALSE—The G4 will reset the CALL HOME flag to FALSE. The following result code will be returned. - STX+[OK-H]+ETX+LRC
- STX+[OK-F]ETX+LRC
- If the G4 terminal is experiencing a situation that under normal circumstance would trigger the G4 terminal to CALL HOME to the USALIVE servers, such as a DEX alarm condition is detected, or the G4 has a full memory of transactions the CALL HOME flag will automatically be set back to TRUE.
- #<esc>I—RETURNS THE CURRENT SERVICE STATE OF THE TERMINAL—The G4 will return the following result codes indicating the terminal’ is either IN or OUT of service at the present moment.
-
- STX+[IN-I]+ETX+LRC
- or . . .
- STX+[OUT-I]+ETX+LRC
#<esc>J—TOGGLES THE CURRENT SERVICE STATE (IN/OUT)—The G4 will toggle the current service state from either IN to OUT or from OUT to IN. The result-string returned will be as follows. - STX+[IN-J]+ETX+LRC
- or . . .
- STX+[OUT-J]+ETX+LRC
#<esc>K—SEND CURRENT LOCAL AUTHORIZATION RECORDS—The G4 will return the result string that includes the record number, last six digits of each card, and the ‘A’ or ‘D’ suffix indicating APPROVAL or DECLINED record data as follows: - STX+[xxxx-LAST SIX DIGITS OF CARD NUMBER-A or D]+ETX+LRC
- Where ‘xxxx’ is the current record number.
- #<esc>L—SEND COMPLETE LOCAL AUTHORIZATION DATABASE—The G4 will return the result string that includes the record number, last six digits of each card, and the ‘A’ suffix indicating APPROVAL record data as follows:
-
STX+Ixxxx-LAST SIX DIGITS OF CARD NUMBER-A or D]+ETX+ LRC ... ... ... STX+[yyyy-LAST SIX DIGITS OF CARD NUMBER-A or D]+ETX+ LRC DONE - Where ‘xxxx’ is the first record number and ‘yyyy’ is the last record number.
- #<esc>M—CLEAR DECLINED CARD PORTION OF LOCAL AUTHORIZATION DATABASE—The G4 terminal will clear the DECLINED card records in the LOCAL AUTHORIZATION DATABASE and return the following result code:
-
- STX+[OK-M]+ETX+LRC
#<esc>N—CLEAR APPROVAL CARD PORTION OF LOCAL AUTHORIZATION DATABASE—The G4 terminal will clear the APPROVAL card records in the LOCAL AUTHORIZATION DATABASE and return the following result code: - STX+[OK-N]+ETX+LRC
#<esc>0—INITIATE A DEX QUERY MODE INQUIRY—The G4 will issue the DEX QUERY MODE string to the attached VMC. See the EVA-DTS DEX protocol standard for details on the DEX QUERY MODE of operation. The G4 will react to the returned DEX QUERY MODE result from the VMC and issue the following result string: - STX+[0K-0]+ETX+LRC
#<esc>P—CLEAR G4 CALL-IN FLAGS—This command clears the G4 CALL-IN flags associated with having the terminal initiate a call to USALIVE. The G4 will issue the following result string: - STX+[OK-P]+ETX+LRC
#<esc>Q—VEND DENY—This command is issued to instruct the G4 to VEND DENY declining the vend request that has been received from the vending machine VMC. See the MDB TRANSACTION STRING ‘R’ state above. The G4 will issue the following result string: - STX+[OK-Q]-ETX+LRC
#<esc>S—SEND BUTTON STATUS—This command will send the current button status for the ‘AAA’BUTTON 1 and ‘BBB’BUTTON 2. If a button has not been pressed (since cleared with the #<esc>T) a ‘False indication will be sent. If the button has been pressed a ‘T’rue indication will be sent. The G4 will issue the following result string: - STX+[BUTTON-]+[T’ or ‘F’ for the
AAA BUTTON 1 STATUS]+[*T′ or ‘F’ for theBBB BUTTON 2 STATUS]+ETX+LRC
For example: - STX+BUTTON-TF+ETX+LRC
- STX+[OK-M]+ETX+LRC
- Indicates that BUTTON I has been pressed and that
BUTTON 2 has not been pressed. - #<esc>T—CLEAR BUTTON STATUS—This command will clearing the button status for
the ‘AAA’BUTTON 1 and ‘BBB’BUTTON 2. Clearing the button status will set the status flags to ‘F’alse. The G4 will issue the following result string: -
- STX+[OK-T]+ETX+LRC
AAA—END SESSION AND PRINT RECEIPT. A session started when the G4 is in the VEND ACTIVE ‘ON’ mode is terminated and a receipt optionally printed by sending a string of ‘AAA . . . ’. The correct use of this command should be to send a string of at least six ‘A’ characters. Though the G4 is only looking for a combination of three consecutive ‘A’s sending more is preferred. This command can also be used in the service mode to select menus and menu items.
BBB—BUTTON 2 PRESS. While in the service mode sending a string of ‘BBB . . . ’ has the same effect as inserting a card in the card reader to advance a menu selection or setting. The correct use of this command should be to send a string of at least three ‘B’ characters.
- STX+[OK-T]+ETX+LRC
- When the G4 is in the VERBOSE ‘ON’ mode the G4 (system 500) will send text messages out of the serial port to a display device. The display device can be the computing platform. The text messages correspond to the activity of the G4. For example, when the G4 is ready to accept cards a text prompt message of ‘Please Swipe’, ‘A Valid Card’ may be displayed.
- To simplify the interface and functionality requirements of the computing platform the text prompts from the G4 can be captured and displayed on the computing platform display. Doing so alleviates the need for the computing platform to ascertain and or determine what message should be displayed to the user. In addition, allowing the G4 to manage the vending transaction, MDB interface, and text prompts removes the need for the computing platform to get involved in the vending transaction.
- The text format display protocol below illustrates how the G4 sends text prompts. The selection of the control characters is consistent with the operating functionality of many text LCD displays.
- Shown in
FIGS. 1A and IB are external views of the G4. The display port/interactive interface port provides the interconnectivity to external devices and computing platforms for the purpose of control as outlined above and for display control as outlined in this section and its subsections. - The display port/interactive interface is a DB-9 pin male connector. As shown below the port is a hybrid serial port with power tap for low current external devices.
-
Connector Pin Out PIN# PIN ID DESCRIPTION Pin 1 Not Used Pin 2 Rxd Receive Input To G4 Pin 3 Txd Transmit Output From G4 Pin 4 Not Used Pin 5 GND Pin 6 +5VDC Power 300ma Max. Pin 7CTS Clear To Send Input To G4 Pin 8 RTS Request To Send Output From G4 Pin 9 Optional + Vprinter With Additional Power Supply - The communication pins Rxd, Txd, CTS, and RTS conform to RS232 standards. A minimum of Rxd, Txd, and GND are required to implement serial communication between the G4 and a computing platform. The RIS and CTS lines only come into play from a flow control prospective when receipt data is being sent from the G4. CTS and RTS are implemented in such a way as to allow a receipt printer that has little to no printer buffer to control the flow of data. CTS and RTS have no other purpose in non-print data communications and can be ignored or left unimplemented.
- Display and Control Codes:
- The G4 will send a series of display and control codes to indicate when screen initializing and formatting could occur. In interpreting the display and control codes the computing device will know when to blank the display area and as appropriate when and where to locate cursor positions.
- The display and control codes are sent from the G4 as a string of hex characters. The table of display control codes is as follows:
-
Table of Display Control Codes DISPLAY CONTROL CODES DESCRIPTION $FE + $FE + $FE Beep Beeper $FD + $FD + $FD Indicates print data is to follow (start print data) $FC + $FC + $FC Indicates print data is concluded (end print data) $FB + $FB + $FB Indicates a transaction is active - used to start a LED or set a status indicator to reflect a transaction is active. This command can be used to indicate to a user to press an ‘END’ button to end vend session. $FA + $FA + $FA Indicates a transaction is NOT active. If a LED or status indicator is ‘ON’ resultant from the above $FB command this command should be interrupted as negating the $FB command. $F9 + $F9 + $F9 Clear display area. If a text LCD is being used this command could indicate when a display initialization process could be started. Such a process has the effect of initializing the LCD and clearing the display area. $F7 + $F7 + $F7 Indicates a transaction is ready to be started. Such is the case when the MDB interface indicates the G4 is ENABLED to conduct a vend, and the G4 is ready to start a transaction. This command can be used to indicate to a user by way of LED or status indicator that the G4 is ready to accept command and or magnetic card to start a vending transaction. $F6 + $F6 + $F6 Indicates the G4 is not ready to start a vending transaction. If a LED or status indicator is ‘ON’ resultant from the above $F7 command this command should be interrupted as negating the $F7 command. - The (14 supplies text prompts in a fixed format. The format supports two lines of text each line being a maximum of 16 characters. The format includes a leading character, which indicates the line (
line 1 or 2) the text should be displayed on, up to 16 characters of text to be displayed, and a trailing character to indicate the end of the text message. When possible the text message should be formatted to contain 16 bytes. Leading spaces and trailing spaces can be used to position the text message and format the text string to 16 bytes. - The leading character conforms to the format supported by many text LCD display modules. The leading character will be a hex $80 to indicate the text message should be displayed on
line 1 of the display area. A hex $C0 will indicate the text message should be displayed online 2 of the display area. - The trailing character will be a hex $F8. The trailing character indicates the end of the text message.
- Text message format:
-
- Lead Character—$80—
Line 1- $C0—
Line 2
- $C0—
- Trailing Character=$F8
- [Lead Character]+[Up to 16 bytes of text message]+[Trailing Character]
- Example; $80+[Swipe A Valid]+$F8 $C0+[Credit Card]+$F8
The above will display ‘Swipe a Valid’ online 1 of the display area, and ‘Credit Card’ online 2 of the display area.
- Lead Character—$80—
- The G4 uses a series of display codes to locate the position of the cursor. There are a maximum of 32 cursor positions—two rows of 16 characters. In addition there are cursor display codes to turn ‘ON’ a flashing cursor, turn ‘ON’ an underline cursor (show cursor), and to turn ‘OFF’ the cursor (hide cursor). The codes are similar to those used for typical text LCD displays.
- To locate the cursor in the display area the table below illustrates the hex code and corresponding cursor location.
-
Column 1 ----------------------------------------------------------------------------------------------------------------Column 16Row 1$80 $81 $82 $83 $84 $85 $86 $87 $88 $89 $8A $8B $8C $8D $8E $8F Row 2 $C0 $C1 $C2 $C3 $C4 $C5 $C6 $C7 $C8 $C9 $CA $CB $CC $CD $CE $CF - As an example, if a hex $82 is received from the G4 this would indicate the cursor location is on
ROW 1,COLUMN 3. - This ‘ON’/OFF control corresponds to the view ability and style of the cursor. An ‘ON’ setting makes the cursor viewable, an ‘OFF’ setting makes the cursor invisible. The table below shows the various cursor control codes.
-
Cursor Control Codes CURSOR TYPE CONTROL HEX CODE Show Cursor ON Hex $0E Hide Cursor OFF Hex $0C Cursor Flash ON Hex $0D - Referring to
FIG. 6A there is shown a card reader anduser interface system 600. The card reader anduser interface system 600 can be manufactured into a card readerprocessor interface board 312 and as shown inFIG. 3B fastened to the card reader assembly. In anexemplary embodiment system 600 is a computing platform that interconnects withsystem 500'sinteractive interface 532. In this regard the credit card anduser interface 600 provide a user with user interface and display means for transacting a cashless transaction. - Interconnected with
microcontroller 602 can be an input and output (I/O)interface 604. I/O interface 604 can be a plurality of data communication lines and or a plurality of communication ports such as RS232, RS485, or other similar I/O interfacing configurations. In an exemplary embodiment I/O interface 604 can be used to implement electrical interface connections to other peripheral devices.Microcontroller 602 can be any suitable microcontroller, or microprocessor. In an exemplary embodiment amicrocontroller 602 can be a MICROCHIP PIC16F876-20/SP, PIC16C76-20/SP, ZILOG, MOTOROLA, UBICOM, INTEL or other similar microcontroller or microprocessor. - Interconnected with
microcontroller 602 can be adisplay 606.Display 606 can provide message prompts and other visual information to a user.Display 606 can be any suitable display, LCD display, or flat panel display. In an exemplary embodiment adisplay 606 can be an OPTREX DMC-16202-NY-LY or a 16×2 line LCD character display. - A
printer interface 608 can be interconnected withmicrocontroller 602. Aprinter interface 608 can be a serial communication style or Centronic style interface. In an exemplaryembodiment printer interface 608 can be utilized to print receipts, coupons, and other print data. - Interconnected with
microcontroller 602 can be acard reader interface 610.Card reader interface 610 can support a variety of card reader interfaces and protocols including for example and not limitation bit strobe type of card readers. Bit strobe type of card readers read predefined tracks of data from a magnetic card. To read track data the card reader can incorporate a plurality of DATA lines and DATA CLOCK lines to transfer magnetic card data.Card reader interface 610 can also support serial communications style card readers. Serial communication style card readers can incorporate TRANSMIT, RECEIVE, CLEAR TO SEND, REQUEST TO SEND control lines to transfer card data tosystem 500 via data communication between theinteractive interfaces - Interconnected with
microcontroller 602 can be a plurality of keypad andbutton inputs 612. Pushbutton switch 308 can be electrically interconnected withbutton inputs 612. - An
interactive interface 614 can be interconnected tomicrocontroller 602. Theinteractive interface 614 operates in similar form and function tointeractive interface 532. - Referring to
FIG. 6B there is shown a card reader anduser interface system 600 data communication routing switch. In anexemplary embodiment system 600 is manufactured onto the card reader anduser interface board 312. Furthermore,system 500 is manufactured intoVIU 100. The card reader assembly and optional printer assembly are then installed into vending equipment in such a way as to allow user access to thefront faceplate 302 of the card reader assembly. Since in many cases there is little room in the vending equipment door area it is more convenient to mount theVIU 100 assembly in a different location within the vending equipment. In order to facilitate correct operation of the card reader assembly it must be electrically connected to theVIU 100. To minimize the number of electrical connections to a single cable connected between thesystems 500 and 600 a cable connection betweeninteractive interfaces - To utilize a single data communication line (transmit line and receive line) a plurality of different types of data need to be combined into a single data stream. To effectuate the combination of data into a single data stream the interactive interface communication protocol shown in the table above can be employed. To decode the data stream and route the data to its correct destination device the data communication routing switch in
FIG. 6B can be implemented. - Referring to
FIG. 6B there is shown aninteractive interface 614 interconnected withmicrocontroller 602.Microcontroller 602 receives the data communication stream from the system SOO'sinteractive interface 532 and by way of the interactive interface protocol shown in the table above decodes and routes the data to the appropriate peripheral devices. Peripheral devices shown include I/O interface 604,display 606,printer interface 608,card reader interface 610, and keypad andbutton inputs 612. - For example and not limitation print data can be packaged with the format and control codes outlined in the interactive interface protocol and specification shown in the table above. Upon the data arriving at
microcontroller 602,microcontroller 602 can decode that the data as print data, remove any protocol formatting characters to obtain pure print data, and then pass or forward the data to theprinter interface 608. Similar processes can occur for the other peripheral devices including I/O interface 604,display 606, andcard reader interface 610, and keypad andbutton inputs 612. Data can also be obtained from each of the peripheral devices and combined into a single data string. The data string can be sent to thesystem 500 where processing can occur based in part on the data string received. - Referring to
FIG. 7 there is shown a transceiver and modembase unit system 25 700 and a plurality ofremote locations Remote locations remote location - One aspect of equipping vending equipment with a
VIU 100 and or a card reader assembly and optional printer assembly is that theVIU 100 device requires a data communication connection with a plurality of remote locations in many vending equipment locations it can be difficult to connect theVIU 100 to a physical communication line. When connecting theVIU 100 to a physical communication line is difficult or undesirable the use of the transceiver and modem base unit 700 (also referred to as base unit 700) can be a more preferred data communication option. A transceiver andmodem base unit 700 can be referred to as atransceiver unit 700.Transceiver unit 700 in incorporated into transceiver andmodem base unit 200. - In an exemplary embodiment the
transceiver unit 700 forms a wireless data link with aVIU 100 having asystem 500 incorporated within. In this regard the requirement of physically connecting theVIU 100 to a communication line can be eliminated. To create a wireless data line theVIU 100 equipped with an audit-credit-interactive system 500 utilizestransceiver 524 to data communicate withtransceiver unit 700'stransceiver 708.Transceiver 708 is interconnected withmicrocontroller 702. Anantenna 716 is interconnected withtransceiver 708.Antenna 716 can be of similar form and function toantenna 538.Transceiver 708 can be similar in form and function totransceiver 524. -
Microcontroller 702 receives and decodes data packet information. Data packets can include command data for configuring thetransceiver unit 700 and or data intended to be passed or forwarded to a plurality of remote locations by way ofmodem 704.Microcontroller 702 can be interconnected withmodem 704.Modem 704 can be similar in form and function tomodem 522. - Also interconnected with
microcontroller 702 can be at least one of the following; awireless interface 720, anetwork connection 722, aninteractive interface 718, or aserial interface 724.Wireless interface 720,network connection 722, andinteractive interface 718 can be referred to as a communication interface orbase unit 700 communication interface.Wireless interface 720 can be similar in form and function toexternal modem interface 528 and ordata modem 514.Network connection 722 can be similar in form and function to networkinterface 542.Interactive interface 718 can be similar in form and function tointeractive interface 532.Serial interface 724 can be similar in form and function tointeractive interface 532. - A plurality of remote locations can include credit bureaus such as
processing bureau 804, host network centers such ashost network center 808, other remote location such asremote location 806, and global network baseddata processing resource 810.Processing bureau 804,host network center 808, andremote location 806 can be referred to as a plurality of remote locations or remote locations.Processing bureau 804 can be a credit card processing bureau.Remote location 810 can be an Internet based data processing device or resource, or a device or resource accessible by way of the Internet—thus referred to as a global network based data processing resource. -
Microcontroller 702 can be any suitable microcontroller, or microprocessor. In an exemplary embodiment amicrocontroller 702 can be a MICROCHIP PIC16F876-20/SP, PIC 16C76-20/SP, ZILOG, MOTOROLA, INTEL, UBICOM, or AMD. - Referring to
FIG. 8 there is shown an audit-credit-interactive system 500 interfaced to a computing platform.FIG. 8 illustrates how a audit-credit-interactive system 500 can be data communication connected to acomputing platform 802 by way ofsystem 500'sinteractive interface 532 andcomputing platform 802 interactive interface. In similar form and function as the interactive interface solution betweensystem 500 andsystem 600 described above,system 500 andcomputing platform 802 can interconnect and data communicate as described with the communication specification and protocol shown in the table above. - There can be at least two methods of interconnecting a
system 500'sinteractive interface 532 to acomputing platform 802. In the first method thesystem 500 and thecomputing platform 802 can be mutually exclusive devices that share a data cable connection between the interactive interfaces. In this regard, thesystem 500 could be manufactured separate from thecomputing platform 802 and later during installation interconnected together with a data cable connection between the interactive interface parts. - This method allows maximum flexibility in the selection of the
computing platform 802's form and functional features as well as allowing maximum flexibility in the selection of thesystem 500's form and functional features. - A second method of interconnecting a
system 500'sinteractive interface 532 to acomputing platform 802's interactive interface can be to integrate thesystem 500 andcomputing platform 802 into a single circuit design, preferably manufactured into a single circuit board device, semiconductor chip, or module. In this regard theVIU 100 could comprise anintegrated system 500 andcomputing platform 802 combined. This method of interconnectivity can be desirable, for example and not limitation, when mass-producedVIU 100's with a computing platform option is required, and where cost, unit size, and or ease of installation and service are considerations. - Referring to
FIG. 9A there is shown a vending machine MULTI-DROP-BUS interface with a plurality of peripheral devices interconnected thereto. Typical vending equipment that operate with a VMC have avending machine interface 902.Vending machine interface 902 can support multi-drop-bus (MDB) interfacing and communications, data exchange format (DEX) interfacing and communications, coin device interfacing and communications, bill device interfacing and communications, and or vending machine controller (VMC) interfacing and communications. In addition to other types of peripheral devices, peripheral devices that support the NAMA MDB specification and or the EVA DEX specification can be interconnected to thevending equipment interface 902. - In an exemplary embodiment, once the peripherals are connected to the VMC, the VMC typically operates as the master device and each of the peripheral devices are designated as slave peripheral devices. Such slave peripheral devices can include
bill acceptor 904,coin mechanism 906,card reader 908, andonline module 910. -
Bill acceptor 904 andcoin mechanism 906 can be of a type for example and not limitation manufactured for or by MARS, COINCO, CONLUX, or other similar bill acceptor and coin mechanism type or manufacturer.Card reader 908 can be of a type for example and not limitation manufactured by or for USA TECHNOLOGIES, MARS, MARCONI, DEBITEK, SCHLUMBERGH, ACT, COINCO, EVEND, WIRCA, US WIRELESS or other similar card reader type. Online module can be of a type for example and not limitation manufactured for or by USA TECHNOLOGIES, MARCONI, MARS, COINCO, WIRCA, US WIRELESS, EVEND or other similar online module type. - A limitation on peripheral devices can be that they must support a compatible version of the MDB protocol specification to operate correctly. This requirement of having to support the version of MDB protocol the VMC supports can limit the selection of compatible peripheral devices as well as limit the range of functionality of the peripheral devices.
- For example and not limitation if the VMC MDB protocol version does not support obtaining audit information from a peripheral device the audit information contained within the peripheral device will go unutilized. If in another example the bill acceptor is able to report it's functional operation information and the VMC does not support a MDB protocol version to obtain this information the data in the bill acceptor will not be retrieved and the benefits of having such informational data will not be realized.
-
FIG. 9B illustrates how an audit-credit-interactive system 500 can be configured in series with thevending machine interface 902. In this regard, the peripheral devices can be supported by thesystem 500'smimic MDB interface 516. The advantage off this network configuration is that thesystem 500 can support multiple versions and derivative versions of the NAMA MDB protocol specification. Furthermore, thesystem 500 can provide peripheral message emulation and message passing to effectuate the VMC's ability to data communicate to each peripheral by way of thesystem 500'sMDB interface 518 andmimic MDB interface 516. - In an exemplary embodiment the VMC can data communicate with each peripheral device at the MDB version level of the VMC. In addition,
system 500 can data communicate with the VMC and each peripheral device at the VMC version level and each peripheral MDB version or derivative version level. In this regard features supported by a peripheral device's MDB version or derivative MDB version can be utilized. In addition, data communication between thesystem 500 and each peripheral device effectuates the ability to remotely monitor and manage each peripheral. In this type ofperipheral support system 500 servers as a data communication gateway for each peripheral device.System 500 ability to data communicate with a plurality of remote locations and with each peripheral device effectuates the ability of each peripheral device to data communicate with a plurality of remote locations. - Referring to
FIG. 9B there is shown asystem 500'sMDB interface 518 interconnected with the VMCvending machine interface 902. In this relationship thesystem 500 can support the version of MDB protocol that the VMC firmware supports. Each of the peripheral devices includingbill acceptor 904,coin mechanism 906,card reader 908, andonline module 910 can then be interconnected with thesystem 500'smimic MDB interface 516. In this regard thesystem 500 can support any number of NAMA MDB protocol versions and or derivative versions of the NAMA MDB protocol. - For example and not limitation if the VMC supports NAMA MDB version 1.0 and an
online module 910 supports a derivative version of the NAMA MDB protocol called advanced version 3.0 both the VMC and theonline module 910 can be interconnect to asystem 500 and operate correctly. In thisrelationship system 500 by way ofMDB interface 518 andmimic MDB interface 516 data communicates with both the VMC andonline module 910. Thesystem 500 interrupts and emulates the correct device protocols as to allow the VMC to data communicate with theonline module 910. - In addition, the
system 500 can data communicate with the online module for the purpose of effectuating MDB command messages not supported by the VMC's MDB version. Thesystem 500 can then selectively data communicate, to a plurality of remote locations, data related to the peripheral devices including theonline module 910. Furthermore, by way ofsystem 500 the peripheral devices interconnected with thesystem 500'smimic MDB bus 516 can data communicate with a plurality of remote locations. - Referring to
FIG. 9C there is shown a audit-credit-interactive system 500 with card reader and audit functionality embodiment interfacing to a vending machine MDB bus and interfacing to a plurality of peripheral devices by way of a audit-credit-interactive system 500 mimic MDB bus. In anexemplary embodiment system 500 combines the functionality of the card reader peripheral and audit or as it is commonly referred to as the online module or telemetry function thus eliminating the need for additional peripheral devices to provide these functions. In addition, themimic MDB interface 516 can optionally support peripheral devices that are not compatible with the vending equipment's VMC. -
FIG. 9C illustrates that with asystem 500 interconnected with thevending equipment interface 902 there is created two alternative bus configurations for the peripheral devices. For example and not limitation thebill acceptor 904,coin mechanism 906, as well as other types of peripheral devices can, based in part on MDB version compatibility, reside on either thevending equipment interface 902, or thesystem 500'smimic MDB interface 516. - Referring to
FIGS. 10A and 10B there is shown asystem 500semiconductor package 1002, and analternative system 500module package 1003. In an exemplary embodiment asystem 500 can be manufactured into a semiconductor package or module package. For purposes of disclosure the module package can be referred to as a semiconductor package. Such semiconductor packages can include industry standard through hole and surface mount technologies. Asystem 500 can also be packaged in a module for through hole or surface mount installation. Thesystem 500 module can include a plurality of discrete and or semiconductors to implement acomplete system 500 solution. In an exemplary embodiment asystem 500 semiconductor orsystem 500 module can be mounted in a socket to enable thesystem 500 to be inserted into or removed from a design as required. - Referring to
FIG. 10C there is shown an audit-credit-interactive system 500 embodied in asemiconductor package 1002. In an exemplary embodiment asystem 500 can be manufactured into a semiconductor, or into a module to support additional components and or connectivity options. This type of manufacture can have the advantage of small size and low cost. In addition, such a semiconductor version of an audit-credit-interactive system 500 can be advantageous when integration ofsystem 500's functionality into other electronic devices is desirable. - For example and not limitation a bill acceptor, a coin mechanism, or other type of electronic device can have a
system 500 embedded intosemiconductor 1002 designed into the peripheral device circuitry. In addition to providingsystem 500functionality semiconductor 1002 can be soldered or mounted into the peripheral circuit board eliminating the need for additional manufacture and packaging of asystem 500. -
FIGS. 10C-10D show asystem 500 integrated intosemiconductor packaging 1002.Semiconductor 1002 packaging can include for example and not limitation quad flat pack style (QFP), as well as other integrated circuit industry standard package styles such as DIP, PLCC, BGA, SOP, TSOP or other suitable package style.Semiconductor package 1002 can also be a module comprising a plurality of electrical components to implement asystem 500.Semiconductor package 1002 can be referred to asmodule 1003. - Referring to
FIG. 10C thesystem 500 shown includesmicrocontroller 502 interconnected withcard reader interface 526,display interface 508, externalperipheral interface 536,interactive interface 532, RAM/NOVRAM memory 512,timekeeper 540,flash memory 512,flash memory interface 544, RAM/NOVRAM interface 546,communication interface 548, and vending equipment interfaces 506, 516, 518, and 520.Other system 500 features can be included as may be required by the application. In addition,system 500 features shown withinsemiconductor package 1002 can be eliminated as may be required or desirable based on the application. -
Timekeeper 540 can be a real time clock (RTC) for keeping track of date and time functions.Flash interface 544 can be an interface to serial and or I2C electrical erasable read only memory (EEROM), a DATA FLASH such as ATMEL DATA FLASH, serial flash memory devices, flash memory device having at least an address bus and data bus connections, or other flash memory types of devices. RAM/NOVRAM interface 546 can be a data connection to an external non-volatile read only memory device such as RAM/NOVRAM 1004. RAM/NOVRAM 1004 can be of similar form and function as 15 RAM/NOVRAM 512. - External interconnections to
semiconductor 1002 can includecard reader 1012,display 606, external peripheral 1016,computing platform 802,external flash 1006,communication device 1008, interface to vending equipment 1010, and RAM/NOVRAM 1004. -
Card reader 1012 can be an industry standard bit strobe, andserial style track - External peripheral 1016 can include RFID readers and writers, biometric devices, common communication ports such as RS232 and RS485, general purpose I/O, keypad, and or other types of peripheral device.
External memory 1006 andexternal memory 1004 can be similar in form and function asmemory 512.External communication device 1008 can include a modem, transceiver, network interface, or other type of communication device.Communication device 1008 andcommunication interface 548 can be similar in form and function tomodem 522,transceiver 524,data modem 514, and ornetwork interface 542. - In an exemplary embodiment where possible software executing within
semiconductor 1002 can emulatecertain system 500 functionality to further reduce the dependence of physical hardware. For example and not limitation thecard reader 10 interface may be implemented in software where general purpose I/O lines could be configured to capture card data received from a card reader such ascard reader 1012. - Referring to
FIG. 10D thesystem 500 is embedded withinsemiconductor package 1002. In this embodiment thesystem 500 relies on software executing inmicrocontroller 502 to implement and emulate thesystem 500's functionality. In this embodiment software configures general purpose I/O lines to implementcard reader interface 526,display interface 508, externalperipheral interface 536,interactive interface 532, RAM/NOVRAM interface 546, vending equipment I/O communication interface 548. - One advantage of implementing
system 500 in software can be that thesystem 500 software solution can be implemented in mass producible generally available microcontroller devices. Such microcontroller devices can include for example and not limitation UBICOM's line of microcontrollers, MOTOROLA, INTEL, MICROCHIP, ZILOG, and other similar or suitable microcontroller or microprocessor devices. - A second advantage of implementing a
system 500 in software can be that the proprietary nature of the software and its functional capabilities can more easily be concealed and protected when resident and secured within a microcontroller. In addition to the secure ability of thesystem 500 solutions, implementing asystem 500 in a microcontroller brand or series that other design engineers are familiar with can be advantageous in easing the integration of thesystem 500semiconductor package 1002 into electrical designs. - Further ease of integration can be achieved by implementing
power converter 1020.Power converter 1020 converts input voltage obtained from the vending equipment's MDB bus via thevending machine interface 902. The output voltage from the power converter can be referred to as +VCC and can power thesystem 500semiconductor 1002. - One advantage of allowing
power convert 1020 to supply power tosemiconductor 1002 can be that the semiconductor can be resident on an adapter card and retrofit to existing VMC's by connection to the VMC'svending equipment interface 902. Through this single connection point the adapter card comprising thesemiconductor 1002 can power itself and data communicate with the VMC by way of the VMCvending equipment interface 902. - Furthermore, the
semiconductor 1002 can be integrated into the VMC controller electronics and electrically connected on the circuit board to the VMCvending equipment interface 902. Simplifying the data and power connections betweensemiconductor 1002 and the VMC can save time and effort in the integration of the combined VMC/system 500 solution. In addition, the fact that thesystem 500 can operate mutually exclusive from the VMC can be advantageous in the design of the overall combined VMC/system 500 solution. - Besides combining the
system 500 on a chip with a VMC control system thesystem 500 packaged insemiconductor 1002 can be integrated into acomputing platform 802. In this regard thesemiconductor 1002 can be integrated into thecomputing platform 802 electronics and electrically connected by way of externalperipheral interface 536. In addition, the fact thatsystem 500 can operate mutually exclusive from thecomputing platform 802 can be advantageous in the design of the overall combinedcomputing platform 802/system 500 solution. - Referring to
FIG. 11 there is shown an MDB initialization tuning routine 1100. With the proliferation of different kinds and styles for vending equipment VMC controllers the NAMA MDB and NAMA derivative MDB protocol implementation can vary from VMC to VMC. In addition the processing capabilities, UART implementations and lack of UART implementations can cause a variation in VMC microcontroller performances. These performance variations in VMC microcontrollers can cause the serial communications between VMC to vary in the devices ability and speed by which data bytes can be consecutively data communicated to the VMC controller. In addition to data communication speed and response timing another variation between VMC's can be interpretation of protocol command functionality, usage, and message formatting. - Another source of VMC MDB protocol implementation variations can occur as a result of the VMC computing power and or microprocessor speed or (millions of instructions per second) MIPS capability. Microprocessor speed can influence MDB protocol implementation and message transaction speed in several ways. One such way can be in the MDB interface to the microprocessor.
- MDB message transactions are a string of serial bytes. As such bytes must arrive one at a time to the VMC microprocessor. Once a byte arrives it must be fetched from the VMC microprocessor receive buffer and processed. The time required to fetch a byte can vary from VMC to VMC. As such the MDB INTER-BYTE TIME SPACING, which is the amount of time delay inserted between sent bytes could be a critical variable. If for example and not limitation a string of bytes arrive to close together, or in other words the MDB INTER-BYTE TIME SPACING is too short the VMC may not be able to process the bytes and as a result the
system 500 could fail to initialize and operate correctly. If for example and not limitation a string of bytes arrive to far apart, or in other words the MDB INTER-BYTE TIME SPACING is too long the VMC may time-out and fail to process the MDB message. As a result thesystem 500 could fail to initialize and operate correctly. - The MDB protocol involves a master-slave relationship between the master vending equipment's VMC and the slave peripheral devices. In implementing the MDB protocol the master VMC initiates an MDB message command to a slave peripheral device. The slave peripheral device then has a finite amount of time to respond the VMC command message with a message response. As such the amount of time allotted for the peripheral device to respond with a MDB message response can vary from VMC to VMC. If for example and not limitation the peripheral device responds too quickly with a message response the VMC's microprocessor may not be ready and miss the return message. As a result the
system 500 could fail to initialize and operate correctly. If for example and not limitation the peripheral device takes too much time to respond to the message the VMC may time-out waiting for the peripherals response message. As a result thesystem 500 could fail to initialize and operate correctly. An MDB MESSAGE RESPONSE timer is utilized to implement a pause from the time a MDB message is received from the VMC to the time an MDB message response from thesystem 500 is sent to the VMC. - The MDB initialization tuning routine 1100 determines through successive iterations of the MDB initialization sequence the optimum MDB INTER-BYTE TIME SPACING and MDB MESSAGE RESPONSE timing. Processing begins in
block 1102. - In
block 1102 the MDB INTER-BYTE INTERVAL SPACING and the MDBMESSAGE RESPONSE timers are set to a minimum range setting. Processing then moves to block 1104. Appropriate MDB MESSAGE RESPONSE time can range from a minimum range of a few microseconds to a maximum range of several milliseconds. Appropriate MDB MESSAGE RESPONSE time can range from a minimum range of less than one millisecond to a maximum range of five to ten milliseconds. Preferable a range can be from 0.5 milliseconds to 7 milliseconds and be changeable by a user and or under software control. - In
block 1104 thesystem 500 waits for the VMC to initiate the POLL command. In response to the POLL command thesystem 500 sends the JUST RESET command. Processing then moves to block 1106. - In
block 1106 thesystem 500 responds to VMC MDB transaction messages with message responses in an attempt to initialize thesystem 500. Processing then moves todecision block 1108. Initialization of thesystem 500 occurs by a series of successful VMC andsystem 500 MDB transaction message exchanges. Thesystem 500 can be considered successfully initialized when the VMC and thesystem 500 have exchanged configuration messages and the VMC has issued to thesystem 500 the MDB ENABLE message. - In decision block 1108 a determination is made as to whether the
system 500 received the MDB ENABLE command from the VMC and if thesystem 500's operation state is now ENABLED. If the resultant is in the affirmative that is thesystem 500's operation is now ENABLED then the routine is exited. If the resultant is in the negative that is the system SOO's operational state is not ENABLED then processing moves to block 1110. - In
block 1110 the MDB INTER-BYTE TIME SPACING is incrementally increased and processing moves todecision block 1112. The incrementing of the MDB INTER-BYTE TIME SPACING can be either automatic insystem 500 software or manually changed by service personnel. - In decision block 1112 a determination is made as to whether the MDB INTER-BYTE TIME SPACING maximum range has been reached. If the resultant is in the affirmative that is the MDB INTER-BYTE TIME SPACING maximum range has been reached then processing moves to block 1114. If the resultant is in the negative that is the MDB INTER-BYTE TIME SPACING maximum range has not been reached then processing returns to block 1104.
- In
block 1114 the MDB INTER-BYTE TIME SPACING is set to the initial minimum range setting. In addition, the MDB MESSAGE RESPONSE time is incremented. The incrementing of the MDB MESSAGE RESPONSE timer can be either automatic insystem 500 software or manually changed by service personnel. Processing then moves todecision block 1118. - In decision block 1118 a determination is made as to whether the MDB MESSAGE RESPONSE time maximum range has been reached. If the resultant is in the affirmative that is the maximum MDB MESSAGE RESPONSE time range has been reached then processing moves to block 1116. If the resultant is in the negative that is the maximum MDB MESSAGE RESPONSE range has not been reached then processing moves back to
block 1104. - In block 1116 a prompt is provided indicating that the MDB communications between the
system 500 and the VMC could not be established. The routine is then exited. - Referring to
FIGS. 12A-12B there is shown aVIU 100 withsystem 500 and transceiver and modembase unit system 700 wireless protocoldata communication routine 1200. In a typical application involving aVIU 100 comprising audit-credit-interactive system 500 theVIU 100 will be installed in vending equipment. In certain of those installations it may be desirable to data communicate wirelessly to atransceiver system 700 instead of trying to hardwire thesystem 500 to a communication line. Atransceiver system 700 can be referred to as a base unit orbase unit 700. - In installations where
system 500 data communicates to a plurality of remote locations by way of a wireless data connection to transceiver system 700 a protocol can be implemented to insure data integrity, security, andtransceiver system 700 correct configurations.Routine 1200 can implement such a protocol betweensystem 500 andtransceiver system 700. Processing begins inblock 1202. - In
block 1202 thetransceiver system 700 data communicates wirelessly an ENQ packet. The ‘ENQ’ packet comprises control codes that indicate the state and or current condition of thebase unit 700.Base unit 700 state or condition codes include an AVAILABLE condition, BUSY condition, and a POLLING condition. - The AVAILABLE state indicates to any
VIU 100system 500 listening in wireless proximity to thebase unit 700 that the base unit and communication interface is AVAILABLE and ready for use by any VIU 100 (system 500). The communication interface includesmodem 704,wireless interface 720,interactive interface 718,serial communication interface 724, andnetwork connection 722. In an exemplaryembodiment base unit 700 is configured to use one of the communication interface options (704, 718, 720, 722, or 724). The BUSY state indicates to anyVIU 100/system 500 listening in wireless proximity to thebase unit 700 that the base unit and communication interface is BUSY servicing adifferent VIU 100 and is unavailable for use. The POLLING state indicates to anyVIU 100/system 500 listening in wireless proximity to thebase unit 700 that a remote location has requested that theVIU 100 initiate a call host sequence. This in effect triggers each VIU based onindividual VIU 100 programming to initiate a call to the requesting remote location. Processing then moves todecision block 1204. - In decision block 1204 a determination is made as to whether the
system 500, referred to as the terminal, wirelessly receives the ENQ message sent by thetransceiver system 700. If the result is in the affirmative that is the terminal receives the ENQ message then processing moves to block 1206. If the resultant is in the negative that is the terminal did not receive the ENQ message then processing moves back toblock 1202. - In reply to block 1206 the terminal is enabled for transaction processing. Processing then moves to block 1208.
- In
block 1208 thetransceiver system 700 referred to as the base unit transmits an ENQ packet with a packet ID attached. Processing then moves to block 1210. - In
block 1210 the terminal receives the ENQ and packet ID from thetransceiver system 700. In accordance withsystem 500 data requirements thesystem 500 then responds as necessary with a data packet. Processing then moves to block 1212. - In
block 1212 thetransceiver system 700 upon receiving the data packet from thesystem 500 decodes the data packet. Processing then moves todecision block 1214. - In
decision block 1214 thetransceiver system 700 makes a determination as to whether the data received from thesystem 500 is data intended forsystem 700 configurations.System 700 can be referred to as the base unit or base. If the resultant is in the affirmative that is the data is configuration data for the base unit processing moves to block 1218. If the resultant is in the negative that is the data is not configuration data for the base unit then processing moves to block 1216. - In
block 1216 the data received from thesystem 500 is data communicated or passed to thesystem 700'smodem 704. Processing then moves back toblock 1208. - In decision block 1218 a determination is made as to whether the data command received from the
system 500 is a baud rate configuration command intended formodem 704 or a baud rate configuration command intended fortransceiver 708. - In an
exemplary embodiment modem 704 data communicates withmicrocontroller 702 at a first baud rate to effectuate data communication with a plurality of remote locations.Transceiver 708 data communicates withmicrocontroller 502 by way oftransceiver 524 at a second baud rate to effectuate data communications betweensystem 500 and a plurality of remote locations by way ofsystem 700. The first baud rate and the second baud rate can be the same or different baud rates. - If the resultant in
decision block 1218 is in the affirmative that is the data command is a baud rate configuration command then processing moves todecision block 1220. If the resultant is in the negative that is the data command received is not a baud rate configuration command then processing moves todecision block 1228. - In decision block 1220 a determination is made as to whether the command is intended for
modem 704. If the resultant is in the affirmative that is the command is intended formodem 704 then processing moves to block 1224. If the resultant is in the negative that is the command is not intended formodem 704 then processing moves to block 1222. - In
block 1220 thetransceiver 708 baud rate is configured. Processing moves to block 1226. - In
block 1224 the baud rate ofmodem 704 is configured. Processing moves to block 1226. - In
block 1226 thetransceiver system 700 sends the acknowledge (ACK) message to thesystem 500 originating the data command. Processing then moves back toblock 1208. - In decision block 1228 a determination is made as to whether the received data command is a hardware-reset command. If the resultant is in the affirmative that is the received data command is a hardware-reset command then processing moves to
decision block 1230. If the resultant is in the negative that is the received data command is not a hardware-reset command then processing moves to block 1234. - In decision block 1230 a determination is made as to whether the received command is a modem hardware-reset command. If the resultant is in the affirmative that is the received data command is a modem hardware-reset command then processing moves to block 1232. If the resultant is in the negative that is the data command received is not a hardware-reset command then processing moves to block 1236.
- In
block 1232 thetransceiver system 700 sends the ACK message to thesystem 500 originating the data command. Processing then move to block 1238. - In
block 1238 themicrocontroller 702 is reset. The routine is then exited. - In
block 1236 themodem 704 is reset. Processing moves to block 1240. - In
block 1240 thetransceiver system 700 sends the ACK message to thesystem 500 originating the data command. Processing then moves back toblock 1208. - In
block 1234 thetransceiver system 700 sends the COMMAND NOT RECOGNIZED message to thesystem 500 originating the data command. Processing then move back toblock 1208. - Referring to
FIG. 20 there is shown a transceiver and modembase unit system 700 wireless protocoldata communication routine 2000. In an exemplary embodiment thebase unit 700 serves as a data gateway between thesystem 500 and a remote location. In operation thesystem 500 1) initially requests data access to thebase unit 700, and if data access is granted by thebase unit 700 then 2) begins utilizing thebase unit 700 internal modem by transmitting and receiving data packets to and from thebase unit 700. Thebase unit 700 manages 1) granting or denying data communication access between thesystem 500 terminal and thebase unit 700, 2) the receiving of packetized wireless data from thesystem 500 for processing and data communication to theinternal base unit 700modem 704, and 3) the receiving of data from theinternal base unit 700 modem, processing, packetizing, and wireless data communication viatransceiver 708 to thesystem 500 terminal. - The data packets and wireless communication protocol can be encrypted, and error checked for data integrity. In addition, the remote hosts both credit bureau and the USALIVE network can perform their own data integrity checking. In essence the data packets can be error checked and the data received at the hosts can be error checked.
- In an exemplary embodiment the packet by packet error checking can be turned off at the
base unit 700 andsystem 500 and the data packets can be automatically sent multiple time. In this regard, error checking of each packet still occurs and only correct error free packets are passed to the remote location. Packets with errors are just discarded. If an error in a packet is detected it is the successive sending of the same packet that is relied upon to overcome the error. With no ACKing or NAKing on a packet by packet basis a half duplex transceiver system can send more data faster by not having to switch between send and receive modes. Since the remote location has calculated its own checksums and appended it to the data the remote location can determine if all data was received and received correctly. If the determination is made at the remote location that the data was not received correctly then the remote location can data communicate a NAK and the system will retransmit the data. - The wireless communication protocol comprises a successive try-retry algorithm to insure the wireless data transmission is received complete and error free. In the event wireless data can't be transmitted error free or packets are missing the
system 500 has embedded programmable functionality to compensate for the dropped transmission. - In an exemplary embodiment, in the event the
system 500 is trying to real time authorize a credit card with a remote credit bureau and the system is unable to wirelessly complete the task; instead of failing the process entirely thesystem 500 can terminate the wireless transmission and rely on its own internallocal authorization routines 1300 or 1900 to validate the user's credit card. - In a second exemplary embodiment, if the
system 500 is trying to data communicate wirelessly with a remote host location such as USALIVE and the wireless communication fails the communication can be automatically rescheduled by thesystem 500 terminal. -
Routine 2000 details the process of wireless data communication between thesystem 500 terminal and a remote location and or a global network based data processing resource such as global network baseddata processing resources 810 by way of thebase unit 700. - Processing begins in
block 2002 where theVIU 100 listens for the ‘ENQ’ status packet communicated from thebase unit 700. The ‘ENQ’ packet comprises control codes that indicate the state and or current condition of thebase unit 700.Base unit 700 state or condition codes include an AVAILABLE condition, BUSY condition, and a POLLING condition. - The AVAILABLE state indicates to any
VIU 100system 500 listening in wireless proximity to thebase unit 700 that the base unit and communication interface is AVAILABLE and ready for use by anyVIU 100. The communication interface includesmodem 704,wireless interface 720,interactive interface 718, andnetwork connection 722. In an exemplaryembodiment base unit 700 is configured to use one of the communication interface options (704, 718, 720, or 722). - The BUSY state indicates to any
VIU 100system 500 listening in wireless proximity to thebase unit 700 that the base unit and communication interface is BUSY servicing adifferent VIU 100 and is unavailable for use. - The POLLING state indicates to any
VIU 100system 500 listening in wireless proximity to thebase unit 700 that a remote location has requested that theVIU 100 initiate a call host sequence. This in effect triggers each VIU, based on individual.VIU 100 programming, to initiate a call to the requesting remote location. If the current state or condition of thebase unit 700 is BUSY or POLLING then the routine is exited, else processing moves todecision block 2022. - In
decision block 2022 where a determination is made as to whether asystem 500 terminal is requesting wireless data communication access to thebase unit 700. If the resultant is in the affirmative, that is there is asystem 500 requesting wireless data communication access to thebase unit 700 then processing moves todecision block 2004. If the resultant is in the negative that is there is nosystem 500 requesting data communication access to thebase unit 700 then the routine is exited. - In decision block 2004 a determination is made as to whether the
base unit 700 is sharing a telephone line with additional equipment, such as a fax machine. If the resultant is in the affirmative that is thebase unit 700 is sharing a telephone line then processing moves todecision block 2006. If the resultant is in the negative that is thebase unit 700 is not sharing a telephone line with additional equipment then processing moves to block 2008. - In decision block 2006 a determination is made as to whether the shared telephone line is currently in use by the additional or shared equipment. If the resultant is in the affirmative, that is the telephone line is in use then processing moves to block 2010. If the resultant is in the negative that is the telephone line is available and not in use then processing moves to block 2008.
- In
block 2010 upon the determination that the telephone line is not available thebase unit 700 wirelessly notifies the requestingsystem 500 that the telephone line is in use. Thesystem 500 depending on feature programming then makes a determination as to whether to invoke thelocal authorization routines 1300 or 1900 or reschedule the data communication attempt to the remote host network. The routine is then exited. - In
block 2008 thebase unit 700 wirelessly notifies the requestingsystem 500 that the telephone line is available and data communication between the requestingsystem 500 and thebase unit 700 can begin. In addition, thebase unit 700 notifies any other 10system 500 in wireless proximity to the base unit that thebase unit 700 is currently unavailable. Processing then moves to block 2012. - In
block 2012 thesystem 500 begins packetizing the desired data and wirelessly data communicates with thebase unit 700. Less the packetizing of data and processing, thesystem 500 in large part data communicates the same data that would be required to initialize a modem and effectuate modem dialing if the modem were physically present on thesystem 500 circuit card. Processing moves to block 2014. - In
block 2014 wireless data packets received at thebase unit 700 from thesystem 500 are validated and acknowledged. The packet is then parsed and the desired data is passed to the base unit'sinternal modem 704. Asystem 500 time-out detection and orbase unit 700 non-acknowledge facilitates a retransmission of the data from thesystem 500. Processing moves to block 2018. - In
block 2018 data received at the base unit'smicrocontroller 702 from the base unit'sinternal modem 704 is packetized and wirelessly data communicated viatransceiver 708 to theappropriate system 500. The data received at thesystem 500 is validated and optionally acknowledged. Abase unit 700 time-out detection and orsystem 500 non-acknowledge facilitates a retransmission of the data from thebase unit 700. Processing then moves todecision block 2016. - In an exemplary embodiment data is successively and continuously handled in
block system 500 and thebase unit 700 is required. Thebase unit 700,system 500, or the remote host can terminate data communication. Where the remote host is typically the credit card bureau, or USALIVE network. - In decision block 2016 a determination is made as to whether the data communication between the
system 500 and the remote host by way of thebase unit 700 is complete. If the resultant is in the affirmative that is the data communication is complete then processing moves to block 2020. If the resultant is in the negative that is the data communication is not complete then processing moves back toblock 2014. - In
block 2016 data communication between the G4 system, thebase unit 700, and the remote host is terminated. Thebase unit 700 notifies all system 500s in wireless proximity of thebase unit 700 that thebase unit 700 is available. Thesystem 500 concludes data communication and resumes normal terminal functionality. The routine is then exited. - Referring to
FIG. 13 there is shown a local transaction authorization routine 1300. A conventional card authorization through a remote processing bureau utilizing dial-up landline access to the remote processing bureau can take ten or more seconds to complete. In certain vending venues and or while vending certain types of products a ten or more second delay may be unacceptable. In these instances authorization routine 1300 can be implemented to reduce or eliminate the authorization delay while maintaining a high confidence that the card is valid. A card can be any form of ID including a credit card, magnetic card, wireless phone, a personal digital assistant PDA, private label card, smart card, hotel room card, radio frequency RFID identification, biometric, and or other similar or suitable form of ID. Processing begins indecision block 1302. - In decision block 1302 a determination is made as to whether the LOCAL AUTHORIZATION FLAG is set for this pass. In an
exemplary embodiment system 500 can be programmed to locally authorize a card based in part on an iterative process, which allows for the local authorization routine to be invoked, at a minimum, on the first pass and subsequently at any successive pass up to the last pass. The current pass through the routine is referred to as the CURRENT AUTHORIZATION ATTEMPT. The last pass is predetermined and is referred to as the MAXIMUM AUTHORIZATION ATTEMPTS LIMIT. The LOCAL AUTHORIZATION FLAG determines on which iterative pass the local authorization routine will be invoked. The iterative pass in which the LOCAL AUTHORIZATION FLAG will be set and the local authorization routine invoked is referred to as the LOCAL AUTHORIZATION ROUTINE ENTRY COUNTER. - In a first example and not limitation the local authorization routine can be invoked on the first pass. In this case no remote location will be contacted unless the local authorization results in a declined card response. In a second example the local authorization flag may be set for the second pass. In this case the
system 500 will first try to remotely authorize the card. If the remote processing bureau is unavailable or unable to authorize the card then on the second pass the local authorization routine will be invoked. - If the resultant in
decision block 1302 is in the affirmative that is the LOCAL AUTHORIZATION flag is set then processing moves todecision block 1304. If the resultant is in the negative that is the LOCAL AUTHORIZATION flag is not set then processing moves to block 1308. - In decision block 1304 a determination is made as to whether the local authorization test was OK. If the resultant is in the affirmative that is the local authorization test was OK then processing moves to
decision block 1306. If the resultant is in the negative that is the local authorization test failed then processing moves to block 1308. - In an exemplary embodiment the local authorization test can include a test of the card's expiration date and the card's modulo-10 check digit. The test of the expiration date will determine whether or whether not the card is expired based on the current date. The test for the modulo-10 check digit will determine if the card number sequence is a valid number sequence.
- In decision block 1306 a determination is made as to whether the CARD USAGE FREQUENCY limit has been reached. The CARD USAGE FREQUENCY is the total amount of time in a predetermined time period the current card has previously been authorized. In an exemplary embodiment the CARD USAGE FREQUENCY can be used to limit the number of times a card will be locally authorized before the
system 500 will attempt to authorize the card by way of aprocessing bureau 804. - If the resultant in
decision block 1306 is in the affirmative that is the CARD USAGE FREQUENCY is within the limit then processing moves todecision block 1310. If the resultant is in the negative that is the CARD USAGE FREQUENCY has been reached the limit then processing moves to block 1308. - In
block 1308system 500 initiates a data communication for the purpose of authorizing the current card with theprocessing bureau 804. Processing moves to block 1312. In block 1312 a local database withinsystem 500 can be updated. This local data can include positive cards, which are cards that have previously been successfully approved. In addition, this local database can include negative cards, which are cards that have previously been declined. Processing then moves todecision block 1314. - In
decision block 1310 the card is tested for its appearance in thesystem 500 local databases. If the resultant is in the affirmative that is the card does not appear in a negative database and or the card appears in the positive database then processing moves to block 1312. If the resultant is in the negative that is the card appears in the negative database and or does not appear in the positive database then processing moves to block 1308. - In decision block 1314 a determination is made as to whether the card has been approved. If the resultant is in the affirmative that is the card has been approved then processing moves to block 1316. If the resultant is in the negative that is the card has been declined than processing moves to
decision block 1318. - In decision block 1318 a determination is made as to whether the MAXIMUM AUTHORIZATION ATTEMPTS LIMIT has been reached. The MAXIMUM AUTHORIZATION ATTEMPTS LIMIT is the count of the number of iterative authorization passes through routine 1300. If the resultant is in the affirmative that is the MAXIMUM AUTHORIZATION ATTEMPTS LIMIT has not been reached then processing moves back to
decision block 1302. If the resultant is in the negative that is the MAXIMUM AUTHORIZATION ATTEMPTS LIMIT has been reached then the routine is exits and the card is reported as declined. - In
block 1316 the transaction is reported as authorized and the vending equipment is enabled for operation. The routine is then exited. - Referring to
FIGS. 19A-19B there is shown alocal authorization routine 1900.Routine 1900 is an exemplary embodiment of a local authorization routine.Routine 1900 utilizes locally stored databases to selectively approve and decline a card transaction. Similar to routine 1300, routine 1900 can be implemented to reduce or eliminate the authorization delay while maintaining a high confidence that the card is valid. - Payment identification data can be referred to as a card, and can be any form of ID including a credit card, magnetic card, wireless phone, a personal digital assistant (PDA), a pager, private label card, smart card, hotel room card, radio frequency RFID identification, touch or contact ID, biometric, and or other similar or suitable form of ID. In general, payment identification data (referred to as card) is a unique ID used by a user for identification and or payment from goods and or services vended from vending equipment. Processing begins in
decision block 1902. - In decision block 1902 a test is performed to determine if the payment identification data (card) presented is expired. In an exemplary embodiment expiration information can be encoded in the payment identification data. If the resultant is in the affirmative that is the card is expired then processing moves to block 1914. If the resultant is in the negative that is the card is not expired then processing moves to
decision block 1904. - In decision block 1904 a test is performed to determine if the modulo-10 of the card presented is correct. The modulo check can be a mathematical routine to determine the validity of payment identification data sequence. Such modulo checks typically utilize a mathematical routine that produces a specific check digit or character. The correct check digit can be encoded in the payment identification data and can be check against the calculated value to determine if the data sequence is valid.
- If the resultant in
decision block 1904 is in the affirmative that is the modulo-10 check digit matches then processing moves todecision block 1906. If the result indecision block 1904 is in the negative that is the modulo-check digit does not match then processing moves to block 1914. - In
block 1914 the transaction authorization is declined and the routine is exited. - In decision block 1906 a test is made to determine if the MAXIMUM APPROVAL RESET HOUR has been reached. If the resultant is in the affirmative that is the MAXIMUM RESET HOUR has been reached then processing moves to block 1910. If the resultant is in the negative that is the MAXIMUM RESET HOUR has not been reached then processing moves to
decision block 1908. - In
block 1910 the APPROVAL database is erased and the MAXIMUM RESET HOUR timer is reset. The MAXIMUM RESET HOUR is a remotely programmable preset condition that indicates the time interval in hours between erasing of the APPROVAL DATABASE. - In an exemplary embodiment erasing the APPROVAL database at a periodic interval limits the amount of time a user can present the same payment identification data in a specific period of time without having the payment identification data declined or requiring the authorization of the payment identification data with a remote location. For example and not limitation if a certain payment identification data can be presented for payment only once every 24 hours the local authorization upon seeing the same payment identification data a second time within the same 24 hour period will either decline the payment identification data or attempt to remotely authorize the payment identification data. If however the user waits more than 24 hours before presenting the same payment identification data the clearing of the APPROVAL database will occur and the user's payment identification data can be accepted as if presented for the first time. Processing then moves to
decision block 1908. - In another exemplary embodiment, under
normal system 500 terminal use payment identification data (card) can be added to the APPROVAL database each time a valid card is locally authorized. Over time the MAXIMUM OCCURRENCE WARNING LIMIT, and the MAXIMUM OCCURRENCE STOP LIMIT will be reached. Upon exceeding these limits, thesystem 500 terminal will attempt to authorize the card remotely. If it is the intention to allow a user to locally authorize a card, for example each day, without requiring an occasional remote authorization, but to limit the amount of local authorizations granted in a single day the MAXIMUM RESET HOUR can be set for example and not limitation at 24 hours. This will erase the APPROVAL database every 24 hours. As long as the repeat user does not exceed the MAXIMUM OCCURRENCE WARNING or STOP limits in a single 24-hour period no remote authorization will be required. The MAXIMUM RESET HOUR can be set to any amount of time including zero. In the case the MAXIMUM RESET HOUR is set to zero the APPROVAL database will not be cleared automatically based on time. - In decision block 1908 a determination is made as to whether the LOCAL AUTHORIZATION FLAG is set for this pass. In an
exemplary embodiment system 500 can be programmed to locally authorize a card based in part on an iterative process, which allows for the local authorization routine to be invoked, at a minimum, on the first pass and subsequently at any successive pass up to the last pass. The current pass through the routine is referred to as the CURRENT AUTHORIZATION ATTEMPT. The last pass is predetermined and is referred to as the MAXIMUM AUTHORIZATION ATTEMPTS LIMIT. The LOCAL AUTHORIZATION FLAG determines on which iterative pass the local authorization routine will be invoked. The iterative pass in which the LOCAL AUTHORIZATION FLAG will be set and the local authorization routine invoked is referred to as the LOCAL AUTHORIZATION ROUTINE ENTRY COUNTER. - In a first example the local authorization can be invoked on the first pass. In this case no remote location will be contacted unless the local authorization results in a declined card response. In a second example the local authorization flag may be set for the second pass. In this case the
system 500 will first try to remotely authorize the card. If the remote processing bureau is unavailable or unable to authorize the card then on the second pass the local authorization routine will be invoked. - If the resultant in
decision block 1908 is in the affirmative that is the LOCAL AUTHORIZATION flag is set then processing moves todecision block 1912. If the resultant is in the negative that is the LOCAL AUTHORIZATION flag is not set then processing moves to block 1926. - In decision block 1912 a test is performed to determine if the card presented for authorization is currently in the local DECLINED database. If the resultant is in the affirmative that is the card is in the DECLINED database then processing moves to block 1926. If the resultant is in the negative that is the card is not in the DECLINED database then processing moves to block 1916.
- In
block 1916 the APPROVED database is queried to determine how many occurrences of the current card are already in the database (having previously been presented and locally authorized). This is referred to as the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE. Processing then moves to block 1920. - In block 1920 a comparison of the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE is made to the MAXIMUM OCCURRENCES WARNING LIMIT. Processing then moves to
decision block 1918. - The MAXIMUM OCCURRENCES WARNING LIMIT is a remotely programmable preset variable that indicates the number of repeat occurrences the same card number can be presented for local authorization before a remote authorization is forced and or the payment identification data (card) declined. In an exemplary embodiment, it may be desirable to accept for local authorization a card no more than 2 time before that card will be authorized at a remote location. The presumption is that only the remote location has access to real time card data validity. In that case a card may be locally authorized that is in fact not a valid active card. To minimize the risk of approving a bad card the MAXIMUM OCCURRENCES WARNING LIMIT can be set as desired to limit exposure on a bad card. For example and not limitation the MAXIMUM OCCURRENCE WARNING LIMIT can be set to two. In this case the card will be accepted and locally authorized twice before a remote authorization step is forced.
- In decision block 1918 a test is performed to determine if the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE exceed the MAXIMUM OCCURRENCE WARNING LIMIT. If the resultant is in the affirmative that is the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE exceed the MAXIMUM OCCURRENCE WARNING LIMIT then processing moves to block 1926. If the resultant is in the negative that is the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE does not exceed the MAXIMUM OCCURRENCE WARNING LIMIT then processing moves to block 1922.
- In
block 1922 the card data is added to the APPROVED database and the transaction is approved. Processing moves to block 1924. - In
block 1924 the transaction is authorized and the user is allowed to utilize the vending equipment, referred to as a transaction, transaction data, and or completing a transaction. The routine is then exited. - In
block 1926system 500 initiates a remote data communication for the purpose of authorizing the current card with theprocessing bureau 804. Processing moves to decision block 1930. - In decision block 1930 a test is performed to determine if during-the remote authorization process a communication line failure was detected. Such a failure could include for example and not limitation a phone line being busy or unavailable, or a server being unavailable. If the resultant is in the affirmative that is a communication line failure was detected then processing moves to block 1928. If the resultant is in the negative that is a communication line failure was not detected then processing moves to
decision block 1934. - In
block 1928 the APPROVED database is queried to determine how many occurrences of the current card are already in the database (having previously been presented and locally authorized). This is referred to as the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE. Processing then moves to block 1932. - In block 1932 a comparison of the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE is made to the MAXIMUM OCCURRENCES STOP LIMIT. Processing then moves to
decision block 1918. - The MAXIMUM OCCURRENCES STOP LIMIT is a remotely programmable preset variable that indicates the number of times the same card number can be presented for local authorization before a remote authorization is forced. In an exemplary embodiment, it may be desirable to accept for local authorization a card no more than three times before that card will be authorized at a remote location.
- The difference between the MAXIMUM OCCURRENCE WARNING LIMIT and the MAXIMUM OCCURRENCE STOP LIMIT is that when the WARNING limit is exceeded a remote authorization will be attempted. If the remote authorization attempt fails due to communication related issues then the MAXIMUM OCCURRENCE STOP LIMIT would serve as a determinant in approving or denying the current transaction. If the MAXIMUM OCCURRENCE STOP LIMIT is not exceeded the local authorization processing will continue. If the MAXIMUM OCCURRENCE STOP LIMIT is exceeded the card will be declined. This feature in effect minimizes the possibility of inadvertently declining a card based on a communication line failure.
- In an exemplary embodiment it can be desirable not to decline a user's payment identification data because the
system 500 was unable to establish a data communication connection with a remote location, wherein such a data communication with a remote location is being attempted for the purpose of authorizing the user's payment identification data (card). In this regard, in an attempt to limit the exposure of locally approving a user's payment identification data while accommodating the possibility of thesystem 500 being unable to remotely authorize, for communication failure reasons, the user's payment identification data with a remote location a MAXIMUM OCCURRENCES STOP LIMIT can be implemented. - The MAXIMUM OCCURRENCES STOP LIMIT can be a number higher than the MAXIMUM OCCURRENCE WARNING LIMIT for example and not limitation the MAXIMUM OCCURRENCE WARNING LIMIT can be set to 2 and the MAXIMUM OCCURRENCES STOP LIMIT can be set to 3. In this example when a user presents payment identification data for the third time the MAXIMUM OCCURRENCE WARNING LIMIT is exceeded forcing a remote authorization attempt. If for communication reasons (busy signal on the phone line, network is down, etc.) a remote authorization fails—since the MAXIMUM OCCURRENCES STOP LIMIT is set to 3 and is not exceeded by the user's third presentation of the payment identification data the transaction is locally authorized and approved.
- If in another exemplary embodiment, the user now were to present the payment identification data for a fourth time and a remote authorization failed for communication reasons, that is a data connection with the remote location could not be established, then the transaction would be locally declined. This authorization decline occurring since now the NUMBER OF CARD OCCURRENCE IN APPROVED DATABASE exceeds the MAXIMUM OCCURRENCES STOP LIMIT.
- In decision block 1940 a test is performed to determine if the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE exceed the MAXIMUM OCCURRENCE STOP LIMIT. If the resultant is in the affirmative that is the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE exceed the MAXIMUM OCCURRENCE STOP LIMIT then processing moves to block 1942. If the resultant is in the negative that is the NUMBER OF CARD OCCURRENCES IN APPROVED DATABASE does not exceed the MAXIMUM OCCURRENCE STOP LIMIT then processing moves to block 1944.
- In
block 1944 the card data is added to the APPROVED database and the transaction is approved. Processing moves to block 1946. Inblock 1946 the transaction is authorized and the user is allowed to utilize the vending equipment. The routine is then exited. - In decision block 1934 a test is made to determine if the card was approved. If the resultant is in the affirmative that is the card was approved then processing moves to block 1938. If the resultant is in the negative that is the card was declined then processing moves to block 1936.
- In
block 1936 the card is entered into the DECLINED database. If multiple occurrences of the card appear in the DECLINED database the duplicate occurrences are removed. Processing then moves to block 1942. - In
block 1938 all occurrences of the card data are removed from the APPROVED database. The transaction is approved and processing moves to block 1946. - In an exemplary embodiment locally authorized and remotely authorized payment identification data and cashless transaction data can be accumulated in the
system 500 over time. At a periodic interval, for example and not limitation once a day, the authorized transactions can be data communicated to a remote data processing resource. A remote data processing resource can be a global network based data processing resource. - In an exemplary embodiment, the authorized transactions can be data communicated to a remote data processing resource by way of a first data communication to a data processing device, such as a
PDA 372, awireless phone 368, apager 370, or other similar or suitable data processing device. The data processing device can then data communicate the authorized transactions including the payment identification data and transaction data to the remote data processing resource. Data communication betweensystem 500 and the remote data processing resource by way of the data processing device can be by wired or wireless methods, and can include physically carrying the data processing device from thesystem 500 to a remote location where data communication with a remote data processing resource can be effectuated. This embodiment can allow a vending equipment service person to visit the vending equipment, download payment identification data and transaction data into a data processing device, return to for example a service vehicle or central office, and download the payment identification data and transaction data to a remote data processing device. - Alternatively the payment identification data and transaction data can be wired or wireless data communicated from the
system 500 to the remote data processing resource. - The authorized transactions, both locally authorized and remotely authorized, can be processed by the remote data processing resource. The locally authorized transaction can be data communicated to a remote location, such as a processing bureau, for reauthorization first and then subsequent settlement with the remote location. The remotely authorized transaction, having previously received an approval code from the remote location, typically need only be data communicated to the remote location for settlement. Settlement is the process of causing charges to be billed to the user or owner of the payment identification data and payment being effectuated to the merchant for goods and services rendered or vended in the transaction.
- The reauthorization processing can include obtaining a new approval code from a remote location. Such an approval code might have been obtained by way of the
system 500 initially if the payment identification data was first authorized with the remote location in lieu of having locally authorized the transaction. Remote authorization can be refer to as obtaining an approval code from a remote location. - Benefits of the local authorization process compared to the remote authorization process can be reduced authorization time. Typically a local authorization can be effectuated in real time virtually instantaneously, whereas remote authorization can take several to many or more seconds to establish a connection and data communicate with a remote location.
- In an exemplary embodiment the
system 500 authorizes locally and or remotely the payment identification data for the cashless transaction. The authorized payment identification data and cashless transaction data (transaction data) can then be data communicated to a remote data processing resource for reauthorization and or settlement. The locally authorized payment identification data and transaction data requires reauthorization and settlement. The remotely authorized payment identification data and transaction data require only settlement. - In another exemplary embodiment the
system 500 having a plurality of locally and or remotely authorized payment identification data and transaction data can first elect to reauthorize the locally authorized transactions and or elect to settle both the locally and remotely authorized transactions with the remote location prior to data communicating to the remote data processing resource. In this regard, the remote data processing resource can still implement a reauthorization process of certain transactions but this process will only confirm that such locally authorized transactions have been previously reauthorized and that: all transactions have been settled. One advantage of processing transactions in this manner can be to decentralize transaction processing. In this regard, reliance for reauthorization and settlement of transactions can be distributed across a plurality ofsystem 500 in lieu of concentrating the reauthorization and settlement process on a remote data processing resource. - Referring to
FIG. 14 there is shown an international transaction authorization andsettlement routine 1400. Standard transaction processing fees for low cost sales can be significant. International card processing can incur even more transaction processing fees in the form of currency conversion fees. Currency conversion fees are fees incurred when currency is converted from one countries currency to another. To minimize the standard transaction processing fees and to minimize and or eliminate the currency conversion fees routine 1400 can be implemented. Processing begins inblock 1402. - In
block 1402 the local authorization routine 1300 is executed. Processing moves todecision block 1404. - In decision block 1404 a determination is made as to whether a remote data communication to a
processing bureau 804 is required. If the resultant is in the affirmative that is the local authorization is approved and a remote authorization is not required then processing moves to block 1408, If the resultant is in the negative that is the local authorization was declined or failed and a remote data communication withprocessing bureau 804 is required then processing moves to block 1406. - In
block 1406 authorization through a network connection to aremote host network 808 and orprocessing bureau 804 is executed. Processing then moves todecision block 1418. - In decision block 1418 a determination is made as to whether the remote authorization was approved. If the resultant is in the affirmative that is the remote authorization was approved then processing moves to block 1408. If the resultant is in the negative that is the remote authorization failed or was declined then the card is declined and the routine is exited.
- In
block 1408 the vending equipment is enabled and vending can occur. Processing then moves to block 1410. - In block 1410 a batch of locally authorized transactions is data communicated to a remote location (the remote location being another country) by way of a network connection. In this regard locally authorized transactions can be moved from the country in which the vending sale occurred to the country where the transactions will be processed with a processing center. Processing then moves to block 1412. The transfer of locally authorized transactions can occur at a predetermined time including hourly, daily, weekly, monthly, or other desirable time interval.
- In
block 1412 the server receiving the locally authorized transactions from a plurality of remotely locatedsystem 500 authorizes and settles each locally authorized transaction. The process of settlement effectuates the transfer of funds from the cardholder to the merchant. In this regard, the transaction is authorized and settled in the same country currency avoiding any currency conversion fees. Additionally, since transactions can be aggregated from a plurality ofsystem 500 in a plurality of countries the transaction and currency volumes increase. These increases in transaction volumes coupled with efficient batching of transactions to the processing bureau can result in the lowest possible standard transaction processing fees. Processing then moves to block 1414. - In
block 1414 the funds generated from the authorization and settlement of the locally authorized transaction can be electronically transferred back to a bank in the country in which the vending sale occurred, or the country of choice. Such a transfer can be accomplished by an electronic funds transfer (EFT), or other similar or desirable method for transfer of funds. The transfer of funds can occur at a predetermined time including hourly, daily, weekly, monthly, or other desirable time interval. Processing then moves to block 1416. - In
block 1416 reporting requirements can be effectuated as required and electronically transmitted to the appropriate parties. Such a reporting cycle can be referred to as a remittance cycle and can be utilized by all parties having involvement in the transactions to among other things verify fund transfers, and monitor vending equipment operational efficiencies. The remittance cycle can occur at a predetermined time including hourly, daily, weekly, monthly, or other desirable time interval. The routine is then exited. - Referring to
FIG. 15 there is shown a data communication transaction message parsing routine 1500. In anexemplary embodiment system 500 can generate data and transactions relating to vending equipment DEX data, vending equipment MDB data, vend transaction data, financial transaction data,system 500 diagnostic data, and other types of data and transactions. While asystem 500 has data communication access to a remotehost network center 808 thesystem 500 can data communicate the mixed batch or varying types and kinds of data to thehost network center 808 servers. It is at the host network centers 808 that the data and transaction must be parsed and handled in different methods. Such parsing method can include forwarding data to a subsequent server, storing data in a database, data processing to produce a new result and then acting on the resultant data, storing and forwarding transaction data including card transaction data for authorization and settlement, as well as implementing other methods for handle mixed batch data parsing. Processing begins inblock 1502. - In block 1502 a host data connection is initiated and established between the
system 500 and thehost network center 808. Such a data connection can be a dial-up connection, and an Internet based connection, or other suitable data connections. Processing then moves to block 1504. - In
block 1504 thesystem 500 terminal configuration data is exchanged between thesystem 500 and the host network servers. This terminal configuration data effectuates the ability to remotely manage the terminal operational parameters including the terminals firmware version from a remotehost network center 808. Processing then moves to block 1506. - In
block 1506 the host network server receives a data stream from thesystem 500. The data stream can comprise a mixed batch of operational data, marketing data, transaction data, and other types of data. Processing then moves to block 1508. - In
block 1508 the server implements a series of parsing methods to identify and separate the different kinds of data and transactional information. Processing then moves to block 1510. - In
block 1510 the host network server stores the parsed data in a temporary data structure, wherein each type and kind of data is uniquely identifiable. The data connection is terminated with thesystem 500 and the routine is exited. - Referring to
FIG. 16A-16B there is shown a determination oftransaction completion routine 1600. In an exemplary embodiment once a transaction has been authorized and approved vending begins. In many vending applications multi-vends per transaction may be desirable.Routine 1600 can implement a method of determining when to allow a user to make an additional purchase and when not to. Processing begins inblock 1602. - In
block 1602 the transaction is authorized. Transaction authorization can occur as disclosed inroutines 1300 and 1400, or by other suitable methods. When a transaction has been approved and the vending equipment is being readied for vending, processing moves to block 1606. - In block 1606 a MAXIMUM VEND ITEM LIMIT is determined and set. The MAXIMUM VEND ITEM LIMIT is the maximum number of items that can be vended on a single authorization. The MAXIMUM VEND ITEM LIMIT can be stored as part of the
system 500's terminal configuration file and remotely managed by way of the remotehost network center 808. In an exemplary embodiment the MAXIMUM VEND ITEM LIMIT can range from one to ten items. Processing then moves to block 1610. - In
block 1610 the AUTHORIZED VALUE LIMIT is determined and set. The AUTHORIZED VALUE LIMIT is the maximum total sale amount a user has been authorized to purchase. The AUTHORIZED VALUE LIMIT can be stored as part of thesystem 500's terminal configuration file and remotely managed by way of the remotehost network center 808. Processing then moves to block 1604. - In
block 1604 the NO ACTIVITY TIMER LIMIT is determined and set. The NO ACTIVITY TIMER LIMIT is the maximum amount of time a user has to make the first vend. The NO ACTIVITY TIMER LIMIT can be stored as part of thesystem 500's terminal configuration file and remotely managed by way of the remotehost network center 808. In an exemplary embodiment the NO ACTIVITY TIMER LIMIT can range from less than one minute to several minutes. Processing then moves to block 1608. - In
block 1608 the RE-VEND TIMER LIMIT is determined and set. The RE-VEND TIMER LIMIT is the maximum amount of time a user has to make additional vends beyond the first vend. The RE-VEND TIMER LIMIT can be stored as part of thesystem 500's terminal configuration file and remotely managed by way of the remotehost network center 808. In an exemplary embodiment the RE-VEND TIMER LIMIT can range from less than one minute to several minutes. Processing then moves to block 1620. - In block 1620 a vending session is started. Processing moves to
decision block 1622. - In decision block 1622 a determination is made as to whether the NO ACTIVITY TIMER LIMIT has been reached. If the resultant is in the affirmative that is the NO ACTIVITY TIMER LIMIT has not reached the limit then processing moves to
decision block 1624. If the resultant is in the negative that is the NO ACTIVITY TIME LIMIT has been reached then processing moves to block 1626. - In
block 1626 the end session sequence is started. The end session sequence includes waiting for the vending equipment to complete any last vends, ending the vending session, saving sales record data, optionally printing a receipt, and any other end sequence steps that may be required. The routine is then exited. - In decision block 1624 a determination is made as to whether the user has pressed the end transaction button. If the resultant is in the affirmative that is the user has pressed the end transaction button then processing moves to block 1626. If the resultant is in the negative that is the user has not pressed the end transaction button then processing moves to
decision block 1628. - In decision block 1628 a determination is made as to whether a VEND REQUEST MDB command has been received from the vending equipment's VMC. If the resultant is in the affirmative that is the VEND REQUEST has been received then processing moves to block 1630. If the resultant is in the negative that is the VEND REQUEST command was not received then processing moves back to
decision block 1622. - In
block 1630 the VEND REQUEST command is processed and a VEND APPROVED or VEND DENIED response message is data communicated from thesystem 500 to the requesting VMC. Processing moves todecision block 1632. - In decision block 1632 a determination is made as to whether the MAXIMUM VEND ITEM LIMIT has been reached. If the resultant is in the affirmative that is the MAXIMUM VEND ITEM LIMIT has been reached then processing moves back to
block 1626. If the resultant is in the negative that is the MAXIMUM. VEND ITEM LIMIT has not been reached-then processing moves todecision block 1634. - In decision block 1634 a determination is made as to whether the AUTHORIZED VALUE LIMIT has been reached. If the resultant is in the affirmative that is the AUTHORIZED VALUE LIMIT has been reached then processing moves back to
block 1626. If the resultant is in the negative that is the AUTHORIZED VALUE LIMIT has not been reached then processing moves todecision block 1638. - In decision block 1638 a determination is made as to whether the user has pressed the end transaction button. If the resultant is in the affirmative that is the user has pressed the end transaction button then processing moves back to
block 1626. If the resultant is in the negative that is the user has not pressed the end transaction button then processing moves to block 1636. - In
block 1636 the RE-VEND TIMER is reset to zero. Processing moves to block 1640. - In block 1640 a vending session is started. A vending session is started by sending the BEGIN SESSION MDB command to the vending equipment's VMC. Processing moves to
decision block 1642. - In decision block 1642 a determination is made as to whether the RE-VEND TIMER has reached the RE-VEND TIMER LIMIT. If the resultant is in the affirmative that is the RE-VEND TIMER has reached the RE-VEND TIMER LIMIT then processing moves back to
block 1626. If the resultant is in the negative that is the RE-VEND TIMER has reached the RE-VEND TIMER LIMIT then processing moves todecision block 1646. - In decision block 1646 a determination is made as to whether the user has pressed the end transaction button. If the resultant is in the affirmative that is the user has pressed the end transaction button then processing moves back to
block 1626. If the resultant is in the negative that is the user has not pressed the end transaction button then processing moves to block 1644. - In decision block 1644 a determination is made as to whether a VEND REQUEST MDB command has been received from the vending equipment's VMC. If the resultant is in the affirmative that is the VEND REQUEST has been received then processing moves to block 1648. If the resultant is in the negative that is the VEND REQUEST command was not received then processing moves back to
decision block 1642. - In
block 1648 the VEND REQUEST command is processed and a VEND APPROVED or VEND DENIED response message is data communicated from thesystem 500 to the requesting VMC. Processing moves back todecision block 1632. Referring toFIG. 17 there is shown a data communication sweeping, processing, and data forwarding routine 1700. In an exemplary embodiment thehost network center 808 accumulates a plurality of different kinds of parsed data transactions in a temporary data structure. Such a parsing and temporary data structure can be implemented as disclosed in routine 1500. To move the data transactions from the temporary data structure to a more permanent data structure and or host network sever routine 1700 can be implemented. Processing begins inblock 1702. - In
block 1702 the transactions stored in the temporary data structure are swept into an operational database. Such an operational database can be implemented as a SQL database, ORACLE database, flat file database, DB2 database, and or a combination of different kinds and types of databases. Processing then moves to block 1704. - In block 1704 locally authorized transactions that have not been previously authorized are authorized with a
processing bureau 804. This authorization after the vending sale has occurred can be referred to as post authorization. Processing then moves to block 1706. - In
block 1706 any transactions including the previously post authorized transactions are settled with theprocessing bureau 804. The process of settlement effectuates the transfer of funds from the cardholder to the merchant. Settlement after the vending sale has occurred can be referred to as post settlement or post settle. Processing then moves to block 1708. - In
block 1708 any refund transactions generated by the host network center customer service are processed. Refund transactions can occur when a previously settled transaction requires some portion of the sale amount be refunded to the cardholder. Customer service can generate a refund transaction by querying from an operational database the original transaction and then initiating a refund transaction based in part on the queried customer's original transaction. Processing then moves to block 1710. - In
block 1710 data related to vending equipment DEX and MDB details can be converted as required and data communicated to databases, and or other servers. The process of converting the DEX and MDB data can involve parsing and repackaging the data into a desired data warehousing interface format. Alternatively, the DEX and MDB data can be posted to a server where customers can by way of a network connection to thehost network center 808 download the data. - In addition to the convert and forward functionality the data handled can be measured and counted as desired for the purpose of billing for the service of gathering data from a
remote system 500 and delivering the data to a customer's desired location. Measurement and counting can include for example and not limitation measuring file and or data size, measuring the frequency the data is gathered, counting the number of times data is gathered and or forwarded, measuring access to thehost network center 808, or by other suitable measurement and counting methods and or criteria. Processing moves to block 1712. - In
block 1712 the funds collected from the processing of transactions can be remitted to the customer, as required, by EFT or other desirable method. The funds remitted can have service fees deducted from them such that their EFT amount is less than the total processed transaction amount. In this regard, customers will not have to be billed for services. The deducting of service fees from the flow of funds can eliminate the need to invoice a customer for service. The routine is then exited. - Referring to
FIG. 18A-18B there is shown a mimic MDBinterface port routine 1800. In an exemplary embodiment thesystem 500 can serve as a MDB protocol conversion gateway. In this regard thesystem 500 can emulate and interpolate VMC MDB messages for a plurality of peripheral devices. In addition, thesystem 500 can act as a MDB master or MDB slave device allowing thesystem 500 to support peripheral devices the VMC cannot.Routine 1800 implements thesystem 500 functionality to support theMDB interface 518 and themimic MDB interface 516. Processing begins inblock 1802. - In
block 1802 the VMC andsystem 500 exchange MDB message commands by way of the VMCvending equipment interface 902 and thesystem 500'sMDB interface 518. Thesystem 500 can be referred to asterminal 500 or as the terminal. Processing moves to block 1804. - In
block 1804 the terminal 500 decodes the MDB command message. Processing moves todecision block 1806. - In decision block 1806 a determination is made as to whether the MDB command message is a coin mechanism command message. If the resultant is in the affirmative that is the MDB command message is a coin mechanism MDB command message then processing moves to block 1808. If the resultant is in the negative that is then MDB command message is not a coin mechanism MDB command message then processing moves to
decision block 1812. - In
block 1808 the MDB command message is encoded and forwarded or passed by way of themimic MDB interface 516 to the coin mechanism. Processing then moves to block 1810. - In
block 1810 thesystem 500 by way of themimic MDB interface 516 receives any response MDB message from the coin mechanism. As required thesystem 500 decodes and determines if the response message from the coin mechanism requires encoding and forwarding or passing of the message to the VMC. As determined by thesystem 500 the message is selectively forwarded to the VMC upon processing returning to block 1802. - In decision block 1812 a determination is made as to whether the MDB command message is a bill acceptor command message. If the resultant is in the affirmative that is the MDB command message is a bill acceptor MDB command message then processing moves to block 1814. If the resultant is in the negative that is the MDB command message is not a bill acceptor MDB command message then processing moves to
decision block 1818. - In
block 1814 the MDB command message is encoded and forwarded or passed by way of themimic MDB interface 516 to the bill acceptor. Processing then moves to block 1816. - In
block 1816 thesystem 500 by way of themimic MDB interface 516 receives any response MDB message from the bill acceptor. As required thesystem 500 decodes and determines if the response message from the bill acceptor requires encoding and forwarding or passing of the message to the VMC. As determined by thesystem 500 the message is selectively forwarded to the VMC upon processing returning to block 1802. - In decision block 1818 a determination is made as to whether the MDB command message is a card reader or online module (OLM) command message. If the resultant is in the affirmative that is the MDB command message is a card reader or OLM MDB command message then processing moves to block 1820. If the resultant is in the negative that is the MDB command message is not a card reader or MDB command message then processing moves to block 1822.
- In
block 1820 the MDB command message is decoded and the appropriate response to the VMC is initiated by thesystem 500. Processing moves back toblock 1802. - In
block 1822 thesystem 500 optionally sends as a master device a MDB command message to the peripherals interconnected with themimic MDB interface 516. Such peripherals can include coin mechanism, bill acceptor or validator, or other peripherals on themimic MDB interface 516. If thesystem 500 does not have a MDB command message to send processing moves back toblock 1802. If thesystem 500 has a command message to send, the command message is sent to the desired peripheral device and processing moves to block 1824. - In
block 1824 thesystem 500 receives any device response messages resultant from the sent MDB message. Processing then moves todecision block 1828. - In decision block 1828 a determination is made as to whether any received message or data on the mimic MDB bus needs to be forwarded or passed to the VMC by way of the
MDB interface 518. If the resultant is in the affirmative that is the system has a command message or data to send to the VMC processing moves to block 1830. If the resultant is in the negative that is thesystem 500 does not have a command message or data to send to the VMC processing moves to block 1826. - In
block 1826 theterminal system 500 can manage the data received from the peripheral device as required. Processing moves backblock 1802. Inblock 1830 theterminal system 500 responds to the VMC POLL command message by passing the command message and or data from the peripheral device to the VMC. Processing moves back toblock 1802. - Referring to
FIG. 22A-B there is shown asystem 500 initiatedvending session routine 2200.Routine 2200 is shown as an example not a limitation, variations in the routine arise based on vending application,system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. - In an
exemplary embodiment system 500 accepts user payment identification data, card data, or other user cashless vending data to initiate a cashless vending transaction. Thesystem 500 authorizes the user's ID and upon determining that the ID is authorized transacts a cashless vending transaction between the user and vending equipment.Routine 2200 details how such a cashless vending transaction controlled bysystem 500 can be effectuated. For this example it is assumed that the VEND ACTIVE mode is ‘ON’, that issystem 500 is in control of the transaction. This implies that if acomputing platform 802 is interconnected withsystem 500 its purpose is to monitor thesystem 500 effectuated cashless transactions and in the VEND ASSIST mode ‘ON’ VEND APPROVE or VEND DENY the user select vend item at the appropriate time. Processing begins inblock 2202. - In
block 2202system 500 operational parameters are set. These parameters can include for example and not limitation MDB INTERVAL and MDB RESPONSE TIME settings, local and remote authorization settings,system 500 operation settings, and other operational parameters. Processing then moves todecision block 2204. - In decision block 2204 a determination is made as to whether
system 500 is ready for a transaction. If the resultant is in the affirmative that issystem 500 is ready for a cashless transaction then processing moves to block 2206. If the resultant is in the negative that is thesystem 500 is not ready for a transaction the routine is exited. - In an exemplary embodiment, the determination as to whether
system 500 is ready for a transaction can be based in part on whethersystem 500 and the vending equipment VMC have successfully negotiated and exchanged MDB messages to arrive at the ENABLED MDB STATE. Aninterconnected computing platform 802 can monitor thecurrent system 500, assystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issuing of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘E0001250000000000C’, wherein ‘E’ MDB STATE indicates thesystem 500 is enabled and ‘C MDB flag state indicates CLEARED for use. In addition cashless card data and or payment identification data presented by the user can be obtained by way of the @<esc>V or @<esc>T commands. - In block 2206 a user can start a cashless vending transaction by presenting valid card data, ID, payment identification data, or other suitable user ID. The
system 500 will in accordance with system settings locally and or remotely attempt to authorize the user's ID. If the user's ID is authorized the system will start a cashless vending session. Alternatively,computing platform 802 can start a cashless vending session by sendingsystem 500 valid user ID, payment identification data, card data, or other valid user ID. Thecomputing platform 802 can start a vending transaction by way of the @<esc>A commands, @<esc>B, or other available commands. Processing upon successful authorization of a user's ID moves to block 2208. - In
block 2208system 500 starts a cashless vending session by sending the VMC the MDB BEGIN SESSION command.System 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘S0001250000000000C’, wherein ‘S’ MDB STATE indicates thesystem 500 is IN-SESSION. Processing then moves todecision block 2212. - In decision block 2212 a determination is made as to whether a time-out, end session, or vend request has been received. If the result is a time-out or end session has occurred then processing moves to block 2216. If the resultant is that a vend request has occurred then processing moves to block 2210.
- In an exemplary embodiment a time-out can occur if a user in a predetermined amount of time does not make a vend item selection. For example and not limitation, the
system 500 may be programmed to automatically end a vending session if a user has not made a vend item selection in 30 seconds. An end-session can occur if the user presses a button, such aspush button 308. This button may be programmed to indicate that a press means end the session and or transaction. A vend request can occur if a user presses a selection button on the vending equipment and the vending equipment VMC issues to the system 500 a MDB VEND REQUEST message. - In
block 2216 the vending session is ended.System 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘E0001250000000000C’, wherein ‘E’ MDB STATE indicates thesystem 500 is ENABLED. The routine is then exited. - In decision block 2210 a determination is made as to whether the VEND ASSIST mode is ‘ON’. If the resultant is in the affirmative that is the vend assist mode is ‘ON’ then processing moves to block 2214. If the resultant is in the negative that is the VEND'ASSIST mode is ‘OFF’ then processing moves to block 2222.
- In an exemplary embodiment, a
system 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500 can initiate a vending session by receiving certain commands from aninterconnected computing platform 802 or by thesystem 500 initiating the vending session. An option is available for thesystem 500 orcomputing platform 802 to essentially approve the vend selection and sale price of a user selected vend item prior to dispensing the product. This mode is called the VEND ASSIST mode and can be utilized to approve the selection and control the charged price of a user selected vend item. - In this regard, forced product selection can be imposed on a user by declining (referred to as VEND DENY) a user's selections that are not correct or otherwise acceptable. In addition, promotional offers such as buy-one-get-one-free and other discounts or markups can be implemented, as well as other promotional combinations.
- As an example and not limitation a user can select a product and the
computing platform 802 and orsystem 500 can VEND APPROVE the selection and charge the user the posted price. The user can then be prompted to select a free item. To this objective the user can select an item and thecomputing platform 802 and orsystem 500 can while in the VEND ASSIST mode ‘ON’, VEND APPROVE the user's selected item this time charging the user zero—creating a buy-one-get-one-free offer. Other discount offers, markup offers and forced selection promotions can also be implemented without limitation. - In
block 2214system 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250000000000R, wherein ‘V MDB STATE indicates the vending equipment is in a vend cycle and the ‘R’ indicating that a REQUEST for VEND APPROVE is being made. Processing then moves todecision block 2218. - In decision block 2218 a determination is made as to whether a VEND APPROVE or VEND DENIED message is received from
computing platform 802 and orsystem 500. If the resultant is in the affirmative that is the cashless vend has been approved then processing moves to block 2222. If the result is in the negative that is the cashless vend has been denied then processing moves to block 2220. - In
block 2222 in an exemplary embodiment, acomputing platform 802 interconnect withsystem 500 can determine from the MDB TRANSACTION string the item selected and item price. For example and not limitation, the MDB TRANSACTION STRING ‘V 000125 000115 0001 R’ indicates that the MAX VEND PRICE in the vending equipment is ‘000125’ or $1.25, the price set in the vending equipment for the user item selected is ‘000115’ or $1.15, and the user selected item or column id ‘0001’ item or column number is one. Thecomputing platform 802 and orsystem 500 can in part use this information to determine whether to issue the VEND APPROVE or VEND DENIED command to the VMC. For example and not limitation, a determination by thecomputing platform 802 to VEND APPROVE the vend request can be made. In this regard, thecomputing platform 802 data communicates to thesystem 500 the @<esc>A+STX+SALE-00100+ETX+LRC where ‘00100’ is the desired sale amount in this case $1.00.System 500 receiving the VEND APPROVE command fromcomputing platform 802 issues the MDB VEND APPROVED message to the vending equipment VMC. Processing then moves todecision block 2226. - In
block 2220 in response to the VEND DENIED response from thecomputing platform 802 and or a determination bysystem 500 to deny the vend,system 500 sends the MDB VEND DENIED message to the vending equipment VMC. Processing then moves to block 2224. - In
block 2224 thesystem 500 and VMC negotiate and exchange MDB messages to change or end the vending session and as a result set a new MDB STATE forsystem 500.System 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘S0001250001150001C’ where ‘S’MDB 25 STATE indicates the vending equipment is IN-SESSION or ‘E0001250001150001C’ where ‘E’ MDB STATE indicates the vending equipment is ENABLED. Processing then moves back toblock 2208. - In decision block 2226 a determination as to whether the vend cycle was successful. If the resultant is in the affirmative that is the vending cycle was successful then processing moves to block 2230. If the resultant is in the negative that is the vend cycle failed then processing moves to block 2228.
- Vend cycle success and failure is typically determined by the vending equipment. If a product or service vend is attempted and, for example and not limitation, a vend column jams or is empty a vend cycle failure may be reported. If the product or service is successfully vended then the vending equipment may report a vend success.
-
System 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION′ STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001000001V’ for vend successfully complete, or a failed vend cycle could be reflected in a MDB TRANSACTION STRING as ‘VOOÔSOOOIOOOOOIF’. - In
block 2228 the vend failure is reported. A failed vend cycle could be reflected in a MDB TRANSACTION STRING as ̂00012500010000011̂. VEND FAILURES typically end a session and or transaction. The routine is then exited. - In
block 2230 upon a vend success,system 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘E0001250001000001V’ where ‘E’ indicates the MDB STATE as ENABLED and MDB flag state ‘V indicates a successful cashless vend has occurred.System 500 captures the transaction detail and creates or updates a transaction record. Processing then moves todecision block 2234. - In decision block 2234 a determination is made whether to continue the current cashless vending transaction. If the resultant is in the affirmative that is the current cashless vending transaction is to continue then processing moves to block 2232. If the resultant is in the negative that is the current cashless vending transaction is complete then processing moves to block 2236.
- In
block 2236 the transaction is ended.System 500 cancels any started vending sessions, a delay to wait for any last vend items is implemented, transaction records are updated and closed, and an optional transaction receipt can be printed. The routine is then exited. - In
block 2232 if the VEND ACTIVE mode is ‘OFF’system 500 waits for thecomputing platform 802 to clear the MDB TRANSACTION STRING with the @<esc>C command. If the VEND ACTIVE mode is ‘ON’ thesystem 500 clears the MDB TRANSACTION STRING. Processing then moves to block 2238. - In
block 2238 the MDB TRANSACTION STRING is cleared.System 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘E0001250001000001C’ where ‘E’ indicates the MDB STATE as ENABLED and the MDB flag state ‘C indicates the MDB TRANSACTION STRING is CLEARED. Processing returns to block 2208. - Referring to
FIG. 23A there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a hardware reset or is powered-up routine 2300. Shown in the figure are messages being passed between a system 500 (SYSTEM 500) and vending equipment VMC (RESPONSE FROM VENDING EQUIPMENT). - Routine 2300 is shown as example not a limitation, variations in the routine arise based on vending application,
system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 receives the hardware reset command, for example @<esc>K, or is initially powered-up and initiates a JUST RESET INITIALIZATION procedure with the vending equipment VMC. In this regard,system 500 and the VMC can exchange a series of MDB bus messages to setup thesystem 500 and set the operational state of thesystem 500 at ENABLED, Processing begins inblock 2302. - In
block 2302system 500 issues to the VMC a MDB JUST RESET message in response tosystem 500 receiving an @<esc>K hardware reset command from aninterconnected computing platform 802 or whensystem 500 goes through a system reset or power-up. In the event thesystem 500 receives the @<esc>K command from acomputing platform 802 thesystem 500 may respond, for example, with a response message such as STX+OK-K+ETX+LRC. Processing then moves to block 2304. - In
block 2304 the vending equipment VMC having received the MDB JUST RESET message should acknowledge the message and begin a reset process taking the system to the INACTIVE STATE, negotiating setup and pricing parameters, and moving the operational state from INACTIVE, to DISABLED, then to ENABLED. Processing then moves to block 2310. A report can be issued to amonitoring system 500 inblock 2306. - In
block 2306 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be 10000000000000000C, wherein T indicates the MDB STATE of INACTIVE. -
System 500 processing can also utilize the updated MDB TRANSACTION STRING to display message prompting and enable or disablesystem 500 operational features. Such operational features can include enabling or disabling card reader functionality based on the current MDB operational state. For example, when the MDB operational state is INACTIVE and or DISABLED thesystem 500 may disable certain card reader or payment identification data acceptance functionality. Conversely, when the MDB operational state is ENABLED thesystem 500 can enable certain card reader or payment identification data acceptance functionality. - In
block 2310 thesystem 500 and the vending equipment VMC exchange setup and configuration MDB message data to arrive at the DISABLED state. Such MDB message data and requirements for the DISABLED state can be found in referring to the NAMA MDB/ICP INTERFACE PROTOCOL version 1.0 and version 2.0. Upon reaching the DISABLED state a report can be issues to amonitoring system 500 inblock 2308. Processing then moves to block 2316. - In
block 2308 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be DOOOOOOOOOOOOOOOOC, wherein ‘D’ indicates the MDB STATE for DISABLED. - In
block 2316 thesystem 500 and the vending equipment VMC exchange setup and configuration MDB message data to arrive at the ENABLED state. Such MDB message data and requirements for the ENABLED state can be found in referring to the NAM A MDB/ICP INTERFACE PROTOCOL version 1.0 and version 2.0. Upon reaching the ENABLED state a report can be issued to amonitoring system 500 inblock 2312. Processing then moves to block 2312. - In
block 2312 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘E0001250000000000C’, wherein ‘E’ indicates the MDB STATE of ENABLED. The following six characters ‘000125’ indicate, for example, the maximum vend price is $1.25. Processing then moves to block 2314. - In
block 2314 the hardware reset system setup is complete. When the MDB state is ENABLED thesystem 500 and VMC typically are ready to transact a cashless vending transaction. - Referring to
FIG. 23B there is shown button press string messaging when asystem 500 clears button flags and initiates button status polling routine 2400. Shown in the figure are messages being passed between a system 500 (SYSTEM 500) and a user interface for example a card reader assembly, and or payment module user interface (RESPONSE AT USER INTERFACE). - Routine 2400 is shown as example not a limitation, variations in the routine arise based on vending application,
system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. - In an exemplary embodiment a
computing platform 802 can monitor button press and card insertions in thecard reader 310 by way of CLEAR BUTTON FLAGS and READ BUTTON FLAGS STATUS. The flags are set by thesystem 500 upon detection of a button press and or card insertion. The flags remain set until thesystem 500 receives a CLEAR BUTTON FLAGS command @<esc>T from aninterconnected computing platform 802. Processing begins inblock 2402. - In
block 2402, in an exemplary embodiment whensystem 500 receives the CLEAR BUTTON FLAGS COMMAND #<esc>T from aninterconnected computing platform 802,system 500 clears the button flags, setting them to ‘F’ for false. A response fromsystem 500 to acomputing platform 802 acknowledging the receipt and execution of the #<esc>T command may be STX+OK-T+ETX+LRC. Processing then moves to block 2404. - In
block 2404 thecomputing platform 802 can optionally test the current status of the button flags by issuing to thesystem 500 the #<esc>S READ BUTTON FLAGS STATUS request command. In this exemplary embodiment, upon clearing the flags inblock 2402 an anticipated sample button status string may be STX+BUTTON-FF+ETX+LRC. The ‘FF’ located in the interior of the string can indicate that two buttons are being monitored for example a transaction button, such aspush button switch 308, andcard reader 310 card input sensor (card sense input). Processing then moves to block 2406. - In block 2408 a user of the system may press a button on the user interface. In this example the button may be the
push button 308. In this regard, the button press would be first reported to thesystem 500. Thesystem 500 would then update the button status string as appropriate. - In
block 2406 thecomputing platform 802 can optional test the current status of the button flags by issuing to thesystem 500 the #<esc>S READ BUTTON FLAGS STATUS request command. In this exemplary embodiment, upon setting of thepush button 308 flag inblock 2408 an anticipated sample button status string may be STX+BUTTON-TF-ETX+LRC. The ‘TF’ located in the interior of the string can indicate that thepush button 308 has been pressed—‘T’ in the first position indicating TRUE a button has been detected. Processing then moves to block 2410. - In block 2412 a user of the system may insert a card in
card reader 310. In this regard, the card reader insertion would be first reported to thesystem 500. Thesystem 500 would then update the button status string as appropriate. - In
block 2410 thecomputing platform 802 can optionally test the current status of the button flags by issuing to thesystem 500 the #<esc>S READ BUTTON FLAGS STATUS request command. In this exemplary embodiment, upon setting of the card reader insertion flag inblock 2412 an anticipated sample button status string may be STX+BUTTON-TT+ETX+LRC. The ‘TT’ located in the interior of the string can indicate that card reader insertion has been detected—the second ‘T’ indicating TRUE a card insertion has been detected. Processing then moves to block 2416. - In
block 2416, when thecomputing platform 802 desires to reset the flag for another button or card reader insertion test thecomputing platform 802 can resend the CLEAR BUTTON FLAGS COMMAND #<esc>T. In response thesystem 500 will clear the button flags setting them to ‘F’ for false no button press detected. A response fromsystem 500 to acomputing platform 802 acknowledging the receipt and execution of the #<esc>T command may be STX+OK-T+ETX+LRC. If thecomputing platform 802 were to request the button status string after the CLEAR BUTTON FLAGS COMMAND the anticipated sample button status string may be STX+BUTTON-FF+ETX+LRC. - Referring to
FIG. 23C there is shownsystem 500 remote display messaging routine 2500. Shown in the figure are messages being passed between a system 500 (SYSTEM 500) and a user's interface for example a card reader assembly and or payment module user interface (RESPONSE AT USER INTERFACE). The remote display can refer to card readerinterface processor board 312 where payment identification data including card reader data, print data, and display data can be communicated with thesystem 500 and read (card reader to system 500), printed, and or displayed at the user interface. - Routine 2500 is shown as example not a limitation, variations in the routine arise based on vending application,
system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. - In an exemplary embodiment a
computing platform 802 can issue display and or print commands tosystem 500. Inresponse system 500 can format and or data communicate the display message and or print data to thesystem 500 display and or card reader interface processor board 312 (remote display to thecomputing platform 802, local display to the system 500). In this regard, thecomputing platform 802 can display messages, print data, and control general purpose I/O such as LEDs as desired on thesystem 500 display and or card reader interface processor board 312 (the user interface). In addition, a series of display commands allow thecomputing platform 802 to turn ‘OFF’ and ‘ON’ certain LEDs on the user interface, route print data to thesystem 500 printer, and beep thesystem 500 user interface beeper. Processing begins inblock 2502. - In
block 2502 thesystem 500 receives a clear text command from aninterconnected computing platform 802. Thesystem 500 having received the command from thecomputing platform 802 can reformat the data and pass it to thesystem 500 display, such asdisplay interface 508. The display data is passed to block 2504. Processing then moves to block 2506. - In
block 2504 the display associated with the user interface in cleared and or initialized. - In
block 2506 thesystem 500 receives a text command from aninterconnected computing platform 802. Thesystem 500 having received the command from thecomputing platform 802 can reformat the data and pass it to thesystem 500 display, such asdisplay interface 508. An example of such text command can be @<esc>A+STX+DISP-1xxxxxx+ETX+LRC. In this example the ‘1’ in the DISP-1 portion of the command indicates display the following text data on line one of thesystem 500 display. The ‘xxxxxx’ represents the text data to be displayed. Such data can be as few as one character and as many, in this embodiment, as 16 characters. The display data is passed to block 2508. Processing then moves to block 2510. - In
block 2508 the display data received fromblock 2506 is displayed on line one of thesystem 500 display. - In
block 2510 thesystem 500 receives a text command from aninterconnected computing platform 802. Thesystem 500 having received the command from thecomputing platform 802 can reformat the data and pass it to thesystem 500 display, such asdisplay interface 508. An example of such text command can be @<esc>A+STX+DISP-2xxxxxx+ETX+LRC. In this example the ‘2’ in the DISP-2 portion of the command indicates display the following text data on line two of thesystem 500 display. The ‘xxxxxx’ represents the text data to be displayed. Such data can be as few as one character and as many, in this embodiment, as 16 characters. The display data is passed to block 2512. Processing then moves to block 2514. - In
block 2512 the display data received fromblock 2506 is displayed on line two of thesystem 500 display. Inblock 2514 thesystem 500 receives a beep-beeper command for aninterconnected computing platform 802. Thesystem 500 having received the command from thecomputing platform 802 can reformat the data and pass it to thesystem 500 card/print/display board, such as card readerinterface processor board 312. The data is pasted to block 2516. - In
block 2516 the card readerinterface processor board 312 associated with the user interface beeps the beeper. - Referring to
FIG. 23D there is shownsystem 500 remote printing routine 2600. Shown in the figure are messages being passed between a system 500 (SYSTEM 500) and a user's interface for example a card reader assembly and or payment module user interface (RESPONSE AT USER INTERFACE). The remote printer can be referred to as card readerinterface processor board 312 where payment identification data including card reader data, print data, and display data can be communicated with thesystem 500 and read, printed, and or displayed. - Routine 2600 is shown as example not a limitation, variations in the routine arise based on vending application,
system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. - In an exemplary embodiment a
computing platform 802 can issue display and or print commands tosystem 500. Inresponse system 500 can format and or data communicate the data message to thesystem 500 display and or card reader interface processor board 312 (remote printer to thecomputing platform 802, local printer to the system 500). In this regard, thecomputing platform 802 can display messages, print data, and control general purpose I/O such as LEDs as desired on thesystem 500 display and or card readerinterface processor board 312. In addition, a series of display commands allow thecomputing platform 802 to turn ‘OFF’ and ‘ON’ certain LEDs on the user interface, route print data to thesystem 500 printer, and beep thesystem 500 user interface beeper. Processing begins inblock 2602. - In block 2602 a
computing platform 802 can issue to the system 500 a command to initiate the transfer of data from thecomputing platform 802 to the card readerinterface processor board 312 such that the data is received by the printer and printed. In this regard, either thecomputing platform 802 by way of thesystem 500 and or thesystem 500 directly, can send print data to the printer interconnected with card readerinterface processor hoard 312. As an example, thecomputing platform 802 can initiate the data switch to route data to the printer instead of the remote display by sending the @<esc>A+STX+DISP-1+$0D+$0D+$0D+ETX+LRC command, wherein the $0D+$0D+$0D is the command for initiating print data switching (see codes above). Thesystem 500 can locally send a command to the card readerinterface processor board 312 to initiate print data switching, such a command can be $FD+$FD+$FD (see codes above). The command message is sent to the card readerinterface processor board 312 inblock 2604. Processing then moves to block 2606. - In
block 2604 the card readerinterface processor board 312 receives the command data from thesystem 500 and data switches to the printer port. In this regard, data now received by the card readerinterface processor board 312 will be directly routed to the printer mechanism. - In
block 2606 thecomputing platform 802 by way ofsystem 500, orsystem 500 directly can data communicate print data to the print mechanism interconnected with card readerinterface processor board 312. -
Block 2608 receives print data fromblock 2606, routes data to the printer and effectuates printing. - In block 2610 a
computing platform 802 can issue to the system 500 a command to end the transfer of print data from thecomputing platform 802 to the card readerinterface processor board 312. To end print data transfer thecomputing platform 802 can send the command @<esc>A+STX+DISP-1+$0C+$0C+$0C+ETX+LRC, wherein the $0C+$0C+$0C is the command for end print data transfer (see codes above). Thesystem 500 can locally send a command to the card readerinterface processor board 312 to end print data switching, such a command can be $FC+$FC+$FC (see codes above). - Referring to
FIG. 23E there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a cashless vend while in the VEND ASSIST mode ‘ON’ routine 2700. Shown in the figure are messages being passed between a system 500 (SYSTEM 500) and the vending equipment VMC (RESPONSE FROM VENDING EQUIPMENT). -
Routine 2700 is shown as example not a limitation, variations in the routine arise based on vending application,system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 can initiate a vending session by receiving certain commands from aninterconnected computing platform 802 or by thesystem 500 initiating the vending session. An option is available for thesystem 500 orcomputing platform 802 to essentially approve the vend selection and sale price of a user selected vend item prior to dispensing the product or service. This mode is called the VEND ASSIST mode and can be utilized to approve the user selection and control the charged price of a user selected vend item. - In this regard, forced product selection can be imposed on a user by declining (referred to as VEND DENY) a user's selections that are not correct or otherwise acceptable. In addition, promotional offers such as buy-one-get-one-free, or other discount or markup offers can be implemented, as well as other promotional combinations.
- As an example and not limitation a user can select a product and the
computing platform 802 and orsystem 500 can VEND APPROVE the selection and charge the user the posted price. The user can then be prompted to select a free item. To this objective the user can select an item and thecomputing platform 802 and orsystem 500 can, while in the VEND ASSIST MODE, VEND APPROVE the user's selected item this time charging the user zero—creating a buy-one-get-one-free offer. Other discount offers, markup offers, and forced selection promotions can also be implemented without limitation. Processing begins inblock 2702. - In block 2702 a session is begun by the
computing platform 802 interconnected with thesystem 500 and or bysystem 500. A session can be started in a number of ways including @<esc>B BEGIN A SESSION command, @<esc>S SESSION START, a valid card swipe or payment identification data presentation, an @<esc>A+STX+CARD-xxxxxx+ETX+LRC command where ‘xxxxxx’ is card or payment identification data, an @<esc>A+STX+DIAL-xxxxxx+ETX+LRC dial-a-vend command, or other suitable start session methods. In response thesystem 500 issues a MDB BEGIN SESSION message command to the vending equipment VMC. Processing then moves to block 2704. - In
block 2704 the vending equipment starts a vending session.System 500 monitoring the MDB bus connection between thesystem 500 and VMC can determine and update the MDB TRANSACTION STRING accordingly. MDB bus data and MDB TRANSACTION STRING updating can be referred to as reporting or reporting data. Reporting data can be communicated to block 2706. Processing then moves to block 2710. - In
block 2706 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘S0001250000000000C’, where an ‘S’ indicates a MDB STATE of IN-SESSION. - In
block 2710 when a user makes a vending selection the VMC sends by way of the MDB bus connection betweensystem 500 and the VMC a MDB VEND REQUEST message. This message typically contains the column or button select by the user and the vending equipment price set for this item. The VEND REQUEST is reported to thesystem 500 and processing then moves to block 2708. - In
block 2708 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0010250001150001R’. In this case the MDB STATE FLAG is set to ‘V to indicate a vend is occurring, and the MDB FLAG state is set to ‘R’ for REQUEST VEND APPROVE. This is the indication tocomputing platform 802 and orsystem 500 that in order to effectuate vending or delivery of the item, or deny vending of the item a VEND APPROVE or VEND DENIED command respectively must be issued to the VMC from thesystem 500. - In an exemplary embodiment, a
computing platform 802 interconnect withsystem 500 can determine from the MDB TRANSACTION string the item selected and item price. For example and not limitation, the MDB TRANSACTION STRING ‘V 000125 000115 0001 R’ indicates that the MAX VEND PRICE in the vending equipment is ‘000125’ or $1.25, the price set in the vending equipment for the user item selected is ‘000115’ or $1.15, and the user selected item or column id ‘0001’ item or column number is one. Thecomputing platform 802 and orsystem 500 can in part use this information to determine whether to issue the VEND APPROVE or VEND DENIED command to the VMC. Processing then moves to block 2712. - In
block 2712, for example and not limitation, a determination by thecomputing platform 802 to VEND APPROVE the vend request can be made. In this regard, thecomputing platform 802 data communicates to thesystem 500 the @<esc>A+STX+SALE-00100+ETX+LRC where ‘00100’ is the desired sale amount in this case $1.00.System 500 receiving the VEND APPROVE command fromcomputing platform 802 issues the MDB VEND APPROVED message to the vending equipments VMC. Processing then moves to block 2720. - In
block 2720 the VEND APPROVED response is received at the VMC from thesystem 500. The vending equipment in accordance with VMC programming initiates the vend product cycle. By the VMC acknowledging the VEND APPROVED message from thesystem 500, thesystem 500 can now indicate a cashless vend is pending. A report is passed back to block 2712 such thatsystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001000001P’. Processing then moves to block 2714. - In
block 2714 the vending equipment either completes or fails to complete a vending cycle. A report is passed to block 2716 such thatsystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001000001V for vend complete, a failed vend cycle could be reflected in a MDB TRANSACTION STRING as ‘V0001250001000001F’. Processing then moves to block 2716. - In
block 2716 thecomputing platform 802 and orsystem 500 accounts for the VEND SUCCESS and or VEND FAILURE. VEND FAILURES typically end a session and or transaction. Processing then moves to block 2718. - In block 2718 a determination is made as to whether the transaction should be ended or a multi-vend session should continue. If a multi-vend session is to continue then processing moves back to block 2704 by the
computing platform 802 and orsystem 500 issuing a MDB BEGIN SESSION message to the vending equipment VMC. - Referring to
FIG. 23F there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a cashless vend while in the VEND ASSIST mode ‘OFF’ routine 2800. Shown in the figure are messages being passed between a system 500 (SYSTEM: 500) and the vending equipment VMC (RESPONSE FROM VENDING EQUIPMENT). -
Routine 2800 is shown as example not a limitation, variations in the routine arise based on vending application,system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 can initiate a vending session by receiving certain commands from aninterconnected computing platform 802 or by thesystem 500 initiating the vending session. When the VEND ASSIST mode is turned ‘OFF’ thesystem 500 will make the determination whether or not to APPROVE or DENY the MDB VEND REQUEST that is generated when a user selects an item from the vending equipment. In this regard, a VEND APPROVE response from thesystem 500 will effectuate the vending of the user selected item from the vending equipment and the subsequent charging for the vended item. Processing begins inblock 2802. - In block 2802 a session is begun by the
computing platform 802 interconnected with thesystem 500 and or bysystem 500. A session can be started in a number of ways including @<esc>B BEGIN A SESSION command, @<esc>S SESSION START, a valid card swipe or payment identification data presentation, an @<esc>A+STX+CARD-xxxxxx+ETX+ERC command where ‘xxxxxx’ is card or payment identification data, an @<esc>A+STX+DIAL-xxxxxx+ETX+LRC dial-a-vend command, or other suitable start session methods. In response thesystem 500 issues a MDB BEGIN SESSION message command to the vending equipments WIC. Processing then moves to block 2804. - In
block 2804 the vending equipment starts a vending session.System 500 monitoring the MDB bus connection between thesystem 500 and VMC can determine and update the MDB TRANSACTION STRING accordingly. MDB bus data and MDB TRANSACTION STRING updating can be referred to as reporting or reporting data. Reporting data can be communicated to block 2806. Processing then moves to block 2810. - In
block 2806 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘S0001250000000000C’. - In
block 2810 when a user makes a vending selection the VMC sends by way of the MDB bus connection betweensystem 500 and the VMC a MDB VEND REQUEST message. This message typically contains the column or button selected by the user and the vending equipment price set for this item. The VEND REQUEST is reported to thesystem 500 and processing moves to block 2808. - In
block 2808 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘VOOÔSOOOIISOOOIP’. In this case the MDB STATE FLAG is set to ‘V to indicate a cashless vend is occurring, and the MDB flag state is set to ‘P’ for VEND PENDING. This is the indication tocomputing platform 802 and orsystem 500 that the vending equipment is in vend cycle to vend an item. - In an exemplary embodiment, a
computing platform 802 interconnect withsystem 500 can determine from the MDB TRANSACTION string the item selected and item price. For example and not limitation, the MDB TRANSACTION STRING ‘V 000125 000115 0001 P’ indicates that the MAX VEND PRICE in the vending equipment is ‘000125’ or $1.25, the price set in the vending equipment for the user item selected is ‘000115’ or $1.15, and the user selected item or column id ‘0001’ item or column number one. Thecomputing platform 802 and orsystem 500 can in part use this information to account for or otherwise process/record the cashless vending transaction data. Processing then moves to block 2812. - In
block 2812 having received the MDB VEND APPROVE response fromsystem 500 the vending equipment either completes or fails to complete a vending cycle. A report is passed to block 2814 such thatsystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001150001V for vend complete a failed vend cycle could be reflected in a MDB TRANSACTION STRING as ‘V000125000115000IF’. Processing then moves to block 2814. - In
block 2814 thecomputing platform 802 and orsystem 500 accounts for the VEND SUCCESS and or VEND FAILURE. VEND FAILURES typically end a session and or transaction. Processing then moves to block 2816. - In block 2816 a determination is made as to whether the transaction should be ended or a multi-vend session should continue. If a multi-vend session is to continue then
system 500 issues a MDB BEGIN SESSION message to the vending equipment VMC. Processing then moves back toblock 2804. - Referring to
FIG. 23G there is shown a computing platform andsystem 500 exchange to effectuate a VEND ASSIST transaction whensystem 500 is selectively interconnected with vending equipment or interconnected with a bill acceptor interface routine 2900. Shown in the figure are messages being passed between a computing platform 802 (COMPUTING PLATFORM) and a system 500 (SYSTEM 500). - Routine 2900 is shown as example not a limitation, variations in the routine arise based on vending application,
system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 can be interconnected withcomputing platform 802. Thesystem 500 may or may not be interconnected with vending equipment. In an embodiment where asystem 500 is not interconnected with vending equipment thecomputing platform 802 may be interconnected with the vending equipment. In an embodiment where thesystem 500 is interconnected with vending equipment the interconnection can be of a type referred to as BILL PULSE INTERFACE or BILL SERIAL INTERFACE. The BILL SERIAL INTERFACE or the BILL PULSE INTERFACE can be, and or be referred to as bill andcoin interface 506, or other similar or suitable bill or coin interface. In this regard, thesystem 500 would look to transfer value to vending equipment by way of the vending equipment's bill acceptor and or coin acceptor interfaces. - In an exemplary
embodiment computing platform 802 communicates withsystem 500 to first indicate to start a vending session by communicating to the system 500 a VEND APPROVE command for example @<esc>A+STX+SALE-00100+ETX+LRC to indicate a ‘000100’ or $1.00 sate is to take place. The determination to initiate a vending session and the value to set for a sale is determined by thecomputing platform 802, in this example, and is based on thesystem 500 being in the VEND ASSIST mode ‘ON’. - Alternatively, in a VEND ASSIST mode ‘OFF’ a user pushing a button, such as
push button 308 on a user interface can effectuatesystem 500 starting a vending session. For example and not limitation, routine 2900 details a VEND ASSIST mode ‘ON’ vending session. Processing begins inblock 2902. - In block 2902 a session is begun by the
computing platform 802 interconnected with thesystem 500, and or bysystem 500. A session can be started by way ofcomputing platform 802 sending system 500 a VEND APPROVE command, for example @<esc>A+STX+SALE-00100+ETX+LRC to indicate a ‘000100’ or $1.00 sale. Inresponse system 500 starts a cashless vending session. Processing then moves to block 2904. - In block 2904 a cashless vending session is started. In this regard, if the VERBOSE mode is ‘ON’ the
system 500 will display the sale amount received from thecomputing platform 802. In addition, the MDB TRANSACTION STRING is updated accordingly. MDB TRANSACTION STRING updating can be referred to as reporting or reporting data. Reporting data can be communicated to block 2906. Processing then moves to block 2908. - In
block 2906 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘E0001250000000000U’, wherein ‘E’ MDB STATE indicates thesystem 500 is enables and ‘U’ MDB flag state indicates that a USER SELECTED AMOUNT has been received. In addition, cashless card data and or payment identification data presented by the user can be obtained by way of the @<esc>V or @<esc>T commands. - In
block 2908 when a user presents cashless identification data, a card, and or payment identification data tosystem 500 for authorization the user data is first authorized. If the resultant is in the affirmative, that is the user data is authorized a REQUEST VEND APPROVE MDB TRANSACTION STRING message is reported to thecomputing platform 802. - In an exemplary embodiment, in
block 2908 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘80001250001150001R’, wherein ‘S’ indicated MDB STATE of in session, and ‘R’ indicates REQUEST VEND APPROVE. This is the indication tocomputing platform 802 and orsystem 500 that in order to effectuate vending of the item or deny vending of the item a VEND APPROVE or VEND DENIED command respectively must be issued to the VMC from thesystem 500. - In an exemplary embodiment, a
computing platform 802 interconnect withsystem 500 can determine from the MDB TRANSACTION string the item selected and item price. For example and not limitation, the MDB TRANSACTION STRING ‘S 000125 000115 0001 R’ indicates that the MAX VEND PRICE in the vending equipment is ‘000125’ or $1.25, the price set in the vending equipment for the user item selected is ‘000100’ or $1.00, and the user selected item or column id ‘0001’ item or column number is one. Thecomputing platform 802 can in part use this information to determine whether to issue the VEND APPROVE, or VEND DENIED command to thesystem 500. Processing then moves to block 2910. - In
block 2910, for example and not limitation, a determination by thecomputing platform 802 to VEND APPROVE the vend request is made. In this regard thecomputing platform 802 data communicates to thesystem 500 the @<esc>A+STX+SALE-00100+ETX-i-LRC where ‘00100’ is the desired sale amount in this case $1.00.System 500 receiving the VEND APPROVE command fromcomputing platform 802 attempts to complete a vend cycle. In the BILL SERIAL, BILL PULSE, and COIN INTERFACE options the vend cycle can include transferring to the vending equipment. If thesystem 500 is not interconnected with vending equipment the vend cycle can be limited to completing the sale. Furthermore, when thesystem 500 is not interconnected with the vending equipment thecomputing platform 802 can be responsible for effectuating the vending cycle, which can include interfacing with the vending equipment, delivery of value transfer, product, or service to the user. Processing moves to block 2911 - In
block 2912 in an exemplary embodiment, the VEND APPROVE response is received at thesystem 500.System 500 either completes or fails to complete a vending cycle. A report is passed to block 2914 such thatsystem 500 updates the MDB’ TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘VOOOO1250001000001V’ for vend complete a failed vend cycle could be reflected in a MDB TRANSACTION STRING as ‘V000125000100000IF’. A report is passed back toblock 2914. Processing then moves to block 2914. - In
block 2914 thecomputing platform 802 and orsystem 500 accounts for the VEND SUCCESS and or VEND FAILURE. VEND FAILURES typically end a session and or transaction. - Referring to
FIG. 23H there is shown MDB TRANSACTION STRING messaging when asystem 500 initiates a cashless vend while in the VEND ACTIVE mode ‘OFF’ routine 3000. Shown in the figure are messages being passed between a system 500 (SYSTEM 500) and the vending equipment VMC (RESPONSE FROM VENDING EQUIPMENT). -
Routine 3000 is shown as example not a limitation, variations in the routine arise based on vending application,system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 can initiate a vending session by receiving certain commands from aninterconnected computing platform 802 or by thesystem 500 initiating the vending session. An option is available for thesystem 500 orcomputing platform 802 to essentially setup thesystem 500 in a slave mode, wherein thesystem 500 essentially receives data communication fromcomputing platform 802 to effectuate control of the vending equipment VMC. In addition, thesystem 500 data communicates with the vending equipment VMC on behalf of thecomputing platform 802 to effectuate a cashless vending transaction. In this regard, thesystem 500 effectuates the ability of the computing platform to transact a cashless vending transaction by thesystem 500 essentially acting as a data communication and translation conduit between thecomputing platform 802 and the VMC. - In an exemplary embodiment the
computing platform 802 is typically responsible for starting and stopping the vend sessions and accounting for cashless vending transactions. Thesystem 500 configuration that turns thesystem 500 into a data conduit for thecomputing platform 802 and VMC can be referred to as the VEND ACTIVE mode ‘OFF’, wherein VEND ACTIVE mode ‘OFF’ indicates thesystem 500 is a data conduit and not running the transactions. Conversely, the VEND ACTIVE mode ‘ON’ indicates thesystem 500 is running the transaction. This example reflects a VEND ACTIVE mode ‘OFF’ cashless transaction vending cycle. Processing begins inblock 3002. - In block 3002 a session is begun by the
computing platform 802 interconnected with thesystem 500 and or bysystem 500. A session can be started by the computing platform issuing the @<esc>S SESSION START command to thesystem 500. In response thesystem 500 issues a MDB BEGIN SESSION message command to the vending equipment VMC. Processing then moves to block 3004. - In
block 3004 the vending equipment starts a vending session.System 500 monitoring the MDB bus connection between thesystem 500 and VMC can determine and update the MDB TRANSACTION STRING accordingly. MDB bus data and MDB TRANSACTION STRING updating can be referred to as reporting or reporting data. Reporting data can be communicated to block 3006. Processing then moves to block 3010. - In
block 3006 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘S0001250000000000C’. - In
block 3010 when a user makes a vending selection the VMC sends by way of the MDB bus connection betweensystem 500 and the VMC a MDB VEND REQUEST message. This message typically contains the column or button select by the user and the vending equipment price set for this item. The VEND REQUEST is reported to thesystem 500 and processing moves to block 3020. - In
block 3008 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001150001R’ (VEND ASSIST mode ‘ON’). In a VEND ASSIST mode ‘OFF’ configuration thesystem 500 would typically respond to the VMC MDB VEND REQUEST with a MDB VEND APPROVED response without thecomputing platform 802 having an opportunity to APPROVE or DENY the vend. - In this example the VEND ASSIST mode is ‘ON’. In this case the MDB STATE FLAG is set to ‘V to indicate a cashless vend is occurring, and the MDB flag state is set to ‘R’ for REQUEST VEND APPROVE. This is the indication to
computing platform 802 and orsystem 500 that in order to effectuate vending of the item or deny vending of the item a VEND APPROVE or VEND DENIED command respectively must be issued to the VMC from thesystem 500. - In an exemplary embodiment, a
computing platform 802 interconnect withsystem 500 can determine from the MDB TRANSACTION string the item selected and item price. For example and not limitation, the MDB TRANSACTION STRING ‘V 000125 000115 0001 R’ indicates that the MAX VEND PRICE in the vending equipment is ‘000125’ or $1.25, the price set in the vending equipment for the user item selected is ‘000115’ or $1.15, and the user selected item or column id ‘0001’ item or column number is one. Thecomputing platform 802 and orsystem 500 can in part use this information to determine whether to issue the VEND APPROVE or VEND DENIED command to the VMC. - For example and not limitation, a determination by the
computing platform 802 to VEND APPROVE the vend request is made. In this regard, thecomputing platform 802 data communicates to thesystem 500 the @<esc>A+STX+SALE-00100+ETX+LRC where ‘00100’ is the desired sale amount in this case $1.00.System 500 receiving the VEND APPROVE command fromcomputing platform 802 issues the MDB VEND APPROVED message to the vending equipment VMC. - In
block 3020 the VEND APPROVED response is received at the VMC from thesystem 500. The vending equipment in accordance with VMC programming initiates the vend product cycle. By the VMC acknowledging the VEND APPROVED message from thesystem 500, thesystem 500 can now indicate a cashless vend is pending. A report is passed back to block 3012 such thatsystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001000001P’. Processing then moves to block 3014. - In
block 3014 the vending equipment either completes or fails to complete a vending cycle. A report is passed to block 3016 such thatsystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001000001V’ for vend complete a failed vend cycle could be reflected in a MDB TRANSACTION STRING as ‘V0001250001000001V’. Processing then moves to block 3016. - In
block 3016 thecomputing platform 802 accounts for the VEND SUCCESS and or VEND FAILURE. VEND FAILURES typically end a session and or transaction. The MDB TRANSACTION STRING must be cleared by the computing platform before another cashless vend can be transacted. Clearing the MDB TRANSACTION STRING can be effectuated by way of the @<esc>C command. Processing then moves to block 3018. - In block 3018 a determination is made as to whether the transaction should be ended or a multi-vend session should continue. If a multi-vend session is to continue then processing moves back to block 3004 initiated by the
computing platform 802 issuing to the system 500 a begin session command @<esc>S andsystem 500 issuing a MDB BEGIN SESSION message to the vending equipment VMC. - Referring to
FIG. 231 there is shown MDB TRANSACTION_STRING messaging when asystem 500 initiates a cashless vend while in the VEND ACTIVE mode ‘ON’ routine 3100. Shown in the figure are messages being passed between a system 500 (SYSTEM 500) and the vending equipment VMC (RESPONSE FROM VENDING EQUIPMENT). -
Routine 3100 is shown as example not a limitation, variations in the routine arise based on vending application,system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 can initiate a vending session by receiving certain commands from aninterconnected computing platform 802 or by thesystem 500 initiating the vending session. An option is available for thesystem 500 orcomputing platform 802 to essentially setup thesystem 500 in a master mode, wherein thesystem 500 essentially runs the cashless transaction and thecomputing platform 802 merely monitors the cashless transaction and vend cycle by way of data communication with thesystem 500. In this regard, thesystem 500 effectuates the ability of thecomputing platform 802 to monitor a cashless vending transaction. - If the VEND ASSIST mode is ‘ON’ the
computing platform 802 can still play a role in APPROVING and DENYING a cashless vend and setting the vend price as previously detailed. In the VEND ASSIST mode ‘OFF’ thesystem 500 will determine whether or not to APPROVE or DENY a vend request made by the vending equipment VMC. - The
system 500 configuration that turns thesystem 500 into the master device for transacting cashless vending transactions can be referred to as the VEND ACTIVE mode ‘ON’, wherein VEND ACTIVE mode ‘OFF’ indicates thesystem 500 is a data conduit and not running the transactions and VEND ACTIVE mode ‘ON’ indicates thesystem 500 is running the transaction. This example reflects a VEND ACTIVE mode ‘ON’ cashless transaction vending cycle. Processing begins in block 31102. - In block 3102 a session is begun by the
computing platform 802 interconnected with thesystem 500 and or bysystem 500. A session can be started in a number of ways including @<esc>B BEGIN A SESSION command, a valid card swipe or payment identification data presentation, an @<esc>A+STX+CARD-xxxxxx-FETX+LRC command where ‘xxxxxx’ is card or payment identification data, an @<esc>A+STX+DIAL-xxxxxx+ETX+LRC dial-a-vend command, or other suitable start session methods. In response thesystem 500 issues a MDB BEGIN SESSION message command to the vending equipment VMC. Processing then moves to block 3104. - In
block 3104 the vending equipment starts a vending session.System 500 monitoring the MDB bus connection between thesystem 500 and VMC can determine and update the MDB TRANSACTION STRING accordingly. MDB bus data and MDB TRANSACTION STRING updating can be referred to as reporting or reporting data. Reporting data can be communicated to block 3006. Processing then moves to block 3110. - In
block 3106 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘S00012500000000000’. - In
block 3110 when a user makes a vending selection the VMC sends by way of the MDB bus connection betweensystem 500 and the VMC a MDB VEND REQUEST message. This message typically contains the column or button selected by the user and the vending equipment price set for this item. The VEND REQUEST is reported to thesystem 500 and processing moves to block 3120. - In
block 3108 thesystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001150001R’ (VEND ASSIST mode ‘ON’). In a VEND ASSIST mode ‘OFF’ configuration thesystem 500 would typically respond to the VMC MDB VEND REQUEST with a MDB VEND APPROVED response without thecomputing platform 802 having an opportunity to APPROVE or DENY the vend request made by the vending equipment VMC. - In this example the VEND ASSIST mode is ‘ON’ the MDB STATE flag is set to ‘V to indicate a vend is occurring, and the MDB flag state is set to ‘R’ for REQUEST VEND APPROVE. This is the indication to
computing platform 802 and orsystem 500 that in order to effectuate vending of the item or deny vending of the item a VENDAPPROVE or VEND DENIED command respectively must be issued to the VMC from thesystem 500. - In an exemplary embodiment, a
computing platform 802 interconnect withsystem 500 can determine from the MDB TRANSACTION string the item selected and item price. For example and not limitation, the MDB TRANSACTION STRING ‘V 000125 000115 0001 R’ indicates that the MAX VEND PRICE in the vending equipment is ‘000125’ or $1.25, the price set in the vending equipment for the user item selected is ‘000115’ or $1.15, and the user selected item or column id ‘0001’ item or column number one. Thecomputing platform 802 and orsystem 500 can in part use this information to determine whether to issue the VEND APPROVE or VEND DENIED command to the VMC. - For example and not limitation, a determination by the
computing platform 802 to VEND APPROVE the vend request is made. In this regard, thecomputing platform 802 data communicates to thesystem 500 the @<esc>A+STX+SALE-00100+ETX+LRC where ‘00100’ is the desired sale amount in this case $1.00.System 500 receiving the VEND APPROVE command fromcomputing platform 802 issues the MDB VEND APPROVED message to the vending equipments VMC. - In
block 3120 the VEND APPROVED response is received at the VMC from thesystem 500. The vending equipment in accordance with VMC programming initiates the vend product cycle. By the VMC acknowledging the VEND APPROVED message from thesystem 500, thesystem 500 can now indicate a cashless vend is pending. A report is passed back to block 3112 such thatsystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V000125000100000IP’. Processing moves to block 3114. - In
block 3114 the vending equipment either completes or fails to complete a vending cycle. A report is passed to block 3116 such thatsystem 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H, and @<esc>V. A sample MDB TRANSACTION STRING could be ‘V0001250001000001V for vend complete a failed vend cycle could be reflected in a MDB TRANSACTION STRING as ‘V0001250001000001F’. Processing then moves to block 3116. - In
block 3116 thesystem 500 accounts for the VEND SUCCESS and or VEND FAILURE. VEND FAILURES typically end a session and or transaction. Processing then moves to block 3118. - In block 3118 a determination is made as to whether the transaction should be ended or a multi-vend session should continue. If a multi-vend session is to continue then processing moves back to block 3104 by the
system 500 issuing a MDB BEGIN SESSION message to the vending equipment VMC. - Referring to
FIG. 23J there is shown a computing platform andsystem 500 exchange to capture MDB bus messages routine 3200. Shown in the figure are messages being passed between a computing platform 802 (COMPUTING PLATFORM) and a system 500 (SYSTEM 500). - Routine 3200 is shown as example not a limitation, variations in the routine arise based on vending application,
system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 can initiate a MDB CAPTURE mode diagnostic routine. In this regard, MDB message data passed between the system 500 (denoted by ‘G4’ in the sample output block 3218) and the vending equipment VMC (VMC) can be captured and dumped tocomputing platform 802 for analysis. In an exemplary embodiment, acomputing platform 802 can be a laptop computer, or other similar type of device. - The MDB CAPTURE mode can be useful in determining the correct MDB RESPONSE and MDB INTERVAL settings. In addition, the MDB message bytes passed between the
system 500 and the VMC can be monitored and viewed during processes such as initialization, setup, and vending sessions. - Routine 3200 is an exemplary embodiment of the use of the MDB CAPTURE to capture initialization, and setup data as a
system 500 and VMC exchange data after asystem 500 hardware reset (@<esc>K command execution). Processing begins inblock 3202. - In
block 3202 the computing platform sends the Toggle MDB CAPTURE command @<esc>I to thesystem 500. Processing then moves to block 3204. - In
block 3204 thesystem 500 toggles ON the MDB CAPTURE mode and begins recording the data bytes exchanged between thesystem 500 and VMC by way of thesystem 500MDB interface 518. In response, to receiving the MDB CAPTURE command @<esc>1. from thecomputing platform 802 thesystem 500 may respond by sending the response message STX+ON-1+ETX+LRC. Processing then moves to block 3206. - In
block 3206 thecomputing platform 802 for example and not limitation, can send thesystem 500 the hardware reset command @<esc>K. This causes thesystem 500 to go through a hardware reset and attempt to reestablish data communication with the interconnected vending equipment VMC—this is the MDB data desired to be captured. Processing then moves to block 3208. - In
block 3208 thesystem 500 first responds to the receipt of the @<esc>K command by sending thecomputing platform 802 the response message STX+OK-K+ETX+LRC. Thesystem 500 then initiates asystem 500 hardware reset. Processing then movesblock 3210. - In
block 3210 thesystem 500 and VMC negotiate and exchange MDB messages to arrive at thesystem 500 being ENABLED. The data exchanged in the negotiation and exchange of MDB messages is captured in asystem 500 MDB data buffer. In this example when the MDB TRANSACTION STRING reflects that thesystem 500 is enabled the MDB CAPTURE is stopped.System 500 updates the MDB TRANSACTION STRING to reflect the operational state changes and pricing information. The MDB TRANSACTION STRING is available to aninterconnected computing platform 802 through issue of appropriate MDB TRANSACTION STRING send commands, such as @<esc>H., and @<esc>V. A sample MDB TRANSACTION STRING could be ‘E 000125 000000 0000 C. MDB bus data and MDB TRANSACTION STRING updating can be referred to as reporting or reporting data. A report is sent to the computing platform and processing moves to block 3212. - In
block 3212 having determined that thesystem 500 is ENABLED thecomputing platform 802 can send thesystem 500 the Toggle MDB CAPTURE mode ‘OFF’ command @<esc>I. Processing then moves to block 3214. - In
block 3214 thesystem 500 toggles ‘OFF’ the MDB CAPTURE mode and ends recording the data bytes exchanged between thesystem 500 and VMC by way of thesystem 500MDB interface 518. In response to receiving the MDB CAPTURE command @<esc>1 from thecomputing platform 802 thesystem 500 may respond by sending the response message STX+OFF-1+ETX+LRC. Processing then moves to block 3216. - In
block 3216 the computing platform can now request thesystem 500 to dump the captured MDB bus data by sending thesystem 500 the MDB BUFFER DUMP command @<esc>2. Processing then moves to block 3218. - In
block 3218 in response to receiving the MDB BUFFER DUMP @<esc>2 command thesystem 500 sends the content of the MDB buffer.Block 3218 shows a sample of such data, wherein the ‘G4-’ denotes data bytes sent by thesystem 500 and the ‘VMC-’ denotes data bytes sent by the VMC. - Referring to
FIG. 23K there is shown a computing platform andsystem 500 exchange to capture DEX bus messages routine 3300. Shown in the figure are messages being passed between a computing platform 802 (COMPUTING PLATFORM) and a system 500 (SYSTEM 500). - Routine 3300 is shown as example not a limitation, variations in the routine arise based on vending application,
system 500 configuration,computing platform 802 configuration, vending equipment configuration, and or other setup operational, or configuration issues. In an exemplary embodiment, G4, EPORT, asystem 500, a payment module, or audit-credit-interactive device, are all referred to as asystem 500. The cooperation betweensystem 500 and acomputing platform 802 to transact a cashless transaction can be referred to as a cashless transaction processing system. -
System 500 can initiate a DEX CAPTURE mode diagnostic routine. In this regard, DEX message data passed between the system 500 (denoted by ‘G4’ in the sample output block 3310) and the vending equipment VMC (VMC) can be captured and dumped tocomputing platform 802 for analysis. In an exemplary embodiment acomputing platform 802 can be a laptop computer, or other similar type of device. - The DEX CAPTURE mode can be useful in determining the inventory, price settings, vend information, vending equipment service status including errors, failures, and alarms, and other vending equipment related information. In addition, the DEX message bytes passed between the
system 500 and the VMC can be monitored and viewed during processes such as initialization, setup, and other vending activities. - Routine 3300 is an exemplary embodiment of the use of the DEX CAPTURE to capture vending machine related information. Processing begins in
block 3302. - In
block 3302 thecomputing platform 802 sends the Toggle DEX CAPTURE command @<esc>3 or @<esc>4 to thesystem 500. The @<esc>3 command captures full mode hexadecimal format. This format shows the handshaking data exchanges as well as the data itself expressed in hexadecimal byte code. The @<esc>4 command captures the parsed or ASCII format version. This format is first parsed to exclude the handshaking parameters and then the hexadecimal is converted to the ASCII equivalent. Processing then moves to block 3304. - In
block 3304 thesystem 500 toggles ‘ON’ the DEX CAPTURE mode and begins recording the data bytes exchanged between thesystem 500 and VMC by way of thesystem 500DEX interface 520. In response to receiving the DEX CAPTURE command @<esc>3 or @<esc>4 from thecomputing platform 802 thesystem 500 may respond by sending the response message STX+ON-3+ETX+LRC or STX+ON-4+ETX+LRC. Processing then moves to block 3308. - In
block 3308 thesystem 500 first responds to the VMC ending a DEX transfer with thesystem 500 by sending thecomputing platform 802 the response message STX+OFF-3+ETX+LRC or STX+OFF-4-ETX+LRC. Processing then movesblock 3306. - In
block 3306 the computing platform can now request thesystem 500 to dump the captured DEX data by sending thesystem 500 the DEX BUFFER DUMP command @<esc>5. Processing then moves to block 3310. - In
block 3310 in response to receiving the DEX BUFFER DUMP @<esc>5 command thesystem 500 sends the content of the DEX buffer.Block 3310 shows a sample of such data, wherein the ‘G4-’ denoted data bytes sent by thesystem 500 and the ‘VMC-’ denotes data bytes sent by the VMC. In addition, a sample of data for the @<esc>3 output hexadecimal and the @<esc>4 output ASCII. Processing then moves to block 3312. - In
block 3312 thecomputing platform 802 receives the DEX data dump. - While this invention has been described with reference to specific embodiments, 15 it is not necessarily limited thereto. Accordingly, the appended claims should be construed to encompass not only those forms and embodiments of the invention specifically described above, but to such other forms and embodiments, as may be devised by those skilled in the art without departing from its true spirit and scope.
Claims (11)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/071,021 US20140143074A1 (en) | 2001-03-26 | 2013-11-04 | Interactive interface effectuated vending |
Applications Claiming Priority (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US27859901P | 2001-03-26 | 2001-03-26 | |
US09/884,755 US6505095B1 (en) | 2001-06-19 | 2001-06-19 | System for providing remote audit, cashless payment, and interactive transaction capabilities in a vending machine |
US88879701A | 2001-06-25 | 2001-06-25 | |
US10/051,594 US7593897B1 (en) | 2001-06-19 | 2002-01-18 | Wireless system for communicating cashless vending transaction data and vending machine audit data to remote locations |
US8303202A | 2002-02-26 | 2002-02-26 | |
US10/100,680 US7865430B1 (en) | 2001-03-26 | 2002-03-18 | Cashless transaction payment module |
US10/118,123 US7630939B1 (en) | 2001-03-26 | 2002-04-08 | System and method for locally authorizing cashless transactions at point of sale |
US10/121,081 US7076329B1 (en) | 2002-04-12 | 2002-04-12 | Cashless vending transaction management by a vend assist mode of operation |
US10/138,385 US7131575B1 (en) | 2001-03-26 | 2002-05-03 | MDB transaction string effectuated cashless vending |
US10/153,478 US8596529B1 (en) | 2001-03-26 | 2002-05-22 | Interactive interface effectuated vending |
US14/071,021 US20140143074A1 (en) | 2001-03-26 | 2013-11-04 | Interactive interface effectuated vending |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/153,478 Continuation US8596529B1 (en) | 2001-03-26 | 2002-05-22 | Interactive interface effectuated vending |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140143074A1 true US20140143074A1 (en) | 2014-05-22 |
Family
ID=49640632
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/153,478 Active 2027-09-29 US8596529B1 (en) | 2001-03-26 | 2002-05-22 | Interactive interface effectuated vending |
US14/071,021 Abandoned US20140143074A1 (en) | 2001-03-26 | 2013-11-04 | Interactive interface effectuated vending |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/153,478 Active 2027-09-29 US8596529B1 (en) | 2001-03-26 | 2002-05-22 | Interactive interface effectuated vending |
Country Status (1)
Country | Link |
---|---|
US (2) | US8596529B1 (en) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150249353A1 (en) * | 2014-02-28 | 2015-09-03 | Nrg Energy, Inc. | Power Pack Vending Apparatus, System and Method of Use |
TWI605422B (en) * | 2016-01-08 | 2017-11-11 | en-xin Zhu | An interactive vending machine interaction system and its interactive management method using Bluetooth communication to manage personal information of members |
TWI611376B (en) * | 2016-03-18 | 2018-01-11 | Optional sales management method and system thereof | |
US10019724B2 (en) | 2015-01-30 | 2018-07-10 | PayRange Inc. | Method and system for providing offers for automated retail machines via mobile devices |
USD836118S1 (en) | 2015-01-30 | 2018-12-18 | Payrange, Inc. | Display screen or portion thereof with an animated graphical user interface |
USD862501S1 (en) | 2015-01-30 | 2019-10-08 | PayRange Inc. | Display screen or portion thereof with a graphical user interface |
US10438208B2 (en) | 2013-12-18 | 2019-10-08 | PayRange Inc. | Systems and methods for interacting with unattended machines using detectable trigger conditions and limited-scope authorization grants |
US20200372506A1 (en) * | 2019-05-24 | 2020-11-26 | Comenity Llc | Distributed credit account information |
US10891608B2 (en) | 2013-12-18 | 2021-01-12 | PayRange Inc. | Method and system for an offline-payment operated machine to accept electronic payments |
US10891614B2 (en) | 2013-12-18 | 2021-01-12 | PayRange Inc. | Method and system for presenting representations of payment accepting unit events |
US11074580B2 (en) * | 2013-12-18 | 2021-07-27 | PayRange Inc. | Device and method for providing external access to multi-drop bus peripheral devices |
US11205163B2 (en) | 2013-12-18 | 2021-12-21 | PayRange Inc. | Systems and methods for determining electric pulses to provide to an unattended machine based on remotely-configured options |
WO2022020513A1 (en) * | 2020-07-21 | 2022-01-27 | Payrange, Inc. | Device and method for providing external access to multi-drop bus peripheral devices |
WO2022034369A1 (en) * | 2020-08-14 | 2022-02-17 | Ezura, Llc | Telemetry system to audit transfers on electronic apparatus or devices for payment |
US11475454B2 (en) | 2013-12-18 | 2022-10-18 | PayRange Inc. | Intermediary communications over non-persistent network connections |
US11481780B2 (en) | 2013-12-18 | 2022-10-25 | PayRange Inc. | Method and system for asynchronous mobile payments for multiple in-person transactions conducted in parallel |
US11481781B2 (en) | 2013-12-18 | 2022-10-25 | PayRange Inc. | Processing interrupted transaction over non-persistent network connections |
US11966926B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Method and system for asynchronous mobile payments for multiple in-person transactions conducted in parallel |
US11966895B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Refund centers for processing and dispensing vending machine refunds via an MDB router |
US11972434B2 (en) * | 2019-11-20 | 2024-04-30 | Bread Financial Payments, Inc. | Distributed credit account information |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102006015255A1 (en) * | 2006-04-01 | 2007-10-04 | National Rejectors, Inc. Gmbh | Payment system for a vending machine |
US11011009B2 (en) * | 2010-03-29 | 2021-05-18 | Pascal Felique | Method and apparatus for controlling and monitoring a vending machine |
US20120239189A1 (en) * | 2011-03-18 | 2012-09-20 | INTUI SENSE Sarl | Systems and Methods for Vending Machine Control Using a Digital Panel |
US9349238B2 (en) | 2013-03-13 | 2016-05-24 | Pantry Retail, Inc. | Vending kit and method |
TWI594113B (en) | 2013-03-29 | 2017-08-01 | 慧榮科技股份有限公司 | Status switching method |
GB2562368B (en) | 2015-09-30 | 2021-08-11 | Hydration Labs Inc | Beverage dispensing |
US10692322B2 (en) * | 2016-05-27 | 2020-06-23 | Intel Corporation | Vending machine interface |
US10810821B2 (en) * | 2017-09-19 | 2020-10-20 | Inhand Networks Inc. | System and method for MDB data processing of vending machines |
CN109062089A (en) * | 2018-07-12 | 2018-12-21 | 山东科技大学 | A kind of automatic vending machine multi-channel control circuit system |
US11148927B2 (en) | 2018-07-27 | 2021-10-19 | Hydration Labs, Inc. | Beverage dispensing |
US11044167B2 (en) * | 2019-03-06 | 2021-06-22 | The Toronto-Dominion Bank | Intraday resource management system |
USD998401S1 (en) | 2020-08-31 | 2023-09-12 | Hydration Labs, Inc. | Dispensing device |
CN114780029B (en) * | 2022-04-12 | 2023-05-09 | 荣耀终端有限公司 | Device identification method and related device |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5091713A (en) * | 1990-05-10 | 1992-02-25 | Universal Automated Systems, Inc. | Inventory, cash, security, and maintenance control apparatus and method for a plurality of remote vending machines |
US5641050A (en) * | 1991-10-11 | 1997-06-24 | Verifone, Inc. | Dispensing machine with data card scanner apparatus and enhanced features |
US5860362A (en) * | 1996-09-13 | 1999-01-19 | Ncr Corporation | Newspaper vending machine with online connection |
US5988346A (en) * | 1997-11-10 | 1999-11-23 | Tedesco; Daniel E. | Method and apparatus for establishing and managing vending machine subscriptions |
US20020004690A1 (en) * | 1999-10-12 | 2002-01-10 | Paulucci Jeno F. | Vending machine |
US6397126B1 (en) * | 1999-05-11 | 2002-05-28 | Kim Marie Nelson | Interfaced dispensing machines and remote automated payment and inventory management system |
US6584309B1 (en) * | 1999-12-16 | 2003-06-24 | The Coca-Cola Company | Vending machine purchase via cellular telephone |
US7167892B2 (en) * | 1998-03-19 | 2007-01-23 | Isochron, Inc. | System, method and apparatus for vending machine wireless audit and cashless transaction transport |
US7455223B1 (en) * | 2005-08-29 | 2008-11-25 | Bob Jones University | RFID-based method for a networked cashless vending system |
Family Cites Families (114)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2703048A (en) | 1951-08-03 | 1955-03-01 | Tele Trip Policy Co Inc | Insurance policy vending and validating apparatus |
US4366481A (en) | 1980-03-26 | 1982-12-28 | Micro Magnetic Industries, Inc. | Vending machine acquisition system |
US4485300A (en) | 1982-03-18 | 1984-11-27 | Visa U.S.A., Inc. | Loss control system |
GB2172720B (en) | 1982-10-18 | 1987-06-10 | Mars Inc | A system for collecting data from a vending machine |
CA1222824A (en) | 1982-10-18 | 1987-06-09 | David Eglise | Data collection system |
US4999672A (en) | 1983-08-15 | 1991-03-12 | Lex Systems Southeast | Computer control of photocopiers |
US4780806A (en) | 1984-09-26 | 1988-10-25 | Minolta Camera Kabushiki Kaisha | Control device for an apparatus |
DE3509552A1 (en) | 1985-03-16 | 1986-09-18 | Vacuumschmelze Gmbh, 6450 Hanau | FERROMAGNETIC FILM FOR A TORQUE SENSOR |
US4812628A (en) | 1985-05-02 | 1989-03-14 | Visa International Service Association | Transaction system with off-line risk assessment |
US4737967A (en) | 1987-01-28 | 1988-04-12 | Hazeltine Corporation | Remote monitoring system receiver with dual baud rate selector |
US5077582A (en) | 1988-05-17 | 1991-12-31 | Monitel Products Corp. | Photocopy monitoring system |
US5132915A (en) | 1988-12-13 | 1992-07-21 | Postal Buddy Corporation | Document dispensing apparatus and method of using same |
US5206488A (en) | 1989-06-07 | 1993-04-27 | Mordechai Teicher | Credit card system including a central unit and a plurality of local units for conducting low-cost transactions |
US5150817A (en) * | 1990-06-15 | 1992-09-29 | Inn-Room Systems, Inc. | Methods and apparatus for dispensing articles |
US5337253A (en) | 1990-12-07 | 1994-08-09 | Kaspar Wire Works, Inc. | Vending machine data processing system |
US5285382A (en) | 1991-02-25 | 1994-02-08 | Keyosk Corporation | System and method for processing credit and debit card validity and funds transactions from vending machines and similar terminals |
US5225977A (en) | 1991-03-18 | 1993-07-06 | Hooper John B | Card payment system for service dispensing devices |
GB2255260B (en) | 1991-04-24 | 1995-06-14 | Mars Inc | Transaction systems |
US5440108A (en) | 1991-10-11 | 1995-08-08 | Verifone, Inc. | System and method for dispensing and revalung cash cards |
US5273183A (en) | 1992-02-18 | 1993-12-28 | Philip Tuttobene | Article vending machine |
EP0750283A4 (en) * | 1994-03-08 | 2000-03-01 | Oki Electric Ind Co Ltd | Transaction processing system and transaction processing method |
NO941202L (en) | 1994-03-30 | 1995-10-02 | Oeystein Konsmo | Method of monitoring and generating messages as well as equipment using the method |
AU2466095A (en) | 1994-04-28 | 1995-11-29 | Music Vending, Inc. | Music vending system |
US5450938A (en) | 1994-05-02 | 1995-09-19 | Xcp, Inc. | Card or cash actuated vending machine assembly |
US5728999A (en) | 1994-06-14 | 1998-03-17 | Advanced Retail Systems Ltd. | Vending machine, a vending system and methods for operating same |
US6056194A (en) | 1995-08-28 | 2000-05-02 | Usa Technologies, Inc. | System and method for networking and controlling vending machines |
US5608643A (en) * | 1994-09-01 | 1997-03-04 | General Programming Holdings, Inc. | System for managing multiple dispensing units and method of operation |
US5442568A (en) | 1994-11-15 | 1995-08-15 | Audit Systems Company | Vending machine audit monitoring system |
US6900720B2 (en) | 2001-12-27 | 2005-05-31 | Micro Enhanced Technology, Inc. | Vending machines with field-programmable locks |
US20050285716A1 (en) | 2001-12-27 | 2005-12-29 | Triteq Lock And Security, Llc | Electronic key control and management system for vending machines and the like |
US5591949A (en) * | 1995-01-06 | 1997-01-07 | Bernstein; Robert J. | Automatic portable account controller for remotely arranging for payment of debt to a vendor |
US6771981B1 (en) | 2000-08-02 | 2004-08-03 | Nokia Mobile Phones Ltd. | Electronic device cover with embedded radio frequency (RF) transponder and methods of using same |
US5555015A (en) | 1995-03-20 | 1996-09-10 | Intrinzix Technologies, Inc. | Wireless two way transmission between center and user stations via a relay |
US5628351A (en) | 1995-06-05 | 1997-05-13 | Shell Oil Company | Method for automated refuelling |
US6000522A (en) | 1995-06-12 | 1999-12-14 | Alice A Johnson | Multi-compartment and acceptors computerized vending machine |
US5596501A (en) | 1995-07-19 | 1997-01-21 | Powerplant Fuel Modules, Llc | System for dispensing fuel at remote locations, and method of operating same |
US5710887A (en) | 1995-08-29 | 1998-01-20 | Broadvision | Computer system and method for electronic commerce |
US5955718A (en) | 1995-10-06 | 1999-09-21 | Coin Acceptors, Inc. | Integrated credit/information exchange module |
CA2160496A1 (en) | 1995-10-13 | 1997-04-14 | Allan M. Brown | Electronic funds acceptor for vending machines |
US5924081A (en) | 1995-11-14 | 1999-07-13 | Audit Systems Co. | Vending machine audit monitoring system with matrix interface |
US5764639A (en) | 1995-11-15 | 1998-06-09 | Staples; Leven E. | System and method for providing a remote user with a virtual presence to an office |
US6038551A (en) | 1996-03-11 | 2000-03-14 | Microsoft Corporation | System and method for configuring and managing resources on a multi-purpose integrated circuit card using a personal computer |
US5850442A (en) | 1996-03-26 | 1998-12-15 | Entegrity Solutions Corporation | Secure world wide electronic commerce over an open network |
US6945457B1 (en) | 1996-05-10 | 2005-09-20 | Transaction Holdings Ltd. L.L.C. | Automated transaction machine |
US6181981B1 (en) | 1996-05-15 | 2001-01-30 | Marconi Communications Limited | Apparatus and method for improved vending machine inventory maintenance |
US5791449A (en) | 1996-05-30 | 1998-08-11 | Mars Incorporated | Bezel for a vending machine |
US6295482B1 (en) | 1996-06-26 | 2001-09-25 | Sun Microsystems, Inc. | Electronic newspaper vending machine |
US5941363A (en) | 1996-07-31 | 1999-08-24 | Proactive Vending Technology, Llc | Vending data collection system |
EP0866400A1 (en) | 1996-07-31 | 1998-09-23 | Nippon T.M.I. Co. Ltd. | Automatic commodity handling apparatus utilizing ic card |
JPH1097671A (en) | 1996-09-20 | 1998-04-14 | Media Maaketeingu Network:Kk | Commodity sales management method and device for automatic vending machine |
US5983200A (en) | 1996-10-09 | 1999-11-09 | Slotznick; Benjamin | Intelligent agent for executing delegated tasks |
US6446049B1 (en) * | 1996-10-25 | 2002-09-03 | Pole/Zero Corporation | Method and apparatus for transmitting a digital information signal and vending system incorporating same |
JPH10143732A (en) | 1996-11-12 | 1998-05-29 | Kuresutetsuku Internatl Corp:Kk | Automatic vending machine and distribution management system |
US6839775B1 (en) | 1996-11-15 | 2005-01-04 | Kim Y. Kao | Method and apparatus for vending machine controller configured to monitor and analyze power profiles for plurality of motor coils to determine condition of vending machine |
US5952638A (en) | 1996-11-25 | 1999-09-14 | Xerox Corporation | Space efficient method of electronic payments |
US5959869A (en) | 1996-12-03 | 1999-09-28 | The Coca-Cola Company | Vending machine controller and system |
US5930771A (en) | 1996-12-20 | 1999-07-27 | Stapp; Dennis Stephen | Inventory control and remote monitoring apparatus and method for coin-operable vending machines |
US6314169B1 (en) | 1997-02-06 | 2001-11-06 | Poweroasis, Inc. | Power and telecommunications access vending machine |
US6430268B1 (en) | 1997-09-20 | 2002-08-06 | Statsignal Systems, Inc. | Systems for requesting service of a vending machine |
US6574603B1 (en) | 1997-09-26 | 2003-06-03 | Gilbarco Inc. | In-vehicle ordering |
US5997170A (en) | 1997-11-03 | 1999-12-07 | Ident, Inc. | System and method for reporting vending status |
JPH11168427A (en) | 1997-12-05 | 1999-06-22 | Nec Corp | Information collection system |
GB9800854D0 (en) | 1998-01-16 | 1998-03-11 | Nexus Corp | A material and device for terminal transaction |
US6272117B1 (en) | 1998-02-20 | 2001-08-07 | Gwcom, Inc. | Digital sensing multi access protocol |
US6457038B1 (en) | 1998-03-19 | 2002-09-24 | Isochron Data Corporation | Wide area network operation's center that sends and receives data from vending machines |
US6119053A (en) | 1998-03-27 | 2000-09-12 | The Coca-Cola Company | Vending machine dual bus architecture |
US6234389B1 (en) | 1998-04-29 | 2001-05-22 | @Pos.Com, Inc. | PCMCIA-based point of sale transaction system |
US6116505A (en) | 1998-07-21 | 2000-09-12 | Gilbarco Inc. | Fuel transaction system for enabling the purchase of fuel and non-fuel items on a single authorization |
AU758958B2 (en) | 1998-09-10 | 2003-04-03 | Mei, Incorporated | A configurable vending machine audit module |
US6462644B1 (en) | 1998-11-19 | 2002-10-08 | The Coca-Cola Company | Network of vending machines connected interactively to data-base building host |
US6123223A (en) | 1998-12-21 | 2000-09-26 | Watkins; Kenneth M. | Automated vending system for floral arrangements |
US6367696B1 (en) | 1999-02-05 | 2002-04-09 | Hitachi, Ltd. | IC card processing device, automatic vending device, and selling method |
US6424884B1 (en) | 1999-03-03 | 2002-07-23 | The Coca-Cola Company | Vending machine with transponder interrogator |
FI990660A (en) | 1999-03-25 | 2000-09-26 | Mecsel Oy | Apparatus and method for buying a product from a vending machine |
GB2349003B (en) | 1999-04-16 | 2003-05-07 | Mars Inc | Money handling mechanism with peripheral port |
US6339731B1 (en) | 1999-09-03 | 2002-01-15 | Mars Incorporated | Configurable vending machine audit module |
US6443642B1 (en) | 1999-10-16 | 2002-09-03 | Sierra Design Group | Modular printing system |
JP2003512686A (en) | 1999-10-21 | 2003-04-02 | キュービック コーポレイション | A system for quickly distributing and adding values to fare cards |
CA2323292A1 (en) | 1999-10-27 | 2001-04-27 | Crane Company | Vending machine communication system |
US20020099608A1 (en) | 1999-10-27 | 2002-07-25 | Robert M. Pons | Tokenless vending system |
US7089322B1 (en) | 1999-10-28 | 2006-08-08 | Motient Communications Inc. | System and method of aggregating data from a plurality of data generating machines |
JP2001126124A (en) | 1999-10-28 | 2001-05-11 | Sanden Corp | Control system for automatic vending machine |
US6934862B2 (en) | 2000-01-07 | 2005-08-23 | Robertshaw Controls Company | Appliance retrofit monitoring device with a memory storing an electronic signature |
DE10000948A1 (en) | 2000-01-12 | 2001-08-02 | Siemens Ag | Arrangement for the provision and flexible charging of a product or service, and automatic dispenser for use in such and method for operating such |
US6473283B1 (en) * | 2000-01-12 | 2002-10-29 | Mp Electronics, Inc. | Voltage protection circuit for multi-drop bus of an automated coin vending machine |
US20010037291A1 (en) | 2000-03-17 | 2001-11-01 | Allen Dale F. | Internet based single entry field electronic payment interface |
JP2001344640A (en) | 2000-03-29 | 2001-12-14 | Sanyo Electric Co Ltd | Automatic vending machine managing method and automatic vending machine |
US6527176B2 (en) | 2000-03-31 | 2003-03-04 | Robert Baric | Collective payment and control system |
US8903737B2 (en) | 2000-04-25 | 2014-12-02 | Accenture Global Service Limited | Method and system for a wireless universal mobile product interface |
US7013337B2 (en) | 2000-05-12 | 2006-03-14 | Isochron, Llc | Method and system for the optimal formatting, reduction and compression of DEX/UCS data |
US6804252B1 (en) | 2000-05-19 | 2004-10-12 | Ipr Licensing, Inc. | Automatic reverse channel assignment in a two-way TDM communication system |
US6487540B1 (en) | 2000-07-25 | 2002-11-26 | In2M Corporation | Methods and systems for electronic receipt transmission and management |
US6427912B1 (en) | 2000-08-16 | 2002-08-06 | Coin Acceptors, Inc. | Off-line credit card transaction system and method for vending machines |
TWI235314B (en) | 2000-08-23 | 2005-07-01 | Sanden Corp | Management system for vending machines |
US6859761B2 (en) | 2001-01-16 | 2005-02-22 | Bluesoft Ltd. | Accurate distance measurement using RF techniques |
EP1366448A2 (en) | 2001-01-29 | 2003-12-03 | U.S. Wireless Data, Inc. | Method and apparatus for conducting live, point-of-sale, electronic monitoring and transaction services |
US20020107742A1 (en) | 2001-02-02 | 2002-08-08 | Magill J. Breck | System for and method of transacting non-fuel purchases using an island transaction terminal |
US7110954B2 (en) | 2001-03-12 | 2006-09-19 | University Of Hong Kong | Wireless purchase and on-line inventory apparatus and method for vending machines |
US7032038B1 (en) | 2001-03-22 | 2006-04-18 | Xilinx, Inc. | Configurable peripheral devices |
US7131575B1 (en) | 2001-03-26 | 2006-11-07 | Usa Technologies, Inc. | MDB transaction string effectuated cashless vending |
US6505095B1 (en) | 2001-06-19 | 2003-01-07 | Usa Technologies, Inc. | System for providing remote audit, cashless payment, and interactive transaction capabilities in a vending machine |
US7076329B1 (en) | 2002-04-12 | 2006-07-11 | Usa Technologies, Inc. | Cashless vending transaction management by a vend assist mode of operation |
US7870029B2 (en) | 2001-05-03 | 2011-01-11 | International Business Machines Corporation | Determining the availability of purchasable items in a network environment |
JP4560237B2 (en) | 2001-05-24 | 2010-10-13 | サンデン株式会社 | Deposit system using vending machines |
US20020188378A1 (en) | 2001-06-12 | 2002-12-12 | Davin Sufer | Vending machine wireless point of sale inventory system |
AU2002355548A1 (en) | 2001-08-07 | 2003-02-24 | Mars Incorporated | Vending audit system |
US6754558B2 (en) | 2001-08-28 | 2004-06-22 | Vending Management Services Ltd. | Efficient collection of information from vending machines |
US6772048B1 (en) | 2001-10-03 | 2004-08-03 | Coin Acceptors, Inc. | Vending machine system |
US6854642B2 (en) | 2001-10-19 | 2005-02-15 | Chesterfield Holdings, L.L.C. | System for vending products and services using an identification card and associated methods |
US6839610B2 (en) | 2001-10-23 | 2005-01-04 | Mars Incorporated | Retrofit audit system |
US20030149827A1 (en) | 2002-02-01 | 2003-08-07 | Chris Smolen | Multi-drop bus to personal computer interface |
US20030204391A1 (en) | 2002-04-30 | 2003-10-30 | Isochron Data Corporation | Method and system for interpreting information communicated in disparate dialects |
US7203486B2 (en) | 2003-05-19 | 2007-04-10 | France Telecom | Wireless system having a dynamically configured multimodal user interface based on user preferences |
US6934594B2 (en) | 2003-07-18 | 2005-08-23 | Dell Products L.P. | System for determining carrier service using logistics considerations |
-
2002
- 2002-05-22 US US10/153,478 patent/US8596529B1/en active Active
-
2013
- 2013-11-04 US US14/071,021 patent/US20140143074A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5091713A (en) * | 1990-05-10 | 1992-02-25 | Universal Automated Systems, Inc. | Inventory, cash, security, and maintenance control apparatus and method for a plurality of remote vending machines |
US5641050A (en) * | 1991-10-11 | 1997-06-24 | Verifone, Inc. | Dispensing machine with data card scanner apparatus and enhanced features |
US5860362A (en) * | 1996-09-13 | 1999-01-19 | Ncr Corporation | Newspaper vending machine with online connection |
US5988346A (en) * | 1997-11-10 | 1999-11-23 | Tedesco; Daniel E. | Method and apparatus for establishing and managing vending machine subscriptions |
US7167892B2 (en) * | 1998-03-19 | 2007-01-23 | Isochron, Inc. | System, method and apparatus for vending machine wireless audit and cashless transaction transport |
US6397126B1 (en) * | 1999-05-11 | 2002-05-28 | Kim Marie Nelson | Interfaced dispensing machines and remote automated payment and inventory management system |
US20020004690A1 (en) * | 1999-10-12 | 2002-01-10 | Paulucci Jeno F. | Vending machine |
US6584309B1 (en) * | 1999-12-16 | 2003-06-24 | The Coca-Cola Company | Vending machine purchase via cellular telephone |
US7455223B1 (en) * | 2005-08-29 | 2008-11-25 | Bob Jones University | RFID-based method for a networked cashless vending system |
Cited By (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11501296B2 (en) | 2013-12-18 | 2022-11-15 | PayRange Inc. | Method and system for presenting representations of payment accepting unit events |
US11966895B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Refund centers for processing and dispensing vending machine refunds via an MDB router |
US11966920B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Method and system for presenting representations of payment accepting unit events |
US11966898B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Systems and methods for determining electric pulses to provide to an unattended machine based on remotely-configured options |
US11966926B2 (en) | 2013-12-18 | 2024-04-23 | PayRange Inc. | Method and system for asynchronous mobile payments for multiple in-person transactions conducted in parallel |
US11935051B2 (en) | 2013-12-18 | 2024-03-19 | Payrange, Inc. | Device and method for providing external access to multi-drop bus peripheral devices |
US11494751B2 (en) | 2013-12-18 | 2022-11-08 | PayRange Inc. | Systems and methods for determining electric pulses to provide to an unattended machine based on remotely-configured options |
US10438208B2 (en) | 2013-12-18 | 2019-10-08 | PayRange Inc. | Systems and methods for interacting with unattended machines using detectable trigger conditions and limited-scope authorization grants |
US10719833B2 (en) | 2013-12-18 | 2020-07-21 | PayRange Inc. | Method and system for performing mobile device-to-machine payments |
US11488174B2 (en) | 2013-12-18 | 2022-11-01 | PayRange Inc. | Method and system for performing mobile device-to-machine payments |
US10891608B2 (en) | 2013-12-18 | 2021-01-12 | PayRange Inc. | Method and system for an offline-payment operated machine to accept electronic payments |
US10891614B2 (en) | 2013-12-18 | 2021-01-12 | PayRange Inc. | Method and system for presenting representations of payment accepting unit events |
US11074580B2 (en) * | 2013-12-18 | 2021-07-27 | PayRange Inc. | Device and method for providing external access to multi-drop bus peripheral devices |
US11205163B2 (en) | 2013-12-18 | 2021-12-21 | PayRange Inc. | Systems and methods for determining electric pulses to provide to an unattended machine based on remotely-configured options |
US11481781B2 (en) | 2013-12-18 | 2022-10-25 | PayRange Inc. | Processing interrupted transaction over non-persistent network connections |
US11481780B2 (en) | 2013-12-18 | 2022-10-25 | PayRange Inc. | Method and system for asynchronous mobile payments for multiple in-person transactions conducted in parallel |
US11481772B2 (en) | 2013-12-18 | 2022-10-25 | PayRange Inc. | Method and system for presenting representations of payment accepting unit events |
US11475454B2 (en) | 2013-12-18 | 2022-10-18 | PayRange Inc. | Intermediary communications over non-persistent network connections |
US20150249353A1 (en) * | 2014-02-28 | 2015-09-03 | Nrg Energy, Inc. | Power Pack Vending Apparatus, System and Method of Use |
US11239674B2 (en) * | 2014-02-28 | 2022-02-01 | Nrg Energy, Inc. | Power pack vending apparatus, system and method of use for charging packs with biased locking arrangement |
US10084329B2 (en) * | 2014-02-28 | 2018-09-25 | Nrg Energy, Inc. | Power pack vending apparatus, system, and method of use for charging power packs with biased locking arrangement |
USD836118S1 (en) | 2015-01-30 | 2018-12-18 | Payrange, Inc. | Display screen or portion thereof with an animated graphical user interface |
US11468468B2 (en) | 2015-01-30 | 2022-10-11 | PayRange Inc. | Method and system for providing offers for automated retail machines via mobile devices |
US11961107B2 (en) | 2015-01-30 | 2024-04-16 | PayRange Inc. | Method and system for providing offers for automated retail machines via mobile devices |
US10019724B2 (en) | 2015-01-30 | 2018-07-10 | PayRange Inc. | Method and system for providing offers for automated retail machines via mobile devices |
USD862501S1 (en) | 2015-01-30 | 2019-10-08 | PayRange Inc. | Display screen or portion thereof with a graphical user interface |
TWI605422B (en) * | 2016-01-08 | 2017-11-11 | en-xin Zhu | An interactive vending machine interaction system and its interactive management method using Bluetooth communication to manage personal information of members |
TWI611376B (en) * | 2016-03-18 | 2018-01-11 | Optional sales management method and system thereof | |
US20200372506A1 (en) * | 2019-05-24 | 2020-11-26 | Comenity Llc | Distributed credit account information |
US11972434B2 (en) * | 2019-11-20 | 2024-04-30 | Bread Financial Payments, Inc. | Distributed credit account information |
WO2022020513A1 (en) * | 2020-07-21 | 2022-01-27 | Payrange, Inc. | Device and method for providing external access to multi-drop bus peripheral devices |
WO2022034369A1 (en) * | 2020-08-14 | 2022-02-17 | Ezura, Llc | Telemetry system to audit transfers on electronic apparatus or devices for payment |
Also Published As
Publication number | Publication date |
---|---|
US8596529B1 (en) | 2013-12-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7693602B1 (en) | Cashless vending transaction management by a vend assist mode of operation | |
US7131575B1 (en) | MDB transaction string effectuated cashless vending | |
US8596529B1 (en) | Interactive interface effectuated vending | |
US6505095B1 (en) | System for providing remote audit, cashless payment, and interactive transaction capabilities in a vending machine | |
US7630939B1 (en) | System and method for locally authorizing cashless transactions at point of sale | |
US7690495B1 (en) | Card reader assembly | |
US7865430B1 (en) | Cashless transaction payment module | |
US7593897B1 (en) | Wireless system for communicating cashless vending transaction data and vending machine audit data to remote locations | |
US10810565B2 (en) | Vending data communications systems | |
US10755257B2 (en) | System and methods associated with vending machine telemetry, replenishment, and configuration utilizing multiple types communication networks | |
CA2437330A1 (en) | Method and apparatus for conducting live, point-of-sale, electronic monitoring and transaction services | |
US6056194A (en) | System and method for networking and controlling vending machines | |
US8998082B2 (en) | Multimedia system and methods for controlling vending machines | |
US7085556B2 (en) | Vending machine | |
TW554298B (en) | Apparatus, systems and methods for wireless purchase and on-line inventory management in vending machines | |
US20070100696A1 (en) | Multimedia system and method for controlling vending machines | |
US20030168508A1 (en) | Money handling device having universal interface board | |
WO2015186141A1 (en) | System and method for a vending machine for money transfer | |
KR101950581B1 (en) | Paying system of vending machine easy to add of payment means using smart phone | |
US20030182243A1 (en) | Method and apparatus for remote control of electronically activated tasks | |
WO1996007134A1 (en) | System and method for networking and controlling vending machines | |
WO2003021397A2 (en) | System for coordinating transaction for pos terminals | |
US20040185937A1 (en) | Wireless communication terminal unit, gaming machine, information managing apparatus and gaming system | |
RU112468U1 (en) | SYSTEM OF ELECTRONIC PAYMENT OF GOODS IN TRADE AUTOMATICS | |
WO2022249029A1 (en) | Multifunction vending machine control apparatus and system for dispensing food and vending machine comprising said apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: USA TECHNOLOGIES, INC., PENNSYLVANIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KOLLS, H. BROCK;REEL/FRAME:031711/0697 Effective date: 20020522 |
|
AS | Assignment |
Owner name: HERITAGE BANK OF COMMERCE, CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:USA TECHNOLOGIES, INC.;REEL/FRAME:038324/0485 Effective date: 20160329 |
|
AS | Assignment |
Owner name: USA TECHNOLOGIES, INC., PENNSYLVANIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:AVIDBANK CORPORATE FINANCE, A DIVISION OF AVIDBANK;REEL/FRAME:038329/0732 Effective date: 20160331 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., ILLINOIS Free format text: NOTICE OF GRANT OF SECURITY INTEREST;ASSIGNOR:USA TECHNOLOGIES, INC.;REEL/FRAME:044787/0597 Effective date: 20171109 |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |
|
AS | Assignment |
Owner name: CANTALOUPE SYSTEMS, INC. (SUCCESSOR IN INTEREST TO Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JP MORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:050916/0732 Effective date: 20191031 Owner name: USA TECHNOLOGIES, INC., PENNSYLVANIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JP MORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:050916/0732 Effective date: 20191031 |