Dispensing system and method with radio frequency customer identification
Abstract
A SYSTEM AND A METHOD FOR FORMING A FUEL SUPPLIER (14) WITH A CAPACITY TO IDENTIFY CUSTOMERS THROUGH RADIO FREQUENCY SIGNALS. WITH THE SYSTEM AND METHOD, IT IS DETERMINED IF A TRANSPONDER (23, 25) THAT CONTAINS CUSTOMER IDENTIFICATION DATA IS FOUND WITHIN THE LIMITS OF A SUPPLIER (14) THAT MUST BE ACTIVATED BY THE CUSTOMER TO START A TRANSACTION AND UNDERSTAND A ASSOCIATED READER (20) TO EMIT RADIO FREQUENCY SIGNS AND RECEIVE THE TRANSFER CUSTOMER IDENTIFICATION DATA (23, 25) THAT RESPOND TO THE RADIO FREQUENCY SIGNS ISSUED. WHEN THE TRANSPONDER (23, 25) IS INSIDE THE SURTIDER'S LIMITS, THE CLIENT RECEIVES A SIGNAL THAT INDICATES THAT IT IS WITHIN THE LIMITS. AFTER THE ACTIVATION OF THE SURTIDER (14) WHICH HAS PLACED AFTER HAVE BEEN DETERMINED THAT THE TRANSPONDER (23, 25) IS FOUND WITHIN THE LIMITS, THE CUSTOMER IDENTIFICATION DATA RECEIVED BY THE READER (20) IS ASSOCIATED WITH A TRANSACTION ACTIVATED. THEN THE TRANSACTION IS ALLOWED IN THE ACTIVATED SURTIDER (14) AND THE CUSTOMER IS CHARGED ACCORDING TO CUSTOMER IDENTIFICATION DATA.

