Dispensing system and method with radio frequency customer identification

DISPENSING SYSTEM AND METHOD WITH RADIO

FREQUENCY CUSTOMER IDENTIFICATION

Cross Reference

This application claims the benefit of U.S. Provisional Application No. 60/009,369. nied December 29. 1995.

Background of the Invention

The présent invention relates to dispensers and, more particulariy, to fùei dispensers that uses radio frequencv identification technology to automatically identify a customer with little or no customer interaction in order to authorize the sale of products or services to the customer and to subsequently bill the customer’s charge account fof the products or services. The présent invention 15 is particulariy useful in a service station environment where customers may purchase fuel for their vehicles, obtain a car wash, or purchase other items such as food, drinks, or sundries from a convenience store, or drive-through window, that may be located on the premises.

Typically, when a customer purchases fuel at a service station, the customer présents payment, in the form of cash or credit/debit card, to the service station attendant either before or 20 after fueling. The. attendant controls the activation of the dispenser to allow fueling. If payment is required before fueling may begin, the attendant must activate a switch, typically near the cash register, in order to unlock the dispenser to allow füeling to begin. Once fueling has been completed and the dispenser nozzle has been retumed to its seat, the attendant manually resets the dispenser again through activation of a switch at the cash register.

An example of an existing service statioft control System that intégrâtes dispenser control and cash register control is the Wayne Plus/2 control System available from Wayne Division, Dresser Industries, Inc. of Austin, Texas. The Wayne Plus/2 System includes a host computer or site controller and a point-ofcsale terminal that interfaces with the attendant.

The Wayne Plus/2 host computer is provided with a microprocessor and a pump controller 30 board that is electrically linked to the various dispensers of the station to provide pump control. The pump controller board tums the dispensers on or off, controls the flow rate, and keeps track of the amount of fuel dispensed. The host computer is also provided with memory, communication ports, and a serial input/output board (“SIO”) that may be linked to a remote customer-authorization computer network.

010801

-25 The point-of-sie termina) (also known as a Wayne Plus brând Retail Control System) includes a card reader for reading and identifying credit/debit cards, a keyboard for use by the attendant, and a display. The attendant can use the point-of-sale terminal to process payments and to control the activation of the dispensers. Should a customer choose to use a credit/debit card for payment, the attendw wns the card through the card reader, and the credit/debit card information 10 is forwarded to the remote customer-authorization network for vérification and billing,

Many service stations, however, aïe now equipped with credit/debit card readers at the dispensers for direct use by the customer. An example of a service station System that intégrâtes dispenser control, cashregister control, and credit/debit card processing that may be originated at the dispenser is the Vajue Plus/3™ System available from Wayne Division, Dresser Industries, Inc.

of Austin, Texas. The Wayne Plus/3 System is similar to the Wayne Plus/2 system described above;

however, the host computer or site controller has been modified to accommodate dispensers equipped with custorner-activated-terminals (CATs) electronically linked to the host computer.

The cusKMner-activated-tenmnals(CATs) each hâve a card reader, a dispiay which displays messages to the customer, a key pad for use by the customer to make fueling and payment 20 sélections, a printer for printing receipts, and individual price displays corresponding to the individual fuel dispensng nozzles of the dispenser. Examples of dispensers equipped with such customer-activated teminals (CATs) are the Vista brand fuel dispensers available from Wayne Division, Dresser Industries, Inc. of Austin, Texas.

The Wayne f*Lus/3 host computer is loaded with a software driver (also referred to herein as a “primitive’¹) forconîrolling and interfacing with the CATs. Before a customer begins fueling, the customer usesthe keyboard of the CAT to select the type of payment desired (e.g., cash or credit/debit card). Kthe customer chooses to pay with a credit/debit card, the customer inserts the credit/debit card intwthe card reader at the CAT. The customer then waits for a message to display indicating that the cœ-tomer may begîn fueling. The CAT forwards the credit/debit card information to the host computer which in tum forwards the credit/debit card information to the remote customer authorinaion network for vérification and billing. U.S. Patent No. 5,340,969 issued ί

August 23, 1994 tî Dresser Industries, Inc, describes a method and apparatus for approving or disapproving fuel tSs.pensing transactions using crédit cards.

In both type of Systems described above, the customer is required to interact (for payment purposes) with ettïitr the service station attendant or with the customer-activated terminal (CAT) at the dispenser. Il, S. Patent No. 5,072,380 issued to Robert E. Randelman et al. describes an auto marie vehicle récognition and customer billing System that may be used in a service station

010801 environment. The system automatically recognizes vehicles and correlates the purchase of products and services with the vehicle.

The system of the '380 patent inciudes an antenna embedded in the ground near a gasoiine dispensing pump. The antenna is connected to a controller located in a housing near the antenna. The controller controls the output of a radio frequency signal from the antenna and can detect an 10 RF input signal. The antenna is always energized and, therefore, créâtes an electromagnetic field at a predetermined radio frequency in the fueling area.

The system of the ‘380 patent also inciudes an emitter (or card) affixed to a vehicle. The card comprises an RF coil and integrated circuit component. When the card crosses :he electromagnetic field, the electromagnetic field energizes the card. The activated card then emits 15 an encoded electromagnetic puise signal. The controller receives the signal and converts it into a data bit stream. A computer receives the data bit stream from the controller and in tum utilizes the data for displaying information on the pump display, for controlling the fuel dispenser, and for biiling purposes.

One disadvantage of the ‘380 patent is that the antenna which emits the electromagnetic 20 field is embedded in the ground near the fuel dispenser. The installation of such an antenna (or antennas where there is more than one dispenser) can be costly and can create a fire hazard from fueling spilis or leaks from the fuel storage tanks typically located under ground near the fuel dispensera. Furthermore, where multiple dispensera are présent and therefore multiple antennas and controllers are présent, the system does not adequately prevent a vehicle card from being activated 25 by more than one antenna at a time and detected by more than one controller at a time, such as may happen where antennas are positioned near each other and therefore interfère with one another. Furthermore, the system does not prevent the. inadvertent détection of vehicle cards not intended to be used in a fueling transaction.

Many service stations provide for separate fueling on both sides of a dispenser and/or hâve 30 several closely-spaced rows of dispensera. Wrth such a dispenser arrangement and the system of the ‘380 patent, the vehicle card of a vehicle stopped between antennas may be detected by the wrong controller, i.e., one not associated with the dispenser where the vehicle is actually receiving fuel, or may wrongly be detected by a controller, i.e., where the vehicle is stopped near an antenna but is not fueling.

Other automatic identification Systems exist that employ radio frequency techiiology. For example. Texas Instruments Incorporated of Dallas, Texas, markets a number of radio frequency identification svstems referred to commercially as its TIRIS™ (Texas Instruments Registration and

019801

Identification Systems) product line. The TIRIS™ product line includes radio frequency transponders (read-only as well as read-writc) that may be low frequency or high frequency in their operation and which may be attached to or embedded in objects or may be hand-held. Readers, through antennes, send out radio frequency waves to the transponders, and the transponders broadcast stored data back to the reader for processing. Suggested applications of the TIRIS™ 10 product line include an automatic access system for parking lot entrance and exit barriers, anti-theft Systems for vehicles (where a transponder is placed in the ignition key and a transceiver module is positioned near the ignition), and a foel dispensing system (where a transponder is mounted beside the vehicle’s fuel tank and a transceiver is mounted on the fuel dispensing nozzle). The foel dispensing system application, however, is not désirable because maintenance of the foel dispensing 15 nozzle with the transceiver can présent a service problem as well as a replacement problem and, furthermore, the location of the transponder and transceiver can create a fire hazard.

Application of the above-described radio frequency customer identification (RF-CID) technology to a service station environment is fraught with heretofore unresolved problems. In large service stations with multiple islands of two-sided pumps and heavy, unpredictable traffic patterns, 20 the potential exists for unintended crosstalk, i.e., “cross-reads,” of an RF-CID transponder attached to a vehicle by the wrong antenna/reader. Crosstalk can resuit in the erroneous billing of a customer for services never received. While commercially available readers can be physically linked or otherwise operated to synchrorüze their transmission puises, a system and strategy has not yet been developed for effectively synchronizing multiple readers in a service station environment to 25 minimize, if not eliminate, cross-reads. The problem of implementing a synchronization strategy, once determined, is forther complicated by indïvidual readers dropping out of synchronization in the course of detectîng transponders.

In addition to transponder crosstalk, other aspects of the customer identification process are less than idéal when RF-CID technology is used in a service station environment. As mentioned 30 previously, the vehicle récognition system ofthe ‘380 patent, in addition to providing an impraciical antenna/controller arrangement, uses a vehicle identification method that begins to activate the

F account when it is determined that the vehicle in proximity to the antenna has stopped moving, and upon such détermination, locks out other antennas (and their respective pump controllers) from reading the same customer’s transponder. While the foregotng may be adéquate in an idealized 35 service station environment with predictable vehicle flow patterns, this method of activation is unreliable in a station with multiple islands of two-sided pumps and can resuit in improper or problematic customer activation.

010801

- 5 What is needed, therefore, is a radio frequency customer identification (RF-CED) System for a service station that reiiably and accurately identifies and charges customers for purchases of services or products in an environment having multiple dispensers and/or sale sites.

Summary of the Invention

A dispensing System and method of the présent invention, accordinglv, utilizes radio frequency customer identification capabilities in a ser/ice station environment to reiiably and accurately identify and charge customers for their purchases.

To this end, the dispensing System and method of the présent invention détermines whether a transponder containing customer identification data is within range of a dispenser, the dispenser requiring activation by the customer to initiale a transaction and the dispenser including a reader associated therewith for emitting radio frequency signais within the dispenser range, and for receiving customer identification data from the transponder responsive to the emitted radio frequency signais received by the transponder. When the transponder is within range of the dispenser, an in-range indication is provided to the customer. A détermination is made whether the dispenser has been activated by the customer following a détermination that the transponder is within the dispenser range. Upon activation of the dispenser following the détermination that the transponder is within the dispenser range, the customer identification data received by the reader is associated with a transaction at the activated dispenser, whereupon the transaction at the activated dispenser is permitted and charged to the customer according to the customer identification data.

In another aspect, the présent invention is embodied as a dispensing System that includes a transponder containing customer identification data; a dispenser for providing a customer transaction within a dispensing area; antennas each associated with the dispensing area of the dispenser, the antennas including a long range antenna located relative to the dispenser for use by the transponder of a type mounted to a vehicle, and a short range antenna located relative to the dispenser for use by the transponder of a type that is hand-held; at least one reader connected to the antennas for * emitting radio frequency signais from the long range antenna within a selected long range of the dispensing area, and from the short range antenna within a selected short range of the dispensing area, and for receiving customer identification data from the transponder, the customer identification data being received by the reader responsive to the emitted radio frequency signais when the transponder is within its range of the dispensing area; and a processor arrangement connected to the at least one reader and to the dispenser for associating customer identification data received at the

010801

-65 dispensing area with a transaction at the dispenser, whereupon the transaction at the dispenser is charged to the customer according to the customer identification data.

The présent invention overcomes the above-noted problems with the prior art by providing a reliable, safe, customer-friendly identification system that can automatïcally identify a customer purchasing services or products at a service station, and bilJ the customer’s account for any 10 purchases made. The system of the présent invention interfaces smoothly with existing service station Systems to provide overall customer identification, billing, account status, and pump control.

With the customer identification system of the présent invention, the customer is provided the fiexibility of using either a long-range, vehicle-mounted transponder and/or a short-range, handheld transponder for automatic customer identification and billing, or may ovenide the use of a 15 transponder and select a more conventional method ofpayment. Both types of transponders contain Personal customer identification data which is broadcast in response to predetermined radio frequency (“RF’) waves.

The system can include long-range antennas that are mounted to the tops of the fuel dispensers and short-range antennas that are mounted to the sides of the fuel dispensers. Readers 20 housed in the dispensers send radio frequency power puises to the antennas which in tum direct the power puises to create electromagnetic fields. The antennas are optimally positioned so that the electromagnetic fields cover predetermined areas near the dispenser. The frequency, power, and antenna design hâve been selected to insure a proper read area and to eliminate reflective signais that are présent at UHF frequencies. The areas are set so that there is Utile or no overlap with 25 electromagnetic fields that may be created at adjacent or nearby dispensers. In the case of a longrange antenna, the electromagnetic field may cover an area that extends several feet from the dispenser; whereas* in the case of a short-range antenna, the electromagnetic field may extend several inches from the dispenser.

The antennas also pick-up customer identification data that is broadcast by the transponders.

In particular, if a vehicle-mounted transponder enters the electromagnetic field created by a longrange antenna, the vehicle-mounted transponder will become activated and broadcast its customer identification (“CED”) code. The long-range antenna detects the CED code and sends the code to the associated reader for decoding and processing. Similarly, if a hand-held transponder enters the electromagnetic field created by a short-range antenna such as when a customer waves the transponder in front of the short-range antenna, the hand-held transponder will bccome activated and broadcast its customer identification (CID”) code. The short-range antenna detects the CED code and sends the code to the associated reader for decoding and processing.

010801

-7·

In order to further minimize the potential for interférence between antennas of adjacent or nearby dispensers, the system of the présent invention coordinates the transmission of the puise waves from the various readers. In general, the readers selectively send out puise waves so that onlv antennas facing the same direction send out puise waves at the same time. Other puise timing arrangements could be used for other antenna configurations to eliminate interférence from nearbv dispensers. The system uses svnc puises and timing to coordinate the transmission of power puises through the various antennas of the system.

The system of the présent invention also provides an alert indication for alerting the customer when a transponder has been detected and the customer is authorized to begin fueling. The alert may be in the form of a light positioned on the dispenser which tums on and off in response to various triggers such as the détection or non-detection of a transponder by an associated antenna. the removal or retum of an associated fuel nozzle to its seat, the sélection of an altemate payment method (e.g., credit/debit card or cash), the recent détection and use of a transponder at the service station, the approval of crédit, or the déniai of crédit.

A technical advantage of the invention is that it intégrâtes easily with the user interface of existing service station equipment.

/Another advantage of the invention is that it provides the customer flexibility in selecting payment methods without eliminating options available with existing payment processing Systems.

Another advantage is that it can be safely and unobtrusively installed in a service station.

Brief Description of the Drawings

Fig. 1 is a schematic block diagram illustrating an overhead view of a service station equipped with the customer identification system of the présent invention.

Fig. 2 is a graph plotting transponder capacitor voltage with respect to time for a transponder used with the system of Fig. 1.

Fig. 3 A is a partial rear perspective view of the back end of a vehicle illustrating the placement of a vehicle-mounted transponder used with the system of Fig. 1.

Fig. 3B illustrâtes a card hand-held transponder and a key ring hand-held transponder used with the system of Fig. 1.

Fig. 4A is a side view of a dispenser used with the system ofFig. 1.

Fig. 4B is an end view of the dispenser ofFig. 4A.

·· Fig. 5A is a side view of another embodiment of a dispenser used with the system ofFig. 1.

Fig. 5B is an end view ofthe dispenser ofFig. 5A.

01Û801 • 8

Figs. 6A and 6B are schematic block diagrams illustrating components of a dispenser for connection to a host computer used with the System of Fig. 1.

Fig. 7 is a schematic block diagram of the site wiring between readers and the host computer of the System of Fig. 1.

Fig. 8 is a schematic représentation of a service station environment and the arrangement of 10 dispensers therein illustrating a reader synchronization strategy for the System of Fig. 1.

Figs. 9A - 9C are timing diagrams of communications signais on the synchronization line between master and slave readers of the System of Fig. 1,

Figs. 10A and 10B are detailed timing diagrams showîng communications to and from a master reader of the System of Fig. 1.

Figs. 11A- 111 and 12 are flowcharts illustrating the user operation ofthe System ofFig. 1.

Fig. 13 is a diagram illustrating the major software tasks and subsystems involved in the handling of a customer identification (CID) transaction for the System ofFig. 1.

Fig. 14 is a diagram illustrating theTransponder Reader Task’s Data Flow for the system of Fig. 1.

Fig. 15 is a diagram illustrating the Retum on Status Change interface for the system ofFig.

1.

Fîg. 16 is a diagram illustrating the Authorization Request and Reply Handling for the System ofFig. 1.

Figs. 17A - 17N and 17Q are flowcharts illustrating the customer identification primitive 25 tasks ofthe system ofFig. 1.

Detailed Description of the Preferred Embodiment

In Fig. 1, the référencé numéral 10 refers to a customer identification (CID) system embodying features of the présent invention. The system 10 electronically identifies a customer, authorizing a transaction involving the purchase of goods or services by that customer, and 30 subsequently bills the customer's account for the services. In one embodiment the system 10 identifies, authorizes, and bills customers for services provided at a service station. Generally, the system 10 allows customers to drive up to a fuel dispenser and immediately begin pumping fuel (or hâve fuel pumped for them) without having to go inside the service station building to pay for the fuel or having to insert a crédit card into a card reader at the fuel dispenser. As explained further 35 below, the system 10 may also be used for other services at the station such as a car wash or for making payments inside a convenience store.

010801

1. SYSTEM OVF.RVTEW

In one embodiment (Fig. 1), the system 10 is implemented in a service station environment that includes two service islands 12, each having two dispensers or fuel pumps 14, it beine understood that the number of islands and pumps, as well as their geometry and relationship to one another, may vary according to the requirements of the environment. Communication and 10 synchronization lines, discussed more follv below, connect the dispensers 14 to a host computer 16 for controiling operation of the dispensers. An additional site 18, representing a car wash. food service, payment station or other amenity, is also connected to the computer 13. It is understood that each of the dispensers 14 includes a dispensing area on each of the opposing sides cf the dispenser, each of which has at least one fuel nozzle (not shown) and a customer activated terminai 15 (CAT) (shown in Figs. 4A and 5A) for performing traditional dispensing fonctions as well as the functions to be described in detail below. It is also understood that the computer 16 may be connected to a network (not shown) for performing fonctions including, but not limited to, customer billing vérification.

Radio frequency customer identification (RF-CID) readers 20 are included with each of the 20 dispensers 12 and with the site 18 (not shown). Connected to each reader 20, and mounted to each foel dispenser 14, are four antennas: two (2) long-range antennas 22A, 22B mounted to the top of the dispenser 14 (on each opposing side thereof) for detecting vehicle-mounted customer transponders 23, and two (2) short-range antennas 24A, 24B mounted inside the head of the dispenser 14, one on each side of the dispenser, for detecting hand-held customer transponders 25.

As discussed in detail below, each reader 20 poils the four antennas 22A, 22B, 24A, 24B of each dispenser 14, sending power puises to the antennas, reading the customer identification (CID) data detected by the antennas from the transponders (e.g., the transponders 23 or 25) and sending the data to the host computer 16. For example, it is contemplated that a vehicle 28 entering a dispensing area in front of one of the fuel dispensers 14 will include a transponder 23 mounted y thereto such that the long-range antenna 22B (as shown in Fig. 1) on the dispenser 14 nearest the vehicle will read the CID data contained in the transponder.

The transponders 23,24 are radio frequency identification tags (RHD tags) that may either be mounted to the customers¹ cars or may be hand-held, key ring/chain or crédit card style units. The transponders 23,25 contain customer identification (CID) data that is broadcast in response to 35 receiving a predetermined radio frequency (“RF’) wave (i.e., a power puise). The RF wave is sent by a ‘reader 20 housed in one or more of the dispensers 14. The antennas 22A, 22B, 24A, 24B mounted to the dispensers 14 read the broadcast data and send the data to the readers 20 for

019801

105 decoding and further transmission to the host computer 16 or also to a network where the data can be verified and the customer billed after completion of the fueling or other purchase.

Suitable transponders 23,25, antennas 22A, 22B, 24A. 24B, and readers 20 used in the system 10 are available from T exas Instruments Incorporated of Dallas, T exas under the TTRIS·™ (Texas Instruments Registration and Identification Systems) product line. Some of the TIRIS™ product line is described in a brochure entitled “Texas Instruments Registration and Identification Systems”, Document Number 22-27-008 (1994), which is incorporated herein by reference. Information about thèse components is publicly available from Texas Instruments Incorporated and should enable those of ordinary skill in the art to make and use the System 10, following the description set forth in this spécification to achieve desired fùnctionalities.

In one preferred embodiment, the readers are low frequency readers that send out periodic power puises of approximately 134.2 kHz to the antennas 22A, 22B, 24A, 24B and receive signais at about 900 MHZ. Other suitable parameters are also contemplated. Such a reader is the Sériés 2000 Reader System available from Texas Instruments, Inc. of Dallas, Texas. Altematively, the reader may be a high frequency reader. The long range antennas are preferably gâte antennas such as the GO3, <302, or G01 model antennas available from Texas Instruments, Inc. The long-rangé antennas may also be custom antennas that blend with the appearance of the dispenser 14. The short range antennas are preferably ferrite rod antennas available from Texas Instruments or altematively .

may be constructed from a printed circuit board that includes a coil having an appropriate inductance.

The readers 20 send out periodic, low frequency, power puises of approximately 13 4.2 kHz to the antennas 22 A 22B, 24A, 24B. The antennas 22 A 22B, 24A, 24B in tum direct the electromagnetic fields generated by the power puises to particular areas adjacent the dispensers. A power puise lasts approximately 50 miliiseconds (ms) and may be generated every 90 ms to 140 ms. When a transponder 23,25 enters the electromagnetic field, the energy is collected by an antenna (not shown) in the transponder and stored in a small capacitor (also not shown). After the power puise is completed, the transponder 23, 25 transmits the customer identification data using the energy stored in the capacitor, The antennas 2-2A 22B, 24A 24B mounted to the dispensers 14 read the data broadcast from the transponder 23 or 25 and send the data to the readers 20 for decoding and further transmission to the host computer 16 or a network where the data can be verified and the customer billed after completion of the fueling or other purchase.

Fig. 2 graphically illustrâtes the operation of a transponder 23 or 25 in coopération with a reader 20. Responsive to a reader 20 emitting a power puise (typically occurring for 50 ms), the * ΰδ 01

-115 transponder 23 or 25 (if within range) will be charged as indicated by the increase in the voltage potential of its capacitor (not shown). Once charged, the transponder 23 or 25 then emits a response signal (lasting about 20 ms) thereby sending its customer identification data to the reader 20. In total about 128 bits are transmitted which are picked up by the antenna (e.s., one of antennas 22A, 22B, 24A, 24B) of the reader 20 and then are decoded. Once the data nas been sent, the 10 transponder 23 or 25 continues to discharge its storage capacitor thereby resetting the transponder to make it ready for the next read cycle. The period between the transmission puises is known as the “sync time” and iasts for about 20 ms, depending upon the chosen criteria. The next power puise may be transmitted approximately 20 ms to 50 ms after the transponder 23 or 25 has completed transmitting the data. As explained further below, the sync time between puises is used 15 to coordinate the transmission of the power puises through the various antennas 22A, 22B, 24A 24B of the system 10.

According to one embodiment of the invention, it is désirable to transmit the power puise at a low frequency and charge the capacitor in transponders 23 and 25. The transponders are designed to émit the response signais at a higher frequency, such as Low Ultra High Frequency.

Referring again to Fig. 1, it is understood that the illustration is not necessarily drawn to scale. In a typical service station, the width of the dispensers 14 is approximately 48 inches. Furthermore, the distance between the dispensers 14 on a single island 12 is approximately 3.6 to 6 meters, and the distance between facing dispensers 14 of adjacent islands 12 is approximately 8 meters. Each fuel dispenser 14 has two separate dispensing areas, one on each side of the dispenser 25 14, where the fuel nozzles and registers are located. As indicated above, each dispensing area typically also has a customer activated terminal (“CAT”) that a customer uses to make sélections such as type of payment and where messages_may be displayed to the customer. Other possible arrangements of the system 10 include environments with more than two service islands, not necessarily parallel to one another, or arrangements in which the islands form a circle with inner and 30 outer rows crr islands.

Referring to Fig. 3A, the vehicle-mounted transponder 23 may be mounted to the rear window 28 of the vehicle 26 preferably near the side of the vehicle where the fuel door 30 is located. In Fig. 3 A, the vehicle-mounted transponder 23 is positioned approximately two (2) inches from the top 32 and side 34 edges of the rear window glass. The vehicle-mounted transponder 23 may be 35 applied to the window 28 with adhesive-backed VELCRO® pads. One pad is adhered to the transponder 23 and another is adhered to the inside surface of the vehicle window 28. Although the vehicle-mounted transponder 23 has been described herein as being positioned on the rear window ü10801 • 125 28 of the vehicle 26, other locations such as a side window may be suitable depending upon the particular arrangement of the long-rangé antennas 22A, 22B. Furthermore, other means for mounting the transponder 23 to the vehicle may be used.

Fig. 3B illustrâtes two variations of a hand-held transponder 25 which a customer can wave in front of one of the short-range antennas 24A, 24B mounted on the opposing sides of the dispenser 10 14. The hand-held transponder 25 may be a key ring or chain style unit 25A or a crédit card style unit 25B, or hâve a different suitable hand-held form. Variations in the shape and size of the transponder 25 are contemplated.

Figs. 4A and 4B illustrate a mounting arrangement for the four antennas 22A, 22B, 24A, 24B on a dispenser 14. The two long-rangé, or vehide-mounted, antennas 22A, 22B, are preferably 15 mounted to a top 36 of the dispenser 14. One long-range antenna 22A or 22B extends outwardly from each side 38A or 38B of the dispenser 14 so that the plane of the antenna is substantially perpendicular to the side 38A or 38B ofthe dispenser 14. The antennas 22A, 22B transmit equally well from either side of the antenna, perpendicular to the plane ofthe antenna. The antennas 22A, 22B, therefore, are aligned so that the electromagnetic field generated from one side of the antenna 20 is directed toward the dispensing area for a vehicle on the appropriate fùeling side of the dispenser 14, and the electromagnetic field from the other side of the antenna is directed up and away from the other side of the dispenser 14 as shown.

The top 36 ofthe dispenser location provides the optimum performance for reading vehiclemounted transponders 23. This location and orientation ofthe long range antennas 22A, 22B also 25 éliminâtes any problems associated with reading a vehicle-mounted transponder 23 of a vehicle located on the opposite side of the dispenser 14. Furthermore, with this location and orientation» the radio frequency waves are iess likely to reach the fueling areas of adjacent service islands 12.

The short-range, or key ring/credit card style transponder antennas 24A, 24B are preferably mounted within the dispenser 14 head behind corresponding authorization lights 45 A, 45B. The 30 authorization lights 45A, 45B advise the customer that he or she is authorized to pump fuel. One short-range antenna 24A or 24B is positioned on either side 34A or 34B, respectively, of the dispenser 14 as shown in Fig. 4B. The antennas 24A, 24B are also positioned near opposing ends 46 of the dispenser 14 as shûwn'in Fig. 4A. This positioning of the antennas 24A, 24B helps prevent the reading of transponders from the wrong side of the dispenser 14. In ancther 35 embodiment, the authorization lights 45A, 45B can be locatcd apart from the dispenser 12 or in different locations on the dispenser.

01U801

- 135 Fig. 4A also shows the customer-activated-terminal (“CAT’) on the dispenser 12. The CAT includes a dispiay 50 where messages may be presented to the customer and a key pad 55 which the . customer may use to make various sélections discussed fürther below.

Figs. 5A and 5B illustrate a second possible arrangement of the antennas on the dispenser.

In this embodiment, the long-range antennas 22A', 22B' are mounted to the top of the dispenser 14' 10 and extend outwardly from the sides 3 8A', 38B’ of the dispenser 14' at an upward angle as snown in Fig. 5B. The elecxromagnetic fields are directed from one side of the antenna toward xhe appropriate füeling area and are directed up and away from the other side. The short-range antennas 24A’, 24B' of this embodiment are arranged in a similar manner as the short-range antennas of the first embodiment.

The transponders 23 and 25 may be read only (R/O), low frequency RFID tags containing a 64-bit customer identification code and are available from Texas Instruments, Inc. For example, the vehicle-mounted transponders may be low frequency transponders available from Texas Instruments’ Vehicle and Container Sériés, and the short-range transponders may be low frequency transponders available from Texas Instruments’ Badge & Card Sériés.

Altematively, the transponders 23, 25 may be read/write (R/W), low frequency RFID tags with a range of different memory capacities. Such R/W transponders are available from Texas Instruments Incorporated. One type of R/W transponder commercially available from Texas Instruments Incorporated is an “authenticated” transponder. Such transponder receives a 40-bit challenge code from reader 20. Every transponder has a unique algorithm contained therein. The transponder receives the 40-bit code, processes it with the unique algorithm, and retums to the reader 20 a 24-bit answer. Thus the reader 20 receives the transponder number and the 24-bit answer. The reader 20 then sends to the hosLpomputer 16 the transponder number, the challenge code and the answer received from the transponder. The host computer 16 then refers to a Iook-up table for that transponder number, identifies the algorithm for that transponder, and runs the 40-bit code through that algorithm, and gets a 24-bit answer out of its algorithm, then compares that with the answer that.came from the transponder. If the answers match, it is an authentic transponder.

The customer identification codes (CIDs) on the R/W transponders may be changed or other data added for business and/or security purposes. For example, the number of times in a day that a vehicle-mounted transponder is used for a füeling transaction at a particular service station or 35 locality can be tracked and written to the transponder 23, 25. This information can’be used for varions reasons including iimiting the number of times that a vehicle-mounted transponder can be used in a day. Furthermore, personal preference information related to the buying expérience may

010801

-14be written to the transponder. Likewise, the transponder can be connectable by a suitable interface to microprocessors such as a vehicle’s on-board computer so that, in coopération with the-system 10, information can be written to the transponder and then displayed to the customer while fueling (e.g., fuel economy calculations, miles traveled since last fill up, engine conditions and the like).

The actual reading range or distance for the antenna/transponder combinations dépends upon such criteria as transponder size and type, antenna size and type, transponder and antenna orientation, and eiectromagnetic noise. A combination of a long-rangé antenna 22A or 22B mounted to the top ofthe dispenser 14 and a vehicle-mounted customer transponder 23 preferably provides a read range of up to approximatcly seven (7) feet measured from the side face of the dispenser 14. The combination of a short-range antenna 24A, 24B located in the dispenser 14 head and a key-ring or crédit card style customer transponder 25 preferably provides a read range of four (4) to six (6) inches.

Table 1 below shows preferred read ranges for the vehicle-mounted transponder/antenna combination and the key chain/credit card transponder/antenna combination in one embodiment.

TABLE, 1

<td rowspan="2"> Transponder Type</td><td colspan="2"> Read Range*</td>

<td> On Side</td><td> OffSide</td>

<td> Vehicle Mounted</td><td> Depth^k: Minimum: 60 inches Idéal: 84 inches Width: 42 to 60 inches Height': 39 to 60 inches</td><td> 18 inches</td>

<td> Key Chain/Credit Card</td><td> Bezel surface to 4 to 6 inches⁴</td><td> No reads allowed</td>

‘Measured from bezel surface ^bMeasured perpendicular to the side of the dispenser 'Measured from the base of the dispenser .

‘‘Measured perpendicular to the side of the dispenser

Fig. 6A is a schematic block diagram illustrating hardware details of a dispenser 14 for the System 10. The two long-rangé antennas 22A, 22B (each labeled as “TOP OF DISPENSER ANTENNA”) are mounted to the top 36 (Fig. 4A) of thé dispenser 14 in a “safe area” 57. An antenna conduit assembly 60 extends through a “dispenser uprights” section 58 and a “dispenser

010801

- 155 hydraulic” section 59 to a “dispenser head safe area” 61 for connecting the long-range antennas 22A, 22B to a muitipiexer 62 (“MUX”). The multiplexer 62 is housed in the dispenser head safe area 61 along with the reader 20. The dispenser head safe area 61 is separated from the hydraulic section 59 by a vapor barrier 64.