Term
Term ended
Projected expiry passed 18 December 2016, 9.8 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
51 claims: 19 independent, 32 dependent
- 1ES 2 239 342 T3 REIVINDICACIONES 1. Un método de distribución con capacidad de identificación de un cliente por radiofrecuencia, para cargar en la cuenta de dicho cliente las transacciones de ventas hechas por él, cuyo método comprende:- determinar si un respondedor (25) que contiene los datos de identificación está dentro del alcance de un distribuidor (14), cuyo distribuidor requiere la activación por dicho cliente para iniciar una transacción, e incluye un lector (20) asociado a él para emitir señales de radiofrecuencia dentro del alcance del distribuidor y para recibir los datos de identificación del cliente procedentes del respondedor, en respuesta a las señales de radiofrecuencia emitidas y recibidas por dicho respondedor;- determinar si el distribuidor ha sido activado por el cliente después de una determinación de que el respondedor está dentro del alcance de dicho distribuidor;- a la activación del distribuidor después de la determinación de que el respondedor está dentro del alcance de dicho distribuidor, asociar los datos de identificación recibidos por el lector a una transacción en el distribuidor activado, con lo que la transacción en dicho distribuidor activo es permitida y cargada al cliente, de acuerdo con los datos de identificación;- caracterizado porque el respondedor comprende un respondedor manual, y loa datos de identificación son datos de identificación del cliente.
- 2El método de la reivindicación 1, que comprende además, antes de permitir la transacción en el distribuidor activado, determinar si la cuenta de un cliente correspondiente a los datos de identificación de dicho cliente es válida, y autorizar un cargo de la transacción sólo a una cuenta de cliente válida.
- 3El método de la reivindicación 1, en el que la determinación de la validez de la cuenta del cliente incluye el acceso a una red de tratamiento de tarjeta a distancia para verificación de la cuenta.
- 4El método de la reivindicación 2, en el que la determinación de la validez de la cuenta del cliente incluye el acceso a un archivo local para verificación de dicha cuenta.
- 5El método de la reivindicación 2, en el que la determinación de la validez de la cuenta del cliente se produce después de la activación de al menos un distribuidor.
- 6El método de la reivindicación 2, en el que la determinación de la validez de la cuenta del cliente se produce antes de la activación de al menos un distribuidor.
- 7El método de cualquiera de las reivindicaciones precedentes, en el que el distribuidor es un surtidor de combustible.
- 8El método de la reivindicación 1, cuyo método comprende además proporcionar al cliente una indicación de dentro de alcance, cuando el respondedor está dentro del alcance del surtidor.
- 9El método de la reivindicación 8, que comprende además:- no cumplir la manera de tratar la transacción en el distribuidor, que no carga al cliente de acuerdo con los datos de identificación de él cuando un tiempo límite se ha excedido antes de que el distribuidor sea activado, después de la determinación de que el respondedor está dentro del alcance de dicho distribuidor.
- 10El método de la reivindicación 8, que comprende además:- no cumplir la manera de tratar la transacción en el distribuidor, que no carga al cliente de acuerdo con los datos de identificación de él, cuando dicho cliente seleccione un método de pago alternativo.
- 11El método de la reivindicación 8, que comprende además:- no cumplir la manera de tratar la transacción en el distribuidor, que no carga al cliente de acuerdo con los datos de identificación de él cuando el respondedor no está dentro del alcance del distribuidor durante un tiempo especificado antes de la activación de dicho distribuidor por el cliente.
- 12El método de la reivindicación 8, que comprende además:- no cumplir la manera de tratar la transacción en el distribuidor, que no carga al cliente de acuerdo con los datos de identificación de él cuando el respondedor ya no está dentro del alcance del distribuidor después de la activación de dicho distribuidor. ES 2 239 342 T3
- 13El método de la reivindicación 8, que comprende además:- anular la provisión de una indicación de dentro de alcance del cliente cuando el respondedor ha sido utilizado previamente para completar una transacción en un distribuidor dentro de un período de tiempo predeterminado.
- 14El método de una cualquiera de las reivindicaciones 8 a 13, que comprende además:- ejecutar actividades especificadas por el cliente en el distribuidor en respuesta a los datos de identificación de dicho cliente recibidos por el lector.
- 15El método de la reivindicación 9, en el que el distribuidor es un surtidor de combustible.
- 16El método de una cualquiera de las reivindicaciones 8 a 15, que comprende además desactivar la indicación del cliente al completar la transacción.
- 17El método de una cualquiera de las reivindicaciones 8 a 16, que comprende además:- a la determinación de que el respondedor está dentro del alcance del surtidor, presentar en éste una indicación al cliente para comenzar la transacción.
- 18El método de una cualquiera de las reivindicaciones 8 a 17, en el que el surtidor es un surtidor de combustible que cuenta con una boquilla, y la activación de dicho surtidor comprende levantar la citada boquilla.
- 19El método de una cualquiera de las reivindicaciones 8 a 17, en el que el surtidor es un surtidor de combustible que cuenta con una boquilla, y la activación de dicho surtidor comprende levantar la palanca de dicha boquilla.
- 20El método de una cualquiera de las reivindicaciones 8 a 17, en el que el surtidor es un surtidor que cuenta con un conmutador de selección, y la activación de dicho surtidor comprende accionar el conmutador de selección.
- 21El método de una cualquiera de las reivindicaciones 8 a 20, que comprende además, antes de permitir la transacción en el surtidor activado, determinar si la cuenta de un cliente que corresponde a los datos de identificación de él es válida, y autorizar un cargo de la transacción sólo en una cuenta de cliente válida.
- 22El método de una cualquiera de las reivindicaciones 8 a 21, en el que el respondedor es un respondedor de lectura-escritura, de modo que los datos de identificación del cliente del respondedor pueden incluir información histórica de transacciones, que es actualizada con el uso.
- 23El método de la reivindicación 1, en el que el lector está dotado de una primera antena (22A, B) para emitir señales de radiofrecuencia dentro del alcance del distribuidor, y para recibir los datos de identificación del cliente, cuyo método comprende además:- determinar si dicho respondedor manual (25) que contiene los datos de identificación del cliente está dentro de un alcance próximo del distribuidor, cuyo lector (20) del distribuidor incluye una segunda antena (24A, B) para emitir señales de radiofrecuencia dentro de dicho alcance próximo, y para recibir datos de identificación del cliente procedentes del respondedor manual en respuesta a las señales de radiofrecuencia emitidas y recibidas por el respondedor manual;y - cuando el respondedor manual está dentro de un alcance próximo antes de que el distribuidor sea activado, anular el uso en el distribuidor del respondedor (23) montado sobre un vehículo, con lo que después de la activación del distribuidor y la asociación de los datos de identificación del cliente del respondedor manual recibidos por el lector a una transacción en el distribuidor activado, la transacción en dicho distribuidor activado es permitida y es cargada al cliente, de acuerdo con los datos de identificación del respondedor manual.
- 24El método de la reivindicación 23, en el que el distribuidor es un surtidor de combustible dotado de una boquilla, y la activación de dicho surtidor comprende levantar dicha boquilla.
- 25El método de la reivindicación 23, en el que el distribuidor es un surtidor de combustible dotado de una palanca de boquilla, y la activación de dicho surtidor comprende levantar la palanca de la boquilla.
- 26El método de una cualquiera de las reivindicaciones 23 a 25, en el que la primera antena es una antena manual que puede hacerse oscilar delante del respondedor montado sobre el vehículo, para situar dicho respondedor dentro del alcance del surtidor.
- 27El método de una cualquiera de las reivindicaciones 23 a 26, en el que el vehículo incluye un ordenador a bordo, y el respondedor montado sobre el vehículo es enlazable al ordenador de a bordo para la lectura de información de diagnóstico para transmisión desde el respondedor montado sobre el vehículo a la primera antena. ES 2 239 342 T3
- 28El método de una cualquiera de las reivindicaciones 24 a 27, en el que el lector está colocado dentro de un edificio de la estación de servicio, para uso del respondedor manual para completar las transacciones en el lector del edificio de dicha estación de servicio.
- 29El método de una cualquiera de las reivindicaciones 23 a 28, en el que un lector está asociado a un lavadero de coches, para uso por el respondedor montado sobre el vehículo para completar una transacción de lavado del coche.
- 30Un sistema de distribución con capacidades de identificación de un cliente por radiofrecuencia, para cargar a dicho cliente las transacciones de las ventas hechas por él, cuyo sistema comprende:- medios para determinar si un respondedor (25) que contiene datos de identificación está dentro del alcance de un distribuidor (14), cuyo distribuidor requiere la activación por dicho cliente para iniciar una transacción, y que incluye un lector (29) asociado al distribuidor para emitir señales de radio frecuencia dentro del alcance de dicho distribuidor, y para recibir datos de identificación procedentes del respondedor que responden a las señales de radio frecuencia recibidas por el respondedor;- medios para proporcionar al cliente una indicación de dentro de alcance, cuando el respondedor está dentro del alcance del distribuidor;- medios (16) para determinar si el distribuidor ha sido activado por el cliente después de una determinación de que el respondedor está dentro del alcance del distribuidor;y - medios (16) para, al activar el distribuidor después de la determinación de que el respondedor está dentro del alcance del distribuidor, asociar los datos de identificación recibidos por el lector con una transacción en el distribuidor activado, con lo que se permite dicha transacción en el distribuidor activado y se carga al cliente de acuerdo con los datos de identificación;- caracterizado porque el respondedor comprende un respondedor manual, y los datos de identificación son datos de identificación del cliente.
- 31El sistema de la reivindicación 30, en el que el distribuidor es un surtidor de combustible que tiene una boquilla, y la activación de dicho surtidor comprende levantar dicha boquilla.
- 32El sistema de la reivindicación 30, en el que el distribuidor es un surtidor de combustible que tiene una palanca de boquilla, y la activación de dicho surtidor comprende el levantamiento de dicha palanca de boquilla.
- 33El sistema de las reivindicaciones 30, 31, o 32, que comprende además medios para antes de permitir la transacción en el surtidor activado, determinar si una cuenta del cliente que corresponde a los datos de identificación de dicho cliente es válida, para autorizar el cargo de la transacción sólo a una cuenta del cliente válida.
- 34El sistema de la reivindicación 30, que comprende una pluralidad de distribuidores (14), para proporcionar cada uno de ellos una transacción de cliente;- una antena (24) asociada a un área de distribución de cada distribuidor;- al menos un lector (20) como antes se ha dicho, conectado al menos a una de las antenas para emitir una señales de radiofrecuencia desde las antenas dentro del alcance de cada área de distribución, y para recibir los datos de identificación del cliente procedentes del respondedor, cuyos datos de identificación del cliente son recibidos por el lector, en el uso del sistema, que responde a las señales de radiofrecuencia emitidas cuando el respondedor está dentro del alcance del área de distribución;- medios para sincronizar las señales de radiofrecuencia emitidas desde las antenas y evitar que datos de identificación del cliente sean recibidos por una antena asociada a una de las áreas de distribución, desde un respondedor situado en una, diferente, de las áreas de distribución;y - medios de tratamiento (16) conectados al menos a un lector y a los distribuidores, para asociar los datos de identificación del cliente recibidos en el área de distribución a una transacción en el distribuidor asociado, con lo que la transacción en el distribuidor es cargada al cliente de acuerdo con los datos de identificación de él.
- 35El sistema de la reivindicación 34, en el que algunas de las antenas (24A) que forman un primer juego se enfrentan en una primera dirección, y otras de las antenas (24B) que forman un segundo juego se enfrentan en una segunda dirección, cuyos medios de sincronización comprenden medios para hacer que las emisiones de señales de radiofrecuencia procedentes del primer juego se produzcan en tiempos diferentes con relación a las emisiones de señales de radiofrecuencia procedentes del segundo juego.
- 36El sistema de la reivindicación 34, en el que las antenas están dispuestas en dos grupos, con las antenas (24A) del grupo uno dispuestas orientadas en una dirección en general frente a la dirección de orientación de las antenas del otro grupo, y en el que los medios de sincronización comprenden:ES 2 239 342 T3 - medios para hacer que las emisiones de señales de radiofrecuencia procedentes de las antenas orientadas en direcciones en general enfrentadas entre sí, se produzcan en tiempos diferentes también entre sí.
- 37El sistema de la reivindicación 34, en el que las emisiones de señales de radiofrecuencia procedentes de cada antena están separadas por un tiempo de sincronismo entre emisiones, y al menos una de las antenas está orientada en una primera dirección, y también al menos una de las antenas está orientada en una segunda dirección, de modo que los medios de sincronización hacen que las antenas orientadas en la primera dirección emitan señales de radiofrecuencia durante el tiempo de sincronismo de las emisiones de las antenas orientadas en la segunda dirección.
- 38El sistema de la reivindicación 34, en el que dicho al menos un lector incluye un lector principal que tiene un procesador y al menos un canal al que está conectada dicha antena, y al menos un lector esclavo que tiene un procesador y al menos un canal al que está conectada la citada antena, cuyos medios de sincronización comprenden:- una línea (74) de señal de sincronización que conecta los procesadores de los lectores principal y esclavos;- una señal de sincronización que opera entre unos estados primero y segundo y que es generada por el procesador del lector principal sobre la línea de señal de sincronización, de modo que cuando la señal de sincronización está en el primer estado, el procesador del lector principal instruye para que señales de radiofrecuencia sean emitidas desde dicha antena conectada a su al menos un canal, y el procesador del lector esclavo instruye para que señales de radiofrecuencia sean emitidas desde dicha antena conectada a su al menos un canal, con lo que se sincronizan las emisiones de radiofrecuencia por las antenas conectadas a los canales de los respectivos lectores.
- 39El sistema de la reivindicación 38, en el que cada uno de el al menos un lector incluye al menos unos canales primero y segundo, y cada uno tiene una de dichas antenas conectada a él, y en el que la señal de sincronización incluye un impulso de longitud variable, cuya longitud indica uno particular de al menos uno de los canales primero y segundo, de modo que el impulso de longitud variable de la señal de sincronización instruye a los procesadores de los lectores principal y esclavos para emitir señales de radiofrecuencia por las antenas conectadas al mismo de al menos los canales primero y segundo al mismo tiempo, con lo que se sincronizan las emisiones de radio frecuencia por las antenas conectadas a los mismos canales de al menos los canales primero y segundo.
- 40El sistema de la reivindicación 30, en el que:- el lector está dotado de antenas, cada una para la emisión de señales de radiofrecuencia y asociada a las respectivas áreas de distribución a cada lado del surtidor;y - al menos un lector (20) está conectado a las antenas, como antes se ha dicho.
- 41El sistema de la reivindicación 40, en el que las antenas se extienden hacia fuera desde los lados opuestos del surtidor, y están alineadas con relación a dicho surtidor de modo que un lado de cada antena está dispuesto para generar un campo electromagnético hacia abajo y hacia fuera desde el surtidor, dirigido hacia el área de distribución, y el otro lado de la antena está dispuesto para generar un campo electromagnético hacia arriba y en alejamiento desde el otro lado del surtidor.
- 42El sistema de la reivindicación 40, en el que las antenas se extienden hacia fuera desde los lados opuestos del surtidor, de modo que el plano de la antena es sustancialmente perpendicular a los lados de dicho surtidor.
- 43El sistema de la reivindicación 40, en el que el alcance es aproximadamente de 1,5 a 2,1 m en profundidad desde el lado del surtidor.
- 44El sistema de la reivindicación 40, en el que las antenas son de alcance corto, montadas con relación al surtidor para uso por el respondedor manual (25).
- 45El sistema de la reivindicación 44, en el que el alcance del respondedor de las antenas de alcance corto es aproximadamente de 76,2 a 152,4 mm.
- 46El sistema de la reivindicación 40, en el que las antenas comprenden:- antenas de alcance largo (22A, 22B) montadas con relación al surtidor para uso por un respondedor (23) montado sobre vehículo;y - antenas de alcance corto (24A, 24B) montadas con relación al surtidor para uso por un respondedor manual (25).
- 47El sistema de la reivindicación 30, en el que cada una de las antenas está asociada al área de distribución del surtidor, y cuyas antenas incluyen una antena de alcance largo (22A) situada con relación al surtidor para uso por un respondedor de tipo montado sobre vehículo, y una antena de alcance corto (24A) situada con relación al surtidor para uso por el respondedor manual;y - al menos un lector como antes se ha dicho, está conectado a las antenas para emitir señales de radiofrecuencia ES 2 239 342 T3 desde la antena de alcance largo dentro de un alcance largo seleccionado del área de distribución, y desde la antena de alcance corto dentro de un alcance corto seleccionado del área de distribución, y para recibir los datos de identificación del cliente procedentes de los respondedores, cuyos datos de identificación del cliente son recibidos por el lector, en el uso del sistema, en respuesta a las señales de radiofrecuencia cuando el respondedor manual o montado en vehículo está dentro del alcance del área de distribución.
- 48El sistema de la reivindicación 47, que comprende además un indicador de alcance asociado al surtidor para indicar al cliente cuándo el respondedor manual o montado sobre vehículo está dentro del alcance del área de distribución.
- 49El sistema de las reivindicaciones 47 ó 48, en el que cuando ambos respondedores, el (23) montado sobre vehículo y el (25) manual, están dentro del alcance del área de distribución, los medios de tratamiento anulan el uso del respondedor montado sobre vehículo para cargo al cliente, y en cambio permiten el uso del respondedor manual (25) para cargar la transacción a dicho cliente.
- 50El sistema de las reivindicaciones 47, 48, 49, en el que el alcance largo seleccionado comprende una distancia desde el surtidor para repostar el vehículo.
- 51El sistema de las reivindicaciones 47, 48, 49, o 50, en el que el alcance corto seleccionado comprende un emplazamiento dentro de varios centímetro desde la antena de alcance corto, en el que el respondedor de alcance corto puede ser hecho oscilar por el cliente.
Independent claims51
728 paragraphs in 51 sections, as filed
ES 2 239 342 T3
DESCRIPTION
Dispensing system and customer identification method with radio frequency.
Background of the invention
The present invention relates to distributors, and more particularly to fuel dispensers that use radio frequency identification technology to automatically identify a customer with little or no intervention from him, to authorize the sale of products or services to said customer, and subsequently charge your account the amount of said products or services. The present invention is particularly useful in a service station environment, in which customers can purchase fuel for their vehicles, wash the car, or purchase items such as food, drinks, or others, in an appropriate store, or from the car through a window located in the establishment.
Typically, when the customer purchases fuel at a service station, he makes the payment in cash or by credit card to the station employee, either before or after refueling. The employee controls the activation of the pump to supply the fuel. If payment is required before refueling begins, the employee must flip a switch, typically near the cash register, to unlock the dispenser and allow dispensing to begin. After the dispensing is completed and the nozzle is returned to its home position, the clerk manually resets the dispenser by activating a switch on the cash register.
An example of an existing gas station control system, integrating dispenser and cash register control, is the Wayne Plus / 2, available from Wayne Division, Dresser Industries, Inc. of Austin, Texas, El Wayne Plus / 2 system includes a base computer or site controller, and a point of sale terminal interfaced with the employee.
The Wayne PLus / 2 base computer is equipped with a microprocessor and a pump control circuit board, electrically linked to the various jets in the station to control the pumps. The pump control circuit board connects or disconnects the jets, controls the flow rate, and keeps track of the amount of fuel delivered. Said base computer is also provided with memory, communication ports, and serial input / output board ("SIO") that can be linked to a remote customer authorization network.
The point of sale terminal (also known as the Wayne Plus brand retail control system) includes a card reader to read and identify credit / debit cards, a keypad for use by employees, and a display. The employee can use the POS terminal to process payments and control the activation of the pumps. If a customer chooses to use a credit / debit card for payment, the employee swipes the card through the card reader, and the information about the card is sent to the remote customer authorization network for verification and annotation. consider.
However, many service stations are now equipped with credit / debit card readers for direct customer use. An example of a service station system that integrates dispenser control, cash register control, and credit / debit card processing, which can be originated at the dispenser, is the Wayne Plus / 3 system.<sup>TM</sup> available from Wayne Division, Dresser Industries, Inc. of Austin Texas. This system is similar to the Wayne Plus / 2 described above. However, the base computer or site controller has been modified to accommodate dispensers equipped with customer-activated terminals (TACs) electronically linked to the base computer.
Each of the customer-activated terminals (TACs) has a card reader, a display that presents messages to the customer, and a keyboard for use by that customer to make fuel and payment selections, a printer to print receipts , and individual price displays corresponding to the dispenser distribution nozzles. Examples of dispensers equipped with such customer activated terminals (TACs) are Vista brand dispensers available from Wayne Division, Dresser Industries Inc. of Austin, Texas.
The Wayne Plus / 3 base computer is loaded with a logic program trigger (also referred to here as "primitive") for control and interface with the TACs. The customer, before starting to refuel, uses the TAC keyboard to select the desired type of payment (for example, cash or credit / debit card). If the customer chooses to pay with said card, he inserts it in the TAC reader and waits for a message to appear indicating that he can start refueling. The TAC sends the credit / debit card information to the base computer, which in turn sends this information to the remote client authorization network, for verification and debiting the account. US Patent No. 5,340,969 issued August 23, 1994 to Dresser Industries Inc. describes a method and apparatus for approving or rejecting fuel supply transactions with the use of credit cards.
In the two types of systems described above, the customer is required to interact (for payment purposes), either with the service station employee or with the terminal (TAC) of the dispenser activated by said customer. US Patent No. 5,072,380 issued to Robert E. Randelman et al. describes an automatic recognition system
ES 2 239 342 T3 of the vehicle and charge to the customer's account, which can be used in the surroundings of a service station. The system automatically recognizes vehicles and relates the purchase of products and services to that vehicle.
The .380 patent system includes an antenna embedded in the ground, near a gasoline distribution pump. The antenna is connected to a controller located in a housing close to the antenna. The controller controls the output of a radio frequency signal from the antenna, and can detect an input RF signal. This antenna is always activated, and therefore can create an electromagnetic field with a certain radio frequency in the refueling area.
The .380 patent system also includes an issuer (or card) attached to a vehicle. Said card comprises an RF coil and an integrated circuit component. When the card crosses the electromagnetic field it is activated. Said card then emits a coded electromagnetic pulse signal. The controller receives the signal and converts it to a stream of data bits. A computer receives said current from the controller, and in turn uses the aforementioned data to present information on the pump display, to control the dispenser and for charging purposes.
A disadvantage of the .380 patent is that the antenna that emits the electromagnetic field is embedded in the ground, near the fuel dispenser. Installing such an antenna (or antennas where there is more than one dispenser) can be costly, and can lead to a fire hazard from splashing or leaking fuel from storage tanks, typically located underground near the dispensers. . Furthermore, when there are multiplex dispensers, and therefore multiple antennas and controllers are present, the system does not adequately prevent a vehicle card from being activated by more than one antenna at the same time, and being detected by more than one controller in that time. , so that it can happen that when antennas are located close to each other they interfere with each other. Furthermore, the system does not prevent the inadvertent detection of vehicle cards not intended to be used in a refueling transaction.
Many service stations provide separate fuel supplies on either side of a pump, and have several rows of pumps spaced in close proximity. With such an arrangement of dispensers and with the .380 patent system, the card of a vehicle stopped between antennas can be detected by the wrong controller, that is, one not associated with the pump where the vehicle is actually receiving fuel, or it can being mistakenly detected by a controller, that is, when the vehicle stops near an antenna, but is not refueling.
There are other automatic identification systems that use radio frequency technology. For example, Texas Instruments Incorporated of Dallas, Texas, markets a number of radio frequency identification systems known as the TIRIS ™ (Texas Instruments Registration and Identification Systems) product line. Such TIRIS ™ product line includes radio frequency transponders (read-only as well as read-write), which can be of low or high frequency operation, and which can be attached to or embedded in objects, or held by hand. The readers, through antennas, send radio frequency waves to the responders, and the responders radiate the stored data back to the reader for treatment. Suggested applications for the TIRIS ™ product line include automatic access systems for car park entry and exit barriers, vehicle anti-theft systems (in which the transponder is located in the ignition key, and a transceiver module is located near the ignition), and a fuel supply system (in which the responder is mounted next to the vehicle's fuel tank, and a transceiver is mounted on the jet nozzle). However, the application of the fuel delivery system is not desirable because the maintenance of the nozzle of the dispenser with the transceiver can present a service problem, as well as the problem of its replacement, and in addition, the location of the responder and of the transceiver may create a fire hazard.
The application of radio frequency customer identification (IDC-RF) technology to a service station is fraught with risks, with problems so far unsolved. In large gas stations, with multiple islands with heavy two-sided pumps, and unpredictable influx of users, there is the possibility of inadvertent crosstalk, that is, “crossed readings” from a transponder (IDC-RF) attached to a vehicle using the wrong reader / antenna. Crosstalk can result in an erroneous charge on a customer's account for services never received. Although commercially available readers can be physically linked or otherwise actuated to synchronize their transmission pulses, a system and strategy to effectively synchronize multiple readers in the gas station environment has not yet been developed, to reduce the minimal, if not completely eliminated, crisscross readings. The problem for implementing a synchronization strategy, once determined, is further complicated by individual readers being left out of synchronization in the course of detecting responders.
In addition to transponder crosstalk, other aspects of the customer identification procedure are less than ideal when using IDC-RF technology in a service station environment. As noted above, the .380 patent vehicle recognition system, in addition to providing an impractical antenna / controller arrangement, utilizes a vehicle identification method that begins by activating the count when the vehicle is determined to be in proximity. to the antenna has stopped, and based on that determination blocks other antennas (and their respective pump controllers) from reading the same client responder. Although the above may be appropriate in the environment of an idealized service station with traffic patterns
ES 2 239 342 T3 of predictable vehicles, this method of activation is unreliable in a multi-island station with two-sided pumps, and can result in problematic or inappropriate client activation.
Therefore, what is needed is a radio frequency customer identification system (IDC-RF) for a service station, which reliably and accurately identifies and charges customers for service or product purchases, in a environment that has multiple dispensers and / or outlets.
Reference is made to document US-A-5,072,380, which describes a method and system that identifies a vehicle in a pre-established area, typically on a refueling and service station associated with said vehicle. Each of these has a transponder that communicates with the service station by means of radio frequency signals. The responder is mounted on the vehicle.
Summary of the invention
Accordingly, the distribution system and method of the present invention uses radio frequency customer identification capabilities in the service station environment to reliably and accurately identify customers and charge their purchases to their account. .
According to one aspect of the invention, a distribution method is provided with capabilities for identifying the customer by radio frequency, and for debiting the amount of the transactions carried out in his account, which method comprises; determine if a responder that contains the customer's identification data is within range of said distributor, whose distributor requires activation by the customer to initiate a transaction, and which includes a reader associated with it to emit radio frequency signals within range from the distributor, and to receive customer identification data from the responder in response to radio frequency signals received by said responder, and whose responder comprises a manual responder that contains the customer's identification data; determining whether the distributor has been activated by the customer after a determination that the responder is in range of the distributor; and upon the activation of the distributor that follows the determination that the responder is within said scope of the distributor, associating the customer identification data received by the reader with a transaction in the activated distributor, which allows said transaction in said distributor activated and the amount is charged to the customer according to his identification data.
According to another aspect of the invention, a distribution system is provided with the ability to identify the customer by radio frequency, to charge said customer the amount of the transaction sales, the system comprising: means to determine if the manual responder that contains the customer's identification data is within the reach of a distributor, which requires its activation by the customer to initiate a transaction, and includes a reader associated with it to emit radio frequency signals within within the scope of the distributor, and to receive customer identification data from the responder in response to radio frequency signals emitted and received by the responder; means for providing an indication to the customer that he is in range when the responder is in range of the distributor; means for determining whether the distributor has been activated by the customer after determining that the responder is in range of the distributor; and means for activating the distributor, after determining that the responder is within the scope of the distributor, to associate the customer identification data received by the reader with a transaction at the activated distributor, thereby allowing said transaction and the amount is charged to the customer according to his identification data.
In one embodiment, the present invention is embodied as a distribution system that includes a responder that contains the customer identification data; a distributor to effect a transaction for the customer within a distribution area; antennas each associated with the distribution area of the distributor, and which antennas also include a long-range antenna located in relation to the distributor for use by the transponder and of a type mounted on a vehicle, and another short-range antenna located with relationship to the distributor for use by the manual type responder; at least one reader connected to the antennas to emit radio frequency signals from the long-range antenna within a selected long-range of the range, and from the short-range antenna within a selected short-range of the range, and to receive the customer's identification data from the responder, whose customer identification data is received by the reader in response to radio frequency signals emitted when the responder is within range of the distribution area; and a processor arrangement connected to at least one reader and the distributor to associate the customer identification data received in the distribution area with a transaction at the distributor, whereby the amount of said transaction is charged to the customer in accordance with his identification data.
Embodiments of the present invention are able to avoid the aforementioned problems of the prior art, by providing a reliable and secure identification system of a known customer, with which the services or products purchased by the customer at a station can be automatically identified. service and charge the customer's account the amount of their purchases. The system, described in detail below, is easily interfaced with existing service station systems to provide general customer identification, billing, statement of account, and pump or dispenser control.
With the customer identification system described, the customer is given flexibility to use a short-range manual responder for automatic identification and debiting, or you can override the use of the responder and select a further payment method. conventional. This responder contains data from
ES 2 239 342 T3 personal identification of the customer, which are transmitted by radio in response to predetermined radio frequency ("RF") waves.
The system may include long-range antennas, mounted on the tops of the fuel dispensers, and short-range antennas mounted on the sides of the fuel dispensers. Readers housed in the dispensers send emergency radio frequency pulses to the antennas, which in turn direct the energy pulses to create electromagnetic fields. The antennas are optimally positioned so that the electromagnetic fields cover predetermined areas near the jet. The frequency, power and design of the antenna have been selected to ensure an adequate reading area, and to eliminate the reflective signals present at UHF frequencies. The areas are set so that there is little or no overlap with electromagnetic fields that may be created in adjacent or nearby jets. In the case of a long-range antenna, the electromagnetic field can cover an area that extends several decimeters from the jet, while in the case of short-range antennas, the electromagnetic field can extend several centimeters from the jet.
The antennas also capture customer identification data that is radiated by the responders. If a hand-held transponder enters the electromagnetic field created by a short-range antenna, such as when a customer moves the transponder in front of such an antenna, the hand-held transponder will be activated and will radiate its customer identification code (“IDC”). ). The short-range antenna detects the IDC code and sends it to the associated reader, for decoding and processing.
To further minimize the potential for interference between antennas from adjacent or nearby sources, the system coordinates the transmission of pulsed waves from the various readers. In general, readers selectively send pulse waves so that only antennas facing each other in the same direction send pulse waves at the same time. Other pulse timing arrangements could be used for other antenna configurations, to eliminate interference from nearby sources. The system uses synchronous pulses and timing to coordinate the transmission of energy pulses through the various antennas in the system.
The system also provides an indication to alert the customer when a responder has been detected, and that customer is authorized to begin refueling. The alert can be in the form of a light located on the spout, which turns on and off in response to various triggers, such as the detection or non-detection of a responder by an associated antenna, the removal or return of a nozzle associated with your seat, the selection of an alternative payment method (for example, cash or by credit / debit card), the recent detection and use of a responder at the service station, credit approval, or the denial of it.
A technical advantage of the present system is that it is easily integrated with the user interface of existing service station equipment.
Another advantage is that the customer is provided with flexibility for payment methods, without eliminating the options available with existing payment processing systems.
Another advantage is that it can be installed safely and without any obstruction in a service station.
Brief description of the drawings
The invention will be better understood with reference, by way of example, to the accompanying drawings, in which:
- fig. 1 is a schematic block diagram illustrating an overview of the service station equipped with one form of the customer identification system of the present invention;
- fig. 2 is a graph showing the transponder capacitor voltage versus time, for a transponder used with the system of FIG. 1;
- fig. 3A is a partial rear perspective view of a vehicle, illustrating placement of the vehicle-mounted transponder used with the system of FIG. 1;
- fig. 3B illustrates a manual transponder and a key fob with it, used with the system of FIG. 1;
- fig. 4A is a side view of the dispenser used with the system of FIG. 1;
- fig. 4B is an end view of the spout of FIG. 4A;
- fig. 5A is a side view of another embodiment of a dispenser used with the system of FIG. 1;
- fig. 5B is an end view of the spout of FIG. 5A;
- figs. 6A and 6B are schematic block diagrams illustrating the components of a dispenser for connection to a host computer used with the system of FIG. 1;
ES 2 239 342 T3
- fig. 7 is a schematic block diagram of the site wiring between the readers and the host computer of the system of FIG. 1;
- fig. 8 is a schematic representation of the gas station environment and dispenser arrangement, illustrating the reader synchronization strategy for the system of FIG. 1;
- figs. 9A to 9C are timing diagrams of the communication signals on the synchronization line between the main and slave readers of the system of FIG. 1;
- figs. 10A and 10B are detailed timing diagrams showing communications to and from the main reader of the system of FIG. 1;
- figs. 11Aa11Iy12 are action flow tables illustrating user performance of the system of FIG.
1;
- fig. 13 is a diagram illustrating the main logic program tasks and subsystems related to identifying a customer (IDC) for the transaction, of the system of FIG. 1;
- fig. 14 is a diagram illustrating the data flow of responder reader tasks for the system of FIG. 1;
- fig. 15 is a diagram illustrating the feedback at the state change interface for the system of FIG. 1;
- fig. 16 is a diagram illustrating authorization request and response handling for the system of FIG. 1;
- figs. 17A through 17N and 17Q are action flow tables illustrating the primitive customer identification tasks of the system of FIG. 1.
Detailed description of a preferred embodiment
In the appended claims it will be appreciated that all embodiments of the invention now described include a handheld transducer. They may also include a vehicle-mounted transducer, and the manual transponder works in override mode. Any of the following descriptions taken as an application to a system having only one vehicle-mounted transducer is outside the scope of the claims, but is included for the purpose of facilitating a full understanding of the background of the invention.
In fig. 1, the number 10 refers to a customer identification system (IDC) in which the characteristics of the present invention are embodied. The system 10 electronically identifies a customer, authorizes a transaction involving the acquisition of goods or services by said customer, and subsequently debits his account for the services. In one embodiment, the system 10 identifies, authorizes, and charges the customer's account for services provided at the service station. In general, the system 10 allows the customer to drive to a fuel dispenser, and immediately begins pumping that fuel (or has it pumped for him) without having to enter the service station building to pay for the fuel or have to insert a credit card into a card reader at the dispenser. As explained in detail below, the system 10 can also be used for other services at the station, such as washing the car or making payments inside a sundries store.
I - System overview
In one embodiment (fig. 1), the system 10 is implemented in the environment of a service station that includes two service islands 12, each one with two fuel nozzles or pumps 14, and it is understood that the number of islets and pumps and their geometry and relationship to each other may vary according to environmental requirements. Communication and synchronization lines, which are explained in detail below, connect the jets 14 with a base computer 16, to control the operation of said jets. An additional location 18, representing a car wash, food service, checkout box, or other entertainment venue, is also connected to the base computer 16. It is understood that each of the dispensers 14 includes a distribution area on each of the opposite sides of the dispenser, and that on each of said sides there is at least one fuel nozzle (not shown) and a terminal activated by the customer. (TAC) (shown in Figures 4A and 5A) to perform traditional supply functions, as well as those described in detail below. It is also understood that the computer 16 may be connected to a network (not shown) to perform functions including, but not limited to, checking the status of the customer's account.
Radio frequency customer identification (IDC-RF) readers 20 are included in each of the dispensers 14 and at location 18 (not shown here). Connected to each reader 20 and mounted on each fuel dispenser 14 are four antennas: two long-range 22A and 22B mounted on top of dispenser 14 (on each opposite side of it) to detect customer responders 23 mounted on the fuel dispenser. vehicle, and two other short-range 24A and 24B mounted within the head of dispenser 14, on each side of said dispenser, to detect hand-held responders
ES 2 239 342 T3 of the customer. As described in detail below, each reader 20 scans the four antennas 22A, 22B, 24A, 24B of each source 14, sends power pulses to the antennas, and reads the customer identification data (IDC) detected by the antennas from of the responders (eg, responders 23 or 25) detected by the antennas, and sends said data to the base computer 16. For example, it is contemplated that a vehicle 28 entering a distribution area in front of one of the jets 14 will include a transponder 23 mounted thereon, such that the long-range antenna 22B (as shown in FIG. 1) from the dispenser 14 closest to the vehicle will read the IDC data contained in the responder.
Responders 23, 25 are radio frequency identification cards (IDRF cards), which can be mounted in the customer's vehicle or held in the hand or on the key fob, like credit card type units. The responders 23, 25 contain customer identification data (IDC) that is radiated in response to the reception of a predetermined radio frequency (RF) wave (ie, a pulse of energy). The RF wave is sent by a reader 20 housed in one or more of the jets 14. The antennas 22A, 22B, 24A, 24B mounted on the jets 14 read the radiated data, and send it to the readers 20 for decoding and transmission. subsequent to the base computer 16, or also to a network in which said data can be verified, and the amount is charged to the customer's account when completing the fuel supply or other purchase.
Suitable responders 23, 25, antennas 22A, 22B, 24A, 24B, and readers 20, used in system 10, are available from Texas Instruments Incorporated of Dallas, Texas, as a TIRIS ™ (Texas Instruments Registration and Identification Systems) product line. ). Some of the products in the TIRIS ™ line are described in a brochure entitled "Texas Instruments Registration and Identification Systems", no. 22-27-008 (1994), which is incorporated herein by reference. Information on these components is advertising available from Texas Instruments Incorporated, and will allow those skilled in the art to make use of the system 10 following the description set forth herein to achieve the desired functionality.
In a preferred embodiment, the readers are low frequency and send periodic pulses of energy of approximately 134.2 kHz to antennas 22A, 22B, 24A, 24B, and receive signals of approximately 900 MHz. Other suitable parameters are also contemplated. Said readers correspond to the Series 2000 system, from Texas Instruments, Inc. of Dallas, Texas. Alternatively, the reader can be a high frequency reader. Long-range antennas are preferably gate antennas, such as model G03, G02, or G01, available from Texas Instruments, Inc. Long-range antennas can also be customary antennas that are tailored to the appearance of the dispenser 14. The short range antennas are preferably ferrite rods available from Texas Instruments, or alternatively they can be manufactured from a printed circuit board that includes a coil having an appropriate inductance.
Readers 20 send periodic pulses of low frequency energy, approximately 134.2 kHz, to antennas 22A, 22B, 24A, 24B. The antennas 22A, 22B, 24A, and 24B, in turn, direct the electromagnetic fields generated by the energy pulses to particular areas adjacent to the jets. An energy pulse lasts approximately 50 milliseconds (ms), and can be generated every 90 ms to 140 ms. When a transponder 23, 25 enters the electromagnetic field, energy is collected by an antenna (not shown) in the transponder, and is stored in a small capacitor (not shown). After completion of the energy pulse, the transponder 23, 25 transmits the customer identification data with the use of the energy stored in the capacitor. The antennas 22A, 22B, 24A, 24B mounted on the jets 14 read the data radiated from the transponder 23 or 25, and send it to the readers 20 for decoding and subsequent transmission to the base computer 16 or to a network, where said data they can be verified, and the customer is billed once the fuel supply or other purchases are completed.
Fig. 2 graphically illustrates the operation of a responder 23 or 25 in cooperation with a reader 20. In response to a reader 20 emitting a pulse of energy (typically occurring for 50 ms), the responder 23 or 25 (if within the scope) will be charged as indicated by increasing the voltage potential of its capacitor (not shown). Once loaded, the responder 23 or 25 then emits a response signal (lasting approximately 20 ms) with which its customer identification data is sent to the reader 20. In total, around 128 bits are transmitted, which are captured by the antenna (for example, one of the antennas 22A, 22B, 24A, 24B) of the reader 20 and then they are decoded. Once the data has been sent, the responder 23 or 25 continues to discharge its storage capacitor, thereby restoring said responder and is ready for the next read cycle. The period between the transmission pulses is known as the "sync time" and lasts approximately 20 ms, depending on the chosen criteria. The next energy pulse can be transmitted approximately 20 ms to 50 ms after responder 23 or 25 has completed data transmission. As discussed in detail below, the pulse sync time is used to coordinate the transmission of energy pulses through the various antennas 22A, 22B, 24A, 24B of system 10.
According to one embodiment of the invention, it is desirable to transmit the energy pulse at a low frequency, and to charge the capacitor in the transponders 23 and 25. Said transponders are designed to output the response signals at a higher frequency, such as frequency ultra high low.
Referring again to FIG. 1, it is understood that the illustration is not necessarily drawn to scale. In a typical filling station, the width of the jets 14 is approximately 1.22 m. Furthermore, the distance between jets 14 of a single island 12 is approximately 3.6 to 6 meters, and the distance between opposite jets
ES 2 239 342 T3 of adjacent islands 12 is approximately 8 meters. Each fuel dispenser 14 has two separate distribution areas, one on each side of the dispenser 14, in which the nozzles and registers are located. As previously mentioned, each distribution area also typically includes a customer-activated terminal ("TAC"), which uses it to make selections, such as payment type, and in which messages can be presented to said customer. . Other possible arrangements of the system 10 include environments with more than two service islands, not necessarily parallel to each other, or arrangements in which the islands form a circle, with rows of inner and outer islands.
With reference to fig. 3A, the vehicle-mounted transponder 23 may be mounted on the rear window 28 of said vehicle 26, preferably near the side of the vehicle where the fuel inlet and cap 30 is located. In fig. 3A, the vehicle-mounted transponder 23 is located approximately 5.1 cm from the top and edges of the side 34 of the rear window glass. Such a vehicle-mounted transponder 23 may be applied to the window 28 with adhesive coated VELCRO® pads. One chip is adhered to the transponder 23 and the other is adhered to the interior surface of the window 28 of the vehicle. Although said vehicle mounted transponder 23 has been described herein as located in the rear window 28 of said vehicle 26, other locations such as a side window may be suitable, depending on the particular arrangement of long range antennas 22a, 22B. In addition, other means may be used to mount the transponder on the vehicle.
Fig. 3B illustrates two variants of the manual transponder 25, which the customer can swing in front of one of the short range antennas 24A, 24B mounted on opposite sides of the dispenser. The manual responder 25 may be a key fob or chain unit 25A, or a credit card type unit 25B, or it may be shaped suitable for manual use. Variations in the shape and size of the responder 25 are contemplated.
Figs. 4A and 4B illustrate a mounting arrangement for the four antennas 22A, 22B, 24A, 24B on the spout 14. The two long-range antennas 22A, 22B are preferably mounted on the top 36 of the spout 14. A long-range antenna 22A or 22B extends outward from each side 38A or 38B of jet 14, such that the plane of the antenna is substantially perpendicular to side 38A or 38B of jet 14. The antennas 22A, 22B transmit equally well from either side of them, perpendicular to the plane of said antenna. Thus, the antennas 22A, 22B are aligned so that the electromagnetic field generated from one side of the antenna is directed toward the distribution area for a vehicle on the appropriate refueling side of the dispenser 14, and the electromagnetic field from the other side of the antenna is directed upward and away from the other side of the spout 14, as shown.
The upper portion 36 of the dispenser location provides the optimal performance for reading the transponders 23 mounted on the vehicle. This placement and orientation of the long-range antennas 22A, 22B also eliminates any problems associated with reading a transponder 23 mounted on a vehicle that is located on the opposite side of the dispenser 14. Furthermore, with this location and orientation, radio frequency waves are less likely to reach the refueling areas of adjacent service islands 12.
The short range antennas 24A, 24B of the credit card or key fob type transponder are preferably mounted within the head of the dispenser 14, behind the corresponding authorization lights 45A, 45B. These lights advise the customer that he is authorized to pump the fuel. A short range antenna 24A or 24B is located on either side 34A or 34B, respectively, of the jet 14, as shown in FIG. 4B. Antennas 24A, 24B are also located near opposite ends 46 of distributor 14, as shown in FIG. 4A. This location of the antennas 24A, 24B helps to avoid the reading of responders from the wrong side of the dispenser 14. In another embodiment, the clearance lights 45A, 45B may be located away from the dispenser 14, or at different locations on said dispenser.
Fig. 4A also shows the customer-activated terminal ("TAC") at dispenser 14. The TAC includes a display 50 on which messages can be presented to said customer, and a keyboard 55 that the customer can use to make various selections that they are discussed later.
Figs. 5A and 5B illustrate a possible second arrangement of the antennas in the jets. In this embodiment, the long-range antennas 22A ', 22B' are mounted on top of the spout 14 'and extend outwardly from the sides 38A', 38B 'of the spout 14' at an upward angle as shown in Fig. fig. 5B. Electromagnetic fields are directed from one side of the antenna towards the appropriate refueling area, and up and away from the other side. The short range antennas 24A ', 24B' of this embodiment are arranged similarly to the short range antennas of the first embodiment.
Responders 23 and 25 may be read-only (R / O) low-frequency IDRF cards, containing a 64-bit customer identification code, and available from Texas Instruments, Inc. For example, vehicle-mounted transponders can be low-frequency, available from the Texas Instruments Vehicle and Dispenser Series, and short-range transponders can be low-frequency, available from the Texas Instruments Nameplates and Cards Series. .
Alternatively, the responders 23, 25 may be low-frequency read / write (L / E) IDRF cards, with different range of memory capacities. Such L / E responders are available from Texas Ins8
ES 2 239 342 T3 truments Inc. One type of L / E responder commercially available from Texas Instruments Inc. is an "authenticated" responder. Said responder receives an identification request code from reader 20. Each responder has a unique algorithm contained within it. The responder receives the 40-bit code, processes it with the unique algorithm, and returns a 24-bit response to reader 20. Thus, reader 20 receives the responder's number and the 24-bit response. Reader 20 then sends home computer 16 the responder's number, identification code, and the response received from the responder. The base 16 computer searches a look-up table for the responder's number, identifies the responder's algorithm, passes the 40-bit code through that algorithm, and obtains a 24-bit response outside of its algorithm, which it then compares with the answer coming from the responder. If the answers match, it is a genuine responder.
Customer identification codes (IDCs) on L / E responders can be changed, or other business-related and / or security data can be added. For example, the number of times per day that a responder is used for a refueling transaction at a particular service station or location can be tracked and written to the responder 23, 25. This information can be used for various purposes, for example limiting the number of times a vehicle-mounted responder can be used in a day. In addition, personal preference information regarding shopping experience can be written on the responder. Similarly, the responder can be connectable via a suitable interface to a microprocessor, such as a vehicle on-board computer, so that in cooperation with the system 10, information can be written to the responder and then presented to the customer while refueling. (for example, fuel economy calculations, miles driven since last refueled, engine conditions, and the like).
The actual reading range or distance of antenna / transponder combinations depends on criteria such as transponder size and type, antenna size and type, transponder and antenna orientation, and electromagnetic noise. A combination of long-range antenna 22A or 22B mounted on top of dispenser 14, and a vehicle-mounted customer transponder 23, preferably provide a read range of up to approximately 2.1 m, measured from the read face. of the spout 14. A combination of short range antenna 24A, 24B located at the head of dispenser 14, and a key fob or credit card type customer transponder 25, preferably provides a 4 to 6 inch read range.
Table 1 below shows preferred read ranges for the vehicle mounted transponder and antenna combination, and the credit card or key fob transponder and antenna combination, in one embodiment.
TABLE 1
Range of scope (a)
Responder type -------------- Correct position Incorrect position
<td>Mounted on the vehicle</td><td>Depth (b) Minimum: 1.5 m Ideal: 2.1 m Width: 1.1 to 1.5 m Height (c): l, 0 to 1.5 m</td><td>45.7 cm</td>
<td>Keychain / credit card</td><td>Framed area up to 10.1 cm to 15.2 cm (d)</td><td>Reading not allowed</td>
(a) - Measured from the covered area (b) - Measured perpendicular to the side of the spout (c) - Measured from the base of the spout (d) - Measured perpendicular to the side of the spout
Fig. 6A is a schematic block diagram illustrating details of the hardware of a dispenser 14 of system 10. The two long-range antennas 22A, 22B (each designated "Top of dispenser antenna") are mounted on said upper part 36 (fig. 4A) of the spout 14, in a "safety area" 57. An antenna conduit assembly 60 extends through a "spout brackets" section 58 and a "spout hydraulics" section 59, to a "spout head safety area" 61, to connect the spouts. long range antennas 22A, 22B to a multiplexer 62 ("MUX"). The multiplexer 62 is housed in the security area 61 of the dispenser head, along with the reader 20. Said safety area 61 of the jet head is separated from the hydraulic section 59 by a vapor barrier 64.
ES 2 239 342 T3
Also housed in the safety area 61 of the dispenser head and coupled to the multiplexer 62 are short range antennas 24A and 24B (each designated a "keychain antenna"). Multiplexer 62 controls the transmission of energy pulses from antennas 22A, 22B, 24A, 24B. A synchronization ("synchro") line 66 provides the coordination commands to multiplexer 62 to transmit the energy pulses. A radio frequency ("RF") line 68 provides the low frequency FM energy pulses that are transmitted by antennas 22A, 22B, 24A, 24B.
The multiplexer 62 and the reader 20 are both coupled to the authorization lights 45A, 45B to control the activation of said lights. Reader 20 is coupled to base computer 16 (FIG. 1) via communication line 72 ("comm.") And to other readers 20 via synchronization line 74 ("synchro"). A power source 76 housed in the head of dispenser 14 provides power to reader 20, multiplexer 62, and authorization lights 45A, 45B. Power source 76 is also coupled to an outside power source via power line 78. A main line assembly 80 ("conj.") Supports and protects communication line 72, synchro line 74, and power line 78, leading to a main junction box 82 coupled to the power storage source and home computer 16.
Fig. 6B is a diagram illustrating the signal flow between the base computer 16, the distributor 14, and the antennas 22A, 22B, 24A, 24B, with connection to these through the multiplexer 62. Each reader 20 includes a microprocessor (not shown) and programming instructions (i.e., a logic program, not shown), to cause pulses of energy to be generated by antennas 22A, 24A, 22B, 24B through channels of multiplexer 62 that connect each antenna to the reader. To be properly synchronized, for the reasons discussed below, all readers 20 of system 10 must be cycled through the channels of multiplexer 62 to activate antennas 22A, 24A, 22B, 24B attached to it in a coordinated sequence. predefined. For example, in the illustrated embodiment, each reader 20 includes a multiplexer 62 with four channels, where each channel 1 to 4 is connected to a different antenna 1 to 4 (eg, antennas 22A, 24A, 22B, 24B). Synchronized operation, as discussed below, therefore requires that all readers 20 generate a load pulse on channels 1 through 4 at the same time. If one reader generates a load pulse on channel 1 while another reader 20 generates a load pulse on channel 3, or if each of the readers 20 actuated to generate pulses on any of the channels independently of the other readers, then these readers will not be synchronized. To keep all readers 20 in sync, synchro line 74 (Figs. 6A and 7) connected to each of readers 20 instructs multiplexer 62 in each reader (via synchro line 66) when to generate a load impulse and which channel is to generate it.
Fig. 6B further illustrates the communication between the payment terminal and pump control circuit 15, and the base computer 16. The payment terminal can be a customer activated terminal (TAC) and the pump control circuit responds to the instructions from the base computer 15 and the payment terminal, to supply fuel from the pump 14. The payment terminal and the pump control circuit are conventional and therefore not described in detail here.
Fig. 7 also illustrates the site wiring for system 10, showing communications line 72 and synchro line 74 connections between multiple readers 20. Timing signals for coordination of the transmission of energy pulses from readers 20 (designated 1, 2, 3, and N) are carried by sync line 74. The coordination of the transmission of the energy pulses from the various readers 20 is discussed below. Any number of readers 20 is contemplated. Although not illustrated, it is understood that each reader 20 includes a radio frequency module and a control module. The radio frequency module generates the energy pulses and receives the radiated data from the transponders 23, 25. The control module has a microprocessor that decodes and processes the data of the responder and that communicates with the base computer 16.
Preferably, the readers 20 are interconnected over an RS-485 loop, to provide synchronization of the transmit / receive cycle. This link ensures that all jet locations 14 are activated as antenna positions, to minimize interference with each other, as described below. Although not shown, the RS232 to 485 converters interface the base computer 16 with the readers 20.
II - Synchronization of readers
Figs. 8-10 illustrate details concerning the synchronization of readers 20 within system 10 to avoid crosstalk between responders 23, which could result in an erroneous billing to a customer for services never received.
In fig. 8 shows a simplified schematic of system 10 in which jets 14 are designated as pumps 1 to 4, and have corresponding readers 20-1 to 20-4, each with antennas A and B on opposite sides of the bomb. To illustrate the problem of crosstalk, the readers of pumps 1 and 3 are not synchronized, thus demonstrating the potential for crosstalk caused by a transponder X being loaded by one of the readers when said transponder X is located between the pumps. . In contrast, the readers for pumps 2 and 4 are synchronized, thus solving the problem of crosstalk for a Y-responder located between the pumps.
Pumps 1 and 3 send energy pulses from antennas B and A, respectively, thus giving rise to the possibility that one or both of them will charge responder X, even if said responder is closer.
ES 2 239 342 T3 to pump 1. Each of the antennas B and A emitting energy pulses generates an energy field extending from the antenna, as represented by the lines in the figure. The energy field in front of each antenna includes a "near field" zone, a "far field" zone, and a "transition zone" between them (not shown). There are no sharp dividing lines between the three zones, and some arbitrary limits are set for each zone based on how the energy diffuses as the distance from the antenna increases. In one example, the near field zone extends generally outside the antenna to a distance of! D<sup>2</sup>/ A λ = A / 2 λ, where D = antenna diameter, A = antenna aperture area, and λ = wavelength. The distance of the far field zone is approximately five times the length of the near field zone, and occurs at a distance of approximately 2D / 22. The transition zone is the zone between them. As shown in fig. 8, there is the possibility of overlapping of the transition zones or remote field zones of antennas B and A for pumps 1 and 3, when the antennas emit energy pulses simultaneously.
Observing the energy pulses emitted from pumps 1 and 3, it is most likely that transponder X is loaded by antenna B of pump 1, since the transponder is relatively far from pump 3; however, it may end up being loaded by the overlap of the pulses from both pumps 1 and 3, even in a situation where the transponder is too far from either pump to be loaded by antenna B or antenna A only. This can occur when the energy at the overlap of the transition zones or field zones far from the antennas, due to their combined strength, is sufficiently high. Once the energy pulses have been completed, if the responder X receives sufficient energy, it will transmit its data in response to those pulses. Although the pump is closed for responder X, it is possible that pump 3 will also receive the response, resulting in crosstalk. An even worse situation could arise if two responders were in the center band between pumps 1 and 2, and pumps 1 and 3 received responses from the wrong responders, resulting in one customer being charged for services rendered to another.
Pumps 2 and 4 send pulses of energy 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 will not be charged by pump 2 since the energy pulse from pump 2 is not in the direction towards the responder. Transponder Y will be charged only when it receives a pulse of energy from antenna B of the pump (which will then be the only antenna that receives a response). Such a synchronized system provides better separation and higher confidence that the correct response comes from the correct responder 23.
Thus, the synchronization of the system 10 takes place when the readers 20 selectively send pulses of energy so that all antennas facing each other in the same general direction (for example, all antennas facing north, south, towards east, or west) send a pulse at the same time, and all antennas facing each other in different directions do not send pulses at that time. This synchronization is performed by readers 20, which transmit pulses from facing antennas in one direction (eg, antennas A) during the synchro time. (see fig. 2) of the transmit / receive cycle of the antennas facing each other in a different direction (for example, antennas B).
Other timing arrangements are possible, depending on the number of pumps and their relationship to each other. In one embodiment, synchronization does not necessarily have to occur for all antennas, but will occur only in the case of antennas for ranges facing each other, where the energy fields in front of the antennas may possibly overlap. .
Referring also to FIG. 1, a synchronization strategy that prevents energy fields from different antennas from overlapping, is achieved when each reader 20 produces pulses from antennas 22A at the same time, followed by pulses from antennas 24A also at the same time, followed by antennas 22B at the same time, and by antennas 24A at the same time. The aforementioned successive sets of antennas are made pulsating during the sync time (or after), followed by the data transmission cycle of the transponders loaded by the preceding set of antennas. In the strategy just described, the antennas for car-mounted responders 23 and for manual responders 25 alternate in their production of pulses, with pulses produced on only one side of each island 12 at a time, so that the Vehicle located between islands is not subject to receiving impulses from opposite directions caused by overlapping energy fields. In this case, each antenna “A” (antennas 22A or 24A) (facing west, seen in the drawing) sends a pulse during the synchro time of the transmission / reception cycle of the antenna “B” pulsing previously (antennas 22B or 24B) (facing east, seen in the drawing), and vice versa. This represents an antenna pulse sequence of: 22A, 24A, 22B. 24B. Alternative sequences include: 22A, 22B. 24A, 24B. Any other combination of these is appropriate as long as antennas "A" and antennas "B" are not loaded in the same cycle.
With reference to figs. 9A to 9C and also to FIGS. 6A, 6B, and 7 discussed above, the operation of the readers 20 will now be described in detail with respect to an implementation of one or more of the aforementioned strategies.
As already indicated in fig. 6B, each reader 20 includes a microprocessor (not shown) and programming instructions (i.e., a logic program, not shown) to cause pulses of energy to be generated by antennas 22A, 24A, 22B, 24B across channels of multiplexer 62 that connect each antenna to a reader. For example, the Texas Instruments TIRIS ™ 2000 Series Reader is available with a standard logic program known as S2000. The S2000 program includes programming instructions to control pulse output
ES 2 239 342 T3 of energy, to receive and process the data coming from the responders 23, 25, and to communicate with the base computer. This logic program can be easily adapted for the presence of four antennas 22A, 22B, 24A, 24B.
To be properly synchronized, all readers 20 in the system (FIG. 7) must be cycled through the channels of multiplexer 62 in synchronization. Synchronized operation requires that all readers 20 generate a load pulse at the same time on channel 1, channel 2, channel 3, and channel 4. It is understood that the specific synchronization strategy can be determined in base which antenna 22A, 22B, 24A, 24B is connected to which channel 1 to 4. Synchronization conduit 74 connected to each of the readers 20 instructs multiplexer 62 in each reader (via synchronization line 6) when to generate a load pulse and on which channel to generate it for synchronization purposes. .
The figs. 7 and 9A illustrate how each reader 20 is instructed on synchro line 74 to generate appropriately timed read / load cycles. One of the readers 20 is designated as "master", and the rest are designated as "slaves". Main reader 20 generates a sync pulse (represented by synchro timing line 900) on sync line 74, which inversely follows its load / read cycle (represented by main timing line 902, in which a A "high" signal is for load, and a "low" signal is for reading Slave readers 20 use the synchro pulse to set their load / read timing (represented by slave timing line 903). Assuming that the load pulse is set at 50 ms, and that the transponder reading is approximately 20 to 25 ms, there will be no reason for variations. However, as illustrated, the slave timing line 904 may result in a variation from the sync pulse, due to the message handling that occurs at the slave reader 20. This has the unfortunate effect of changing the timing of the slave reader processor 20 by lengthening the time it remains low. Therefore, the timing can be adversely affected as a function of the load on the individual reader 20, causing a reader to "lose the information" of a load / read cycle if it is unable to complete its processing in time to capture the signal. synchro.
Fig. 9B illustrates the effect of slave reader 20 temporarily losing synchronization information with main reader 20 (main line 902) due to delay in processing the message at the slave reader. Once the processing of the message is completed in the slave reader 20, it is again synchronized with the synchro signal (synchro line 900); however, the slave reader remains out of antenna sync because the master reader 20 is loading an antenna on a different channel (for example, the master reader is loading antenna channel 0, while the slave is loading channel 4 antenna). Thus, the channels of multiplexer 62 loaded on all readers 20 are no longer the same channels at the same time.
Fig. 9C illustrates a solution that corrects the timing of a slave reader 20, when it loses timing information during message processing. The solution is to use synchro line 74 to communicate downstream of slave readers 20 which channel (ie which antenna) is to be used in the next load cycle. Alternatively, communication line 72 can be used by base computer 16 to instruct readers 20 which channel to use. However, a disadvantage of the latter method is that in some implementations, the processing time of the base computer 16 is required for more important tasks.
As shown in fig. 9C, the use of the synchro line 74 to communicate the channel number to each of the slave readers 20 is done by encoding said channel number on the synchro line. In this way, the processor in all readers knows which antenna has to be loaded, even if they lose a load cycle. As shown by synchro timing line 900, a variable length pulse 908 indicates to slave readers 20 which channel to use for the read cycle. The synchro line signal includes an initial bit 906 of 200 microseconds, and then a variable width pulse 908 is transmitted. The pulse length 908 indicates which channel of multiplexer 62 is to be used. A pulse of approximately 1 to 100 microseconds indicates channel 1, 101 to 200 microseconds indicates channel 2, and so on.
The interrupts in the readers 20 are enabled until the initial bit 906 is detected. At that point in the series the interrupts are disabled, and remain so until the measurement of the variable length of the synchronous pulse 908 of the multiplexer is completed, and then these interrupts are enabled again. Interrupts are disabled for a maximum of approximately 600 microseconds. Reader 20 will not lose any of the incoming serial data, because a character cannot be fully received in 600 microseconds. Any character that is fully received when interrupts are disabled is passed to an integral register, and the next character is partially received in the shift register.
It will be appreciated that reliance on hardware for intermediate characters allows the reader to avoid an overflow of a universal asynchronous receiver transmitter (UART), which, as explained in detail below, is implemented in the reader's logic program. in accordance with the present invention.
The aforementioned reader synchronization follows the basic concept that all slave readers wait until the synchronous line is lowered. However, the slave reader must be able to distinguish between a low value, which precedes the multiplexer pulse 908, and a low value that indicates that a load cycle 910 (power pulse) is occurring. This is done by timing the low value, and knowing that if it exceeds 200 //.s, the reader is in the middle of a load pulse. In the case where the synchro line 900 is high there is no confusion, since the slave reader will continue to wait for a transition from high to low.
ES 2 239 342 T3
In the case where the synchro line is low, as in the initial bit 906, it can be determined whether the low value precedes a pulse 908 from the multiplexer, or is a load cycle 910 by measuring the amount of time in which the synchro line remains low. If that line remains low for more than 200 pm (± 10%), then it is not actually preceding a pulse from the multiplexer, but rather a load cycle 910, in which case the interrupts are cleared and tracking of the initial bit is resumed. .
It will also be appreciated that the processing routines are written so that the processing of the message does not occur in such a way as to disorderly delay the main reader 20. Such delay of the main reader 20 is to be avoided as this would delay the entire delivery system. readers 20.
A pseudo-code written for storage and processing in the main and slave readers 20, which implements the synchronization of the channels of the multiplexer 52, can be expressed as follows:
Synchronization pseudocode (slave reader)
Start:
start timer when synchro line is high wait if timer disconnects, go to start // check if this is 200ps low value. If not, we were not synchronized start the timer when the sync line is low wait if the timer had disconnected go to start // correct, we are synchronized. Timing the pulse to determine the multiplex channel disable interrupts start the timer when the line sync. high wait to enable interrupts if the timer is zero go to start if the timer is greater than 310 ms select antenna 3 or if the timer is greater than 210 ms select antenna 2 or if the timer is greater than 110 ms select antenna antenna 1 or if the timer is longer than 10 ms select antenna 0
Synchronization pseudocode (main reader)
Start:
ES 2 239 342 T3 // make sure that the synchro line is high for a time that the slave appreciates force the synchro line to go high set the timer for 15 ms when the timer has not finished waiting // go low 200 ps so that the slave appreciates it // this is the start of the multiplexer sync timing force the synchro line to go low disable interrupts loop approximately 200 ps // create the width pulse variable force synchro line to go high if antenna number = 0 loop for 75 ps if antenna number = 1 loop for 175 ps or if antenna number = 2 loop for 275 ps or if antenna number = 3 loop for 375 ps enable interrupts force synchro line to go low (all readers should now start their power / load cycle End of sync pseudocode // this code should be called after have read the responder // and enabled the serial interruptions End of multiplexer synchronization force the synchro line to go high
Reference is made to "Appendix A" for a slave reader line protocol 20, which may be used in one embodiment of system 10 to implement the synchronization functions described above.
III - Base computer communications
With reference to fig. 7, communications on line 72 between the readers 20 and the base computer 16 of the present embodiment are limited because the readers are unable to reliably communicate with the base computer during the read cycle, that is, when the reader is receiving information from responders 23, 25. This problem is due, in part, to a lack of hardware resources available in commercially available readers 20 (ie, the 2000 series of TIRIS ™ readers available from Texas Instruments Inc. of said TIRIS ™ product line).
ES 2 239 342 T3
For example, the TIRIS ™ Series 2000 Reader 20 lacks a Universal Asynchronous Transceiver (UART) to transmit / receive data from the responder. With the current TIRIS ™ Series 2000 reader logic program, there can be 100% communications with the base computer (with occasional altered transponder readings) or 100% transponder reads (with imperfections in computer communications base), but not 100% communications with the base computer and 100% reads from the responder. Accordingly, the present embodiment implements a UART in the reader's logic program (not shown) that is stored and executed within said reader 20. The program originates communications between the base computer 16 and the readers 20 only when reader 20 is used in a charge cycle. See fig. 2, which illustrates the load cycle (“Power Pulse”) lasting approximately 50 ms, and the read cycle (“Data Read”) which lasts approximately 20 ms. During the load cycle, the processor (not shown) in the reader is available for communications on line 72 of them, while waiting for a 50 ms timeout to manifest. Subsequently, once the reader has finished loading the responder 23, 25, it will attempt to read the information from that responder. To do this, serial interrupts must be disabled for at least 20 to 25 ms. The timer is embodied in the physical equipment, and therefore is not affected by serial interruptions. However, this will not be a good time for communications with the base computer 16 to occur because the transponder reading or communications with said base computer will be unintelligible due to said interruptions.
In accordance with the present invention, the program within the reader 20 implements the UART (Universal Asynchronous Transceiver) function through the use of the synchro line 74, to ensure that the base computer 16 does not communicate with the reader 20 when it is reading the data from the responder (and interrupts are disabled). In particular, the UART function is implemented allowing only the base computer 16 to communicate with the reader 20 on the communication line 72, when the synchro line 74 is low, and adjusts the logic of the synchro line so that a Low synchro line is a reliable indicator of when charging is occurring. When synchro line 74 goes from high to low (see fig. 9a where the synchro timing line 900 moves from a high position 1 to a low position 2) the reader load cycle begins. The synchro line remains low during charging, and the logic program according to the invention then instructs the synchro line to go from low to high at the end of the charge cycle (see Fig. 9A, in which line 900 of synchro timing goes from low position 3 to high position 4). Therefore, the synchro line is low only when the charging cycle is occurring. Following the rule that the base computer 16 can communicate only on the communication line 72 with the readers 20, when the synchro line 74 is low, it is ensured that there will never be the case that information is sent during the read cycle. , when interrupts are disabled.
In the base computer 16, the free to send (CTS) line (not shown) on the RS-232 ports regulates the flow of data to and from the readers 20 depending on whether the line is high or low. The synchro line 74 is thus connected to the CTS line through an RS-485 to another RS-232 converter, to prevent the base computer 16 from sending data when the reader 20 is unable to process it.
Appendix B describes a communications protocol between the logic program within readers 20 and the base computer 16, for an embodiment where said base computer is a Wayne Plus system, for example, a Wayne Plus base computer / 2 or Wayne Plus / 3 available from Wayne Division, Dresser Industries, Inc. of Austin, Texas, and the reader logic program is a modified version of the TIRIS ™ S2000 reader program, available from Texas Instruments Inc.
Figs. 10A and 10B are timing diagrams 1002, 1004 illustrating the timing of communications between base computer 16 and readers 20, for typical communications to and from a reader working with the program in accordance with the present invention. In fig. 10A, diagram 1002 represents the timing for a reader without responders 23 or 25, within range of any of its antennas 22A, 22B, 24A, 24B. In fig. 10B, diagram 1004 represents the timing for a reader 20 with responders 23 or 25 on all of its four 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 system 10.
In both diagrams 1002,1004, an RCV signal 1006 shows the timing of the data received by the reader 20 from the base computer 16. An XMT signal 1008 shows the timing of the data sent by the reader to the base computer 16. A Sync signal 1010 shows the timing of the data from synchro line 74, which keeps all readers 20 and base computer 16 in sync. It is also linked to the base 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 reader program 20, for debugging and diagnostic purposes. Reference points A through I illustrate events in signal timing for purposes of explanation of the diagrams below. All timing diagrams, figs. 10A and 10B, were generated by a Tektronics Prism Logic analyzer.
In fig. 10A, diagram 1002 (illustrating the case of a reader 20 without responders 23, 25 in range) is generated by using the command "achieve a scan log with variable length antenna" (described later in the Appendix C).
ES 2 239 342 T3
AD - Multiplex responder / synchro charge
The synchro signal 1010 is referenced between points A and D. Before setting the synchro line 74 low, the main reader (fig. 7) outputs the multiplex-sync pulse 908 (fig. 9C) that tells the slave readers 20 (that is, to their processors) which antenna to use for loading. When this pulse completes, line 74 goes low, line 74 goes high, and all readers output a load pulse on the correct antenna until main reader 20 raises line 74 to high.
The processor of each slave reader 20 searches for synchro line 74 for the multiplexer synchro pulse, which informs all slave reader processors 20 which multiplexer channel (i.e. antenna) is to be used for the next load cycle. reading.
The processor of each slave reader 20 looks for a change in the synchro line (from high to low). Then measure that impulse (the initial impulse) which must be within a range of approximately 200 ps (which is why it does not appear in diagram 1002). Immediately thereafter, the interrupts are disabled, so that the reader 20 can determine the length of the next low pulse (75 ps to 375 ps). This determines which antenna should be used (a pulse of 0 to 99 ps indicates antenna 1, 100 to 199 ps indicates antenna 2, etc. as explained with reference to Fig. 9C.
Once the correct antenna is determined, it is connected and a TIRIS ™ reader program function is called which starts the loading of the transponder 23 or 25. This basically consists of setting an external flag to allow the analog section of the reader 20 to start the signal. transmission. This function is repeated until the timing is complete.
BC - Central Transmission
The RCV signal 1006 is referenced between points B and C, which illustrates the dual nature of synchro line 74. Since reader processor 20 is essentially idle during AD time, synchro line 74 indicates to the computer base 16 that it can send data to reader 20, as indicated by the reception signal in BC. At this point, the reader is executing the TIRIS ™ reader program function code "write_sequence ()" and is unable to process any messages received from the host computer up to point E.
D - Beginning of responder's reading
Synchro signal 1010 is referenced at point D. Both master and slave readers 20 exit the "write_sequence ()" function after 50 to 52 milliseconds. At point D, main reader 20 raises synchro line 74 to prevent base computer 20 from sending any other data. It may be the case that a character has been loaded into the uArt shift register of base computer 16 and it is too late to stop transmission. To avoid losing this character, main reader 20 raises synchro line 74 prematurely for 5 milliseconds. This gives the reader 20 sufficient time to pick up the characters sent by the base computer 20. After the five milliseconds have elapsed, the serial interrupts are disabled and another function of the TIRIS ™ reader program is called to read the transponder 23, 25 (resulting in an implementation of the program's UART function, as described above. previously described).
DE - responder reading
Signal REF 1012 is referenced between points D and E. The reading of a responder 23, 25 by reader 20 occurs in approximately 20 to 23 ms (note that DE includes the aforementioned 5 milliseconds of delay). During this time, all interrupts are disabled, and there can be no communication to or from the base computer 20.
E - Start of message processing
The REF 1012 signal is referenced at point E. This is where the reader 20 actually achieves a chance to handle the message received in BC from the base computer 16. In this example, 77.608650 ms are taken from when the Base computer 16 begins sending the message until reader 20 finally begins to process said message.
EF - Message handling
The signal REF 1012 is referenced between points E and F. During the message processing, the reader 20 determines what the base computer 20 requests, acts on this request, and forms the buffers required for a response. . The treatment varies depending on the type of message as well as its size.
F - Beginning of response
The XMT signal 1008 is referenced at point F, where reader 20 begins data transmission to home computer 16.
ES 2 239 342 T3
FG - Treatment completed
Signal REF 1012 is referenced between points F and G. This is the time taken to do all the work necessary to store a packet in the serial output buffer.
FH - Transmission of the response by the reader
The XMT signal 1008 is referenced between points F and H. The data, which has been loaded into an output queue, is sent via serial interrupts from reader 20 to base computer 16. Readers 20, to Unlike the base computer 16, they are not limited by the rule of "transmit only when synchro line is high" and can transmit at any time. This is desirable because in the worst case (as described later in diagram 1004), the message lasts approximately 47.9 ms, and the load time is approximately 51.5 ms. This leaves approximately 3.5 ms, which is too short a time for the base computer 16 to send another request (ideally one response and one request per cycle). The more octets the reader 20 transmits during a low sync signal, the less it must send when the sync line 74 goes high. This allows the base computer 16 to communicate more efficiently with the reader 20.
Point G is where reader 20 has completed the response to a message, and is ready to search for the next multiplex-sync pulse. Point H is the end of the response from reader 20. Point I is the beginning of the next pulse. multiplex-synchro
In fig. 10B, diagram 1004 (illustrating the case of a reader 20 with transponders 23, 25 in range and detected by all antennas) is generated by using the command "achieve an exploratory record with variable length antenna" (which described below in Appendix C).
The description of diagram 1004 is substantially the same as the previous one for diagram 1002, with the differences in timing of events appreciated by reference to FIG. 10B. At the reference point E, the reader 20 manages to process the message received in BC from the base computer 16. In this example, the time from point B to point E is 79.109765 ms. At the reference point H, the beginning of the next multiplex-sync pulse is indicated. The timing shown requires that the reader 20 detect the start bit of the multiplex-sync data while sending the data to the base computer 16. This requires that the serial output routine be faster than the start bit of multiplex-sync, and that the multiplex-sync pulse is short enough not to influence overall timing.
Point 1 is the end of reader 20's response. Since reader 20 begins transmission approximately 21.3 ms before synchro line 74 goes high (synchro signal 1010), base computer 16 has a time enough (20 to 25 ms) to send another request. Since an average request is approximately 8 to 12 ms (depending on the number of DLE characters inserted), there is enough time.
Other details regarding the communications between the base computer 16 and the readers 20 are contained in the documentation available from Texas Instrument Inc. for its TIRIS product line.<sup>TM</sup>, for example, "TIRIS: 2000 Series Reader System Reference Manual", Texas Instruments, (# RI-ACC-D01A), incorporated herein by reference.
Appendix C is a description of certain features and enhancements made to the software of readers 20, specifically for the implementation of the system supported in this specification.
IV. System operation and user interface
1.0 System overview
The following is an overview of the Customer Identification System (IDC) operation and user interface. A more detailed description of the operation and the user-client interface is described in detail below with reference to Figs. 11A to 11I, 12 to 16, 17A to 17N, and 17Q. It is understood that the operation of the system 10 is controlled by the programming instructions executed by the base computer 16 and by the program of the reader 20 described above. System 10 is integrated into a suitable fuel dispensing system, which in one embodiment may be Wayne Plus / 2 or Wayne Plus / 3, available from Wayne Division, Dresser Industries, Inc. of Austin, Texas, although other systems are contemplated. refueling and logic programs. System 10 may be integrated, for example, into the Nucleus control system, also available from Wayne Division, Dresser Industries, Inc. The aforementioned commercially available intelligent distribution systems or other commercially available distribution arrangements, in cooperation with IDC system 10 of the present invention, integrate pump control, cash register, card processing and customer identification, in a complete and operational system for a service station environment.
When a customer enters a service station with a transponder 23, 25 is detected at a fuel dispenser 14, and the corresponding authorization light 45A or 45B or another "in range" indicator is connected, as explained in more detail. forward, informing the client that the responder is within reading distance. After the jet has been activated, for example by lifting the nozzle or lever of said jet, or by
ES 2 239 342 T3 start to refuel, the system 10 sends to the computer network an authorization request containing the IDC data of the responder. However, before refueling, the customer can press a cancel key on the customer-activated terminal (TAC) or select a different payment method, in order to eliminate the use of the responder's IDC code for the payment of the transaction.
If a responder is read for the first time at a dispenser where the mouthpiece has already been removed, the dispenser will not be authorized to use the responder's IDC code for a sale. For example, if a first customer removes the nozzle on a pump, and a second customer's responder is subsequently read by the reader on that pump, the sale will not be charged to the second customer's responder's IDC account.
1.1 Overview of actions with vehicle-mounted responders
When a customer with a vehicle-mounted transponder 23 passes through a dispenser 14, the IDC data is read from transponder 23 by the long-range antenna 22A or 22B facing the vehicle. After reading said IDC data, the authorization light 45A or 45B on the side closest to the vehicle and corresponding to the long-range antenna turns on. If the customer continues driving and passes the dispenser without refueling, said light will remain on until the transponder 23 mounted on the vehicle goes out of the reading range of that pump. Preferably, the light 45A or 45B is turned off after a programmable number of blank readings have been made, when the transponder 23 exits the pump's read field. Accordingly, when the vehicle passes the pumps 14 without refueling, the corresponding authorization lights of the distributors turn on while said vehicle is within the reading field, and they turn off when the car leaves said field.
If the customer chooses to use a vehicle mounted responder 23 to pay for a transaction, they can verify that the authorization light 45A or 45B has come on by stopping the vehicle at the dispenser. When the customer lifts the nozzle from the dispenser (or begins refueling), the dispenser is "authorized" and a request for IDC account authorization is sent through the base computer 16 to a charge-account network. Preferably, the authorization light 45A or 45B remains on during the transaction. As the customer returns the nozzle to its place, the sale is finalized by the base computer 16, and a receipt can be printed on the TAC (terminal activated by the customer). After the sale is completed, the authorization light 45 a or 45B turns off and remains so as long as the transponder is continuously read by the antenna. An "empty" or blank responder read (or a predetermined number of such reads) produced after the sale is complete resets the system to allow subsequent responder reads, which will turn on the authorization light. Alternatively, the authorization light 45A or 45B remains on after the transaction is complete, until the customer's vehicle exits the read field.
Once the sale or transaction is completed at a dispenser using a vehicle-mounted responder 23, said responder preferably cannot be used at another dispenser for a predetermined time interval. However, it is understood that a vehicle-mounted responder 23 may be used at more than one dispenser at the same time, if a sale has not been completed at one dispenser before the responder 23 is used at another dispenser. Furthermore, it is understood that the system can be programmed so that although a vehicle-mounted responder 23 has recently been used to complete a sale at a pump, said responder could still be used for a different service, eg car wash. or driving to the window of a sundries store.
1.2 Overview of actions with manual responders
If the customer has a manual responder 25, of a type such as a key fob or credit card, he must present it and move it to the short range antenna 24A, 24B located in the authorization light (see FIGS. 4A and 5A). The short range antenna 24A, 24B reads the IDC data from the transponder, thus lighting the corresponding authorization light.
An account IDC authorization request is sent to the network through the base computer 16, when the customer lifts the nozzle (or begins to refuel). When the customer places the nozzle back in place, the authorization light turns off, the sale is finalized, and a receipt can be printed on the TAC. Preferably, the handheld responders 25 can work in more than one customer activated terminal (TAC) (be it a dispenser, car wash, or sundries store area). In other words, manual responders 25 may work on a particular TAC, although they are currently used as a payment method for a transaction on another TAC.
1.3 Overview of the authorization light operation
When the identification of a customer (IDC) is read at a dispenser 14 in which a refueling operation is not yet being performed, the authorization light 45A, 45B turns on.
When IDC data from a passing vehicle-mounted responder 23 is read at dispenser 14, the authorization light 45A, 45B at that dispenser illuminates and remains so until the responder is out of read range. As the vehicle passes the first dispenser and continues to read range of a second dispenser, the IDC data is read at that second dispenser, and the authorization light for the second dispenser turns on.
ES 2 239 342 T3
For transactions with a vehicle-mounted responder 23, the authorization light 45A, 45B turns off when the nozzle is snapped back into place at the end of the sale, or alternatively remains on until the vehicle-mounted responder is out of range. reading. If the manual responder 25 is used, the authorization light turns off when the mouthpiece is put in place at the end of the sale.
If a customer circumvents the transaction through the IDC and selects a different payment method, the authorization light 45A, 45B turns off.
Once the refueling operation is finished and the nozzle is returned to its place, the system 10 can be programmed to prevent an authorization light from turning on at any other pump (or alternatively at any other place) of the service station for a period of time. Default by IDC responder 23, 25 which has been used for recently completed refuel transactions. Therefore, the vehicle can leave the station without any other authorization light coming on.
1.4 Customer cancellation
A customer can override the use of the responder 23, 25 for a transaction by pressing the cancel key on the customer-activated terminal (TAC), as long as the dispenser 14 has not been activated (for example, the nozzle has not been lifted) or the refueling action has not started. A question such as “Cancel the use of the IDC system? (Y / N) ”is displayed on the TAC of dispenser 14 by pressing the cancel key. The customer can verify the cancellation of the transaction by IDC by pressing the "Yes" key on the TAC. If the "No" key is selected at that time, the sale will continue as an IDC transaction, that is, a transaction in which the IDC code is used to debit the account. The customer can also cancel the transaction with IDC before refueling by inserting a credit card, or by selecting another type of payment, such as cash. When the customer voids a transaction with IDC, the light 45A, 45B turns off.
Once a transaction or sale using IDC is in the refueling phase, a different payment method cannot be selected at the pump 14, nor can that transaction be canceled with IDC.
1.5 Authorization denied or time expired
If an authorization is denied, that is, the IDC code has been sent to the network and it returns a signal indicating that the authorization to use the system 10 is denied, that is, the IDC code for payment, the transaction is treated as a denied pre-authorization sale. The pump 14 is stopped and the customer is informed to contact the inside clerk for payment. If a vehicle mounted transponder 23 is used, the authorization light goes out and remains so until the nozzle is snapped back into place. Likewise, if an authorization response is not received from the network for a sale with IDC within a predetermined period of time (eg, 60 seconds), the sale will be treated as authorization denied.
1.6 Network communication problems
If the computer network is down when a customer lifts the nozzle on a dispenser 14 that has the authorization light on, the dispenser will not start. Rather, the TAC viewer notifies the customer that the network is down and prompts them to cancel the transaction with the IDC before selecting another payment method. When the customer finishes refueling but the sale cannot be paid through the IDC system due to network problems, such a “sale” is considered an unpaid TAC sale, and can be recorded and saved for information purposes.
2.0 Customer Identification Operation (IDC) and User Interface Action Flow Tables
Figs. 11A and 11I and FIG. 12 are action flow tables that describe the procedures that occur when a customer uses the system 10 in the case of the vehicle-mounted responder 23, and in the case of the manual responder 25, respectively.
Figs. 13-16 are action flow diagrams illustrating the relationships between tasks and subsystems related to customer transactions.
Figs. 17A to 17N and 17Q are action flow tables that describe the procedures executed by the primitive CID, that is, the routine of the program written to handle the execution of the customer identification functions.
2.1 Vehicle-mounted responder case
Figs. 11A and 11B show an action table 1100 illustrating the operation of the system 10 in a case corresponding to a transponder 23 mounted on a vehicle. In step 1104, a vehicle approaches a pump, that is, a refueling area within the vicinity of the service station. At step 1106 a determination is made as to whether the responder 23 is within range of the pump. As discussed above with reference to Figs. 1 and 8, this determination requires that a reader 20 receive data from the vehicle-mounted transponder 23, after said transponder is first loaded by the antenna 22A or 22b. If the approaching vehicle has no transponder 23 mounted on it, that is, there is no transponder 23 mounted on the vehicle
ES 2 239 342 T3 within scope, then the system 10 continues with the normal treatment of the customer, operation 1110, in which the payment is not made with the use of the IDC code, In the normal treatment of the customer, the customer performs the payment with the use of a traditional method, such as inserting a credit / debit card in the terminal activated by the client (TAC), or by direct payment to the station employee. In such a case, the TAC may present payment instructions, such as "insert credit / debit card or pay clerk," followed by refueling instructions such as "lift the nozzle."
If the vehicle-mounted responder 23 is in range, then in step 1108 the IDC system 10 determines if the detected IDC has been used recently (eg, in the last five to ten minutes) to complete a sale at another dealer. from the service station. If so, system 10 defaults to traditional customer treatment as indicated in step 1110, and the corresponding authorization light will not be lit (see step 1112, below). The customer will be required to select another form of payment, and the transaction will be processed without the use of the IDC code. This helps prevent fraud and avoids the feeling of unease that a customer might have when leaving with a car from a bomb after a sale is completed just to see that as they pass through successive pumps the light comes on when activated. The customer is given ample time after refueling to leave the service area without activating the clearance lights on any of the other pumps. As an option, the default step to traditional customer treatment can be eliminated when it is not objectionable to see other pumps “on” after the sale is completed on a different pump.
At step 1108, if the responder 23 has not recently been used to complete a sale, at step 1112 it provides the pump with a "customer in range" indication. In one embodiment, when the transponder 23 is within range of the refueling area of the pump, the authorization light 45A, 45B illuminates to provide that indication. Light 45A, 45B may be in any suitable location, on or near dispenser 14. Although in one embodiment the "in range" indicator is light 45A, 45B, it will be appreciated that the indication may alternatively be provided by an audible sound (eg, music, tone, or voice), a mechanical movement, a display of video or multimedia, or any combination of them or other activity that can be detected by the client.
After the in-range indicator light 45A, 45B is turned on, the system then determines whether the vehicle-mounted transponder 23 can be moved out of read range, as would be the case if the vehicle was simply passing the dispenser. At step 1113, the system checks if the vehicle-mounted transponder 23 is still in the reading field. If so, at step 1114 (discussed in detail below) the system checks whether responder 23 has been in range for a predetermined enough time. If, however, the vehicle-mounted transponder 23 is no longer in range, at step 1115 the system checks whether a predetermined number of blank reads (N) have occurred, that is, reads where no blank reads occurred. have detected responders. If so, this is an indication that the vehicle has drifted away, and accordingly in step 1116 the in-range indicator is turned off. At step 1110, system 10 returns to the default condition. It is understood that if the customer approaches, and the responder is within range of another pump, the light 45A, 45B for that pump will illuminate. It is also understood that the indication of "in scope" provided in step 1112 does not mean that the customer's identification (ie, their account number) has yet been associated with that pump for the purpose of completing a sale. This avoids the potential for fraud or mischarges to a customer when a responder simply enters within range of a bomb. If operation 1115 does not produce the predetermined number of blank readings, this is an indication that the vehicle may still be within range of the pump, and the system returns again to operation 1113 to check the transponder readings. .
As noted above, at step 1114 a determination is made as to whether the responder 23 is within range of the pump for a long enough time. If not, the system determines in step 1115 whether a predetermined number of blank reads has occurred. If the responder remains out of range, the in-range indicator will be turned off at step 1116, and the system will default at step 1110 to traditional customer treatment. If the vehicle-mounted responder 23 is in range for a sufficient time (eg, about 4 seconds), the customer-activated pump terminal allows the sale to continue in step 1118, by presenting the customer with an indication. that the pump nozzle can be removed for immediate refueling, or alternatively that another form of payment can be chosen (eg "insert a card"), or cancellation of the pending sale (for example, "cancel"). The purpose of operation 1114, delay time before the sale can continue, is to give the customer enough time to get out of the vehicle and operate the pump, thereby avoiding a fraudulent or accidental activation of the pump by someone else. other than the customer.
At step 1122 a determination is made as to whether a time limit has been exceeded. If too much time has elapsed since the vehicle was in range without the customer continuing with the sale, that is, without the customer lifting the nozzle or starting to refuel, then the in-range indicator is switched off (operation 1116) , and the system defaults to the traditional treatment of the customer (operation 1110). The time limit operation 112 may be, for example, several seconds or one or two minutes. The purpose of time limit operation 1122 is to prevent the fraudulent or accidental use of customer identification if the customer leaves the vehicle (for example, going to a service facility) or otherwise becomes inactive to complete the sale. . As an option, the time limit operation 1122 may be omitted.
ES 2 239 342 T3
If at step 1122 the time limit is not exceeded, at step 1124 a determination is made as to whether the customer has activated the pump. In step 1124, the customer can activate the pump by lifting the nozzle from the dispenser 14, or by a combination of lifting the nozzle of the pump and beginning to refuel. In a dispenser 14 that is not equipped with a nozzle lift detector, the pump can be activated by other techniques, such as by lifting a pump lever, sliding an element, or perhaps by pressing a selector switch. degree, to start the pump. For the purposes of the present specification, any of the exposed techniques or any combination of them, or any other techniques used to start the pump, are considered as "activation" of said pump.
If at step 1124 it is determined that pump 14 has not been activated, then the system checks at step 1125 whether the use of the IDC code has been aborted. A reversal can occur when the customer cancels the transaction or selects another form of payment, for example, credit card. If an override does not occur, the procedure returns to step 1122, in which the system again determines whether the set period of time has been exceeded. If there is a cancellation, the system goes to the traditional treatment of the customer, whose type of treatment depends on the type of cancellation selected. Details of checking an override when the pump has not yet been activated are set forth below with reference to FIG. 11C. Alternatively, checking for an override can be done before operation time 1122 expires; however, since the signal processing is so fast, the time-out in operation 1122 probably will not have occurred when the system first executes operation 1122. Consequently, any subsequent time-out checks in operation 1122 they will be preceded by an override check (step 1125).
If at step 1124 it is determined that the pump has been activated, then at step 1126 a determination is made as to whether the responder 23, previously determined to be within range of the pump, is still within range. In order to minimize the effect of any spurious signals that may be picked up by the antennas, and to verify that the same IDC code is being detected, both before and after pump activation, the IDC system 10 compares preferably a sample of readings made before activation of the pump, with a sample made after said activation. The IDC system verifies that the readings before and after pump activation are the same, or nearly the same. For example, the IDC system can take five readings before activation, and five readings after activation. If all, or two or three of the five readings made before activation match, as well as two or three of the five readings made after activation, then the IDC code is verified. If desired, further readings could be made. For example, ten readings made before activation could be compared to another ten readings made after activation. An acceptable comparison might be that five of the readings made before lifting the nozzle match five of the readings made after lifting.
The purpose of the above determination made in step 1125 is to ensure that the customer's vehicle is the one being refueled. This avoids the possibility of a bomb being fraudulently or accidentally activated by someone in the vicinity of said bomb during the brief instant that responder 23 is within range of said bomb. It will be appreciated that in some embodiments, step 1126 is optional, when step 1114 has already been used to determine if the responder is in range long enough. It is contemplated that both operations 1126 and 1114 may be executed, or that if one is executed the other may not be. In a way, both operations are optional, depending on the level of customer security desired for the system 10.
If at step 1126, the same responder 23 is not yet in range, then at step 1116 the "in range" flag is turned off, and at step 1110 the pump defaults to traditional customer treatment. If it is still in range, then in step 1128 the data from the transponder 23 is associated with the pump, so that a sale (eg, refueling or other acquisition) will be allowed. The pump / responder association 23 in step 1128 occurs only after the pump is turned on in step 1124.
In operation 1130, the authorization of the respondent's data (which can be information about the customer's account) is carried out. For example, the base computer 16 in combination with a network is used to determine if the customer's account number is valid for purchases. Alternatively, the home computer 16 may instead review the data stored in a local negative bad account file, and authorize the customer's account as long as it does not match a bad account number. The authorization procedure of operation 1130 may be performed prior to, or as part of, operation 1128, associating the responder 23 with the pump. In some embodiments, the association procedure is all that is needed, and no additional authorization procedure is required. The authorization could consist only of the recognition that the customer identification is valid, or of the correct number of characters. However, in most applications of system 10 some forms of database for credit authorization will be desired.
In other embodiments, authorization operation 1130 may be executed as soon as transponder 23 is within range of any pump or other reader (perhaps at the entrance to the service station environment). However, a sale will not be allowed (step 1132) unless and until the pump is activated in step 1124. Authorization operation 1128 may also include a "time out" determination (not to be confused with the elapsed time quoted with reference to operation 1122). A "time out" occurs when the TDC code has been sent to the base 16 computer or network for authorization, but has not been
ES 2 239 342 T3 received confirmation or denial after a predetermined time. Fig. 11, which is described in detail below, illustrates how a denial of authorization or "time out" can be handled, when it occurs before or after refueling or before or after the nozzle has been raised.
In operation 1132 a sale is allowed in which. for example, the customer can refuel and perhaps purchase other merchandise (which may be food) or services (car wash) at the station, all of which is charged to the customer's account identified by the responder's data 23.
In operation 1134, the sale has been completed using the customer's IDC data. Fig. 11C illustrates in more detail the operations performed to complete a transaction with the IDC. With reference to fig. 11C, while the customer is refueling, the terminal activated by him indicates that "the pump is connected" (step 1140), and the system executes certain activities specific to the customer. For example, the system can offer (by displaying a message on the TAC) to wash the car, if the customer has already purchased fuel a certain number of times; or the system can remind the customer that it is time to wash the car, when he is used to doing it every so often. Other customer-specific activities may include offering desired food or beverages, to be charged to said customer's account. The customer-specific information may come from a database that is regularly updated, and is or is accessible by the home computer 16, or such information may be included in the data radiated from the customer's responder 23, 25. If the responder is read / write (L / E), then the base computer may periodically update the information for that responder, based on customer preferences.
At step 1142, the system determines if the customer is authorized to use the IDC code for payment, or if the time has expired. Step 1142 can be included if "Authorize" step 1130 (FIG. 11B) is skipped, prior to "Sell allowed" step 1132 (FIG. 11B). It can be appreciated that the "authorization" operation may be included before or after the "sale allowed" operation 1132 (FIG. 11B) or both. If in operation 1144 (fig. 11C) authorization is denied or time expires, the handling is as illustrated in fig. 11E.
During the refueling operation the system checks again in operation 1146 for an override. Fig. 11F, discussed below, illustrates in detail checking for an override during refueling. If an override has not occurred, at step 1148 the system determines whether or not the nozzle has been snapped back into place. If not, the system continues to determine if the authorization has been denied or the time has expired (if operation 1142 is included) and if a cancellation has occurred.
After the nozzle is replenished, indicating completion of refueling, the IDC system determines in step 1150 if the network is idle, that is, if the home computer 16 can access the network. Fig. 11G further illustrates the case for determining whether the network is idle. It is understood that the network can be checked before and after starting to refuel. With reference to fig. 11C, if the network is inactive, the transaction is treated as a sale with TAC without payment (operation 1152), and the information of said sale can be stored in the memory of the base computer to be sent to the network later, when said network is operational. If the network is idle, the authorization light or other in-range indicator is turned off in step 1154. The sale is finalized, and any final specific activities of the client, such as submitting a receipt request, are executed in operation 1156.
2.2 Manual responder case
Fig. 12 shows an action table 1200 that illustrates the operation of system 10 in the case that corresponds to the use of a manual responder 25. Said responder 25 can still be used in situations in which a customer, with responder 23 mounted on the vehicle, approaches the pump, whereby responder 25 can be used to void or cancel a possible transaction related to responder 23. This can occur, for example, when the customer wants to charge the sale of the pump to a different account than that associated with the responder 23 mounted on the vehicle.
Referring now to FIG. 12, in step 1204 a customer approaches a pump, that is, a distribution area, within the vicinity of a service station. At step 1206 a determination is made as to whether the manual responder 25 is within range of the pump. As previously discussed with reference to FIGS. 1 Through 8, this determination requires that a reader 20 receive data from a transponder 25 after it is first loaded by antenna 24A or 24B. If in range, the customer typically must locate the responder 25 near the dispenser 14 or at some other designated location near the antenna 24A or 24B. If the approaching customer does not present manual responder 25, then the system defaults at operation 1221 to traditional customer treatment. It is understood that if a vehicle-mounted transponder is detected, the procedure occurs as described with reference to FIGS. 11A and 11B. At step 1206, if hand-held responder 25 is in range, the pump is provided at step 1212 with a "client in range" indication. In one embodiment, when the transponder 25 is within range of the pump's range, the authorization light 45A, 45B turns on to provide the indication. Light 45A, 45B may be at any suitable location on or near distributor 14. In one embodiment, it is at antenna location 24A or 24B that the customer presents transponder 25. If desired, separate "in range" indicators can be provided for the manual and vehicle-mounted transponder.
ES 2 239 342 T3
Once the indication has been activated, if the indicator is in the form of light, when the transponder 25 moves away from the light, it remains illuminated until a certain time expires, as explained later.
Once the indication of "in range" is produced on a bomb, in response to the presentation of a responder within range, if the customer approaches another pump so that the responder is within range, the response will also be provided. indication for the other pump, and subsequent activation and sale is allowed on both pumps, as discussed below. In one embodiment, when two prompts and activations occur concurrently, corresponding to the same manual responder 25, an prompt is provided to the service employee to alert him to this fact, so that if fraudulent or unintentional use of more than a pump by the customer's responder 25, such use may be interrupted.
Although in one embodiment, the "in range" indicator is light 45A, 45B, it will be appreciated that the indication may alternatively be provided by an audible sound (eg, music, tone, or voice), a mechanical movement, a video , or a multimedia presentation, or any combination of the aforementioned media or other activity that can be detected by the client.
In step 1218, the customer-operated pump terminal allows the sale to continue by presenting said customer with an indication that the pump nozzle can be removed for immediate refueling, or alternatively, that it can be done. another form of payment (for example, "insert a card"), or cancellation of the impending sale (for example, "cancel"). At step 1222, a determination is made as to whether a timeout has been exceeded. If too much time has elapsed since responder 25 was in scope without the customer continuing with the sale, the “in scope” indicator is disconnected (operation 1219), and the system defaults to the traditional customer treatment ( operation 1221). The operation timeout 1222 may be, for example, several seconds or a minute or two. The purpose of the time limit of operation 1222 is to prevent the fraudulent or accidental use of the customer's identification, if the customer leaves the distribution area (for example, goes to a service facility), or for another reason stops serving the complete execution of a sale. As an option, the time limit operation 1222 may be omitted.
If at step 1222 the time limit has not been exceeded, at step 1224 a determination is made as to whether the customer has activated the pump. In step 1224, the customer can activate the pump by lifting the nozzle from the dispenser 14, or by a combination of lifting the nozzle of the pump and beginning to refuel. In a dispenser 14 that is not equipped with a nozzle lift detector, activation occurs, for example, by lifting a lever on said pump, sliding an element, or perhaps by pressing a grade selection button to starting the pump. For the purposes of the present exposition, any of the above techniques or a combination of them, or others used to start the pump, are considered as "activation" of said pump.
If pump 14 has not yet been activated, the system checks in step 1225 for an override of the use of the IDC code. Cancellation can occur when the customer cancels the transaction or selects another form of payment, for example, credit card. If an abort does not occur, the procedure returns to step 1222, where the system again determines whether the time has been exceeded. If no cancellation occurs, the system goes in operation 1221 to the traditional treatment of the client, the type of treatment of which depends on the type of cancellation requested. Details of checking an override when the pump has not yet been activated are set forth below with reference to FIG. 11C.
Once the pump is activated in step 1223, then in step 1228 the responder data 25 (for example, customer account information) is associated with the pump, so that a sale is allowed (for example, refueling). or other acquisition The pump / responder association 25 in step 1228 only occurs once the pump is activated in step 1126.
In operation 1230, the authorization of the respondent's data (for example, information about the customer's account) and the verification of the elapsed time are carried out. Fig. 11E illustrates how a denial of authorization or "time expired" can be handled. At the opera operation 1232 a sale is allowed, and in operation 1234 the sale is completed with the use of the customer's IDC data. Fig. 11c illustrates in more detail the operations performed to complete a transaction with the IDC. The above operations 1230 to 1234 are performed, respectively, in substantially the same way as the operations 1130 to 1134 described above. Note that if a customer voids a transaction with IDC and selects a different payment method, the 45A or 45B indicator light will turn off.
2.3 Override check when pump is not activated
Fig. 11D describes the procedure that runs when the IDC system 10 checks for an override when the pump has not yet been activated. The procedure applies if the detected responder 23 is mounted on the vehicle or is a manual responder 25. As mentioned before, the aforementioned cancellation can occur when the customer chooses a payment method other than the use of the IDC code, or the customer decides to cancel the transaction.
Initially, the IDC system checks that the refueling action has not yet started, by determining whether the dispenser nozzle has been removed from its seat, or whether the actual refueling action has started (operations 1160 and 1162). If the nozzle has been removed and the refueling action has started, the system checks in step 1164
ES 2 239 342 T3 an override when said refueling action has been initiated. Fig. 11 describes the procedure for checking an override after the refueling action has started.
If the nozzle has not been removed and refueling has not started, then the IDC system determines if the customer: 1) has canceled the transaction by pressing the “Cancel” button on the customer-operated terminal (TAC) ( operation 116); 2) you have inserted a credit / debit card into the TAC as payment (operation 1168); or
3) you have selected a different payment method (such as cash at cash) (operation 1170). If so, the “in range” indicator turns off (operation 1172), the TAC display is changed to read “Insert card or remove mouthpiece”, or some other similar message (operation 1174), and the transaction is treated using the customer's traditional treatment methods, that is, without using the IDC code (operation 1176).
Note that if the customer clicks the "Cancel" button, he is given the opportunity to cancel said cancellation. After pressing the "Cancel" button, the display asks "Yes / No" (operation 1178). If the customer selects "No", the TAC displays a message such as "Mouthpiece, Cancel, Card" (step 1108), and the transaction continues to be treated as IDC (step 1182). Similarly, if a card is not inserted (operation 1168) or another payment key is selected (operation 1170), the transaction continues to be treated as IDC (operation 1184), in operations 1182 and 1184, if the responder is one 23 mounted on the vehicle, the procedure continues with the elapsed time operation 1122 of FIG. 11C. If the responder is a manual responder, the procedure continues with the elapsed time operation 1222 of FIG. 12.
2.4 Override check when pump is on
Fig. 11F describes the procedure when the IDC system checks for a system override that has been attempted after starting to refuel. The IDC system verifies that the refueling action has started (step 1190). If not, the system checks in operation 1191 for an override when refueling has not yet started. Fig. 11D, discussed above, describes the procedure when checking an override before starting to refuel.
If refueling has started, the IDC system determines whether or not the "Cancel" button on the customer activated terminal (TAC) has been pressed (step 1192). If so, the dispenser pump is stopped (operation 1194), and the customer is instructed on the TAC display to put the nozzle back in place and pay the clerk in the station building (operation 1195). The system then continues to complete the sale (step 1196) by checking the network (step 1150 of FIG. 11C). If the "cancel" button was not pressed in operation 1192, the IDC system determines whether or not a credit / debit card was inserted in the TAC (operation 1193), or if a different payment method was selected in said TAC ( operation 1197). If the result is affirmative, the TAC display is changed to read that the system override cannot be performed, and says, for example, that the credit / debit card cannot be accepted (step 1198). The procedure then continues processing the sale to completion at step 1199, by determining whether the nozzle has been returned to its place (step 1148, FIG. 11C). If a credit / debit card has not been inserted and a different payment has not been selected, the message for operation 1198 is not displayed, but the system continues the sale procedure until it is completed in operation 1199.
2.5 Treatment of authorization denied or time expired
Fig. 11E describes the procedure to be followed when client authorization has been denied or there is a system timeout due to a network failure to provide confirmation of client authorization or denial for the use of the IDC code. If the refueling action has already been started (step 2210), then the IDC system 10 stops the pump (2210) and informs the customer to put the nozzle back in place and pay the employee inside the service station building ( operation 2214). If said action has not started (step 2210), the IDC system 10 determines if the nozzle has been raised (step 2216).
If the nozzle has not yet been raised, the IDC procedure continues (step 2217) with step 1222 timed out, fig. 11C, if a manual responder is involved. Another opportunity to authorize the use of the IDC (for example, if there has been a system timeout) is provided again in operation 1130, fig. 11A, and in step 1230, fig. 12. If the mouthpiece has been lifted, the customer is informed through the TAC display that the IDC authorization has been denied, and is required to select another payment method (operation 2218). The transaction then continues with the traditional treatment of the customer, that is, without the use of the IDC code for payment (operation 2220).
2.6 Activation of the authorization light (In-range indicator)
Figs. 11H and 11I illustrate the general actuation of clearance lights 45A, 45B (or other "in range" indication) of dispenser 14. In FIGS. 11H and 11I not included every actuator to connect or disconnect “in range” indicators. It is understood that other figures and disclosures may here describe additional or modified systems for activating or deactivating the "in-range" indicators. With reference to figs. 11H and 11I, the IDC system 10 continuously takes readings to determine whether an IDC responder 23, 25 is present or in read range at operation 2230. If a vehicle-mounted responder 23 is in range, the system 10 IDC determines in operation 2232 if the detected IDC code has been used
ES 2 239 342 T3 recently at another gas station pump. Step 2232 is similar to step 1108 of FIG. 11A. If the answer is yes, the transaction is processed even though there is no IDC present, and the sale is processed using traditional customer methods in step 2234. As discussed above with reference to FIGS. 11A and 11B, during operation 2232, the IDC system 10 is checked to see if a transaction using the vehicle-mounted IDC code has recently been completed on another pump, that is, completed in the last five to ten minutes. . If the transaction has been completed with the use of said vehicle-mounted IDC code in the aforementioned five to ten minutes, the IDC system will not disconnect the in-range indicator, and the dispenser will not work unless another form of control is selected. pay. As mentioned above, this helps prevent fraud by giving the customer enough time after refueling to leave the service area without activating clearance lights at other dispensers in that area. Note that if a manual responder is detected in operation 2230, then system 10 will not check for recent use in operation 2232.
If the IDC code has not been used recently on another pump, or the detected IDC code has originated from a handheld responder 25, then the IDC system connects the "in range" indicator in operation 2236. While said indicator 45A, 45B is connected, the IDC system 10 determines in operations 2237, 2239, and 2241 if the responder is still in range, and if a time has elapsed. These operations (2237, 2239, and 2241) are similar to operations 1113, 1114, and 1115, respectively, of FIG. 11A.
At step 2238, the system determines whether the TAC "cancel" pushbutton has been pressed. If the answer is yes, the system determines at step 2240 whether refueling has begun, and if so, the system checks for an override at step 2242 (see FIG. 11F). If the "cancel" button has been pressed and the refueling action has not been initiated, then in step 2244 the "in range" indicator is turned off.
If the "cancel" pushbutton has not been activated in operation 2238, the IDC system 10 determines in operation 2243 if the time has been exceeded, and if not, determines if the refuel operation has been started in operation 2245. Steps 2243 and 2245 are similar to steps 1122 and 1124, respectively, of FIG. 11B, and accordingly, the description of operations 1122 and 1124 applies to operations 2243 and 2245, respectively. Note that if the time has been exceeded in operation 2243, then the "in range" indicator is turned off in operation 2244. Once the refueling action has started, the system continually checks if the nozzle has been returned to its place ( operation 2246). Once said nozzle is reset, the "in range" indicator is turned off in step 2244.
After the "in range" flag is turned off, the IDC system continues checking at step 2248 to see if the detected IDC responder is still within read range. The "in range" indicator remains off as long as the transponder is continuously read by the dispenser antenna. Thus, the "in range" indicator 45A, 45B is prevented from being turned on again as soon as the sale is completed, and before the customer has left the dispenser. Once the IDC responder is out of read range, that is, the antenna obtains an "empty" responder reading, the system essentially resets, and the authorization light will illuminate in response to a subsequent responder read. . However, as previously stated, the dispenser authorization lights will not come on for a period of five to ten minutes after the sale is completed.
2.7 Case of inactive network
Fig. 11G describes what happens if a computer network failure occurs. After a vehicle-mounted responder 23 or a manual IDC responder is read (step 2250), and the authorization light is turned on (step 2252), the IDC system 10 determines if the computer network is down (step 2254), and therefore, if the IDC code can be verified and / or final sales information can be sent from the base computer to the network for processing. If the network is inactive, the customer is informed of a network failure, and is asked to consult with the cashier (operation 2256), and the authorization light 45A, 45B (“within range” indicator) is disconnected (operation 2258).
If the network is not idle, the IDC system then determines whether the refueling operation has started (operation 2260). If not and the network is up and running, the system continues the transaction as IDC. However, once the refueling operation has started, the IDC system continually checks whether the network is interrupted (operation 2262). If at any time during the refueling operation, the network fails or is interrupted, the sale will be treated as unpaid IDC (operation 2264), and the information of said sale is stored for subsequent delivery to the network. network failures during refueling, transaction continues to be treated as IDC.
3.0 Tasks of the logic program and subsystems
The following is a description of the specific tasks carried out by the logic program and subsystems of the IDC system in one embodiment. Other provisions are contemplated.
3.1 Overview of logic program / subsystem tasks
Fig. 13 is a diagram 1300 illustrating the relationship between the main tasks of the logic program and the subsystems related to the IDC transaction. The program and subsystem tasks required to deal with the
ES 2 239 342 T3 customer identification feature (IDC), generally fall within the following areas:
A. Reading of responder numbers 23, 24 ("IDC"). This is performed by a low level responder reader task 1302.
B. Treatment of IDCs. obtaining clearances, lighting clearance lights (or other “in range” indicators), and so on. This is executed by the primitive routine 1304 of the IDC program.
C. Treatment of IDC information in a sale, by, for example, making changes to the basis and application of the Customer Platform Service code (“SPC”); Note that the SPC application and base code refers to the service station program that controls the fuel pumps and handles transactions without CID.
D. Treatment of IDC authorization requests, authorization returns, and elapsed times. This is accomplished by communications 1306 from the IDC application network, which is in communication with outside network 1308.
E. Treatment of sales activities abroad 1310, that is, those that occur at pump 14, such as reading a new IDC, inserting a credit / debit card in a terminal activated by the customer (TAC ), the customer's pressure on a different payment type key, the lifting or return of the nozzle, and the end of the sale.
F. Treatment of order entry in programming screens 1312. Through the programming screens (detailed in Appendix D), the service employee (or other authorized personnel) is able to, for example, turn IDC functions on or off for individual dispensers 14 or for the entire service station, connecting or disconnecting individual readers, assigning antennas to particular TACs, and running IDC system diagnostics.
3.2 Respondent reading task
Fig. 14 is a diagram 1400 more particularly illustrating the flow of data and commands between responder reader task 1302 and IDC primitive program routine 1304. The responder reader task 1302 selectively sends command signals to the responder readers 20 in order to connect and disconnect the readers 20 (i.e., activate them) and sends authorization light control commands from the IDC primitive 1304 also to readers 20. The transponder reader task 1302 further receives the IDC numbers read from all the antennas of the service station. In a gas station of typical dimensions, there may be eight readers 20 in the system, and each reader handles up to four antennas. Consequently, there can be up to thirty-two antennas in a typical system.
After receiving the IDC numbers, the responder reader task writes the IDC number data to Table 2, as illustrated below. The table contains the IDC numbers or values of all antennas. The antennas are grouped into pairs of high power antennas (long range) and low power antennas (short range). The first pair of antennas provides the first two values in the IDC array, one for the high power antenna and one for the low power antenna. IDC values can be eight octets, so there will be two pairs of eight octet values per reader 20. Note that the reader and antenna columns in Table 2 below are just for reference.
TABLE 2
Respondent reader task data structure
Reader
IDC antenna read on antenna
<td> 1</td><td> 1</td><td>xxxxxxxx</td>
<td> 1</td><td> 2</td><td>yyyyyyyy</td>
<td> 1</td><td> 3</td><td>zzzzzzzz</td>
<td> 1</td><td> 4</td><td></td>
<td> 2</td><td> 5</td><td></td>
<td> 2</td><td> 6</td><td></td>
<td> 2</td><td> 7</td><td></td>
<td> 2</td><td> 8</td><td></td>
<td> 3</td><td> 9</td><td></td>
<td>etc.</td><td></td><td></td>
ES 2 239 342 T3
In one embodiment, a typical reader is capable of handling two pairs of antennas (eg, antennas 22A, 22B, 24A, 24B). This means that each reader 20 provides thirty-two bytes of IDC data, or as stated above two pairs of eight-byte values. When no responder number is read from an antenna, the value zero is set in the table as the responder number for that antenna. When all responder values have been read for all antennas, a signal is sent to the IDC primitive program 1304 to process the new responder numbers. This signal is in the form of a command packet sent to the command box 1402 of the IDC primitive program. Both IDC numbers and a pointer to those IDC numbers can be sent in the order package.
The authorization light control is considered a higher program level than the responder reader task 1302, and is passed to that task 1302 as commands to turn individual lights on or off.
3.3 IDC primitive program
With reference to figs. 15 and 16, the IDC primitive program 1304 receives commands in its mailbox 1402 from them. These orders include:
1) Procedures for reading IDC numbers (data) from responder reader task 1302.
2) Connection or disconnection of the responder light (authorization light).
3) Use of IDC override on a pump (originated from SPC base 1502, (Customer Platform Service) or application code 1504).
4) Use of IDC latch on a pump (from Base of SPC 1502 when lifting nozzle).
5) Handling of IDC authorizations (authorization responses) returned from the network 1308 through the application network interface (or communications 1306).
6) End use of the IDC in a sale (from the SPC base or application code 1504 to the end of a sale.
7) Return of IDC usage status for a pump (from SPC base or application code).
8) Return of information on IDC revision (from SPC base, report generation code).
The IDC primitive program 1304 will receive a command to process a new batch of IDC number reads on the pumps or jets 14, from the responder reader task. During processing, the IDC primitive program 1304 allocates the antenna data from specific pumps 14 for use in determining the IDCs on those pumps. Each pair of antennas provides two IDC values (one per antenna). As discussed in detail below, the primitive IDC program 1304 uses non-zero value IDCs if one of them is read from any antenna of a pair of them. This non-zero IDC value is used for the pump assigned to the antenna pair. The IDC primitive program 1304 is able to determine by which antenna the IDC value is read from a vehicle mounted transponder 23, or a key fob type transponder 25. For example, if the transponder was read by a low level antenna 24A, 24B, said transponder is considered to be a keychain type 25. If the IDC was read by a high level antenna 22A, 22B, it is considered to be a vehicle mounted transponder 23.
If both antennas of a pair of IDCs give a non-zero value, that is, when 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 reads a keychain-type responder 25, the low-level reading takes precedence, and is the one used by the primitive IDC 1304 program. In this way, the key fob type responder 25 is capable of overriding a vehicle-mounted transponder 23 in a pump 14, and the transaction is debited to the account corresponding to said key fob transponder 25. The nullification measure is discussed in detail below with reference to FIG. 17M.
The primitive IDC 1304 program maintains two lists of data structures. A list, as shown in Table 3 below, provides the status of pump 14 and includes the following information for each pump: a) type of responder detected by the pump, either a 23 vehicle mounted (window), or 25 keychain / card type;
b) an index to the IDC list (the second data list, Table 4, held by primitive IDC memory 1304);
c) if there has been an IDC override on the pump and the authorization light has been forced to go out; d) if there has been a return in the change of state; and e) the previous state.
ES 2 239 342 T3
TABLE 3
Data structure of the pump list
<td>Pump type</td><td>index</td><td>Cancellation of</td><td>Return</td><td>Condition</td>
<td>no. responder</td><td>within</td><td>IDC / disconnect.</td><td>in the change</td><td>previous</td>
<td>(from veho keychain)</td><td>the IDC list</td><td>of the light</td><td>of State</td><td></td>
The second list maintained by the primitive IDC program is another structure for IDC numbers that are being processed by the system, as shown in Table 4 below. This list includes the following information for each IDC number: a) IDC number responder type, which comes from a 23 vehicle mounted, or a 25 key / card type; b) which pump 14 has read the IDC number; c) which pump 14 is using the number read; d) IDC authorization status; e) account information; d) time out; and f) shipping mailbox. Different functions change or query the two data structures (Table 3 or Table 4) in different ways.
TABLE 4
Data structure of the IDC list
IDC Respon type Read by In use in vehicle no. / Keychain pump no. Pump no.
Infor status. Mailbox time authorized it. depleted account of env
Figs. 17A through 17N and 17Q are action tables that describe the primitive IDC program and the various commands it handles. Fig. 17A describes the general IDC primitive program command procedures. Said program continually checks the orders in its IDC command box 1402 (operation 1702). If there is no command, the IDC primitive program continues with the purging of the IDC list (step 1704; see action table 1700I of FIG. 17I) where the data structure of the IDC list (Table 4) is stripped of the number of IDCs that are no longer read by a pump or not in use in a pump after an IDC override time has elapsed. With the IDC list cleanup completed, the primitive program again checks the IDC command box 1402 (step 1702 of FIG. 17A).
In action table 1700A, if there is a command in mailbox 1402, the IDC primitive program determines whether that mailbox contains IDC data from responder reader task 1302 (step 1705). If so, the IDC primitive program handles the IDC data with the use of the subroutine "IDC Data Handling" in operation 1706, box 276. The action table 1700D, "IDC Data Handling" of the figs. 17D and 17E describe in more detail how IDC data is handled.
With reference to figs. 17D and 17E, handling the IDC data requires, among other things, updating the pump list data (Table 3 above) and the structure of the IDC list data (Table 4 above) in base on IDC data received from responder's reader task 1302. In step 1800 of FIG. 17A, the IDC primitive program assigns the antenna data to the pumps 14. The action table 1700M of FIG. 17M describes in more detail the procedure by which the primitive IDC program handles the assignment of antenna data to pumps. With reference to fig. 17M, the system checks all antenna data and makes
ES 2 239 342 T3 match the antenna pairs with the appropriate pump numbers or reader chosen in operations 1802 and 1804. Then, for each pair of antenna readings (one high energy reading and one low energy reading per pair), the system determines whether or not a CID number is zero (meaning that at least one responder has been read) (step 1806). If none of the antenna readings are non-zero, that is, no antenna has detected a transponder, the system then sets the new IDC for the pump to 0 (step 1808).
If at least one IDC is not zero, then at step 1820 the IDC primitive program determines whether both IDCs in a pump are not zero. If so, that is, the high-power antenna detects a vehicle-mounted transponder 23 and the low-power antenna detects a manual transponder 25, then the data from the low-power antenna takes precedence, so the new IDC for the pump it is set to the non-zero number corresponding to the manual or key fob type responder (step 1812). If it is not desirable to allow an override by the manual responder 25. Alternatively the system can maintain an error condition and set the new IDC for the pump to zero (box 406).
If both IDCs in a pump are not zero in step 1810, then in step 1814 the new IDC for the pump is set to the non-zero IDC number, and the IDC type is set to vehicle mount or vehicle mount. keychain, depending on which antenna the new non-zero IDC value has been read from.
Returning to the action table 1700D of FIGS. 17D, 17E, after the antenna data has been assigned to the pumps (operation 1800), processing of the antennas begins individually (operations 1750, 1752). If in operation 1754 the IDC value for an antenna is zero, and the pump has not associated an IDC number, the IDC primitive program removes the signal that forces the authorization light on the pump to turn off, so that they are possible future IDC reads to connect said authorization light (step 1756). Whether or not the signal that forces the authorization light to turn off has been removed, the IDC primitive program compares in step 1758 the current IDC reading with the previous one. If there has been no change, that is, the current IDC reading is the same as the previous one, then said IDC primitive program takes no action (operation 1760).
If the current IDC is different from the previous one (step 1762), the system determines again in step 1764 if the current IDC is null. If not, in operations 1820 and 1711, the system executes subroutines to handle a new non-null IDC reading in the pump, as well as the return on the change of state, respectively. The subroutine to handle the new non-null IDC reading is described in more detail in action table 1700F of FIGS. 17F, 17G, and the subroutine for handling return on state changes is described in more detail in action table 1700C of FIG. 17C. These subroutines are discussed in detail later.
If in operation 1764, fig. 17E, the current IDC is null, the system determines in step 1766 if the previous one came from a vehicle-mounted responder 23. If not, the system does not act on operation 1768, as this means that the old IDC came from a keychain type responder 25. If the old IDC came from a vehicle-mounted responder 23, the IDC primitive program executes the operations (1770, 1772, 1711, 1774, 1776, and 1778) to update the data structure of the pump list (Table 3 ) and the data structure of the IDC list (Table 4), in order to "disconnect" the IDC from the pump (operation 1774) and disassociate said pump from any IDC (operation 1778). In operation 1776, the vehicle-mounted IDC is not immediately overridden, but instead, a time is set for a later override. Thus, the vehicle-mounted transponder 23 will not turn on clearance lights when passing other pumps for a predetermined period of time.
With reference to figs. 17F, 17G, the operations performed by the primitive IDC program to process a new non-null IDC reading on a pump will now be described (step 1820 of FIG. 17E). First, the primitive IDC program determines in step 1821 whether the new IDC is on the active IDC list (Table 4). If not, the new IDC is added to the active list in step 1822, and an authorization request is sent to the network for the new IDC (step 1823). The authorization light remains on on the pump (step 1824), and the system then determines whether a different IDC had previously been associated with the pump (step 1825). If so, and the previous (old) IDC came from a keychain type responder, the old IDC is deleted from the Tables (operations 1826 and 1827). If so, but that the previous IDC did not come from a key fob responder 25, that is, it came from a vehicle-mounted responder 23, in operations 1828 and 1830, the old IDC entry in the column “read by the pump no. from Table 4 is deleted (set to zero), and a time is set to delete the old IDC from the Table, respectively. Next, in operations 1831 and 1832, the index of IDCs associated with the pump is established (Table 3), and the present pump is established as input for the column "read by pump no. (Table 4), respectively. In operation 1834 the treatment of the new non-null IDC is completed.
If at step 1821, the new non-null IDC is already on the active IDC list, the primitive IDC program checks if the new non-null IDC is in use on another pump (steps 1836 to 1842). If the new IDC comes from a keychain responder 25, and is currently being used by another pump (operations 1837, 1838, 1839), the new IDC is added to the list of active IDCs in 1822. Thus, the responder 25 Keychain can be used on more than one pump at a time. If the new IDC comes from a chain responder, and is not currently being used in another pump, (operations 1837, 1838, and 1839), then in operation 1840, the existing IDC entry in the table is used, that is, a new entry is not made.
ES 2 239 342 T3
If the new IDC comes from a transponder 23 mounted on a vehicle, and is not used by another pump (operations 1837, 1840), in operation 1840 the existing IDC entry in the table is used, that is, it is not carried out a new entry. If, however, the new IDC comes from a transponder 23 mounted on a vehicle and is in use by another pump (operations 1837, 1840, 1842), the signaling that forces the light to turn off is set, so that the reading of the new IDC will not turn on the authorization light. Accordingly, the vehicle-mounted transponder is prevented from being used on more than one pump each time. The treatment then ends in operation 1834.
Following are other commands handled by the primitive IDC program.
3.4 IDC Primitive Program Interface / Sales Treatment
The treatment of sales abroad, that is, when the customer does not go through a box or employee but makes the payment at the pump 14 by using the TAC or IDC code, requires the interconnection in a certain number of the operations in the sale process, as described below. The various operations include:
1. First a new IDC is read in a pump, or no one (zero CID) is read.
two. Inserting an account number, inserting a card, or pressing the type of payment key.
3. Lift the nozzle from the dispenser.
Four. Authorization approval, denial, or time out.
5. End of sale or cancellation.
In each of the above cases, the SPC (platform service client) base code 1502 notifies the IDC primitive program 1304, or the SPC base code 1502, that the event or operation has occurred. Both the SPC codebase and the IDC primitive program handle these events.
3.4.1 An IDC number is first read from a pump
With reference to fig. 17A, when an IDC number is first read from a pump, the IDC primitive program 1304 checks for a return on the IDC status change request for the pump (see step 1708 and the subroutine at step 1710 of Fig. 17A, and the action table 1700B "Return handling on state change request" in Fig. 17B). If so, the IDC primitive program sends a notification to the SPC base treatment code to report the reading of a new IDC. The SPC base code notifies the application code, which can perform some of the functions such as changing the TAC display, to reflect that the IDC has been read from the pump.
Similarly, if a vehicle-mounted transponder 23 exceeds the reading range of a pump, the IDC primitive program informs the SPC base that the IDC is no longer read from the pump (if a return on change of status is requested for that pump). This allows the application code to change the query on the TAC viewer back to its original state (not to the IDC read state), or perform any necessary actions.
The primitive IDC state return interface uses mailboxes for command request and for state change notification. The SPC base sends a state change or return request to the primitive IDC program, through the command mailbox of said primitive IDC program, and the latter processes the request and checks the IDC reads in the TAC. When a new IDC is read, the change of state is returned to the appropriate state mailbox for cpt request. Fig. fifteen is a diagram 1500 illustrating the feedback over the state change interface.
3.4.2 Inserting an account number, card number, or payment type keypress
When an account is inserted in its acceptor, a card in the TAC, or a payment type key is pressed in said TAC, the SPC base code 1502 handles the event in the normal way, The SPC code also calls the new override routine_idc_in_pump-.
The format of the call is:
- override_idc_in_pump (pump number and status)
This routine sends an override_idc_on_pump command to the IDC command mailbox (see operation 1712 and subroutine operation 1714 of Fig. 17A, and action table 1700H "IDC override handling" of Fig. 17H). With reference to fig. 17H, if the pump has not been activated yet, the authorization light is off on the pump, and the IDC is prevented from being used in a sale at the pump (operations 1850 and 1852). However, if the pump has already been activated, the intended override is ignored, and a message is displayed on the TAC that the override cannot be done (operations 1850 and 1854). In operation 1856 the abort subroutine ends.
ES 2 239 342 T3
3.4.3 Lifting the nozzle
When the nozzle is raised on a pump 14, if it is not already authorized or an authorization is in progress, and if the pump does not present problems that prevent authorization, the SPC base code 1502 calls the new hook_idc_in_pump routine ( ).
The format of the call is:
hitch_idc_in_pump (pump number and status).
This routine sends a lock_idc_in_pump command to the IDC command mailbox (see operation 1716 and subroutine 1718 of FIG. 17A, and action table 1700K "Handling IDC lock on pump" of FIG. 17K) . With reference to fig. 17K, when processed, the order checks if the pump has read the IDC, and if it can be used in a new sale. In particular, in step 1902, the system determines whether the pump has an associated IDC index. If not, the sale will not be from IDC (operation 1904), and a signal is provided to force the light to turn off, that is, the pump light is switched off (if it is not already) (operation 1906 ).
If the pump has an associated IDC index in step 1902, the system checks if the signaling that forces the light to turn off is already set, that is, for disconnection (step 1908). If so, then in operation 1910, the IDC cannot be used for sale. If the light is not ready to go out, the IDC can be used in the sale, and the IDC is associated with the sale in said pump (step 1912). A status situation is returned indicating whether or not the sale is an IDC sale. In run 1914, Table 4 is updated to indicate that IDC is in use at the pump. In operations 1916, 1918, and 1920, the appropriate mailbox for authorization responses is specified, and the primitive IDC program sends the authorization or elapsed time response to the appropriate task mailbox, which is how the system works with preauthorizations. .
As previously discussed, to reduce the effect of any extraneous signals that may be picked up by the antennas, and to verify that the same IDC code is being detected both before and after lifting the nozzle, the IDC system preferably compares a sample of readings made before said nozzle lift with another sample after lift. The IDC system verifies that the readings before and after the survey are the same or nearly the same. For example, the IDC system can take five readings before lifting the nozzle, and five after lifting the nozzle. If all, or two or three of the five pre-survey readings match all, or two or three of the five post-survey readings, the IDC code is verified. More readings could be done if desired. For example, ten readings taken before the lift could be compared with ten readings after the lift, and an acceptable comparison would be that five of the readings taken before the lift match up to five more after the lift.
3.4.4 End of sale / cancellation
When a sale is canceled or finalized, the SPC base code 1502 calls the new routine fin_sale_idc_ in_pump (). The format of the call is:
end_selling_idc_in_pump (pump_n °, and status)
This routine sends an end_sell_idc_in_pump command to the IDC command mailbox (see operation 1720 and subroutine 1722 of FIG. 17A and action table 1700L, "Handling end_use_idc_in_pump" of FIG. 17L). This command informs the IDC primitive program that the sale of the pump has ended. With reference to fig. 17L, the IDC primitive program determines in operation 1930 if an IDC in their Table is associated with the pump, and if so, it begins cleaning on the IDC in operations 1932, 1934, 1936, 1938, and 1940 The IDC is not rejected immediately, as the system needs to keep it in a state of use in a sale. This is so that when a vehicle-mounted responder 23 sale concludes on a bomb, said responder does not turn on clearance lights when passing other pumps for a predetermined period of time.
3.5 Primitive IDC communication interface / Network
The primitive IDC 1302 interfaces with the communications code of the specific application network in order to send authorization requests to the appropriate network, and to receive responses from that network.
3.5.1 IDC authorization request
When a new IDC is sent to an antenna for the first time, an authorization request is generated for that IDC. A new routine, authorization_idc (), interacts with existing network communications code to generate an authorization request to be sent to the network. The format of the call is:
authorization_idc (idc_num, idc_index, mailbox_return, and status);
ES 2 239 342 T3 where index_id is a method of identifying the return authorization with the IDC from which said authorization is requested. This procedure is called by the primitive IDC program, and does not require sending any commands from the command box of the primitive IDC program.
Authorization requests are filled out with the IDC number, instead of the credit card account number, and its associated information. This has to be done for each application, since the network interfaces are different.
3.5.2 Approval, denial of authorization, or time out
When the authorization of an IDC is approved, denied, or the time has expired, the primitive IDC program receives an authorization response from the network communications code (see operation 1724 and subroutine operation 1726 of FIG. 17A and the action table 1700J "Authorization response" of Fig. 17J). Fig. 16 is a spatial diagram showing the authorization request and response handling. The decoding_idc_authoriz_response () procedure is called by the network communications code of the specific project. This procedure deals with the "decoding" of the response from the network to a format that can be used by the application's authorization response handling routine. This routine returns the decoded authorization response to the primitive IDC program.
The format of the call is:
decode_idc_authoriz_response (parameters to be determined)
This procedure is called by the network communications code. The procedure generates a command (treat_idc_autori_response) to the command mailbox of the primitive IDC program, to process and possibly forward the decoded authorization response.
When a decoded authorization response is received by the IDC primitive program, it first determines in step 1940 whether the IDC is on their list (in use). If not, the IDC authorization or override time is discarded in operation 1943. If yes, the primitive IDC memory stores a flag for the authorization response in the IDC structure, and changes the authorization state. for that IDC (operation 1942). If the IDC is in use in a pump, and the forward send mailbox is set (step 1944), the primitive IDC program sends the IDC authorization response to that mailbox (step 1946). Note that in said 1946 operation, if the authorization is approved, the SPC / authorization base will copy the information about the account for the completion of the sale. If authorization is denied or time runs out, the SPC / App Base will terminate the sale and stop the pump. If in operation 1944, the IDC forwarding mailbox has not been established, in operation 1948 the authorization information for future forwarding is saved, in case the IDC is used later in a pump. .
The authorization response, after the correct mailbox is sent forward, is handled by the application-specific code, which proceeds to process it. If the authorization is approved, the application can continue the sale. If such authorization is denied or time runs out, the application can stop the sale at the pump.
Note that figs. 17N and 17Q show a 1700N action table of a 1950 “IDC authorization task start”. Operations 1750N, 1752N, 1754N, 1756N, 1758N, 1760N, 1762N 1764Q, 1766Q, 1768Q, 1770Q, 1772Q, 1774Q, 1776Q, 1778Q, and 1820Q, are similar to operations 1750, 1752, 1754, 1756, 1758, 1760, 1762, 1764,1766, 1768,1770,1772,1774, 1776,1778, and 1880 of the 1700D stock table. of figs. 17D and 17E. The action table 1700N has the added operation 1952 of determining if the pump is in use. If so, in operation 1954, any IDC reading on a pump in use is ignored.
4.0 Options
What follows are various descriptions of additions or changes that can be made to the IDC system. One or more of the variations can be made to the system at one time.
4.1 Car wash
For service stations that have an automatic car wash facility, an independent reader with a long-range antenna to detect vehicle-mounted responders, and a short-range antenna to detect keyfob / card type responders, can be located at the entrance to the car wash. Customers can use both the vehicle-mounted responder and the manual to pay for the car wash, or they can be authorized for a free wash if the service station gives away car washes for refueling.
The network can provide information regarding the customer's preferences for car washing (such as just washing, waxing, drying, etc.) so that the customer does not need to enter the information at the beginning, but to continue with the car wash one once authorization is obtained. Preferences can be displayed on a customer-activated terminal (TAC) arranged in the separate reader, and overridden by pressing the appropriate keys on the TAC, if desired.
ES 2 239 342 T3
When a service station provides free car washes, and the customer has met the conditions to receive a free wash, the TAC presents a message to the customer that they have been granted a free wash. The customer is also given the option to add other services to the car wash, such as waxing or drying. These additional services can then be charged to the client's responder account.
4.2 Manual antenna
As an option, service stations could be equipped with manual or wand-type antennas on the pump islands. The handheld antenna could be swung in front of a vehicle-mounted transponder by the station employee who refuels on that island.
4.3 Nozzle antenna
As an option, the reader antennas may be located at the nozzle of the dispensers, and the customer's responder may be located at the entrance to or on the neck of the vehicle's fuel tank. When the jet nozzle is inserted into the fuel tank inlet, the nozzle antenna detects the tank responder.
4.4 PIN number
As an option, the IDC system may be programmed to submit a request to the TAC for a personal identification number (PIN). The PIN would be a different number than the IDC number, and can be used in place of a correct reading of the IDC number, or to verify a responder's reading of an IDC number. In response to the PIN request, the customer will use the TAC keypad to enter the PIN.
4.5 Payment within
A keychain / card reader can be placed inside the building of the service station, for purchases of other products such as food, articles for the car, magazines, which can be offered by said station. For example, many gas stations include a utility store, which offers a certain variety of items for sale. A reader could be located near the checkout counter, and the customer can swing the key fob / card type responder as they pass the reader, to make payment for the purchased items.
4.6 Awards and recognition
The network keeps track of past purchases and customer purchasing preferences, and provides rewards for frequent purchases. When a responder is read, the TAC may present a message indicating the prizes awarded to a customer, such as a car wash.
The network may also maintain a profile of the customer, and provide a personalized service to that customer based on their profile. Said profile can include information about the client, such as name, address, telephone number, date of birth, security code; payment information, such as primary method of payment (no. card, validity date, card type), and secondary payment method (with the same data), preference information such as desired receipt in the TAC, language (English, Spanish), car wash preference, and information on acquisitions, such as products acquired, date of acquisition, value of it, quantity acquired. An example of a personalized service based on the customer's profile includes the automatic printing of a receipt at the TAC, or that the customer can get a full service when refueling, that is, refueling by a service employee. The customer simply drives to the station, allows the vehicle-mounted transponder (or manual) to be read by a station antenna, and the network sends a signal to the employee to refuel.
The customer's profile can be based on questionnaires filled out by him and entered into the network, and on previous transactions completed by the customer.
4.7 Car diagnosis
Many vehicles include computers that keep track of car diagnostics. For example, the computer keeps track of the water level in the radiator, oil level, and miles. tours of the car. The IDC responders can be linked to the vehicle's computer in order to read the diagnostic information, and can radiate that information to an IDC antenna at the service station. The station dispenser TAC can then present the customer with a reminder based on diagnostic information, such as the need for a car oil change.
4.8 Employee control over the dispenser
A gas station employee can override the use of a responder if he suspects fraud. For example, an employee may wish to interrupt the fuel supply at a pump, if he suspects that the user is simply waiting at the pump until a vehicle with a transponder mounted on it passes nearby and activates the clearance light on that pump.
ES 2 239 342 T3
5.0 Additional system description
Following is Appendix D, which contains a further description of the IDC system 10, implemented with a commercially available fuel distribution system, such as Wayne Plus / 2. Wayne Plus / 3, or Nucleus, available from Wayne Division. Dresser Industries, Inc. of Austin, Texas. Specifically, Appendix C illustrates certain changes to be made to the fuel distribution control system to incorporate the remote RF IDC features of the system 10, including changes that can be made on the programming screens as part of the computer. base 16, the network log, and the reports and action logs. Although illustrative embodiments of the present invention have been shown and described, a certain degree of modifications, changes, and substitutions is provided in the foregoing specification, and in certain cases some features of the invention will be employed without corresponding use of others. For example, any type of commercially available distribution system can be modified, adapted, or replaced to comprise system 10. Any number of pumps, islands, antennas, distribution areas, and kiosks can be included as part of the system. Certain features have to be modified to meet the specific needs of different competitive service station companies. Aspects of the operating flow of the system may or may not be used optionally. Although the system can be used for retail fuel supply, it is also understood that such a system has application to utility stores, quick service restaurants, car washes, and the like. For example, the system may have application in a service desk or window acquisition system. Accordingly, it is appropriate that the appended claims be considered broadly and in a manner consistent with the scope of the invention.
Appendix a
Slave reader line protocol
1.1 General
The data link described here is based on a main unit / slave unit relationship in which the main unit (SPC) (Service Platform Client) sends data or orders to the slave units (TPCs). Slave units will make appropriate responses to communication initiated by the master. In no case will a slave unit initiate communications. Communication is half duplex, and the protocol is transparent and octet oriented. This protocol allows a variable length.
1.2 Data format
- Asynchronous communication
- 9600baud
- 1 start bit
- 8 data bits
- no parity bit
- 1 bit high
1.3 Data link hardware
The data link is a 2-wire multi-terminal line, RS-485.
1.4 Error check
Error checking is done through a CRC-16 (cyclic redundancy checker) on all transmissions. Parity is not required at the octet level, since CRC-16 is used in all transmitted octets.
1.5 Transmission mode
The transmission mode will be half-duplex, asynchronous, and in a start-end format.
1.6 Buffer size
The transmit and receive buffers on the master and slave devices are variable, and depend on the application. Nevertheless. the maximum size is 251 octets, excluding the protocol control and inserted DLE (delivery error) octets. (The "inserted DLE" bytes are used to achieve data transparency, as explained in the CODE TRANSPARENCY section).
ES 2 239 342 T3
1.7 Protocol
The protocol structure consists of a sync octet followed by the slave device octet, an optional data field, a stop octet, and two CRC octets. A protocol octet map and a description of each octet follows.
SYNCHRO / DIRECC / Data octets (251 max.) / SF / CRC1 / CRC2
Octet SINCRO (FE exag)
The SYNCHRO byte indicates to the receiving device that the transmission of the communication block begins. It also indicates that the next octet transmitted contains the address of the slave device.
DIRECC octet (00 to FF exag)
The DIRECC octet is the address of the slave device
Octet SF (FD exag)
The SF (stop signaling) byte indicates the end of the control and data parts of the transmission. SF also indicates that the next two octets contain the CRC of the transmission.
Octets of CRC1 and CRC2
CRC1 is the least significant octet of the CRC-16 check job. CRC1 and CRC2 are calculated on the following octets: SYNCHRO, DIRECC, (DATA, excluding inserted DLEs), SF.
The main unit transmits a message according to the above protocol. The recipient unit responds using the same protocol.
After the master or slave unit receives its latest data, it waits a minimum of 5 ms before connecting its transmitter. This provides the sender with a possibility to disconnect their transmitter and connect their receiver.
If the slave unit detects a transmission error, it does not respond.
1.8 Code transparency
Code transparency for eight-bit data is achieved by inserting the Data Link Escape (DLE). The DLE character octet has a value of OFCH. Note that this is not an ASCII value for the DLE. The DLE character is inserted before the data patterns specified in the protocol, to clarify the meaning of those data patterns. The inserted DLE characters are not included in the CRC-16 calculation. The rules for DLE insertion are as follows:
- The DLE is inserted before any octet in the transmission that has a value equal to SYNCHRO, except for the actual SYNCHRO octet. This includes DIRECC, all data bytes, CRC1 and CRC2.
- The DLE is inserted before any octet in the transmission that has a value equal to SF, except the actual SF octet. Any octet, includes DIRECC, all data octets, CRC1 and CRC2.
- The DLE is inserted before any octet in the transmission that has a value equal to that of DLE. This allows the DLE value to be transmitted to the receiver. Any octet includes DIRCC, all data octets, CRC1 and CRC2.
Appendix b
Communication protocol between the base computer and the readers
The TIRIS ™ 52000 reader application software available from Texas Instruments Inc. includes a "gate function" in which serial interrupts are disabled just prior to a "responder receive" routine. This TIRIS ™ S2000 program synchronizes the readers by moving the synchronization line from high to low. The program of the S2000 reader is modified according to the present invention, so that at the end of a load cycle, the synchronization line is forced to go high, so that it is always in the case of low value during the charge cycle.
The original TIRIS ™ program has what is called input-character time-output, and if more than three character times have passed, the reader 20 would consider it a bad request and move on to another. Although this is adjustable through the logic program, it is unusual and too rigid. This stiffness has the side effect of forcing the base computer 16 to accommodate the peripheral timing, rather than another of the environment.
ES 2 239 342 T3
Cooperative communications require the base computer 16 to transmit only during a load pulse. If one were to use time overrides between characters, it is possible that a message could be split between two load pulses (this has been seen in the checks). The result is that the TIRIS ™ reader 20 estimates that it has received only part of a message (which is rejected). Since timing during communications is so important, if the TIRIS ™ reader 20 sees a character, it waits until the entire message has been sent, and the override time period has elapsed.
In order to allow reuse of Wayne base computer communications publications, the base level protocol has been redefined to follow the TPC or slave unit protocol (see Appendix A above) also known as the “TAC protocol. ”. Since this protocol is quite generalized in the way data is formatted, it has been defined in a limited way by the reader 20. This protocol differs from the TIRIS Bus protocol<sub>tm</sub> available from Texas Instruments Inc. (See “TIRIS ™ Bus Protocol” (TBP), Chapter 7, in “TIRIS: Series 2000 Reader System Reference Manual”, Texas Instruments, (part no. .RI-ACC-D01A), which is incorporated herein by reference), in the following respects:
- the beginning of the header has been changed from 0x01 to 0xFE
- the end of the message has been changed from 0x04 to 0xFD
- CRC has been changed from CRC-CCITT to CRC-16 (initialized to 0xFFFF)
- all responses from readers contain, as their first data byte, the order code that initiates the response.
All reader commands have the following format:
<td>Oct.O</td><td>Oct 1</td><td>Oct. 2</td><td>Oct 3</td><td>Oct 4</td><td>Oct 5 ...</td><td>Oct long + 5</td><td>Oct long + 6</td><td>Oct long + 7</td>
<td>I ate. encab</td><td>Destination</td><td>Source</td><td>Order</td><td>Length</td><td>Data</td><td>End of message</td><td>LSBde CRC</td><td>CRC MSB</td>
Octet Description
Beginning of header - always 0xFE
Destination - which reader is this message going to
Origin - address of the base computer (always 0x00)
Command - which command reader executes it
Length - length of the data (can be 0)
Data - data to send long + 5 End of message - always 0xFD long + 6 CRC - most significant byte long + 7 CRC - least significant byte
The responses from the reader have the following form:
<td>Oct.O</td><td>Oct 1</td><td>Oct 2</td><td>Oct 3 Oct 4</td><td>Oct 5 ...</td><td>Oct long + 5</td><td>Oct long + 6</td><td>Oct long + 7</td>
<td>I ate.</td><td>Destination</td><td>Source</td><td>Code Length</td><td>Data</td><td>End of</td><td>LSBde</td><td>MSB of</td>
<td>encab</td><td></td><td></td><td>of resp.</td><td></td><td>message</td><td>CRC</td><td>CRC</td>
ES 2 239 342 T3
Octet Description
Beginning of header - always -xFE
Destination - address computer .debase- always 0x00
Origin - which reader is this message coming from
Response code - described on pages 7 and 8 of “TIRIS ™ Bus Protocol”
Length - length of the data (never less than 1)
Data - answer. The first octet is always the command that initiates the response long + 5 End of the message - always 0xFD long + 6 CRC - most significant octet long + 7 CRC - least significant octet
To allow "data transparency", the CPT protocol implements a special code called Data Link Escape or DLE. The DLE is used before any character that for one reason or another is 0xFE (beginning of header), 0xFD (end of message), or 0xFC (DLE). Inserting DLE before any of these three characters informs the receiving program to treat the next octet as data, rather than Start of Header, End of message, or even another DLE.
Example
Data stream
22 FC FE FC FD 22 FD
Data
Data
DLE
Data
DLE
Data
Data
End of message
Note that the DLE characters are not included as part of the CRC calculation, which is on the data packet prior to DLE insertion. Therefore, it is perfectly valid to have DLE characters inserted in the CRC.
Appendix c
Improvements in the reader logic program
The TIRIS ™ reader software has been modified and improved in accordance with the present invention by adding functions, antenna synchronization, and modifying the base reader-computer protocol, to make it more robust. The enhancements made to the reader program are designed to add functionality, without suppressing any of those currently existing in the commercially available TIRIS ™ reader software. Enhancements include new command codes for the TIRIS ™ Bus protocol (see Appendix B) that controls the antenna multiplexer, addition of an antenna scan buffer, use of a built-in DIP switch to set the address of the plate control, and provide a new communications scheme. Enhancements can be implemented by adding command codes to the TIRIS ™ Bus protocol, defined as Group 3 commands (96 to 127), which have been reserved by Texas Instruments specifically for the user. By adding commands in this area, possible future conflicts with the functions of the TIRIS ™ program are avoided.
1.0 Scan Buffer
The scan buffer is designed to allow the host computer to retrieve all four antennas at once, rather than individually. Part of this is put into practice by putting the system in door mode.
The gate mode indicates that the system will do repetitive read-load cycles, normally storing any responder ID it reads in the reader's queue, for later access. This action has been modified so that the data is now stored in the scan buffer, with the use of the following algorithm:
ES 2 239 342 T3
Arrange the multiplexer of the reader for the antenna N Charge the transponder (send an energy pulse)
Read the responder
If a responder ID is received:
store responder in scan buffer (N)
Also, if the scan buffer (N) has an ID and has not been read by the host computer, stay idle Also, clear the scan buffer (N)
Later, when the buffer is read, signals are provided indicating that the four antennas have been read. This provides a "latch" mechanism in which any responder reads remain in the buffer until read by the home computer (thus preventing home computer errors from losing any responder reads due to these readings are within the antenna cycle).
2.0 Order codes
They are the most visible part of the program improvement, and consist of the following commands:
- 0x40 (decimal 64) IDC and TIRIS ™ Wayne revision returns
- 0x62 (decimal 98) antenna scan block results returns
- 0x64 (decimal 100) gate power pulse
- 0x65 (decimal 101) returns from history read
- 0x66 (decimal 102) variable length antenna scan block result return
- 0x67 (decimal 103) echo check data
- 0x68 (decimal 104) enabling / disabling of the dispenser lamps.
2.1 Getting version
Order code: 0x40 (96) Immediate mode only
Sent data: None
Received data: Indication of success or failure. Success is indicated by the return of a version number string (0-24 octets). The failure is indicated by the standard error response.
Description: This modifies the get version order to the following:
1 23456789 10 l 12 13 14 15 16 17 18 19 20 21 22 23 24 IDC Wayne x.xx TIRIS x.xx
This fixed string makes it easy to check the version number of the IDC (customer identification) logic program. The version of the TIRIS program<sup>TM</sup> it is also returned for documentation and maintenance purposes.
2.2 Getting Antenna Scan Buffer
Order code: 0x62 (98) Immediate mode only
Sent data: None
ES 2 239 342 T3
Data returned: A total of 36 octets, 9 octets per antenna (1 status octet and 8 responder ID octets). The failure is indicated by the standard error response.
Description: This represents the code of the last responder seen. If no responder was seen, 0x0000000000000000 is returned. This function returns a structure of what follows.
Type of responder ID structure {
State octet
Responder ID Octet [8];
} Responder ID
Responder ID Return of Responders [4]
The returned status will be one of the following:
Valid response Invalid response
RO-TRP (0x00) NO_LECT (0x40)
RW_TRP (0x01) INCOMPLETE (0x41)
MPTCOTRP-U (0x02)<sup>2</sup> MPTRERR_SPC_DATOS (0x46)<sup>2</sup>
MPTCOTRP_L (0x03)<sup>2</sup> MPTTRERR_ESTADO (0x47)<sup>2</sup>
Note: All status octets are set to NO_READ after this command is executed
2.3 Obtaining the variable length antenna scan buffer
Order code: 0x6 (102) Immediate mode only
Sent data: None
Returned data: A variable length block of data consisting of one (non-responders) to octets (all responders) is returned, one octet indicates which antenna data is being returned with 9 octets per antenna (1 status octet and 8 octets of responder ID). The failure is indicated by the standard error response.
Description: This is a variable length version of the Antenna Scan Buffer Get Function. It was designed under the condition that a responder will not be present for a majority of the time. Even in the normal case you have two active responders (one on each side of the pump). The user of this function allows the reader to “consume” less time executing CRCs on empty packets. This function returns a structure of the following:
Structure Paquetelnf {
Active antenna byte; // eslruct. bit 0 = = antenna 1, etc // follow 0-4 of these
[
State octet;
Responder Octet of ID [8J;
J Antenna;
} ID responder
ES 2 239 342 T3
The returned status will be one of the following:
Valid answer
RO_ TRP (0x00)
RW_TRP (0x1)
MPTCOTRPU (0x02)
MPTCOTRP_L<sup>3</sup> (0x03)
Example (excluding package body):
no antenna
00 41. ..ff antennal
00 41. ..ff antenna 3
00 41 ... ff 0041 ... ff antennas2y3
090041 ... ff 0041 ... ff antennas ly4
Note: All status octets in the scan buffer are set to NO_READ after the execution of this command.
2.4 Gate Power Boost
Order code: 0x64 (100) Immediate mode only
Data sent: Octet 9 0x00 disconnects the energy pulse
0x01 connects power boost
Data returned: Success is indicated by the standard order completed message. The failure is indicated by the standard error response.
Description: This function allows the base computer to emit a power pulse, but still continue to operate. The antenna scan buffers for that reader will eventually be cleared of all values.
The connection of the energy pulse allows the reader to continue connected to the next antenna (the same as the other readers).
Note. When the power pulse is disconnected, the red LED will no longer flash.
2.5 Obtaining the reading history
Order code: 0.65 (101) Immediate mode only
Sent data: None
Returned data: If successful, a total of 80 octets are returned as 20 unassigned integers of four octets. The failure is indicated by the standard error response.
Description: This function allows the base computer to read the history around the event and / or the failure of the reader to read the codes of the responder. Returns the data as follows:
structure {
unsigned length of total reads; unsigned length of total success; unsigned length of total unread errors unsigned length of incomplete total errors unsigned length of other total errors} Structure taken over [4]
ES 2 239 342 T3
This routine clears the totals immediately after sending them to the base computer.
2.6 Echo check data
Order code: 0x67 (103) Immediate mode only
Sent data: Up to 200 bytes of test data.
Data returned: If successful, the check data is returned successfully.
The failure is indicated by the standard error response.
Description: This feature is designed to validate communication by a reader by allowing a user to send arbitrary data to a reader. The reader must return the same string that was sent to him.
To check for a DLE (delivery error) in the CRC (Cyclic Redundancy Checker), send a 0xFE to reader 1, for example:
<td></td><td>Start</td><td>Destination</td><td>Source</td><td>Order</td><td>Length</td><td>Data</td><td>End</td><td>CRC</td>
<td>The ord.</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>
<td>base transmits</td><td>FAITH</td><td> 01</td><td> 00</td><td> 67</td><td> 01</td><td>FCFE</td><td>FD</td><td>4BCA</td>
<td>The ord. base</td><td>FAITH</td><td> 00</td><td> 01</td><td> 00</td><td> 02</td><td>67FCFE</td><td>FD</td><td>FCFE 94</td>
receives
Note that the DLEs are not counted in the data length.
2.7 Enable / disable dispenser lamps
Order code: 0x68 (104) Immediate mode only
Sent data: Octet 0 - lamp n<sup>or</sup> (1 or 2)
Octet 1 - light mode (0 - off, 1 - on - blink)
Data returned: Success is indicated by the standard order completed message. The failure is indicated by the standard error response
Description: This feature is designed to control the lamps on either side of the dispenser (aka clearance or distribution lights). This command allows the user to indicate which lamp is to be connected, disconnected, or set to blink, without affecting the state of the other lamp. This function is such that a lamp can go to any state from any other. For example, you can switch from connect to disconnect, connect to blink, disconnect to connect, disconnect to blink, blink to connect, and blink to disconnect.
2.8 Structure of the scan buffer
During the antenna scan, the ID of any responder found will be stored in the eight octets corresponding to that antenna. Current 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:
ES 2 239 342 T3
Character ID responder structure type unsigned status; character unsigned ID [8];
// antenna state // responder id} responder ID;
Mem. Buffer explode respond.ID [4]; // four antennas
2.9 DIP switch address
Normally a program connected to the TIRIS ™ configuration gate is required to set the address of that gate (as well as other parameters). Since this is a field problem, where technicians need to exchange parts quickly with a minimum of preparation, the DIP switch that resides on the TIRIS ™ board has been chosen for this task. Four switches provide a total of 16 unique addresses. Readers will have addresses ranging from 0x01 to 0x10 (1-16). In particular, the main reader will always have address 1 (0x01) which will be represented by setting the main reader DIP switches numbered 1, 2, 3, and 4 in the ON, OFF, OFF, and OFF positions. (disconnection), respectively. Similarly, the DIP switches of a slave reader with address 15 (0x0F) will all be in the ON position, and the DIP switches of a slave reader with address 16 (0x10) will all be set to the OFF position. Due to how DIP switches are used, readers can never be set to have an address of 0x00 (the address of the host computer).
In addition, the configuration is fixed at 9600 baud, 8 bit, 1 bit high, no parity, BUS TIRIS ™ protocol, and multiplex-sync sync.
2.10 Tuning antennas
The tuning of the antennas is important for error-free reception of the transponder data. The simplest tuning method is to unplug the multiplexer line (ST35) coming from the reader. The multiplexer will default to antenna 1.
2.11 IDC System Check Plug
The check lamp is normally controlled by the base computer program, which issues a command to the reader. There are some cases where it is beneficial to have the reader turn on the lamps when a valid responder is detected. This is done by means of a "test plug". This plug consists of a four-pin Phenix male plug with a connection cable to all four pins 1 to 4. When this plug is inserted into the St33 (RES / INP) receptacle and the reader is reset (either by cyclic power or by pressing the S1 switch), the IDC program will light the appropriate lamp when it “sees” a responder.
Appendix d
Additional system details
1. Detailed description of the system
1.1 Changes in the programming screens
To work in a service station environment with a customer identification system (IDC), certain programming screens need to be added. An option screen that has the ability to connect and disconnect IDC functions is added as described in detail below. The ability to connect and disconnect the reader is programmed. Likewise, if the station is configured for IDC, the coupling of the antennas to the TACs terminals (Terminals activated by the client) is programmed. A diagnostic screen is added to present the status of each reader and its corresponding antenna.
1.1.1 Option screens
The aforementioned screens can be added under the Plus / 3 options menu or the Wayne Plus dealer programming menu.
The options screen will contain the station options, the reader activation screen, the antenna and TAC assignment screen, and the diagnostic screen. Each of these screens is described below. The "Reader Activation", "Antenna to TAC Assignment", and "Diagnostic" screens will not be seen if a station is not configured to handle an IDC.
ES 2 239 342 T3
1.1.2 Station Options Screen
The options screen, as shown in Table D-1 below, contains the information necessary to set up a station for IDC.
TABLE D-1
Station options screen
SpeedPass (fast pass) allowed in the station ....... YES
This screen allows the station to connect or disconnect the IDC option for the entire station. This allows stations to discontinue the IDC option in the event that a station does not want to work with IDC. “SpeedPass” or Quick Pass is a commercial reference to System 10. If the “Quick Pass allowed in the station” is set to NO, the “Reader Activation”, “Antenna to TAC Assignment”, and “Diagnostic ”Will not be seen on the options screen.
1.1.3 Reader activation screen
In this menu, a reader can be connected or disconnected. If the reader is disconnected, the four antennas connected to it will not be used. The reader activation screen is shown in Table D-2 below.
TABLE D-2
Reader activation screen
Reader 1 SpeedPass ....... CONNECTED
Reader 2 SpeedPass ....... CONNECTED
Reader 3 SpeedPass ....... DISCONNECTED
Reader 4 SpeedPass ....... CONNECTED
Switching a reader to "off" for a particular pump may be necessary if an individual reader is malfunctioning.
1.1.4 Antenna to TAC assignment screen
The screen for assigning the antennas to the TAC is shown in Table D-3 below:
TABLE D-3
Antenna to TAC assignment screen
<img file="ES2239342T3_D0001.tif" />
The Antenna to TAC Assignment screen indicates which antennas are located on which TACs. The odd-numbered antennas will be long-range antennas, read by vehicle-mounted transponders. The even-numbered antennas will be the short-range antennas, which are read by handheld responders.
If the TAC number is "0", then the antennas are not connected to a TAC, and are ignored. An example of this type of reader arrangement is for a single-sided CT, where the reader only has two antennas connected.
ES 2 239 342 T3
1.1.5 Diagnostic screen
This screen provides the status of the IDCs on the antennas, and serves as an aid in the debugging procedure. An example of this screen is shown in Table D-4 below.
TABLE D-4
Diagnostic Screen SpeedPass Diagnostics
<td>Previous reading</td><td>Vehicle Mounted IDC No.</td><td>Manual CID No.</td>
<td> 1-1/2</td><td> 1234567890123456789</td><td> 0000000000000000000</td>
<td> 1-3/4</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>Renovate</td><td></td><td></td>
1.2 Changes in network registers
1.2.1 IDC authorization request
For an IDC authorization request, an “IIDC” will be prepared for the reading of 20 digits from the responder and sent in the magnetic strip field of the authorization record.
1.2.2 IDC authorization response
For the IDC authorization response, the network will send the account number in the response record, with the following fields:
- Field 5, the type of record is set to "A", which indicates an IDC transaction
- Field 8 (new field), account number - 19 octets of number. account, space full
- Field 9 (new field), expiration date - 4 octets
- Field 10 (new field), printed receipt indicator - 1 octet
- Field 11 (new field), car wash indicator query - 1 octet
- Field 12 (new field), language indicator - 1 octet
- Field 13 (new field), award indicator - 1 octet
- Field 14 (new field), preference indicator - 1 octet
- Field 15 (new field), preference data - 40 octets
The printed receipt indicator (field 10) refers to whether the receipt will be printed automatically, or the customer will be consulted. If the answer is Yes, the receipt will be printed automatically. If the answer to the authorization is No, the customer will be asked to press Yes to obtain the receipt.
The car wash inquiry indicator. the language indicator, and the award indicator (fields 11, 12, and 13, respectively, will be implemented in a future issue.
The preference indicator (field 14) indicates whether or not the preference data field is present. The first 33 octets of the preference data field (field 15) will be displayed on the indoor console, in the pump message window.
ES 2 239 342 T3
1.2.3 Selling with IDC
To complete a sale with IDC, position no. 37 of the data on the magnetic strip will contain a “C” indicator similar to a manual entry.
1.3 Reports and records
The reporting and authorization record will change for any transaction that requires an IDC including your number. The reports that change will be the TAC Preauthorization Denied Report and the Hardware Configuration Report. The proposed changes are described below. The transaction without IDC will be reported as before, with no change in records or TAC pre-authorization report denied.
1.3.1 Registration of authorizations
The authorization record will be changed for IDC, to indicate that an IDC transaction has occurred. The IDC number will be added under the account number field in the record. An example IDC authorization record is shown below in Table D-5. Proposed changes are printed in bold type. If the transaction is an IDC pre-authorization (that is, the pre-authorization field on the card is set to Yes), the title of the authorization record will be “SP pre-authorization”.
TABLE D-5 Authorization record
051695 14:30:36 AUTHORIZATION SP Account n ° 805 086 000 91 906 Exp 0697 SP n ° IIDC 1234 5678 9012 3456 7890 Address, n ° 1 TID n ° 01 Amount $ 10.00 Message to base order: ACCORDING to pump 05000
1.3.2 IDC Denied / Timed Out
If the customer has removed the nozzle on a Vista pump, or raised the lever on a non-Vista pump, and the authorization received from the network is denied, the transaction will be treated as a denied pre-authorization, as shown in Table D- 6 next:
TABLE D-6
Pre-authorization report. TAC Denied No SpeedPass Station
Report Taker: Donna
Report X of pre-authorizations. TAC denied
Start time and date: 12:00:00 pm Tuesday, May 9, 95
Fuel ticket number 002929 05/17/95 06:05:18 Pump n ° 1
Account CR 805 086 000 91 906 File 0597 SPECIAL Grade n ° 2 Amount $ 11.78 x0006e10s01t1 04; 25: 00 pm. Wed 24 May 95
The modified TAC Denied Preauthorization Report will include the IDC numbers, as shown in bold in Table D-7 below.
ES 2 239 342 T3
TABLE D-7
Pre-authorization report. TAC Denied Modified, with SpeedPass
Station
Report Taker: Donna
Report X of pre-authorizations. TAC denied
Start time and date: 12:00:00 pm Tuesday, May 9, 95
Fuel ticket number 002929 05/17/95 06:05:18 Pump n ° 1
Account CR 805 086 000 91 906 Exp. 0597 SP n ° 1IDC 1234 5678 9012 3456 7890 SPECIAL Grade n ° 02 Amount $ 11.78 x0006e10s01t1 04:25:00 pm Wed 24 May 95
If a customer has removed the nozzle (Vista pump) or raised the lever (non-Vista pump), and the network is paralyzed before receiving the authorization response, the transaction will be treated as a TAC pre-authorization denied (the report is displayed in Table D-8 below). The account number and expiration time data fields will be printed with zeros, to indicate that it has occurred outside the period to receive the authorization (that is, there is no account information available at that time).
TABLE D-8
TAC pre-authorization report with SpeedPass and no authorization response
Station
Report Taker: Donna
Report X of pre-authorizations. TAC denied
Start time and date: 12:00:00 pm Tuesday, May 9, 95
Fuel ticket number 003131 05/17/95 06:05:18 Pump n ° 1
Account n ° 000 000 000 00 000 Exp. 0000 SP n ° 1IDC 1234 5678 9012 3456 7890 SPECIAL Grade n ° 02 Amount $ 11.78 x0006e10s01t1 04:25:00 pm Wed 24 May 95
1.3.3 Physical equipment configuration report
The hardware configuration report will change to include IDC reader signature review information. A sample of such a report appears in Table D-9 below.
ES 2 239 342 T3
TABLE D-9
Report on the configuration of the modified physical equipment, with SpeedPass
Station
Report Taker: Donna
POS.CPU physical equipment configuration report:
Wayne Plus / 2. Issue 2.10e Date: March 23, 1995
PUMP 1:
Type: 3 products REVIEW: 15
PUMP 2:
Type: 3 products REVIEW: 15
SPEEDPASS READER 1: REVIEW: 1.23 x000E04S0IT1 08:00:00 am Mon May 1 95
1.4 Changes in the presentation of the TAC
If the TAC light is on and the IDC is available, the TAC displays the indication “Start refueling or cancel SpeedPass”, indicating that an IDC has been read from the TAC and the nozzle has not been removed or the lever has not been raised, so the customer can press the cancel key to cancel the payment method through the IDC. The TAC will ask the customer "Cancel the use of SpeedPass?" (Y / N) ?. If Yes is pressed, the IDC light turns off, and the TAC displays the normal available message (for example, “Insert a card, or start refueling”). If you press NO, the TAC will display the message “Start refueling or Cancel SpeedPass”, and the actions will continue as if the cancel key had never been pressed (ie the transaction via the IDC).
Table D-10 below describes the queries available if an IDC has been read.
TABLE D-10
Changes in the consultations available in the TAC
Station operation
Viewing available *
New visualization available<sup>1</sup>
Subsequent payment Insert card or start refueling Start refueling or cancel SpeedPass
Post payment / Inact network Refuel first and then pay within Inact network. Press cancel.
Post payment with charge Insert taij / payment box or remove nozzle on account
Pay per charge in Refuel first and then pay within inact account / Network
Start refueling or cancel SpeedPass Red inact. Pres. Channel
Advance payment
Insert) or pay at the cashier
Start refueling or cancel SpeedPass
ES 2 239 342 T3
<td>Previous payment / Inactive network.</td><td>Pay at the till before refueling</td><td>Network inact. Press cancel</td>
<td>Previous payment with account charge</td><td>Insert card or pay at the cashier</td><td>Start refueling or cancel SpeedPass</td>
<td>Payment prev account / Network inact charge</td><td>Insert.taij or pay at the cash register</td><td>Network inact. Press cancel</td>
<td>Full service<sup>1</sup></td><td>Taij. nozzle, or prior arrangement 0.00</td><td>Taij. Nozzle, or prior arrangement 0.00</td>
<td>Full service / Network inactive.<sup>1</sup></td><td>Remove.nozzle, or prior agreement 0.00</td><td>Remove nozzle, or prior agreement 0.00</td>
<td>Serv. full with charge on account<sup>1</sup></td><td>Card, box, mouthpiece or previous agreement 0.00</td><td>Taij, box, nozzle. Or prior arrangement 0.00</td>
<td>Compl.serv with cc Network inactive<sup>1</sup></td><td>Box, mouth. or here. previous 0.00</td><td>Box, mouth or here. previous 0.00</td>
<td>Without attention</td><td>Insert card</td><td>Start refueling or cancel. SpeedPass</td>
<td>No attention, with a charge</td><td>Insert card or pay at the cashier</td><td>Yo hice</td>
<td>Without attention, with charge in c. Network inac.</td><td>Insert payment at checkout</td><td>Network inact. Press cancel</td>
* Consultations available
Queries to be used if the station is configured for IDC, and the responder has read said IDC
Consultations available in full service mode will not change
two. Additional characteristics
2.1 Use of multiple responder
A responder can be used on more than one pump at a time. An alert system has been put in place to inform the teller that a responder is currently being used for an IDC sale on one pump, and another sale is starting on another pump using the same IDC. A report message is displayed on the POS for the second use of the IDC when the nozzle is removed from a Vista pump, or when the lever is lifted on a non-Vista pump. The cashier is asked to acknowledge receipt of the message. The client is not interrupted in any way in the use of this responder in a multiple use case. If the cashier does not want the customer to use the responder in this way, they stop the pump or notify the customer.
The message displayed on the interior POS is "IDC on TAC # X also in use on TAC # Y". The cashier presses the acknowledgment key. A registration error message "IDC in use on another TAC" may also be displayed.
ES 2 239 342 T3
2.2 Prize indicator
The authorization response received from the base computer contains a prize indication field. If this field contains an "S", then the IDC light will remain on until the IDC is indicated that it has been read. When the light is in blinking mode, it is not an indication that an IDC is no longer in the reading field; If the nozzle is removed from a Vista pump, or lifted from a non-Vista pump, when the light is off during this flashing mode, the sale is a transaction with IDC.
2.3 Blank reading threshold
The station options screen has been modified to include a programmable blank reading threshold, as shown in Table D-11 below. This field is used to help eliminate false IDC reads. These blank reads can occur while the IDC is momentarily in range. This option allows the programming of a consecutive number of blanks that record that the IDC has drifted out of the reading field. The IDC light will not be turned off for a received IDC until the threshold of consecutive blank reads is reached.
TABLE D-11
Modified Station Options Screen Station SpeedPass Options
SpeedPass allowed in the Station ....... YES
Blank IDC reads required to indicate no IDC ....... 5
2.4 IDC Light Operation for Received and Denied IDC Authorization
For received IDCs, the IDC light will be turned off if an authorization denied is received from the base computer. The light will not be turned on again after the nozzle is reset for that IDC received.
3. Miscellaneous additional features
The following concepts can also be put into practice:
- Use of car wash preference
- Use of indoor responders
- Car wash connection
- Presentation of an award at the TAC (Customer Terminal) during the refueling operation.
- Blink "P" for customer preferences displayed on the console.
- Use of the language indicator.
- Shop with discounts and credit.
Contents51
32 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31 Sheet 32
41 members in 23 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 19950009369P | United States of America | – | |
| 936995 | United States of America | P |
Members41
| Document | Office | Kind | |
|---|---|---|---|
| CA2240174A1 | Canada | A1 | |
| WO9724689A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU1432797A | Australia | A | |
| TR199801246T2 | Türkiye | T2 | |
| MX9805285A | Mexico | A | |
| CZ207098A3 | Czechia | A3 | |
| SI9620132A | Slovenia | A | |
| PL328941A1 | Poland | A1 | |
| EP0906598A1 | European Patent Office (EPO) | A1 | |
| EP0906598A4 | European Patent Office (EPO) | A4 | |
| JPH11508714A | Japan | A | |
| HU9901163A2 | Hungary | A2 | |
| HUP9901163A2 | Hungary | A2 | |
| CN1229491A | China | A | |
| BR9612333A | Brazil | A | |
| HU9901163A3 | Hungary | A3 | |
| HUP9901163A3 | Hungary | A3 | |
| NZ326243A | New Zealand | A | |
| HK1022024A1 | Hong Kong, China | A1 | |
| RU2161329C2 | Russian Federation | C2 | |
| AU733869B2 | Australia | B2 | |
| AP981A | African Regional Intellectual Property Organization (ARIPO) | A | |
| AU6549401A | Australia | A | |
| OA10801A | African Intellectual Property Organization (OAPI) | A | |
| PL183486B1 | Poland | B1 | |
| AU757073B2 | Australia | B2 | |
| JP3481254B2 | Japan | B2 | |
| HU223023B1 | Hungary | B1 | |
| EP0906598B1 | European Patent Office (EPO) | B1 | |
| AT290705T | Austria | T | |
| ATE290705T1 | Austria | T1 | |
| DE69634452D1 | Germany | D1 | |
| PT906598E | Portugal | E | |
| ES2239342T3This record | Spain | T3 | |
| CN1242362C | China | C | |
| SI9620132B | Slovenia | B | |
| DE69634452T2 | Germany | T2 | |
| CZ298081B6 | Czechia | B6 | |
| BR9612333B1 | Brazil | B1 | |
| CA2240174C | Canada | C | |
| US7640185B1 | United States of America | B1 |
Numbers
- Publication
- 2239342
- Application
- 96945125
Titles2
- Spanish
- SISTEMA DISPENSADOR Y METODO DE IDENTIFICACION DE CLIENTE CON RADIO FRECUENCIA.
- English
- DISPENSING SYSTEM AND CLIENT IDENTIFICATION METHOD WITH FREQUENCY RADIO.
Classification
- CPC, 6
- G07F7/0866
- G06Q20/342
- G06Q20/363
- G07C5/008
- G07F7/025
- G07F13/025
- IPC, 10
- G07F7 00
- B67D7 24
- B67D7 32
- G06Q30 06
- G07C5 00
- G07F7 02
- G07F7 08
- G07F13 02
- H04B1 59
- H04W12 00