Also housed in the dispenser head safe area 61 and coupled to the multiplexer 62 are the short-range antennas 24A, 24B (each labeled “KEY RING ANTENNA”). The multiplexer 62 controis the transmission of the energy puises from the antennas 22 A, 22B, 24A, 24B. A svnchronization (“SYNC”) line 66 provides the coordination commands to the muitipiexer 62 for transmitting power puises. A radio frequency (“RF') line 68 provides the iow frequency, FM power puises that are transmitted by the antennas 22A, 22B, 24A, 24B.

The multiplexer 62 and reader 20 are both coupled to the authorization lights 45A, 45B for controlling the activation of the lights. The reader 20 is coupled to the host computer 16 (Fig. 1) via a communications (“COMM”) line 72 and to the other readers 20 via a synchronization (“SYNC”) line 74. A power supply 76 housed in the dispenser 14 head provides power to the reader 20, the multiplexer 62 and the authorization lights 45A, 45B. The power supply 76 is also coupled to an outside power source via a power line 78. A main conduit assembly 80 ( labeled “ASSY”) supports and protects the communication line 72, the sync line 74, and the power line 78 which are fed to a main junction box 82 coupled to the power storage source and the host computer 16.

Fig. 6B is a schematic illustrating the signal flow between the host computer 16, the dispenser 14 and the antennas 22A, 22B, 24A, 24B connected to the antennas through the MUX 62. Each reader 20 includes a microprocessor (not shown) and programming instructions (i.e., software, not shown) for causing the power puises to be generated by the antennas 22A, 24A, 22B, 24B through the channels ofthe MUX 62 that connect each antenna to the reader. To be pîoperly synchronized, for reasons described below, ail of the readers 20 in the System 10 must cycle through the MUX 62 channels to activate the antennas 22A, 24A, 22B, 24B attached thereto in a predefined, coordinated sequence. For example, in the illustrated embodiment each reader 20 includes a MUX 62 with four channels wherein each channel 1-4 is connected to a different antenna 1-4 (e.g., antennas 22A, 24A, 22B, 24B). Synchronized operation, as explained below, therefore requires that ail of the readers 20 generate a charge puise on channel 1 at the same time, on channel 2 at the same time, on channel 3 at the same time and on channel 4 at the same time. If one reader generated a charge puise on channel 1 while another reader 20 generated a charge puise on· channel 3, or if the readers 20 each operated to generate puises on any of the channels independently of the other

010801

-165 readers, then the readers would be out of synchronization. To keep al! of the readers 20 in synchronization, the sync line 74 (Fig. 6A and 7) connected to each of the readers 20 instructs the MUX 62 in each reader (through the sync line 66) when to generate a charge puise and on what channel to generate it.

Fig. 6B further illustrâtes the communication between payment terminal and pump controller 10 circuitry 15 and the host computer 16. The payment terminal may be a customer activaled terminal (CAT) and the pump controller circuitry responds to instructions from the host computer 16 and the payment terminal for dispensing fuel from the dispenser 14. The payment terminal and pump controller circuitry are conventional and therefore not described in further detail.

Fig. 7 further illustrâtes the site wiring for the system 10 showing the communication line 15 72 and sync line 74 connections among the multiple readers 20. The timing signais for coordinating the transmission of power puises from readers 20 (labeled with numbers 1,2,3 and N) are carried by the sync line 74, The coordination of the transmission of the power puises from the various readers 20 is discussed further below. Any number of the readers 20 is contemplated. While not shown, it is understood that each reader 20 includes a radio frequency module and a control module.

The radio frequency module generates the power puises and receives the data broadcast from the transponders 23, 25. The control module has a microprocessor that décodés and processes the transponder data and communicates with the host computer 16.

Preferably, the readers 20 are interconnected on an RS-485 loop to provide synchronization of the transmit/receive cycle. This link ensures that ail dispenser 14 locations are activating like 25 antenna positions to minimize interférence from each other, as described below. While not shown, RS232-485 converters interconnect the host computer 16 with the readers 20.

Π. SYNCHRONIZAT1OH.QEIHE READERS

Figs. 8-10 illustrate details conceming synchronization of the readers 20 within the System to avoid crosstalk among the transponders 23 that could resuit in erroneously billing a customer 30 for services never received.

In Fig. 8, a simplified schematic ofthe System 10 is shown in which the dispensers 14 are labeled as pumps 1-4 and hâve corresponding readers 20-1 to 20-4, each with antennas A and B on opposite sides of the pump. To illustrate the crosstalk problem, the readers in pumps 1 and 3 are unsynchronized thus demonstrating the potential for crosstalk caused by a transponder X being 35 charged by one of the readers when the transponder X is located between the pumps. In contrast, the readers in pumps 2 and 4 are synchronized thus solving the crosstalk problem for a transporter Y located between the pumps.

OluSGl

- 175 Pumps 1 and 3 send out power puises from antennas B and A, respectively, thereby causing the potential for one or both of them to charge the transponder X, even though the transponder X is closer to pump 1. Each of the antennas B and A emitting power puises generates an energy field extending from the antenna, as represented by lines in the figure. The energy field in front of each antenna inciudes a “near field” région, a “far field” région, and a “transition zone” therebetween (not 10 shown). There are no sharp dividing lines between the three régions and somewhat arbitrary limits are set for each région based upon the way in which energy spreads as the distance from the antenna increases. In one example, the near field région generally extends out from the antenna to a distance of XD^2/A λ = A'2 λ where D = the diameter of the antenna, A = area of antenna aperture, and λ = wavelength. The distance of the far field région is about five times the length of the near field région 15 and occurs at a distance of roughly 2D/22. The transition zone is the région therebetween. As shown in Fig. 8, the possibility exists for overlap of the transition zones or far field régions of the antennas B and A for pumps 1 and 3 when the antennas émit power puises simultaneousiy.

In looking at the power puises emitted from pumps 1 and 3, it is most likely that the Transponder X will be charged by antenna B in pump 1, because the transponder is relativeiy far 20 from pump 3; however, it may end up being charged by the overlap of power puises from both pumps 1 and 3 even in a situation where the transponder is too far from either pump to be charged by antenna B or antenna A alone. This can occur when the energy in the overlapping transition zone or far field régions of the antennas, by virtue of their combined strength, is sufficiently high. Once the power puises are completed, if the transponder X receives sufficient energy it will transmit its 25 data in response. Even though pump 1 is closest to the Transponder X, it is possible that pump 3 will also receive the response, thereby resulting in crosstalk. An even worst situation could arise if two transponders were in the center lane between pump 1 and pump 2 and the pumps 1 and 3 receive the responses from the wrong transponders resulting in a customer being charged for services provided for another customer.

Pumps 2 and 4 send out power puises from their antennas A and A, respectively.

*

Transponder Y is too far away to be charged by the energy field generated by pump 4 alone; and it will not he charged by pump 2, since the power puise from pump 2 is not in a direction facing the transponder. Transponder Y will only be charged when it receives a power puise from antenna B on pump 2 (which will then be the only antenna receiving a response). Such a synchronized system 35 provides better séparation and higher confidence that the proper response is coming from the correct transponder 23.

010801

- 18 Thus synchronization of the System 10 îs accomplishcd when the readers 20 selcctively send out power puises so that ail the antennas facing the same general direction (e.g. ail antennas'facing north, or facing south, or facing east, or facing west) send out a puise at the same time, and ail antennas facing different-directions do not send out puises at that time. This synchronization is accomplished by the readers 20 transmitting puises from antennas facing one direction (e.g., antennas A) during the sync time (see Fig. 2) of the transmit/receive cycle of antennas facing a different direction (e.g., antennas B).

Other synchronization arrangements are possible depending upon the number of pumps and their relationship to one another. In one embodiment, the synchronization does not necessarily need to occur for ail antennas but instead will occur only in the case of antennas for dispensing areas that face each other where the energy fields in front of the antennas might possibly overlap.

Referring also to Fig. 1, a synchronization strategy that prevents energy fields from the different antennas from overlapping results when each reader 20 puises antennas 22A at the saine time, followed by antennas 24A at the same time, followed by antennas 22B and the same time, followed by antennas 24B at the same time. The foregoing successive sets of antennas are pulsed during the sync time (or thereafter) following the data transmit cycle of transponders charged by the previous antenna set. In the strategy just described, antennas for car mounted transponders 23 and hand-held transponders 25 altemate in their pulsing, and pulsing only occurs on one side of each island 12 at a time so that a vehicle located between the îslands is not subject to receiving puises from opposite directions caused by overlapping energy fields. In this case, each “A” antenna (antenna 22A or 24A) (facing west as viewed in the drawing) sends out a puise during the sync time of the transmit/receive cycle of the previously pulsed B”antenna (antenna 22B or 24B) (facing east as viewed in the drawing), and vice-versa. This represents an antenna puise sequence of: 22A, 24A, 22B, 24B. Alternative sequences include: 22A, 22B, 24A, 24B. Any other combination thereof is appropriate so long as “A” antennas and “B” antennas do not charge in the same cycle.

Referring to Figs. 9A-9C and also to Figs. 6A, 6B and 7 discussed previously, operation of the readers 20 will now be described in further detail with respect to an implémentation of one or more of the synchronization strategies mentioned above.

As indicated previously in Fig. 6B, each reader 20 includes a microprocessor (not shown) and programming instructions (i.e., software, not shown) for causing the power puises to be generated by the antennas 22A, 24A, 22B, 24B through the MUX 62 channels that connect each antenna to the reader. For example, the Texas Instruments TIRIS™ Sériés 2000 reader is available with standard software known as the S2000 software. The S2000 software includes programming

010801

- 19instructions for controlling the émission of power puises, for receiving and processing data from the transponders 23, 25, and for communicating with the host computer. This software may be easilv adapted for the presence of the four antennas 22A, 22B, 24A, 24B.

To be properly synchronized, ail of the readers 20 in the System (Fig. 7) must cycle through the MUX 62 channels in synchronization. Synchronized operation requires that ail of the readers 20 generate a charge puise on channel 1 at the same time, on channe! 2 at the same time, on channel 3 at the same time and on channel 4 at the same time. It is understocd that the spécifie synchronization strategy may be determined baséd upon which antenna 22A, 22B, 24A. 24B is connected to which channel 1-4. The sync line 74 connected to each ofthe readers 20 instructs the MUX 62 in each reader (through the sync line 66) when to generate a charge puise and on what channel to generate it for purposes of synchronization.

Figs. 7 and 9A illustrate how each reader 20 is instructed on the sync line 74 to generate properly synchronized charge/read cycles. One of the readers 20 is designated as the “master reader and the remainder are designated as “slaves.” The master reader 20 generates a synchronization puise (represented by sync timing line 900) on the sync line 74 which inversely follows its charge/read cycle (represented by the master timing line 902, wherein a “high” signa! is for charge and a “low” signal is for read). The slave readers 20 use the sync puise to set up their charge/read timing (represented by slave timing line 903). Assuming the charge puise is fixed at 50 ms and the transponder read is about 20-25 ms, there should be no reason for variance. However, as illustrated the slave timing line 904 may resuit in a variance from the sync puise because of message processing occurring in the slave reader 20. This has the unfortunate effect of changing the slave reader 20 processor’s timing by lengthening the time it remains low. Hence synchronization can be adversely affected depgnding upon the loading of the individual reader 20, causing a reader to “drop out” of a charge/read cycle if it is unable to finish its processing in time to catch the sync signal.

i*Fig. 9B illustrâtes the effect of a slave reader 20 temporarily dropping out of synchronization with the master reader 20 (master line 902) due to a message processing delay in the slave reader. Once the message processing in the slave reader 20 is complété, the slave synchronizes once again with the sync signal (sync line 900), however the slave reader remains out of antenna synchronization because the master reader 20 is charging an antenna on a different channel (e.e., the master reader is charging antenna channel 0 while the slave is charging antenna channel 4). Thus the MUX 62 channels being charged on ail the readers 20 are no longer the same channels at the same time.

010801

-20Fig. 9C illustrâtes a solution that corrects the synchronization of a slave reader 20 when it drops out of sync during message processing. The solution is to use the synchronization line 74 to communicate downstream to the slave readers 20 which channel (i.e., which antenna) to use on the next charge cycle. Altematively, the comm line 72 can be used by the host computer 16 to instruct the readers 20 which channel to use. A disadvantage of the latter approach, however, is that in some implémentations the host computer 16 processing time is required for more important tasks.

As shown in Fig. 9C, use of the sync line 74 to communicate the channel number to each of the slave readers 20 is done by encoding the channel number on the sync line. Jn this manner, the processors in ail the readers know which antenna to charge eyen if they miss a charge cycle. As shown by the sync timing line 900, a variable length puise 908 indicates to the slave readers 20 which channel to use for the read cycle. The sync line signal includes a 200 microsecond start bit 906 and after that a puise 908 of vaiying width is transmitted. The length of the puise 908 indicates which channel of the MUX 62 is to be used. A puise of about 1-100 microseconds indicates channel 1,101-200 microseconds indicates channel 2, and so on.

Interrupts in the readers 20 are enabled until the start bit 906 is detected. At that point the serial interrupts are disabled and remain disabled until the measurement of the variable length muxsync puise 908 is compieted, whereupon interrupts are again enabled. The interrupts are disabled for a maximum of about 600 microseconds. The reader 20 will not lose any incoming serial data because a character cannot be completcly rcceived in 600 microseconds. Any character that is completely received when interrupts are disabled are moved to an internai register and the next character is partially received in the shift register.

It will be appreciated that reliance on the hardware to buffer characters allows the reader to avoid an overrun of a universal asynchronous receiver transmitter (UART), which as explained in more detail below is implemented in the reader software according to the présent invention.

The aforementioned synchronization of the readers follows the basic concept that ail the slave readers wait until the sync line is pulled low. The slave reader, however, must be able to distinguish between a low that précédés the MUX puise 908 and a low that indicates that a charge cycle 910 (power puise) is occurring. This is adcomplished by timing the low and knowing that if it exceeds 200 ps the reader is in the middle of a charge puise. In the case where the sync line 900 is high, there is no confusion since the slave reader will continue to wait for a high to low transition.

In the case where the sync line is low, as at the start bit 906, it can be determined whether the low is preceding a MUX puise 908 or is a charge cycle 910 by measuring the amount of time the sync line remains low. If the sync line remains low for more than 200 μ3 (± 10%), then it is not

010801 actually preceding a MUX puise, but actually a charge cycle 910, in which case the interrupts are re-enabled and the hunt for the start bit résumés.

It will be also appreciated that processing routines are written such that message processing does not occur in a manner to inordinately slow down the master reader 20. Slowing down the master reader 20 is to be avoided since this will slow down the entire system of readers 20.

Pseudo-code written for storage and processing in the master and slave readers 20 that implements the svnchronization of MUX 62 channels using the sync line 62 may be expressed as follows:

Sync Pseudo-Code (Slave Reader)

Start:

start timer while sync line is high wait if timer goes off, go to Start // test to see if this is the 200 low. If not, we were not synced!

start timer while sync line is low wait if timer had gone off then go to Start

H okay, we are synced. Time the puise to détermine the mux channel disable interrupts start timer while sync line-is high wait enable interrupts if timer is zéro go to Start if timer is greater than 310 ras select antenna-3 else if timer is greater than 210 ms select antenna-2 else if timer is greater than 110 ms select antenna 1 else if timer is greater than 10 ms select antenna 0

Sync Pseudo-code (Master Reader)

Start:

// make sure the sync line is high for some period that slave will notice....

010801

-22force sync line high set timer for 15 ms while timer has not expired wait

Il go low for 200 ms so that the slave will know that

H this is the start of the mux-sync timing force sync Jine low disable intemipts loop for approx. 200 ms U croate the variable width puise force sync line high if antenna_number ~ 0 loop for 75 ms else if antenna_nutnbcr == I loop for 175 ps else if antenna_numbcr “» 2 loop for 275 ps else if antenna_number -= 3 loop for 375 ms enable interrupts force sync line low (ail readers should now start their powcr/charge cycle)

End Sync Pseudo-code

U this code should be called after we hâve read the transponder

U and re-enablcd the serial intemipts

End MuxSync:

force sync line high

Référencé is made to Appendix A for a slave reader 20 line protocol that may be used in one embodiment of the system 10 for implementing the above described synchronisation fonctions. IU. HOST .COMPUTER COMMUNICATIONS

Referring to Fig. 7, communications on the comm line 72 between the readers 20 and the host computer 16 in the présent embodiment are limited because the readers are urjable to communicate reliably to the host computer during the read cycle, i.e., when the reader is receiving information from the transponders 23, 25. This problem is due, in part, to the lack of hardware resources available in the commercially available readers 20 (i.e., the TIRIS™ Sériés 2000 reader available from Texas Instruments Incorporated under the TIRIS™ product line).

010801

-235 For example, the TIRIS™ Sériés 2000 reader 20 lacks a universal asynchronous receivertransmitter (UART) to transmit/receive transponder data. With the current TIRIS™ Sériés 2000 reader software, there can be either 100% communications with the host computer (with occasional garbled transponder reads) or 100% transponder reads (with dropouts in host computer communications), but not both 100% communications with the host computer and 100% 10 transponder reads. Accordingly, the présent embodiment implements a UART in the reader software (not shown) which is stored and executed within the reader 20. The software causes communications between the host computer 16 and trie readers 20 only when a reader 20 is implementing a charge cycle. See Fig. 2 which illustrâtes the charge cycle (“POWER PULSE’’) lasting approximately 50 ms and the read cycle (“DATAXMIT”) lasting approximately 20 ms.

During the charge cycle, the processor (not shown) in the reader is available for communications on the comm line 72 while it is waiting for a 50 ms tinter (not shown) to transpire. Subsequentlv, once the reader 20 has finished charging the transponder 23, 25, it will attempt to read information from the transponder. To do this, serial interrupts must be disabled for at least 20-25 ms. The tinter is implemented in hardware and, therefore, is not affected by the serial interrupts. However, this 20 would not be a good time for host computer 16 communications to occur because either the transponder read or the communications with the host computer will be garbled by the interrupt for host computer communications.

According to the présent invention, the software within the reader 20 implements the UART fonction by using the sync line 74 to ensure that the host computer 16 does not communicate with 25 the reader 20 when the reader is reading transponder data (and the interrupts are disabled). In particular, the UART fonction is implemented by only allowing the host computer 16 to communicate with the reader 20 on the comm line 72 when the sync line 74 is low, and adjusts the logic of the sync line such that a low sync line is a reliable indicator of when charging is occurring. When the sync line 74 transitions from high to low (see Fig. 9 A where the sync timing line 900 30 moves from a high position 1 to a low position 2), the charge cycle for the reader commences. The sync line stays low during charging and the software according to the présent invention then instructs the sync line to transition from low to high at the end of the charge cycle (see Fig. 9A where the sync timing line 900 moves from a low position 3 to a high position 4). Thus the sync line is low only when the charge cycle is occurring. By foiiowing the rule that the host computer 16 can 35 only communicate on the comm line 72 with the readers 20 when the sync line 74 is low, it is ensured that there will never be a case when information is sent during the read cycle when interrupts are disabled.

-24ln the host computer 16, the clear-to*send (CTS) Hne (not shown) onRS-232 ports régulâtes flow ofdata to and from the readers 20 according to when the line is high or low. The sync line 74 is thus connected to the CTS line through an RS-485 to RS-232 converter for prevcnting the host computer 16 from sending data when the reader 20 is unable to process it.

Appendix B describes a communications protocol between the software within the readers 20 and the host computer 16 for an embodiment in which the host computer is a Wayne Plus System, e.g., a Wayne Plus/2 or Wayne Pius/3 host computer available from Wayne Division, Dresser Industries, Inc. of Austin, Texas, and the reader software is a modified version of TIRIS™ S20D0 reader software available from Texas Instruments lncorporated.

Figs. 10A and 10B are timing diagrams 1002,1004 illustratïng the timing of communications between the host computer 16 and the readers 20 for typica! communications to and from a reader running the reader software according to the présent invention. The Fig. 10A diagram 1002 représente the timing for a reader with no transponders 23 or 25 within range of any of its antennas 22A, 22B, 24A, 24B. The Fig. 10B diagram 1004 represents the timing for a reader 20 with transponders 23 or 25 at ail four ofïts antennas 22A, 22B, 24A, 24B. Figs, 10A and 10B thus show the lightest possible load and the heaviest possible load, respectively, on a reader 20 of the System

10.

In both diagrams 1002,1004, a RCV signal 1006 shows timing of the data received by the reader 20 from host computer 16. A XMT signal 1008 shows timing of the data sent by the reader to the host computer 16. A SYNC signal 1010 shows timing of the sync line 74 data that keeps ail ofthe readers 20 and host computer 16 synchronized. It is also tied to the host computer to indicate when it is safe to send data to any of the readers. A REF signal 1012 shows the timing of a signal generated by the software of the reader 20 for debug and diagnostic purposes. Reference points A through I ïllustrate events în the timing of the signais for purposes of explanation of the diagrams set forth bdow. Ail timing diagrams, Fig. 10A and Fig. 10B, were generated by a Tektronics Prism Logic Analyzer.

In Fig. 10A, the diagram 1002 (iilustrating the case of a reader 20 with no transponders 23, 25 in range) is generated by using the “Get Variable Length Antenna Scan Buffer” command (described below in Appendix C). _

AD - Mux/Sync-Charge Transponder.

Reference is made to the SYNC signal 1010 between points A and D. Prior to setting the sync line 74 Jow, the master reader (Fig. 7) outputs the mux-sync puise 908 (Fig. 9C) that tells the slave readers 20 (i.e., their processors) which antenna to use when charging. When this puise

010801

-255 complétés, the line 74 goes low and ail readers 20 output a charge puise on the correct antenna until the master reader 20 raises the line 74 high.

The processor of each slave reader 20 searches the sync line 74 for the mux-sync puise that informs ail the slave reader 20 processors which multiplexer channel (i.e., antenna) to use for the next charge-read cycle.

The processor of each slave reader 20 searches for a change in the sync line 74 (from hiah to low). It then measures that puise (the start puise) which should be in the range of about 200 _/s (that is why it does not appear in the diagram 1002). Immediately after that, interrupts are disabled so that the reader 20 can détermine the length of the following low (75 us - 375 ^s). This détermines which antenna should be used (a 0-99 us puise indicates antenna 1, a 100-199 us puise indicates antenna 2, etc. as explained with reference to Fig. 9C).

Once the correct antenna is determined, it is switched and a TIRIS™ reader software function is cailed that begins charging the transponder 23 or 25. Basically this consists or setting an extemal flag to let the analog section of the reader 20 begin transmission. This function loops until a timer complétés.

BC - Host Transmission.

Reference is made to the RCV signal 1006 between points B and C. This illustrâtes the dual nature of the sync line 74. Since the processor of the reader 20 is in essence doing nothing during the time of AD the sync line 74 indicates to the host computer 16 that it is may send data to the reader 20, as indicated by the receive signal at BC. At this point the Reader is executing code in the 25 TIRIS™ reader software function “write_sequence( )” and is unable to process any messages received from the host computer until point E.

D - Start Transponder Read.

Reference is made to the SYNC signal 1010 at point D. Both the master and slave readers 20 exit from the function “write_sequence( )” after 50-52 milliseconds. At point D the master 30 reader 20 raises the sync line 74 to prevent the host computer 20 from sending any more data.

There may be a. case where a character has been loaded into the host computer 16 UART shift register and it is too laie to stop transmission. To avoid losing this character, the master reader 20 raises the Sync line 74 prematurely for 5 milliseconds. This gives the reader 20 ample time to capture the characters sent by the host computer 20. After the fîve milliseconds are up, serial 35 interrupts are disabled and another TIRIS™ reader software function is cailed to read the transponder 23, 25 (which results in an implémentation of the software UART function, as previously described).

010801

-26DE - Traospondsr Read·

Référencé is made to the REF signai 1012 between points D and E. A transponder 23,25 read by the reader 20 occurs in approximately 20-23 ms (note that DE includes the 5 millisecond delay mentioned above). During this time ail interrupts are disabled and there can be no communication firom or to the host computer 20.

E - Begin Message Processing.

Référencé is made to the REF signal 1012 at point E. This is where the reader 20 actually gets a chance to process the message it receivcd at BC from the host computer 16. In this example it took 77.608650 ms from when the host computer 16 started sending the message to when the reader 20 finally manages to begin processing the message.

EF - Message Processine.

Référencé is made to the REF signal 1012 between points E and F. During message processing the reader 20 détermines what it is that the host computer 20 requested, acts on this request, and builds the buffers required for a response. This processing varies depending on the type of message as well as the size of the message.

E-..St art of Response

Référencé is made to the XMT signal 1008 at point F where the reader 20 begins transmission of data to the host computer 16.

FQ-Complété Processing.

Référencé is made to the REF signal 1012 between points F and G. This is the time that it takes to do ail the necessary work to store a packet in the serial output buffer.

FH - Reader Transmit s Response.

Référencé is made to the XMT signal 1008 between points F and H. The data, having been loaded in an output queue, is sent by serial interrupts from the reader 20 to the host computer 16. Readers 20, unlike the host computer 16, are not bound by the “transmit only when sync line is high” rule and can transmit at any time. This is désirable because the worst-case message (as described in diagram 1004 below) is approximately 47.9 ms and the charge time is approximately 51.5 ms. This leaves approximately 3.6 ms, which is far too short a time for the host computer 16 to rend another request (ideally one response and one request per cycle). The more bytes the reader 20 transmits during a low sync signal the fewer it must send when the sync line 74 goes high. This permits the host computer 16 to communicate more efficiently with the reader 20.

010801

-275 Point G is where the reader 20 has completed answering a message and is ready to search for the next Mux-Sync puise. Point H is the end of the reader 20 response. Point I is the beginning of the next Mux-Sync puise.

In Fig. 10B, the diagram 1004 (illustrating the case of a reader 20 with transponders 23, 25 in range and detected on ail antennas) is generated by using the “Get Variable Length Antenna Scan 10 Buffer” command (described below in Appendix Cï

The description of the diagram 1004 is substantially the same as described above for the diagram 1002, with the différences of the timing of events being noted by reference to Fig. 10B. At reference point E, the reader 20 gets to process the message it received at BC from the host computer 16. In this example, the time from point B to point E is 79.109765 ms. At reference point 15 H, the start of the next Mux-Sync puise is indicated. The timing shown requires the reader 20 to detect the start bit of the Mux-Sync data while sending data to the host computer 16. This requires that the serial output routine be faster than the Mux-Sync start bit and that the Mux-Sync puise be short enough not to influence the overall timing.

Point I is the end of the reader 20 response. Since the reader 20 began transmission 20 approximately 21.3 ms prior to the sync line 74 going high (SYNC signal 1010), the host computer has ample time (20-25 ms) to send another request. Since an average request is approximately 8-12 ms (depending on the number of DLE characters inserted), there is plenty of time.

Further details conceming communications between the host computer 16 and the readers 20 is contained in documentation available from Texas Instruments Incorporated for its TIRIS™ 25 product line, for examplé “TIRIS: Sériés 2000 Reader System Reference Manual,” Texas Instruments, (#RI-ACC-D01A), which is incorporated herein by reference.

Appendix C is a description of certain fonctions and enhancements made to the software of the readers 20 spécifie to implémentation of the system 10 consistent with the présent spécification. IV. SYSTEM OPERATION AND USER INTERFACE

1.0 System Overview

The following is an overview of the operation and customer user interface of the CFD system. A more detailed description of the operation and customer user interface is described further belowwith referenceto Figs. 11 A-l II, 12-16 and 17A-17N and 17Q. It is understood that the operation of the system 10 is controlled by programrning instructions executed by the host 35 computer 16, and by the reader 20 software described previously. The system 10 is integrated with a suitable fuel dispensing system that, in one embodiment, may be the Wayne Plus/2 or Wayne Plus/3 system available from the Wayne Division, Dresser Industries, Inc. of Austin, Texas, although

010801

- 28 · other dispensing Systems and software are contemplated. The System 10 may be integrated into the Nucléus control System also available from the Wayne Division, Dresser Industries, Inc., for example. The foregoing commercially available intelligent dispenser Systems, or other commercially available dispenser arrangements, in coopération with the CID System 10 of the présent invention, integrate pump control, cash register, card processing and customer identification into a complété and operative System for a service station environment.

When a customer enters a service station and a transponder 23, 25 is detected at a fuel dispenser 14, the corresponding authorization light 45A or 45B, or other in-range indicator as dïscussed further below, is turned on to inform the customer that the transponder is in read range. After the dispenser is activated, for example by lifting the dispenser nozzle or lever or by commencing fueling, the System 10 sends an authorization request containing the transponder CED data to the computer network. Prior to actual fueling, however, the customer can press a cançel key on the customer-activated-tenninal (CAT) or select a different payment method in order to ovenide the use of the transponder CID code for payment of the transaction.

If a transponder is read for the first time at a dispenser where the dispenser nozzle has already been removed, the dispenser will not be authorized to use the CID code from the transponder for a sale. For exemple, if a first customer removes the nozzle at a pump and a second customer’s transponder is subsequently read by the reader at that pump, the sale will not be charged to the second customer’s transponder CID account.

1.1 Overview of Scénario for Window-Mounted Transponders

When a customer with a vehicle-mounted transponder 23 passes a fuel dispenser 14, the CID data is read from the transponder 23 by the long-rangé antenna 22A or 22B that is facing the vehicle. After the CID data is read, the authorization light 45A or 45B on the side closest the vehicle and corresponding to the long-rangé antenna tums on. If the customer proceeds to drive past the fuel dispenser without fueling, the light will remain on until the vehicle-mounted transponder 23 moves out of the read range for that pump. The light 45 A or 45B preferably tums off after a programmable amount of blank reads hâve been made after the transponder 23 teaves the pump’s read range. Accordingly, as the vehicle passes dispensera 14 without fueling, the corresponding authorization lights on the dispensera will tum on while the vehicle is within the read range and tum off when the car leaves the read range.

If the customer chooses to use a vehicle-mounted transponder 23 to pay for a transaction, the customer can check to see that the authorization light 45 A or 45B has tumed on when the car stops at the dispenser. When the customer lifts the dispenser nozzle (or begins fueling), the

010801

-295 dispenser is “authorized” and a request for CDD account authorization is sent through the host computer 16 to a network for billing purposes. The authorization light 45A or 45B preferably remains on throughout the transaction. After the customer replaces the nozzle, the saie is finalized with the host computer 16, and a receipt may be printed at the CAT. .After the saie is completed, the authorization light 45A or 45B tums off and remains off as long as the transponder is 10 continuously read by the antenna. A blank or “empty” transponder read (or predetermined number of blank reads) occumng after the sale is completed will reset the system to allow subséquent transponder reads to tum on the authorization light. Altemativeiy, the authorization light 45A or 45B remains on after the transaction is over until the customer s vehic’.es leaves the read ranae

Once a saie or transaction is completed at a dispenser using a vehicle-mounted transponder

23, the vehicle-mounted transponder 23 preferably cannot be used at another dispenser for a predetermined intervai of time. It is understood, however, that a vehicle-mounted transponder 23 may be used at the same time at more than one dispenser provided a sale has not been completed at one dispenser before the transponder 23 is used at another dispenser. Furthermore, it is understood that the system can be programmed so that although a vehicle-mounted transponder 23 has recently been used to complété a sale at a dispenser, the vehicle-mounted transponder could still be used for a different service, for example at a car wash or drive-up window of a convenience store.

1.2 Oyerview of Scenado_for Hand-Held Transponders

If a customer has a hand-held transponder 25, such as a key ring or crédit card style transponder, it must be presented to the short range antenna 24A, 24B by waving the transponder 25 in front of the short-range antenna located at the authorization light (see Figs. 4A and 5A). The short-range antenna 24A, 24B reads the CID data from the transponder and the corresponding authorization light is tumed on.

A request for CID account authorization is sent to the network through the host computer 16 when the customer lifts the nozzle (or begins fueling). When the customer replaces the nozzle, 30 the authorization light tums off, the sale is finalized, and a receipt may be printed at the CAT. Preferably, the hand-held transponders 25 can work at more than one customer-activated terminal (CAT) (whether at a dispenser, car wash, or convenience store area). In other words, the hand-held transponders 25 can work at a particular CAT even if it is currently being used as the payment method for a transaction at another CAT.

1.3 Overview of Authorization Light Operation

When a customer identification (CID) is read at a dispenser 14 where a ftieling transaction is not alreadv in progress, the authorization light 45A, 45B tums on.

°1ύ86^!1

-30When CID data from a passing vehicle-mounted transponder 23 is read at the dispenser 14, the authorization light 45A, 45B at that dispenser turns on and remains on until the transponder is out of read range. As the vehicle passes the first dispenser and proceeds to the read range of a second dispenser, the CID data is read at the second dispenser and the authorization light of the second dispenser is tumed on.

For vehide-mounted transponder 23 transactions, the authorization light 45A, 45B turns off when the nozzle is replaced at the end of the sale or, altematively, remains lit until the vehiclemounted transponder is out of read range. If a hand-held transponder 25 is used, the authorization light turns off when the nozzle is replaced at the end of a sale.

If a customer overrides a CID transaction and selects a different method of payment, the authorization light 45A, 45B will turn off.

After fueling is complété and the nozzle is retumed, the system 10 can be programmed to prevent an authorization light from being tumed on at any other dispenser (or altematively, anywhere) in the service station for a predetcrmined interval of lime by the CID transponder 23, 25 that had been used for the recently completed fueling transaction. Thus, the vehicle can leave the station without tuming on any more authorization lights.

1.4. Customer Override

A customer can override the use of the transponder 23, 25 for a transaction by pressing the cancel key at the customer activated terminal (CAT) provided the dispenser 14 has not been activated (e.g., the nozzle has not been lifted) or fueling has not begun. A prompt such as “Cancel use of CID System? (Y/N) is displayed at the CAT of the dispenser 14 once the cancel key is pressed. The customer can vcrify the override of the CID transaction by pressing the “Yes” key at the CAT. If the “No” key is selected at this time, the sale will continue as a CID transaction, Le., a transaction where the customer’s CID code is used for billing, A customer can also override a CID transaction before fùeling by inserting a bill or crédit card or by selecting another payment type such as cash. When the customer overrides a CID transaction, the light 45 A, 45B is tumed off.

Once a transaction or sale using a CID code is in the fueling stage, a different payment method cannot be selected at that dispenser 14, nor can the CID transaction be canceled.

1.5 Authorizatton is Denied or Times Put

If an authorization is denied, i.e., a CID code has been sent to the network and the network retums a signal indicating that the customer is denied authorization to use the system 10, /.e., the CID code, for payment, the transaction is treated like a denied pre-authorization sale. The dispenser 14 is stopped and the customer is informed to see the inside attendant for payment. If a vehicle01Ü8C1

-315 mounted transponder 23 is used, the authorization light tums off and remains off until the nozzie is replaced. Similarly, if an authorization response is not received from the network for a CID sale within a predetermined time {e.g., 60 seconds), the sale will be treated like a denied preauthorization sale.

1.6 Network Communications Problems

If the computer network is down when a customer lifts a nozzie at a dispenser 14 that has an authorization light on, the dispenser will not start. Instead, the CAT displav notifies the customer that the network is down and asks the customer to cance! the CID transaction berore seiecting another pay method. When the customer complétés the füeling, but the sale cannot be paid through the CID system due to network problems, the CID “sale” is considered an unpaid CAT sale and mav be iogged and saved for reporting purposes.

2.0 Customer Identification (CID) Operation and User Interface Flowcharts

Figs. 11A - 111 and Fig. 12 are flowcharts describing the processes that occur when a customer uses the system 10 in a vehicie mounted transponder 23 scénario and in a hand-héld transponder 25 scénario, respectively.

Figs. 13-16 are flow diagrams illustrating the relationships between tasks and subsystems involved in handling customer transactions.

Figs. 17A-17N and 17Q are flow charts describing the processes performed by the CID primitive, i.e., the software routine written to manage performance of the customer identification fonctions.

2.1. Scénario for Vehicle-Mounted Transponder

Figs. 1 IA and 1 IB depicts a flow chart 1100 illustrating operation of the system 10 in a scénario that involves a vehicie mounted transponder 23. In step 1104 a vehicie approaches a pump, i.e., a dispensing area, within the service station environment. In step 1106 a détermination is made whether the transponder 23 is in range of the pump. As previously discussed with reference to Figs.

1 and 8, this détermination involves a reader 20 receiving data from a vehicle-mounted transponder after the transponder is first charged by the antenna 22A or 22B. If the approaching vehicie does not hâve a vehicle-mounted transponder 23, i.e., there is no vehicle-mounted transponder 23 in range, then the system 10 proceeds with traditional customer processing, step 1110, where payment is not made using the CID code. With traditional customer processing, the customer makes payment using a traditional method, such as inserting a credit/debit card into the customer-activated terminal (CAT) or paying the station attendant directly. With traditional customer processing, the CAT may il10801

-32display payment instructions, such as “insert credit/debit card or pay attendant”, followed bÿ fùeling instructions, such as “lift nozzle.

If a vehicle-mounted transponder 23 is in range, then m step 1108, the CID system 10 détermines whcther or not the detected CID has been used recently (for, example, in the last iive to ten (5-10) minutes) to complété a sale at another dispenser at the service station. If yes, then the system 10 defaults to traditional customer processing, as indicated in step II10, and the corresponding authorization light will not be activated (see step 1112, below). The customer will berequired to select another form of payment, and the transaction will be processed without using the CDD code. This helps avoid fraud and prevents the uneasy feeling a customer might otherwise hâve driving away from a pump after completing a sale only to see each successive pump he or she drives by “light up” as if being activated. The customer is given ample time after fueling to ieave the service area without activating authorization lights at any of the other pumps. As an option, the foregaing defànlt to traditional customer processing can be e’.iminated when it is not objectionable to see other pumps “light up” after completing a sale on a different pump.

In step 1108 if the transponder 23 was not recently used to complété a sale, then in step 1112a “customer in range” indication is provided at the pump. In one embodiment, when the transponder 23 is in range of the pump dispensing area, the authorization light 45 A 45B tums on to provide the indication. The light 45A, 45B may be at any suitable location on or near the dispenser 14. While in one embodiment the in-range indicator is the light 45A 45B, it will be appreciated that the indication can altematively be provided by an audible sound (e.g., music, tone or voice), a mechanical movement, a video or multimedia présentation, or any combination thereof or other activity that can be sensed by the customer.

After the in-range indicator light 45A, 45B cornes on, the system next détermines whether the vehicle-mounted transponder 23 may hâve moved out of read range as would happen if the vehicle was merely passing a fuel dispenser. In step 1113, the System checks to see if the vehiclemounted transponder 23 is still in read range. If yes, then in step 1114 (discussed in more detail further below), the system tests to see if the transponder 23 has been in range a sufïicient predetermined length of time. If_t however, the vehicle-mounted transponder 23 is no longer in range, then in step 1115 the system tests to see if a predetermined number (N) of blank reads, i.e., reads where no transponders are detected, has occurred. If yes, this is an indication that the vehicle may hâve driven on, and the in-range indicator is accordingly tumed off in step 1116. The system 10 retums to a dcfàult condition in step 1110. It is understood that if the customer then approaches, and the transponder cornes within range of, another pump, then the light 45 A 45B for that pump

010801 •335 will tum on. It is still further understood that the in-range indication provided in step 1112 does not mean that the customer’s identification (z.e., account number) has yet been associated with the pump for purposes of compieting a sale. This avoids the potential for fraud or accidentai customer charges when a transponder merely enters the range of the pump. If in step 1115 the predetermined number ofblank reads does not occur, this is an indication that the vehicle may still be within range of the 10 pump, and the system retums to step 1113 again to check for transponder reads.

As mentioned above. in step 1114a détermination is made whether the transponder 23 is in range of the pump for a sufficient length or time. If not, the system détermines in step 1115 if a predetermined number ofblank reads has occurred. Should the transponder remain out of range, the in-range indicator will be tumed off in step 1116, and the system will default to traditional 15 customer processing in step 1110. If the vehicle-mounted transponder 23 is in range for a sufficient time (e.g., about 4 seconds, for example) then in step 1118 the pump’s customer activated terminal allows the sale to proceed by displaying to the customer an indication that the pump handle may be removed for immédiate fueling, or altematively that another form of pavment (e.g., “insert card”), or cancellation of the pending sale (e.g., “cancel”) may be made. The purpose of the step 1114 time 20 delay before the sale can proceed is to give the customer sufficient time to get out of the vehicle to operate the pump, thereby avoiding fraudulent or accidentai activation of the pump by someone other than the customer.

In step 1122 a détermination is made whether a time limit has been exceeded. If toc much time has passed since the vehicle came in range without the customer proceeding with the saie, i.e., 25 without the customer lifting the nozzle or commencing fueling, then the in-range indicator goes off (step 1116) and the system defaults to traditional customer processing (step 1110). The step 1122 time limit may be several seconds to a minute or two, for example. The purpose of the step 1122 time limit is to avoid fraudulent or accidentai use of the customer’s identification should the customer leave the vehicle (e.g., to go in to the service facility) or otherwise be inattentive to 30 performing an sale completion. As an option, the time limit step 1122 may be omitted.

If in step 1122 the time limit is not exceeded, then in step 1124 a détermination is made whether the customer has activated the pump. In step 1124 the customer may activate the pump by lifting the pump nozzle from the dispenser 14, or by a combination of lifting the pump nozzle and commencing fueling. In a dispenser 14 that is not equipped with a nozzle-lift detector, the pump 35 may be activated by other techniques, such as, by lifting a pump lever, sliding an element,'or perhaps by pressing a grade select button to start the pump. For purposes of the présent disclosure, any of

01C8C1

-34the foregoing techniques, or any combination thereof, or any other techniques utilized to sîart the pump, are considered a pump “activation.”

If, in step 1124, it is determined that the pump 14 has not been activated, then the System tests in step 1125 for an override of the use of the CID code. An override may occur when the customer cancels the transaction or selects another form of payment, e.g,, a crédit card. If an override does not occur, the process retums to step 1122 whereby the System again détermines whether the time out period has been exceeded. If an override does occur, the System proceeds with traditional customer processing, with the type of processing being dépendent upon the type of override selected. The details of the test for an override when the pump has not yet been activated are discussed further below with reference to Fig. 1 IC. Altematively, the test for an override can be made before the time out step 1122; however, since the signal processing is so quick, the time out in step 1122 will not likely to hâve been exceeded when the System first performs step 1122. Consequently, any subséquent tests for a time out being exceeded in step 1122 will be preceded by the test for an override (step 1125).

If in step 1124, it is determined that the pump 14 has been activated, then, in step 1126, a détermination is made whether the transponder 23, previously determined to be within range of the pump, is still within range. In order to mitigate the effect of any spurious signais that may be picked up by the antennas and to verify that the same CID code is being detected both before and after pump activation, the CID System 10 preferably compares a sampling of readings made before pump activation with a sampling of readings made after pump activation. The CID system vérifiés that the readings before and after pump activation are the same or nearly the same. For example, the CID system may take five readings before activation and fivç readings after activation. If ail, two or three of the five readings made prior to activation match ail, two or three of the five readings made after activation, then the CID code is verified. More readings could be made if desired. For example, ten readings made prior to activation could be compared with ten readings made after activation. An acceptable comparison may be if five of the readings made before the lift match five of the readings made after the lift.

The purpose of the foregoing détermination made in step 1126 is to make sure that the customer’s vehicle is the one being fueled. This avoids the potential for a pump to be activated fraudulently or by accident by someone standing near the pump when the vehicle drives by, during the brief instant when the transponder 23 is in range of the pump. It will be appreciated that in some embodiments step 1126 ïs optional when step 1114 has aiready been used to détermine whether the transponder is in range for a sufficient length oftime. It is contemplated that both steps.1126 and

0108C1

-355 1114 may be performed, or that if one is performed the other might not be needed. Both steps in a sense are optional, depending upon the level of customer security desired for the system 10.

If in step 1126 the same transponder 23 is not still in range, then in step 1116 the in-range indicator goes off and in step 1110 the pump defaults to traditional customer processing. If still in range, then in step 1128 the transponder 23 data (e.g., the customer account information) is 10 associated with the pump so that a sale (e.g., fueling or other purchase) will be permitted.

Pump/transponder 23 association in step 1128 only occurs once the pump is activated in step 1124.

In step 1130 authorization of the transponder data (e.g., customer account information) is performed. For example, the host computer 16 in combination with a network is used to détermine whether the customer account number is valid for purchases. Altematively, the host computer 16 15 may instead review data stored in a local négative file of bad accounts and authorize the customer account so long as it does not match a bad account number. The authorization process of step 1130 can be performed prior to, or as part of, the step 1128 of associating the transponder 23 with the pump. In some embodiments the association process is ail that is needed, and no additiônal authorization process is required. The authorization might consist only of recognizing that the 20 customer identification is a valid identification or of the correct number of characters. However, in most applications of the system 10, some form of database crédit authorization will be desired.

In other embodiments, the authorization step 1130 can be performed as soon as the transponder 23 is within range of any pump or other reader (perhaps even at the entrance to the service station environment). However, a sale will not be permitted (step 1132) unless and until the 25 pump is activated in step 1124. The authorization step 1128 may also include a “time-out” détermination (not to be confused with the time out discussed with reference to step 1122). A “time-out” occurs when the CID code has been sent to the host computer 16 or network for authorization, but no confirmation or déniai has been received after a predetermined amount of time. Fig. 11E, described in more detail further beiow, illustrâtes how a déniai of authorization or a “time30 out” may be handled when occurring before or after fueling or before or after the nozzle has been lifted.

In step 1132 a sale is permitted whereupon, for example, the customer can dispense fuel and perhaps order goods (e.g., food) or services (e.g., a car wash) at the pump, ail of which is charged to the customer account identified by the transponder 23 data.

In step 1134, the sale is completed using the customer’s CID data. Fig. 1 IC illustrâtes in more detail the steps taken to complété a CID transaction. With reference to Fig. 1 IC, while the customer is fueling, the customer-activated-terminal indicates that the “Pump is on” (step 1140), and

010801

V ί

- 36 5 the System 10 performs certain customer spécifie activities. For example, the System may offer (by displaying a message on the CAT) the customer a car wash if the customer has purchased fuel a certain number of times. Or, the System may remind the customer it is time for a car wash where the customer desires a car wash at certain times. Other customer spécifie activities may include offering desired food or beverages to be charged against the customer’s account. The customer spécifie 10 information may corne from a database that is up-dated regularly and which is in or accessible by the host computer 16. Or, the information may be included in the data broadcast from the customer’s transponder 23,25. If the transponder is a read/write (R/W) transponder, then the host computer can periodically update the information on the transponder based on the customer’s preferences.

In step 1142 the system détermines whether the customer is authorized to use the CID code for payment or whether a time-out has occurred. Step 1142 may be included if the “authorization” step 1130 (Figs. 1 IB) is omitted before the “permit sale” step 1132 (Fig. 11B). It can be appreciated that the “authorization” step can be included either before or after the permit sale” step 1132 (Fig. 11B) or both. If in step 1144 (Fig. 1 IC) authorization is denied or a time-out occurs, it is handled as illustrated in Fig. 11E.

During fueling, the system again tests for an override in step 1146. Fig. 11F, which is discussed further below, illustrâtes in more detail the test for an override during fueling. If an override has not occurred then in step î 14S, the System détermines whether or not the nozzle has been replaced in its seat. If the nozzle has not been repiaced in its seat, the system continues to 25 détermine whether authorization has been denied or a time-out has occurred (if step 1142 is included) and whether an override has occurred.

Once the nozzle has been replaced indicating that fueling has been completed, the CID system détermines in step 1150 whether the network is down, i.e. whether the host computer 16 can access the network. Fig. 1 IG illustrâtes in more detail the scénario for determining if the network 30 is down. It should be understood that the network can be checked at a number of different times during the customer transaction. For example, the network can be checked before and after fueling has begun. With reference to Fig. UC, ifthe network is down, the transaction is processed as an unpaid CAT sale (step 1152) andjhe sales information may be stored in the host’s computer’s memory for forwarding to the network at a later time when the network is operational. If the 35 network is not down, the authorization light or other in-range indicator is tumed offin step 1154.

The sale is finalized and any final customer spécifie activities such as displaying a prompt for receipt are performed in step 1156.

010801

2.2 Scénario for Hand-Held Transponder

Fig. 12 depicts a flow chart 1200 illustrating operation of the svstem 10 in a scénario that involves a hand-held transponder 25. The transponder 25 may be used even in situations where a customer with a vehicle mounted transponder 23 approaches the pump, whereupon the transponder 25 may be used to override or cancel a possible transaction involving the transponder 23. This might occur, for example, when the customer wishes to charge the sale at the pump to an account different than the account associated with the vehicle mounted transponder 23.

Referring now to Fig. 12, in step 1204 a customer approaches a pump, i.e., a dispensing area, within the service station environment. In step 1206 a détermination is made whether the hand-held transponder 25 is in range of the pump. As previously discussed with reference to Figs. 1 and 8, this détermination involves a reader 20 receiving data from a transponder 25 after the transponder is ôrst charged by the antenna 24A or 24B. To be in range, typicallv the customer must place the transponder 25 up next to the dispenser 14 or in some other designated location up close to the antenna 24 A or 24B. If the approaching customer does not présent a hand-held transponder 25, then the System defaults to traditional customer processing in step 1221. It should be understood that if a vehicle-mounted transponder is detected, then the process as described with reference to Figs. 11A and 1 IB occurs. In step 1206 if the hand-held transponder 25 is in range, then in step 1212 a “customer in range” indication is provided at the pump. In one embodiment, when the transponder 25 is in range of the pump dispensing area, the authorization light 45A, 45B tums on to provide the indication. The light 45A, 45B may be at any suitable location on or near the dispenser 14. In one embodiment, it is in the location ofthe antenna 24A or 24B, where the customer présents the transponder 25. Separate in-range indicators may be provided for the handheld transponders and the vehicle-mounted transppnders if desired. Once the indication is activated, if the indication is in the form of a light, for example, upon moving the transponder 25 away from the light the light remains illuminated until a time out occurs, as explained below.

Once an in-range indication occurs at a pump responsive to the customer presenting the transponder 25 in. range, ifjhe customer then approaches another pump so that the transponder is in range, the. indication for that other pump will also be provided, and subséquent activation and sale is allowed, as explained below, at both pumps. In one embodiment, when two indications and activations occur concurrently that involve the same hand-held transponder 25, an indication is provided to the service attendant to alert the attendant of the fact, so that if a fraudulent or unintentional use of more than one pump by the customer transponder 25 is occurring, it can be terminated.

θΐν80ί

- 38 While in one embodiment the in-range indicator is the light 45A, 45B, it will be appreciaced that the indication can altematively be provided by an audible Sound (e.g., music, tone or voice), a mechanical movement, a video or multimedia présentation, or any combination thereof or other activity that can be sensed by the customer.

In step 1218 the pump’s customer activated terminal allows the sale to proceed by displaying to the customer an indication that the pump handle may be removed for immédiate fueling, or altematively that another form of payment (e.g., “insert card”) or cancellation of the imminent sale (e.g., “canceT) may be made. In step 1222, a détermination is made whether a time limit has been exceeded. If too much time has passed since the transponder 25 came in range without the customer proceeding with the sale, then the in-range indicator goes off (step 1219) and the system defaults to traditional customer processing (step 1221). The step 1222 time limit may be several seconds to a minute or two, for example. The purpose of the step 1222 time limit is to avoid fraudaient or accidentai use of the customer’s identification should the customer leave the dispenser area (e.g., to go in to the service fàcîiity) or otherwise be inattentive to performing an sale completion. As an option, the time limit step 1222 may be omitted,

If, in step 1222, the time limit is not exceeded, then in step 1224 a détermination is made whether the customer has activated the pump. In step 1224, the customer may activâte the pump by lifting the pump nozzle from the dispenser 14, or by a combination of lifting the pump nozzle and commencing fueling. In a dispenser 14 that is not equipped with a nozzle-lift detector, the activation occurs, for example, by lifting a pump lever, sliding an element, or perhaps by pressing a grade select button to start the pump. For purposcs ofthe présent disclosure, any of the foregoing techniques, or any combination thereof, or other techniques utilized to start the pump, are considered a pump “activation.”

If the pump 14 has not yet been activated, the System tests in step 1225 for an override of the use of the CID code. An override may occur when the customer cancels the transaction or selects another form of payment, e.g., a crédit card. If an override does not occur, the process returns to step 1222 whereby the system again détermines whether the time out period has been exceeded. If an override does occur, the system proceeds with traditional customer processing, step 1221, with the type ofprocessing being dépendent upon the type of override selected. The details of the test for an override when the pump has not yet been activated are discussed further below with reference to Fig. 1 IC.

Once the pump is activated in step 1224, then in step 1228 the transponder 25 data (e.g., the customer account information) is associated with the pump so that a sale (e.g., fueling or other

01Û801

-39purchase) will be permitted. Pump/transponder 25 association in step 1228 only occurs once the pump is activated in step 1126.

In step 1230 authorization ofthe transponder data (e.g., customer account information) and a test for a time-out are performed. Fig. 11E illustrâtes how a déniai of authorization or a “timeout” may be handled. In step 1232 a sale is permitted and in step 1234 the sale is compieted using the customer’s CID data. Fig. 1 IC illustrâtes in more detail the steps taken to complété a CID transaction. T'ne foregoing steps 1230-1234 are performed, respectively, substantiallv the same wav as are steps 1130-1134, described previously. Note that if a customer overrides a CID transaction and selects a different method of payment, the indication light 45A or 45B will tum off.

2.3 Test For Override When Pump Not Activated

Fig. 11D. describes the process that occurs when the CID system tests 10 for an overrice of the system when the pump has not yet been activated. The process applies whether the transponder detected is a vehicle-mounted transponder 23 or a hand-held transponder 25. As discussed above, such an override may happen when the customer chooses a different method. of payment other than the use of the CID code or the customer décidés to cancel the transaction.

Initially, the CID System vérifiés that fueling has not started by determining whether the dispenser nozzle has been removed from its seat and whether actual fueling has started (steps 1160 and 1162). If the nozzle has been removed and fueling has started, then the system tests for an override when the fueling has started, in step 1164. Fig. 11F describes the process for testing for an override when the fueling has started.

If the nozzle has not been removed and/or fueling has not started, then the CID system détermines whether the customer has: (1) canceled the transaction by hitting the “CANCEL” button on the customer-activated-terminal (CAT) (step^l 166),(2) inserted a credit/debit card into the CAT as payment (step 1168), or (3) selected a different method of payment (such as cash) (1170), If yes, the in-range indicator is tumed off (step 1172), the display on the CAT is changed to read “Insert card or remove nozzle” or some simiiar message (step 1174), and the transaction is processed using traditional customer processing methods, i.e., without using the CID code (step 1176).

Note, if the customer hits the “Cancel” button, he or she is given the opportunity to undo the cancel. After the “Cancel” button is selected, the display will read “Y/N” (step 1178). If the customer selects “N” for no, the CAT will display a message such as “Nozzle, Cancel, Card” (step 1180), and the transaction continues to be processed as a CID transaction (step 1182). Similarly. if neitherfc card in inserted (step 1168) or another payment key is selected (step 1170), then the transaction continues to be processed as a CID transaction (step 1184). In steps 1182 and 1184,

010801

-40if the transponder is a vehicle-mounted transponder 23, the process continues with the time out step 1122 ofFig. HC. If the transponder is a hand-held transponder 25, then the process continues with thetime-out step 1222 ofFig. 12.

2.4 Test For Override When Pump Activatcd

Fig. 11F describes the process that occurs when the CID system tests for an override of the system that has been attempted after fueling has started. The CDD system vérifiés that fueling has started (step 1190). If fueling has not started, then the system in step 1191 tests for an override when fueling has not started. Fig. IID, discussed above, describes the process that occurs when testing for an override before fueling begins..

If fueling has started, the CID system détermines whether or not the “Cancel” button was hit on the customer-activated-terminal (CAT) (step 1192). If yes, the pump in the dispenser is stopped (step 1194) and the customer is instructed by the display on the CAT to replace the nozzle and pay the attendant inside the service station building (step 1195). The system then continues to complété the sale (step 1196) by testing the network (step 1150 ofFig. 1 IC). If the “Cancel button was not hit in step 1192, the CID System détermines whether or not a credit/debit card was inserted into the CAT (Step 1193) or if a diffèrent payment key on the CAT was selected (step 1197). If yes, the display on the CAT is changed to read that an override of the system cannot be accomplished for example, saying that a credit/debit card cannot be accepted (step 1198). The process then continues processing the sale to completion in step 1199 by determining whether the nozzle has been replaced (step 1148, Fig. 11 C). If a credit/debit card has not been inserted and a different payment has not been selected, the message of step 1198 is not dispiayed, but the system continues to process the sale to completion in step 1199.

2.5 Authorization Denied orTime-Out Handling

Fig. IIE describes the process that occurs when customer authorization has been denied or there is a System time-out due to the faiiure of the network to provide customer authorization confirmation or déniai for the use of the CID code. If fueling has already started (step 2210), then the CED system 10 stops the fuel pump (step 2212) and informs the customer to replace the nozzle and pay the attendant inside the service station building (step 2214). If the fueling has not started (step 2210), then the CID system· 10 détermines whether the nozzle has been lifled (step 2216).

If the nozzle has not yet been lîfted then, then the CDD process continues (step 2217) with the time out step 1122, Fig. 1 IB, if a vehicle-mounted transponder is involved or with the time out step 1222, Fig. 1 IC, if a hand-held transponder is involved. Another opportunity to authorize the CID use (for cxample if there had been a system time-out) is provided again in step 1130, Fig. 11 A,

010801

-41 and step 1230, Fig. 12. If the nozzle has been lifted, the customer is informed through the CAT display that the CED authorization has been denied and is requested to select another method of payment (step 2218). The transaction then proceeds with traditional customer processine, i.e., without using the CID code for payment (step 2220).

2.6 Authorization Light (In-Range Indicator) Operation

Figs. 11H and 1II illustrate the general operation of the authorization lights 45A, 45B (or other in-rar.ge indicator) of the dispenser 14. Not every trigger for tuming the in-range indicators on or off is included in Figs. 11H and III. It should be understood that other usures and discussions nerein may describe additional or modified scénarios for activating or deactivating the in-range indicators. With reference to Figs. 11H and 111, the CID System 10 continually takes readings to détermine if a CID transponder 23, 25 is présent or in read range in step 2230. If a vehicle-mounted transponder 23 is in range, the CID system 10 in step 2232 détermines whether the detected CID code has been used recently at another pump at the service station. Step 2232 is similar to step 1108 of Fig. 11 A. If yes, the transaction is processed as though no CFD is présent and the sale is processed using traditional customer methods in step 2234. As discussed previously with reference to Figs. 11A and 1 IB, during step 2232, the CID system 10 is checking to see if a transaction using the vehicle-mounted CID code has been completed recently at another pump, i.e., completed in the last five to ten (5-10) minutes. If a transaction has been completed using the vehicle-mounted CID code in the last five to ten (5-10) minutes, then the CED system will not tum on the in-range indicator and the dispenser will not operate unless another form of payment is selected. As mentioned further, this helps avoid fraud by providing the customer ample time after fueling to leave the service area without activating authorization lights at any other dispensers in the service area. Note, if a hand-held transponder is^detected in step 2230, then the system 10 does not check for recent use in step 2232.

If the detected CID code has not been used recently at another pump or the detected CID code originated from a hand-held transpbnder 25, then the CED system tums the in-range indicator on in step 2236. While the in-range indicator 45A 45B is on, the CID system 10 détermines in steps 2237, 2239, and 2241 whether the transponder is still in read range and whether a time out has exceeded. These steps (2237, 2239, and 2241) are similar to steps 1113, 1114, and 1115, respectively, of Fig. 11A.

In step 2238, the system détermines whether the “Cancel” button on the CAT has been hit. If yes, the system then détermines in step 2240 whether fueling has started, and if.fùeling has started.

019801 • 42 5 the System tests for an override in step 2242 (see Fig. 11F). If the “Cancel” button has been hit and fùeling has not been started, then in step 2244, the in-range indicator is tumed off.

If the “Cancer button has not been activated in step 2238, the CID System 10 détermines whether a time out has been cxceeded in step 2243 and, if not, détermines if fùeling has started in step 2245. Steps 2243 and 2245 are similar to steps 1122 and 1124, respectively, of Fig. 1 IB, and 10 the description for steps 1122 and 1124 accordingly apply for steps 2243 and 2245, respectively. Note, if a time out is exceeded in step 2243, then the in-range indicator is tumed off in step 2244. Once fùeling has started, the system 10 then continuaily checks to see if the nozzle has been replaced (step 2246). Once the nozzle has been replaced, the in-range indicator is tumed off in step 2244.

After the in-range indicator is tumed off, the CID system continues to check to see if the 15 detected CID transponder is still in read range in step 2248. The in-range indicator remains off as long as the transponder is continuously read by the antenna on the dispenser. The in-range indicator 45A, 45B, therefore, is prevented from coming on again as soon as the sale is completed but before the customer has driven away from the dispenser. Once the CID transponder is out of read range, i.e., the antenna gets an “empty” transponder read, the system is essentially reset and the 20 authorization light will corne on in response to a subséquent transponder read. However, as discussed above, the dispenser authorization lights will not corne on before a period of five to ten (5-10) minutes after the completion of the sale.

2.7 Network Dpwn5gcnario

Fig. 1 IG describes the process that occurs if there is a computer network failure. After 25 either a vehicle-mounted 23 or hand-hdd CID transponder is read (step 2250) and the authorization light is tumed on (step 2252), the CDD system 10 détermines whether the computer network is down (step 2254) and, therefore, whether the customer's CID code can be verified and/or any final sales information can be forwarded from the host computer to the network for procesàng and. If the network is down, the customer is informed of the network failure and is asked to see the cashier 30 (step 2256), and the authorization light 45A, 45B (in-range indicator) is tumed off (step 2258).

If the network is not down, the CID system then détermines if fùeling has started (step 2260). If fùeling has not started and the network is up and running, then the system continues to process the transaction as a CID transaction. Once fùeling has started, however, the CID system continuaily checks to see if the network is down (step 2262). If at anytime during fùeling the 35 network fails or goes down, the sale will be processed as an unpaid CAT sale (step 2264) and the sales information is stored for future forwardir.g to the network. If no network failure occurs during fùeling, then the transaction continues to be processed as a CID transaction.

010801

-435 3.0 Software Tasks and Subsystems

The following is a description of the spécifie tasks carried out by software and subsystems of the CID System in one embodiment. Other arrangements are contemplated.

3.1 Overview of Software Tasks/Subsvstems

Fig. 13 is a diagram 1300 illustrating the relationship between the major software tasks and 10 subsystems invoived in handling a CID transaction. The software tasks and subsystems needed to process the customer identification (CID) feature generally fall into the following areas:

A. Reading the transponder 23, 24 numbers C’CIDs). This is performed by a low-levei Transponder Reader Task 1302.

B. Handling the CIDs, getting auths (authorizations), tuming on authorization lights (or 15 other in-range indicator), etc. This is performed by the CID Primitive software routine 1304.

C. Handling the CID information in a sale by, for example, making changes to the Base and Application customer platform service (“CPS”) code; note that the Base and Application CPS code refers to the service station software that controls the fuel pumps and handles non-CID transactions.

D. Handling CID authorization requests, authorization retums and time outs. This is 20 performed by the CID application’s Network Communications 1306, which is in communication with the outside network 1308.

E. Processing outdoor sales activities 1310, i.e., customer activities that occur at the dispenser 14, such as a new CID read, the insertion of a credit/debit card into the customeractivated-terminal (CAT), the customer pressing the cancel key of a different Pay Type key, nozzle lift or retum, and the end of the sale.

F. Handling command input at programming screens 1312. Through programmas screens (discussed in more detail in Appendix D) the service attendant (or other authorized personnel) is given the ability, for example, to tum CID fonctions on or off for individual dispensers 14 or for the entire service station; tum individual readers on or off; map antennae to particular CATs, and perform CID System diagnostics. &gt;

3.2. The Transponder Reader Task

Fig. 14 is a diagram 1400 which more particularly illustrâtes the flow of data and commands between the Transponder Reader Task 1302 and the CID Primitive software routine 1304. The Transponder Reader Task 1302 selectively sends commands signais to the transponder readers 20 35 in order to tum the readers 20 on or off (i.e., activate) and forwards authorization light control commands from the CFD Primitive 1304 to the readers 20 as well. The Transponder Reader Task 1302 furthermore receives the CID numbers read at ail the antennas in the service station. In a

010801

ClD Read at Antenna

<img file="OA10801A_D0001.tif" />

-44typical-sized service station there may be eight (8) readers 20 in the system, with each reader handling up to four (4) antennas. Consequently, there may be up to thirty-two (32) antennas in a typical system.

After receiving the CID numbers, the Transponder Reader Task writes the transponder CID number data to a table illustrated by Table 2 below. The table contains CID numbers or values for al! the antennas. The antennas are grouped in pairs of a high-power (long-range) antenna and a low-power (short-range) antenna. The first antenna pair provides the first two values in the array of CIDs, one for a high-power antenna and one for a low-power antenna. The CID values may be eight (8) bytes so that there would be two (2) pairs of eight (8) byte values per reader 20. Note that the reader and antenna columns in Table 2 below are just for reference.

Reader Antenna

I3

9 etc.

. Table 2: Transponder Reader Task's Data Structure

A typical reader, in one embodiment, is able to handle two (2) pairs of antennas (e.g., antennas 22A, 22B, 24A, 24B). This means that each reader 20 provides thirty-two (32) bytes of CID data, or as mentioned above two (2) pairs of eight (8) byte values. When no transponder number is read at an antenna, the value zéro (0) is placcd in the table as the transponder number for that antenna. When ail the transponder values hâve been read for ail antennas, a signal is sent to the CED Primitive 1304 to process the new transponder numbers. This signal is in the form of a *

command packet sent to the CED Primitive's Command Mailbox 1402. Either the CID numbers or a pointer to the CID numbers may be sent in the command packet.

Authorization light control is decided at a higher software level than the Transponder Reader Task 1302 and is passed to the Transponder Reader Task 1302 as commands to tum on or tum off individuai lights.

010801

- 45 ·

3.3. The CID Primitive

With reference to Figs. 15 and 16, the CID Primitive 1304 receives commands in its command mailbox 1402. These commands include:

1) Process the ready CID numbers (data) from the Transponder Reader task 1302. -

2) Tum on or tum off the transponder light (authorization light).

3) Override CID use at a pump (originated from the Base CPS 1502 or Application code 1504).

4) Latch CED use at a pump (from the Base CPS 1502 at nozzle lift).

5) Handle CID Auths (authorization replies) retumed from the network 1308 through the Applications Network Interface (or Communications) 1306.

6) End CID use in a sale (from the Base CPS 1502 or Application code 1504 at the end of a sale).

7) Retum CID use status for a pump (from the Base CPS or Application code)

8) Retum CID révision information (from Base CPS report génération code)

The CID Primitive 1304 will receive a command to process a new batch of CID numbers read at the pumps or dispensers 14 from the Transponder Reader Task 1302. During processing, the CED Primitive 1304 maps the antennae data to spécifie pumps 14 for use in determining CED use at the pumps. Each antenna pair provides two (2) CID values (one per antenna).As discussed in more detail below, the CID Primitive 1304 utilizes the non-zero CED if one is read at either antenna of a pair. This non-zero CID value is used for the pump that is mapped to the antenna pair (if any). The CID Primitive 1304 is abie to détermine whether the CID value came from a vehicle-mounted transponder 23 or a key ring/chain transponder 25 by which antenna read the transponder. For example, if the transponder was read by a low-lçvel antenna 24A, 24B, the transponder is considered to be a key ring/chain transponder 25. If the CED was read by a high-level antenna 22A, 22B, it is considered to be a vehicle-mounted transponder 23.

If both antennas of a CID pair are non-zero, i.e. where the high-level antenna 22A, 22B of a pump 14 reads a vehicle-mounted transponder 23, and the low-level antenna 24A, 24B of the same pump 14 reads a key ring/chain type transponder 25, the low-level read takes precedence and is used by the CID Primitive 1304, In this way, the key ring/chain type transponder 25 is abie to override a vehicle-mounted transponder 23 at pump 14, and the transaction is charged against the key ring/chain transponder 25 account. This override measure is discussed further below with reference toFig.,17M.

010801 • 46 The CED Primitive 1304 maintains two lists of data structure. One list, as shown by Table 3 below, provides the status ofthe pump 14 and includes the following information for each pump: (a) the type of transponder that was detected by the pump — either the vehicle-mounted (window) 23 or key chain/credit card 25 type; (b) an index to the CID list (the second data list (Table 4) maintained by the CID Primitive 1304); (c) whether there has been an override of CID use at the pump and the authorization light has been forced off; (d) whether there has been a retum on status change; and (e) the previous status.

<td> Pump No.</td><td> Transp. Type (Window or Key)</td><td> Index into CID list</td><td> Override CID/ Force OffLight</td><td> Ret, on Status Change Mask</td><td> Previous Status</td>

<td> 1</td><td></td><td></td><td></td><td></td><td></td>

<td> 2</td><td></td><td></td><td></td><td></td><td></td>

<td> 3</td><td></td><td></td><td></td><td></td><td></td>

<td> ...</td><td></td><td></td><td></td><td></td><td></td>

<td>ⁿ</td><td></td><td></td><td></td><td></td><td></td>

Table 3 — Pump List Data Structure

The second list maintained by the CID Primitive is another structure for CID numbers that are being processed by the System as shown in Table 4 below. This list includes the following information for each CID number: (a) the type of transponder the CID number came from — either the vehicle-mounted (window) 23 or key chain/credit card 25 type; (b) which pump 14 read the CDD number, (c) which pump 14 is using the CID number; (d) the status of the CID authorization; (e) biliing information; (f) deiete time; and (f) a forwarding mailbox. Different fonctions change or query the two data structures (Table 3 and Table 4) in different ways.

<td> CID#</td><td> Type: Win/Key</td><td> Readby Pump#</td><td> Inüseaî Pump#</td><td> Aiith Status</td><td> Biliing Info</td><td> Deiete Time</td><td> Forwarding Mailbox</td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

-47010801

Table 4 CED List Data Structure

Figs. 17A-17N and 17Q are flowcharts describing the CID Primitive and the various commands it handles. Fig. 17A describes the overall command processes of the CID Primitive. Tne CID Primitive continually checks for commands in its CID Command Mailbox (CID Cmd Mbx) 1402 (step 1702). If there is no command, the CID Primitive proceeds with a CID list Cleanup (step 1704; see flowchart 17001 of Fis. 171) where the CID List Data Structure (Table 4) is cieared of CID numbers no longer read by a pump or in use at a pump after the ClD's delete time has passed. After completing the CID list cleanup, the CID Primitive again checks its CED Command Mailbox 1402 for commands (step 1702 of Fig. 17A).

In flowchart 1700A, if there is a command in the mailbox 1402, the CID Primitive détermines if the mailbox contains CID data from the Transponder Reader Task 1302, (step 1705). If yes, the CID Primitive processes the CID data using a “Handle CID Data” subroutine in step 1706 Box 276. The flowchart 1700D, “Handle CID Data”, ofFigs. 17D and 17E describes in more detail how the CED data is processed.

With reference to Figs. 17D and 17E, handling of the CID data involves, among other things, updating the Pump List Data Structure (Table 3 above) and CED List Data Structure (Table 4 above) based on the CID data received from the Transponder Reader Task 1302. In step 1800 of Fig. 17A, the CID Primitive maps the antenna data to the pumps 14. Flowchart 1700M of Fig. 17M describes in more detail the process by which the CID Primitive handles the mapping of antenna data to the pumps. With reference to Fig. 17M, the System checks ail antenna data and matches antenna pairs to appropriate pump numbers or free-standing reader in steps 1802 and 1804). Then for each pair of antenna readings (one high-power and one low-power reading per pair), the System détermines if either CID number is non-zero (meaning at least one transponder has been read) (step 1806). If neither antenna reading is non-zero, i.e. neither antenna detected a transponder, then System sets the new CED for the pump to none (0) (Step 1808).

If at least one CID is non-zero then in step 1810, the CID Primitive détermines whether both CIDs at a pump are non-zero. If both CIDs at a pump are non-zero, i.e., a the high-power antenna detects a vehicle-mounted transponder 23 and the low-power antenna detects a hand-held transponder 25, then the low-power antenna data takes precedence so that the new CED for the pump is set to the non-zero CID number corresponding to the hand-held or key chain type transponder (step 1812). If it is not desired to allow an override by the hand-held transponder 25,

010801

-485 then altematively the system can maintain an errer condition and set the new CID for the pump to none (0)(Box 406).

If both CIDs at a pump are not non-zero in step 1810, then in step 1814 the new CID for the pump is set to the non-zero CID number, and the CID type is set to either window-mounted or key chain depending upon which antenna it was read the new non-zero CID.

Returning to flowchart 1700D of Figs. 17D, 17E, after the antenna data has been mapped to the pumps (step 1800), individually begins processing the antennas (steps 1750, 1752). If in step 1754 the CID value for an antenna is blank (zéro) and the pump has no associated CED number, the CID Primitive clears the flag that forces the authorization Iight off at the pump so that future CID reads will be able to turn on the authorization light (step 1756). Whether or not the force authorization light ftag has been cleared, the CID Primitive in step 1758 next compares the current CID read with the previous CID read. If there has been no change, i.e., the current CID read is the same as the previous CID read, then the CED Primitive does nothing (step 1760).

If the current CED is different than the previous CID (step 1762), then the system again détermines in step 1764 whether the current CID is blank. If no, then in steps 1820, and 1711, the 20 system perforais subroutines to handle new non-blank CID read at the pump and to handle retum on status change, respectively. The subroutine for handling new non-blank CID reads is described in more detail in flowchart 1700F of Figs. 17F, 17G, and the subroutine for handling retum on status changes is described in more detail in flowchart 1700C ofFig. 17C. These subroutines are discussed in more detail further below.

If in step 1764, Fig. 17E, the current CID is blank, the system détermines whether the previous CID was from a window-mounted (vehicle-mounted) transponder 23 in step 1766. If no, the system does nothing in step 1768 since this means that the previous CID was from a key chain type transponder 25. Ifthe previous CDD was a vehicle-mounted transponder 23, the CID Primitive perforais steps (steps 1770, 1772, 1711, 1774, 1776, and 1778) to update the Pump List Data 30 Structure (Table 3) and the CED List Data Structure (Table 4) in order to “disconnect” the CID from the pump (step 1774) and disassociate the pump with any CID (step 1778). In step 1776 the vehicle-mounted CID is not immediatdy deleted, but rather a time is set for later délétion. That way the vehicle-mounted transponder 23 will not tum on authorization lights as it passes other pumps for a predetermined period of time.

With référencé to Figs. 17F, 17G, the steps taken by the CED Primitive to handle a new nonblank CID read at a pump (step 1820 ofFig. 17E) will now be described. First, the CID Primitive détermines in step 1821 whether the new CID is in the active CED list (Table 4). If no, the new CID

010801

5 is added to the active list in step 1822, and an authorization request is sent to the network for the new CID (step 1823). The authorization light stays on at the pump (step 1824), and the system next détermines whether a different CID had previously be associated with the pump (step 1825). If yes, and the previous (old) CID was from a key chain transponder 25, then the old key chain CED is deleted from the tables (steps 1826 and 1827). If yes, but the previous CED was not from a key 10 chain transponder 25, i.e., it was from a vehicle-mounted transponder 23, then in steps 1828 and 1830. the old CED’s entry for “Read by Pump ï coiumn of Table 4 is cleared (set to zéro (0)1 and a time to delete the old CED from the tabie is sei, respectiveiy. Next, in steps 1831 and 1832 the pump’s associated CED index (Table 3) is set and the présent pump is set as the entry for the “Read by Pump” coiumn (Table 4), respectiveiy. In srep 1834 the processing of the new non-biank CID 15 is completed.

If in step 1821, the new non-blank CED is already on the active CID list, the CID Primitive checks to for whether the new non-blank CED is in use at another pump (steps 1836-1 842). If the new CID is from a key chain transponder 25 and is currently being used by another the pump (steps 1837, 1838 and 1839), then the new CID is added to the active CID list in 1822. In this way, the 20 key chain transponder 25 may be used at more than one pump at a time. If the new CED is from a key chain transponder 25 and is not currently being used by another the pump (steps 1837, 183 8 and 1839), then in step 1840, the existing CED entry on the table is used, i.e., the a new entry is net made.

If the new CED is from a vehicle-mounted transponder 23 which is not in use by another 25 pump (steps 1837, 1840), then in step 1840, the existing CID entry on the table is used, i.e., the a new entry is not made. If, however, the new CID is from a vehicle-mounted transponder 23 that is in use by another pump (steps 1837, 1840,1842), then the force light off flag is set so that the new CID read will not tum the authorization light on. Accordingly, the vehicle-mounted transponder is prevented from being used at more than one pump at a time. The processing then 30 ends in step 1834. ^?

Other commanda handled by the CID Primitive are discussed further below.

3.4. The CID Primitive/Sale Processing Interface

Outdoor sales processing, i.e., where the customer does not go through a cashier or attendant but makes pavment at the dispenser 14 by using either the CAT or the CID code, requires 35 interfàcing at a number of steps in the sale process as described below. The various steps include: . 1. A new CDD is first read at a pump or is first no longer read (goes to.a zéro CED)

2. Bill Insertion, Card Insertion or Pay Type Key Pressed

010801

-505 3. Nozzie Lifi

4. Authorization Approval, Déniai or Timeout

5. End of Sale/Cancel

In each of the above cases, either the Base CPS code 1502 notifies the CID Primitive 1304 or the CO Primitive 1304 notifies the Base CPS code 1502 that the event or step has transpired.

Both the Base CPS code and the CED Primitive handle these events.

3.4.1. A CID Number is First Rcad at a Pump

Referring to Fig. 17A when a CID number is first read at a pump, the CID Primitive 1304 checks to see if there is a retum on CID status change request for the pump (see step 1708 and subroutine step 1710 ofFig. 17A and flowchart 1700B Handle Retum on Status Change Request” 15 in Fig. 17B). If so, the CID Primitive sends notification to the Base CPS processing code to inform it of the new CO read. The Base CPS code notifies the application code, which may perform sonie fonctions such as changing the CAT display to reflect that a CO has been read at the pump.

Similariy, if a vehicle-mounted CID transponder 23 passes out of the read range of a pump, the CO Primitive informs the Base CPS that the CID is no longer being read at the pump (if a retum 20 on status change is requested for that pump). This enables the application code to change the CAT display prompt back to îts original state (no CO read state), or perform whatever actions are needed.

The CID Primitive status retum interface uses mailboxes for the command request and for the status change notification. The Base CPS sends a retum on status change request to the CID 25 Primitive via the CID primitive's Command Mailbox. The CID Primitive processes the request and monitors the CID reads at the CAT. When a new CID is read, it retums the status change to the appropriate statejnbx for the requesting cpt. Fig. 15 is a diagram 1500 illustrating the retum on status change interface.

3.4.2. Bill Insertion. Card Insertion orPav Type Kev Pressed

When a bi11 is inserted in the bill accepter, a card is inserted at the CAT, or a pay type key is pressed at the CAT, the Base CPS code 1502 handles the event in its normal manner. The CPS code also calls the new routine ^!override_cid_At_Pump(),

The formai of the cali is:

override-cid-at-pump( pump-num, &amp;status);

This routine sends an override_cid_at_pump command to the CID command mailbox (see step 1712 and subroutine step 1714 ofFig. 17A, and flowchart 1700H “Handle CID Override” ofFig. 17H). With reference to Fig. 17H, if the pump is not activated yet, then the authorization light is tumed

010801

-51 off at the pump and the CID is prevented from being used in a sale at the pump (steps 1850 and 1852). If the pump has already been activated, however, then the attempted override is ignored and a message is displayed at the CAT to the effect that the override can not be made (steps 1850, 1854). In step 1856, the override subroutine is ended.

3.43. Nozzle Lift

When the nozzle is lifted at a pump 14, if the pump is not already authed (authorized) or an auth (authorization) in progress is set, and if the pump 14 has ne problems preventir.g an authorization, the Base CPS code 1502 calls the new routine latch-cid-at-pumpQ.

The format of the call is:

latch_cid_at_pump( pump-num, &amp;status);

This routine sends a latch_cîd_at_pump command to the CID command mailbox (see step 1716 and subroutine 1718 of Fig. 17A and flowehart 1700K “Handle Latch CID At Pump” of Fig. 17K). With reference to Fig. 17K, when processed, the command checks to see if the pump has a CID read, and if it can be used in the new sale. In particular, in step 1902, the system détermines if the pump as an associated CID index. If ηοζ then the sale will not be a CID sale (step 1904) and the force light off flag is set for true, i.e., the pump light is tumed off (if not already off) (step 1906).

If the pump does hâve an associated CID index in step 1902, then the system checks to see whether the force light off flag is already set for the pump, i.e. set to off (step 1908). If yes, then in step 1910 the CID cannot be used in the sale. If the light not set to off, then the CID may be used in the sale, and the CID is associated with the pump sale (step 1912). A status is retumed indicating whether or not the sale is a CID sale. In step 1914, Table 4 is updated to indicate the CID is in use at pump. In steps 1916, 1918, and 1920, the appropriate mailbox for the authorization responses is specified, and the CID Primitive forwards the Auth reply or timeout to the appropriate task's mailbox, which is how the system works with pre-auths.

As discussed fùrther above, in order mitigate the effect of any spurious signais that may be picked up by the antennas and to verifylhat the same CED code is being detected both before and after the nozzle lift, the CID system preferably compares a sampling of readings made before the nozzle lift with a sampling of readings made after the nozzle is lifted. The CID system vérifiés that the readings before and after the nozzle lift are the same or nearly the same. For example, the CID system may take five readings before the nozzle lift and five readings after the nozzle lift. If ail, two or three of the five readings made prior to the lift match ail, two or three of the five readings made after the lift, then the CID code is verified. More readings could be made if desired. For example, ten readings made prior to the lift could be compared with ten readings made after the lift. An

010801

-52 acceptable comparison may be iffive ofthe readings made before the lift match five of the readings made after the lift.

3.4.4. End of Sale/Cancel

When a sale is canceled or finalized, the Base CPS code 1502 calls the new routine end-cid-at-pump(). The format of the call is:

end_cid_sale_at_pump( pump_num, &amp;status);

This routine sends an end_cid_sale_at_pump command to the CID Command Mailbox (see step 1720 and subroutine 1722 ofFig. 17Aand flowchart 1700L “Handle end_cid_use_at_pump” of Fig. 17L). This command tells the CID Primitive that the pump sale is over. With reference to Fig. 17L, the CID Primitive détermines in step 1930 if a CID in the CID table is associated with the pump and ifso, begins cleanup operations on the CID in steps 1932, 1934, 1936, 1938, and 1940. The CID is not immediately deleted, as the system needs to keep thé CID and the status of its use in a sale. This is so that when a mounted transponder 23 sale is finished at a pump, the transponder does not tum on authorization lights as it passes other pumps for a predetermined period of time.

3.5 The CID Primitive/Network Communications Interface

The CID Primitive 1302 interfaces with the application-specific network communications code in order to send authorization requests to the appropriate network, and to receive replies from the network.

3.5.1. CED Authorization Request

When a new CID is first seen at an antenna, an authorization request is generated for the CID. A new routine, authorize_cid0, interacts with existing network communications code lo generate an auth (authorization) request to be sent to a network.

The format of the call is:

authorize-cid( cid_number, dd_index, retum-mbx, &amp;status );

where cîd_index is a method of identifying the auth retum with the CID that is requesting the authorization. This procedure is called by the CED Primitive and does not involve sending any commands to the CID Primitive Command Mailbox.

The Auth Requests are filled in with the CID number rather than a crédit card account number and its associated information. This needs to be done for each application, as the individu al network interfaces are different.

3.5.2. Auth Apprayal. Déniai or Timesut

When the CID auth is approved, denied or timed out, the CID Primitive receives an auth reply from the network communications code (see step 1724 and subroutine step 1726 ofFig. 17A

010801

535 and flowchart 1700J “Auth Reply” of Fig. I7J). Fig. 16 is a spacial diagram showing the authorization request and reply handling. The procedure decode_cid_auth_ reply() is called by the project-specific network communications code. This procedure handles “decoding” the response from the network into a format that can be used by the application's auth reply handler. It then retums the decoded auth reply to the CID primitive.

The format of the call is:

decode_cid_auth_reply (parameters to be determined);

This procedure is called by the application network communications code. The procedure generales a command (process_cid_auth_reply) to the CID Primitive Command Mailbox to process and possibly forward the decoded Auth Reply.

When a decoded auth reply is received by the CID Primitive, it first détermines whether the

CID is in the CID list (is in use) in step 1940. If no, the CID authorization or time oui is thrown away in step 1943. If yes, the CID Primitive stores a pointer to the auth reply in the CID structure, and changes the Auth Status for that CID (step 1942). If the CID is in use at a pump and the Forwarding Mailbox is set (step 1944), the CID Primitive sends the CID Auth Reply to the forwarding mailbox (step 1946). Note that in step 1946, if the Auth is approved, the Base CP S/Application will copy the billing information for the sale finalization. If the Auth is denied or times out, the Base CP S/Application will terminate the sale and stop the pump. If in step 1944 the CID’s forwarding mailbox has not been set, then in step 1948 the authorization information is saved for future forwarding incase the CID is used later at a pump.

The auth reply, after being forwarded to the correct mailbox, is handled by the applicationspecific code, which processes the auth reply. If the auth is approved, the application may continue the sale. If the auth is denied or timed out, the^pplication may stop the sale at the pump.

Note Figs. 17N and 17Q shows a flowchart 1700N of a “Begin CID Auth Task” 1950. The steps 1750N, 1752N, 1754N, 1756N, 1758N, 1760N, 1762N, 1764Q, 1766Q, 1768Q, 1770Q, 30 1772Q, 1774Q, 1776Q, 1778Q, and 1820Q are similar to steps 1750, 1752, 1754, 1756, 1758, *

1760, 1762, 1764, 1766, 1768, 1770, 1772, 1774, 1776, 1778, and 1820 of flowchart 1700D of Figs. 17D and 17E. Flowchart 1700N has the added step 1952 of determining whether the pump is in use. If so, then in step 1954, any CID read at an in-use pump is ignored.

4.0 .Options'

The following are various descriptions of additions or changes that may be made to the CID

System·. One or more of the variations may be made to the System at a time.

4.1 Car..Wash

010801 • 54 ·

For service stations that hâve an automated car wash, a stand-alone reader with a long.-range antenna for detecting vehicle-mounted transponders and a short-range antenna for detecting key ring/card type transponders may be positioned at the entrance to the car wash. Customers can use cither their vehicle-mounted transponder or hand-held transponder to pay for the car wash or be authorized for a free car wash if the service station gives free car washes for fueling.

The network can keep information regarding the customefs preferences for a car wash (such as a wash only, wax, dry, etc.) so that the customer does not need to input the information at the carwash, but may proceed with the car wash once authorization is given. The preferences may lie displayed at a customer-activated-terminal (CAT) provided on the stand-alone reader and overridden by pressing appropriate keys at the CAT ifdesired.

Where a service station provides free car washes and the customer has met the criteria for recaving the free car wash, the CAT displays a message to the customer that the customer is entitled to the free car wash. The customer is also give the option to add other car wash services (such as wax or dry) that may not be induded with the free car wash. These additional services can then be charged against the customer's transponder account.

4.2 Hand-Held Antenna

As an option service stations could be provided with hand-held or wand-type antennas at the dispenser islands. The hand-held antenna may be waved in front of a vehicle-mounted transponder by, for example, a gas station attendant who is dispensing fuel at a full service island.

4.3 NozzlSuAnifiima

As an option, reader antennas may be placed on the fuel dispenser nozzle, and the customer transponder may be placed in the inlet or neck of the vehicle gas tank. When the fuel nozzle dispenser nozzle is inserted into the gas tank inlet, the nozzle antenna detects the gas tank transponder.

4.4 PIN Numtei

As an option, the CID system may be programmed to display a request at the CAT for a Personal identification number (PIN). The PIN would be a number different from the CID number f. _{&lt; t} and may be used in lieu of a correct CID number reading or to verify a transponder readtng of a CID number. In response to the PIN request, the customer would use the key pad at the CAT to enter the PIN.

4.5 Indoor Paymcni

A key ring/card reader may placed inside the service station building for purchases of other products such as food, car supplies, or magazines that may be offered by the service station. For

010801

- 55 5 example, many service stations include a convenience store that offers a variety of items for sale. A reader could be positioned near the check-out counter. The customer may wave a key ring/card type transponder past the reader in order to pay for items being purchased.

4.6 Reward and Récognition

The network keeps track of the customer's past purchases and buying preferences and 10 provides rewards for frequent purchases. When a transponder is read, the CAT can display a message indicating rewards that the customer may be entitled to such as a car wash.

The network can also keep a profile of the customer and provide cusiomized service for the customer based on the profile. The profile can include customer information such as: customer name, address, téléphoné number, date of birth, and security code, payment information such as: 15 primary method of payment(card number, valid dates, card type) and secondary method of payment (card number, valid dates, card type); preference information such as: CAT receipt desired, language (English, Spanish), car wash preference; and purchasing information such as: product purchased, date of purchase, amount of purchase, quantity purchased. An example of cusiomized service based on a customer profile includes the automatic printing of a receipt at the CAT. Or, the 20 customer can obtain full service fueling, i.e., dispensing of the fuel by a service attendant. The customer merely drives up to the dispenser, allow the vehicle-mounted transponder (or hand-held transponder) to be read by a dispenser antenna, and the network sends a signal to the attendant to dispense the fuel.

The profile of the customer can be constructed based on questionnaires completed by the 25 customer and input into the network and by prior transactions completed by the customer.

4.7 Car Diagnostic

Many vehicles include computers that keep track of the caris diagnostics. For example, the computer keeps track of the radiator water level, the oil level, and the car mileage. Th'e CED transponders may be linked to the vehicle's computer in order to read the diagnostic information and f30 may broadcast the information to a service station CID antenna. The CAT at the service station dispenser can then display reminders based on the diagnostic information to the customer such as the caris oil needs to be changed.

4.8 Attendant Control Qver.PjsDgns.gr

A service station attendant may override the use of a transponder if ffaud is suspected. For 35 example, an attendant may wish to hait the dispensing of fuel at a pump if the attendant suspects that the user was merely waiting at the pump until a vehicle with a vehicle-mounted transponder went by and activated the authorization light on the pump.

01080J

-565.0 Further System Description

Attached as Appendix D hereto is a further description ofthe CID system 10 as implemented with a commercially available fuel dispensing system, such as the Wayne Plus/2, Wayne Plus/3, or Nucléus fuel dispensing Systems available from Wayne Division, Dresser Industries, Inc. of Austin, Texas. Specifically, the Appendix D illustrâtes certain changes to be made to the fuel dispensing control system for incorporating the remote RF CID features of the system 10, including changes that can be made to the programming screens as part of the host computer 16, the network record, and the reports and logs. Although illustrative embodiments ofthe présent invention hâve been shown and described, a latitude of modification, change and substitution is intended in the foregoing disclosure, and in certain instances, some features of the invention will be employed without a corresponding use of other features. For example, any type of commercially available dispensing system may be modified, adapted or replaced to comprise the system 10. Any number of punrps, islands, antennas, dispensing areas and kiosks may be included as part of the system. Certain features are to be modified to meet the spécifie needs of different competing service station companies. Aspects of the opérations! flow of the system may optionally be used or not used. While the system may be used for retail fuel dispensing; it is also understood that the System also has application for convenience stores, quick service restaurants, car washes and the like. For example, the system may hâve application at a drive-up window or service counter, Accordingly, ' it is appropriate that the appended daims be construed broadly and in a manner consistent with the scope of the invention.

010801

- 57 APPENDIX A

SLAVE READER LINE PROTOCOL

1.1 GENERAL

The data link described here is based on a master/slave relationship in which the master (the CPS) sends data or commands to the slave units (the CPTs). The slave units will make appropriate responses to the master-initiated communication. Under no circumstance will a slave initiale communications. The communication is haif-duplex and the protocol is transparent and bvxeoriented. The protocol allows variable-length.

1.2 DATA FORMAT

- Asynchronous Communication

- 9600 Baud

- 1 Start Bit

- 8 Data Bits • No Parity Bit

- 1 Stop Bit

1.3 DATA LINK HARDWARE

The data link is 2-wire, multi-dropped, RS-485.

1.4 ERROR-CHECKING

Error-checking is via CRC-16 on ail transmissions. Parity is not required at the byte level since CRC-16 is used on ail data bytes transmitted.

1.5 MODE OF TRANSMISSION

The mode of transmission shall be half-duplex, asynchronous, start-stop format.

1.6 BUFFER SIZE

Transmit and receive buffers at the Master and the Slave devices are variable and application-dependent. However, the maximum size is 251 bytes, excluding protocol control and inserted DLE bytes. (Tnserted DLE’ bytes are used to achieve data transparency, as explained in the CODE TRANSPARENCY section.)

1.7 PROTOCOL

The protocol structure consists of a synchronizing byte followed by the slave device byte, an optional data field, a stop byte and two CRC bytes. A protocol byte-map and a description of each byte follows.

SYNC / ADDR / Data Bytes (251 max) / SF / CRC1 / CRC2

SYNC Byte (FE hex)

01U801

-58The SYNC Byte indicates to the recéiving device that the transmission of communication block is starting. It also indicates that the next byte transmitted coniains the slave device address.

ADDR Byte (00 to FF hex)

The ADDR Byte is the address of the slave device.

SF Byte ŒD hcx)

The SF Byte (stop flag) indicates the end of control and data portions of the transmission. SF also indicates that the next two bytes contain the CRC of the transmission.

CRC1 and CRC2 Bytes

CRC1 is the least significant byte of the CRC-16 çhççk work. CRCl and CRC2 are calculated on the followingbytes: SYNC, ADDR, (DATA excluding inserted DLE’s), SF.

The Master transmits a message according to the above protocol. The addressed Slave responds using the same protocol.

After the Master or the Slave receives its last data, it waits a minimum of 5 ms before tuming on its transmitter. This gives the sender a chance to tum off its transmitter and tum on its receiver.

If the Slave detects a transmission error, it does not respond.

1.8 CODE TRANSPARENCY

Code transparency for eigbt-bit data is achieved by Data Link Escape (DLE) insertion. The DLE charactcr byte has a value ofOFCH. Note that this is not the ASCII value for DLE. The DLE charactcr is inserted before specified data patterns in the protocol to clarify the meaning of those data patterns. Inserted DLE characters are not ïncluded in the CRC-16 calculation. The rules for DLE insertion follow.

- DLE is inserted before any byte in the transmission that has a value equal to SYNC except the actual SYNC byte. This includes ADDR, ali data bytes, CRCl and CRC2.

DLE is inserted before any byte in the transmission that has a value equal to SF except the actual SF byte. Any·byte, includes ADDR, ail data bytes, CRCl and CRC2.

DLE is inserted before any byte in the transmission that has a value equal to DLE. This allows the value of DLE to be transmitted to the receiver. Any byte, includes ADDR, ail data bytes, CRCl and CRC2.

010801

-59APPENDIXB

COMMUNICATIONS PROTOCOL BETWEEN HOST COMPUTER AND READERS

The TIRIS™ S2000 reader application software available from Texas Instruments

Incorporated includes a “Gâte fonction” in which serial interrupts are disabled right before a “Transponder Receive” routine. The TIRIS™ S2000 reader software svnchronizes the readers by sending the synchronization line from a high to a lôw. The S2000 reader software is modified according to the présent invention so that at the end of a charge cycle the synchronization line is forced high so that it is always the case that the line is low during the charge cycle.

The original TIRIS™ reader software has what is called an inter-character time-out - if more than three character times went by, the reader 20 would cail it a bad request and move on. Although this was adjustable through software, it is unusuai and too rigid. This rigidity has the sideeffect of forcing the host computer 16 to accommodate the peripheral’s timing rather than the other way around.

Cooperative communications requires the host computer 16 only transmit during a charge puise. If one were to use inter- character time-outs, it is possible that a message could be split between two charge puises (this has been seen in tests). The resuit is that the TIRIS™ reader 20 believes that it has received only part of a message (which it throws away). Since timing during communications is so important, if the TIRIS™ reader 20 sees one character, it waits unti! a whole message has been sent, hanging in a loop until the time-out period has elapsed.

In order to allow reuse of existing Wayne host computer communication libraries, the base level protocol has been redefined to follow the CPT, or slave unit, protocoi (see Appendix A. herein), which is also known as the “CAT protocol”. Since this protocol is fairly generalized in the way that data is formatted, it has been narrowly defined for the reader 20. This protocol differs from 25 the bus protocol used by the TIRIS™ S2000 Reader, which is also known as the TIRIS™ Bus Protocol available from Texas Instruments Incorporated (see TIRIS™ Bus Protocol (TBP), Chapter 7 in “TIRIS: Sériés 2000 Reader System Reference ManuaT’, Texas Instruments, (#RI-ACC-D01 A), which is incorporated herein by reference) in the following ways:

• Start of Header has been changed from 0x01 to OxFE · End of Message has been changed from 0x04 to OxFD • The CRC has been changed from CRC-CCITT to CRC-16 (initialized to OxFFFF).

.. · AU responses from readers contain, as their first byte in the data, the command code that initiated the response.

010801

-60AJ1 commands to the reader hâve the following format:

<td colspan="4"> Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5...</td><td> Byte len+5</td><td> Byte Jen+6</td><td> Byte len-7</td>

<td> Start of</td><td> Destina-</td><td> Com-</td><td></td><td> End of</td><td> LSBof</td><td> MSBaf</td>

<td> Header</td><td> tion</td><td> Source mand Length</td><td> Data</td><td> Message</td><td> CRC</td><td> CRC</td>

<td> Byte</td><td></td><td> Description</td><td></td><td></td><td></td><td></td>

O

LEN+5

LEN+6

LEN+7

Start of Header - always OxFE

Destination - which reader this message goes to Source - the Host address (always 0x00) Command - command reader should execute Length - length of data (can be 0)

Data - data to send (if any)

End of Message - always OxFD

CRC - most significant byte

CRC - least significant byte

Replies from the Reader hâve the following form:

Byte 0

Start of Header

<td> Byte 1</td><td> Byte 2</td><td> Byte 3 Byte 4</td><td> Byte 5...</td><td> Byte len+5</td><td> Byte len+6</td><td> Byte len+7</td>

<td> Destina-</td><td></td><td> Response</td><td></td><td> End of</td><td> LSB of</td><td> MSBaf</td>

<td> tion</td><td> Source</td><td> Code Length</td><td> Data</td><td> Message</td><td> CRC</td><td> CRC</td>

Byte

O

Description

Start of Header * always -xFE

Destination - the Host address (always 0x00)

Source - which reader this message cam from

Response code - described on pg, 7-8 of the “TIRIS™ Bus Protocol”

Length - length of data (never less than i )

Data · response. Fist byte is always the command that initiated

010801

LEN+5

LEN+6

LEN+7

-61the response.

End of Message - always OxFD

CRC - most significant byte

CRC - lease significant byte

To allow for “data transparency”, the CPT protocol impiements a spécial code called the

Data Link Escape or DLE. The DLE is used prior to any character that may for some reason or another be a OxFE (Start of Header), OxFD (End of Message) or OxFC (DLE). Inserting a DLE prior to any of these three characters informs the receiving software to treat the next byte as data 10 instead of a Start of Header, End of Message or even as another DLE.

Example:

Data Stream.·

<td></td><td> 03 Data</td><td> 22</td><td> FC FE FC</td><td> FD 22</td><td> FD</td>

<td> 15</td><td></td><td> Data</td><td></td><td></td><td></td>

<td></td><td></td><td></td><td> DLE</td><td></td><td></td>

Data

DLE

Data

Data

End of Message

Please note that DLE characters are notmciuded as part of the CRC computation, The CRC is calculated on the data packet before DLE insertion. Therefore it is perfectly valid to hâve DLE characters inserted in the CRC.

010801

-62 APPENDIX C

READER SOFTWARE ENHANCEMENTS SOFTWARE

The TIRIS™ reader software has been modified and enhanced according to the présent invention by adding fonctions, synchrônizing the antennas, and modifÿing the host computer-reader protocol to make rt more robust. The enhancements made to the reader software are designed to add fonctionality without removing any that currently exists in commercially available TIRIS™ reader software. The enhancements include, new command codes for the TIRIS™ Bus Protocol (see Appendix BY controlling the antenna multiplexer, adding an antenna scan buffer, utilizing an 10 on-board DIP switch to set the address of the control board, and providing a new communications scheme. The enhancements may be implemented by adding command codes to the TIRIS™ Bus Protocol, defined as Group 3 commands (96 to 127), which hâve been reserved by Texas Instruments specifically for the user. By adding commands in this area, potential future conflicts with the TIRIS™ software fonctions are avoided.

1.0 Scan Buffer

The Scan Buffer is designed to allow the host computer to retrieve ail four antennas at once rather than individually. Part of this is accomplished by putting the System in Gâte Mode.

Gâte Mode îndicates that the system will do répétitive charge-read cycles normally storing any transponder ID that it reads in the reader’s queue for later access. This action has been modified 20 so that the data is actually stored in the Scan Buffer using the foiiowing algorithm:

Set the reader ’s multiplexer to antenna N Charge transponder (send it a Power Puise) Read transponder if received transponder 1D store transponder in Scan BufferfN) else if Scan Buffer(N) has an ID and it has not been read by Host do nothing else clear Scan BufferfN)

Later, when the Scan Buffer is read, flags are set indicating that ail four antennas hâve been read. This provides a “latching” mechanism where any transponder read remaîns in the Scan Buffer

010801

-63until it is read by the host computer (thereby avoiding the pitfall of the host computer missing any transponder reads due to where the host computer read fails within the antenna cycle).

2.0 Command Codes

These are the most visible part of the software enhancement and consists of the following commands:

0x40 (décimal 64) Retums the Wayne CID and TIRIS™ révision

0x62 (décimal 98) Retums the antenna Scan block results

0x64 (décimal 100) Gâte Power Puise

0x65 (décimal 101) Retums the read history

0x66 (décimal 102) Retum variable length antenna scan block results

0x67 (décimal 103) Echo test data

0x68 (décimal 104) Enable/Disable Dispenser Lamps

2.1 Get Version

Command Code: 0x40 (96) Immédiate Mode Only

Data Sent: None

Data Retumed: Success or failure indication. Success is indicated the retuming of a version number string (bytes 0-24 bytes). Failure is indicated by the standard ErrorResponse.

Description: This modifies the current Get Version command to the following:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Wayne CIDx.xx TIRIS x.xx

This fixed string makes it easy to test the version number of the CID (Customer Identification) software. The version of the TIRIS™ software is also retumed for documentation and rtiaintenance purposes.

2.2 Gst Anigrma^çanBugfii:

Command Code: 0x62 (98) Immédiate Mode Only

Data Sent: None

Data Retumed: A total of 36 bytes are retumed, 9 bytes per antenna (1 byte status and 8 byte transponder ID). Failure is indicated by the standard Error-Response.

010801

-64Description: These represent the transponder code last seen. If no transponder was secn, then

0x0000000000000000 is retumed. This fonction retums a structure of the following.

typedef stnict TransponderlD {

Byte Status;

Byte TranspondcrID[8]; } TransponderlD;

TransponderlD Retum Transponders (4);

The status retumed will be one of the following:

Valid Response RO-TRP(OxOO)

RW_TRP (0x01)

MPTCOTRP_U (0x02)'

Invalid Response

NO_READ (0x40)

INCOMPLETE (0x41)

MPTRERR_SPC_DATA (0x46)²

MPTCOTRPJL (0x03)² MPTRERR_STATUS (0x47)²

Note: Ail Status bytes are set to NOJREAD after this command is executed.

2.3 Get Variable Length Antenna Scan Buffer

Command Code: 0x66(102) Immédiate Mode Only

Data Sent: Noue

Data Retumed: A variable length block of data is retumed consisting of one (no transponders) to 25 37 bytes (ail transponders); one byte indicates which antenna data is being retumed with 9 bytes per antenna (1 byte status and 8 byte transponder ID). Fatlure is indicated by the standard Error-Response.

Description: This is a variable length version of the Get Antenna Scan Buffer fonction. It was desïgned on the premise that for a majority of the time, there will not be a 30 transponder présent Even the normal case has two transponders being active (one on each ride ofthe pump). The user ofthis fonction allows the reader to “waste” less time performing CRC’s on empty packets. This fonction returns a structure of the following:

01080

-65struct Packetlnfo {

Byte ActiveAntenna; // bit 0 = = antenna 1, etc.

struct // 0-4 of these follow [

Byte Status;

Byte TransponderID[8J;

J Antenna;

} Transponder ID;

The status retumed will be one of the following:

<td> Valid Response</td><td></td>

<td> RO.TRP</td><td> (0x00)</td>

<td> RW TRP</td><td> (0x01)</td>

<td> MPTCOTRPJJ¹</td><td> (0x02)</td>

<td> MPTCOTRPJL³</td><td> (0x03)</td>

Example (excluding packet body):

00 41...ff

00 41...ff

00 4Uff 00 41...ff

00 41.JF 00 41...ff no antenna antenna 1 antenna 3 antenna 2 and 3 antenna 1 and 4

Note: AU Status bytes in the Scan Buffer are set to NO_READ after this command is executed.

2.4 Gâte Power Puise

Command Code: 0x64 (100)

Data Sent: Byte 0:

Immédiate Mode Only

0x00 tums the Power Puise off

0x01 tums the Power Puise on ^lUnlikely this will be seen in a CID application, i.e., in the présent embodiment.

010801

- 66 Data Retumed: Success is indicated by the standard Command-Completed message. Failure is indïcated by the standard Error-Response.

Description: This fonction allows the Host to prevent a reader from emitting a Power Puise, yet continue to operate. The antenna scan buffets for that reader wili eventually be 5 cleared of ail values.

Tunùng the Power Puise on allows the reader to continue on with the next antenna (the same one that ail the other readers are on).

Note: When the power puise is tumed off the red LED will no longer flash.

2.5 Get Read Hîstory

Command Note: 0x65(101) Immédiate Mode Only

Data Sent: None

Data Retumed: On success, a total of 80 bytes are retumed as 20 four byte unsigned integers. Failure is indicated by the standard Error-Response.

Description: This fonction allows the Host to read history about the success and/or failure of the reader to read transponder codes. It retums the data as follows;

strucl {

unsigned long TotalReads;

unsigned long TotalSuccess;

unsigned long TotalErrNotRead;

unsigned long TotalErrlncompleie; unsigned long TotalErrOther } ReturnedSiruct [4];

This routine clears the totals immediately after sending them to the Host.

2.6 Echo Test Data

Command Code: 0x67 (103) ' Immédiate Mode Only

Data Sent: Up to 200 bytes of test data.

DataRetumed: Onsuccess, thetest dataisretumed conectly. Failure is indicated by the standard Enror-Response.

010801 • 67 Description: This fonction is designed to validate communication by a reader by allowing the user to send arbitrary data to a reader. The reader should retum the same string it was sent.

To test DLE in the CRC, send one OxFE to reader 1, for example,

<td></td><td> Start</td><td> Dst</td><td> Src</td><td> Cmd</td><td> Len</td><td> Data</td><td> End</td><td> CRC</td>

<td> Host Transmits:</td><td> FE</td><td> 01</td><td> 00</td><td> 67</td><td> 01</td><td> FCFE</td><td> FD</td><td> 4B CA</td>

<td> Host Receives:</td><td> FE</td><td> 00</td><td> 01</td><td> 00</td><td> 02</td><td> 67 FCFE</td><td> FD</td><td> FCFE 94</td>

Note that the DLE’s are not counted in the length of the data.

2.7 Enable/Disable Dispenser Lamps

Command Code: 0x68 (104) Immédiate Mode Only

Data Sent: Byte 0 - lamp number (1 or 2)

Byte 1 - light mode (0 - off, I - on, 2 - flash)

Data Retumed: Success is indicated by the standard Command-Completed message. Failure is indicated by the standard Error-Response.

Description: This fonction is designed to control the lamps that are on either side of the dispenser (a.k.a. dispenser or authorization lights). This command allows the user to indicate which lamp should be tumed on, off, or set to flash without affecting the state of the other lamp. This fonction is such that a lamp can go to any state from any other state. For example, the lamp can go from on-to-off, on-to-flashing, off-to-on, off-to-flashing, flashing-to-on, and flashing-to-off.

2.8 Scan Buffer Structure

During the scan of the antennas, the ID of any transponder found will be stored in the eight bytes corresponding to that antenna. Currently the antennas are defined as follows:

Antenna* 1 :large antenna on side 1

Antenna 2:small antenna on side 1

Antenna 3: large antenna on side 2 Antenna 4:small antenna on side 2 The data is stored in a structure similar to the following:

typedef struct TrcmsponderlD

0H8H •68{ unsigned char Status;

unsigned char ID/8J;

/7 antenna status // transponder id } TransponderiD;

TransponderlD ScanBuffer [4]; //Jour antennas

2.9 Dio Switch Addressing

Normally it requires a program connected to the TIRIS™ configuration port to set the address port (as well as other parameters). Since this is a problem in the field, where technicians need to swap parts quickly with a minimum of set-up, the DIP switch that résides on the TIRIS™ board has been co-opted for this task. Four switches give a total of 16 unique addresses. Readers will havc addresses that range from 0x01 through 0x10 (1-16). The master reader, in parttcular, will always hâve address 1 (0x01) which will be represented by setting the master reader DIP switches, numbered 1,2,3, and 4, to the ON, OFF, OFF, and OFF positions, respectively. Similarly, the DIP switches of a slave reader with address 15 (0x0F) will ail be set to the ON position; and the DIP switches of a slave reader with address 16 (0x10) will ail be set to the OFF position. Because of how the DIP switches are used, readers can never be set to hâve an address of 0x00 (the host address).

In addition, the configuration is fixed at 9600 baud, 8 bits, 1 stop bit, no parity, TIRIS™ Bus Protocol, and Mux-Sync synchronization.

2.10 Tuning Antennas

Tuning of the antennas is important for error-free réception of the transponder data. The simplest method of tuning is to unplug the multiplexer line (ST35) coming out of the reader. The multiplexer will default to antenna 1.

2.11 CID System Test Plug

The vérification lamp is normally controlled by the host software which issues a command to the reader. There are some cases where it is handy to hâve the reader tum the lamps on when a valid transponder is detected. This is accomplished by a “test plug”. This test plug consists of a four pin Phoenix plug with a wire-connecting pins 1 and 4. When this plug is inserted into socket ST33 (RES/INP) and the reader is reset (either by cycling power or pressing switch S1 ), the CID software will tum on the appropriate lamp when it “sees” a transponder.

0U801

-69APPENDIXD ADDITIONAL SYSTEM DETAILS

1. Detailed System Description

1.1. Changes to Programming Screens

For a station environment to operate with a CID system, certain programming screens will need to be added. An options screen, which contains the ability to tum CID fonctions on and off for an entire station, is added and is described in more detail below. The ability to tum on and off each reader is programmed. Also, if the station is confïgured for CID, a screen for the mapping of the antennae to the CATs is programmed. A diagnostic screen is added to display the status of each reader and its corresponding antennae.

1.1.1. Options Screen

The above mentioned screens can be added under the Plus/3 Options Menu of the Programming Menu on the Wayne Plus dispenser.

The Options Screen will contain the Station Options screen, the Reader Activation screen, the Antenna to CAT Mapping screen, and the Diagnostic screen. Each of these screens is described below. The “Reader Activation”, “Antenna to CAT Mapping”, and “Diagnostics” screens will not be seen if a station is not confïgured to run CID.

1.1.2. Station Options Screen

The Options screen, as shown in Table D-l below, contains the information needed to setup a station for CID.

SpeedPass allowed at station ................................YES

Table D-1 : Station Options Screen ?

This screen allows the station to tum the CID option on or off for the entire station. This will allow stations to shut off the CDD option in the event that the station does not want to operate with CID. “SpeedPass” is a commercial reference to the system 10. If “SpeedPass allowed at station” is set to No, the “Reader Activation”, “Antenna to CAT Mapping”, and “Diagnostics” screens will not be seen on the Options Screen.

1.1.3. Reader Activation Screen

016801

-70A reader can be turned on or off at this menu. If a reader is turned off, the 4 antennae associated with it wiil not be used. The Reader Activation screen is shown in Table D-2 below.

SpeedPass Reader 1ON

SpeedPass Reader 2 ON

SpeedPass Reader 3OFF

SpeedPass Reader 4ON

Table D-2: Reader Activation Screen

Turning a reader off for a particular pump may be necessary îf an individual reader is

<td> malfunctioning.</td><td> 1.1.4. Antenna to CAT Mapping Screen The Antenna to CAT Mapping Screen is shown in Table D-3 below. Antenna to CAT Mapping</td>

<td> Rdr-Ant:CAT</td><td> Rdr-Ant.CAT Rdr-Ant:CAT Rdr-Ant:CAT Rdr-Ant:CAT Rdr-Ant:CAT</td>

<td> 1-1/2 : 1</td><td> 4-1/2:7</td>

<td> 1- 3/4:2 2- 1/2:3</td><td> 4-3/4 : 8</td>

2-3/4:4

<td> 3-1/2 : 5</td><td></td>

<td> 3-3/4:0</td><td> Table D-3: Antenna to CAT Mapping Screen</td>

The Antenna-to-CAT Mapping screen indicates which antennae are positioned on which

FCATs. There are two antennae per CAT. The odd numbered antennae will be the long range antennae that read the mounted transponders. The even numbered antennae will be the short-range antennae that read the hand held transponders.

If the CAT number is a “0”, then the antennae are not physically connected to a CAT and are ignored. An example of this type of reader setup is for a single-sided CAT where the reader only has 2 antennae connected.

010801

1.1.5 Diagnostic Screen

This screen will provide the status of CIDs at the antennae. This screen'will serve as an aid in the debugging process. An example of this screen is shown below in Table D-4.

<td colspan="3"> SpeedPass Diagnostics</td>

<td> Rdr-Ant</td><td> Mounted CED #</td><td> Hand-Held CID #</td>

<td> 1-1/2</td><td> 1234567890123456789</td><td> OCOOOOCœOOOOOOOOCO</td>

<td> 1-34</td><td> 0000000000000000000</td><td> 1234567890123456789</td>

<td> 2-1/2</td><td> 3456789012345678901</td><td> 0000000000000000000</td>

<td> 2-3/4</td><td> 4567890123456789012</td><td> 2345678901234567890</td>

<td> 3-1/2</td><td> 0000000000000000000</td><td> 0000000000000000000</td>

<td> 3-3/4</td><td> 0000000000000000000</td><td> 0000000000000000000</td>

<td> Refresh</td><td></td><td></td>

<td></td><td> Table D-4: Diagnostics Screen</td><td></td>

<td> 1.2.</td><td> Network Record Changes</td><td></td>

<td></td><td> 1.2.1 CED Authorization Request</td><td></td>

For the CID authorization request, “ICID” will be prepended to the 20 digits read from the transponder and sent in the magnetic stripe field of the authorization record.

1.2.2. CID Authorization Reply

For the CID authorization reply, Network will send the account number back in the reply record with the following fîelds

F- • Field 5, record type will be set to “A” denoting a CID transaction • Field 8 (new field), account number -19 bytes of account number, space filled • Field 9 (new field), expiration date - 4 bytes • Field 10 (new field), print receipt indicator -1 byte • Field 11 (new field), prompt for car wash indicator 1 byte • Field 12 (new field), language indicator -1 byte • Field 13 (new field), reward indicator -1 byte • Field 14 (new field), preference indicator -1 byte

Λί 0801 .72♦ Field 15 (new field), preference data - 40 bytes

The print receipt indicator (field 10) dénotés whether the receipt will be automatically printed or the customer will be prompted. If a Ύ’ is received in the authorization response, the receipt will 5 automatically be printed for the customer. If a ‘N’ is received in the authorization response, the customer will be prompted “Press Yes for a receipt”.

The prompt for car wash indicator, the language indicator, and the reward indicator (fields 11,12, and 13 respectively) will be implemented in a future release.

The preference indicator (field 14) dénotés whether the preference data field is présent or 10 not. The first 33 bytes of the preference datafield (field 15) will be displayed on the indoor console in the pump message window.

1.2.3. CID Sale

For the CID sale completion, the 37th position of the magnetic stripe data will contain a “C” indicator similar to a manual entry,

1.3. Reports &amp; Logs

The reports and authorization log will change for any transactions invûlving CID to include the CID number. The reports that will change are the Denied CAT Pre-Auth report and the Hardware Configuration report. The proposed changes are described below. Non-CID transaction will be reported as they previously were, with no change to the logs or the Denied CAT Pre-Auth 20 report.

1.3.1. Authorization Log

The authorization log will be changed for CID to indicate that a CID transaction has occurred. The CID number will be added under the account number field on the log. An example 25 of the CID authorization log is shown below in Table D-5. The proposed changes are in bold face print. Ifthe transaction is a CID pre-auth (i.e. the Pre-auth field in the card table is set to ‘Y’), the title on the authorization log will be “SP PRE AUTHORIZATION”.

¢10801

-73051695 14:30:36 SP AUTHORIZATION

Acct # 805 086 000 91 906 Exp 0697

SP # 1CED 1234 5678 9012 3456 7890

Addr # 1 TID#01 AmountSIO.OO

Host Message: OK TO PUMP 05000

Table D-5: Authorization Log

<td></td><td> 1.3.2. Denied CID / Timed-Out CID</td>

<td> 10</td><td> If a customer has removed the nozzle on a Vista pump or lifted the lever on a non-Vista pump and the auth received from the network is denied, the transaction will be treated as a Denied Pre-Auth, shown in Table D-6 below. Station</td>

<td> 15</td><td> Report Taker: Donna Denied CAT Pre-Auths X Report Start Time; 12:00:00pm Tue 09 May 95</td>

<td> 20</td><td> FUEL TICKET #002929 05/17/95 06:05:18 PMP#01 CR Acct 805 086 000 91 906 Exp. 0597 SPECIAL, Grade# 02 AmtS 11.78</td>

<td> 25</td><td> . x0006el0s01tl 04:25:00pm Wed 24 May 95 Table D-6: Denied CAT Pre-Auth Report without SpeedPass</td>

<td> 30</td><td> The Modified Denied CAT Pre-Auth report will include CID numbers as shown in bold face print in Table D-7 below.</td>

Station

0K8G1

-74Report Taker Donna Denied CAT Pre-Auths X Report Start Time; 12:00;00pm Tue 09 May 95

FUEL TICKET #002929

05/17/95 06:05:18 PMP#01

CR Acct 805 086 000 91 906 Exp. 0597 SP #1CID 1234 5678 9012 3456 7890 SPECIAL Grade# 02 AmtS 11.78 x0006e!0s0ltl 04:25:00pm Wed 24 May 95

Table D-7: Modified Denied CAT Pre-Auth Report with SpeedPass

If a customer has removed the nozzie (Vista pump) or lifted the lever (non-Vista pump) and the network goes down prior to receiving the auth response, the transaction will be treated as a Denied CAT Pre-Auth (the report is shown in Table D-8 below). The account number and expiration date fields will be printed with ail zeroes to indicate that a time-out has occurred prior to receiving the auth (i.e. no account information is available at that time).

Station

Report Taker: Donna

Denied CAT Pre-Auths X Report Start Time: 12:00:00pm Tue 09 May 95

FUEL TICKET #003131

05/17/95? 06:05:18 PMP#01 . CR Acct 000 000 000 00 000 Exp. 0000

SP#1CID 1234 5678 9012 3456 7890

SPECIAL Grade# 02 Amtî 11.78 xOOOôelOsOlt) 04:25:00pm Wed 24 May 95

01Û891

-75TableD-8: Denied CAT Pre-Auth Report with SpeedPass and No Auth Response

1.3.3. Hardware Configuration Report

The Hardware Configuration Report will change to include the CID reader firmware révision 5 information. A sample report is shown in Table D-9 beiow. .

Station

Report Taker: Donna

H/W Configuration Report

POS CPU:

Wayne Plus/2 Release 2.10e

DATE: Mar 23, 1995 •

PUMP 1:

TYPE: 3 Product

REVISION: 15

PUMP 2:

TYPE: 3 Product

REVISION: 15

SPEEDPASS READER 1:

REVISION: 1.23

XÛ00E04S01T1 08:00:00am Mon 1 Jan 95 ' fTable D-9: Modified Hardware Configuration Report with SpeedPass

1.4. CAT Display Changes

If the CID light is on and the CID idle prompt “Begin Fueling or Cancel SpeedPass” is displayed at the CAT, indicating a CID has been read at the CAT, and the nozzle has not been removed or the lever has not been lifted, the customer may press the cancel key to override the CID

<img file="OA10801A_D0002.tif" />

-76payment method. The CAT wiU prompt the customer “Cancel use of SpeedPass? (Y/N)”. If Yes is pressed, the CID light will tum off and the CAT will display the normal idle prompt (e.g. Insert card or Begin Fueling”). If No is pressed, the CAT will display “Begin fueling or Cancel SpeedPass” and the scénario will continue as if the cancel key was never pressed (i.e. as a CID 5 transaction).

Table D-10 below describes the idle prompts that will be used if a CID has been read.

<td></td><td> Station Operation</td><td colspan="2"> Carrent Idle Display*</td><td colspan="2"> New Idle Display'</td>

<td></td><td> Postpay</td><td> Insert card or Begin fueling</td><td></td><td></td><td> Begin fueling or Cancel SpeedPass</td>

<td> 10</td><td> Postpay/Network Down</td><td> Pump first then Pay inside</td><td></td><td></td><td> Network down Press cancel</td>

<td></td><td> Postpay w/BAC</td><td colspan="2"> Insert card/cash or Rcmove nozzle</td><td></td><td> Begin fueling or Cancel SpeedPass</td>

<td> 15</td><td> Postpay w/BAC/Network Down</td><td> Pump first then Pay inside</td><td></td><td></td><td> Network down Press cancel</td>

<td></td><td> Prepay</td><td> Insert card or Pay cashier</td><td></td><td></td><td> Begin fueling or Cancel SpeedPass</td>

<td></td><td> Prepay/Network Down</td><td> Pay cashier before fueling</td><td></td><td></td><td> Network down Press cancel</td>

<td> 20</td><td></td><td></td><td></td><td></td><td></td>

<td></td><td> Prepay w/BAC</td><td colspan="2"> Insert card/cash or Pay cashier</td><td></td><td> Begin fueling or Cancel SpeedPass</td>

<td></td><td> Prepay w/BAC/Network Down</td><td> Insert cash or Pay cashier</td><td></td><td></td><td> Network down Press cancel</td>

<td> 25</td><td> Full Serve'</td><td> Card, Nozzle or Preset</td><td> 0.00</td><td></td><td> Card, Nozzle or Preset 0.00</td>

<td></td><td> Fuît Serve/Network Down¹</td><td> Remove Nozzle or Preset</td><td> 0.00</td><td></td><td> Rcmovc Nozzle or Preset 0.00</td>

<td></td><td> Full Serve w/BAC'</td><td colspan="2"> Card, Cash, Nozzle or Preset 0.00</td><td></td><td> Card. Cash, Nozzle or Preset 0.00</td>

<td> 30</td><td> Full Serve w/BAC/Net Down¹</td><td> Cash, Nozzle or Preset</td><td> 0.00</td><td></td><td> Cash, Nozzle or Preset 0.00</td>

<td></td><td> Unattended</td><td> Insert card</td><td></td><td></td><td> Begin fueling or Cancel SpeedPass</td>

<td></td><td> Unattended w/BAC</td><td> Insert card or cash</td><td></td><td></td><td rowspan="2"> Begin fueling or Cancel SpeedPass</td>

<td> 35</td><td></td><td></td><td></td><td></td>

<td></td><td> Unattended w/BAC, Net Down</td><td> Insert cash</td><td></td><td></td><td> Network down Press cancel</td>

* Idle Prompts ¹ Prompts to be used if station is configured for CID and a transponder has been read at CAT ¹ Idle prompts in full serve mode will not change

Table D-10: CAT Idle Prompt Changes

019801

2. Additional Features

2.1. Multiple Transponder Use

A transponder may be used at more than one pump at a time. A waming system has been implemented to inform the cashier that a transponder is currently being used fora CDD sale at one 5 pump and a sale is beginning at another pump that will use the same CED. An inform message is dispiaved on the POS for the second use of the CID when the nozzle is removed for a Vista pump or when the lever is lifted for a non-Vista pump. The cashier is required to acknowiedge the message, the customer is not stopped in any way from using this transponder in a multiple use scénario. If the cashier does not want the customer to use the transponder in this manner then the 10 cashier must hit pump stop or notify the customer.

The message dispiaved on the indoor POS is “CDD at CAT #X in use at CAT #Ύ. The cashier will then press the acknowiedge key. An error log message, “CID IN USE AT OTHER CAT”, will also be printed.

2.2. Reward Indicator

The authorization response received from the host contains a reward indicator field. If this field contains a Ύ’, then the CID light will flash off and on until the end of the sale, if this field contains a ‘N’, then the CDD light will remain on as before indicating that a CID has been read. When the light is in flash mode, the light is not an indicating of a CID in read range anymore; if the nozzle is removed for a Vista pump or lifted for a non-Vista pump when the light is off during this flash mode, the sale is a CID transaction.

2.3. Blank Read Threshold

The Station Options Screen has been modified to include a programmable blank read threshold as shown in Table D-l 1 below. This field is used to aid in weeding out false CID reads. these blank reads can occur while the CID is actually in read range. This option allows 25 programming the number of consecutive blanks that register that the CDD has moved out of read range. The.CDD light will not be tumed off for a mounted CDD until the number of consecutive blank reads threshold is reached.

SpeedPass Station Options ³⁰

SpeedPass allowed at station.................................YES

Blank CDD reads required to indicate no CID...........5

010801

-78Table D-l 1 : Modified Station Options Screen

2.4. CID Light Operation for Denied Mounted CID Authorization

For mounted CIDs, the CID light will be tumed off whenever a denîed authorization is 5 received from the host. The light will not be tumed on again after the nozzie is replaced for that mounted CED.

3. Misccllaneous Additional Features

The following items may also be implemented:

« Use Car Wash preference • Use of transponders indoors • Tum on car wash • Dispiay rewardat the CAT during fueling • Flashing P” for customer préférences display on the console lô · Use of the language indicator • Poor Man’s Store &amp; Forward